WO2025178791A1 - Design for sending 5g session management (5gsm) messages at a user equipment (ue) in a non-allowed service area - Google Patents

Abstract

A method of sending 5G session management (5GSM) messages at a user equipment (UE) in a non-allowed service area, comprising camping on a cell in a tracking area; identifying, at the UE, from a list of allowed tracking areas, that the tracking area is not an allowed tracking area; entering a fifth generation mobility management (5GMM)-REGISTERED-NON-ALLOWED-SERVICE state at the UE; and allowing non-access stratum (NAS) procedures related to a handling of NW initiated 5GSM procedures in a 5GMM CONNECTED state; or allowing any NAS procedures related to a handling of UE initiated 5GSM procedures related to emergency services.

Description

DESIGN FOR SENDING 5G SESSION MANAGEMENT (5GSM) MESSAGES AT A USER EQUIPMENT (UE) IN A NON-ALLOWED SERVICE AREA

FIELD

[0001] Embodiments of the invention relate to wireless communications, including apparatuses, systems, and methods to send 5G session management (5GSM) messages at a UE in a non-allowed service area.

DESCRIPTION OF THE RELATED ART

[0002] Wireless communication systems are rapidly growing in usage. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now provide access to the internet, email, text messaging, and navigation using the global positioning system (GPS) and are capable of operating sophisticated applications that utilize these functionalities.

[0003] Long Term Evolution (LTE) has been the technology of choice for the majority of wireless network operators worldwide, providing mobile broadband data and high-speed Internet access to their subscriber base. LTE was first proposed in 2004 and was first standardized in 2008. Since then, as usage of wireless communication systems has expanded exponentially, demand has risen for wireless network operators to support a higher capacity for a higher density of mobile broadband users. In 2015, a study of a new radio access technology began and, in 2017, a first release of Fifth Generation New Radio (5G NR) was standardized.

[0004] 5G-NR, also simply referred to as NR, provides, as compared to LTE, a higher capacity for a higher density of mobile broadband users, while also supporting device-to-device, ultra-reliable, and massive machine type communications with lower latency and/or lower battery consumption. Further, NR may allow for more flexible scheduling as compared to current LTE. Consequently, efforts are being made in ongoing developments of NR to take advantage of higher throughputs possible at higher frequencies. [0005] Wireless communication systems provide mobility through the use of battery-powered user equipment (UEs) that communicate with network components, such as base stations that may be referred to as gNBs or gNodeBs.

SUMMARY

[0006] Embodiments relate to wireless communications, and more particularly to methods of sending 5G session management (5GSM) messages at a user equipment (UE) in a non-allowed service area, comprising: camping on a cell in a tracking area; identifying, at the UE, from a list of allowed tracking areas, that the tracking area is not an allowed tracking area; entering a fifth generation mobility management (5GMM)-REGISTERED-NON-ALLOWED-SERVICE state at the UE; allowing non-access stratum (NAS) procedures related to a handling of NW initiated 5GSM procedures in a 5GMM CONNECTED state; or allowing any NAS procedures related to a handling of UE initiated 5GSM procedures related to: emergency services; or emergency services fallback; or high priority access; or responding to paging or responding to a notification; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status; and sending a 5GSM message for one or more network-requested 5GSM procedures; or sending a 5GSM message for one or more UE-requested 5GSM procedures from the UE for one or more of: emergency services; or high priority access; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status.

[0007] The techniques described herein may be implemented in and/or used with a number of different types of devices, including but not limited to unmanned aerial vehicles (UAVs), unmanned aerial controllers (UACs), base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, internet of things (IOT) and any of various other computing devices.

[0008] This Summary is intended to provide a brief overview of some of the subject matter described in this document. Accordingly, it will be appreciated that the above-described features are merely examples and should not be construed to narrow the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A better understanding of the present subject matter can be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0010] FIG. 1 illustrates an example wireless communication system according to some embodiments.

[0011] FIG. 1 B illustrates an example of a base station and an access point in communication with a user equipment (UE) device, according to some embodiments.

[0012] FIG. 2 illustrates an example block diagram of a base station, according to some embodiments.

[0013] FIG. 3 illustrates an example block diagram of a server according to some embodiments.

[0014] FIG. 4 illustrates an example block diagram of a UE according to some embodiments.

[0015] FIG. 5 illustrates an example block diagram of cellular communication circuitry, according to some embodiments.

[0016] FIG. 6 illustrates an example of a baseband processor architecture for a UE, according to some embodiments.

[0017] FIG. 7 illustrates an example block diagram of an interface of baseband circuitry according to some embodiments.

[0018] FIG. 8 illustrates an example of a control plane protocol stack in accordance with some embodiments.

[0019] FIG. 9 illustrates an example of a user plane protocol stack in accordance with some embodiments.

[0020] FIG. 10 illustrates an example of a diagram showing a multimedia telephony (MMTEL) service with a non-allowed service area in accordance with some embodiments.

[0021] FIG. 1 1 illustrates an example of a diagram showing an MMTEL call that results in a failure of a Service Area Restriction (SAR) in accordance with some embodiments.

[0022] FIG. 12 illustrates an example of improvements to a third generation partnership project (3GPP) technical specification (TS) 24.501 section 5.3.5.2 in accordance with some embodiments.

[0023] FIG. 13 illustrates an example of a diagram showing an MMTEL call that results in a success of a Service Area Restriction (SAR), in accordance with some embodiments.

[0024] FIGs. 14A and 14B illustrate an example method of sending 5G session management (5GSM) messages at a user equipment (UE) in a non-allowed service area, in accordance with some embodiments.

[0025] FIG. 15 illustrates an example of a block diagram illustrating components able to read instructions from a machine-readable or computer-readable medium, in accordance with some embodiments.

[0026] While the features described herein may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to be limiting to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims.

DETAILED DESCRIPTION

Terms

[0027] The following is a glossary of terms used in this disclosure:

[0028] Memory Medium or Memory - Any of various types of non-transitory memory devices or storage devices. The term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random-access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may include other types of non-transitory memory as well or combinations thereof. In addition, the memory medium may be located in a first computer system in which the programs are executed or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer for execution. The term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network. The memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors.

[0029] Carrier Medium - a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.

[0030] Programmable Hardware Element includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field Programmable Object Arrays), and CPLDs (Complex PLDs). The programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores). A programmable hardware element may also be referred to as "reconfigurable logic”.

[0031] Computer System (or Computer) - any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0032] User Equipment (UE) (or “UE Device”) - any of various types of computer systems devices which are mobile or portable and which performs wireless communications. Examples of UE devices include mobile telephones or smart phones (e.g., iPhone™, Android™-based phones), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices (e.g., smart watch, smart glasses), PDAs, portable Internet devices, Internet of Things, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), and so forth. In general, the term “UE” or “UE device” can be broadly defined to encompass any electronic, computing, and/or telecommunications device (or combination of devices) which is easily transported by a user and capable of wireless communication.

[0033] Base Station - The term “Base Station” has the full breadth of its ordinary meaning, and at least includes a wireless communication station installed at a fixed location and used to communicate with UEs as part of a wireless telephone system or radio system, including but not limited Next Generation Node-Bs (gNB or gNodeB) in NR.

[0034] Processing Element (or Processor) - refers to various elements or combinations of elements that are capable of performing a function in a device, such as a user equipment or a cellular network device. Processing elements may include, for example: processors and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as an ASIC (Application Specific Integrated Circuit), programmable hardware elements such as a field programmable gate array (FPGA), as well any of various combinations of the above.

[0035] Channel - a medium used to convey information from a sender (transmitter) to a receiver. It should be noted that since characteristics of the term “channel” may differ according to different wireless protocols, the term “channel” as used herein may be considered as being used in a manner that is consistent with the standard of the type of device with reference to which the term is used. In some standards, channel widths may be variable (e.g., depending on device capability, band conditions, etc.). For example, LTE may support scalable channel bandwidths from 1.4 MHz to 20MHz. 5G NR can support scalable channel bandwidths from 5 MHz to 100 MHz in Frequency Range 1 (FR1 ) and up to 400 MHz in FR2. In other radio access technologies, WLAN channels may be 22 MHz wide while Bluetooth channels may be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, e.g., different channels for uplink or downlink and/or different channels for different uses such as data, control information, etc.

