Reassignment of Fifth Generation (5G) Globally Unique Temporary Identity (GUTI) for Cellular Internet of Things (CIOT)

Abstract

A wireless communication system and method are provided related to the reallocation of a globally unique temporary identifier (GUTI) for cellular Internet of Things (CIoT). A user equipment (UE) receives (1110) a paging message associated with an early data transmission (MT-EDT) terminated by a mobile station from the network. In response to the paging, the UE sends (1120) a data request to the network. The UE receives (1130) a message from the network in response to the data request, the message including at least one of a globally unique temporary identifier (GUTI) and a data or connection release indication associated with the paging.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Patent Application No. 16 / 948,506, filed on September 21, 2020, and U.S. Provisional Patent Application No. 62 / 911,202, filed on October 4, 2019, both of which are incorporated herein by reference in their entirety as if fully set forth below and for all applicable purposes. Technical Field

[0003] The present disclosure is directed to wireless communication systems and methods. Certain aspects may enable and provide techniques for global unique temporary identity (GUTI) reallocation (eg, in a cellular Internet of Things (CIoT) network). Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multiple-access communication system may include multiple base stations (BSs), each of which simultaneously supports communication for multiple communication devices, which may otherwise be referred to as user equipment (UE).

[0005] To meet the growing demand for expanded mobile broadband connections, wireless communication technology is evolving from Long Term Evolution (LTE) technology to the next generation New Radio (NR) technology, which may be referred to as the fifth generation (5G). For example, NR is designed to provide lower latency, higher bandwidth or higher throughput, and higher reliability compared to LTE. NR is designed to operate over a wide range of spectrum bands, for example, from low frequency bands below about 1 gigahertz (GHz) and mid-frequency bands from about 1 GHz to about 6 GHz, to high frequency bands such as millimeter wave (mmWave). NR is also designed to operate across different spectrum types, from licensed spectrum to unlicensed spectrum and shared spectrum. In addition, NR or 5G is designed to improve UE identity privacy.

[0006] When a UE subscribes to a network, the network may provide a Subscription Permanent Identifier (SUPI) to the UE. During initial network registration, the network may authenticate the UE based on the SUPI. The UE may encrypt the SUPI using the public key of the home public land mobile network (PLMN) before transmitting it over the air. Upon successful authentication, the network may assign a GUTI to the UE. As long as the UE is registered with the network, the UE may use the GUTI to identify itself to the network in subsequent communications. One advantage of using the GUTI for UE identification is that the GUTI may uniquely identify the UE in the network without the UE sending the SUPI over the air, and may therefore improve UE identity privacy. To provide further UE identity protection, the network may frequently reallocate or refresh the UE GUTI. The network may define certain trigger events to refresh the UE GUTI. Summary of the invention

[0007] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This review is not a broad overview of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to provide some concepts of one or more aspects of the present disclosure in a summarized form as a prelude to a more detailed description given later.

[0008] For example, in one aspect of the present disclosure, a method of wireless communication includes: receiving, by a user equipment (UE) from a network, paging associated with mobile terminated early data transfer (MT-EDT); in response to the paging, sending, by the UE, a data request to the network; receiving, by the UE, a message in response to the data request from the network, the message including: a globally unique temporary identifier (GUTI), and at least one of data associated with the paging or a connection release indication.

[0009] In an additional aspect of the present disclosure, a method of wireless communication includes: sending, by a core network entity, a paging for a user equipment (UE) associated with a first global unique temporary identifier (GUTI) to a base station (BS); receiving, by the core network entity, a request associated with at least one of service or context recovery of the paged UE from the BS; and sending, by the core network entity, a message to the BS in response to the request, the message including: a second GUTI for the paged UE that is different from the first GUTI, and at least one of data associated with the paging or a connection release indication.

[0010] In an additional aspect of the present disclosure, a method of wireless communication includes: receiving, by a base station (BS), a data request associated with paging from a user equipment (UE); sending, by the BS, a request associated with service or context recovery of the UE to a core network in response to the data request; receiving, by the BS, a message in response to the request associated with service or context recovery of the UE from the core network, the message including a global unique temporary identifier (GUTI) and a connection release indication; and sending, by the BS, a connection release message including the GUTI to the UE.

[0011] In an additional aspect of the present disclosure, a user equipment (UE) includes a transceiver configured to: receive a paging associated with a mobile terminated early data transfer (MT-EDT) from a network; send a data request in response to the paging; and receive a message from the network in response to the data request, the message including: a globally unique temporary identifier (GUTI), and at least one of the data associated with the paging or a connection release indication.

[0012] When reviewing the following description of specific, exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, other aspects, features, and embodiments of the present invention will become apparent to those skilled in the art. Although features of the present invention may be discussed with respect to certain embodiments and drawings below, all embodiments of the present invention may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used according to the various embodiments of the present invention discussed herein. In a similar manner, although exemplary embodiments are discussed below as device, system, or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 A wireless communication network in accordance with some aspects of the present disclosure is shown.

[0014] Figure 2 is a signaling diagram illustrating a wireless network communication method according to some aspects of the present disclosure.

[0015] Figure 3 is a block diagram of a user equipment (UE) according to some aspects of the present disclosure.

[0016] Figure 4 is a block diagram of an exemplary base station (BS) according to some aspects of the present disclosure.

[0017] Figure 5 is a block diagram of an exemplary network element according to some aspects of the present disclosure.

[0018] Figure 6 is a signaling diagram illustrating a globally unique temporary identity (GUTI) reallocation method for mobile terminated (MT) early data transfer (EDT) control plane CP optimization according to some aspects of the present disclosure.

[0019] Figure 7 is a signaling diagram illustrating a GUTI reallocation method for MT-EDT CP optimization according to some aspects of the present disclosure.

[0020] Figure 8 is a signaling diagram illustrating a GUTI reallocation method for MT-EDT CP optimization according to some aspects of the present disclosure.

[0021] Fig. 9 is a signaling diagram illustrating a GUTI reallocation method for MT-EDT CP optimization according to some aspects of the present disclosure.

[0022] Fig.10 is a signaling diagram illustrating a GUTI reallocation method for MT-EDT User Plane (UP) optimization according to some aspects of the present disclosure.

[0023] Fig.11 is a flow chart of a communication method according to some aspects of the present disclosure.

[0024] Fig.12 is a flow chart of a communication method according to some aspects of the present disclosure.

[0025] Fig.13 is a flow chart of a communication method according to some aspects of the present disclosure. DETAILED DESCRIPTION

[0026] The specific embodiments described below in conjunction with the accompanying drawings are intended only as descriptions of various configurations and are not intended to represent the only configurations in which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, in order to avoid blurring such concepts, known structures and components are shown in block diagram form.

[0027] The present disclosure generally relates to wireless communication systems (also referred to as wireless communication networks). In various embodiments, the techniques and apparatuses may be used in wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, global system for mobile communications (GSM) networks, fifth generation (5G) or new radio (NR) networks, and other communication networks. As used herein, the terms "network" and "system" may be used interchangeably.

[0028] An OFDMA network may implement radio technologies such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDMA, and the like. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). In particular, Long Term Evolution (LTE) is a release of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided from an organization named "3rd Generation Partnership Project" (3GPP), and CDMA2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are either known or under development. For example, the 3rd Generation Partnership Project (3GPP) is a writing between a group of telecommunications associations that aims to define globally applicable third generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project that aims to improve the UMTS mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution of wireless technology from LTE, 4G, 5G, NR, and beyond, which uses a new and different set of radio access technologies, or radio air interfaces, to share access to the wireless spectrum between networks.

[0029] In particular, 5G networks envision a variety of deployments, spectrum, and services and devices that can be implemented using a unified OFDM-based air interface. To achieve these goals, in addition to the development of new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also being considered. 5G NR will be able to scale to provide: (1) Coverage for massive Internet of Things (IoT) with ultra-high density (e.g., ~1M nodes / km) 2), ultra-low complexity (e.g., ~10s of bits / second), ultra-low energy consumption (e.g., ~10+ years of battery life), and deep coverage with the ability to reach challenging locations; (2) coverage including mission-critical control with strong security to protect sensitive personal, financial, or confidential information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1 ms), and users with a wide range of mobility or lack of mobility; and (3) provision of enhanced mobile broadband including ultra-high capacity (e.g., ~10Tbps / km 2 ), extreme data rates (e.g., multi-Gbps rates, 100+ Mbps user experience rates), and deep perception with improved discovery and optimization.

[0030] 5G NR can be implemented to use an optimized OFDM-based waveform with a scalable digital scheme and transmission time interval (TTI); a general flexible framework to efficiently multiplex services and features with dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of the digital scheme in 5G NR (with extension of subcarrier spacing) can efficiently address the operation of various services across various spectrums and various deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, such as on bandwidths (BW) of 5, 10, 20MHz, etc., the subcarrier spacing can occur at 15 kHz. For other various outdoor and small cell coverage deployments of TDD greater than 3 GHz, the subcarrier spacing can occur at 30 kHz on 80 / 100 MHz BW. For various other indoor broadband implementations using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing may occur at 60 kHz at 160 MHz BW. Finally, for various deployments transmitting with mmWave components at 28 GHz TDD, subcarrier spacing may occur at 120 kHz at 500 MHz BW.

[0031] 5G NR's scalable digital scheme facilitates scalable TTIs for various latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmissions to start at symbol boundaries. 5G NR also envisions a self-contained integrated subframe design with UL / downlink scheduling information, data, and acknowledgments in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, and adaptive UL / downlink that can be flexibly configured on a per-cell basis to dynamically switch between UL and downlink to meet current business needs.

[0032] Various other aspects and features of the present disclosure are further described below. It should be apparent that the teachings herein can be embodied in a variety of forms, and any specific structure, function, or both disclosed herein are only representative and non-restrictive. Based on the teachings herein, it should be understood by those skilled in the art that the aspects disclosed herein can be implemented independently of any other aspects, or two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement a device or a method can be practiced. In addition, other structures, functions, or structures and functions other than or different from one or more aspects set forth herein can be used to implement such a device or practice such a method. For example, the method can be implemented as a part of a system, device, device, and / or implemented as an instruction stored on a computer-readable medium to be executed on a processor or computer. In addition, an aspect can include at least one element of a claim.

[0033] In order to provide identity privacy to subscriber user equipment (UE), the network may allocate a globally unique temporary identity (GUTI) to the UE based on the UE's subscription permanent identifier (SUPI) based on successful authentication of the UE. The network may allocate or reallocate a new GUTI to the UE from time to time based on certain triggering events. For example, the network may allocate a new GUTI to the UE upon receiving a registration request message indicating an initial registration, a mobility registration update, and / or a periodic registration update from the UE. In addition, the network may allocate a new GUTI to the UE upon receiving a service request message triggered by a paging event from the UE.

[0034] Mobile terminated early data transfer (MT-EDT) control plane (CP) and MT-EDT user plane (UP) procedures may be optimized to provide data transfer to a UE in a very short duration during a paging event, for example, with a minimum number of message exchanges between the UE and the network. MT-EDT CP refers to the transmission of data through the control plane during a paging event. MT-EDT UP refers to the transmission of data through the user plane during a paging event. In the context of a 5G core network, during the MT-EDT CP, data may be transmitted from an access and mobility management function (AMF) component in the 5G core to a serving base station (BS) of a corresponding UE. During the MT-EDT UP, data may be transmitted from a 5G core user plane function (UPF) component to a serving BS of a corresponding UE. For example, in MT-EDT CP, the UE may exchange four messages with the network (e.g., a physical random access channel (PRACH) preamble, a random access response, a radio resource control (RRC) early data request message, and an RRC early data complete message), wherein data associated with paging is carried in the RRC early data complete message. Similarly, in MT-EDT UP, the UE may exchange four messages with the network (e.g., a PRACH preamble, a random access response, an RRC connection recovery request message, and an RRC connection release message), wherein data associated with paging is carried in the RRC connection release message. Similar MT-EDT CP and / or MT-EDT UP may be applied to an evolved packet system (EPS) (i.e., a 4G network), wherein a mobility management entity (MME) replaces the AMF, and a serving gateway (S-GW) / packet data network gateway (P-GW) replaces the UPF.

[0035] GUTI reallocation is typically performed using the UE Configuration Update (UCU) procedure, where non-access stratum (NAS) messages are exchanged between the UE and the corresponding AMF. The typical UCU procedure may not be suitable for use with the MT-EDT CP or MT-EDT UP procedure to reallocate a new GUTI to the UE, as the additional UCU procedure may offset the benefits of the MT-EDT CP and MT-EDT UP optimizations.

[0036] The present application describes a mechanism for GUTI reallocation during MT-EDT CP or MT-EDT UP optimization without utilizing UCU procedures. The disclosed embodiments utilize messages in the current MT-EDT CP or MT-EDT UP to carry a new GUTI for the UE. For example, the network may include the new GUTI for the UE in an RRC Early Data Complete message or RRC Connection Release message currently being exchanged during the MT-EDT CP or MT-EDT UP. In order to provide a new GUTI to be sent via an RRC Early Data Complete message or an RRC Connection Release message, the message flow between the 5G Core AMF and the BS in the current MT-EDT CP or MT-EDT UP may be modified to include GUTI signaling.

