Enabling priority services in wireless communication systems

Abstract

To access a radio access network (RAN), a user equipment (UE) receives (304), in a cell of the RAN, an indication that the cell supports a priority service. The UE initiates (308), in a cell of the RAN, a priority service based on a configuration other than a Service User subscription. The UE communicates (318), via the RAN, data packets associated with the priority service.

Description

PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00ENABLING PRIORITY SERVICES IN WIRELESS COMMUNICATION SYSTEMSCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to and the benefit of the filing date of provisional U.S. Patent Application No. 63 / 709,403 entitled “Enabling Priority Services in Wireless Communication Systems,” filed on October 18, 2024. The entire content of the provisional application is hereby expressly incorporated herein by reference).FIELD OF THE DISCLOSURE

[0002] This disclosure relates generally to wireless communication systems, and particularly to enabling priority services for a user equipment (UE).BACKGROUND

[0003] 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.

[0004] Generally speaking, a base station operating a cellular radio access network (RAN) communicates with a user equipment (UE) using a certain radio access technology (RAT) and multiple layers of a protocol stack. For example, the physical layer (PHY) of a RAT provides transport channels to the Medium Access Control (MAC) sublayer, which in turn provides logical channels to the Radio Link Control (RLC) sublayer, and the RLC sublayer in turn provides data transfer services to the Packet Data Convergence Protocol (PDCP) sublayer. The Radio Resource Control (RRC) sublayer is disposed above the PDCP sublayer.

[0005] The RRC sublayer specifies the RRC_IDLE state, in which a UE does not have an active radio connection with a base station and does not store a UE access stratum (AS) context; the RRC_CONNECTED state, in which the UE has an active radio connection with the base station; and the RRC_INACTIVE to allow a UE to more quickly transition back to thePATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00RRC_CONNECTED state due to Radio Access Network (RAN)-level base station coordination and RAN-paging procedures. Depending on different implementations or scenarios, the base station can configure Small Data Transmission (SDT) for the UE operating in the RRC_INACTIVE to transmit one or more small packets.

[0006] The 5G technology relies primarily on legacy terrestrial networks. However, the 3rd Generation Partnership Project (3GPP) organization has proposed to extend 5G communications to non-terrestrial networks (NTNs) with 5G new radio (NR) technologies, or with the Long- Term-Evolution (LTE) technologies tailored for the Narrowband Internet-of-Thing (NB-loT) or the enhanced Machine Type Communication (eMTC) scenarios. In an NTN, an RF transceiver is mounted on a satellite, an unmanned aircraft system (UAS), also called drone, balloon, plane, or another suitable apparatus. For simplicity, the discussion below refers to all such apparatus as satellites. In addition to satellites, an NTN can include the sat-gateways that connect the NonTerrestrial Network to a public data network, feeder links between sat-gateways and satellites, service links between satellites and UEs, and inter-satellite links (ISL) when satellites form constellations.

[0007] A satellite can belong to one of several types based on altitude, orbit, and beam footprint size. The types include Low-Earth Orbit (LEO) satellite, Medium-Earth Orbit (MEO) satellite, Geostationary Earth Orbit (GEO) satellite, UAS platform (including High Altitude Platform Station, HAPS), and High Elliptical Orbit (HEO) satellite. GEO satellites are also known as the Geosynchronous Orbit (GSO) satellites, and LEO / MEO satellites are also known as the non-GSO (NGSO) satellites.

[0008] A GSO satellite is stationary relative to the Earth’s surface and can communicate continuously with same one or several sat-gateways within a satellite targeted coverage area (e.g., a region or even a continent). In contrast, the location of a non-GSO satellite changes its location relative to the Earth's surface over time and, at certain times, can communicate only temporarily with one or several serving sat-gateways. An NTN is designed to ensure service and feeder link continuity between successive serving sat-gateways, with sufficient time duration to proceed with mobility anchoring and hand-over.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0009] A satellite can support a transparent or a regenerative (with on-board processing) payload, and typically generates several beams for a given service area bounded by the field of view. The footprints of the beams typically have an elliptic shape and depend on the on-board antenna configuration and the elevation angle. For a transparent payload implementation, a satellite can apply RF filtering and frequency conversion and amplification, and not change the waveform signal. For a regenerative payload implementation, a satellite can apply RF filtering, frequency conversion and amplification, demodulation and decoding, routing, and coding / modulation. This approach is effectively equivalent to implementing most of the functions of a base station, e.g.. a gNB.

[0010] NB-IoT and eMTC technologies are expected to be particularly suitable for loT devices operating in remote areas with limited or no terrestrial connectivity. Such ToT 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- loT or eMTC is defined in a complementary manner to terrestrial deployments.

[0011] 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 have to rely on public network services when the communication capability of the serving network may be impaired, for example due to congestion or partial network infrastructure outages. To address these and other limitations, 3GPP introduced Multimedia Priority Service (MPS).

[0012] More particularly, 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 is a 3GPP feature designed so that National Security or Emergency Preparedness (NS / EP) subscribers can make priority calls or establish data sessions on a Service Providers network, particularly at times of congestion. MPS is provided only for the ServicePATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00Users which are government- authorized personnel, emergency management officials, and / or other authorized users.

[0013] Further, a Mission Critical Service (MCx Service) is a communication service with capabilities for mission critical applications. End users from mission critical organizations (e.g. public utilities, railways) and users of mission critical applications can gain access to an MCx Service such as Mission Critical Push To Talk (MCPTT) as defined in 3GPP TS 23.379, Mission Critical Video (MCVideo) as defined in 3GPP TS 23.281, or Mission Critical Data (MCData) as defined in 3GPP TS 23.282.

[0014] There is no mechanism in a 3GPP network to offer priority treatment for a UE using messaging services for urgent events or to differentiate between UEs initiating messages for urgent events from UEs initiating “normal,” non-urgent messaging services.

[0015] Further, it is unclear how the functionality of a core network, such as a 5GS, can be enhance to support MPS for IMS Messaging and Short Message Service (SMS) including SMS over non-access stratum (NAS) and SMS over Internet Protocol (IP). Currently, MPS is not supported for NB-IoT because NB-IoT is defined specifically for loT devices, which are a type of a UE used by non-human entities for machine type communication. Because it is possible to deploy an NB-IoT NTN to provide messaging services for human-operated UEs and for loT devices, there is a lack of functionality that would allow Service Users to utilize the NB-IoT NTN to perform MPS for National Security or Emergency Preparedness, especially when TNs are not available. It is not clear how NB-IoT can support MPS.

[0016] For similar reasons, there is no support of MCx Services for NB-IoT, and it remains impossible for MCx Service subscribers to utilize an NB-IoT NTN for an MCx Service.

[0017] Further, because loT devices have limited memory, SMS and IMS protocol stacks (which require a certain amount of memory) are generally unsuitable for these devices. Still further, loT devices and technology (e.g., NB-loT) only support low-data-rate communications, whereas SMS and IMS protocols are not suitable for low-data-rate communications. Some loT devices accordingly support messaging services with Non-Internet Protocol Data Delivery (NIDD)), i.e., NIDD-based messaging services, rather than supporting SMS over NAS or SMSPATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 over IP. It is not clear how to provide support of MPS for NIDD-based messaging services, or how to support an MCx Service for NIDD-based messaging services in a 3GPP system.SUMMARY

[0018] An example embodiment of the techniques of this disclosure is a method for accessing a radio access network (RAN). The method is implemented in a user equipment (UE) and comprises receiving, in a cell of the RAN, an indication that the cell supports a priority service; initiating, in a cell of the RAN, a priority service based on a configuration other than a Service User subscription; and communicating, via the RAN, data packets associated with the priority service.

[0019] Another example embodiment of these techniques is a method for accessing a RAN, the method implemented in a UE and comprising: receiving, in a cell that operates using a low- power wide area network (LPWA) technology, an indication of support of a priority service; and initiating the priority service in the cell using a Non-Internet Protocol Data Delivery (NIDD)- based messaging service.

