5G New Radio NAS Notification Procedure

Abstract

The present invention discloses a 5G New Radio NAS notification procedure. The present invention provides an apparatus, system and method for a wireless device to perform a method of dual registration in a fifth generation (5G) new radio (NR) network, including notification procedure enhancements, dual registration enhancements and paging enhancements through cellular (e.g., 3GPP) access and non-cellular (e.g., non-3GPP) access. The method also includes a procedure for the network to determine the access type to notify the UE of pending data and for the wireless device and the network to mitigate paging conflicts.

Description

[0001] This application is a divisional application of the invention patent application with application number 201910741920.1, filed on August 13, 2019, and invention name “5G New Radio NAS Notification Procedure”. Technical Field

[0002] The present application relates to wireless devices, and more particularly to apparatus, systems and methods for improving dual registration in fifth generation (5G) new radio (NR) networks, including notification procedure enhancements, dual registration enhancements and paging enhancements. Background Art

[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now also 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 functions.

[0004] Long Term Evolution (LTE) has become the technology of choice for most wireless network operators around the world to provide mobile broadband data and high-speed Internet access to their user base. LTE defines a number of downlink (DL) physical channels classified as transport or control channels to carry information blocks received from the medium access control (MAC) and higher layers. LTE also defines the number of physical layer channels for the uplink (UL).

[0005] For example, LTE defines a physical downlink shared channel (PDSCH) as a DL transport channel. PDSCH is the primary data bearing channel allocated to users on a dynamic and opportunistic basis. PDSCH carries data in a transport block (TB) corresponding to a MAC protocol data unit (PDU), which is passed from the MAC layer to the physical (PHY) layer once per transmission time interval (TTI). PDSCH is also used to transmit broadcast information such as system information blocks (SIBs) and paging messages.

[0006] As another example, LTE defines the physical downlink control channel (PDCCH) as a DL control channel that carries the resource allocation of the UE contained in the downlink control information (DCI) message. Multiple PDCCHs can be transmitted in the same subframe using control channel elements (CCEs), each of which is nine groups of four resource elements called resource element groups (REGs). PDCCH uses quadrature phase shift keying (QPSK) modulation, where four QPSK symbols are mapped to each REG. In addition, depending on the channel conditions, the UE can use 1, 2, 4, or 8 CCEs to ensure sufficient robustness.

[0007] In addition, LTE defines the physical uplink shared channel (PUSCH) as a UL channel shared by all devices (user equipment, UE) in a radio cell to transmit user data to the network. The scheduling of all UEs is under the control of the LTE base station (enhanced Node B or eNB). The eNB uses an uplink scheduling grant (DCI format 0) to inform the UE of the resource block (RB) allocation and the modulation and coding scheme to be used. PUSCH typically supports QPSK and orthogonal amplitude modulation (QAM). In addition to user data, PUSCH also carries any control information required to decode the information, such as a transport format indicator and multiple-input multiple-output (MIMO) parameters. The control data is multiplexed with the information data before the digital Fourier transform (DFT) is unfolded.

[0008] The next telecommunication standard proposed to go beyond the current International Mobile Telecommunications Advanced (IMT-Advanced) standard is referred to as the 5th Generation Mobile Network or 5th Generation Wireless System, or 5G for short (also referred to as 5G-NR for 5G New Radio, also referred to as NR for short). Compared to the current LTE standard, 5G-NR proposes higher capacity for a higher density of mobile broadband users while supporting device-to-device ultra-reliable and massive machine communications, as well as lower latency and lower battery consumption. In addition, the 5G-NR standard may allow for less restrictive UE scheduling than the current LTE standard. Therefore, efforts are ongoing to develop 5G-NR to take advantage of less restrictive UE scheduling in order to further exploit power saving opportunities. Summary of the invention

[0009] Embodiments relate to apparatus, systems, and methods for improving dual registration in fifth generation (5G) New Radio (NR) networks, including notification procedure enhancements, dual registration enhancements, and paging enhancements.

[0010] In some embodiments, a user equipment device (UE) registered on a first access network and a second access network may be configured to perform a method for determining that a first periodic paging window of the first access network overlaps with a second periodic paging window of the second access network, wherein the overlap causes the UE to miss at least one page on one of the first access network or the second access network and perform a conflict avoidance procedure to adjust the timing of the second periodic paging window relative to the first periodic paging window, thereby allowing the UE to receive pages on both the first access network and the second access network. In some embodiments, the conflict avoidance procedure may include transmitting a NAS uplink message to one of the core networks to request a change in one of the periodic paging windows; negotiating a paging offset with one of the access networks, including transmitting a NAS registration uplink message indicating the paging offset, or receiving a NAS notification message from one of the access networks indicating pending downlink information over a non-cellular (e.g., non-3GPP) access (e.g., such as Wi-Fi). In some embodiments, the change in the periodic paging window may at least partially reduce the overlap between the periodic paging windows, thereby allowing the UE to receive pages from both access networks. In some embodiments, the paging offset may shift the paging windows relative to each other such that the overlap between periodic paging windows is at least partially reduced, thereby allowing the UE to receive pages from both access networks.

[0011] In some embodiments, a user equipment device (UE) registered on a first cellular access network and a second cellular access network and simultaneously registered to a common core network via a non-cellular access may be configured to perform a method for operating in a dual registration mode with a mobile initiated connection only (MICO) mode enabled. The UE may be configured to perform a method including registering on a first cellular access network, indicating that the UE supports dual registration mode and requesting MICO mode for the first cellular access network, registering on a second cellular access network, communicating on the second cellular access network, determining that a quality of service requirement of an application is higher than the quality of service currently available via the non-cellular access network, and initiating a connection on the first cellular access network to improve the available quality of service to meet the quality of service requirement of the application. In some embodiments, the first cellular access network may be a 5G NR access network, the second cellular access network may be a 4G access network, and the non-cellular access may be a non-3GPP access network connected to a common core network, which may be a fifth generation (5G) core network.

[0012] In some embodiments, a network node, a network entity, or a functional entity included within the network entity and / or the network node may be configured to perform a method for determining that the network has pending downlink information for a UE and, in response to determining that the UE is in a connected state (e.g., a CM connected state), in response to determining that the UE is dual registered or that the UE is not dual registered but has missed a previous paging on a 3GPP (e.g., cellular) access, transmitting a NAS notification message over a non-3GPP access, wherein the NAS notification message indicates that the access type is 3GPP.

[0013] The techniques described herein may be implemented in and / or used with a number of different types of devices, including, but not limited to, any of cellular telephones, tablet computers, wearable computing devices, portable media players, and a variety of other computing devices.

[0014] This disclosure is intended to provide a brief overview of some of the topics described in this document. Therefore, it should be understood that the above features are only examples and should not be interpreted as narrowing the scope or essence of the topics described herein in any way. Other features, aspects and advantages of the topics described herein will become apparent through the following detailed description, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0016] Figure 1A An exemplary wireless communication system is shown in accordance with some embodiments.

[0017] Figure 1B Examples of base stations (BSs) and access points in communication with user equipment (UE) devices are shown in accordance with some embodiments.

[0018] Figure 2 An exemplary simplified block diagram of a WLAN access point (AP) is shown in accordance with some embodiments.

[0019] Figure 3 An example block diagram of a UE according to some embodiments is shown.

[0020] Figure 4 An example block diagram of a BS according to some embodiments is shown.

[0021] Figure 5 An example block diagram of cellular communication circuitry is shown according to some embodiments.

[0022] Fig. 6AAn example of the connection between the EPC network, LTE base stations (eNBs), and 5G NR base stations (gNBs) is shown.

[0023] Figure 6B An example of a protocol stack for eNB and gNB is shown.

[0024] Fig. 7A An example of a 5G network architecture according to some embodiments is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access in the 5G CN.

[0025] Figure 7B An example of a 5G network architecture according to some embodiments is shown, which combines both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPP access in the 5G CN.

[0026] Figure 8 An example of a baseband processor architecture for a UE according to some embodiments is shown.

[0027] Fig.9A An example of a paging conflict for a dual registered UE is shown.

[0028] Fig. 9B An example of paging offset for dual registered UEs is shown according to some embodiments.

[0029] Fig.10 An example of a flow diagram of a network for determining an access type to notify a UE of pending downlink information is shown in accordance with some embodiments.

[0030] Fig.11 A block diagram illustrating an example of a method of a network for determining an access type to notify a UE of pending downlink information according to some embodiments.

[0031] Fig.12 A block diagram illustrating another example of a method of a network for determining an access type to notify a UE of pending downlink information according to some embodiments.