[0037] In some aspects, during the MT-EDT CP, when the UE is paged, the UE may send an RRC Early Data Request message including a NAS Control Plane Service Request (CPSR). The serving BS may forward the NAS CPSR to the AMF serving the UE. The AMF may send a DL NAS Transfer message including a NAS Service Accept message to the serving BS, the NAS Service Accept message carrying DL data associated with the paging event and a new GUTI for the UE. The DL NAS Transfer message may include a Release Indication. The DL NAS Transfer message is a message exchanged between the BS and the AMF over the N2 interface. Therefore, the DL NAS Transfer message may be referred to as an N2 DL NAS Transfer message. The serving BS may send an RRC Early Data Complete message including a NAS Service Accept message to the paged UE, wherein the NAS Service Accept message includes data and a new GUTI. In some aspects, the AMF may additionally include a NAS Acknowledgement (ACK) request in the NAS Service Accept message to trigger the UE to send an ACK after receiving the NAS Service Accept message and the new GUTI.

[0038] In some aspects, during the MT-EDT CP, the AMF may include a NAS service accept message including data, a separate GUTI information element (IE) including a new GUTI, and a release indication in an N2 DL NAS transport message. The serving BS may send an RRC early data complete message including the NAS service accept message (carrying data) and the GUTI IE to the paged UE. In some aspects, the AMF may additionally include an ACK request in the N2 DL NAS transport message, and the BS may include the ACK request in the RRC early data complete message.

[0039] In some aspects, during the MT-EDT CP, the AMF may send a UE context release message including a GUTI IE to the serving BS instead of modifying the NAS service accept message or the DL NAS message. The UE context release message may instruct the serving BS to send a GUTI IE to the paged UE and release the RRC connection. The BS may send an RRC early data complete message carrying a NAS accept message to the UE as in the current MT-EDT CP, and then send an RRC connection release message including a GUTI IE.

[0040] In some aspects, during MT-EDT UP, when the UE is paged, the UE may send an RRC context recovery request to the serving BS. The serving BS may send a UE context recovery request to the serving AMF. The AMF may respond by sending a UE context recovery response including a GTUI IE for the paged UE. The UE context recovery response may instruct the serving BS to send a GTUI IE to the paged UE and release the connection. The UPF may forward the DL data associated with the paging to the BS via the user plane. The BS sends an RRC connection release message including the GUTI IE and the DL data to the paged UE.

[0041] Various aspects of the present disclosure may provide several benefits. For example, the inclusion of a new GUTI in the current MT-EDT CP and / or MT-EDT UP messages eliminates the need to include an additional UCU procedure in the MT-EDT CP and / or MT-EDT UP procedures. Thus, the disclosed embodiments may efficiently provide a new GUTI to a paged UE with a minimum number of messages exchanged between the UE and the network. Thus, the disclosed embodiments may retain the benefits of MT-EDT CP and / or MT-EDT UP optimization.

[0042] The disclosed embodiments are suitable for use with a fourth generation (4G) BS connected to a 5G core network, which may be referred to as an evolved Node B (eNB), and a fifth generation (5G) BS connected to a 5G core network, which may be referred to as a next generation eNB (gNB). Although the disclosed embodiments are described in the context of a 5G core network and the GUTI may be referred to as a 5G-GUTI, the disclosed embodiments may be applied to a 4G core network connected to a 4G eNB or a 5G gNB. The present invention describes in more detail the mechanisms for GUTI reallocation using the MT-EDT CP and / or MT-EDT UP procedures.

[0043] Figure 1A wireless communication network 100 is shown according to some aspects of the present disclosure. The network 100 may be a 5G network. The network 100 includes a plurality of base stations (BSs) 105 (labeled 105a, 105b, 105c, 105d, 105e, and 105f, respectively) and other network entities. The BS 105 may be a station that communicates with a UE 115 and may also be referred to as an eNB, gNB, access point, etc. Each BS 105 may provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to that particular geographic coverage area of ​​the BS 105 and / or a BS subsystem serving a coverage area, depending on the context in which the term is used.

[0044] The BS 105 may provide communication coverage for a macro cell or a small cell (e.g., a pico cell or a femto cell and / or other types of cells). A macro cell typically covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with a service subscription with a network provider. Small cells such as pico cells will typically cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription with a network provider. Small cells such as femto cells will also typically cover a relatively small geographic area (e.g., a residence) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in a home, etc.). A BS for a macro cell may be referred to as a macro BS. A BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1 In the example shown in , BS 105d and 105e may be conventional macro BSs, while BS 105a-105c may be macro BSs enabled with one of three-dimensional (3D) MIMO, full-dimensional (FD) MIMO, or massive MIMO. BS 105a-105c may utilize their higher dimensional MIMO capabilities to utilize 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. BS 105f may be a small cell BS, which may be a home node or a portable access point. BS 105 may support one or more (e.g., two, three, four, etc.) cells.

[0045] The network 100 may support synchronous or asynchronous operation. For synchronous operation, the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.

[0046] UE 115 is dispersed throughout the wireless network 100, and each UE 115 may be fixed or mobile. UE 115 may also be referred to as a terminal, a mobile station, a subscriber unit, a station, and the like. UE 115 may be a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, and the like. In one aspect, UE 115 may be a device including a universal integrated circuit card (UICC). On the other hand, UE may be a device that does not include a UICC. In some aspects, UE 115 that does not include a UICC may also be referred to as an IoT device or an Internet of Everything (IoE) device. UE 115a-115d is an example of a mobile smart phone type device that accesses the network 100. UE 115 may also be a machine that is specifically configured for connected communications (including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), and the like). UE 115e-115h are examples of various machines configured for communication to access network 100. UE 115i-115k are examples of vehicles equipped with wireless communication devices configured for communication to access network 100. UE 115 may be able to communicate with any type of BS, whether macro BS, small cell, or other. Figure 1 , lightning (e.g., communication link) indicates wireless transmission between UE 115 and serving BS 105 (which is a BS designated to serve UE 115 on downlink (DL) and / or uplink (UL)), desired transmission between BS 105, backhaul transmission between BSs, or sidelink transmission between UE 115.

[0047] In operation, BS 105a-105c may use 3D beamforming and cooperative spatial techniques (such as cooperative multi-point (CoMP) or multi-connectivity) to serve UE 115a and UE 115b. Macro BS 105d may perform backhaul communications with BS 105a-105c and small cell BS 105f. Macro BS 105d may also transmit multicast services that are subscribed to and received by UE 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts (e.g., Amber Alerts or Gray Alerts).

[0048] The BS 105 may also communicate with a core network. The core network may provide user authentication, access granting, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BSs 105 (e.g., which may be examples of gNBs or access node controllers (ANCs)) may interface with the core network via a backhaul link (e.g., NG-C, NG-U, etc.) and may perform radio configuration and scheduling to communicate with the UE 115. In various examples, the BSs 105 may communicate with each other directly or indirectly (e.g., via the core network) via a backhaul link (e.g., X1, X2, etc.) (which may be a wired or wireless communication link).

[0049] The network 100 may also support mission-critical communications with ultra-reliable and redundant links for mission-critical devices, such as UE 115e, which may be a drone. The redundant communication links with UE 115e may include links from macro BS 105d and BS 105e, and links from small cell BS 105f. Other machine type devices, such as UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device), may communicate directly with a BS (e.g., small cell BS 105f and macro BS 105e) through the network 100, or in a multi-step size configuration by communicating with another user device that relays its information to the network (e.g., UE 115f transmits temperature measurement information to smart meter UE 115g, which is then reported to the network through small cell BS 105f). The network 100 can also provide additional network efficiency through dynamic, low-latency TDD / FDD communications, such as V2V, V2X, C-V2X communications between UE 115i, 115j or 115k and other UEs 115, and / or vehicle-to-infrastructure (V2I) communications between UE 115i, 115j or 115k and BS 105.

[0050] In some implementations, the network 100 communicates using an OFDM-based waveform. An OFDM-based system can divide the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, frequencies, etc. Each subcarrier can be modulated with data. In some instances, the subcarrier spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system BW. The system BW can also be divided into subbands. In other instances, the subcarrier spacing and / or the duration of the TTI can be scalable.

[0051] In some aspects, in the network 100, the BS 105 may allocate or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions. DL refers to the transmission direction from the BS 105 to the UE 115, and UL refers to the transmission direction from the UE 115 to the BS 105. The communication may be in the form of a radio frame. The radio frame may be divided into a plurality of subframes or time slots, for example, about 10. Each time slot may be further divided into micro-time slots. In FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands. For example, each subframe includes a UL subframe in the UL frequency band and a DL subframe in the DL frequency band. In TDD mode, UL and DL transmissions using the same frequency band occur in different time periods. For example, a subset of subframes in a radio frame (e.g., DL subframes) may be used for DL ​​transmissions, and another subset of subframes in a radio frame (e.g., UL subframes) may be used for UL transmissions.

[0052] The DL subframe and the UL subframe may be further divided into several regions. For example, each DL or UL subframe may have a predefined region for transmitting reference signals, control information, and data. A reference signal is a predetermined signal that facilitates communication between the BS 105 and the UE 115. For example, the reference signal may have a specific pilot pattern or structure, wherein the pilot tone may span the operating BW or frequency band, all at a predefined time and a predefined frequency. For example, the BS 105 may send a cell-specific reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) to enable the UE 115 to estimate the DL channel. Similarly, the UE 115 may send a sounding reference signal (SRS) to enable the BS 105 to estimate the UL channel. The control information may include resource allocation and protocol control. The data may include protocol data and / or operational data. In some aspects, the BS 105 and the UE 115 may communicate using a self-contained subframe. The self-contained subframe may include a portion for DL ​​communication and a portion for UL communication. A self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a longer duration for DL ​​communications than UL communications. A UL-centric subframe may include a longer duration for UL communications than DL communications.

[0053] In some aspects, the network 100 may be an NR network deployed on a licensed spectrum. The BS 105 may send synchronization signals (e.g., including a primary synchronization signal (PSS) and a secondary synchronization signal (SSS)) in the network 100 to facilitate synchronization. The BS 105 may broadcast system information associated with the network 100 (e.g., including a master information block (MIB), remaining system information (RMSI), and other system information (OSI)) to facilitate initial network access. In some instances, the BS 105 may broadcast the PSS, SSS, and / or MIB in the form of a synchronization signal block (SSB) on a physical broadcast channel (PBCH), and may broadcast the RMSI and / or OSI on a physical downlink shared channel (PDSCH).

[0054] In some aspects, a UE 115 attempting to access the network 100 may perform an initial cell search by detecting a PSS from the BS 105. The PSS may enable synchronization of periodic timing and may indicate a physical layer identification value. The UE 115 may then receive the SSS. The SSS may enable radio frame synchronization and may provide a cell identification value, which may be combined with a physical layer identification value to identify a cell. The PSS and SSS may be located at a central portion of a carrier, respectively, or may be any suitable frequency within a carrier.

[0055] After receiving the PSS and SSS, the UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for RMSI and / or OSI. After decoding the MIB, the UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource sets (CORESET) for physical downlink control channel (PDCCH) monitoring, physical UL control channel (PUCCH), physical UL shared channel (PUSCH), power control, and SRS.

[0056] After obtaining the MIB, RMSI, and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS 105. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE 115 may send a random access preamble, and the BS 105 may respond with a random access response. The random access response (RAR) may include a detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, UL grant, temporary cell radio network temporary identifier (C-RNTI), and / or a backoff indicator. Upon receiving the random access response, the UE 115 may send a connection request to the BS 105, and the BS 105 may respond with a connection response. The connection response may indicate contention resolution. In some examples, the random access preamble, RAR, connection request, and connection response may be referred to as message 1 (MSG1), message 2 (MSG2), message 3 (MSG3), and message 4 (MSG4), respectively. In some examples, the random access procedure may be a two-step random access procedure, where the UE 115 may send a random access preamble and a connection request in a single transmission, and the BS 105 may respond by sending a random access response and a connection response in a single transmission.

[0057] After establishing the connection, the UE 115 and the BS 105 may enter a normal operation phase, in which operational data may be exchanged. For example, the BS 105 may schedule the UE 115 for UL and / or DL ​​communications. The BS 105 may send an UL and / or DL ​​scheduling grant to the UE 115 via the PDCCH. The scheduling grant may be sent in the form of DL control information (DCI). The BS 105 may send a DL communication signal (e.g., carrying data) to the UE 115 via the PDSCH according to the DL scheduling grant. The UE 115 may send an UL communication signal to the BS 105 via the PUSCH and / or PUCCH according to the UL scheduling grant.

[0058] In some aspects, after establishing a connection with BS 105, UE 115 may initiate an initial network attachment or registration process with network 100. BS 105 may coordinate with various network entities or fifth generation core (5GC) entities (e.g., AMF and UPF) to complete the network attachment process. For example, BS 105 may coordinate with network entities in 5GC to identify UE 115, authenticate UE 115, and / or authorize UE 115 to send and / or receive data in network 100. When UE 115 has no active data communication with BS 105 after network attachment, UE 115 may return to an idle state (e.g., RRC idle state). Figure 2The mechanisms for performing network attachment, registration and / or idle mode operations are described in more detail in .

[0059] Figure 2 2 is a signaling diagram illustrating a wireless network communication method 200 according to some aspects of the present disclosure. The method 200 is employed by the network 100. In particular, the method 200 is implemented by the UE 215 and the network 202 to perform initial network access and idle mode operations, and the network 202 includes a BS 205 in communication with a 5G core network 220. The network 202 may correspond to the network 100. The UE 215 may correspond to the UE 115 of the network 100. The BS 205 may correspond to the BS 105 of the network 100. In some instances, the BS 205 may be a 4G eNB. In some other instances, the BS 205 may be a 5G gNB. The 5G core network 220 may include an AMF 222 and a UPF 224. The steps of the method 200 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other appropriate components) of the core network entity implementing the AMF 222 and / or the UPF 224. As shown, method 200 includes a plurality of enumerated steps, but embodiments of method 200 may include other steps before, after, and between the enumerated steps. In some embodiments, one or more of the enumerated steps may be omitted or performed in a different order.

