Method and system for exchanging messages in a radio network

Abstract

A method and system for a centralized unit and a distributed unit of a base station operable to cooperate with each other are disclosed. In one embodiment, a method performed by a first communication node includes, in response to receiving a request, transmitting a first message to a second wireless communication node requesting to establish or modify a context of a data radio bearer (DRB), and receiving a second message from the second wireless communication node indicating that the context of the DRB has been established or modified at the second wireless communication node, wherein the first message includes first user plane address information of the DRB and the second message includes second user plane address information of the DRB.

Description

Technical Field

[0001] This disclosure generally relates to radio communications, and more specifically, to the exchange of messages between two wireless communication nodes in a radio network. Background Technology

[0002] Due to the massive connectivity and higher speed requirements of users in 5G New Radio (NR) communication networks (5G networks), the transmission capacity of the CPRI (Common Public Radio Interface) fronthaul interface between the BBU (Baseband Unit) and RRU (Radio Remote Unit) in LTE (Long-Term Evolution) communication networks faces significant challenges. Because the CPRI interface transmits I / Q (real / imaginary) signals that have already undergone physical layer encoding, it has stricter requirements for transmission latency and bandwidth. If the 5G F1 interface rate is increased to tens of gigabits per second (Gbps), the traffic demand on the CPRI interface will rise to the level of gigabits per second (Tbps), which will increase the cost and difficulty of network deployment. Therefore, in 5G networks, the fronthaul interface needs to be redefined considering transmission capacity, transmission latency, deployment convenience, and other factors. For example, considering non-ideal forward transmission, when partitioning a base station (BS), latency-insensitive network functions can be placed in a first network element such as a centralized unit (CU), and latency-sensitive network functions can be placed in a second network element such as a distributed unit (DU). Ideal and / or non-ideal forward transmission exists between the first and second network elements. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more issues presented by the prior art, and to provide additional features that will become apparent when taken in conjunction with the accompanying drawings and the following detailed description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not limitation, and that various modifications can be made to the disclosed embodiments by those skilled in the art who have read this disclosure, while remaining within the scope of this disclosure.

[0004] In one embodiment, the method performed by a first communication node includes: in response to receiving a request, transmitting a first message to a second wireless communication node, the first message requesting the establishment or modification of a data radio bearer (DRB) context; and receiving a second message from the second wireless communication node, the second message indicating that a DRB context has been established or modified at the second wireless communication node, wherein the first message includes first user plane address information of the DRB, and the second message includes second user plane address information of the DRB.

[0005] In another embodiment, the method performed by the second communication node includes: receiving a first message from a first wireless communication node requesting the establishment or modification of the context of a data radio bearer (DRB); and transmitting a second message to the first wireless communication node, the second message indicating that the context of the DRB has been established or modified at the second wireless communication node, wherein the first message includes first user plane address information of the DRB, and the second message includes second user plane address information of the DRB. Attached Figure Description

[0006] Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. The drawings are provided for illustrative purposes only and depict only exemplary embodiments of the invention to facilitate the reader's understanding of it. Therefore, the drawings should not be construed as limiting the breadth, scope, or applicability of the invention. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of illustration.

[0007] Figure 1 Examples of certain embodiments according to this disclosure are shown. Figure 1 The communication network base station shown has a centralized unit-distributed unit (CU-DU) separation structure.

[0008] Figure 2 Some embodiments according to this disclosure are shown in Figure 1 The illustrated base station demonstrates an exemplary functional division between the Centralized Unit (CU) and the Distributed Unit (DU).

[0009] Figure 3 Exemplary cellular communication networks according to some embodiments of the present disclosure are shown, in which the techniques disclosed herein can be implemented.

[0010] Figure 4 Examples of embodiments according to this disclosure are shown. Figure 3The exemplary block diagram of the base station shown is divided into a control plane of a centralized unit (CU-C), a user plane of a centralized unit (CU-U), and a distributed unit (DU).

[0011] Figure 5A , 5B 5C and 5C respectively illustrate some embodiments according to this disclosure, such as Figure 4 The exemplary block diagrams of CU-C, CU-U, and DU are shown.

[0012] Figure 6 Scenarios according to some embodiments of this disclosure are shown, in which, as Figure 4 The CU-C, CU-U, and DU of the base station shown cooperate to perform exemplary methods to establish or modify packet data unit (PDU) sessions.

[0013] Figure 7 Another scenario is illustrated according to some embodiments of this disclosure, in which, as Figure 4 The base station shown demonstrates an exemplary method for modifying a PDU session by having its CU-C, CU-U, and DU work together. Detailed Implementation

[0014] Various exemplary embodiments of this disclosure are described below with reference to the accompanying drawings to enable those skilled in the art to make and use this disclosure. It will be apparent to those skilled in the art that, after reading this disclosure, various changes or modifications can be made to the examples described herein without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely exemplary. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this disclosure. Therefore, those skilled in the art should understand that the methods and techniques disclosed herein present various steps or actions in a sample order, and unless otherwise expressly stated, this disclosure is not limited to the specific order or hierarchy presented.

