WO2020080307A1

WO2020080307A1 - Radio access network and methods for expedited network access

Info

Publication number: WO2020080307A1
Application number: PCT/JP2019/040285
Authority: WO
Inventors: Kamel M. Shaheen
Original assignee: Sharp Kabushiki Kaisha
Priority date: 2018-10-19
Filing date: 2019-10-11
Publication date: 2020-04-23

Abstract

In a radio access network (24) wherein a protocol stack is split between anchor processor circuitry (40) and distributed processor circuitry (42). The anchor processor circuitry (40) is configured to perform high layer radio access network node operations (50) and the distributed processor circuitry (42) is configured to perform low layer radio access network node operations (52), including a medium access control (MAC) operation for a wireless terminal served by the radio access network wherein the distributed processor circuitry handles data radio bearers and signaling radio bearers for the wireless terminal.

Description

RADIO ACCESS NETWORK AND METHODS FOR EXPEDITED NETWORK ACCESS

The technology relates to wireless communications, and particularly to radio access network architecture and operation.

A radio access network typically resides between wireless devices, such as user equipments (UEs), mobile phones, mobile stations, or any other device having wireless termination, and a core network. Example of radio access network types includes the GRAN, GSM radio access network; the GERAN, which includes EDGE packet radio services; UTRAN, the UMTS radio access network; E-UTRAN, which includes Long-Term Evolution; and g-UTRAN, the New Radio (NR) .

A radio access network may comprise one or more access nodes, such as base station nodes, which facilitate wireless communication or otherwise provides an interface between a wireless terminal and a telecommunications system. A non-limiting example of a base station can include, depending on radio access technology type, a Node B (“NB”), an enhanced Node B (“eNB”), a home eNB (“HeNB”), a gNB (for a New Radio [“NR”] technology system), or some other similar terminology.

The 3rd Generation Partnership Project (“3GPP”) is a group that, e.g., develops collaboration agreements such as 3GPP standards that aim to define globally applicable technical specifications and technical reports for wireless communication systems. Various 3GPP documents may describe certain aspects of radio access networks. Overall architecture for a fifth generation system, e.g., the 5G System, also called “NR” or “New Radio”, as well as “NG” or “Next Generation”, is shown in Fig. 1, and is also described in 3GPP TS 38.300. The 5G NR network is comprised of NG RAN (Next Generation Radio Access Network) and 5GC (5G Core Network). As shown, NGRAN is comprised of gNBs (e.g., 5G Base stations) and ng-eNBs (i.e. LTE base stations). An Xn interface exists between gNB-gNB, between (gNB)-(ng-eNB) and between (ng-eNB)-(ng-eNB). The Xn is the network interface between NG-RAN nodes. Xn-U stands for Xn User Plane interface and Xn-C stands for Xn Control Plane interface. AgNG interface exists between 5GC and the base stations (i.e. gNB & ng-eNB). A gNB node provides NR user plane and control plane protocol terminations towards the UE, and is connected via the NG interface to the 5GC. The 5G NR (New Radio) gNB is connected to AMF (Access and Mobility Management Function) and UPF (User Plane Function) in 5GC (5G Core Network). The protocol layers are mapped into three units: RRH (Remote Radio Head), DU (Distributed Unit) and CU (Central Unit) as shown in Fig. 2. Fig. 2 also shows the user plane (UP) protocol stack for New Radio and the control plane (CP) protocol stack for New Radio.

In contrast to classical network architecture, Network Functions Virtualizations, abbreviated as NFV, aims to consolidate many network equipment types onto industry standard high volume servers, switches and storage, which could be located in Datacentres, Network Nodes, and in the end user premises, as illustrated in Fig. 3. NFV involves the implementation of network functions in software that can run on a range of industry standard server hardware, and that can be moved to, or instantiated in, various locations in the network as required, without the need for installation of new equipment. See, e.g., "Network Functions Virtualizations- Introductory White Paper" (PDF). ETSI. 22 October 2012. Retrieved 20 June 2013. Standard terminology definitions and NVF use cases that act as references for vendors and operators have been published as announced in Mulligan, Ultan. "ETSI Publishes First Specifications for Network Functions Virtualizations". Retrieved 5 December 2013. Fig. 3 particularly shows that radio access network nodes are one of the network elements that may be included in a NFV approach.

Currently, 3GPP is working on defining new generation networks that utilize “Network Function Virtualization” or NFV, such as NFV key elements and key requirements for a fifth generation system, e.g., the 5G System, also called “NR” or “New Radio”, as well as “NG” or “Next Generation”. For example, 3GPP TS 38.913 states that RAN architecture shall allow deployments using Network Function Virtualization; 3GPP TS 38.801 states that NR shall allow Centralized Unit (CU) deployment with Network Function virtualization (NFV)’ and, 3GPP TS 38.401 defines a Network Function as "a logical node within a network infrastructure that has well-defined external interfaces and well-defined functional behavior."
As currently envisioned, Network Function Virtualization (NFV) allows flexibility, such as flexibility in time and location. In other words, Network Function Virtualization (NFV) allows for assignment of network functions (e.g., logical nodes) dynamically to hardware resources:

Network Function Virtualization (NFV) allows flexibility in using hardware resources, and results in capacity/pooling gains, compared to static allocation of hardware resources to logical nodes. For example, using Network Function Virtualization (NFV) the same hardware resource can be assigned to several logical nodes at the same time, instead of a single logical node. For a process executed at a node, a certain single process, e.g. an instance of a New Radio Packet Data Convergence Protocol (NR PDCP) entity, can belong to one, and only one, logical RAN node. However, as soon that single instance of the protocol entity is released (e.g., the NR PDCP protocol entity is released), it can be allocated anew to another logical RAN node. Such a pool of RAN UP and RAN CP (Control Plane) protocol entities may be realized in a single physical hardware entity, a central UP entity, and may follow key requirements for 5G system for Network Function Virtualization (NFV).

For NG-RAN (including all dual- and multi-connectivity scenarios), such a central UP entity would provide UP interface termination points (i.e. NG-U, Xn-U and F1-U), provide resources for instantiating protocol entities (e.g. GTP-U, SDAP, PDCP), and would provide access to these resources via a control interface towards a logical CP node. The control interface would be the E1 interface (CP only) in case of gNB-CU. If the gNB-CU is implemented as a single logical node (i.e. no CP-UP split is deployed), then such interface would be internal to the gNB-CU. A possible depiction of CU-UP function virtualization for 5GS and NG-RAN consisting of gNBs is shown in Fig. 4. Fig. 4 shows a Network Function Virtualization (NFV) scheme for 5G New Radio, wherein a shared central unit/user plane entity, CU-UP, is connected across an E1 interface to plural control plane units, CU-CP_gNB.

A virtualization such as the type shown in Fig. 4 may be utilized in both mobility and multi-connectivity scenarios.

In order to support the above:

However, the foregoing introduces layers and layers of signaling which will ultimately add the delay in session establishment, re-establishment, resume, and ON-OFF operations.

What is needed are methods, apparatus, and/or techniques to expedite and/or simplify access to a virtualized radio access network.

In one example, a radio access network comprising: anchor processor circuitry configured to perform a high layer radio access network node operation; distributed processor circuitry configured to perform a low layer radio access network node operation including a medium access control (MAC) operation for a wireless terminal served by the radio access network wherein the distributed processor circuitry handles data radio bearers and signaling radio bearers for the wireless terminal.

In one example, a method in a radio access network comprising: using anchor processor circuitry to perform high layer radio access network node operations; using distributed processor circuitry to perform low layer radio access network node operations including handling data radio bearers and signaling radio bearers for a wireless terminal served by the radio access network.

In one example, a radio access network comprising: processor circuitry configured to establish, for a wireless terminal, both user plane connection and control plane connection prior to the wireless terminal sending or receiving user plane data; transceiver circuitry configured to communicate with the wireless terminal over a radio interface.

In one example, a method in a radio access network comprising: using processor circuitry to establish, for a wireless terminal, both user plane connection and control plane connection prior to the wireless terminal sending or receiving user plane data; communicating with the wireless terminal over a radio interface.

The foregoing and other objects, features, and advantages of the technology disclosed herein will be apparent from the following more particular description of preferred embodiments as illustrated in the accompanying drawings in which reference characters refer to the same parts throughout the various views. The drawings are not necessarily to scale, emphasis instead being placed upon illustrating the principles of the technology disclosed herein.
Fig. 1 is a diagrammatic view of overall architecture for a 5G New Radio system. Fig. 2 is a diagrammatic view showing gNB interface types for the 5G New Radio system of Fig. 1. Fig. 3 is a diagrammatic view showing a migration from a classical network appliance approach to a network virtualization approach. Fig. 4 is a schematic view of an example Network Function Virtualization (NFV) scheme for 5G New Radio. Fig. 5 is a schematic view of an example embodiment of a communications system including a packetized virtual radio access network. Fig. 6 is a diagrammatic view showing how protocols handled by the radio access network of Fig. 5 are split into high layer protocols and low layer protocols. Fig. 7 is an enlarged schematic view of distributed processor circuitry of Fig. 5 which additionally shows a MAC controller. Fig. 8 is a flowchart showing example, basic, representative acts or steps performed by the radio access network of Fig. 5 according to a basic embodiment and mode. Fig. 9 is a diagrammatic view showing example, representative, basic acts or steps involved in an authentication and registration procedure between a wireless terminal and the radio access network of Fig. 5 according to an example embodiment and mode. Fig. 10 is a diagrammatic view showing handover of a wireless terminal between various distributed processor circuitry sites of Fig. 5. Fig. 11 is a flowchart showing example, basic, representative acts or steps performed by the radio access network of Fig. 5 in conjunction with a handover operation. Fig. 12 is a schematic view of an example embodiment of a communications system including a packetized virtual radio access network and comprising plural anchor processor circuitry servers. Fig. 13 is an enlarged schematic view of distributed processor circuitry of Fig. 5 which additionally shows a MAC controller which handles radio bearers for a wireless terminal. Fig. 14 is a flowchart shows example acts or steps performed by a radio access network wherein distributed processor circuitry handles radio bearers. Fig. 15 is a diagrammatic view showing example, representative, non-limiting acts or steps in an example embodiment and mode in which distributed processor circuitry handles data radio bearers and signaling radio bearers for a connection involving the wireless terminal in conjunction with an authentication and registration procedure for the wireless terminal. Fig. 16 is a diagrammatic view showing example, representative, non-limiting acts or steps in an example embodiment and mode in which distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers for a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the anchor processor circuitry makes a handover decision affecting the connection. Fig. 17 is a diagrammatic view showing example, representative, non-limiting acts or steps in an example embodiment and mode in which distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the distributed processor circuitry makes a handover decision affecting the connection. Fig. 18 is a diagrammatic view showing example, representative, non-limiting acts or steps in an example embodiment and mode in which distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the wireless terminal circuitry makes a handover decision affecting the connection. Fig. 19 is a diagrammatic view showing example, representative, non-limiting acts or steps in an example embodiment and mode in which distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover operation or a cell reselection operation when the wireless terminal is not operating in a connected mode and in a situation in which the wireless terminal circuitry makes a handover decision or a cell reselection decision. Fig. 20 is a diagrammatic view showing example, representative, non-limiting acts or steps in an example embodiment and mode in which distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a routing or area update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site. Fig. 21 is a diagrammatic view showing example, representative, non-limiting acts or steps in a first example scenario in which distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a context update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site. Fig. 22 is a diagrammatic view showing example, representative, non-limiting acts or steps in a second example scenario in which distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a context update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site. Fig. 23 is a schematic view of an example embodiment of a generic communications system in which both user plane connection and control plane connection may be established even before a wireless terminal sends or receives User Plane data. Fig. 24 is a diagrammatic view showing example elements comprising electronic machinery which may comprise a wireless terminal, a radio access node, and a core network node according to an example embodiment and mode.

In one of its example aspects the technology disclosed herein concerns structure and operation of a radio access network wherein a protocol stack is split between anchor processor circuitry and distributed processor circuitry. The anchor processor circuitry is configured to perform high layer radio access network node operations; the distributed processor circuitry is configured to perform low layer radio access network node operations, including a medium access control (MAC) operation for a wireless terminal served by the radio access network wherein the distributed processor circuitry handles data radio bearers and signaling radio bearers for the wireless terminal.

