Wireless communication method, user equipment and network entity

Abstract

Some techniques and apparatuses described herein enable synchronization of a user equipment (UE) identifier between a UE and a base station when the UE identifier is reallocated, which enables the UE to use preconfigured uplink resources to reduce latency, reduce signaling overhead, etc. For example, some techniques and apparatuses described herein enable the UE to use preconfigured uplink resources when a UE identifier is reallocated between configuration of the preconfigured uplink resources and the UE sending uplink data using the preconfigured uplink resources.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 62 / 914,098, filed October 11, 2019, entitled “Synchronizing AUSER EQUIPMENT IDENTIFIER FOR PRECONFIGURED UPLINK RESOURCES,” and U.S. Non-Provisional Patent Application No. 16 / 948,679, filed September 29, 2020, entitled “Synchronizing AUSER EQUIPMENT IDENTIFIER FOR PRECONFIGURED UPLINK RESOURCES,” which are expressly incorporated herein by reference. Technical Field

[0003] Various aspects of this disclosure generally relate to wireless communications, and specifically to techniques and apparatus for synchronizing user equipment identifiers used for pre-configuring uplink resources. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] Wireless communication networks may include multiple base stations (BSs) capable of supporting communication between multiple user equipments (UEs). UEs can communicate with the BS via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the BS to the UE, while an uplink (or reverse link) refers to the communication link from the UE to the BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, Access Point (AP), Radio Headend, Transmit / Receive Point (TRP), 5G BS, 5G Node B, etc.

[0006] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, and even global levels. 5G, also known as New Radio (NR), is a set of enhancements to the LTE mobile standard issued by the 3rd Generation Partnership Project (3GPP). 5G is designed to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and better integrating with other open standards (using OFDM with a cyclic prefix (CP-OFDM) on the downlink (DL), and using CP-OFDM and / or SC-FDM (e.g., also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink (UL), as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies, and carrier aggregation. However, with the continued growth in demand for mobile broadband access, further improvements to LTE and 5G technologies are needed. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0007] In some cases, the base station may be unaware of the User Equipment (UE) identifier reassignment and may continue to store the first UE identifier in the UE's UE context. If the UE enters RRC idle mode and then later enters RRC connected mode, the UE will send a second UE identifier to the base station, and the base station will store the second UE identifier in association with the UE's UE context. However, for pre-configured uplink resources, the UE can send uplink data to the base station without first establishing a new RRC connection. In this case, the UE will send the second UE identifier along with the uplink data, but the base station will not store the second UE identifier in memory in association with the UE. As a result, the base station may be unable to verify the UE and / or may discard the uplink data.

[0008] Some of the techniques and apparatus described herein enable the synchronization of UE identifiers between the UE and the base station during UE identifier reallocation. This allows the UE to use pre-configured uplink resources to reduce latency, signaling overhead, and other factors. For example, some of the techniques and apparatus described herein enable the UE to use pre-configured uplink resources when a UE identifier reallocation occurs between the configuration of pre-configured uplink resources and the UE's use of pre-configured uplink resources to transmit uplink data.

[0009] In some aspects, a wireless communication method performed by a UE may include: sending a connection request to a base station, wherein the connection request indicates a first UE identifier for preconfiguring uplink resources; receiving configuration from the base station for preconfiguring uplink resources; receiving a UE identifier reallocation message instructing the UE to replace the first UE identifier with a second UE identifier; and sending a request to the base station, at least in part based on the received UE identifier reallocation message, to update the first UE identifier to the second UE identifier for the preconfigured uplink resources.

[0010] In some aspects, a wireless communication method performed by a UE may include: sending a connection request to a base station, wherein the connection request indicates a UE identifier that identifies the UE in a core network; receiving from the base station a configuration for preconfigured uplink resource (PUR), wherein the configuration indicates the uplink resource and the PUR identifier; and sending a preconfigured uplink message to the base station in the uplink resource, wherein the preconfigured uplink message includes uplink data, the UE identifier, and the PUR identifier.

[0011] In some aspects, a wireless communication method performed by a base station may include: receiving a connection request from a UE, wherein the connection request indicates a first UE identifier for preconfiguring uplink resources; sending a configuration for preconfiguring uplink resources to the UE; receiving a request to update the first UE identifier to a second UE identifier for the preconfigured uplink resources; and updating the first UE identifier to the second UE identifier in a memory of the base station storing a context associated with the preconfigured uplink resources, based at least in part on receiving the request to update the first UE identifier to the second UE identifier.

[0012] In some aspects, a wireless communication method performed by a base station may include: receiving a connection request from a UE, wherein the connection request indicates a UE identifier that identifies the UE in a core network; sending a configuration for a PUR to the UE, wherein the configuration indicates uplink resources and a PUR identifier; and receiving a pre-configured uplink message from the UE in the uplink resources, wherein the pre-configured uplink message includes uplink data, the UE identifier, and the PUR identifier.

[0013] In some aspects, a method performed by a core network device may include: establishing a connection with a base station, wherein the connection is associated with a UE and a first UE identifier, wherein the first UE identifier identifies the UE in the core network and is associated with pre-configured uplink resources for the UE; sending a UE identifier reallocation message to the UE via the base station instructing the UE to replace the first UE identifier with a second UE identifier; and sending a request to the base station to update the first UE identifier to the second UE identifier for the pre-configured uplink resources.

[0014] In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: send a connection request to a base station, wherein the connection request indicates a first UE identifier for pre-configuring uplink resources; receive configuration from the base station for pre-configuring uplink resources; receive a UE identifier reallocation message instructing the UE to replace the first UE identifier with a second UE identifier; and, at least in part based on the received UE identifier reallocation message, send a request to the base station to update the first UE identifier to the second UE identifier for pre-configured uplink resources.

[0015] In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: send a connection request to a base station, wherein the connection request indicates a UE identifier that identifies the UE in the core network; receive configuration for a PUR from the base station, wherein the configuration indicates uplink resources and a PUR identifier; and send a pre-configured uplink message to the base station in the uplink resources, wherein the pre-configured uplink message includes uplink data, the UE identifier, and the PUR identifier.

[0016] In some aspects, a base station for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive a connection request from a UE, wherein the connection request indicates a first UE identifier for pre-configuring uplink resources; send configuration to the UE for pre-configuring the uplink resources; receive a request to update the first UE identifier to a second UE identifier for the pre-configured uplink resources; and update the first UE identifier to the second UE identifier in the base station's memory, storing the context associated with the pre-configured uplink resources, based at least in part on receiving the request to update the first UE identifier to the second UE identifier.

[0017] In some aspects, a base station for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive a connection request from a UE, wherein the connection request indicates a UE identifier that identifies the UE in the core network; send a configuration for a PUR to the UE, wherein the configuration indicates uplink resources and a PUR identifier; and receive a pre-configured uplink message from the UE in the uplink resources, wherein the pre-configured uplink message includes uplink data, the UE identifier, and the PUR identifier.

[0018] In some aspects, a core network device may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: establish a connection with a base station, wherein the connection is associated with a UE and a first UE identifier, wherein the first UE identifier identifies the UE in the core network and is associated with pre-configured uplink resources for the UE; send a UE identifier reallocation message to the UE via the base station instructing the UE to replace the first UE identifier with a second UE identifier; and send a request to the base station to update the first UE identifier to the second UE identifier for the pre-configured uplink resources.

[0019] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of the UE, the one or more instructions may cause the one or more processors to: send a connection request to a base station, wherein the connection request indicates a first UE identifier for pre-configuring uplink resources; receive configuration from the base station for pre-configuring uplink resources; receive a UE identifier reallocation message instructing the UE to replace the first UE identifier with a second UE identifier; and, at least in part based on the receipt of the UE identifier reallocation message, send a request to the base station to update the first UE identifier to the second UE identifier for the pre-configured uplink resources.

[0020] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of the UE, the one or more instructions may cause the one or more processors to: send a connection request to a base station, wherein the connection request indicates a UE identifier that identifies the UE in the core network; receive configuration for a PUR from the base station, wherein the configuration indicates uplink resources and a PUR identifier; and send a pre-configured uplink message to the base station in the uplink resources, wherein the pre-configured uplink message includes uplink data, the UE identifier, and the PUR identifier.

[0021] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause the one or more processors to: receive a connection request from a UE, wherein the connection request indicates a first UE identifier for preconfiguring uplink resources; send configuration to the UE for preconfiguring the uplink resources; receive a request to update the first UE identifier to a second UE identifier for the preconfigured uplink resources; and update the first UE identifier to the second UE identifier in a memory of the base station storing a context associated with the preconfigured uplink resources, based at least in part on the receipt of the request to update the first UE identifier to the second UE identifier.

[0022] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause the one or more processors to: receive a connection request from a UE, wherein the connection request indicates a UE identifier that identifies the UE in the core network; send a configuration for a PUR to the UE, wherein the configuration indicates uplink resources and a PUR identifier; and receive a pre-configured uplink message from the UE in the uplink resources, wherein the pre-configured uplink message includes uplink data, the UE identifier, and the PUR identifier.

[0023] In some aspects, a non-transitory computer-readable medium may store one or more instructions. When executed by one or more processors of a core network device, the one or more instructions may cause the one or more processors to: establish a connection with a base station, wherein the connection is associated with a UE and a first UE identifier, wherein the first UE identifier identifies the UE in the core network and is associated with pre-configured uplink resources for the UE; send a UE identifier reallocation message to the UE via the base station instructing the UE to replace the first UE identifier with a second UE identifier; and send a request to the base station to update the first UE identifier to the second UE identifier for the pre-configured uplink resources.

[0024] In some aspects, an apparatus for wireless communication may include: a means module for sending a connection request to a base station, wherein the connection request indicates a first UE identifier for pre-configuring uplink resources; a means module for receiving from the base station a configuration for pre-configuring uplink resources; a means module for receiving a UE identifier reallocation message instructing the means to replace the first UE identifier with a second UE identifier; and a means module for sending to the base station, at least in part, a request to update the first UE identifier to the second UE identifier for pre-configured uplink resources based on the received UE identifier reallocation message.

[0025] In some aspects, an apparatus for wireless communication may include: an apparatus module for sending a connection request to a base station, wherein the connection request indicates a UE identifier that identifies the apparatus in a core network; an apparatus module for receiving a configuration for a PUR from the base station, wherein the configuration indicates uplink resources and a PUR identifier; and an apparatus for sending a pre-configured uplink message to the base station in the uplink resources, wherein the pre-configured uplink message includes uplink data, a UE identifier, and a PUR identifier.

[0026] In some aspects, an apparatus for wireless communication may include: an apparatus module for receiving a connection request from a UE, wherein the connection request indicates a first UE identifier for preconfiguring uplink resources; an apparatus module for transmitting a configuration for preconfiguring uplink resources to the UE; an apparatus module for receiving a request to update the first UE identifier to a second UE identifier for the preconfigured uplink resources; and an apparatus module for updating the first UE identifier to the second UE identifier in a memory storing a context associated with the preconfigured uplink resources, based at least in part on receiving the request to update the first UE identifier to the second UE identifier.

[0027] In some aspects, an apparatus for wireless communication may include: an apparatus module for receiving a connection request from a UE, wherein the connection request indicates a UE identifier that identifies the UE in a core network; an apparatus module for sending a configuration for a PUR to the UE, wherein the configuration indicates uplink resources and a PUR identifier; and an apparatus for receiving a pre-configured uplink message from the UE in the uplink resources, wherein the pre-configured uplink message includes uplink data, a UE identifier, and a PUR identifier.

[0028] In some aspects, an apparatus may include: an apparatus module for establishing a connection with a base station, wherein the connection is associated with a UE and a first UE identifier, wherein the first UE identifier identifies the UE in a core network and is associated with pre-configured uplink resources for the UE; an apparatus module for sending a UE identifier reallocation message to the UE via the base station instructing the UE to replace the first UE identifier with a second UE identifier; and an apparatus module for sending a request to the base station to update the first UE identifier to the second UE identifier for the pre-configured uplink resources.

[0029] In some aspects, a wireless communication method performed by a UE may include: sending a connection request to a base station, wherein the connection request indicates a first UE identifier that identifies the UE in a core network; receiving configuration for a PUR from the base station, wherein the configuration indicates uplink resources and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier; and communicating with the base station at least in part based on the configuration.

[0030] In some aspects, a wireless communication method performed by a base station may include: receiving a connection request from a UE, wherein the connection request indicates a first UE identifier that identifies the UE in a core network; sending a configuration for a PUR to the UE, wherein the configuration indicates an uplink resource and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier; and communicating with the UE at least in part based on the configuration.

[0031] In some aspects, a UE for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: send a connection request to a base station, wherein the connection request indicates a first UE identifier that identifies the UE in the core network; receive configuration for a PUR from the base station, wherein the configuration indicates uplink resources and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier; and communicate with the base station at least in part based on the configuration.

[0032] In some aspects, a base station for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: receive a connection request from a UE, wherein the connection request indicates a first UE identifier that identifies the UE in the core network; send a configuration for a PUR to the UE, wherein the configuration indicates an uplink resource and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier; and communicate with the UE at least in part based on the configuration.

[0033] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of the UE, the one or more instructions may cause the one or more processors to: send a connection request to a base station, wherein the connection request indicates a first UE identifier that identifies the UE in the core network; receive configuration for a PUR from the base station, wherein the configuration indicates uplink resources and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier; and communicate with the base station at least in part based on the configuration.

[0034] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. When executed by one or more processors of a base station, the one or more instructions may cause the one or more processors to: receive a connection request from a UE, wherein the connection request indicates a first UE identifier that identifies the UE in the core network; send a configuration for a PUR to the UE, wherein the configuration indicates an uplink resource and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier; and communicate with the UE at least in part based on the configuration.

[0035] In some aspects, an apparatus for wireless communication may include: an apparatus module for sending a connection request to a base station, wherein the connection request indicates a first UE identifier that identifies the apparatus in a core network; an apparatus module for receiving a configuration for a PUR from the base station, wherein the configuration indicates uplink resources and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier; and an apparatus module for communicating with the base station at least in part based on the configuration.

[0036] In some aspects, an apparatus for wireless communication may include: an apparatus module for receiving a connection request from a UE, wherein the connection request indicates a first UE identifier that identifies the UE in a core network; an apparatus module for sending a configuration for a PUR to the UE, wherein the configuration indicates an uplink resource and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier; and an apparatus module for communicating with the UE at least in part based on the configuration.

[0037] The terms generally include, as described in the accompanying drawings and description, methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment, core network equipment, and / or processing systems illustrated in the drawings and description.

[0038] The features and technical advantages of the examples according to this disclosure have been outlined rather broadly above to facilitate a better understanding of the detailed description that follows. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, their organization and operation, and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each drawing is provided for illustrative and descriptive purposes and is not intended to define limitations of the claims. Attached Figure Description

[0039] Figure 1This is a diagram illustrating an example of a wireless communication network.

[0040] Figure 2 This is a diagram illustrating an example of a base station communicating with a UE in a wireless communication network.

[0041] Figure 3 This is a diagram illustrating an example of UE identifier reassignment.

[0042] Figure 4 This is a diagram illustrating an example of configuring and using pre-configured uplink resources.

[0043] Figure 5-Figure 8 This is a diagram illustrating an example of UE identifiers used for pre-configuring uplink resources.

[0044] Figures 9-13 This is a flowchart of a wireless communication method.

[0045] Figure 14 It is a data flow diagram that shows the data flow between different modules / device modules / components in the example device.

[0046] Figure 15 This is a diagram illustrating an example of a hardware implementation using a processing system.

[0047] Figure 16 It is a data flow diagram that shows the data flow between different modules / device modules / components in the example device.

[0048] Figure 17 This is a diagram illustrating an example of a hardware implementation using a processing system.

[0049] Figure 18 It is a data flow diagram that shows the data flow between different modules / device modules / components in the example device.

[0050] Figure 19 This is a diagram illustrating an example of a hardware implementation using a processing system. Detailed Implementation

[0051] The detailed description following, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as a representation of configurations in which the concepts described herein can be practiced. The detailed description includes specific details and is intended to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, to avoid obscuring these concepts, well-known structures and components are shown in block diagram form.

[0052] Several aspects of a telecommunications system will now be presented with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0053] For example, an element, any part of an element, or any combination of elements may be implemented using a "processing system" comprising one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system may execute software. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or others.

