CN109076479B - Tracking user equipment at radio access network level - Google Patents

Abstract

Embodiments of the present disclosure describe methods and apparatus for providing a mechanism for tracking at the radio access network level of user equipment.

Description

Tracking user equipment at radio access network level

Technical Field

Embodiments of the present disclosure relate generally to the field of networks and, more particularly, to an apparatus, system, and method for radio access network level tracking.

Background

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of the various embodiments. However, it will be apparent to one having ordinary skill in the art, having had the benefit of the present disclosure, that the various aspects of the embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail.

In Long Term Evolution (LTE), User Equipment (UE) in idle state is tracked on a Core Network (CN) level on a CN-based basis. For CN-based tracking, an evolved node b (enb) may broadcast a tracking area update message in each cell. When the UE crosses the tracking area, it performs a tracking area update on the CN. This provides the CN with information about the location of the UE at the tracking area level. When there is downlink data for the UE, the CN pages the UE in the tracking area to locate the UE. Radio Access Network (RAN) -based mobility management involves managing inactive UEs (e.g., UEs that are not in an active communication state and are placed in a suspended state). This may be the RAN equivalent to an idle state. There is a need to define mechanisms to track UE location to assist RAN-based mobility management.

Drawings

The embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings.

FIG. 1 illustrates an architecture of a system according to some embodiments.

Figure 2 illustrates a control plane protocol stack in accordance with some embodiments.

FIG. 3 illustrates a message flow according to some embodiments.

Fig. 4 illustrates an example operational flow/algorithm structure of a user equipment according to some embodiments.

Fig. 5 illustrates an example operational flow/algorithm structure of an access node according to some embodiments.

Fig. 6 illustrates an example operational flow/algorithm structure of an access node according to some embodiments.

FIG. 7 illustrates an electronic device in accordance with some embodiments.

Fig. 8 illustrates a baseband circuit according to some embodiments.

FIG. 9 illustrates hardware resources according to some embodiments.

Detailed Description

In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. Like numerals designate like parts throughout the drawings and these detailed descriptions are shown by way of illustrative embodiments which may be practiced. It is to be understood that other embodiments may be utilized and structural or logical modifications may be made without departing from the scope of the present disclosure.

Various operations may be described as multiple discrete actions or operations performed in turn in a manner that is most helpful in understanding the claimed subject matter. However, the order of description should not be construed as to imply that these operations are necessarily performed in order. In particular, these operations may not be performed in the order of presentation. The operations described may be performed in an order different than the described embodiments. Various additional operations may be performed in additional embodiments or described operations may be omitted.

For the purposes of this disclosure, the phrases "a or B", "a and/or B", and "a/B" mean "a", "B", or "a and B".

The description may use the phrases "in one embodiment" or "in an embodiment," which each refer to one or more of the same or different embodiments. In addition, the terms "comprising," "including," "having," and the like, as used with respect to embodiments of the present disclosure, are synonymous.

Embodiments of the present disclosure describe mechanisms to enable RAN-level tracking without broadcasting two area identifiers and without having the UE perform two levels of update signaling (e.g., Core Network (CN) and Radio Access Network (RAN) -level Tracking Area Update (TAU) procedures). This may greatly reduce the amount of data broadcast and may also reduce uplink and downlink signaling. These spectral efficiencies can result in reduced processing by the UE and the network, which can conserve battery in the UE.

As will be described, some embodiments may reuse the CN level tracking area mechanism at the RAN level. In some embodiments, the UE may perform a CN-based tracking area update by sending only, for example, a CN-level TAU message. The RAN node may detect and use these CN level TAU messages sent by the UE to track the UE at the RAN level as well. This may then be used to identify a paging area (e.g., an area in which the UE needs to be paged) to reach the UE. Note that the RAN (e.g., Access Node (AN)) does not necessarily use the CN level TAU message as such, but merely uses the CN level TAU message as evidence of UE access in the cell. Thus, the AN can infer from the cell the TA in which the UE accesses. The AN can be confident that the UE will initiate a message when it crosses a TA boundary because the UE needs to update the CN with a non-access stratum (NAS) TAU. This RAN level tracking may be applied when the UE is in an inactive state, which may also be referred to as a suspended or loose connected (light connected) state in some contexts.

