Architecture for handling multiple networks in a wireless access node device

Abstract

This provides a solution to the challenge of configuring RANs to handle traffic related to different CNs that may belong to different network operators. [Solution] An access node device having a segmented layer function for operating in a wireless access network, comprising: at least two upper layer subnodes (300, 301) configured to implement the upper layer (313) of a wireless protocol stack for individual core network connections (316D); a lower layer subnode (200) shared by the upper layer subnodes (300, 301), comprising a wireless unit (215), implementing a lower layer (213) that supports the upper layer of the at least two upper layer subnodes (300, 301), and configured to communicate lower layer data using the wireless unit (215); and a scheduler (214), wherein one of the upper layer subnodes is a master subnode configured to control the scheduler to manage the allocation of resources for data communication to any of the upper layer subnodes connected to the lower layer subnodes.

Description

Technical Field

[0001] The present disclosure relates to various aspects of a radio access network of a wireless communication network. Specifically, it provides various architectures and functions of an access node device of a radio access network, including different entities or sub-nodes that provide split functions for the access node device.

Background Art

[0002] In various generations of wireless communication systems provided through the 3rd Generation Partnership Project (3GPP (registered trademark)), multiple specifications have been released that define common rules regarding the establishment and operation of the radio interface between a wireless terminal and a base station, as well as the operation at various levels of the wireless network. Generally, a wireless network may be composed of a core network (CN) connected to other networks such as the Internet. To provide wireless access of a device to the wireless network, a radio access network (RAN) is connected to the CN, and in particular, the transfer of control signaling and data signaling between the wireless terminal and the CN is performed.

[0003] In 3GPP documents, a terminal is generally referred to as a user equipment (UE), and this term is consistently used in this specification for simplicity. The RAN is composed of a number of access nodes that operate to provide wireless access to the UE. Each access node, also called a RAN node or a base station, can provide a connection via a radio interface within a so-called cell. Various 3GPP releases relate to the specifications of a wireless communication system called the 5G wireless communication system (5GS), including new radio (NR) technology for the RAN, and the term gNB is used to identify an access node. In this specification, the term gNB is also used at least sometimes to indicate an access node. In 5G, the core network is also called 5GC.

[0004] The 3GPP specification for RAN specifies that the functionality of an access node (gNB) can be divided between a centralized unit (CU) and a distributed unit (DU), which can be split into two physical entities. DUs are located near antennas, while CUs are typically located in data servers. CUs support the upper layers of the 5G NR protocol stack, such as SDAP (Service Data Adaptive Protocol), PDCP (Packet Data Convergence Protocol), and RRC (Radio Resource Control). DUs support the lower layers of the protocol stack, such as RLC (Radio Link Control), MAC (Media Access Control), and PHY (Physical Layer). In practice, there may be one CU per gNB, but a single CU may control multiple DUs; for example, one CU can connect to more than 100 DUs. The interface between CUs and DUs is called an FL, and 3GPP requires it to be an open interface. Therefore, a CU from one vendor can be connected to a DU from another vendor. In such a partitioned architecture, CUs, like their associated CN nodes, may be located within the data center. Therefore, in the future, it is expected that the RAN CU will be further integrated with the CN, and the DU will become hardware located closer to the antenna.

[0005] The concept of a shared RAN has been proposed, which allows a RAN to be connected to multiple CNs belonging to different operators. This allows multiple operators to share hardware at RAN nodes, and the frequency spectrum can also be shared, even by small local operators that do not have their own spectrum, such as private networks. In 3GPP, a RAN can be connected to multiple operators, and each operator has one CN. This is called MORAN (Multi-Operator RAN). Each CN has one interface to both the user plane and the control plane. Data is added to a common user plane protocol stack within the RAN, where it is added to the 5QI flow based on its respective QoS (Quality of Service).

[0006] One anticipated scenario is that the number of micro-operators will increase in the future as 6G is deployed locally or distributed across many locations (as public or private networks). While micro-operators have their own CNs, they may not have authorized spectrum or access nodes. One solution is to utilize spectrum shared among multiple operators or to utilize a portion of the spectrum or access nodes of a large operator. However, this presents challenges regarding the handling of data traffic related to different CNs. [Overview of the project] [Problems that the invention aims to solve]

[0007] The general objective is to provide a solution to the challenge of configuring a RAN to handle traffic associated with different CNs that may belong to different network operators. The solution proposed herein is defined by the terminology of the independent claims, although various embodiments are outlined in the dependent claims. [Means for solving the problem]

[0008] According to one embodiment, an access node device is provided having a segmented layer function for operating in a wireless access network, comprising: at least two upper layer subnodes configured to implement the upper layers of a wireless protocol stack for individual core network connections; a lower layer subnode shared by the upper layer subnodes, equipped with a wireless unit, implementing a lower layer that supports the upper layers of the at least two upper layer subnodes, and configured to communicate lower layer data using the wireless unit; and a scheduler, wherein one of the upper layer subnodes is a master subnode configured to control the scheduler in order to manage the allocation of resources for data communication to any of the upper layer subnodes connected to the lower layer subnodes.

[0009] In another embodiment, an upper-layer subnode configured as a master subnode is provided in an access node device having a segmented layer function for operating in a wireless access network. The upper-layer subnode is An interface configured to provide connectivity to one core network, A logic circuit configured to implement the upper layer of the wireless protocol stack, A communication interface configured for connection to a lower layer subnode, wherein the lower layer subnode is configured to implement a lower layer that supports the upper layer of each of a plurality of upper layer subnodes in parallel in order to obtain full support for the radio protocol, The above logic circuit is configured to control a scheduler to manage resource allocation for any upper-layer subnode connected to the lower-layer subnode.

[0010] In yet another embodiment, an upper layer subnode is provided for use in an access node device having a segmented layer function for operating in a wireless access network. The upper layer subnode is, An interface configured to provide connectivity to one core network, A logic circuit configured to implement the upper layer of the wireless protocol stack, A communication interface configured for connection to a lower-layer subnode, wherein the lower-layer subnode is configured to implement a lower layer that supports the upper layers of multiple upper-layer subnodes in parallel, and the upper-layer subnode uses the communication interface to obtain full support for the wireless protocol stack. For the allocation of resources by the scheduler to the above-mentioned upper-layer subnodes, it includes an interface to the above-mentioned scheduler, which is under the control of an even higher-layer subnode acting as a master subnode. The above-mentioned upper-layer subnodes are configured as slave subnodes of the above-mentioned master subnodes.

[0011] The proposed solutions and their various forms stem from the understanding that the functionality and support of CUs and most DUs can now be implemented in the same data center, often the same data center where the corresponding core network operates. For example, in today's architectures using MORAN (Multi-Operator RAN), everything within the RAN except the radio carrier (antennas, towers, sites, power) is shared among two or more operators. In such solutions, all data is sent to the same common data center, processed there, and then transmitted and received between data centers where the core networks of different operators operate for further distribution. Furthermore, DL data, after being sent to the RAN, is processed in a common manner using different available 5QI flows. Direct control of the load on each operator on the radio interface is impossible.

[0012] On the other hand, the proposed solution provides an efficient architecture and operation of a shared access node in which partitioning functionality is defined by lower-layer components configured to work in conjunction with multiple upper-layer components of different networks and operators. The lower-layer entities can be controlled to manage resource allocation and scheduling based on the network to which the data is associated. Thus, the proposed solution provides a technical solution that facilitates a proper balance between the spectrum usage needs of micro-operators and the traffic and usage control needs of network-owning operators. Resource allocation and scheduling can be suitably controlled by configuring the access node device so that one upper-layer subnode acts as the master of any connected upper-layer subnodes, and by extension, multiple core networks. Furthermore, even when the access node device is used by multiple core networks for signaling, random access processing, etc., radio resource control can be operated under the control of the master subnode.

[0013] Various embodiments will be described with reference to the drawings. [Brief explanation of the drawing]