[0054] Therefore, in one or more example embodiments, the described functionality can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, these functions can be stored on or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium can be any available medium accessible to a computer. By way of example, and not limitation, such a computer-readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc ROM (CD-ROM) or other optical disc storage, magnetic disk storage or other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures.

[0055] It should be noted that although terms commonly associated with 5G or NR radio access technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or RATs after 5G (e.g., 6G).

[0056] Figure 1This is a schematic diagram illustrating a wireless network 100 in which various aspects of this disclosure can be practiced. The wireless network 100 can be an LTE network or some other wireless network, such as a 5G network. The wireless network 100 can include multiple BS110s (shown as BS110a, BS110b, BS110c, and BS110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and can also be referred to as a base station, 5G BS, Node B, gNB, 5G NB, access point, Transmit / Receive Point (TRP), etc. Each BS can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the coverage area of ​​a BS and / or the BS subsystem serving that coverage area, depending on the context in which the term is used.

[0057] A Base Station (BS) can provide communication coverage for macrocells, picocells, femtocells, and / or another type of cell. A macrocell can cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access for UEs with service subscriptions. A picocell can cover a relatively small geographic area and allow unrestricted access for UEs with service subscriptions. A femtocell can cover a relatively small geographic area (e.g., a home) and allow restricted access for UEs associated with that femtocell (e.g., UEs in a Closed Subscriber Group (CSG)). A BS for a macrocell can be referred to as a macro BS. A BS for a picocell can be referred to as a pico BS. A BS for a femtocell can be referred to as a femtocell BS or a home BS. Figure 1 In the example shown, BS110a can be a macro BS of macro cell 102a, BS110b can be a pico BS of pico cell 102b, and BS110c can be a femto BS of femto cell 102c. A BS can support one or more (e.g., three) cells. The terms “eNB,” “base station,” “5G BS,” “gNB,” “TRP,” “AP,” “Node B,” “5G NB,” and “cell” are used interchangeably herein.

[0058] In some examples, the cell is not necessarily stationary, and the geographical area of ​​the cell can move depending on the location of the mobile BS. In some examples, the BS can use any suitable transport network to interconnect with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 via various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.).

[0059] The wireless network 100 may also include relay stations. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and send data transmissions to a downstream station (e.g., a UE or a BS). A relay station can also be a UE capable of relaying transmissions for other UEs. Figure 1In the example shown, relay station 110d can communicate with macro BS110a and UE 120d to facilitate communication between BS110a and UE 120d. A relay station can also be referred to as a relay BS, relay base station, relay, etc.

[0060] Wireless network 100 can be a heterogeneous network comprising different types of Base Stations (BSs) (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs can have different transmit power levels, different coverage areas, and different effects on interference in wireless network 100. For example, macro BSs can have high transmit power levels (e.g., 5 to 40 watts), while pico BSs, femto BSs, and relay BSs can have lower transmit power levels (e.g., 0.1 to 2 watts).

[0061] Network controller 130 can be coupled to a set of Base Stations (BSs) and can provide coordination and control for these BSs. Network controller 130 can communicate with the BSs via backhaul. The BSs can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0062] UEs 120 (e.g., 120a, 120b, 120c) may be distributed throughout the wireless network 100, and each UE may be fixed or mobile. A UE may also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. A UE may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or equipment, a biosensor / device, a wearable device (smartwatch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet)), an entertainment device (e.g., a music or video device, or a satellite radio), a vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, or any other suitable device configured to communicate via wireless or wired media.

[0063] Some UEs can be considered Machine-Type Communication (MTC) or Evolved or Enhanced Machine-Type Communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, instruments, monitors, location tags, etc., which can communicate with base stations, another device (e.g., remote devices), or some other entity. Wireless nodes can provide connectivity to networks (e.g., wide area networks such as the Internet or cellular networks) via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices, and / or can be implemented as NB-IoT (Narrowband Internet of Things) devices. Some UEs can be considered Customer Premises Equipment (CPE). UE 120 can be included within a housing that houses the components of UE 120, such as processor components, memory components, etc.

[0064] Generally, any number of wireless networks can be deployed in a given geographical area. Each wireless network can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology, air interface, etc. A frequency can also be referred to as a carrier, channel, etc. Each frequency can support a single RAT in a given geographical area to avoid interference between wireless networks using different RATs. In some cases, 5G RAT networks can be deployed.

[0065] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station) allocates resources for communication between some or all devices and equipment within the scheduling entity's service area or cell. In this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, the subordinate entities utilize the resources allocated by the scheduling entity.

[0066] A base station is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity, scheduling resources for one or more subordinate entities (e.g., one or more other UEs). In this example, the UE acts as the scheduling entity, while other UEs utilize the resources scheduled by that UE for wireless communication. A UE can act as a scheduling entity in peer-to-peer (P2P) networks and / or mesh networks. In the mesh network example, in addition to communicating with a scheduling entity, UEs can optionally communicate directly with each other.

[0067] Therefore, in a wireless communication network with scheduled access to time-frequency resources and with cellular, P2P, and mesh configurations, the scheduling entity and one or more subordinate entities can communicate using the scheduled resources.

[0068] Devices of the wireless network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, devices of the wireless network 100 can communicate using an operating band with a first frequency range (FR1) spanning from 410 MHz to 7.125 GHz, and / or can communicate using an operating band with a second frequency range (FR2) spanning from 24.25 GHz to 52.6 GHz. Frequency ranges between FR1 and FR2 are sometimes referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. Similarly, although FR2 differs from the extremely high frequency (EHF) band (30 GHz to 300 GHz) recognized as the "millimeter wave" band by the International Telecommunication Union (ITU), FR2 is often referred to as the "millimeter wave" band. Therefore, unless otherwise specifically stated, it should be understood that, if used herein, the terms "sub-6GHz," etc., can broadly refer to frequencies less than 6GHz, frequencies within FR1, and / or mid-band frequencies (e.g., greater than 7.125GHz). Similarly, unless otherwise specifically stated, it should be understood that, if used herein, the terms "millimeter wave," etc., can broadly refer to frequencies within the EHF band, frequencies within FR2, and / or mid-band frequencies (e.g., less than 24.25GHz). It is anticipated that the frequencies included in FR1 and FR2 may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0069] As indicated above, Figure 1 Provided as an example only. Other examples may differ from those provided. Figure 1 described.

[0070] Figure 2 Block diagram 200 shows the design of base station 110 and UE 120, wherein base station 110 and UE 120 can be Figure 1 One of the base stations and one of the UEs. Base station 110 may be equipped with T antennas 234a to 234t, and UE 120 may be equipped with R antennas 252a to 252r, where typically T≥1 and R≥1.

