Flexible radio resource control user equipment identifier

Abstract

The present disclosure relates to flexible radio resource control user equipment identifiers. A method performed by a user equipment (UE) includes receiving an assigned radio resource control (RRC) UE identifier (ID) that identifies the UE in a radio access network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value that indicates that a zone ID field is present in the assigned RRC UE ID. The method includes making a determination, based on at least one of a location of the UE, a mobility characteristic, a mobility behavior, or a RRC state, whether to maintain or remove the zone ID field from the RRC UE ID for communications with the RAN. And the method includes constructing a version of the RRC UE ID based on the determination, and communicating with the RAN using the version of the RRC UE ID.

Description

Technical Field

[0001] This disclosure relates generally to telecommunications, and more particularly to the allocation and use of user equipment identifiers for flexible radio resource control in telecommunications systems. Background Technology

[0002] A telecommunications system can be viewed as a facility that enables communication sessions between two or more entities (such as user terminals, base stations, and / or other nodes) by providing carrier waves between the various entities involved in the communication path. A telecommunications system can be provided, for example, by means of a communication network and one or more compatible communication devices. Communication sessions can include, for example, data communications for carrying communications such as voice, video, email, text messages, multimedia, and / or content data. Non-limiting examples of the services provided include two-way or multi-way calling, data communication or multimedia services, and access to data network systems such as the Internet.

[0003] In wireless telecommunications systems, at least a portion of a communication session between at least two entities occurs via a wireless link. Examples of telecommunications systems include Public Land Mobile Networks (PLMNs), satellite-based communication systems, and various wireless local networks, such as Wireless Local Area Networks (WLANs). Some wireless systems can consist of cells and are therefore often referred to as cellular systems.

[0004] Users can access telecommunications systems using appropriate communication equipment or terminals. A user's communication equipment may be referred to as user equipment (UE) or user device. The communication equipment is provided with appropriate signal receiving and transmitting means to enable communication, for example, enabling access to a communication network or direct communication with other users. The communication equipment can access a carrier provided by an entity, such as a base station of a cell in a radio access network (RAN), and transmit and / or receive communication on that carrier.

[0005] Telecommunication systems and associated equipment typically operate according to a given standard or specification that defines what the various entities associated with the communication system are permitted to do and how they should operate. The communication protocols and / or parameters used for the connections between these entities are also typically defined. An example of a telecommunications system is the Universal Mobile Telecommunications System (UMTS). Other examples of telecommunications systems include Long Term Evolution (LTE), LTE Advanced, and so-called 5G or New Radio (NR) networks. NR is being standardized by the 3rd Generation Partnership Project (3GPP).

[0006] In 3GPP, communication between a User Equipment (UE) and the RAN is guided by protocols including Radio Resource Control (RRC). RRC is guided by a state machine that defines certain specific states in which the UE may exist. Different states in the RRC state machine have different amounts of radio resources associated with them, and these radio resources are the resources that the UE can use when it exists in each state. In 5G NR, these RRC states include RRC IDLE, RRC CONNECTED, and RRC INACTIVE. A RAN node or set of RAN nodes can identify a UE using / knowing the RRC UE identifier (ID), but the current structure of the RRC UE ID raises several issues when the same RRC UE ID is used across different RRC states, different RAN nodes, or sets of RAN nodes. Summary of the Invention

[0007] The example implementations of this disclosure relate to telecommunications, and more particularly to the allocation and use of flexible RRC UE IDs in telecommunications systems. According to some example implementations, a UE can be assigned at least one RRC UE ID identifying that UE. The RRC UE ID also includes multiple ID header fields carrying multiple header values ​​indicating the presence of additional ID fields in the RRC UE ID. These additional ID fields may include one or more of an area ID field, a RAN node set ID field, or a RAN node ID field. The RRC UE ID can be constructed or selected at the network (e.g., at the RAN) or by the UE based on one or more factors or conditions, such as the UE's location, mobility characteristics, mobility behavior, and / or RRC status. Therefore, this disclosure includes, but is not limited to, the following example implementations.

[0008] Some example implementations provide an apparatus for implementing a user equipment (UE), the apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute instructions such that the apparatus at least: receives an assigned Radio Resource Control (RRC) UE identifier (ID), the assigned RRC UE ID identifying a UE in a Radio Access Network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value indicating the presence of an area ID field in the assigned RRC UE ID; determines, based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, whether to maintain or remove the area ID field from the RRC UE ID for communication with the RAN; constructs a version of the RRC UE ID based on the determination; and communicates with the RAN using the version of the RRC UE ID.

[0009] Some example implementations provide a method performed by a user equipment (UE), the method comprising: receiving an assigned Radio Resource Control (RRC) UE identifier (ID), the assigned RRC UE ID identifying a UE in a radio access network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value indicating the presence of an area ID field in the assigned RRC UE ID; determining, based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, whether to maintain or remove the area ID field from the RRC UE ID for communication with the RAN; constructing a version of the RRC UE ID based on the determination; and communicating with the RAN using the version of the RRC UE ID.

[0010] Some example implementations provide an apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute instructions to cause the apparatus to at least: determine, based on the determination, at least one of the following regarding a user equipment (UE) in a radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) status; construct, based on the determination, at least one radio resource control (RRC) UE identifier (ID) for the UE, the RRC UE ID identifying the UE and including at least one ID header field carrying at least one header value indicating the presence of an area ID field in the at least one RRC UE ID; and assign the at least one RRC UE ID to the UE for communication with the RAN.

[0011] Some example implementations provide a method comprising: determining at least one of the following regarding a user equipment (UE) in a radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) status; based on the determination, constructing at least one radio resource control (RRC) UE identifier (ID) for the UE, the RRC UE ID identifying the UE and including at least one ID header field carrying at least one header value indicating the presence of an area ID field in the at least one RRC UE ID; and assigning the at least one RRC UE ID to the UE for communication with the RAN.

[0012] Some example implementations provide an apparatus for implementing a user equipment (UE), the apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute instructions such that the apparatus at least: receives an assigned Radio Resource Control (RRC) UE identifier (ID), the assigned RRC UE ID identifying a UE in a Radio Access Network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value indicating the presence of a RAN Node Set ID field in the assigned RRC UE ID; determines, based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, whether to maintain or remove the RAN Node Set ID field from the RRC UE ID for communication with the RAN; constructs a version of the RRC UE ID based on the determination; and communicates with the RAN using the version of the RRC UE ID.

[0013] Some example implementations provide a method performed by a user equipment (UE), the method comprising: receiving an assigned Radio Resource Control (RRC) UE identifier (ID), the assigned RRC UE ID identifying a UE in a radio access network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value indicating the presence of a RAN node set ID field in the assigned RRC UE ID; determining, based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, whether to maintain or remove the RAN node set ID field from the RRC UE ID for communication with the RAN; constructing a version of the RRC UE ID based on the determination; and communicating with the RAN using the version of the RRC UE ID.

[0014] Some example implementations provide an apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute instructions to cause the apparatus to at least: determine, based on at least one of the following regarding a user equipment (UE) in a radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) state; construct, based on the determination, at least one radio resource control (RRC) UE identifier (ID) for the UE, the RRC UE ID identifying the UE and including at least one ID header field carrying at least one header value indicating the presence of a RAN node set ID field in the at least one RRC UE ID; and assign the at least one RRC UE ID to the UE for communication with the RAN.

[0015] Some example implementations provide a method comprising: making a determination of at least one of the following regarding a user equipment (UE) in a radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) status; based on the determination, constructing at least one radio resource control (RRC) UE identifier (ID) for the UE, the RRC UE ID identifying the UE and including at least one ID header field carrying at least one header value indicating the presence of a RAN node set ID field in the at least one RRC UE ID; and assigning the at least one RRC UE ID to the UE for communication with the RAN.

[0016] Some example implementations provide an apparatus for implementing a user equipment (UE), the apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute instructions such that the apparatus at least: receives an assigned Radio Resource Control (RRC) UE identifier (ID), the assigned RRC UE ID identifying a UE in a Radio Access Network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value indicating the presence of a RAN node ID field in the assigned RRC UE ID; determines, based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, whether to maintain or remove the RAN node ID field from the RRC UE ID for communication with the RAN; constructs a version of the RRC UE ID based on the determination; and communicates with the RAN using the version of the RRC UE ID.

[0017] Some example implementations provide a method performed by a user equipment (UE), the method comprising: receiving an assigned Radio Resource Control (RRC) UE identifier (ID), the assigned RRC UE ID identifying a UE in a radio access network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value indicating the presence of a RAN node ID field in the assigned RRC UE ID; determining, based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, whether to maintain or remove the RAN node ID field from the RRC UE ID for communication with the RAN; constructing a version of the RRC UE ID based on the determination; and communicating with the RAN using the version of the RRC UE ID.

[0018] Some example implementations provide an apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute instructions to cause the apparatus to at least: determine, based on the determination, at least one of the following regarding a user equipment (UE) in a radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) state; construct, based on the determination, at least one radio resource control (RRC) UE identifier (ID) for the UE, the RRC UE ID identifying the UE and including at least one ID header field carrying at least one header value indicating the presence of a RAN node ID field in the at least one RRC UE ID; and assign the at least one RRC UE ID to the UE for communication with the RAN.

[0019] Some example implementations provide a method comprising: making a determination of at least one of the following regarding a user equipment (UE) in a radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) status; based on the determination, constructing at least one radio resource control (RRC) UE identifier (ID) for the UE, the RRC UE ID identifying the UE and including at least one ID header field carrying at least one header value indicating the presence of a RAN node ID field in the at least one RRC UE ID; and assigning the at least one RRC UE ID to the UE for communication with the RAN.

[0020] These and other features, aspects, and advantages of this disclosure will become apparent from the following detailed description and the accompanying drawings, which are briefly described below. This disclosure includes any combination of two, three, four, or more features or elements set forth in this disclosure, whether or not such features or elements are explicitly combined in the particular example implementation described herein or otherwise described. This disclosure is intended to be interpreted holistically; therefore, unless the context of this disclosure explicitly specifies otherwise, any separable feature or element in any aspect of this disclosure and any example implementation should be considered composable.

[0021] Therefore, it should be understood that the content of this invention is provided only to summarize some exemplary implementations in order to provide a basic understanding of some aspects of this disclosure. Accordingly, it should be understood that the above exemplary implementations are merely examples and should not be construed as limiting the scope or spirit of this disclosure in any way. Other exemplary implementations, aspects, and advantages will become apparent from the following detailed description taken in conjunction with the accompanying drawings, which illustrate by way of example the principles of some of the described exemplary implementations. Attached Figure Description

[0022] Having provided a general description of an example implementation of this disclosure, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and in which:

[0023] Figure 1 The illustration shows a telecommunications system implemented according to some examples of the present disclosure, which includes one or more public land mobile networks (PLMNs) coupled to one or more external data networks.

[0024] Figure 2 The illustration shows the deployment of a PLMN based on some examples;

[0025] Figure 3 The illustration shows a set of RAN nodes in a de-aggregating radio access network (RAN) architecture, implemented according to some examples;

[0026] Figure 4 The illustration shows a trusted RAN node, implemented according to some examples, in which the UE context for a user equipment (UE) can be identified by a radio resource control (RRC) UE identifier (ID);

[0027] Figure 5A , Figure 5B and Figure 5C The diagram illustrates a signaling diagram of a process involving a flexible RRC UE ID, implemented according to various examples;

[0028] Figure 6 It is a flowchart illustrating the steps in a method executed by the UE, implemented according to various examples;

[0029] Figure 7A , Figure 7B and Figure 7C It is a flowchart illustrating the steps in a method implemented based on various examples;