[0015] Figure 1The fronthaul interfaces of such first and second network elements of BS 100 are shown. As shown, BS 100 is divided into first network element 110 and second network element 120. First network element 110 and second network element 120 communicate through fronthaul interface 130, wherein the fronthaul can be ideal or non-ideal depending on the latency. Ideal fronthaul transmission has a relatively small latency (e.g., tens to hundreds of microseconds). Non-ideal fronthaul transmission has a relatively large latency (e.g., milliseconds). Due to the difference between ideal and non-ideal fronthaul transmission, different network functions can be divided into first network element 110, i.e., CU; and second network element 120, i.e., DU, in different ways. In a CU-DU separated network architecture, latency-insensitive network functions can be placed in the CU; while latency-sensitive network functions can be placed in the DU. Accordingly, the CU and DU can have different hardware and structures for implementing different network functions.

[0016] For example, a first protocol entity (e.g., a radio resource control (RRC) entity) is located at the CU. The first protocol entity generates control signals, maintains the establishment, modification, and / or release of radio bearers, and maintains update parameters for the base station's second, third, and fourth protocol entities and the physical (PHY) layer. The second protocol entity has similar or enhanced functionality compared to the PDCP (Packet Data Convergence Protocol) function of an LTE system. The third protocol entity has similar or enhanced functionality compared to the RLC (Radio Link Control) function of an LTE system. The fourth protocol entity has similar or enhanced functionality compared to the MAC (Medium Access Control) function of an LTE system. The DU includes at least one of the following: the base station's second, third, and fourth protocol entities, the physical layer, and a radio frequency (RF) unit.

[0017] Figure 2 Exemplary functional partitioning between a first network element and a second network element (e.g., between CU110 and DU 120) according to certain embodiments of the present disclosure is illustrated. More specifically, Figure 2Eight possible functional partitioning options between CU 110 and DU 120 are shown, which will be described below. Option 1 (RRC / PDCP separation): This option's functional partitioning is similar to the 1A structure in a dual connection (DC). The RRC is located in the CU; the PDCP, RLC, MAC, PHY, and RF functions are located in the DU. That is, the entire UP is located in the DU; Option 2 (PDCP / RLC separation): This option's functional partitioning is similar to the 3C structure in a dual connection (DC). RRC and PDCP are located in the CU; RLC, MAC, PHY, and RF functions are located in the DU; Option 3 (RLC high-level / low-level separation): Low-level RLC (part of RLC functions), MAC, PHY, and RF are located in the DU; RRC, PDCP, and high-level RLC (part of RLC functions) functions are located in the CU; Option 4 (RLC-MAC separation): Part of MAC, PHY, and RF are located in the DU; PDCP and RLC functions are located in the CU; Option 5 (MAC internal separation): Some MAC functions (e.g., HARQ), PHY, and RF are located in the DU; other upper-level functions are located in the CU; Option 6 (MAC-PHY): Part of PHY and RF are located in the DU; RRC, PDCP, RLC, and MAC functions are located in the CU; Option 7 (PHY internal separation): Some PHY functions and RF are located in the DU; other upper-level functions are located in the CU; and Option 8 (PHY-RF separation): Part of RF is located in the DU; other upper-level functions are located in the CU.

[0018] Regarding option 2 discussed above, the PDCP located within the CU can be further separated into a control plane protocol (CP) and a user plane protocol (UP). In other words, the CP and UP portions of the PDCP reside in two distinct wireless communication nodes derived from the CU. In the following discussion, wireless communication nodes without presenting the CP and UP portions of the PDCP are referred to as "CU-C" and "CU-U," respectively.

[0019] However, to date, no research has been conducted on how CU-C and CU-U communicate with each other to manage (e.g., establish, delete, modify, etc.) Packet Data Unit (PDU) sessions. Therefore, a method and system are needed for CU-C and CU-U to cooperate in handling such scenarios to meet the expected requirements of 5G networks.

[0020] Figure 3Exemplary wireless communication networks 300 according to various embodiments of the present disclosure are illustrated, in which the techniques disclosed herein can be implemented. The exemplary communication network 300 includes base station (BS) 302 and user equipment (UE) 304 capable of communicating with each other via communication link 310 (e.g., a wireless communication channel), and virtual cell clusters 326, 330, 332, 334, 336, 338, and 340 covering a geographic area 301. Figure 3 In this disclosure, BS 302 and UE 304 are contained within the geographical boundary of cell 326. Each of the other cells (cells 330, 332, 334, 336, 338, and 340) may include at least one base station operating with its allocated bandwidth to provide sufficient radio coverage to its target users. For example, BS 302 may operate on its allocated channel transmission bandwidth to provide sufficient coverage to UE 304. BS 302 and UE 304 may communicate via downlink radio frame 318 and uplink radio frame 324, respectively. Each of radio frames 318 / 324 may be further divided into subframes 320 / 327, which may include data symbols 322 / 328. In this disclosure, base station (BS) 302 and user equipment (UE) 304 are described herein as non-limiting examples of “wireless communication devices or nodes” from which the methods disclosed herein can generally be practiced. According to various embodiments of this disclosure, such communication devices may be capable of wireless and / or wired communication.

