Enabling on-demand priority messaging services

Abstract

Methods for priority messaging implemented in a user equipment (UE)are described. The method can include receiving, from a core network (CN) via a radio access network (RAN), an indication that priority treatment is enabled for an access identity (AID) corresponding to a priority messaging service (PMS) for a third-party user. The method can further include establishing, with the RAN, a radio connection for the PMS. Other methods and apparatuses for performing these methods are also described.

Description

PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00ENABLING ON-DEMAND PRIORITY MESSAGING SERVICES

[0001] CROSS-REFERENCE TO RELATED APPLICATIONSThis application claims priority to and the benefit of the filing date of provisional U.S. Patent Application No. 63 / 718,539 entitled “Enabling On-Demand Priority Messaging Services,” filed on November 8, 2024. The entire contents of the provisional application are hereby expressly incorporated herein by reference.FIELD OF THE DISCLOSURE

[0001] This disclosure relates generally to wireless communication systems, and particularly to enabling on-demand priority messaging services for third parties.BACKGROUND

[0002] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0003] Responses to emergency situations (e.g. floods, hurricanes, earthquakes, etc.) depend, to a large extent, on the capabilities of public communication 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 authorized users must 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. 3GPP introduced Multimedia Priority Service (MPS) to address these and other scenarios MPS provides 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. MPS enables National Security or Emergency Preparedness subscribers to make priority calls or data sessions on a Service Providers network at times of congestion. Service Users can be government-authorized personnel, emergency management officials and / or otherPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 authorized users, although Service Users are not always restricted to being human users of a service (e.g., in the case of Internet of Things (loT), a Service User could be a specialized application using MPS through machine interactions that may not directly involved a human Service User). Both Evolved Packet System (EPS) and 5G systems can support MPS.

[0004] MPS allows qualified and authorized users to obtain priority access to the next available radio channel on a priority basis before other public land mobile network (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 priority mechanisms can be classified as subscription-related and invocation-related. Subscription related mechanisms are divided into those that always apply and those that apply conditionally. Invocation -related mechanisms are divided into a category for mobile originated SIP call / sessions, a category for mobile terminated SIP call / sessions, and a category for Priority PDU connectivity services. 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.

[0005] Messaging services have been fundamental 3 GPP services for UEs and loT devices in consumer markets for decades. Due to their lightweight nature, efficiency, and reliability, messaging services are essential for communication. An authorized Service User may use a UE with an MPS for messaging subscription. In at least these scenarios, the MPS subscription related information is associated with the UE’s home public land mobile network HPLMN) subscription. The MPS subscription related information can be stored in the UE and the HPLMN, or only in the HPLMN. However, it is unclear how the 3GPP system provides differential treatment for a UE based on whether the UE is associated with a Service User or with a third-party user.

[0006] In some cases, an authorized Service User may use a UE that does not have an MPS for messaging subscription. In at least these cases, the Service User’s MPS subscription informationPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00(e.g., credentials) is not associated with the UE’s HPLMN subscription. For example, the Service User may be using a borrowed UE that does not have an MPS subscription. In this case, it is unclear how the 5GS is to authorize a third-party user using Priority Messaging Services (PMS).

[0007] Furthermore, it may be desirable to enhance 5GS to support MPS for IMS Messaging and SMS services including SMS over NAS and SMS over IP. However, current solutions in the field provided by third-party service providers utilize Over-The-Top (OTT) messaging for specific urgent events. These solutions employ methods such as SMS over NAS, SMS over IP, or non-lP data delivery (NlDD)-based messaging for UEs using normal sessions over the 3GPP system or for proprietary devices using non-3GPP compliant access. These solutions lack standardized priority treatment within the 3GPP system, which limits the effectiveness of these solutions in delivering urgent messages promptly. Enabling priority treatment for third-party users using legacy messaging services, including SMS and NIDD-based messaging can greatly enhance the availability of messaging services for urgent events. This can potentially save lives in urgent situations. However, the priority treatment for the third-party user using the commercial OTT messaging should not supersede the priority for the Service Users (granted and assigned by regional / national authority) and the emergency calls in periods of network congestion during which normal commercial messaging services are degraded. It is not clear how to support OTT messaging services with proper priority treatment as well as access control.

[0008] Furthermore, an authorized third-party user may, in some cases, use a UE with a stored PMS subscription in the USIM. However, in an on-demand PMS scenario, a third-party service provider can request an operator’s network to enable a PMS subscription for a UE associated with a third-party user. In this case, the UE may not be configured with a PMS subscription in the USIM. It is unclear how to enable on-demand PMS.SUMMARY

[0009] An example embodiment of the techniques of this disclosure is a method for priority messaging implemented in a user equipment (UE). The method can comprise receiving, from aPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 core network (CN) via a radio access network (RAN), an indication that priority treatment is enabled for an access identity (AID) corresponding to a priority messaging service (PMS) for a third-party user; and establishing, with the RAN, a radio connection for the PMS.

[0010] Another example embodiment of these techniques is a UE comprising a transceiver and processing hardware to implement the method above.

[0011] Another example embodiment of these techniques is a RAN node comprising a transceiver, and processing hardware. The RAN node is configured to implement the method above.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate one or more embodiments and, together with the detailed description, explain these embodiments.

[0013] Fig. l is a block diagram of an example wireless communication system in which a user equipment (UE)and a base station can support priority services using the techniques of this disclosure;

[0014] Fig. 2 is a block diagram of an example protocol stack according to which the UE of Fig. 1 A communicates with a base station and a core network;

[0015] Fig. 3 is a service-based representation of the 5GS architecture;

[0016] Fig. 4 is a reference-point based representation of the 5GS architecture, including overall non-roaming reference architecture of the policy and charging control framework for the 5GS;

[0017] Fig. 5 is a flow diagram of an example method in a UE for access control;

[0018] Fig. 6 is a messaging diagram of a third-party Application Function (AF) provisioning network configuration parameters;

[0019] Fig. 7 is a messaging diagram illustrating priority treatment for messaging services in a 3GPP system based on an MPS service;PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00

[0020] Fig. 8 is a messaging diagram illustrating enablement of extended MPS for messaging services;

[0021] Fig. 9 is a messaging diagram illustrating message flows for PMS; and

[0022] Fig. 10 is a flow diagram of a method for priority messaging implemented in a UE.DETAILED DESCRIPTION OF THE DRAWINGSOverview

[0023] As discussed in more detail below, a user equipment (UE) and / or a network node of a radio access network (RAN) or a core network (CN) can use the techniques of this disclosure to provide Priority Messaging Services (PMS) subscription information from a third-party service provider to a network to enable PMS for a UE. PMS can alternatively or additionally be referred as Express Messaging Services or Expedited Messaging Services, A UE, RAN node or CN can use other techniques of the disclosure to provide and receive PMS subscription information for the authorized UE or loT device. The PMS subscription information can provide differentiation to existing priority messaging services provided by the operator’s network subject to regulation requirements and operator policy. Still further, a UE and network can use messaging described herein to perform authentication and authorization for UE PMS during an urgent event. In addition, network nodes can use methods described herein to perform access barring control, during periods of high network congestion, to the UE using MPS messaging for a Service User or to the UE using PMS for a third-party user.

[0024] The present disclosure further describes priority treatment for messaging services in 3GPP systems based on an MPS service. For example, aspects of the present disclosure provide enhancements to MPS for messaging (MPS4msg). MPS4msg enables authorized users to send and receive priority messages using SMS over NAS, SMS over IP, IMS messaging, and NIDD- based messaging during periods of network congestion when normal commercial messaging services may be degraded. Unlike traditional MPS which is limited to government-authorized Service Users, MPS4msg can be extended to support third-party users through commercialPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 arrangements with network operators, while ensuring that Service Users maintain higher priority levels than third-party users.

[0025] NB-IoT and eMTC technologies, which are suitable for loT devices operating in remote areas with limited or no terrestrial connectivity, may also use MPS services. Such loT devices can be used in a variety of industries including, for example transportation (maritime, road, rail, air) and logistics; solar, oil, and gas harvesting; utilities; farming; environmental monitoring; and mining. However, to ensure the required loT connectivity, deployment of these technologies requires satellite connectivity to provide coverage beyond terrestrial deployments. Satellite NB-IoT or eMTC is defined in a complementary manner to terrestrial deployments.

[0026] Aspects of the disclosure are applicable for both EPS and 5GS, and for a UE or loT device. Furthermore, aspects of the present disclosure are applicable for all 3GPP RATs (including RAT for TN and RATs for NTN for satellite access, or non-3GPP RAT). In addition, features of the present disclosure described with relation to network functions (AMF, SMF, NEF, AF) can be enhanced for the corresponding features of the entities (MME, SGW, SCEF, SCS) in the EPS (TS23.682). Also, the described registration request procedure, PDU Session Establishment request procedure, and other procedures in 5GS can be enhanced for the corresponding procedures (attach procedure, Default / Dedicated Bearer Activation Procedure) in EPS.Systems

[0027] Referring first to Fig. 1, an example wireless communication system 100 includes a UE 102, a base station (BS) 104, a base station 106, and a core network (CN) 110. In some implementations, the base stations 104 and 106 can operate in a RAN 105 connected to the core network (CN) 110. The base station 104 and / or base station 106 may provide coverage (e.g., one or more cells) via a satellite. In such cases, the RAN 105 is a non-terrestrial network (NTN). In other implementations, the base station 104 and / or base station 106 provide coverage (e.g., one or more cells) via antennas on the ground. In such cases, the RAN 105 is a terrestrial network (TN). In some implementations, the RAN 105 can be an NTN and a TN. For example, the basePATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 station 104 provides coverage via a satellite while the base station 106 provides coverage via antennas on the ground. In another example, the base station 104 provides a cell via antennas on the ground while provides another cell via satellite.

[0028] The base station 104 covers a cell 124, and the base station 106 covers a cell 126. If the base station 104 is a gNB, the cell 124 is an NR. cell. If the base station 104 is an eNB, the cell 124 is an Evolved Universal Terrestrial Radio Access (E-UTRA) cell or a Narrow Band Internet of Things (NB-IoT) cell. If the base station 104 is a 6G base station, the cell 124 is a 6G cell or a 6G Internet of Things (6G-I0T) cell. Similarly, the cell 126 is an NR cell, a E-UTRA or NB-loT cell, a 6G or 6G-I0T cell, depending on the base station is a gNB, an ng-eNB or eNB, or a 6G baes station. The cells 124 and 126 can be in the same Radio Access Network Notification Areas (RNA) or different RNAs. In general, the RAN 105 can include any number of base stations, and each of the base stations can cover one, two, three, or any other suitable number of cells. The UE 102 can support at least one of a 6G, 5G NR (or simply, “NR”), E-UTRA and / or NB-IoT air interface to communicate with the base station 104 or 106. Each of the base stations 104 and 106 can connect to the CN 110 via an interface (e.g., SI, NG, N6G interface). The base stations 104 and 106 also can be interconnected via an interface (e.g., X2, Xn, or X6G interface).