[0032] Fig.13 A block diagram illustrating an example of a method for a UE operating in a dual registration mode according to some embodiments is shown.

[0033] Although the features described herein are susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and described in detail herein. However, it should be understood that the drawings and detailed description thereof are not intended to limit this document to the specific forms disclosed, but on the contrary, their purpose is to cover all modifications, equivalents and alternatives that fall within the spirit and scope of the subject matter as defined by the appended claims. DETAILED DESCRIPTION

[0034] the term

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

[0036] Memory medium - any of various types of non-transitory memory devices or storage devices. The term "memory medium" is intended to include installation media, such as CD-ROM, floppy disk or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, for example, hard disk drive or optical storage device; registers or other similar types of memory elements, etc. The memory medium may also include other types of non-transitory memory or combinations thereof. In addition, the memory medium may be located in the first computer system executing the program, or may be located in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term "memory medium" may include two or more memory media that may reside in different locations in different computer systems connected, for example, via a network. The memory medium may store program instructions (e.g., expressed as a computer program) that may be executed by one or more processors.

[0037] Carrier Medium—storage media as described above, and physical transmission media such as a bus, network, and / or other physical transmission media that transport signals such as electrical, electromagnetic or digital signals.

[0038] Programmable hardware elements - include various hardware devices that include multiple programmable function blocks connected via programmable interconnects. Examples include FPGAs (field programmable gate arrays), PLDs (programmable logic devices), FPOAs (field programmable object arrays), and CPLDs (complex PLDs). Programmable function blocks can vary from fine-grained (combinational logic components or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic."

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

[0040] User Equipment (UE) (or "UE device") - any of various types of computer system devices that are mobile or portable and that perform wireless communications. Examples of UE devices include mobile phones or smart phones (e.g., iPhone TM , based on Android TM phones), portable gaming devices (e.g., Nintendo DS TM , PlayStation Portable TM 、Gameboy Advance TM , iPhone TM ), laptops, wearable devices (e.g., smart watches, smart glasses), PDAs, portable Internet devices, music players, data storage devices or other handheld devices, etc. In general, the term "UE" or "UE device" can be broadly defined to cover any electronic device, computing device and / or telecommunication device (or combination of devices) that can be easily transmitted by a user and capable of wireless communication.

[0041] Base Station—The term “base station” has the full breadth of its ordinary meaning and includes at least a wireless communication station that is installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.

[0042] Processing element - refers to various elements or combinations of elements that are capable of performing functions in a device such as a user device or a cellular network device. A processing element may include, for example, a processor and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as ASICs (application specific integrated circuits), programmable hardware elements such as field programmable gate arrays (FPGAs), and any of the above combinations.

[0043] Channel - a medium used to transmit information from a sender (transmitter) to a receiver. It should be noted that since the characteristics of the term "channel" may vary according to different wireless protocols, the term "channel" used herein may be considered to be used in a manner that conforms to the standards of the type of device to which the term is used. In some standards, the channel width may be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE may support scalable channel bandwidths of 1.4 MHz to 20 MHz. In contrast, a WLAN channel may be 22 MHz wide, while a Bluetooth channel may be 1 MHz wide. Other protocols and standards may include different definitions of channels. In addition, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.

[0044] Frequency band—The term “frequency band” has the full breadth of its ordinary meaning and includes at least a segment of the spectrum (eg, radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0045] Automatic—refers to an action or operation performed by a computer system (e.g., software executed by a computer system) or a device (e.g., a circuit, a programmable hardware element, an ASIC, etc.) without the need for user input to directly specify or perform the action or operation. Thus, the term "automatic" is in contrast to a user manually performing or specifying an action, where the user provides input to directly perform the action. An automatic process may be initiated by input provided by a user, but subsequent actions performed "automatically" are not specified by the user, i.e., are not performed "manually," where the user specifies each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing in information, selecting check boxes, radio selections, etc.) is manually filling out the form, even though the computer system must update the form in response to the user action. The form may be automatically filled out by a computer system, where the computer system (e.g., software executed on the computer system) analyzes the fields of the form and fills out the form without any user input specifying the answers to the fields. As indicated above, a user may invoke automatic filling out of a form, but not participate in the actual filling out of the form (e.g., the user does not manually specify the answers to the fields but rather they are automatically completed). This specification provides various examples of operations that are automatically performed in response to actions taken by a user.

[0046] About - refers to a value that is close to a correct or exact value. For example, about can refer to a value that is within 1% to 10% of an exact (or desired) value. However, it should be noted that the actual threshold (or tolerance) may depend on the application. For example, in some embodiments, "about" 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%, etc., depending on the desires or requirements of a particular application.

[0047] Concurrency - refers to parallel execution or implementation, where tasks, processes, or programs are executed in an at least partially overlapping manner. For example, concurrency can be achieved using "strong" or strict parallelism, where tasks are executed (at least partially) in parallel on respective computing elements, or using "weak parallelism", where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).

[0048] Various components may be described as being "configured to" perform one or more tasks. In such environments, "configured to" is a broad statement that generally means "having a structure" that performs one or more tasks during operation. Thus, even when the component is not currently performing the task, the component can be configured to perform the task (e.g., a set of electrical conductors can be configured to electrically connect a module to another module even when the two modules are not connected). In some environments, "configured to" can be a broad statement that generally means "having a circuit" that performs one or more tasks during operation. Thus, even when the component is not currently turned on, the component can be configured to perform the task. Typically, the circuitry that forms the structure corresponding to "configured to" may include hardware circuits.

[0049] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase "configured to". The description of a component being configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. §112(f) interpretation of that component.

[0050] Figure 1A and Figure 1B -Communication system

[0051] Figure 1A A simplified exemplary wireless communication system according to some embodiments is shown. Note that the system of FIG. 1 is only one example of a possible system, and features of the present disclosure may be implemented in any of a variety of systems as desired.

[0052] As shown, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipment 106A, user equipment 106B, etc. to user equipment 106N through a transmission medium. Each of the user equipments may be referred to as a "user device" (UE) in this document. Therefore, user equipment 106 is referred to as a UE or UE device.

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

[0054] The communication area (or coverage area) of a base station may be referred to as a "cell". The base station 102A and the UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), which are 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, Advanced LTE (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), and the like. Note that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as 'eNodeB' or "eNB". Note that if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as "gNodeB" or "gNB".

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

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

[0057] Thus, although base station 102A may act as a "serving cell" for UEs 106A-N as shown in FIG. 1 , each UE 106 may also be able to receive signals from (and possibly be within communication range of) one or more other cells (which may 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 able to facilitate communication between user devices and / or between user devices and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any various other granularity that provide service area sizes. For example, base stations 102A-B shown in FIG. 1 may be macro cells, while base station 102N may be a micro cell. Other configurations are also possible.

[0058] 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 an 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 in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

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

[0060] Figure 1B A user device 106 (e.g., one of device 106A-106N) is shown in communication with base station 102 and access point 112 according to some embodiments. UE 106 may be a device with cellular communication capabilities and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.

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

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

[0063] In some embodiments, UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate with it. As another possibility, UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used uniquely by a single wireless communication protocol. For example, UE 106 may include a shared radio component for communicating using either LTE or 5GNR (or LTE or 1xRTT, or LTE or GSM), and an independent radio component for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0064] Figure 2 -Access Point Block Diagram

[0065] Figure 2 An exemplary block diagram of an access point (AP) 112 is shown. Note that Figure 2 The AP block diagram of is only one example of a possible system. As shown, the AP 112 may include one or more processors 204 that may execute program instructions for the AP 112. The processor 204 may also be coupled (directly or indirectly) to a memory management unit (MMU) 240 or other circuit or device that may be configured to receive addresses from the processor 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).

[0066] AP 112 may include at least one network port 270. The network port 270 may be configured to couple to a wired network and provide access to the Internet for multiple devices such as UE 106. For example, network port 270 (or an additional network port) may be configured to couple to a local network, such as a home network or an enterprise network. For example, port 270 may be an Ethernet port. The local network may provide a connection to an additional network such as the Internet.

[0067] The AP 112 may include at least one antenna 234, which may be configured to function as a wireless transceiver and may be further configured to communicate with the UE 106 via the wireless communication circuit 230. The antenna 234 communicates with the wireless communication circuit 230 via a communication chain 232. The communication chain 232 may include one or more receive chains, one or more transmit chains, or both. The wireless communication circuit 230 may be configured to communicate via Wi-Fi or WLAN, such as 802.11. For example, when the AP is co-located with a base station in the case of a small cell, or in other cases where it may be desirable for the AP 112 to communicate via a variety of different wireless communication technologies, the wireless communication circuit 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including, but not limited to, 5G NR, Long Term Evolution (LTE), Advanced LTE (LTE-A), Global System for Mobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000, etc.