Fig. 1 illustrates an architecture of a system 100 of networks according to some embodiments. The system 100 is shown to include a UE 101. The UE 101 is illustrated as a smart phone (e.g., a handheld touch screen mobile computing device connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a Personal Digital Assistant (PDA), pager, laptop computer, desktop computer, wireless handset, or any computing device that includes a wireless communication interface.

In some embodiments, the UE 101 may include an internet of things (IoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-lived UE connections. IoT UEs may utilize technologies such as machine-to-machine (M2M) or Machine Type Communication (MTC) to exchange data with MTC servers or devices via Public Land Mobile Networks (PLMNs), distance-based services (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated data exchange. IoT networks describe interconnecting IoT UEs that may include uniquely identifiable embedded computing devices (in an internet architecture) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connection of the IoT network.

UE 101 may be configured to connect (e.g., communicatively couple) with AN (e.g., AN 111 or AN 112) of RAN 110 via a Uu interface. For purposes of describing various embodiments, the UE 101 may first connect with a source AN, which may be one of AN 111 or AN 112, and then with a target AN, which may be the other of AN 111 or AN 112. In some embodiments, the source AN may configure the UE 101 for RAN-level or CN-level TAU procedures, while the UE 101 may perform at least a portion of the configured procedures with the target AN.

RAN 110 may be, for example, AN evolved universal terrestrial radio access network (E-UTRAN) (in which case the AN may be AN evolved node b (enb)), a next generation RAN (ng RAN) (in which case the AN may be a next generation node b (gnb)), or some other type of RAN. The UE 101 may utilize an air interface protocol to enable communicative coupling over the Uu interface. The air interface protocol may conform to a cellular communication protocol such as a global system for mobile communications (GSM) protocol, a Code Division Multiple Access (CDMA) network protocol, a push-to-talk (PPT) protocol, a push-to-talk over cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.

RAN 110 may include one or more ANs that enable connection 103. These ANs may be referred to as Base Stations (BSs), node BS, enbs, gnbs, RAN nodes, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage in a geographic area (e.g., a cell). RAN 110 may include one or more RAN nodes for providing macro cells and one or more RAN nodes for providing micro or pico cells (e.g., cells with smaller coverage areas, smaller user capacities, or higher bandwidths than macro cells).

Either of ANs 111 and 112 may terminate the air interface protocol and may be the first point of contact for UE 101. In some embodiments, any one of ANs 111 and 112 may implement various logical functions of RAN 110 including, but not limited to, Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

The AN 111/112 of RAN 110 may communicate with other ANs 112/111 (or some other AN) over AN X2 signaling interface.

In accordance with some embodiments, UE 101 may be configured to communicate with any of ANs 111 and 112, or with other UEs, using Orthogonal Frequency Division Multiplexed (OFDM) communication signals over a multicarrier communication channel in accordance with various communication techniques such as, but not limited to, AN Orthogonal Frequency Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink or ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signal may include a plurality of orthogonal subcarriers. In some embodiments, the downlink resource grid can be used for downlink transmissions from any of ANs 111 and 112 to UE 101, while uplink transmissions can utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, where the time-frequency grid is the physical resource in the downlink in each slot. This time-frequency plane representation is a common practice for OFDM systems, which makes radio resource allocation more intuitive. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one time slot in a radio frame. The smallest time-frequency unit in the resource grid is denoted as a resource element. Each resource grid may include a plurality of resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a batch of resource elements; in the frequency domain, this may represent the minimum number of resources that can currently be allocated. There are a number of different physical downlink channels that may be conveyed using such resource blocks.

The Physical Downlink Shared Channel (PDSCH) may carry user data and higher layer signaling to the UE 101. A Physical Downlink Control Channel (PDCCH) may carry information on a transport format and resource allocation with respect to a PDSCH channel, and the like. It may also inform the UE 101 about the transport format, resource allocation, and hybrid automatic repeat request (H-ARQ) for the uplink shared channel. In general, downlink scheduling (assigning control and shared channel resource blocks to the UE 101 in a cell) can be performed at any of the ANs 111 and 112 based on channel quality information fed back from the UE 101. The downlink resource allocation information may be sent on a PDCCH used for (e.g., allocated to) the UE 101.

The PDCCH may use Control Channel Elements (CCEs) to convey control information. The PDCCH complex-valued symbols may first be organized into quadruplets (quadruplets) before being mapped to resource elements, which may then be arranged using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of resource elements called Resource Element Groups (REGs), where each resource element group includes four physical resource elements. Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH may be transmitted using one or more CCEs according to a channel condition and a size of Downlink Control Information (DCI). Four or more different PDCCH formats are defined in LTE, each PDCCH format having a different number of CCEs (e.g., aggregation level L ═ 1, 2, 4, or 8)

Some embodiments may use the concept of resource allocation for control channel information as an extension of the above concept. For example, some embodiments may utilize an Enhanced Physical Downlink Control Channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more Enhanced Control Channel Elements (ECCEs). Similar to the above, each ECCE may correspond to nine sets of physical resource elements called Enhanced Resource Element Groups (EREGs), each enhanced resource element group including four physical resource elements. In some cases, ECCE may have other numbers of EREGs.

RAN 110 is shown communicatively coupled to CN 120 via S1 interface 113. In this embodiment, the S1 interface 113 is divided into two parts: AN S1-U interface 114 to carry traffic data between ANs 111 and 112 and serving gateway (S-GW)122, and AN S1 Mobility Management Entity (MME) interface 115 to be a signaling interface between ANs 111 and 112 and MME 121.

In this embodiment, CN 120 includes MME121, S-GW 122, Packet Data Network (PDN) gateway (P-GW)123, and Home Subscriber Server (HSS) 124. MME121 may be similar in function to the control plane of a conventional serving General Packet Radio Service (GPRS) support node (SGSN). MME121 may manage mobility aspects in access, such as gateway selection and tracking area list management. HSS 124 may include a database of network users that includes subscription-related information that supports handling of communication sessions by network entities. The CN 120 may include one or more HSS 124 depending on the number of mobile subscribers, device capabilities, network organization, etc. For example, HSS 124 may provide support for routing/roaming, authentication, authorization, name/address resolution, location dependency, and the like.

S-GW 122 may terminate S1 interface 113 to RAN 110 and route data packets between RAN 110 and EPC network 120. In addition, S-GW 122 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3 GPP mobility. Other functions may include lawful interception, billing, and some policy enforcement.

The P-GW 123 may terminate the SGi interface to the PDN. The P-GW 123 may route data packets between the CN 123 and an external network, such as a network including an application server 130 (alternatively referred to as an Application Function (AF)), via an Internet Protocol (IP) interface 125. In general, the application server 130 may be an element that provides a core network (e.g., UMTS Packet Service (PS) domain, LTE PS data services, etc.) to applications that use IP bearer resources. In the present embodiment, P-GW 123 is shown communicatively coupled to application server 130 via an IP communications interface 125. The application server 130 may also be configured to support one or more communication services (e.g., voice over internet protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 101 via the CN 120.

P-GW 123 may also be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF)126 is a policy and charging control element of CN 120. In a non-roaming scenario, there may be a single PCRF in a Home Public Land Mobile Network (HPLMN) associated with an internet protocol connectivity access network (IP-CAN) session for a UE. In a roaming scenario with local traffic breakthrough, there may be two PCRFs associated with the IP-CAN session of the UE: a home PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). PCRF 126 may be communicatively coupled to application server 130 via P-GW 123. Application server 130 may signal to PCRF 126 the new service flow and select the appropriate quality of service (QoS) and charging parameters. PCRF 126 may provide the rules in a Policy and Charging Enhancement Function (PCEF) (not shown) using appropriate Traffic Flow Templates (TFTs) and QoS class identifiers, which initiate QoS and charging as specified by application server 130.

Figure 2 illustrates a control plane protocol stack in accordance with some embodiments. In the present embodiment, control plane 200 is shown as a communication protocol stack between UE 101, AN 111/112, and MME 124.

PHY layer 204 may transmit/receive information used by MAC layer 208 over one or more air interfaces. The PHY layer 204 may also perform link adaptive or Adaptive Modulation and Coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 220. PHY layer 204 may also perform error detection on transport channels, Forward Error Correction (FEC) encoding/decoding of transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and multiple-input multiple-output (MIMO) antenna processing.

The MAC layer 208 may perform mapping between logical channels and transport channels, multiplexing of MAC Service Data Units (SDUs) from one or more logical channels onto transport blocks delivered to the PHY layer 204 via transport channels, demultiplexing of MAC SDUs from transport blocks delivered from the PHY layer 204 via transport channels onto one or more logical channels, multiplexing of MAC SDUs onto transport blocks, scheduling information reporting, error correction by hybrid automatic repeat request (HARQ), and logical channel prioritization.

The RLC layer 212 may operate in a variety of operating modes including: transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layer 212 may perform transmission of upper layer Protocol Data Units (PDUs), error correction of AM data transmission by automatic repeat request (ARQ), and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. The RLC layer 212 may also perform re-segmentation of RLC data PDUs for AM data transmission, reordering RLC data PDUs for UM and AM data transmission, detecting duplicate data for UM and AM data transmission, discarding RLC SDUs for UM and AM data transmission, detecting protocol errors for AM data transmission, and performing RLC re-establishment.

The PDCP layer 216 may perform header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-order delivery of upper layer PDUs when lower layers are reconstructed, eliminate copies of lower layer SDUs when lower layers for radio bearers mapped onto the RLC AM are reconstructed, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer based data discard, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.). The main services and functions of the RRC layer 220 may include system information related to the non-access stratum (NAS) (e.g., included in a Master Information Block (MIB)) or broadcast of System Information Blocks (SIBs), broadcast of system information related to the Access Stratum (AS), paging, establishment, hold, and release of RRC connections between the UE and the RAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, hold, and release of point-to-point radio bearers, security functions including key management, inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting. The MIB and SIBs may include one or more Information Elements (IEs), which may include corresponding data fields or data structures, respectively. In some embodiments, the system information broadcast by the RRC layer 220 may include a CN level TA identifier. The UE 101 may refer to the CN-level TA identifier to determine whether the UE 101 needs to perform a tracking area update, as described in further detail below.

The RRC layer 220 and its lower layers may be collectively referred to AS an AS. The UE 101 and AN 111/112 may utilize a Uu interface (e.g., LTE-Uu interface) to exchange control plane data via a protocol stack including AS (e.g., PHY layer 204, MAC layer 208, RLC layer 212, PDCP layer 216, and RRC layer 220).

NAS layer 224 may form the highest layer of the control plane between UE 104 and MME 124. The NAS layer 224 may support mobility and session management procedures for the UE 104 to establish and maintain IP connectivity between the UE 104 and the P-GW. In some embodiments, the NAS layer 224 of the MME 124 may configure the NAS layer 224 of the UE 101 with a CN level TA. For example, the MME 124 may send configuration information to the UE 101 including a CN level tracking area list. The CN level tracking area list may include one or more tracking area identifiers that collectively define the CN level TAs of the UE 101. When the UE 101 moves to a tracking area with an identifier that is not in the CN level tracking area list, the UE 101 may be triggered to provide a tracking area update message.

In some embodiments, the AS of AN 111/112 may configure the RAN-level TA with the AS of UE 101. For example, AN 111/112 may send configuration information to UE 101 including a RAN-level tracking area list. The RAN-level tracking area list may include one or more tracking area identifiers that collectively define a RAN-level TA for the UE 101. When the UE 101 moves to a tracking area with an identifier that is not in the RAN level tracking area list, the UE 101 may be triggered to provide a tracking area update message.

The tracking area identifiers in the CN-level tracking area list may be the same as or different from the tracking area identifiers in the RAN-level tracking area list. In some embodiments, only one tracking area list may be used. This may be a tracking area list configured by NAS layer 224 of MME 124.

The S1 application protocol (S1-AP) layer 228 may support the functionality of the S1 interface and may include basic procedures (EPs). AN EP may be AN interactive element between AN 111/112 and CN 120. The S1-AP layer services may include two groups: UE-related services and non-UE-related services. These services perform functions including, but not limited to: E-UTRAN radio access bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transport.

Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as SCTP/IP layer) 232 may ensure reliable delivery of signaling messages between AN 111/112 and MME 124 based on IP protocols supported by IP layer 236. The L2 layer 240 and the L1 layer 244 may refer to communication links (e.g., wired or wireless) that the AN 111/112 and MME 124 use to exchange information.