[0060] At step 230, UE 215 performs a random access procedure with BS 205. In this regard, UE 215 may send a physical random access channel (PRACH) preamble (MSG1) to BS 205, and BS 205 may respond with a random access response (MSG2).

[0061] At step 240, UE 215 performs an RRC connection establishment with BS 205. In this regard, UE 215 may send an RRC connection request to BS 205, and BS 205 may respond with an RRC connection establishment response.

[0062] At step 250, after establishing an RRC connection with the BS 205, the UE 215 may initiate a network attachment / registration procedure with the network 202. The BS 105 may coordinate with the 5G core network 220 to identify the UE 215, authenticate the UE 215, and / or authorize the UE 215 to send and / or receive data in the network 100. In this regard, the AMF 222 may perform authentication and / or authorization for the UE 215, and the UPF 224 may establish a bearer to transmit data for the UE 215 to the BS 205.

[0063] In some aspects, a subscription permanent identifier (SUPI) may be assigned to the UE 215. The UE 215 may encrypt the SUPI using a public key of a home public land mobile network (PLMN) before transmission over the air. The UE 215 may perform mutual authentication with the 5G core network 220 and establish NAS security with the AMF 222 (e.g., using a NAS security mode command procedure). Upon successful activation of NAS security, the AMF 222 assigns a GUTI to the UE 215. The GUTI may include a PLMN ID and a service temporary mobile user identity (S-TMSI). When the UE 215 communicates with the AMF 222, the UE 215 may then use the GUTI (or the S-TMSI of the GUTI) to identify itself.

[0064] In addition, the AMF 222 may allocate a tracking area (TA) to the UE 215. Once the network attach procedure is successful, a context is established in the AMF 222 for the UE 115. After successfully attaching to the network 202, the UE 215 may move around the current TA. For a tracking area update (TAU), the BS 205 may require the UE 215 to periodically update the location of the UE 215 to the network 202. Alternatively, the UE 215 may report the location of the UE 215 to the network 202 only when entering a new TA. The TAU allows the network 202 to quickly locate the UE 215 and page the UE 215 when an incoming data packet or call for the UE 215 is received. When the UE 215 has no active data communication with the BS 105 after network attach, the UE 215 may return to an idle mode (e.g., an RRC idle state).

[0065] At step 260, the UE 215 may perform various idle mode processes. In some aspects, the UE 215 may be configured with a sleep wake-up cycle. The UE 215 may shut down certain front-end components, baseband components, and / or network layer processing components during the sleep period to save power. The UE 215 may wake up during the wake-up period to perform idle mode processes. Some examples of idle mode processes may include cell measurement, cell monitoring, cell reselection, periodic registration, mobile registration updates, and / or operations related to paging. In some aspects, the UE 215 may perform periodic registration with the network 202 to update the status of the UE 215, or notify the network 202 of the presence of the UE 215 at specific time intervals. Upon receiving a registration request message with a periodic registration type from the UE 215, the AMF 222 may perform GUTI reallocation by generating a new GUTI for the UE 215, and notify the UE 215 of the new GUTI.

[0066] In some aspects, when the UE moves to a new TA, the UE 215 may perform a TAU procedure. The UE may send a registration request message including a mobility registration update type. Upon receiving a registration request message with a mobility registration update type from the UE 215, the AMF 222 may perform GUTI reallocation by generating a new GUTI for the UE 215 and notifying the UE 215 of the new GUTI.

[0067] In some aspects, the UE 215 may monitor a paging channel when in idle mode. When the UPF 224 receives DL data for the UE 215 when the UE 215 is in idle state, the UPF 224 may page the UE 215 via the paging channel. The UE 215 may respond to the network 202 by sending a service request. Upon receiving the service request from the UE 215, the AMF 222 may perform GUTI reallocation by generating a new GUTI for the UE 215 and notifying the UE 215 of the new GUTI. The new GUTI may be sent to the UE 215 before releasing the current NAS signaling connection.

[0068] In some aspects, the UE 215 is a low power device, such as an IoT device. When the network 202 (e.g., at the UPF 224) receives DL data for the UE 215 while the UE 215 is in idle mode, the network 202 may utilize the MT-EDT CP procedure or the MT-EDT UP procedure to reduce the wake-up time of the UE 215 to allow power to be saved at the UE 215. For example, compared to the traditional paging procedure, the MT-EDT procedure may utilize the reduced number of message exchanges between the UE 215 and the network 202 so that the UE 215 can quickly return to sleep mode. For example, upon detecting a paging from the network 202, the UE 215 may exchange MSG1, MSG2, MSG3, and MSG4 with the network BS 205, and the BS 205 may include the DL data that triggered the paging in MSG4. However, the GUTI allocation is performed using the UCU procedure, which requires additional NAS message exchanges and may therefore offset the benefits of the ET MDT CP or UP procedure.

[0069] Thus, the present disclosure provides techniques for providing a new GUTI to a UE (e.g., UE 115 and / or 215) in an MT-EDT CP procedure or an MT-EDT UP procedure without utilizing a UCU procedure. For example, an ET MDT CP procedure, an RRC Early Data Complete message (MSG4) may include DL data associated with paging and the new GUTI. Alternatively, an additional RRC Connection Release message including the new GUTI may be added to the ET MDT CP procedure. In the MT-EDT UP procedure, the RRC Connection Release message (MSG4) may include DL data associated with paging and the new GUTI. The present invention describes in more detail mechanisms for optimizing new GUTI reallocation for MT-EDTCP procedures and / or MT-EDT UP procedures.

[0070] Figure 3 300 is a block diagram of an exemplary UE 300 according to some aspects of the present disclosure. The UE 300 may be the Figure 1 As shown, UE 300 may include a processor 302, a memory 304, an MT-EDT module 308, a GUTI module 309, a transceiver 310 (which includes a modem subsystem 312 and a radio frequency (RF) unit 314), and one or more antennas 316. These elements may communicate with each other, directly or indirectly, for example, via one or more buses.

[0071] The processor 302 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 302 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such structure.