[0021] As mentioned above, in a 5G network, the BS can be separated into CU and DU, wherein when using option 2, the CU can be further separated into CU-U and CU-C. According to certain embodiments of this disclosure, Figure 4 An exemplary block diagram of BS 302 according to certain embodiments of the present disclosure is shown, wherein BS 302 is divided into CU 410 and DU 420, and CU 410 is further divided into CU-C 410-1 and CU-U410-2. Although Figure 4The illustrated embodiment shows BS 302 divided into one CU-C, one CU-U, and one DU; however, it should be understood that BS 302 can be divided into one CU-C, multiple CU-Cs, and multiple DUs while remaining within the scope of this disclosure. CU-C 410-1 and CU-U 410-2 communicate with each other via E1 interface 430, and CU-C 410-1 and CU-U 410-2 communicate with DU 420 via F1-C interface 440 and F1-U interface 450, respectively. In some embodiments, the control planes of RRC and PDCP are located in CU-C 410-1; the user plane of PDCP is located in CU-U 410-2; and as described above, RLC, MAC, PHY, and RF are located in DU 420.

[0022] Figure 5A An exemplary block diagram of a CU-C 410-1 according to certain embodiments of the present disclosure is shown. The CU-C410-1 is an example of a device that can be configured to implement the various methods described, as will be discussed below. As shown, the CU-C410-1 includes a housing 501 comprising: a system clock 502, a processor 504, a memory 506, a transceiver 510 (including a transmitter 512 and a receiver 514), a power module 508, and a CU-C network connectivity module 520. In some embodiments, the components / modules mentioned above are coupled together via a bus system 524. The bus system 524 may include a data bus and, for example, a power bus, a control signal bus, and / or a status signal bus in addition to the data bus. It should be understood that the components / modules of the CU-C 410-1 can be operatively coupled to each other using any suitable technology and medium.

[0023] In some embodiments, system clock 502 provides processor 504 with timing signals for timing all operations of CU-C 510. Processor 504 controls the general operation of CU-C 510 and may include one or more processing circuits or modules, such as any combination of a central processing unit (CPU) and / or a general-purpose microprocessor, microcontroller, digital signal processor (DSP), field-programmable gate array (FPGA), programmable logic device (PLD), controller, state machine, gated logic, discrete hardware components, dedicated hardware finite state machine, or any other suitable circuitry, device, and / or structure capable of performing calculations or other data operations.

[0024] Memory 506, which may include read-only memory (ROM) and random access memory (RAM), can provide instructions and data to processor 504. A portion of memory 506 may also include non-volatile random access memory (NVRAM). Processor 504 typically performs logical and arithmetic operations based on program instructions stored in memory 506. Instructions stored in memory 506 (also referred to as software) can be executed by processor 504 to perform the methods described herein. Processor 504 and memory 506 together form a processing system that stores and executes software. As used herein, “software” means any type of instructions that can configure a machine or device to perform one or more desired functions or processes, whether referred to as software, firmware, middleware, microcode, etc. Instructions may include code (e.g., source code format, binary code format, executable code format, or any other suitable code format). When executed by one or more processors, the instructions cause the processing system to perform the various functions described herein.

[0025] Transceiver 510, including transmitter 512 and receiver 514, allows CU-C 410-1 to transmit and receive data from remote devices (e.g., CU-U 410-2, DU 420, etc.). In one embodiment, antenna 522 may be attached to housing 501 and electrically coupled to transceiver 510. In various embodiments, CU-C410-1 includes (not shown) multiple transmitters, multiple receivers, multiple transceivers, and / or multiple antennas. Transmitter 512 may be configured to wirelessly transmit packets with different packet types or functions, such packets being generated by processor 504. Similarly, receiver 514 is configured to receive packets with different packet types or functions, and processor 504 is configured to process multiple packets of different packet types. For example, processor 504 may be configured to determine the type of a packet and process the packet and / or its fields accordingly. In another embodiment, CU-C 410-1 can communicate with DU 420 via optical fiber communication, such that transmitter 512 and receiver 514 are respectively configured to transmit and receive signals via optical fiber.

[0026] Power module 508 may include a power source (such as one or more batteries) and a power regulator to supply power to... Figure 5A Each of the above modules provides regulated power. In some embodiments, if the CU-C410-1 is coupled to a dedicated external power source (e.g., a wall power outlet), the power module 508 may include a transformer and a power conditioner.

[0027] The CU-C network communication module 520 typically represents the hardware, software, firmware, processing logic, and / or other components of the CU-C 410-1, enabling bidirectional communication between the transceiver 510 and other network components and communication devices configured to communicate with the CU-C 410-1 (e.g., CU-U410-2, DU 420, etc.). For example, the CU-C network communication module 520 can generate messages including various information related to a UE, which is cooperatively served by the CU 410 (including CU-C 410-1 and CU-U 410-2) and DU 420. The CU-C network communication module 520 can transmit messages to the transmitter 512 and instruct the transmitter 512 to transmit messages to either the CU-U410-2 or DU 420, where the CU-C 410-1, together with the CU-U 410-2 and DU 420, can cooperate to act as the first base station in a wireless network. The detailed operation of CU-C 410-1 will be discussed further below.