The AN 111/112 and MME 124 may exchange control plane data via a protocol stack including L1 layer 244, L2 layer 240, IP layer 236, SCTP layer 232, and S1-AP layer 228 using the S1-MME interface.

Referring again to fig. 1, in some embodiments, AN 111/112 may broadcast only CN level tracking area IDs, and UE 101 may perform only CN level tracking area updates. When AN 111/112 receives a transmission from a UE 101, AN 111/112 may record AN indication of the cell and tracking area in which the UE 101 performed some activity (e.g., sending the transmission). The transmission may be a TAU message. The recorded indication of the cell and tracking area in which the UE performs activity may be used by the AN 111/112 as a RAN-level paging area. The RAN-level paging area may be AN area in which the UE 101 is allowed to move without generating TAU messages, and thus is AN area in which the AN 111/112 may need to page the UE 101 in order to locate the UE 101.

In some embodiments, the AN 111/112 may use AN algorithm to determine which cells of the tracking area to page. For example, AN 111/112 may first page the cell in which UE 101 sent the TAU message, and then page the remaining tracking areas in the widened area.

The activity performed by the UE 101 may or may not be a tracking area update. For example, the activity may be UL or DL data transmission, or it may be a TAU procedure. In most cases, the AN 111/112 need not know that the UE has performed a TAU, because the AN 111/112 can simply assume that the tracking area where the most recent activity occurred is the registration tracking area of the UE 101. The exception to this is that the CN 120 allocates a tracking area list to the UE 101, as described in more detail below.

The RAN-level paging area is an area representing a range in which the location of the UE 101 is uncertain from the perspective of the RAN 110. Thus, the RAN-level paging area corresponds to an area in which the UE 101 must be paged to locate the UE 101. During movement of AN inactive UE, if the RAN-level paging area includes a set of cells, some cells may be provided by different ANs. Therefore, X2 signaling may be considered. X2 signaling may be used to carry paging messages to other ANs in the RAN-level paging area whenever there is downlink data for the UE 101. The RAN-level paging area may also correspond to the RAN-level tracking area described in this document. Similar to the above, the CN-level tracking/paging area is a range where the location of the UE 101 is uncertain from the perspective of the CN 120.

To enable AN 111/112 to associate CN level tracking area updates with the context of UE 101, UE 101 should use a known RAN level UE identifier as part of the tracking area update. This may be a resume identifier provided to the UE 101 when the UE 101 is suspended (or otherwise placed in an inactive state). Alternatively, a CN-level identifier may be used as the RAN-level identifier. For example, a CN level System architecture evolution temporary Mobile subscriber identity (S-TMSI), which the UE 101 needs to provide to the AN 111/112 during CN level TAUs, may be used as the RAN level identifier. If S-TMSI is used as the RAN level identifier, the CN 120 must provide the S-TMSI of the UE 101 to the AN 111/112. Similar CN level tracking may be applied to 5G or next generation core networks and may also be applied to future systems. In these cases, the messages and details may be different, but the tracking concept as described above may be applied, which may then be used by the AN of future technologies.

When the network tracks UE 101 using multiple TA lists, this information may be provided by the node of CN 120 (e.g., MME 121) to AN 111/112, making AN 111/112 aware that AN 111/112 may need to page in order to reach the area of UE 101 (TA list). In some embodiments, the TA list may be provided as a list of TA identifiers, ANs, cells, and the like. If there is a single TA list, MME121 may not need to provide a TA list to AN 111/112 because the TA list may be inferred by AN 111/112. In some embodiments, AN 111/112 may use any access attempts made by UE 101 to indicate the current tracking area of UE 101. The UE access may be, for example, sending data, requesting a bearer, performing CN level TAU, etc. The exact reason for the NAS message itself may be independent of the AN 111/112.

Figure 3 illustrates a flow 300 for using RAN-level tracking and tracking area updates with CN-level identifiers, in accordance with some embodiments.

The flow 300 assumes that the UE 101 is initially connected with the AN 1111. At 304, the UE 101 can determine that the UE 101 has crossed a TA boundary. The UE 101 may receive the system information broadcast by AN 2112. The system information can include a TA identifier associated with the AN 2112. If the TA identifier does not match the TA list(s) that the UE 101 has configured, the UE 101 can learn that it has crossed the TA boundary and needs to perform a TA update.

At 304, the UE 101 can send a resume request message to AN 2112. The resume request message may include a UE resume identifier. The UE resume identifier may have been provided to the UE 101 by the AN 1111 while the UE 101 was in the inactive state. When AN 111 places UE 101 in AN inactive state, it can store the context of UE 101 and the relevant UE resume identifier. This may allow the UE 101 to quickly become active and resume communication with the network when needed.

At 312, upon receiving the resume request message, AN 2112 may indicate the location of the UE 101 based on the cell receiving the resume request message.

At 316, AN 2112 can send a request using the UE resume ID to obtain the UE 101's context stored by AN 1111. At 320, AN 1111 may respond to the request by sending the UE context.

At 324, AN 2112 can store the UE context and the location (e.g., cell and TA) in which the UE 101 performs the TA update.

Flow 400 may include, at 328, MME121 and AN 112 may participate in a path switch procedure. The path switch procedure may include AN 112 sending a path switch request to MME121 to inform MME121 that UE 101 has switched cells. MME121 may then respond with a path switch acknowledgement. After the path switch procedure, the UE may perform CN level TAU by sending a TAU message (which may be a NAS message) to the CN 120 at 332. AN 112 may receive the TAU message and forward the message to MME 121.