[0068] In some embodiments, as further described below, AP 112 may be configured to perform methods for improving dual registration in 5G NR networks, including notification procedure enhancements, dual registration enhancements, and paging enhancements as further described herein.

[0069] Figure 3 –Block diagram of UE

[0070] Figure 3 An example simplified block diagram of a communication device 106 according to some embodiments is shown. Note that Figure 3The block diagram of the communication device is only an example of a possible communication device. According to the embodiment, the communication device 106 can 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 (such as a laptop, a notebook or a portable computing device), a tablet computer and / or a combination of devices, in addition to other devices. As shown in the figure, the communication device 106 may include a group of components 300 configured to perform core functions. For example, the group of components may be implemented as a system on a chip (SOC), which may include parts for various purposes. Alternatively, the group of components 300 may be implemented as a separate component or a group of components for various purposes. This group of components 300 may be (e.g., communicatively; directly or indirectly) coupled to various other circuits of the communication device 106.

[0071] For example, the communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as a connector I / F 320 (e.g., for connecting to a computer system; a docking station; a charging station; an input device such as a microphone, a camera, a keyboard; an output device such as a speaker; etc.), a display 360 that may be integrated with the communication device 106 or external to the communication device, and cellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc., and short-range to medium-range wireless communication circuitry 329 (e.g., Bluetooth TM In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0072] Cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as, for example, antennas 335 and 336, as shown. Short-range to medium-range wireless communication circuitry 329 may also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as, for example, antennas 337 and 338, as shown. Alternatively, short-range to medium-range wireless communication circuitry 329 may be (e.g., communicatively; directly or indirectly) coupled to antennas 335 and 336 in addition to or in lieu of being (e.g., communicatively; directly or indirectly) coupled to antennas 337 and 338. Short-range to medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 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.

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

[0074] 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 various elements such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0075] The communication device 106 may also include one or more smart cards 345 having SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more Universal Integrated Circuit Cards) 345 .

[0076] As shown, the SOC 300 may include a processor (one or more) 302, which may execute program instructions for the communication device 106, and a display circuit 304, which may perform graphics processing and provide display signals to a display 360. The one or more processors 302 may also be coupled to a memory management unit (MMU) 340 (which may be configured to receive addresses from the one or more processors 302 and convert those addresses into locations in a memory (e.g., a memory 306, a read-only memory (ROM) 350, a NAND flash memory 310)) and / or to other circuits or devices (such as the display circuit 304, the short-range wireless communication circuit 229, the cellular communication circuit 330, the connector I / F 320, and / or the display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the one or more processors 302.

[0077] As described above, the communication device 106 may be configured to communicate using wireless and / or wired communication circuits. The communication device 106 may be configured to perform methods for improving dual registration in 5G NR networks, including notification procedure enhancements, dual registration enhancements, and paging enhancements as further described herein.

[0078] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features of the communication device 106 to transmit a scheduling profile for power saving to the network. The processor 302 of the communication device 106 may be configured to implement part or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 302 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), in combination with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, the processor 302 of the communication device 106 may be configured to implement part or all of the features described herein.

[0079] Furthermore, as described herein, processor 302 may include one or more processing elements. Thus, processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of processor 302. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 302.

[0080] In addition, as described herein, both the cellular communication circuit 330 and the short-range wireless communication circuit 329 may include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 330, and similarly, one or more processing elements may be included in the short-range wireless communication circuit 329. Thus, the cellular communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 330. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 330. Similarly, the short-range wireless communication circuit 329 may include one or more ICs configured to perform the functions of the short-range wireless communication circuit 329. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-range wireless communication circuit 329.

[0081] Figure 4 – Block diagram of a base station

[0082] Figure 4An example block diagram of a base station 102 according to some embodiments is shown. Note that Figure 4 The base station of is only one example of a possible base station. As shown, the base station 102 may include one or more processors 404 that may execute program instructions for the base station 102. The one or more processors 404 may also be coupled to a memory management unit (MMU) 440 (which may be configured to receive addresses from the one or more processors 404 and convert these addresses to locations in memory (e.g., memory 460 and read-only memory (ROM) 450)) or other circuits or devices.

[0083] Base station 102 may include at least one network port 470. Network port 470 may be configured to couple to a telephone network and provide access to the network as described above in FIG. Figure 2 Multiple devices of the telephone network described in, such as UE device 106.

[0084] The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as the UE device 106. In some cases, the network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0085] 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 an NR Core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0086] The base station 102 may include at least one antenna 434 and possibly multiple antennas. At least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with the UE device 106 via the radio component 430. The antenna 434 communicates with the radio component 430 via a communication chain 432. The communication chain 432 may be a receive chain, a transmit chain, or both. The radio component 430 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, and the like.

[0087] Base station 102 may be configured to perform wireless communications using multiple wireless communication standards. In some cases, base station 102 may include multiple radio components that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communications according to LTE and a 5G NR radio component for performing communications according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component that can perform communications according to any one 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.).

[0088] As further described later herein, BS 102 may include hardware and software components for implementing or supporting implementations of the features described herein. The processor 404 of base station 102 may be configured to implement or support some or all of the implementations of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 404 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 thereto), in combination with one or more of the other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of BS 102 may be configured to implement or support some or all of the implementations of the features described herein.

[0089] In addition, as described herein, the one or more processors 404 may be composed of one or more processing elements. In other words, the one or more processing elements may be included in the one or more processors 404. Therefore, the one or more processors 404 may include one or more integrated circuits (ICs) configured to perform the functions of the one or more processors 404. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the one or more processors 404.

[0090] Additionally, as described herein, radio 430 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 430. Thus, radio 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio 430. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 430.

[0091] Figure 5 : Block diagram of a cellular communication circuit

[0092] Figure 5 An example simplified block diagram of a cellular communication circuit according to some embodiments is shown. Note that Figure 5 The block diagram of the cellular communication circuit of is only one example of one possible cellular communication circuit. According to an embodiment, the cellular communication circuit 330 may be included in a communication device such as the communication device 106 described above. As described above, the 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 computer, and / or a combination of devices, among other devices.

[0093] Cellular communication circuitry 330 may be (eg, communicatively; directly or indirectly) coupled to one or more antennas, such as ( Figure 3 In some embodiments, the cellular communication circuit 330 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, Figure 5 As shown, cellular communication circuitry 330 may include modem 510 and modem 520. Modem 510 may be configured for communication according to a first RAT, such as, for example, LTE or LTE-A, and modem 520 may be configured for communication according to a second RAT, such as, for example, 5G NR.

[0094] As shown, the modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuits for transmitting and receiving radio signals. For example, the RF front end 530 may include a receiving circuit (RX) 532 and a transmitting circuit (TX) 534. In some embodiments, the receiving circuit 532 may communicate with a downlink (DL) front end 550, which may include circuits for receiving radio signals via an antenna 335a.

[0095] Similarly, the modem 520 may include one or more processors 522 and a memory 526 in communication with the processor 522. The modem 520 may communicate with the RF front end 540. The RF front end 540 may include circuits for transmitting and receiving radio signals. For example, the RF front end 540 may include a receiving circuit 542 and a transmitting circuit 544. In some embodiments, the receiving circuit 542 may communicate with the DL front end 560, which may include circuits for receiving radio signals via the antenna 335b.

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

[0097] In some embodiments, the cellular communication circuit 330 may be configured to perform methods for improving dual registration in a 5G NR network, including notification procedure enhancements, dual registration enhancements, and paging enhancements as further described herein.

[0098] As described herein, the modem 510 may include hardware and software components for implementing the above-described features or for time-division multiplexing UL data for NSA NR operations and various other techniques described herein. The processor 512 may be configured to implement part or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the 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), in combination with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, the processor 512 may be configured to implement part or all of the features described herein.

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

[0100] As described herein, the modem 520 may include hardware and software components intended to implement the above-described features for transmitting a power-saving scheduling profile to a network, as well as various other techniques described herein. The processor 522 may be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the 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), in combination with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336, the processor 522 may be configured to implement some or all of the features described herein.

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

[0102] 5G NR architecture with LTE