[0028] Figure 5B and 5C Exemplary block diagrams of CU-U 410-2 and DU 420 according to some embodiments of the present disclosure are shown respectively. Examples of devices that can be configured to implement the various methods described are discussed below. Since the components of CU-U 410-2 and DU 420 are substantially similar to those described... Figure 5A The functions of the corresponding components of CU-C410-1 (except for CN-U network communication module 550 of CU-U 410-2 and DN network communication module 580 of DU 420) will not be repeated for similar components of CU-U 410-2 and DU420.

[0029] First refer to Figure 5B The CU-U 410-2 includes a housing 531, which includes a system clock 532, a processor 534, a memory 536, a transceiver 540 (including a transmitter 542 and a receiver 544), a power module 538, and the CU-C network connectivity module 550 described above. In some embodiments, the components / modules mentioned above are coupled together via a bus system 554. The bus system 554 may include a data bus as well as, for example, a power bus, a control signal bus, and / or a status signal bus in addition to the data bus. It should be understood that the components / modules of the CU-U 410-2 can be operatively coupled to each other using any suitable technology and medium. Refer then to... Figure 5CThe DU 420 includes a housing 561, which includes a system clock 562, a processor 564, a memory 566, a transceiver 570 (including a transmitter 572 and a receiver 574), a power module 568, and the aforementioned DU network connection module 580, wherein the above components / modules are coupled together via a bus system 584.

[0030] In some embodiments, the CU-U network communication module 550 typically represents the hardware, software, firmware, processing logic, and / or other components of the CU-U 410-2, enabling the transceiver 540 to conduct bidirectional communication with other network components and communication devices configured to communicate with the CU-U 410-2 (e.g., CU-C410-1). For example, the CU-U network communication module 550 can generate messages including various information related to a UE, which is cooperatively served by CU 410 (including CU-C 410-1 and CU-U 410-2) and DU 420. The CU-U network communication module 550 can transmit messages to a transmitter 542 and instruct the transmitter 542 to transmit messages to CU-C 410-1, wherein the CU-U 410-2, together with CU-C 410-1 and DU 420, cooperates to act as a first base station in a wireless network. The detailed operation of the CU-U 410-2 will be discussed in further detail below.

[0031] Similarly, the CU-C network communication module 580 typically represents the hardware, software, firmware, processing logic, and / or other components of the DU 420, enabling bidirectional communication between the transceiver 570 and other network components and communication devices configured to communicate with the DU 420 (e.g., the CU-C 410-1 or the UE). For example, the DU network communication module 580 can process messages including various information related to the UE mentioned above. The DU network communication module 580 can transmit messages to the transmitter 572 and instruct the transmitter 572 to transmit messages to the UE. The detailed operation of the DU 420 will be discussed further below. As used herein with respect to a particular operation or function, the terms “configured for,” “configured to,” and variations thereof refer to devices, components, circuits, structures, machines, signals, etc., that are physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0032] This disclosure provides various embodiments of systems and methods to illustrate how CU-C 410-1, CU-U 410-2, and DU 420 of BS 302 can operatively cooperate to manage (e.g., establish, modify, etc.) PDU sessions. Such establishment or modification of a PDU session can be initiated by a UE served by BS 302, or by the core network to which both UE 304 and BS 302 are connected. Generally, the purpose of establishing or modifying a PDU session is to assign or change resources on the Uu interface and the Next Generation User Plane Interface (NG-U) for the PDU session and the corresponding Quality of Service (QoS) flow, and to set up appropriate data radio bearers for a given UE.