[0020] Another example embodiment of these techniques is a UE comprising a transceiver; and processing hardware. The UE is configured to implement one of the methods above.

[0021] Still another example embodiment of these techniques is a method for supporting a priority service. The method is implemented in a RAN and comprises transmitting, in a cell, an indication that the cell supports a priority service; and receiving, from a UE, a request to initiate the non-emergency priority service.

[0022] Another example embodiment of these techniques is a method for supporting a priority service. The method is implemented in a RAN and comprises transmitting, in a cell, an indication that the cell supports a non-emergency priority service; receiving, from a UE, a request to initiate the non-emergency priority service; and communicating, with the UE, data packets associated with the priority service using a NIDD-based messaging service.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0023] 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

[0024] 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.

[0025] Fig. 1 is a block diagram of an example wireless communication system in which a user device and a base station can support priority services using the techniques of this disclosure;

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

[0027] Fig. 3 is a messaging diagram of an example scenario in which a UE initiates a priority service other than one based on a Service User subscription, and the cell of a RAN indicates support of this priority service;

[0028] Fig. 4 is a messaging diagram of an example scenario generally similar to that of Fig.3, but with the UE and an NB-IoT cell using an MPS as the priority service;

[0029] Fig. 5 is a messaging diagram of an example scenario generally similar to that of Fig.3, but with the UE and an NB-IoT cell using an MCx as the priority service;

[0030] Fig. 6A is a flow diagram of an example method in a UE for initiating a priority service and performing an access barring check to determine whether the UE can access a cell for communicating data packets associated with the priority service;

[0031] Fig. 6B is a flow diagram of an example method generally similar to that of Fig. 6A, but according to which the UE checks whether the UE received a barring configuration for the cell;PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0032] Fig. 7 is a flow diagram of an example method in a UE for initiating a priority service and transmitting a specific cause for the priority service in an RRC message;

[0033] Fig. 8A is a flow diagram of an example method in a UE for initiating a priority service and transmitting a specific cause for the priority service in an RRC message, when the cell supports the specific cause;

[0034] Fig. 8B is a flow diagram of an example method in a UE for initiating a priority service and transmitting a specific cause for the priority service in an RRC message, when the UE is configured for the priority service;

[0035] Fig. 8C is a flow diagram of an example method in a UE for initiating a priority service and transmitting a specific cause for the priority service in an RRC message, when a downlink message from RAN and / or the CN includes a priority service indicator;

[0036] Fig. 8D is a flow diagram of an example method in a UE for initiating a priority service and transmitting a specific cause for the priority service in an RRC message, when the cell supports the specific cause and when the UE is configured for the priority service;

[0037] Fig. 9 is a flow diagram of an example method in a UE for determining whether the UE is configured for a priority service based on a downlink message received from the network;

[0038] Fig. 10 is a flow diagram of an example method in a UE for determining whether the UE is configured for a priority service based on the information in a USIM;

[0039] Fig. 11 is a flow diagram of an example method in a RAN for receiving, from a UE, a cause value indicating a priority service;

[0040] Fig. 12 is a flow diagram of an example method in a CN for configuring a UE for a priority service;

[0041] Fig. 13 is a flow diagram of an example method in a CN for configuring a UE for a priority service based on whether the UE qualifies for a priority service;

[0042] Fig. 14 is a flow diagram of an example method in a UE for initiating a priority service via a certain type of a RAN node;PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0043] Fig. 15 is a flow diagram of an example method in a RAN for supporting priority services via NB-IoT and non-NB-IoT nodes; and

[0044] Fig. 16 is a flow diagram of an example method in a CN for configuring UEs for priority services via NB-IoT and non-NB-IoT nodes.DETAILED DESCRIPTION OF THE DRAWINGS

[0045] In some of the implementations discussed below, a user equipment (UE) initiates, in a cell of a radio access network (RAN), a priority service based on a configuration other than a Service User subscription. The UE thus need not be associated with an authorized user. The cell can be a non-terrestrial network (NTN) cell that operates using a low-power wide area network (LPWA) technology.

[0046] Further, in some implementations also discussed below, a UE can receive, in an NTN cell that operates using LPWA technology, an indication of support of a priority service, and initiate the priority service in the NTN cell using a NIDD-based messaging service. The priority service in this case is associated with a Service User subscription.

[0047] 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 a NTN and a TN. For example, the base 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.

[0048] 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 NarrowBandPATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00Internet 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-IoT 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, 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).

[0049] NB-IoT 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.

[0050] 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 (6GC) 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 transfer 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 MobilityPATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00Management 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.

[0051] 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.

[0052] 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, 184 connects to the UDM 172 via an interface. In yet otherPATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 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.

[0053] As illustrated in Fig. 1A, the base station 104 supports a cell 124, and the base station 106 supports a cell 126. If the cell 124 is a 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.

[0054]

[0055] 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. 1A, 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 priority services, as discussed below.

[0056] 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.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0057] 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.

[0058] 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).