[0014] [Figure 1] Figure 1 schematically shows a radio network with a radio access network including at least two base stations, each base station comprising a central unit and at least one distributed unit. [Figure 2A] Figure 2A schematically illustrates the partitioning function and protocol layer processing in a RAN access node device related to various examples of the proposed solution, providing common lower-layer entities. [Figure 2B] Figure 2B schematically illustrates the architecture of Figure 2A, further showing that the distributed units are divided into network-specific parts and common lower-layer parts that are shared. [Figure 2C] Figure 2C schematically shows an example of an architecture similar to Figure 2A, but with a different scheduler configuration. [Figure 3] Figure 3 schematically illustrates the functional elements included in lower-layer subnodes that are available to multiple connected network-specific upper-layer subnodes, according to various embodiments of the proposed solution. [Figure 4] Figure 4 schematically shows the functional elements included in an upper-layer subnode that can realize base station functionality for a single network by connecting to a lower-layer subnode, according to various embodiments of the proposed solution. [Figure 5] Figure 5 is a signaling diagram showing various signals and configuration steps that may be included in various embodiments of the proposed solution. [Modes for carrying out the invention]

[0015] Hereinafter, the present invention will be described in more detail while referring to the accompanying drawings showing embodiments of the present invention. However, the present invention can be implemented in various forms and is not limited to the embodiments described in this specification. These embodiments are provided so that this disclosure is thorough and complete, and those skilled in the art can fully understand the scope of the present invention.

[0016] When an element is described as "connected to" another element, it should be understood that the element is directly connected to the other element or there may be intervening elements. On the other hand, when an element is described as "directly connected to" another element, there are no intervening elements. Throughout the specification, the same reference numerals refer to the same elements. Further, although terms such as "first," "second," etc. may be used in this specification to describe various elements, it should be understood that these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the present invention, the first element can also be referred to as the second element, and similarly, the second element can also be referred to as the first element. The term "and / or" used in this specification includes any combination of one or more of the related listed items.

[0017] For the sake of brevity and / or clarity, well-known functions or configurations may not be described in detail. Unless otherwise defined, all terms (including technical and scientific terms) used in this specification have the same meaning as commonly understood by those skilled in the technical field to which the present invention pertains. Further, terms defined in commonly used dictionaries, etc. should be interpreted to conform to the meaning in the context of this specification and the related technology, and it should also be understood that they should not be interpreted in an idealized or overly formal meaning as explicitly defined in this specification.

[0018] Embodiments of the present invention are described herein with reference to schematic drawings of ideal embodiments of the invention. Therefore, deviations from the illustrated shapes and relative sizes are expected, for example, as a result of manufacturing techniques and / or tolerances. Accordingly, embodiments of the invention should not be construed as being limited to specific shapes and relative sizes of the areas shown herein, but rather include deviations in shape and / or relative size resulting, for example, from different operational and / or manufacturing constraints. Accordingly, the elements shown in each figure are essentially schematic, and their shapes are not intended to represent the actual shapes of the areas of the device, nor are they intended to limit the scope of the invention. Where this disclosure refers to the transmission or reception of information, it should be noted that this information may be transmitted in one or more messages. Figure 1 shows a wireless network 100 in a configuration usable to understand the proposed solution. The wireless network 100 may be a wireless communication network operating under general and specific regulations and restrictions issued by 3GPP. The wireless network 100 may include a core network 110 connected to other networks such as the Internet. The wireless network 100 further includes an access network 120 which includes multiple base stations or access nodes (the figure shows a first base station 130 and a second base station 140).

[0019] Furthermore, UE10 is shown that can access the wireless network via any base station included in RAN120. UE10 may be any device capable of wirelessly communicating with network 100 via base stations 130, 140, such as a mobile phone, computer, tablet, M2M device, or IoT device.

[0020] In RAN120 of FIG. 1, at least two base stations 130 and 140 are configured with an architecture in which the base station functions are split into two different types of entities. In conventional 3GPP terminology, each access node 130, 140 may include a first entity that is a central unit (CU) 131, 141 respectively, and a second entity that is one or more distributed units (DUs) 132, 133 and 142, 143. Such an architecture type is described in particular in 3GPP Technical Specification TS38.401 version 15.6.0 Release 15 section 6. The CU processes SDAP / PDCP / RRC, and the DU processes RLC / MAC / PHY. The CU and the DU are connected via the logical interface F1, and the logical interface F1 can transmit either control signaling V1-C or data packet V1-U. Each DU provides service to one cell and has an associated cell ID. The actual transmit and receive points of each of the DUs 132, 133, 142, 143 may be referred to as transmit and receive points (TRPs), which can be regarded as network nodes that include or are co-located with the antenna system of each DU.

[0021] The following describes various aspects of the proposed solution with reference to the drawings, specifically Figures 2A, 2B, 2C, 3, and 4. The proposed solution is based on the idea that different operators with different core networks can share at least a portion of the access node HW located near the antennas, and the associated SW for operating the HW. In this specification, this HW and logic circuitry are referred to as a lower-layer subnode (LL-DU), and incorporate logic circuitry that implements the lower layers of a radio protocol stack (e.g., a 5G NR protocol stack). The LL-DU further provides interfaces to complementary portions of the protocol stack implemented in different upper-layer subnodes belonging to different operators. Here, a subnode is a functional entity that is a sub-part of an access node (e.g., a gNB) and implements a portion of the complete / whole radio protocol stack implemented by the access node. The proposed solution identifies, for an access node of a network belonging to one operator, one functional entity configured to implement the upper layers and one functional entity configured to implement the lower layers. A division is set up between collaborating subnodes, with functional entities that process lower layers configured as lower-layer subnodes (LL-DU), and functional entities that process upper layers configured as upper-layer subnodes.

[0022] In one example, the lower layer has physical layer functions such as multiplexing, encoding, and modulation of DL data, and demodulation, decoding, and demultiplexing of UL data, as described in 3GPP Technical Specification 38.212. The lower layer also receives LI control information and measurement results from the UE, primarily used by the UL and DL data resource allocation scheduler. The lower layer may also include a MAC layer that receives data from a PHY capable of processing the destination and quality of each data. For example, different QoS flows are processed there. In the solution proposed herein, the MAC layer is also configured to transmit data to the correct subnodes that form the upper layer entities.

[0023] The functional entity that handles the upper layers includes a data buffer for DL ​​data and operates link layer protocols such as retransmission connected to each UE link. This functional entity further implements the PDCP and SDAP layers and is configured to pass data to these upper layers. These upper layers handle, for example, different QoS flows, interfaces to the core network for the user plane, and interfaces to the RRC layer for the control plane. The RRC layer of this functional entity controls all connections between the access node, configured as a gNB, and the UE.

[0024] By using LL-DU, each upper-layer subnode obtains full support for the radio protocol stack and full base station functionality, such as gNB, for each connected core network. In the context of 5G RAN, full support may refer to the user plane protocol stack of SDAP / PDCP / RLC / MAC / PHY and the control plane protocol stack of RRC / PDCP / RLC / MAC / PHY. The partition between each upper-layer and lower-layer subnode may be set between RLC and PHY. Specifically, this partition may be set between RLC and MAC, or between MAC and PHY. Furthermore, as will be described later, the partition between upper-layer and lower-layer subnodes may differ from conventional CU-DU partitions. This combined structure is configured so that each upper-layer subnode uses a common LL-DU to form individual base stations, and each individual base station forms an access node device that can be operated independently by, for example, different operators. The upper-layer subnodes of the access nodes can be implemented in different data centers or clouds. Data transmitted and received via the radio interface with the UE is controlled by a scheduler that allocates downlink and uplink physical layer resources, as specified in section 10.1 of 3GPP Technical Specification 38.300, for example, and the amount of radio resources used by each operator can be controlled. Thus, the scheduler is configured to manage the allocation of radio resources to each upper-layer subnode and, by extension, to each network of each operator. Here, the access network may be shared by at least some access nodes. On the other hand, the entire radio network may not be shared, and therefore mobility may be configured to be handled on an operator-by-operator basis. According to some examples, the radio network of an operator that owns and / or controls an LL-DU is called the master network, which includes the master core network. The upper-layer subnodes of the master network are referred to herein as master subnodes, and the combination of the LL-DU and master subnodes forms the master access node.The master subnode configures the LL-DU via an interface and controls resource allocation within the LL-DU according to the source CN. Other wireless networks that utilize the LL-DU in an access node device by connecting higher-layer subnodes are referred to as slave networks. The higher-layer subnodes of a slave network are referred to as slave subnodes in this specification.

[0025] Figure 2A shows a RAN architecture relating to various examples of the proposed solution, illustrating various interfaces. As an example, four CNs with individual upper-layer subnodes of an access node device 20 are schematically shown, with upper-layer subnodes 300 and 301 identified. All upper-layer subnodes of the access node device 20 are connected to the same lower-layer subnode, i.e., a common lower-layer subnode, LL-DU200. In other words, although different upper-layer subnodes of the access node device 20 are used by different networks, they all share a common lower-layer subnode 200.