[0071] At base station 110, transmitting processor 220 can receive data for one or more UEs from data source 212, select a modulation and coding scheme (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for that UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. Transmitting processor 220 can also process system information (e.g., for semi-static resource partitioning information (SRPI) and so on) and control information (e.g., CQI requests, grants, upper-layer signaling, etc.), and provide overhead symbols and control symbols. Transmitting processor 220 can also generate reference symbols for reference signals (e.g., CRS) and synchronization signals (e.g., primary synchronization signal (PSS) and secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols (if applicable), and can provide T output symbol streams to T modulators (MODs) 232a to 232t. Each modulator 232 can process its own output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The T downlink signals from modulators 232a to 232t can be transmitted separately via T antennas 234a to 234t. Position coding can be used to generate synchronization signals to convey additional information, according to various aspects described in more detail below.

[0072] At UE 120, antennas 252a to 252r can receive downlink signals from base station 110 and / or other base stations, and can provide the received signals to demodulators (DEMODs) 254a to 254r respectively. Each demodulator 254 can adjust (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM, etc.) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols if applicable, and provide the detected symbols. Receive (RX) processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data of UE 120 to data sink 260, and provide the decoded control information and system information to controller / processor 280. The channel processor can determine the Received Reference Power (RSRP), Received Signal Strength Indicator (RSSI), Received Reference Quality (RSRQ), Channel Quality Indicator (CQI), etc.

[0073] On the uplink, at UE 120, the transmitting processor 264 can receive and process data from data source 262 and control information from controller / processor 280 (e.g., reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmitting processor 264 can also generate reference symbols for one or more reference signals. If applicable, the symbols from the transmitting processor 264 can be pre-encoded by the TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and transmitted to base station 110. At base station 110, uplink signals from UE 120 and other UEs can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 (if applicable), and further processed by receiving processor 238 to obtain decoded data and control information transmitted by UE 120. The receiving processor 238 can provide decoded data to the data sink 239 and decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0074] The controller / processor 240 of base station 110, the controller / processor 280 of UE 120 and / or Figure 2Any other component(s) may perform one or more techniques associated with synchronizing user equipment identifiers used for pre-configuring uplink resources, as described in more detail elsewhere herein. For example, the controller / processor 240 of base station 110, the controller / processor 280 of UE 120, and / or Figure 2 Any other component(s) can perform or direct, for example Figure 9 Method 900 Figure 10 Method 1000 Figure 11 Method 1100 Figure 12 Method 1200 Figure 13 The operation of method 1300 and / or other processes described herein. Memory 242 and 282 may store data and program code for BS110 and UE 120, respectively. Scheduler 246 may schedule data transmission by the UE on the downlink and / or uplink.

[0075] As indicated above, Figure 2 Provided as an example only. Other examples may differ from those provided. Figure 2 described.

[0076] Figure 3 This is a diagram illustrating example 300 of UE identifier reassignment.

[0077] At point 305, the UE and the base station can communicate with each other to establish a Radio Resource Control (RRC) connection. As shown, the UE can send a first UE identifier (shown as UE-ID1) to the base station in an RRC message (e.g., an RRC connection request). The base station can store the first UE identifier in its memory, such as in association with the UE context associated with the UE. The UE context can be used to associate information (such as the UE's RRC configuration, one or more UE capabilities, etc.) with the UE using the first UE identifier. As shown, the first UE identifier may include a Serving Temporary Mobile Subscriber Identity (S-TMSI). The base station can configure the UE for an RRC connection (e.g., in an RRC connection establishment message), which places the UE in an RRC connected state with the base station. The base station can use the first UE identifier to establish S1 connections (e.g., S1 Application Protocol (S1-AP) connections) and / or NG connections (e.g., NG Application Protocol (NG-AP) connections) with core network entities, such as an S1-MME connection with a Mobility Management Entity (MME). The core network entity may store the first UE identifier together with the UE's UE context in memory, for purposes such as mobility, billing, or subscription.

[0078] At point 310, the UE can communicate with the core network (e.g., a network controller or another core network device or entity, such as an MME) via a base station to perform a tracking area update or another process that results in a UE identifier reassignment. For example, the UE can send a tracking area update (TAU) request to the base station, and the base station can send a TAU request to the core network. As shown, the TAU request can be sent by the UE to the base station in a Non-Access Stratum (NAS) Protocol Data Unit (PDU) and can also be sent in an RRC connection establishment completion message. As further illustrated, the base station can send the NAS PDU along with the UE's first UE identifier (e.g., S-TMSI) (e.g., retrieved from the UE context stored in the base station's memory) to the core network.

[0079] As further illustrated, the core network can send a UE identifier reassignment message to the UE, shown as a TAU accept message, which indicates the UE's second UE identifier (shown as UE-ID2). Upon receiving the UE identifier reassignment message, the UE replaces the first UE identifier (UE-ID1) with the second UE identifier (UE-ID2) in its memory. The UE can then signal the completion of the UE identifier reassignment, for example, by sending a TAU complete message. Although the TAU process is in... Figure 3 The example shown is a UE identifier reassignment process, but the UE identifier can be reassigned as part of one or more other processes, such as a security process for updating the UE's UE identifier.

[0080] It is worth noting that the base station does not read the UE identifier reallocation message. As a result, the base station is unaware of the UE identifier reallocation and continues to store the first UE identifier in the UE's UE context. If the UE enters RRC idle mode (e.g., due to the RRC connection being released) and then later enters RRC connected mode, the UE will send a second UE identifier to the base station, and the base station will store the second UE identifier in association with the UE's UE context. However, for pre-configured uplink resources (see below in conjunction with...) Figure 4 (Description) In this scenario, the UE can send uplink data to the base station without first establishing a new RRC connection. In this case, the UE will send a second UE identifier along with the uplink data, but the base station will not store the second UE identifier in memory in association with that UE. As a result, the base station may be unable to verify the UE and / or may discard the uplink data. Some of the techniques and apparatus described herein enable the synchronization of UE identifiers between the UE and the base station during UE identifier reallocation, allowing the UE to utilize pre-configured uplink resources to reduce latency, signaling overhead, etc.

[0081] As indicated above, Figure 3 Provided as an example only. Other examples may differ from those provided. Figure 3 described.

[0082] Figure 4 This is a diagram illustrating example 400 of configuring and using pre-configured uplink resources.

[0083] At point 405, the UE and the base station can communicate with each other to establish an RRC connection. As shown, the UE can send a first UE identifier (shown as UE-ID1) to the base station in an RRC message (e.g., an RRC connection request). The base station can store the first UE identifier in its memory, such as in association with the UE context associated with the UE. The UE context can be used to associate information (such as the UE's RRC configuration, one or more UE capabilities, etc.) with the UE using the first UE identifier. As shown, the first UE identifier may include an S-TMSI. The base station can configure the UE for an RRC connection (e.g., in an RRC connection establishment message), which can place the UE in an RRC connected state with the base station. The base station can use the first UE identifier to establish an S1 connection (e.g., an S1-AP connection) and / or an NG connection (e.g., an NG-AP connection), such as an S1-MME connection with an MME. The core network entity can store the first UE identifier together with the UE's UE context in its memory, such as for mobility purposes, charging purposes, subscription purposes, etc.

[0084] At point 410, the UE can communicate with the core network (e.g., a network controller or another core network device or entity, such as an MME) via a base station to send a NAS PDU to the core network. As shown, the NAS PDU can be sent by the UE to the base station and can be sent in an RRC connection establishment completion message. As further illustrated, the base station can send the NAS PDU along with the UE's first UE identifier (e.g., S-TMSI) (e.g., retrieved from the UE context stored in the base station's memory) to the core network. The UE and the base station can then communicate with each other, such as by exchanging data (e.g., uplink data and / or downlink data).

[0085] At 415, the base station can configure the UE using preconfigured uplink resources (PUR) (shown as dedicated preconfigured uplink resources (DPUR)). The PUR may include one or more time resources, one or more frequency resources, and / or transport block (TB) sizes allocated to the UE for uplink communication (e.g., uplink data). The PUR may include one or more periodic resources. The UE can use the PUR to transmit uplink data without first requesting and receiving uplink grants for the uplink data, thereby reducing latency and signaling overhead. Furthermore, the UE can be allowed to use the PUR to transmit uplink data while in RRC idle mode without first establishing an RRC connection and entering RRC connected mode, further saving signaling overhead and reducing UE battery consumption. The base station can determine the PUR configuration (e.g., resource set) for the UE and can send the PUR configuration to the UE. As further shown, the base station can store the PUR configuration and a first UE identifier in the UE's PUR context, which may be stored in the base station's memory. As shown in the figure, after PUR configuration, the UE can enter the RRC idle state.

[0086] At position 420, the UE can undergo a UE identifier reassignment process, as described above. Figure 3 The described TAU procedure or another UE identifier reassignment procedure. The UE identifier reassignment procedure may assign a second UE identifier (UE-ID2) to the UE, and the second UE identifier may replace the first UE identifier (UE-ID1). After the UE reassignment procedure, the UE can send uplink data to the base station using a PUR (e.g., using one or more resources pre-configured for uplink data). For example, the UE may send a PUR request to the base station, where the PUR request may include uplink data. Because the UE has already been reassigned a second UE identifier, the UE can include the second UE identifier (UE-ID2) in the PUR request. However, because the UE does not need to enter the RRC connected state to send the PUR request, the base station is not notified of the second UE identifier now associated with the UE. As a result, the base station cannot recognize the PUR context associated with the UE and may therefore discard the uplink data.

[0087] Some of the techniques and apparatus described herein enable the synchronization of UE identifiers between the UE and the base station during UE identifier reallocation. This allows the UE to use pre-configured uplink resources to reduce latency, signaling overhead, and other factors. For example, some of the techniques and apparatus described herein enable the UE to use the PUR when a UE identifier reallocation occurs between PUR configuration and the UE using the PUR to transmit uplink data.

[0088] As indicated above, Figure 4 Provided as an example only. Other examples may differ from those provided. Figure 4 described.

[0089] Figure 5 This is a diagram illustrating example 500 of UE identifiers used for pre-configuring uplink resources.

[0090] At point 505, UE 120 and base station 110 can communicate with each other to establish an RRC connection, and base station 110 can configure UE 120 using PUR configuration (as described above). Figure 4 (Described). As shown in the figure, UE 120 may send a first UE identifier (shown as UE-ID1) to base station 110 in an RRC message (e.g., a connection request, such as an RRC connection request). Base station 110 may store the first UE identifier of UE 120 in its memory, such as in association with the UE context and / or PUR context associated with UE 120. Therefore, the first UE identifier can be used for PUR. The first UE identifier may include, for example, a first NAS identifier, a first S-TMSI, a first 5G S-TMSI, etc. Base station 110 may configure UE 120 for RRC connection (e.g., in an RRC connection establishment message), which may place UE 120 in an RRC connected state with base station 110. Base station 110 may send the UE identifier to a core network entity to establish an S1 connection and / or NG connection with the core network entity, such as an S1-MME connection with an MME. The core network entity may store the first UE identifier together with the UE context of UE 120 in memory for purposes such as mobility, billing, and subscription.

[0091] Base station 110 can configure UE 120 for a PUR (e.g., before or after establishing an RRC connection), shown as a DPUR. The PUR may include one or more time resources, one or more frequency resources, and / or TB size allocated to UE 120 for uplink communication (e.g., uplink data). The PUR may include one or more periodic resources. In some aspects, the PUR configuration may indicate a first UE identifier. UE 120 can use the PUR (and the first UE identifier) ​​to transmit uplink data without first requesting and receiving uplink grants for uplink data, thereby reducing latency and signaling overhead. Furthermore, UE 120 can be allowed to use the PUR to transmit uplink data while in RRC idle mode without first establishing an RRC connection and entering RRC connected mode, further saving signaling overhead and reducing UE 120 battery consumption. Base station 110 can determine the PUR configuration (e.g., resource set) for UE 120 and can send the PUR configuration to UE 120. As further illustrated, base station 110 may store the PUR configuration and the first UE identifier in the PUR context of UE 120, wherein the PUR context may be stored in the memory of base station 110. In some aspects, base station 110 may send the PUR configuration in an RRC message.

[0092] At point 510, UE 120 can undergo a UE identifier reassignment process, as described above. Figure 3 The described TAU procedure or another UE identifier reassignment procedure. For example, UE 120 may receive (e.g., from a core network entity) a UE identifier reassignment message (e.g., a TAU acceptance message or another message). The UE identifier reassignment procedure may assign a second UE identifier (UE-ID2) to UE 120, and the second UE identifier may replace the first UE identifier (UE-ID1). For example, the UE identifier reassignment message may instruct and / or may instruct UE 120 to update the stored UE identifier (e.g., replace the first UE identifier with the second UE identifier). UE 120 may replace the first UE identifier with the second UE identifier in UE 120's memory. The second UE identifier may include, for example, a second NAS identifier, a second S-TMSI, a second 5G S-TMSI, etc.

[0093] At point 515, UE 120 may send a request to base station 110 to update the first UE identifier to a second UE identifier in response to the PUR. In some aspects, UE 120 may send the request at least partially based on receiving a UE identifier reallocation message. Additionally or alternatively, UE 120 may send the request at least partially based on receiving a PUR configuration. In some aspects, if UE 120 has not configured a PUR configuration, UE 120 may suppress sending the request to base station 110. As shown, UE 120 may send a request in an RRC message (such as an RRC update message) to update the UE identifier used for the PUR (shown as RrcUpdateDPUR-ID). The request may include a second UE identifier (UE-ID2). As shown, base station 110 may update information stored in base station 110's memory (e.g., PUR context) to store the second UE identifier. For example, base station 110 may replace the first UE identifier in its memory with the second UE identifier at least partially based on receiving a request from UE 120.

[0094] although Figure 5 The illustration shows that base station 110 receives a request from UE 120 to update the first UE identifier to the second UE identifier. However, in some aspects, base station 110 may receive the request to update the first UE identifier to the second UE identifier from core network equipment (e.g., core network entities such as MME, Access and Mobility Management Function (AMF) entities, etc.). The following is in conjunction with... Figure 8 Describe additional details.

[0095] In some aspects, the request to update the first UE identifier to the second UE identifier is a single message, shown as an RRC update message. In some aspects, a single message can be sent when UE 120 is in an RRC connection state with UE 120. In this case, base station 110 can receive the second UE identifier and can identify the first UE identifier to be replaced because the second UE identifier is received as part of the same RRC connection in which the first UE identifier is received. Therefore, base station 110 can identify the RRC connection through which the second UE identifier is received, can identify the first UE identifier associated with that RRC connection (e.g., previously received in an RRC message within the same RRC connection), and can replace the first UE identifier with the second UE identifier in base station 110's memory (e.g., in the PUR context).

[0096] In some aspects, a request to update a first UE identifier to a second UE identifier includes two messages. The first message may include a request to delete pre-configured uplink resources associated with the first UE identifier. The second message may include a second RRC connection request indicating the second UE identifier (e.g., where the first RRC connection request indicates the first UE identifier). The following is in conjunction with... Figure 6 Describe additional details.

[0097] At point 520, after notifying base station 110 of the second UE identifier, UE 120 can send uplink data to base station 110 using a PUR (e.g., using one or more resources pre-configured for uplink data). In some aspects, UE 120 can send uplink data to base station 110 after entering RRC idle mode. As shown, UE 120 can send a PUR request to base station 110, which can include uplink data. Because UE 120 has been reassigned a second UE identifier, UE 120 can include the second UE identifier (UE-ID2) in the PUR request. Because of the request to update the first UE identifier to the second UE identifier, the second UE identifier now associated with UE 120 has been notified to base station 110. As a result, base station 110 can identify the PUR context associated with UE 120. Base station 110 can then send the uplink data along with the second UE identifier to the core network. In this way, the core network can use the second UE identifier already assigned to UE 120 for subscription purposes, billing purposes, mobility purposes, etc.

[0098] Because UE 120 notifies base station 110 of the second UE identifier after the UE identifier reallocation process, the UE identifier is synchronized between UE 120 and base station 110. This enables UE 120 to use pre-configured uplink resources to reduce latency, reduce signaling overhead, etc.

[0099] As indicated above, Figure 5 Provided as an example only. Other examples may differ from those provided. Figure 5 described.

[0100] Figure 6 This is a diagram illustrating example 600 of UE identifiers used for pre-configuring uplink resources.

[0101] At point 605, UE 120 and base station 110 can communicate with each other to establish an RRC connection (e.g., a first RRC connection), and base station 110 can configure UE 120 using PUR configuration, as described above. Figure 5 As described above. Figure 5As described, UE 120 may send a first UE identifier (shown as UE-ID1) to base station 110, and base station 110 may store the first UE identifier of UE 120 in its memory, such as in association with the UE context and / or PUR context associated with UE 120 (e.g., a first PUR context). In some aspects, UE 120 may send the first UE identifier in a first connection request (such as a first RRC connection request). Base station 110 may send the UE identifier to a core network entity to establish an S1 connection and / or NG connection with the core network entity, as described above. Figure 5 As described above. Figure 5 As described, base station 110 can configure UE 120 for PUR, and base station 110 can store the PUR configuration and first UE identifier in the memory of base station 110 (e.g., in the PUR context of UE 120).

[0102] At point 610, UE 120 can undergo a UE identifier reassignment process and can receive a UE identifier reassignment message instructing UE 120 to replace the first UE identifier with a second UE identifier, as described above. Figure 5 As described, UE 120 can replace the first UE identifier with a second UE identifier in UE 120's memory.

[0103] At point 615, UE 120 may send a request to base station 110 to update the first UE identifier to the second UE identifier in response to the PUR. In some aspects, UE 120 may send the request at least in part based on receiving a UE identifier reallocation message. Additionally or alternatively, UE 120 may send the request at least in part based on receiving a PUR configuration. In some aspects, if UE 120 does not configure a PUR, UE 120 may suppress sending the request to base station 110.

[0104] In some aspects, a request to update a first UE identifier to a second UE identifier includes two messages. As shown, the first message (e.g., an RRC message, shown as RrcDeleteDPUR-ID) may include a request to delete pre-configured uplink resources associated with the first UE identifier. In some aspects, UE 120 may send the first message while UE 120 is in a connected state. Based at least in part on the first message, base station 110 may delete the PUR context associated with UE 120 (e.g., associated with the first UE identifier) ​​from base station 110's memory. As shown, the second message may include a second connection request (e.g., a second RRC connection request) indicating the second UE identifier. As further shown, in some aspects, UE 120 may send the second message after entering an RRC idle state (e.g., after releasing the first RRC connection). In some aspects, UE 120 may request base station 110 to release the first RRC connection, and UE 120 may enter the RRC idle state based at least in part on an RRC release message received from base station 110. Based at least in part on the second message, base station 110 may store the UE context associated with the second UE identifier. Base station 110 may configure UE 120 to establish a second RRC connection (e.g., in an RRC connection establishment message), and UE 120 may enter RRC connection mode.

[0105] At point 620, because the previously configured PUR configuration has been deleted by base station 110, base station 110 can configure a new PUR configuration for UE 120. For example, UE 120 can send a PUR configuration request to base station 110. Based at least in part on the PUR configuration request, base station 110 can generate a second PUR configuration for UE 120 and can store the second PUR configuration in memory (e.g., in the second PUR context) in association with a second UE identifier. As shown, base station 110 can send the second PUR configuration to UE 120. As described elsewhere herein, UE 120 can use the second PUR configuration to transmit uplink data.

[0106] Because UE 120 notifies base station 110 of the second UE identifier after the UE identifier reallocation process, the UE identifier is synchronized between UE 120 and base station 110. This enables UE 120 to use pre-configured uplink resources to reduce latency, reduce signaling overhead, etc.

[0107] As indicated above, Figure 6 Provided as an example only. Other examples may differ from those provided. Figure 6 described.

[0108] Figure 7This is a diagram illustrating example 700 of UE identifiers used for pre-configuring uplink resources.

[0109] At 705, UE 120 and base station 110 can communicate with each other to establish an RRC connection. As shown, UE 120 can send its UE identifier (shown as UE-ID1) to base station 110 in an RRC message (e.g., a connection request, such as an RRC connection request). Base station 110 can store UE 120's UE identifier in its memory, such as in association with the UE context associated with UE 120. In example 700, base station 110 does not store the UE identifier in association with a PUR context. The UE identifier can be used to identify UE 120 in the core network. For example, the UE identifier can include a NAS identifier, S-TMSI, 5GS-TMSI, etc. In example 700, the UE identifier is not used for PUR.

[0110] Base station 110 can configure UE 120 for RRC connection (e.g., in an RRC connection establishment message), which places UE 120 in an RRC connected state with base station 110. Base station 110 can send a UE identifier to a core network entity to establish an S1 connection and / or NG connection with the core network entity, such as an S1-MME connection with an MME. The core network entity can store the UE identifier along with the UE context of UE 120 in memory for purposes such as mobility, charging, and subscription.

[0111] At 710, base station 110 can configure UE 120 for a PUR (e.g., before or after establishing an RRC connection). As described elsewhere herein, the PUR configuration can indicate one or more time resources, one or more frequency resources, and / or TB size allocated to UE 120 for uplink communication (e.g., uplink data). The PUR configuration can indicate one or more periodic resources. Base station 110 can determine the PUR configuration (e.g., resource set) for UE 120 and can send the PUR configuration to UE 120. In example 700, the PUR configuration includes a PUR identifier (shown as DPUR-ID). The PUR identifier can be used with the PUR, while the UE identifier may not be used with the PUR. As further shown, base station 110 can store the PUR configuration and the PUR identifier in the PUR context of UE 120, wherein the PUR context can be stored in the memory of base station 110. In some aspects, base station 110 can send the PUR configuration in an RRC message.

[0112] In some respects, the PUR identifier is an identifier of a different type than the UE identifier. For example, a different random number generation algorithm and / or a different seed may be used to generate the PUR identifier compared to the UE identifier. Additionally or alternatively, the PUR identifier may include a different number of bits than the UE identifier. In some respects, the UE identifier is a NAS identifier, while the PUR identifier is not a NAS identifier. In some respects, the UE identifier is S-TMSI, while the PUR identifier is not S-TMSI. In some respects, the UE identifier is 5G S-TMSI, while the PUR identifier is not 5G S-TMSI. In some respects, the UE identifier is a NAS identifier used in conjunction with a NAS protocol, and / or the PUR identifier is a RAN identifier used in conjunction with a RAN protocol.

[0113] Alternatively, in some aspects, the PUR identifier and the UE identifier can be identifiers of the same type, but can have different values. For example, the UE identifier can be a NAS identifier with a first value (e.g., a first NAS identifier), and the PUR identifier can be a NAS identifier with a second value (e.g., a second NAS identifier). As another example, the UE identifier can be an S-TMSI with a first value (e.g., a first S-TMSI), and the PUR identifier can be an S-TMSI with a second value (e.g., a second S-TMSI). As yet another example, the UE identifier can be a 5G S-TMSI with a first value (e.g., a first 5G S-TMSI), and the PUR identifier can be a 5G S-TMSI with a second value (e.g., a second 5G S-TMSI).

[0114] In some respects, the UE identifier may change due to the UE reallocation process (as described elsewhere herein), and the PUR identifier may remain unchanged after the UE reallocation process. In some respects, the PUR identifier may change and / or be updated with the transmission of a connection request (e.g., an RRC connection request), but may remain static until a subsequent connection request. For example, at the time of transmission of the first RRC connection request, both the PUR identifier and the UE identifier may be UE-ID1. Subsequently, if the UE identifier is reallocated, the UE identifier may be updated to UE-ID2, while the PUR identifier may remain UE-ID1.

[0115] At point 715, UE 120 can send uplink data to base station 110 using a PUR (e.g., using one or more resources pre-configured for uplink data). In some aspects, UE 120 can send uplink data to base station 110 after entering RRC idle mode. As shown, UE 120 can send a pre-configured uplink message (e.g., a PUR request) to base station 110, which may include uplink data. As further shown, the pre-configured uplink message may include both a PUR identifier (DPUR-ID) and a UE identifier (UE-ID1). As shown, base station 110 can use the PUR identifier (DPUR-ID) to identify the PUR context associated with UE 120, such as to authenticate UE 120, determine how to process uplink data, etc. As further shown, base station 110 can send uplink data along with the UE identifier (UE-ID1) to the core network. In some respects, base station 110 can suppress the transmission of the PUR identifier to the core network (e.g., because the PUR identifier is used locally by base station 110 and not by the core network). The core network can use the UE identifier for subscription purposes, billing purposes, mobility purposes, etc.

[0116] Because UE 120 and base station 110 use separate identifiers for UE identifier and PUR identifier, the PUR identifier can be kept synchronized between UE 120 and base station 110 (e.g., before and after the UE identifier reallocation process). This allows UE 120 to use pre-configured uplink resources to reduce latency, reduce signaling overhead, etc.

[0117] As indicated above, Figure 7 Provided as an example only. Other examples may differ from those provided. Figure 7 described.

[0118] Figure 8 This is a diagram illustrating example 800 of UE identifiers used for pre-configuring uplink resources.

[0119] At point 805, UE 120 and base station 110 can communicate with each other to establish an RRC connection, and base station 110 can configure UE 120 using PUR configuration. As shown, UE 120 can send a first UE identifier (shown as UE-ID1) to base station 110 in an RRC message (e.g., a connection request, such as an RRC connection request). Base station 110 can store the first UE identifier of UE 120 in its memory, such as in association with the UE context and / or PUR context associated with UE 120. Therefore, the first UE identifier can be used in the PUR. The first UE identifier may include, for example, a first NAS identifier, a first S-TMSI, a first 5G S-TMSI, etc. Base station 110 can configure UE 120 for an RRC connection (e.g., in an RRC connection establishment message), which can put UE 120 into an RRC connected state with base station 110.

[0120] Base station 110 can send a UE identifier to a core network entity to establish an S1 connection and / or NG connection with the core network entity, such as an S1-MME connection with an MME. The core network entity can store the first UE identifier along with the UE context of UE 120 in memory, for purposes such as mobility, billing, and subscription. Therefore, the base station and the core network (e.g., core network devices and / or core network entities) can establish a connection (e.g., an S1 connection and / or NG connection), and this connection can be associated with UE 120 and the first UE identifier, wherein the first UE identifier identifies UE 120 in the core network and is associated with the PUR of UE 120.

[0121] Base station 110 can configure UE 120 for a PUR (e.g., before or after establishing an RRC connection), shown as a DPUR. The PUR may include one or more time resources, one or more frequency resources, and / or TB size allocated to UE 120 for uplink communication (e.g., uplink data). The PUR may include one or more periodic resources. In some aspects, the PUR configuration may indicate a first UE identifier. UE 120 can use the PUR (and the first UE identifier) ​​to transmit uplink data without first requesting and receiving uplink grants for uplink data, thereby reducing latency and signaling overhead. Furthermore, UE 120 can be allowed to use the PUR to transmit uplink data while in RRC idle mode without first establishing an RRC connection and entering RRC connected mode, further saving signaling overhead and reducing UE 120 battery consumption. Base station 110 can determine the PUR configuration (e.g., resource set) for UE 120 and can send the PUR configuration to UE 120. As further illustrated, base station 110 may store the PUR configuration and the first UE identifier in the PUR context of UE 120, wherein the PUR context may be stored in the memory of base station 110. In some aspects, base station 110 may send the PUR configuration in an RRC message.

[0122] At 810, UE 120 can undergo a UE identifier reassignment process, as described above. Figure 3 The described TAU procedure or another UE identifier reassignment procedure. For example, UE 120 may receive (e.g., from a core network entity) a UE identifier reassignment message (e.g., a TAU acceptance message or another message). The UE identifier reassignment procedure may assign a second UE identifier (UE-ID2) to UE 120, and the second UE identifier may replace the first UE identifier (UE-ID1). For example, the UE identifier reassignment message may instruct and / or may instruct UE 120 to update the stored UE identifier (e.g., replace the first UE identifier with the second UE identifier). UE 120 may replace the first UE identifier with the second UE identifier in UE 120's memory. The second UE identifier may include, for example, a second NAS identifier, a second S-TMSI, a second 5G S-TMSI, etc.

[0123] At point 815, a core network device (e.g., an MME, AMF entity, etc.) may send a request to base station 110 to update the first UE identifier of the PUR to a second UE identifier. In some aspects, the core network device may send the request at least in part based on sending a UE identifier reallocation message. As shown, the core network device may send the request via an S1 connection (e.g., an S1-AP connection), an NG connection (e.g., an NG-AP connection), etc. The request may include the second UE identifier (UE-ID2). As shown, base station 110 may update information (e.g., the PUR context) stored in base station 110's memory to store the second UE identifier. For example, base station 110 may replace the first UE identifier in its memory with the second UE identifier at least in part based on receiving a request from the core network device. In some aspects, the request to update the first UE identifier to the second UE identifier is a single message from the core network device to base station 110.

[0124] At point 820, after the core network device notifies base station 110 of the second UE identifier, UE 120 can send uplink data to base station 110 using a PUR (e.g., using one or more resources pre-configured for uplink data). In some aspects, UE 120 can send uplink data to base station 110 after entering RRC idle mode. As shown, UE 120 can send a PUR request to base station 110, which can include uplink data. Because UE 120 has been reassigned a second UE identifier, UE 120 can include the second UE identifier (UE-ID2) in the PUR request. Because of the request to update the first UE identifier to the second UE identifier, the second UE identifier now associated with UE 120 has been notified to base station 110. As a result, base station 110 can identify the PUR context associated with UE 120. Base station 110 can then send uplink data to the core network along with the second UE identifier. In this way, the core network can use the second UE identifier already assigned to UE 120 for subscription purposes, billing purposes, mobility purposes, etc.

[0125] Because the core network device notifies the base station 110 of the second UE identifier after the UE identifier reassignment process, the UE identifier is synchronized between UE 120, base station 110 and the core network device. This enables UE 120 to use pre-configured uplink resources to reduce latency, reduce signaling overhead, etc.

[0126] As indicated above, Figure 8 Provided as an example only. Other examples may differ from those provided. Figure 8 described.

[0127] Figure 9 This is a diagram illustrating an example method 900 performed by a UE, for example, according to various aspects of this disclosure. Example method 900 is an example of a UE (e.g., UE 120, device 1402, etc.) performing operations associated with a user equipment identifier for synchronizing pre-configured uplink resources.

[0128] In some aspects, block 910 may include sending a connection request to the base station, wherein the connection request indicates a first UE identifier for pre-configuring uplink resources. For example, as described above, the UE (e.g., using transmit processor 264, controller / processor 280, memory 282, etc.) may send a connection request to the base station, wherein the connection request indicates a first UE identifier for pre-configuring uplink resources. In some aspects, the connection request is sent in a radio resource control message. In some aspects, the first UE identifier is a first non-access stratum (NAS) identifier, a first serving temporary mobile subscriber identity (S-TMSI), or a first 5G S-TMSI (5G-S-TMSI).

[0129] In some aspects, block 920 may include receiving configuration from a base station for pre-configuring uplink resources. For example, as described above, the UE (e.g., using receive processor 258, controller / processor 280, memory 282, etc.) may receive configuration for pre-configuring uplink resources from the base station. In some aspects, the configuration is received in a radio resource control message.

[0130] In some aspects, block 930 may include receiving a UE identifier reallocation message instructing the UE to replace the first UE identifier with a second UE identifier. For example, as described above, the UE (e.g., using receive processor 258, controller / processor 280, memory 282, etc.) may receive the UE identifier reallocation message instructing the UE to replace the first UE identifier with a second UE identifier. In some aspects, the second UE identifier is a second NAS identifier, a second S-TMSI, or a second 5G S-TMSI.

[0131] In some aspects, block 940 may include sending a request to the base station, at least in part, to update the first UE identifier to the second UE identifier for pre-configured uplink resources, based on receiving a UE identifier reallocation message. For example, as described above, the UE (e.g., using transmit processor 264, controller / processor 280, memory 282, etc.) may send the request to the base station, at least in part, to update the first UE identifier to the second UE identifier for pre-configured uplink resources, based on receiving a UE identifier reallocation message. In some aspects, the request to update the first UE identifier to the second UE identifier for pre-configured uplink resources is also at least in part based on receiving configuration for pre-configured uplink resources. In some aspects, the request to update the first UE identifier to the second UE identifier is sent in a radio resource control message. In some aspects, the request to update the first UE identifier to the second UE identifier is a single message sent while the UE is in a connected state. In some aspects, the request to update the first UE identifier to the second UE identifier includes: a request to delete pre-configured uplink resources associated with the first UE identifier while the UE is in a connected state, and another connection request indicating the second UE identifier.

[0132] Method 900 may include additional aspects, such as any single aspect or any combination of aspects described in conjunction with one or more other processes described elsewhere herein.

[0133] although Figure 9 An example block of method 900 is shown, but in some respects, method 900 may include more than Figure 9 The blocks described in the diagram may be additional blocks, fewer blocks, different blocks, or blocks with different arrangements. Alternatively or additionally, two or more blocks of method 900 may be executed in parallel.

[0134] Figure 10 This is a diagram illustrating an example method 1000 performed by a UE, for example, according to various aspects of this disclosure. Example method 1000 is an example of a UE (e.g., UE 120, device 1402 / 1402', etc.) performing operations associated with a user equipment identifier for synchronizing uplink resources.

[0135] In some aspects, block 1010 may include sending a connection request to the base station, wherein the connection request indicates a first UE identifier that identifies the UE in the core network. For example, as described above, the UE (e.g., using transmit processor 264, controller / processor 280, memory 282, etc.) may send a connection request to the base station, wherein the connection request indicates a first UE identifier that identifies the UE in the core network. In some aspects, the connection request is sent in an RRC message. In some aspects, the first UE identifier is a NAS identifier, S-TMSI, or 5G TMSI.

[0136] In some aspects, block 1020 may include receiving configuration from a base station for pre-configuring uplink resources (PUR), wherein the configuration indicates uplink resources and a PUR identifier. For example, as described above, the UE (e.g., using a receive processor 258, a controller / processor 280, a memory 282, etc.) may receive the configuration for the PUR from the base station. In some aspects, the configuration indicates uplink resources and a PUR identifier. In some aspects, the PUR identifier is an identifier of a different type from the UE identifier. In some aspects, the UE identifier is a first NAS identifier, a first S-TMSI, or a first 5G S-TMSI, and the PUR identifier is a second NAS identifier, a second S-TMSI, or a second 5G S-TMSI. In some aspects, the uplink resources are pre-configured uplink resources.

[0137] In some aspects, block 1030 may include communicating with the base station at least in part based on this configuration. For example, the UE (e.g., using transmit processor 264, controller / processor 280, memory 282, etc.) may communicate with the base station at least in part based on this configuration. In some aspects, communicating with the base station includes sending a pre-configured uplink message to the base station in pre-configured uplink resources, wherein the pre-configured uplink message includes uplink data. In some aspects, the UE may send a message including a PUR identifier to the base station.

[0138] Method 1000 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or in combination with one or more other processes described elsewhere herein.

[0139] In some aspects, the UE can perform a UE identifier reassignment procedure, wherein the procedure assigns a second UE identifier to the UE that is different from the first UE identifier. The UE can send a message including a PUR identifier to the base station, at least in part, based on the execution of the UE identifier reassignment procedure. In this case, the UE identifier reassignment procedure does not change the PUR identifier. In this case, the first UE identifier can be a first NAS identifier, a first S-TMSI, or a first 5G S-TMSI, and the second UE identifier can be a second NAS identifier, a second S-TMSI, or a second 5G S-TMSI.

[0140] In some aspects, the UE may receive a message that causes the UE to replace the first UE identifier with a second UE identifier. The UE may, at least in part, send a message including a PUR identifier to the base station based on receiving the message causing the UE to replace the first UE identifier with a second UE identifier. In this case, the message causing the UE to replace the first UE identifier with a second UE identifier does not change the PUR identifier. In this case, the first UE identifier may be a first NAS identifier, a first S-TMSI, or a first 5G S-TMSI, and the second UE identifier may be a second NAS identifier, a second S-TMSI, or a second 5G S-TMSI.

[0141] although Figure 10 An example block of method 1000 is shown, but in some respects, method 1000 may include more than Figure 10 The blocks described herein may be additional blocks, fewer blocks, different blocks, or blocks with different arrangements. Alternatively or concurrently, two or more blocks of method 1000 may be executed in parallel.

[0142] Figure 11 This is a diagram illustrating, for example, an example method 1100 performed by a base station according to various aspects of this disclosure. Example method 1100 is an example of a base station (e.g., base station 110, device 1602 / 1602', etc.) performing operations associated with VIP identifiers for synchronizing uplink resources.

[0143] In some aspects, block 1110 may include receiving a connection request from the UE indicating a first UE identifier for pre-configuring uplink resources. For example, as described above, the base station (e.g., using a receive processor 238, controller / processor 240, memory 242, etc.) may receive the connection request from the UE indicating a first UE identifier for pre-configuring uplink resources. In some aspects, the connection request is received in an RRC message. In some aspects, the first UE identifier is a first NAS identifier, a first S-TMSI, or a first 5G S-TMSI.

[0144] In some aspects, block 1120 may include sending a configuration for pre-configuring uplink resources to the UE. For example, as described above, the base station (e.g., using transmit processor 220, controller / processor 240, memory 242, etc.) may send the configuration for pre-configuring uplink resources to the UE. In some aspects, this configuration is sent in an RRC message. In some aspects, the configuration indicates one or more uplink resources for the UE to transmit uplink data without first receiving authorization.

[0145] In some aspects, block 1130 may include receiving a request to update a first UE identifier to a second UE identifier for pre-configured uplink resources. For example, as described above, a base station (e.g., using a receive processor 238, controller / processor 240, memory 242, etc.) may receive the request to update the first UE identifier to a second UE identifier for pre-configured uplink resources. In some aspects, the request to update the first UE identifier to the second UE identifier is received from the UE. In some aspects, the request to update the first UE identifier to the second UE identifier is received in an RRC message. In some aspects, the request to update the first UE identifier to the second UE identifier is received from a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF) entity, or another core network entity. In some aspects, the request to update the first UE identifier to the second UE identifier is an S1 application protocol message or an NG application protocol message. In some aspects, the request to update the first UE identifier to the second UE identifier is a single message received when the UE is in a connected state. In some aspects, a request to update a first UE identifier to a second UE identifier includes: a request to delete pre-configured uplink resources associated with the first UE identifier while the UE is in a connected state, and another connection request indicating the second UE identifier. In some aspects, the second UE identifier is a second NAS identifier, a second S-TMSI, or a second 5G S-TMSI.

[0146] In some aspects, block 1140 may include updating the first UE identifier to the second UE identifier in the memory of the base station's storage of the context associated with the pre-configured uplink resources, based at least in part on receiving a request to update the first UE identifier to the second UE identifier. For example, as described above, the base station (e.g., using controller / processor 240, memory 242, etc.) may update the first UE identifier to the second UE identifier at least in part on receiving a request to update the first UE identifier to the second UE identifier. In some aspects, the base station may update the first UE identifier to the second UE identifier in the memory of the base station's storage of the context associated with the pre-configured uplink resources. The context may include, for example, a PUR context.

[0147] Method 1100 may include additional aspects, such as any single aspect or any combination of aspects described in conjunction with one or more other processes described elsewhere herein.

[0148] although Figure 11 An example block of method 1100 is shown, but in some respects, method 1100 may include more than Figure 11 The blocks described herein may be additional blocks, fewer blocks, different blocks, or blocks with different arrangements. Alternatively or concurrently, two or more blocks of method 1100 may be executed in parallel.

[0149] Figure 12 This is a diagram illustrating an example method 1200 performed by a base station, for example, according to various aspects of this disclosure. Example method 1200 is an example of a base station (e.g., base station 110, device 1602 / 1602', etc.) performing operations associated with VIP identifiers for synchronizing uplink resources.

[0150] In some aspects, block 1210 may include receiving a connection request from the UE, wherein the connection request indicates a first UE identifier that identifies the UE in the core network. For example, as described above, a base station (e.g., using a receive processor 238, a controller / processor 240, a memory 242, etc.) may receive the connection request from the UE, wherein the connection request indicates a first UE identifier that identifies the UE in the core network. In some aspects, the connection request is received in an RRC message. In some aspects, the first UE identifier is a NAS identifier, an S-TMSI, or a 5G S-TMSI.

[0151] In some aspects, block 1220 may include sending a configuration for the PUR to the UE, wherein the configuration indicates uplink resources and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier. For example, as described above, a base station (e.g., using a transmit processor 220, a controller / processor 240, a memory 242, etc.) may send the configuration for the PUR to the UE. In some aspects, the configuration indicates uplink resources and a PUR identifier. In some aspects, the configuration is sent in an RRC message. In some aspects, the PUR identifier is an identifier of a different type from the first UE identifier. In some aspects, the first UE identifier is a first NAS identifier, a first S-TMSI, or a 5G S-TMSI, and the PUR identifier is a second NAS identifier, a second S-TMSI, or a second 5GS-TMSI.

[0152] In some aspects, block 1230 may include communicating with the UE at least partially based on this configuration. For example, as described above, the base station (e.g., using receive processor 238, controller / processor 240, memory 242, etc.) may communicate with the UE at least partially based on this configuration. In some aspects, communicating with the UE includes receiving a pre-configured uplink message from the UE in a pre-configured uplink resource, wherein the pre-configured uplink message includes uplink data. In some aspects, the pre-configured uplink message includes uplink data, a UE identifier, and a PUR identifier. In some aspects, the base station may identify a context associated with the pre-configured uplink resource at least partially based on the PUR identifier. The context may include, for example, a PUR context. In some aspects, the base station may receive a message including a PUR identifier from the UE.

[0153] Method 1200 may include additional aspects, such as any single aspect or any combination of aspects described below, and / or in combination with one or more other processes described elsewhere herein.

[0154] In some aspects, the base station can send a message that causes the UE to replace the first UE identifier with a second UE identifier. The base station can receive a message including a PUR identifier from the UE, at least in part, based on sending the message that causes the UE to replace the first UE identifier with a second UE identifier. In this case, the message that causes the UE to replace the first UE identifier with a second UE identifier does not change the PUR identifier. In this case, the first UE identifier is a first NAS identifier, a first S-TMSI, or a first 5GS-TMSI, and the second UE identifier is a second NAS identifier, a second S-TMSI, or a second 5G S-TMSI.

[0155] although Figure 12 An example block of method 1200 is shown, but in some respects, method 1200 may include more than Figure 12 The blocks described herein may be additional blocks, fewer blocks, different blocks, or blocks with different arrangements. Alternatively or concurrently, two or more blocks of method 1200 may be executed in parallel.

[0156] Figure 13 This is a diagram illustrating an example method 1300 performed, for example, by a core network device according to various aspects of this disclosure. Example method 1300 is an example of a core network device (e.g., network controller 130, MME, AMF entity, device 1802 / 1802', etc.) performing operations associated with VIP identifiers for synchronizing pre-configured uplink resources.

[0157] In some aspects, block 1310 may include establishing a connection with a base station, wherein the connection is associated with a UE and a first UE identifier, wherein the first UE identifier identifies the UE in the core network and is associated with pre-configured uplink resources for the UE. For example, as described above, a core network device (e.g., using controller / processor 290, memory 292, communication unit 294, etc.) may establish a connection with the base station. In some aspects, the connection is associated with a UE and a first UE identifier, wherein the first UE identifier identifies the UE in the core network and is associated with pre-configured uplink resources for the UE. In some aspects, the connection is established for an S1-AP interface and / or an NG-AP interface. For example, the connection with the base station may be an S1 application protocol connection or an NG application protocol connection. In some aspects, the core network device is a Mobility Management Entity (MME) or an Access and Mobility Management Function (AMF) entity.

[0158] In some aspects, block 1320 may include sending a UE identifier reallocation message to the UE via a base station, instructing the UE to replace the first UE identifier with a second UE identifier. For example, as described above, core network equipment (e.g., using controller / processor 290, memory 292, communication unit 294, etc.) may send the UE identifier reallocation message to the UE via a base station, instructing the UE to replace the first UE identifier with a second UE identifier. In some aspects, the first UE identifier is a first NAS identifier, a first S-TMSI, or a first 5G S-TMSI. In some aspects, the second UE identifier is a second NAS identifier, a second S-TMSI, or a second 5G S-TMSI.

[0159] In some aspects, block 1330 may include sending a request to the base station to update the first UE identifier to the second UE identifier for pre-configured uplink resources. For example, as described above, a core network device (e.g., using controller / processor 290, memory 292, communication unit 294, etc.) may send the request to the base station to update the first UE identifier to the second UE identifier for pre-configured uplink resources. In some aspects, the request to update the first UE identifier to the second UE identifier is sent via an S1 application protocol connection or an NG application protocol connection.

[0160] Method 1300 may include additional aspects, such as any single aspect or any combination of aspects described in conjunction with one or more other processes described elsewhere herein.

[0161] although Figure 13 An example block of method 1300 is shown, but in some respects, method 1300 may include more than Figure 13 The blocks described herein may be additional blocks, fewer blocks, different blocks, or blocks with different arrangements. Alternatively or concurrently, two or more blocks of method 1300 may be executed in parallel.

[0162] Figure 14 This is a conceptual data flow diagram 1400 illustrating the data flow between different modules / device modules / components in example device 1402. Device 1402 may be a UE. In some aspects, device 1402 includes a receiving module 1404, a determining module 1406, a transmitting module 1408, etc.

[0163] In some aspects, the transmitting module 1408 may send a connection request to the device 1450 (e.g., a base station), wherein the connection request indicates a first UE identifier that identifies the device 1402 in the core network. The receiving module 1404 may receive from the device 1450 a configuration for pre-configuring uplink resources, wherein the configuration indicates uplink resources and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier. In some aspects, the receiving module 1404 may receive a UE identifier reallocation message instructing the UE to replace the first UE identifier with a second UE identifier. In some aspects, the transmitting module 1408 may, at least in part, send a request to the device 1450 to update the first UE identifier to a second UE identifier for pre-configured uplink resources based on the received UE identifier reallocation message. The receiving module 1404 or the transmitting module 1408 may communicate with the device 1450 at least in part based on this configuration. For example, the transmitting module 1408 may transmit a pre-configured uplink message to the device 1450 in a pre-configured uplink resource, wherein the pre-configured uplink message includes uplink data. In some aspects, the determining module 1406 may determine the transmission request based at least in part on the receipt of a UE identifier reallocation message and / or at least in part on the receipt of a configuration for pre-configuring uplink resources. The determining module 1406 may instruct the transmitting module 1408 to transmit the request.

[0164] In some aspects, the transmitting module 1408 may send a connection request to the device 1450, wherein the connection request indicates a UE identifier that identifies the UE in the core network. The receiving module 1404 may receive a configuration for the PUR from the device 1450, wherein the configuration indicates uplink resources and a PUR identifier. The transmitting module 1408 may send a pre-configured uplink message to the device 1450 in the uplink resources, wherein the pre-configured uplink message includes uplink data, a UE identifier, and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier. In some aspects, the determining module 1406 may determine a transmission request and / or may instruct the transmitting module 1408 to send the request.

[0165] In some respects, the determining module 1406 can perform a UE identifier reallocation process, wherein the process assigns a second UE identifier to the device 1402 that is different from the first UE identifier. The sending module 1408 can send a message including the PUR identifier to the device 1450 based at least in part on the execution of the UE identifier reallocation process.

[0166] In some respects, receiving module 1404 may receive a message that causes device 1402 to replace the first UE identifier with the second UE identifier. Sending module 1408 may send a message including the PUR identifier to device 1450 based at least in part on receiving the message that causes device 1402 to replace the first UE identifier with the second UE identifier.

[0167] The apparatus may include the means to perform the aforementioned Figure 9 Method 900 Figure 10 The method 1000 and other algorithms are additional modules for each block of the algorithm. (The aforementioned...) Figure 9 Method 900 Figure 10 Each block in method 1000, etc., can be executed by a module, and the apparatus can include one or more of these modules. These modules can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0168] Figure 14 The number and arrangement of modules shown are provided as an example. In reality, with... Figure 14 Compared to the modules shown, there can be additional modules, fewer modules, different modules, or modules with different arrangements. Furthermore, Figure 14 The two or more modules shown can be implemented in a single module, or Figure 14 The single module shown can be implemented as multiple distributed modules. Additionally or alternatively, Figure 14 The set of modules shown (e.g., one or more modules) can perform actions described by Figure 14 The other set of modules shown performs one or more functions.

[0169] Figure 15 Figure 1500 illustrates an example of a hardware implementation of a device 1402 employing a processing system 1502. Device 1402 may be a UE.

[0170] Processing system 1502 can be implemented using a bus architecture (typically represented by bus 1504). Depending on the specific application and overall design constraints of processing system 1502, bus 1504 may include any number of interconnect buses and bridges. Bus 1504 links together various circuits including one or more processors and / or hardware modules represented by processor 1506, modules 1404, 1406, 1408, and computer-readable medium / memory 1508. Bus 1504 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0171] Processing system 1502 may be coupled to transceiver 1510. Transceiver 1510 is coupled to one or more antennas 1512. Transceiver 1510 provides a device module for communicating with various other devices via a transmission medium. Transceiver 1510 receives signals from one or more antennas 1512, extracts information from the received signals, and provides the extracted information to processing system 1502, specifically, receiving module 1404. Furthermore, transceiver 1510 receives information from processing system 1502 (specifically, transmitting module 1408) and generates signals to be applied to one or more antennas 1512, at least in part, based on the received information. Processing system 1502 includes processor 1506 coupled to computer-readable medium / memory 1508. Processor 1506 is responsible for general processing, including executing software stored on computer-readable medium / memory 1508. When executed by processor 1506, the software causes processing system 1502 to perform the various functions described herein with respect to any particular device. The computer-readable medium / memory 1508 can also be used to store data manipulated by the processor 1506 during software execution. The processing system also includes at least one of modules 1404, 1406, 1408, etc. These modules may be software modules running in the processor 1506, software modules residing in / stored in the computer-readable medium / memory 1508, one or more hardware modules coupled to the processor 1506, or some combination thereof. The processing system 1502 may be a component of the UE 120 and may include at least one of memory 282 and / or TX MIMO processor 266, RX processor 258, and / or controller / processor 280.

[0172] In some aspects, the apparatus 1402 for wireless communication includes: an apparatus module for sending a connection request to a base station, wherein the connection request indicates a first UE identifier for pre-configuring uplink resources; an apparatus module for receiving from the base station a configuration for pre-configuring uplink resources; an apparatus module for receiving a UE identifier reallocation message instructing the apparatus to replace the first UE identifier with a second UE identifier; an apparatus module for sending, at least in part based on the received UE identifier reallocation message, a request to the base station to update the first UE identifier to the second UE identifier for pre-configured uplink resources; and / or the like. Additionally or alternatively, the apparatus 1402 for wireless communication includes: an apparatus module for sending a connection request to a base station, wherein the connection request indicates a first UE identifier identifying the apparatus in a core network; an apparatus module for receiving from the base station a configuration for a PUR, wherein the configuration indicates uplink resources and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier; an apparatus for communicating with the base station at least in part based on the configuration; and / or the like. The aforementioned device modules may be one or more of the aforementioned modules of device 1402 and / or a processing system 1502 of device 1402 configured to perform the functions listed herein. As described elsewhere herein, processing system 1502 may include TX MIMO processor 266, RX processor 258, and / or controller / processor 280. In one configuration, the aforementioned device modules may be TX MIMO processor 266, RX processor 258, and / or controller / processor 280 configured to perform the functions and / or operations listed herein.

[0173] Figure 15 This is provided as an example. Other examples may differ from the combination. Figure 15 described.

[0174] Figure 16 This is a conceptual data flow diagram 1600 illustrating the data flow between different modules / device modules / components in example device 1602. Device 1602 may be a base station. In some aspects, device 1602 includes a receiving module 1604, a determining module 1606, an updating module 1608, a transmitting module 1610, etc.

[0175] In some aspects, receiving module 1604 may receive a connection request from device 1650 (e.g., UE) indicating a first UE identifier for pre-configuring uplink resources. Sending module 1610 may send a configuration for pre-configuring uplink resources to device 1650. Receiving module 1604 may receive a request to update the first UE identifier to a second UE identifier for pre-configuring uplink resources. Updating module 1608 may update the first UE identifier to the second UE identifier in the memory of the base station's storage of the context associated with the pre-configured uplink resources, based at least in part on receiving the request to update the first UE identifier to the second UE identifier. Determining module 1606 may determine to send the configuration for pre-configuring uplink resources, and / or may notify sending module 1610 to send the configuration. Additionally or alternatively, determining module 1606 may determine to update the first UE identifier to the second UE identifier and / or may notify updating module 1608 to perform the update.

[0176] In some respects, receiving module 1604 may receive a connection request from device 1650, wherein the connection request indicates a first UE identifier that identifies the UE in the core network. Transmitting module 1610 may send a configuration for a PUR to device 1650, wherein the configuration indicates uplink resources and a PUR identifier, the PUR identifier being an identifier of a different type from the first UE identifier. Receiving module 1604 or transmitting module 1610 may communicate with the UE at least in part based on this configuration.

[0177] The apparatus may include the means to perform the aforementioned Figure 11 Method 1100 Figure 12 Additional modules for each block of the algorithm in Method 1200, etc. (as mentioned above) Figure 11 Method 1100 Figure 12 Each block in method 1200, etc., can be executed by a module, and the apparatus can include one or more of these modules. These modules can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0178] Figure 16 The number and arrangement of modules shown are provided as an example. In reality, there can be more. Figure 16 The examples show additional modules, fewer modules, different modules, or modules with different arrangements. Furthermore, Figure 16 The two or more modules shown can be implemented in a single module, or Figure 16 The single module shown can be implemented as multiple distributed modules. Additionally or alternatively, Figure 16The set of modules shown (e.g., one or more modules) can perform actions described by Figure 16 The other set of modules shown performs one or more functions.

[0179] Figure 17 Figure 1700 shows an example of a hardware implementation of the device 1602 employing the processing system 1702. Device 1602' may be a base station.

[0180] Processing system 1702 can be implemented using a bus architecture (typically represented by bus 1704). Depending on the specific application and overall design constraints of processing system 1702, bus 1704 may include any number of interconnect buses and bridges. Bus 1704 links together various circuits including one or more processors and / or hardware modules represented by processor 1706, modules 1604, 1606, 1608, 1610, etc., and computer-readable medium / memory 1708. Bus 1704 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0181] Processing system 1702 may be coupled to transceiver 1710. Transceiver 1710 is coupled to one or more antennas 1712. Transceiver 1710 provides a device module for communicating with various other devices via a transmission medium. Transceiver 1710 receives signals from one or more antennas 1712, extracts information from the received signals, and provides the extracted information to processing system 1702, specifically, receiving module 1604. Furthermore, transceiver 1710 receives information from processing system 1702 (specifically, transmitting module 1610) and generates signals to be applied to one or more antennas 1712, at least in part, based on the received information. Processing system 1702 includes processor 1706 coupled to computer-readable medium / memory 1708. Processor 1706 is responsible for general processing, including executing software stored on computer-readable medium / memory 1708. When executed by processor 1706, the software causes processing system 1702 to perform the various functions described herein with respect to any particular device. The computer-readable medium / memory 1708 can also be used to store data manipulated by the processor 1706 during software execution. The processing system also includes at least one of modules 1604, 1606, 1608, 1610, etc. These modules may be software modules running in the processor 1706, software modules residing in / stored in the computer-readable medium / memory 1708, one or more hardware modules coupled to the processor 1706, or some combination thereof. The processing system 1702 may be a component of the eNB 110 and may include at least one of memory 242 and / or TX MIMO processor 230, RX processor 238, and / or controller / processor 240.

[0182] In some aspects, the apparatus 1602 for wireless communication includes: an apparatus module for receiving a connection request from a UE, wherein the connection request indicates a first UE identifier for preconfiguring uplink resources; an apparatus module for transmitting a configuration for preconfiguring the uplink resources to the UE; an apparatus module for receiving a request to update the first UE identifier to a second UE identifier for the preconfigured uplink resources; an apparatus module for updating the first UE identifier to the second UE identifier in a memory storing a context associated with the preconfigured uplink resources, based at least in part on receiving the request to update the first UE identifier to the second UE identifier; and / or the like. In some aspects, apparatus 1602 may include: an apparatus module for receiving a connection request from a UE, wherein the connection request indicates a first UE identifier that identifies the UE in the core network; an apparatus module for sending a configuration for a PUR to the UE, wherein the configuration indicates uplink resources and a PUR identifier, wherein the PUR identifier is an identifier of a different type from the first UE identifier; an apparatus module for communicating with the UE at least in part based on the configuration; an apparatus module for receiving a pre-configured uplink message from the UE in uplink resources, wherein the pre-configured uplink message includes uplink data, a UE identifier, and a PUR identifier; and / or the like. The aforementioned apparatus modules may be one or more of the aforementioned modules of apparatus 1602 and / or a processing system 1702 of apparatus 1602' configured to perform the functions listed for the aforementioned apparatus modules. As described elsewhere herein, processing system 1702 may include a TX MIMO processor 230, a receive processor 238, and / or a controller / processor 240. In one configuration, the aforementioned device module may be a TX MIMO processor 230, a receiver processor 238, and / or a controller / processor 240 configured to perform the functions and / or operations listed herein.

[0183] Figure 17 This is provided as an example. Other examples may differ from the combination. Figure 17 described.

[0184] Figure 18 This is a conceptual data flow diagram 1800 illustrating the data flow between different modules / device modules / components in example device 1802. Device 1802 may be a core network device. In some aspects, device 1802 includes a receiving module 1804, a determining module 1806, an establishing module 1808, a sending module 1810, etc.

[0185] In some aspects, the establishment module 1808 can establish a connection with the device 1850 (e.g., a base station), wherein the connection is associated with the UE and a first UE identifier, wherein the first UE identifier identifies the UE in the core network and is associated with pre-configured uplink resources for the UE. The transmission module 1810 can send a UE identifier reallocation message to the UE via the device 1850, instructing the UE to replace the first UE identifier with a second UE identifier. The transmission module 1810 can send a request to the device 1850 to update the first UE identifier to the second UE identifier for the pre-configured uplink resources. The determination module 1806 can determine to establish a connection, determine to send a UE identifier reallocation message, and / or determine to send a request. The determination module 1806 can notify the transmission module 1810 accordingly.

[0186] The apparatus may include the means to perform the aforementioned Figure 13 The method 1300 and other algorithms are additional modules for each block of the algorithm. (The aforementioned...) Figure 13 Each block in method 1300, etc., can be executed by a module, and the apparatus can include one or more of these modules. These modules can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0187] Figure 18 The number and arrangement of modules shown are provided as an example. In reality, there can be more. Figure 18 The examples show additional modules, fewer modules, different modules, or modules with different arrangements. Furthermore, Figure 18 The two or more modules shown can be implemented within a single module, or Figure 18 The single module shown can be implemented as multiple distributed modules. Additionally or alternatively, Figure 18 The set of modules shown (e.g., one or more modules) can perform actions described by Figure 18 The other set of modules shown performs one or more functions.