[0036] Band - The term "band" has the full breadth of its ordinary meaning, and at least includes a section of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0037] Automatically - refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuitry, programmable hardware elements, ASICs, etc.), without user input directly specifying or performing the action or operation. Thus, the term "automatically" is in contrast to an operation being manually performed or specified by the user, where the user provides input to directly perform the operation. An automatic procedure may be initiated by input provided by the user, but the subsequent actions that are performed "automatically” are not specified by the user, i.e., are not performed “manually”, where the user specifies each action to perform. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting check boxes, radio selections, etc.) is filling out the form manually, even though the computer system will update the form in response to the user actions. The form may be automatically filled out by the computer system where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user input specifying the answers to the fields. As indicated above, the user may invoke the automatic filling of the form but is not involved in the actual filling of the form (e.g., the user is not manually specifying answers to fields but rather they are being automatically completed). The present specification provides various examples of operations being automatically performed in response to actions the user has taken. [0038] Approximately - refers to a value that is almost correct or exact. For example, approximately may refer to a value that is within 1 to 10 percent of the exact (or desired) value. It should be noted, however, that the actual threshold value (or tolerance) may be application dependent. For example, in some embodiments, “approximately” may mean within 0.1 % of some specified or desired value, while in various other embodiments, the threshold may be, for example, 2%, 3%, 5%, and so forth, as desired or as set by the particular application.

[0039] Concurrent - refers to parallel execution or performance, where tasks, processes, or programs are performed in an at least partially overlapping manner. For example, concurrency may be implemented using “strong” or strict parallelism, where tasks are performed (at least partially) in parallel on respective computational elements, or using “weak parallelism”, where the tasks are performed in an interleaved manner, e.g., by time multiplexing of execution threads.

[0040] Information Element - a group of information that may be included within a Signaling Message or Data Flow which is sent across an interface.

[0041] Legacy - The 3rd Generation Partnership Project (3GPP) produces specifications that define 3GPP technologies. 3GPP specifications cover cellular telecommunications technologies, including radio access, core network and service capabilities, which provide a complete system description for mobile telecommunications. 3GPP uses a system of parallel “Releases” that provides developers with a stable platform for the implementation of features at a given point and then allows for the addition of new functionality in subsequent releases. Release 17 was released in 2022. Release 18 (Rel-18), at the time of this disclosure, is nearing release as its specifications have been largely defined. Accordingly, implementations and concepts compatible with Rel-18, or previous Releases, are sometimes referred to herein as “Legacy.” One or more embodiments of the present disclosure may be adopted in future Releases, e.g., Release 19.

[0042] rN - As used herein rN, when used in conjunction with an Information Element (IE) refers to a UE that is capable of supporting 3GPP Release N. For example, r18 denotes a UE capable of supporting 3GPP release 18. A UE that is capable of supporting a release greater than N may also be capable of supporting 3GPP Release N. A UE that is not capable of supporting 3GPP Release N may not be capable of supporting the lEs that include rN.

[0043] Various components may be described as “configured to” perform a task or tasks. In such contexts, “configured to” is a broad recitation generally meaning “having structure that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect a module to another module, even when the two modules are not connected). In some contexts, “configured to” may be a broad recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently on. In general, the circuitry that forms the structure corresponding to “configured to” may include hardware circuits.

[0044] Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) interpretation for that component.

[0045] The example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The example embodiments relate to apparatuses, systems and methods for reducing energy usage by network components, e.g., base stations in wireless communication systems.

[0046] The example embodiments are described with regard to communication between a Next Generation Node B (gNB) and a user equipment (UE). However, reference to a gNB or a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and/or firmware to support for reducing energy usage by network components in wireless communication systems. Therefore, the gNB or UE as described herein is used to represent any appropriate type of electronic component.

[0047] The example embodiments are also described with regard to a fifth generation (5G) New Radio (NR) network that may configure a UE to support for reducing energy usage by network components in wireless communication systems. However, reference to a 5G NR network is merely provided for illustrative purposes. The example embodiments may be utilized with any appropriate type of network.

[0048] Throughout this description various information elements (lEs) are referred to by specific names. It should be understood that these names are only examples and the lEs carrying the information referred to throughout this description may be referred to by other names by various entities.

Figures 1 A and 1 B: Communication Systems

[0049] FIG. 1 A illustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system of FIG. 1 A is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.

[0050] As shown, the example wireless communication system includes a base station 102A which communicates over a transmission medium with one or more user devices 106A, 106B, etc., through 106N. Each of the user devices may be referred to herein as a “user equipment” (UE). Thus, the user devices 106 are referred to as UEs or UE devices.

[0051] The base station (BS) 102A may be a base transceiver station (BTS) or cell site (a “cellular base station”) and may include hardware that enables wireless communication with the UEs 106A through 106N.

[0052] The communication area (or coverage area) of the base station may be referred to as a “cell.” The base station 102A and the UEs 106 may be configured to communicate over the transmission medium using any of various radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1 xRTT, 1 xEV-DO, HRPD, eHRPD), etc. Note that if the base station 102A is implemented in the context of LTE, also referred to as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN, it may alternately be referred to as an 'eNodeB' or ‘eNB’. Note that if the base station 102A is implemented in the context of 5G NR, it may alternately be referred to as ‘gNodeB’ or ‘gNB’.

[0053] As shown, the base station 102A may also be equipped to communicate with a network 100 (e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN), and/or the Internet, among various possibilities). Thus, the base station 102A may facilitate communication between the user devices and/or between the user devices and the network 100. In particular, the cellular base station 102A may provide UEs 106 with various telecommunication capabilities, such as voice, SMS and/or data services.

[0054] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or a different cellular communication standard may thus be provided as a network of cells, which may provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0055] Thus, while base station 102A may act as a “serving cell” for UEs 106A- N as illustrated in FIG. 1A, each UE 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which might be provided by base stations 102B-N and/or any other base stations), which may be referred to as “neighboring cells”. Such cells may also be capable of facilitating communication between user devices and/or between user devices and the network 100. Such cells may include “macro” cells, “micro” cells, “pico” cells, and/or cells which provide any of various other granularities of service area size. For example, base stations 102A-B illustrated in FIG. 1 A might be macro cells, while base station 102N might be a micro cell. Other configurations are also possible.

[0056] In some embodiments, base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0057] Note that a UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using a wireless networking (e.g., Wi-Fi) and/or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1 xRTT, 1xEV-DO, HRPD, eHRPD), etc.). The UE 106 may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M/H or DVB-H), and/or any other wireless communication protocol, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0058] In some embodiments, the base station 102A may select a paging configuration and a PEI configuration for UEs 106. The base station 102A may encode and transmit the paging configuration and the PEI configuration to UEs 106 as part of a registration process. Using the paging configuration, UEs 106 can determine which PO and PF to monitor in a paging cycle. Using the PEI configuration, UEs 106 can determine the radio frame that carries relevant PEI.

[0059] FIG. 1 B illustrates user equipment 106 (e.g., one of the devices 106A through 106N) in communication with a base station 102 and an access point 112, according to some embodiments. The UE 106 may be a device with both cellular communication capability and non-cellular communication capability (e.g., Bluetooth, Wi-Fi, and so forth) such as a mobile phone, a hand-held device, a computer or a tablet, or virtually any type of wireless device.

[0060] The UE 106 may include a processor that is configured to execute program instructions stored in memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively, or in addition, the UE 106 may include a programmable hardware element such as an FPGA (field-programmable gate array) that is configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein.

[0061] The UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UE 106 may be configured to communicate using, for example, CDMA2000 (1 xRTT 1 1 xEV-DO / HRPD I eHRPD), LTE/LTE- Advanced, or 5G NR using a single shared radio and/or GSM, LTE, LTE-Advanced, or 5G NR using the single shared radio. The shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for MIMO) for performing wireless communications. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), ordigital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the aforementioned hardware. For example, the UE 106 may share one or more parts of a receive and/or transmit chain between multiple wireless communication technologies, such as those discussed above.

[0062] In some embodiments, the UE 106 may include separate transmit and/or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As a further possibility, the UE 106 may include one or more radios which are shared between multiple wireless communication protocols, and one or more radios which are used exclusively by a single wireless communication protocol. For example, the UE 106 might include a shared radio for communicating using either of LTE or 5G NR (or LTE or IxRTTor LTE or GSM), and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible. FIG. 2: Block Diagram of a Base Station (gNB)

[0063] FIG. 2 illustrates an example block diagram of a base station 102, according to some embodiments. It is noted that the base station of FIG. 2 is merely one example of a possible base station. As shown, the base station 102 may include processor(s) 204 which may execute program instructions for the base station 102. The processor(s) 204 may also be coupled to memory management unit (MMU) 240, which may be configured to receive addresses from the processor(s) 204 and translate those addresses to locations in memory (e.g., memory 260 and read only memory (ROM) 250) or to other circuits or devices.

[0064] The base station 102 may include at least one network port 270. The network port 270 may be configured to couple to a telephone network and provide a plurality of devices, such as UE devices 106, access to the telephone network as described above in Figures 1 and 2.

[0065] The network port 270 (or an additional network port) may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider. The core network may provide mobility related services and/or other services to a plurality of devices, such as UE devices 106. In some cases, the network port 270 may couple to a telephone network via the core network, and/or the core network may provide a telephone network (e.g., among other UE devices serviced by the cellular service provider).