[0059] 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 sublayer 208) that can be referred to as service data units (SDUs), and output packets (e.g., to the RLC sublayer 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, the PHY layer 202, MAC sublayer 204, RLC sublayer 206, PDCP sublayer 208, RRC sublayer 210 are NR layers or sublayers.

[0060] The RRC sublayer 210 provide data transfer services to a Non- Access-Stratum (NAS) layer 212. The NAS layer 212 includes a mobility management (MM) sublayer and / or a sessionPATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 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.

[0061] 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.

[0062] Next, several example scenarios that involve several components of Figs. 1-2 are discussed next with reference to Figs. 3-5, followed by a discussion of several example methods with reference to Figs. 6-16. The UE 102 and the base station 104 in these scenarios can communicate with each other via satellite or terrestrial antennas and using the NB-IoT radio access technology (RAT), satellite NB-IoT RAT (i.e., NB-IoT NTN), E-UTRA RAT, satellite E- UTRA RAT, NR RAT, satellite NR RAT, 6G-I0T RAT, 6G RAT, satellite 6G RAT, or satellite 6G-I0T RAT.

[0063] Generally speaking, events, messages, blocks, etc. in Figs. 3-16 that are similar are labeled with similar reference numbers (e.g., event 314 of Fig. 3 is similar to event 414 of Fig 4, event 514 of Fig. 5, and block 614 of Figs. 6A and 6B, blocks 714-1 and 714-2 of Fig. 7, block 814 of Figs. 8A-8D, blocks 1114-1 and 1114-2, and blocks 1414-land 1414-2), with differences discussed below where appropriate. With the exception of the differences shown in the figures and discussed below, any of the alternative implementations discussed with respect to a particular event (e.g., for messaging and processing) may apply to events labeled with similar reference numbers in other figures.

[0064] Prior to the discussion of Fig. 3, example MPS, MCx, and third-party messaging approaches are briefly considered.

[0065] Generally speaking, MPS allows qualified and authorized users to obtain priority access to the next available radio channel on a priority basis before other Public Land MobilePATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00Network (PLMN) users, in situations when PLMN congestion is blocking session establishment attempts. The qualified Service Users must be are government- authorized personnel, emergency management officials and / or other authorized users. An MPS can support priority sessions on an “end-to-end” priority basis and can include signaling priority and media priority. An MPS can provides the ability to invoke, modify, maintain and release sessions with priority, as well deliver the priority media packets under network congestion conditions.

[0066] MPS priority mechanisms can include subscription-related and invocation-related mechanisms. The subscription-related mechanisms in turn can include those that apply at all times and those that apply conditionally. The invocation-related mechanisms can include a category for mobile originated Session Initiation Protocol (SIP) call / sessions, a category for mobile terminated SIP call / sessions, and a category for Priority PDU connectivity services. MPS can provide priority treatment to increase the probability of an authorized Service User’s Voice, Video, and Data communication session being successful. A type of priority treatment can apply to the MPS invocation and session establishment, and can continue to apply until the MPS session is released. The priority treatment can apply before the invocation if a greater probability of success in receiving, recognizing, and processing the invocation is needed

[0067] Operator policy and / or local regulation can define MCx Services. MCx Services are based on the ability to invoke, modify, maintain and release sessions with priority, and deliver the priority media packets under network congestion conditions. In general, MCx Users require network functionality that supports real-time, dynamic, secure and limited interaction with the quality of service (QoS) and policy framework for modification of the QoS and policy framework by authorized users. The limited interaction is based on the operator policy, and provides specific limitations on what aspects of the QoS and policy framework an authorized MCx User can modify.

[0068] MCx Services can be supported in a roaming environment subject to roaming agreements and regulatory requirements. An MCx-subscribed UE can obtain priority access to the RAN using the Unified Access Control (UAC) mechanism, which can provides preferential access to UEs based on its assigned Access Identity. If an MCx-subscribed UE belongs to the special Access Identity (as defined in 3GPP TS 22.261, for example), the UE has preferentialPATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 access to the network compared to ordinary UEs in periods of congestion. MCx subscription allows users to receive priority services, if the network supports MCx. MCx subscription provides a USIM with a special Access Identity.

[0069] In is possible for a third party to support commercial messaging services for urgent events for UEs using normal (regular) sessions, over a 3GPP system and using terrestrial access and / or satellite. For example, a message for an urgent event can travel to an urgent contact preconfigured by the user / UE via a third party application server. The application server then subsequently dispatches the message for the urgent event to the preconfigured urgent contact.

[0070] Fig. 3 illustrates an example scenario 300 involving a UE 102, a RAN 105 and a CN 110. Initially, the UE 102 is configured 302 for a certain priority service or services other than the existing MPS or MCx services, referred to below as a “new” or “special” priority service. For simplicity, “service” can refer to “service or services.” In some implementations, when the UE 102 is configured for the new priority service, and the UE initiates a service (e.g. event 308), the service is a priority service. That is, the service has a higher priority treatment than the same service that the UE 102 initiates without being configured for the new priority service. In some implementations, the new priority service is none of an emergency service, the MPS and / or the MCx Service (MCS). In some implementations, a priority treatment of the new priority service is lower than the emergency service, the MPS and / or the MCS.

[0071] In some implementations, the priority of the new priority service to which a user of a third party subscribes is lower than the same service to which a Sendee User subscribes. In some implementations, a first new priority service to which a user of a third party subscribes is different than a second new priority service to which a Service User subscribes. In other words, the system can support two different new priority services for different subscribers, and the priority of the service for the Service User is higher than the priority of the user of a third party. In some implementations, when the UE 102 is configured for the new priority service, a priority treatment for the new priority service generally refers to services (e.g., voice, video or messaging, etc.) that the UE 102 supports and may initiate. In other implementations, the new priority service refers to a specific service (e.g., messaging service). In some implementations,PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 the messaging service is SMS. In other implementations, the messaging service is a NIDD messaging service, which is different from the SMS.

[0072] In some implementations, the UE 102 determines whether the UE 102 is configured for the new priority service based on information the UE 102 reads from a Universal Subscriber Identity Module (USIM). The UE 102 in one example implementation determines 302 that the UE 102 is configured for the new / special priority service based on the information in the USIM. For example, the UE 102 reads an elementary file (EF) from the USIM. The EF includes a specific indication (e.g., one or more specific bits) for the new priority service. If the specific indication is set to a first value, the UE 102 determines that the UE 102 is configured for the new priority service. Otherwise, if the specific indication is set to a second value, the UE 102 determines that the UE 102 is not configured for the new priority service. In some implementations, the EF is an existing EF defined in 3GPP specification 31.102. For example, the existing EF is an EFUAC_AIC for unified access control (UAC) Access Identities Configuration. The specific indication is a bit in the existing EF (e.g., bit N where N is an integer larger within a value range 2 < N < 8). If the bit is set to 1, the UE 102 determines that the UE 102 is configured for the new priority service. If the bit is set to 0, the UE 102 determines that the UE 102 is not configured for the new priority service. If the UE 102 determines that the UE 102 is configured for the new priority service, the UE 102 may determine that the UE 102 is configured with an access identity M for the new priority service, where M is an integer and 3 < M < 11.

[0073] In other implementations, the EF is a new (dedicated, special-purpose) EF defined in a version of 3GPP specification 31.102 that augments a prior version without this EF. In one implementation, the new EF includes a bit (e.g., bit N where N is an integer larger within a value range 0 < N < 8). In another implementation, the new EF includes the access identity M for the new priority service. In some implementations, the new EF is defined for one or more specific RATs described above. In some implementations, the new EF may include RAT information indicating one or more RATs where the UE 102 is configured for the new priority service. For example, the RAT information indicates that 6G and / or NR are the RATs in which the UE 102 is configured for the new priority service. In another example, the RAT information indicates thatPATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 the UE 102 is configured for the new priority service in E-UTRA or non-IoT E-UTRA . In yet another example, the RAT information indicates that the UE 102 is configured for the new priority service in satellite NB-IoT. In other implementations, the new EF does not include RAT information. In such cases, the UE 102 applies the new EF to RATs that supports the new priority service.

[0074] In other implementations, the UE 102 determines whether the UE 102 is configured for the new priority service based on a pre-configuration stored in the UE 102 (e.g., non-volatile memory). In this case, the UE 102 determines 302 that the UE 102 is configured for the new priority service. In some implementations, the UE 102 may receive, from a server, an over-the- air (OTA) message including a new pre-configuration updating the pre-configuration. In cases where the stored pre-configuration indicates that the UE 102 is configured for the new priority service, the new pre-configuration indicates that the UE 102 is not configured for the new priority service. In such cases, the UE 102 determines, in response to the new pre-configuration, that the UE 102 is not configured for the new priority service.

[0075] In other implementations, the UE 102 determines whether the UE 102 is configured for the new (dedicated, special-purpose) priority service based on a UE context stored in the UE 102. In the scenario of Fig. 3, the UE 102 can determine 302 that the UE 102 is configured for the new priority service. In some implementations, the UE 102 receives, from the AMF 164 operating in the CN 110, a NAS message including a new priority service indicator. The UE stores the new priority service indicator in the UE context, which indicates that the UE 102 is configured for the new priority service. When the UE context does not store the indicator for the new priority service, the UE 102 is not configured for the new priority service. For example, the network can configure the UE via NAS signaling by including new priority service indicator as a part of the information in the 5GS network feature IE, included in a Registration Access message during a registration request procedure. The new priority service indicator includes a specific standardized value of access identity. For example, the AMF 164 in the CN 110 configures the UE via NAS signaling message by including a new priority service indicator in a UE Configuration Update Command message during a UE configuration update procedure, and thePATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 new priority service indicator in this case includes a specific standardized value of access identity.

[0076] The UE 102 receives 304 system information from the RAN 105 via a serving cell (e.g., cell 124). The system information may include one or more system information blocks (SIBs). In some implementations, the system information (e.g., a first SIB) may include a baring configuration. Alternatively, the system information does not include a barring configuration. In some implementations, the system information (e.g., the first SIB or a second SIB) includes a new priority service indicator that indicates that the cell 124 supports processing a new priority service indication received from a UE as described below. In some implementations, the new priority service indication is a new (dedicated, special-purpose) RRC establishment cause, which can augment the definitions in 3GPP specification 38.331 or 36.331. In other implementations, the new priority service indication is a new RRC resume cause that augments the definitions in 3GPP specification 38.331 or 36.331. Alternatively, the system information does not include the new priority service indicator.

[0077] Before or after receiving 304 the system information, the UE 102 may receive 305 a downlink (DL) NAS message from the CN 110, via the RAN 105 and the serving cell. The DL NAS message may include a new / special priority service indicator. In some implementations, the new priority service indicator is set to a first value (e.g., 1) to indicate that the UE 102 is configured for the new priority service. Thus, the UE 102 determines that the UE 102 is configured for the new priority service in response to the new priority service indicator having the first value. In some implementations, if the new priority service indicator is set to a second value (e.g., 0), the UE 102 determines that the UE 102 is not configured for the new priority service. In some implementations, the DL NAS message is a Registration Accept message, which the CN 110 transmits in response to a Registration Request message from the UE. In other implementations, the DL NAS message is a UE Configuration Update Command message.

[0078] Further, before or after receiving 304 the system information, the UE 102 may receive 307 a DL RRC message from the RAN 105. The DL RRC message may include a new / special priority service indicator. In some implementations, the DL RRC message is an RRC release message (e.g., an RRCRelease message or an RRCConnectionRelease message). The RRCPATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 release message may include redirection information redirecting the UE 102 to a target cell. In other implementations, the DL RRC message is a Paging message. The UE 102 may use the new priority service indicator to determine an access identity (e.g., the access identity M) for an access attempt for the service as described in connection with the event 305.

[0079] After receiving 304 the system information, the UE 102 initiates 308 a service. In some implementations, the service a mobile originated (MO) service. In other implementations, the service is a mobile terminated (MT) service initiated in response to receiving 307 the Paging message. In some implementations, the service is a messaging service as described above. In other implementations, the service is a voice call or a video call. In some implementations, the UE 102 determines 310 an access identity associated with the service (e.g., the access identity associated with an access attempt for initiating the service). In some implementations, the UE 102 determines 310 the access identity M associated with the service as described above.

[0080] In some implementations, the UE 102 determines 310 an access category associated with the service. In some implementations, the access category is an integer K. In one implementation, 10 < K < 32. For example, K is a value indicating the MO service. In another implementation, 0 < K < 11. For example, K is a value (e.g., 10) indicating MO exception data. In another example, A is a value (e.g., 0) indicating MT access. In other implementations, the UE 102 does not determine an access category.

[0081] In some implementations, when the baring configuration is applicable or configured to the service, the UE 102 performs 312 an access barring check for the access attempt for the service based on the baring configuration, the access identity, and / or the access category.

[0082] In some implementations, if the access barring check indicates that the access attempt is allowed, and the UE 102 operates in an idle state, the UE 102 may perform 314 an RRC connection establishment procedure with the RAN 105 via the serving cell. In other implementations, if the access barring check indicates that the access attempt is allowed, and the UE 102 operates in an idle state, the UE 102 may perform 314 a RRC connection resume procedure with the RAN 105 via the serving cell. In some implementations, if the UE 102 has a stored UE context or a suspended RRC connection, the UE 102 performs 314 the RRC resumePATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 procedure. Otherwise, if the UE 102 does not have a stored UE context or a suspended RRC connection, the UE 102 performs 314 the RRC connection establishment procedure. If the access barring check indicates that the access attempt is allowed, and the UE 102 operates in an inactive state, the UE 102 performs 314 an RRC connection establishment procedure with the RAN 105. In the case of receiving 307 the RRC release message, the UE 102 performs 314 the RRC connection establishment procedure or the RRC connection resume procedure with the RAN 105 via the target cell instead of the serving cell.

[0083] During the procedure 314, the UE 102 transmits an RRC request message to the RAN 105, receives an RRC response message from the RAN 105 in response to the RRC request message, and may transmit a RRC complete message to the RAN 105 in response to the RRC response message. In some implementations, the RRC response message includes configuration parameters that configure a connection between the UE 102 and the RAN 105. The connection may include a signaling radio bearer (SRB) such as an SRB1. The UE 102 configures the connection based on the configuration parameters. In some implementations, the UE 102 transitions to a connected state in response to the RRC response message. The UE 102 may transmit the RRC response message via the connection (e.g.. SRB1) to the RAN 105. In some implementations, the UE 102 includes a cause (e.g., an establishment cause or a resume cause) in the RRC request message. The RAN 105 may use the cause to determine whether to accept or reject the RRC request, e.g. while the RAN 105 or the CN 110 is congested. In some implementations, the UE 102 sets the cause to a specific value, based on the access identity and / or access category. In other implementations, the UE 102 sets the cause to a specific cause value indicating that the UE 102 is configured for the new / special priority service. In some implementations, the cause value indicates the RRC request pertains to the new priority service, and the cause value is a (new) value that augments the corresponding 3GPP specification (e.g., 3GPP specification for 6G or a new version of 3GPP specification 38.331 or 36.331). In other implementations, the cause value indicates the RRC request pertains to MO exception data. In yet other implementations, the cause value indicates the RRC request pertains to MT access. In yet other implementations, the cause value indicates the RRC request pertains to high priority access. In yet other implementations, the cause value indicates the RRC request messagePATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 pertains to MPS priority access. In still other implementations, the cause value indicates that the RRC request message pertains to MCS priority access.

[0084] In some implementations, the RRC request message, the RRC response message and the RRC complete message are an RRC CormectionRe quest message, an RRCConnectionSetup message, and an RRCConnectionSetupComplete message, respectively. In some implementations, the RRC request message, the RRC response message and the RRC complete message are an RRCConnectionRequest-NB message, an RRCConnectionSetup-NB message, and an RRCConnectionSetupComplete-NB message, respectively. In some implementations, the RRC request message, the RRC response message and the RRC complete message are an RRCConnectionResumeRequest message, an RRCConnectionResume message, and an RRCConnectionResumeComplete message, respectively. In some implementations, the RRC request message, the RRC response message and the RRC complete message are an RRCConnectionResumeRequest-NB message, an RRCConnectionResume-NB message, and an RRCConnectionResumeComplete-NB message, respectively. In some implementations, the RRC request message, the RRC response message and the RRC complete message are an RRCSetupRequest message, an RRCSetup message, and an RRCSetupComplete message, respectively. In some implementations, the RRC request message, the RRC response message and the RRC complete message are an RRCResumeRequesl message or an RRCResumeRequesll message, an RRCResume message, and an RRCResumeComplete message, respectively.

[0085] After establishing 314 the connection, the UE 102 may transmit 316 a UL NAS message to the CN 110 via the RAN 105 and the connection (e.g., the SRB). In some implementations, the UE 102 includes the UL NAS message in the RRC complete message. In some implementations, the UL NAS message is a Control Plane Service Request message that requests user plane data communication via a control plane interface. In such cases, the UE 102 communicates 318 one or more packets of the service with the CN 110 via the RAN 105 and the connection.

[0086] In other implementations, the UL NAS message is a Service Request message that requests user plane data communication via a user plane interface. In such cases, the CN 110 causes the RAN 105 to configure a data radio bearer (DRB) for the UE 102. Thus, the RAN 105PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 transmits a DL RRC message (e.g., RRCConnectionReconfiguration message or RRCReconfiguration message) including configuration parameters configuring the DRB to the UE 102. The UE 102 communicates one or more packets of the service with the CN 110 via the RAN 105 and the DRB. In yet other implementations, the RRC response message resumes a DRB suspended by the UE 102. The UE 102 resumes the DRB and performs the communication 318 with the CN 110 via the RAN 105 and the resumed DRB. In such cases, event 316 may be omitted. After completing the communication 318. the RAN 105 may transmit 320 a RRC release message to the UE 102 to stop the communication 318. The UE 102 may transition to the idle or inactive state in response to the RRC release message.

[0087] In some implementations, the one or more packets in the communication 318 include zero, one or more UL packets, and / or zero, one or more DL packets. In some implementations, the one or more packets in the communication 318 include one or more NIDD packets. In other implementations, the one or more packets in the communication 318 includes one or more SMS messages. In yet other implementations, the one or more packets in the communication 318 include one or more voice packets. In yet other implementations, the one or more packets in the communication 318 include one or more video packets.

[0088] In some implementations, the RRC request message and / or the RRC response message may include one or more packets of the service. In some implementations, the RRC request message and the RRC response message are an RRCEarlyDataRequest message and an RRCEarlyDataComplete message, respectively. In such cases, the communication 318 may be omitted. For example, the UE 102 may include zero or one UL packet of the service in the RRCEarlyDataRequest message, and / or the RAN 105 may include zero or one DL packet of the service in the RRCEarlyDataComplete message.

[0089] Fig. 4 illustrates a scenario 400 similar to the scenario 300, except that the UE 102 and the RAN 105 communicates with each other using NB-IoT and “MPS” is used instead of “new priority service” or “special priority service.” Generally, the discussion of Fig. 3 above can apply to Fig. 4, with “new priority service” replaced with “MPS”. The difference between the scenarios 400 and 300 is described below.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0090] Initially, the UE 102 is configured 402 for the MPS. In some implementations, a priority treatment of the MPS is lower than an emergency service, and may be equal to, higher than or lower than the MCS. In some implementations, the UE 102 determines 402 whether the UE 102 is configured for the MPS based on an existing EF (e.g., EFUAC_AIC) read from a USIM in the UE 102. Bit M (e.g., 1) in the EF indicates whether the UE 102 is configured for the MPS. If bit 1 in the EF set to 1, the UE 102 determines that the UE 102 is configured for the MPS. If bit 1 in the EF set to 0, the UE 102 determines that the UE 102 is not configured for the MPS. If the UE 102 determines that the UE is configured for the MPS, the UE 102 may determine that the UE 102 is configured with access identity 1 for the MPS. In some implementations, the UE 102 determines 402 whether the UE 102 is configured for the MPS based on stored UE context where stores the received information of MPS indicator from the NAS signaling message, i.e. Registration Accept message or UE Configuration Update Command message from the AMF 164 in Core Network 110. The UE 102 determines 402 that the UE 102 is configured for the MPS if the MPS indicator with access identity set to 1 for the MPS is stored in the UE context.