[0029] NB-loT provides access to network services using physical layer optimized for very low power consumption (e.g., full carrier bandwidth is 180 kHz, subcarrier spacing can be 3.75 kHz or 15 kHz). Unlike 6G, NR and E-UTRA, a number of functions, such as inter-RAT mobility, handover, measurement reports, public warning functions, Guaranteed Bit Rate (GBR), carrier aggregation, multi-radio dual connectivity, real-time services, interference avoidance for in-device coexistence, minimization of drive test (MDT), emergency call, Circuit Switched (CS) fallback, access barring, and / or RRC INACTIVE, are not supported for NB-IoT. Similar functionalities may not be supported for 6G loT.

[0030] The CN 110 can be implemented as an evolved packet core (EPC) 111 or a fifth generation (5G) core (5GC) 160, for example. The CN 110 can also be implemented as a sixth generation (6G) core 180, in another example. Among other components, the EPC 111 can include a Serving Gateway (SGW) 112, a Mobility Management Entity (MME) 114, and a Packet Data Network Gateway (PGW) 116. The SGW 112 in general is configured to transferPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 user-plane packets related to audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, security activation, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE to one or more external packet data networks, e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network. The 5GC 160 includes a User Plane Function (UPF) 162 and an Access and Mobility Management Function (AMF) 164, and / or Session Management Function (SMF) 166. Generally speaking, the UPF 162 is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc., the AMF 164 is configured to manage authentication, security activation, registration, paging, and other related functions, and the SMF 166 is configured to manage PDU sessions. The 6GC 180 includes a 6G UPF 182 and a 6G AMF 184, and / or 6G SMF 186, similar to the UPF 162, the AMF 164 and the SMF 166 with enhanced functions respectively. In some implementations, the NR RAN 105 connects to the 6GC 180. In other implementations, the 6G RAN 105 connects to the 5GC 160.

[0031] The CN 110 may connect to a short message service center (SMSC) 170 directly or via one or more other network nodes to provide short message services (SMS) via a control plane function or a user plane function. In some implementations, to support SMS via the control plane function, the MME 114 may connect to a SMS-Gateway Mobile Switching Center (SMS- GMSC) (not shown in Fig. 1) and the SMS-GMSC connects to the SMSC 170. In other implementations, the MME 114 may connect to the SMSC 170 directly, i.e., via an interface. In some implementations, to support SMS (i.e., IMS SMS) via the user plane function, the SGW 112 or PGW 116 connects to an IMS network (not shown in Fig. 1), the IMS network connects to an Internet Protocol (IP) short message gateway (IP-SM-GW), and the IP-SM-GW connects to the SMSC. In some implementations, to support SMS via the control plane function, the AMF 164, 184 may connect to a short message service function (SMSF) (not shown in Fig. 1) and the SMSF connects to the SMSC 170. In other implementations, to support SMS (i.e., IMS SMS) via the user plane function, the UPF 162,182 connects to an IMS network (not shown in Fig. 1), the IMS network connects to the SMSF, and the SMSF connects to the SMSC 170. The IMS network may include one or more Call Session Control Function (CSCF) nodes such as Interrogating CSCF, Proxy CSCF, and / or Serving CSCF.PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00

[0032] The CN 110 may connect to a Home Subscriber Server (HSS) or a Unified Data Management (UDM) 172 directly or via one or more other network nodes. In some implementations, the MME 114 connects to the HSS 172 via an interface. In other implementations, the AMF 164 and 184 connects to the UDM 172 via an interface. In yet other implementations, the SMF 166, 186, connects to the UDM 172 via an interface. The HSS / UDM 172 may connect to the SMSC 170 via an interface. A third-party application 157 may be associated with a UE for accessing priority, expedited or express services as described herein.

[0033] The base station 104 supports a cell 124, and the base station 106 supports a cell 126. If the cell 124 is an NTN cell, that cell 124 has a shape corresponding to the footprint of the satellite beams, which unlike cell 126, can project on different areas at different times. The cells 124 and 126 can partially overlap, so that the UE 102 can select, reselect, or hand over from one of the cells 124 and 126 to the other. To directly exchange messages or information, the base station 104 and base station 106 can support an X2, Xn or X6G interface. In general, the CN 110 can connect to any suitable number of base stations supporting 6G cells, 6G-I0T cells, NR cells, EUTRA cells, and / or NB-IoT cells.

[0034] The base station 104 is equipped with processing hardware 130 that can include one or more general -purpose processors (e.g., CPUs) and a non-transitory computer-readable memory (CRM) storing instructions that the one or more general -purpose processors execute.Additionally, or alternatively, the processing hardware 130 can include special-purpose processing units. According to an embodiment illustrated in Fig. 1, the processing hardware 130 includes a processor 132 to process data that the base station 104 will transmit in the downlink direction, or data received by the base station 104 in the uplink direction. The processing hardware 130 also includes a transceiver 134 configured to transmit data in the downlink direction and to receive data in the uplink direction. The processing hardware 130 can include a memory storing executable codes for the processor 132 to perform methods according to embodiments described in this section. The processing hardware 130 can implement, among other components, an access control controller 136 that implements some or all of the techniques for supporting on-demand priority messaging services for third parties, as discussed below.PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00

[0035] The base station 106 can include generally similar components. In particular, components 140, 142, 144, and 146 of the base station 106 can be similar to the components 130, 132, 134, and 136 respectively.

[0036] The UE 102 is equipped with processing hardware 150 that can include one or more general-purpose processors such as CPUs and non-transitory computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or special-purpose processing units. The processing hardware 150 in an example implementation includes a processor 152 to process data that the UE 102 will transmit in the uplink direction, or process data received by UE 102 in the downlink direction. The processing hardware 150 can also include a transceiver 154 configured to transmit data in the downlink direction and to receive data in the uplink direction. The processing hardware 150 can implement, among other components, an access control controller 156 to apply access control and a service controller 158 to control priority and non-priority services, for example.

[0037] Fig. 2 illustrates, in a simplified manner, an example protocol stack 200 according to which the UE 102 can communicate with a 6G gNB, an eNB / ng-eNB or a gNB (e.g., one or more of the base stations 104, 106).

[0038] In the example stack 200, a physical (PHY) layer 202 provides transport channels to a MAC sublayer 204, which in turn provides logical channels to a RLC sublayer 206. The RLC sublayer 206 in turn provides RLC channels to a PDCP sublayer 208. The PDCP sublayer 208 in turn can provide data transfer services to a radio resource control (RRC) sublayer 210, an Internet Protocol (IP) layer and / or a Service Data Adaptation Protocol (SDAP) sublayer (not shown in Fig. 2). The PDCP sublayer 208 receives packets (e.g., from the RRC sublayer 210, the SDAP sublayer, or the IP layer, layered directly or indirectly over the PDCP layer 208) that can be referred to as service data units (SDUs), and output packets (e.g., to the RLC layer 206) that can be referred to as protocol data units (PDUs). Except where the difference between SDUs and PDUs is relevant, this disclosure for simplicity refers to both SDUs and PDUs as “packets”. In some implementations, the PHY layer 202, MAC sublayer 204, RLC sublayer 206, PDCP sublayer 208, RRC sublayer 210 are EUTRA layers or sublayers. In other implementations, thePATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00PHY layer 202, MAC sublayer 204, RLC sublayer 206, PDCP sublayer 208, RRC sublayer 210 are NR layers or sublayers.

[0039] The RRC sublayer 210 provides data transfer services to a Non-Access-Stratum (NAS) layer 212. The NAS layer 212 includes a mobility management (MM) sublayer and / or a session management (SM) sublayer. In some implementations, the MM sublayer is an EPS MM (EMM) sublayer, a 5G MM (5GMM) sublayer or a 6G MM (6GMM) sublayer. In some implementations, the SM sublayer is an EPS SM (ESM) sublayer, a 5G SM (5GSM) sublayer or a 6G SM (6GSM) sublayer.

[0040] On a control plane, the PDCP sublayer 208 can provide signaling radio bearers (SRBs) to the RRC sublayer 210 to exchange RRC messages or NAS messages (e.g., MM messages and / or SM messages), for example. On a user plane, the PDCP sublayer 208 can provide Data Radio Bearers (DRBs) to support user plane data exchange. User plane data exchanged on the PDCP sublayer 208 can be SDAP PDUs, Internet Protocol (IP) packets or Ethernet packets.

[0041] Fig. 3 is a service-based representation 300 of the 5GS architecture, which the system of Fig. 1 can implement. In the representation 300, the overall non-roaming reference architecture of the policy and charging control (PCC) framework for the 5GS includes components illustrated using solid lines, and the other components are illustrated using dashed lines. According to this representation, network functions enable other authorized network functions to access their services. The components that are outside the PCC framework include a Network Slicing Selection Function (NSSF) 302, a Network Repository Function (NRF) 306, a Unified Data Management (UDM) 308, an Edge Application Server Discovery Function (EASDF) 310, a Network Slice Specific Authentication and Authorization Function (NSAAF) 312, an Authentication Server Function (AUSF) 314, a Service Communication Proxy (SCP) 316, and a Network Slice Admission Control Function (NSACF) 318. The non-PCC architecture further includes the UE 102, the RAN 105, and a data network (DN) 330. An application server (AS) 33 loperates in the DN 330.

[0042] The PCC framework in the architecture 300 includes a Unified Data Repository (UDR) 352, a Network Exposure Function (NEF) 354, a network data analytics function (NWDAF) 356,PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 an Application Function (AF) 358, a Policy Control Function (PCF) 360, a Charging Function (CHF) 362, an Access & Mobility Management Function (AMF) 364, a Session Management Function (SMF) 366, and a User Plane Function (UPF) 370. In aspects of the present disclosure, the architecture 300 supports PMS activation when other normal commercial messaging service is congested. With respect to charging aspects, a network supporting PMS records the following charging information, in addition to non-PMS information: a.) PMS invocation attempt and successful session set-up; b.) Originations and / or terminations Session on which PMS was used to gain access to resources; c.) Recording of PMS information, e.g., priority level; and d.) PMS related events on which messaging service was used and by which authorized third-party user. The system or architecture 300 associates PMS related charging events with an authorized third- party service operator for its authorized third-party user using a UE or loT device that may not have an PMS subscription, in which case the third-party service provider sponsors the PMS usage for their third-party users to the operator.

[0043] Fig. 4 is a reference-point based representation 400 of the 5GS architecture. In Fig. 4, the non-roaming reference architecture of the PCC framework for the 5GS is illustrated as blocks and connections with solid lines, and components and connections outside the PCC framework are illustrated using dashed lines.Messaging services may be used in any of the above systems or networks in situations such as natural disasters, public safety incidents, and health crises, which are often subject to regulation requirements and operator policies. However, there is a lack of standardized priority treatment within 3GPP system which limits their effectiveness in delivering urgent messages promptly. This is particularly problematic for third-party users that rely on these services from third party service providers, especially during urgent events. Without proper integration with the 3GPP system, messages may experience delays or fail to reach their intended recipients, hindering timely delivery between the UE and the OTT application server.Enabling on-demand priority messaging services

[0044] Methods and systems provide solutions to address these and other concerns.PATENT APPLICATION Attorney Docket No.: 31730 / 308600-00

[0045] Methods and systems according to one aspect of the present disclosure specify UE behavior 500 for access control checks as shown in Fig. 5. Referring to Fig. 5, a UE without a PMS subscription stored in the USIM performs 502 a registration request procedure. In an alternative aspect, the network initiates a UE configuration update procedure. The UE receives configuration parameters for priority messaging (e.g., a Registration Accept message or a UE Configuration Update command message) from the network. The UE stores the configuration parameters of priority messaging in the UE context.