In another of its example aspects the technology disclosed herein concerns a radio access network comprising processor circuitry and transceiver circuitry. The processor circuitry is configured to establish, for a wireless terminal, both user plane connection and control plane connection prior to the wireless terminal sending or receiving user plane data. The transceiver circuitry configured to communicate with the wireless terminal over a radio interface. In an example, non-limiting implementation, the radio access network comprises both anchor processor circuitry and distributed processor circuitry. The anchor processor circuitry is configured to perform a high layer radio access network node operation. The distributed processor circuitry is configured to perform a low layer radio access network node operation, and wherein the radio network is configured to establish both the user plane connection and the control plane connection between the anchor processor circuitry and the distributed processor circuitry prior to the wireless terminal sending or receiving user plane data.

In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the technology disclosed herein. However, it will be apparent to those skilled in the art that the technology disclosed herein may be practiced in other embodiments that depart from these specific details. That is, those skilled in the art will be able to devise various arrangements which, although not explicitly described or shown herein, embody the principles of the technology disclosed herein and are included within its spirit and scope. In some instances, detailed descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the technology disclosed herein with unnecessary detail. All statements herein reciting principles, aspects, and embodiments of the technology disclosed herein, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure.

Thus, for example, it will be appreciated by those skilled in the art that block diagrams herein can represent conceptual views of illustrative circuitry or other functional units embodying the principles of the technology. Similarly, it will be appreciated that any flow charts, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.

As used herein, the term “core network” can refer to a device, group of devices, or sub-system in a telecommunication network that provides services to users of the telecommunications network. Examples of services provided by a core network include aggregation, authentication, call switching, service invocation, gateways to other networks, etc.

As used herein, the term “wireless terminal” can refer to any electronic device used to communicate voice and/or data via a telecommunications system, such as (but not limited to) a cellular network. Other terminology used to refer to wireless terminals and non-limiting examples of such devices can include user equipment terminal, UE, mobile station, mobile device, access terminal, subscriber station, mobile terminal, remote station, user terminal, terminal, subscriber unit, cellular phones, smart phones, personal digital assistants (“PDAs”), laptop computers, tablets, netbooks, e-readers, wireless modems, etc.

As used herein, the term “access node”, “node”, or “base station” can refer to any device or group of devices that facilitates wireless communication or otherwise provides an interface between a wireless terminal and a telecommunications system. A non-limiting example of a base station can include, in the 3GPP specification, a Node B (“NB”), an enhanced Node B (“eNB”), a home eNB (“HeNB”), a gNB (for a New Radio [“NR”] technology system), or some other similar terminology.

As used herein, the term “telecommunication system” or “communications system” can refer to any network of devices used to transmit information. A non-limiting example of a telecommunication system is a cellular network or other wireless communication system.

As used herein, the term “cellular network” or “cellular radio access network” can refer to a network distributed over cells, each cell served by at least one fixed-location transceiver, such as a base station. A “cell” may be any communication channel that is specified by standardization or regulatory bodies to be used for International Mobile Telecommunications-Advanced (“IMTAdvanced”). All or a subset of the cell may be adopted by 3GPP as licensed bands (e.g., frequency band) to be used for communication between a base station, such as a Node B, and a UE terminal. A cellular network using licensed frequency bands can include configured cells. Configured cells can include cells of which a UE terminal is aware and in which it is allowed by a base station to transmit or receive information. Examples of cellular radio access networks include E-UTRAN, and any successors thereof (e.g., NUTRAN).

Fig. 5 illustrates a telecommunication network 20 which comprises core network 22 and radio access network 24. For sake of non-limiting, example illustration, the core network 22 is illustrated as being a 5G core network, and thus the radio access network 24 is shown as connected to core network 22 over an interface labeled as the NG interface. Although the radio access network 24 is illustrated as using some terminology and functionality of a New Generation (NG) radio access network, as described further herein the radio access network 24 differs from the radio access network of Fig. 1, for example, in being a packetized virtual radio access network, PVRAN. The fact that the core network 22 and radio access network 24 are described somewhat in 5G terms does not limit the networks to being 5G networks, as the structure and operation of radio access network 24 as described herein have applicability to other networks as well.

As understood by those skilled in the art, when the core network 22 is a 5G core network, the 5G core network 22 performs various core network functions, such as an access and mobility management function (AMF); session management function; user plane function (UPF); policy control function (PCF); authentication server function (AUSF); unified data management (UDM) function; application function (AP); network exposure function (NEF); NF repository function (FRF); and network slice selection function (NSSF). As representative ones of these functions, user plane function (UPF) 26 and access and mobility management function (AMF) 28 are illustrated in Fig. 5.

The radio access network 24 serves one or more wireless terminals 30 which communicate over an air or radio interface 31 with radio access network 24, only one such wireless terminal 30 being shown in Fig. 5 for simplicity. Generally speaking, a wireless terminal 30 may comprise a transceiver 32 and processor circuitry 34 which executes one or more programs or code in an operating system and one or more application programs, which may be stored in non-transient memory 36. The wireless terminal 30 may also include user interface(s) 38.

Fig. 5 further shows that packetized virtual radio access network 24 comprises anchor processor circuitry 40 and distributed processor circuitry 42. The distributed processor circuitry 42 is associated with, e.g., may comprise or be connected to, transceiver circuitry 44. Fig. 5 shows anchor processor circuitry 40 as being connected through packet network 48 by pipes or channels 46 to two distributed processor circuits, particularly to distributed processor circuitry 42₁ and distributed processor circuitry 42₂, although one or any number of distributed processor circuits 42 may be connected to anchor processor circuitry 40. The distributed processor circuits 42, each having associated transceiver circuitry 44, are preferably located at different geographical sites, in a manner such as of conventional base station nodes. As such, the distributed

processor circuits

42₁ and 42₂ are also referred to distributed processor circuitry sites. Plural distributed processor circuitry sites may comprise the overall distributed processor circuitry 42.

The elements of radio access network 24 as described above may also be known by other names. For example, the anchor processor circuitry 40 may be referred to as an “anchor central unit”, or “anchor CU”, for example. The distributed processor circuitry 42, since it may comprise the transceiver circuitry 44, may be referred to as a “radio/DU” or “radio/distributed unit”. The transceiver circuitry 44 may be referred to as a “radio part”, or “radio head”, for example. The transceiver circuitry 44 may comprise both transmitter circuitry and receiver circuitry, and typically includes antenna(e). For its transmitter circuitry the transceiver circuitry 44 may include, e.g., amplifier(s), modulation circuitry and other conventional transmission equipment. For its receiver circuitry the transceiver circuitry 44 may comprise, e.g., amplifiers, demodulation circuitry, and other conventional receiver equipment.

The anchor processor circuitry 40 is configured to perform high layer radio access network node operations for a connection with a wireless terminal. As such, Fig. 5 shows anchor processor circuitry 40 as executing certain high layer protocols 50. In addition, the distributed processor circuitry 42 is configured to generate and maintain a context for the connection with the wireless terminal. Fig. 5 thus shows anchor processor circuitry 40 as comprising context memory 52.

In contrast to anchor processor circuitry 40, the distributed processor circuitry 42 is configured to perform low layer radio access network node operations for the connection with the wireless terminal. Fig. 5 accordingly shows distributed processor circuitry 42 as executing lower layer protocols 54. In addition, distributed processor circuitry 42 comprises context memory 56.

The distributed processor circuitry 42 may comprise one or more distributed processor circuitry sites such as

sites

42₁ and 42_2.The distributed processor circuitry 42 is connected to anchor processor circuitry 40 through packet network 48. The packet network 48 may comprise, for example, an Internet Protocol (IP) packet network, although other types of packet networks are also possible. For a given connection with a wireless terminal, the anchor processor circuitry 40 is configured to provide a first endpoint TEID_A for a tunnel 60 through which the connection is carried over packet network 48 to the distributed processor circuitry 42, and the distributed processor circuitry 42 is configured to provide a second endpoint for tunnel 60. The second endpoint for the tunnel 60 at the distributed processor circuitry 42 depends on the particular distributed processor circuitry site to which the tunnel 60 is connected. For example, when the tunnel 60 is connected to distributed processor circuitry site 421, the second endpoint of tunnel 60 is labeled as TEID₁.

For each connection handled by the radio access network, a “context”, sometimes referred to as a “UE context”, is generated and maintained. As used herein, “context” or “UE context” may include items of information such as an identification of the wireless terminal involved in the connection; encryption keys for the wireless terminal; parameters associated with each of the protocol layers; and other information (such as whether the wireless terminal is moving, measurement activity by the wireless terminal, etc.). The context for a UE connection may be spread throughout a system, e.g., to different elements which support or are involved in the UE connection. For example, for a given UE context there may be contexts in an IMS application server, Core network elements, and various RAN elements, for example. Therefore, the UE connection may be viewed as having plural “contexts”, e.g., a different portion of the overall UE context perhaps being stored at variously throughout the system. The contexts are generated when the UE powers up and performs registration (e.g., attach procedures). These contexts may have variations in terms of attributes and IE depending on the functionality of the node. The contexts may be stored, maintained, and used by radio resource management (RRM) functionality, which may comprise or be included in Controlling Software or the Operation System.

In an example embodiment and mode, the radio resource management (RRM) functionality is split between anchor processor circuitry 40 and distributed processor circuitry 42. Fig. 5 therefore shows that anchor processor circuitry 40 comprises anchor radio resource management (RRM) controller 58 and that distributed processor circuitry 42 comprises distributed radio resource management (RRM) controller 59. As such, the distributed processor circuitry 42 includes at least some of the radio resource management (RRM) functionality. The anchor radio resource management (RRM) controller 58 manages and stores certain context content in context memory 52, the distributed radio resource management (RRM) controller 59 manages and stores certain context content in context memory 56. The context stored in context memory 56 of distributed processor circuitry of a distributed processor circuitry site 42 includes information pertaining to admission control, including resource allocation and tracking for all UEs within the coverage area of the particular distributed processor circuitry site. The context stored in context memory 52 of anchor processor circuitry 40 includes information pertaining to IP connectivity contexts, Identifications, TEIDs, security keys, and mobility-related contexts.
Fig. 6 provides further illustration of how protocols handled by the radio access network 24 are split into high layer protocols and low layer protocols, and does so in contrast to the conventional 5G gNodeB protocol stack. A portion of Fig. 6 to the left of the developmental progression arrow shows that the conventional 5G unified gNodeB handles a protocol stack comprising, from lowest to highest protocol layer: physical layer (PHY) and medium access control (MAC) protocols; radio link control (RLC) protocol; Radio Packet Data Convergence (PDCP) protocol; and Service Data Adaptation Protocol (SDAP) protocol. The portion of Fig. 6 to the right of the developmental progression arrow shows the radio access network 24 of the technology disclosed herein, featuring the anchor processor circuitry 40, also known as the anchor CU, and three distributed

processor circuitry sites

42₁, 42₂, and 42₃. Although three sites 42 are shown, the split of the protocols of Fig. 6 applies to any number of sites, e.g., one or more sites. The high layer protocols 50 of the anchor processor circuitry 40 are shown in Fig. 6 as comprising the Radio Packet Data Convergence (PDCP) protocol and the Service Data Adaptation Protocol (SDAP), whereas the lower layer protocols 54 of the distributed processor circuitry 42 is shown as comprising the physical layer and medium access control (MAC) protocols and the radio link control (RLC) protocols. Thus, the high layer radio access network node operations comprise a Service Data Adaptation Protocol (SDAP) operation and a Packet Data Convergence Protocol (PDCP) operation; whereas the low layer radio access network node operations comprise a radio link control (RLC) operation and a medium access control (MAC) operation.

As indicated above, the low layer radio access network node operations comprise a medium access control (MAC) operation. At the distributed processor circuitry 42 the medium access control (MAC) operation is executed by a MAC controller or MAC entity, such as MAC controller 64 shown in the representative distributed processor circuitry cite 42i of Fig. 7. Advantageously, the MAC protocol, and MAC controller 64 in particular, handles at least some of the radio resource management (RRM) functionality required for a connection between the wireless terminal and the radio access network. Fig. 7 thus shows that the distributed radio resource management (RRM) controller distributed radio resource management (RRM) controller 59 for distributed processor circuitry 42i may be included in or comprise the MAC controller 64.