[0091] In some implementations, the UE 102 determines 402 whether the UE 102 is configured for the MPS for a user of a third party based on the stored UE context, which includes the received information of MPS indicator and a new (special) service indicator from the NAS signaling message, i.e. Registration Accept message or UE Configuration Update Command message from the AMF 164 in Core Network 110. The UE 102 determines 402 that the UE 102 is configured for the MPS to which a user of third party subscribes if the MPS indicator with access identity set to 1 for the MPS, as well as the new service indicator set to 1, are both stored in the UE context. In some implementations, the UE 102 determines 402 whether the UE 102 is configured for the MPS for a user of a third party based on the stored UE context which includes the received information of a new priority service indicator from the NAS signaling message, i.e. Registration Accept message or UE Configuration Update Command message from the AMF 164 in Core Network 110. The UE 102 determines 402 that the UE 102 is configured for the MPS to which a user of third party subscribes if the new priority service indicator with access identity is set to X for the MPS to which the user of the third party subscribes.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0092] Fig. 5 illustrates a scenario 500 similar to the scenarios 300 and 400, except that the UE 102 and the RAN 105 communicates with each other using NB-IoT, and the UE 102 and network use “MCS” instead of “new priority service” (or “special priority service”) and “MPS”. Generally, the discussion of Figs. 3 and 4 applies toto Fig. 5, with the “new priority service” replaced with “MCS”. The differences between the scenarios 500, 400, and 300 are considered below.