At 336, MME121 may send a TA list to AN 2112. The TA list may be a CN level TA list defining CN level tracking areas. In this embodiment, the RAN-level TA list may be the same as, e.g., have a one-to-one correspondence with, the CN-level TA list.

At 340, the AN 2112 can forward the TA list to the UE 101.

At 344, the AN 2112 may decide to place the UE 101 in AN inactive state and send a suspend message to the UE 101. The suspend message may be sent after a non-communication period of the UE 101.

At 348, AN2 may receive DL data directed to UE 101. The AN 2112 may then page the cell in which the TA list UE 101 is TA updated at 352. As described above, in some embodiments, AN 2112 may initially page the cell corresponding to the location saved at 312. If the UE 101 does not respond, the AN 112 may page one or more cells in the TA list provided to the AN 2112 at 336.

FIG. 4 illustrates an example operational flow/algorithm structure of the UE 101 according to some embodiments.

Flow/structure 400 may include, at 404, identifying a RAN-level identifier. The RAN-level identifier identified at 404 may be an identifier used in RAN-level TA operation. The RAN level identifier may be a UE resume identifier provided to the UE 101 by the access node when the UE 101 is placed in an inactive state. In some embodiments, the RAN level identifier may be S-TMSI.

Flow/structure 400 may include, at 408, receiving broadcast system information including a TA ID. The UE 101 may cross-reference the TA ID received in the broadcast system information and one or more TA lists defining the TA for the UE 101. In various embodiments, the UE 101 may include only one TA associated therewith. If the TA ID received in the broadcast system information does not match the TA with which the UE 101 is currently associated, the UE 101 can determine that it must provide an update to the network. In some embodiments, the UE 101 may include one or more TA lists. For example, the UE 101 may include a RAN-level TA list or a CN-level TA list. The UE 101 may determine whether the TA ID received in the broadcast system information matches any TA identifier stored in one or more CN/RAN-level TA lists. If the TA ID does not match any TA identifier in the at least one TA list, the flow/structure 400 can proceed to 412 to cause the UE 101 to perform the update.

Flow/structure 400 may include, at 412, sending a RAN-level identifier to AN 111/112. If the UE 101 is configured with a CN level TA list and the TA IDs received in the broadcast system information do not match these identifiers and the CN level TA list, the UE 101 may perform the transmission of RAN level identifiers by sending a NAS message to the MME 121. The NAS message may be, for example, a TAU including a CN level ID (e.g., S-TMSI). The TAU may allow the CN 120 to perform CN level TA updates.

In some embodiments, the UE 101 may be configured with a RAN-level TA list that is different from the CN-level TA list. For example, the RAN-level TA list may be a subset of the CN-level TA list. In some embodiments, if the TA ID received in the broadcast system information matches AN identifier in the CN-level TA list but does not match AN identifier in the RAN-level TA list, the UE 101 may send the RAN-level ID to the AN 111/112 to perform RAN-level TAU, but need not perform a separate TAU on the CN 120, and thus may not send the NAS message TAU.

Fig. 5 illustrates AN example operational flow/algorithm structure 500 of AN 111/112 according to some embodiments.

The flow/structure 500 may include, at 504, receiving a message from the UE 101. In some embodiments, the message received from the UE 101 may include a RAN-level identifier, e.g., a UE recovery identifier.

Flow/structure 500 may also include, at 508, determining that UE 101 is located in a RAN-level paging area. In some embodiments, AN 111/112 may determine that UE 101 is in a particular cell that receives the message. The AN 111/112 may cross-reference the cell and RAN/CN level TA lists to determine the RAN level paging area. AN 111/112 may have previously received a CN-level TA list from CN 120 (e.g., MME 121) if AN 111/112 cross-references the cell and CN-level TA lists.

The flow/structure 500 may also include, at 512, receiving downlink data from the CN 120. Downlink data may be directed to the UE 101, which may be in an inactive state. Flow/structure 500 may also include, at 516, paging the UE 101 in a RAN-level paging area. In some embodiments, AN 111/112 may perform a first round of paging in a cell in which a message is received from a UE at 504. If the UE 101 does not respond to the first paging round, an additional paging round or rounds may be performed in other cells of the RAN-level paging area.

Fig. 6 illustrates AN example operational flow/algorithm structure 600 of AN 111/112 according to some embodiments.

The flow/structure 600 may include, at 604, sending configuration information to the UE 101. The configuration information may include information that configures a RAN-level TA list to the UE 101. The RAN-level TA list may include one or more TA identifiers that collectively define a RAN-level paging area.

Flow/structure 600 may also include, at 608, broadcasting system information including a tracking area identifier associated with a cell in which the system information is broadcast. As described herein, the tracking area identifier may be used by the UE to perform RAN-level tracking and CN-level tracking.

The embodiments described herein may be implemented as a system using suitably configured hardware or software. FIG. 7 illustrates example components of an electronic device 700 for one embodiment. In embodiments, electronic device 100 may be implemented or incorporated in or otherwise part of UE 101, AN 111, AN 112, MME121, or some other electronic device. In some embodiments, electronic device 100 may include application circuitry 702, baseband circuitry 704, Radio Frequency (RF) circuitry 106, front-end module (FEM) circuitry 708, and one or more antennas 710 coupled together at least as shown.

The application circuitry 702 may include one or more application processors. For example, the application circuitry 702 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The one or more processors may include any combination of general-purpose processors and special-purpose processors (e.g., graphics processors, application processors, etc.). The processor may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the system. The baseband circuitry 704 may include circuitry such as, but not limited to, one or more single-core or multi-core processors to perform the various CN/RAN level tracking operations described herein. Baseband circuitry 704 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of RF circuitry 706 and to generate baseband signals for a transmit signal path of RF circuitry 706. Baseband processing circuitry 704 may interface with application circuitry 702 for generating and processing baseband signals and for controlling the operation of RF circuitry 706. For example, in some embodiments, the baseband circuitry 704 may include a second generation (2G) baseband processor 704a, a third generation (3G) baseband processor 704b, a fourth generation (4G) baseband processor 704c, a fifth generation (5G) baseband processor 704h, or one or more other baseband processors 704d for other existing generations, generations under development, or generations developed in the future (e.g., 6G, etc.).

The baseband circuitry 704 (e.g., one or more baseband processors 704a-d, h) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 706. Radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like. In some embodiments, the modulation/demodulation circuitry of baseband circuitry 704 may include Fast Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, the encoding/decoding circuitry of baseband circuitry 704 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functions are not limited to these examples, and other suitable functions may be included in other embodiments.

In some embodiments, the baseband circuitry 704 may include elements of a protocol stack, such as elements of the EUTRAN protocol (including, for example, PHY, MAC, RLC, PDCP, or RRC elements). The Central Processing Unit (CPU)704e of the baseband circuitry 704 may be configured to run elements of a protocol stack for signaling of the PHY, MAC, RLC, PDCP, or RRC layers. In some embodiments, the baseband circuitry 704 may also include NAS elements configured to be executed by the CPU 704 e. In other embodiments, the NAS element may reside in the application circuitry 702.

In some embodiments, the baseband circuitry may include one or more audio Digital Signal Processors (DSPs) 704 f. The one or more audio DSPs 704f may include elements for compression/decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