[0066] In some embodiments, base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network. In addition, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0067] The base station 102 may include at least one antenna 234, and possibly multiple antennas. The at least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices 106 via radio 230. The antenna 234 communicates with the radio 230 via communication chain 232. Communication chain 232 may be a receive chain, a transmit chain or both. The radio 230 may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0068] The base station 102 may be configured to communicate wirelessly using multiple wireless communication standards. In some instances, the base station 102 may include multiple radios, which may enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5G NR. In such a case, the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0069] As described further subsequently herein, the base station 102 may include hardware and software components for implementing or supporting implementation of features described herein. The processor 204 of the base station 102 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 204 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor 204 of the base station 102, in conjunction with one or more of the other components 230, 232, 234, 240, 250, 260, 270 may be configured to implement or support implementation of part or all of the features described herein.

[0070] In addition, as described herein, processor(s) 204 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s) 204. Thus, processor(s) 204 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 204. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 204.

[0071] Further, as described herein, radio 230 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 230. Thus, radio 230 may include one or more integrated circuits (ICs) that are configured to perform the functions of radio 230. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio 230.

FIG. 3: Block Diagram of a Server

[0072] FIG. 3 illustrates an example block diagram of a server 104, according to some embodiments. It is noted that the server of FIG. 3 is merely one example of a possible server. As shown, the server 104 may include processor(s) 344 which may execute program instructions for the server 104. The processor(s) 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from the processor(s) 344 and translate those addresses to locations in memory (e.g., memory 364 and read only memory (ROM) 354) or to other circuits or devices.

[0073] The server 104 may be configured to provide a plurality of devices, such as base station 102, and UE devices 106 access to network functions, e.g., as further described herein.

[0074] In some embodiments, the server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) radio access network. In some embodiments, the server 104 may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.

[0075] As described herein, the server 104 may include hardware and software components for implementing or supporting implementation of features described herein. The processor 344 of the server 104 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 344 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor 344 of the server 104, in conjunction with one or more of the other components 354, 364, and/or 374 may be configured to implement or support implementation of part or all of the features described herein.

[0076] In addition, as described herein, processor(s) 344 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s) 344. Thus, processor(s) 344 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 344. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 344.

FIG. 4: Block Diagram of a User Equipment (UE)

[0077] FIG. 4 illustrates an example simplified block diagram of a communication device 106, according to some embodiments. It is noted that the block diagram of the communication device of FIG. 4 is only one example of a possible communication device. According to embodiments, communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, an unmanned aerial vehicle (UAV), a UAV controller (UAC) and/or a combination of devices, among other devices. As shown, the communication device 106 may include a set of components 400 configured to perform core functions. For example, this set of components may be implemented as a system on chip (SOO), which may include portions for various purposes. Alternatively, this set of components 400 may be implemented as separate components or groups of components for the various purposes. The set of components 400 may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device 106.

[0078] For example, the communication device 106 may include various types of memory (e.g., including NAND flash 410), an input/output interface such as connector l/F 420 (e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display 460, which may be integrated with or external to the communication device 106, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication circuitry 429 (e.g., Bluetooth™ and WLAN circuitry). In some embodiments, communication device 106 may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet.

[0079] The cellular communication circuitry 430 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435 and 436 as shown. The short to medium range wireless communication circuitry 429 may also couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 437 and 438 as shown. Alternatively, the short to medium range wireless communication circuitry 429 may couple (e.g., communicatively; directly or indirectly) to the antennas 435 and 436 in addition to, or instead of, coupling (e.g., communicatively; directly or indirectly) to the antennas 437 and 438. The short to medium range wireless communication circuitry 429 and/or cellular communication circuitry 430 may include multiple receive chains and/or multiple transmit chains for receiving and/or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration.

[0080] In some embodiments, as further described below, cellular communication circuitry 430 may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). In addition, in some embodiments, cellular communication circuitry 430 may include a single transmit chain that may be switched between radios dedicated to specific RATs. For example, a first radio may be dedicated to a first RAT, e.g., LTE, and may be in communication with a dedicated receive chain and a transmit chain shared with an additional radio, e.g., a second radio that may be dedicated to a second RAT, e.g., 5G NR, and may be in communication with a dedicated receive chain and the shared transmit chain.

[0081] The communication device 106 may also include and/or be configured for use with one or more user interface elements. The user interface elements may include any of various elements, such as display 460 (which may be a touchscreen display), a keyboard (which may be a discrete keyboard or may be implemented as part of a touchscreen display), a mouse, a microphone and/or speakers, one or more cameras, one or more buttons, and/or any of various other elements capable of providing information to a user and/or receiving or interpreting user input.

[0082] The communication device 106 may further include one or more smart cards 445 that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards 445. Note that the term “SIM” or “SIM entity” is intended to include any of various types of SIM implementations or SIM functionality, such as the one or more UICC(s) cards 445, one or more eUlCCs, one or more eSIMs, either removable or embedded, etc. In some embodiments, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and/or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that may be embedded, e.g., may be soldered onto a circuit board in the UE 106, or each SIM 410 may be implemented as a removable smart card. Thus, the SIM(s) may be one or more removable smart cards (such as UICC cards, which are sometimes referred to as “SIM cards”), and/or the SIMs 410 may be one or more embedded cards (such as embedded UICCs (eUlCCs), which are sometimes referred to as “eSIMs” or “eSIM cards”). In some embodiments (such as when the SIM(s) include an eUlCC), one or more of the SIM(s) may implement embedded SIM (eSIM) functionality; in such an embodiment, a single one of the SIM(s) may execute multiple SIM applications. Each of the SIMs may include components such as a processor and/or a memory; instructions for performing SIM/eSIM functionality may be stored in the memory and executed by the processor. In some embodiments, the UE 106 may include a combination of removable smart cards and fixed/non-removable smart cards (such as one or more eUlCC cards that implement eSIM functionality), as desired. For example, the UE 106 may comprise two embedded SIMs, two removable SIMs, or a combination of one embedded SIMs and one removable SIMs. Various other SIM configurations are also contemplated.

[0083] As noted above, in some embodiments, the UE 106 may include two or more SIMs. The inclusion of two or more SIMs in the UE 106 may allow the UE 106 to support two different telephone numbers and may allow the UE 106 to communicate on corresponding two or more respective networks. For example, a first SIM may support a first RAT such as LTE, and a second SIM 410 supports a second RAT such as 5G NR. Other implementations and RATs are of course possible. In some embodiments, when the UE 106 comprises two SIMs, the UE 106 may support Dual SIM Dual Active (DSDA) functionality. The DSDA functionality may allow the UE 106 to be simultaneously connected to two networks (and use two different RATs) at the same time, or to simultaneously maintain two connections supported by two different SIMs using the same or different RATs on the same or different networks. The DSDA functionality may also allow the UE 106 to simultaneously receive voice calls or data traffic on either phone number. In certain embodiments the voice call may be a packet switched communication. In other words, the voice call may be received using voice over LTE (VoLTE) technology and/or voice over NR (VoNR) technology. In some embodiments, the UE 106 may support Dual SIM Dual Standby (DSDS) functionality. The DSDS functionality may allow either of the two SIMs in the UE 106 to be on standby waiting for a voice call and/or data connection. In DSDS, when a call/data is established on one SIM, the other SIM is no longer active. In some embodiments, DSDx functionality (either DSDA or DSDS functionality) may be implemented with a single SIM (e.g., a eUlCC) that executes multiple SIM applications for different carriers and/or RATs.

[0084] As shown, the SOC 400 may include processor(s) 402, which may execute program instructions for the communication device 106 and display circuitry 404, which may perform graphics processing and provide display signals to the display 460. The processor(s) 402 may also be coupled to memory management unit (MMU) 440, which may be configured to receive addresses from the processor(s) 402 and translate those addresses to locations in memory (e.g., memory 406, read only memory (ROM) 450, NAND flash memory 410) and/or to other circuits or devices, such as the display circuitry 404, short to medium range wireless communication circuitry 429, cellular communication circuitry 430, connector l/F 420, and/or display 460. The MMU 440 may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU 440 may be included as a portion of the processor(s) 402.

[0085] As described herein, the communication device 106 may include hardware and software components for implementing the above features for a communication device 106 to communicate a scheduling profile for power savings to a network. The processor 402 of the communication device 106 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 402 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 402 of the communication device 106, in conjunction with one or more of the other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460 may be configured to implement part or all of the features described herein.

[0086] In addition, as described herein, processor 402 may include one or more processing elements. Thus, processor 402 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor 402. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 402.