[0093] Initially, the UE 102 is configured 502 for the MCS. In some implementations, a priority treatment of the MCS is lower than an emergency service, and may be equal to, higher than or lower than the MPS. In some implementations, the UE 102 determines 502 whether the UE 102 is configured for the MPS based on an existing EF (e.g., EFUAC_AIC) read from a USIM in the UE 102. Bit M (e.g., 2) in the EF indicates whether the UE 102 is configured for the MCS. If bit 2 in the EF set to 1, the UE 102 determines that the UE 102 is configured for the MCS. If bit 2 in the EF set to 0, the UE 102 determines that the UE 102 is not configured for the MCS. If the UE 102 determines that the UE is configured for the MCS, the UE 102 may determine 502 that the UE 102 is configured with access identity 2 for the MCS. In some implementations, the UE 102 determines 502 whether the UE 102 is configured for the MCS based on the stored UE context that includes the received information of MPS indicator from the NAS signaling message, i.e. Registration Accept message or UE Configuration Update Command message from the AMF 164 in Core Network 110. The UE 102 determines 502 that the UE 102 is configured for the MCS if the MCS indicator with access identity set to 2 for the MCS is stored in the UE context.

[0094] Next, several example methods that can be implemented in a UE (e.g., the UE 102), a RAN node (e.g., the base station 104), or a CN node (e.g., the CN 110, the MME 114, or the AMF 164 or 184) are discussed with reference to Figs. 6-16. The relevant discussion of Figs. 3- 5 above can also apply to Figs. 6-16. In the following description, the “priority service” can be the “new priority service” / ” special priority service” as described with respect to Fig. 3. Alternatively, the “priority service” can be the MPS or MCS for NB-IoT as described with respect to Figs. 4 or 5 respectively. Each of these methods can be implemented using processingPATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 hardware such as one or more processors to execute instructions stored on a non-transitory computer-readable medium such as computer memory.

[0095] Fig. 6A illustrates an example method 600A, which can be implemented in a UE such as the UE 102. The method 600A begins at block 602, where the UE determines that the UE is configured for a priority service. At block 604, the UE receives a baring configuration from a cell. At block 608, the UE initiates a priority service. At block 610, the UE determines the access identity and / or an access category for the priority service. At block 612, the UE performs an access barring check based on the baring configuration, the access identity and / or the access category. At block 624, the UE determines whether the access barring check allows an access attempt to the cell for the priority service. If the access barring check allows an access attempt to the cell for the priority service (e.g., “Yes” branch of block 624), the flow proceeds to block 614. At block 614, the UE establishes or resumes a connection with a base station via the cell. At block 618, the UE communicates one or more data packets of the priority service via the connection with the base station. In some implementations, the connection includes an SRB and / or a DRB. Otherwise, if the access barring check does not allow an access attempt to the cell for the priority service (e.g., “No” branch of block 624), the flow proceeds to block 626. At block 626, the UE bars an access attempt to the cell for the priority service. In some implementations, the UE bars an access attempt to the cell for a predetermined time period. In some implementations, the UE receives a configuration from the RAN via the cell, configuring the predetermined time period. After the predetermined time period passes, the flow may proceed to block 612 from block 626.

[0096] Fig. 6B is a flow diagram of an example method 600B similar to the method 600A, except that the method 600B includes block 623 instead of blocks 604. At block 623, the UE determines whether the UE receives a baring configuration for the priority service from the cell. If the UE receives a baring configuration for the priority service from the cell (e.g., “Yes” branch of block 623), the flow proceeds to block 612. Otherwise, if the UE does not receive a baring configuration for the priority service from the cell (e.g., “No” branch of block 623), the flow proceeds to block 614.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0097] Fig. 7 illustrates an example method 700, which can be implemented by a UE. The method 700 begins at block 708, where the UE initiates a priority service. At block 714-1, the UE transmits a RRC request message to a RAN, including a specific cause for the priority service. At block 714-2, the UE receives an RRC response message from the RAN in response to the RRC request message. At block 718, the UE communicates one or more data packets of the priority service with the RAN. In some implementations, the UE determines an access identity and / or an access category for the priority service. The UE determines the cause based on the access identity and / or access category

[0098] Fig. 8A illustrates an example method 800A, which can be implemented in a UE such as the UE 102. The method 800A begins at block 808, where the UE initiates a priority service when camping on a cell. At block 828, the UE determines whether the cell supports a specific cause for the priority service. If the cell supports a specific cause for a priority service (i.e., “Yes” branch of block 828), the flow proceeds to block 814. At block 814, the UE transmits a RRC request message on the cell to a RAN, including a specific cause for the priority service. In some implementations, the cause indicates MO exception data, MPS priority access, MCS priority access, high priority access. In other implementations, the cause is a newly defined cause specific for the priority service.

