Entity configuration method, apparatus and system, CU-U

Abstract

The application provides an entity configuration method, device and system, and CU-U; the entity configuration method comprises the following steps: acquiring specified information used for configuring each packet data convergence protocol (PDCP) entity for processing a data radio bearer through an Xn interface, wherein the Xn interface is an interface between a control plane PDCP entity (CU-C) and a user plane PDCP entity (CU-U); and performing a configuration operation on each PDCP entity according to the specified information. Through the application, the problem of how to realize the configuration of the CU-U protocol entity is solved, and centralized service convergence is realized.

Description

[0001] This application is a divisional application of application number "201710032552.4", application date "January 16, 2017", and invention title "Entity Configuration Method, Apparatus and System, CU-U". Technical Field

[0002] This invention relates to the field of wireless communication, and more specifically, to a physical configuration method, apparatus, system, and CU-U. Background Technology

[0003] In fifth-generation (5G) mobile communication, massive connectivity and higher user speed requirements pose significant challenges to the transmission capacity of the Common Public Radio Interface (CPRI), the fronthaul interface between the Building Baseband Unit (BBU) and the Remote Radio Unit (RRU) in Long Term Evolution (LTE). Because the CPRI interface transmits IQ signals processed by physical layer coding and modulation, it has high requirements for transmission latency and bandwidth. If 5G air interface speeds increase to tens of Gbps, the traffic demand of the CPRI interface will rise to the Tbps level, placing enormous pressure on network deployment costs and complexity. Therefore, in 5G, the fronthaul interface partitioning method needs to be redefined. This partitioning should consider factors such as transmission capacity, transmission latency, and ease of deployment. For example, considering non-ideal fronthaul transmission, latency-insensitive network functions are placed in the first network element (e.g., the Centralized Unit (CU)), while latency-sensitive network functions are placed in the second network element (e.g., the Distributed Unit (DU)). The interface between the first and second network elements, which transmits data via ideal and / or non-ideal fronthaul, is called the forward interface. Figure 1 This is a schematic diagram of the fronthaul interface between the first network element and the second network element, as shown below. Figure 1 As shown.

[0004] The first protocol entity (such as the Radio Resource Control (RRC) entity) is located in the first network element. This entity generates control signaling, maintains the establishment and / or modification and / or release of radio bearers, and maintains parameter updates for the second, third, and fourth protocol entities and the physical layer. The second protocol entity functions similarly to and enhanced with the Packet Data Convergence Protocol (PDCP) of LTE. A user can define multiple PDCP entities, and each PDCP entity carrying user plane data can be configured. Each PDCP entity carries data for one radio bearer. Depending on the data carried by the radio bearer, the PDCP entity corresponds to either the control plane or the user plane. The third protocol entity functions similarly to and enhanced with the Radio Link Control (RLC) of LTE. The fourth protocol entity functions similarly to and enhanced with the Medium Access Control (MAC) of LTE. The second network element includes at least one of the following: a second protocol entity, a third protocol entity, a fourth protocol entity, a physical layer, or a radio frequency unit. The first and second network elements communicate via a fronthaul interface. Figure 2 This is a possible functional partitioning diagram between the first network element and the second network element. The possible functional partitioning for CU-DU separation is as follows: Figure 2 As shown.

[0005] It should be noted that the control plane PDCP entity and the user plane PDCP entity in the CU may be separate, that is, the two PDCPs of the user plane and the control plane are located in two different CUs. For ease of description, these two CUs are referred to as CU-C and CU-U, thus realizing the separation of user plane data and control plane data. Figure 3 This is a schematic diagram illustrating the separation of control plane data and user plane data for the first network element, as shown below. Figure 3 As shown.

[0006] Assume there is an Xn interface between CU-C and CU-U, and a forward interface NGx between CU and DU. The interface between CU-C and DU is called NGx-C, and the interface between CU-U and DU is called NGx-U. Therefore, how to configure the CU-U protocol entity is the current problem that needs to be solved.

[0007] There is currently no effective solution to the aforementioned technical problems in the related technologies. Summary of the Invention

[0008] This invention provides an entity configuration method, apparatus, system, and CU-U to at least address the problem of how to configure CU-U protocol entities in related technologies.

[0009] According to an embodiment of the present invention, an entity configuration method is provided, comprising: obtaining specified information for configuring each Packet Data Convergence Protocol (PDCP) entity that processes data radio bearers through an Xn interface, wherein the Xn interface is an interface between the control plane PDCP entity CU-C and the user plane PDCP entity CU-U; and performing configuration operations on each PDCP entity according to the specified information.

[0010] Optionally, the specified information includes at least one of the following: Protocol Data Unit (PDU) session information, and user plane configuration information.

[0011] Optionally, when the specified information includes the PDU session information, configuring each PDCP entity according to the specified information includes: determining user plane configuration information corresponding to the obtained PDU session information based on the obtained PDU session information and the correspondence between the PDU session information and the user plane configuration information; and configuring each PDCP entity according to the user plane configuration information corresponding to the obtained PDU session information.

[0012] Optionally, when the specified information includes the user plane configuration information, configuring each PDCP entity according to the specified information includes: directly configuring each PDCP entity according to the user plane configuration information.

[0013] Optionally, when the PDU session information is the information required to establish a PDU session in the PDU session establishment process, the PDU session information includes at least one of the following: session identifier ID, one or more data stream IDs in a single session, QoS information of non-guaranteed code rate (Non-GBR) services corresponding to one or more data streams, QoS information of guaranteed code rate (GBR) services corresponding to one or more data streams, and Xn interface identification terminal flag information.

[0014] Optionally, after configuring each PDCP entity according to the specified information, the method further includes: sending a PDU session establishment success message to the CU-C, wherein the PDU session establishment success message carries PDU session information that has been successfully configured; wherein the PDU session information that has been successfully configured includes at least one of the following: session ID, one or more data stream IDs that have been successfully configured in a single session, Xn interface identification terminal flag information, one or more data stream IDs and configuration failure reasons that have failed in a single session; or, sending a PDU session establishment failure message to the CU-C, wherein the PDU session establishment failure message includes at least one of the following: user plane configuration failure reason, Xn interface identification terminal flag information.

[0015] Optionally, when the PDU session information is the PDU session information to be modified in the PDU session modification process, the PDU session information includes at least one of the following: session identifier ID, one or more data stream IDs to be added in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be added, QoS information of the GBR service corresponding to the one or more data streams to be added, one or more data stream IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be modified, QoS information of the GBR service corresponding to the one or more data streams to be modified, one or more data stream IDs to be deleted in a single session, and the Xn interface identification terminal flag information.

[0016] Optionally, after configuring each PDCP entity according to the specified information, the method further includes: sending a PDU session modification success message to the CU-C, wherein the PDU session modification success message carries PDU session information that successfully completed the configuration modification; wherein the PDU session information that successfully completed the configuration modification includes at least one of the following: session ID, one or more data stream IDs that successfully completed the user plane configuration modification in a single session, one or more data stream IDs that failed to complete the user plane configuration modification in a single session, the reason for the modification failure, and the identification information of the terminal identified by the Xn interface; or, sending a PDU session modification failure message to the CU-C, wherein the PDU session modification failure message includes: the reason for the failure of the PDU session user plane configuration and the identification information of the terminal identified by the Xn interface.

[0017] Optionally, when the PDU session information is the PDU session information to be deleted in the PDU session deletion process, the PDU session information includes at least one of the following: session ID, session deletion reason, and Xn interface identification terminal identification information.

[0018] Optionally, after configuring each PDCP entity according to the specified information, the method further includes: sending a PDU session deletion success message to the CU-C, wherein the PDU session deletion success message includes at least one of the following: the session ID of the successfully deleted session and the identification information of the Xn interface identifying the terminal.

[0019] Optionally, the user plane configuration information is the user plane configuration information in the PDU session establishment process, wherein the user plane configuration information includes at least one of the following: the index ID of each PDCP entity to be configured and the configuration information of each PDCP entity to be configured.