[0188] Figure 19 Figure 1900 shows an example of a hardware implementation of device 1802 employing processing system 1902. Device 1802' may be a core network device.

[0189] Processing system 1902 can be implemented using a bus architecture (typically represented by bus 1904). Depending on the specific application and overall design constraints of processing system 1902, bus 1904 may include any number of interconnect buses and bridges. Bus 1904 links together various circuits including one or more processors and / or hardware modules represented by processor 1906, modules 1804, 1806, 1808, 1810, etc., and computer-readable medium / memory 1908. Bus 1904 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0190] Processing system 1902 may be coupled to transceiver 1910. Transceiver 1910 is coupled to one or more antennas 1912. Transceiver 1910 provides a device module for communicating with various other devices via a transmission medium. Transceiver 1910 receives signals from one or more antennas 1912, extracts information from the received signals, and provides the extracted information to processing system 1902, specifically, receiving module 1804. Furthermore, transceiver 1910 receives information from processing system 1902 (specifically, transmitting module 1810) and generates signals to be applied to one or more antennas 1912, at least in part, based on the received information. Processing system 1902 includes processor 1906 coupled to computer-readable medium / memory 1908. Processor 1906 is responsible for general processing, including executing software stored on computer-readable medium / memory 1908. When executed by processor 1906, the software causes processing system 1902 to perform the various functions described herein with respect to any particular device. The computer-readable medium / memory 1908 can also be used to store data manipulated by the processor 1906 during software execution. The processing system also includes at least one of modules 1804, 1806, 1808, 1810, etc. These modules may be software modules running in the processor 1906, software modules residing in / stored in the computer-readable medium / memory 1908, one or more hardware modules coupled to the processor 1906, or some combination thereof. The processing system 1902 may be a component of the network controller 130 and may include a memory 292, a controller / processor 290, and / or a communication unit 294.