[0072] Memory 304 may include cache memory (e.g., cache memory of processor 302), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory devices, hard drives, other forms of volatile and non-volatile memory, or a combination of different types of memory. In one aspect, memory 304 includes a non-transitory computer-readable medium. Memory 304 may store instructions 306, or have instructions 306 recorded thereon. Instructions 306 may include instructions that, when executed by processor 302, cause processor 302 to perform various aspects of the present disclosure referenced herein (e.g., Figure 2 and Figure 6-11 Instructions 306 may also be referred to as program code. The program code may be used to cause the wireless communication device to perform the operations, such as by causing one or more processors (such as processor 302) to control or command the wireless communication device to do so. The terms "instructions" and "code" should be broadly interpreted to include any type of computer-readable statements. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, processes, etc. "Instructions" and "code" may include a single computer-readable statement or multiple computer-readable statements.

[0073] Each of the MT-EDT module 308 and the GUTI module 309 may be implemented via hardware, software, or a combination thereof. For example, each of the MT-EDT module 308 and the GUTI module 309 may be implemented as a processor, a circuit, and / or instructions 306 stored in the memory 304 and executed by the processor 302. In some examples, the MT-EDT module 308 and / or the GUTI module 309 may be integrated within the modem subsystem 312. For example, the MT-EDT module 308 and / or the GUTI module 309 may be implemented by a combination of software components (e.g., executed by a DSP or a general purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 312. In some examples, the UE may include the MT-EDT module 308 or the GUTI module 309. In other examples, the UE may include the MT-EDT module 308 and the GUTI module 309.

[0074] The MT-EDT module 308 may be used in various aspects of the present disclosure, for example, Figure 2 and Figure 6-11. The MT-EDT module 308 is configured to monitor paging from a network (e.g., network 100 and / or 202) during RRC idle mode. For example, the UE 300 may be configured with a paging occasion (e.g., a scheduled time-frequency resource) for monitoring paging messages. Upon receiving a paging message with an MT-EDT indication from the network, the MT-EDT module 308 is configured to perform a random access procedure with a serving BS (e.g., BS 105 and / or 205) to communicate with the network, send an RRC early data request message with a CPSR to the BS, and receive an RRC early data complete message from the BS. In some instances, the RRC early data complete message may include a NAS service accept message carrying data associated with the paging and a new GUTI assigned to the UE 300. In some instances, the NAS service accept message may include a NAS ACK request, and the MT-EDT module 308 is also configured to send a NAS ACK to the network to confirm receipt of the NAS service accept message.

[0075] In some instances, the RRC Early Data Complete message may include a NAS Service Accept message carrying data and a separate GUTI IE carrying a new GUTI assigned to the UE 300. In some instances, the RRC Early Data Complete message may include a NAS Service Accept message carrying data, and the MT-EDT module 308 is further configured to receive an RRC Connection Release message including a GUTI IE carrying the new GUTI after receiving the RRC Early Data Complete message.

[0076] In some aspects, the MT-EDT module 308 is configured to receive a paging message while still connected to the network but without active data transmission. Upon receiving the paging message, upon receiving the paging message with the MT-EDT indication from the network, the MT-EDT module 308 is configured to perform a random access procedure with the serving BS to resume communication with the network, send an RRC connection recovery request message to the BS, and receive an RRC connection release message from the BS. The RRC connection release message includes DL data associated with the paging and a GUTI IE carrying a new GUTI assigned to the UE 300.

[0077] The GUTI module 309 is configured to receive a GUTI from the network during initial registration, during mobility registration updates (e.g., during TAU), during periodic registration, and / or after sending a service request message to the network (e.g., triggered by a paging event), store the current GUTI in the memory 304, update the GUTI in the memory 304 when a new GUTI is received, and retrieve the current GUTI from the memory 304 when communicating with an AMF (e.g., AMF 222) of a core network (e.g., core network 220). Mechanisms for receiving a new GUTI using optimized MT-EDT CP and / or MT-EDT UP procedures during a paging event are described in more detail herein.

[0078] As shown, the transceiver 310 may include a modem subsystem 312 and an RF unit 314. The transceiver 310 may be configured to communicate bidirectionally with other devices, such as the BS 105. The modem subsystem 312 may be configured to modulate and / or encode data from the memory 304, the MT-EDT module 308, and / or the GUTI module 309 according to a modulation and coding scheme (MCS) (e.g., a low-density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 314 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data (for outbound transmissions) (e.g., PRACH preambles, RRC early data request messages, RRC connection recovery request messages, NAS ACKs) from the modem subsystem 312 or a transmission originating from another source, such as the UE 115 or the BS 105. In addition, the RF unit 314 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in the transceiver 310, the modem subsystem 312 and the RF unit 314 may be separate devices that are coupled together at the UE 115 to enable the UE 115 to communicate with other devices.

[0079] The RF unit 314 may provide modulated and / or processed data (e.g., data packets (or more generally, data messages containing one or more data packets and other information)) to the antenna 316 for transmission to one or more other devices. The antenna 316 may also receive data messages sent from other devices. The antenna 316 may provide the received data messages for processing and / or demodulation at the transceiver 310. The transceiver 310 may provide the demodulated and decoded data (e.g., paging messages, UL data, DL data, random access responses, RRC early data completion messages, RRC connection release messages) to the MT-EDT module 308 for processing. The antenna 316 may include multiple antennas with similar or different designs to maintain multiple transmission links. The RF unit 314 may configure the antenna 316.

[0080] In one example, the transceiver 310 is configured to: receive a paging associated with the MT-EDT from the network, send a data request to the network in response to the paging, and receive a message including a new GUTI and at least one of the data associated with the paging or a connection release from the network (e.g., by coordinating with the MT-EDT module 308).

[0081] In an aspect, the UE 300 may include multiple transceivers 310 that implement different RATs (e.g., NR and LTE). In an aspect, the UE 300 may include a single transceiver 310 that implements multiple RATs (e.g., NR and LTE). In an aspect, the transceiver 310 may include various components, where different combinations of components may implement different RATs.

[0082] Figure 4 is a block diagram of an exemplary BS 400 according to some aspects of the present disclosure. BS 400 may be as described above in Figure 1 4. As shown, BS 400 may include a processor 402, a memory 404, an MT-EDT module 408, a transceiver 410 (which includes a modem subsystem 412 and an RF unit 414), and one or more antennas 416. These elements may communicate with each other, directly or indirectly, for example, via one or more buses.

[0083] Processor 402 may have various features as a particular type of processor. For example, these may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. Processor 402 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such structure.

[0084] Memory 404 may include cache memory (e.g., cache memory of processor 402), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, memory 404 may include non-transitory computer-readable media. Memory 404 may store instructions 406. Instructions 406 may include instructions that, when executed by processor 402, cause processor 402 to perform the operations described herein (e.g., Figure 2 , Figure 6-10 and Fig.12 Instructions 406 may also be referred to as code, which may be broadly interpreted as including any type of computer-readable statements, such as those described above with respect to Figure 3 discussed.

[0085] The MT-EDT module 408 may be implemented via hardware, software, or a combination thereof. For example, the MT-EDT module 408 may be implemented as a processor, circuit, and / or instructions 406 stored in the memory 404 and executed by the processor 402. In some examples, the MT-EDT module 408 may be integrated within the modem subsystem 412. For example, the MT-EDT module 408 may be implemented by a combination of software components (e.g., executed by a DSP or general purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 412.

[0086] The MT-EDT module 408 may be used in various aspects of the present disclosure, for example, Figure 2 , Figure 6-10 and Fig.12 Aspects of the MT-EDT module 408. The MT-EDT module 408 is configured to facilitate MT-EDT CP and / or MT-EDT UP procedures during paging. For example, the MT-EDT module 408 is configured to: receive a DL data notification message associated with paging from a core network (e.g., AMF 222 of core network 220), send a paging message to a corresponding UE (e.g., UE 115, 215, and / or 300) served by BS 400, receive a PRACH preamble from the UE, send a random access response to the UE, receive an RRC early data request message including a NAS CPSR from the UE, send an initial UE message including a NAS CPRS to the AMF, and receive an N2 DL NAS transport message in response to the initial UE message from the AMF.

[0087] In some instances, the N2 DL NAS transport message includes a release indication and a NAS service accept message, the NAS service accept message includes DL data associated with the paging and a new GUTI assigned to the UE, and the MT-EDT module 408 is configured to forward the NAS service accept message to the UE in an RRC Early Data Complete message, and then perform an S1 release or N2 release with the AMF. In some instances, the NAS service accept message includes a NAS ACK request, and the MT-EDT module 408 is configured to receive a NAS ACK message from the UE after sending the RRC Early Data Complete message, forward the NAS ACK to the AMF, and then perform an S1 release or N2 release with the AMF. In some instances, the N2 DL NAS transport message includes a release indication, a separate GUTI IE carrying a new GUTI for the UE, and a NAS service accept message including DL data associated with paging, and the MT-EDT module 408 is configured to: forward the GUTI IE and the NAS service accept message including the data to the UE in an RRC early data complete message, and then perform an S1 release or an N2 release with the AMF. In some instances, the N2 DL NAS transport message includes DL data associated with paging, and the MT-EDT module 408 is further configured to: receive a UE context release message including a GUTI IE carrying a new GUTI for the UE from the AMF, send an RRC early data complete message including the DL data to the UE, send an RRC connection release message including the GUTI IE to the UE, and then perform an S1 release or an N2 release with the AMF.

[0088] In some instances, the MT-EDT module 408 is configured to: receive a DL data notification message associated with paging from an AMF of a connected core network, send a paging message to a corresponding UE served by the BS 400 and connected to the network, receive a PRACH preamble from the UE, send a random access response to the UE, receive an RRC connection resumption request from the UE, retrieve a UE context of the UE, send a UE context resumption request message to the AMF based on the UE context, receive a UE context response message from the AMF (which includes a GUTI IE carrying a new GUTI for the UE), receive DL data associated with paging and a UPF of the core network, send an RRC connection release message including the DL data and the GUTI IE to the UE, and then perform a suspension procedure with the AMF.

[0089] As shown, the transceiver 410 may include a modem subsystem 412 and an RF unit 414. The transceiver 410 may be configured to communicate bidirectionally with other devices (such as UE 115 and / or 300 and / or another core network element). The modem subsystem 412 may be configured to modulate and / or encode data according to an MCS (e.g., an LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.). The RF unit 414 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data (for outbound transmissions) from the modem subsystem 412 (e.g., paging messages, random access responses, initial UE messages, RRC early data complete messages, RRC messages including NAS ACK, UE context recovery request messages, and RRC connection release messages) or transmissions originating from another source (such as UE 115 and / or UE 300). In addition, the RF unit 414 may also be configured to perform analog beamforming in conjunction with digital beamforming. Although shown as being integrated together in transceiver 410, modem subsystem 412 and / or RF unit 414 may be separate devices that are coupled together at BS 105 to enable BS 105 to communicate with other devices.

[0090] The RF unit 414 may provide modulated and / or processed data (e.g., data packets (or more generally, data messages containing one or more data packets and other information)) to the antenna 416 for transmission to one or more other devices. For example, this may include transmitting information to complete attachment to the network and communication with the resident UE 115 or 300 according to some aspects of the present disclosure. The antenna 416 may also receive data messages sent from other devices and provide the received data messages for processing and / or demodulation at the transceiver 410. The transceiver 410 may provide the demodulated and decoded data (e.g., DL data indication, PRACH preamble, RRC early data request message, RRC connection recovery request message, N2DL NAS transmission message, UE context recovery response message, UE context release message) to the MT-EDT module 408 for processing. The antenna 416 may include multiple antennas with similar or different designs to maintain multiple transmission links.

[0091] In one example, the transceiver 410 is configured to receive a data request associated with paging from a UE (e.g., UE 115, 215, and / or 300), send a service request and / or a context recovery request for the UE to the AMF, and receive a message including a new GUTI for the UE and at least one of DL data associated with paging or a release indication from the AMF (e.g., by coordinating with the MT-EDT module 408).

[0092] In an aspect, the BS 400 may include multiple transceivers 410 that implement different RATs (e.g., NR and LTE). In an aspect, the BS 400 may include a single transceiver 410 that implements multiple RATs (e.g., NR and LTE). In an aspect, the transceiver 410 may include various components, where different combinations of components may implement different RATs.

[0093] Figure 5 5 is a block diagram of an exemplary network unit 500 according to some aspects of the present disclosure. The network unit 500 may be a core network (such as Figure 2 As shown, the network unit 500 may include a processor 502, a memory 504, an MT-EDT module 508, a GUTI module 509, and a transceiver 510 (which includes a modem subsystem 512 and a front end unit 514). These elements may communicate with each other directly or indirectly, for example, via one or more buses.

[0094] The processor 502 may have various features as a particular type of processor. For example, these may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 502 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such structure.

[0095] Memory 504 may include cache memory (e.g., cache memory of processor 502), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, memristor-based arrays, other forms of volatile and nonvolatile memory, or a combination of different types of memory. In some embodiments, memory 504 may include non-transitory computer-readable media. Memory 504 may store instructions 506. Instructions 506 may include instructions that, when executed by processor 502, cause processor 502 to perform the operations described herein (e.g., Figure 2 , Figure 6-10 and Fig.13 Instructions 506 may also be referred to as code, which may be broadly interpreted as including any type of computer-readable statements, such as those described above. Figure 3 discussed.

[0096] Each of the MT-EDT module 508 and the GUTI module 509 may be implemented via hardware, software, or a combination thereof. For example, each of the MT-EDT module 508 and the GUTI module 509 may be implemented as a processor, a circuit, and / or an instruction 506 stored in the memory 504 and executed by the processor 502. In some examples, the MT-EDT module 508 and / or the GUTI module 509 may be integrated within the modem subsystem 512. For example, the MT-EDT module 508 and / or the GUTI module 509 may be implemented by a combination of software components (e.g., executed by a DSP or a general purpose processor) and hardware components (e.g., logic gates and circuits) within the modem subsystem 512. In some examples, the UE may include the MT-EDT module 508 or the GUTI module 509. In other examples, the UE may include the MT-EDT module 508 and the GUTI module 509.

[0097] The MT-EDT module 508 may be used in various aspects of the present disclosure, for example, Figure 2 , Figure 6-10 and Fig.13 In some aspects, the network unit 500 implements the functionality of a UPF (e.g., UPF 224). The MT-EDT module 508 is configured to receive DL data from an external network for a UE registered with the network, and for an MT-EDT CP, page the UE by sending a DL data indication including the data to an AMF (e.g., AMF 222) serving the UE. Alternatively, for an MT-EDT UP, the MT-EDT module 508 is configured to receive DL data from an external network for a UE registered with the network, page the UE by sending a DL data indication to a corresponding AMF, and forward the data to a serving BS (e.g., BS 105, 205, and / or 400) of the paged UE.

[0098] In some aspects, the network element 500 implements the functionality of the AMF. For the MT-EDT CP, the MT-EDT module 508 is configured to: receive a DL data notification including DL data and an MT-EDT indication for the UE from the UPF, send a paging message to the BS serving the UE, receive an initial UE message including a NAS CPSR from the BS, and send an N2 DL NAS transport message including the DL data, a new GUTI for the UE, and a release indication. In some instances, the N2 DL NAS transport message includes a release indication and a NAS service accept message carrying the data and the new GUTI. In some instances, the NAS service accept message may additionally include a NASACK request, and the MT-EDT module is configured to receive a NAS ACK from the UE to confirm receipt of the NAS service accept message with the new GUTI. In some instances, the N2 DL NAS transport message includes a NAS service accept message carrying the DL data, a separate GUIT IE carrying the new GUTI, and a release indication. In some examples, the N2 DL NAS transport message includes DL data, and the MT-EDT module is configured to send a UE context release message including a new GUTI to the serving BS.

[0099] For MT-EDT UP, the MT-EDT module 508 is configured to: receive a DL data notification including an MT-EDT indication and DL data for the UE from the UPF, send a paging message to the BS serving the UE, receive a UE context recovery request message from the BS, and send a UE context recovery release message including a GUTI IE carrying a new GUTI for the UE to the BS.

[0100] The GUTI module 509 is configured to allocate a GUTI for a UE after receiving a NAS service request message from the UE during an initial registration, a mobility update registration, a periodic registration, and / or during a paging event. The GUTI module 509 may perform a GUTI allocation or reallocation from a pool of available values, and may use various mechanisms or algorithms to generate a new value for a new GUTI. Mechanisms for GUTI reallocation optimized for MT-EDT CP and / or MT-EDT UP are described in more detail herein.

[0101] As shown, the transceiver 510 may include a modem subsystem 512 and a front end unit 514. The transceiver 510 may be configured to communicate bidirectionally with other devices (such as BS 105, 205, and 400 and / or another core network element). The modem subsystem 512 may be configured to modulate and / or encode data according to an MCS (e.g., an LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, etc.). The front end unit 514 may include an electro-optical (E / O) component and / or an optoelectronic (O / E) component that converts an electrical signal into an optical signal for transmission to a BS (such as BS 105, 205, and 500), and / or receives an optical signal from the BS and converts the optical signal into an electrical signal. The front end unit 514 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, optoelectronic conversion, or electro-optical conversion, etc.) the modulated / encoded data from the modem subsystem 512 (for outbound transmission) or a transmission originating from another source (e.g., a backend or core network). Although shown as being integrated together in the transceiver 510, the modem subsystem 512 and the front end unit 514 can be separate devices that are coupled together at the network unit 500 to enable the network unit 500 to communicate with other devices. The front end unit 514 can send optical signals carrying modulated and / or processed data on an optical link (e.g., a backhaul link). The front end unit 514 can also receive optical signals carrying data messages and provide the received data messages for processing and / or demodulation at the transceiver 510.

[0102] In one example, the transceiver 510 is configured to: send a paging message for a UE associated with a first GUTI, receive a service request or a context recovery request for the UE, and send a message including a second GUTI different from the first GUTI and at least one of data associated with the paging or a connection release, for example, by coordinating with the MT-EDT module 508 and the GUTI module 509.

[0103] Figure 66 is a signaling diagram illustrating a GUTI reallocation method 600 for MT-EDT CP optimization according to some aspects of the present disclosure. The method 600 is implemented by a UE 615, a BS 605, an AMF 622, and a UPF 624. The UE 615 may be similar to the UE 115, 215, and / or 300. In some instances, the UE 615 is a low power device (such as an IoT device). The BS 605 may be similar to the BS 105, 205, and / or 400. The AMF 622 may be similar to the AMF 222. The UPF 624 may be similar to the UPF 224. The AMF 622 and the UPF 624 may correspond to a portion of a 5G core network (e.g., the network 220). In some instances, the BS 605 may be a 4G eNB serving the UE 615. In some other instances, the BS 605 may be a 5G gNB serving the UE 615. BS 605, AMF 622 and UPF 624 may be generally referred to as a network, a core network component or a network side. The steps of method 600 may be performed by a computing device (e.g., a processor, a processing circuit and / or other appropriate components) of UE 615, BS 605, a core network (e.g., a network unit 500 implementing AMF 622 and / or UPF 624). As shown, method 600 includes a plurality of enumerated steps, but embodiments of method 600 may include other steps before, after and between the enumerated steps. In some embodiments, one or more of the enumerated steps may be omitted or performed in a different order.

[0104] The method 600 may be implemented after the UE 615 has completed an initial network attachment or registration procedure with the network and received a GUTI (eg, including a PLMN ID and an S-TSMI) from the AMF 622, for example, as described above with respect to Figure 2 The method 600 may be performed when the UE 615 is in an idle state. For example, the method 600 may be implemented as part of an idle mode procedure during step 260 of the method 200. The method 600 forwards data associated with paging, for example, from the AMF 622 to the serving BS 605 via a control plane.

[0105] At step 630, UPF 624 receives DL data for UE 615, for example, from an external network (eg, an Internet Protocol (IP) network or a non-IP network such as a local area network (LAN)). For example, UE 615 may be in sleep mode during this time.

[0106] At step 632, the UPF 224 sends a DL data notification message to the AMF 622. The DL data notification message includes the MT-EDT indication for the UE 615 and the DL data.

[0107] At step 634 , in response to the DL data notification message, the AMF 622 sends a DL data notification ACK message to the UPF 624 .

[0108] At step 636 , the AMF 622 buffers the DL data for the UE 615 .

[0109] At step 638, AMF 622 sends a paging message to BS 605 serving UE 615. The paging message includes an MT-EDT indication. BS 605 may have configured a paging occasion for UE 615 and may send a paging message to UE 615 during the paging occasion of UE 615.

[0110] At step 640, upon receiving the paging message from the AMF 622, the BS 605 sends the paging message to the UE 615. The paging message includes an MT-EDT indication. For example, the UE 615 may cycle through a sleep-wake cycle during an idle state and may wake up during a paging occasion (configured by the BS 605) to monitor paging messages from the network.

[0111] At step 642, UE 615 receives a paging message. Upon receiving the paging message, UE 615 performs a RACH procedure with BS 605 to establish an RRC connection to receive data associated with the paging. At step 644, UE 615 sends a PRACH preamble (MSG1) to BS 605. At step 646, upon detecting the PRACH preamble, BS 605 sends a random access response (MSG2) to UE 615. The random access response may include scheduling resources for UE 615. At step 648, UE 615 sends an RRC early data request message (MSG3) to BS 605. The RRC early data request message includes a NAS CPSR message. The RRC early data request message may include an S-TMSI from an earlier received GUTI. Alternatively, the CPSR may include an S-TMSI from an earlier received GUTI.

[0112] At step 650, upon receiving the RRC Early Data Request message, the BS 605 sends an Initial UE Message to the AMF 622. The BS 605 forwards the CPSR to the AMF 622 by including the CPSR in the Initial UE Message. The BS 605 may determine which AMF to forward the CPSR based on the S-TMSI in the RRC Early Data Request message.

[0113] At step 652, in response to the initial UE message, the AMF 622 sends an N2 DL NAS transport message to the BS 605. The N2DL NAS transport message includes a NAS service accept message and a release indication. The AMF 622 may identify the UE 615 based on the S-TMSI in the initial UE message. Alternatively, the AMF 622 may identify the UE 615 based on the S-TMSI in the CPSR. The AMF 622 generates or reallocates a new 5G-GUTI for the UE 615. The NAS service accept message includes DL data and a new 5G-GUTI. The NAS service accept message may be represented by NAS service accept (DL data, 5G-GUTI). The release indication is used to indicate that the BS 605 releases the RRC connection with the UE 615 after sending the NAS service accept message to the UE 615. In some instances, the N2 DL NAS transport message may also include a packet data unit (PDU) session identifier (ID) associated with the data. For example, the UE 615 may have established a PDU session before entering the idle mode, and data associated with the PDU session may arrive while the UE 615 is in the idle mode.

[0114] At step 654, upon receiving the N2 DL NAS transport message, BS 605 sends an RRC Early Data Complete message in response to the RRC Early Data Request message to UE 615. BS 605 forwards the NAS Service Accept message to UE 615 by including the NAS Service Accept message (including DL data and 5G-GUTI) in the RRC Early Data Complete message.

[0115] At step 656, after receiving the N2 DL NAS transport message including the 5G-GUTI, the BS 605 performs N2 release via N2 signaling with the AMF 622. N2 refers to the interface between the 5G core network and the 5G gNB or between the 5G core network and the 4G eNB. At this point, the UE 615 has completed receiving DL data associated with paging and returns to sleep mode to save power.

[0116] As discussed above, the newly allocated GUTI is typically sent in a UCU procedure. For example, the AMF 622 may send a UCU update command including a new GUTI to a UE (e.g., UE 615), and the UE may respond by sending a UCU complete message to the AMF 622. If the AMF 622 utilizes the UCU update procedure to update the new 5G-GUTI to the UE 615, the BS 605 is required to send an additional RRC connection release message to the UE 615 after the UCU procedure. Therefore, after the last RRC early data complete message, there will be at least three additional messages exchanged between the UE 615 and the BS 605. The method 600 optimizes the GUTI reallocation procedure by enabling the AMF 622 to send a single NAS message including DL data and 5G-GUTI and enabling the BS 605 to include the 5G-GUTI in the RRC early data complete message for MT-EDT, rather than utilizing the UCU procedure.

[0117] In some aspects, the AMF 622 may forward the DL data to the BS 605 in multiple NAS DL transport messages, and may include the release indication and the NAS message including the 5G-GUTI in the last N2 DL NAS transport message. The BS 605 may forward the DL data to the UE 615. Thus, upon receiving the NAS DL transport message including the NAS message including the 5G-GUTI, the BS 605 may send an RRC connection release message including the 5G-GUTI to the UE 615.

[0118] Figure 7700 is a signaling diagram illustrating a GUTI reallocation method 700 for MT-EDT CP optimization according to some aspects of the present disclosure. The method 700 may be implemented by a UE 715, a BS 705, an AMF 722, and a UPF 724. The UE 715 may be similar to the UE 115, 215, 300, and / or 615. In some instances, the UE 715 is a low power device (such as an IoT device). The BS 705 may be similar to the BS 105, 205, 400, and / or 605. The AMF 722 may be similar to the AMF 222 and / or 622. The UPF 724 may be similar to the UPF 224 and / or 624. The AMF 722 and the UPF 724 may correspond to a portion of a 5G core network (e.g., the network 220). In some instances, the BS 705 may be a 4G eNB serving the UE 715. In some other instances, BS 705 may be a 5G gNB serving UE 715. The steps of method 700 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other appropriate components) of UE 715, BS 705, a core network (e.g., a network element 500 implementing AMF 722 and / or UPF 724). As shown, method 700 includes a plurality of enumerated steps, but embodiments of method 700 may include additional steps before, after, and between the enumerated steps. In some embodiments, one or more of the enumerated steps may be omitted or performed in a different order.

[0119] In general, method 700 includes features similar to method 600 in many respects. For example, at step 702, the network pages UE 715 when DL data for UE 715 arrives. Paging may include steps similar to steps 632, 634, 636, 638, and 640. At step 704, in response to the paging, UE 715 performs a random access with BS 705 by performing steps similar to steps 642 and 646. At step 720, similar to step 648, UE 715 sends an RRC early data request to BS 705. At step 730, similar to step 650, BS 705 sends an initial UE message to AMF 722. Therefore, for the sake of brevity, the details of steps 702, 704, 720, and 730 are not repeated here. Please refer to the corresponding description above.

[0120] At step 740, similar to step 654, in response to the initial UE message, the AMF 722 sends an N2 DL NAS transport message including DL data, a new 5G-GUTI and a release indication to the BS 705. The AMF 722 generates a 5G-GUTI in response to the CPSR. However, the NAS service accept message additionally includes an ACK request. The NAS service accept message can be represented by NAS service accept (DL data, 5G-GUTI, ACK request).

[0121] At step 750, upon receiving the N2 DL NAS transport message, BS 705 sends an RRC Early Data Complete message to UE 715. BS 705 forwards the NAS Service Accept message to UE 715 by including the NAS Service Accept message (including DL data, new 5G-GUTI and ACK request) in the RRC Early Data Complete message.

[0122] At step 760, in response to the NAS ACK, the UE 715 sends a NAS ACK message to the network to confirm the reception of the new 5G-GUTI. At step 770, the BS 705 forwards the NAC ACK to the AMF 722.

[0123] At step 780, BS 705 performs N2 release with AMF 722. At this point, UE 715 has completed receiving DL data associated with paging and returns to sleep mode to save power.

[0124] Receipt of the NAS ACK at the AMF 722 ensures that the UE 715 and the AMF 722 are using the same GUTI for the UE 715. In some aspects, instead of using a NAS ACK to confirm receipt of the new GUTI, N2 signaling may be used for confirmation. For example, the AMF 722 may send an N2 delivery confirmation request, and the BS 605 may send an N2 delivery ACK or a negative ACK (NACK) to the AMF 722. In some aspects, when there is no confirmation for the new GUTI, the AMF 722 may retain both the old GUTI and the new GUTI for the UE 715. The AMF 722 may use the new GUTI for subsequent communications with the UE 715. If the communication fails, the AMF 722 may fall back to using the old GUTI.

[0125] Figure 88 is a signaling diagram illustrating a GUTI reallocation method 800 for MT-EDT CP optimization according to some aspects of the present disclosure. The method 800 is implemented by a UE 815, a BS 805, an AMF 822, and a UPF 824. The UE 815 may be similar to the UE 115, 215, 300, 615, and / or 715. In some instances, the UE 815 is a low power device (such as an IoT device). The BS 805 may be similar to the BS 105, 205, 400, 605, and / or 705. The AMF 822 may be similar to the AMF 222, 622, and / or 722. The UPF 824 may be similar to the UPF 224, 624, and / or 724. The AMF 822 and the UPF 824 may correspond to a portion of a 5G core network (e.g., the network 220). In some instances, BS 805 may be a 4G eNB serving UE 815. In some other instances, BS 805 may be a 5G gNB serving UE 815. The steps of method 800 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other appropriate components) of UE 815, BS 805, a core network (e.g., a network element 500 implementing AMF 822 and / or UPF 824). As shown, method 800 includes a plurality of enumerated steps, but embodiments of method 800 may include additional steps before, after, and between the enumerated steps. In some embodiments, one or more of the enumerated steps may be omitted or performed in a different order.

[0126] In general, method 800 includes features similar to method 600 in many respects. For example, at step 802, the network pages UE 815 when DL data for UE 815 arrives. Paging may include steps similar to steps 632, 634, 636, 638, and 640. At step 804, in response to the paging, UE 815 performs a random access with BS 805 by performing steps similar to steps 642 and 646. At step 820, similar to step 648, UE 815 sends an RRC early data request to BS 805. At step 830, similar to step 650, BS 805 sends an initial UE message to AMF 822. Therefore, for the sake of brevity, the details of steps 802, 804, 820, and 830 will not be repeated here. Please refer to the corresponding description above.

[0127] At step 840, in response to the initial UE message, the AMF 822 sends an N2 DL NAS transport message including DL data, a new 5G-GUTI, and a release indication to the BS 805, similar to step 654. However, the 5G-GUTI is sent as a message separate from the NAS service accept message. The 5G-GUTI is sent as a 5G-GUTI IE. In other words, the N2 DL NAS transport message includes: a NAS service accept message including DL data, a 5G-GUTI IE including a new 5G-GUTI assigned to the UE 815, and a release indication.

[0128] At step 850, upon receiving the N2 DL NAS transport message, BS 805 sends an RRC Early Data Complete message to UE 815. BS 805 forwards the NAS Service Accept message to UE 815 by including the NAS Service Accept message (including DL data) and 5G-GUTI IE in the RRC Early Data Complete message.

[0129] At step 860, after receiving the N2 DL NAS transport message including the 5G-GUTI, the BS 805 performs an N2 release with the AMF 822. At this point, the UE 815 has completed receiving DL data associated with the paging and returns to sleep mode to save power.

[0130] In some aspects, method 800 may include the NAS ACK mechanism described in method 700, for example, by including a NAS ACK request in a NAS SERVICE ACCEPT message at step 840. Alternatively, method 800 may include an ACK request in an N2 DL NAS Transport message as a separate message or parameter from the NAS SERVICE ACCEPT message at step 840, and BS 805 may include the ACK request in an RRC EARLY DATA COMPLETE message.

[0131] Fig. 99 is a signaling diagram illustrating a GUTI reallocation method 900 for MT-EDT CP optimization according to some aspects of the present disclosure. The method 900 is implemented by a UE 915, a BS 905, an AMF 922, and a UPF 924. The UE 915 may be similar to the UE 115, 215, 300, 615, 715, and / or 815. In some instances, the UE 915 is a low-power device, such as an IoT device. The BS 905 may be similar to the BS 105, 205, 400, 605, 705, and / or 805. The AMF 922 may be similar to the AMF 222, 622, 722, and / or 822. The UPF 924 may be similar to the UPF 224, 624, 724, and / or 824. The AMF 922 and the UPF 924 may correspond to a portion of a 5G core network (e.g., the network 220). In some instances, BS 905 may be a 4G eNB serving UE 915. In some other instances, BS 905 may be a 5G gNB serving UE 915. The steps of method 900 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other appropriate components) of UE 915, BS 905, a core network (e.g., a network element 500 implementing AMF 922 and / or UPF 924). As shown, method 900 includes a plurality of enumerated steps, but embodiments of method 900 may include additional steps before, after, and between the enumerated steps. In some embodiments, one or more of the enumerated steps may be omitted or performed in a different order.

[0132] In general, method 900 includes features similar to method 600 in many respects. For example, at step 902, the network pages UE 915 when DL data for UE 915 arrives. Paging may include steps similar to steps 632, 634, 636, 638, and 640. At step 904, in response to the paging, UE 915 performs a random access with BS 905 by performing steps similar to steps 642 and 646. At step 920, similar to step 648, UE 915 sends an RRC early data request to BS 905. At step 930, similar to step 650, BS 905 sends an initial UE message to AMF 922. Therefore, for the sake of brevity, the details of steps 902, 904, 920, and 930 will not be repeated here. Please refer to the corresponding description above.

[0133] At step 940, in response to the initial UE message, the AMF 922 sends an N2 DL NAS transport message including DL data.

[0134] At step 950, upon receiving the N2 DL NAS transfer message, the BS 905 sends an RRC Early Data Complete message to the UE 915. The BS 905 forwards the NAS Service Accept message to the UE 915 by including the NAS Service Accept message (including DL data) in the RRC Early Data Complete message.

[0135] At step 960, AMF 922 sends a UE context release message including a new 5G-GUTI IE to BS 905 and instructs BS 905 to send an RRC connection release to UE 915.

[0136] At step 970, BS 905 sends an RRC connection release message including 5G-GUTI IE to UE 915.

[0137] In some aspects, when method 800 or 900 is employed, the 5G-GUTI IE may be sent as an encrypted transparent container in an RRC (connection release or early data completion) message. In this aspect, the RRC layer at the UE 815 or 915 may forward the container to the NAS layer. The NAS decrypts the container to receive the new 5G-GUTI. The container may be in the form of a type-length-value (TLV) message or a value-only (V) message. A message authentication code (NAS-MAC) for NAS integrity may additionally be included in the transparent container. If a NAS-MAC is present, the UE may verify the integrity protection of the container by verifying with the received NAS-MAC.

[0138] Fig.101 is a signaling diagram illustrating a GUTI reallocation method 1000 for MT-EDT UP optimization according to some aspects of the present disclosure. The method 1000 is implemented by a UE 1015, a BS 1005, an AMF 1022, and a UPF 1024. The UE 1015 may be similar to the UE 115, 215, 300, 615, 715, 815, and / or 915. In some instances, the UE 1015 is a low power device, such as an IoT device. The BS 1005 may be similar to the BS 105, 205, 400, 605, 705, 805, and / or 905. The AMF 1022 may be similar to the AMF 222, 622, 722, 822, and / or 922. The UPF 1024 may be similar to the UPF 224, 624, 724, 824, and / or 924. AMF 1022 and UPF 1024 may correspond to part of a 5G core network (e.g., network 220). In some instances, BS 1005 may be a 4G eNB serving UE 1015. In some other instances, BS 1005 may be a 5G gNB serving UE 1015. The steps of method 1000 may be performed by a computing device (e.g., a processor, processing circuitry, and / or other appropriate components) of UE 1015, BS 1005, a core network (such as a network element 500 implementing AMF 1022 and / or UPF 1024). As shown, method 1000 includes a plurality of enumerated steps, but embodiments of method 1000 may include additional steps before, after, and between the enumerated steps. In some embodiments, one or more of the enumerated steps may be omitted or performed in a different order. For example, as described above with respect to Figure 2 As discussed in method 200 of , method 1000 may be implemented after UE 615 has completed an initial network attachment procedure with the network and received a GUTI (eg, including a PLMN ID and an S-TMSI) from AMF 622.

[0139] In general, method 1000 includes features similar to method 600 in many respects. For example, at step 1002, when DL data for UE 1015 arrives, the network pages UE 1015. Paging may include steps similar to steps 632, 634, 636, 638, and 640. At step 1004, in response to the paging, UE 1015 performs random access with BS 1005 by performing steps similar to steps 642 and 646. Accordingly, for the sake of brevity, the details of steps 1002 and 1004 will not be repeated here. Please refer to the corresponding description above.

[0140] However, the method 1000 may be performed while the UE 1015 is in RRC connected mode but during a suspended state. During the RRC connected mode, the BS 1005 may have a UE context for the UE 1015. Additionally, the method 1000 forwards data associated with paging from the UPF 624 to the BS 605, for example, via a user plane.

[0141] At step 1020, after performing random access, the UE 1015 sends an RRC connection resumption request message (MSG3) to the BS 1005. The RRC connection resumption request message may include a resumption ID and / or a short resume message authentication code integrity (MAC-I) (e.g., referred to as "shortResumeMAC-I"). The UE 1015 may receive the resumption ID from a previous suspension procedure.

[0142] At step 1030, upon receiving the RRC Connection Recovery Request message, BS 1005 sends a UE Context Recovery Request message to AMF 1022. The UE Context Recovery Request message may include a UE context for UE 1015. In some instances, the UE context may include an S-TMSI of UE 1015. AMF 1022 may identify UE 1015 based on the S-TMSI upon receiving the UE Context Recovery Request message.

[0143] At step 1040, upon receiving the UE context restoration request message, the AMF 1022 may modify the bearer so that data available for the UE 1015 may be transmitted to the BS 1005 serving the UE 1015. In this regard, the AMF 1022 and the UPF 1024 may exchange a modify bearer request message and a modify bearer response message.

[0144] At step 1050, after completing the modify bearer procedure, the AMF 1022 sends a UE context restoration response message to the BS 1005. The UE context restoration response message includes a 5G-GUTI IE, and the 5G-GUTI IE includes a new 5G-GUTI for the UE 1015. The AMF 1022 generates a new GUTI for the UE 1015 in response to receiving the UE context restoration request message. The UE context restoration response message may instruct the BS 1005 to release the RRC connection with the UE 1015 after transmitting the new GUTI and DL data to the UE 1015.

[0145] At step 1060 , after modifying the bearer, UPF 1024 sends DL data to BS 1005 .

[0146] At step 1070, BS 1005 sends an RRC connection release message (MSG4) to UE 1015. BS 1005 includes DL data and 5G-GUTI IE for UE 1015 in the RRC connection release message.

[0147] At step 1080, after sending the RRC connection release message to UE 1015, BS 1005 performs a suspension process with AMF 1022.

[0148] At step 1090, AMF 1022 performs a modify bearer procedure with UPF 1024 by exchanging modify bearer request and modify bearer response messages with UPF 1024.

[0149] As can be observed, the method 1000 delivers a new 5G-GUTI to the UE 1015 by piggybacking the 5G-GUTI in the RRC Connection Release message. The MT-EDT UP optimization process does not include NAS signaling, which may be required for GUTI reallocation in general. Including the GUTI IE in the RRC Connection Release message allows 1000 to pass the new 5G-GUTI to the UE 1015 without performing the UCU process.

[0150] In some aspects, instead of including the 5G-GUTI IE in the UE context recovery response message at step 1050, the AMF 1022 may send another message including the 5G-GUTI IE to the BS 1005.

[0151] Although methods 600-1000 are discussed in the context of a 5G core, a similar GUTI reallocation mechanism may be used with EPS by replacing the AMF (e.g., AMF 622, 722, 822, 922, and / or 1022) with an MME and replacing the UPF (e.g., UPF 624, 724, 824, 924, and / or 1024) with an S-GW / P-GW.

[0152] Fig.111 is a flow chart of a communication method 1100 according to some aspects of the present disclosure. The steps of the method 1100 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other appropriate components) of a wireless communication device or other appropriate means for performing the steps. For example, a wireless communication device (e.g., a UE 115, 215, 300, 615, 715, 815, 915, and / or 1015) may utilize one or more components (e.g., a processor 302, a memory 304, an MT-EDT module 308, a GUTI module 309, a transceiver 310, a modem 312, and one or more antennas 316) to perform the steps of the method 1100. The method 1100 may be implemented as described above with respect to Figure 2 , 6 , 7, 8, 9 and / or Fig.10 Similar mechanisms are described in methods 200, 600, 700, 800, 900, and / or 1000. As shown, method 1100 includes a plurality of enumerated steps, but aspects of method 1100 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0153] At step 1110, method 1100 includes receiving, by the UE, a page including an MT-EDT from the network. In some examples, the UE may receive the page using one or more components such as the processor 302, the MT-EDT module 308, the GUTI module 309, the transceiver 310, the modem 312, and one or more antennas 316.

[0154] At step 1120, method 1100 includes: in response to the paging, the UE sends a data request to the network. In some examples, the UE can use one or more components (such as processor 302, MT-EDT module 308, GUTI module 309, transceiver 310, modem 312 and one or more antennas 316) to send the data request.

[0155] At step 1130, the method 1100 includes: receiving, by the UE, a message in response to the data request from the network, the message including: a global unique temporary identifier (GUTI), and at least one of data associated with paging or a connection release indication. In some examples, the UE may receive the information using one or more components (such as the processor 302, the MT-EDT module 308, the GUTI module 309, the transceiver 310, the modem 312, and one or more antennas 316).

[0156] In some aspects, step 1120 includes: sending the data request includes: sending an RRC Early Data Request message by the UE to the network, and step 1130 includes: receiving an RRC Early Data Complete message including the data and the GUTI from the network by the UE. In some aspects, the RRC Early Data Complete message includes a NAS Service Accept message, and wherein the NAS Service Accept message includes the data and the GUTI. In some aspects, the RRC Early Data Complete message includes: a NAS Service Accept message including the data and an Information Element (IE) including the GUTI. In some aspects, the RRC Early Data Complete message also includes a NAS ACK request, and the method 1100 also includes: in response to the NAS ACK request, sending a NAS ACK by the UE to the network.

[0157] In some aspects, step 1120 includes sending, by the UE, a radio resource control (RRC) early data request message to the network, and step 1130 includes receiving, by the UE, a RRC connection release message from the network including a connection release indication and the GUTI.

[0158] In some aspects, step 1120 includes sending, by the UE, a radio resource control (RRC) connection resume request message to the network, and step 1130 includes receiving, by the UE, a RRC connection release message from the network including a connection release indication, data, and the GUTI.

[0159] Fig.12 1 is a flow chart of a communication method 1200 according to some aspects of the present disclosure. The steps of method 1200 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other appropriate components) of a wireless communication device or other appropriate means for performing the steps. For example, a core network entity (e.g., a network unit 500, an AMF 222, 622, 722, 822, 922, and / or 1022, and / or a UPF 224, 624, 724, 824, 924, and / or 1024) may utilize one or more components (e.g., a processor 502, a memory 504, an MT-EDT module 508, a GUTI module 509, a transceiver 510, a modem 512, and a front end 514) to perform the steps of method 1200. Method 1200 may be implemented as described above with respect to Figure 2 , 6 , 7, 8, 9 and / or Fig.10 Similar mechanisms are described in methods 200, 600, 700, 800, 900, and / or 1000. As shown, method 1200 includes a plurality of enumerated steps, but aspects of method 1200 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0160] At step 1210, the method 1200 includes sending, by the core network entity, a page for a UE (e.g., UE 115, 215, 300, 615, 715, 815, 915, and / or 1015) associated with a first GUTI to a BS (e.g., BS 105, 205, 400, 605, 705, 805, 905, and / or 1005). In some examples, the core network entity may send the page using one or more components (e.g., processor 502, MT-EDT module 508, GUTI module 509, transceiver 510, modem 312, and front end 514).