[0087] Further, as described herein, cellular communication circuitry 430 and short to medium range wireless communication circuitry 429 may each include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry 430 and, similarly, one or more processing elements may be included in short to medium range wireless communication circuitry 429. Thus, cellular communication circuitry 430 may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry 430. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of cellular communication circuitry 430. Similarly, the short to medium range wireless communication circuitry 429 may include one or more ICs that are configured to perform the functions of short to medium range wireless communication circuitry 429. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of short to medium range wireless communication circuitry 429.

[0088] In some embodiments, the UE 106 and/or the processors 402 thereof can be configured to and/or capable of identifying, at the UE 106, from a list of allowed tracking areas, that a tracking area is not an allowed tracking area.

FIG. 5: Block Diagram of Cellular Communication Circuitry

[0089] FIG. 5 illustrates an example simplified block diagram of cellular communication circuitry, according to some embodiments. It is noted that the block diagram of the cellular communication circuitry of FIG. 5 is only one example of a possible cellular communication circuit. According to embodiments, cellular communication circuitry 530, which may be cellular communication circuitry 430, may be included in a communication device, such as communication device 106 described above. As noted above, communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet and/or a combination of devices, among other devices.

[0090] The cellular communication circuitry 530 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435a-b and 436 as shown (in FIG. 4). In some embodiments, cellular communication circuitry 530 may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown in FIG. 5, cellular communication circuitry 530 may include a modem 510 and a modem 520. Modem 510 may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR. [0091] As shown, modem 510 may include one or more processors 512 and a memory 516 in communication with processors 512. Modem 510 may be in communication with a radio frequency (RF) front end 535. RF front end 535 may include circuitry for transmitting and receiving radio signals. For example, RF front end 535 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, receive circuitry 532 may be in communication with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0092] Similarly, modem 520 may include one or more processors 522 and a memory 526 in communication with processors 522. Modem 520 may be in communication with an RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, receive circuitry 542 may be in communication with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0093] In some embodiments, a switch 570 may couple transmit circuitry 534 to uplink (UL) front end 572. In addition, switch 570 may couple transmit circuitry 544 to UL front end 572. UL front end 572 may include circuitry for transmitting radio signals via antenna 336. Thus, when cellular communication circuitry 530 receives instructions to transmit according to the first RAT (e.g., as supported via modem 510), switch 570 may be switched to a first state that allows modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry 534 and UL front end 572). Similarly, when cellular communication circuitry 530 receives instructions to transmit according to the second RAT (e.g., as supported via modem 520), switch 570 may be switched to a second state that allows modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry 544 and UL front end 572).

[0094] As described herein, the modem 510 may include hardware and software components for implementing the above features or for time division multiplexing UL data for NSA NR operations, as well as the various other techniques described herein. The processors 512 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 512 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 512, in conjunction with one or more of the other components 530, 532, 534, 535, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.

[0095] In addition, as described herein, processors 512 may include one or more processing elements. Thus, processors 512 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 512. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 512.

[0096] The processors 522 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 522 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 522, in conjunction with one or more of the other components 540, 542, 544, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.

[0097] In addition, as described herein, processors 522 may include one or more processing elements. Thus, processors 522 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 522. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 522.

FIG. 6: Block Diagram of a Baseband Processor Architecture for a UE

[0098] FIG. 6 illustrates example components of a device 600 in accordance with some embodiments. It is noted that the device of FIG. 6 is merely one example of a possible system, and that features of this disclosure may be implemented in any of various UEs, as desired.

[0099] In some embodiments, the device 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown. The components of the illustrated device 600 may be included in a UE 106 or a RAN node 102A. In some embodiments, the device 600 may include less elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor/controller to process IP data received from an EPG). In some embodiments, the device 600 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C- RAN) implementations).

[00100] The application circuitry 602 may include one or more application processors. For example, the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 600. In some embodiments, processors of application circuitry 602 may process IP data packets received from an EPC.

[00101] The baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606. Baseband processing circuity 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606. For example, in some embodiments, the baseband circuitry 604 may include a third generation (3G) baseband processor 604A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) baseband processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 604 (e.g., one or more of baseband processors 604A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 606. In other embodiments, some or all of the functionality of baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 604 may include Fast- Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[00102] In some embodiments, the baseband circuitry 604 may include one or more audio digital signal processor(s) (DSP) 604F. The audio DSP(s) 604F may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 may be implemented together such as, for example, on a system on a chip (SOC).

[00103] In some embodiments, the baseband circuitry 604 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 604 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[00104] RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 606 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604. RF circuitry 606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.

[00105] In some embodiments, the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c. In some embodiments, the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a. RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 606a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d. The amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 604 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a necessity. In some embodiments, mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[00106] In some embodiments, the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608. The baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.

[00107] In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be configured for super-heterodyne operation.

[00108] In some embodiments, the output baseband signals, and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals, and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 606 may include analog- to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.

[00109] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[00110] In some embodiments, the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider. [00111] The synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606d may be a fractional N/N+1 synthesizer.

[00112] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a necessity. Divider control input may be provided by either the baseband circuitry 604 or the applications processor 602 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 602.

[00113] Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[00114] In some embodiments, synthesizer circuitry 606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 606 may include an IQ/polar converter.

[00115] FEM circuitry 608 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing. FEM circuitry 608 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM 608, or in both the RF circuitry 606 and the FEM 608.

[00116] In some embodiments, the FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606). The transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).

[00117] In some embodiments, the PMC 612 may manage power provided to the baseband circuitry 604. In particular, the PMC 612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 612 may often be included when the device 600 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[00118] While FIG. 6 shows the PMC 612 coupled only with the baseband circuitry 604, in other embodiments the PMC 612 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM 608.

[00119] In some embodiments, the PMC 612 may control, or otherwise be part of, various power saving mechanisms of the device 600. For example, if the device 600 is in a radio resource control_Connected (RRC_Connected) state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for brief intervals of time and thus save power.

[00120] If there is no data traffic activity for an extended period of time, then the device 600 may transition off to an RRCJdle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 600 goes into a very low power state and it performs paging where, again, it periodically wakes up to listen to the network and then powers down at least portions of the device again. The device 600 may not receive data in this state. In order to receive data, it will transition back to an RRC_Connected state.

[00121] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

[00122] Processors of the application circuitry 602 and processors of the baseband circuitry 604 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 604, alone or in combination, may be used for defining clusters of PFs, POs, and PEIs during paging cycles. Accordingly, the baseband circuitry 604 can be used to encode a message for transmission between a UE and a gNB, or decode a message received between a UE and a gNB. For example, the baseband circuitry 604 can be used to encode a 5GSM message for one or more network-requested 5GSM procedures for transmission to a base station; or encode a 5GSM message for transmission of one or more UE-requested 5 GSM procedures from the UE.

FIG. 7: Block Diagram of an Interface of Baseband Circuitry

[00123] FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments. It is noted that the baseband circuitry of FIG. 7 is merely one example of a possible circuitry, and that features of this disclosure may be implemented in any of various systems, as desired.

[00124] As discussed above, the baseband circuitry 604 of FIG. 6 may comprise processors 604A-604E and a memory 604G utilized by said processors. Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send/receive data to/from the memory 604G.

[00125] The baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 712 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604), an application circuitry interface 714 (e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6), an RF circuitry interface 716 (e.g., an interface to send/receive data to/from RF circuitry 606 of FIG. 6), a wireless hardware connectivity interface 718 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 720 (e.g., an interface to send/receive power or control signals to/from the PMC 612.

FIG. 8: Control Plane Protocol Stack

[00126] FIG. 8 is an illustration of a control plane protocol stack in accordance with some embodiments. In this embodiment, a control plane 800 is shown as a communications protocol stack between the UE 106a (or alternatively, the UE 106b), the RAN node 102A (or alternatively, the RAN node 102B), and the mobility management entity (MME) 621 .

[00127] The PHY layer 801 may transmit or receive information used by the MAC layer 802 over one or more air interfaces. The PHY layer 801 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 805. The PHY layer 801 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.

[00128] The MAC layer 802 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.

[00129] The RLC layer 803 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layer 803 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC layer 803 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

[00130] The PDCP layer 804 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform insequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timerbased discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).

[00131] The main services and functions of the RRC layer 805 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting. Said MIBs and SIBs may comprise one or more information elements (lEs), which may each comprise individual data fields or data structures.

[00132] The UE 601 and the RAN node 102A may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 801 , the MAC layer 802, the RLC layer 803, the PDCP layer 804, and the RRC layer 805.

[00133] The non-access stratum (NAS) protocols 806 form the highest stratum of the control plane between the UE 601 and the MME 621. The NAS protocols 806 support the mobility of the UE 601 and the session management procedures to establish and maintain IP connectivity between the UE 601 and the P-GW 623.

[00134] The S1 Application Protocol (S1 -AP) layer 815 may support the functions of the S1 interface and comprise Elementary Procedures (EPs). An EP is a unit of interaction between the RAN node 102A and the network 100. The S1 -AP layer services may comprise two groups: UE-associated services and non UE- associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.