The baseband circuitry 704 may also include memory/storage 704 g. The memory/storage device 704g may be used to load or store data or instructions for operations performed by the processor of the baseband circuitry 704. The memory/storage for one embodiment may comprise any combination of suitable volatile or non-volatile memory. The memory/storage 704g may include any combination of various levels of memory/storage including, but not limited to, Read Only Memory (ROM) embedded with software instructions (e.g., firmware), random access memory (e.g., Dynamic Random Access Memory (DRAM)), cache, buffers, and the like. The memory/storage device 704g may be shared among various processors or dedicated to a particular processor.

The components of the baseband circuitry may be suitably combined in a single chip or a single chip set, or arranged on the same circuit board. In some embodiments, some or all of the constituent components of baseband circuitry 704 and application circuitry 702 may be implemented together, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry 704 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuitry 704 may support communication with a RAN (e.g., EUTRAN or next generation RAN (ng RAN)), or other Wireless Metropolitan Area Network (WMAN), Wireless Local Area Network (WLAN), Wireless Personal Area Network (WPAN). Embodiments in which the baseband circuitry 704 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

RF circuitry 706 may enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 106 may include switches, filters, amplifiers, etc. that facilitate communication with the wireless network. RF circuitry 706 may include a receive signal path that may include circuitry to down-convert RF signals received from FEM circuitry 708 and provide baseband signals to baseband circuitry 704. RF circuitry 706 may also include a transmit signal path that may include circuitry to up-convert baseband signals provided by baseband circuitry 704 and provide RF output signals to FEM circuitry 708 for transmission.

In some embodiments, RF circuitry 706 may include a receive signal path and a transmit signal path. The receive signal path of RF circuit 706 may include mixer circuit 106a, amplifier circuit 706b, and filter circuit 706 c. The transmit signal path of RF circuitry 706 may include filter circuitry 706c and mixer circuitry 706 a. RF circuitry 706 may also include synthesizer circuitry 706d for synthesizing frequencies for use by mixer circuitry 706a of the receive signal path and the transmit signal path. In some embodiments, mixer circuit 706a of the receive signal path may be configured to down-convert the RF signal received from FEM circuit 708 based on the synthesized frequency provided by synthesizer circuit 706 d. The amplifier circuit 706b may be configured to amplify the downconverted signal, and the filter circuit 706c may be a Low Pass Filter (LPF) or a Band Pass Filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 704 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required. In some embodiments, mixer circuit 706a of the receive signal path may comprise a passive mixer, although the scope of the embodiments is not limited in this respect.

In some embodiments, mixer circuitry 706a of the transmit signal path may be configured to upconvert the input baseband signal based on a synthesis frequency provided by synthesizer circuitry 706d to generate an RF output signal for FEM circuitry 708. The baseband signal may be provided by baseband circuitry 704 and filtered by filter circuitry 706 c. Filter circuit 706c may include a Low Pass Filter (LPF), although the scope of the embodiments is not limited in this respect.

In some embodiments, mixer circuit 706a of the receive signal path and mixer circuit 706a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion or up-conversion, respectively. In some embodiments, the mixer circuit 706a of the receive signal path and the mixer circuit 706a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., hartley image rejection). In some embodiments, mixer circuit 706a of the receive signal path and mixer circuit 706a of the transmit signal path may be arranged for direct down-conversion or direct up-conversion, respectively. In some embodiments, mixer circuit 706a of the receive signal path and mixer circuit 706a of the transmit signal path may be configured for superheterodyne operation.

In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuitry 706 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry, and baseband circuitry 704 may include a digital baseband interface in communication with RF circuitry 706.

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

In some embodiments, synthesizer circuit 706d may be a fractional-N synthesizer or a fractional-N/N +1 synthesizer, although the scope of the embodiments is not limited in this respect (as other types of frequency synthesizers are also suitable). For example, synthesizer circuit 706d may be a delta-sigma (delta-sigma) synthesizer, a frequency multiplier, or a synthesizer including a phase locked loop with a frequency divider.

Synthesizer circuit 706d may be configured to synthesize an output frequency for use by mixer circuit 706a of RF circuit 706 based on the frequency input and the divider control input. In some embodiments, synthesizer circuit 706d may be a fractional N/N +1 synthesizer.

In some embodiments, the frequency input may be provided by a Voltage Controlled Oscillator (VCO), although this is not required. The divider control input may be provided by baseband circuitry 704 or application processor 702 based on a desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a look-up table based on the channel indicated by the application processor 702.

Synthesizer circuit 706d of RF circuit 706 may include a frequency divider, a Delay Locked Loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a dual-mode divider (DMD) and the phase accumulator may be a Digital Phase Accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N +1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, a DLL may include a set of cascaded, tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to divide the VCO period into Nd equal phase groups, Nd being the number of delay elements in the delay line. Thus, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuit 706d may be configured to generate a carrier frequency as the output frequency, while in other embodiments the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with the quadrature generator and frequency divider circuit to generate a plurality of signals at the carrier frequency having a plurality of different phases relative to each other. In some embodiments, the output frequency may be the LO frequency (fLO). In some embodiments, the RF circuit 706 may include an IQ/polarity converter.

FEM circuitry 708 may include a receive signal path that may include circuitry configured to operate on RF signals received from one or more antennas 710, amplify the received signals, and provide amplified versions of the received signals to RF circuitry 706 for further processing. FEM circuitry 708 may also include a transmit signal path, which may include circuitry configured to amplify signals provided by RF circuitry 706 for transmission for one or more of one or more antennas 710.

In some embodiments, FEM circuitry 708 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a Low Noise Amplifier (LNA) that amplifies the received RF signal and provides the amplified receive RF signal as an output (e.g., to RF circuitry 706). The transmit signal path of FEM circuitry 708 may include a Power Amplifier (PA) that amplifies an input RF signal (e.g., provided by RF circuitry 706) and one or more filters that generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 710).

In some embodiments, electronic device 700 may include additional elements such as memory/storage devices, displays, cameras, sensors, or input/output (I/O) interfaces. In some embodiments, electronic device 700 of fig. 7 may be configured to perform one or more processes, techniques, or methods described herein, or portions thereof. For example, electronic device 700 may perform the operations described in fig. 3-6.

Fig. 8 illustrates an example interface of a baseband circuit 804 according to some embodiments. Baseband circuitry 804 may be similar to baseband circuitry 704 and may be substantially used interchangeably with baseband circuitry 704. As discussed above, the baseband circuitry 804 of FIG. 8 may include processors 804A-804E and 804H and a memory 804G for use by the processors. Each of the processors 804A-804E and 804H may include a memory interface 804A-804E and 804H, respectively, to send/receive data to/from the memory 804G.

The baseband circuitry 804 may also include one or more interfaces communicatively coupled to other circuitry/devices, such as a memory interface 812 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 804), an application circuitry interface 814 (e.g., an interface to send/receive data to/from the application circuitry 802 of fig. 8), an RF circuitry interface 816 (e.g., an interface to send/receive data to/from the RF circuitry 806 of fig. 8), and a wireless hardware connectivity interface 818 (e.g., send/receive data to/from Near Field Communication (NFC) components, bluetooth: (r) ((r) ("NFC)

) The components (e.g.,

low energy),

Interfaces for components, and other data communicating components).

Figure 9 is a block diagram illustrating example components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing one or more RAN/CN level tracking methods discussed herein, according to some example embodiments. In particular, fig. 9 shows a schematic representation of a hardware resource 900 that includes one or more processors (or processor cores) 910, one or more memory/storage devices 920, and one or more communication resources 930, each of which may be communicatively coupled via a bus 940. For embodiments that utilize node virtualization (e.g., Network Function Virtualization (NFV)), hypervisor 902 may be executed to provide an execution environment for one or more network slices/subslices to utilize hardware resources 900.

Processor 910 (e.g., a CPU, a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP) such as a baseband processor, an Application Specific Integrated Circuit (ASIC), a Radio Frequency Integrated Circuit (RFIC), other processor, or any suitable combination thereof) may include, for example, processor 912 and processor 914.