[0046] The UE receives 504, from a third-party user, an upper layer request for priority treatment of a messaging service using SMS or NIDD-based messaging. The UE determines 506 access identities and access attempts for the upper layer request and performs an access control check based on a received System Information Block Type 1, which the network configures and broadcasts on the cell. The SIB1 contains the uac-Barringlnfo IE with the desired access barring parameters according to Access Control Information in SIB 1 : uac-Barringlnfo SEQUENCE { uac-BarringForCommon UAC-BarringPerCatList OPTIONAL, — Need S uac-BarringPerPLMN-List UAC-BarringPerPLMN-List OPTIONAL, — Need S uac-BarringlnfoSetList UAC-BarringlnfoSetList, uac-AccessCategoryl-SelectionAssistancelnfo CHOICE { plmnCommon UAC-AccessCategoiyl-SelectionAssistancelnfo, individualPLMNList SEQUENCE (SIZE (2..maxPLMN)) OF UAC-AccessCategory l-SelectionAssistancelnfo

[0047] The unified access control framework is 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). In the context of examples of the present disclosure , a "new session request" in RRC Connected refers to events, e.g. a new multimedia telephony (MMTEL) voice or video session, sending of SMS (SMS over IP, or SMS over NAS), sending of an NIDD-based message, sending of IP Multimedia Subsystem (IMS) registration related signaling, new PDU session establishment,PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 existing PDU session modification, and service requests to re-establish the user plane for an existing PDU session.

[0048] The UE determines 508 whether to allow access to the network based on one or more access identities and access categories with further reference and consideration to the received uac-Barringlnfo.

[0049] If the access attempt is allowed, the UE accesses 510 the network by initiating an RRC connection by transmitting, to the network, an RRCSetupRequest message. The RRCSetupRequest message can include: (i) an Establishmentcause IE, which informs the network about the reason for the connection request based on the determined Access Identity; and (ii) a NAS container IE including a NAS signaling message, e.g., UL NAS Transport message. The NAS container IE may include: (a) payload for delivery of SMS or NIDD-based messaging, or (b) a PDU Session Establishment request message to establish an NEF / UPF anchored PDU Session for NIDD-based messaging.

[0050] If the access attempt is barred, the UE may wait for a specified duration defined by uac-BarringTime before attempting to connect again, after which the UE may to operation 508. Alternatively, the UE may perform cell reselection and / or network reselection for another network and proceed to operation 502.

[0051] In another aspect of the present disclosure, illustrated in Fig. 6, a third-party AF can provide configuration parameters to request priority treatment for messaging services in a 3GPP system. This procedure is enhanced for priority messaging using SMS- or NIDD-based messaging for third party users using a UE subscribed to priority messaging based on TS23.502 clause 4.15.6.2 (“NEF service operations information flow”).

[0052] As shown in Fig. 6, a Network Function, e.g. AMF 364, can request 600 to subscribe to a UDM service for notification of subscription changes. The AF 358 provides 602, to the NEF 354, one or more parameter(s) for a target UE to be created (using an Nnef ParameterProvision Create message), updated (using an Nnef ParameterProvision Update message), or deleted (using anNnef ParameterProvision Delete Request) to the NEF 354. The AF 358 may identify the targetPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00UE using a UE identifier (e.g. GPSI or External Group ID.) The NEF 354 checks whether the requestor is allowed to perform the requested service operation by checking the requestor’s identifier (i.e., the AF Identifier of the third party’s AF).

[0053] The payload of the Nnef ParameterProvision Update Request includes one or more of the following network configuration parameters for messaging service with priority treatment. First, the parameters can include Network Configuration parameters described later herein with reference to Figures 7-9. Other parameters can include AF-provided application server address Configuration Information for handling SMS and NIDD-based messaging from the 3GPP network. Parameters can also include a DNN and an S-NSSAI of the priority messaging using NIDD based messaging (which can be used in operator defined access category as indicated later herein). As a fourth example, parameters can include a Validity Time associated with any of the Network Configuration parameters. When the validity time expires, the related NFs delete their local copy of the associated Network Configuration parameter(s).

[0054] If the NEF 354 authorizes the AF 358 to provision the parameters, the NEF 354 requests 604 to create, update and store, or delete the provisioned parameters as part of the subscriber data in the UDM 308 (using, e.g., the Nudm_ParameterProvision_Create, Nudm ParameterProvision Update or Nudm ParameterProvision Delete Request messages described earlier herein). The message can include the data provided in operation 602 and optionally third-party service provider information. If the AF 358 is not authorized to provision the parameters, then the NEF 354 continues 612 by indicating the reason for failure in an Nnef_ParameterProvision_Create / Update / Delete Response message.

[0055] The UDM 308 may read 606, from the UDR 352 (using, e.g., an Nudr_DM_Query message), corresponding subscription information to validate required data updates and authorize these changes for this subscriber or Group for the corresponding AF 358. For non-roaming cases and when no authorization or validation by the UDM 308 is required, the NEF 354 can forward the external parameter to the UDR via an Nudr DM Update Request message. For such nonroaming cases not requiring authorization or validation, the UDR 352 responds to the NEF 354 via an Nudr_DM_Update Response message. If the AF 358 is authorized by the UDM 308 to provision the parameters for this subscriber, the UDM 308 resolves the GPSI to SUPI andPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 requests to create, update or delete the provisioned parameters as part of the subscriber data via an Nudr_DM_Create / Update / Delete Request message, wherein the message includes the provisioned data. The UDR 352 stores the provisioned data as part of the UE and / or Group subscription data and responds with an Nudr DM Create / Update / Delete Response message.

[0056] If the AF 358 is not authorized to provision the parameters, then the UDM 308 continues 610 by indicating the reason for failure in an Nudm ParameterProvision Update Response message and operation 612 is not executed. The UDM 308 classifies the received parameters into AMF-associated and SMF-associated parameters. The UDM 308 may use the AF Identifier received 604 from the NEF 354 to relate the received parameter with a particular subscribed DNN and / or S-NSSAI. The UDM 308 stores the SMF-Associated parameters under a corresponding Session Management Subscription data type. Each parameter or parameter set may be associated with a validity time. The validity time is stored at the UDM / UDR 308 / 352 and in each of the NFs, to which parameters are provisioned (e.g., in the AMF or SMF). Upon expiration of the validity time, each node deletes the parameters autonomously without explicit signaling.

[0057] The UDM 308 responds 610 to the request with an Nudm ParameterProvision Create / Update / Delete Response. If the procedure failed, the cause value indicates the reason. The NEF 354 responds 612 to the request with an Nnef ParameterProvision Create / Update / Delete Response. If the procedure failed, the cause value indicates the reason.

[0058] In operation 614, (which occurs only after successful completion of operation 606), the UDM 308 notifies the subscribed Network Function of the updated UE and / or Group subscription data via an Nudm_SDM_Notification Notify message. In some example embodiments, if the subscribed NF is the AMF 364, the UDM 308 performs an Nudm_SDM_Notification (SUPI or Internal Group Identifier, AMF-Associated Subscribed PMS parameters, etc.) service operation. The AMF 364 uses the received parameters to derive the appropriate UE configuration of the NAS parameters. If PMS is for SMS, the AMF 364 configures the SMSF accordingly.PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00

[0059] In some example embodiments, if the subscribed NF is an SMF, the UDM 308 performs an Nudm SDM Notifi cation (SUPI or Internal Group Identifier, SMF- Associated Subscribed PMS parameters, DNN / S-NSSAI, Session Management Subscription data, etc.) service operation. The SMF stores the received parameters and associates them with a PDU Session based on the DNN and S-NSSAI included in the message from the UDM 308. If PMS is for NIDD based messaging, the SMF configures the NEF / UPF 354 accordingly to set the PDU Session.

[0060] Methods according to other aspects of the present disclosure provide priority treatment for messaging services in 3GPP systems based on an MPS service as shown in Fig. 7. The method illustrated in Fig. 7 enables priority treatment for third-party user messaging services by enhancing (MPS4msg services, e.g., using SMS or NIDD based messaging, for an authorized third-party user.

[0061] The UE 102 can support providing subscription of MPS4msg services, which can be for third party users or Service Users, whereby the AF of the third-party service provider provisions network configuration parameters to the UDM based on an Nnef ParameterProvision Service operation as described in TS 23.502, clause 4.15.6.2. The network configuration parameters can include an MPS for Messaging indication (MPS4M1) which indicates enabling or disabling the MPS treatment of messaging service for a third-party user using an MPS- subscribed UE. When enabled, this parameter is associated with access identity for access attempt control.

[0062] The network configuration parameters can further include a new (e.g., special purpose or dedicated) third-party priority indication IE, which can be set to indicate a priority level for the third-party user based on operator’s policy and service level agreement with a third-party service provider. The value for the IE can include, for example, a binary indication (e.g., 0, 1 to enable or disable the priority treatment), an indication for priority level (e.g., High, Medium, Low), an integer value of the priority level (e.g., 0~10), or an enumerated value of the priority level (e.g., pO, p5, . .. , plO), although aspects of the present disclosure are not limited to these examples. When provided with a 3PPriority indication, the IE indicates, to the network, that the requested MPS for Messaging is for third party users, and that the priority level for third partyPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 users is equal or lower than the priority level for Service Users. The network configuration parameters can further include the preferred MPS4msg type, e.g., SMS or NIDD-based Messaging, or both.

[0063] The network stored configuration parameters for MPS4msg for authorized third party users configure related service parameters in the UE via NAS signaling by including an MPS for Messaging indication (MPS4MI) in a 5GS network feature IE and in third-party priority (3PPriority) IE. Alternatively, an Allowed MPS4msg type IE in a Registration Accept message can configure the UE 102with related service parameters using during a registration request procedure. As another alternative, the network can configure the UE during a UE configuration update procedure by including MPS4MI in a priority indicator IE and a new (e.g., special purpose or dedicated) commercial priority indication IE in a UE Configuration Update Command message.

[0064] An MPS4MI indication (or use of MPS priority IE for MPS) is associated with a specific standardized value of access identity (AID), i.e. AID=1. The MPS4MI indicates to the UE 102 whether configuration of Access Identity 1 is valid within the selected PLMN.The network can set 3PPriority to indicate a priority level for the third-party user based on the operator’s policy and service level agreement with a third-party service provider. The priority level can be indicated with, for example: i.) a binary indication (e.g. 0, 1 such that 0 signifies that priority or PMS is disabled for the third party); ii.) an indication for priority level (e.g. High, Medium, Low); iii.)an integer value of the priority level (e.g. 0—10); iv.) an enumerated value of the priority level (e.g. pO, p5, . .. , plO), or other indications or indication types. By setting 3PPriority, the network indicates to the UE 102 that the MPS for Messaging is for third party users and that the priority level for third party users should be equal or lower than the priority level for Service Users. The 3PPriority may be the same as or different from the network configuration parameters provisioned by the AF of the third-party service provider. The Allowed MPS4msg type indicates which type of MPS for messaging service are allowed, e.g., SMS, NIDD-based messaging, or both.PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00