[0099] Otherwise, if the cell does not support the specific cause for the priority service (i.e., “No” branch of block 828), the flow proceeds to block 815. At block 815, the UE transmits an RRC request message on the cell to the RAN, including a cause not specific for the priority service. In some implementations, the cause in block 814 indicates MO data or MO signaling. In other implementations, the cause in block 814 indicates MT access.

[0100] Fig. 8B is a flow diagram of an example method 800B similar to the method 800A, except that the method 800B includes block 827 instead of block 828. At block 827, the UE determines whether the UE is configured for the priority service (i.e., “Yes” branch of block 827). If the UE is configured for the priority service, the flow proceeds to block 814. Otherwise, if the UE is not configured for the priority service (i.e., “No” branch of block 827), the flow proceeds to block 815.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0101] Fig. 8C is a flow diagram of an example method 800C similar to the method 800A, except that the method 800C includes blocks 807 and 829 instead of blocks 808 and 828. At block 807, the UE receives a DL message from a RAN. At block 829, the UE determines whether the DL message includes a priority service indicator for a priority service. If the DL message includes a priority service indicator for a priority service (i.e., “Yes” branch of block 829), the flow proceeds to block 814. Otherwise, if the DL message does not include a priority service indicator for the priority service (i.e., “No” branch of block 829), the flow proceeds to block 815.

[0102] Fig. 8D is a flow diagram of an example method 800D similar to the methods 800A and 800B. If the UE is configured for the priority service (i.e., “Yes” branch of block 827). the flow proceeds to block 828. If the cell supports a specific cause for a priority service (i.e., “Yes” branch of block 828), the flow proceeds to block 814.

[0103] Fig. 9 illustrates an example method 900, which can be implemented by an UE. The method 900 begins at block 930, where the UE receives a DL message from a network (e.g., event 304, 305, 307, 404, 405, 407, 504, 505 or 507). At block 932, the UE determines whether the DL message includes a priority service indicator (e.g., event 304, 305, 307, 404, 405, 407, 504, 505 or 507). If the DL message includes a priority service indicator (i.e., “Yes” branch of block 932), the flow proceeds to block 934. At block 934, the UE determines that the UE is configured for the priority service (e.g., event 302, 402 or 502). Otherwise, if the DL message does not include a priority service indicator (i.e., “No” branch of block 932), the flow proceeds to block 936. At block 936, the UE determines that the UE is not configured for the priority service.

[0104] Fig. 10 illustrates an example method 1000, which can be implemented in a UE (e.g.. the UE 102). The method 1000 begins at block 1031, where the UE reads a USIM. At block 1033, the UE determines whether the USIM includes a specific indicator indicating that the UE is configured for a priority service. If the USIM includes a specific indicator indicating that the UE is configured with a priority service (i.e., “Yes” branch of block 1033), the flow proceeds to block 1034. At block 1034, the UE determines that the UE is configured for the priority service. Otherwise, if the USIM does not include a specific indicator indicating that the UE is configuredPATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 for the priority service or includes the specific indicator indicating that the UE is not configured for the priority service (i.e. “No” branch of block 1033), the flow proceeds to block 1036. At block 1036, the UE determines that the UE is not configured for the priority service.

[0105] Fig. 11 illustrates an example method 1100, which can be implemented by a RAN node. The method 1100 begins at block 1107, where the RAN node may transmit a DL message to a UE, including a priority service indicator. At block 1114-1, the RAN node receives a RRC request message from the UE, including a specific cause for a priority service. At block 1114-2, the RAN node transmits a RRC response message to the UE in response to the RRC request message. At block 1118, the RAN node communicates one or more data packets of the priority service with the UE.

[0106] Fig. 12 illustrates an example method 1200, which can be implemented in a CN node. The method 1200 begins at block 1203, where the CN node receives a UL message from a UE via a first base station, including a priority service indicator. At block 1240, the CN node determines to configure the UE for a priority service. At block 1242, the CN includes a priority service indicator in a DL message in response to the determination, where the priority service indicator indicates that the UE is configured for the priority service. At block 1205, the CN transmits the DL message to the UE via a second base station. In some implementations, the first and second base stations are the same base station. In other implementations, the first and second base stations are different base stations.

[0107] Fig. 13 illustrates an example method 1300, which can be implemented in a first network node (e.g., the MME 114 or the AMF 164 or 184). The method 1300 begins at block 1350, where the first network node receives a UE context for a UE from a second network node (e.g., the HSS or UDM 172). At block 1352, the first network node determines whether the UE context indicates that the UE qualifies for a priority service. If the UE context indicates that the UE qualifies for a priority service (i.e., “Yes” branch of block 1352), the flow proceeds to blocks 1242 and 1205 as described for Fig. 12. Otherwise, if the UE context does not indicate that the UE qualifies for a priority service (i.e., “No” branch of block 1352), the flow proceeds to block 1305. At block 1305, the CN transmits a DL message to the UE, where the DL message indicates that the UE is not configured for the priority service.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0108] Fig. 14 illustrates an example method 1400, which can be implemented by a UE. The method 1400 begins at block 1454, where the UE performs actions in blocks 708, 714-1, 714-2, and 718 with a NB-IoT RAN (e.g., a NB-IoT base station) as described in connection with Fig.7. At block 1408, the UE initiates a priority service. At block 1414-1, the UE transmits a RRC request message to a non-NB-IoT RAN (e.g., a non-NB-IoT base station), including a specific cause for the priority service. At block 1414-2, the UE receives a RRC response message from the non-NB-IoT RAN in response to the RRC request message. At block 1418, the UE communicates one or more data packets of the priority service with the non-NB-IoT RAN.

[0109] Fig. 15 illustrates an example method 1500 similar to the method 1100, which can be implemented by a network (e.g., the RAN 105, the base station 104 and / or the base station 106). The method 1500 begins at block 1556, where the network performs actions in blocks 1 107 (optional), 1114-1, 1114-2, and 1118 with a first UE via NB-IoT as described for Fig. 11. At block 1507, the network transmits a DL message to a second UE using a RAT other than the NB- loT, including a priority service indicator. At block 1514-1, the network receives a RRC request message from a second UE using the RAT, including a specific cause for a priority service. At block 1514-2, the network transmits a RRC response message to the UE using the RAT, in response to the RRC request message. At block 1518, the network communicates one or more data packets of the priority service with the UE using the RAT.

[0110] Fig. 16 illustrates an example method 1600 similar to the method 1200, which can be implemented by a CN node. The method 1600 begins at block 1658, where the CN node performs actions in blocks 1203, 1240, 1242, and 1205 with a first UE via one or more base stations of NB-IoT, as described for Fig. 12. At block 1603. the CN node receives a UL message from a second UE via a first base station of a RAT other than NB-IoT, including a priority service indicator. At block 1640, the CN node determines to configure the second UE for a priority service. At block 1642, the CN node includes a priority service indicator in a DL message in response to the determination, where the priority service indicator indicates that the UE is configured for the priority service. At block 1605, the CN node transmits the DL message to the second UE via a second base station of the RAT.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0111] The following list of examples reflects a variety of the embodiments explicitly contemplated by the present disclosure.

[0112] Example 1. A method for accessing a radio access network (RAN), the method implemented in a user equipment (UE) and comprising: initiating, in a cell of the RAN, a priority service based on a configuration other than a Service User subscription: and communicating, via the RAN, data packets associated with the priority service.

[0113] Example 2. The method of example 1, further comprising: prior to the initiating, determining that the UE is configured for the priority service.

[0114] Example 3. The method of example 2, wherein: the determining includes retrieving an indication of the configuration from a Universal Subscriber Identity Module (USIM).

[0115] Example 4. The method of example 2, wherein: the determining includes retrieving an indication of the subscription from a non-volatile memory of the UE.

[0116] Example 5. The method of example 2 or 3, wherein: the retrieving of the indication includes determining an access identity for the priority service using a file that stores a unified access control (UAC) identities configuration.