[0030] Figure 8 It is a flowchart illustrating the steps in a method executed by the UE, implemented according to various examples;

[0031] Figure 9A , Figure 9B and Figure 9C It is a flowchart illustrating the steps in a method implemented based on various examples;

[0032] Figure 10 It is a flowchart illustrating the steps in a method executed by the UE, implemented according to various examples;

[0033] Figure 11A , Figure 11B and Figure 11C It is a flowchart illustrating the steps in a method implemented based on various examples;

[0034] Figure 12 The diagram illustrates a device implemented based on some examples. Detailed Implementation

[0035] Some implementations of this disclosure will be described more fully below with reference to the accompanying drawings, which illustrate, but are not exhaustive, implementations of this disclosure. In fact, various implementations of this disclosure may be embodied in many different forms and should not be construed as limited to the implementations set forth herein; rather, these example implementations are provided to make this disclosure exhaustive and to fully communicate the scope of this disclosure to those skilled in the art. The same reference numerals throughout refer to the same elements.

[0036] Unless otherwise stated or the context clearly indicates, references to first, second, etc., should not be construed as implying a particular order. A feature described as above another feature (unless otherwise stated or the context clearly indicates) may actually be below it, and vice versa; and similarly, a feature described as to the left of another feature may actually be to its right, and vice versa. Furthermore, although this document may reference quantitative measurements, numerical values, geometric relationships, etc., one or more of these (if not all) may be absolute or approximate values ​​to account for possible acceptable deviations, such as those caused by engineering tolerances, etc., unless otherwise stated.

[0037] As used herein, unless otherwise specified or the context explicitly states, "OR" in the operand set is an "inclusive OR," and therefore true if and only if one or more of the operands are true, not an "exclusive OR," which is false if all operands are true. For example, "[A] OR [B]" is true if [A] is true, or if [B] is true, or if both [A] and [B] are true. Furthermore, unless otherwise specified or the context explicitly points to the singular form, the articles "a" and "an" mean "one or more." Additionally, it should be understood that, unless otherwise specified, the terms "data," "content," "digital content," "information," and similar terms are sometimes used interchangeably. The term "network" can refer to a group of interconnected computers, including clients and servers; and within a network, these computers can be interconnected directly or indirectly in various ways, including via one or more switches, routers, gateways, access points, etc.

[0038] This disclosure discusses systems and architectures, and while specific terminology may be used, the concepts are broadly applicable to a wide range of technologies. For example, while this disclosure may refer to 3GPP technologies such as Global System for Mobile Communications (GSM), UMTS, LTE, LTE Advanced, 5G NR, 5G Advanced, and 6G, this disclosure is equally relevant to non-3GPP technologies such as IEEE 802, Bluetooth, and Bluetooth Low Energy. The example implementations of this disclosure described herein also refer to Public Land Mobile Networks (PLMNs) and Mobile Network Operators (MNOs), but the example implementations are similarly applicable to Standalone Non-Public Networks (SNPNs) and the private entities operating these networks. Furthermore, although some examples and figures focus on Radio Access Networks (RANs) and 3GPP access, the example implementations are applicable to any type of network access. This includes not only 5G or 6G 3GPP access, but also non-3GPP access, such as wired access, untrusted non-3GPP access, and trusted non-3GPP access that connects to the 5G or 6G core network using the Radio Access Gateway Function (W-AGF), Non-3GPP Interoperability Function (N3IWF), or Trusted Non-3GPP Gateway Function (TNGF).

[0039] Furthermore, as used in this application, the term "circuit system" may refer to one or more or all of the following: (a) a purely hardware circuit implementation (such as an implementation of an analog and / or digital circuit system alone); (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuitry and software / firmware, and (ii) any portion of (multiple) hardware processors and software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or a server) to perform various functions; or (c) (multiple) hardware circuitry and / or (multiple) processors (such as (multiple) microprocessors or portions thereof) that require software (e.g., firmware) for operation, but which may not be present when not required for operation.

[0040] The above definition of "circuit system" applies to all uses of the term in this application, including all uses in any claim. As another example, as used herein, the term "circuit system" also covers only hardware circuitry or a processor (or processors) or a portion thereof, and its accompanying software and / or firmware implementation. For example, and where applicable to specific claim elements, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0041] Figure 1 The illustration depicts a telecommunications system 100 implemented according to various examples of this disclosure. This telecommunications system typically includes one or more telecommunications networks. As shown, for example, the system includes one or more PLMNs 102 coupled to one or more other external data networks 104—particularly including wide area networks (WANs), such as the Internet. It should be understood that PLMNs can be deployed in a variety of different ways. In particular, some deployments of 4G LTE and 5G NR are considered standalone (SA) deployments. Other deployments combine 4G LTE and 5G technologies and are referred to as non-standalone (NSA) deployments.

[0042] Each PLMN 102 comprises a core network (CN) 106 backbone, such as the Evolved Packet Core (EPC) for 4G LTE, the 5G Core (5GC) (sometimes also called NGC) for 5G NR, and the 6G Core Network (6GC) for 6G; and each core network in this core network, as well as the Internet, is coupled to one or more RAN 108, air interfaces, etc., which implement one or more Radio Access Technologies (RATs). Examples of these RANs include the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) for 4G LTE, the Next Generation (NG) Radio Access Network (NG-RAN) for 5G NR, and the 6G RAN. As used herein, “network equipment” refers to any applicable equipment on the network side of a telecommunications network. Examples of applicable network equipment will be described in more detail below.

[0043] Examples of RATs include 3GPP radio access technologies such as GSM, CDMA2000 1xEV-DO (HRPD), CDMA2000 1x (1xRTT), UTRA, E-UTRA, 5G NR, Advanced 5G, and 6G. Other examples of RATs include IEEE 802 technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.15 (including 802.15.1 (WPAN / Bluetooth), 802.15.4 (Zigbee), and 802.15.6 (WBAN)), Bluetooth, Bluetooth Low Energy (BLE), Ultra Wideband (UWB), and so on. In general, RAT can refer to any 2G, 3G, 4G, 5G, 6G, or higher generation RAT and its different versions, as well as any other RAT that can be configured to interoperate with such mobile communication technologies to provide access to CN 106 of the MNO.

[0044] Telecommunication system 100 also includes one or more radio units, which may be referred to differently as: User Equipment (UE) 110, terminal device, mobile station, etc. A UE is generally a device configured to communicate with network equipment in a telecommunications network or with another UE. A UE can be a portable computer (e.g., laptop, notebook, tablet), a mobile phone (e.g., cell phone, smartphone), a wearable computer (e.g., smartwatch), etc. In other examples, a UE can be an Internet of Things (IoT) device, an Industrial IoT (IIoT) device, a vehicle equipped with Vehicle-to-Everything (V2X) communication technology, etc. As cited by 3GPP, in some examples, a UE can be a Narrowband IoT (NB-IoT) device, an enhanced machine-type communication (eMTC) device, a RedCap device, an environmental IoT device, etc.

[0045] In operation, UE 110 can connect to one or more of RAN 108 based on its specific RAT, thereby accessing a specific CN 106 of PLMN 102, or accessing one or more of external data networks 104 (e.g., the Internet). External data networks can provide Internet access, operator services, third-party services, etc. For example, the International Telecommunication Union (ITU) classifies 5G mobile network services into three categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC) or massive Internet of Things (MIoT).

[0046] In various examples, RAN 108 can be configured as one or more macro cells, micro cells, pico cells, femto cells, etc. RAN generally includes one or more RAN nodes that interact with UE 110. In various examples, RAN nodes can be referred to as base stations (BS), access points (AP), base transceiver stations (BTS), NodeBs (NB), evolved NBs (eNB), macro BS, macro NBs (MNB) or macro eNBs (MeNB), home BS, home NBs (HNB) or home eNBs (HeNB), next-generation NBs (gNB), enhanced gNBs (en-gNB), next-generation eNBs (ng-eNB), 6G NBs (6gNB), etc. The term "gNB" in 5G NR can correspond to eNB in ​​4G LTE. Furthermore, NG-RAN nodes can refer to gNBs or ng-eNBs. Unless otherwise specified, gNBs in 5G NR or 6gNBs in 6G can sometimes be more generally referred to as gNBs or (6)gNBs.

[0047] RAN 108 may include some type of network control / management entity responsible for controlling the RAN nodes. The network control / management entity and the RAN nodes may be separate or integrated into a single device. The network control / management entity may include processing circuitry configured to perform various management functions, etc. The processing circuitry may be associated with memory, computer-readable storage media, or a database for maintaining the information required for management functions.

[0048] Figure 2The diagram illustrates the deployment of PLMN 102, such as a 5G NR deployment or a 6G deployment. As shown, RAN 108 (e.g., NG-RAN, 6G RAN) includes one or more RAN nodes 202 (e.g., gNB, 6gNB) configured to connect one or more UEs 110 to the RAN, thereby accessing CN 106 (e.g., 5GC, 6GC). In 5G NR, NG-RAN and 5GC are sometimes collectively referred to as the 5G system (5GS). RAN nodes can be deployed in a monolithic RAN architecture or a de-aggregated RAN architecture.

[0049] In a de-aggregated RAN architecture, the operation of RAN node 202 can be distributed or functionally decomposed into components, including one or more Remote Radio Heads (RRHs) or Radio Units (RUs) and Baseband Units (BBUs). In some architectures, the BBU can be split into a Central Unit (CU) (Central Node) 204 and one or more Distributed Units (DUs) (Distributed Nodes) 206. For example, a CU can be a server, host, or node. In some architectures, the CU can also be divided into a Control Plane (CP) portion and one or more User Plane (UP) portions, i.e., CU-CP and (multiple) CU-UP. In some architectures, RRHs / RUs and DUs can be co-located. Node operations can also be distributed across multiple servers, hosts, or nodes.

[0050] It should also be understood that the distribution of work between core network operations and RAN node operations may vary depending on the implementation. 5G network architectures can be based on so-called CU-DU splitting. One gNB-CU (CU 204) can control one or more gNB-DUs (DU206). A gNB-CU can control multiple spatially separated gNB-DUs, which can at least act as transmit / receive (Tx / Rx) nodes. In some example implementations, a gNB-DU may include, for example, radio protocol stack layers such as the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical (PHY) layer, while the gNB-CU may include layers above the RLC layer, such as the Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Internet Protocol (IP) layer. Other functional splitting is also possible. Those skilled in the art are considered familiar with suitable radio protocol stacks and the functionality within each layer of such a radio protocol stack.

[0051] In the radio protocol stack, RRC operation is specifically guided by a state machine, which defines certain specific states that the UE 110 may exist in. Different states in the RRC state machine have different amounts of radio resources associated with them, and these radio resources are the resources that the UE can use when it exists in each state. Because the amount of resources available varies in different states, the quality of service experienced by the user and the UE's power consumption are affected by this state machine. Compared to previous generations, 5G NR adds an RRC INACTIVE state to the RRC IDLE and RRC CONNECTED states. This RRC INACTIVE state provides lightweight connectivity, in which major power-saving methods are integrated into this state.

[0052] In some example implementations, the server or CU 204 can generate a virtual network through which the server communicates with the radio nodes. In general, a virtual network can involve the process of combining hardware and software network resources and network functionality into a single software-based management entity (virtual network). Such a virtual network can provide flexible distribution of operations between the server and the radio heads / nodes. In practice, any digital signal processing task can be performed in the CU or DU206, and the boundaries of responsibility transfer between the CU and DU can be selected depending on the implementation.