[0065] Before attempting to access the network due to MPS4msg service for an authorized third-party user, the UE 102 performs operations 502-510 in Figure 5.

[0066] To set the Access Category, the 102 can identify the type of access attempt for the MPS messaging service for the third-party user by setting the Access Category according to one or more of the following options.

[0067] According to a first option, the UE may set the Access Category to MO Data (see Table 2 later herein defining Access Categories) if the MPS4msg is for a third-party user. In another option, the UE may set the Access Category to a new (e.g., special purpose or dedicated) standardized value of MPS for messaging for a third-party user. In yet another option, the UE may set the Access Category based on Operator-Defined Access Categories received in NAS signaling (e.g., in Registration Accept message during registration request procedure or in a UE Configuration Update Command during UE Configuration Update procedure).

[0068] Example access control criteria can include the access identity defined for MPS4msg services (e.g., over SMS, NIDD based messaging), and an additional or operator-defined access category having at least one of the following settings: i.) DNN for MPS4msg for a third-party user; ii.) Application ID for MPS4msg for a third-party user; or iii.) Network Slice for MPS4msg for a third-party user.

[0069] During a UE access attempt for MPS4msg using SMS or NIDD-based messaging for a third-party user, the 5GS can be enhanced by characterizing and prioritizing the access attempts by indicating the Establishm entCause as mps-Priority Access or highPriority Access, and additionally a new commercial priority IE (CPriority) in the RRCSetupRequest message. As such, the RAN node can take MPS for messaging priority and CPriority for a third-party user into account for managing radio resources for the UE 102.

[0070] The CPriority IE indicates priority of the third-party user using the MPS4msg service, whereby CPriority can be set to indicate a priority level for the third-party user based on the operator’s policy and service level agreement with a third-party service provider. As described earlier herein, example priority level indications can include a binary indication(e.g. 0, 1 such that 0 means disabled for third party); an indication for priority level (e.g. High, Medium, Low);PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 an integer value of the priority level (e.g. 0~10); or an enumerated value of the priority level (e.g. pO, p5, . . ., plO), although aspects of the present disclosure are not limited thereto. By using 3PPriority, the network indicates to the UE 102 that the MPS for Messaging is for third-party users whose priority level should be equal or lower than the priority level for Service Users. Based on the UE 102 implementation, or RAN support, the CPriority may be the same as 3PPriority or different from 3PPriority stored in the UE 102 context which is received from the network in the NAS message (Registration Accept or UE Configuration Update Command message).

[0071] Referring to Fig. 7the AF / AS provisions 700 network configuration parameters of MPS4msg for third-party users to the UDM based on an Nnef_ParameterProvision Service operation as described in TS 23.502, clause 4.15.6.2 (as illustrated with reference to Fig. 6 earlier herein). The network configuration parameters can include an MPS for Messaging indication (MPS4MI), which indicates enabling or disabling the MPS treatment of messaging service for an MPS-subscribed UE. When enabled, the MPS4MI is associated to an access identity for access attempt control.

[0072] Network configuration parameters can further include a new (e.g., special purpose or dedicated) third party priority (3PPriority) indication IE, which can be set to indicate a priority level for the third-party user based on operator’s policy and service level agreement with third party service provider. The priority level can include a binary indication (e.g. 0, 1 to enable or disable the priority treatment); an indication for priority level (e.g. High, Medium, Low); an integer value of the priority level (e.g. 0~10);ab enumerated value of the priority level (e.g. pO, p5, . . ., plO) or other indicator type or value. By setting 3PPriority indications, the network is informed that the requested MPS for Messaging is for third party users whose priority level should be equal or lower than the priority level for Service Users. The network configuration parameters can further include a preferred MPS4msg type, e.g. SMS or NIDD based Messaging, or both.

[0073] The UE 102 sends 702, to the network, a Registration Request message for negotiating the UE 102 and network capability support of SMS or NIDD based messaging. For example, the UE 102 can indicate "SMS supported" included in the Registration Request, or the UE 102 canPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 indicate “Control Plane CIoT 5GS Optimization” or new, dedicated or special purpose “NIDD based messaging” included in the Registration Request for NIDD based messaging.

[0074] The AMF 364 obtains 704 subscription information from the UDM 308 and stores information in the UE context. For MPS4msg for a third-party user, the AMF stores MPS4MI, 3PPriority indication, and allowed MPS4msg type (e.g. SMS or NIDD-based messaging service, based on Preferred MPS4msg and UE subscription). For messaging service support, the following may be applied. First, if “SMS supported” is indicated in 702, the AMF checks within the SMS Subscription data whether the SMS service is allowed to the UE 102, and the AMF stores “SMS service is allowed” and optionally “available SMSF of the serving PLMN” in the UE 102 context.

[0075] If “Control Plane CIoT 5GS Optimization” or “NIDD-based messaging is supported” is indicated in Operation 702, the AMF checks within the Subscription data, e.g. messaging subscription or access and mobility subscription, whether the NIDD-based messaging service is allowed to the UE 102, and the AMF stores “NIDD based messaging service is allowed” and optionally “available SMF / NEF of the serving PLMN” in the UE 102 context.

[0076] The AMF may perform the following. First, the AMF may activate SMS by sending an Nsmsf_SMService_Activate service operation to the SMSF based on stored SMSF Address for SMS based on a registration procedure for SMS over NAS in TS23.502 clause 4.13.3.1 [2], or the AMF may activate NIDD based messaging through SMF / NEF by sending an Nsmf_PDUSession_PDUSession_CreateSMContext Request service operation to a selected SMF. Then the SMF sends Nnef SMContext Create Request to 1) NEF to establish NEF PDU Session (based on TS23.502 clause 4.25.2) if PDU Session Establishment request is indicated in Registration Request message and NEF address is stored at the UE context, or 2) to selected UPF to establish UPF anchored PDU Session based on TS23.502 clause 4.3.2.2.1.

[0077] With the activation of SMS or NIDD based messaging, the messaging services can be expedited during urgent events. Alternatively, the NIDD based messaging services can be activated when UE 102 initiates the messaging service procedure in Operation 720-726.PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00

[0078] The AMF 364 determines 706 if the network supports MPS4msg for third party users using SMS or NIDD based messaging based on stored UE 102 context, or both.

[0079] The AMF 364 sends 708, to the UE 102, a Registration Accept message including MPS for messaging indication (MPS4MI or use of MPS priority IE for MPS) in a 5GS network feature, 3PPriority Indication IE, and allowed MPS4msg type. If allowed MPS4msg type is not provided, the AMF indicates “SMS allowed” and / or “NIDD-based messaging allowed” with MPS4MI, and the UE 102 is allowed to use SMS and / or NIDD based messaging for MPS4msg.

[0080] If the UE 102 subscription is changed or needs to be provided, the network may perform a UE Configuration Update procedure to update UE 102 configuration, whereby the UE Configuration Update Command message 710 includes an MPS4MI in priority indicator, a 3PPriority Indication, and an allowed MPS4msg type. If the 3PPriority Indication is provided, the MPS4msg is supported for the third-party user with the indicated 3PPrioirty. Otherwise, the priority level can be set based on operator’s policy and service level agreement with third party service provider.

[0081] The UE 102 stores 712 MPS4MI, 3PPriority Indication, and allowed MPS4msg type in the UE context.

[0082] The UE 102 receives 714 an upper layer request for MPS4msg for a third-party user using SMS or NIDD based messaging.

[0083] The UE 102 determines 716 the following for MPS4msg for third party users. First, the UE can determine the type of MSG4msg for the service, e.g., SMS or NIDD based messaging, based on the allowed MPS4msg type or the UE 102 implementation based on network supported messaging information (SMS supported or NIDD based messaging supported or both). Second, the UE can set an access identity and access category as described earlier herein with reference to Table 2 or with reference to operator-defined access categories received in NAS signaling.

[0084] The UE 102 performs 718 an access attempt checks as indicated in Figure 5.

[0085] When the access attempt check for MPS4msg for a third-party user is allowed, the UE 102 initiates 720, with the RAN 105, an RRCSetupRequest message including thePATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00Establishmentcause as mps-Priority Access or highPriority Access. The RRCSetupRequest message can further include a new commercial priority IE (CPriority), whereby CPriority indicates priority of the third-party user using the MPS4msg service. The CPriority can be set to indicate a priority level for the third-party user based on operator’s policy and service level agreement with a third-party service provider, which can include any of the priority level indications described earlier herein. A 3PPriority indicates to the UE 102 that the MPS for Messaging is for third party users whose priority level should be equal or lower than the priority level for Service Users. Based on the UE 102 implementation, or RAN support, the CPriority may be the same as 3PPriority or different from 3PPriority stored in the UE context which is received from the network in Operation 708 or Operation 710.

[0086] The RRCSetupRequest message can additionally or alternatively include an NAS container containing a UL NAS Transport message with the following cases: for delivering MPS4msg using SMS; for delivering MPS4msg using NIDD based messaging; or for requesting NEF / UPF anchored PDU Session for NIDD- based messaging if not activated during the registration procedure in operation 704.

[0087] Accordingly, the RAN node can take an EstablishmentCause and CPriority into account for managing radio resources for the UE 102 using an MPS4msg. If the RAN node 105 rejects the access attempt, the RAN node 105 rejects the RRC Setup Request with proper reject cause for MPS or MPS4msg.

[0088] The RAN node 105 sends 722, to the AMF 364, an N2 message including a UL NAS Transport message in the NAS container to the AMF 364. For example, the NAS container may include an SMS message for delivering an MPS4msg using SMS, or the NAS container may include an MO data payload for delivering MO data using NIDD based messaging if NIDD based messaging is activated in operation 704, or the NAS container may include a PDU Session Establishment Request message to create an NEF PDU Session or a UPF anchored PDU Session for NIDD based messaging.

[0089] For an MPS4msg using SMS, when the AMF 364 receives an SMS message, the AMF 364 determines that the UE has the MPS4MI indication in the UE context as specified inPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 operation 704. The AMF sends 724A, to the SMSF, an Nsmsf_SMService_UplinkSMS message, which includes an SMS message and the Message Priority header indicated with a value appropriate for MPS4msg to indicate priority treatment based on a stored MPS4MI and 3PPriority indication in the UE context. The related procedure can be based on TS23.502 clause 4.13.3.3, MO SMS over NAS.

[0090] For MPS4msg using NIDD based messaging, when the AMF receives an MO data payload for NIDD-based messaging, the AMF 364 includes a Message Priority header indicated with a value appropriate for MPS4msg to indicate priority treatment based on anMPS4Ml and 3PPriority indication stored in the UE context. The related procedure can be based on an NEF Anchored Mobile Originated Data Transport procedure in TS23.502 clause 4.25.4 or UPF anchored Mobile Originated Data Transport in Control Plane CIoT 5GS Optimization procedure based on TS23.502 clause 4.24.1.

[0091] If an NEF (or UPF anchored) PDU Session is not established and the AMF determines that the UE has the MPS4MI indication in UE context in operation 704, the AMF receives 724B a UL NAS Transport message with a PDU Session Establishment Request message indicating: i.) a PDU Session ID; ii) S-NSSAI for a third party user using MPS4msg; and / or iii.) a DNN for third party user using MPS4msg.