[0103] In some implementations, fifth generation (5G) wireless communications will initially be deployed in parallel with current wireless communications standards (e.g., LTE). For example, dual connectivity between LTE and 5G New Radio (5G NR or NR) has been specified as part of the initial deployment of NR. Fig. 6A -B, the evolved packet core (EPC) network 600 may continue to communicate with the current LTE base station (e.g., eNB 602). In addition, the eNB 602 may communicate with the 5G NR base station (e.g., gNB 604), and data may be transferred between the EPC network 600 and the gNB 604. Thus, the EPC network 600 may be used (or reused), and the gNB 604 may serve as additional capacity for the UE, for example, to provide increased downlink throughput for the UE. In other words, LTE may be used for control plane signaling, and NR may be used for user plane signaling. Thus, LTE may be used to establish a connection with the network, and NR may be used for data services.

[0104] Figure 6B The proposed protocol stack for the eNB 602 and the gNB 604 is shown. As shown, the eNB 602 may include a medium access control (MAC) layer 632 that interfaces with the radio link control (RLC) layers 622a-b. The RLC layer 622a may also interface with the packet data convergence protocol (PDCP) layer 612a, and the RLC layer 622b may interface with the PDCP layer 612b. Similar to the dual connectivity specified in LTE-Advanced Release 12, the PDCP layer 612a may interface with the EPC network 600 via a master cell group (MCG) bearer, while the PDCP layer 612b may interface with the EPC network 600 via a separate bearer.

[0105] In addition, as shown, the gNB 604 may include a MAC layer 634 that interfaces with the RLC layers 624a-b. The RLC layer 624a may interface with the PDCP layer 612b of the eNB 602 via an X2 interface for information exchange and / or coordination (e.g., scheduling UEs) between the eNB 602 and the gNB 604. In addition, the RLC layer 624b may interface with the PDCP layer 614. Similar to the dual connectivity specified in Advanced LTE Release 12, the PDCP layer 614 may interface with the EPC network 600 via a secondary cell group (SCG) bearer. Thus, the eNB 602 may be considered a master node (MeNB) and the gNB 604 may be considered a secondary node (SgNB). In some cases, the UE may be required to maintain a connection with both the MeNB and the SgNB. In such a case, the MeNB may be used to maintain a radio resource control (RRC) connection with the EPC, while the SgNB may be used for capacity (e.g., additional downlink and / or uplink throughput).

[0106] 5G Core Network Architecture—Interworking with Wi-Fi

[0107] In some embodiments, the 5G core network (CN) can be accessed via (or through) a cellular connection / interface (e.g., via a 3GPP communication architecture / protocol) and a non-cellular connection / interface (e.g., a non-3GPP access architecture / protocol such as a Wi-Fi connection). Fig. 7AAn example of a 5G network architecture according to some embodiments is shown, which combines both 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access in 5G CN. As shown, a user device (e.g., UE 106) can access 5G CN through both a radio access network (RAN, such as a gNB or base station 604) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to a non-3GPP interworking function (N3IWF) 702 network entity. N3IWF may include a connection to a core access and mobility management function (AMF) 704 of 5G CN. AMF 704 may include an instance of a 5G mobility management (5G MM) function associated with UE 106. In addition, RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, 5G CN can support unified authentication on both connections and allow UE 106 access to be registered simultaneously via gNB 604 and AP 112. As shown, the AMF 704 may include one or more functional entities associated with the 5G CN (e.g., a network slice selection function (NSSF) 720, a short message service function (SMSF) 722, an application function (AF) 724, a unified data management (UDM) 726, a policy control function (PCF) 728, and / or an authentication server function (AUSF) 730). Note that these functional entities may also be supported by the session management function (SMF) 706a and SMF 706b of the 5G CN. The AMF 706 may be connected to (or communicate with) the SMF 706a. In addition, the gNB 604 may communicate with (or be connected to) a user plane function (UPF) 708a, which may also communicate with the SMF 706a. Similarly, the N3IWF 702 may communicate with the UPF 708b, which may also communicate with the SMF 706b. Both UPFs may communicate with data networks (eg, DNs 710a and 710b) and / or the Internet 700 and the IMS core network 710.

[0108] Figure 7BAn example of a 5G network architecture according to some embodiments is shown, which combines dual 3GPP (e.g., LTE and 5GNR) access and non-3GPP access to 5G CN. As shown, a user device (e.g., UE 106) can access 5G CN through both a radio access network (RAN, such as gNB or base station 604 or eNB or base station 602) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to the N3IWF 702 network entity. N3IWF may include a connection to the AMF 704 of the 5G CN. AMF 704 may include an instance of a 5G MM function associated with UE 106. In addition, the RAN (e.g., gNB 604) may also have a connection to AMF 704. Therefore, 5G CN can support unified authentication on two connections and allow UE 106 access to be registered simultaneously via both gNB 604 and AP 112. In addition, 5G CN can support dual registration of UE on both traditional networks (e.g., LTE via base station 602) and 5G networks (e.g., via base station 604). As shown, base station 602 can have connections to mobility management entity (MME) 742 and service gateway (SGW) 744. MME 742 can have connections to both SGW 744 and AMF 704. In addition, SGW 744 can have connections to both SMF 706a and UPF708a. As shown, AMF 704 can include one or more functional entities associated with 5G CN (e.g., NSSF 720, SMSF 722, AF 724, UDM 726, PCF 728 and / or AUSF 730). It should be noted that UDM 726 can also include home subscriber server (HSS) functions, and PCF can also include policy and charging rules functions (PCRF). It should also be noted that these functional entities can also be supported by SMF 706a and SMF 706b of 5G CN. AMF 706 can be connected to (or communicate with) SMF 706a. In addition, gNB 604 can communicate with (or be connected to) UPF 708a, which can also communicate with SMF 706a. Similarly, N3IWF 702 can communicate with UPF 708b, which can also communicate with SMF 706b. Both UPFs can communicate with data networks (e.g., DN 710a and 710b) and / or the Internet 700 and IMS core network 710.

[0109] Note that in various embodiments, one or more of the above-mentioned network entities may be configured to perform methods for improving dual registration in 5G NR networks, including, for example, notification procedure enhancements, dual registration enhancements, and paging enhancements as further described herein.

[0110] Figure 8 An example of a baseband processor architecture for a UE (e.g., UE 106) according to some embodiments is shown. As described above, Figure 8 The baseband processor architecture 800 described in the figure can be implemented on one or more radio components (e.g., the radio components 329 and / or 330 described above) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access layer 810 may include a 5G NAS 820 and a traditional NAS 850. The traditional NAS 850 may include a communication connection with a traditional access layer (AS) 870. The 5G NAS 820 may include a communication connection with both a 5G AS 840 and a non-3GPP AS 830 (e.g., such as a Wi-Fi AS 832). The 5G NAS 820 may include functional entities associated with two access layers. Therefore, the 5G NAS 820 may include multiple 5G MM entities 826 and 828 and 5G session management (SM) entities 822 and 824. The legacy NAS 850 may include functional entities such as a short message service (SMS) entity 852, an evolved packet system (EPS) session management (ESM) entity 854, a session management (SM) entity 856, an EPS mobility management (EMM) entity 858, and a mobility management (MM) / GPRS mobility management (GMM) entity 860. In addition, the legacy AS 870 may include functional entities such as an LTE AS 872, a UMTS AS 874, and / or a GSM / GPRS AS 876.

[0111] Thus, the baseband processor architecture 800 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access). Note that, as shown, 5G MM can maintain a separate connection management and registration management state machine for each connection. In addition, a device (e.g., UE 106) can register to a single PLMN (e.g., 5G CN) using 5G cellular access as well as non-cellular access. In addition, a device can be in a connected state in one access and in an idle state in another access, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0112] It should be noted that in various embodiments, one or more of the above-mentioned functional entities of the 5G NAS and / or 5G AS may be configured to perform methods for improving dual registration in 5G NR networks, including, for example, notification procedure enhancements, dual registration enhancements, and paging enhancements as further described herein.

[0113] 5G NR Dual Registration Mode

[0114] In some embodiments, a device may independently register with both a 4G network (e.g., such as an Evolved Packet Core (EPC) network) and a 5G network, and maintain registration status for both the 4G network and the 5G network on a single public land mobile network (PLMN). When the interworking bit (e.g., IWK N26) in the 5G network feature support information element (IE) indicates in a registration accept message (e.g., a network access layer (NAS) message) that the network supports dual registration mode (e.g., the IE is set to "interworking without N26 support"), a device supporting dual registration mode may operate in dual registration mode. In addition, the device may perform periodic registration updates on both networks to maintain registration status on each network. In addition, the device may move any (and / or all) PDUs from one network (or technology) to another at any time, and the networks may maintain IP continuity of the PDUs. In addition, the device may maintain independent security contexts for each network.