[0117] Example 6. The method of example 3 or 4, wherein: the indication is retrieved from a file dedicated to the priority service.

[0118] Example 7. The method of example 6, wherein the file includes an indication of radio access technology (RAT) over which the UE is configured to use the priority service.

[0119] Example 8. The method of example 2, wherein: the determining is based on a UE context stored at the UE.

[0120] Example 9. The method of example 2, wherein the determining includes: receiving, from a core network (CN), a non-access stratum (NAS) message including an indication that the UE is configured to use the priority service.

[0121] Example 10. The method of example 9, wherein the indication that the UE is configured to use the priority service is included in a Registration Access message.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0122] Example 11. The method of example 9, wherein the indication that the UE is configured to use the priority service is included in a UE Configuration Update Command message.

[0123] Example 12. The method of any of examples 2-11, wherein: the determining that the UE is configured for the priority service includes determining that the UE is a commercial UE subscribed to the priority service.

[0124] Example 13. The method of example 12, further comprising: determining that the UE is subscribed to the priority service at a particular one of a plurality of subscription levels.

[0125] Example 14. The method of any of the preceding examples, further comprising: receiving, in the cell, an indication that the cell supports the priority service.

[0126] Example 15. The method of example 14, wherein: the indication that the cell supports the priority service is received in broadcast of a system information block (SIB).

[0127] Example 16. The method of example 14 or 15, wherein: the indication is a radio resource control (RRC) establishment cause dedicated to the priority service.

[0128] Example 17. The method of example 14 or 15, wherein: the indication is an RRC resume cause dedicated to the priority service.

[0129] Example 18. The method of any of the preceding examples, further comprising: receiving, in the cell, a barring configuration.

[0130] Example 19. The method of any of the preceding examples, wherein: the configuration indicates a subscription for the priority service; and the priority service is associated with a higher priority treatment than a service of a same type but without a subscription.

[0131] Example 20. The method of any of the preceding examples, wherein: the configuration indicates a subscription for the priority service; and the priority service is associated with a lower priority treatment than a service of a same type provided to the Service User subscription.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0132] Example 21. The method of any of the preceding examples, wherein: the priority service is none of an emergency service, a Multimedia Priority Service (MPS), or a Mission Critical Service (MCx).

[0133] Example 22. The method of any of the preceding examples, wherein: the priority service has lower priority than an emergency service.

[0134] Example 23. The method of example 19 or 20. wherein: the subscription applies to a plurality of services the UE supports.

[0135] Example 24. The method of example 19 or 20, wherein: the subscription applies only to a specific service in a plurality of services the UE supports.

[0136] Example 25. The method of example 24, wherein the specific service is a Short Message Service (SMS).

[0137] Example 26. The method of example 24, wherein the specific service is a voice call.

[0138] Example 27. The method of any of the preceding examples, wherein: the priority service is one of a mobile-originated (MO) service or mobile-terminated (MT) service.

[0139] Example 28. The method of any of the preceding examples, further comprising: performing an access barring check for the priority service.

[0140] Example 29. The method of example 28, further comprising: determining at least one of an access identity or an access category for the priority service; wherein the performing the access barring check is based on the determined access identity and / or the access category.

[0141] Example 30. The method of any of the preceding examples, further comprising: transmitting, to the RAN, an RRC message including a cause value specific to the priority service.

[0142] Example 31. The method of example 30, wherein: the transmitting of the cause value specific to the priority service is in response to determining that the cell supports the cause value specific to the priority service.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0143] Example 32. The method of example 30, wherein: the transmitting of the cause value specific to the priority service is in response to determining that the UE is configured for the priority service.

[0144] Example 33. The method of any of examples 1-20, wherein: the priority service is an MPS: and the communicating of the data packets associated with the priority service includes layering the MPS over SMS or Internet Protocol (IP) Multimedia Subsystem (IMS).

[0145] Example 34. The method of any of examples 1-20, wherein: the priority service is an MPS; and the communicating of the data packets associated with the priority service includes layering the MPS over a Non-Internet Protocol Data Delivery (NIDD)-based messaging service.

[0146] Example 35. The method of any of examples 1-20, wherein: the priority service is an MCx; and the communicating of the data packets associated with the priority service includes layering the MPx over a NIDD-based messaging service.

[0147] Example 36. The method of example 34 or 35. wherein: the communicating of the data packets using the NIDD-based messaging service is in response to determining that the cell operates using a low-power wide area network (LPWA) technology.

[0148] Example 37. The method of example 36, wherein the cell is a non-terrestrial network (NTN) cell.

[0149] Example 38. The method of example 36 or 37, wherein the NTN cell is a Narrowband Internet-of-Things (NB-IoT) cell.

[0150] Example 39. A method for accessing a radio access network (RAN), the method implemented in a user equipment (UE) and comprising: receiving, in a cell that operates using a low-power wide area network (LPWA) technology, an indication of support of a priority service; and initiating the priority service in the cell using a Non-Internet Protocol Data Delivery (NlDD)-based messaging service.

[0151] Example 40. The method of example 39, wherein: the priority service is associated with a Service User subscription.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0152] Example 41. The method of example 39 or 40, further comprising: prior to the initiating, determining that the UE is configured for the priority service.

[0153] Example 42. The method of example 41, wherein: the determining includes retrieving an indication of the configuration from a Universal Subscriber Identity Module (USIM).

[0154] Example 43. The method of example 41, wherein: the determining includes retrieving an indication of the subscription from a non-volatile memory of the UE.

[0155] Example 44. The method of example 41 or 42, wherein: the retrieving of the indication includes determining an access identity for the priority service using a file that stores a unified access control (UAC) identities configuration.

[0156] Example 45. The method of example 42 or 43. wherein: the indication is retrieved from a file dedicated to the priority service.

[0157] Example 46. The method of example 45, wherein the file includes an indication of radio access technology (RAT) over which the UE is configured to use the priority service.

[0158] Example 47. The method of example 41, wherein: the determining is based on a UE context stored at the UE.

[0159] Example 48. The method of example 41, wherein the determining includes: receiving, from a core network (CN), a non-access stratum (NAS) message including an indication that the UE is configured to use the priority service.

[0160] Example 49. The method of example 48, wherein the indication that the UE is configured to use the priority service is included in a Registration Access message.

[0161] Example 50. The method of example 48, wherein the indication that the UE is configured to use the priority service is included in a UE Configuration Update Command message.

[0162] Example 51. The method of any of examples 41-50, wherein: the determining that the UE is configured for the priority service includes determining that the UE is a commercial UE subscribed to the priority service.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0163] Example 52. The method of example 51, further comprising: determining that the UE is subscribed to the priority service at a particular one of a plurality of subscription levels.

[0164] Example 53. The method of any of examples 39-52, further comprising: receiving, in the cell, an indication that the cell supports the priority service.

[0165] Example 54. The method of example 53, wherein: the indication that the cell supports the priority service is received in broadcast of a system information block (SIB).

[0166] Example 55. The method of example 53 or 54, wherein: the indication is a radio resource control (RRC) establishment cause dedicated to the priority service.

[0167] Example 56. The method of example 54 or 55, wherein: the indication is an RRC resume cause dedicated to the priority service.

[0168] Example 57. The method of any of examples 39-56. further comprising: receiving, in the cell, a barring configuration.

[0169] Example 58. The method of any of examples 39-57, wherein: the configuration indicates a subscription for the priority service; and the priority service is associated with a higher priority treatment than a service of a same type but without a subscription.

[0170] Example 59. The method of any of examples 39-58, wherein: the configuration indicates a subscription for the priority service; and the priority service is associated with a lower priority treatment than a service of a same type provided to the Service User subscription.

[0171] Example 60. The method of any of examples 39-59. wherein: the priority service is none of an emergency service, a Multimedia Priority Service (MPS), or a Mission Critical Service (MCx).

[0172] Example 61. The method of any of examples 39-60, wherein: the priority service has lower priority than an emergency service.