[00135] The Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP/IP layer) 814 may ensure reliable delivery of signaling messages between the RAN node 102A and the MME 621 based, in part, on the IP protocol, supported by the IP layer 813. The L2 layer 812 and the L1 layer 81 1 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.

[00136] The RAN node 102A and the MME 621 may utilize an S1 -MME interface to exchange control plane data via a protocol stack comprising the L1 layer 81 1 , the L2 layer 812, the IP layer 813, the SCTP layer 814, and the S1 -AP layer 815.

FIG. 9: User Plane Protocol Stack

[00137] FIG. 9 is an illustration of an example of a user plane protocol stack in accordance with some embodiments. In this embodiment, a user plane 900 is shown as a communications protocol stack between the UE 106A (or alternatively, the UE 106B or 106N), the RAN node 102A (or alternatively, the RAN node 102B), the S-GW 622, and the P-GW 623. The user plane 900 may utilize at least some of the same protocol layers as the control plane 800. For example, the UE 601 and the RAN node 102A may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 801 , the MAC layer 802, the RLC layer 803, the PDCP layer 804.

[00138] The General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 904 may be used for carrying user data within the GPRS core network and between the radio access network and the core network. The user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example. The UDP and IP security (UDP/IP) layer 903 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows. The RAN node 102A and the S-GW 622 may utilize an S1 -U interface to exchange user plane data via a protocol stack comprising the L1 layer 81 1 , the L2 layer 812, the UDP/IP layer 903, and the GTP-U layer 904. The S-GW 622 and the P-GW 623 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the L1 layer 811 , the L2 layer 812, the UDP/IP layer 903, and the GTP- U layer 904. As discussed above with respect to FIG. 8, NAS protocols support the mobility of the UE 106 and the session management procedures to establish and maintain IP 813 connectivity between the UE 106 and the P-GW 623.

[00139] For the remainder of this disclosure, references to base station (gNB) and user equipment (UE) are assumed to refer to base station (gNB) 102 and user equipment (UE) 106, respectively, even though specific reference numerals may be omitted. FIG. 10: MMTEL Service with non-allowed service area

[00140] The 3GPP I Next Generation Network (NGN) Internet Protocol (IP) Multimedia Subsystem (IMS) multimedia telephony (MMTel) service is a global standard that is based on the IMS. The standard provides converged, fixed and mobile, real-time multimedia communication using media capabilities such as voice, real-time video, text, file transfer other multimedia formats such as the transfer of pictures, audio and video clips.

[00141] The MMTel standard is described in 3GPP technical specification (TS) 24.173 V18.0.0 (January 2023) and provides telecommunications grade voice services over IP technology. It allows for interoperable services between different types of operators and towards legacy networks, such as the plain old telephone service (PSTN) and other standards, such as the Institute of Electronics and Electrical Engineers (IEEE) 802.1 1 (Wi-Fi) standard. Operators can use multiple vendors within a network and integrate it with services provided over the internet.

[00142] FIG. 10 provides an example illustration of one variation of an MMTel service in which a UE 106 is in a first cell 1002. The UE 106 is transitioning from the first cell 1002 to a second cell 1004. Each cell 1002, 1004 can be coupled to a network 100, such as a 3GPP cellular network. The UE 106 can also be coupled to an access point (AP) 112, such as an IEEE 802.1 1 AP. The AP 112 can also be in communication with the network 100.

[00143] Each cell 1002, 1004 can be referred to as a tracking area. Each tracking area (TA) can be associated with a tracking area code (TAG). In this example, base station 102A is located in TAC1 and base station 102B is in TAG2. Each tracking area can have the same or different service area restrictions. The service area restrictions consist of tracking areas forming either an allowed area, or a non-allowed area. The tracking areas belong to either the registered PLMN or its equivalent PLMNs in a registration area. The allowed area can contain up to 16 tracking areas or include all tracking areas in the registered PLMN and its equivalent PLMN(s) in the registration area. The non-allowed area can contain up to 16 tracking areas. The network 100 can convey the service area restrictions to the UE by including either an allowed area, or a non-allowed area, but not both, in a service area list information element (IE) of a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message.

[00144] When the UE 106 camps on a tracking area which is a non-allowed area (e.g. TAC2 1004), the UE 106 enters a state designated as a non-allowed service using the 5G system (5GS) mobility management protocol (5GMM). The 5GMM provides procedures for the control of mobility when the UE is using the nextgeneration (NG) radio access network (NG-RAN) and/or a non-3GPP access network. The 5GMM protocol also provides for control of security for non-access stratum (NAS) protocols.

[00145] In the example of FIG. 10, when the UE 106 camps in TAC2 1004, the UE enters a state designated as 5GMM-REGISTERED.NON-ALLOWED- SERVICE. To reduce signaling, the 3GPP TS 24.501 specification designates that only limited procedures are allowed by the UE in the 5GMM-REGISTERED.NON- ALLOWED-SERVICE. As used herein, reference to 3GPP TS 24.501 refers to TS 24.501 Version 18.5.0 (December 2023).

[00146] In section 5.3.5.2 of 3GPP TS 24.501 , 3GPP access service area restrictions are listed when the UE 106 is in the 5GMM-REGISTERED.NON- ALLOWED-SERVICE state. While in this state, the UE 106 is still allowed critical services such as: emergency services; emergency services fallback; high priority access; indicating a change of 3GPP PS data off UE status. In addition, the transmission of a NAS transport procedure is restricted to the following: a Short Message Service (SMS); a Long Term Extended (LTE) Positioning Protocol (LPP) message; a location services message; a Steering of Roaming (SOR) transparent container; a UE policy container; UE parameters update transparent container; or a cellular internet of things (CloT) user data container.

[00147] Accordingly, when the UE 106 is camped in the TAC2 non-allowed service area 1004, the UE is typically not able to send signaling or data that is not related to the allowed critical services and NAS signaling listed in the previous paragraph.

[00148] In one example, when the UE may be camped in a non-allowed service area, such as TAC2, and the NW has started an MMTEL session. However, because IMS signaling is not allowed according to the service area restrictions in section 5.3.5.2 of 3GPP TS 24.501 , the UE 106 is not able to complete the MMTEL call establishment, and an IMS call failure can occur. This is a common scenario for a UE in a non-allowed service area, based on the current rules in 3GPP TS 24.501. The call failure can result in an increase of the call Key Performance Indicators (KPI) and service area KPI.

[00149] In the example of FIG. 10, the UE 106 is illustrated as transitioning from TAC1 , that is an allowed service area, to TAC2, that is a non-allowed area. Accordingly, in a scenario where the network (NW) initiates session modification (SM) signaling to the UE, while the UE is located in the non-allowed service area of TAC2, and the UE is in a 5GMM-REGISTERED. NON-ALLOWED-SERVICE state, the UE is not allowed to send 5G session management (5GSM) messages. This can also result in a failure of critical services at the UE, such as emergency services, high priority access services, or mobile terminated (MT) MMTEL calls.

FIG. 1 1 : MMTEL Call with Critical Service Failure

[00150] FIG. 1 1 provides an example 1 100 illustration of an MMTEL call that results in a failure while a UE is operating in a TAG having a Service Area Restriction (SAR), in accordance with some embodiments. In this example 1 100, the UE 106 may move from Tracking Area 1 into the Tracking Area 2 (e.g. FIG. 10) that is associated with the TAC2, and camp on the TAC2 cell 1 102. In the registration procedure, the NW 100 can send a service area list 1104 that includes the allowed tracking areas. The UE can determine from the service area list that the cell associated with TAC2 is a non-allowed tracing area. Alternatively, the nonallowed location of the UE may be determined in other ways. For example, the UE and/or NW may determine that the UE is in a non-allowed-service area based on the geographic location of the UE, or the location of the UE relative to a base station.

[00151] The UE 106 can then determine that the UE is in a non-allowed-service area 1104 and enter a 5GMM-REGISTERED. NON-ALLOWED-SERVICE state 1106. When the UE is in the 5GMM-REGISTERED. NON-ALLOWED-SERVICE state, the UE can only communicate based on the service area restrictions in section 5.3.5.2 of 3GPP TS 24.501 , as previously discussed. The restriction to critical services 1108 is illustrated in FIG. 1 1 .

[00152] In one example, the UE 106 may receive an emergency call 1 110. The emergency call 1 1 10 may be initiated by an application processor 1 12, as illustrated in FIG. 11 . Alternatively, the emergency call can also be routed by the NW 100. The UE can then configure high priority access based on the emergency call 1 110. Multimedia priority services (MPS) allows priority access to system resources to the UE 106, creating the ability of the UE to deliver or complete sessions of a high priority nature. The MPS-subscribed UE can obtain priority for quality of service (QoS) Flows (for example, used for IMS signaling). MPS provides priority treatment to increase the probability of the UE’s voice, video, and data communication session being successful.