[0115] In some implementations, dual registration mode can be used to compensate for sporadic 5G network availability. For example, the initial 5G network deployment may not have as much coverage (or availability) as the existing 4G network. In addition, the initial 5G network deployment may not support voice (e.g., packet-switched voice communications, such as voice over NR (VoNR)) over the IP Multimedia Subsystem (IMS), but can still be trusted to increase downlink speeds and address downlink capacity issues. Therefore, in these cases, a device operating in dual registration mode can use the 4G network for mobile originating / mobile called (MO / MT) voice call purposes and the 5G network for uplink and downlink data transmission purposes. In addition, in the case of sporadic 5G network availability, when the device loses 5G coverage, the device can quickly (or immediately) move the PDU to the 4G network with minimal delay because the 4G network already has the context of the device. In addition, switching delays can also be reduced for similar reasons.

[0116] However, in idle mode, the device may be required to listen to paging on both access networks by waking up at an appropriate discontinuous reception (DRX) cycle specified by the network. In other words, the device may be required to tune the antenna to monitor paging at regular intervals. Therefore, as discussed further below, due to paging conflicts (or overlaps) between access networks, the device may miss paging from one of the access networks. In addition, when a voice call (MO or MT) occurs via a 4G network, the device needs to notify the 5G network by sending a service request message. Similarly, if the device needs to move completely to one of the access networks (e.g., a 4G dedicated connection or a 5G dedicated connection), the device needs to send an extended service request to access the network that has lost connection. Note that once the device has moved to a dedicated connection, the device may need to perform a registration process on another access network to restore dual registration mode.

[0117] Paging conflict avoidance

[0118] In some implementations, a device operating in 5G NR dual registration mode (e.g., registered on both a 4G network and a 5G network) may miss mobile station called (MT) paging when the discontinuous reception (DRX) cycles of these networks collide (or overlap). For example, a device may be capable (or operable) in single radio mode while also being in 5G NR dual registration mode, so the overlap of the DRX cycles of these networks may result in missed MT paging. Such missed MT paging may result in a poor user experience.

[0119] According to 3GPP TS 24.501 version 15, if both 5GMM and EMM are enabled, a UE operating in dual registration mode and capable of N1 mode and S1 mode can independently maintain independent registration for 5GMM and EMM. In addition, no coordination is required between 5GMM and EMM, except when:

[0120] a) A UE operating in dual registration mode is only registered to N1 mode, S1 mode, or both N1 mode and S1 mode;

[0121] b) The UE decides to operate under dual registration and NAS informs the lower layers;

[0122] c) the UE is registered in N1 mode only, and then in order to register in S1 mode, the UE may use the same PLMN (with which it was registered in N1 mode) or an equivalent PLMN; or

[0123] d) The UE is registered in S1 mode only, and then in order to register in N1 mode, the UE may use the same PLMN (to which it was registered in S1 mode) or an equivalent PLMN.

[0124] Therefore, when in dual registration mode (and in non-LTE deployments), the UE may need to camp on unique frequencies simultaneously, such as on an E-UTRA cell for LTE functionality, and on a 5G NR cell for 5G System (5GS) functionality. In such a case, it is likely that the paging moments of the LTE cell and the NR cell may conflict (or overlap), causing the UE to miss MT paging for one of the systems.

[0125] For example, Fig.9A An example of a paging conflict for a device operating in a 5G NR dual registration mode is shown. As shown, the LTE timeline of the device may include a receive period 902 during a DRX cycle. In addition, the 5G NR timeline of the device may include a receive period 904 during a DRX cycle. In some implementations, the receive period 902 and the receive period 904 may overlap at a time period 906. Therefore, when the device operates in a single radio mode, the device may miss MT paging for one of the networks (e.g., LTE or 5G NR) during the overlapping time period 906.

[0126] In some embodiments, a device (e.g., such as UE 106) may specify or request a DRX cycle. For example, the UE may specify a DRX cycle (e.g., a UE-specific DRX cycle) in a network access stratum (NAS) registration uplink (UL) message. The NAS registration UL message may request the network to change the DRX cycle for the UE. In some embodiments, the UE may specify a higher DRX cycle value so that paging conflicts (or overlaps) may be avoided and / or reduced. In some embodiments, when the UE specifies a higher DRX value (e.g., compared to a default value included in a broadcast message and / or a network-specified DRX value), the network may support the UE's request and may use the DRX value indicated by the UE instead of using the DRX value specified in the broadcast message sent from the network to the UE.

[0127] In some embodiments, a device (e.g., such as UE 106) may negotiate a paging offset with the network. In some embodiments, the UE may indicate the paging offset via a NAS registration UL message. In some embodiments, the UE may specify a paging offset in a NAS registration UL message so that paging conflicts (or overlaps) between these networks may be avoided because the paging moment in one of the networks is moved by an offset to avoid conflicts. In other words, the paging offset may move the paging window of one network relative to another network. For example, the paging window of a 5G NR network may be moved (or offset) relative to the paging window of an LTE network. In other words, in some embodiments, the DRX cycle of one network may be effectively offset relative to the DRX cycle of another network.

[0128] For example, Fig. 9B A paging offset for a dual registered UE according to some embodiments is shown. As shown, the receive period 908 of the 5GNR DRX timeline may be moved (or offset) by an offset 910 to avoid overlapping (or conflicting) with the receive period 902. Such an offset may improve call performance and paging monitoring by a UE (such as UE 106). In addition, such an offset may enhance battery performance. In some embodiments, a dual registered UE may request (or specify) an offset 910 from a serving base station via signaling. For example, the serving base station may be a legacy base station, such as eNB 602. As another example, the serving base station may be a 5G NR base station, such as eNB 604. In some embodiments, the signaling may include, for example, a NAS registration UL message as described above.

[0129] In some implementations, MT paging (or other downlink notifications) may be missed due to poor radio conditions. In such implementations, the device may operate in a single registration mode or a dual registration mode. According to 3GPP TS23.501 version 15, when the connection management (CM) state of the device in the AMF is CM-IDLE for 3GPP access and CM-CONNECTED for non-3GPP access, when the network sends DL data to the device of 3GPP access by sending a paging request, the AMF may perform a network triggered service request procedure. The paging request may be sent via 3GPP access or via a NAS notification of non-3GPP. In other words, when the CM state of the device is CM-CONNECTED for non-3GPP access, a NAS notification message indicating that the access type is 3GPP may be sent via non-3GPP access. Therefore, in some embodiments, the network may use a NAS notification message via non-3GPP access to deliver downlink notifications (e.g., such as MT paging) to the UE.

[0130] Fig.10 An example of a flow diagram of a network for determining an access type to notify a UE of pending downlink information according to some embodiments is shown. In addition to other devices, Fig.10 The flow chart shown can be used in conjunction with any one of the systems or devices shown in the above figures. In various embodiments, some of the elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional elements can also be performed as needed. As shown, the flow chart can be operated as follows.

[0131] At 1002, a network (e.g., a network entity and / or a network node, such as gNB 604) may determine that there is pending downlink information for a UE, such as UE 106. The pending downlink information may be associated with voice and / or data. Delivery of the pending downlink information may be through (or via) a 5G NR network.

[0132] At 1004, the network may determine whether a non-3GPP (e.g., non-cellular) 5GMM function (or entity) associated with the UE is in a CM-CONNECTED state. In other words, the network may determine the connection state of the 5G mobility management function associated with the UE.

[0133] At 1006, in response to determining that the UE is in a connected state via non-3GPP access, the network may further determine whether the UE is dual registered (e.g., via EPC and 5GC). In other words, the network may determine the registration mode of the UE.

[0134] At 1008, in response to determining that the UE is not dual registered, the network may determine whether the UE missed a previous page. In other words, the network may determine whether the UE received and / or responded to a previous page associated with pending downlink information. In some embodiments, if the UE does not respond before a specified timeout, the network may assume that the UE missed the previous page.

[0135] At 1010, in response to determining that the UE has not missed a previous page, the network may page the UE via 3GPP (e.g., cellular) access. In some embodiments, this may typically be the case for the first paging attempt. Alternatively, at 1010, in response to determining that the UE is not in a connected state via a non-3GPP access (e.g., a non-3GPP 5GMM function associated with the UE is not in a CM connected state), the network may page the UE via a 3GPP access.

[0136] At 1012, in response to determining that the UE missed the previous paging, the network may send a NAS notification message to the UE via non-3GPP access. Alternatively, in response to determining that the UE is dual registered, the network may send a NAS notification message to the UE via non-3GPP access. The NAS notification message may indicate an access type of 3GPP.

[0137] In some implementations, section 5.3.3.4 of TS 23.501 may be altered to state that "In the event that the UE does not respond to paging on the 3GPP access for some reason, the AMF may send a NAS notification to the UE via the non-3GPP access before retrying the 3GPP access."