[0173] Example 62. The method of example 59 or 60, wherein: the subscription applies to a plurality of services the UE supports.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0174] Example 63. The method of example 59 or 60. wherein: the subscription applies only to a specific service in a plurality of services the UE supports.

[0175] Example 64. The method of any of examples 39-63, further comprising: performing an access barring check for the priority service.

[0176] Example 65. The method of example 64, further comprising: determining at least one of an access identity or an access category for the priority service: wherein the performing the access barring check is based on the determined access identity and / or the access category.

[0177] Example 66. The method of any examples 39-65, further comprising: transmitting, to the RAN. an RRC message including a cause value specific to the priority service.

[0178] Example 67. The method of example 66, wherein: the transmitting of the cause value specific to the priority service is in response to determining that the cell supports the cause value specific to the priority service.

[0179] Example 68. The method of example 66, wherein: the transmitting of the cause value specific to the priority service is in response to determining that the UE is configured for the priority service.

[0180] Example 69. The method of any of examples 39-68, wherein the cell is a nonterrestrial network (NTN) cell.

[0181] Example 70. 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.

[0182] Example 71. A method for supporting a priority service, the method implemented in a radio access network (RAN) and comprising: transmitting, in a cell, an indication that the cell supports a non-emergency priority service; and receiving, from a user equipment (UE), a request to initiate the priority service.

[0183] Example 72. The method of example 71, wherein the non-emergency priority service is none of an emergency service, a Multimedia Priority Service (MPS), or a Mission Critical Service (MCx).PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0184] Example 73. The method of example 71, wherein the non-emergency priority service is MPS or MCx.

[0185] Example 74. The method of example 73, wherein the cell operates using a low-power wide area network (LPWA) technology.

[0186] Example 75. The method of example 74, wherein the cell is a non-terrestrial (NTN) cell.

[0187] Example 76. The method of example 74 or 75, wherein the cell is a Narrowband Internet-of-Things (NB-IoT) cell.

[0188] Example 77. The method of any of examples 74-76, further comprising: communicating, with the UE, data packets associated with the priority service using a NonInternet Protocol Data Delivery (NIDD)-based messaging service.

[0189] Example 78. The method of example 71, further comprising: forwarding, from a core network (CN) to the UE, a non-access stratum (NAS) message including an indication that the UE is configured to use the priority service.

[0190] Example 79. The method of example 78, wherein the indication that the UE is configured to use the priority service is included in a Registration Access message.

[0191] Example 80. The method of example 78, wherein the indication that the UE is configured to use the priority service is included in a UE Configuration Update Command message.

[0192] Example 81. The method of any of examples 71-80, wherein: the UE is a commercial UE subscribed to the priority service.

[0193] Example 82. The method of any of examples 71-81, further comprising: transmitting, in the cell, an indication that the cell supports the priority service.

[0194] Example 83. The method of example 82, wherein: the indication that the cell supports the priority service is transmitted in broadcast of a system information block (SIB).PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0195] Example 84. The method of example 81 or 82, wherein: the indication is a radio resource control (RRC) establishment cause dedicated to the priority service.

[0196] Example 85. The method of example 81 or 82, wherein: the indication is an RRC resume cause dedicated to the priority service.

[0197] Example 86. The method of any of examples 71-85, further comprising: transmitting, in the cell, a barring configuration.

[0198] Example 87. The method of any of examples 71-86, wherein: the UE is configured with a subscription for the priority service; and the priority service is associated with a higher priority treatment than a service of a same type but without a subscription.

[0199] Example 88. The method of any of examples 71-87. wherein: the UE is configured with a subscription for the priority service; and the priority service is associated with a lower priority treatment than a service of a same type provided to the Service User subscription.

[0200] Example 89. The method of examples 71-88, wherein: the priority service is none of an emergency service, a Multimedia Priority Service (MPS), or a Mission Critical Service (MCxS ).

[0201] Example 90. The method of any of the preceding examples, wherein: the priority service has lower priority than an emergency service.

[0202] Example 91. The method of example 87 or 88. wherein: the subscription applies to a plurality of services the UE supports.

[0203] Example 92. The method of example 87 or 88, wherein: the subscription applies only to a specific service in a plurality of services the UE supports.

[0204] Example 93. The method of example 92, wherein the specific service is a Short Message Service (SMS).

[0205] Example 94. The method of example 92, wherein the specific service is a voice call.

[0206] Example 95. The method of any of examples 71 -94, wherein: the priority service is one of a mobile-originated (MO) service or mobile-terminated (MT) service.PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00

[0207] Example 96. A radio access network (RAN) node comprising: a transceiver; and processing hardware; wherein the RAN node is configured to implement a method of any of examples 71 -example 95.

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

[0209] 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”.

[0210] 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” and “PDU Session Establishment Accept”, respectively and the “Activate Default EPS Bearer Context Accept” is omitted.

[0211] 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 electronicPATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 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 internet-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.

[0212] 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.

[0213] 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. The software may be executed by one or more general-purpose processors or one or more specialpurpose processors.

Claims

PATENT APPLICATION Attorney Docket No.: 31730 / 308487-00Claims:

1. A method for accessing a radio access network (RAN), the method implemented in a user equipment (UE) and comprising: receiving, in a cell of the RAN, an indication that the cell supports a priority service; initiating, in the cell, the priority service based on a configuration other than a ServiceUser subscription; and communicating, via the RAN, data packets associated with the priority service.

2. The method of claim 1, further comprising: prior to the initiating, determining that the UE is configured for the priority service, including one of:(i) retrieving an indication of the configuration from a Universal Subscriber Identity Module (USIM);(ii) retrieving an indication of the configuration from a non-volatile memory of the UE,(iii) receiving, from a core network (CN), a non-access stratum (NAS) message including an indication that the UE is configured to use the priority service, or(iv) determining that the UE is a commercial UE subscribed to the priority service.

3. The method of claim 1 or 2, wherein: the indication that the cell supports the priority service is received in a broadcast of a system information block (SIB).

4. The method of claim 1 or 2, wherein the indication is one of:(i) a radio resource control (RRC) establishment cause dedicated to the priority service, or(ii) an RRC resume cause dedicated to the priority service.

5. The method of any of the preceding claims, wherein:PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 the configuration indicates a subscription for the priority service; and the priority service is associated with a higher priority treatment than a service of a same type but without the Service User subscription.

6. The method of any of the preceding claims, wherein: the priority service has a lower priority than an emergency service.

7. The method of any of the preceding claims, wherein: the priority service is a non-emergency priority Short Message Service (SMS), or a nonemergency Multimedia Priority Service (MPS), or a non-emergency Missions Critical Service (MCx).

8. The method of any of the preceding claims, further comprising: performing an access barring check for the priority service.

9. The method of claim 8, further comprising: determining at least one of an access identity or an access category for the priority service; wherein the performing the access barring check is based on the determined access identity and / or the access category.

10. The method of any of claims 1-6, wherein: the communicating of the data packets associated with the priority service includes layering the priority service over a Non-Internet Protocol Data Delivery (NIDD)-based messaging service11. A method for supporting a priority service, the method implemented in a radio access network (RAN) and comprising: transmitting, in a cell, an indication that the cell supports a priority service;PATENT APPLICATIONAttorney Docket No.: 31730 / 308487-00 receiving, from a user equipment (UE), a request to initiate the priority service; and communicating, with the UE, data packets associated with the priority service using a Non-Intemet Protocol Data Delivery (NIDD)-based messaging service.

12. The method of claim 11, wherein the cell is a Narrowband Internet-of-Things (NB-IoT) cell.

13. The method of claim 11, further comprising: forwarding, from a core network (CN) to the UE, a non-access stratum (NAS) message including an indication for the priority service.

14. The method of any of claims 11-13 wherein: the priority service has lower priority than an emergency service.

15. A device comprising: a transceiver; and processing hardware; wherein wherein the device is configured to implement a method of any of the preceding claims.