[0026] In this diagram, the master network is shown on the right, and slave networks 1-3 are shown on the left. Here, the master network, through the master subnode 300, constitutes the Fx communication interface between the LL-DU200 and the transmit data buffers in the various upper-layer subnodes. The transmit data buffers are used to store DL data in the upper-layer subnodes of each network until the scheduler allocates resources for sending data to the UE. Thus, the scheduler is configured to manage the allocation of downlink data from each data buffer in the upper-layer subnodes. Once resources are allocated, the scheduler instructs the data buffers to send the buffered data to the LL-DU200. Note that the master subnode 300 does not need to have a data buffer; it only needs to be configured to control one or more slave networks. An Fy interface is configured between the master subnode 300 and the LL-DU200 to provide control information, including configuration and control signaling, to the LL-DU200. The master subnode 300 is further configured with Fz interfaces to each of the upper-layer subnodes of the slave network, such as the slave subnode 301.

[0027] Figure 2B corresponds to Figure 2A, but with slightly different wording. Here, it is more clearly shown that the RAN protocol stack of the access node device 20 can maintain the CU-DU partitioning (F1) for each network, but the DU includes further partitioning to identify the (common) LL-DU200. Thus, each upper-layer subnode 300, 301 comprises a CU and a portion of the conventional DU. Thus, the access node device 20 can identify three subnodes for each network. In the example of the master network CN-M, the access node device 20 may comprise CU(CU_M)300A, DU(DU_M)300B, and LL-DU200. In the example of the slave network CN-1, the access node device 20 may comprise CU(CU_1)301A, DU(DU_1)301B, and LL-DU200.

[0028] From a user plane perspective, as shown in the diagram, a lower layer division is defined between MAC and PHY, or between RLC and MAC, and the scheduler 214 is placed within the LL-DU. This makes it possible to connect upper layer subnodes 300 and 301 from different networks in parallel to the same LL-DU 200, that is, upper layer subnodes 300 and 301 from different networks are connected to the same LL-DU 200 simultaneously.

[0029] In this example, the scheduler 214 is located within the LL-DU200. Therefore, resource allocation and scheduling management of DL data are handled by the LL-DU200. The LL-DU200 is configured to control the DL data buffers in each upper-layer subnode 300, 301 so that data is sent to the LL-DU200 via the corresponding Fx interface based on the allocation by the scheduler 214. Figure 2C shows another example where the scheduler 214 is contained within a master subnode 300, such as the master DU(DU_M)300B. Therefore, resource allocation and scheduling management of DL data is configured to be performed by the master subnode 300. The master subnode 300 is configured to control the DL data buffers in each upper-layer subnode 300, 301 so that data is sent to the LL-DU200 via the corresponding Fx interface based on the allocation by the scheduler 214.

[0030] As illustrated in Figures 2A, 2B, and 2C, the scheduler 214 is configured to manage the allocation of DL data from each data buffer within the upper-layer subnodes 300, 301, as shown in these figures. In other words, each upper-layer subnode 300, 301 has a data buffer for holding the DL data to be transmitted, and the scheduler 214 is configured to manage resource allocation for all upper-layer subnodes 300, 301 of the access node device 20. This may include the association of data with the core network, i.e., resource allocation dependent on core networks CN-1, CN-M connected to the upper-layer subnodes 300, 301 that have buffers for holding data.

[0031] In both examples of Figures 2B and 2C, after the DL RAN data links of each network utilizing the access node device 20 are terminated in the buffer, the scheduler 214 determines which data to receive from which upper-layer entities 300, 301 at the common LL-DU 200, for example, for subsequent transmission over the radio link to the UE. At the UL (uplink), data belonging to different networks is distributed from the LL-DU 200 to the correct upper-layer subnodes 300, 301 based on the operator to which the data belongs.

[0032] The proposed solution would allow scheduler 214 to manage resource allocation and scheduling based on which operator / network to prioritize. This may also be based on the agreement and usage of available radio resources, which may change over time. Resource management, including scheduling, may also be based on services associated with the data, latency requirements, data volume, radio resources allowed per operator, etc.

[0033] From a control plane perspective, broadcast signaling needs to be consistent and transmitted from a single source. According to one aspect of the proposed solution, broadcast signaling is performed from an upper-layer subnode 300 under the control of a single network, such as a master network. Furthermore, when a UE accesses a network, such as by initiating network registration, a master control layer 300C is proposed that controls the radio resources of any connected CN before the UE connects to the relevant CN of the network to which the UE belongs. This also involves control signaling. Thus, the master subnode 300 may be configured to control signaling, such as broadcast and random access signaling, by the master control layer 300C, including sending messages in a random access procedure to multiple upper-layer subnodes, such as any upper-layer subnodes connected to the LL-DU200 (as illustrated with reference to Figure 5).

[0034] For example, this master control layer 300C is called a common control layer and may be exemplified herein as master RRC300C. Master RRC330C may be configured to control random access signaling to any upper-layer subnode connected to a lower-layer subnode. This random access signaling may form part of UE registration, where registration may include registration management procedures as described in 3GPP Technical Specification 4.2.2. This may also be managed by master subnode 300.

[0035] For example, broadcast signaling is transmitted from the RRC implemented in the master control layer 300C, for example, the master subnode 300, through its protocol stack to the LL-DU200, and transmitted in SSB (Synchronization Signal Block). The LL-DU200 is controlled by the master control layer 300C via the Fy interface. The master control layer 300C is controlled by the operation and management (O&M) of the master network, i.e., the operator that manages and owns the rights to use the radio communication spectrum. On the other hand, other control layers (RRCs) of the upper layer subnodes of each slave network, for example, the control layer 301C of the upper layer subnode 301, are partially controlled by the master control layer 300C (hereinafter mainly referred to as master RRC300C). Therefore, the control layer 300C (e.g., RRC) implemented by the master subnode may be configured to control broadcast signaling to any upper layer subnode of the access node device 20.

[0036] In some examples, the master RRC300C is implemented as a higher-layer subnode of the operator handling the traffic. That is, the master RRC300C is included in the higher-layer subnode 300 of the master network, which also handles data traffic and has a data buffer. However, in another example, the protocol stack of the master network is configured solely for the purpose of controlling the access nodes of other (slave) networks and does not need to camp a UE. That is, the UE monitors the relevant system information on the channel and the cell's paging channel, for example, as defined in section 5.2.5 of 3GPP Technical Specification 38.304. In this example, the master subnode 300 does not need to be configured to buffer data transmitted on data channels such as PDSCH (Physical Downlink Shared Channel).

[0037] The master RRC300C function is configured to handle broadcast information and random access reception from at least unregistered UEs. In some examples, random access messages received from registered UEs are forwarded via a configured Fz interface to the corresponding RRC (e.g., 301C) in a higher-layer subnode (e.g., 301) of the network to which the UE belongs.

[0038] When registered with one of the active operators connected to the access node device 20, RRC signaling, mobility, etc., are processed by a dedicated RRC in a higher-layer subnode connected to the core network of the relevant operator. For example, when a UE belonging to slave network 1 connects to that network via the access node device 20, RRC signaling with that UE is processed by RRC301C in the higher-layer subnode 301.

[0039] Therefore, the master RRC300C handles broadcast signaling and the initial steps of initial access and connection (e.g., by random access procedure) of UEs belonging to any network connected to the access node device 20 via their respective upper-layer subnodes 300, 301. Thus, the master RRC330C may be configured to control random access signaling of any upper-layer subnode connected to the LL-DU200. The master RRC and its associated / connected master CN define common configurations of the RAN HW, e.g., information related to supported QoS (Quality of Service) flows, and thus the common RRC300C and core network may communicate the configuration and limitations of the LL-DU node to a dedicated upper-layer subnode 301, for example, via a configured Fz interface.

[0040] Referring to conventional 5G standards, the proposed solution may identify the addition of a new lower-layer subnode 200, LL-DU, which includes lower layers (PHY and, potentially, MAC). The LL-DU 200 further comprises a radio unit configured to transmit a physical channel to any connected network, thereby allowing the LL-DU 200 to handle all radio transmissions and receptions of the access node device 20 to any connected core network. In some examples, a common scheduler 214 is included in the LL-DU 200.