[0053] CN 106 may include multiple network functions (NFs) divided between CP and UP. Specifically, CN may include, for example, NF 208 for mobility management (MM) (sometimes referred to as MM NF) and NF 210 for session management (SM) (sometimes referred to as SM NF), as well as user plane function (UPF) 212. MM may be, for example, the Access and Mobility Management Function (AMF) in 5GC, or 6G MM in 6GC. Similarly, SM may be, for example, the Session Management Function (SMF) in 5GC, or 6G SM in 6GC.

[0054] Network resilience can be considered a key differentiator for 6G networks. The concept of RAN node sets can improve network resilience and service continuity for UE 110. This set concept can be applied to both monolithic (i.e., without CU-DU splitting) and de-aggregated RAN architectures. In a monolithic RAN architecture, a RAN node set is a group of RAN node instances, and a RAN node instance is an identifiable instance of RAN node 202. RAN node instances within the same RAN node set can provide the same or different geographical coverage areas, but can have access to the same context data (e.g., UE context).

[0055] Figure 3The diagram illustrates the RAN node set 300 in a clustered RAN architecture. As shown, the RAN node set can correspond to a set of logical entities, such as a CU 204 set or a DU set. In other examples where CUs are separated into CP and UP parts, the RAN node set can correspond to a CU-CP set or a CU-UP set. Figure 3 In this context, the RAN node set includes the CU set 302 of the CU. In the case of CUs or separate CUs, the CU (-CP / UP) set is a group of interchangeable CU (-CP / UP) instances, and a CU (-CP / UP) instance is an identifiable instance of a CU (-CP / UP). CU (-CP / UP) instances within the same CU (-CP / UP) set can be geographically distributed but can have access to the same (CP / UP) context data. Similarly, the DU set is a group of interchangeable DU instances, and a DU instance is an identifiable instance of a DU. DU instances within the same DU set can be geographically distributed but can have access to the same UP context data. Also... Figure 3 As shown, RAN nodes 202 in the set can share a common database or storage 304 to maintain UE context data and process data operations such as storage, updates, and retrieval.

[0056] RAN node 202 in the set can also use / know the same UE identifier (ID) to identify UE 110, and this UE ID can be called the RRC UE ID. The RRC UE ID identifies the UE and includes the RAN node set ID (also simply called the set ID) and the RAN node ID (also simply called the node ID). Figure 4 As shown, the RRC UE ID identifies UE context 402 within and between trusted RAN nodes 404. A single ID structure can be used for any RRC procedure / state as well as for other purposes, such as RAN node maintenance, faulting, and recovery. Although the RRC UE ID can be used to identify UE contexts in many scenarios, several issues arise in some scenarios when the same RRC UE ID is used across RRC states that use a fixed RRC UE ID.

[0057] A unified UE identifier across RRC states might mean a single identifier for UE 110, which may not be suitable for the different location coverage area sizes assigned to UE 110 for different RRC states. Currently in 5G NR, the size of the UE identifier varies for different RRC states; and the size of the UE identifier increases as the coverage area that uniquely identifies the UE increases.

[0058] A fixed-size identifier applicable to all RRC states may increase the ID size for the RRC CONNECTED state, and thus increase the message payload; or, if the ID size remains short, it may cause problems for the RRC INACTIVE state due to truncation. For similar reasons, a fixed-size identifier may also limit the number of UEs that RAN node 202 can support, considering different deployment types (such as distributed deployment, centralized deployment, enterprise deployment, dense urban scenarios, etc., each expected to support a different number of UEs). Furthermore, a fixed-size identifier may not be optimized for all device types, considering devices with different mobility characteristics and / or mobility behaviors (such as non-mobile UEs, low-mobility UEs, high-mobility UEs, etc.). Non-mobile UEs can include stationary UEs that do not move, such as some Internet of Things (IoT) devices. Examples of high-mobility UEs include UEs in cars, airplanes, trains, etc.

[0059] The RRC UE ID size could also be large enough to support any expected number of UEs on RAN node 202. In this case, any air interface signaling would suffer from high throughput that could overload that air interface. In short, having a fixed RRC UE ID size, and a fixed size for each field within the RRC UE ID, is likely problematic and suboptimal.

[0060] In view of the above, the example implementation of this disclosure provides a solution in which the RRC UE ID can have a flexible structure that takes into account factors such as deployment type, location, RRC state, UE mobility characteristics (e.g., mobile, non-mobile), mobility behavior (e.g., RRC-connected mobility), and so on. In some examples, RAN 108 (e.g., RAN node 202) can determine the deployment type, location, mobility characteristics, mobility behavior, and / or RRC state of UE 110 in the RAN, and construct (multiple) RRC UE IDs for the UE based on this determination. The RAN can then assign (multiple) RRC UE IDs to the UE for communication with the RAN. Additionally or alternatively, in some examples, the UE can receive the assigned (multiple) RRC UE IDs from the network (e.g., the RAN) and determine the deployment type, location, mobility characteristics, mobility behavior, and / or RRC state of the UE, and construct a version of the RRC UE ID based on this determination. In these examples, the UE can use this version of the RRC UE ID for communication with the RAN.

[0061] As explained in more detail below, in some examples, the flexible RRC UE ID identifies UE 110 in RAN108 via a UE ID (UID), and the RRC UE ID includes at least one ID header field carrying at least one header indicating whether additional ID fields(s) are present in the RRC UE ID, such as a Region ID (RID) field, a RAN Node Set ID (SID) field, and a RAN Node ID (e.g., 6ID for a 6gNB). The RRC UE ID also includes any one of the RID, SID, or 6ID fields indicated by the header(s) to be present.

[0062] The RID field carries an RID indicating the area of ​​RAN 108; and the SID field carries a SID indicating the set of RAN nodes 202 in the RAN (e.g., CU set 302, trusted RAN node 404). In the context of an area, an area can refer to any of multiple different coverage areas, such as a coverage area covered by one or more tracking coverage areas (TAs) that form the registered coverage area of ​​UE 110. The 6ID field carries a 6ID indicating a RAN node in the RAN, which in some cases can be a RAN node in the set of RAN nodes. As described, the (multiple) ID field can be more simply referred to by the (multiple) IDs carried by that (multiple) ID field. That is, the RID field can be more simply referred to as RID, and similarly, the SID field and the 6ID field can be more simply referred to as SID and 6ID, respectively.

[0063] In some example implementations, the flexible RRC UE ID structure can be as follows: RRC UE ID = [RH, RID, SH, SID, 6H, 6ID, UID], where RH, SH, and 6H are the ID header fields for the RID, SID, and 6ID fields, respectively. Assuming the RRC UE ID is S bits in size, the fields of the RRC UE ID and their corresponding sizes can be defined as follows: RH = Region ID header (1 bit) RID = Region ID (M-1 bits) SH = Set ID header (1 bit) SID = Set ID (N-1 bits) 6H = RAN node (e.g., 6gNB) ID header (1 bit) 6ID = RAN node (e.g., 6gNB) ID (0-1 bits) UID = UEID (≤SMNO bits and ≥S-3 bits)

[0064] In the flexible RRC UE ID structure described above, each header bit can indicate whether its corresponding ID exists in the RRC UE ID. For example, RH = 0 indicates that the RID does not exist in the RRC UE ID, and the next field in the RRC UE ID is the SH field. Conversely, SH = 1 indicates that the SID exists in the RRC UE ID, and the next N-1 bits in the RRC UE ID represent the SID.

[0065] In some examples, the 6gNB or other RAN node 202 can be configured with usable RH, SH, and 6H values ​​based on one or both of (semi-)static or dynamic factors. These factors can include, for example, deployment type, the expected number of supported UEs 110, UE mobility behavior, RRC state, etc. The default configuration may be that the RH, SH, and 6H values ​​are each set to 1, meaning the RAN node can support 2 in any RRC state. S-M-N-O One UE.

[0066] In a more specific example, in the case of a region boundary RAN node, the RAN node can construct the RRC UE ID for both mobile UEs and non-mobile UEs (e.g., IoT devices) as follows: Mobile UE: RRC UE ID = [RH(1), RID, SH(1), SID, 6H(1), 6ID, UID] Non-mobile UE: RRC UE ID=[RH(0), SH(0), 6H(0), UID] In this context, the area boundary RAN node can be, for example, a RAN node in a segment between TAs within the registered coverage area of ​​UE 110.

[0067] In another example, in a non-regional boundary coverage area and a centralized deployment scenario, where a large coverage area is covered by CU 204 (e.g., 6gNB-CU), the RAN node can construct the RRC UE ID for both mobile and non-mobile UEs as follows: Mobile UE: RRC UE ID = [RH(0), SH(1), SID, 6H(1), 6ID, UID] Non-mobile UE: RRC UE ID = [RH(0), SH(0), 6H(0), UID] In another example, in a non-regional boundary coverage area and a centralized deployment scenario, where a large coverage area is covered by the CU, the RAN node can construct the RRC UE ID for both mobile and non-mobile UEs as follows: Mobile UE: RRC UE ID=[RH(0), SH(1), SID, 6H(1), 6ID, UID] Non-mobile UE: RRC UE ID=[RH(0), SH(0), 6H(1), 6ID, UID]

[0068] In some examples, RAN node 202 can be configured to provide UE 110 with multiple RRC UE IDs to optimize RRC signaling, such as based on RRC status and / or coverage areas for UE movement / operation. In some of these examples, the UE may be provided (e.g., by the RAN node) with instructions for the UE to send the correct RRC UE ID version among multiple RRC UE IDs. These instructions can be coverage area-based and may include coverage area information indicating one or more cell IDs, one or more tracking coverage areas (TAs), area IDs, RAN node set IDs, etc. The coverage area information indicating (multiple) cell IDs, (multiple) TAs, area IDs, RAN node set IDs, etc., can be conveyed in various ways, such as through System Information Block (SIB) signaling for each RAN node.

[0069] In a more specific example, the multiple RRC UE IDs provided to UE 110 may include the following RRC UE IDs used outside the defined coverage area: [RH(1), RID, SH(1), SID, 6H(1), 6ID, UID] Multiple RRC UE IDs may also include any of the following RRC UE IDs used within a defined coverage area: [RH(0), SH(0), 6H(1), 6ID, UID] [RH(0), SH(0), 6H(0), UID]

[0070] Given that RAN node 202 can provide UE 110 with multiple RRC UE IDs, there may be situations where the UE is unaware of which ID to use at any given time. This could occur, for example, if the RAN node does not provide a RAN node set ID in its SIB signaling, and / or if the RAN node does not implement set logic. In these cases, in some examples, the UE may report all multiple RRC UE IDs when connected to the RAN node, and the RAN node can decode the RRC UE ID by examining its fields.

[0071] To make the RRC UE ID more flexible, although this comes at the cost of increased size or a reduced number of UEs 110 that RAN node 202 can support, in some examples, one or more of the header fields may include subfields to indicate the presence of their corresponding ID and the size of the field carrying that corresponding ID. In some of these examples, the header fields may include: a first subfield carrying header bits indicating whether their corresponding ID exists in the RRC UE ID; and a second subfield indicating the size of the field carrying that corresponding ID.

[0072] In some examples where the header includes subfields, the header can therefore be constructed as follows: [H_B, H_S], where H_B represents the ID field presence indicator (1 bit), and H_S represents the ID field size indicator (n bits). The number of bits "n" for the ID field size indicator may differ for RH, SH, and / or 6H (e.g., 3 bits for RH, 4 bits for SH, and 4 bits for 6H). Furthermore, in some of these examples, if H_B = 0, then H_S does not exist, and the corresponding ID field does not exist. Alternatively, H_S can be a required field, while H_B is not required.