[0092] To create an NEF PDU Session, the AMF sends 724B anNsmf PDUSession CreateSMContext Request message to the SMF, and the SMF creates a PDU session towards the NEF by sending an Nnef_SMContext_Create Request message to the NEF. Then the NEF creates an NEF PDU Session and invokes an Nnef_SMContext_Create Response towards the SMF confirming establishment of the NEF PDU session for the UE. The related operations for NEF PDU Session Establishment are based on TS23.502 clause 4.25.2. To create a UPF anchored PDU Session, the related operations are based on messaging that is based on TS23.502 clause 4 3.2.2.1.

[0093] The AF / AS with SMSC functionalities receives 726A, from the SMSF, the SMS message, whereby the SMSF can enable a new Event Exposure service operation to forward the SMS message to the third-party AF / AS (the details are not in the scope of this disclosure) basedPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 on a received AF / AS address from the AMF. The SMF creates 726B1 an NIDD-based PDU Session with NEF / AF / AS based on an AF / AS address received from the SMF, and responds 726B2, 726B3 with a PDU Session Establishment accept message to the UE 102.

[0094] The UE continuously uses 728 UL NAS Transport to send SMS with priority treatment. The UE 102 uses UL NAS Transport for the NEF / UPF anchored PDU Session to send NIDD based messaging with priority treatment. When the NEF / UPF receives the unstructured data, and finds an NEF PDU Session context / PDU Session context, the NEF / UPF sends the unstructured data to the AF in an Nnef_NlDD_DeliveryNotify Request message or via N6 for a UPF anchored PDU Session. The related procedure can refer to NEF Anchored Mobile Originated Data Transport (MO) based on TS23.502 Figure 4.25.4-1 for the NEF Anchored Mobile Originated Data Transport procedure and NEF Anchored Mobile Terminated Data Transport (MT) based on TS23.502 Figure 4.25.5-1 for the procedure that the AF uses to send unstructured data to a given user for the call back if needed.

[0095] Methods according to another aspect of the present disclosure, illustrated in Fig. 8, extend priority treatment for messaging services in a 3GPP system from an MPS service. The eMPSmsg is associated with a third-party user and a new access Identity, which is different from MPSls or MPSM1 for a Service User (or for a third-party user as described with reference to Fig. 7). This aspect can use a same or new (e.g., special purpose or dedicated) Access Category, and single or multiple priority levels.

[0096] Methods according to at least this aspect enable priority treatment for a third-party user using messaging services by enhancing MPS for messaging, e.g. using SMS or NIDD based messaging, for a third-party user, with the following features.

[0097] First, the UE has or provides a subscription of extended MPS for Messaging (eMPS4msg) priority for third party users, whereby the AF of the third-party service provider provisions network configuration parameters to the UDM based on an Nnef ParameterProvision Service operation as described in TS 23.502, clause 4.15.6.2. The network configuration parameters can include extended-MPS for Messaging indication (eMPS4MI) which indicates the enabling or disabling of MPS treatment of a messaging service for a third-party user using anPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00MPS -sub scribed UE. When enabled, the indication is associated with an access identity for network access control.

[0098] The network configuration parameters can further include a new (e.g., special purpose or dedicated) third party priority indication IE, which can be set to indicate a priority level for the third-party user based on operator’s policy and service level agreement with third party service provider. The value for the IE can be similar to other priority level indications described above, e.g., a binary indication (e.g. 0, 1 to enable or disable the priority treatment), an indication for priority level (e.g. High, Medium, Low), an integer value of the priority level (e.g. 0~10), or an enumerated value of the priority level (e.g. pO, p5, .. ., plO). With a 3PPriority indication, the IE indicates to the network that the requested MPS for Messaging is for third party users whose priority level should be equal or lower than the priority level for Service Users. The network configuration parameters can also include a preferred MPS4msg type, e.g., SMS or NIDD based Messaging, or both.

[0099] The network stored network configuration parameters of MPS4msg for authorized third party users can configure the UE with related service parameters via NAS signaling by i.) including eMPS4MI in a 5GS network feature IE and third party priority (3PPriority) IE; ii.) including the Allowed MPS4msg type IE in a Registration Accept message during registration request procedure; or iii. including an MPS4MI in priority indicator IE and a new commercial priority indication IE in a UE Configuration Update Command message during a UE configuration update procedure.

[0100] The eMPS4MI indication is associated with a specific standardized value of access identity (AID) as described earlier herein with i.e. AID=X. 3PPriority can be set to indicate a priority level for the third party user based on operator’s policy and service level agreement with a third party service provider, which can be a binary indication (e.g. 0, 1 such that 0 means disabled for third party), or an indication for priority level (e.g. High, Medium, Low), or an integer value of the priority level (e.g. 0~10), or enumerated value of the priority level (e.g. pO, p5, . . ., plO). When 3PPriority is provided, this indicates to the UE that the MPS for Messaging is for third party users whose priority level should be equal or lower than priority level for Service Users. The 3PPriority may be the same as or different from the network configurationPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 parameters provisioned by the AF of a third-party service provider. The Allowed MPS4msg type indicates which type of MPS for messaging services are allowed, e.g. SMS, NIDD-based messaging, or both.

[0101] Before attempting to access the network due to extended MPS4msg for an authorized third-party user, the UE 102 performs operations 502-512 in Figure 5. To set the Access Category, the UE 102 can identify the type of access attempt for eMPS4msg, i.e., the MPS messaging service for a third-party user, by setting Access Category according to the following options. According to a first option, the Access Category can be set as MO Data for eMPS4msg. In a second option, the Access Category can be provided as a new (e.g., special purpose or dedicated) standardized value for eMPS4msg. As a third option, the Access Category can be provided based on Operator-Defined Access Categories received in NAS signaling (e.g., as a Registration Accept message during a registration request procedure or as a UE Configuration Update Command during a UE Configuration Update procedure). For example, the access control criteria can include: the access identity (AID#X) for the eMPS4msg, and one operator- defined access category with at least one of the following settings: i.) DNN for eMPS4msg; ii.) Application ID for eMPS4msg; or iii.) Network Slice for eMPS4msg.

[0102] During a UE access attempt for eMPS4msg using SMS or NIDD-based messaging for a third party user, the 5GS can be enhanced by characterizing and prioritizing the access attempts by indicating the Establishmentcause as i.) a new (e.g., dedicated or special purpose) value for emps-Priority Access or as ii.) a new (e.g., dedicated or special purpose) value of highPriority Access for eMPS4msg, with the inclusion of a new (e.g., special purpose or dedicated) commercial priority IE (CPriority) in an RRCSetupRequest message. As such, the RAN node can take the MPS4msg priority and the CPriority for a third-party user into account when managing radio resources for the UE 102.

[0103] The CPriority IE indicates the priority of the third-party user using an MPS4msg service, whereby CPriority can be set to indicate a priority level for the third-party user based on the operator’s policy and service level agreement with the third-party service provider. The priority level indication can be a binary indication (e.g. 0, 1 such that 0 means disabled for third party). Alternatively, the priority level indication can include a level (e.g. High, Medium, Eow),PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 an integer value (e.g. 0~10), or an enumerated value (e.g. pO, p5, .. plO). When 3PPriority is indicated, this indicates to the UE 102 that the eMPSmsg for third party users is with priority level equal or lower than priority level for Service Users. Based on the UE 102 implementation, or RAN support, the CPriority may be the same as the 3PPriority or different from the 3PPriority stored in the UE 102 context which is received from the network in the NAS message (Registration Accept or UE Configuration Update Command message).

[0104] Table 1 below provides example access class identities (also defined in TS 24.501, Table 4.5.2.1 : Access identities). Aspects of the present disclosure provide a new (e.g., special purpose or dedicated) Access identity X, which signifies that the UE is configured for extended MPS4msg (or eMPSmsg).Table 1: example for adding a new access identity

[0105] With respect to Access Identity X in Table 1 (where X = 4, although aspects of the present disclosure are not limited thereto), Access Identity X is used by an authorized third-party user’s Messaging communication using UEs configured for PMS for Messaging, 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 X (or Access Identity 4) is also valid when the UE is explicitly authorized by the network based on specific configured PLMNs inside and outside the home country. Access Identity 1 is used by an authorized Service User’s Voice, Video, Data and Messaging communication using UEsPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 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.Table 2 below provides example access categories and corresponding type of access attempt, including a new (e.g., special purpose or dedicated) access category (e.g., Access Category Z) wherein a UE attempts access using NIDD based messaging or eMPS4msg. Table 2 can be based on TS22.261, Table 6.22.2.3-1 : Access Categories:

[0106] With reference to Table 2, it is noted that Access Category 7 includes IMS Messaging and NIDD-based Messaging, i.e., if eMPS4msg supports only NIDD-based messaging, the type of access attempt can be eMPS4msg or NIDD based messaging for Access Category Z. If PMS supports both SMS and NIDD based messaging, the type of access attempt is an NIDD based message (Access Category=Z in Table 2).PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00

[0107] Access Control options may include configuring a new (e.g., dedicated or special purpose) Access Identifier for UE configured for a new (e.g., dedicated or special purpose) PMS for third party user for urgent event, (note that no new (e.g., dedicated or special purpose) access category is defined, i.e. the existing access category may be used). When a UE’s access attempt is SMS for eMPS4msg, the UE sets the Access ID to, e.g., X (see Table 2), and the access category to, e.g., AC=6. When a UE’s access attempt is NIDD based messaging for eMPS4msg, the UE determines AID=Y (new (e.g., dedicated or special purpose)), and AC=7 (MO data).

[0108] Access Control options can further include defining a new (e.g., special purpose or dedicated) standardized value that defines UE 102’s access attempt type as NIDD based messaging for eMPS4msg. When UE 102’s access attempt is SMS for eMPS4msg, the UE 102 determines AID=0, and AC=6, referring to Tables 1 and 2 above. When UE 102’s access attempt is NIDD based messaging for eMPS4msg, the UE 102 determines that AID=0, and AC=Z from Tables 1 and 2 above.

[0109] Access Control options can further include defining a new (e.g., special purpose or dedicated) standardized value that defines the UE 102 access attempt type as eMPS4msg (for both SMS and NIDD based messaging). When UE 102’s access attempt is via an eMPS4msg using SMS, the UE 102 determines AlD=0, and AC=Z from Tables 1 and 2 earlier herein. When UE 102’s access attempt is via eMPS4msg using NIDD based messaging, the UE 102 determines AID=0, and AC=Z from Tables 1 and 2 earlier herein.

[0110] Access control options can further include defining no specialized or dedicated AIDs or ACs for UE 102’s access attempt type as eMPS4msg (for both SMS and NIDD based messaging). According to this access control option, when the UE 102’s access attempt is an eMPS4msg using SMS, the UE 102 determines Access Identifier = 0, and an Access Category of 0 (from Tables 1 and 2 earlier herein), or operator-defined access categories.