[0041] Regarding mobility, in idle mode (including RRC_Inactive), mobility is handled by the UE identifying available cells based on the PLMN used by the UE. In connected mode, it is beneficial for different operators to handle mobility independently, as one operator may share some access nodes with other operators and not others. Therefore, adjacent cells may differ from operator to operator. In the 5G example, 3GPP refers to RRC_Connected (within RAN) and CM-Connected (within CN) to identify connected mode.

[0042] Based on the architecture described herein, as illustrated in Figures 2A to 2C, the UE recognizes only one access node, and the broadcast information (provided by the master RRC300C) lists multiple PLMNs. Thus, the master RRC300C of the upper layer subnode 300 of the master network may be configured to control the LL-DU200 to broadcast information identifying the network ID associated with any connected upper layer subnodes 300, 301. From the UE's perspective, the broadcast in this context may appear to correspond to a multi-operator radio access network (MORAN) broadcast, a system concept in which the same RAN is shared by two core networks of different operators, each having its own distinct frequency within the spectrum.

[0043] Figure 3 schematically illustrates a lower-layer subnode 200, also referred to herein as LL-DU200, representing various examples of the proposed solution that can be commonly used by multiple operators and networks at an access node of the RAN.

[0044] The LL-DU200 includes logic circuits 210 configured to control its operation. These may include data and signal communication between one or more core networks and a wireless interface.

[0045] The logic circuit 210 may include a processing unit 211 which includes one or more processors, microprocessors, data processors, coprocessors, and / or other types of components that interpret and / or execute instructions and / or data. The processing unit 211 may be implemented as hardware (e.g., a microprocessor) or as a combination of hardware and software (e.g., a system-on-a-chip (SoC), an application-specific integrated circuit (ASIC), etc.). The processing unit 211 may be configured to perform one or more operations based on an operating system and / or various applications or programs.

[0046] The logic circuit 210 may further include memory storage 212. Memory storage 212 may include one or more memories and / or one or more other types of storage media. For example, memory storage 312 may include random access memory (RAM), dynamic random access memory (DRAM), cache, read-only memory (ROM), programmable read-only memory (PROM), flash memory, and / or other types of memory. Memory storage 212 may also include hard disks (e.g., magnetic disks, optical disks, magneto-optical disks, solid-state disks, etc.). Memory storage 212 is configured to hold computer program code that can be executed by the processing unit 211, and the logic circuit 210 is configured to control the LL-DU200 to perform any of the steps specified herein. The software defined by the computer program code may include applications or programs that provide functions and / or processes. The software may include device firmware, an operating system (OS), or various applications that can be executed on the logic circuit 210.

[0047] The LL-DU200 may implement the lower layer 213 of the wireless protocol stack, specifically the PHY and possibly the MAC, which is used for data transmission and support of the upper layer of the wireless protocol stack. This is handled by the program code and instructions of the logic circuit 210 through communication with one or more individual upper layer subnodes, specifically, the upper layer of the protocol stack supported by the upper layer (master) subnode 300 of the master network of the same access node device 20, as described above. Thus, the LL-DU200 is configured to provide connectivity to the relevant individual core networks CN-1, CN-M via each connected upper layer subnode. Here, each core network, for example CN-1, is connected to one relevant upper layer subnode 301 of the access node device 20, and this upper layer subnode 301 is connected to the LL-DU200, and this combination implements the entire wireless protocol stack.

[0048] The LL-DU200 may further include a scheduler 214 configured to manage resource allocation for data communication between the wireless interface and one or more connected networks in various examples. Resource allocation to different networks can be based on agreement between operators, data QoS, connection priority, signal quality to the UE, etc. Specifically, the scheduler 214 may be configured to manage resource allocation for data communication, as described above, depending on the connected relevant core networks involved in data communication, using control information from the master of a connected upper-layer subnode or a common RRC300C.

[0049] The LL-DU200 may further comprise a radio unit 215 that includes one or more radio transceivers for wireless communication with other subnodes of the wireless communication network 100, such as the UE10. Thus, the radio unit 215 may comprise at least a radio receiver and a radio transmitter for communication via a radio interface. The LL-DU200 may achieve coverage of one cell of any connected wireless network. In other words, the LL-DU200 may be configured using a cell ID shared by any connected upper-layer subnodes of the access node device 20.

[0050] The LL-DU200 also features various interfaces 216 for data and control signaling, as described above.

[0051] The Fx interface 216A is configured on any connected upper-layer subnode (and thus on the associated core network). The Fx interface can be used, in particular, to receive DL data from a data buffer in the connected upper-layer subnode, under the control of the scheduler 214. The Fx interface may also be used to transmit UL data received from the UE to the associated upper-layer subnodes 300, 301 via the radio interface (Uu), and for control signaling.

[0052] Interface Fy 216B is configured on the master RRC300C for configuration and control of the LL-DU200 by a control network, such as the master network of the operator who owns or manages the LL-DU200. Therefore, interface Fy is a control interface configured to connect to one upper-layer subnode configured as a master subnode and to receive configurations for controlling the signaling of any connected upper-layer subnode.

[0053] Interface 216C may be included for connecting to an antenna for wireless communication.

[0054] Figure 4 schematically shows an upper-layer subnode 300 representing an upper-layer entity related to various examples of the proposed solution, operated by a single operator and therefore associated with one network (e.g., PLMN (Public Land Mobile Network)). The upper-layer subnode 300 is configured to be used in conjunction with LL-DU200 to form a separate base station (e.g., gNB) of the associated network's RAN.

[0055] The upper layer subnodes in Figure 4 are denoted by reference numeral 300, and it should be noted that these are primarily used to identify the upper layer subnodes of the master network in this specification. However, unless otherwise specified below, the corresponding functions and structures may be used in the upper layer subnodes of any slave network, e.g., upper layer subnode 301.

[0056] The upper-layer subnode 300 may consist solely of software code configured to be executed by logic circuits to implement the layer of the wireless stack for communicating with the associated core network and other entities such as the LL-DU200. However, the following description assumes that it includes logic circuits. In some examples, the upper-layer subnode 300 may be located in the same location as one or more entities of the associated network's core network, such as within a data center or in the cloud.

[0057] The upper layer subnode 300 may include logic circuits 310 configured to control its operation. This may include data and signal communication between one or more core networks and a wireless interface.

[0058] The logic circuit 310 may include a processing unit 311 which includes one or more processors, microprocessors, data processors, coprocessors, and / or other types of components that interpret and / or execute instructions and / or data. The processing unit 311 may be implemented as hardware (e.g., a microprocessor) or as a combination of hardware and software (e.g., a system-on-a-chip (SoC), an application-specific integrated circuit (ASIC), etc.). The processing unit 311 may be configured to perform one or more operations based on an operating system and / or various applications or programs.

[0059] The logic circuit 310 may further include memory storage 312. Memory storage 312 may include one or more memories and / or one or more other types of storage media. For example, memory storage 312 may include random access memory (RAM), dynamic random access memory (DRAM), cache, read-only memory (ROM), programmable read-only memory (PROM), flash memory, and / or other types of memory. Memory storage 312 may also include hard disks (e.g., magnetic disks, optical disks, magneto-optical disks, solid-state disks, etc.). Memory storage 312 is configured to hold computer program code that can be executed by the processing unit 311, and the logic circuit 310 is configured to control the upper layer subnode 300 to perform any of the steps defined herein. The software defined by the computer program code may include applications or programs that provide functions and / or processes. The software may include device firmware, an operating system (OS), or various applications that can be executed on the logic circuit 310.

[0060] The upper layer subnode 300 may implement the upper layer 313 of the radio protocol stack, specifically the RLC, SDAP, PDCP, and RRC for the control plane. If the upper layer subnode is the master subnode 300, the RRC may be configured to control at least partially further upper layer subnodes 301 of the slave network as the master or common RRC300C described herein. If the upper layer subnode is the slave subnode 301, the RRC may be configured as an RRC301C dedicated to that network. The upper layer implementation 313 is processed by the program code and instructions of the logic circuit 310 and operates in communication with the lower layers of the protocol stack supported by the LL-DU200.

[0061] In some examples, the upper layer subnode 300 further includes a data buffer for buffering DL data.

[0062] In various examples, the upper layer subnode 300 may further include a scheduler 214 configured to manage the allocation of resources for data communication between the upper layer subnode 300 and the radio interface configured by the LL-DU200, as shown in Figure 2C. Specifically, the scheduler 214 may be configured by the master RRC300C to manage the allocation of resources for data communication, as described above, using control information, depending on the relevant connection core network involved in the data communication.