[0191] In some aspects, apparatus 1802 includes a means module for establishing a connection with a base station, wherein the connection is associated with a UE and a first UE identifier, wherein the first UE identifier identifies the UE in the core network and is associated with pre-configured uplink resources for the UE; a means module for sending a UE identifier reallocation message to the UE via the base station instructing the UE to replace the first UE identifier with a second UE identifier; a means module for sending a request to the base station to update the first UE identifier to the second UE identifier for the pre-configured uplink resources; and / or the like. The aforementioned means module may be one or more of the aforementioned means module of apparatus 1802 and / or a processing system 1902 of apparatus 1802 configured to perform the functions listed herein. As described elsewhere herein, processing system 1902 may include memory 292, controller / processor 290, and / or communication unit 294. In one configuration, the aforementioned means module may be memory 292, controller / processor 290, and / or communication unit 294 configured to perform the functions and / or operations listed herein.

[0192] Figure 19 This is provided as an example. Other examples may differ from the combination. Figure 19 described.

[0193] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is illustrative of the method. Based on design preferences, it should be understood that the specific order or hierarchy of blocks in the process / flowchart can be rearranged. Furthermore, some blocks may be combined or omitted. The appended method claims present elements of various blocks in a sample order and are not intended to limit one to the specific order or hierarchy presented.