[0073] Alternatively, the standard could define different variants of the RRC UE ID that can be used. In this regard, the standard could define a fixed subset of the RRC UE ID structure, and a fixed size for each field. This provides flexibility for different deployment types and the expected number of UEs that these different deployment types need to support. In this case, multiple most significant bits (MSB) of the RRC UE ID can provide an ID header field to identify the different variants of the RRC UE ID. In some of these examples, the ID header field can carry a multi-bit value indicating the presence of the RID, SID, and 6ID fields, and can also indicate the size of any of these fields that are indicated to be present.

[0074] In a more specific example, the ID header field can use two MSBs to define three variations of the RRC UE ID. All three variations include each of the RID, SID, and 6ID fields, but indicate different field sizes to support different numbers of UEs. The MSBs for the RRC UE ID can include: 00 (for the default number of supported UEs), 01 (for a smaller number of supported UEs compared to the default), and 10 (for a higher number of supported UEs compared to the default). The value 11 can be reserved. Therefore, the three variations of the RRC UE ID including the ID header field can be as follows: RRC UE ID (default) = Header (00) + RID (M bits) + SID (N bits) + 6ID (0 bits) + UID (P bits) RRC UE ID (small UE ID) = header (01) + RID (M + 3 bits) + SID (N + 3 bits) + 6ID (0 + 6 bits) + UID (P - 12 bits) RRC UE ID (Big UE ID) = Header (10) + RID (M-3 bits) + SID (N-3 bits) + 6ID (O-6 bits) + UID (P+12 bits)

[0075] When the RRC UE ID size is sufficiently large, in some examples, RAN node 202 can construct and assign a single RRC UE ID including all ID header fields, as well as all corresponding ID fields. To enable signaling payload optimization, the RAN node can also provide the UE with instructions on how to construct the correct RRC UE ID version to be sent to the network (e.g., the RAN), such as based on coverage area and / or RRC status. For example, instructions based on field type could include bitmasks, string splitting, etc. In this case, UE 110 could have the functionality to construct an RRC UE ID version based on instructions.

[0076] To further illustrate the various example implementations, Figure 5A , Figure 5B and Figure 5C The diagram 500 illustrates a signaling diagram involving a flexible RRC UE ID, implemented according to various examples. For example... Figure 5AAs shown, at step 0, multiple RAN nodes (including first RAN node 202A, second RAN node 202B, third RAN node 202C, and fourth RAN node 202D) are located in the same region, identified by Region ID (RID) = 1. Fourth RAN node 202D is located at the region boundary. First RAN node 202A and second RAN node 202B are located in the same set identified by RAN node set ID (SID) = 1. Third RAN node 202C is located in another set identified by RAN node set ID = 2, and fourth RAN node 202D is located in yet another set identified by RAN node set ID = 3. All RAN nodes are configured using a flexible RRC UE ID structure for different types of UE 110 and RRC states.

[0077] As shown in step 501, each RAN node 202A-202D provides its RAN node set ID in the System Information Block (SIB) and broadcasts this information to the UE, and the UE 110 reads the SIB including the RAN node set ID to understand which RRC UE ID should be sent to which RAN node where applicable.

[0078] In the case involving non-mobile UE 110 (Case 1), the UE can camp in the cell of the first RAN node 202A at step 502. The first RAN node can be configured with {RH=0, SH=0, 6H=0} values ​​for the non-mobile UE, and thus construct and assign them to the UE: RRC UE ID = [RH(0), SH(0), 6H(0), UID]. At step 503, the UE and the first RAN node can communicate via the access layer (AS) (RRC signaling) using the ID assigned to the UE.

[0079] like Figure 5B As shown, in another scenario (Scenario 2) involving mobile UE 110 and multiple RRC UE IDs, the UE can camp in the cell of the first RAN node 202A at step 504. The RAN node can be configured to provide the mobile UE with multiple RRC UE IDs, where the values ​​{RH=0, SH=1, 6H=1} are used when the UE is in RRC INACTIVE; and the values ​​{RH=0, SH=0, 6H=1} are used when the UE is in RRC CONNECTED state. Therefore, the first RAN node can construct and assign the following first and second RRC UE IDs to the UE, and provide instructions on under what conditions which RRC UE ID is used: First RRC UE ID = [RH(0), SH(1), SID, 6H(1), 6ID, UID] Second RRC UE ID = [RH(0), SH(0), 6H(1), 6ID, UID]

[0080] When UE 110 transitions to the RRC CONNECTED state at step 505 after having transitioned to the RRC INACTIVE state based on an instruction from the last serving RAN node (e.g., RAN node 202A), the UE can use the second RRC UE ID at step 506 when it reconnects to the second RAN node 202B. And when the UE reconnects to the third RAN node 202C, the UE can use the first RRC UE ID at step 507.

[0081] like Figure 5C As shown, the first RAN node 202A (in case 3) can be configured to provide a single RRC UE ID to all UEs 110, and different bitmask instructions are provided to the UEs to cover different UE behaviors, RRC states, etc. At step 508, the mobile UE can camp in the cell of the first RAN node, and the first RAN node can assign the UE RRC UEID = [RH(1), RID, SH(1), SID, 6H(1), 6ID, UID] and bitmask instructions. The first RAN node can also store the RRC UE ID and bitmask instructions in the UE context. The UE can use the bitmask instructions to construct a version of the RRC UE ID.

[0082] The bitmasking instruction may include a first bitmasking instruction within the same set for the RRC CONNECTED state. When applied to the RRC UE ID, this first bitmasking instruction produces a first RRC UE ID version: {RH = 0, SH = 0, 6H = 0}, i.e., RRC UE ID = [RH(0), SH(0), 6H(0), UID]. A second bitmasking instruction within the same set for RRC CONNECTED state mobility, when applied to the RRC UE ID, may produce a second RRC UE ID version: {RH = 0, SH = 0, 6H = 1}, i.e., RRC UE ID = [RH(0), SH(0), 6H(1), 6ID, UID]. Furthermore, for the RRC INACTIVE cross-set third bit mask instruction, when applied to RRC UE ID, a third RRC UE ID version can be generated: {RH = 0, SH = 1, 6H = 1}, that is, RRC UE ID = [RH(0), SH(1), SID, 6H(1), 6ID, UID].

[0083] In one scenario (Scenario 3.1), UE 110 may apply a first bitmask instruction at step 509 and communicate with the first RAN node 202A via AS.

[0084] In another scenario (Scenario 3.2), UE 110 can apply a first bitmask instruction at step 510 and communicate with the first RAN node 202A to send measurements. At step 511, the first RAN node can decide to hand over the UE to the third RAN node 202C, and at step 512, use the RRC UE ID and a second bitmask instruction to communicate with the third RAN node. After the handover confirmation, the third RAN node can provide the UE with a new RRC UE ID and bitmask instruction.

[0085] In another scenario (Scenario 3.3), UE 110 can receive an RRC release message at step 513 and transition to the RRC INACTIVE state. Then, at step 514, the UE can use a second bitmask instruction to restore connectivity in the second RAN node 202B. The second RAN node can read the RRC UE ID, understand that the last serving cell for the UE is in the same set, and extract the UE context from the first RAN node 202A. At step 515, the UE can also restore connectivity in the third RAN node 202C using a third bitmask instruction. The third RAN node can read the RRC UE ID, understand that the last serving cell for the UE is in another set, and extract the UE context from the first RAN node. After the UE context extraction is complete, either the second or third RAN node can provide the UE with a new RRC UE ID and bitmask instruction.

[0086] The flexible RRC UE ID in the example implementation may affect both RAN node 202 and UE 110. The RAN node can construct different types of RRC UE IDs based on configuration and can use all forms when needed. In some examples, the RAN node can also provide the UE with additional instructions regarding when to use which RRC UE ID, etc. The RAN node can store this information in the UE context. In some examples, the UE can receive different types of RRC UE IDs and can understand and use all types. In some examples, the UE can also store and use different RRC UE IDs based on different conditions.

[0087] Figure 6 The diagram illustrates flowcharts of various steps in method 600 performed by a user equipment (UE) according to various examples. The method includes receiving an assigned Radio Resource Control (RRC) UE Identifier (ID) that identifies a UE in a Radio Access Network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value indicating the presence of an area ID field in the assigned RRC UE ID, as shown in box 602. The method includes determining, based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, whether to maintain or remove the area ID field from the RRC UE ID for communication with the RAN, as shown in box 604. The method includes constructing a version of the RRC UE ID based on this determination, as shown in box 606. The method also includes communicating with the RAN using this version of the RRC UE ID, as shown in box 608.

[0088] In some examples, method 600 also includes receiving instructions from the RAN regarding the construction of the version of the RRC UE ID. In some of these examples, the determination is made according to these instructions.

[0089] In some examples, the Region ID field carries the region ID of the RAN region, and this determination is made to remove the Region ID field for communication with the RAN within that region. In some of these examples, the RRC UE ID version is constructed in which at least one header value is changed to indicate that the Region ID field does not exist and that the Region ID field has been removed.

[0090] In some examples, the Region ID field carries the region ID of the RAN region, and this determination is made to maintain the Region ID field for communication with the RAN at the region boundary of that region. In some of these examples, a version of the RRC UEID is constructed in which at least one header value is maintained to indicate the presence of the Region ID field.

[0091] In some examples, the Region ID field carries the region ID of the RAN region, and this determination is made to maintain the Region ID field for communication with the RAN outside the region. In some of these examples, a version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the Region ID field.

[0092] In some examples, at least one ID header field of the assigned RRC UE ID includes a first subfield and a second subfield, the first subfield carrying at least one header value and the second subfield indicating the size of the area ID field present in the assigned RRC UE ID.

[0093] In some examples, at least one header value also indicates the presence of a RAN node set ID field and a RAN node ID field in the assigned RRC UE ID, and the determination is also made on whether to maintain or remove at least one of the RAN node set ID field or the RAN node ID field.

[0094] In some examples, at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field. Each of these fields carries a one-bit value indicating the presence of the corresponding field in the region ID field, RAN node set ID field, and RAN node ID field.

[0095] In some examples, at least one ID header field carries at least one header value that is a multi-bit value indicating the presence of the region ID field, the RAN node set ID field, and the RAN node ID field.

[0096] In some examples, this multi-bit value also indicates the size of the region ID field, RAN node set ID field, and RAN node ID field that are indicated to be present.

[0097] Figures 7A to 7C This is a flowchart illustrating the various steps of method 700 implemented according to various examples. The method includes: determining at least one of the following regarding a user equipment (UE) in a radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) state, such as... Figure 7A As shown in box 702. The method includes: based on the determination, constructing at least one Radio Resource Control (RRC) UE ID for the UE, the RRC UE ID identifying the UE and including at least one ID header field carrying at least one header value indicating whether an area ID field exists in the at least one RRC UE ID, such as... Figure 7A As shown in box 704. The method includes: assigning the at least one RRC UE ID to the UE for communication with the RAN, such as... Figure 7A As shown in box 706.

[0098] In some examples, allocating the at least one RRC UE ID at box 706 includes sending the RRC UE ID to the UE, such as Figure 7B As shown in box 708. In some of these examples, the method also includes sending instructions to the UE to construct a version of the RRC UE ID based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, such as... Figure 7B As shown in box 710.

[0099] In some examples, constructing at least one RRC UE ID at box 704 includes constructing multiple RRC UE IDs, and multiple RRC UE IDs are assigned to the UE, such as... Figure 7C As shown in box 712. In some of these examples, the method also includes sending instructions to the UE to select an RRC UE ID from a plurality of RRC UE IDs based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, as shown in box 714.

[0100] In some examples, the Region ID field carries the region ID of the RAN region, and this determination is made such that, for communication with the RAN within that region, the Region ID field is not included in at least one RRC UE ID. In some of these examples, at least one RRC UE ID is constructed where at least one header value indicates that the Region ID field does not exist.