[0111] Referring to Fig. 8, the AF / AS provisions 800, to the UDM 308, network configuration parameters of extended-MPS4msg for third party users based on an Nnef ParameterProvision Service operation as described in TS 23.502, clause 4.15.6.2 (as shown in Fig. 6). The network configuration parameters can include an eMPS for Messaging indication (eMPS4MI) whichPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 indicates enabling or disabling the MPS treatment of messaging service for a third-party user using an MPS-subscribed UE 102. When enabled, this indication is associated with access identity for access attempt control. The network configuration parameters can further include a new (e.g., dedicated or special purpose) third party priority (3PPriority) indication IE, which can be set to indicate a priority level for the third-party user based on the operator’s policy and service level agreement with third party service provider. Values for this indication can be as described above, e.g., a binary indication (e.g. 0, 1 to enable or disable the priority treatment), an indication for priority level (e.g. High, Medium, Low), an integer value of the priority level (e.g. 0~10), enumerated value of the priority level (e.g. pO, p5, ..., plO), etc., although embodiments are not limited to these indications. When set to the 3PPriority indication, the network is notified that the requested MPS for Messaging is for third party users whose priority level should be equal or lower than the priority level for Service Users. The network configuration parameters can further include a Preferred eMPS4msg type, e.g. SMS or NIDD based Messaging, or both.

[0112] The UE 102 sends 802, to the network, a Registration Request message for negotiating the UE 102 and network capability support of SMS or NIDD based messaging. For example, the UE 102 can indicate "SMS supported" included in the Registration Request, or the UE 102 can indicate “Control Plane CIoT 5GS Optimization” or “NIDD based messaging” is included in the Registration Request for NIDD based messaging.

[0113] The AMF 364 obtains 804 subscription information from the UDM 308 and stores information in the UE 102 context. For an eMPS4msg for third party user, the AMF 364 stores eMPS4MI, a 3PPriority indication, and an allowed eMPS4msg type (e.g. SMS or NIDD-based messaging service, based on Preferred MPS4msg and UE subscription). For messaging service support, if “SMS supported”, is indicated in Operation 702 (Fig. 7), the AMF 364 checks the SMS Subscription data to determine whether the SMS service is allowed to the UE 102. The AMF 364 stores, in the UE 102 context parameters including “SMS service is allowed” and, optionally “available SMSF of the serving PLMN”.

[0114] Messaging service support can further include, if “Control Plane CIoT 5GS Optimization” or “NIDD-based messaging is supported” is indicated in operation 702, the AMF 364 checking, in the Subscription data (e.g. messaging subscription or access and mobilityPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 subscription) whether the Control Plane CIoT 5GS Optimization or NIDD-based messaging service is allowed to the UE 102. If the AMF 364 determines this service is allowed to the UE 102, the AMF 364 stores “Control Plane CIoT 5GS Optimization is allowed” or “NIDD based messaging service is allowed” and, optionally, “available SMF / NEF of the serving PLMN” in the UE context.

[0115] The AMF 364 may activate SMS by sending an Nsmsf_SMService_Activate service operation to the SMSF based on a stored SMSF Address for SMS based on registration procedure for SMS over NAS in TS23.502 clause 4.13.3.1. Alternatively, or additionally, the AMF 364 may activate NIDD based messaging through the SMF / NEF 366 / 354 by sending an Nsmf_PDUSession_PDUSession_CreateSMContext Request service operation to a selected SMF. Then the SMF 366 sends an Nnef_SMContext_Create Request to 1) NEF 354 to establish an NEF PDU Session (based on TS23.502 clause 4.25.2) if PDU Session Establishment request is indicated in Registration Request message and NEF 354 address is stored at the UE 102 context, or 2) to selected UPF to establish a UPF anchored PDU Session based on TS23.502 clause 4.3.2.2.1.

[0116] With the activation of SMS or NIDD based messaging, the messaging services can be expedited during urgent events. Alternatively, the NIDD based messaging services can be activated when the UE 102 initiates the messaging service procedure in operations 620-626.

[0117] The AMF determines 806 if the network supports eMPS4msg for a third-party user using SMS or NIDD based messaging based on a stored UE 102 context.

[0118] The AMF 364 sends 808, to the UE 102, a Registration Accept message including extended MPS for messaging indication (eMPS4MI) in a 5GS network feature, 3Ppriority Indication IE, and allowed eMPS4msg type. If the allowed MPS4msg type is not provided, the AMF 364 indicates “SMS allowed” and / or “NIDD-based messaging allowed” with MPS4MI, and the UE 102 is allowed to use SMS and / or NIDD based messaging for MPS4msg.

[0119] If the UE 102 subscription is changed or needs to be provided, the network may perform a UE Configuration Update procedure to update a UE 102 configuration, whereby a UE Configuration Update Command 810 includes an eMPS4MI in a priority indicator, a 3PPriorityPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00Indication, and an allowed MPS4msg type. If the 3PPriority Indication is provided, the MPS4msg is supported for the third-party user with the indicated 3PPriority. Otherwise, the priority level can be set based on the operator’s policy and service level agreement with third party service provider.

[0120] The UE stores 412 the eMPS4MI, 3PPriority Indication, and allowed eMPS4msg type in the UE 102 context.

[0121] The UE receives 814 an upper layer request for an eMPS4msg for a third-party user using SMS or NIDD based messaging.

[0122] The UE 102 determines 816 the following for an eMPS4msg for a third-party user. First, the UE 102 determines the type of eMSG4msg for the service, e.g., SMS or NIDD based messaging, based on the allowed eMPS4msg type or on UE 102 implementation based on network supported messaging information (SMS supported or NIDD based messaging supported or both). The UE 102 also determines an access identity as X (AID=X), which is different from MPS4msg or MPS for Service Users, and the access category as MO data for eMPSmsg for a third-party user, or a new standardized value for eMPS4msg for third party user, or Operator- defined Access categories.

[0123] The UE 102 performs 818 an access attempt check. When the access attempt check for eMPS4msg for third party user is allowed, the UE 102 initiates 820 an RRCSetupRequest message including: Establishmentcause as a new (e g., dedicated or special purpose) value for emps-Priority Access or a new (e.g., dedicated or special purpose) value of highPriority Access for eMPS4msg; and / or a new (e.g., dedicated or special purpose) commercial priority IE (CPriority), whereby CPriority indicates priority of the third party user using eMPS4msg service. The CPriority can be set to indicate a priority level for the third-party user based on operator’s policy and service level agreement with third party service provider. As described earlier herein, the priority level indication can be a binary indication (e.g. 0, 1 such that 0 means disabled for third party), or an indication for priority level (e.g. High, Medium, Low), an integer value of the priority level (e.g. 0~10), or an enumerated value of the priority level (e.g. pO, p5, ..., plO), etc., although aspects of the present disclosure are not limited to these indications. When thePATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 indication indicates 3PPriority, this indicates to the UE 102 that the MPS for Messaging is for third party users whose priority level should be equal or lower than the priority level for Service Users. Based on the UE implementation, or RAN support, the CPriority may be the same as 3PPriority or different from 3PPriority stored in the UE 102 context which is received (see e.g., 708 or 710, Fig. 7) from the network.

[0124] The NAS container contains UL NAS Transport message in the following cases: for delivering eMPS4msg using SMS or for delivering messaging data using NIDD based messaging or for requesting NEF / UPF anchored PDU Session for NIDD based messaging if not activated during a registration procedure 804.

[0125] Accordingly, the RAN node 105 can take EstablishmentCause, and CPriority into account for managing radio resources for the UE 102 using eMPS4msg. If the RAN node 105 rejects the access attempt, the RAN node 105 rejects the RRC Setup Request with a proper reject cause for MPS or MPS4msg or eMPSmsg.

[0126] Subsequent operations proceed similarly to operation 722 (Fig. 7).

[0127] For MPS4msg using SMS, when the AMF 364 receives an SMS message and determines the UE 102 has the eMPS4Ml indication in UE 102 context as specified in Operation 704, the AMF sends 824A, to the SMSF, an Nsmsf_SMService_UplinkSMS message which includes the SMS message and the Message Priority header indicated with a value appropriate for MPS4msg to indicate priority treatment based on stored eMPS4MI and 3PPriority indication in the UE context. The related procedure can be based on TS23.502 clause 4.13.3.3, MO SMS over NAS.

[0128] For MPS4msg using NIDD based messaging, when the AMF 364 receives an MO data payload for NIDD based messaging, the AMF 364 includes a Message Priority header indicated with a value appropriate for MPS4msg to indicate priority treatment based on stored eMPS4MI and 3PPriority indications in the UE 102 context. The related procedure can be based on an NEF Anchored Mobile Originated Data Transport procedure in TS23.502 clause 4.25.4 or a UPF anchored Mobile Originated Data Transport in Control Plane CIoT 5GS Optimization procedure based on TS23.502 clause 4.24.1.PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00

[0129] If an NEF (or UPF anchored) PDU Session is not established and the AMF 364 determines that the UE 102 has the MPS4MI indication in the UE 102 context in operation 704, the AMF 364 receives a UL NAS Transport message with a PDU Session Establishment Request message indicating a PDU Session ID, an S-NSSAI for third party user using MPS4msg, and a DNN for third party user using MPS4msg.

[0130] To create an NEF PDU Session, the AMF sends, to the SMF, anNsmf PDUSession CreateSMContext Request message. The SMF creates a PDU session towards the NEF by sending an Nnef_SMContext_C reate Request message to the NEF. Then the NEF creates an NEF PDU Session and invokes an Nnef SMContext Create Response towards the SMF confirming establishment of the NEF PDU session for the UE 102. The related operations for NEF PDU Session Establishment are based on TS23.502 clause 4.25.2.

[0131] To create a UPF anchored PDU Session, the related operations are based on messaging based on TS23.502 clause 4.3.2.2.1.

[0132] Operations 826-828 can proceed similarly to similarly-numbered operations in Fig. 7.

[0133] Methods according to another aspect, illustrated in Figure 9, provide priority treatment for messaging services in 3GPP system based on a new (e.g., special purpose or dedicated) service referred to as a priority messaging service (PMS). PMS can also be described as an express messaging service or an expedited messaging service. A priority messaging service can additionally or alternatively be referred to as an express messaging service or an expedited messaging service in some aspects of the present disclosure.

[0134] Methods according to at least this aspect enable a new (e.g., special or dedicated purpose) priority messaging service (PMS) which is solely for third party user using SMS or NIDD based messaging, with the following features.

[0135] The UE 102 is with Subscription of PMS priority for third party users, whereby the AF of the third-party service provider provisions network configuration parameters to the UDM 308 based on an Nnef_ParameterProvision Service operation as described in TS 23.502, clause 4.15.6.2. The network configuration parameters can include a PMS indication (PMSI) to indicate enabling or disabling the priority treatment of PMS for third party user using a PMS-PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 subscribed UE. When enabled, the indication is associated with an access identity for network access control. The network configuration parameters can further include a new (e.g., special purpose or dedicated) third party priority indication IE, which can be set to indicate a priority level for the third-party user based on operator’s policy and service level agreement with third party service provider. The value for this indication can be as described earlier herein, e.g., a binary indication (e.g. 0, 1 to enable or disable the priority treatment), an indication for priority level (e.g. High, Medium, Low), an integer value of the priority level (e.g. 0~10), or enumerated value of the priority level (e.g. pO, p5, . . ., plO). The PMSI and 3PPriority indication, indicates to the network that the requested PMS for a third-party user is with a priority level that is to be equal or lower than the priority level of MPS / MPS4msg for Service Users. The network configuration parameters can further include a preferred PMS type, e.g. SMS or NIDD based Messaging, or both.