[0063] The upper layer subnode 300 is configured to work in conjunction with the LL-DU200, which implements a complementary part of the radio protocol stack. As a result, the combined upper layer subnode and LL-DU200 implement a complete radio protocol stack in which the layer implemented by the LL-DU200 transmits data from the layer implemented by the upper layer subnode, and the LL-DU200 further includes at least a radio unit for communication via a radio interface.

[0064] The upper layer subnode 300 further includes various interfaces 316 for data and control signaling, as described above.

[0065] The Fx interface 316A is configured to connect to the LL-DU200. The Fx interface can be used, in particular, to receive data from the LL-DU200 in UL and to supply data from the data buffer 314 included in the upper layer subnode 300, under the control of the scheduler 214 included in the upper layer subnode 300 or the LL-DU200. The Fx interface may also be used for control signaling.

[0066] The upper-layer subnode operating as the master subnode 300 is provided with an Fy interface 316B. The Fy interface is configured to connect the master subnode 300's RRC300C to the LL-DU200 and is available for configuring the LL-DU200. This may include sending a configuration to the LL-DU200 that manages resource allocation (including scheduling) for any upper-layer subnodes 300, 301 connected to the LL-DU200, if the LL-DU200 is equipped with a scheduler 214. Therefore, the master subnode 300 may be configured in the access node device 20 to control the scheduler 214 to manage allocations to the upper-layer subnodes 300, 301 connected to the LL-DU200. Through the Fy interface, the LL-DU200 may receive a configuration that controls signaling to any connected upper-layer subnodes. Based on the received configuration, the LL-DU200 may be configured to control the scheduler 214, if it includes a scheduler 214, to manage allocations to any connected upper-layer subnodes. As illustrated herein, this control by the master subnode 300 may include transmitting control information that controls resource allocation depending on the association of the core networks of each connected upper-layer subnode 300, 301. Thus, the scheduler may be configured by the control information to manage allocations based on the core network associated with the UE, i.e., based on or depending on the outgoing core network in the case of a DL, and based on the incoming core network in the case of a UL. Here, the control information may be configured depending on, for example, an operator agreement between the master network operator and the slave network operator that sets ranges and limits regarding bandwidth and latency. Here, the control information may be configured so that the scheduler preferentially allocates resources based on which core network the data to be scheduled is associated with (source or destination of the data).In other words, the scheduler may be configured to prioritize resource allocation based on the requesting core network.

[0067] An Fz interface 316C may be provided. The Fz interface is configured to connect the RRC of a higher-layer subnode to the RRC of an even higher-layer subnode. If the higher-layer subnode is a master subnode 300, the Fz interface may connect its master RRC 300C to one or more RRC 301Cs of each slave network. If the higher-layer subnode is a slave subnode 301, the Fy interface may connect its RRC 301C to the master RRC 300C of the master subnode 300. Thus, interface Fy is used for configuration and control between higher-layer subnodes by a control network, such as the master network of an operator that owns or manages the master subnode 300.

[0068] Furthermore, an interface 316D is included, which is configured for connection to a core network (CN), such as a single CN, for example, the core network CN-M of the master network or CN-1 of slave network 1. In other words, in the architecture of the access node device 20, each upper-layer subnode is provided with an interface 316D configured to provide a connection to an individual core network.

[0069] In some examples, as shown by the dashed line in Figure 4, and in Figures 2B and 2C, the access node device 20 may be configured such that the upper layer subnode 300 (here, using the master network as an example) includes CU300A (CU_M) and at least the RLC (DU_M) of the DU. In this case, the upper layer subnode 300 includes the CU and the first portion of the DU in the conventional CU-DU partition. Thus, the upper layer subnode 300 is connectable to an LL-DU200 that implements a second lower layer portion common to multiple DUs of different upper layer subnodes 300, 301. In the example shown in Figure 2B, where this conventional CU-DU partition is maintained, the access node device 20 consists of multiple CUs CU_1, CU_M and multiple DUs DU_1, DU_M. Each upper layer subnode 300, 301 individually implements either CU300A, 201A and one of the first DU portions 300B, 301B of the DU. LL-DU200 implements a second lower-layer DU portion 213 common to multiple DUs. Here, the first DU portions 300B, 301B and the second lower-layer DU portion 213 provide a combined implementation of each layer of a single DU. In the example of slave network 1, the access node device 20 has the upper-layer subnode 301 with CU(CU_1)301A and DU portion (DU_1)301B implemented, and the second lower-layer DU portion 213 implemented in LL-DU200. Figure 5 shows a signaling diagram schematically illustrating the signals and configurations between various subnodes of the proposed solution.

[0070] Two different UE1 and UE2 are shown, and at least UE2 is not initially registered with that network.

[0071] An LL-DU (lower layer subnode) 200 is shown, which is configured to connect the master network and at least one additional slave network, including an upper layer subnode 301, via an upper layer subnode 300 of the master network. The upper layer subnodes 300 and 301 are similar to those in Figures 2B and 2C, and are shown here with two sub-parts 300A, 300B, and 301A, 301B, respectively, as described with reference to Figure 4.

[0072] The upper layer subnode 300 of the master network includes a sub-part 301A designated as gNB-CU (master). This sub-part 301A supports and processes SDAP, PDCP, and the master RRC 300C, and in particular operates to constitute the upper layer subnode 301 and lower layer subnode 200 of other connected networks. The upper layer subnode 300 of the master network further includes a sub-part 300B designated as gNB-DU (master), which includes a sub-part of the conventional DU functionality as described above. This sub-part 300B implements and processes the RLC of the master network and may further include a data buffer.

[0073] Similarly, the upper layer subnode 301 of the slave network, which does not own or control the lower layer subnode 200, includes a sub-part 301A denoted as gNB-CU1, which contains CU functionality. This sub-part 301A implements and processes the slave network's SDAP, PDCP, and network-specific RRC301C. The upper layer subnode 301 of the slave network further includes a sub-part 301B denoted as gNB-DU1, which contains the conventional DU functionality sub-part as described above. This sub-part 301B implements and processes the slave network's RLC and includes a data buffer. As described above, the top of the figure shows the interfaces Fl, Fx, Fy, and Fz between the cooperating entities.

[0074] Various aspects and examples of the proposed solution are shown in the drawings below.

[0075] 501 shows the configuration of the F1 interface between the master CU portion (CU_M) 300A and the master DU portion (DU_M) 300B in the master subnode 300.

[0076] In 502, the configuration step is performed between sub-part 300A (CU_M) and sub-part 300B (DU_M) using the F1 interface.

[0077] 503 shows the configuration of the Fy interface between the master subnode 300, specifically its CU portion 300A, and the LL-DU200.

[0078] In step 504, the FY interface is used to perform the wireless configuration step between sub-section 300A and LL-DU200.

[0079] 505 indicates the configuration of the Fz interface between the master subnode 300 and the slave upper layer subnode 301. Specifically, interface Fz is configured between the master RRC300C of the master CU portion 300A and the RRC301C of the slave CU portion 301A.

[0080] In 506, the cell configuration step is performed between the master CU300A and (each) slave CU301A using the FZ interface.

[0081] Section 507 shows the configuration of the Fx interface between the master subnode 300, specifically its DU portion 300B, and the LL-DU200.

[0082] Section 508 further illustrates the configuration of the FX run by the master subnode 300 (exemplified here by master DU300B).

[0083] Step 509 shows the configuration of the FL interface between the slave CU portion (CU_1) 301A and the slave DU sub portion (DU_1) 301B in the slave subnode 301. This corresponds to step 501.

[0084] In step 510, the configuration step is performed between sub-part 301A (CU_1) and sub-part 301B (DU_1) using the F1 interface. This corresponds to step 502.

[0085] Step 511 shows the configuration of the Fx interface between the slave subnode 301, specifically its DU portion 301B, and the LL-DU200. This corresponds to step 507.

[0086] Section 512 further illustrates the configuration of the FX performed by the slave subnode 301 (exemplified here by slave DU301B). This corresponds to step 508.

[0087] 513 indicates that the broadcast channel is transmitted wirelessly from the master subnode 300 via a physical channel, from the master CU300A to the LL-DU200 via the master DU300B. Slave network-related information, such as PLMN identification included in the broadcast signaling, may be obtained from the slave CU301A at the master CU300A in step 506. The access node device 20, including the LL-DU200 and the upper layer entities 300 and 301, provides separate base station (e.g., gNB) functionality to both the master network and the slave network. The broadcast signal and SSB may be received by UEs in the area, such as UE1 and UE2.