In an example embodiment and mode, all RRC messages may be terminated at the MAC layer, and hence become MAC Control Functions. For example, in an example embodiment and mode, the MAC controller 64 is configured to handle the data radio bearers, DRBs, and signaling radio bearers, SRBs, for the connection. This means that, for such example embodiment and mode, preferably the MAC controller 64 allocates, modifies, and releases all data radio bearers, DRBs, and signaling radio bearers, SRBs, for the connection.

In addition, in an example embodiment and mode, some or all security/encryption functions may or may not (for support of backward compatibility UEs and operations) be moved from the Radio Packet Data Convergence (PDCP) layer to the MAC layer, e.g., some keys are negotiated by MAC controller 64. Performing the security functions at the MAC layer allows for faster key exchanges and session establishment and release, hence enhancing the network performance and mobility. Keeping the same context (at the CU or the PDCP) after handover from one distributed processor circuitry site to another, means that the same encryption keys may be utilized before, during, and after the handover as before the handover process is initiated, which eliminates the need for the establishment/release or the reconfiguration of the PDCP entity including further security negotiations, and thus conserves processing resources and expedites the handover. As used herein, keeping a “same context” in a handover operation means at least one and preferably both of the following: (1) that the context maintained by anchor radio resource management (RRM) controller 58 for the anchor processor circuitry 40 remains mostly the same (especially the encryption functionality and Key assignments for CP and UP traffic is maintained in the CU/PDCP) after the handover as before the handover. There is some small change expected in the context information at the Anchor CU unit, including the context information related to the new connections established with the New/target DU) as used by the anchor processor circuitry 40 for the involved connection after the handover; and (2) that the PDCP/CU related context information as used by the distributed processor circuitry 42 for the connection involving the wireless terminal does not change when the wireless terminal is handed over from one distributed processor circuitry site to another distributed processor circuitry site. In other words, the context at the CU may be updated to include information related to the new distributed processor circuitry site, but the contexts related to the UE and the CP/UP traffic, e.g., Keys, PDCP entities, …etc., at the PDCP, should not be affected since everything is anchored at that anchor processor circuitry 40, e.g., at the CU. Only the DU-related contexts such as DU-TEIDs, CU-DU connection information, etc., are expected to change and hence it shall be updated at the anchor processor circuitry 40 and established at the distributed processor circuitry site.

Fig. 8 shows example, basic, representative acts or steps performed by the radio access network 24 of Fig. 5 according to a basic embodiment and mode of the technology disclosed herein. Act 8-1 comprises using anchor processor circuitry to perform high layer radio access network node operations for a connection with a wireless terminal and to maintain a context for the connection with the wireless terminal. Act 8-2 comprises using distributed processor circuitry to perform low layer radio access network node operations for the connection with the wireless terminal and to utilize the context as used by the anchor processor circuitry. Act 8-3 comprises transmitting and receiving packets comprising the connection, both between the distributed processor circuitry and the wireless terminal over a radio interface with the wireless terminal and over a packet network through a tunnel having a first endpoint at the anchor processor circuitry and a second endpoint at the distributed processor circuitry.

Fig. 9 shows example, representative, basic acts or steps involved in an authentication and registration procedure between a wireless terminal and the radio access network of Fig. 5 according to an example embodiment and mode. Act 9-1 comprises the wireless terminal 30 performing a power up operation. Upon completion of the power up operation of act 9-1, an authentication and registration procedure 9-2 is performed between the wireless terminal 30 and radio access network 24. As a first aspect of the authentication and registration procedure 9-2, a random access procedure 9-2-1 is performed between wireless terminal 30 and one of the distributed processor circuits, such as distributed processor circuitry 42₁ in the present example scenario. After the wireless terminal 30 is granted access, and as a second aspect of the authentication and registration procedure 9-2, as act 9-2-2 a UE context for the wireless terminal 30 is established at distributed processor circuitry 42₁. The UE context is stored in context memory 56 of the distributed processor circuitry 42₁. As a third aspect of the authentication and registration procedure 9-2, as act 9-2-3 a tunnel endpoint for the connection is established at the distributed processor circuitry 42 and both the UE context and the tunnel endpoint for the connection are signaled to anchor processor circuitry 40. The tunnel endpoint may be, for example, endpoint TEID₁ shown in Fig. 5. The tunnel endpoint TEID₁ is the endpoint for the tunnel for the access permitted-connection for wireless terminal 30. In conjunction with a fourth aspect of the authentication and registration procedure 9-2, as act 9-2-4 the UE context is stored in context memory 52 of anchor processor circuitry 40. Moreover, the tunnel endpoint TEID₁ at distributed processor circuitry 42₁ for this connection with the wireless terminal 30 is noted by anchor processor circuitry 40. As act 9-2-5 the MAC controller 64 of distributed processor circuitry 42₁ conducts an authentication procedure whereby security keys are negotiated for anchor processor circuitry 40 and distributed processor circuitry 42₁ for this connection with the wireless terminal 30. The authentication procedure typically results in the generation of security keys for the distributed processor circuitry 42, e.g., DU-Keys, and security keys for the anchor processor circuitry 40, e.g., CU-Keys. Also the distributed processor circuitry 42₁ receives the identifier of the tunnel endpoint for tunnel 60 at the anchor processor circuitry 40, e.g., receives the endpoint identifier TEID_A of Fig. 5, for example. As act 4-3 the wireless terminal 30 is provided by distributed processor circuitry 42₁ with the UE context, as well as the endpoints for tunnel 60, e.g., both TEID_A = UE-1 CU TEID and TEID₁ = UE-1 DU TEID, and the encryption keys e.g., the encryption key for distributed processor circuitry 42₁ (DU-keys) and the encryption key for anchor processor circuitry 40 (CU-keys).

As understood from Fig. 5 and the preceding discussion, the transceiver circuitry 44 may comprise plural transceivers, such as transceiver circuitry 44₁ and transceiver circuitry 44₂, any possibly other transceiver circuits as well, located at different sites. Similarly, the distributed processor circuitry 42 may comprise plural distributed processor circuitry sites such as the

sites

42₁ and 42₂ shown in Fig. 5, or even a greater number of plural sites as indicated by

sites

42₁, 42₂, and 42₃ shown in Fig. 6, Fig. 9, and Fig. 10.

Fig. 10 shows handover of a wireless terminal between various distributed processor circuitry sites, such as the sites of Fig. 6 and Fig. 9. Fig. 10 shows by arrow 70₁ a first handover of wireless terminal 30, e.g., UE 1, from distributed processor circuitry 42₁ to distributed processor circuitry 42₂, and by arrow 70₂a second handover of wireless terminal 30 from distributed processor circuitry 42₂ to distributed processor circuitry 42₃. Usage of the term “handover” herein should be understood to encompass and/or include a “handoff” to the extent, if any, that the terms have any different meaning.

The plural distributed processor circuitry sites 42 are configured so that, upon a handover of the connection with the wireless terminal from a first distributed processor circuitry site to a second distributed processor circuitry site, the same context may be utilized for the connection involving the wireless terminal. In other words, the second distributed processor circuitry site after the handover uses a same context for the connection as was used by the first distributed processor circuitry site before the handover. Moreover, the anchor processor circuitry 40 may use the same context for the connection after the handover as it used before the handover.

Fig. 10 illustrates that, at the time of initial setup of the connection for wireless terminal 30 UE 1, UE context 72_A for UE 1 is established in context memory 52 of anchor processor circuitry 40, and a corresponding context 72₁ is established at distributed processor circuitry 42₁. As indicated above, the context 72_A stored in context memory 52 of anchor processor circuitry 40 may include information pertaining to IP connectivity contexts, Identifications, TEIDs, security keys, and mobility-related contexts. On the other hand, the context 72₁ stored in context memory 56 may include context information pertaining to admission control, including resource allocation and tracking for all UEs within the coverage area of the particular distributed processor circuitry site. Before the handover of the connection involving wireless terminal 30 indicated by arrow 70₁, the anchor processor circuitry 40 and distributed processor circuitry 42₁ communicate over tunnel 60₁, the tunnel 60₁ having endpoints TEID_A and TEID₁.

After the handover of the connection involving wireless terminal 30 indicated by arrow 70_1,the anchor processor circuitry 40 and distributed processor circuitry 42₂ communicate over tunnel 60₂, the tunnel 60₂ having endpoints TEID_A and TEID₂. The second endpoint of the tunnel changes as a result of the handover, but the UE context 72 as utilized by the distributed processor circuitry 42 for the involved wireless terminal 30, e.g., UE 1, remains the same after the handover indicated by arrow 72₁. In other words, a new context for the wireless terminal 30 does not need to be established within the distributed processor circuitry 42 as a result of the handover, with the result that the content of the original UE context 72₁ established when the connection existed at distributed processor circuitry site 42₁ can be used at the distributed processor circuitry site 42₂ and thus does not have to be changed or a new context generated and signaled between anchor processor circuitry 40 and distributed processor circuitry 42₂because of the handover. Accordingly, when the connection is handed over to distributed processor circuitry site 42₂ the same UE context 72₁ can be utilized at the distributed processor circuitry site 42₂ as was used when the connection was at distributed processor circuitry site 42₁. Moreover, the context 72_A as used by the anchor processor circuitry 40 before the handover can also be used after the handover.

Fig. 10 further illustrates by arrow 70₂ that the connection involving wireless terminal 30, e.g., UE 1, may be further handed over from distributed processor circuitry site 42₂ to distributed processor circuitry site 42₃. After the handover indicated by arrow 70_2,the anchor processor circuitry 40 and distributed processor circuitry 42₃ communicate over tunnel 60₃, the tunnel 60₃ having endpoints TEID_A and TEID₃. Again, the second endpoint of the tunnel changes as a result of the handover, but the UE context 72₁ for the involved wireless terminal 30, e.g., UE 1, remains the same after the handover indicated by arrow 72₂. Thus a new context for the wireless terminal 30 does not need to be established as a result of the handover, with the result that the content of the original UE context 72₁ established when the connection existed at distributed processor circuitry site 42₁ does not have to be changed or a new context generated and signaled between anchor processor circuitry 40 and distributed processor circuitry 42₃. Thus again, when the connection is handed over to distributed processor circuitry site 42₃ the same UE context 72₁ can be utilized as was used when the connection was at distributed processor circuitry site 42₃. As in the case of the earlier handover indicated by arrow 70₁, the context 72_A as used by the anchor processor circuitry 40 before the handover indicated by arrow 70₂ can also be used after that handover.

Since the same UE context 72₁ is essentially handed over between the different distributed processor circuitry sites as the connection involving wireless terminal 30 is handed over, the contents of the UE context 72₁ need not be re-negotiated, thus eliminating considerable signaling between the anchor processor circuitry 40 and the handed-over-to distributed processor circuitry site. The UE context 72₁ includes many elements of information, none of which thus need to be changed or re-negotiated. Among the elements of the UE context 72₁ is encryption information, e.g., encryption keys, such as the encryption or security keys CU-Keys and DU-keys illustrated in and discussed in conjunction with Fig. 9, for example. Moreover, the UE context 72_A for the connection involving wireless terminal 30, as initially set up for the connection, can be maintained at anchor processor circuitry 40 regardless of subsequent handover. In other words, after the handover indicated by arrow 70₁, the anchor processor circuitry 40 still maintains the same UE context 72_A for the connection through distributed processor circuitry 42₂, and after the handover indicated by arrow 70₁, the anchor processor circuitry 40 still maintains the same UE context 72_A for the connection through distributed processor circuitry 42₃.

A handover such as that depicted by Fig. 10 is also illustrated by a handover operation having example, representative acts or steps as shown in Fig. 11. It is understood that, in a handover scenario, the transceiver circuitry 44 comprises plural transceivers, such as

transceivers

44₁, 44_{2, …}; the distributed processor circuitry 42 comprises plural distributed processor circuitry sites, e.g., distributed

processor circuitry sites

42₁, 42₂, …; and each of the plural distributed processor circuitry sites is associated with a respective one of the plural transceivers. According to a basic example embodiment and mode, upon a handover of the connection with the wireless terminal from a first distributed processor circuitry site to a second distributed processor circuitry site, acts 11-1 and 11-2 are performed. Act 11-1 comprises the second distributed processor circuitry site using a same context for the connection as was used by the first distributed processor circuitry site before the handover. Act 11-2 comprises changing the second endpoint for the tunnel to an endpoint associated with the second distributed processor circuitry site rather than an endpoint associated with the first distributed processor circuitry site.