[0161] At step 1220, the method 1200 includes receiving, by the core network entity from the BS, a request associated with at least one of a service or context recovery of the paged UE. In some examples, the core network entity may receive the request using one or more components such as the processor 502, the MT-EDT module 508, the GUTI module 509, the transceiver 510, the modem 312, and the front end 514.

[0162] At step 1230, the method includes: sending, by the core network entity, a message in response to the request to the BS, the message including: a second GUTI different from the first GUTI for the paged UE, and at least one of data associated with the paging or a connection release indication. In some examples, the core network entity may send the message using one or more components (such as the processor 502, the MT-EDT module 508, the GUTI module 509, the transceiver 510, the modem 312, and the front end 514).

[0163] In some aspects, the method 1200 further includes: generating, by the core network entity, a second GUTI in response to the request. In some instances, the core network entity may utilize one or more components (such as the processor 502 and the MT-EDT module 508, the GUTI module 509) to generate the second GUTI, for example, by selecting from a set of values.

[0164] In some aspects, step 1220 includes: receiving, by the core network entity, an initial UE message including a NAS service request, and step 1230 includes: sending, by the core network entity, a NAS transport message including data and a second GUTI to the BS. In some aspects, the NAS transport message includes a NAS service accept message, and wherein the NAS service accept message includes data and the second GUTI. In some aspects, the NAS transport message includes: a NAS service accept message including data, and an information element (IE) including the second GUTI. In some aspects, the NAS transport message also includes a NAS acknowledgement (ACK) request, and the method 1200 also includes: receiving, by the core network entity, a NAS ACK in response to the NAS ACK request from the BS. In some instances, the core network entity may receive the ACK using one or more components such as the processor 502, the MT-EDT module 508, the GUTI module 509, the transceiver 510, the modem 312, and the front end 514.