[0136] The network stored network configuration parameters of MPS4msg for authorized third party users can configure the UE 102 with related service parameters via NAS signaling by including PMSI in a 5GS network feature IE and a third party priority (3PPriority) IE, Allowed PMS type IE in a Registration Accept message during registration request procedure, or by including PMSI in a priority indicator IE and a new (e.g., dedicated or special purpose) commercial priority indication IE in a UE Configuration Update Command message during a UE configuration update procedure. PMSI indication is associated with a specific standardized value of access identity (AID) as described earlier herein with reference to Tables 1 and 2. 3PPriority can be set to indicate a priority level for the third party user based on operator’s policy and service level agreement with third party service provider, which can be similar to indicators described earlier herein, e.g., a binary indication (e.g. 0, 1 such that 0 means disabled for third party), an indication for priority level (e.g. High, Medium, Low), an integer value of the priority level (e.g. 0~10), or an enumerated value of the priority level (e.g. pO, p5, .. ., plO). A parameter of 3PPriority indicates to the UE 102 that the PMS has a priority level set for third party users whose priority level should be equal or lower than the priority level for Service Users using MPS / MPS4msg. The 3PPriority may be the same as or different from the network configurationPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 parameters provisioned by the AF of a third-party service provider. An Allowed PMS type indicates which type of PMS are allowed, e.g. SMS, NIDD-based messaging, or both.

[0137] Before attempting to access the network due to PMS for authorized third party user, the UE performs operations 502-512 described with reference to Figure 5. To set the Access Category, the UE 102 can identify the type of access attempt for PMS, i.e. for a third-party user, by setting Access Category according to the following options. In a first option, the UE may set the Access Category to MO Data for PMS (see e.g., Table 1 earlier herein and Table 3 below). In another option, the UE may set a new (e.g., dedicated or special purpose) standardized value for PMS. In yet another option, the UE may set access categories according to Operator-Defined Access Categories received in NAS signaling (e.g., in a Registration Accept message during registration request procedure or in UE Configuration Update Command during UE Configuration Update procedure). For example, the access control criteria can include: the access identity defined in Table 3 herein for PMS, and an operator-defined access category with at least one of the following settings: DNN for PMS; Application ID for PMS; or Network Slice for PMS.

[0138] During a UE 102 access attempt for PMS using SMS or NIDD based messaging, the 5GS can be enhanced by characterizing and prioritizing the access attempts by indicating Establishmentcause as a new (e.g., dedicated or special purpose) value for pms-Priority Access or a new (e.g., dedicated or special purpose) value of hi ghPriority Access for PMS, and additionally a new (e.g., dedicated or special purpose) commercial priority IE (CPriority) in an RRCSetupRequest message. As such, the RAN node can take the MPS4msg priority and CPriority for a third-party user into account for managing radio resources for the UE 102.

[0139] CPriority IE indicates priority of the third party user using PMS, whereby CPriority can be set to indicate a priority level for the third party user based on operator’s policy and service level agreement with third party service provider, which as described earlier herein can be a binary indication (e.g. 0, 1 such that 0 means disabled for third party), an indication for priority level (e.g. High, Medium, Low), an integer value of the priority level (e.g. 0~10), or an enumerated value of the priority level (e g. pO, p5, .. ., plO), although aspects of the present disclosure are not limited thereto. When PMSI and 3PPriority are indicated, this indicates to thePATENT APPLICATION Attorney Docket No.: 31730 / 308600-00UE that the PMS for third party users is with priority level equal or lower than priority level for Service Users using MPS or MPS4msg. Based on the UE implementation, or RAN support, the CPriority may be the same as 3PPriority or different from 3PPriority stored in the UE context which is received from the network in the NAS message (Registration Accept or UE Configuration Update Command message).

[0140] Access identities can be in Table 3 below and similar to those illustrated in Table 1 earlier herein, with respect to Access Identity Y (where Y = 4, although aspects of the present disclosure are not limited thereto):

[0100] Further, Access Categories can be similar to those described with reference to Table 2, with an additional or alternative Access Category number as shown in Table 4:PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00

[0141] It is noted that if PMS only supports NIDD-based messaging, the type of access attempt can be PMS or NIDD based messaging for Access Category Z. If PMS supports both SMS and NIDD based messaging, the type of access attempt is an NIDD -based message for Access Category Z.

[0142] Access Control options may include configuring a new (e.g., dedicated or special purpose) Access Identifier for UE configured for a new (e.g., dedicated or special purpose) PMS for third party user for urgent event, (note that no new (e.g., dedicated or special purpose) access category is defined, i.e. the existing access category may be used). When a UE’s access attempt is SMS for PMS, the UE sets the Access ID to, e.g., Y, and the access category to, e.g., AC=6. When a UE’s access attempt is NIDD based messaging for PMS, the UE determines AID=Y (new (e.g., dedicated or special purpose)), and AC=7 (MO data).

[0143] Access Control options can further include defining a new (e.g., special purpose or dedicated) standardized value that defines UE I02’s access attempt type as NIDD based messaging for PMS. When a UE’s access attempt is SMS for PMS, the UE 102 determines AID=0, and AC=6, referring to Tables 1-4 herein. When a UE’s access attempt is NIDD based messaging for PMS, the UE 102 determines AID=0, and AC=Z (new (e.g., dedicated or special purpose)) from Tables 1-4 herein.

[0144] Access Control options can further include defining a new (e.g., special purpose or dedicated) standardized value that defines the UE 102 access attempt type as PMS (for both SMS and NIDD based messaging). When a UE’s access attempt is PMS using SMS, the UE 102 determines AID=0, and AC=Z (new (e.g., dedicated or special purpose) from Tables 1-4 herein).PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00When a UE’s access attempt is PMS using NIDD based messaging, the UE determines AID=O, and AC=Z (new (e.g., dedicated or special purpose)).

[0145] Referring to Fig. 9, the AF / AS 358 provisions 900, to the UDM 308, network configuration parameters of extended-MPS4msg for third party users to UDM based on an Nnef_ParameterProvision Service operation as described in TS 23.502, clause 4.15.6.2). The network configuration parameters can include: PMS indication (PMSI) which is to indicate enabling or disabling the PMS treatment for third party user using PMS-subscribed UE. When enabled, this indication is associated to an access identity for access attempt control. The network configuration parameters can include a new (e.g., dedicated or special purpose ) third party priority (3PPriority) indication IE, which can be set to indicate a priority level for the third party user based on operator’s policy and service level agreement with third party service provider, and its value can be as described earlier herein, e.g., a binary indication (e.g. 0, 1 to enable or disable the priority treatment), an indication for priority level (e.g. High, Medium, Low), an integer value of the priority level (e.g. 0~10), or an enumerated value of the priority level (e g. pO, p5, .. ., plO). When 3PPriority is indicated, this indicates to the network that the requested PMS is with priority level set by third party user which priority level should be equal or lower than priority level for Service Users using MPS / MPS4msg. The network configuration parameters can further include a preferred PMS type, e g., SMS or NIDD based Messaging, or both.

[0146] The UE 102 sends 902, to the network, a Registration Request message for negotiating the UE 102 and network capability support of SMS or NIDD based messaging. For example, the UE 102 can indicate "SMS supported" included in the Registration Request message, or the UE can indicate “Control Plane CIoT 5GS Optimization” or (new (e.g., dedicated or special purpose)) “NIDD based messaging” included in the Registration Request message for NIDD based messaging.

[0147] The AMF 364 obtains 904 subscription information from the UDM 308 and stores the information in the UE 102 context. For an eMPS4msg for a third-party user, the AMF 364 stores PMSI, 3PPriority indication, and allowed PMS type (e.g. SMS or NIDD-based messagingPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 service, based on Preferred PMS and UE subscription). For messaging service support, the following may be applied:

[0148] If “SMS supported” is indicated in Operation 702 (Fig. 7), the AMF 364 checks in theSMS Subscription data whether the SMS service is allowed to the UE 102, and the AMF 364 stores “SMS service is allowed” and optional “available SMSF of the serving PLMN” in the UE 102 context.

[0149] If “Control Plane CIoT 5GS Optimization” or “NIDD-based messaging is supported” is indicated in Operation 702, the AMF 364 checks in the Subscription data, e.g. messaging subscription or access and mobility subscription, whether the Control Plane CIoT 5GS Optimization or NIDD-based messaging service is allowed to the UE 102, and the AMF 364 stores “Control Plane CIoT 5GS Optimization is allowed” or “NIDD based messaging service is allowed” and optional “available SMF / NEF of the serving PLMN” in the UE 102 context.The AMF 364 may perform the following. First, the AMF 364 can activate SMS by sending, to the SMSF, an Nsmsf_SMService_Activate service operation based on a stored SMSF Address for an SMS based on registration procedure for SMS over NAS in TS23.502 clause 4.13.3.1; or the AMF 364 may activate NIDD based messaging through SMF / NEF by sending an Nsmf_PDUSession_PDUSession_CreateSMContext Request service operation to a selected SMF 366. Then the SMF366 sends an Nnef_SMContext_C reate Request to 1) NEF354 to establish an NEF PDU Session (based on TS23.502 clause 4.25.2) if PDU Session Establishment request is indicated in Registration Request message and an NEF address is stored at the UE 102 context, or 2) to a selected UPF to establish a UPF anchored PDU Session based on TS23.502 clause 4.3.2.2.1.

[0150] With the activation of SMS or NIDD based messaging, the messaging services can be expedited during urgent events. Alternatively, the NIDD based messaging services can be activated when the UE 102 initiates the messaging service procedure in Operation 720-726 (Fig. 7).

[0151] The AMF 364 determines 906 if the network supports PMS for a third-party user using SMS or NIDD based messaging based on the stored UE 102 context.PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00

[0152] The AMF 364 sends 908, to the UE 102, a Registration Accept message including PMS indication (PMSI) in 5GS network feature, 3Ppriority Indication IE, and allowed eMPS4msg type. If an allowed MPS4msg type is not provided, the AMF 364 indicates “SMS allowed” and / or “NIDD-based messaging allowed” with MPS4MI, and the UE 102 is allowed to use SMS and / or NIDD based messaging for MPS4msg.

[0153] If the UE 102 subscription is changed or needs to be provided, the network may perform a UE Configuration Update procedure 910 to update the UE 102 configuration, whereby a UE Configuration Update Command message includes a PMSI in priority indicator, a 3PPriority Indication, and an allowed PMS type. If the 3PPriority Indication is provided, the PMS is supported for the third-party user with the indicated 3PPrioirty. Otherwise, the priority level can be set based on operator’s policy and service level agreement with third party service provider.

[0154] The UE 102 stores 912 the PMSI, 3PPriority Indication, and allowed PMS type in the UE 102 context. The UE 102 receives 914 an upper layer request for an eMPS4msg for a third- party user using SMS or NIDD based messaging.

[0155] The UE 102 determines 916 the following for PMS for a third party user: (1) type of PMS for the service, e.g., SMS or NIDD based messaging, based on allowed PMS type or UE implementation based on network supported messaging information (SMS supported or NIDD based messaging supported or both); (2) access identity as Y (AID=Y), which is different from MPS / MPS4msg for Service Users, and the access category as MO data for PMS for third party user, or a new (e g., dedicated or special purpose) standardized value for PMS, or Operator- defined Access categories.