Memory/storage 920 may include a main memory, a disk storage device, or any suitable combination thereof. The memory/storage 920 may include, but is not limited to, any type of volatile or non-volatile memory such as Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid state memory devices, and the like.

The communication resources 930 may include interconnection or network interface components or other suitable devices that communicate with one or more peripheral devices 904 or one or more databases 906 via the network 908. For example, communication resources 930 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, Near Field Communication (NFC) components, a wireless communication component, and/or a wireless communication component,

The components (e.g.,

low energy),

Components, and other communication components.

The instructions 950 may include software, programs, applications, applets, applications, or other executable code for causing at least any one of the processors 910 to perform any one or more of the methods discussed herein.

In embodiments where the hardware resources 900 are incorporated into the UE 101, the instructions 950 may cause the processor 910 to perform: the operational flow/algorithm structure 400; for example, the operation of the UE described in the flow of fig. 3; or other operations of the UE, for example, as described with respect to fig. 1 and 2.

In embodiments where hardware resources 900 are incorporated into AN 111/112, instructions 950 may cause processor 910 to perform: the operational flow/ algorithm structure 500 or 600; for example, the operation of AN as described in the flow of fig. 3; or other operations of the AN, for example, as described with respect to fig. 1 and 2.

In embodiments where hardware resources 900 are incorporated into MME 124, instructions 950 may cause processor 910 to perform operations of the MME, e.g., as described in the flow of fig. 3 or with respect to fig. 1 and 2.

The instructions 950 may reside, completely or partially, within the processor 910 (e.g., within a cache memory of the processor), the memory/storage 920, or any suitable combination thereof. Additionally, any portion of instructions 950 may be transmitted to hardware resource 900 from any combination of peripherals 904 or database 906. Thus, the memory of the processor 910, the memory/storage 920, the peripherals 904, and the database 906 are examples of computer-readable media and machine-readable media.

Some non-limiting examples are provided below.

Example 1 may include a user equipment having circuitry to: identifying a Radio Access Network (RAN) level identifier for use in Radio Access Network (RAN) level Tracking Area (TA) operations; receiving broadcast system information including a tracking area identifier; and sending a RAN-level ID to allow the RAN to perform RAN-level TA updates based on the tracking area identifier.

Example 2 may include the UE of example 1 or some other example herein, wherein the circuitry is further to: tracking area updates are sent to allow the core network to perform CN level TA updates.

Example 3 may include the UE of example 2 or some other example herein, wherein the tracking area update comprises a CN level identifier.

Example 4 may include the UE of example 3 or some other example herein, wherein the CN-level identifier is a system architecture evolution temporary mobile subscriber identity (S-TMSI).

Example 5 may include the UE of example 1 or some other example herein, wherein the RAN-level identifier is a resume identifier or a system architecture evolution temporary mobile subscriber identity (S-TMSI) provided to the UE when the UE is suspended.

Example 6 may include the UE of example 1 or some other example herein, wherein the circuitry is further to: receiving configuration information from a RAN, the configuration information including a RAN-level tracking area list, the RAN-level tracking area list including one or more tracking area identifiers; and transmitting the RAN-level identifier based on a determination that the tracking-area identifier is not in the RAN-level tracking-area list.

Example 7 may include the UE of example 6 or some other example herein, wherein the configuration information is first configuration information, and the circuitry is further to: receiving second configuration information from the CN, the second configuration information comprising a CN tracking area list, the CN tracking area list comprising at least one tracking area identifier.

Example 8 includes the UE of example 7 or some other example herein, wherein the CN-level tracking area list has a one-to-one correspondence with the RN-level tracking area list.

Example 9 may include AN having circuitry to: receiving a message from a User Equipment (UE), the message including a Radio Access Network (RAN) level identifier; determining, based on the uplink message, that the UE is located in a RAN-level paging area; receiving downlink data directed to the UE; and ceasing paging the UE in the one or more cells of the RAN-level paging area.

Example 10 may include the AN of example 9 or some other example herein, wherein the circuitry is further to: broadcasting system information including a tracking area identifier; and receiving an uplink message from the UE based on the tracking area message.

Example 11 may include the AN of example 9 or some other example herein, wherein the circuitry is further to: a request is sent to acquire a context of the UE from another AN previously associated with the UE, wherein the request includes a RAN-level identifier.

Example 12 may include the AN of any one of examples 9 to 11 or some other example herein, wherein the circuitry is further to: receiving a tracking area list from a mobility management entity; and determining a cell of the RAN-level paging area based on the tracking area list.

Example 13 may include the AN of any one of examples 9 to 12 or some other example herein, wherein the circuitry is further to: determining a cell transmitting an uplink message from the UE; paging a UE in the cell; and paging the UE in one or more other cells of the RAN-level paging area if the UE does not respond to the paging in the cell.

Example 14 may include AN Access Node (AN) having circuitry to: sending configuration information to a User Equipment (UE) to configure a Radio Access Network (RAN) level Tracking Area (TA) list to the UE; and broadcasting system information including a tracking area identifier associated with the cell, the tracking area identifier being used to perform both RAN-level tracking and CN-level tracking.

Example 15 may include the AN of example 14 or some other example herein, wherein the RAN-level TA list comprises one or more TA identifiers.

Example 16 may include the AN of example 14 or 15 or some other example herein, wherein the circuitry is further to: a RAN-level identifier for use in RAN-level TA operation is sent to the UE.

Example 17 may include the AN of example 16 or some other example herein, wherein the circuitry is further to: a suspend message is sent to the UE, the suspend message including a resume identifier corresponding to the RAN-level identifier.

Example 18 may include one or more computer-readable media having instructions that, when executed, cause a User Equipment (UE) to: identifying a Radio Access Network (RAN) level identifier for use in Radio Access Network (RAN) level Tracking Area (TA) operations; receiving broadcast system information including a tracking area identifier; and sending a RAN-level ID to allow the RAN to perform RAN-level TA updates based on the tracking area identifier.

Example 19 may include the one or more computer-readable media of example 18 or some other example herein, wherein the instructions, when executed, further cause the UE to: tracking area updates are sent to allow the core network to perform CN level TA updates.

Example 20 may include the one or more computer-readable media of example 19 or some other example herein, wherein the tracking area update comprises a CN level identifier.

Example 21 may include the one or more computer-readable media of example 20 or some other example herein, wherein the CN-level identifier is a system architecture evolution temporary mobile subscriber identity (S-TMSI).

Example 22 may include the one or more computer-readable media of example 18 or some other example herein, wherein the RAN-level identifier is a resume identifier or a system architecture evolution temporary mobile subscriber identity (S-TMSI) provided to the UE when the UE is suspended.