[0101] In some examples, the Region ID field carries the region ID of the RAN region, and this determination is made to include the Region ID field in at least one RRC UE ID for communication with the RAN at the region boundary of that region. In some of these examples, at least one RRC UE ID is constructed, wherein at least one header value indicates the presence of the Region ID field.

[0102] In some examples, the Region ID field carries the region ID of the RAN region, and this determination is made to include the Region ID field in at least one RRC UE ID for communication with the RAN outside the region. In some of these examples, at least one RRC UE ID is constructed, wherein at least one header value indicates the presence of the Region ID field.

[0103] In some examples, at least one ID header field of at least one RRC UE ID includes a first subfield and a second subfield, the first subfield carrying at least one header value indicating the presence of the area ID field, and the second subfield indicating the size of the area ID field.

[0104] In some examples, at least one header value also indicates whether the assigned RRC UE ID contains a RAN node set ID field and a RAN node ID field.

[0105] In some examples, at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field. Each of these fields carries a one-bit value indicating whether the corresponding field exists.

[0106] In some examples, at least one header value carried by at least one ID header field is a multi-bit value that indicates the presence of any one of the region ID field, RAN node set ID field, or RAN node ID field.

[0107] In some examples, this multi-bit value also indicates the size of any of the fields indicated as present: the Region ID field, the RAN Node Set ID field, and the RAN Node ID field.

[0108] Figure 8 This is a flowchart illustrating the various steps of method 800 performed by a user equipment (UE) according to various examples. The method includes receiving an assigned Radio Resource Control (RRC) UE identifier (ID), the assigned RRC UE ID identifying a UE in a radio access network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value indicating the presence of a RAN node set ID field in the assigned RRC UE ID, such as... Figure 8 As shown in box 802. The method includes determining, based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, whether to maintain or remove the RAN node set ID field from the RRC UE ID for communication with the RAN, such as... Figure 8 As shown in box 804. The method includes, based on this determination, constructing a version of the RRC UE ID, as... Figure 8 As shown in box 806. And the method includes using the version with the RRC UE ID to communicate with the RAN, as... Figure 8 As shown in box 808.

[0109] In some examples, method 800 also includes receiving instructions from the RAN regarding the construction of the version of the RRC UE ID. In some of these examples, the determination is made according to these instructions.

[0110] In some examples, the RAN Node Set ID field carries the RAN Node Set ID of the RAN's RAN node set, and this determination is made to remove the RAN Node Set ID field for communication with RAN nodes in that RAN node set. In some of these examples, the RRC UE ID version is constructed in which at least one header value is changed to indicate that the RAN Node Set ID field does not exist and is removed.

[0111] In some examples, the RAN Node Set ID field carries the RAN Node Set ID of the RAN's RAN node set, and this determination is made to maintain the RAN Node Set ID field for communication with RAN nodes outside the RAN node set. In some of these examples, a version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the RAN Node Set ID field.

[0112] In some examples, the RAN Node Set ID field carries the RAN Node Set ID of the RAN's RAN node set, and this determination is made to remove the RAN Node Set ID field for communication of the UE in RRC connected state. In some of these examples, the version of the RRC UE ID is constructed in which at least one header value is changed to indicate that the RAN Node Set ID field does not exist and that the RAN Node Set ID field has been removed.

[0113] In some examples, the RAN Node Set ID field carries the RAN Node Set ID of the RAN's RAN node set, and this determination is made to maintain the RAN Node Set ID field for communication with a UE in an RRC inactive state. In some of these examples, a version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the RAN Node Set ID field.

[0114] In some examples, at least one ID header field of the assigned RRC UE ID includes a first subfield and a second subfield, the first subfield carrying at least one header value, and the second subfield indicating the size of the RAN node set ID field present in the assigned RRC UE ID.

[0115] In some examples, at least one header value also indicates the presence of an area ID field and a RAN node ID field in the assigned RRC UE ID, and the determination is also made on whether to maintain or remove at least one of the area ID field or the RAN node ID field.

[0116] In some examples, at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field. Each of these fields carries a one-bit value indicating the presence of the corresponding field in the region ID field, RAN node set ID field, and RAN node ID field.

[0117] In some examples, at least one header value carried by at least one ID header field is a multi-bit value that indicates the presence of the region ID field, the RAN node set ID field, and the RAN node ID field.

[0118] In some examples, this multi-bit value also indicates the size of the region ID field, RAN node set ID field, and RAN node ID field that are indicated to be present.

[0119] Figures 9A to 9CThis is a flowchart illustrating the various steps of method 900 implemented according to various examples. The method includes: determining at least one of the following regarding a user equipment (UE) in a radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) state, such as... Figure 9A As shown in box 902. The method includes: based on the determination, constructing at least one Radio Resource Control (RRC) UE ID for the UE, the RRC UE ID identifying the UE and including at least one ID header field carrying at least one header value indicating the presence of a RAN Node Set ID field in the at least one RRC UE ID, as shown in box 904. The method also includes: assigning the at least one RRC UE ID to the UE for communication with the RAN, as shown in box 906.

[0120] In some examples, allocating the at least one RRC UE ID at box 906 includes sending the RRC UE ID to the UE, such as Figure 9B As shown in box 908. In some of these examples, the method also includes sending instructions to the UE to construct a version of the RRC UE ID based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, as shown in box 910.

[0121] In some examples, constructing at least one RRC UE ID at box 904 includes constructing multiple RRC UE IDs, and multiple RRC UE IDs are assigned to the UE, such as... Figure 9C As shown in box 912. In some examples, the method further includes sending instructions to the UE to select an RRC UE ID from a plurality of RRC UE IDs based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, as shown in box 914.

[0122] In some examples, the RAN Node Set ID field carries the RAN Node Set ID of the RAN's RAN node set, and the determination is made such that, for communication with RAN nodes in that RAN node set, the RAN Node Set ID field is not included in at least one RRC UE ID. In some of these examples, at least one RRC UE ID is constructed, wherein at least one header value indicates that the RAN Node Set ID field does not exist.

[0123] In some examples, the RAN Node Set ID field carries the RAN Node Set ID of the RAN's RAN node set, and this determination is made to include the RAN Node Set ID field in at least one RRC UE ID for communication with RAN nodes outside the RAN node set. In some of these examples, at least one RRC UE ID is constructed, wherein at least one header value indicates the presence of the RAN Node Set ID field.

[0124] In some examples, the RAN Node Set ID field carries the RAN Node Set ID of the RAN's RAN node set, and this determination is made so that for communication of a UE in RRC connected state, the RAN Node Set ID field is not included. In some of these examples, at least one RRC UE ID is constructed, wherein at least one header value indicates that the RAN Node Set ID field does not exist.

[0125] In some examples, the RAN Node Set ID field carries the RAN Node Set ID of the RAN's RAN node set, and this determination is made for communication of a UE in an RRC inactive state, including the RAN Node Set ID field. In some of these examples, at least one RRC UE ID is constructed, wherein at least one header value indicates the presence of the RAN Node Set ID field.

[0126] In some examples, at least one ID header field of at least one RRC UE ID includes a first subfield and a second subfield, the first subfield carrying at least one header value indicating the presence of the RAN node set ID field, and the second subfield indicating the size of the RAN node set ID field.

[0127] In some examples, at least one header value also indicates whether the assigned RRC UE ID contains a region ID field and a RAN node ID field.

[0128] In some examples, at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field. Each of these fields carries a one-bit value indicating whether the corresponding field exists.

[0129] In some examples, at least one ID header field carries at least one header value that is a multi-bit value indicating the presence of any one of the region ID field, RAN node set ID field, or RAN node ID field.

[0130] In some examples, this multi-bit value also indicates the size of any of the fields indicated as present: the Region ID field, the RAN Node Set ID field, and the RAN Node ID field.

[0131] Figure 10 This is a flowchart illustrating various steps in method 1000 performed by a user equipment (UE) according to various examples. The method includes receiving an assigned Radio Resource Control (RRC) UE identifier (ID) that identifies a UE in a radio access network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value indicating the presence of a RAN node ID field in the assigned RRC UE ID, as shown in box 1002. The method includes determining, based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, whether to maintain or remove the RAN node ID field from the RRC UE ID for communication with the RAN, as shown in box 1004. The method includes constructing a version of the RRC UE ID based on this determination, as shown in box 1006. The method also includes communicating with the RAN using this version of the RRC UE ID, as shown in box 1008.

[0132] In some examples, method 1000 also includes receiving instructions from the RAN regarding the construction of the version of the RRC UE ID. In some of these examples, the determination is made according to these instructions.

[0133] In some examples, the RAN Node ID field carries the RAN Node ID of the RAN node in the RAN's RAN node set, and this determination is made to remove the RAN Node ID field for communication of a UE in RRC connected state within that RAN node set. In some of these examples, a version of the RRC UE ID is constructed in which at least one header value is changed to indicate that the RAN Node ID field does not exist and is removed.

[0134] In some examples, the RAN Node ID field carries the RAN Node ID of a RAN node in the RAN's RAN node set, and this determination is made to maintain the RAN Node ID field for UE communications within that RAN node set that are for RRC connected-state mobility. In some of these examples, a version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the RAN Node ID field. In some examples, the RAN Node ID field carries the RAN Node ID of a RAN node in the RAN's RAN node set, and this determination is made to maintain the RAN Node ID field for UE communications outside the RAN node set that are in an RRC inactive state. In some of these examples, a version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the RAN Node ID field.

[0135] In some examples, at least one ID header field of the assigned RRC UE ID includes a first subfield and a second subfield, the first subfield carrying at least one header value and the second subfield indicating the size of the RAN node ID field present in the assigned RRC UE ID.

[0136] In some examples, at least one header value also indicates the presence of a region ID field and a RAN node set ID field in the assigned RRC UE ID, and the determination is also made on whether to maintain or remove at least one of the region ID field or the RAN node ID field.

[0137] In some examples, at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field. Each of these fields carries a one-bit value indicating the presence of a corresponding field. In some examples, at least one header value carried by the at least one ID header field is a multi-bit value indicating the presence of the region ID field, the RAN node set ID field, and the RAN node ID field.

[0138] In some examples, this multi-bit value also indicates the size of the region ID field, RAN node set ID field, and RAN node ID field that are indicated to be present.

[0139] Figures 11A to 11CThis is a flowchart illustrating the various steps of method 1100 implemented according to various examples. The method includes: determining at least one of the following regarding a user equipment (UE) in a radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) state, such as... Figure 11A As shown in box 1102. The method includes: based on the determination, constructing at least one Radio Resource Control (RRC) UE ID for the UE, the RRC UE ID identifying the UE and including at least one ID header field carrying at least one header value indicating the presence of a RAN Node ID field in the at least one RRC UE ID, as shown in box 1104. The method also includes: assigning the at least one RRC UE ID to the UE for communication with the RAN, as shown in box 1106.

[0140] In some examples, allocating the at least one RRC UE ID at box 1106 includes sending the RRC UE ID to the UE, such as Figure 11B As shown in box 1108. In some examples, the method also includes sending instructions to the UE to construct a version of the RRC UE ID based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, as shown in box 1110.

[0141] In some examples, constructing at least one RRC UE ID at box 1104 includes constructing multiple RRC UE IDs, and multiple RRC UE IDs are assigned to the UE, such as... Figure 11C As shown in box 1112. In some examples, the method also includes sending an instruction to the UE to select an RRC UE ID from a plurality of RRC UE IDs based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, as shown in box 1114.

[0142] In some examples, the RAN Node ID field carries the RAN Node ID of a RAN node in the RAN's RAN node set, and the determination is made such that, for communication of a UE in an RRC connected state within that RAN node set, the RAN Node ID field is not included in at least one RRC UE ID. In some of these examples, at least one RRC UE ID is constructed, wherein at least one header value indicates that the RAN Node ID field does not exist.