[0156] The UE 102 performs 918 an access attempt check. When the access attempt check for PMS for third party user is allowed, the UE initiates 920 an RRCSetupRequest message including (1) Establishmentcause as a new (e.g., dedicated or special purpose) value for pms- Priority Access or a new (e.g., dedicated or special purpose) value of highPriority Access for PMS; (2) a new (e.g., dedicated or special purpose) commercial priority IE (CPriority), whereby CPriority indicates priority of the third party user using PMS. The CPriority can be set toPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 indicate a priority level for the third party user based on operator’s policy and service level agreement with third party service provider, which can be a binary indication (e.g. 0, 1 such that 0 means disabled for third party), or an indication for priority level (e g. High, Medium, Low), or an integer value of the priority level (e.g. 0~10), or enumerated value of the priority level (e.g. pO, p5, . . . , plO). With 3PPriority, it indicates to the UE that the PMS for third party users is with priority level equal to or lower than priority level for Service Users using MPS / MPS4msg. Based on the UE implementation, or RAN support, the CPriority may be the same as 3PPriority or different from 3PPriority stored in the UE context which is received from the network in Operation 3008 or Operation 3010.

[0157] The NAS container contains a UL NAS Transport message in the following cases: (1) for delivering PMS using SMS or (2) for delivering PMS messaging data using NIDD based messaging or (3) for requesting NEF / UPF anchored PDU Session for NIDD based messaging if not activated during registration procedure in Operation 4004.

[0158] Accordingly, the RAN node can take Establishmentcause, and CPriority into account for managing radio resources for the UE using PMS. If the RAN node rejects the access attempt, it rejects the RRCSetup Request with proper reject cause for PMS.

[0159] Operation 922 may be similar to operation 722 (Fig. 7).

[0160] The AMF 364 performs the following. For PMS using SMS, when the AMF 364, receiving an SMS message, determines the UE 102 has the PMSI indication in UE 102 context as specified in Operation 704 (Fig. 7), the AMF 364 sends 924A, to the SMSF, an Nsmsf SMService UplinkSMS message which include an SMS message and the Message Priority header indicated with a value appropriate for MPS4msg to indicate priority treatment based on stored PMSI and 3PPriority indication in the UE context. The related procedure can be based on TS23.502 clause 4.13.3.3, MO SMS over NAS.

[0161] For PMS using NIDD based messaging, when the AMF 364 receives an MO data payload for NIDD based messaging, the AMF 364 includes a Message Priority header indicated with a value appropriate for PMS to indicate priority treatment based on a stored PMSI and 3PPriority indication in the UE 102 context. The related procedure can be based on an NEFPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00Anchored Mobile Originated Data Transport procedure in TS23.502 clause 4.25.4 or UPF anchored Mobile Originated Data Transport in Control Plane CIoT 5GS Optimization procedure based on TS23.502 clause 4.24.1.

[0162] If an NEF (or UPF anchored) PDU Session is not established and the AMF determines that the UE 102 has the PMSI indication in the UE 102 context in Operation 704 , the AMF 364 receives a UL NAS Transport message with a PDU Session Establishment Request message indicating a PDU Session ID, an S-NSSAI for a third party user using MPS4msg, and / or a DNN for a third party user using MPS4msg.

[0163] To create an NEF PDU Session, the AMF sends 924B, to the SMF, anNsmf PDUSession CreateSMContext Request message and the SMF creates 926B1 a PDU session towards the NEF by sending an Nnef_SMContext_Create Request message to the NEF. Then the NEF creates NEF PDU Session and invokes Nnef_SMContext_Create Response towards the SMF confirming establishment of the NEF PDU session for the UE). The related operations for NEF PDU Session Establishment are based on TS23.502 clause 4.25.2.

[0164] To create UPF anchored PDU Session, the related operations are based messaging based on TS23.502 clause 4.3.2.2.1.

[0165] Operation 926-928 can be like similarly numbered operations illustrated in Fig. 7.

[0166] Fig. 10 is a flowchart illustrating a method 1000, implemented in a UE (e.g., UE 102).

[0167] The method 1000 can begin with the UE receiving 1008, from a CN via a RAN, an indication that priority treatment is enabled for an AID corresponding to a PMS for a third-party user (see e.g., events 508 and 510).

[0168] The method 1000 can continue with the UE 102 establishing 1020, with the RAN, a radio connection for the PMS (see e.g., events 920, 926, or 928).

[0169] The method 1000 can further include transmitting, to the CN and prior to the receiving of the indication that the priority treatment is enabled for the AID, an indication that the UE supports non-IP data delivery (NIDD) and / or a short message service (SMS) (see e.g., event 902). The method 1000 can further comprise receiving, from the CN, an indication of a priorityPATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 level for the PMS. The priority level can be one of High, Medium, or Low. The priority level can be an enumerated value. The priority level for the PMS can be lower than a respective priority level of each of Multimedia Priority Service (MPS) for an authorized user or a Mission Critical Service (MCS).

[0170] The method 1000 can further comprise receiving, from the CN, an indication a type of service allowed to operate as the PMS. The method 1000 can further comprise receiving, from the CN, an indication of the AID defined by an operator of the CN. The indication that the priority treatment is enabled for the AID can be included in one of (i) registration accept message or (ii) a UE configuration update command.

[0171] The method 1000 can further comprise determining, for the PMS, an access category as one of (i) mobile-originated (MO) data for the PMS, (ii) a value dedicated to the PMS, or (iii) an operator-defined value; performing, at the UE, an access control check based on the access category (see, e.g., event 916 or 918). Establishing of the radio connection for the PMS can include transmitting, to the RAN, a request to establish the radio connection, the request including an establishment cause indicating priority access for the PMS (see e.g., event 920). The request can further include a commercial priority information element (IE) to indicate a level of priority for the PMS. The request can further include a non-access stratum (NAS) container that contains an uplink (UL) NAS Transport message including a message associated with the PMS.

[0172] The method 1000 can further include receiving a request for the priority treatment from an upper layer; wherein the establishing of the radio connection is in response to (i) the request from the upper layer and (ii) determining that the UE received the indication that the priority treatment is enabled for the AID (see e.g., event 914).

[0173] Example 1. A method for access control implemented in a user equipment (UE), the method comprising: receiving, from a third-party user, an upper layer request related to priority messaging services (PMS); transmitting a connection method including an EstablishmentCause for priority messaging upon determining that an access control list authorizes the third-party user for PMS and attempting a mitigation action otherwise.PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00

[0174] Example 2. The method of Example 1, wherein PMS is requested for Short Messaging Service (SMS) or non-IP data delivery (NIDD)-based messaging. UE does not have a PMS subscription information stored in memory for the third-party user.

[0175] Example 3. The method of any of the preceding examples, wherein the mitigation action includes, after a wait time duration, re-attempting access.

[0176] Example 4, The method of any of the preceding examples, wherein the mitigation action includes selecting a different cell.

[0177] Example 5. A user equipment (UE) comprising: a transceiver; and processing hardware; wherein the UE is configured to implement a method of any of the preceding Examples.

[0178] The following description may be applied to the description above.

[0179] Generally speaking, description for one of the above figures can apply to another of the above figures. Examples, implementations and methods described above can be combined, if there is no conflict. An event or block described above can be optional or omitted. For example, an event or block with dashed lines in the figures can be optional. In some implementations, “message” is used and can be replaced by “information element (IE)”, and vice versa. In some implementations, “IE” is used and can be replaced by “field”, and vice versa. In some implementations, “configuration” can be replaced by “configurations” or “configuration parameters”, and vice versa. The “attach” can be replaced by “registration”. The “Attach” can be replaced by “Registration”. The “EPS attach type” can be replaced by “5GS registration type”. “EPS emergency attach” can be “emergency registration”. The “emergency messaging service” can be replaced by “emergency SMS” or “emergency messaging services”. The “emergency messaging” can be replaced by “emergency SMS” or “emergency messaging service(s)”. “via a cell” can be replaced by “via a satellite”, “via the cell” can be replaced by “via the satellite”.

[0180] In some implementations, the “PDN connectivity procedure” can be replace by “PDU session establishment procedure”. In such cases, the “PDN Connectivity Request” and “Activate Default EPS Bearer Context Request” can be replaced by “PDU Session Establishment Request”PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 and “PDU Session Establishment Accept”, respectively and the “Activate Default EPS Bearer Context Accept” is omitted.

[0181] A user device in which the techniques of this disclosure can be implemented (e.g., the UE 102) can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media-streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an intemet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general -purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0182] Certain embodiments are described in this disclosure as including logic or a number of components or modules. Modules may be software modules (e.g., code, or machine-readable instructions stored on non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

[0183] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. ThePATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 software may be executed by one or more general-purpose processors or one or more specialpurpose processors.

Claims

PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00Claims:

1. A method for priority messaging implemented in a user equipment (UE), the method comprising: receiving, from a core network (CN) via a radio access network (RAN), an indication that priority treatment is enabled for an access identity (AID) corresponding to a priority messaging service (PMS) for a third-party user; and establishing, with the RAN, a radio connection for the PMS.

2. The method of claim 1, further comprising: transmitting, to the CN and prior to the receiving of the indication that the priority treatment is enabled for the AID, an indication that the UE supports non-lP data delivery (N1DD) and / or a short message service (SMS).

3. The method of claim 1 or 2, further comprising: receiving, from the CN, an indication of a priority level for the PMS.

4. The method of claim 3, wherein the priority level is one of High, Medium, or Low.

5. The method of claim 3, wherein the priority level is an enumerated value.

6. The method of any of claims 3-5, wherein the priority level for the PMS is lower than a respective priority level of each of Multimedia Priority Service (MPS) for an authorized user or a Mission Critical Service (MCS).

7. The method of any of the preceding claims, further comprising: receiving, from the CN, an indication a type of service allowed to operate as the PMS.

8. The method of any of the preceding claims, further comprising:PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-00 receiving, from the CN, an indication of the AID defined by an operator of the CN.

9. The method of any of the preceding claims, wherein: the indication that the priority treatment is enabled for the AID is included in one of (i) registration accept message or (ii) a UE configuration update command.

10. The method of any of the preceding claims, further comprising: determining, for the PMS, an access category as one of (i) mobile-originated (MO) data for the PMS, (ii) a value dedicated to the PMS, or (iii) an operator-defined value; and performing, at the UE, an access control check based on the access category.

11. The method of any of the preceding claims, wherein the establishing of the radio connection for the PMS includes: transmitting, to the RAN, a request to establish the radio connection, the request including an establishment cause indicating priority access for the PMS.

12. The method of claim 11, wherein the request further includes: a commercial priority information element (IE) to indicate a level of priority for the PMS.

13. The method of claim 11 or 12, wherein the request further includes: a non-access stratum (NAS) container that contains an uplink (UL) NAS Transport message including a message associated with the PMS.

14. The method of any of the preceding claims, further comprising: receiving a request for the priority treatment from an upper layer; wherein the establishing of the radio connection is in response to (i) the request from the upper layer and (ii) determining that the UE received the indication that the priority treatment is enabled for the AID.PATENT APPLICATIONAttorney Docket No.: 31730 / 308600-0015. A user equipment (LE) comprising: processing hardware; and a transceiver; the UE configured to implement a method of any of the preceding claims.

Images