[0088] 514 shows the first step of the Random Access Process (RACH) for connecting UE2 to its associated network, using the access node device 20 as the slave network. The RACH process, also called initial access, includes a series of processes between UE2 and the access node device 20 for UE2 to obtain uplink synchronization and a designated ID for radio access communication. The Random Access process includes a Random Access transmission from UE2 (e.g., Msg.1), which is received by LL-DU200. The Random Access transmission may also be called a preamble and may constitute a Random Access request, such as a Random Access Channel (RACH) request. In one example, the master subnode 300 is configured to also process the initial steps of RACH for UEs belonging to the slave network, as described later. In such an example, the Random Access message is forwarded from LL-DU200 to the master CU300A.

[0089] 515 indicates that the master CU300A responds via LL-DU200 with a random access response message.

[0090] Message 516 indicates that Msg.3, containing the ID of UE2, is sent by UE2, received by LL-DU200, and forwarded to master CU300A. Master CU300A forwards or reports the message to the slave CU301A of the network associated with UE2, based on the network information contained in or determined based on Msg.3. This determines that the master subnode 300 is involved in the RACH process. In other words, the master RRC300C within the master CU may be configured to forward messages received from UE2 after receiving a random access request. Based on subsequent messages received from the UE indicating a network association (e.g., Msg.3), forwarding of the higher-layer entity corresponding to that network association is performed to the RRC(301C). Therefore, the slave subnode RRC301C, i.e., the slave CU301A, is configured to receive messages originating from UE2 (e.g., Msg.3) from the master subnode 300A via the RRC interface Fz, following a random access request (e.g., Msg.1).

[0091] 517 demonstrates the establishment of a connection between UE2 and the appropriate network via LL-DU200, namely slave CU301A via slave DU301B. Slave CU301A is further connected to the associated slave core network CN-1 (not shown here).

[0092] 518 shows a DL transmission of data from the slave core network CN-1. The data, with the support of the protocol layer, is sent from slave CU301A to buffer 314 of slave subnode 301B. From there, the data is scheduled by LL-DU200 and transmitted to UE2. As mentioned above, the scheduler 214 may be included in either LL-DU200 or master DU300B. The remaining steps in Figure 5 relate to an example where the scheduler 214 is included in LL-DU200. An alternative example where the scheduler 214 is included in master DU300B is also briefly described.

[0093] 519 indicates that the slave subnode 301B sends a DL buffer status report (BSR) to the scheduler 214 contained in the LL-DU200, which shows the data received in 518. In an alternative example where the scheduler 214 is contained in the master DU300B, the BSR is sent to the master DU300B.

[0094] Resource allocation and scheduling may be performed by the scheduler 214 based on control information obtained at or from the master subnode 300. If the scheduler 214 is included in the LL-DU, the control information may be obtained using the Fy interface. The acquisition of control information in the LL-DU 200 may be performed in step 504, or after the steps corresponding to step 504, for example, after the Fz settings and configuration in steps 505 and 506 have been established. The control information may, for example, specify the allowable bandwidth or latency, and / or determine the priority for acquiring resource allocation in relation to other networks using the access node device 20.

[0095] 520 indicates that the scheduler (within LL-DU200) sends a DL data request to the slave subnode 301B, which indicates the scheduling determined by the scheduler 214. This DL data request notifies the slave subnode 301B of the amount and timing of data to send to LL-DU200 for data transmission using the wireless unit 215.

[0096] In step 521, data from the slave DU301B's buffer is sent to UE2 by LL-DU200 according to the resource allocation determined by scheduler 214 based on the DL data request in step 520.

[0097] 522 indicates a UL transmission of data from UE2 in connected mode, where the data is received by LL-DU200 and transmitted to the associated upper layer subnode 301, which is then further forwarded to its core network CN-1.

[0098] As described herein, the scheduler 214 may be configured by the master subnode 300 to manage prioritizing allocations based on the requesting core network. This allows the master network, which owns or manages the spectrum within the cell, to maintain control over data traffic. Furthermore, this enables the operator of the master network to make technical scheduling settings based on different contracts with the operators of the slave networks, for example, by controlling the scheduler 214 to manage resource allocations to different upper-layer subnodes 3001 based on different requirements such as latency and / or bandwidth.

[0099] According to one aspect of the proposed solution described and illustrated above, a common RAN node architecture for an access node device 20 having a segmented layer function, wherein the access node device is At least two upper layer subnodes 300, 301 configured to implement the upper layer 313 of the wireless protocol stack for individual core network connections, The system includes a lower layer subnode 200 which is shared by the above upper layer subnodes 300 and 301, has a wireless unit 215, implements a lower layer 213 that supports the upper layers of at least two of the above upper layer subnodes 300 and 301, and is configured to communicate lower layer data using the wireless unit 215, Each of the above upper-layer subnodes has a communication interface Fx for parallel connection to the above lower-layer subnodes, thereby enabling each of the upper-layer subnodes 300, 301 to obtain full support for the above wireless protocol stack. A common RAN node architecture is provided. Here, parallel connectivity means that each upper-layer subnode 300, 301 is individually and independently connected to a lower-layer subnode 200 in order to communicate data with the individual core networks connected to each upper-layer subnode 300, 301. Therefore, although the upper-layer subnodes are associated with separate core networks, they share the lower-layer subnode 200.

[0100] Therefore, each upper-layer subnode 300, 301 is connected to a lower-layer subnode 200 and, when operated together with the lower-layer subnode 200, forms an individual base station such as a gNB, and each base station can be operated individually by, for example, a different operator. In this case, the access node device comprises a single lower-layer subnode 200 that can connect to multiple upper-layer subnodes 300, 301.

[0101] The proposed solution further offers the advantage of conveniently sharing the actual hardware and spectrum required for the wireless interface, while the base station functions, which can be configured by software-based logic circuits, can be configured separately by each operator in different locations, such as connections to the associated core network. This provides a way to reuse hardware and save at least the necessary materials and energy.

[0102] In another embodiment, the proposed solution is a lower-layer subnode 200 of an access node device 20 having a segmented-layer function for operating in a RAN, Wireless unit 215 and, A communication interface Fx configured to provide parallel connections to multiple upper-layer subnodes 300, 301 of the access node device, wherein each upper-layer subnode is configured to implement the upper layer of a wireless protocol stack for individual core network connections. A logic circuit 210 implements the lower layer 213 of the wireless protocol stack that supports the upper layers of at least two upper layer subnodes 300, 301, and is configured to communicate lower layer data using the wireless unit 215. A lower-layer subnode 200 is provided, which includes the following:

[0103] Thus, the lower-layer subnodes 200 form base station subunits of a complete base station, such as a gNB, by connecting the lower-layer subnodes 200 to upper-layer subnodes. Specifically, multiple individual base stations can be configured sharing a common lower-layer subnode 200, and each base station can be operated independently by, for example, a different operator. The proposed solution further offers the advantage of easily sharing the actual hardware required for the radio interface, while the functions of the base station, which can be configured by logic circuits operating in software, can be configured independently in different locations for each operator, such as connection to the associated core network. This provides a way to reuse hardware and save at least the necessary materials and energy. Furthermore, the master operator (i.e., the operator of the master network) that owns or manages the rights to the radio spectrum and controls the lower-layer subnodes 200 may allow other operators to connect to the lower-layer subnodes and obtain scheduling and resource allocation under the control of the master operator or based on an agreement with the master operator.

[0104] In another aspect, the proposed solution is an upper layer subnode 300 (or 301) used in an access node device 20 having a segmented layer function for operating in a wireless access network, wherein the upper layer subnode is Interface 316D is configured to provide connectivity to one core network CN-1, CN-M, A logic circuit 310 configured to implement the upper layer 313 of the wireless protocol stack, It comprises a communication interface Fx configured for connection to a lower layer subnode 200 configured to implement a lower layer 213 that supports the upper layers of multiple upper layer subnodes in parallel, and the lower layer subnode comprises a wireless unit 215 configured to communicate lower layer data. The above upper-layer subnodes obtain full support for the above wireless protocol stack using the above communication interface. Provides upper-layer subnodes 300 (or 301).