[0143] In some examples, the RAN Node ID field carries the RAN Node ID of a RAN node in the RAN's RAN node set, and this determination is made to include the RAN Node ID field in at least one RRC UE ID for UE communications for RRC connection-state mobility within that RAN node set. In some of these examples, at least one RRC UE ID is constructed, wherein at least one header value indicates the presence of the RAN Node ID field.

[0144] In some examples, the RAN Node ID field carries the RAN Node ID of a RAN node in the RAN's RAN node set, and this determination is made for communication of a UE that is in an RRC inactive state outside the RAN node set, including the RAN Node ID field. In some of these examples, at least one RRC UE ID is constructed, wherein at least one header value indicates the presence of the RAN Node ID field.

[0145] In some examples, at least one ID header field of at least one RRC UE ID includes a first subfield and a second subfield, the first subfield carrying at least one header value indicating the presence of the RAN node ID field, and the second subfield indicating the size of the RAN node ID field.

[0146] In some examples, at least one header value also indicates whether the assigned RRC UE ID contains a region ID field and a RAN node set ID field.

[0147] In some examples, at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field. Each of these fields carries a one-bit value indicating whether the corresponding field exists.

[0148] In some examples, at least one header value carried by at least one ID header field is a multi-bit value that indicates the presence of any one of the region ID field, RAN node set ID field, or RAN node ID field.

[0149] In some examples, this multi-bit value also indicates the size of any of the fields indicated as present: the Region ID field, the RAN Node Set ID field, and the RAN Node ID field.

[0150] According to the example implementations of this disclosure, the telecommunications system 100 or PLMN 102 and its components (such as UE 110, CN 106, RAN 108, RAN node 202, CU 204, and / or DU 206) can be implemented in a variety of ways. Components used to implement the system and its components can include hardware, firmware, software, or a combination thereof. In some examples, one or more devices can be configured to act as or otherwise implement the system and its components shown and described herein. In examples involving more than one device, the respective devices can be interconnected or otherwise communicate with each other in a variety of different ways, such as directly or indirectly via wired or wireless networks.

[0151] Based on some example implementations, regarding Figure 6 and Figures 7A-7C At least some of the described methods 600 and 700 can be performed by corresponding apparatus, which includes components for performing functions corresponding to the steps of the method. Similarly, regarding Figure 8 and Figures 9A-9C At least some of the described methods 700 and 800 can be performed by corresponding apparatus, which includes components for performing functions corresponding to the steps of the method. Furthermore, regarding... Figure 10 and Figures 11A-11C At least some of the described methods 1000 and 1100 can be performed by a suitable device that includes components for performing functions corresponding to the steps of the method. Examples of suitable devices may include user equipment, user terminals, user terminals, etc. Other examples of suitable devices may include RAN nodes (e.g., (6)gNB, (6)gNB-DU, (6)gNB-CU) or any suitable device such as a server, host, or node.

[0152] Figure 12 The illustration shows an apparatus 1200 implemented according to some examples of the present disclosure, wherein components for performing various functions include hardware, which may be standalone or directed by one or more computer programs from a computer-readable storage medium or other memory, such as computer memory. The apparatus may include one or more of each of a plurality of components, such as, for example, a processing circuitry system 1202 connected to a computer-readable storage medium or other memory 1204.

[0153] The processing circuit system 1202 may be comprised of one or more processors individually or in combination with one or more computer-readable storage media. Generally, a processing circuit system is any computer hardware capable of processing information such as, for example, data, computer programs, and / or other suitable electronic information. The processing circuit system comprises a set of electronic circuits, some of which may be packaged as integrated circuits or multiple interconnected integrated circuits (integrated circuits are sometimes more commonly referred to as “chips”). The processing circuit system may be configured to execute computer programs, which may be stored on the processing circuit system or otherwise stored in memory 1204 (of the same or another device).

[0154] Depending on the specific implementation, the processing circuitry system 1202 may be multiple processors, a multi-core processor, or some other type of processor. Furthermore, the processing circuitry system may be implemented using several heterogeneous processor systems, where the main processor and one or more auxiliary processors reside on a single chip. As another illustrative example, the processing circuitry system may be a symmetric multiprocessor system containing multiple processors of the same type. In yet another example, the processing circuitry system may be embodied as or otherwise include one or more ASICs, FPGAs, etc. Therefore, while the processing circuitry system may be able to execute computer programs to perform one or more functions, the various example processing circuitry systems may also be able to perform one or more functions without the assistance of a computer program. In either case, the processing circuitry system can be appropriately programmed to perform functions or operations according to the example implementations of this disclosure.

[0155] Memory 1204 is generally any computer hardware capable of storing information such as, for example, data, computer programs, instructions 1206 (e.g., computer-readable program code), and / or other suitable information, whether on a temporary or permanent basis. Memory may include volatile and / or non-volatile memory and may be fixed or removable. Examples of suitable memory include recording media, random access memory (RAM), read-only memory (ROM), hard disk drives, flash memory, USB flash drives, removable computer floppy disks, optical disks, or combinations thereof.

[0156] Memory 1204 is a non-transitory device capable of storing information. An example of a suitable memory is a computer-readable storage medium, which differs from a computer-readable transport medium capable of carrying information from one location to another. Examples of suitable computer-readable transport media include electronic carrier signals, telecommunication signals, or combinations thereof. As used herein, the term "non-transitory" is a limitation of the medium itself (i.e., tangible, not signaling), not a limitation of the persistence of data storage (e.g., RAM and ROM). The computer-readable medium described herein generally refers to either a computer-readable storage medium or a computer-readable transport medium. A computer-readable medium is any entity or device in which information, such as one or more computer programs or portions thereof, can be stored and carried.

[0157] In addition to memory 1204 (e.g., a computer-readable storage medium), processing circuitry 1202 may also be connected to one or more interfaces for displaying, sending, and / or receiving information. Interfaces may include communication interface 1208 and / or one or more user interfaces. Communication interfaces may be configured to send and / or receive information, such as to and / or from (multiple) other devices, (multiple) networks, etc. Communication interfaces may be configured to send and / or receive information via physical (wired) communication links and / or wireless communication links. Examples of suitable communication interfaces include network interface controllers (NICs), wireless NICs (WNICs), and so on.

[0158] The user interface may include a display 1210 and / or one or more user input interfaces 1212. The display may be configured to present or otherwise display information to a user; suitable examples include liquid crystal displays (LCDs), light-emitting diode (LED) displays, organic LED (OLED) displays, active-matrix OLEDs (AMOLEDs), and the like. The user input interface may be wired or wireless and may be configured to receive information from the user into the device, such as for processing, storage, and / or display. Suitable examples of the user input interface include a microphone, an image or video capture device, a keyboard or keypad, a joystick, a touch-sensitive surface (separate from or integrated into the touchscreen), a biometric sensor, and the like. The user interface may also include one or more interfaces for communicating with peripheral devices such as printers, scanners, and the like.

[0159] The execution of instruction 1206 by processing circuitry system 1202, or the storage of instruction in memory 1204, supports combinations of operations for implementing exemplary implementations of this disclosure. In this way, apparatus 1200 may include at least one processing circuitry system and at least one memory coupled to said at least one processing circuitry system, wherein the at least one processing circuitry system is configured to execute instructions stored in the at least one memory. It should also be understood that one or more functions, and combinations thereof, may be implemented by a dedicated hardware-based computer system and / or processing circuitry system performing a specific function, or by a combination of dedicated hardware and program code instructions.

[0160] Some example implementations of this disclosure can also be executed as a computer process defined by one or more computer programs or portions thereof. Example implementations of this disclosure can be executed by executing at least one portion of a computer program including instructions. The computer program can be in source code form, object code form, or some intermediate form. The computer program can be stored on a computer-readable medium that can be read by a computer, processing circuitry system, or other suitable means. As indicated above, for example, the computer program can be stored in memory, such as a computer-readable storage medium. Additionally or alternatively, for example, the computer program can be stored on a computer-readable transmission medium. The software coding used to perform the example implementations of this disclosure is entirely within the scope of those skilled in the art.

[0161] It should be understood that any suitable instructions can be loaded from memory or a computer-readable medium (e.g., a computer-readable storage medium, a computer-readable transmission medium) into a computer, processing circuitry, or other programmable means to produce a particular machine, thereby making that particular machine a component for implementing the functions specified herein. Instructions can also be stored in a computer-readable medium that can instruct a computer, processing circuitry, or other programmable means to function in a particular manner to produce a particular machine or a particular article of manufacture. In some examples, instructions stored in a computer-readable medium can produce an article of manufacture, wherein the article of manufacture becomes a component for implementing the functions described herein. Instructions can be retrieved from a computer-readable medium and loaded into a computer, processing circuitry, or other programmable means to configure the computer, processing circuitry, or other programmable means to perform operations to be performed on or by that computer, processing circuitry, or other programmable means.

[0162] The retrieval, loading, and execution of instructions, including program code instructions, can be performed sequentially, such that one instruction is retrieved, loaded, and executed at a time. In some example implementations, retrieval, loading, and / or execution can be performed in parallel, such that multiple instructions are retrieved, loaded, and / or executed together. The execution of program code instructions can produce computer-implemented processes that provide operations for implementing the functions described herein, executed by a computer, processing circuitry system, or other programmable device.

[0163] As explained above and stated below, this disclosure includes, but is not limited to, the following example implementations.

[0164] Clause 1. A method performed by a user equipment (UE), the method comprising: receiving an assigned radio resource control (RRC) UE identifier (ID), the assigned RRC UE ID identifying a UE in a radio access network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value indicating the presence of an area ID field in the assigned RRC UE ID; determining, based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, whether to maintain or remove the area ID field from the RRC UE ID for communication with the RAN; constructing a version of the RRC UE ID based on the determination; and communicating with the RAN using the version of the RRC UE ID.

[0165] Clause 2. The method according to Clause 1, wherein the method further includes receiving an instruction from the RAN regarding the construction of the version of the RRC UEID, and wherein the determination is made pursuant to the instruction.

[0166] Clause 3. The method according to Clause 1 or Clause 2, wherein the area ID field carries the area ID of the RAN area, and the determination is made to: remove the area ID field for communication with the RAN within the area, and wherein a version of the RRC UE ID is constructed, wherein at least one header value is changed to indicate that the area ID field does not exist and that the area ID field is removed.

[0167] Clause 4. The method according to any one of Clauses 1 to 3, wherein the area ID field carries the area ID of the RAN's area, and the determination is made to: maintain the area ID field for communication with the RAN at the area boundary of the area, and wherein a version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the area ID field.

[0168] Clause 5. The method according to any one of Clauses 1 to 4, wherein the area ID field carries the area ID of the RAN area, and the determination is made to: maintain the area ID field for communication with the RAN outside the area, and wherein a version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the area ID field.

[0169] Clause 6. The method according to any one of Clauses 1 to 5, wherein at least one ID header field of the assigned RRC UE ID includes a first subfield and a second subfield, the first subfield carrying at least one header value, and the second subfield indicating the size of the area ID field present in the assigned RRC UE ID.

[0170] Clause 7. The method according to any one of Clauses 1 to 6, wherein at least one header value further indicates the presence of a RAN node set ID field and a RAN node ID field in the assigned RRC UE ID, and the determination is also made on whether to maintain or remove at least one of the RAN node set ID field or the RAN node ID field.

[0171] Clause 8. The method according to Clause 7, wherein at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field, each of the region ID header field, the RAN node set ID header field, and the RAN node ID header field carrying a one-bit value indicating the presence of a corresponding one of the region ID field, the RAN node set ID field, and the RAN node ID field.