Example 23 may include the one or more computer-readable media of example 18 or some other example herein, wherein the instructions, when executed, further cause the UE to: receiving configuration information from a RAN, the configuration information including a RAN-level tracking area list, the RAN-level tracking area list including one or more tracking area identifiers; and transmitting the RAN-level identifier based on a determination that the tracking-area identifier is not in the RAN-level tracking-area list.

Example 24 may include the one or more computer-readable media of example 23 or some other example herein, wherein the configuration information is first configuration information, and the instructions, when executed, further cause the UE to: receiving second configuration information from the CN, the second configuration information comprising a CN tracking area list, the CN tracking area list comprising at least one tracking area identifier.

Example 25 may include the one or more computer-readable media of example 24 or some other example herein, wherein the CN-level tracking area list has a one-to-one correspondence with the RAN-level tracking area list.

Example 26 may include one or more computer-readable media having instructions that, when executed, cause AN Access Node (AN) to: receiving a message from a User Equipment (UE), the message including a Radio Access Network (RAN) level identifier; determining, based on the uplink message, that the UE is located in a RAN-level tracking area; receiving downlink data directed to the UE; and paging the UE in one or more cells of the RAN-level tracking area.

Example 27 may include the one or more computer-readable media of example 26 or some other example herein, wherein the instructions, when executed, further cause the AN to: broadcasting system information including a tracking area identifier; and receiving an uplink message from the UE based on the tracking area message.

Example 28 may include the one or more computer-readable media of example 26 or some other example herein, wherein the instructions, when executed, further cause the AN to: a request is sent to acquire a context of the UE from another AN previously associated with the UE, the request including a RAN-level identifier.

Example 29 may include the one or more computer-readable media of any one of examples 26 to 28 or some other example herein, wherein the instructions, when executed, further cause the AN to: receiving a tracking area list from a mobility management entity; and determining a cell of the RAN-level paging area based on the tracking area list.

Example 30 may include the one or more computer-readable media of any one of examples 26 to 29 or some other example herein, wherein the instructions, when executed, further cause the AN to: determining a cell transmitting an uplink message from the UE; paging a UE in the cell; and paging the UE in one or more other cells of the RAN-level paging area if the UE does not respond to the paging in the cell.

Example 31 may include one or more computer-readable media having instructions that, when executed, cause AN Access Node (AN) to: sending configuration information to a User Equipment (UE) to configure a Radio Access Network (RAN) level Tracking Area (TA) list to the UE; and broadcasting system information including a tracking area identifier associated with the cell, the tracking area identifier being used to perform both RAN-level tracking and CN-level tracking.

Example 32 may include the one or more computer-readable media of example 31 or some other example herein, wherein the RAN-level TA list comprises one or more TA identifiers.

Example 33 may include the one or more computer-readable media of examples 31 or 32 or some other example herein, wherein the instructions, when executed, further cause the AN to: a RAN-level identifier for use in RAN-level TA operation is sent to the UE.

Example 34 may include the one or more computer-readable media of example 33 or some other example herein, wherein the instructions, when executed, cause the AN to: a suspend message is sent to the UE, the suspend message including a resume identifier corresponding to the RAN-level identifier.

Example 35 may include a method comprising: identifying a Radio Access Network (RAN) level identifier for use in Radio Access Network (RAN) level Tracking Area (TA) operations; receiving broadcast system information including a tracking area identifier; and sending a RAN-level ID to allow the RAN to perform RAN-level TA updates based on the tracking area identifier.

Example 36 may include the method of example 35 or some other example herein, further comprising: tracking area updates are sent to allow the core network to perform CN level TA updates.

Example 37 may include the method of example 36 or some other example herein, wherein the tracking area update comprises a CN level identifier.

Example 38 may include the method of example 37 or some other example herein, wherein the CN-level identifier is a system architecture evolution temporary mobile subscriber identity (S-TMSI).

Example 39 may include the method of example 35 or some other example herein, wherein the RAN-level identifier is a resume identifier or a system architecture evolution temporary mobile subscriber identity (S-TMSI) provided to the UE when the UE is suspended.

Example 40 may include the method of example 35 or some other example herein, further comprising: receiving configuration information from a RAN, the configuration information including a RAN-level tracking area list, the RAN-level tracking area list including one or more tracking area identifiers; and transmitting the RAN-level identifier based on a determination that the tracking-area identifier is not in the RAN-level tracking-area list.

Example 41 may include the method of example 40 or some other example herein, wherein the configuration information is first configuration information, and the method further comprises: receiving second configuration information from the CN, the second configuration information comprising a CN tracking area list, the CN tracking area list comprising at least one tracking area identifier.

Example 42 may include the method of example 41 or some other example herein, wherein the CN-level tracking area list has a one-to-one correspondence with the RAN-level tracking area list.

Example 43 may include a method comprising: receiving a message from a User Equipment (UE), the message including a Radio Access Network (RAN) level identifier; determining, based on the uplink message, that the UE is located in a RAN-level paging area; receiving downlink data directed to the UE; and paging the UE in one or more cells of the RAN-level paging area.

Example 44 may include the method of example 43 or some other example herein, further comprising: broadcasting system information including a tracking area identifier; and receiving a downlink message from the UE based on the tracking area message.

Example 45 may include the method of example 43 or some other example herein, further comprising: a request is sent to acquire a context of the UE from another AN previously associated with the UE, the request including a RAN-level identifier.

Example 46 may include the method of any one of examples 43 to 45 or some other example herein, further comprising: receiving a tracking area list from a mobility management entity; and determining a cell of the RAN-level paging area based on the tracking area list.

Example 47 may include the method of any one of examples 43 to 46 or some other example herein, further comprising: determining a cell transmitting an uplink message from the UE; and paging the UE in the cell; and paging the UE in one or more other cells of the RAN-level paging area if the UE does not respond to the paging in the cell.

Example 48 may include a method comprising: sending configuration information to a User Equipment (UE) to configure a Radio Access Network (RAN) level Tracking Area (TA) list to the UE; and broadcasting system information including a tracking area identifier associated with the cell, the tracking area identifier being used to perform both RAN-level tracking and CN-level tracking.

Example 49 may include the method of example 48 or some other example herein, wherein the RAN-level TA list includes one or more TA identifiers.

Example 50 may include the method of example 48 or 49 or some other example herein, further comprising: a RAN-level identifier for use in RAN-level TA operation is sent to the UE.

Example 51 may include the method of example 50 or some other example herein, further comprising: a suspend message is sent to the UE, the suspend message including a resume identifier corresponding to the RAN-level identifier.

Example 52 may include a method of tracking a User Equipment (UE) at Core Network (CN) and Radio Access Network (RAN) levels using a common tracking area.

Example 53 may include the method of example 52 or some other example herein, wherein only one level of tracking area is broadcast.

Example 54 may include the method of example 52 or some other example herein, wherein the UE performs only one level of tracking area update procedures in an idle state when the UE is in a suspended or connected mode.

Example 55 may include the method of any one of examples 52 to 54 or some other example herein, wherein the access node performs RAN-level tracking as well using CN-level tracking area updates.

Example 56 may include the method of any one of examples 52 to 54 or some other example herein, wherein the access node performs RAN-level tracking using any access by the UE.

Example 57 may include the method of any one of examples 52 to 54 or some other example herein, wherein the CN uses RAN-level tracking area updates to also perform CN-level tracking.

Example 58 may include the method of example 57 or some other example herein, wherein the RAN notifies the CN of the UE location based on a RAN-level tracking area update.