[0165] In some aspects, step 1220 includes receiving, by the core network entity, a UE initial message including a non-access stratum (NAS) service request, and step 1230 includes sending, by the core network entity to the BS, a UE context release message including a connection release indication and the second GUTI.

[0166] In some aspects, step 1220 includes receiving, by the core network entity, a UE context restoration request message, and step 1230 includes sending, by the core network entity to the BS, a UE context restoration response message including a connection release indication and the second GUTI.

[0167] Fig.13 1300 is a flow chart of a communication method 1300 according to some aspects of the present disclosure. The steps of the method 1300 may be performed by a computing device (e.g., a processor, a processing circuit, and / or other appropriate components) of a wireless communication device or other appropriate means for performing the steps. For example, a wireless communication device (e.g., a BS 105, 205, 400, 605, 705, 805, 905, and / or 1005) may utilize one or more components (e.g., a processor 402, a memory 404, an MT-EDT module 408, a transceiver 410, a modem 412, and one or more antennas 416) to perform the steps of the method 1300. The method 1300 may be implemented as described above with respect to Figure 2 , 6 , 7, 8, 9 and / or Fig.10Similar mechanisms are described in methods 200, 600, 700, 800, 900, and / or 1000. As shown, method 1300 includes a plurality of enumerated steps, but aspects of method 1300 may include additional steps before, after, and between the enumerated steps. In some aspects, one or more of the enumerated steps may be omitted or performed in a different order.

[0168] At step 1310, method 1300 includes receiving, by the BS, a data request associated with paging from the UE. In some examples, the BS may receive the data request using one or more components such as the processor 402, the MT-EDT module 408, the transceiver 410, the modem 412, the RF unit 414, and one or more antennas 416.

[0169] At step 1320, the method 1300 includes: in response to the data request, the BS sends a request associated with service or context recovery of the UE to the core network. In some examples, the BS can use one or more components (such as the processor 402, the MT-EDT module 408, the transceiver 410, the modem 412, the RF unit 414, and one or more antennas 416) to send the request associated with service or context recovery of the UE.

[0170] At step 1330, the method 1300 includes: receiving, by the BS from the core network, a message in response to a request associated with service or context recovery of the UE, the message including a global unique temporary identifier (GUTI) and a connection release indication. In some examples, the BS may receive the message using one or more components such as the processor 402, the MT-EDT module 408, the transceiver 410, the modem 412, the RF unit 414, and one or more antennas 416.

[0171] At step 1340, the method 1300 includes: sending, by the BS, a connection release message including the GUTI to the UE. In some examples, the BS may utilize one or more components (such as the processor 402, the MT-EDT module 408, the transceiver 410, the modem 412, the RF unit 414, and one or more antennas 416) to send the connection release message.