[00153] In addition, the UE 106 can be configured for mission critical services (MCS). Mission critical services are services that require preferential handling compared to normal telecommunication services. The mission critical services can be used for public safety applications and also for general commercial applications. Mission critical services can enable the UE to communicate using methods that aren’t available for non-critical UEs, including but not limited to mission critical data signaling and mission critical video signaling. Additional information regarding mission critical services can be found in 3GPP TS 24.484 V18.4.0 (December 2023).

[00154] The UE can transmit a trigger 11 13 indicating a change of 3GPP packet switched (PS) data off UE status. The UE 106 can receive paging messages 1 1 14 from the network 100 when the UE is in the 5GMM Registered Non-Allowed Service state 1 106 if the paging is related to the emergency services, such as the emergency call 11 10. In this example, the paging is sent from the network 100, and encoded by the base station using a baseband processor 604 and transmitted to the UE 106 by the base station, such as 102B or 102A (FIG. 10).

[00155] In one embodiment, the emergency call may be a video call that uses more bandwidth than the UE is currently using in the non-allowed area 1004. The NW 100 is aware of the bandwidth needed for the emergency call and may send a downlink (DL) non-access stratum (NAS) transport (DL_NAS_TRANSPORT) message with a packet data unit (PDU) session modification (SM) command (PDU SESSION MODIFICATION COMMAND) 11 16. In this example, the network may want to modify the session by adding additional bearers to provide more bandwidth between the UE and the base station 102B to enable the emergency video call.

[00156] However, the UE 106 is not allowed to respond to the PDU SM command message 1 1 16 received from the NW 100 via the base station 102B. Since UE 106 can only communicate, while the UE is in the non-allowed area, based on the service area restrictions in section 5.3.5.2 of 3GPP TS 24.501 , the UE is not allowed to send any uplink (UL) NAS transport (UL_NAS_TRANSPORT) message 11 18 in the non-allowed service area 1004. The UE can’t respond to any type of SM related signaling from the network. In accordance with the restrictions, the UE can only send a status message (5GMM STATUS) with a selected error code, such as error #98 “message type not compatible with protocol state” 1120.

[00157] While the NW 100 may not immediately disconnect from the UE 106, after the NW receives a number of error messages, the NW may choose to eventually release the connection with the UE 106. This will result in a failure of the emergency call 11 10 at the UE 106.

[00158] The failure of the emergency call 1 110 at the UE 106 can have real world consequences. For example, an emergency worker may be communicating with a command center regarding an emergency, such as a fire, earthquake, building collapse, avalanche, or any other type of emergency. The emergency worker may enter a non-allowed area, as previously discussed. The command center may be attempting to show the emergency worker important details regarding the potential rescue of victims. However, due to the current service area restrictions in section 5.3.5.2 of 3GPP TS 24.501 , the UE is not allowed to perform session modifications to modify the emergency call in the non-allowed area 1004, which may result in the call being lost and the UE dropped from the NW 100.

[00159] In accordance with some embodiments, the service area restrictions in section 5.3.5.2 of 3GPP TS 24.501 can be updated to allow a UE to place or maintain an emergency call in a non-allowed area, such as 1004 in FIG. 10, while still minimizing non-emergency traffic in the non-allowed area. FIG. 12 illustrates one example of additional exceptions that can be added to the service area restrictions in section 5.3.5.2 of 3GPP TS 24.501 to reduce dropped calls in nonallowed areas.

FIG. 12: 3GPP TS 24.501 , Section 5.3.5.2 with 5GSM Modifications

[00160] In the example of FIG. 12, 3GPP TS 24.501 , Section 5.3.5.2 (b)(2)(iii) includes the restriction that if the UE is successfully registered to a PLMN or standalone non-public network (SNPN) and the UE has a stored list of "allowed tracking areas” the UE shall enter the state 5GMM-REGISTERED.NON- ALLOWED-SERVICE, and: if the UE is in a 5GMM-CONNECTED mode or a 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access, the UE, according section (iii), shall not initiate a 5G session management (5GSM) procedure except for: emergency services; high priority access; or indicating a change of 3GPP packet switched (PS) data off UE status. In addition, according to section (iv), the UE shall not perform the NAS transport procedure except for sending: SMS; an LPP message; a location services message; an SOR transparent container; a UE policy container; a UE parameters update transparent container; or a CIOT user data container.

[00161] To enable reduced call failures and an increase in call KPI and service area KPI, 3GPP TS 24.501 Section 5.3.5.2 (b)(2)(iv) can be amended to include the additional conditions that the UE shall not perform the NAS transport procedure except for the sending: 5G session management (5GSM) messages for UE- requested 5GSM procedures allowed in TS 24.501 Section 5.3.5.2 (b)(2)(iii); and 5GSM messages for Network-requested 5GSM procedures, as illustrated in FIG. 12. It should be noted that the 5GSM messages for Network-requested 5GSM procedures are not limited by the list in TS 24.501 Section 5.3.5.2 (b)(2)(iii)

[00162] With the proposed changes to 3GPP TS 24.501 Section 5.3.5.2 (b)(2)(iv), the UE can send 5G session management messages for UE requested procedures (that are allowed in 3GPP TS 24.501 Section 5.3.5.2 (b)(2)(iii)), and 5G session management messages for any network-requested 5GSM procedures. With these capabilities, the emergency call illustrated in the example illustrated in FIG. 1 1 would not have ended in a critical service failure 1 122 since the UE would have been allowed to send the UL_NAS_TRANSPORT message 1 1 18 and perform the session modifications requested by the network, thereby enabling more bearers to be added to support a video call at the UE.

FIG. 13: MMTEL Call with Critical Service Success

[00163] FIG. 13 provides an example illustration 1300 of an MMTEL call that results in a critical service success while the UE is operating in a TA having a Service Area Restriction (SAR), in accordance with some embodiments. In this example 1300, the UE 106 proceeds under the same process described in FIG. 11. However, when the NW 100 sends the paging message 1314 informing the UE 106 of the MMTEL call. At some point, the NW can send the DL- NAS_TRANSPORT message for a

PDU SESSION MODIFICATION COMMAND 1316. The UE 106 can detect that the procedure is started as part of a critical service that is allowed in the NON- ALLOWED-SERVICE according to the modified section of 3GPP TS 24.501 Section 5.3.5.2 (b)(2)(iv), as illustrated in FIG. 12, and according to 3GPP TS 24.501 Section 5.3.5.2 (b)(2)(iii). In this case, the NW 100 receives the PDU session modification command complete message 1320 from the UE 106. Accordingly, there is a critical service success 1322 and the emergency call, in this example a video call, is maintained by the NW and the UE based on the modified rules, thereby enabling the emergency worker, or the person located in the nonallowed area, to place or receive the emergency call within the non-allowed area.

[00164] Accordingly, with the modified section of 3GPP TS 24.501 Section 5.3.5.2 (b)(2)(iv), as illustrated in FIG. 12, critical service failures will decrease and call KPI and service area KPI will increase.

FIGs. 14A and 14B: Flow Chart for Sending 5GSM Messages at a UE in a Non- Allowed Service Area

[00165] FIGs. 14A and 14B illustrates a flow chart of an example of a method 1400 of sending 5G session management (5GSM) messages at a user equipment (UE) in a non-allowed service area. The method comprises camping on a cell in a tracking area, as shown in block 1410. The UE can identify, from a list of allowed tracking areas, that the tracking area is not an allowed tracking area, as shown in block 1420. The UE can enter a fifth generation mobility management (5GMM)- REGISTERED-NON-ALLOWED-SERVICE state, as shown in block 1430. The method 1400 further comprises allowing non-access stratum (NAS) procedures related to a handling of NW initiated 5GSM procedures in a 5GMM CONNECTED state, as shown in block 1440; or allowing any NAS procedures related to a handling of UE initiated 5GSM procedures related to: emergency services; or emergency services fallback; or high priority access; or responding to paging or responding to a notification; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status, as shown in block 1450. Continuing in FIG. 14B, the method 1400 can further comprise encoding a fifth generation session management (5GSM) message for transmission from the UE for one or more network-requested 5GSM procedures; or encoding a 5GSM message for transmission from the UE for one or more UE-requested 5GSM procedures related to the handling of UE initiated 5GSM procedures, as shown in blocks 1460 and 1470. The step of encoding the 5GSM message for transmission from the UE for one or more UE-requested 5GSM procedures in block 1470 can occur for procedures related to: emergency services; or emergency services fallback; or high priority access; or responding to paging or responding to a notification; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status.

[00166] In some embodiments, the cell is in a registered public land mobile network (PLMN), a PLMN from a list of equivalent PLMNs, or a standalone nonpublic network (SNPN).