[0194] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily be apparent to those skilled in the art, and the general principles defined herein may apply to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be consistent with the full scope of the language claims, wherein, unless specifically stated otherwise, elements referenced in the singular are not intended to mean “one and only one,” but rather “one or more.” The term “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or more advantageous than other aspects. Unless specifically stated otherwise, the term “some” means one or more. Combinations such as “at least one of A, B, or C,” “at least one of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "at least one of A, B, and C," and "A, B, C, or any combination thereof" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described in this disclosure that are known to or will be known hereafter by those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. No claim element is to be construed as a device module plus function unless the element is expressly recited using the phrase "device module for...".

Claims

1. A method of wireless communication performed by a user equipment UE, comprising: sending a radio resource control (RRC) connection request to a network entity, wherein the connection request includes a first UE identifier that identifies the UE in a core network; receiving a configuration for pre-configured uplink resources PUR from the network entity, wherein the configuration indicates uplink resources and includes a PUR identifier, performing a UE identifier reallocation procedure to allocate a second UE identifier to the UE, wherein the second UE identifier is different from the first UE identifier and the UE identifier reallocation procedure does not cause the PUR identifier to change; as well as After performing a UE identifier reallocation procedure, a message including at least one of the PUR identifier or the second UE identifier is sent to the network entity.