[0138] In some embodiments, if the network determines that it has not responded to the NAS notification message via non-3GPP access, then based on local policy, the network may retry to page the UE via 3GPP access. In some embodiments, section 4.2.3.3 of TS 25.502 may be changed to indicate that "However, if the AMF does not receive a response to the NAS notification message from the UE, then based on local policy, the AMF may retry via a paging message to the NG-RAN node via 3GPP access to reach the UE."

[0139] Fig.11 A block diagram illustrating an example of a method for determining an access type to notify a UE of pending downlink information in accordance with some embodiments. Fig.11 The method shown can be used in conjunction with any of the systems or devices shown in the above figures. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown, the method can be operated as follows.

[0140] At 1102, a UE (such as UE 106) may determine that a first periodic paging window of a first access network overlaps with a second periodic paging window of a second access network. In some embodiments, the overlap may cause the UE to miss at least one paging on one of the first access network or the second access network. In some embodiments, the UE may be registered to the first access network and the second access network. In some embodiments, the first access network may operate according to a first cellular (e.g., 3GPP) radio access technology (RAT), and the second access network may operate according to a second cellular RAT. In some embodiments, the first RAT may be a 4G 3GPP RAT and the second RAT may be a 5G 3GPP RAT. In some embodiments, the first RAT may be a 3G 3GPP RAT and the second RAT may be a 5G 3GPP RAT. In some embodiments, the first RAT may be a 5G 3GPP RAT and the second RAT may be a 4G 3GPP RAT. In some embodiments, the first RAT may be a 3G 3GPP RAT and the second RAT may be a 5G 3GPP RAT. In some embodiments, the first RAT may be a 5G 3GPP RAT and the second RAT may be a 4G 3GPP RAT. In some embodiments, the first RAT may be a 3GPP 5GNR and the second RAT may be a 3GPP LTE.

[0141] In some embodiments, the first periodic paging window may include a first discontinuous reception period specified by the first access network. In some embodiments, the second periodic paging window may include a second discontinuous reception period specified by the second access network. In some embodiments, the UE may receive a first broadcast message specifying the first discontinuous reception period from the first access network. In some embodiments, the UE may receive a second broadcast message specifying the second discontinuous reception period from the second access network.

[0142] At 1104, the UE may perform at least one conflict avoidance procedure to adjust the timing of the second periodic paging window relative to the first periodic paging window. In some embodiments, the avoidance procedure may allow the UE to receive paging on both the first access network and the second access network. In some embodiments, the conflict avoidance procedure may include any one, any combination, and / or all of the UE transmitting a request to the first access network to change the first periodic paging window, the UE transmitting a request to the second access network to change the second periodic paging window, the UE negotiating a paging offset with the first access network, the UE negotiating a paging offset with the second access network, and / or the UE receiving a NAS notification message from one of the first access network or the second access network via a non-cellular (e.g., non-3GPP) access.

[0143] In some embodiments, the request to change the first periodic paging window may be transmitted via a NAS registration uplink message. In some embodiments, the change may specify a higher discontinuous reception period value. In some embodiments, the change of the first periodic paging window may at least partially reduce the overlap between the first periodic paging window and the second periodic paging window, thereby allowing the UE to receive paging from both the first access network and the second access network.

[0144] In some embodiments, the request to change the second periodic paging window may be transmitted via a NAS registration uplink message. In some embodiments, the change may specify a higher discontinuous reception period value. In some embodiments, the change of the second periodic paging window may at least partially reduce the overlap between the first periodic paging window and the second periodic paging window, thereby allowing the UE to receive paging from both the first access network and the second access network.

[0145] In some embodiments, the negotiation may include the UE transmitting a NAS registration uplink message indicating a paging offset to the first access network. In some embodiments, the paging offset may shift the first periodic paging window relative to the second periodic paging window such that an overlap between the first periodic paging window and the second periodic paging window is at least partially reduced, thereby allowing the UE to receive pages from both the first access network and the second access network.

[0146] In some embodiments, the negotiation may include the UE transmitting a NAS registration uplink message indicating a paging offset to the second access network. In some embodiments, the paging offset may shift the second periodic paging window relative to the first periodic paging window such that an overlap between the first periodic paging window and the second periodic paging window is at least partially reduced, thereby allowing the UE to receive paging from both the first access network and the second access network.

[0147] In some implementations, the NAS notification message received from one of the first access network or the second access network may indicate that one of the first access network or the second access network has pending downlink data for the UE. In some implementations, the UE may have missed a previous paging associated with the pending downlink data.

[0148] In some embodiments, the UE may initiate a connection through a non-3GPP access network. In addition, the UE may receive a NAS notification message via a connection through a non-3GPP access network. In some embodiments, the NAS notification message may indicate a 3GPP access type. The 3GPP access type may be associated with one of the first access network or the second access network. In some embodiments, the UE may be in a radio resource control (RRC) inactive state on the indicated 3GPP access type. In some embodiments, the UE may resume an RRC connection on the indicated 3GPP access type in response to the NAS notification message.

[0149] In some embodiments, the UE may request from the first access network to operate in a mobile initiated connection only mode (MICO). In such embodiments, the first access network may operate in accordance with a 5G RAT. The UE may communicate on a second access network, which may operate in accordance with a 4G RAT. The UE may determine that the quality of service requirement of the application is higher than the quality of service currently available via the second access network. In response, the UE may initiate a connection on the first access network to improve the available quality of service to meet the quality of service requirement of the application.

[0150] In some embodiments, the UE may request from the first access network to operate in a mobile initiated connection only mode (MICO). In such embodiments, the first access network may operate in accordance with the 5G RAT. The UE may register on the first access network with the MICO mode enabled and establish a non-3GPP connection associated with the first access network. The UE may communicate on the second access network, which may operate in accordance with the 4G RAT. The UE may determine that the non-3GPP connection is no longer available and may re-register on the first access network with the MICO mode disabled.

[0151] Fig.12 A block diagram of another example of a method for determining an access type to notify a UE of pending downlink information in accordance with some embodiments. Fig.12The method shown can be used in conjunction with any of the systems or devices shown in the above figures. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown, the method can be operated as follows.

[0152] At 1202, a network node, such as base station 604, may determine that the network has pending downlink information for a UE, such as UE 106. In some embodiments, the network node may serve the UE, and the UE may be connected to the network via a first access type and a second access type. In some embodiments, the downlink information may be associated with a voice call and / or data.

[0153] At 1204, the network node may determine a connection state of the UE. In some embodiments, determining the connection state of the UE may include determining a state of a 5G mobility management function associated with the UE.

[0154] At 1206, the network node may determine that the UE is in a connected state. In addition, at 1216, the network node may determine that the UE is dual registered and / or that the UE is not dual registered but has missed a previous page on a 3GPP (e.g., cellular) access. At 1226, the network node may transmit a NAS notification indicating that the access type is 3GPP via a non-3GPP (e.g., non-cellular) access type. In some embodiments, the network node may determine that the UE has not responded to the NAS notification message, but is in a connected state and the UE may be paged via a 3GPP access type. In some embodiments, the 3GPP connection may include (or may be) a cellular connection, and the non-3GPP connection may include (or may be) a non-cellular connection. In some embodiments, the non-cellular connection may include (or may be) a Wi-Fi connection.

[0155] At 1208, the network node may determine that the UE is not in a connected state and / or that the UE is in a connected state that is not dual registered and has not missed a previous page on the 3GPP access. At 1228, the network node may page the UE by 3GPP access type. In some embodiments, the 3GPP connection may include (or may be) a cellular connection, and the non-3GPP connection may include (or may be) a non-cellular connection. In some embodiments, the non-cellular connection may include (or may be) a Wi-Fi connection.

[0156] In some embodiments, the network node may receive a request from the UE to change the periodic paging window. In some embodiments, the request may be received via a NAS registration uplink message. In some embodiments, the change may specify a higher discontinuous reception period value and may at least partially reduce the overlap between the periodic paging window of the network and the periodic paging window of another network serving the UE, thereby allowing the UE to receive paging from both networks.

[0157] In some embodiments, the network node may negotiate a paging offset with the UE. In some embodiments, the negotiation may include the network node receiving a NAS registration uplink message indicating the paging offset. In some embodiments, the paging offset may shift the periodic paging window of the network relative to the periodic paging window of another network serving the UE such that the overlap is at least partially reduced, thereby allowing the UE to receive pages from both networks.

[0158] In some embodiments, the network node may receive a request from the UE to operate in a mobile initiated connection only mode (MICO). In such embodiments, the network node may also receive a request from the UE to initiate a connection to improve the available quality of service.