[0033] Figure 6 The illustration shows a scenario according to certain embodiments of the present disclosure, in which CU-C 410-1, CU-U410-2, DU420 and core network 600 (such as Next Generation Core (NGC), or typically referred to as "5GC") collaboratively perform method 602 in order to enable the UE (e.g., 304, which is not in Figure 6 The method 602 provides certain embodiments of how CU-C 410-1 establishes or modifies a PDU session with CU-U 410-2, as shown in the diagram. The embodiments shown in 602 are merely examples. Therefore, it should be understood that any of the various operations may be omitted, reordered, and / or added while remaining within the scope of this disclosure.

[0034] Method 602 begins with operation 604, in which NGC 600 sends a control message to CU-C 410-1 requesting the establishment or modification of a PDU session. In some embodiments, such a control message may be a PDU session control signal, and as described above, NGC 600 may send the control message via the Next Generation (NG) interface in response to receiving a request from UE 304 or determining that a new PDU session needs to be established or an existing PDU session needs to be modified. The control message may include various information relating to the establishment or modification of the PDU session. For example, the control message may include: a session identifier (ID) for the PDU session, corresponding IDs for the QoS flows of one or more PDU sessions, corresponding Guaranteed Bit Rate (GBR) information for each of the QoS flows of one or more PDU sessions, and so on.

[0035] Method 602 continues to operation 606, wherein CU-C 410-1 sends a first message to CU-U 410-2 requesting the establishment or modification of the DRB context at CU-U 410-2. As mentioned above, each PDU session to be established or modified may include one or more QoS flows, and in some embodiments, the DRB may be included in the aforementioned PDU session, and CU-C 410-1 may map such one or more QoS flows to the DRB. Furthermore, CU-C 410-1 may include QoS-related information corresponding to the DRB (e.g., one or more QoS profiles), DRB allocation information, and the first user plane address information of the DRB in the first message, and via E1 interface 430 ( Figure 4 Send the first message to CU-U 410-2.

[0036] In some embodiments, DRB allocation information can indicate whether CU-C 410-1 is serving UE 304 via a dual connectivity (DC) configuration, and whether the DRB's Packet Data Convergence Protocol (PDCP) is located in CU-C 410-1. As used herein, the term "DC" generally refers to a radio communication configuration where multiple Rx / Tx UEs are configured to use radio resources provided by (i.e., served by) two different wireless communication nodes, one providing E-TURA (typically referred to as Long Term Evolution (LTE)) access and the other providing New Radio (NR) access. Generally, one of these wireless communication nodes is referred to as the primary node, and the other as the secondary node, with at least the primary node connected to the core network. Accordingly, in some embodiments, BS 302 is used cooperatively ( Figure 3 CU-C 410-1, CU-U 410-2 and DU 420 can be used as auxiliary nodes of the DC network, while another BS can be used as the master node of the DC network.

[0037] Depending on whether CU-C 410-1 is serving UE 304 via DC configuration and whether the corresponding PDCP of the DRB is located in CU-C 410-1, in some embodiments, the first user plane address information of the DRB included in the first message may differ. For example, when the first message indicates that CU-C 410-1 is not serving UE 304 via DC configuration, the first user plane address information of the DRB includes: the S1 / NG uplink (UL) General Packet Radio Service Technology Tunneling Protocol (GTP) Tunnel Endpoint Identifier (TEID) in the NGC; when the first message indicates that CU-C 410-1 is serving UE 304 via DC configuration and the DRB's PDCP is located in CU-C 410-1, the first user plane address information of the DRB includes: the S1 / NG ULGTP TEID in the NGC and the downlink (DL) GTP TEID in the master node of the DC network; and when the first message indicates that CU-C 410-1 is serving UE 304 via DC configuration and the DRB's PDCP is not located in CU-C 410-1, the first user plane address information of the DRB includes: the X2 / Xn UL GTP TEID in the master node of the DC network.

[0038] Method 602 continues to operation 608, wherein CU-U 410-2 sends a second message to CU-C 410-1, the second message indicating a response to a request to establish or modify a DRB context. In some embodiments, in response to receiving the first message, CU-U 410-2 allocates resources for the context of the DRB to be established or modified. More specifically, if CU-U 410-2 is able to successfully allocate resources for the DRB context by following the information included in the first message, CU-U 410-2 may send a second message to CU-C 410-1 including second user plane address information of the DRB to confirm the successful establishment or modification of the DRB context; and, on the other hand, if CU-U 410-2 is unable to successfully allocate resources for the DRB context by following the information included in the first message, CU-U 410-2 may send a second message to reject the establishment or modification of the DRB context.

[0039] In some embodiments, the second user plane address information of the DRB included in the second message may vary depending on whether CU-C 410-1 is serving UE 304 via DC configuration and whether the corresponding PDCP of the DRB is located in CU-C 410-1 as shown in the first message. For example, when the second message indicates that CU-C 410-1 is not serving UE304 via DC configuration, the DRB's second user plane address information includes: the S1 / NG downlink (DL) GTP TEID in CU-U 410-2 and the F1 UL GTP TEID in CU-U 410-2; when the first message indicates that CU-C 410-1 is serving UE304 via DC configuration and the DRB's PDCP is located in CU-C 410-1, the DRB's second user plane address information includes: the S1 / NG DL GTP TEID in CU-U 410-2; the X2 / Xn UL GTP TEID in the secondary node of the DC network; the X2 / XnDL forwarding the GTP TEID; the X2 / Xn UL forwarding the GTP TEID; and the F1 UL GTP TEID in CU-U 410-2; and when the first message indicates that CU-C When 410-1 is serving UE 304 via DC configuration and the DRB's PDCP is not located in CU-C 410-1, the DRB's second user plane address information includes: X2 / Xn DLGTP TEID in the secondary node of the DC network.

[0040] Based on the second message, in which, for example, resources for the DRB context have been successfully allocated by CU-U410-2, in some embodiments, a portion of the DRB may be referred to as successfully established or modified across CU-C 410-1 and CU-U 410-2. Accordingly, CU-C 410-1, DU 420, and NGC 600 may each perform one or more operations known to those skilled in the art to complete the establishment or modification of the PDU session, such operations being briefly described below. For example, method 600 proceeds to operation 610, in which CU-C 410-1 sends a request message to DU 420 to establish or modify the context of UE 304 at DU 420. Then proceeds to operation 612, in which DU 420 sends a response message to CU-C 410-1, the response message indicating whether the context of UE 304 has been successfully established or modified at DU 420. And proceed to operation 614, in which CU-C 410-1 sends a response message to NGC, the response message indicating whether the PDU session has been successfully established or modified.

[0041] Figure 7Another scenario according to certain embodiments is illustrated, in which CU-C 410-1, CU-U 410-2, DU420 and NGC600 cooperate to perform method 702 in order to modify the UE (e.g., not in Figure 7 The PDU session between 304 and NGC 600 is shown in the diagram. (Similar to...) Figure 6 The method described in 602 is different, in Figure 7 In the illustrated embodiment, CU-U 410-2 initiates a request to change the context of the DRB of the PDU session. The illustrated embodiment of method 702 is merely an example. Therefore, it should be understood that any of the various operations can be omitted, reordered, and / or added while still remaining within the scope of this disclosure.

[0042] Method 702 begins with operation 704, in which CU-U 410-2 sends a first message to CU-C 410-1, the first message requesting modification of the DRB context at CU-U 410-2. In some embodiments, CU-U 410-2 may include QoS-related information corresponding to the DRB (e.g., one or more QoS profiles), DRB allocation information, and the first user plane address information of the DRB in the first message, and send the first message to CU-C 410-1 via E1 interface 430. Figure 4 ).

[0043] In some embodiments, DRB allocation information may indicate whether CU-C 410-1 is serving UE 304 via dual connectivity (DC) configuration and whether the DRB's packet data convergence protocol (PDCP) is located in CU-C 410-1.

[0044] In some embodiments, the first user plane address information of the DRB included in the first message may vary depending on whether CU-C 410-1 is serving UE 304 via DC configuration and whether the corresponding PDCP of the DRB is located in CU-C 410-1. For example, when the first message indicates that CU-C 410-1 is not serving UE 304 via DC configuration, the first user plane address information of the DRB includes: the S1 / NG uplink (UL) General Packet Radio Service Technology Tunneling Protocol (GTP) Tunnel Endpoint Identifier (TEID) in the NGC; when the first message indicates that CU-C 410-1 is serving UE 304 via DC configuration and the DRB's PDCP is located in CU-C 410-1, the first user plane address information of the DRB includes: the S1 / NG ULGTP TEID in the NGC and the downlink (DL) GTP TEID in the master node of the DC network; and when the first message indicates that CU-C 410-1 is serving UE 304 via DC configuration and the DRB's PDCP is not located in CU-C 410-1, the first user plane address information of the DRB includes: the X2 / Xn UL GTP TEID in the master node of the DC network.

[0045] Method 702 continues to operation 706, in which CU-C 410-1 sends a second message to CU-U 410-2, the second message indicating a response to a request to modify the context of the DRB. In some embodiments, CU-C 410-1 modifies the context of the DRB in response to receiving the first message. More specifically, if CU-C 410-1 can successfully modify the context of the DRB by following the information included in the first message, CU-C 410-1 may send a second message to CU-U 410-2, the second message including the successfully modified context of the DRB and the address information of the corresponding second user plane of the DRB, to confirm the successful establishment or modification of the DRB context; and, on the other hand, if CU-C 410-1 cannot successfully modify the context of the DRB by following the information included in the first message, CU-C 410-1 may send a second message to reject the modification of the DRB context.

[0046] In some embodiments, the second user plane address information of the DRB included in the second message may vary depending on whether CU-C 410-1 is serving UE 304 via DC configuration and whether the corresponding PDCP of the DRB is located in CU-C 410-1 as shown in the first message. For example, when the second message indicates that CU-C 410-1 is not serving UE304 via DC configuration, the DRB's second user plane address information includes: the S1 / NG downlink (DL) GTP TEID in CU-U 410-2 and the F1 UL GTP TEID in CU-U 410-2; when the first message indicates that CU-C 410-1 is serving UE304 via DC configuration and the DRB's PDCP is located in CU-C 410-1, the DRB's second user plane address information includes: the S1 / NG DL GTP TEID in CU-U 410-2; the X2 / Xn DL GTP TEID in the secondary node of the DC network; the X2 / Xn DL forwarding the GTP TEID; the X2 / Xn UL forwarding the GTP TEID; and the F1 UL GTP TEID in CU-U 410-2; and when the first message indicates that CU-C When 410-1 is serving UE 304 via DC configuration and the DRB's PDCP is not located in CU-C 410-1, the DRB's second user plane address information includes: X2 / Xn UL GTP TEID in the secondary node of the DC network.

[0047] Based on the second message, in which, for example, resources for the DRB context have been successfully modified by CU-C410-1, in some embodiments, a portion of the DRB may be referred to as successfully established or modified across CU-C410-1 and CU-U 410-2. Accordingly, CU-C 410-1, DU 420, and NGC 600 may each perform one or more operations known to those skilled in the art to complete the establishment or modification of the PDU session. Such operations will be briefly described below. For example, method 700 proceeds to operation 708, in which CU-C 410-1 sends a request message to DU 420 to modify the context of UE 304 at DU 420. Then, operation 710 proceeds to operation 710, in which DU 420 sends a response message to CU-C 410-1 indicating whether the context of UE 304 has been successfully modified in DU 420. In operation 712, CU-C 410-1 sends a request message to NGC requesting modification of the PDU session; and in operation 714, NGC 600 sends a response message to CU-C 410-1 indicating whether the PDU session has been successfully modified.

[0048] While various embodiments of the invention have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, various illustrations may depict exemplary architectures or configurations, provided to enable those skilled in the art to understand the exemplary features and functions of the invention. However, those skilled in the art should understand that the invention is not limited to the exemplary architectures or configurations shown, but can be implemented using a variety of alternative architectures and configurations.

[0049] Furthermore, those skilled in the art will understand that one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0050] It should also be understood that any references to elements using designations (such as "first," "second," etc.) herein do not generally restrict the number or order of those elements. Rather, these names serve as a convenient means of distinguishing two or more elements or instances of elements. Therefore, references to the first and second elements do not imply that only two elements can be used, or that the first element must somehow precede the second element.

[0051] Furthermore, those skilled in the art will understand that any and all different technologies can be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols referenced throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0052] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of programs or design code containing instructions (which may be referred to herein as "software" or "software module" for convenience), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been generally described above in accordance with their functions. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functions in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure.