[0172] Clause 9. The method according to Clause 7 or Clause 8, wherein at least one header value carried by at least one ID header field is a multi-bit value indicating the presence of the region ID field, the RAN node set ID field, and the RAN node ID field.

[0173] Clause 10. The method according to Clause 9, wherein the multi-bit value further indicates the size of the region ID field, the RAN node set ID field, and the RAN node ID field that are indicated to be present.

[0174] Clause 11. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus to perform the method of any one of Clauses 1 to 10.

[0175] Clause 12. An apparatus comprising components for performing the method described in any one of Clauses 1 to 10.

[0176] Clause 13. A computer-readable medium comprising instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 1 to 10.

[0177] Clause 14. A computer-readable storage medium including instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 1 to 10.

[0178] Clause 15. A computer program comprising instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 1 to 10.

[0179] Clause 16. A method comprising: determining, based on the determination, at least one of the following regarding a user equipment (UE) in a radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) status; constructing, based on the determination, at least one radio resource control (RRC) UE identifier (ID) for the UE, the RRC UE ID identifying the UE and including at least one ID header field carrying at least one header value indicating the presence of an area ID field in the at least one RRC UE ID; and assigning the at least one RRC UE ID to the UE for communication with the RAN.

[0180] Clause 17. The method according to Clause 16, wherein allocating the at least one RRC UE ID includes sending the RRC UE ID to the UE, and the method further includes sending instructions to the UE for the UE to construct a version of the RRC UE ID based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state.

[0181] Clause 18. The method according to Clause 16 or Clause 17, wherein constructing at least one RRC UE ID includes constructing a plurality of RRC UE IDs, and the plurality of RRC UE IDs are assigned to the UE, and wherein the method further includes sending an instruction to the UE for the UE to select an RRC UE ID from the plurality of RRC UE IDs based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state.

[0182] Clause 19. The method according to any one of Clauses 16 to 18, wherein the area ID field carries the area ID of the RAN's area, and the determination is made such that: for communication with the RAN within the area, the area ID field is not included in at least one RRC UE ID, and wherein at least one RRC UE ID is constructed, wherein at least one header value indicates that the area ID field does not exist.

[0183] Clause 20. The method according to any one of Clauses 16 to 19, wherein the area ID field carries the area ID of the RAN's area, and the determination is made to: include the area ID field in at least one RRC UE ID for communication with the RAN at the area boundary of the area, and wherein at least one RRC UE ID is constructed, wherein at least one header value indicates the presence of the area ID field.

[0184] Clause 21. The method according to any one of Clauses 16 to 20, wherein the area ID field carries the area ID of the RAN's area, and the determination is made to include the area ID field in at least one RRC UE ID for communication with the RAN outside the area, and wherein at least one RRC UE ID is constructed, wherein at least one header value indicates the presence of the area ID field.

[0185] Clause 22. The method according to any one of Clauses 16 to 21, wherein at least one ID header field of at least one RRC UE ID includes a first subfield and a second subfield, the first subfield carrying at least one header value indicating the presence of an area ID field, and the second subfield indicating the size of the area ID field.

[0186] Clause 23. The method according to any one of Clauses 16 to 22, wherein at least one header value further indicates the presence of a RAN node set ID field and a RAN node ID field in the assigned RRC UE ID.

[0187] Clause 24. The method according to Clause 23, wherein at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field, each of the region ID header field, the RAN node set ID header field, and the RAN node ID header field carrying a one-bit value indicating whether a corresponding item in the region ID field, the RAN node set ID field, and the RAN node ID field exists.

[0188] Clause 25. The method according to Clause 23 or Clause 24, wherein at least one header value carried by at least one ID header field is a multi-bit value indicating the presence of any one of the region ID field, RAN node set ID field, or RAN node ID field.

[0189] Clause 26. The method according to Clause 25, wherein the multi-bit value further indicates the size of any one of the area ID field, RAN node set ID field, and RAN node ID field that is indicated to be present.

[0190] Clause 27. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus to perform any one of Clauses 16 to 26.

[0191] Clause 28. An apparatus comprising components for performing the method described in any one of Clauses 16 to 26.

[0192] Clause 29. A computer-readable medium comprising instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 16 to 26.

[0193] Clause 30. A computer-readable storage medium including instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 16 to 26.

[0194] Clause 31. A computer program comprising instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 16 to 26.

[0195] Clause 32. A method performed by a user equipment (UE), the method comprising: receiving an assigned radio resource control (RRC) UE identifier (ID), the assigned RRC UE ID identifying a UE in a radio access network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value indicating the presence of a RAN node set ID field in the assigned RRC UE ID; determining, based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, whether to maintain or remove the RAN node set ID field from the RRC UE ID for communication with the RAN; constructing a version of the RRC UE ID based on the determination; and communicating with the RAN using the version of the RRC UE ID.

[0196] Clause 33. The method according to Clause 32, wherein the method further includes receiving an instruction from the RAN regarding the construction of a version of the RRC UEID, and wherein the determination is made pursuant to the instruction.

[0197] Clause 34. The method according to Clause 32 or Clause 33, wherein the RAN node set ID field carries the RAN node set ID of the RAN node set, and the determination is made to: remove the RAN node set ID field for communication with RAN nodes in the RAN node set, and wherein a version of the RRC UE ID is constructed, wherein at least one header value is changed to indicate that the RAN node set ID field does not exist and the RAN node set ID field is removed.

[0198] Clause 35. The method according to any one of Clauses 32 to 34, wherein the RAN node set ID field carries the RAN node set ID of the RAN node set, and the determination is made to: maintain the RAN node set ID field for communication with RAN nodes outside the RAN node set, and wherein a version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the RAN node set ID field.

[0199] Clause 36. The method according to any one of Clauses 32 to 35, wherein the RAN node set ID field carries the RAN node set ID of the RAN node set, and the determination is made to: remove the RAN node set ID field for communication of the UE in the RRC connection state, and wherein a version of the RRC UE ID is constructed, wherein at least one header value is changed to indicate that the RAN node set ID field does not exist and the RAN node set ID field is removed.

[0200] Clause 37. The method according to any one of Clauses 32 to 36, wherein the RAN node set ID field carries the RAN node set ID of the RAN node set, and the determination is made to: maintain the RAN node set ID field for communication of a UE in an RRC inactive state, and wherein a version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the RAN node set ID field.

[0201] Clause 38. The method according to any one of Clauses 32 to 37, wherein at least one ID header field of the assigned RRC UE ID includes a first subfield and a second subfield, the first subfield carrying at least one header value, and the second subfield indicating the size of the RAN node set ID field present in the assigned RRC UE ID.

[0202] Clause 39. The method according to any one of Clauses 32 to 38, wherein at least one header value further indicates the presence of an area ID field and a RAN node ID field in the assigned RRC UE ID, and the determination is also made on whether to maintain or remove at least one of the area ID field or the RAN node ID field.

[0203] Clause 40. The method according to Clause 39, wherein at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field, each of the region ID header field, the RAN node set ID header field, and the RAN node ID header field carrying a one-bit value indicating the presence of a corresponding one of the region ID field, the RAN node set ID field, and the RAN node ID field.

[0204] Clause 41. The method according to Clause 39 or Clause 40, wherein at least one header value carried by at least one ID header field is a multi-bit value indicating the presence of the region ID field, the RAN node set ID field, and the RAN node ID field.

[0205] Clause 42. The method according to Clause 41, wherein the multi-bit value further indicates the size of the region ID field, the RAN node set ID field, and the RAN node ID field that are indicated to be present.

[0206] Clause 43. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus to perform any one of Clauses 32 to 42.

[0207] Clause 44. An apparatus comprising components for performing the method of any one of Clauses 32 to 42.

[0208] Clause 45. A computer-readable medium comprising instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 32 to 42.

[0209] Clause 46. A computer-readable storage medium including instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 32 to 42.

[0210] Clause 47. A computer program comprising instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 32 to 42.

[0211] Clause 48. A method comprising: determining, based on the determination, at least one of the following regarding a user equipment (UE) in a radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) status; constructing, based on the determination, at least one radio resource control (RRC) UE identifier (ID) for the UE, the RRC UE ID identifying the UE and including at least one ID header field carrying at least one header value indicating the presence of a RAN node set ID field in the at least one RRC UE ID; and assigning the at least one RRC UE ID to the UE for communication with the RAN.

[0212] Clause 49. The method according to Clause 48, wherein allocating the at least one RRC UE ID includes sending the RRC UE ID to the UE, and the method further includes sending instructions to the UE for the UE to construct a version of the RRC UE ID based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state.

[0213] Clause 50. The method according to Clause 48 or Clause 49, wherein constructing at least one RRC UE ID includes constructing a plurality of RRC UE IDs, and the plurality of RRC UE IDs are assigned to the UE, and wherein the method further includes sending an instruction to the UE for the UE to select an RRC UE ID from the plurality of RRC UE IDs based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state.

[0214] Clause 51. The method according to any one of Clauses 48 to 50, wherein the RAN node set ID field carries the RAN node set ID of the RAN node set, and the determination is made such that: for communication with RAN nodes in the RAN node set, the RAN node set ID field is not included in at least one RRC UE ID, and wherein at least one RRC UE ID is constructed, wherein at least one header value indicates that the RAN node set ID field does not exist.

[0215] Clause 52. The method according to any one of Clauses 48 to 51, wherein the RAN node set ID field carries the RAN node set ID of the RAN node set, and the determination is made to include the RAN node set ID field in at least one RRC UE ID for communication with RAN nodes outside the RAN node set, and wherein at least one RRC UE ID is constructed, wherein at least one header value indicates the presence of the RAN node set ID field.

[0216] Clause 53. The method according to any one of Clauses 48 to 52, wherein the RAN node set ID field carries the RAN node set ID of the RAN node set, and the determination is made such that: for communication of a UE in an RRC connection state, the RAN node set ID field is not included, and wherein at least one RRC UE ID is constructed, wherein at least one header value indicates that the RAN node set ID field does not exist.

[0217] Clause 54. The method according to any one of Clauses 48 to 53, wherein the RAN node set ID field carries the RAN node set ID of the RAN node set, and the determination is made to: include the RAN node set ID field in communications for a UE in an RRC inactive state, and wherein at least one RRC UE ID is constructed, and wherein at least one header value indicates that the RAN node set ID field is present.

[0218] Clause 55. The method according to any one of Clauses 48 to 54, wherein at least one ID header field of at least one RRC UE ID includes a first subfield and a second subfield, the first subfield carrying at least one header value indicating the presence of the RAN node set ID field; the second subfield indicating the size of the RAN node set ID field.

[0219] Clause 56. The method according to any one of Clauses 48 to 55, wherein at least one header value further indicates whether an area ID field and a RAN node ID field are present in the assigned RRC UE ID.

[0220] Clause 57. The method according to Clause 56, wherein at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field, each of the region ID header field, the RAN node set ID header field, and the RAN node ID header field carrying a one-bit value indicating whether a corresponding item in the region ID field, the RAN node set ID field, and the RAN node ID field exists.

[0221] Clause 58. The method according to Clause 56 or Clause 57, wherein at least one header value carried by at least one ID header field is a multi-bit value indicating the presence of any one of the region ID field, the RAN node set ID field, or the RAN node ID field.

[0222] Clause 59. The method according to Clause 58, wherein the multi-bit value further indicates the size of any one of the region ID field, RAN node set ID field, and RAN node ID field that is indicated to be present.

[0223] Clause 60. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus to perform the method of any one of Clauses 48 to 59.

[0224] Clause 61. An apparatus comprising components for performing the method described in any one of Clauses 48 to 59.

[0225] Clause 62. A computer-readable medium comprising instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 48 to 59.