There may be several different variation of handover procedures. For example, in Network-based handover the anchor processor circuitry 40 triggers the handover and determine the target distributed processor circuitry site 42. In such case, the anchor processor circuitry 40 may install the same context, e.g., context 72₁, in the new distributed processor circuitry site and establish the TEID for the new distributed processor circuitry site, and then communicate that back to the wireless terminal in a handover command. In another embodiment of handover procedure, a first distributed processor circuitry site may trigger the handover and may determine the target or second distributed processor circuitry site, after which the same context, e.g., context 72₁, may be installed in the target distributed processor circuitry site either directly via a direct interface (e.g., Xn interface) or indirectly through the anchor processor circuitry 40. Either way a new TEID is established at the new or second distributed processor circuitry site and a new tunnel with the anchor processor circuitry 40 is established. Related information will be communicated to the wireless terminal so that the wireless terminal can perform the handover to the target distributed processor circuitry site). In yet another embodiment of handover procedure, the wireless terminal may trigger the handover and the wireless terminal may determine the target distributed processor circuitry site for the handover. In this third embodiment the wireless terminal UE may also communicate information to the source distributed processor circuitry site to perform the Tunnel establishment before the actual handover (e.g., in make before break fashion), or the wireless terminal may initiate the handover to the target distributed processor circuitry site, with the result that the new or target distributed processor circuitry site may retrieve the context from the source distributed processor circuitry site either directly (e.g., through the Xn interface( or indirectly through the anchor processor circuitry 40. In either case the wireless terminal may provide the identification of the source distributed processor circuitry site and/or the identification of the anchor processor circuitry 40. The target distributed processor circuitry site may then request the contexts using these identifications. The target distributed processor circuitry site may also establish the TEID for the tunnel with the CU.

It should thus be apparent that shifting of many radio access network functions from high protocol layers to low protocol layers, e.g., the protocol layers handled by the distributed processor circuitry 42, in the manner of the technology disclosed herein, facilitates faster establishment and tear-down of connections and faster handover.

According to another example embodiment and mode illustrated in Fig. 12, the anchor processor circuitry 40 may comprise plural anchor processor circuitry servers, such as plural anchor processor circuitry server 40₁ through 40₃, also illustrated and known as CU1 through CU3. The plural anchor processor circuitry servers are connected through packet network 48 to the plural distributed processor circuitry sites 42₁ - 42₁₀ comprising the distributed processor circuitry 42. As such each of the plural anchor processor circuitry servers 40 is connected by the packet network 48 to one or more of the plural distributed processor circuitry sites 42₁- 42₁₀.

One non-limiting example advantage of the packetized virtual radio access network 40 of Fig. 12 is that an initial anchor processor circuitry server involved in initial setup of the connection is configured to maintain the context for the connection with the wireless terminal regardless of to which of the plural distributed processor circuitry sites the connection is handed over. For example, suppose in the Fig. 12 scenario that a connection is initially setup between anchor processor circuitry 40₁ and wireless terminal UE1 through distributed processor circuitry site 42₁. The connection between anchor processor circuitry 40₁ and wireless terminal UE1 through distributed processor circuitry site 42₁ involves UE context 72₁, as understood with reference to the previous discussion of Fig. 10. Fig. 12 also shows that another connection is setup between anchor processor circuitry 40₂ and wireless terminal UE14 through distributed processor circuitry site 42_5.After setup of the initial connection involving wireless terminal UE1, further suppose that wireless terminal UE1 is involved in a handover and is handed over to distributed processor circuitry site 42₅, as shown by arrow 70₁₂. Despite the handover of wireless terminal UE1 to a distributed processor circuitry site such as distributed processor circuitry site 42₅ that is handling a connection routed to another anchor processor circuitry server 40₂, e.g., the connection involving wireless terminal UE14, after the handover the connection involving wireless terminal UE1 is still with anchor processor circuitry server 40₁ and the same UE context 72₁ for the wireless terminal UE1 can be utilized while the connection is routed through and served by distributed processor circuitry site 42₅. Fig. 12 thus illustrates the distributed processor circuitry sites 42₁- 42₁₀ are flexibly associated with the plural anchor processor circuitry servers 40, with the result that an initial anchor processor circuitry server involved in initial setup of the connection maintains the context for the connection regardless of to which distributed processor circuitry site the connection is handed over. Thus, the wireless terminal, as it moves between distributed processor circuitry sites 42, does not need to change between plural anchor processor circuitry servers 40as long as the wireless terminal remains in the same packetized virtual radio access network. Viewed another way, a migrating wireless terminal is not obligated to change to another plural anchor processor circuitry server in view of the particular distributed processor circuitry site to which it has been handed over. In other words, a particular distributed processor circuitry site is required to utilize a particular plural anchor processor circuitry server_. This assures continuity of delivery.

As a corollary of the foregoing, a particular distributed processor circuitry site may use one anchor processor circuitry server for a first connection, e.g., with UE1, and another plural anchor processor circuitry server for a second connection, e.g., with UE14.

As described herein, pipes 46 are packet connections, e.g., IP connections, which are used to connect the various processor circuitries to the packet network 48. In view of advantages of the technology disclosed herein such as, for example, the reusability of contexts, the bandwidth required for a particular connection may be less than for a conventional radio access network. But preferably the pipes 46 have large bandwidth for the sake of accommodate numerous connections, e.g., connections involving plural wireless terminals, perhaps with some of the wireless terminals being involved in plural connections. In view of the large bandwidth, the pipes 46 may be referred to herein an illustrated as “fat pipes”. The concept of a FAT PIPE may be implemented between the anchor processor circuitry 40 and all distributed processor circuitry sites 42 where the wireless terminal does not have to initiate or reconfigure all the layering (e.g., MAC, RLC, PDCP, SDAP) for individual pipes or bearers that it needs to establish connectivity within the radio access network.

The radio access network 24 fully implement a packet model rather than the dedicated Circuit model where individual SRBs and DRBs are established for individual UEs and for particular services. Moreover, the MAC protocol layer, e.g., MAC controller 64, at the distributed processor circuitry site 42 may be able to receive data from wireless terminal s over the air and multiplex these data packets and forward them to anchor processor circuitry 40 without any impact or degradations. The anchor processor circuitry 40 may be able to process these packets and forward them to the appropriate destination depending on their headers rather than its PIPE ID.
In the prior art, all RRC messages have to go through all layers of the protocol stack of the gNB shown in Fig. 6. This involves a separate instance in the UE for each layer of the protocol stack. Whenever a UE establishes or re-establishes a connection, e.g., at a handover, the instance for each layer must be established or re-established. Repeated establishment and re-establishment of the instances for each protocol layer on occasion of a handover, for example, utilizes considerable signaling, processing power, and time. As one of its advantages the technology disclosed herein addresses the signaling, processing power, and time concerns by separating the protocol stack so that only certain high layer protocols are executed at the anchor processor circuitry 40, and certain low layer protocols are moved to and executed at the distributed processor circuitry 42, at the distributed processor circuitry sites. In particular, at least some functionality of the Radio Resource Management (RRM) is moved to the radio unit, e.g., to distributed processor circuitry 42. When a channel is needed, the channel can be obtained at the distributed processor circuitry 42 rather than having to request the channel from the anchor processor circuitry 40. The technology disclosed herein achieves the desired connectivity, and sets up and flows in a faster way.

Some aspects of telephone technology years ago migrated from a circuit switched philosophy, involving dedicated wires or connections, to a packet switched philosophy, in which packets could take any route between source and destination. In a similar migratory manner, the Network Function Virtualization (NFV) radio access network of the technology disclosed herein flexibly routes packets transmitted through the radio access network between a wireless terminal and anchor processor circuitry without requiring a dedicated or unchangeable path for the packets, as illustrated, for example, by Fig. 12.

Fig. 13 shows an example embodiment and mode wherein the MAC controller 64 of distributed processor circuitry 42 handles radio bearers, e.g., one or more and preferably all of the data radio bearers, DRBs, and signaling radio bearers, SRBs, e.g., for an operation or a connection involving a wireless terminal. MAC controller 64 of Fig. 13 comprises radio bearer handler 80 which preferably allocates, modifies, and releases all data radio bearers, DRBs, and signaling radio bearers, SRBs, for the connection, and does so in a variety of operations as discussed with reference to each of Fig. 15 - Fig. 22. By “handling” a radio bearer may mean one or more of setting up, adding, releasing, or modifying a radio bearer.

Fig. 14 shows example, representative, non-limiting acts or steps performed by a radio access network 24 wherein distributed processor circuitry, such as distributed processor circuitry 42 of Fig. 13, comprises MAC controller 64 which handles radio bearers. Act 14-1 comprises using anchor processor circuitry to perform high layer radio access network node operations. Act 14-2 comprises using distributed processor circuitry to perform low layer radio access network node operations including handling data radio bearers and signaling radio bearers for a wireless terminal served by the radio access network.

Fig. 15 shows example, representative, non-limiting acts or steps in an example embodiment and mode in which distributed processor circuitry 42 handles data radio bearers and signaling radio bearers for a connection involving the wireless terminal in conjunction with (e.g., upon completion of) an authentication and registration procedure for the wireless terminal. Act 15-1 comprises the wireless terminal 30 powering up. After power-up, DU-CU authentication and registration procedure(s) 15-2 are performed.

Authentication and registration procedure(s) 15-2 of Fig. 15 comprise acts 15-3 through 15-7. Act 15-3 comprises wireless terminal 30 performing a random access procedure with distributed processor circuitry site 42₁. The context information for the UE context is obtained as a result of the random access procedure (act 15-3), which is executed to connect to the network after Power UP (act 15-1). Following successful completion of the random access procedure of act 15-3, as act 15-4 the distributed processor circuitry site 42₁ constructs a context for wireless terminal 30, e.g., UE-1. As act 15-5 the distributed processor circuitry site 42₁ and anchor processor circuitry 40 engage in signaling so that both distributed processor circuitry site 42₁ and anchor processor circuitry 40 have respective contexts for UE-1 and know the endpoints TEID_A and TIED₁ that will be used for a tunnel for the connection being set up. Some of the signaling of act 15-5 involves the distributed processor circuitry site 42₁ providing anchor processor circuitry 40 with at least some of the context information for UE-1 as constructed by distributed processor circuitry site 42₁ and the distributed processor circuitry site 42₁ requesting the tunnel endpoints. As a result of the signaling of act 15-5, act 15-6 shows that anchor processor circuitry 40 has both a context that it will maintain for UE-1 and tunnel endpoints (TEIDs) for the connection with UE-1. Similarly as a result of the signaling of act 15-5, act 15-7 shows that distributed processor circuitry site 42₁ now has, in addition to the already-constructed context for UE-1, the tunnel endpoints, e.g., UE-1 CU TEID and DU TEID, as well as encryption keys that are to be used for the connection. In this parlance, UE-1 CU TEID is the tunnel endpoint at the anchor processor circuitry 40, e.g., TEID_A, and DU TEID is the tunnel endpoint at distributed processor circuitry site 42₁, e.g., TEID₁.

The framed box of authentication and registration procedure(s) 15-2 of Fig. 15 shows, e.g., an arrow to depict random access procedures 15-3 and an arrow to depict the request signal of act 15-5, and certain boxes as act 15-4, act 15-6, and act 15-7 to depict either establishment or content of contexts. However, it should also be understood that the framed box of authentication and registration procedure(s) 15-2 of Fig. 15 also includes an attachment procedure whereby, e.g., the wireless terminal 30 registers with the network to receive services that require registration, and wherein a mobile equipment identity is obtained from wireless terminal 30. This should be understood to apply to all instances of authentication and registration procedure(s) as described herein.

Act 15-8 of Fig. 15 shows that both control plane (CP) and user plane (UP) connectivity between anchor processor circuitry 40 and distributed processor circuitry site 42₁ result upon completion of the Authentication and registration procedure(s) 15-2 of Fig. 15. As explained above, The DU-CU authentication and registration process 15-2 results in the establishment of UE contexts at the distributed processor circuitry site 42₁ (DU) and anchor processor circuitry 40 (CU). The wireless terminal 30 powers up and does not perform any other procedures than the initial attach procedures. In an example embodiment and mode, a difference of the technology disclosed herein from the prior art attachment procedures is the establishment of a user plane connection and a control plane connection between the distributed processor circuitry site 42₁ , e.g., DU, and anchor processor circuitry 40, e.g., CU, as shown by step 15-8. In the prior art, only a control plane connection is established during the attachment procedure, and user plane connectivity is established only subsequently when the UE sends or receives User Plane data.

Act 15-9 shows that control plane connectivity may be established between wireless terminal 30 UE-1 and distributed processor circuitry site 42₁. Act 15-9 shows that the signaling connection which include the establishment procedures of the contexts in all nodes is configured and is active. The arrow of act 15-9 is shown as a broken arrow since at act 15-9 only control plane connectivity is established, in contrast to the solid arrow of act 15-8 which indicates that both control plane connectivity and user plane connectivity are established.

Act 15-10 shows that wireless terminal 30 has its context for the connection, e.g., UE-1 context. As mentioned above, the context information for the UE context, e.g., the keys and tunnel endpoint identifiers, was obtained as a result of the random access procedure 15-3, which was executed to connect to the network after Power UP (act 15-1). The UE-1 context includes, for example, encryption keys for both anchor processor circuitry 40 and distributed processor circuitry site 42₁, e.g., CU-keys and DU-keys, respectively, and the tunnel endpoint identifiers, e.g., the UE-1 CU TEID and UE-1 DU TEID, for anchor processor circuitry 40 and distributed processor circuitry site 42₁, respectively.

Act 15-11 of Fig. 15 illustrates example operations including radio bearer handling operations which may occur between distributed processor circuitry site 42₁ and wireless terminal 30 after the wireless terminal 30 powers up (act 15-1) and after the authentication and registration procedure(s) 15-2 is performed. At the distributed processor circuitry site 42₁ the radio bearer handling operations 15-11 may be executed or performed by radio bearer handler 80; at the wireless terminal 30 the radio bearer handling operations 15-11 may be executed or performed, at least in part, by a UE MAC entity. Act 15-12 comprises performing a MAC-based DRB/SRB add/modify operation. The MAC-based DRB/SRB add/modify operation 15-12 may result in one or more data radio bearer(s) and one or more signaling radio bearer(s) being added, e.g., set up, between distributed processor circuitry site 42₁ and wireless terminal 30. As act 15-12, the wireless terminal 30 may perform the procedures to establish new Data Radio Bearer (DRB) or new Signaling Bearer (SRB), and/or Add or Modify existing DRBs and/or SRBs using MAC signaling, or using normal backward compatible RRC signaling with the RRC at the CU. As a result of the signaling of act 15-12 signaling, wireless terminal 30 has a full CP/UP connection with the distributed processor circuitry site 42₁ as shown by solid line arrow of act 15-13, in contrast to the broken arrow of act 15-9.

Other radio bearer handling operations may also be performed, as needed, in the operations of act 15-11. Act 15-14shows that the wireless terminal 30 may perform DRB/SRB release procedures where one or more DRB/SRB are removed. As act 15-15 the wireless terminal 30 may perform DRB resume procedures for any suspended DRBs. As act 15-16 the wireless terminal 30 may perform Reconfiguration procedures as in the prior art but using MAC based commands on the uplink and downlink instead of RRC signaling. As act 15-17 the wireless terminal 30 may also perform optional subsequent procedures/activities. Traditional RRC signaling can also be used for one or more of the operations of act 15-11 and the distributed processor circuitry site should be able to recognize the message format and forward these toward the anchor processor circuitry 40.

Fig. 16 shows example, representative, non-limiting acts or steps in an example embodiment and mode in which distributed processor circuitry site is configured to handle data radio bearers and signaling radio bearers for a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the anchor processor circuitry makes a handover decision affecting the connection. At the start of the scenario shown in Fig. 16, UE-1 also known as wireless terminal 30 is involved in a connection. As such, the UE-1 is in connected mode, as indicated by act 16-1; a context shown in Fig. 16 as UE-1 context has been established at distributed processor circuitry site 42₁ for UE-1, as indicated by act 16-2; and the UE-1 context and tunnel endpoint identifiers for the connection involving UE-1 are known to anchor processor circuitry 40, as indicated by act 16-3. Moreover, control plane connectivity and user plane connectivity exists between anchor processor circuitry 40 and distributed processor circuitry site 42₁, as depicted by act/arrow 16-4; and control plane connectivity and user plane connectivity exists between distributed processor circuitry site 42₁ and wireless terminal 30, as depicted by act/arrow 16-5.

As act 16-6 the anchor processor circuitry 40 makes a determination that the connection involving wireless terminal 30, e.g., UE-1, should be handed over from distributed processor circuitry site 42₁ to distributed processor circuitry site 42₂. After the handover determination of act 16-6, as act 16-7 the anchor processor circuitry 40 determines or obtains a tunnel endpoint identifier for distributed processor circuitry site 42₂. Thereafter, as act 16-8, the anchor processor circuitry 40 sends to distributed processor circuitry site 42₂ a message or signal which includes information so that distributed processor circuitry site 42₂ may acquire or construct a context for UE-1, e.g., a context essentially identical to that already existing at distributed processor circuitry site 42₁ (as was indicated by act 16-2). Act 16-9 shows the distributed processor circuitry site 42₂ as having used the context information to construct or establish the context for UE-1.

As act 16-10 the anchor processor circuitry 40 sends a handover command to wireless terminal 30 (via distributed processor circuitry site 42₁) as well as other information including an identifier of the target site for the handover, e.g., distributed processor circuitry site 42₂, also known as DU-2; the tunnel endpoint identifier UE-1 DU-2 TEID; and the DU-2 encryption keys. This other information is preferably included in the handover command, but may instead be included in another command, message, or signal. Act 16-11 shows the wireless terminal 30 as updating its context, e.g., UE-1 context, to now include the DU-2 keys, CU-keys, the UE-1 CU TEID, and the UE-1 DU-2 TEID. At this point wireless terminal 30 knows the tunnel end point identifiers and encryption keys as well as the identifier for the target site for the handover.

Act 16-12 reflects the fact that both control plane connectivity and user plane connectivity, e.g., CP/UP connectivity, has been established between anchor processor circuitry 40 and distributed processor circuitry site 42₂. Thus, as in the example embodiment and mode of Fig. 15, both user plane connection and control plane connection are established between the distributed processor circuitry site 42₁, e.g., DU, and anchor processor circuitry 40, e.g., CU, with the user plane connectivity being established even before the UE sends or receives User Plane data.

With the context also having been updated for wireless terminal 30 at act 16-11, control plane connectivity and user plane connectivity also exists between wireless terminal 30 and distributed processor circuitry site 42₂ as shown by act 16-13. The wireless terminal 30 may then transition into connected mode as shown by act 16-14. With the connectivity having been established, MAC-based handover signaling is exchanged between wireless terminal 30 and distributed processor circuitry site 42₂, as indicated by act 16-15. One or more data radio bearer(s) and one or more signaling radio bearer(s) are set up, e.g., by radio bearer handler 80, for the handed over connection, and wireless terminal 30 uses the DU-2 TEID for communicating through distributed processor circuitry site 42₂ to anchor processor circuitry 40.

Act 16-16 of Fig. 16 illustrates example operations including radio bearer handling operations which may occur between distributed processor circuitry site 42₂ and wireless terminal 30. The operations of act 16-16 include optional alternative procedures that wireless terminal 30 may perform after the handover is completed. At the distributed processor circuitry site 42₂ the radio bearer handling operations 16-16 may be executed or performed by radio bearer handler 80; at the wireless terminal 30 the radio bearer handling operations 16-16 may be executed or performed, at least in part, by a UE MAC entity. Act 16-17 comprises performing a MAC-based DRB/SRB release operation so that the wireless terminal 30 may release the DRBs/SRBs that are established during handover. Act 16-18 shows that the wireless terminal 30 may perform a MAC-based DRB resume operation to resume any suspended DRBs or modify existing ones. Act 16-19 comprises performing a MAC-based DRB/SRB add or modify operation. Act 16-20 comprises performing a MAC-based reconfiguration, which can take place either by wireless terminal 30 or distributed processor circuitry site 42₁. Although not shown in Fig. 16, the wireless terminal 30 may also perform optional subsequent procedures/activities as described above with reference to Fig. 15. Traditional RRC signaling can also be used for one or more of the operations of act 16-16 and the distributed processor circuitry site should be able to recognize the message format and forward these toward the anchor processor circuitry 40.

Fig. 17 shows example, representative, non-limiting acts or steps in an example embodiment and mode in which distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the distributed processor circuitry makes a handover decision affecting the connection. At the start of the scenario shown in Fig. 17, UE-1 also known as wireless terminal 30, is involved in a connection. As such, the UE-1 is in connected mode, as indicated by act 17-1; a context shown in Fig. 17 as UE-1 context has been established at distributed processor circuitry site 42₁ for UE-1, as indicated by act 17-2; and the UE-1 context and tunnel endpoint identifiers for the connection involving UE-1 are known to anchor processor circuitry 40, as indicated by act 17-3. Moreover, control plane connectivity and user plane connectivity exists between anchor processor circuitry 40 and distributed processor circuitry site 42₁, as depicted by act/arrow 17-4; and control plane connectivity and user plane connectivity exists between distributed processor circuitry site 42₁ and wireless terminal 30, as depicted by act/arrow 17-5.

As act 17-6 the distributed processor circuitry site 42₁ makes a determination that the connection involving wireless terminal 30, e.g., UE-1, should be handed over from distributed processor circuitry site 42₁ to a target site, e.g., distributed processor circuitry site 42₂. After the handover determination of act 17-6, as act 17-7 the anchor processor circuitry 40 determines or obtains a tunnel endpoint identifier for distributed processor circuitry site 42₂. Thereafter, as act 17-8, the distributed processor circuitry site 42₁ sends to target distributed processor circuitry site 42₂ a message or signal which includes information so that distributed processor circuitry site 42₂ may acquire or construct a context for UE-1, e.g., a context essentially identical to that already existing at distributed processor circuitry site 42₁ (as was indicated by act 17-2). Act 17-9 shows the distributed processor circuitry site 42₂ as having used the context information to construct or establish the context for UE-1.

As act 17-10 the distributed processor circuitry site 42₁ sends a message or signal to anchor processor circuitry 40 to apprise anchor processor circuitry 40 of the impending handover, and particularly to enable anchor processor circuitry 40 to update the context maintained at anchor processor circuitry 40 for UE-1. The context for UE-1 needs updating at anchor processor circuitry 40 in view of, e.g., the tunnel endpoint identifier DU-2 TEID to be used for the tunnel which will connect distributed processor circuitry site 42₂ and anchor processor circuitry 40.

As act 17-11 the distributed processor circuitry site 42₁ sends a handover command to wireless terminal 30 as well as other information including an identifier of the target site for the handover, e.g., distributed processor circuitry site 42₂, also known as DU-2; the tunnel endpoint identifier UE-1 DU-2 TEID; and the DU-2 encryption keys. This other information is preferably included in the handover command, but may instead be included in another command, message, or signal. Act 17-12 shows the wireless terminal 30 as updating its context, e.g., UE-1 context, to now include, e.g., the DU-2 keys, CU-keys, the UE-1 CU TEID, and the UE-1 DU-2 TEID. At this point wireless terminal 30 knows the tunnel end point identifiers and encryption keys as well as the identifier for the target site for the handover.

Act 17-13 reflects the fact that both control plane connectivity and user plane connectivity, e.g., CP/UP connectivity, have been established between anchor processor circuitry 40 and distributed processor circuitry site 42₂. Thus, as in the example embodiment and mode of Fig. 15, both user plane connection and control plane connection are established between the distributed processor circuitry site 42₁, e.g., DU, and anchor processor circuitry 40, e.g., CU, with the user plane connectivity being established even before the UE sends or receives User Plane data.

Act 17-14 depicts a handover of the connection involving UE-1 from distributed processor circuitry site 42₁ to distributed processor circuitry site 42₂. The handover act 17-14 comprises setting up one or more signaling radio bearer(s) and one or more data radio bearer(s) between wireless terminal 30 and distributed processor circuitry site 42₂, as well as wireless terminal 30 using the tunnel endpoint identifier DU-2 TEID for the tunnel between distributed processor circuitry site 42₂ and anchor processor circuitry 40. The radio bearer handler 80 of distributed processor circuitry site 42₂ and the MAC entity of wireless terminal 30 may be involved in setting up the signaling radio bearer(s) and data radio bearer(s). It should be realized that, in various example embodiments and modes described herein, the MAC entity of wireless terminal 30 mat be involved when data radio bearer(s) or signaling radio bearer(s) are set up for wireless terminal 30 to any distributed processor circuitry site or any portion of distributed processor circuitry 42.

As a result of the handover of act 17-14, the wireless terminal 30 may be in or transition to the connected mode as shown by act 17-15. Moreover, control plane connectivity and user plane connectivity also exists between wireless terminal 30 and distributed processor circuitry site 42₂ as shown by act 17-13. The wireless terminal 30 may then transition into connected mode as shown by act 17-16.

Act 17-17 of Fig. 17 illustrates example operations including example radio bearer handling operations which may occur between distributed processor circuitry site 42₂ and wireless terminal 30. At the distributed processor circuitry site 42₂ the radio bearer handling operations 17-17 may be executed or performed by radio bearer handler 80; at the wireless terminal 30 the radio bearer handling operations of act 17-17 may be performed by a UE MAC entity. Act 17-18 comprises performing a MAC-based DRB/SRB release operation so that the wireless terminal 30 may release the DRBs/SRBs that are established during handover. Act 17-19 shows that the wireless terminal 30 may perform a MAC-based DRB resume operation to resume any suspended DRBs or modify existing ones. Act 17-20 comprises performing a MAC-based DRB/SRB add or modify operation. Act 17-21 comprises performing a MAC-based reconfiguration, which can take place either by wireless terminal 30 or distributed processor circuitry site 42₁. Although not shown in Fig. 17, the wireless terminal 30 may also perform optional subsequent procedures/activities as described above with reference to Fig. 15. Traditional RRC signaling can also be used for one or more of the operations of act 17-17 and the distributed processor circuitry site should be able to recognize the message format and forward these toward the anchor processor circuitry 40.

Fig. 18 shows example, representative, non-limiting acts or steps in an example embodiment and mode in which distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the wireless terminal circuitry makes a handover decision affecting the connection.

At the start of the scenario shown in Fig. 18, UE-1 also known as wireless terminal 30, is involved in a connection. As such, the UE-1 is in connected mode, as indicated by act 18-1; a context shown in Fig. 18 as UE-1 context has been established at distributed processor circuitry site 42₁ for UE-1, as indicated by act 18-2; and the UE-1 context and tunnel endpoint identifiers for the connection involving UE-1 are known to anchor processor circuitry 40, as indicated by act 18-3. Moreover, control plane connectivity and user plane connectivity exists between anchor processor circuitry 40 and distributed processor circuitry site 42₁, as depicted by act/arrow 18-4; and control plane connectivity and user plane connectivity exists between distributed processor circuitry site 42₁ and wireless terminal 30, as depicted by act/arrow 18-5.

As act 18-6 the wireless terminal 30 makes a determination that the connection involving wireless terminal 30, e.g., UE-1, should be handed over from distributed processor circuitry site 42₁ to a target site, e.g., distributed processor circuitry site 42₂. After the handover determination of act 18-6, as act 18-7 a MAC-based handover is performed between wireless terminal 30 and distributed processor circuitry site 42₂. In conjunction with the MAC-based handover the MAC entities of wireless terminal 30 and distributed processor circuitry site 42₂ communicate with one another as the radio bearer handler 80 of distributed processor circuitry site 42₂ allocates one or more signaling radio bearer(s) and one or more data radio bearer(s) for the handed-over connection. Moreover, as act 18-8 the wireless terminal 30 supplies the distributed processor circuitry site 42₂ with information concerning the UE-1 context, and encryption information, and a tunnel endpoint identifier DU-2 TEID to be used for a tunnel between distributed processor circuitry site 42₂ and anchor processor circuitry 40. Act 18-9 shows the distributed processor circuitry site 42₂ as having used the context information to construct or establish the context for UE-1 at distributed processor circuitry site 42₂.

Since a handover of the connection was performed as act 18-7, as act 18-10 a MAC-based DRB/SRB release is performed to release the one or more signaling radio bearer(s) and one or more data radio bearer(s) that may been existed between distributed processor circuitry site 42₁ and wireless terminal 30. Moreover, in view of the handover having occurred and the tunnel endpoint identifiers known, as act 18-11 the distributed processor circuitry site 42₂ provides anchor processor circuitry 40 with information to update the context for UE-1, e.g., to update UE-1 context, such information including the DU-2 TEID. Act 18-12 reflects that anchor processor circuitry 40 updates the context for UE-1, the updated UE-1 context including the DU-2 TEIDs.

In addition, as act 18-13 the distributed processor circuitry site 42₂ provides wireless terminal 30 with information so that the wireless terminal 30 can update its context, such updating information now enabling the UE-1 context as maintained by wireless terminal 30 to include identifiers of one or more signaling radio bearer(s) and one or more data radio bearer(s) set up at act 18-7, the tunnel endpoint identifier DU-2 TEID, and the DU-2 keys for encryption. Act 18-14 shows the wireless terminal 30 as updating its context, e.g., UE-1 context, to now include, e.g., the DU-2 keys, CU-keys, the UE-1 CU TEID, and the UE-1 DU-2 TEID. At this point wireless terminal 30 knows the tunnel end point identifiers and encryption keys as well as the identifier for the target site for the handover.

Act 18-15 reflects the fact that both control plane connectivity and user plane connectivity, e.g., CP/UP connectivity, have been established between anchor processor circuitry 40 and distributed processor circuitry site 42₂. Thus, as in the example embodiment and mode of Fig. 15, both user plane connection and control plane connection are established between the distributed processor circuitry site 42₂, e.g., DU, and anchor processor circuitry 40, e.g., CU, with the user plane connectivity being established even before the UE sends or receives User Plane data. Act 18-16 reflects the fact that both control plane connectivity and user plane connectivity, e.g., CP/UP connectivity, have been established between distributed processor circuitry site 42₂ and wireless terminal 30.

Act 18-17 of Fig. 18 illustrates example operations including example radio bearer handling operations which may occur between distributed processor circuitry site 42₂ and wireless terminal 30. At the distributed processor circuitry site 42₂ the radio bearer handling operations 18-17 may be executed or performed by radio bearer handler 80; at the wireless terminal 30 the radio bearer handling operations of act 17-17 may be performed by a UE MAC entity. Act 18-18 comprises performing a MAC-based DRB/SRB release operation. Act 18-19 comprises performing a MAC-based DRB resume operation. Act 18-20 comprises performing a MAC-based DRB/SRB add or modify operation. Act 18-21 comprises performing a MAC-based reconfiguration. Although not shown in Fig. 18, the wireless terminal 30 may also perform optional subsequent procedures/activities as described above with reference to Fig. 15. Traditional RRC signaling can also be used for one or more of the operations of act 18-17 and the distributed processor circuitry site should be able to recognize the message format and forward these toward the anchor processor circuitry 40
Fig. 19 shows example, representative, non-limiting acts or steps in an example embodiment and mode in which distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover operation or a cell reselection operation when the wireless terminal is not operating in a connected mode and in a situation in which the wireless terminal circuitry makes a handover decision or a cell reselection decision. At the start of the scenario shown in Fig. 19, UE-1 also known as wireless terminal 30, is not involved in a connection, but is in idle mode or inactive as shown by act 19-1. Although UE-1 is not in connected mode, yet a context does exist for UE-1 at both distributed processor circuitry site 42₁ and anchor processor circuitry 40, as indicated by act 19-2 and act 19-3, respectively. Moreover, as indicated by act 19-3, tunnel endpoint identifiers for the connection involving UE-1 are known to anchor processor circuitry 40. The tunnel endpoint identifiers, TEIDs, for UE-1 in 19-3 are related to DU-1 and to the CP/UP connectivity that is to be established as act 19-4. The UE is in an active state waiting for something to happen, e.g., a cell re-selection as may occur as act 19-6. Act/arrow 19-4 depicts control plane connectivity and user plane connectivity being established between anchor processor circuitry 40 and distributed processor circuitry site 42_.Control plane connectivity and user plane connectivity is established between distributed processor circuitry site 42₁ and wireless terminal 30, as depicted by act/arrow 19-5.

As act 19-6 the wireless terminal 30 makes a determination that the connection involving wireless terminal 30, e.g., UE-1. The determination of act 19-6 may be either a handover decision, or a cell reselection decision. A cell reselection decision is a decision that the idle mode UE-1 should now be served by another cell rather than the currently serving cell. In the example scenario of Fig. 19, act 19-6 may involve a decision that UE-1should be served by the cell of distributed processor circuitry site 42₂ rather than the current cell of distributed processor circuitry site 42₁. In other words, the cell reselection decision of act 19-6 is that the target site/cell for UE-1 should be distributed processor circuitry site 42₂.

In view of the handover/reselection decision of act 19-6, as act 19-7 a MAC-based handover is performed between wireless terminal 30 and distributed processor circuitry site 42₂. In conjunction with the MAC-based handover the MAC entities of wireless terminal 30 and distributed processor circuitry site 42₂ communicate with one another as the radio bearer handler 80 of distributed processor circuitry site 42₂ allocates one or more signaling radio bearer(s) and one or more data radio bearer(s) for UE-1. The signaling radio bearer(s) is added to establish the CP connectivity with the target DU (DU-2) in act 19-7 in case the UE does not have anything running, e.g., no data radio bearers, e.g., no DRBs. Alternatively, if there are DRBs which are suspended before the HO/re-selection, then the new DRB may be established to resume.

As act 19-8 the wireless terminal 30 supplies the distributed processor circuitry site 42₂ with information concerning the UE-1 context, encryption information, and a tunnel endpoint identifier DU-2 TEID to be used for a tunnel between distributed processor circuitry site 42₂ and anchor processor circuitry 40. Act 19-9 shows the distributed processor circuitry site 42₂ as having used the context information to construct or establish the context for UE-1 at distributed processor circuitry site 42₂. Thus, distributed processor circuitry site 42₂ does not have to negotiate or create from scratch the UE-1 context, but may easily use the context information acquired from distributed processor circuitry site 42₁.

As act 19-10 distributed processor circuitry site 42₂ supplies anchor processor circuitry 40 with information with which anchor processor circuitry 40 may update its context for UE-1. The updating information may include the tunnel endpoint identifier DU-2 TEID for UE-1. Act 19-11 reflects that anchor processor circuitry 40 updates the context for UE-1, the updated UE-1 context including the DU-2 TEIDs.

In addition, as act 19-12 the distributed processor circuitry site 42₂ provides wireless terminal 30 with information so that the wireless terminal 30 can update its context. The updating information of act 19-12 enables the UE-1 context as maintained by wireless terminal 30 to include identifiers of one or more signaling radio bearer(s) and one or more data radio bearer(s) set up at act 19-7, the tunnel endpoint identifier DU-2 TEID, and the DU-2 keys for encryption. Act 19-13 shows the wireless terminal 30 as updating its context, e.g., UE-1 context, to now include, e.g., the DU-2 keys, CU-keys, the UE-1 CU TEID, and the UE-1 DU-2 TEID. At this point wireless terminal 30 knows the tunnel end point identifiers and encryption keys as well as the identifier for the target site for the handover.

Act 19-14 reflects the fact that both control plane connectivity and user plane connectivity, e.g., CP/UP connectivity, have been established between anchor processor circuitry 40 and distributed processor circuitry site 42₂. Thus, as in the example embodiment and mode of Fig. 15, both user plane connection and control plane connection are established between the distributed processor circuitry site 42₁, e.g., DU, and anchor processor circuitry 40, e.g., CU, with the user plane connectivity being established even before the UE sends or receives User Plane data. Act 19-15 reflects the fact that both control plane connectivity and user plane connectivity, e.g., CP/UP connectivity, have been established between distributed processor circuitry site 42₂ and wireless terminal 30.

Act 19-16 of Fig. 19 illustrates example operations including example radio bearer handling operations which may occur between distributed processor circuitry site 42₂ and wireless terminal 30. At the distributed processor circuitry site 42₂ the radio bearer handling operations 19-16 may be executed or performed by radio bearer handler 80; at the wireless terminal 30 the radio bearer handling operations of act 17-17 may be performed by a UE MAC entity. Act 19-19 comprises performing a MAC-based DRB/SRB add operation. Act 19-18 comprises performing a MAC-based DRB resume operation. Act 19-19 comprises performing a MAC-based DRB/SRB release operation. Act 19-20 comprises performing a MAC-based reconfiguration. Although not shown in Fig. 19, the wireless terminal 30 may also perform optional subsequent procedures/activities as described above with reference to Fig. 15. Traditional RRC signaling can also be used for one or more of the operations of act 19-16 and the distributed processor circuitry site should be able to recognize the message format and forward these toward the anchor processor circuitry 40.

Fig. 20 shows example, representative, non-limiting acts or steps in an example embodiment and mode in which distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a routing or area update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site. As used herein, an “area update” may be a routing area update, a tracking area update, or a radio access network area update. At the start of the scenario shown in Fig. 20, UE-1 also known as wireless terminal 30, is not involved in a connection, but is in idle mode or inactive as shown by act 20-1. Although UE-1 is not in connected mode, yet a context does exist for UE-1 at both distributed processor circuitry site 42₁ and anchor processor circuitry 40, as indicated by act 20-2 and act 20-3, respectively. Moreover, as indicated by act 20-3, tunnel endpoint identifiers for the connection involving UE-1 are known to anchor processor circuitry 40.

Control plane connectivity and user plane connectivity exists between anchor processor circuitry 40 and distributed processor circuitry site 42₁, as depicted by act/arrow 20-4. In other words, wireless terminal 30 has a connection between anchor processor circuitry 40 and distributed processor circuitry site 42₁ set up for both the control plane, CP for SRB based control traffic, and the user plane UP for user data traffic (DRBs). The connection between the wireless terminal 30 and distributed processor circuitry site 42₁ may have control plane CP connectivity where it can receive notifications and other SRB activities; and the UP connectivity (i.e., DRB) is established in a dynamic fashion, e.g., switches between ON and OFF as needed.

As act 20-5 the wireless terminal 30, currently in a cell served by distributed processor circuitry site 42₁, detects a new distributed processor circuitry site, e.g., distributed processor circuitry site 42_N. In view of the detection of the new site, an area update procedure may be performed as described in the remainder of Fig. 20. As mentioned above, an “area update” may be a routing area update, a tracking area update, or a radio access network area update. In connection with the area update procedure of Fig. 20, as act 20-6 random access procedures are performed between wireless terminal 30 and the newly detected site, e.g., distributed processor circuitry site 42_N. In conjunction with the random access procedures of act 20-6, as act 20-7 the wireless terminal 30 supplies the distributed processor circuitry site 42_N with information concerning the UE-1 context, an identifier for the currently serving distributed processor circuitry site 42₁, an identifier for anchor processor circuitry 40, encryption information, and tunnel endpoint identifiers DU-1 TEID and CU-TEID. Act 20-8 shows the distributed processor circuitry site 42_N as using the context information to construct or establish the context for UE-1 at distributed processor circuitry site 42_N. Thus, distributed processor circuitry site 42_N does not have to negotiate or create from scratch the UE-1 context, but may easily use the context information acquired from distributed processor circuitry site 42₁.

As act 20-9 distributed processor circuitry site 42_N supplies anchor processor circuitry 40 with information with which anchor processor circuitry 40 may update its context for UE-1. The updating information may include the tunnel endpoint identifier DU-N TEID for UE-1. Act 20-10 reflects that anchor processor circuitry 40 updates the context for UE-1, the upated UE-1 context including the DU-N TEIDs.

In addition, as act 20-11 the distributed processor circuitry site 42_N provides wireless terminal 30 with information so that the wireless terminal 30 can update its context. The updating information of act 20-11 enables the UE-1 context as maintained by wireless terminal 30 to include identifiers of one or more signaling radio bearer(s), the tunnel endpoint identifiers DU-N TEID, and the DU-N key for encryption. The signaling radio bearer (SRB) is needed to obtain information from distributed processor circuitry site 42_1.Act 20-12 shows the wireless terminal 30 as updating its context, e.g., UE-1 context, to now include, e.g., DU-N keys for encryption; the tunnel endpoint identifier UE-1 CU TEID, e.g., the tunnel endpoint identifier for UE-1 at CU/anchor processor circuitry 40, and the tunnel endpoint identifier UE-1 DU-N TEID, e.g., the tunnel endpoint identifier for UE-1 at DU-N/distributed processor circuitry site 42_N. At this point wireless terminal 30 knows the tunnel end point identifiers and encryption keys as well as the identifier for the detected site, e.g., distributed processor circuitry site 42_N.

Act 20-13 reflects the fact that both control plane connectivity and user plane connectivity, e.g., CP/UP connectivity, have been established between anchor processor circuitry 40 and distributed processor circuitry site 42_N. Thus, as in the example embodiment and mode of Fig. 15, both user plane connection and control plane connection are established between the distributed processor circuitry site 42₁, e.g., DU, and anchor processor circuitry 40, e.g., CU, with the user plane connectivity being established even before the UE sends or receives User Plane data. Act 20-14 reflects the fact that both control plane connectivity and user plane connectivity, e.g., CP/UP connectivity, have been established between distributed processor circuitry site 42_N and wireless terminal 30.

Act 20-15 of Fig. 20 illustrates example operations including radio bearer handling operations which may occur between distributed processor circuitry site 42_N and wireless terminal 30. At the distributed processor circuitry site 42_N the radio bearer handling operations 20-15 may be executed or performed by radio bearer handler 80; at the wireless terminal 30 the radio bearer handling operations of act 17-17 may be performed by a UE MAC entity. Act 20-16 comprises performing a MAC-based DRB/SRB add operation. Act 20-17 comprises performing a MAC-based DRB resume operation. Act 20-18 comprises performing a MAC-based DRB/SRB release operation. Act 20-19 comprises performing a MAC-based reconfiguration. Although not shown in Fig. 20, the wireless terminal 30 may also performed optional subsequent procedures/activities as described above with reference to Fig. 15. Traditional RRC signaling can also be used for one or more of the operations of act 20-15 and the distributed processor circuitry site should be able to recognize the message format and forward these toward the anchor processor circuitry 40
Fig. 21 shows example, representative, non-limiting acts or steps in a first example scenario in which distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a context update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.

At the start of the scenario shown in Fig. 21, UE-1 also known as wireless terminal 30, is not involved in a connection, but is in idle mode or inactive as shown by act 21-1. Although UE-1 is not in connected mode, yet a context does exist for UE-1 at both distributed processor circuitry site 42₁ and anchor processor circuitry 40, as indicated by act 21-2 and act 21-3, respectively. Moreover, as indicated by act 21-3, tunnel endpoint identifiers for the connection involving UE-1 are known to anchor processor circuitry 40. Moreover, control plane connectivity and user plane connectivity exists between anchor processor circuitry 40 and distributed processor circuitry site 42₁, as depicted by act/arrow 21-4; control plane connectivity and user plane connectivity may exist between distributed processor circuitry site 42₁ and wireless terminal 30, as depicted by act/arrow 21-5. Since the wireless terminal 30 is in idle mode, connectivity between wireless terminal 30 and distributed processor circuitry site 42₁ is only control plane connectivity, for which reason the arrow of act 21-5 is shown with a broken line.

As act 21-6 the wireless terminal 30, currently in a cell served by distributed processor circuitry site 42₁, detects a new distributed processor circuitry site, e.g., distributed processor circuitry site 42_N. In view of the detection of the new site, a context update procedure may be performed as described in the remainder of Fig. 21. In connection with the context update procedure of Fig. 21, as act 21-7 random access procedures are performed between wireless terminal 30 and the newly detected site, e.g., distributed processor circuitry site 42_N. In conjunction with the random access procedures of act 21-7, as act 21-8 the wireless terminal 30 supplies the distributed processor circuitry site 42_N with information concerning the UE-1 context, an identifier for the currently serving distributed processor circuitry site 42₁, an identifier for anchor processor circuitry 40, encryption information, and tunnel endpoint identifiers DU-1 TEID and CU-TEID. Act 21-9 shows the distributed processor circuitry site 42_N as using the context information to construct or establish the context for UE-1 at distributed processor circuitry site 42_N. Thus, distributed processor circuitry site 42_N does not have to negotiate or create from scratch the UE-1 context, but may easily use the context information acquired from distributed processor circuitry site 42₁. In addition, act 21-9 comprises creating a tunnel endpoint identifier DU-N TEID for distributed processor circuitry site 42_N, as well as establishing a tunnel between distributed processor circuitry site 42_N and anchor processor circuitry 40. The endpoint identifiers for the endpoints of the tunnel of Fig. 21 are DU-N TEID and CU-N TEID.

As act 21-10 distributed processor circuitry site 42_Nretrieves the UE-1 context from distributed processor circuitry site 42₁. As act 21-11 distributed processor circuitry site 42_N supplies anchor processor circuitry 40 with information with which anchor processor circuitry 40 may update its context for UE-1. The updating information may include the tunnel endpoint identifier DU-N TEID for UE-1. Act 21-12 reflects that anchor processor circuitry 40 updates the context for UE-1, the updated UE-1 context including the DU-N TEIDs.

In addition, as act 21-13 the distributed processor circuitry site 42_N provides wireless terminal 30 with information so that the wireless terminal 30 can update its context. The updating information of act 21-13 enables the UE-1 context as maintained by wireless terminal 30 to include identifiers of one or more signaling radio bearer(s), the tunnel endpoint identifiers CU TEID, and the DU-N key for encryption. The signaling radio bearer(s) (SRB) and the context in the wireless terminal 30 were established at act 21-8. Act 21-14 shows the wireless terminal 30 as updating its context, e.g., UE-1 context, to now include, e.g., DU-N and CU keys for encryption; the tunnel endpoint identifier UE-1 CU TEID, e.g., the tunnel endpoint identifier for UE-1 at CU/anchor processor circuitry 40, and the tunnel endpoint identifier UE-1 DU-N TEID, e.g., the tunnel endpoint identifier for UE-1 at DU-N/distributed processor circuitry site 42_N. At this point wireless terminal 30 knows the tunnel end point identifiers and encryption keys as well as the identifier for the detected site, e.g., distributed processor circuitry site 42_N.

Act 21-15 reflects the fact that both control plane connectivity and user plane connectivity, e.g., CP/UP connectivity, have been established between anchor processor circuitry 40 and distributed processor circuitry site 42_N. Thus, as in the example embodiment and mode of Fig. 15, both user plane connection and control plane connection are established between the distributed processor circuitry site 42₁, e.g., DU, and anchor processor circuitry 40, e.g., CU, with the user plane connectivity being established even before the UE sends or receives User Plane data.

Act 21-16 comprises a release of distributed processor circuitry site 42₁, e.g., that distributed processor circuitry site 42₁ is no longer responsible for wireless terminal 30. Act 21-17 reflects the fact that both control plane connectivity and user plane connectivity, e.g., CP/UP connectivity, have been established between distributed processor circuitry site 42_N and wireless terminal 30.

Fig. 21 thus reflects a first non-limiting, example technique or option for performing a context update procedure wherein UE-1 context retrieval may occur between distributed processor circuitry sites, e.g., between distributed processor circuitry site 42₁ and distributed processor circuitry site 42_N. A second non-limiting, example technique or option for performing a context update procedure is described with reference to Fig. 22. In the example embodiment and mode of Fig. 22 the distributed processor circuitry site 42₁ and distributed processor circuitry site 42_N do not have direct interaction as in the Fig. 1 example embodiment and mode. Rather, in the Fig. 22 example embodiment and mode distributed processor circuitry site 42_N obtains the UE-1 context from anchor processor circuitry 40, the anchor processor circuitry 40 having obtained the UE-1 context from distributed processor circuitry site 42₁. Fig. 22 differs from Fig. 21 by replacing acts 21-10 and 21-11 with acts 22-1 through 22-3. Act 22-1 comprises distributed processor circuitry site 42_N providing a tunnel endpoint identifier DU-N TEID to anchor processor circuitry 40. Act 22-2 comprises the anchor processor circuitry 40 obtaining a UE-1 context from distributed processor circuitry site 42₁. Act 22-3 comprises the anchor processor circuitry 40 providing an updated UE-1 connect to distributed processor circuitry site 42_N, the updated UD-1 context including the DU-N TEID.

The foregoing discussion of the operations and procedures of each of Fig. 15 - Fig. 22 includes description particularly regarding the MAC-based operations involved in handling radio bearers, e.g., data radio bearer(s) and signaling radio bearer(s). Such MAC-based operations include adding, setting up, modifying, and releasing MAC-based radio bearers. However, it should be understood that the entities shown in Fig. 15 - Fig. 22 may also perform other activities and perform in accordance with activities described herein other than radio bearer handling.

It was mentioned above in conjunction with each of the example embodiments and modes of Fig. 15 - Fig. 22 that both user plane connection and control plane connection may be established between the distributed processor circuitry site 42₁, e.g., DU, and anchor processor circuitry 40, e.g., CU, with the user plane connectivity being established even before the UE sends or receives User Plane data. It should be understood that such early setup of user plane connectivity may occur also in an example embodiment and mode in which the radio access network is not segmented into anchor processor circuitry and one or more distributed processor circuitry sites 42. For example, Fig. 23 illustrates an example embodiment and mode wherein the radio access network 24 comprises one or more RAN node(s) 90. The node(s) 90 of Fig. 23 is shown generically as not split into anchor processor circuitry 40 and distributed processor circuitry 42, although node(s) 90 may be so split in the manner of Fig. 5, for example. The node(s) 90 comprise RAN processing circuitry 92, which in turn may comprise or include connectivity controller 94. The RAN processing circuitry 92, and connectivity controller 94 in particular, may establish, for a wireless terminal, both user plane connection and control plane connection prior to the wireless terminal sending or receiving user plane data, in a manner as understood with reference to the foregoing example embodiments and modes of Fig. 15 - Fig. 22. The node(s) 90 further comprises transceiver circuitry 44₂₃configured to communicate with the wireless terminal over a radio interface.

The technology disclosed herein advantageously reduces signaling and expedites session establishment, re-establishment, resume, and ON-OFF operations. For example, upon handover from one distributed processor circuitry site to another, the procedures performed at the anchor processor circuitry 40 may remain essentially the same, resulting in significant savings and efficiency.

Among its various embodiments and modes, the technology disclosed herein includes one or more of the following features and/or benefits, which may be achieved either alone or in combination:

Network Function Virtualization (NFV) may be further described by one or more of the following (all of which are incorporated herein by reference in their entirety):

Certain units and functionalities of radio access network 24 may be implemented by electronic machinery. For example, electronic machinery may refer to the processor circuitry described herein, such as anchor processor circuitry 40 and distributed processor circuitry 42, and RAN processing circuitry 92. Moreover, the term “processor circuitry” is not limited to mean one processor, but may include plural processors, with the plural processors operating at one or more sites. Moreover, as used herein the term “server”, as in plural anchor processor circuitry servers 40_,is not confined to one server unit, but may encompasses plural servers and/or other electronic equipment, and may be co-located at one site or distributed to different sites. With these understandings, Fig. 24 shows an example of electronic machinery, e.g., processor circuitry, as comprising one or more processors 190, program instruction memory 192; other memory 194 (e.g., RAM, cache, etc.); input/

output interfaces

196 and 197, peripheral interfaces 198; support circuits 199; and busses 200 for communication between the aforementioned units. The processor(s) 190 may comprise the processor circuitries described herein, for example, the anchor processor circuitry 40 and distributed processor circuitry 42 distributed processor circuitry 42.

The memory 194, or computer-readable medium, may be one or more of readily available memory such as random access memory (RAM), read only memory (ROM), floppy disk, hard disk, flash memory or any other form of digital storage, local or remote, and is preferably of non-volatile nature, as and such may comprise memory 60 shown in Fig. 5. The support circuits 199 are coupled to the processors 190 for supporting the processor in a conventional manner. These circuits include cache, power supplies, clock circuits, input/output circuitry and subsystems, and the like.

Although the processes and methods of the disclosed embodiments may be discussed as being implemented as a software routine, some of the method steps that are disclosed therein may be performed in hardware as well as by a processor running software. As such, the embodiments may be implemented in software as executed upon a computer system, in hardware as an application specific integrated circuit or other type of hardware implementation, or a combination of software and hardware. The software routines of the disclosed embodiments are capable of being executed on any computer operating system, and is capable of being performed using any CPU architecture.

The functions of the various elements including functional blocks, including but not limited to those labeled or described as “computer”, “processor” or “controller”, may be provided through the use of hardware such as circuit hardware and/or hardware capable of executing software in the form of coded instructions stored on computer readable medium. Thus, such functions and illustrated functional blocks are to be understood as being either hardware-implemented and/or computer-implemented, and thus machine-implemented.

In terms of hardware implementation, the functional blocks may include or encompass, without limitation, digital signal processor (DSP) hardware, reduced instruction set processor, hardware (e.g., digital or analog) circuitry including but not limited to application specific integrated circuit(s) [ASIC], and/or field programmable gate array(s) (FPGA(s)), and (where appropriate) state machines capable of performing such functions.

In terms of computer implementation, a computer is generally understood to comprise one or more processors or one or more controllers, and the terms computer and processor and controller may be employed interchangeably herein. When provided by a computer or processor or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by a plurality of individual computers or processors or controllers, some of which may be shared or distributed. Moreover, use of the term “processor” or “controller” may also be construed to refer to other hardware capable of performing such functions and/or executing software, such as the example hardware recited above.

Nodes that communicate using the air interface also have suitable radio communications circuitry. Moreover, the technology disclosed herein may additionally be considered to be embodied entirely within any form of computer-readable memory, such as solid-state memory, magnetic disk, or optical disk containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.

Moreover, each functional block or various features of the wireless terminal 30 and radio access network 24 used in each of the aforementioned embodiments may be implemented or executed by circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.

The technology disclosed herein thus comprises and compasses the following non-exhaustive example embodiments and modes:
Example Embodiment 1: A radio access network comprising:

Example Embodiment 2: The radio access network of Example Embodiment 1, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers for a connection involving the wireless terminal in conjunction with an authentication and registration procedure for the wireless terminal.

Example Embodiment 3: The radio access network of Example Embodiment 1, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers for a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the anchor processor circuitry makes a handover decision affecting the connection.

Example Embodiment 4: The radio access network of Example Embodiment 1, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the distributed processor circuitry makes a handover decision affecting the connection.

Example Embodiment 5: The radio access network of Example Embodiment 1, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the wireless terminal circuitry makes a handover decision affecting the connection.

Example Embodiment 6: The radio access network of Example Embodiment 1, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover operation or a cell reselection operation when the wireless terminal is not operating in a connected mode and in a situation in which the wireless terminal circuitry makes a handover decision or a cell reselection decision.

Example Embodiment 7: The radio access network of Example Embodiment 1, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with an operation when the wireless terminal is not operating in a connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.

Example Embodiment 8: The radio access network of Example Embodiment 7, wherein the distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a routing or area update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.

Example Embodiment 9: The radio access network of Example Embodiment 7, wherein the distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a context update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.

Example Embodiment 10: A method in a radio access network comprising:

Example Embodiment 11: The method of Example Embodiment 10, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers for a connection involving the wireless terminal in conjunction with an authentication and registration procedure for the wireless terminal.

Example Embodiment 12: The method of Example Embodiment 10, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers for a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the anchor processor circuitry makes a handover decision affecting the connection.

Example Embodiment 13: The method of Example Embodiment 10, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the distributed processor circuitry makes a handover decision affecting the connection.

Example Embodiment 14: The method of Example Embodiment 10, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the wireless terminal circuitry makes a handover decision affecting the connection.

Example Embodiment 15: The method of Example Embodiment 10, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover operation or a cell reselection operation when the wireless terminal is not operating in a connected mode and in a situation in which the wireless terminal circuitry makes a handover decision or a cell reselection decision.

Example Embodiment 16: The method of Example Embodiment 10, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with an operation when the wireless terminal is not operating in a connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.

Example Embodiment 17: The method of Example Embodiment 16, wherein the distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a routing or area update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.

Example Embodiment 18: The method of Example Embodiment 16, wherein the distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a context update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.

Example Embodiment 19: A radio access network comprising:

Example Embodiment 20: The radio access network of Example Embodiment 19 , wherein the radio network comprises:

Example Embodiment 21: A method in a radio access network comprising:

It will be appreciated that the technology disclosed herein is directed to solving radio communications-centric issues and is necessarily rooted in computer technology and overcomes problems specifically arising in radio communications. Moreover, the technology disclosed herein improves basic function of a radio access network, e.g., enabling faster and simplified operations such expedited network access.

Although the description above contains many specificities, these should not be construed as limiting the scope of the technology disclosed herein but as merely providing illustrations of some of the presently preferred embodiments of the technology disclosed herein. Thus the scope of the technology disclosed herein should be determined by the appended claims and their legal equivalents. Therefore, it will be appreciated that the scope of the technology disclosed herein fully encompasses other embodiments which may become obvious to those skilled in the art, and that the scope of the technology disclosed herein is accordingly to be limited by nothing other than the appended claims, in which reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more." The above-described embodiments could be combined with one another. All structural, chemical, and functional equivalents to the elements of the above-described preferred embodiment that are known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the present claims. Moreover, it is not necessary for a device or method to address each and every problem sought to be solved by the technology disclosed herein, for it to be encompassed by the present claims. Furthermore, no element, component, or method step in the present disclosure is intended to be dedicated to the public regardless of whether the element, component, or method step is explicitly recited in the claims.

<Cross Reference>
This Nonprovisional application claims priority under 35 U.S.C. § 119 on provisional Application No. 62/748,015 on October 19, 2018, the entire contents of which are hereby incorporated by reference.

Claims

A radio access network comprising:
anchor processor circuitry configured to perform a high layer radio access network node operation;
distributed processor circuitry configured to perform a low layer radio access network node operation including a medium access control (MAC) operation for a wireless terminal served by the radio access network wherein the distributed processor circuitry handles data radio bearers and signaling radio bearers for the wireless terminal.
The radio access network of claim 1, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers for a connection involving the wireless terminal in conjunction with an authentication and registration procedure for the wireless terminal.
The radio access network of claim 1, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers for a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the anchor processor circuitry makes a handover decision affecting the connection.
The radio access network of claim 1, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the distributed processor circuitry makes a handover decision affecting the connection.
The radio access network of claim 1, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the wireless terminal circuitry makes a handover decision affecting the connection.
The radio access network of claim 1, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover operation or a cell reselection operation when the wireless terminal is not operating in a connected mode and in a situation in which the wireless terminal circuitry makes a handover decision or a cell reselection decision.
The radio access network of claim 1, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with an operation when the wireless terminal is not operating in a connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.
The radio access network of claim 7, wherein the distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a routing or area update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.
The radio access network of claim 7, wherein the distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a context update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.
A method in a radio access network comprising:
using anchor processor circuitry to perform high layer radio access network node operations;
using distributed processor circuitry to perform low layer radio access network node operations including handling data radio bearers and signaling radio bearers for a wireless terminal served by the radio access network.
The method of claim 10, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers for a connection involving the wireless terminal in conjunction with an authentication and registration procedure for the wireless terminal.
The method of claim 10, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers for a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the anchor processor circuitry makes a handover decision affecting the connection.
The method of claim 10, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the distributed processor circuitry makes a handover decision affecting the connection.
The method of claim 10, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover of a connection involving the wireless terminal operating in a connected mode and in a situation in which the wireless terminal circuitry makes a handover decision affecting the connection.
The method of claim 10, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with a handover operation or a cell reselection operation when the wireless terminal is not operating in a connected mode and in a situation in which the wireless terminal circuitry makes a handover decision or a cell reselection decision.
The method of claim 10, wherein the distributed processor circuitry is configured to handle data radio bearers and signaling radio bearers in conjunction with an operation when the wireless terminal is not operating in a connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.
The method of claim 16, wherein the distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a routing or area update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.
The method of claim 16, wherein the distributed processor circuitry is configured to handle the data radio bearers and the signaling radio bearers in conjunction with a context update operation when the wireless terminal is not operating in the connected mode and in a situation in which the wireless terminal circuitry detects a new identity for a new distributed processor circuitry site.
A radio access network comprising:
processor circuitry configured to establish, for a wireless terminal, both user plane connection and control plane connection prior to the wireless terminal sending or receiving user plane data;
transceiver circuitry configured to communicate with the wireless terminal over a radio interface.
The radio access network of claim 19, wherein the radio network comprises:
anchor processor circuitry configured to perform a high layer radio access network node operation;
distributed processor circuitry configured to perform a low layer radio access network node operation, and wherein the radio network is configured to establish both the user plane connection and the control plane connection between the anchor processor circuitry and the distributed processor circuitry prior to the wireless terminal sending or receiving user plane data.
A method in a radio access network comprising:
using processor circuitry to establish, for a wireless terminal, both user plane connection and control plane connection prior to the wireless terminal sending or receiving user plane data;
communicating with the wireless terminal over a radio interface.