[00167] In some embodiments, a tracking area indicator (TAI) for the cell, at a time that the UE is in the cell, is not in the list of allowed tracking areas. The list of allowed tracking areas can be stored at the UE. The UE can be in a 5GMM- CONNECTED mode or a 5GMM-CONNECTED mode with a radio resource control (RRC) inactive indication over 3GPP access.

[00168] In some embodiments, the UE is configured to not initiate a 5GSM procedure except for one or more 5GSM procedures comprising: emergency services; high priority access; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status. The UE is configured to not perform a non-access stratum (NAS) procedure except for sending: the 5GSM message for one or more UE-requested 5GSM procedures for that are the one or more 5GSM procedures; the 5GSM message for one or more network-requested 5GSM procedures; a Short Message Service (SMS); a Long Term Evolution (LTE) Positioning Protocol (LPP) message; a location services message; a Steering of Roaming (SOR) transparent container; a UE policy container; UE parameters update transparent container; or a cellular internet of things (CloT) user data container.

[00169] FIG. 15 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 15 shows a diagrammatic representation of hardware resources 1500 including one or more processors (or processor cores) 1510, one or more memory/storage devices 1520, and one or more communication resources 1530, each of which may be communicatively coupled via a bus 1540. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1502 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1500.

[00170] The processors 1510 may include, for example, a processor 1512 and a processor 1514. The processor(s) 1510 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[00171] The memory/storage devices 1520 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1520 may include, but are not limited to, any type of volatile or nonvolatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

[00172] The communication resources 1530 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1504 or one or more databases 1506 via a network 1508. For example, the communication resources 1530 may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

[00173] Instructions 1550 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1510 to perform any one or more of the methodologies discussed herein. The instructions 1550 may reside, completely or partially, within at least one of the processors 1510 (e.g., within the processor’s cache memory), the memory/storage devices 1520, or any suitable combination thereof. Furthermore, any portion of the instructions 1550 may be transferred to the hardware resources 1500 from any combination of the peripheral devices 1504 or the databases 1506. Accordingly, the memory of processors 1510, the memory/storage devices 1520, the peripheral devices 1504, and the databases 1506 are examples of computer-readable and machine-readable media.

Examples of Systems, Apparatuses, and Methods

[00174] The following examples pertain to specific technology embodiments and point out specific features, elements, or actions that can be used or otherwise combined in achieving such embodiments.

[00175] Example 1 is directed to a method of sending 5G session management (5GSM) messages at a user equipment (UE) in a non-allowed service area, the method comprising: camping on a cell in a tracking area; identifying, at the UE, from a list of allowed tracking areas, that the tracking area is not an allowed tracking area; entering a fifth generation mobility management (5GMM)-REGISTERED- NON-ALLOWED-SERVICE state at the UE; and sending a 5GSM message for one or more network-requested 5GSM procedures; or sending a 5GSM message for one or more UE-requested 5GSM procedures from the UE for one or more of: emergency services; or high priority access; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status.

[00176] Example 2 includes the method of Example 1 , wherein the cell is in a registered public land mobile network (PLMN), a PLMN from a list of equivalent PLMNs, or a standalone non-public network (SNPN).

[00177] Example 3 includes the method of example 1 , wherein a tracking area indicator (TAI) for the cell, at a time that the UE is in the cell, is not in the list of allowed tracking areas.

[00178] Example 4 includes the method of example 1 , wherein the list of allowed tracking areas is stored at the UE.

[00179] Example 5 includes the method of example 1 , wherein the UE is in a 5GMM-CONNECTED mode or a 5GMM-CONNECTED mode with a radio resource control (RRC) inactive indication over 3GPP access.

[00180] Example 6 includes the method of example 1 , wherein the UE is configured to not initiate a 5GSM procedure except for one or more 5GSM procedures comprising: emergency services; high priority access; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status.

[00181] Example 7 includes the method of example 6, wherein the UE is configured to not perform a non-access stratum (NAS) procedure except for sending: the 5GSM message for one or more UE-requested 5GSM procedures for that are the one or more 5GSM procedures; the 5GSM message for one or more network-requested 5GSM procedures; a Short Message Service (SMS); a Long Term Extended (LTE) Positioning Protocol (LPP) message; a location services message; a Steering of Roaming (SOR) transparent container; a UE policy container; UE parameters update transparent container; or a cellular internet of things (CloT) user data container.

[00182] Example 8 is directed to an apparatus configured to cause a user equipment (UE) to perform any of the methods of examples 1 -7. Example 9 is directed to a baseband processor configured to perform one or more of the methods in examples 1 to 7. Example 10 is directed to an apparatus configured to cause a base station (BS) to perform any of the methods of examples 1 to 7.

[00183] Example 1 1 is directed to an apparatus of a user equipment (UE) comprising: one or more processors, coupled to a memory, configured to: identify that the UE is camping on a cell in a tracking area; determine, at the UE, from a list of allowed tracking areas, that the tracking area is not an allowed tracking area; configure the UE to enter a fifth generation mobility management (5GMM)- REGISTERED-NON-ALLOWED-SERVICE state at the UE when the UE is not in the allowed tracking area; encode a fifth generation session management (5GSM) message for transmission from the UE for one or more network-requested 5GSM procedures; or encode a 5GSM message for transmission from the UE for one or more UE-requested 5GSM procedures for one or more of: emergency services; or high priority access; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status.

[00184] Example 12 includes the apparatus of example 1 1 , wherein the cell is in: a registered public land mobile network (PLMN); a PLMN from a list of equivalent PLMNs; or a standalone non-public network (SNPN).

[00185] Example 13 includes the apparatus of example 1 1 , wherein a tracking area indicator (TAI) for the cell, at a time that the UE is in the cell, is not in the list of allowed tracking areas.

[00186] Example 14 includes the apparatus of example 1 1 , wherein the list of allowed tracking areas is stored at the UE.

[00187] Example 15 includes the apparatus of example 11 , wherein the UE is in a 5GMM-CONNECTED mode or a 5GMM-CONNECTED mode with a radio resource control (RRC) inactive indication over 3GPP access.

[00188] Example 16 includes the apparatus of example 1 1 , wherein the UE is configured to not initiate a 5GSM procedure except for one or more 5GSM procedures comprising: emergency services; high priority access; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status. [00189] Example 17 includes the apparatus of example 16, wherein the UE is configured to not perform a non-access stratum (NAS) procedure except for sending: the 5GSM message for one or more UE-requested 5GSM procedures for that are the one or more 5GSM procedures; the 5GSM message for one or more network-requested 5GSM procedures; a Short Message Service (SMS); a Long Term Evolution (LTE) Positioning Protocol (LPP) message; a location services message; a Steering of Roaming (SOR) transparent container; a UE policy container; UE parameters update transparent container; or a cellular internet of things (CloT) user data container.

[00190] Example 18 is directed to a computer program product, comprising computer instructions which, when executed by one or more processors, perform any of the operations or methods described herein.

[00191] Example 19 is directed to at least one machine readable storage medium having instructions embodied thereon for sending fifth generation session management (5GSM) messages at a user equipment (UE) in a non-allowed service area, the instructions when executed by one or more processors at a user equipment (UE) perform the following: camping on a cell in a tracking area; identifying, at the UE, from a list of allowed tracking areas, that the tracking area is not an allowed tracking area; entering a fifth generation mobility management (5GMM)-REGISTERED-NON-ALLOWED-SERVICE state at the UE; and sending a 5GSM message for one or more network-requested 5GSM procedures; or sending a 5GSM message for one or more UE-requested 5GSM procedures from the UE for one or more of: emergency services; or high priority access; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status.

[00192] Example 20 includes the at least one machine readable storage medium of example 19 wherein the cell is in a registered public land mobile network (PLMN), a PLMN from a list of equivalent PLMNs, or a standalone non-public network (SNPN).

[00193] Example 21 includes the at least one machine readable storage medium of example 19 wherein, a tracking area indicator (TAI) for the cell, at a time that the UE is in the cell, is not in the list of allowed tracking areas. [00194] Example 22 includes the at least one machine readable storage medium of example 19 wherein the list of allowed tracking areas is stored at the UE.

[00195] Example 23 includes the at least one machine readable storage medium of example 19 wherein the UE is in a 5GMM-CONNECTED mode or a 5GMM- CONNECTED mode with a radio resource control (RRC) inactive indication over 3GPP access.

[00196] Example 24 includes the at least one machine readable storage medium of example 19 wherein the UE is configured to not initiate a 5GSM procedure except for one or more 5GSM procedures comprising: emergency services; high priority access; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status.