[0226] Clause 63. A computer-readable storage medium including instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 48 to 59.

[0227] Clause 64. A computer program comprising instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 48 to 59.

[0228] Clause 65. A method performed by a user equipment (UE), the method comprising: receiving an assigned radio resource control (RRC) UE identifier (ID), the assigned RRC UE ID identifying a UE in a radio access network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value indicating the presence of a RAN node ID field in the assigned RRC UE ID; determining, based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state, whether to maintain or remove the RAN node ID field from the RRC UE ID for communication with the RAN; constructing a version of the RRC UE ID based on the determination; and communicating with the RAN using the version of the RRC UE ID.

[0229] Clause 66. The method according to Clause 65, wherein the method further comprises receiving an instruction from the RAN regarding the construction of a version of the RRC UEID, and wherein the determination is made pursuant to the instruction.

[0230] Clause 67. The method according to Clause 65 or Clause 66, wherein the RAN Node ID field carries the RAN Node ID of a RAN node in the RAN Node set, and the determination is made to: remove the RAN Node ID field for communication of a UE in an RRC connected state in the RAN Node set, and wherein a version of the RRC UE ID is constructed, wherein at least one header value is changed to indicate that the RAN Node ID field does not exist and that the RAN Node ID field is removed.

[0231] Clause 68. The method according to any one of Clauses 65 to 67, wherein the RAN Node ID field carries the RAN Node ID of a RAN node in the RAN Node set, and the determination is made to maintain the RAN Node ID field for UE communications for RRC connection-state mobility in the RAN Node set, and wherein a version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the RAN Node ID field.

[0232] Clause 69. The method according to any one of Clauses 65 to 68, wherein the RAN Node ID field carries the RAN Node ID of a RAN node in the RAN Node set, and the determination is made to maintain the RAN Node ID field for communication with a UE outside the RAN Node set that is in an RRC inactive state, and wherein a version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the RAN Node ID field.

[0233] Clause 70. The method according to any one of Clauses 65 to 69, wherein at least one ID header field of the assigned RRC UE ID includes a first subfield and a second subfield, the first subfield carrying at least one header value, and the second subfield indicating the size of the RAN node ID field present in the assigned RRC UE ID.

[0234] Clause 71. The method according to any one of Clauses 65 to 70, wherein at least one header value further indicates the presence of an area ID field and a RAN node set ID field in the assigned RRC UE ID, and the determination is also made on whether to maintain or remove at least one of the area ID field or the RAN node ID field.

[0235] Clause 72. The method according to Clause 71, wherein at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field, each of the region ID header field, the RAN node set ID header field, and the RAN node ID header field carrying a one-bit value indicating the presence of a corresponding one of the region ID field, the RAN node set ID field, and the RAN node ID field.

[0236] Clause 73. The method according to Clause 71 or Clause 72, wherein at least one header value carried by at least one ID header field is a multi-bit value indicating the presence of the region ID field, the RAN node set ID field, and the RAN node ID field.

[0237] Clause 74. The method according to Clause 73, wherein the multi-bit value further indicates the size of the region ID field, the RAN node set ID field, and the RAN node ID field that are indicated to be present.

[0238] Clause 75. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus to perform the method of any one of Clauses 65 to 74.

[0239] Clause 76. An apparatus comprising components for performing the method described in any one of Clauses 65 to 74.

[0240] Clause 77. A computer-readable medium including instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 65 to 74.

[0241] Clause 78. A computer-readable storage medium including instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 65 to 74.

[0242] Clause 79. A computer program comprising instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 65 to 74.

[0243] Clause 80. A method comprising: making a determination regarding at least one of the following regarding a user equipment (UE) in a radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) status; based on the determination, constructing at least one radio resource control (RRC) UE identifier (ID) for the UE, the RRC UE ID identifying the UE and including at least one ID header field carrying at least one header value indicating the presence of a RAN node ID field in the at least one RRC UE ID; and assigning the at least one RRC UE ID to the UE for communication with the RAN.

[0244] Clause 81. The method according to Clause 80, wherein allocating the at least one RRC UE ID includes sending the RRC UE ID to the UE, and the method further includes sending instructions to the UE for the UE to construct a version of the RRC UE ID based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC state.

[0245] Clause 82. The method according to Clause 80 or Clause 81, wherein constructing at least one RRC UE ID includes constructing a plurality of RRC UE IDs and the plurality of RRC UE IDs are assigned to the UE, and wherein the method further includes sending an instruction to the UE for the UE to select an RRC UE ID from the plurality of RRC UE IDs based on at least one of the UE's location, mobility characteristics, mobility behavior or RRC state.

[0246] Clause 83. The method according to any one of Clauses 80 to 82, wherein the RAN Node ID field carries the RAN Node ID of a RAN node in the RAN Node set, and the determination is made such that: for communication of a UE in an RRC connection state in the RAN Node set, the RAN Node ID field is not included in at least one RRC UE ID, and wherein at least one RRC UE ID is constructed, wherein at least one header value indicates that the RAN Node ID field does not exist.

[0247] Clause 84. The method according to any one of Clauses 80 to 83, wherein the RAN Node ID field carries the RAN Node ID of a RAN node in the RAN Node set, and the determination is made to include the RAN Node ID field in at least one RRC UE ID for communication of a UE for RRC connection-state mobility in the RAN Node set, and wherein at least one RRC UE ID is constructed, wherein at least one header value indicates the presence of the RAN Node ID field.

[0248] Clause 85. The method according to any one of Clauses 80 to 84, wherein the RAN Node ID field carries the RAN Node ID of a RAN node in the RAN Node set, and the determination is made to: include the RAN Node ID field in communications for a UE outside the RAN Node set that is in an RRC inactive state, and wherein at least one RRC UE ID is constructed, and wherein at least one header value indicates that the RAN Node ID field is present.

[0249] Clause 86. The method according to any one of Clauses 80 to 85, wherein at least one ID header field of at least one RRC UE ID includes a first subfield and a second subfield, the first subfield carrying at least one header value indicating the presence of the RAN node ID field, and the second subfield indicating the size of the RAN node ID field.

[0250] Clause 87. The method according to any one of Clauses 80 to 86, wherein at least one header value further indicates the presence of an area ID field and a RAN node set ID field in the assigned RRC UE ID.

[0251] Clause 88. The method according to Clause 87, wherein at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field, each of the region ID header field, the RAN node set ID header field, and the RAN node ID header field carrying a one-bit value indicating whether a corresponding item in the region ID field, the RAN node set ID field, and the RAN node ID field exists.

[0252] Clause 89. The method according to Clause 87 or Clause 88, wherein at least one header value carried by at least one ID header field is a multi-bit value indicating the presence of any one of the region ID field, the RAN node set ID field, or the RAN node ID field.

[0253] Clause 90. The method according to Clause 89, wherein the multi-bit value further indicates the size of any one of the region ID field, RAN node set ID field, and RAN node ID field that is indicated to be present.

[0254] Clause 91. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus to perform the method of any one of Clauses 80 to 90.

[0255] Clause 92. An apparatus comprising components for performing the method described in any one of Clauses 80 to 90.

[0256] Clause 93. A computer-readable medium comprising instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 80 to 90.

[0257] Clause 94. A computer-readable storage medium including instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 80 to 90.

[0258] Clause 95. A computer program comprising instructions that, in response to execution of at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 80 to 90.

[0259] Benefiting from the teachings presented in the foregoing description and associated drawings, those skilled in the art to which this disclosure pertains will conceive of numerous modifications and other implementations of this disclosure set forth herein. Therefore, it should be understood that this disclosure is not limited to the specific implementations disclosed, and that modifications and other implementations are intended to be included within the scope of the appended claims. Furthermore, although the foregoing description and associated drawings describe exemplary implementations in the context of certain exemplary combinations of elements and / or functions, it should be understood that different combinations of elements and / or functions can be provided by alternative implementations without departing from the scope of the appended claims. In this regard, for example, combinations of elements and functions different from those explicitly described above, as set forth in some of the appended claims, may also be considered. Although specific terminology is used herein, it is used only in a general and descriptive sense and not for limiting purposes.

Claims

1. An apparatus for implementing a user equipment (UE), the apparatus comprising: At least one memory, the at least one memory being configured to store instructions; as well as At least one processing circuitry system is configured to access the at least one memory and execute the instructions to cause the device to at least: Receive an assigned Radio Resource Control (RRC) UE Identifier (ID), the assigned RRC UE ID identifying a UE in a Radio Access Network (RAN), the RRC UE ID including at least one ID header field carrying at least one header value, the at least one header value indicating the presence of an area ID field in the assigned RRC UE ID; Based on at least one of the UE's location, mobility characteristics, mobility behavior, or RRC status, determine whether to maintain or remove the area ID field from the RRC UE ID for communication with the RAN. Based on the determination, construct the version of the RRC UE ID; as well as Use the version of the RRC UE ID to communicate with the RAN.

2. The apparatus of claim 1, wherein the at least one processing circuitry is configured to execute the instructions to cause the apparatus to also receive instructions from the RAN regarding the construction of the version of the RRC UE ID, and The determination mentioned therein is made in accordance with the instructions.

3. The apparatus of claim 1, wherein the region ID field carries the region ID of the region of the RAN, and the determination is made as follows: The region ID field is removed for communication with the RAN within the region, and the version of the RRC UEID is constructed, wherein at least one header value is changed to indicate that the region ID field does not exist and the region ID field is removed; or For communication with the RAN at the area boundary of the area, the area ID field is maintained, and the version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the area ID field.

4. The apparatus of claim 1, wherein the region ID field carries a region ID of the RAN region, and the determination is made to maintain the region ID field for communication with the RAN outside the region, and The version of the RRC UE ID is constructed, wherein at least one header value is maintained to indicate the presence of the area ID field.

5. The apparatus of claim 1, wherein the at least one ID header field of the assigned RRC UE ID includes a first subfield and a second subfield, the first subfield carrying the at least one header value, and the second subfield indicating the size of the area ID field present in the assigned RRC UE ID.

6. The apparatus of claim 1, wherein the at least one header value further indicates the presence of a RAN node set ID field and a RAN node ID field in the assigned RRC UEID, and the determination is further made on whether to maintain or remove at least one of the RAN node set ID field or the RAN node ID field.

7. The apparatus of claim 6, wherein the at least one ID header field of the assigned RRC UE ID includes a region ID header field, a RAN node set ID header field, and a RAN node ID header field, each of the region ID header field, the RAN node set ID header field, and the RAN node ID header field carrying a one-bit value indicating the presence of a corresponding one of the region ID field, the RAN node set ID field, and the RAN node ID field.

8. The apparatus of claim 6, wherein the at least one header value carried by the at least one ID header field is a multi-bit value, the multi-bit value indicating the presence of the region ID field, the RAN node set ID field, and the RAN node ID field.

9. The apparatus of claim 8, wherein the multi-bit value further indicates the size of the region ID field, the RAN node set ID field, and the RAN node ID field that are indicated to be present.

10. A device for communication, comprising: At least one memory, the at least one memory being configured to store instructions; as well as At least one processing circuitry system is configured to access the at least one memory and execute the instructions to cause the device to at least: Make a determination of at least one of the following regarding a user equipment (UE) in the radio access network (RAN): location, mobility characteristics, mobility behavior, or radio resource control (RRC) status; Based on the determination, at least one Radio Resource Control (RRC) UE Identifier (ID) is constructed for the UE. The RRC UE ID identifies the UE and includes at least one ID header field carrying at least one header value, the at least one header value indicating whether an area ID field exists in the at least one RRC UE ID. as well as The at least one RRC UE ID is assigned to the UE for communication with the RAN.

Images