2. The method according to claim 1, wherein: Communicating with the network entity includes sending a pre-configured uplink message to the network entity in the uplink resources, wherein the pre-configured uplink message includes uplink data. 3 . The method of claim 1 , further comprising sending a message including the PUR identifier to the network entity.

4. The method according to claim 1, wherein the UE identifier reallocation process comprises: A message is received causing the UE to replace the first UE identifier with a second UE identifier.

5. The method according to claim 1, wherein: The first UE identifier is a non-access stratum NAS identifier, a service temporary mobile subscriber identity S-TMSI or a fifth generation 5G TMSI.

6. The method according to claim 1, wherein: The first UE identifier is a first non-access stratum NAS identifier, a first serving temporary mobile subscriber identity S-TMSI or a first fifth generation 5G S-TMSI, and the PUR identifier is a second NAS identifier, a second S-TMSI or a second 5G S-TMSI.

7. The method of claim 1, wherein the message transmitted after performing a UE identifier reallocation procedure includes the PUR identifier and the second UE identifier.

8. A method of wireless communication performed by a network entity, comprising: receiving a radio resource control (RRC) connection request from a user equipment (UE), wherein the connection request comprises a first UE identifier identifying the UE in a core network; sending a configuration for pre-configured uplink resources PUR to the UE, wherein the configuration indicates uplink resources and includes a PUR identifier, performing a UE identifier reallocation procedure to allocate a second UE identifier to the UE, wherein the second UE identifier is different from the first UE identifier and the UE identifier reallocation procedure does not cause the PUR identifier to change; as well as After performing a UE identifier reallocation procedure, a message including at least one of the PUR identifier or the second UE identifier is received from the UE.