[0053] According to various embodiments, processors, devices, components, circuits, structures, machines, modules, etc., may be configured to perform one or more of the functions described herein. As used herein in connection with a particular operation or function, the terms "configured to" or "configured for" refer to processors, devices, components, circuits, structures, machines, modules, etc., that are physically constructed, programmed, and / or arranged to perform the specified operation or function.

[0054] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or executed by an integrated circuit (IC), which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communication with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors combined with a DSP core, or any other suitable configuration to perform the functions described herein.

[0055] If implemented as software, the functionality can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, with communication media including any medium capable of transferring a computer program or code from one place to another. Storage media can be any available medium that is accessible to a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and is accessible to a computer.

[0056] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the relevant functions described herein. Furthermore, for the purposes of discussion, various modules are described as discrete modules; however, it will be apparent to those skilled in the art that two or more modules can be combined to form a single module that performs the relevant functions according to embodiments of the invention.

[0057] Additionally, in embodiments of the present invention, memory or other storage devices and communication components may be used. It should be understood that, for clarity, embodiments of the present invention have been described above with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains may be used without departing from the present invention. For example, a function illustrated as being performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing said function and do not indicate a strict logical or physical structure or organization.

[0058] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be endowed with the broadest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A method performed by a first wireless communication node, the method comprising: Receive requests from the core network to modify or establish a Packet Data Unit (PDU) session between the core network and the user equipment (UE); In response to a request to modify or establish the PDU session, a first message is transmitted to the second wireless communication node, the first message requesting the establishment or modification of the context of the data radio bearer (DRB) within the second wireless communication node; A second message is received from the second wireless communication node, indicating that the context of the DRB has been established or modified on the second wireless communication node. Wherein, the first message includes the first user plane address information of the DRB, and the second message includes the second user plane address information of the DRB; and Send a response to the core network indicating that the PDU session has been established or modified.