Example 59 may include the method of any one of examples 52 to 58 or some other example herein, wherein the UE identity is used to identify and associate a CN and RAN level tracking area update, wherein the UE identity is a CN level UE identifier or a RAN level UE identifier.

Example 60 may include the method of example 59 or some other example herein, wherein the UE provides the UE identifier.

Example 61 may include the method of any one of examples 52 to 58 or some other example herein, wherein the UE provides both the NAS level UE identifier and the RAN level UE identifier in a common tracking area update.

Example 62 may include the method of any one of examples 59 to 61 or some other example herein, wherein the UE identifier provided by the UE is a UE resume ID.

Example 63 may include the method of any one of examples 52 to 62 or some other example herein, wherein the AN obtains the UE context from a previous AN storing the UE context during the tracking area update, wherein the UE context and the previous AN are identified using a UE resume UD provided by the UE during the tracking area update.

Example 64 may include the method of any one of examples 52 to 63 or some other example herein, wherein the CN provides a CN-level identifier to the RAN for the RAN to associate the UE with two tracking areas.

Example 65 may include the method of any one of examples 52 to 64 or some other example herein, wherein the CN provides to the RAN a list of tracking areas that the CN uses to track the UE.

Example 66 may include the method of example 65 or some other example herein, wherein the RAN node uses a tracking area list provided by the CN to determine a paging area to locate the UE.

Example 67 may include the method of any one of examples 52 to 66 or some other example herein, wherein the CN and the RAN are LTE or 5G networks.

Example 68 may include an apparatus comprising means for performing one or more elements of a method described in or relating to any one of examples 35 to 67 or some other example herein, or any other method or process described herein.

Example 69 may include one or more non-transitory computer-readable media comprising instructions, which, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of any one of examples 35 to 67 or the methods described in or related to some other example herein or any other method or process described herein.

Example 70 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of any one of examples 35 to 67 or a method described in or relating to some other example herein or any other method or process described herein.

Example 71 may include any one of examples 35 to 67 or some other example herein, or a method, technique, or process described in or relating to a portion or component thereof.

Example 72 may include an apparatus comprising: one or more processors; and one or more computer-readable media comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the methods, techniques, or processes described in or relating to any one of examples 35-67 or some other example herein, or portion thereof.

The description herein of illustrated embodiments, including what is described in the abstract, is not intended to be exhaustive or to limit the disclosure to the precise forms disclosed. Although specific embodiments of, and examples for, the disclosure are described herein for illustrative purposes, various alternative or equivalent embodiments or implementations calculated to achieve the same purposes may be made in accordance with the above detailed description without departing from the scope of the disclosure, as will be recognized by those skilled in the relevant art.

Claims (18)

1. A user equipment, UE, having circuitry to:

receiving configuration information from a core network, CN, the configuration information comprising a CN level tracking area list, the CN level tracking area list comprising one or more tracking differentiation identifiers;

identifying a CN level identifier for use in CN level tracking area, TA, operations;

receiving configuration information from a radio access network, RAN, the configuration information comprising a RAN-level tracking area list, the RAN-level tracking area list comprising one or more tracking area identifiers;

identifying a RAN-level identifier for use in RAN-level tracking area, TA, operation;

receiving broadcast system information including a tracking area identifier; and

based on a determination that the tracking area identifier is not in the RAN-level tracking area list and that the tracking area identifier is in the CN-level tracking area list, sending a RAN-level ID to allow the RAN to perform a RAN-level TA update without sending a tracking area update TAU to the CN.

2. The UE of claim 1, wherein the circuitry is further to:

sending a tracking area update TAU to allow a core network to perform a CN level TA update based on a determination that the tracking area identifier is not in the CN level tracking area list.

3. The UE of claim 2, wherein the TAU includes the CN level identifier.

4. The UE of claim 1, wherein the CN-level identifier is a system architecture evolution temporary mobile subscriber identity, S-TMSI.

5. The UE of claim 1, wherein the RAN-level identifier is a resume identifier or a system architecture evolution temporary mobile subscriber identity, S-TMSI, provided to the UE when the UE is suspended.

6. The UE of claim 1, wherein the CN-level tracking area list has a one-to-one correspondence with the RAN-level tracking area list.

7. AN access node, AN, having circuitry to:

receiving an uplink message from a user equipment, UE, the uplink message including a radio access network, RAN, level identifier, the RAN level identifier to perform RAN level and CN level tracking, the uplink message being different from a tracking area update, TAU;

determining, based on an uplink message, that the UE is located in a RAN-level paging area;

receiving downlink data directed to the UE; and

ceasing to page the UE in one or more cells of the RAN-level paging area.

8. The AN of claim 7, wherein the circuitry further performs:

broadcasting system information including a tracking area identifier; and

receiving the uplink message from the UE based on the tracking area identifier.

9. The AN of claim 7, wherein the circuitry is further to:

transmitting a request to acquire a context of the UE from another AN previously associated with the UE, wherein the request includes the RAN-level identifier.

10. The AN of any of claims 7-9, wherein the circuitry is further to:

receiving a CN level tracking area list from a mobility management entity; and

determining a cell of the RAN-level paging area based on the tracking area list.

11. The AN of any of claims 7-9, wherein the circuitry is further to:

determining a cell that transmits the uplink message from the UE;

paging the UE in the cell; and

paging the UE in one or more other cells of the RAN-level paging area if the UE does not respond to the paging in the cell.

12. One or more computer-readable media having instructions that, when executed, cause a user equipment, UE, to:

receiving configuration information from a core network, CN, the configuration information comprising a CN level tracking area list, the CN level tracking area list comprising one or more tracking differentiation identifiers;

identifying CN level identifiers for use in CN level Tracking Area (TA) operations

Receiving configuration information from a radio access network, RAN, the configuration information comprising a RAN-level tracking area list, the RAN-level tracking area list comprising one or more tracking area identifiers;

identifying a RAN-level identifier for use in RAN-level tracking area, TA, operation;

receiving broadcast system information including a tracking area identifier; and

based on a determination that the tracking area identifier is not in the RAN-level tracking area list and that the tracking area identifier is in the CN-level tracking area list, sending a RAN-level ID to allow the RAN to perform a RAN-level TA update without sending a tracking area update TAU to the CN.

13. The one or more computer-readable media of claim 12, wherein the instructions, when executed, further cause the UE to:

sending a tracking area update TAU to allow a core network to perform a CN level TA update based on a determination that the tracking area identifier is not in the CN level tracking area list.

14. The one or more computer-readable media of claim 13, wherein the TAU comprises the CN-level identifier.

15. The one or more computer-readable media of claim 14, wherein the CN-level identifier is a system architecture evolution temporary mobile subscriber identity, S-TMSI.

16. The one or more computer-readable media of claim 12, wherein the RAN-level identifier is a resume identifier or a system architecture evolution temporary mobile subscriber identity, S-TMSI, provided to the UE when the UE is suspended.

17. The one or more computer-readable media of claim 16, wherein the configuration information is first configuration information, and the instructions, when executed, further cause the UE to:

receiving second configuration information from a CN, the second configuration information comprising a CN tracking area list, the CN tracking area list comprising at least one tracking area identifier; and

sending a tracking area update TAU to allow the CN to perform a CN level TA update based on a determination that the tracking area identifier is not in the CN tracking area list.

18. The one or more computer-readable media as recited in claim 17, wherein the CN-level tracking area list has a one-to-one correspondence with the RAN-level tracking area list.

Images