9. The method according to claim 8, wherein: Communicating with the UE includes receiving a pre-configured uplink message from the UE in the uplink resources, wherein the pre-configured uplink message includes uplink data.

10. The method of claim 8, wherein the UE identifier reallocation procedure comprises sending a message causing the UE to replace a first UE identifier with a second UE identifier.

11. The method according to claim 8, wherein: The first UE identifier is a first non-access stratum NAS identifier, a first service temporary mobile subscriber identity S-TMSI or a first fifth generation 5G S-TMSI, and the second UE identifier is a second NAS identifier, a second S-TMSI or a second 5G S-TMSI.

12. The method of claim 8, further comprising identifying a context associated with the preconfigured uplink resources based at least in part on the PUR identifier.

13. The method of claim 8, wherein the message transmitted after performing a UE identifier reallocation procedure includes the PUR identifier and the second UE identifier.

14. A user equipment UE for wireless communication, comprising: Memory; and One or more processors, coupled to the memory, the one or more processors configured to: sending a radio resource control (RRC) connection request to a network entity, wherein the connection request includes a first UE identifier that identifies the UE in a core network; receiving a configuration for pre-configured uplink resources PUR from the network entity, wherein the configuration indicates uplink resources and includes a PUR identifier, performing a UE identifier reallocation procedure to allocate a second UE identifier to the UE, wherein the second UE identifier is different from the first UE identifier and the UE identifier reallocation procedure does not cause the PUR identifier to change; as well as After performing a UE identifier reallocation procedure, a message including at least one of the PUR identifier or the second UE identifier is sent to the network entity.

15. The UE according to claim 14, wherein: The one or more processors, when communicating with the network entity, are configured to send a pre-configured uplink message to the network entity in the uplink resources, wherein the pre-configured uplink message includes uplink data.

16. The UE according to claim 14, wherein: The one or more processors are further configured to send a message including the PUR identifier to a network entity.

17. The UE according to claim 14, wherein: The first UE identifier is a first non-access stratum NAS identifier, a first service temporary mobile subscriber identity S-TMSI or a first fifth generation 5G S-TMSI, and the second UE identifier is a second NAS identifier, a second S-TMSI or a second 5G S-TMSI.

18. The UE according to claim 14, wherein the UE identifier reallocation process comprises: A message is received causing the UE to replace the first UE identifier with a second UE identifier.

19. The UE according to claim 14, wherein: The first UE identifier is a non-access stratum NAS identifier, a service temporary mobile subscriber identity S-TMSI or a fifth generation 5G TMSI.

20. The UE of claim 14, wherein the message transmitted after performing a UE identifier reallocation procedure includes the PUR identifier and the second UE identifier.

21. A network entity for wireless communication, comprising: Memory; and One or more processors coupled to the memory, the one or more processors configured to: receiving a radio resource control (RRC) connection request from a user equipment (UE), wherein the connection request comprises a first UE identifier identifying the UE in a core network; sending a configuration for pre-configured uplink resources PUR to the UE, wherein the configuration indicates uplink resources and includes a PUR identifier, performing a UE identifier reallocation procedure to allocate a second UE identifier to the UE, wherein the second UE identifier is different from the first UE identifier and the UE identifier reallocation procedure does not cause the PUR identifier to change; as well as After performing a UE identifier reallocation procedure, a message including at least one of the PUR identifier or the second UE identifier is received from the UE.

22. The network entity according to claim 21, wherein the UE identifier reallocation procedure comprises: A message is sent causing the UE to replace the first UE identifier with a second UE identifier.

23. The network entity of claim 21, wherein the message sent after performing a UE identifier reallocation procedure includes the PUR identifier and the second UE identifier.

24. A user equipment UE for wireless communication, comprising: a component for sending a Radio Resource Control (RRC) connection request to a network entity, wherein the connection request comprises a first UE identifier identifying the UE in a core network; a component for receiving a configuration for pre-configured uplink resources PUR from the network entity, wherein the configuration indicates uplink resources and comprises a PUR identifier, a component for performing a UE identifier reallocation procedure to allocate a second UE identifier to the UE, wherein the second UE identifier is different from the first UE identifier and the UE identifier reallocation procedure does not cause the PUR identifier to change; a component for sending a message including at least one of the PUR identifier or the second UE identifier to the network entity after performing a UE identifier reallocation procedure; and and components for communicating with the network entity based at least in part on the configuration.

25. A network entity for wireless communication, comprising: a component for receiving a Radio Resource Control (RRC) connection request from a user equipment (UE), wherein the connection request comprises a first UE identifier identifying the UE in a core network; a component for sending a configuration for pre-configured uplink resources (PUR) to the UE, wherein the configuration indicates uplink resources and includes a PUR identifier, a component for performing a UE identifier reallocation procedure to allocate a second UE identifier to the UE, wherein the second UE identifier is different from the first UE identifier, and wherein the UE identifier reallocation procedure does not cause the PUR identifier to change; and a component for receiving, after performing a UE identifier reallocation procedure, a message from the UE including at least one of the PUR identifier or the second UE identifier; and Components for communicating with the UE based at least in part on the configuration.

Images