[0159] In some embodiments, the network node may receive a request from the UE to operate in a mobile initiated connection only mode (MICO). In such embodiments, the network node may approve the UE's request to operate with the MICO mode enabled. The network node may receive a request from the UE to re-register with the MICO mode disabled.

[0160] RRC Inactivity to Connection Recovery

[0161] According to 3GPP TS 23.501 version 15, in some implementations, when the device is in the CM-CONNECTED state with the RRC inactive state, the device may restore the RRC connection because:

[0162] (1) Uplink data is pending;

[0163] (2) Mobile-initiated NAS signaling process;

[0164] (3) As a response to RAN paging;

[0165] (4) Notify the network that you have left the RAN notification area; or

[0166] (5) When the periodic RAN notification area update timer ends.

[0167] Therefore, in some specific implementations, the possibility of restoring the RRC connection based on receiving a NAS notification message via a non-3GPP access is not included. Therefore, the benefits of being in the RRC inactive state (this expected low-latency transition to the RRC connected state) are not realized, especially in ultra-reliable and low-latency (uRLLC) systems. Therefore, the network and the device may maintain the corresponding security context and bearer information in the RRC inactive state. In addition, as described above, one of the possible options for transitioning from the RRC inactive state to the RRC connected state is via a paging mechanism. However, the paging mechanism may have an inherent worst-case delay of the paging DRX cycle. In other words, the network may need to wait up to 1.28 seconds to page the UE, which may result in higher than acceptable delays in the uRLLC system.

[0168] Thus, in some embodiments, the AMF may determine that sending a NAS notification message via a non-3GPP access (e.g., rather than waiting for the next available paging event) helps a UE (such as UE 106) transition from an RRC inactive state to an RRC connected state more quickly (e.g., in less than a few milliseconds, compared to more than one second for a paging DRX cycle). In some embodiments, the AMF may send a NAS notification via a non-3GPP access when the UE is in a CM-CONNECTED state and has an RRC inactive state on a 3GPP access and a non-3GPP access. The NAS notification may indicate the access type as 3GPP. In some embodiments, the UE may resume the RRC connection based on receiving a NAS notification message indicating that the access type is 3GPP via a non-3GPP access. In some embodiments, section 5.3.3.2.5 of 3GPP TS 23.501 Version 15 may be updated to further indicate that the UE may resume the RRC connection due to "receiving a NAS notification message indicating that the access type is 3GPP via a non-3GPP access" and transitioning from the RRC inactive state to the RRC connected state.

[0169] Dual registration mode extension

[0170] In some specific implementations, according to 3GPP TS 23.501 version 15, when a device transitions between 5G and 4G (e.g., from 5G to 4G and / or from 4G to 5G), interworking between the evolved packet core (EPC) and the 5G core (5GC) may facilitate the movement of protocol data units (PDUs). In addition, the device may register with the 5GC of a PLMN or equivalent PLMN via 3GPP and non-3GPP accesses, and may further move PDUs from one access to another (e.g., from 3GPP to non-3GPP and / or from non-3GPP to 3GPP). In addition, the 5G device may operate in a mobile initiated connection only mode (MICO). It should be noted that the 5G device may request to use the MICO mode in a registration request message to the network. However, if the network accepts the request (e.g., via a MICO indication information element in a registration acceptance message sent from the network to the 5G device), the 5G device may only use the MICO mode.

[0171] In MICO mode, only 5G devices can initiate a radio connection with the network. In other words, the network cannot page 5G devices. However, in some specific implementations, a 5G device accessed via 3GPP in MICO mode also supports non-3GPP access, and the 5G device can be registered to a single AMF. Therefore, the device can register to the AMF as a MICO device via 3GPP access, and register to the AMF as a non-MICO device via non-3GPP access.

[0172] In some embodiments, a UE (such as UE 106 described above) may operate under a dual registration mode extension with MICO mode enabled. In such embodiments, the UE may request dual registration mode and indicate to the network or network entity (such as gNB 604) that the UE supports dual registration mode. The network may indicate support for dual registration mode via an interworking bit (e.g., IWK N26) in a 5G network feature support information element (IE) in a registration accept message. The UE may register with a 4G network and a 5G network independently, and may maintain the registration status of both networks to a common PLMN. In addition, the UE may obtain Wi-Fi through a non-3GPP access (e.g., Wi-Fi) and register with a public 5G core network (e.g., public to the 5G network). In some embodiments, the UE may move part or all of its 5G PDUs to a non-3GPP access. In some embodiments, the UE may establish multiple flows for each 5G PDU (e.g., one flow through a 3GPP access and another flow through a non-3GPP access). In some embodiments, the UE may perform periodic registration updates on two access networks (e.g., 4G and 5G) to maintain its registration status on each access network. In some embodiments, the UE may move some or all PDUs from one access technology to another at any time, and the access network may maintain IP continuity between technologies. For example, the UE may move some or all PDUs from 4G to 5G, and vice versa. As another example, the UE may move some or all PDUs from 5G-3GPP to 5G non-3GPP, and vice versa. In some embodiments, the UE may maintain independent security contexts for two access technologies (e.g., 4G and 5G).

[0173] In some embodiments, the UE may initiate registration by requesting a MICO mode for a 5G network in a 3GPP access. In such embodiments, if an application (e.g., executed on the UE) requires a higher quality of service (e.g., higher data rate (or usage) and / or lower latency) than is currently available on a 5G non-3GPP network, the UE may initiate a 5G cellular connection on the 5G network and improve the quality of service by combining the 5G 3GPP access and the flow of each data PDU on the 5G non-3GPP. In some embodiments, after serving a higher quality of service requirement, the UE and / or the network may choose to move to an IDLE state through a 5G 3GPP access while maintaining the MICO mode. In some embodiments, the UE and the 5G core network may use non-3GPP access to deliver mobile station called data, and serve low data requirement applications without 5G 3GPP cellular resources. In some embodiments, if Wi-Fi (e.g., 5G non-3GPP access) is lost, the UE may attempt to register through a 5G 3GPP access, and may re-register by disabling the MICO mode with a hysteresis timer to avoid frequent re-registration. In other words, if the UE determines that 5G non-3GPP access is not available (or is no longer currently available), the UE may re-register for 5G 3GPP access to disable MICO mode. In some embodiments, the hysteresis timer value may be selected (or determined and / or selected) as being configured to support different types of devices. Note that the method (or mechanism) is not limited to Internet data PDUs and can be easily extended to any other services and / or PDUs. In some embodiments, 5G non-3GPP access (e.g., Wi-Fi access) may be used for reachability purposes through 5G, while 5G 3GPP access may be maintained in MICO mode, thereby saving resources (e.g., the UE does not need to monitor 5G 3GPP access for paging) while maintaining the ability to improve downlink service quality as needed. In addition to avoiding tuning away from 4G access to 5G access to monitor 5G paging, this method may also avoid paging conflicts associated with dual mode operation and eliminate signaling associated with dual mode operation, such as, for example, a service request message sent to the 5G network to indicate tuning away and a registration process message for resuming data reception through the 5G network.

[0174] In some embodiments, section 5.17.3 of 3GPP TS 23.501, version 15, which includes interworking with the EPC in the presence of non-3GPP PDU sessions, may be modified to specify:

[0175] When the UE is connected to the 5GC via both 3GPP access and non-3GPP access: The UE supports dual registration mode, and the UE and AMF can optimize the power efficiency and signaling efficiency of the UE when in CM-IDLE state by activating MICO mode (see clause 5.4.1.3). When a control plane request for MT services (e.g. MT SMS) is sent, the network routes it through the EPC.

[0176] Furthermore, in some embodiments, section 5.17.2.3.3 of 3GPP TS 23.501, version 15, which includes mobility of UEs in dual registration mode, may modify Note 4 to indicate that "When the device is in MICO mode and CM-IDLE state, the network shall select EPC to deliver MT services."

[0177] Fig.13 A block diagram of an example of a method for a UE operating in a dual registration mode according to some embodiments is shown. In addition to other devices, Fig.13 The method shown can be used in conjunction with any of the systems or devices shown in the above figures. In various embodiments, some of the method elements shown can be performed concurrently in an order different from the order shown, or can be omitted. Additional method elements can also be performed as needed. As shown, the method can be operated as follows.

[0178] At 1302, a UE (such as UE 106) may request to operate in MICO mode from a first access network operating according to 5G NR.

[0179] At 1304, after registering on the first access network with the MICO mode enabled, the UE may establish a non-cellular (eg, non-3GPP) connection associated with the first access network.