[0020] Optionally, the configuration information for each PDCP entity to be configured includes at least one of the following: whether the PDCP protocol used by each PDCP entity requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Layer (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information.

[0021] Optionally, after configuring each PDCP entity according to the specified information, the method further includes: sending a configuration completion confirmation message to the CU-C, wherein the configuration completion confirmation message includes: index information of one or more successfully configured PDCP entities; or, sending configuration failure information to the CU-C, wherein the configuration failure information includes: the reason for the configuration failure.

[0022] Optionally, obtaining specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data radio bearer via the Xn interface includes: obtaining specified information from the CU-C via the Xn interface; wherein, the specified information includes PDU session-related information; the PDU session-related information is obtained by the CU-C from the core network via the NG interface, and the PDU session-related information includes at least one of the following: session ID, one or more data stream IDs in a single session, QoS information of non-guaranteed code rate (Non-GBR) services corresponding to one or more data streams, and QoS information of guaranteed code rate (GBR) services corresponding to one or more data streams; wherein, the NG interface is the interface between the CU-U and the core network.

[0023] Optionally, the user plane configuration information is the user plane configuration information to be modified in the PDU session modification process, wherein the user plane configuration information includes at least one of the following: the index ID of each PDCP entity to be added and the configuration information of each PDCP entity to be added; the index ID of each PDCP entity to be modified and the configuration information of each PDCP entity to be modified; and the index ID of each PDCP entity to be deleted.

[0024] Optionally, the configuration information for each PDCP entity to be added includes at least one of the following: whether the PDCP protocol used by each PDCP entity to be added requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Layer Control (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information; the configuration information for each PDCP entity to be modified includes at least one of the following: whether the PDCP protocol used by each PDCP entity to be added requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Layer Control (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information.

[0025] Optionally, after configuring each PDCP entity according to the specified information, the method further includes: sending a configuration completion confirmation message to the CU-C, wherein the configuration completion confirmation message includes: one or more successfully configured PDCP entity index information, one or more PDCP entity index information whose configuration modification failed, and the reason for the modification failure; or, sending configuration failure information to the CU-C, wherein the configuration failure information includes: the reason for the configuration failure.

[0026] Optionally, obtaining specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data radio bearer via the Xn interface includes: obtaining specified information from the CU-C via the Xn interface; wherein, the specified information includes PDU session-related information, which is obtained by the CU-C from the core network via the NG interface, wherein the PDU session-related information includes at least one of the following: session identifier ID, one or more data stream IDs to be added in a single session, QoS information of the Non-GBR service corresponding to one or more data streams to be added, QoS information of the GBR service corresponding to one or more data streams to be added, one or more data stream IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to one or more data streams to be modified, QoS information of the GBR service corresponding to one or more data streams to be modified, and one or more data stream IDs to be deleted in a single session.

[0027] Optionally, the user plane configuration information is the user plane configuration information to be deleted in the PDU session deletion process, wherein the user plane configuration information includes at least one of the following: the index ID and deletion reason of each PDCP entity to be deleted.

[0028] Optionally, after configuring each PDCP entity according to the specified information, the method further includes: sending a user plane configuration deletion success message to the CU-C, wherein the user plane configuration deletion success message includes: the index ID of the successfully deleted PDCP entity.

[0029] Optionally, obtaining specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data radio bearer via the Xn interface includes: obtaining specified information from the CU-C via the Xn interface, wherein the specified information includes PDU session deletion information, wherein the PDU session deletion information is obtained by the CU-C from the core network via the NG interface, wherein the PDU session deletion information includes at least one of the following: session ID and session deletion reason.

[0030] According to an embodiment of the present invention, an entity configuration apparatus is provided, comprising: an acquisition module, configured to acquire specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of a processing data radio bearer via an Xn interface, wherein the Xn interface is an interface between a control plane PDCP entity CU-C and a user plane PDCP entity CU-U; and a configuration module, configured to perform configuration operations on each PDCP entity according to the specified information.

[0031] Optionally, the specified information includes at least one of the following: Protocol Data Unit (PDU) session information, and user plane configuration information.

[0032] Optionally, if the specified information includes the PDU session information, the configuration module is further configured to determine the user plane configuration information corresponding to the obtained PDU session information based on the obtained PDU session information and the correspondence between the PDU session information and the user plane configuration information; and to perform configuration operations on each PDCP entity based on the user plane configuration information corresponding to the obtained PDU session information.

[0033] Optionally, if the specified information includes the user plane configuration information, the configuration module is further configured to directly perform configuration operations on each PDCP entity based on the user plane configuration information.

[0034] According to an embodiment of the present invention, a user plane packet data convergence protocol PDCP entity CU-U is provided, comprising: a radio frequency module, configured to obtain specified information for configuring each packet data convergence protocol PDCP entity for processing data radio bearers via an Xn interface, wherein the Xn interface is an interface between the control plane PDCP entity CU-C and the user plane PDCP entity CU-U; and a processor, configured to perform configuration operations on each PDCP entity according to the specified information.

[0035] Optionally, the specified information includes at least one of the following: Protocol Data Unit (PDU) session information, and user plane configuration information.

[0036] Optionally, if the specified information includes the PDU session information, the processor is further configured to determine user plane configuration information corresponding to the acquired PDU session information based on the acquired PDU session information and the correspondence between the PDU session information and the user plane configuration information; and to perform configuration operations on each PDCP entity based on the user plane configuration information corresponding to the acquired PDU session information.

[0037] Optionally, if the specified information includes the user plane configuration information, the processor is further configured to directly perform configuration operations on each PDCP entity based on the user plane configuration information.

[0038] Optionally, when the PDU session information is the information required to establish a PDU session in the PDU session establishment process, the PDU session information includes at least one of the following: session identifier ID, one or more data stream IDs in a single session, QoS information of non-guaranteed code rate (Non-GBR) services corresponding to one or more data streams, QoS information of guaranteed code rate (GBR) services corresponding to one or more data streams, and Xn interface identification terminal flag information.

[0039] Optionally, the radio frequency module is further configured to send a PDU session establishment success message to the CU-C after performing configuration operations on each PDCP entity according to specified information, wherein the PDU session establishment success message carries PDU session information that has been successfully configured; wherein the PDU session information that has been successfully configured includes at least one of the following: session ID, one or more data stream IDs that have been successfully configured in a single session, Xn interface identification terminal flag information, one or more data stream IDs and configuration failure reasons that have failed in a single session; or, send a PDU session establishment failure message to the CU-C, wherein the PDU session establishment failure message includes at least one of the following: user plane configuration failure reason, Xn interface identification terminal flag information.

[0040] Optionally, when the PDU session information is the PDU session information to be modified in the PDU session modification process, the PDU session information includes at least one of the following: session identifier ID, one or more data stream IDs to be added in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be added, QoS information of the GBR service corresponding to the one or more data streams to be added, one or more data stream IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be modified, QoS information of the GBR service corresponding to the one or more data streams to be modified, one or more data stream IDs to be deleted in a single session, and the Xn interface identification terminal flag information.

[0041] Optionally, the radio frequency module is further configured to send a PDU session modification success message to the CU-C after performing a configuration operation on each PDCP entity according to specified information, wherein the PDU session modification success message carries PDU session information on which the configuration modification was successfully completed; wherein the PDU session information on which the configuration modification was successfully completed includes at least one of the following: session ID, one or more data stream IDs on which the user plane configuration modification was successfully completed in a single session, one or more data stream IDs on which the user plane configuration modification failed in a single session, the reason for the modification failure, and the identification information of the terminal identified by the Xn interface; or, send a PDU session modification failure message to the CU-C, wherein the PDU session modification failure message includes: the reason for the user plane configuration failure of the PDU session and the identification information of the terminal identified by the Xn interface.

[0042] Optionally, when the PDU session information is the PDU session information to be deleted in the PDU session deletion process, the PDU session information includes at least one of the following: session ID, session deletion reason, and Xn interface identification terminal identification information.

[0043] Optionally, the radio frequency module is configured to send a PDU session deletion success message to the CU-C after performing a configuration operation on each PDCP entity according to specified information, wherein the PDU session deletion success message includes at least one of the following: the session ID of the successfully deleted session and the identification information of the Xn interface identifying the terminal.

[0044] Optionally, the user plane configuration information is the user plane configuration information in the PDU session establishment process, wherein the user plane configuration information includes at least one of the following: the index ID of each PDCP entity to be configured and the configuration information of each PDCP entity to be configured.

[0045] Optionally, the radio frequency module is further configured to send a configuration completion confirmation message to the CU-C after performing configuration operations on each PDCP entity according to specified information, wherein the configuration completion confirmation message includes: index information of one or more successfully configured PDCP entities; or, send configuration failure information to the CU-C, wherein the configuration failure information includes: the reason for configuration failure; wherein the NG interface is the interface between the CU-U and the core network.

[0046] Optionally, the user plane configuration information is the user plane configuration information to be modified in the PDU session modification process, wherein the user plane configuration information includes at least one of the following: the index ID of each PDCP entity to be added and the configuration information of each PDCP entity to be added; the index ID of each PDCP entity to be modified and the configuration information of each PDCP entity to be modified; and the index ID of each PDCP entity to be deleted.

[0047] Optionally, the radio frequency module is configured to send a configuration completion confirmation message to the CU-C after performing a configuration operation on each PDCP entity according to specified information. The configuration completion confirmation message includes: index information of one or more successfully configured PDCP entities, index information of one or more PDCP entities whose configuration modification failed, and the reason for the modification failure; or, it sends configuration failure information to the CU-C, wherein the configuration failure information includes: the reason for the configuration failure.

[0048] Optionally, the user plane configuration information is the user plane configuration information to be deleted in the PDU session deletion process, wherein the user plane configuration information includes at least one of the following: the index ID and deletion reason of each PDCP entity to be deleted.

[0049] Optionally, the radio frequency module is also configured to send a user plane configuration deletion success message to the CU-C after performing a configuration operation on each PDCP entity according to specified information, wherein the user plane configuration deletion success message includes: the index ID of the PDCP entity that was successfully deleted.

[0050] According to an embodiment of the present invention, an entity configuration system is provided, comprising: a control plane Packet Data Convergence Protocol (PDCP) entity CU-C, a user plane PDCP entity CU-U, and an Xn interface, wherein the Xn interface is an interface between CU-C and CU-U; CU-C is configured to send specified information for configuring each PDCP entity processing data radio bearer to CU-U via the Xn interface; CU-U is configured to receive the specified information and perform configuration operations on each PDCP entity according to the specified information.

[0051] Optionally, CU-U is further configured to send a PDU session establishment success message to CU-C after performing configuration operations on each PDCP entity according to specified information, wherein the PDU session establishment success message carries PDU session information that has been successfully configured; wherein the PDU session information that has been successfully configured includes at least one of the following: session ID, one or more data flow IDs that have been successfully configured in a single session, Xn interface identification terminal flag information, one or more data flow IDs and configuration failure reasons that have failed in a single session; or, send a PDU session establishment failure message to CU-C, wherein the PDU session establishment failure message includes at least one of the following: user plane configuration failure reason, Xn interface identification terminal flag information.

[0052] Optionally, after performing configuration operations on each PDCP entity according to specified information, CU-U also sends a PDU session modification success message to CU-C, wherein the PDU session modification success message carries PDU session information that successfully completed the configuration modification; wherein the PDU session information that successfully completed the configuration modification includes at least one of the following: session ID, one or more data stream IDs that successfully completed the user plane configuration modification in a single session, one or more data stream IDs that failed to complete the user plane configuration modification in a single session, the reason for the modification failure, and the identification information of the terminal identified by the Xn interface; or, sending a PDU session modification failure message to CU-C, wherein the PDU session modification failure message includes: the reason for the failure of the PDU session user plane configuration and the identification information of the terminal identified by the Xn interface.

[0053] Optionally, CU-U is also used to send a PDU session deletion success message to CU-C after performing configuration operations on each PDCP entity according to specified information, wherein the PDU session deletion success message includes at least one of the following: the session ID of the successfully deleted session and the identification information of the Xn interface terminal.

[0054] Optionally, CU-U is also used to send a configuration completion confirmation message to CU-C after performing configuration operations on each PDCP entity according to specified information, wherein the configuration completion confirmation message includes: index information of one or more successfully configured PDCP entities; or, to send configuration failure information to CU-C, wherein the configuration failure information includes: the reason for configuration failure.

[0055] Optionally, the CU-C is also used to obtain PDU session-related information from the core network through the NG interface, wherein the specified information includes PDU session-related information; the PDU session-related information includes at least one of the following: session ID, one or more data flow IDs in a single session, QoS information of non-guaranteed code rate (Non-GBR) services corresponding to one or more data flows, and QoS information of guaranteed code rate (GBR) services corresponding to one or more data flows; wherein the NG interface is the interface between the CU-U and the core network.

[0056] Optionally, CU-U is also used to send a configuration completion confirmation message to CU-C after performing configuration operations on each PDCP entity according to specified information. The configuration completion confirmation message includes: one or more successfully configured PDCP entity index information, one or more PDCP entity index information whose configuration modification failed, and the reason for the modification failure; or, to send configuration failure information to CU-C, wherein the configuration failure information includes: the reason for the configuration failure.

[0057] Optionally, CU-C is also used to obtain PDU session modification information from the core network via the NG interface, wherein the specified information includes PDU session modification information; wherein the specified information includes PDU session modification information, wherein the PDU session modification information includes at least one of the following: session identifier ID, one or more data flow IDs to be added in a single session, QoS information of the Non-GBR service corresponding to one or more data flows to be added, QoS information of the GBR service corresponding to one or more data flows to be added, one or more data flow IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to one or more data flows to be modified, QoS information of the GBR service corresponding to one or more data flows to be modified, and one or more data flow IDs to be deleted in a single session.

[0058] Optionally, CU-U is also used to send a user plane configuration deletion success message to CU-C after performing configuration operations on each PDCP entity according to specified information, wherein the user plane configuration deletion success message includes: the index ID of the PDCP entity that was successfully deleted.

[0059] Optionally, the CU-C is also used to obtain PDU session deletion information from the core network via the NG interface, wherein the specified information includes PDU session deletion information, and the PDU session deletion information is obtained by the CU-C from the core network via the NG interface, wherein the PDU session deletion information includes at least one of the following: session ID and session deletion reason.

[0060] According to another embodiment of the present invention, a storage medium is also provided. The storage medium is configured to store program code for performing the following steps: obtaining specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data processing radio bearer via an Xn interface, wherein the Xn interface is an interface between the control plane PDCP entity CU-C and the user plane PDCP entity CU-U; and performing configuration operations on each PDCP entity according to the specified information.

[0061] Through this invention, since the specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data processing radio bearer can be obtained through the Xn interface, and the configuration operation of each PDCP entity can be performed according to the specified information, the CU-U protocol entity configuration is realized. Therefore, the problem of how to implement the configuration of CU-U protocol entities can be solved, and centralized service convergence is realized. Attached Figure Description

[0062] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0063] Figure 1 This is a schematic diagram of the fronthaul interface between the first network element and the second network element;

[0064] Figure 2 This is a possible functional division diagram between the first network element and the second network element;

[0065] Figure 3 A schematic diagram illustrating the separation of control plane data and user plane data for the first network element;

[0066] Figure 4 This is a flowchart of an entity configuration method according to an embodiment of the present invention;

[0067] Figure 5 This is a structural block diagram of a physical configuration device according to an embodiment of the present invention;

[0068] Figure 6 This is a structural block diagram of the CU-U provided according to an embodiment of the present invention;

[0069] Figure 7 This is a structural block diagram of an entity configuration system provided according to an embodiment of the present invention;

[0070] Figure 8 This is a flowchart illustrating the method provided in preferred embodiment 1 of the present invention;

[0071] Figure 9 This is a flowchart illustrating the method provided in preferred embodiment 2 of the present invention;

[0072] Figure 10 This is a flowchart illustrating the method provided in preferred embodiment 3 of the present invention;

[0073] Figure 11 This is a flowchart illustrating the method provided in preferred embodiment 4 of the present invention;

[0074] Figure 12 This is a flowchart illustrating the method provided in preferred embodiment 5 of the present invention;

[0075] Figure 13 This is a flowchart illustrating the method provided in preferred embodiment 6 of the present invention. Detailed Implementation

[0076] The present invention will be described in detail below with reference to the accompanying drawings and embodiments. It should be noted that, unless otherwise specified, the embodiments and features described in the present application can be combined with each other.

[0077] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0078] Example 1

[0079] This embodiment provides an entity configuration method that can be run on the above-mentioned... Figure 3 In the aforementioned architecture, Figure 4 This is a flowchart of an entity configuration method according to an embodiment of the present invention, such as... Figure 4 As shown, the process includes the following steps:

[0080] Step S402: Obtain specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data processing radio bearer through the Xn interface, wherein the Xn interface is the interface between the control plane PDCP entity CU-C and the user plane PDCP entity CU-U.

[0081] Step S404: Configure each PDCP entity according to the specified information.

[0082] Through the above steps, since the specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data processing radio bearer can be obtained through the Xn interface, and the configuration operation of each PDCP entity can be performed according to the specified information, the CU-U protocol entity configuration is realized. Therefore, the problem of how to implement the configuration of CU-U protocol entities can be solved, and centralized service convergence is realized.

[0083] It should be noted that the specified information mentioned above may include at least one of the following: Protocol Data Unit (PDU) session information, and user plane configuration information.

[0084] It should be noted that, when the specified information includes the PDU session information, the above step S404 can be expressed as: determining the user plane configuration information corresponding to the obtained PDU session information based on the obtained PDU session information and the correspondence between the PDU session information and the user plane configuration information; and performing configuration operations on each PDCP entity based on the user plane configuration information corresponding to the obtained PDU session information.

[0085] Optionally, if the specified information includes the user plane configuration information, step S404 above can be expressed as: directly performing configuration operations on each PDCP entity according to the user plane configuration information.

[0086] It should be noted that the PDU session information mentioned above can be PDU session information from one of the following processes: PDU session establishment process, PDU session modification process, and PDU session deletion process.

[0087] In one embodiment of the present invention, when the PDU session information is the information required to establish a PDU session in the PDU session establishment process, the PDU session information may include at least one of the following: session identifier ID, one or more data stream IDs in a single session, quality of service (QoS) information of non-guaranteed code rate (Non-GBR) services corresponding to one or more data streams, QoS information of guaranteed code rate (GBR) services corresponding to one or more data streams, and Xn interface identification terminal flag information.

[0088] It should be noted that after step S404 above, the method may further include: sending a PDU session establishment success message to the CU-C, wherein the PDU session establishment success message carries PDU session information that has been successfully configured; wherein the PDU session information that has been successfully configured includes at least one of the following: session ID, one or more data stream IDs that have been successfully configured in a single session, Xn interface identification terminal flag information, one or more data stream IDs and configuration failure reasons that have failed in a single session; or, sending a PDU session establishment failure message to the CU-C, wherein the PDU session establishment failure message includes at least one of the following: user plane configuration failure reason, Xn interface identification terminal flag information.

[0089] In one embodiment of the present invention, when the PDU session information is the PDU session information to be modified in the PDU session modification process, the PDU session information may include at least one of the following: session identifier ID, one or more data stream IDs to be added in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be added, QoS information of the GBR service corresponding to the one or more data streams to be added, one or more data stream IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be modified, QoS information of the GBR service corresponding to the one or more data streams to be modified, one or more data stream IDs to be deleted in a single session, and Xn interface identification terminal flag information.

[0090] It should be noted that the above configuration operations may include at least one of the following: adding configuration, modifying configuration, and deleting configuration.

[0091] It should be noted that after step S404 above, the method may further include: sending a PDU session modification success message to the CU-C, wherein the PDU session modification success message carries PDU session information that successfully completed the configuration modification; wherein the PDU session information that successfully completed the configuration modification includes at least one of the following: session ID, one or more data stream IDs that successfully completed the user plane configuration modification in a single session, one or more data stream IDs that failed to complete the user plane configuration modification in a single session, the reason for the modification failure, and the identification information of the terminal identified by the Xn interface; or, sending a PDU session modification failure message to the CU-C, wherein the PDU session modification failure message includes: the reason for the failure of the PDU session user plane configuration and the identification information of the terminal identified by the Xn interface.

[0092] In one embodiment of the present invention, when the PDU session information is the PDU session information to be deleted in the PDU session deletion process, the PDU session information includes at least one of the following: session ID, session deletion reason, and Xn interface identification terminal identification information.

[0093] It should be noted that after step S404 above, the method may further include: sending a PDU session deletion success message to the CU-C, wherein the PDU session deletion success message includes at least one of the following information: the session ID of the successfully deleted session and the identification information of the Xn interface identifying the terminal.

[0094] It should be noted that the above user plane configuration information can also be the user plane configuration information in one of the following processes: PDU session establishment process, PDU session modification process, and PDU session deletion process.

[0095] It should be noted that the above user plane configuration information can be transmitted in plaintext through newly defined Xn AP messages, or through Xn AP messages via containers, but is not limited to these methods.

[0096] In one embodiment of the present invention, the user plane configuration information is the user plane configuration information in the PDU session establishment process, wherein the user plane configuration information includes at least one of the following: the index ID of each PDCP entity to be configured and the configuration information of each PDCP entity to be configured.

[0097] It should be noted that the configuration information for each PDCP entity to be configured includes at least one of the following: whether the PDCP protocol used by each PDCP entity requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Control (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information.

[0098] It should be noted that after step S404 above, the method may further include: sending a configuration completion confirmation message to the CU-C, wherein the configuration completion confirmation message includes: one or more successfully configured PDCP entity index information; or, sending configuration failure information to the CU-C, wherein the configuration failure information includes: the reason for the configuration failure.

[0099] It should be noted that step S402 above can be manifested as: obtaining specified information from CU-C through the Xn interface; wherein, the specified information includes PDU session-related information; the PDU session-related information is obtained by CU-C from the core network through the NG interface, and the PDU session-related information includes at least one of the following: session ID, one or more data flow IDs in a single session, QoS information of non-guaranteed code rate (Non-GBR) services corresponding to one or more data flows, and QoS information of guaranteed code rate (GBR) services corresponding to one or more data flows; wherein, the NG interface is the interface between CU-U and the core network.

[0100] In one embodiment of the present invention, the above-mentioned user plane configuration information is the user plane configuration information to be modified in the PDU session modification process. The user plane configuration information may include at least one of the following: the index ID of each PDCP entity to be added and the configuration information of each PDCP entity to be added; the index ID of each PDCP entity to be modified and the configuration information of each PDCP entity to be modified; and the index ID of each PDCP entity to be deleted.

[0101] It should be noted that the configuration information for each PDCP entity to be added may include at least one of the following: whether the PDCP protocol used by each PDCP entity to be added requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Layer (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information; the configuration information for each PDCP entity to be modified may include at least one of the following: whether the PDCP protocol used by each PDCP entity to be added requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Layer (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information.

[0102] It should be noted that after step S404 above, the above method may further include: sending a configuration completion confirmation message to the CU-C, wherein the configuration completion confirmation message includes: one or more successfully configured PDCP entity index information, one or more PDCP entity index information whose configuration modification failed, and the reason for the modification failure; or, sending configuration failure information to the CU-C, wherein the configuration failure information includes: the reason for the configuration failure.

[0103] It should be noted that step S402 above can be manifested as: obtaining specified information from CU-C through the Xn interface; wherein, the specified information includes PDU session related information, which is obtained by CU-C from the core network through the NG interface, wherein the PDU session related information includes at least one of the following: session identifier ID, one or more data flow IDs to be added in a single session, QoS information of the Non-GBR service corresponding to one or more data flows to be added, QoS information of the GBR service corresponding to one or more data flows to be added, one or more data flow IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to one or more data flows to be modified, QoS information of the GBR service corresponding to one or more data flows to be modified, and one or more data flow IDs to be deleted in a single session.

[0104] In one embodiment of the present invention, the user plane configuration information is the user plane configuration information to be deleted in the PDU session deletion process, wherein the user plane configuration information may include at least one of the following: the index ID and deletion reason of each PDCP entity to be deleted.

[0105] It should be noted that after step S402 above, the above method may further include: sending a user plane configuration deletion success message to CU-C, wherein the user plane configuration deletion success message includes: the index ID of the successfully deleted PDCP entity.

[0106] It should be noted that the above step S402 can be manifested as: obtaining specified information from CU-C through the Xn interface, wherein the specified information includes PDU session deletion information, and the PDU session deletion information is obtained by CU-C from the core network through the NG interface, wherein the PDU session deletion information includes at least one of the following: session ID and session deletion reason.

[0107] Optionally, the entity performing the above steps may be CU-U, etc., but is not limited to this.

[0108] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0109] Example 2

[0110] This embodiment also provides a physical configuration device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0111] Figure 5 This is a structural block diagram of a physical configuration device according to an embodiment of the present invention, such as... Figure 5 As shown, the device includes:

[0112] The acquisition module 52 is used to acquire specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data processing radio bearer through the Xn interface, wherein the Xn interface is the interface between the control plane PDCP entity CU-C and the user plane PDCP entity CU-U.

[0113] The configuration module 54, connected to the acquisition module 52, is used to configure each PDCP entity according to specified information.

[0114] With the above-mentioned device, since the specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data processing radio bearer can be obtained through the Xn interface, and then each PDCP entity can be configured according to the specified information, the CU-U protocol entity configuration is realized. Therefore, the problem of how to configure the CU-U protocol entity can be solved, and centralized service convergence is realized.

[0115] It should be noted that the specified information mentioned above may include at least one of the following: Protocol Data Unit (PDU) session information, and user plane configuration information.

[0116] It should be noted that, when the specified information includes the PDU session information, the configuration module 54 can also be used to determine the user plane configuration information corresponding to the obtained PDU session information based on the obtained PDU session information and the correspondence between the PDU session information and the user plane configuration information; and to perform configuration operations on each PDCP entity based on the user plane configuration information corresponding to the obtained PDU session information.

[0117] It should be noted that, when the specified information includes the user plane configuration information, the configuration module 54 can also be used to directly perform configuration operations on each PDCP entity based on the user plane configuration information.

[0118] It should be noted that the PDU session information mentioned above can be PDU session information from one of the following processes: PDU session establishment process, PDU session modification process, and PDU session deletion process.

[0119] In one embodiment of the present invention, when the PDU session information is the information required to establish a PDU session in the PDU session establishment process, the PDU session information may include at least one of the following: session identifier ID, one or more data stream IDs in a single session, quality of service (QoS) information of non-guaranteed code rate (Non-GBR) services corresponding to one or more data streams, QoS information of guaranteed code rate (GBR) services corresponding to one or more data streams, and Xn interface identification terminal flag information.

[0120] It should be noted that the above-mentioned device may further include: a first sending module, connected to the configuration module 54, used to send a PDU session establishment success message to the CU-C after performing configuration operations on each PDCP entity according to specified information, wherein the PDU session establishment success message carries PDU session information that has been successfully configured; wherein the PDU session information that has been successfully configured includes at least one of the following: session ID, one or more data stream IDs that have successfully completed user plane configuration in a single session, Xn interface identification terminal flag information, one or more data stream IDs and configuration failure reasons that have failed user plane configuration in a single session; or, sending a PDU session establishment failure message to the CU-C, wherein the PDU session establishment failure message includes at least one of the following: user plane configuration failure reason, Xn interface identification terminal flag information.

[0121] In one embodiment of the present invention, when the PDU session information is the PDU session information to be modified in the PDU session modification process, the PDU session information may include at least one of the following: session identifier ID, one or more data stream IDs to be added in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be added, QoS information of the GBR service corresponding to the one or more data streams to be added, one or more data stream IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be modified, QoS information of the GBR service corresponding to the one or more data streams to be modified, one or more data stream IDs to be deleted in a single session, and Xn interface identification terminal flag information.

[0122] It should be noted that the above configuration operations include at least one of the following: adding configuration, modifying configuration, and deleting configuration.

[0123] It should be noted that the above-mentioned device may further include: a second sending module, connected to the configuration module 54, used to send a PDU session modification success message to the CU-C after performing configuration operations on each PDCP entity according to specified information, wherein the PDU session modification success message carries PDU session information that has successfully completed the configuration modification; wherein the PDU session information that has successfully completed the configuration modification includes at least one of the following: session ID, one or more data stream IDs that have successfully completed user plane configuration modification in a single session, one or more data stream IDs that have failed to complete user plane configuration modification in a single session, the reason for modification failure, and the identification information of the Xn interface identifying the terminal; or, sending a PDU session modification failure message to the CU-C, wherein the PDU session modification failure message includes: the reason for the failure of PDU session user plane configuration and the identification information of the Xn interface identifying the terminal.

[0124] In one embodiment of the present invention, when the PDU session information is PDU session information to be deleted in the PDU session deletion process, the PDU session information may include at least one of the following: session ID, session deletion reason, and Xn interface identification terminal identification information.

[0125] It should be noted that the above-mentioned device may further include: a third sending module, connected to the above-mentioned configuration module 54, used to send a PDU session deletion success message to the CU-C after performing configuration operations on each PDCP entity according to specified information, wherein the PDU session deletion success message includes at least one of the following information: the session ID of the successfully deleted session and the identification information of the Xn interface terminal.

[0126] It should be noted that the above user plane configuration information can also be the user plane configuration information in one of the following processes: PDU session establishment process, PDU session modification process, and PDU session deletion process.

[0127] It should be noted that the above user plane configuration information can be transmitted in plaintext through newly defined Xn AP messages, or through Xn AP messages via containers, but is not limited to these methods.

[0128] In one embodiment of the present invention, the user plane configuration information is the user plane configuration information in the PDU session establishment process, wherein the user plane configuration information includes at least one of the following: the index ID of each PDCP entity to be configured and the configuration information of each PDCP entity to be configured.

[0129] It should be noted that the configuration information for each PDCP entity to be configured includes at least one of the following: whether the PDCP protocol used by each PDCP entity requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Control (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information.

[0130] It should be noted that the above-mentioned device may further include: a fourth sending module, connected to the above-mentioned configuration module 54, used to send a configuration completion confirmation message to the CU-C after performing configuration operations on each PDCP entity according to specified information, wherein the configuration completion confirmation message includes: index information of one or more successfully configured PDCP entities; or, send configuration failure information to the CU-C, wherein the configuration failure information includes: the reason for configuration failure.

[0131] It should be noted that the aforementioned acquisition module 52 can also be used to acquire specified information from the CU-C via the Xn interface; wherein, the specified information includes PDU session-related information; the PDU session-related information is acquired by the CU-C from the core network via the NG interface, and the PDU session-related information includes at least one of the following: session ID, one or more data flow IDs in a single session, QoS information of non-guaranteed code rate (Non-GBR) services corresponding to one or more data flows, and QoS information of guaranteed code rate (GBR) services corresponding to one or more data flows; wherein, the NG interface is the interface between the CU-U and the core network.

[0132] In one embodiment of the present invention, the user plane configuration information is the user plane configuration information to be modified in the PDU session modification process, wherein the user plane configuration information includes at least one of the following: the index ID of each PDCP entity to be added and the configuration information of each PDCP entity to be added; the index ID of each PDCP entity to be modified and the configuration information of each PDCP entity to be modified; and the index ID of each PDCP entity to be deleted.

[0133] It should be noted that the configuration information for each newly added PDCP entity includes at least one of the following: whether the PDCP protocol used by each newly added PDCP entity requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Layer (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information; the configuration information for each modified PDCP entity includes at least one of the following: whether the PDCP protocol used by each modified PDCP entity requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Layer (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information.

[0134] It should be noted that the above-mentioned device may further include: a fifth sending module, connected to the above-mentioned configuration module 54, used to send a configuration completion confirmation message to the CU-C after performing configuration operations on each PDCP entity according to specified information, wherein the configuration completion confirmation message includes: one or more successfully configured PDCP entity index information, one or more PDCP entity index information whose configuration modification failed, and the reason for the modification failure; or, send configuration failure information to the CU-C, wherein the configuration failure information includes: the reason for the configuration failure.

[0135] It should be noted that the aforementioned acquisition module 52 can also be used to obtain specified information from the CU-C via the Xn interface; wherein, the specified information includes PDU session modification related information, which is obtained by the CU-C from the core network via the NG interface, wherein the PDU session modification related information includes at least one of the following: session identifier ID, one or more data flow IDs to be added in a single session, QoS information of the Non-GBR service corresponding to one or more data flows to be added, QoS information of the GBR service corresponding to one or more data flows to be added, one or more data flow IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to one or more data flows to be modified, QoS information of the GBR service corresponding to one or more data flows to be modified, and one or more data flow IDs to be deleted in a single session.

[0136] In one embodiment of the present invention, the user plane configuration information is the user plane configuration information to be deleted in the PDU session deletion process, wherein the user plane configuration information may include at least one of the following: the index ID and deletion reason of each PDCP entity to be deleted.

[0137] It should be noted that the above-mentioned device may further include: a sixth sending module, connected to the above-mentioned configuration module 54, used to send a user plane configuration deletion success message to CU-C after performing configuration operations on each PDCP entity according to specified information, wherein the user plane configuration deletion success message includes: the index ID of the PDCP entity that was successfully deleted.

[0138] It should be noted that the above-mentioned acquisition module 52 can also be used to obtain specified information from CU-C through the Xn interface. The specified information includes information related to the deletion of PDU sessions. The information related to the deletion of PDU sessions is obtained by CU-C from the core network through the NG interface. The information related to the deletion of PDU sessions includes at least one of the following: session ID and session deletion reason.

[0139] It should be noted that the above-mentioned device may be located in CU-U, but is not limited to this.

[0140] It should be noted that the above modules can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but are not limited to: all the above modules are located in the same processor; or, the above modules are located in different processors in any combination.

[0141] Example 3

[0142] This invention also provides a User Plane Packet Data Convergence Protocol (PDCP) entity CU-U. Figure 6 This is a structural block diagram of the CU-U provided according to an embodiment of the present invention, as shown in FIG6. The CU-U includes:

[0143] The radio frequency module 62 is used to obtain specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data processing radio bearer through the Xn interface, wherein the Xn interface is the interface between the control plane PDCP entity CU-C and the user plane PDCP entity CU-U.

[0144] The processor 64, connected to the aforementioned radio frequency module 62, is used to configure each PDCP entity according to specified information.

[0145] Through the CU-U described above, since the specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data radio bearer can be obtained through the Xn interface, and then each PDCP entity can be configured according to the specified information, the CU-U protocol entity configuration is realized. Therefore, the problem of how to configure the CU-U protocol entity can be solved, and centralized service convergence is realized.

[0146] It should be noted that the specified information mentioned above may include at least one of the following: Protocol Data Unit (PDU) session information, and user plane configuration information.

[0147] Optionally, if the specified information includes the PDU session information, the processor 64 can also be used to determine the user plane configuration information corresponding to the acquired PDU session information based on the acquired PDU session information and the correspondence between the PDU session information and the user plane configuration information; and to perform configuration operations on each PDCP entity based on the user plane configuration information corresponding to the acquired PDU session information.

[0148] It should be noted that, when the specified information includes the user plane configuration information, the processor 64 can also be used to directly perform configuration operations on each PDCP entity based on the user plane configuration information.

[0149] It should be noted that the PDU session information mentioned above can be PDU session information from one of the following processes: PDU session establishment process, PDU session modification process, and PDU session deletion process.

[0150] In one embodiment of the present invention, when the PDU session information is the information required to establish a PDU session in the PDU session establishment process, the PDU session information includes at least one of the following: session identifier ID, one or more data stream IDs in a single session, quality of service (QoS) information of non-guaranteed code rate (Non-GBR) services corresponding to one or more data streams, QoS information of guaranteed code rate (GBR) services corresponding to one or more data streams, and Xn interface identification terminal flag information.

[0151] It should be noted that the aforementioned radio frequency module 62 can also be used to send a PDU session establishment success message to the CU-C after performing configuration operations on each PDCP entity according to specified information. The PDU session establishment success message carries PDU session information that has been successfully configured. The PDU session information that has been successfully configured includes at least one of the following: session ID, one or more data stream IDs that have been successfully configured in a single session, Xn interface identification terminal flag information, one or more data stream IDs and configuration failure reasons that have failed in a single session; or, send a PDU session establishment failure message to the CU-C, wherein the PDU session establishment failure message includes at least one of the following: user plane configuration failure reason, Xn interface identification terminal flag information.

[0152] In one embodiment of the present invention, when the PDU session information is the PDU session information to be modified in the PDU session modification process, the PDU session information includes at least one of the following: session identifier ID, one or more data stream IDs to be added in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be added, QoS information of the GBR service corresponding to the one or more data streams to be added, one or more data stream IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be modified, QoS information of the GBR service corresponding to the one or more data streams to be modified, one or more data stream IDs to be deleted in a single session, and the Xn interface identification terminal's flag information.

[0153] It should be noted that the above configuration operations include at least one of the following: adding configuration, modifying configuration, and deleting configuration.

[0154] It should be noted that the aforementioned radio frequency module 62 can also be used to send a PDU session modification success message to the CU-C after performing configuration operations on each PDCP entity according to specified information. The PDU session modification success message carries PDU session information indicating successful configuration modification. This information includes at least one of the following: session ID, one or more data stream IDs that successfully completed user plane configuration modification in a single session, one or more data stream IDs that failed user plane configuration modification in a single session, the reason for modification failure, and the identification information of the Xn interface terminal. Alternatively, it can send a PDU session modification failure message to the CU-C, wherein the PDU session modification failure message includes: the reason for the PDU session user plane configuration failure and the identification information of the Xn interface terminal.

[0155] In one embodiment of the present invention, when the PDU session information is the PDU session information to be deleted in the PDU session deletion process, the PDU session information includes at least one of the following: session ID, session deletion reason, and Xn interface identification terminal identification information.

[0156] It should be noted that the radio frequency module 62 described above is used to send a PDU session deletion success message to the CU-C after performing configuration operations on each PDCP entity according to the specified information. The PDU session deletion success message includes at least one of the following information: the session ID of the successfully deleted session and the identification information of the Xn interface terminal.

[0157] It should be noted that the user plane configuration information mentioned above can also be the user plane configuration information in one of the following processes: PDU session establishment process, PDU session modification process, and PDU session deletion process.

[0158] It should be noted that the above user plane configuration information can be transmitted in plaintext through newly defined Xn AP messages, or through Xn AP messages via containers, but is not limited to these methods.

[0159] In one embodiment of the present invention, the user plane configuration information is the user plane configuration information in the PDU session establishment process, wherein the user plane configuration information includes at least one of the following: the index ID of each PDCP entity to be configured and the configuration information of each PDCP entity to be configured.

[0160] It should be noted that the configuration information for each PDCP entity to be configured includes at least one of the following: whether the PDCP protocol used by each PDCP entity requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Control (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information.

[0161] It should be noted that the radio frequency module 62 described above can also be used to send a configuration completion confirmation message to the CU-C after performing configuration operations on each PDCP entity according to specified information. The configuration completion confirmation message includes: index information of one or more successfully configured PDCP entities; or, to send configuration failure information to the CU-C, the configuration failure information including: the reason for configuration failure.

[0162] It should be noted that the aforementioned radio frequency module 62 can also be used to obtain specified information from the CU-C via the Xn interface; wherein, the specified information includes PDU session-related information; the PDU session-related information is obtained by the CU-C from the core network via the NG interface, and the PDU session-related information includes at least one of the following: session ID, one or more data stream IDs in a single session, QoS information of non-guaranteed code rate (Non-GBR) services corresponding to one or more data streams, and QoS information of guaranteed code rate (GBR) services corresponding to one or more data streams; wherein, the NG interface is the interface between the CU-U and the core network.

[0163] In one embodiment of the present invention, the user plane configuration information is the user plane configuration information to be modified in the PDU session modification process. The user plane configuration information may include at least one of the following: the index ID of each PDCP entity to be added and the configuration information of each PDCP entity to be added; the index ID of each PDCP entity to be modified and the configuration information of each PDCP entity to be modified; and the index ID of each PDCP entity to be deleted.

[0164] It should be noted that the configuration information for each newly added PDCP entity includes at least one of the following: whether the PDCP protocol used by each newly added PDCP entity requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Layer (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information; the configuration information for each modified PDCP entity includes at least one of the following: whether the PDCP protocol used by each modified PDCP entity requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Layer (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information.

[0165] It should be noted that the radio frequency module 62 described above can also be used to send a configuration completion confirmation message to the CU-C after performing configuration operations on each PDCP entity according to specified information. The configuration completion confirmation message includes: index information of one or more successfully configured PDCP entities, index information of one or more PDCP entities whose configuration modification failed, and the reason for the modification failure; or, send configuration failure information to the CU-C, wherein the configuration failure information includes: the reason for the configuration failure.

[0166] It should be noted that the aforementioned radio frequency module 62 can also be used to obtain specified information from the CU-C via the Xn interface; wherein, the specified information includes PDU session-related information, which is obtained by the CU-C from the core network via the NG interface. The PDU session-related information includes at least one of the following: session identifier ID, one or more data flow IDs to be added in a single session, QoS information of the Non-GBR service corresponding to one or more data flows to be added, QoS information of the GBR service corresponding to one or more data flows to be added, one or more data flow IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to one or more data flows to be modified, QoS information of the GBR service corresponding to one or more data flows to be modified, and one or more data flow IDs to be deleted in a single session.

[0167] In one embodiment of the present invention, the user plane configuration information is the user plane configuration information to be deleted in the PDU session deletion process, wherein the user plane configuration information includes at least one of the following: the index ID and deletion reason of each PDCP entity to be deleted.

[0168] It should be noted that the radio frequency module 62 described above can also be used to send a user plane configuration deletion success message to the CU-C after performing configuration operations on each PDCP entity according to specified information. The user plane configuration deletion success message includes the index ID of the successfully deleted PDCP entity.

[0169] It should be noted that the above-mentioned radio frequency module 62 can also be used to obtain specified information from CU-C through the Xn interface. The specified information includes PDU session deletion information. The PDU session deletion information is obtained by CU-C from the core network through the NG interface. The PDU session deletion information includes at least one of the following: session ID and session deletion reason.

[0170] Example 4

[0171] This application also provides an entity configuration system. Figure 7This is a structural block diagram of an entity configuration system provided according to an embodiment of the present invention, such as... Figure 7 As shown, the system includes: a control plane Packet Data Convergence Protocol (PDCP) entity CU-C72, a user plane PDCP entity CU-U74, and an Xn interface 76, wherein the Xn interface 76 is the interface between CU-C72 and CU-U74; CU-C72 is used to send specified information for configuring each PDCP entity processing data radio bearer to CU-U74 through the Xn interface 76; CU-U74 is used to receive the specified information and perform configuration operations on each PDCP entity according to the specified information.

[0172] Through the above system, since the CU-U74 can obtain the specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data radio bearer through the Xn interface 76, and can then perform configuration operations on each PDCP entity according to the specified information, the CU-U protocol entity configuration is realized. Therefore, the problem of how to implement the configuration of CU-U protocol entities can be solved, and centralized service convergence is realized.

[0173] It should be noted that the specified information mentioned above may include at least one of the following: Protocol Data Unit (PDU) session information, and user plane configuration information.

[0174] It should be noted that, when the specified information includes the PDU session information, the CU-U74 can also be used to determine the user plane configuration information corresponding to the obtained PDU session information based on the obtained PDU session information and the correspondence between the PDU session information and the user plane configuration information; and to perform configuration operations on each PDCP entity based on the user plane configuration information corresponding to the obtained PDU session information.

[0175] It should be noted that, when the specified information includes the user plane configuration information, the CU-U74 can also directly perform configuration operations on each PDCP entity based on the user plane configuration information.

[0176] It should be noted that the PDU session information mentioned above can be PDU session information from one of the following processes: PDU session establishment process, PDU session modification process, and PDU session deletion process.

[0177] In one embodiment of the present invention, when the PDU session information is the information required to establish a PDU session in the PDU session establishment process, the PDU session information includes at least one of the following: session identifier ID, one or more data stream IDs in a single session, quality of service (QoS) information of non-guaranteed code rate (Non-GBR) services corresponding to one or more data streams, QoS information of guaranteed code rate (GBR) services corresponding to one or more data streams, and Xn interface identification terminal flag information.

[0178] It should be noted that the CU-U74 described above is also used to send a PDU session establishment success message to the CU-C72 after performing configuration operations on each PDCP entity according to specified information. The PDU session establishment success message carries PDU session information that has been successfully configured. The PDU session information that has been successfully configured includes at least one of the following: session ID, one or more data stream IDs that have been successfully configured in a single session, Xn interface identification terminal flag information, one or more data stream IDs and configuration failure reasons that have failed in a single session; or, to send a PDU session establishment failure message to the CU-C72. The PDU session establishment failure message includes at least one of the following: user plane configuration failure reason, Xn interface identification terminal flag information.

[0179] In one embodiment of the present invention, when the PDU session information is the PDU session information to be modified in the PDU session modification process, the PDU session information includes at least one of the following: session identifier ID, one or more data stream IDs to be added in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be added, QoS information of the GBR service corresponding to the one or more data streams to be added, one or more data stream IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be modified, QoS information of the GBR service corresponding to the one or more data streams to be modified, one or more data stream IDs to be deleted in a single session, and the Xn interface identification terminal's flag information.

[0180] It should be noted that the above configuration operations include at least one of the following: adding configuration, modifying configuration, and deleting configuration.

[0181] It should be noted that, after performing configuration operations on each PDCP entity according to the specified information, the CU-U74 also sends a PDU session modification success message to the CU-C72. This message carries PDU session information indicating successful configuration modification. The successfully modified PDU session information includes at least one of the following: session ID, one or more data stream IDs that successfully completed user plane configuration modification in a single session, one or more data stream IDs that failed to complete user plane configuration modification in a single session, the reason for the modification failure, and the terminal identification information of the Xn interface. Alternatively, the CU-U74 sends a PDU session modification failure message to the CU-C72, which includes the reason for the PDU session user plane configuration failure and the terminal identification information of the Xn interface.

[0182] In one embodiment of the present invention, when the PDU session information is the PDU session information to be deleted in the PDU session deletion process, the PDU session information includes at least one of the following: session ID, session deletion reason, and Xn interface identification terminal identification information.

[0183] It should be noted that CU-U74 is also used to send a PDU session deletion success message to CU-C72 after configuring each PDCP entity according to the specified information. The PDU session deletion success message includes at least one of the following: the session ID of the successfully deleted session and the identification information of the Xn interface terminal.

[0184] It should be noted that the above user plane configuration information can also be the user plane configuration information in one of the following processes: PDU session establishment process, PDU session modification process, and PDU session deletion process.

[0185] It should be noted that the above user plane configuration information can be transmitted in plaintext through newly defined Xn AP messages, or through Xn AP messages via containers, but is not limited to these methods.

[0186] In one embodiment of the present invention, the user plane configuration information is the user plane configuration information in the PDU session establishment process, wherein the user plane configuration information includes at least one of the following: the index ID of each PDCP entity to be configured and the configuration information of each PDCP entity to be configured.

[0187] It should be noted that the configuration information for each PDCP entity to be configured includes at least one of the following: whether the PDCP protocol used by each PDCP entity requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Control (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information.

[0188] It should be noted that the CU-U74 is also used to send a configuration completion confirmation message to the CU-C72 after performing configuration operations on each PDCP entity according to the specified information. The configuration completion confirmation message includes: one or more successfully configured PDCP entity index information; or, to send configuration failure information to the CU-C72, the configuration failure information including: the reason for the configuration failure.

[0189] It should be noted that the CU-C72 is also used to obtain PDU session-related information from the core network through the NG interface. The specified information includes PDU session-related information. The PDU session-related information includes at least one of the following: session ID, one or more data stream IDs in a single session, QoS information of non-guaranteed code rate (Non-GBR) services corresponding to one or more data streams, and QoS information of guaranteed code rate (GBR) services corresponding to one or more data streams. The NG interface is the interface between the CU-U and the core network.

[0190] In one embodiment of the present invention, the user plane configuration information is the user plane configuration information to be modified in the PDU session modification process, wherein the user plane configuration information includes at least one of the following: the index ID of each PDCP entity to be added and the configuration information of each PDCP entity to be added; the index ID of each PDCP entity to be modified and the configuration information of each PDCP entity to be modified; and the index ID of each PDCP entity to be deleted.

[0191] It should be noted that the configuration information for each newly added PDCP entity includes at least one of the following: whether the PDCP protocol used by each newly added PDCP entity requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Layer (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information; the configuration information for each modified PDCP entity includes at least one of the following: whether the PDCP protocol used by each modified PDCP entity requires header compression, data encryption key information, PDCP Service Data Unit (SDU) discard timer, Radio Link Layer (RLC) layer configuration information, Media Access Control (MAC) layer configuration information, and physical layer configuration information.

[0192] It should be noted that CU-U74 is also used to send a configuration completion confirmation message to CU-C72 after performing configuration operations on each PDCP entity according to specified information. The configuration completion confirmation message includes: one or more successfully configured PDCP entity index information, one or more PDCP entity index information whose configuration modification failed, and the reason for the modification failure; or, to send configuration failure information to CU-C72, wherein the configuration failure information includes: the reason for the configuration failure.

[0193] It should be noted that the CU-C72 is also used to obtain PDU session modification information from the core network via the NG interface. The specified information includes PDU session modification information, which includes at least one of the following: session identifier ID, one or more data flow IDs to be added in a single session, QoS information of the Non-GBR service corresponding to the one or more data flows to be added, QoS information of the GBR service corresponding to the one or more data flows to be added, one or more data flow IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to the one or more data flows to be modified, QoS information of the GBR service corresponding to the one or more data flows to be modified, and one or more data flow IDs to be deleted in a single session.

[0194] In one embodiment of the present invention, the user plane configuration information is the user plane configuration information to be deleted in the PDU session deletion process, wherein the user plane configuration information may include at least one of the following: the index ID and deletion reason of each PDCP entity to be deleted.

[0195] It should be noted that CU-U74 can also be used to send a user plane configuration deletion success message to CU-C72 after performing configuration operations on each PDCP entity according to specified information. The user plane configuration deletion success message includes the index ID of the successfully deleted PDCP entity.

[0196] It should be noted that the CU-C72 can also be used to obtain PDU session deletion information from the core network via the NG interface. The specified information includes PDU session deletion information. The PDU session deletion information is obtained by the CU-C72 from the core network via the NG interface. The PDU session deletion information includes at least one of the following: session ID and session deletion reason.

[0197] Example 5

[0198] Embodiments of the present invention also provide a storage medium. Optionally, in this embodiment, the storage medium may be configured to store program code for performing the steps of the method in Embodiment 1.

[0199] Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0200] Optionally, in this embodiment, the processor executes the steps of the method in embodiment 1 based on the program code stored in the storage medium.

[0201] Optionally, specific examples in this embodiment can refer to the examples described in the above embodiments and optional implementations, and will not be repeated here.

[0202] To better understand the embodiments of the present invention, the present invention will be further explained below in conjunction with preferred embodiments.

[0203] Preferred embodiments of the present invention provide two user plane configuration methods, wherein,

[0204] Method 1 includes:

[0205] Step 1: CU-C obtains PDU session-related information from NGC through the PDU session establishment process of the NG interface. This information includes the information required to establish a PDU session, including but not limited to one or more of the following: session ID, one or more flow IDs in a single session, QoS-related information of the Non-GBR service corresponding to the flow, and QoS-related information of the GBR service corresponding to the flow.

[0206] Step 2: The CU-C transmits the PDU session information to the CU-U through the PDU session establishment process of the Xn interface. This includes the information required to establish the PDU session, including but not limited to one or more of the following: session ID, one or more flow IDs in a single session, QoS-related information of the Non-GBR service corresponding to the flow, QoS-related information of the GBR service corresponding to the flow, and the UE identification information of the Xn interface;

[0207] Step 3: After receiving the relevant information of the PDU session, CU-U configures each PDCP entity carrying user plane data locally.

[0208] Step 4: After successfully completing local configuration, the CU-U can send a PDU session establishment success message to the CU-C, feeding back the successfully configured PDU session information to the CU-C, including but not limited to one or more of the following: session ID, one or more flow IDs that successfully completed user plane configuration in a single session, and Xn interface identification information for the UE. If local processing fails, a PDU session establishment failure message is sent, which may include the reason for the user plane configuration failure and Xn interface identification information for the UE.

[0209] Step 5: Based on the result of Step 4, CU-C sends a PDU session establishment success message or a PDU session establishment failure message to NGC through the NG interface.

[0210] Furthermore, when a PDU session is modified or deleted, CU-C also needs to notify CU-U of the PDU session modification and deletion information through the Xn interface, so that CU-U can perform local user plane configuration updates and deletions.

[0211] Method 2 includes:

[0212] Step 1: The CU-C obtains PDU session-related information from the NGC through the PDU session establishment process of the NG interface. This information includes the information required to establish a PDU session, including but not limited to one or more of the following: session ID, one or more flow IDs in a single session, QoS-related information of the Non-GBR service corresponding to the flow, and QoS-related information of the GBR service corresponding to the flow. After receiving the PDU session-related information, the CU-C configures the CU-U and configures each PDCP entity carrying user plane data.

[0213] Step 2: CU-C transmits user plane configuration information to CU-U via the Xn interface. This includes, but is not limited to, one or more of the following: the index ID of each PDCP entity to be configured, configuration information for each PDCP entity for user plane data, and one or more of the following: whether header compression is required, data encryption key information, PDCP SDU discard timer, RLC layer configuration information, MAC layer configuration information, and physical layer configuration information. User plane configuration information can be transmitted in plaintext via a newly defined Xn AP message, or via a container using Xn AP messages.

[0214] Step 3: The CU-U configures each PDCP entity carrying user plane data locally based on the received user plane configuration information.

[0215] Step 4: Optionally, after receiving the user plane configuration and successfully completing the local configuration, the CU-U can send a configuration completion confirmation message to the CU-C. If local processing fails, a configuration failure message will be returned.

[0216] Step 5: Optionally, based on the result of step 4, CU-C sends a PDU session establishment success message or a PDU session establishment failure message to NGC through the NG interface.

[0217] Furthermore, when a PDU session is modified or deleted, CU-C also needs to notify CU-U of the configuration changes of each PDCP entity corresponding to the PDU session modification and deletion through the Xn interface to update and delete the local user plane configuration.

[0218] The user plane configuration method proposed in the preferred embodiment of the present invention is used to define user plane configuration management on the Xn interface between CU-C and CU-U, realize the protocol entity configuration of CU-U, realize centralized service aggregation, and support independent user plane functions while having centralized RRC / RRM functions.

[0219] like Figure 1 As shown, the first network element and the second network element exchange information through a fronthaul interface. The fronthaul interface can be either ideal or non-ideal, depending on the latency. Ideal fronthaul has a relatively small transmission latency, such as tens to hundreds of microseconds, while non-ideal fronthaul has a relatively large latency, such as milliseconds. This distinction between ideal and non-ideal fronthaul leads to different functional divisions between the first and second network elements.

[0220] like Figure 2 As shown, the possible functional division schemes are as follows:

[0221] Option 1 (RRC / PDCP separation, similar to 1A structure): This option's functional separation is similar to the 1A structure in a dual-connection (DC) architecture. The RRC is located within the CU, while PDCP, RLC, MAC, PHY, and RF functions are all located in the DU. That is, the entire UP is located in the DU.

[0222] Option 2 (PDCP / RLC Separation): This option's functional separation is similar to the 3C structure in a dual-connection (DC) architecture. RRC and PDCP are located within the CU, while RLC, MAC, PHY, and RF functions are located within the DU.

[0223] Option 3 (Separation of RLC High-Level / Low-Level): The low-level RLC (part of the RLC's functions), MAC, PHY, and RF are located within the DU, while PDCP and the high-level RLC (part of the RLC's functions) are located within the CU.

[0224] Option 4 (RLC-MAC separation): The MAC, PHY and RF components are located within the DU, while PDCP and RLC functions are located in the CU.

[0225] Option 5 (MAC Internal Separation): Some MAC functions (such as HARQ), PHY and RF are located in DU, while other upper-layer functions are located in CU.

[0226] Option 6 (MAC-PHY Separation): The MAC, PHY, and RF components are located within the DU, while functions such as PDCP and RLC are located in the CU.

[0227] Option 7 (PHY Internal Separation): Some MAC functions (such as HARQ), PHY and RF are located in DU, while other upper-layer functions are located in CU.

[0228] Option 8 (PHY-RF Separation): The RF part is located within the DU, while other upper-layer functions are located in the CU.

[0229] like Figure 3 As shown, the two PDCPs for the user plane and control plane are located in two different CUs. For ease of description, these two CUs are referred to as CU-C and CU-U, thus achieving the separation of user plane data and control plane data. Assume that there is an Xn interface between CU-C and CU-U, and a forward interface NGx between CU and DU. The interface between CU-C and DU is called NGx-C, and the interface between CU-U and DU is called NGx-U.

[0230] Preferred embodiment 1

[0231] Figure 8 This is a flowchart illustrating the method provided in preferred embodiment 1 of the present invention. The CU-U is automatically configured during PDU session establishment, such as... Figure 8 As shown, the method includes:

[0232] Step 1: CU-C obtains PDU session-related information from NGC through the PDU session establishment process of the NG interface. This information includes the information required to establish a PDU session, including but not limited to one or more of the following: session ID, one or more flow IDs in a single session, QoS-related information of the Non-GBR service corresponding to the flow, and QoS-related information of the GBR service corresponding to the flow.

[0233] Step 2: The CU-C transmits the PDU session information to the CU-U through the PDU session establishment process of the Xn interface. This includes the information required to establish the PDU session, including but not limited to one or more of the following: session ID, one or more flow IDs in a single session, QoS-related information of the Non-GBR service corresponding to the flow, QoS-related information of the GBR service corresponding to the flow, and the UE identification information of the Xn interface;

[0234] Step 3: After receiving the relevant information of the PDU session, CU-U configures each PDCP entity carrying user plane data locally.

[0235] Step 4: After successfully completing local configuration, the CU-U can send a PDU session establishment success message to the CU-C, feeding back the successfully configured PDU session information to the CU-C, including but not limited to one or more of the following: session ID, one or more flow IDs that successfully completed user plane configuration in a single session, and Xn interface identification information for the UE. If local processing fails, a PDU session establishment failure message is sent, which may include the reason for the user plane configuration failure and the Xn interface identification information for the UE.

[0236] Step 5: Based on the result of Step 4, CU-C sends a PDU session establishment success message or a PDU session establishment failure message to NGC through the NG interface.

[0237] Preferred embodiment 2

[0238] Figure 9 This is a flowchart illustrating the method provided in preferred embodiment 2 of the present invention. (The CU-U is automatically configured when the PDU session is modified, such as...) Figure 9 As shown, the method includes:

[0239] Step 1: CU-C obtains relevant information for PDU session modification from NGC through the PDU session modification process of the NG interface. This information includes the information required to modify the PDU session, including but not limited to one or more of the following: session ID, one or more flow IDs to be added in a single session, QoS-related information of the Non-GBR service corresponding to the flow, QoS-related information of the GBR service corresponding to the flow, one or more flow IDs to be modified in a single session, QoS-related information of the Non-GBR service corresponding to the flow, QoS-related information of the GBR service corresponding to the flow, and one or more flow IDs to be deleted in a single session.

[0240] Step 2: The CU-C transmits the modified PDU session information to the CU-U via the PDU session modification procedure of the Xn interface. This includes information required to establish a PDU session, including but not limited to one or more of the following: session ID, one or more flow IDs to be added in a single session, QoS-related information of the Non-GBR service corresponding to the flow, QoS-related information of the GBR service corresponding to the flow, one or more flow IDs to be modified in a single session, QoS-related information of the Non-GBR service corresponding to the flow, QoS-related information of the GBR service corresponding to the flow, one or more flow IDs to be deleted in a single session, and the UE identification information of the Xn interface.

[0241] Step 3: After receiving the relevant information about the PDU session modification, CU-U can locally modify the configuration of one or more PDCP entities carrying user plane data, such as adding, modifying or deleting them.

[0242] Step 4: After successfully completing local configuration, CU-U can send a PDU session modification success message to CU-C, feeding back the PDU session information indicating successful configuration modification, including but not limited to one or more of the following: session ID, one or more flow IDs that successfully completed user plane configuration modification in a single session, one or more flow IDs that failed to complete user plane configuration modification in a single session, and the reason for modification failure. If local processing fails, a PDU session modification failure message is sent, which may include the reason for the user plane configuration failure of that PDU session.

[0243] Step 5: Based on the result of Step 4, CU-C sends a PDU session modification success message or a PDU session modification failure message to NGC through the NG interface.

[0244] Preferred embodiment 3

[0245] Figure 10 This is a flowchart illustrating the method provided in preferred embodiment 3 of the present invention. When a PDU session is deleted, the CU-U is automatically configured, such as... Figure 10 As shown, the method includes:

[0246] Step 1: CU-C obtains PDU session-related information from NGC through the PDU session deletion process of the NG interface, which includes the information required to delete the PDU session, including but not limited to one or more of the following: session ID, reason for session deletion;

[0247] Step 2: The CU-C transmits the PDU session information to be deleted to the CU-U through the PDU session deletion procedure of the Xn interface. This includes, but is not limited to, one or more of the following information: session ID, reason for session deletion, and UE identification information from the Xn interface;

[0248] Step 3: After receiving the relevant information for deleting the PDU session, CU-U deletes the corresponding PDCP entity locally.

[0249] Step 4: After the CU-U successfully completes the local configuration, it can send a PDU session deletion success message to the CU-C, including but not limited to one or more of the following information: the session ID of the successfully deleted session, and the UE identification information of the Xn interface.

[0250] Step 5: Based on the result of step 4, CU-C sends a PDU session deletion confirmation message to NGC through the NG interface.

[0251] Preferred embodiment 4

[0252] Figure 11 This is a flowchart illustrating the method provided in preferred embodiment 4 of the present invention (CU-C configures CU-U when PDU session is established), as follows. Figure 11 As shown, the method includes:

[0253] Step 1: The CU-C obtains PDU session-related information from the NGC through the PDU session establishment process of the NG interface. This information includes the information required to establish a PDU session, including but not limited to one or more of the following: session ID, one or more flow IDs in a single session, QoS-related information of the Non-GBR service corresponding to the flow, and QoS-related information of the GBR service corresponding to the flow. After receiving the PDU session-related information, the CU-C configures the CU-U and configures each PDCP entity carrying user plane data.

[0254] Step 2: CU-C transmits user plane configuration information to CU-U via the Xn interface. This includes, but is not limited to, one or more of the following: the index ID of each PDCP entity to be configured, configuration information for each PDCP entity for user plane data, and one or more of the following: whether header compression is required, data encryption key information, PDCP SDU discard timer, RLC layer configuration information, MAC layer configuration information, and physical layer configuration information. User plane configuration information can be transmitted in plaintext via a newly defined Xn AP message, or via a container using Xn AP messages.

[0255] Step 3: The CU-U configures each PDCP entity carrying user plane data locally based on the received user plane configuration information.

[0256] Step 4: Optionally, after receiving the user plane configuration and successfully completing the local configuration, the CU-U can send a configuration completion confirmation message to the CU-C, containing the index information of one or more successfully configured PDCP entities, enabling the CU-C to index the flow or session corresponding to the PDCP entity locally. If local processing fails, a configuration failure message is returned, which may include the reason for the configuration failure.

[0257] Step 5: Optionally, based on the result of step 4, CU-C sends a PDU session establishment success message or a PDU session establishment failure message to NGC through the NG interface.

[0258] Preferred Example 5

[0259] Figure 12 This is a flowchart illustrating the method provided in preferred embodiment 5 of the present invention. When the PDU session is modified, the CU-C configures the CU-U, such as... Figure 12 As shown, the method includes:

[0260] Step 1: CU-C obtains relevant information for PDU session modification from NGC through the PDU session modification process of the NG interface. This information includes the information required to modify the PDU session, including but not limited to one or more of the following: session ID, one or more flow IDs to be added in a single session, QoS-related information of the Non-GBR service corresponding to the flow, QoS-related information of the GBR service corresponding to the flow, one or more flow IDs to be modified in a single session, QoS-related information of the Non-GBR service corresponding to the flow, QoS-related information of the GBR service corresponding to the flow, and one or more flow IDs to be deleted in a single session.

[0261] Step 2: CU-C transmits the user plane configuration information to be modified to CU-U via the Xn interface. This includes, but is not limited to, one or more of the following: the index ID of each PDCP entity to be added, and the corresponding configuration information of the PDCP entity; the index ID of each PDCP entity to be modified, and the corresponding configuration information of the PDCP entity; and the index ID of each PDCP entity to be deleted. The configuration information for each PDCP entity in the user plane data includes, but is not limited to, one or more of the following: whether header compression is required, data encryption key information, PDCP SDU discard timer, RLC layer configuration information, MAC layer configuration information, and physical layer configuration information. The user plane configuration information can be transmitted in plaintext via a newly defined Xn AP message, or via a container using an Xn AP message.

[0262] Step 3: The CU-U configures each PDCP entity carrying user plane data locally based on the received user plane configuration information to be modified.

[0263] Step 4: Optionally, after receiving the user plane configuration and successfully completing the local configuration, the CU-U can send a configuration completion confirmation message to the CU-C, including but not limited to one or more of the following information: PDCP entity index information for one or more successfully configured configurations, PDCP entity index information for one or more configuration modification failures, and the reason for the modification failure. If local processing fails, a configuration failure message is returned, which may include the reason for the configuration failure.

[0264] Step 5: Optionally, based on the result of step 4, CU-C sends a PDU session establishment success message or a PDU session establishment failure message to NGC through the NG interface.

[0265] Preferred Example 6

[0266] Figure 13 This is a flowchart illustrating the method provided in preferred embodiment 6 of the present invention. When a PDU session is deleted, CU-C configures CU-U, such as... Figure 13 As shown, the method includes:

[0267] Step 1: CU-C obtains PDU session-related information from NGC through the PDU session deletion process of the NG interface, which includes the information required to delete the PDU session, including but not limited to one or more of the following: session ID, reason for session deletion;

[0268] Step 2: CU-C transmits the user plane configuration information to be deleted to CU-U via the Xn interface. This includes, but is not limited to, one or more of the following: the index ID of each PDCP entity to be deleted, and the reason for deletion. The user plane configuration information can be transmitted in plaintext via a newly defined Xn AP message, or it can be transmitted via a container using an Xn AP message.

[0269] Step 3: CU-U deletes the corresponding PDCP entity locally based on the received user plane configuration information.

[0270] Step 4: Optionally, after CU-U successfully completes local configuration, it can send a user plane configuration deletion success message to CU-C, including but not limited to one or more of the following information: the index ID of the successfully deleted PDCP entity.

[0271] Step 5: Optionally, based on the result of step 4, CU-C sends a PDU session deletion confirmation message to NGC via the NG interface.

[0272] Furthermore, in specific embodiments 4, 5, and 6, if it is assumed that CU-U can complete the local configuration completely according to the request of CU-C, then step 5 can also be performed after step 2.

[0273] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0274] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. An entity configuration method, said method being executed by a centralized unit-user plane (CU-UP), characterized in that, include: Obtain the specified information used to configure each Packet Data Convergence Protocol (PDCP) entity for processing data radio bearers; Configure each PDCP entity according to the specified information; The specified information includes Protocol Data Unit (PDU) session information and user plane configuration information; The user plane configuration information includes user plane configuration information for the PDU session establishment process, and the user plane configuration information includes configuration information for each PDCP entity to be configured. The configuration information for each PDCP entity to be configured includes at least one of the following: Data encryption key information, media access control MAC layer configuration information, and physical layer configuration information; The specified information is obtained through the Xn interface, which is the interface between the centralized unit-control plane CU-CP and the centralized unit-user plane CU-UP.

2. The method according to claim 1, characterized in that, The method further includes: Based on the acquired PDU session information and the correspondence between the PDU session information and user plane configuration information, determine the user plane configuration information corresponding to the acquired PDU session information.

3. The method according to claim 1, characterized in that, When the PDU session information is the information required to establish a PDU session in the PDU session establishment process, the PDU session information includes at least one of the following: session identifier ID, one or more data stream IDs in a single session, QoS information of the non-guaranteed code rate (Non-GBR) service corresponding to the one or more data streams, QoS information of the guaranteed code rate (GBR) service corresponding to the one or more data streams, and terminal identification information of the Xn interface between CU-CP and CU-UP.

4. The method according to claim 3, characterized in that, After configuring each PDCP entity according to the specified information, the method further includes: Send a PDU session establishment success message to the CU-CP; wherein, the PDU session information for successful configuration includes: the session ID, one or more data stream IDs for which user plane configuration was successfully completed in a single session, and the terminal identification information of the Xn interface; or, Send a PDU session establishment failure message to the CU-CP, wherein the PDU session establishment failure message includes at least one of the following: the reason for the user plane configuration failure and the identification information of the terminal by the Xn interface.

5. The method according to claim 1, characterized in that, When the PDU session information is the PDU session information to be modified in the PDU session modification process, the PDU session information includes at least one of the following: session identifier ID, one or more data stream IDs to be added in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be added, QoS information of the GBR service corresponding to the one or more data streams to be added, one or more data stream IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be modified, QoS information of the GBR service corresponding to the one or more data streams to be modified, one or more data stream IDs to be deleted in a single session, and the terminal identification information of the Xn interface between CU-CP and CU-UP.

6. The method according to claim 5, characterized in that, After configuring each PDCP entity according to the specified information, the method further includes: Send a PDU session modification success message to the CU-CP; wherein, the PDU session information for successfully completing the configuration modification includes: the session ID, one or more data stream IDs for which user plane configuration modification was successfully completed in a single session, and the terminal identification information of the Xn interface; or, Send a PDU session modification failure message to the CU-CP, wherein the PDU session modification failure message includes: the reason for the failure of PDU session user plane configuration and the identification information of the terminal of the Xn interface.

7. A centralized unit-user plane (CU-UP) node, characterized in that, include: The radio frequency module is used to acquire specified information for configuring each Packet Data Convergence Protocol (PDCP) entity of the data processing radio bearer; A processor is configured to perform configuration operations on each PDCP entity based on the specified information; The specified information includes Protocol Data Unit (PDU) session information and user plane configuration information; The user plane configuration information includes user plane configuration information for the PDU session establishment process, and the user plane configuration information includes configuration information for each PDCP entity to be configured. The configuration information of each PDCP entity to be configured includes at least one of the following: data encryption key information, media access control (MAC) layer configuration information, and physical layer configuration information; The specified information is obtained through the Xn interface, which is the interface between the centralized unit-control plane CU-CP and the centralized unit-user plane CU-UP.

8. The CU-UP node according to claim 7, characterized in that, The processor is further configured to determine user plane configuration information corresponding to the acquired PDU session information based on the acquired PDU session information and the correspondence between the PDU session information and the user plane configuration information.

9. The CU-UP node according to claim 7, characterized in that, When the PDU session information is the information required to establish a PDU session in the PDU session establishment process, the PDU session information includes at least one of the following: session identifier ID, one or more data stream IDs in a single session, QoS information of the non-guaranteed code rate (Non-GBR) service corresponding to the one or more data streams, QoS information of the guaranteed code rate (GBR) service corresponding to the one or more data streams, and terminal identification information of the Xn interface between CU-CP and CU-UP.

10. The CU-UP node according to claim 9, characterized in that, The radio frequency module is further configured to send a PDU session establishment success message to the CU-CP after configuring each PDCP entity according to the specified information; wherein the PDU session information for successful configuration includes: the session ID, one or more data stream IDs for successfully completing user plane configuration in a single session, and the identification information of the Xn interface terminal; or, send a PDU session establishment failure message to the CU-CP, wherein the PDU session establishment failure message includes at least one of the following: the reason for user plane configuration failure, and the identification information of the Xn interface terminal.

11. The CU-UP node according to claim 7, characterized in that, When the PDU session information is the PDU session information to be modified in the PDU session modification process, the PDU session information includes at least one of the following: session identifier ID, one or more data stream IDs to be added in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be added, QoS information of the GBR service corresponding to the one or more data streams to be added, one or more data stream IDs to be modified in a single session, QoS information of the Non-GBR service corresponding to the one or more data streams to be modified, QoS information of the GBR service corresponding to the one or more data streams to be modified, one or more data stream IDs to be deleted in a single session, and the terminal identification information of the Xn interface between CU-CP and CU-UP.

12. The CU-UP node according to claim 11, characterized in that, The radio frequency module is further configured to send a PDU session modification success message to the CU-CP after performing configuration operations on each PDCP entity according to the specified information; wherein the PDU session information for successfully completing the configuration modification includes: the session ID, one or more data stream IDs for successfully completing user plane configuration modification in a single session, and the Xn interface identification terminal's flag information; or, send a PDU session modification failure message to the CU-CP, wherein the PDU session modification failure message includes: the reason for the PDU session user plane configuration failure and the Xn interface identification terminal's flag information.

Images