2. The method according to claim 1, wherein: The first wireless communication node serves as the control plane of the centralized unit; and The second wireless communication node serves as the user plane of the centralized unit.

3. The method according to claim 1, wherein the first user plane address information of the DRB includes at least one of the following: S1 / NG uplink UL General Packet Radio Service Technology Tunneling Protocol GTP Tunnel Endpoint Identifier (TEID) in the next-generation core NGC; Downlink DL GTP TEID in the master node Mnode of the dual-connectivity DC configuration; and X2 / Xn UL GTP TEID in Mnode.

4. The method of claim 3, wherein the second user plane address information of the DRB includes at least one of the following: S1 / NG downlink DL GTP TEID at the second wireless communication node; F1 UL GTP TEID at the second wireless communication node; X2 / Xn UL GTP TEID in the auxiliary node Snode of the DC network; Forward the X2 / Xn DL of the GTP tunnel endpoint; Forwarding the X2 / Xn UL of the GTP tunnel endpoint; and X2 / Xn DL GTP TEID in the Snode.

5. The method of claim 4, wherein the first message indicates whether the first wireless communication node serves the user equipment via a dual-connectivity DC, and whether the packet data convergence protocol (PDCP) of the DRB is located in the first wireless communication node.

6. The method of claim 5, wherein in response to a first message indicating that the first wireless communication node does not serve the user equipment via the DC, the first user plane address information of the DRB includes: S1 / NG UL GTP TEID in the NGC.

7. The method of claim 5, wherein in response to a first message indicating that the first wireless communication node serves the user equipment via the DC and that the PDCP of the DRB is located in the first wireless communication node, the first user plane address information of the DRB includes: S1 / NG UL GTP TEID in the NGC; as well as DL GTP TEID in the Mnode.

8. The method of claim 5, wherein in response to a first message indicating that the first wireless communication node is serving the user equipment via the DC and that the PDCP of the DRB is not located in the first wireless communication node, the first user plane address information of the DRB includes: X2 / Xn UL GTP TEID in the Mnode.