[0180] At 1306, after registering on the second access network operating according to the 4G RAT, the UE may operate in a dual registration mode with MICO mode enabled.

[0181] At 1308, the UE may communicate on the second access network via a cellular (eg, 3GPP) connection to the second access network.

[0182] At 1310, the UE may determine that the quality of service requirement of the application is higher than the quality of service currently available via the non-cellular (e.g., non-3GPP) connection associated with the enabled first access network. In some embodiments, the quality of service requirement may include one of a data rate requirement and / or a delay requirement.

[0183] At 1312, the UE may initiate a cellular connection over the first access network to improve quality of service to meet the quality of service requirements of the application.

[0184] In some implementations, the UE may determine that the non-cellular connection is no longer available. In such implementations, the UE may re-register on the associated first access network with the MICO mode disabled.

[0185] In some implementations, the UE may maintain a first security context associated with a first access network and a second security context associated with a second access network.

[0186] In some implementations, the UE may determine that the quality of service requirement is no longer needed and may move (or transition) to an idle state on the first access network with the MICO mode enabled.

[0187] In some embodiments, the UE may determine that a first periodic paging window of a first access network overlaps with a second periodic paging window of a second access network. In some embodiments, the overlap may cause the UE to miss at least one paging on one of the first access network or the second access network. In some embodiments, the first periodic paging window may include a first discontinuous reception cycle specified by the first access network. In some embodiments, the second periodic paging window may include a second discontinuous reception cycle specified by the second access network. In some embodiments, the UE may receive a first broadcast message specifying a first discontinuous reception cycle from the first access network. In some embodiments, the UE may receive a second broadcast message specifying a second discontinuous reception cycle from the second access network. In response to determining the overlap, the UE may perform at least one conflict avoidance procedure to adjust the timing of the second periodic paging window relative to the first periodic paging window, thereby allowing the UE to receive paging on both the first access network and the second access network.

[0188] In some embodiments, the conflict avoidance procedure may include any one, any combination, and / or all of the UE transmitting a request to the first access network to change the first periodic paging window, the UE transmitting a request to the second access network to change the second periodic paging window, the UE negotiating a paging offset with the first access network, the UE negotiating a paging offset with the second access network, and / or the UE receiving a NAS notification message from one of the first access network or the second access network via non-3GPP access.

[0189] In some embodiments, the request to change the first periodic paging window may be transmitted via a NAS registration uplink message. In some embodiments, the change may specify a higher discontinuous reception period value. In some embodiments, the change of the first periodic paging window may at least partially reduce the overlap between the first periodic paging window and the second periodic paging window, thereby allowing the UE to receive paging from both the first access network and the second access network.

[0190] In some embodiments, the request to change the second periodic paging window may be transmitted via a NAS registration uplink message. In some embodiments, the change may specify a higher discontinuous reception period value. In some embodiments, the change of the second periodic paging window may at least partially reduce the overlap between the first periodic paging window and the second periodic paging window, thereby allowing the UE to receive paging from both the first access network and the second access network.

[0191] In some embodiments, the negotiation may include the UE transmitting a NAS registration uplink message indicating a paging offset to the first access network. In some embodiments, the paging offset may shift the first periodic paging window relative to the second periodic paging window such that an overlap between the first periodic paging window and the second periodic paging window is at least partially reduced, thereby allowing the UE to receive pages from both the first access network and the second access network.

[0192] In some embodiments, the negotiation may include the UE transmitting a NAS registration uplink message indicating a paging offset to the second access network. In some embodiments, the paging offset may shift the second periodic paging window relative to the first periodic paging window such that an overlap between the first periodic paging window and the second periodic paging window is at least partially reduced, thereby allowing the UE to receive paging from both the first access network and the second access network.

[0193] In some implementations, the NAS notification message received from one of the first access network or the second access network may indicate that one of the first access network or the second access network has pending downlink data for the UE. In some implementations, the UE may have missed a previous paging associated with the pending downlink data.

[0194] In some embodiments, the UE may initiate a connection through a non-3GPP access network and receive a NAS notification message via the connection through the non-3GPP access network. In some embodiments, the NAS notification message may indicate a 3GPP access type associated with one of the first access network or the second access network. In some embodiments, the UE may be in a radio resource control (RRC) inactive state on the indicated 3GPP access type. In some embodiments, the UE may resume the RRC connection on the indicated 3GPP access type in response to the NAS notification message.

[0195] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0196] The embodiments of the present disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.

[0197] In some embodiments, a non-transitory computer-readable storage medium may be configured such that it stores program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system is caused to perform a method, such as any one 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.

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

[0199] Although the above embodiments 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 encompass all such variations and modifications.

[0200] priority

[0201] This patent application claims the benefit of priority to U.S. Provisional Patent Application Serial No. 62 / 718,327, filed on August 13, 2018, and entitled “5G New Radio NAS Notification Procedures,” which is hereby incorporated by reference in its entirety as if fully and completely set forth herein.

Claims

1. A method for a network to determine an access type to notify a user equipment device UE of pending downlink information, comprising: The UE, determining, at the UE, that a first paging window of a first 3GPP network overlaps with a second paging window of a second 3GPP network, wherein the UE is registered to the first 3GPP network and the second 3GPP network; and In response to determining that the first paging window overlaps with the second paging window, at least one conflict avoidance procedure is performed to adjust the timing of the second paging window to allow the UE to receive paging on both the first 3GPP network and the second 3GPP network, wherein the conflict avoidance procedure includes transmitting, by the UE, a non-access stratum (NAS) request message to adjust the timing of the second paging window.

2. The method according to claim 1, in, The NAS message includes an indication of an offset for adjusting the timing of the second paging window.

3. The method according to claim 1, wherein the first 3GPP network is a fourth generation 4G 3GPP Radio Access Network RAN ​​and the second 3GPP network is a fifth generation 5G 3GPP RAN; or wherein the first 3GPP network is a 5G 3GPP RAN and the second 3GPP network is a 4G 3GPP RAN; or wherein the first 3GPP network is a 3GPP Long Term Evolution (LTE) RAN and the second 3GPP network is a 3GPP Fifth Generation New Radio (5G NR) RAN; or The first 3GPP network is 3GPP 5G NR RAN and the second 3GPP network is LTE RAN.

4. The method according to claim 1, Wherein the overlap causes the UE to miss at least one page on one of the first 3GPP network and the second 3GPP network.

5. The method of claim 1, further comprising: The UE, Initiate a connection via a non-cellular access network; receiving a NAS notification message via the connection through the non-cellular access network, wherein the NAS notification message indicates a 3GPP access type, wherein the 3GPP access type is associated with one of a first 3GPP network and a second 3GPP network, and wherein the UE is in a radio resource control (RRC) inactive state on the indicated 3GPP access type; as well as Resume the RRC connection on the indicated 3GPP access type in response to the NAS notification message.

6. The method of claim 1, further comprising: The UE, requesting from a first 3GPP network to operate in a mobile originated connection only mode MICO, wherein the first 3GPP network operates according to a fifth generation 5G radio access technology RAT; communicating over a second 3GPP network, wherein the second 3GPP network operates according to a fourth generation (4G) RAT; determining that a quality of service requirement of the application is higher than a quality of service currently available via the second 3GPP network; and A connection is initiated on the first 3GPP network to improve the available quality of service to meet the quality of service requirements of the application.

7. The method of claim 1, further comprising: The UE, Requesting a first 3GPP network to operate in a mobile originated connection only mode MICO, wherein the first 3GPP network operates according to a fifth generation 5G radio access technology RAT; Registering on the first 3GPP network with MICO mode enabled; establishing a non-3GPP connection associated with the first 3GPP network; communicating over a second 3GPP network operating in accordance with a fourth generation 4G RAT; Determining that the non-3GPP connection is no longer available; and Re-register on the first 3GPP network with MICO mode disabled.

8. The method according to claim 1, The first paging window includes a first discontinuous reception cycle specified by the first 3GPP network, and the second paging window includes a second discontinuous reception cycle specified by the second 3GPP network.

9. A user equipment device UE, comprising: at least one antenna; at least one radio device, wherein the at least one radio device is configured to perform cellular communications using at least one cellular radio access technology (RAT); and one or more processors coupled to the at least one radio, wherein the one or more processors and the at least one radio are configured to perform voice and / or data communications; The one or more processors are configured to cause the UE to perform the method according to any one of claims 1 to 8.

10. A non-transitory computer-readable storage medium storing instructions, wherein the instructions can be executed by a processing circuit of a user equipment device UE to perform the method according to any one of claims 1 to 8.

Images