[0105] Thus, the upper-layer subnodes 300 and 301 form base station subunits of a complete base station, such as a gNB, by connecting to the lower-layer subnode 200. The proposed solution provides a division that defines the interface Fx to the lower-layer unit containing the HW necessary for wireless communication in the radio interface, and this HW can be easily shared with other upper-layer subnodes. On the other hand, the functions of the base station, which can be configured by logic circuits operating on software, can be configured individually in different locations for each operator. This improves the flexibility of the operator's computing infrastructure, for example, by providing the ability to configure upper-layer subnodes based on connections to the relevant core network. Furthermore, operators who do not own their own spectrum may connect to the lower-layer subnode 200 of the master network and obtain scheduling and resource allocation under the control of or based on an agreement with the master operator who owns or manages the spectrum.

[0106] In another embodiment, the proposed solution is an access node device 20 having a segmented layer function for operating in a wireless access network, At least two upper layer subnodes 300, 301 configured to implement the upper layer 313 of the wireless protocol stack for individual core network connections 316D, A lower layer subnode 200 is shared by the above upper layer subnodes 300 and 301, includes a wireless unit 215, implements a lower layer 213 that supports the upper layers of at least two of the above upper layer subnodes 300 and 301, and is configured to communicate lower layer data using the wireless unit 215, Equipped with a scheduler 214, One of the above upper-layer subnodes is a master subnode configured to control the scheduler in order to manage the allocation of data communication resources to any of the above upper-layer subnodes connected to the lower-layer subnodes. An access node device 20 is provided.

[0107] Therefore, the proposed access node device 20 provides an architecture in which the master network controls resource allocation and scheduling for all base stations of the access node device 20, where the upper layer subnodes 300 and 301 are each connected to the lower layer subnode 200, forming a base station subunit of a complete base station such as a gNB, and the master network controls resource allocation and scheduling for all base stations of the access node device 20. This provides the additional advantage that resource allocation and scheduling of data traffic can be configured differently depending on the source (or incoming) network. This allows operators who do not have their own spectrum rights to easily connect their upper layer subnode 301 to the lower layer subnode 200 of the master network and obtain an appropriate level of resource allocation based on an agreement with the master operator who owns or manages the spectrum. On the other hand, the proposed solution allows the master operator to maintain control over both scheduling and the control and execution of broadcast signaling.

[0108] Various aspects of the proposed solutions have been outlined above. The details and examples described herein may be combined in any way or in any form, or in any combination of the characteristics of the items shown below.

[0109] Item 1: An access node device having a segmented layer function for operation in a wireless access network, At least two upper-layer subnodes (300, 301) configured to implement the upper layer (313) of the radio protocol stack for individual core network connections (316D), A lower layer subnode (200) is shared by the above upper layer subnodes (300, 301), includes a wireless unit (215), implements a lower layer (213) that supports the upper layers of at least two of the above upper layer subnodes (300, 301), and is configured to communicate lower layer data using the wireless unit (215), It includes a scheduler (214), One of the above upper-layer subnodes is a master subnode configured to control the scheduler in order to manage the allocation of data communication resources to any of the above upper-layer subnodes connected to the lower-layer subnodes. Access node device.

[0110] Item 2: An access node device as described in Item 1, The master subnode described above implements the Radio Resource Control Layer (RRC) (300C) and has an RRC interface (Fz) to the RRC layer (301C) of any upper-layer subnode connected to the lower-layer subnode described above. Access node device.

[0111] Item 3: An access node device as described in Item 2, The RRC(300C) of the master subnode described above is configured to control broadcast signaling to any upper-layer subnode connected to the lower-layer subnode described above. Access node device.

[0112] Item 4 An access node device as described in Item 2 or 3, The RRC(330C) of the master subnode described above is configured to control the lower layer subnodes to broadcast information identifying the network ID associated with any connected upper layer subnode. Access node device.

[0113] Item 5 An access node device as described in any of Items 2 to 4, The RRC of the master subnode is configured to control random access signaling to any upper-layer subnode connected to the lower-layer subnode. Access node device.

[0114] Item 6 The access node device described in item 6, The above RRC of the master subnode is, Responding to random access requests from user devices (UEs), Subsequent messages indicating network associations received from the above UE are forwarded to the above RRC(301C) of the above-mentioned higher-layer entity corresponding to the above network association. It is configured to Access node device.

[0115] Item 7 An access node device as described in any of items 1 to 6, The above scheduler is included in the above lower layer subnode. Access node device.

[0116] Item 8 An access node device as described in Item 7, The lower-layer subnode described above is connected to the master subnode and includes a control interface (Fy) that receives configuration and control signals for the scheduler. Access node device.

[0117] Item 9 An access node device as described in any of Items 1 to 6, The above scheduler is included in the above master subnode. Access node device.

[0118] Item 10 An access node device as described in any of items 1 to 9, The above scheduler is configured to manage assignments that depend on the source core network. Access node device.

[0119] Item 11 An access node device as described in any of items 1 to 10, The above scheduler is configured to manage allocations by prioritizing them based on the requesting core network. Access node device.

[0120] Item 12 An access node device as described in any of items 1 to 11, The above scheduler is configured to manage the allocation of downlink data transmissions from each data buffer within the above upper-layer subnodes. Access node device.

[0121] Item 13 An access node device as described in any of items 1 to 12, The lower-layer subnodes described above are configured using cell IDs shared by the upper-layer subnodes described above. Access node device.

[0122] Item 14 An access node device as described in any of items 1 to 13, Each upper layer subnode includes the radio link control (RLC) layer of the above radio protocol stack. Access node device.

[0123] Item 15 An access node device as described in Item 14, The division between each upper layer subnode and the lower layer subnode is configured between the RLC and the physical layer (PHY) of the wireless protocol stack. Access node device.

[0124] Item 16 An access node device as described in Item 14, The division between each upper layer subnode and the lower layer subnode is configured between the RLC and the Media Access Control Layer (MAC) of the wireless protocol stack. Access node device.

[0125] Item 17 An access node device as described in any of items 14 to 16, Each upper-layer subnode includes the central unit (CU) of the access node device and at least the RLC of the distributed unit (DU). Access node device.

[0126] Item 18 An access node device as described in any of items 1 to 17, It comprises multiple central units (CU) (CU_1, CU_M) and multiple distributed units (DU) (DU_1, DU_M), Each upper layer subnode (300) One of the above CU(300A) and One of the above DUs, the first DU layer portion (300B) and Implement them separately, The above lower layer subnode (200) implements a second lower DU layer portion (213) common to the above multiple DUs. Access node device.

[0127] Item 19 An access node device as described in any of items 1 to 18, Each of the above upper-layer subnodes has its own communication interface (Fx) for parallel connection to the above common lower-layer subnode, thereby allowing each upper-layer subnode (300, 301) to obtain full support for the above wireless protocol stack. Access node device.

[0128] Item 20 An access node device as described in any of items 1 to 19, Each upper-layer subnode has an interface (316D) configured to provide connectivity to a separate core network (CN-1, CN-M). Access node device.

[0129] Item 21 An access node device as described in any of items 1 to 20, The lower layer subnode described above is equipped with an antenna interface (216C). Access node device.

[0130] Item 22 An upper layer subnode (300) configured as a master subnode in an access node device (20) having a segmented layer function for operating in a wireless access network, An interface (316D) configured to provide connectivity to one core network (CN-M), A logic circuit (310) configured to implement the upper layer (313) of the wireless protocol stack, A communication interface (Fx) configured for connection to a lower layer subnode (200), wherein the lower layer subnode (200) is configured to implement a lower layer (213) that supports the upper layers of each of a plurality of upper layer subnodes in parallel in order to obtain full support for the radio protocol, The above logic circuit is configured to control a scheduler to manage resource allocation for any upper-layer subnode connected to the lower-layer subnode. Upper layer subnodes (300).

[0131] Item 23: An upper-layer subnode as described in Item 22, and further, The data buffer is configured to provide data to the lower layer subnode via the above communication interface (Fx). Upper layer subnodes.

[0132] Item 24: An upper-layer subnode as described in Item 22 or 23, The above logic circuit is configured to implement the radio link control (RLC) layer of the above-mentioned radio protocol stack. Upper layer subnodes.

[0133] Item 25: An upper-layer subnode described in any of items 22 to 24, The above logic circuit implements a wireless resource control layer (RRC) (300C) and an RRC interface (Fz) connected to the RRC layer (301C) of any upper layer subnode connected to the lower layer subnode. Upper layer subnodes.