[0172] In some aspects, step 1310 includes receiving, by the BS, a radio resource control (RRC) early data request message from the UE, and step 1340 includes sending, by the BS, an RRC early data complete message including the GUTI to the UE.

[0173] In some aspects, step 1330 includes receiving, by the BS from the core network, a NAS transport message including a NAS service accept message including data associated with paging, an information element (IE) including the GUTI, and a connection release indication.

[0174] In some aspects, step 1310 includes receiving the data request including receiving, by the BS, an RRC Early Data Request message from the UE, and step 1340 includes sending, by the BS, an RRC Connection Release message including the GUTI to the UE.

[0175] In some aspects, step 1330 includes receiving, by the BS from the core network, a UE context release message including the GUTI in response.

[0176] In some aspects, step 1310 includes sending the request including sending, by the UE, a UE context restore request message to the core network, and step 1330 includes receiving, by the BS, a UE context restore response message including the GUTI and a connection release indication from the core network.

[0177] In some aspects, method 1300 includes receiving, by the BS, data associated with paging for the UE from the core network, and step 1340 includes sending, by the BS, an RRC connection release message including the data and the GUTI to the UE.

[0178] A further embodiment of the present disclosure includes a method of wireless communication. The method of wireless communication includes: receiving, by a user equipment (UE), a paging associated with mobile terminated early data transfer (MT-EDT) from a network; sending, by the UE, a data request to the network in response to the paging; and receiving, by the UE, a message in response to the data request from the network, the message including: a globally unique temporary identifier (GUTI), and at least one of data associated with the paging or a connection release indication.

[0179] The method may also include one or more of the following features. For example, the method includes: wherein sending a data request includes: sending a radio resource control (RRC) early data request message by the UE to the network; and receiving the message includes: receiving an RRC early data completion message including data and a GUTI by the UE from the network. The RRC early data completion message includes a non-access stratum (NAS) service acceptance message, and wherein the NAS service acceptance message includes data and the GUTI. The RRC early data completion message includes: a non-access stratum (NAS) service acceptance message including data, and an information element (IE) including the GUTI. The RRC early data completion message also includes a non-access stratum (NAS) confirmation (ACK) request, and wherein the method further includes: in response to the NAS ACK request, sending a NAS ACK by the UE to the network. Sending a data request includes: sending a radio resource control (RRC) early data request message by the UE to the network; and receiving the message includes: receiving an RRC connection release message including a connection release indication and a GUTI by the UE from the network. Sending the data request includes: sending a radio resource control (RRC) connection resumption request message by the UE to the network; and receiving the message includes: receiving an RRC connection release message including a connection release indication, data and GUTI by the UE from the network.

[0180] Further embodiments of the present disclosure include a method of wireless communication. The method of wireless communication includes: sending, by a core network entity, a paging for a user equipment (UE) associated with a first global unique temporary identifier (GUTI) to a base station (BS); receiving, by the core network entity, a request associated with at least one of service or context recovery of the paged UE from the BS; sending, by the core network entity, a message in response to the request to the BS, the message including: a second GUTI for the paged UE different from the first GUTI, and at least one of data associated with the paging or a connection release indication.

[0181] The method may also include one or more of the following features. For example, the method includes: generating a second GUTI by the core network entity in response to the request. Receiving the request includes: receiving an initial UE message including a non-access stratum (NAS) service request by the core network entity; and sending the message includes: sending a NAS transfer message including data and a second GUTI by the core network entity to the BS. The NAS transfer message includes a NAS service acceptance message, and wherein the NAS service acceptance message includes data and the second GUTI. The NAS transfer message includes: a non-access stratum (NAS) service acceptance message including data, and an information element (IE) including the second GUTI. The NAS transfer message also includes a NAS confirmation (ACK) request, and wherein the method also includes: receiving a NAS ACK in response to the NAS ACK request from the BS by the core network entity. Receiving the request includes: receiving a UE initial message including a non-access stratum (NAS) service request by the core network entity; and sending the message includes: sending a UE context release message including a connection release indication and a second GUTI by the core network entity to the BS. Receiving the request includes: receiving, by the core network entity, a UE context restoration request message; and sending the message includes: sending, by the core network entity, a UE context restoration response message including a connection release indication and the second GUTI to the BS.

[0182] A further embodiment of the present disclosure includes a method of wireless communication. The wireless communication method includes: receiving, by a base station (BS), a data request associated with paging from a user equipment (UE); in response to the data request, sending, by the BS, a request associated with service or context recovery of the UE to a core network; receiving, by the BS, a message in response to the request associated with service or context recovery of the UE from the core network, the message including a global unique temporary identifier (GUTI) and a connection release indication. The wireless communication method also includes: sending, by the BS, a connection release message including the GUTI to the UE.

[0183] The method may also include one or more of the following features. For example, the method includes: wherein receiving the data request includes: receiving a radio resource control (RRC) early data request message from the UE by the BS; and sending the connection release message includes: sending an RRC early data complete message including a GUTI to the UE by the BS. Receiving the message includes: receiving a non-access stratum (NAS) transfer message from the core network by the BS, the NAS transfer message including: a NAS service accept message including data associated with paging, an information element (IE) including the GUTI, and a connection release indication. Receiving the data request includes: receiving a radio resource control (RRC) early data request message from the UE by the BS; and sending the connection release message includes: sending an RRC connection release message including the GUTI to the UE by the BS. Receiving the message includes: receiving a UE context release message including the GUTI as a response from the core network by the BS. Sending the request includes: sending a UE context recovery request message to the core network by the UE; and receiving the message includes: receiving a UE context recovery response message including the GUTI and the connection release indication by the BS from the core network. Sending the connection release message includes: the BS sends the RRC connection release message including data and GUTI to the UE.

[0184] A further embodiment of the present disclosure includes a user equipment (UE). The user equipment includes a transceiver configured to: receive a paging associated with a mobile terminated early data transfer (MT-EDT) from a network; send a data request in response to the paging; and receive a message in response to the data request from the network, the message including: a globally unique temporary identifier (GUTI), and at least one of the data associated with the paging or a connection release indication.

[0185] The UE may also include one or more of the following features. For example, the UE includes: wherein the transceiver configured to send a data request is also configured to: send a radio resource control (RRC) early data request message to the network; and the transceiver configured to receive the message is also configured to: receive an RRC early data completion message including data and a GUTI from the network. The RRC early data completion message includes a non-access stratum (NAS) service acceptance message, and wherein the NAS service acceptance message includes data and a GUTI. The RRC early data completion message includes: a non-access stratum (NAS) service acceptance message including data, and an information element (IE) including a GUTI. The RRC early data completion message also includes a non-access stratum (NAS) acknowledgment (ACK) request, and wherein the transceiver is also configured to: send a NAS ACK in response to the NAS ACK request to the network. The transceiver configured to send the data request is further configured to send a radio resource control (RRC) early data request message to the network; and the transceiver configured to receive the message is configured to receive an RRC connection release message including a connection release indication and a GUTI from the network. The transceiver configured to send the data request is further configured to send a radio resource control (RRC) connection recovery request message to the network; and the transceiver configured to receive the message is configured to receive an RRC connection release message including a connection release indication, data, and a GUTI from the network.

[0186] A further embodiment of the present disclosure includes a core network entity. The core network entity includes a transceiver configured to: send a page for a user equipment (UE) associated with a first global unique temporary identifier (GUTI) to a base station (BS); receive a request associated with at least one of service or context recovery of the paged UE from the BS; and in response to the request, send a message to the BS, the message including: a second GUTI for the paged UE different from the first GUTI, and at least one of data associated with the paging or a connection release indication.

[0187] The core network entity may also include one or more of the following features. For example, the core network entity includes a processor configured to generate a second GUTI in response to a request. The transceiver configured to receive the request is configured to receive an initial UE message including a non-access stratum (NAS) service request; and the transceiver configured to send the message is configured to send a NAS transmission message including data and a second GUTI to the BS. The NAS transmission message includes a NAS service acceptance message, and wherein the NAS service acceptance message includes data and a second GUTI. The NAS transmission message includes: a non-access stratum (NAS) service acceptance message including data, and an information element (IE) including the second GUTI. The NAS transmission message also includes a NAS confirmation (ACK) request, and wherein the transceiver is further configured to: receive a NAS ACK in response to the NAS ACK request from the BS. The transceiver configured to receive the request is configured to receive a UE initial message including a non-access stratum (NAS) service request; and the transceiver configured to send the message is configured to send a UE context release message including a connection release indication and a second GUTI to the BS. The transceiver configured to receive the request is configured to: receive a UE context recovery request message from the BS; and the transceiver configured to send the message is configured to: send a UE context recovery response message including a connection release indication and a second GUTI to the BS.

[0188] A further embodiment of the present disclosure includes a base station (BS). The BS includes a transceiver configured to: receive a data request associated with paging from a user equipment (UE); send a request associated with service or context recovery of the UE to a core network in response to the data request; receive a message in response to the request associated with service or context recovery of the UE from the core network, the message including a global unique temporary identifier (GUTI) and a connection release indication; and send a connection release message including the GUTI to the UE.

[0189] The BS may also include one or more of the following features. For example, the BS includes: wherein the transceiver configured to receive a data request is configured to receive a radio resource control (RRC) early data request message from the UE; and the transceiver configured to send a connection release message is configured to send an RRC early data complete message including a GUTI to the UE. The transceiver configured to receive a message is configured to receive a non-access stratum (NAS) transmission message from the core network, the NAS transmission message including: a NAS service accept message including data associated with paging, an information element (IE) including the GUTI, and a connection release indication. The transceiver configured to receive a request is configured to receive a radio resource control (RRC) early data request message from the UE; and the transceiver configured to send a connection release message is configured to send an RRC connection release message including the GUTI to the UE. The transceiver configured to receive a message is configured to receive a UE context release message including the GUTI as a response from the core network. The transceiver configured to send the request is configured to send a UE context recovery request message to the core network; and the transceiver configured to receive the message is configured to: receive a UE context recovery response message including a GUTI and a connection release indication from the core network. The transceiver is also configured to receive data associated with paging for the UE from the core network; and the transceiver configured to send a connection release message is configured to: send an RRC connection release message including data and the GUTI to the UE.

[0190] A further embodiment of the present disclosure includes a non-transitory computer-readable medium having program code recorded thereon. The non-transitory computer-readable medium includes code for causing a user equipment (UE) to receive a paging associated with a mobile terminated early data transfer (MT-EDT) from a network. The non-transitory computer-readable medium also includes code for causing the UE to send a data request in response to the paging. The non-transitory computer-readable medium also includes code for causing the UE to receive a message in response to the data request from the network, the message including a global unique temporary identifier (GUTI), and at least one of data associated with the paging or a connection release indication.

[0191] The non-transitory computer-readable medium may also include one or more of the following features. For example, the non-transitory computer-readable medium includes: wherein the code for causing the UE to send a data request is also configured to: send a radio resource control (RRC) early data request message to the network; and the code for causing the UE to receive the message is also configured to: receive an RRC early data completion message including data and GUTI from the network. The code for causing the UE to send a data request is also configured to: send a radio resource control (RRC) early data request message to the network; and the code for causing the UE to receive the message is also configured to: receive an RRC connection release message including a connection release indication and GUTI from the network. The code for causing the UE to send a data request is also configured to: send a radio resource control (RRC) connection recovery request message to the network; and the code for causing the UE to receive the message is also configured to: receive an RRC connection release message including a connection release indication, data, and GUTI from the network.

[0192] A further embodiment of the present disclosure includes a non-transitory computer-readable medium having program code recorded thereon. The non-transitory computer-readable medium includes code for causing a core network entity to send a page for a user equipment (UE) associated with a first global unique temporary identifier (GUTI) to a base station (BS). The non-transitory computer-readable medium also includes code for causing the core network entity to receive a request associated with at least one of a service or context recovery for the paged UE from the BS. The non-transitory computer-readable medium also includes code for causing the core network entity to send a message to the BS in response to the request, the message including: a second GUTI for the paged UE different from the first GUTI, and at least one of data associated with the paging or a connection release indication.

[0193] The non-transitory computer-readable medium may also include one or more of the following features. For example, the non-transitory computer-readable medium includes code for causing the core network entity to generate a second GUTI in response to the request. The code for causing the core network entity to receive the request is configured to receive an initial UE message including a non-access stratum (NAS) service request; and the code for causing the core network entity to send the message is configured to send a NAS transmission message including data and a second GUTI to the BS. The NAS transmission message includes a NAS service acceptance message, and wherein the NAS service acceptance message includes data and a second GUTI. The NAS transmission message includes: a non-access stratum (NAS) service acceptance message including data, and an information element (IE) including the second GUTI. The NAS transmission message also includes a NAS confirmation (ACK) request, and wherein the non-transitory computer-readable medium also includes: receiving a NAS ACK in response to the NAS ACK request from the BS. The code for causing the core network entity to receive the request is configured to: receive a UE initial message including a non-access stratum (NAS) service request; and the code for causing the core network entity to send the message is configured to: send a UE context release message including a connection release indication and a second GUTI to the BS. The code for causing the core network entity to receive the request is configured to receive a UE context restoration request message from the BS; and the code for causing the core network entity to send the message is configured to: send a UE context restoration response message including a connection release indication and a second GUTI to the BS.

[0194] A further embodiment of the present disclosure includes a non-transitory computer-readable medium having program code recorded thereon. The non-transitory computer-readable medium includes code for causing a base station (BS) to receive a data request associated with paging from a user equipment (UE). The non-transitory computer-readable medium also includes code for causing the BS to send a request associated with a service or context recovery of the UE to a core network in response to the data request. The non-transitory computer-readable medium also includes code for causing the BS to receive a message from the core network in response to a request associated with a service or context recovery of the UE, the message including a global unique temporary identifier (GUTI) and a connection release indication. The non-transitory computer-readable medium also includes code for causing the BS to send a connection release message including the GUTI to the UE.