9. The method of claim 5, wherein in response to a first message indicating that the first wireless communication node does not serve the user equipment via the DC, the second user plane address information of the DRB includes: S1 / NG DL GTP TEID at the second wireless communication node; as well as F1 UL GTP TEID at the second wireless communication node.

10. The method of claim 5, wherein in response to a first message indicating that the first wireless communication node is serving the user equipment via the DC and that the PDCP of the DRB is located in the first wireless communication node, the second user plane address information of the DRB includes: S1 / NG DL GTP TEID at the second wireless communication node; X2 / Xn UL GTP TEID in the auxiliary node Snode; Forward the X2 / Xn DL of GTP TEID; Forwarding GTP TEID's X2 / Xn UL; and F1 UL GTP TEID at the second wireless communication node.

11. The method of claim 5, wherein in response to a first message indicating that the first wireless communication node is serving the user equipment via the DC and that the PDCP of the DRB is located in the first wireless communication node, the second user plane address information of the DRB includes: X2 / Xn DL GTP TEID in the auxiliary node Snode.

12. A non-transitory computer-readable medium having stored thereon computer-executable instructions for performing the method according to any one of claims 1 to 11.

13. A method performed by a second wireless communication node, the method comprising: In response to a request to modify or establish a Packet Data Unit (PDU) session between the core network and the User Equipment (UE), a first message is received from a first wireless communication node, the first message requesting the establishment or modification of the context of a Data Radio Bearer (DRB) within the second wireless communication node; A second message is transmitted to the first wireless communication node, the second message indicating that the context of the DRB has been established or modified at the second wireless communication node; as well as The first wireless communication node sends a response to the core network indicating that the PDU session has been established or modified. The first message includes the first user plane address information of the DRB, and the second message includes the second user plane address information of the DRB.

14. The method of claim 13, wherein: The first wireless communication node serves as the control plane of the centralized unit; and The second wireless communication node serves as the user plane of the centralized unit.

15. The method of claim 13, wherein the first user plane address information of the DRB includes at least one of the following: S1 / NG uplink UL General Packet Radio Service Technology Tunneling Protocol GTP Tunnel Endpoint Identifier (TEID) in the next-generation core NGC; Downlink DLGTP TEID in the master node (Mnode) of the dual-connectivity DC network; and X2 / Xn UL GTP TEID in Mnode.

16. The method of claim 15, wherein the second user plane address information of the DRB includes at least one of the following: S1 / NG DL GTP TEID at the second wireless communication node; F1 UL GTP TEID at the second wireless communication node; X2 / Xn UL GTP TEID in the auxiliary node Snode of the DC network; Forward the X2 / Xn DL of the GTP tunnel endpoint; Forwarding the X2 / Xn UL of the GTP tunnel endpoint; and X2 / Xn DL GTP TEID in the Snode.

17. The method of claim 16, wherein the first message indicates whether the first wireless communication node is serving a user equipment via a dual-connectivity DC, and whether the packet data convergence protocol (PDCP) of the DRB is located in the first wireless communication node.

18. The method of claim 17, wherein in response to a first message indicating that the first wireless communication node does not serve the user equipment via the DC, the first user plane address information of the DRB includes: S1 / NG UL GTP TEID in the NGC.

19. The method of claim 17, wherein in response to a first message indicating that the first wireless communication node is serving the user equipment via the DC and that the PDCP of the DRB is located in the first wireless communication node, the first user plane address information of the DRB includes: S1 / NG UL GTP TEID in the NGC; as well as DL GTP TEID in the Mnode.

20. The method of claim 17, wherein in response to a first message indicating that the first wireless communication node is serving the user equipment via the DC and that the PDCP of the DRB is not located in the first wireless communication node, the first user plane address information of the DRB includes: X2 / Xn UL GTP TEID in the Mnode.

21. The method of claim 17, wherein in response to a first message indicating that the first wireless communication node does not serve the user equipment via the DC, the second user plane address information of the DRB includes: S1 / NG DL GTP TEID at the second wireless communication node; as well as F1 UL GTP TEID at the second wireless communication node.

22. The method of claim 17, wherein in response to a first message indicating that the first wireless communication node is serving the user equipment via the DC and that the PDCP of the DRB is located in the first wireless communication node, the second user plane address information of the DRB includes: S1 / NG DL GTP TEID at the second wireless communication node; X2 / Xn UL GTP TEID in the auxiliary node Snode; Forward the X2 / Xn DL of GTP TEID; Forwarding GTP TEID via X2 / Xn UL; and F1 UL GTP TEID at the second wireless communication node.

23. The method of claim 17, wherein in response to a first message indicating that the first wireless communication node is serving the user equipment via the DC and that the PDCP of the DRB is located in the first wireless communication node, the second user plane address information of the DRB includes: X2 / Xn DL GTP TEID in the auxiliary node Snode.

24. A non-transitory computer-readable medium having stored thereon computer-executable instructions for performing the method according to any one of claims 13 to 23.

Images