[00197] Example 25 includes the at least one machine readable storage medium of example 24 wherein the UE is configured to not perform a non-access stratum (NAS) procedure except for sending: the 5GSM message for one or more UE- requested 5GSM procedures for that are the one or more 5GSM procedures; the 5GSM message for one or more network-requested 5GSM procedures; a Short Message Service (SMS); a Long Term evolution (LTE) Positioning Protocol (LPP) message; a location services message; a Steering of Roaming (SOR) transparent container; a UE policy container; UE parameters update transparent container; or a cellular internet of things (CloT) user data container.

[00198] Embodiments of the present disclosure may be realized in any of various forms. For example, some embodiments may be realized as a computer- implemented method, a computer readable memory medium, or a computer system. Other embodiments may be realized using one or more custom-designed hardware devices such as ASICs. Still other embodiments may be realized using one or more programmable hardware elements such as FPGAs.

[00199] In some embodiments, a non-transitory computer-readable memory medium may be configured so that it stores program instructions and/or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of the method embodiments described herein, or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets.

[00200] In some embodiments, a device (e.g., a UE 106) may be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets). The device may be realized in any of various forms.

[00201] Any of the methods described herein for operating a user equipment (UE) may be the basis of a corresponding method for operating a base station, by interpreting each message/signal X received by the UE in the downlink as message/signal X transmitted by the base station, and each message/signal Y transmitted in the uplink by the UE as a message/signal Y received by the base station.

[00202] Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims

CLAIMS What is claimed is:

1 . A method of sending 5G session management (5GSM) messages at a user equipment (UE) in a non-allowed service area, the method comprising: camping on a cell in a tracking area; identifying, at the UE, from a list of allowed tracking areas, that the tracking area is not an allowed tracking area and the UE is in a non-allowed tracking area; entering a fifth generation mobility management (5GMM)- REGISTERED-NON-ALLOWED-SERVICE state at the UE; and allowing non-access stratum (NAS) procedures related to a handling of NW initiated 5GSM procedures in a 5GMM CONNECTED state; or allowing any NAS procedures related to a handling of UE initiated 5GSM procedures related to: emergency services; or emergency services fallback; or high priority access; or responding to paging or responding to a notification; or indicating a change of third generation partnership project

(3GPP) packet switched (PS) data off UE status; and encoding a fifth generation session management (5GSM) message for transmission from the UE for one or more network- requested 5GSM procedures; or encoding a 5GSM message for transmission from the UE for one or more UE-requested 5GSM procedures related to the handling of UE initiated 5GSM procedures.

2. The method of claim 1 , wherein the cell is in a registered public land mobile network (PLMN), a PLMN from a list of equivalent PLMNs, or a standalone non-public network (SNPN).

3. The method of claim 1 , wherein a tracking area indicator (TAI) for the cell, at a time that the UE is in the cell, is not in the list of allowed tracking areas.

4. The method of claim 1 , wherein the list of allowed tracking areas is stored at the UE.

5. The method of claim 1 , wherein the UE is in a 5GMM- CONNECTED mode or a 5GMM-C0NNECTED mode with a radio resource control (RRG) inactive indication over 3GPP access.

6. The method of claim 1 , wherein the UE is configured to not initiate a 5GSM procedure except for one or more 5GSM procedures comprising: emergency services; high priority access; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status.

7. The method of claim 6, wherein the UE is configured to not perform a non-access stratum (NAS) procedure except for sending: the 5GSM message for one or more UE-requested 5GSM procedures for that are the one or more 5GSM procedures; the 5GSM message for one or more network- requested 5GSM procedures; a Short Message Service (SMS); a Long Term Extended (LTE) Positioning Protocol (LPP) message; a location services message; a Steering of Roaming (SOR) transparent container; a UE policy container; UE parameters update transparent container; or a cellular internet of things (CloT) user data container.

8. An apparatus configured to cause a user equipment (UE) to perform any of the methods of claims 1 to 7.

9. A baseband processor configured to perform one or more of the methods claims 1 to 7.

10. An apparatus configured to cause a base station (BS) to perform any of the methods of claims 1 to 7.

1 1 . An apparatus of a user equipment (UE) comprising: one or more processors, coupled to a memory, configured to: identify that the UE is camping on a cell in a tracking area; determine, at the UE, from a list of allowed tracking areas, that the tracking area is not an allowed tracking area; configure the UE to enter a fifth generation mobility management (5GMM)-REGISTERED-NON-ALLOWED-SERVICE state at the UE when the UE is not in the allowed tracking area; allowing non-access stratum (NAS) procedures related to a handling of NW initiated 5GSM procedures in a 5GMM CONNECTED state; or allowing any NAS procedures related to a handling of UE initiated 5GSM procedures related to: emergency services; or emergency services fallback; or high priority access; or responding to paging or responding to a notification; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status; and encode a fifth generation session management (5GSM) message for transmission from the UE for one or more network- requested 5GSM procedures; or encode a 5GSM message for transmission from the UE for one or more UE-requested 5GSM procedures related to the handling of UE initiated 5GSM procedures.

12. The apparatus of claim 11 , wherein the cell is in: a registered public land mobile network (PLMN); a PLMN from a list of equivalent PLMNs; or a standalone non-public network (SNPN).

13. The apparatus of claim 11 , wherein a tracking area indicator (TAI) for the cell, at a time that the UE is in the cell, is not in the list of allowed tracking areas.

14. The apparatus of claim 11 , wherein the list of allowed tracking areas is stored at the UE.

15. The apparatus of claim 11 , wherein the UE is in a 5GMM- CONNECTED mode or a 5GMM-CONNECTED mode with a radio resource control (RRC) inactive indication over 3GPP access.

16. The apparatus of claim 11 , wherein the UE is configured to not initiate a 5GSM procedure except for one or more 5GSM procedures comprising: emergency services; high priority access; or indicating a change of third generation partnership project

(3GPP) packet switched (PS) data off UE status.

17. The apparatus of claim 16, wherein the UE is configured to not perform a non-access stratum (NAS) procedure except for sending: the 5GSM message for one or more UE-requested 5GSM procedures for that are the one or more 5GSM procedures; the 5GSM message for one or more network- requested 5GSM procedures; a Short Message Service (SMS); a Long Term Evolution (LTE) Positioning Protocol (LPP) message; a location services message; a Steering of Roaming (SOR) transparent container; a UE policy container; UE parameters update transparent container; or a cellular internet of things (CloT) user data container.

18. A computer program product, comprising computer instructions which, when executed by one or more processors, perform any of the operations or methods described herein.

19. At least one machine readable storage medium having instructions embodied thereon for sending fifth generation session management (5GSM) messages at a user equipment (UE) in a non-allowed service area, the instructions when executed by one or more processors at a user equipment (UE) perform the following: camping on a cell in a tracking area; identifying, at the UE, from a list of allowed tracking areas, that the tracking area is not an allowed tracking area; entering a fifth generation mobility management (5GMM)- REGISTERED-NON-ALLOWED-SERVICE state at the UE; and allowing non-access stratum (NAS) procedures related to a handling of NW initiated 5GSM procedures in a 5GMM CONNECTED state; or allowing any NAS procedures related to a handling of UE initiated 5GSM procedures related to: emergency services; or emergency services fallback; or high priority access; or responding to paging or responding to a notification; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status; and encode a fifth generation session management (5GSM) message for transmission from the UE for one or more network- requested 5GSM procedures; or encode a 5GSM message for transmission from the UE for one or more UE-requested 5GSM procedures related to the handling of UE initiated 5GSM procedures.

20. The at least one machine readable storage medium of claim 19, wherein the cell is in a registered public land mobile network (PLMN), a PLMN from a list of equivalent PLMNs, or a standalone non-public network (SNPN).

21 . The at least one machine readable storage medium of claim 19, wherein a tracking area indicator (TAI) for the cell, at a time that the UE is in the cell, is not in the list of allowed tracking areas.

22. The at least one machine readable storage medium of claim 19, wherein the list of allowed tracking areas is stored at the UE.

23. The at least one machine readable storage medium of claim 19, wherein the UE is in a 5GMM-CONNECTED mode or a 5GMM- CONNECTED mode with a radio resource control (RRC) inactive indication over 3GPP access.

24. The at least one machine readable storage medium of claim 19, wherein the UE is configured to not initiate a 5GSM procedure except for one or more 5GSM procedures comprising: emergency services; high priority access; or indicating a change of third generation partnership project (3GPP) packet switched (PS) data off UE status.

25. The at least one machine readable storage medium of claim 24, wherein the UE is configured to not perform a non-access stratum (NAS) procedure except for sending: the 5GSM message for one or more UE-requested 5GSM procedures for that are the one or more 5GSM procedures; the 5GSM message for one or more network- requested 5GSM procedures; a Short Message Service (SMS); a Long Term Evolution (LTE) Positioning Protocol (LPP) message; a location services message; a Steering of Roaming (SOR) transparent container; a UE policy container; UE parameters update transparent container; or a cellular internet of things (CloT) user data container.