[0195] The non-transitory computer-readable medium may also include one or more of the following features. For example, the non-transitory computer-readable medium includes: wherein the code for causing the BS to receive the request is configured to: receive a radio resource control (RRC) early data request message from the UE; and the code for causing the BS to send a connection release message is configured to send an RRC early data complete message including a GUTI to the UE. The code for causing the BS to receive the message is configured to: receive a non-access stratum (NAS) transmission message from the core network, the NAS transmission message including: a NAS service accept message including data associated with paging, an information element (IE) including the GUTI, and a connection release indication. The code for causing the BS to receive the request is configured to receive a radio resource control (RRC) early data request message from the UE; and the code for causing the BS to send a connection release message is configured to send an RRC connection release message including the GUTI to the UE. The code for causing the BS to receive the message is configured to: receive a UE context release message including the GUTI as a response from the core network. The code for causing the BS to send a request is configured to send a UE context recovery request message to the core network; and the code for causing the BS to receive a message is configured to receive a UE context recovery response message including a GUTI and a connection release indication from the core network. The code for causing the core network entity to send a connection release message is configured to send an RRC connection release message including data and the GUTI to the UE.

[0196] A further embodiment of the present disclosure includes a user equipment (UE). The user equipment includes means for receiving a paging associated with a mobile terminated early data transfer (MT-EDT) from a network. The user equipment also includes means for sending a data request to the network in response to the paging. The user equipment also includes means for receiving a message in response to the data request from the network, the message including a globally unique temporary identifier (GUTI), and at least one of data associated with the paging or a connection release indication.

[0197] The UE may also include one or more of the following features. For example, the UE includes: wherein the unit for sending the data request is also configured to send a radio resource control (RRC) early data request message to the network; and the unit for receiving the message is configured to receive an RRC early data completion message including data and a GUTI from the network. The RRC early data completion message includes a non-access stratum (NAS) service acceptance message, and wherein the NAS service acceptance message includes data and a GUTI. The RRC early data completion message includes: a non-access stratum (NAS) service acceptance message including data, and an information element (IE) including a GUTI. The RRC early data completion message also includes a non-access stratum (NAS) confirmation (ACK) request, and wherein the UE also includes a unit for sending a NAS ACK to the network in response to the NAS ACK request. The unit for sending the data request is also configured to send a radio resource control (RRC) early data request message to the network; and the unit for receiving the message is configured to receive an RRC connection release message including a connection release indication and a GUTI from the network. The unit for sending the data request is further configured to send a radio resource control (RRC) connection resumption request message to the network; and the unit for receiving the message is configured to receive an RRC connection release message including a connection release indication, data, and GUTI from the network.

[0198] A further embodiment of the present disclosure includes a core network entity. The core network entity includes: a unit for sending a page for a user equipment (UE) associated with a first global unique temporary identifier (GUTI) to a base station (BS). The core network entity also includes: a unit for receiving a request associated with at least one of a service or context recovery of the paged UE from the BS. The core network entity also includes: a unit for sending a message to the BS in response to the request, the message including: a second GUTI for the paged UE different from the first GUTI, and at least one of data associated with the paging or a connection release indication.

[0199] The core network entity may also include one or more of the following features. For example, the core network entity includes: a unit for generating a second GUTI in response to the request. The unit for receiving the request is configured to receive an initial UE message including a non-access stratum (NAS) service request; and the unit for sending the message is configured to send a NAS transfer message including data and a second GUTI to the BS. The NAS transfer message includes a NAS service acceptance message, and wherein the NAS service acceptance message includes data and a second GUTI. The NAS transfer message includes: a non-access stratum (NAS) service acceptance message including data, and an information element (IE) including the second GUTI. The NAS transfer message also includes a NAS confirmation (ACK) request, and wherein the core network entity also includes receiving a NAS ACK in response to the NAS ACK request from the BS. The unit for receiving the request is configured to receive a UE initial message including a non-access stratum (NAS) service request; and the unit for sending the message is configured to send a UE context release message including a connection release indication and a second GUTI to the BS. The unit for receiving the request is configured to receive a UE context restoration request message from the BS; and the unit for sending the message is configured to send a UE context restoration response message including a connection release indication and a second GUTI to the BS.

[0200] A further embodiment of the present disclosure includes a base station (BS). The base station includes: a unit for receiving a data request associated with paging from a user equipment (UE). The base station also includes: a unit for sending a request associated with service or context recovery of the UE to a core network in response to the data request. The base station also includes: a unit for receiving a message in response to the request associated with service or context recovery of the UE from the core network, the message including a global unique temporary identifier (GUTI) and a connection release indication. The base station also includes a unit for sending a connection release message including the GUTI to the UE.

[0201] The BS may also include one or more of the following features. For example, the BS includes: wherein the unit for receiving the request is configured to receive a radio resource control (RRC) early data request message from the UE; and the unit for sending the connection release message is configured to send an RRC early data complete message including the GUTI to the UE. The unit for receiving the message is configured to receive a non-access stratum (NAS) transmission message from the core network, the NAS transmission message including: a NAS service accept message including data associated with paging, an information element (IE) including the GUTI, and a connection release indication. The unit for receiving the request is configured to receive a radio resource control (RRC) early data request message from the UE; and the unit for sending the connection release message is configured to send an RRC connection release message including the GUTI to the UE. The unit for receiving the message is configured to receive a UE context release message including the GUTI as a response from the core network. The unit for sending the request is configured to send a UE context recovery request message to the core network; and the unit for receiving the message is configured to receive a UE context recovery response message including the GUTI and the connection release indication from the core network. The unit for sending a connection release message is configured to send an RRC connection release message including data and a GUTI to the UE.

[0202] Information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0203] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed using a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may also be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such structure).

[0204] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on a computer-readable medium as one or more instructions or codes, or transmitted via a computer-readable medium. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardware lines, or a combination of any of these items. Features that implement the functions may also be physically located in multiple locations, including being distributed so that parts of the functions are implemented in different physical locations. In addition, as used herein (including in the claims), "or" as used in a list item (e.g., a list item ending with, for example, "at least one of" or "one or more of") indicates an inclusive list, so that, for example, the list [at least one of A, B, or C] means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0205] As those skilled in the art will now understand, and depending on the specific application on site, many modifications, substitutions and changes may be made to the materials, devices, structures and methods of use of the apparatus of the present disclosure without departing from the spirit and scope of protection of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the scope of the specific embodiments shown and described herein (because the specific embodiments are only examples thereof), but more precisely, should fully correspond to the scope of the claims attached hereto and their functional equivalents.

Claims

1. A method of wireless communication, comprising: receiving, by a user equipment (UE) from a network, a paging associated with mobile terminated early data transfer (MT-EDT); In response to the paging, the UE sends a data request to the network; as well as A message in response to the data request is received by the UE from the network, the message comprising: Globally Unique Temporary Identifier (GUTI); as well as At least one of data associated with the paging or a connection release indication.

2. The method according to claim 1, wherein: The sending the data request comprises: sending, by the UE, a radio resource control (RRC) early data request message to the network; and The receiving the message comprises: An RRC Early Data Complete message including the data and the GUTI is received by the UE from the network.

3. The method according to claim 2, wherein: The RRC Early Data Complete message includes a Non-Access Stratum (NAS) Service Accept message, and wherein the NAS Service Accept message includes the data and the GUTI.

4. The method according to claim 2, wherein: The RRC early data complete message includes: a non-access stratum (NAS) service accept message including the data; and An information element (IE) comprising the GUTI.

5. The method according to claim 2, wherein: The RRC Early Data Complete message also includes a Non-Access Stratum (NAS) Acknowledgement (ACK) request, and wherein the method further includes: In response to the NAS ACK request, the UE sends a NAS ACK to the network.

6. The method according to claim 1, wherein: The sending the data request comprises: sending, by the UE, a radio resource control (RRC) early data request message to the network; and The receiving the message comprises: An RRC connection release message including the connection release indication and the GUTI is received by the UE from the network.

7. The method according to claim 1, wherein: The sending the data request comprises: sending, by the UE, a radio resource control (RRC) connection restoration request message to the network; and The receiving the message comprises: An RRC connection release message including the connection release indication, the data and the GUTI is received by the UE from the network.

8. A method of wireless communication, comprising: sending, by a core network entity, a page for a user equipment (UE) associated with a first globally unique temporary identifier (GUTI) to a base station (BS); receiving, by the core network entity, from the BS, a request associated with at least one of service or context recovery of the paged UE; as well as The core network entity sends a message to the BS in response to the request, where the message includes: a second GUTI for the paged UE different from the first GUTI; as well as At least one of data associated with the paging or a connection release indication.

9. The method according to claim 8, further comprising: The core network entity generates the second GUTI in response to the request.

10. The method according to claim 8, wherein: The receiving the request comprises: receiving, by the core network entity, an initial UE message including a non-access stratum (NAS) service request; and The sending of the message comprises: A NAS transmission message including the data and the second GUTI is sent by the core network entity to the BS.

11. The method according to claim 10, wherein: The NAS transport message comprises a NAS service accept message, and wherein the NAS service accept message comprises the data and the second GUTI.

12. The method according to claim 10, wherein: The NAS transmission message includes: a non-access stratum (NAS) service accept message including the data; and An information element (IE) including the second GUTI.

13. The method according to claim 10, wherein: The NAS transport message also includes a NAS acknowledgement (ACK) request, and wherein the method further includes: A NAS ACK is received by the core network entity from the BS in response to the NAS ACK request.

14. The method of claim 8, wherein: The receiving the request comprises: receiving, by the core network entity, a UE initialization message including a non-access stratum (NAS) service request; and The sending of the message comprises: The core network entity sends a UE context release message including the connection release indication and the second GUTI to the BS.

15. The method of claim 8, wherein: The receiving the request comprises: The core network entity receives a UE context restoration request message; and The sending of the message comprises: The core network entity sends a UE context recovery response message including the connection release indication and the second GUTI to the BS.

16. A method of wireless communication, comprising: receiving, by a base station (BS), a data request associated with paging from a user equipment (UE); In response to the data request, the BS sends a request associated with service or context recovery of the UE to a core network; receiving, by the BS, from the core network a message in response to the request associated with the service or the context resumption of the UE, the message including a Globally Unique Temporary Identifier (GUTI) and a connection release indication; and The BS sends a connection release message including the GUTI to the UE.

17. The method of claim 16, wherein: The receiving the data request comprises: receiving, by the BS, a radio resource control (RRC) early data request message from the UE; and The sending of the connection release message comprises: The BS sends an RRC early data complete message including the GUTI to the UE.

18. The method according to claim 16, wherein: The receiving the message comprises: A non-access stratum (NAS) transport message is received by the BS from the core network, the NAS transport message comprising: a NAS service accept message including data associated with the paging, an information element (IE) including the GUTI, and the connection release indication.

19. The method of claim 16, wherein: The receiving the data request comprises: receiving, by the BS, a radio resource control (RRC) early data request message from the UE; and The sending of the connection release message comprises: The BS sends an RRC connection release message including the GUTI to the UE.

20. The method according to claim 16, wherein: The receiving the message comprises: A UE context release message including the GUTI is received by the BS from the core network in response.

21. The method of claim 16, wherein: The sending the request comprises: The UE sends a UE context recovery request message to the core network; and The receiving the message comprises: A UE context restoration response message including the GUTI and the connection release indication is received by the BS from the core network.

22. The method according to claim 21, further comprising: receiving, by the BS from the core network, data associated with the paging for the UE, Wherein, sending the connection release message includes: The BS sends an RRC connection release message including the data and the GUTI to the UE.

23. A user equipment (UE), comprising: A transceiver configured to: receiving a page associated with a mobile terminated early data transfer (MT-EDT) from the network; In response to the paging, sending a data request; as well as receiving a message in response to the data request from the network, the message comprising: Globally Unique Temporary Identifier (GUTI); as well as At least one of data related to the paging or a connection release indication.

24. The UE according to claim 23, wherein: The transceiver configured to send the data request is further configured to: sending a radio resource control (RRC) early data request message to the network; and The transceiver configured to receive the message is configured to: An RRC Early Data Complete message including the data and the GUTI is received from the network.

25. The UE according to claim 24, wherein: The RRC Early Data Complete message includes a Non-Access Stratum (NAS) Service Accept message, and wherein the NAS Service Accept message includes the data and the GUTI.

26. The UE according to claim 24, wherein: The RRC early data complete message includes: a non-access stratum (NAS) service accept message including the data; and An information element (IE) comprising the GUTI.

27. The UE according to claim 24, wherein: The RRC Early Data Complete message also includes a Non-Access Stratum (NAS) Acknowledgement (ACK) request, and wherein the transceiver is further configured to: In response to the NAS ACK request, a NAS ACK is sent to the network.

28. The UE according to claim 23, wherein: The transceiver configured to send the data request is further configured to: sending a radio resource control (RRC) early data request message to the network; and The transceiver configured to receive the message is configured to: An RRC connection release message including the connection release indication and the GUTI is received from the network.

29. The UE according to claim 23, wherein: The transceiver configured to send the data request is further configured to: sending a radio resource control (RRC) connection restoration request message to the network; and The transceiver configured to receive the message is configured to: An RRC connection release message including the connection release indication, the data, and the GUTI is received from the network.

30. The UE according to claim 23, wherein: The transceiver configured to receive the message is configured to: A radio resource control (RRC) message including the GUTI based on a non-access stratum message authentication code (NAS-MAC) is received from the network.

Images