[0134] Item 26 The upper layer subnodes described in Item 25, The RRC of the master subnode described above is configured to control broadcast signaling to any upper-layer subnode connected to the lower-layer subnode described above. Upper layer subnodes.

[0135] Item 27 An upper-layer subnode as described in Item 25 or 26, The RRC of the master subnode described above is configured to control the lower layer subnodes to broadcast information identifying the network ID associated with any connected upper layer subnode. Upper layer subnodes.

[0136] Item 28: An upper-layer subnode described in any of items 25 to 27, The RRC of the master subnode is configured to control random access signaling to any upper-layer subnode connected to the lower-layer subnode. Upper layer subnodes.

[0137] Item 29 The upper layer subnodes described in Item 28, The above RRC of the master subnode is, Responding to random access requests from user devices (UEs), The system is configured to forward subsequent messages indicating network associations received from the above UE to the above RRC of the above-mentioned higher-tier entity corresponding to the above network association. Upper layer subnodes.

[0138] Item 30: An upper-layer subnode described in any of items 22 to 29, and further, The above scheduler is equipped with a control interface (Fy), The above scheduler is included in the lower layer subnodes. Upper layer subnodes.

[0139] Item 31: An upper-layer subnode described in any of items 22 through 29, and further, The above scheduler is included. Upper layer subnodes.

[0140] Item 32 An upper layer subnode (300) for use in an access node device (20) having a segmented layer function for operating in a wireless access network, An interface (316D) configured to provide connectivity to one core network (CN-1), A logic circuit (310) configured to implement the upper layer (313) of the wireless protocol stack, A communication interface (Fx) configured for connection to a lower layer subnode (200), wherein the lower layer subnode (200) is configured to implement a lower layer (213) that supports the upper layers of multiple upper layer subnodes in parallel, and the upper layer subnode obtains full support for the wireless protocol stack using the communication interface (Fx), For the allocation of resources by the scheduler to the above-mentioned upper-layer subnodes, it includes an interface to the above-mentioned scheduler, which is under the control of an even higher-layer subnode acting as a master subnode. The above upper-layer subnodes are configured as slave subnodes of the above master subnodes. Upper layer subnodes (300).

[0141] Item 33: An upper-layer subnode as described in Item 32, The above logic circuit implements the Wireless Resource Control Layer (RRC) (301C), The slave subnode further comprises an RRC interface (Fz) to the RRC layer (300C) of the master subnode. Upper layer subnodes.

[0142] Item 34: The upper layer subnodes described in Item 33, The RRC of the slave subnode is configured to receive messages originating from user equipment following a random access request from the master subnode via the RRC interface (Fz). Upper layer subnodes.

Claims

1. An access node device having a segmented layer function for operation in a wireless access network, At least two upper layer subnodes (300, 301) configured to implement the upper layer (313) of the radio protocol stack for individual core network connections (316D), A lower layer subnode (200) is shared by the upper layer subnodes (300, 301), includes a wireless unit (215), implements a lower layer (213) that supports the upper layers of at least two upper layer subnodes (300, 301), and is configured to communicate lower layer data using the wireless unit (215), It comprises a scheduler (214), One of the upper-layer subnodes is a master subnode configured to control the scheduler in order to manage the allocation of data communication resources to any of the upper-layer subnodes connected to the lower-layer subnodes. Access node device.

2. An access node device according to claim 1, The master subnode implements a radio resource control layer (RRC) (300C) and includes an RRC interface (Fz) to the RRC layer (301C) of any upper layer subnode connected to the lower layer subnode. Access node device.

3. The access node device according to claim 2, The RRC (300C) of the master subnode is configured to control broadcast signaling to any upper-layer subnode connected to the lower-layer subnode. Access node device.

4. An access node device according to claim 2 or 3, The RRC (330C) of the master subnode is configured to control the lower layer subnodes to broadcast information identifying the network ID associated with any connected upper layer subnode. Access node device.

5. An access node device according to any one of claims 2 to 4, The RRC of the master subnode is configured to control random access signaling to any upper layer subnode connected to the lower layer subnode. Access node device.

6. An access node device according to the claim, The RRC of the master subnode is Responding to random access requests from user equipment (UE), Subsequent messages indicating network associations received from the UE are forwarded to the RRC (301C) of the upper-layer entity corresponding to the network association. It is configured to Access node device.

7. An access node device according to any one of claims 1 to 6, The scheduler is included in the lower layer subnode. Access node device.

8. An access node device according to claim 7, The lower layer subnode is connected to the master subnode and includes a control interface (Fy) that receives configuration and control signals for the scheduler. Access node device.

9. An access node device according to any one of claims 1 to 6, The scheduler is included in the master subnode. Access node device.

10. An access node device according to any one of claims 1 to 9, The scheduler is configured to manage assignments that depend on the source core network. Access node device.

11. An access node device according to any one of claims 1 to 10, The scheduler is configured to manage allocations by prioritizing them based on the requesting core network. Access node device.

12. An access node device according to any one of claims 1 to 11, The scheduler is configured to manage the allocation of downlink data transmissions from each data buffer within the upper layer subnodes. Access node device.

13. An access node device according to any one of claims 1 to 12, The lower layer subnode is configured using a cell ID shared by the upper layer subnode. Access node device.

14. An upper layer subnode (300) configured as a master subnode in an access node device (20) having a segmented layer function for operating in a wireless access network, An interface (316D) configured to provide connectivity to one core network (CN-M), A logic circuit (310) configured to implement the upper layer (313) of the wireless protocol stack, A communication interface (Fx) configured for connection to a lower layer subnode (200), wherein the lower layer subnode (200) is configured to implement a lower layer (213) that supports the upper layers of each of a plurality of upper layer subnodes in parallel in order to obtain full support for the wireless protocol, The logic circuit is configured to control a scheduler to manage resource allocation for any upper-layer subnode connected to the lower-layer subnode. Upper layer subnodes (300).

15. The upper layer subnode according to claim 14, further, The system comprises a data buffer configured to provide data to the lower layer subnodes via the aforementioned communication interface (Fx). Upper layer subnodes.

16. An upper layer subnode according to claim 14 or 15, The logic circuit implements a wireless resource control layer (RRC) (300C) and an RRC interface (Fz) connected to the RRC layer (301C) of any upper layer subnode connected to the lower layer subnode. Upper layer subnodes.

17. An upper layer subnode according to claim 16, The RRC of the master subnode is configured to control broadcast signaling to any upper layer subnode connected to the lower layer subnode. Upper layer subnodes.

18. An upper layer subnode according to claim 16 or 17, The RRC of the master subnode is configured to control the lower layer subnodes to broadcast information identifying the network ID associated with any connected upper layer subnode. Upper layer subnodes.

19. An upper layer subnode according to any one of claims 16 to 18, The RRC of the master subnode is configured to control random access signaling to any upper layer subnode connected to the lower layer subnode. Upper layer subnodes.

20. An upper layer subnode according to claim 19, The RRC of the master subnode is Responding to random access requests from user equipment (UE), The system is configured to forward subsequent messages indicating network associations received from the UE to the RRC of the higher-tier entity corresponding to the network association. Upper layer subnodes.

21. An upper layer subnode (300) for use in an access node device (20) having a segmented layer function for operating in a wireless access network, An interface (316D) configured to provide connectivity to one core network (CN-1), A logic circuit (310) configured to implement the upper layer (313) of the wireless protocol stack, A communication interface (Fx) configured for connection to a lower layer subnode (200), wherein the lower layer subnode (200) is configured to implement a lower layer (213) that supports the upper layers of a plurality of upper layer subnodes in parallel, and the upper layer subnode obtains full support for the wireless protocol stack using the communication interface (Fx), For the allocation of resources by the scheduler to the aforementioned upper-layer subnodes, it comprises an interface to the scheduler, which is under the control of an even higher-layer subnode acting as a master subnode, The aforementioned upper-layer subnode is configured as a slave subnode of the master subnode. Upper layer subnodes (300).

22. An upper layer subnode according to claim 21, The aforementioned logic circuit implements a wireless resource control layer (RRC) (301C), The slave subnode further comprises an RRC interface (Fz) to the RRC layer (300C) of the master subnode. Upper layer subnodes.

23. An upper layer subnode according to claim 22, The RRC of the slave subnode is configured to receive messages originating from user equipment following a random access request from the master subnode via the RRC interface (Fz). Upper layer subnodes.

Images