WO2018130026A1 - 实体配置方法、装置及系统、cu-u - Google Patents

实体配置方法、装置及系统、cu-u Download PDF

Info

Publication number
WO2018130026A1
WO2018130026A1 PCT/CN2017/114952 CN2017114952W WO2018130026A1 WO 2018130026 A1 WO2018130026 A1 WO 2018130026A1 CN 2017114952 W CN2017114952 W CN 2017114952W WO 2018130026 A1 WO2018130026 A1 WO 2018130026A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
configuration
pdu session
user plane
session
Prior art date
Application number
PCT/CN2017/114952
Other languages
English (en)
French (fr)
Inventor
高音
何青春
黄河
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP17890976.8A priority Critical patent/EP3570582B1/en
Priority to EP22209835.2A priority patent/EP4192083A1/en
Priority to FIEP17890976.8T priority patent/FI3570582T3/fi
Publication of WO2018130026A1 publication Critical patent/WO2018130026A1/zh
Priority to US16/511,817 priority patent/US11019680B2/en
Priority to US17/328,461 priority patent/US11765787B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/08—Upper layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present disclosure relates to the field of wireless communications, and in particular, to a physical configuration method, apparatus, and system, CU-U.
  • the massive connection In the fifth generation (Fifth Generation, 5G) mobile communication, the massive connection, the higher rate requirement of the user, the baseband processing unit (BBU) and the remote end in the Long Term Evolution (LTE)
  • the transmission capacity of the common public radio interface (CPRI) between the radio frequency unit (RRU) poses a great challenge, because the CPRI interface transmits the physical layer code modulation and the like.
  • the CPRI interface After the IQ signal, the CPRI interface has a large requirement for transmission delay and bandwidth. If the 5G air interface rate is increased to tens of Gbps, the traffic demand of the CPRI interface will rise to the Tbps level, which puts tremendous pressure on the network deployment cost and deployment difficulty. Therefore, in 5G, the division mode of the preamble interface needs to be redefined.
  • the delay-insensitive network function is placed in the first network element (such as a Centralized Unit (CU)), and the delay-sensitive network function is placed in the second network element (such as a distributed processing unit (Distributed) In the unit (referred to as DU), the interface between the first network element and the second network element transmitted through the ideal and/or non-ideal pre-transmission is called a forward interface, and FIG. 1 is between the first network element and the second network element.
  • CU Centralized Unit
  • DU distributed processing unit
  • FIG. 1 Schematic diagram of the preamble interface, as shown in Figure 1.
  • the first protocol entity (such as the radio resource control RRC entity) is located in the first network element, and the first protocol entity performs control signaling generation, maintains establishment and/or modification and/or release of the radio bearer, and maintains the second protocol entity, Parameter updates for the three protocol entities, the fourth protocol entity, and the physical layer.
  • the function of the second protocol entity is similar to and enhanced by the Packet Data Convergence Protocol (PDCP) function of the Long Term Evolution (LTE) system.
  • PDCP Packet Data Convergence Protocol
  • LTE Long Term Evolution
  • a user can define multiple PDCP entities and can each PDCP entity carrying user plane data. Configured, each PDCP entity carries data of one radio bearer.
  • the PDCP entity corresponds to the control plane or the user plane
  • the third protocol entity function and the long-term evolution LTE radio link control (Radio Link) Control referred to as RLC
  • RLC radio link control
  • 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, and a radio frequency unit.
  • the first network element communicates with the second network element through the preamble interface.
  • 2 is a possible functional division diagram between the first network element and the second network element, and the possible functional division of the CU-DU separation is as shown in FIG. 2.
  • control plane PDCP entity and the user plane PDCP entity in the CU may be separated, that is, the two PDCPs of the user plane and the control plane are respectively located in two different CUs.
  • the two CUs are called The control plane centralized processing unit CU-C and the user plane centralized processing unit CU-U realize separation of user plane data and control plane data.
  • FIG. 3 is a schematic diagram of the separation of the first network element control plane data and the user plane data, as shown in FIG. 3.
  • the embodiments of the present disclosure provide a method, an apparatus, and a system for configuring an entity, and a CU-U, to solve at least the problem of how to implement configuration of a CU-U protocol entity in the related art.
  • an entity configuration method comprising: acquiring, by using an Xn interface, specifying information for configuring each packet data convergence protocol PDCP entity that processes a data radio bearer, wherein the Xn interface is a control The interface between the centralized processing unit CU-C and the user centralized processing unit CU-U; performs a configuration operation on each PDCP entity according to the specified information.
  • an entity configuration apparatus comprising: an obtaining module configured to acquire, by using an Xn interface, specified information for configuring each packet data convergence protocol PDCP entity that processes a data radio bearer, wherein
  • the Xn interface is an interface between the control plane centralized processing unit CU-C and the user plane centralized processing unit CU-U; and the configuration module is configured to perform a configuration operation on each PDCP entity according to the specified information.
  • a user plane centralized processing unit CU-U including: a radio frequency module, configured to acquire, by using an Xn interface, each packet data convergence protocol PDCP entity for processing a data radio bearer.
  • the specified information wherein the Xn interface is an interface between the control plane centralized processing unit CU-C and the user plane centralized processing unit CU-U; and the processor is configured to perform a configuration operation on each PDCP entity according to the specified information.
  • an entity configuration system including: a control plane centralized processing unit CU-C, user plane centralized processing unit CU-U and Xn interface, wherein Xn interface is an interface between CU-C and CU-U; CU-C is set to send to CU-U through Xn interface for pair The specified information configured by each packet data convergence protocol PDCP entity of the data radio bearer is processed; the CU-U is configured to receive the specified information, and perform a configuration operation on each PDCP entity according to the specified information.
  • a storage medium is also provided.
  • the storage medium is configured to store program code for performing the following steps: obtaining, by the Xn interface, designation information for configuring each packet data convergence protocol PDCP entity for processing data radio bearers, wherein the Xn interface is a centralized control plane An interface between the unit CU-C and the user facet processing unit CU-U; each PDCP entity is configured according to the specified information.
  • the configuration operation of each of the PDCP entities can be performed according to the specified information.
  • the protocol entity configuration of the CU-U can solve the problem of how to implement the configuration of the CU-U protocol entity and realize centralized service aggregation.
  • FIG. 1 is a schematic diagram of a preamble interface between a first network element and a second network element
  • FIG. 2 is a possible functional division diagram between a first network element and a second network element
  • 3 is a schematic diagram of separation of control data of the first network element and user plane data
  • FIG. 5 is a structural block diagram of an entity configuration apparatus according to an embodiment of the present disclosure.
  • FIG. 6 is a structural block diagram of a CU-U according to an embodiment of the present disclosure.
  • FIG. 7 is a structural block diagram of an entity configuration system according to an embodiment of the present disclosure.
  • FIG. 8 is a flow chart showing a method according to a preferred embodiment 1 of the present disclosure.
  • FIG. 9 is a flow chart showing a method according to a preferred embodiment 2 of the present disclosure.
  • FIG. 10 is a flow chart showing a method according to a preferred embodiment 3 of the present disclosure.
  • FIG. 11 is a flow chart showing a method according to a preferred embodiment 4 of the present disclosure.
  • FIG. 13 is a flow diagram of a method provided in accordance with a preferred embodiment 6 of the present disclosure.
  • FIG. 4 is a flowchart of an entity configuration method according to an embodiment of the present disclosure. Including the following steps:
  • Step S402 obtaining, by using an Xn interface, specifying information for configuring each packet data convergence protocol PDCP entity for processing a data radio bearer, where the Xn interface is a control plane centralized processing unit CU-C and a user plane centralized processing unit CU- Interface between U;
  • Step S404 performing a configuration operation on each PDCP entity according to the specified information.
  • the specified information for configuring each packet data convergence protocol PDCP entity for processing the data radio bearer can be obtained through the Xn interface, and then the configuration operation of each of the PDCP entities can be performed according to the specified information.
  • the protocol entity configuration of the CU-U can solve the problem of how to implement the configuration of the CU-U protocol entity and realize centralized service aggregation.
  • protocol data unit PDU session information may include at least one of the following: protocol data unit PDU session information, user plane configuration information.
  • the foregoing step S404 may be performed according to the obtained PDU session information and the correspondence between the PDU session information and the user plane configuration information.
  • the relationship determines the user plane configuration information corresponding to the acquired PDU session information; and performs a configuration operation on each of the PDCP entities according to the user plane configuration information corresponding to the acquired PDU session information.
  • the foregoing step S404 may be performed to directly perform a configuration operation on each of the PDCP entities according to the user plane configuration information.
  • PDU session information may be PDU session information in one of the following processes: a PDU session establishment procedure, a PDU session modification procedure, and a PDU session deletion procedure.
  • the PDU session information when the PDU session information is information required for establishing a PDU session in the PDU session establishment process, the PDU session information may include at least one of the following: a session identifier ID, one or more in a single session. Data stream ID, quality of service QoS information of non-guaranteed code rate Non-GBR service corresponding to one or more data streams, guaranteed code rate corresponding to one or more data streams, QoS information of GBR service and flag of Xn interface identification terminal information.
  • the method may further include: sending a PDU session establishment success message to the CU-C, where the PDU session establishment success message carries the successfully completed configuration PDU session information; wherein, the configuration is successfully completed.
  • the PDU session information includes at least one of the following: a session ID, one or more data stream IDs successfully configured in the user plane in a single session, the Xn interface identifying the terminal's flag information, and one or more user plane configuration failures in a single session.
  • the data stream ID and the configuration failure cause; or, the CU session establishment failure message is sent to the CU-C, where the PDU session establishment failure message includes at least one of the following information: the user plane configuration failure reason, and the Xn interface identifies the terminal identifier information. .
  • the PDU session information 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: a session identification ID, one or more to be added in a single session.
  • Data stream ID 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 to be modified in a single session
  • the data stream ID, the Xn interface identifies the flag information of the terminal.
  • configuration operations may include at least one of the following: configuration addition, configuration modification, and configuration deletion.
  • the method may further include: sending a PDU session modification success message to the CU-C, where the PDU session modification success message carries the PDU session information that successfully completes the configuration modification;
  • the configuration of the modified PDU session information includes at least one of the following: a session ID, one or more data stream IDs that successfully complete the user plane configuration modification in a single session, and one or more data stream IDs in which the user plane configuration modification fails in a single session.
  • the PDU session information 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: a session ID, a session deletion reason, and an Xn interface identifying the terminal's flag information.
  • the method may further include: sending a PDU session deletion success message to the CU-C, where the PDU session deletion success message includes at least one of the following information: deleting the successful session ID and the Xn interface. Identify the terminal's logo information.
  • the user plane configuration information may also be user plane configuration information in one of the following processes: The PDU session establishment process, the PDU session modification process, and the PDU session deletion process.
  • the user plane configuration information may be transmitted in a clear text by using a newly defined Xn AP message, or may be transmitted through a container through an Xn AP message, but is not limited thereto.
  • the user plane configuration information is user plane configuration information in a PDU session establishment process, where the user plane configuration information includes at least one of the following: an index ID of each PDCP entity to be configured and Configuration information of each PDCP entity to be configured.
  • the configuration information of each PDCP entity to be configured includes at least one of the following: whether the PDCP protocol used by each PDCP entity to be configured requires header compression, data encryption key information, and PDCP service data unit SDU drop timer.
  • the method may further include: sending a configuration completion confirmation message to the CU-C, where the configuration completion confirmation message includes: one or more configured PDCP entity index information; or The CU-C sends a configuration failure message, where the configuration failure information includes: a configuration failure reason.
  • step S402 may be performed by: acquiring the specified information from the CU-C through 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 through the NG interface.
  • the PDU session related information includes at least one of: a session ID, one or more data stream IDs in a single session, a non-guaranteed code rate corresponding to one or more data streams, and quality of service QoS information of the Non-GBR service and one or more The QoS information of the guaranteed code rate GBR service corresponding to the data stream; wherein the NG interface is an interface between the CU-U and the core network.
  • the user plane configuration information is the user plane configuration information to be modified in the PDU session modification process, where the user plane configuration information may include at least one of the following: each PDCP entity to be newly configured. The index ID and the configuration information of each PDCP entity to be newly added; the index ID of each PDCP entity to be modified and the configuration information of each PDCP entity to be modified; the index ID of each PDCP entity to be deleted.
  • the configuration information of each PDCP entity to be newly added may include at least one of the following information: whether the PDCP protocol used by each PDCP entity to be newly added needs header compression, data encryption key information, and PDCP service.
  • the configuration information of each PDCP entity to be modified may include at least one of the following information: Whether the PDCP protocol to be newly configured for the PDCP entity requires header compression, data encryption key information, PDCP service data unit SDU drop timer, radio link layer control protocol RLC layer configuration information, media access control MAC layer configuration information And physical layer configuration information.
  • the method may further include: sending a configuration completion confirmation message to the CU-C, where the configuration completion confirmation message includes: one or more configured PDCP entity index information, one or more The configuration fails to change the PDCP entity index information, and the reason for the failure is modified; or the configuration failure information is sent to the CU-C, where the configuration failure information includes: a configuration failure reason.
  • step S402 may be performed by: acquiring the specified information from the CU-C through the Xn interface, where the specifying information includes modifying the PDU session related information, and modifying the PDU session related information to the CU-C from the core network through the NG interface.
  • the obtained PDU session related information includes at least one of the following: a session identifier ID, one or more data stream IDs that need to be added in a single session, and one or more data streams that need to be added corresponding to the Non-GBR service.
  • the user plane configuration information is the user plane configuration information to be deleted in the PDU session deletion process, where the user plane configuration information may include at least one of the following: an index ID of each PDCP entity to be deleted. And the reason for the deletion.
  • the method may further include: sending a user plane configuration deletion success message to the CU-C, where the user plane configuration deletion success message includes: deleting the index ID of the successful PDCP entity.
  • step S402 may be performed by: obtaining the specified information from the CU-C through the Xn interface, where the specifying information includes deleting the PDU session related information, and deleting the PDU session related information is the CU-C from the core network through the NG interface.
  • the information about the deleted PDU session includes at least one of the following information: a session ID and a session deletion reason.
  • the execution body of the foregoing steps may be a CU-U or the like, but is not limited thereto.
  • a physical configuration device is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and has not been described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 5 is a structural block diagram of an entity configuration apparatus according to an embodiment of the present disclosure. As shown in FIG. 5, the apparatus includes:
  • the obtaining module 52 is configured to acquire, by using an Xn interface, specified information for configuring each packet data convergence protocol PDCP entity that processes the data radio bearer, where the Xn interface is the control plane centralized processing unit CU-C and the user plane centralized processing Interface between units CU-U;
  • the configuration module 54 is connected to the obtaining module 52, and is configured to perform a configuration operation on each PDCP entity according to the specified information.
  • the protocol entity configuration of the CU-U can solve the problem of how to implement the configuration of the CU-U protocol entity and realize centralized service aggregation.
  • protocol data unit PDU session information may include at least one of the following: protocol data unit PDU session information, user plane configuration information.
  • the configuration module 54 may be further configured to: according to the acquired PDU session information, the PDU session information, and the user plane configuration information.
  • the corresponding relationship determines the user plane configuration information corresponding to the acquired PDU session information; and performs a configuration operation on each of the PDCP entities according to the user plane configuration information corresponding to the acquired PDU session information.
  • the configuration module 54 may be further configured to directly perform a configuration operation on each of the PDCP entities according to the user plane configuration information.
  • PDU session information may be PDU session information in one of the following processes: a PDU session establishment procedure, a PDU session modification procedure, and a PDU session deletion procedure.
  • the PDU session information when the PDU session information is information required to establish a PDU session in the PDU session establishment procedure, the PDU session information may include at least one of: a session identification ID, one or more data in a single session.
  • the flow ID the quality of service QoS information of the non-guaranteed code rate non-GBR service corresponding to one or more data streams, the QoS information of the guaranteed code rate GBR service corresponding to one or more data streams, and the flag information of the Xn interface identification terminal.
  • the foregoing apparatus may further include: a first sending module, connected to the configuration module 54, and configured After the configuration operation is performed on each of the PDCP entities according to the specified information, the PDU session establishment success message is sent to the CU-C, where the PDU session establishment success message carries the successfully completed configuration PDU session information;
  • the PDU session information includes at least one of the following: a session ID, one or more data flow IDs successfully configured in the user plane in a single session, the Xn interface identifying the terminal's flag information, and one or more user plane configuration failures in a single session.
  • the data stream ID and the configuration failure cause; or, the CU session establishment failure message is sent to the CU-C, where the PDU session establishment failure message includes at least one of the following information: the user plane configuration failure reason, and the Xn interface identifies the terminal identifier information.
  • the PDU session information 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: a session identification ID, one or more to be added in a single session.
  • Data stream ID 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 to be modified in a single session
  • the data stream ID, the Xn interface identifies the flag information of the terminal.
  • configuration operations include at least one of the following: configuration addition, configuration modification, and configuration deletion.
  • the foregoing apparatus may further include: a second sending module, connected to the configuration module 54, configured to send a PDU session modification success message to the CU-C after performing a configuration operation on each PDCP entity according to the specified information,
  • the PDU session modification success message carries the PDU session information that successfully completes the configuration modification.
  • the PDU session information that successfully completes the configuration modification includes at least one of the following: a session ID, and one or more of the user plane configuration changes successfully completed in a single session.
  • the PDU session modification failure message includes: a reason why the PDU session user plane configuration fails, and the Xn interface identifies the terminal identifier information.
  • the PDU session information when the PDU session information is to be deleted in the PDU session deletion process, the PDU session information may include at least one of the following: a session ID, a session deletion reason, and an Xn interface identifier information of the terminal. .
  • the foregoing apparatus may further include: a third sending module, connected to the configuration module 54, configured to send a PDU session deletion success message to the CU-C after performing a configuration operation on each PDCP entity according to the specified information,
  • the PDU session deletion success message includes at least one of the following information: the successful session ID is deleted and the Xn interface identifies the terminal's flag information.
  • the user plane configuration information may also be user plane configuration information in one of the following processes: a PDU session establishment procedure, a PDU session modification procedure, and a PDU session deletion procedure.
  • the user plane configuration information may be transmitted in a clear text by using a newly defined Xn AP message, or may be transmitted through a container through an Xn AP message, but is not limited thereto.
  • the user plane configuration information is user plane configuration information in a PDU session establishment process, where the user plane configuration information includes at least one of the following: an index ID of each PDCP entity to be configured and each Configuration information of the PDCP entity to be configured.
  • the configuration information of each PDCP entity to be configured includes at least one of the following: whether the PDCP protocol used by each PDCP entity to be configured requires header compression, data encryption key information, and PDCP service data unit SDU drop timer.
  • the foregoing apparatus may further include: a fourth sending module, configured to be connected to the configuration module 54, configured to send a configuration completion confirmation message to the CU-C after performing a configuration operation on each PDCP entity according to the specified information, where
  • the configuration completion confirmation message includes: one or more configured PDCP entity index information; or, the configuration failure information is sent to the CU-C, where the configuration failure information includes: a configuration failure reason.
  • the obtaining module 52 may be further configured to obtain the specified information from the CU-C through the Xn interface, where the specified information includes PDU session related information, and the PDU session related information is the CU-C from the core network through the NG interface.
  • the obtained PDU session related information includes at least one of: a session ID, one or more data stream IDs in a single session, a non-guaranteed code rate corresponding to one or more data streams, and a quality of service QoS information of the Non-GBR service and a Or QoS information of the guaranteed code rate GBR service corresponding to the multiple data flows; wherein the NG interface is an interface between the CU-U and the core network.
  • the user plane configuration information is the user plane configuration information to be modified in the PDU session modification process, where the user plane configuration information includes at least one of the following information: an index of each PDCP entity to be newly configured. ID and configuration information of each PDCP entity to be newly added; an index ID of each PDCP entity to be modified and configuration information of each PDCP entity to be modified; an index ID of each PDCP entity to be deleted.
  • the configuration information of each PDCP entity to be newly added includes at least one of the following information: whether the PDCP protocol used by each PDCP entity to be newly added needs header compression, data encryption key information, and PDCP service data.
  • the unit SDU discards the timer, the radio link layer control protocol, the RLC layer configuration information, the medium access control, the MAC layer configuration information, and the physical layer configuration information.
  • the configuration information of each PDCP entity to be modified includes at least one of the following information: Whether to modify the PDCP protocol used by the PDCP entity to require header compression, data encryption key letter Information, PDCP service data unit SDU drop timer, radio link layer control protocol RLC layer configuration information, media access control MAC layer configuration information and physical layer configuration information.
  • the foregoing apparatus may further include: a fifth sending module, configured to be connected to the configuration module 54, configured to send a configuration completion confirmation message to the CU-C after performing a configuration operation on each PDCP entity according to the specified information, where
  • the configuration completion confirmation message includes: one or more configured PDCP entity index information, one or more PDCP entity index information whose configuration modification fails, and a modification failure reason; or, the configuration failure information is sent to the CU-C, where the configuration is performed.
  • the failure information includes: the reason for the configuration failure.
  • the foregoing obtaining module 52 may be further configured to obtain the specified information from the CU-C through the Xn interface, where the specifying information includes modifying the PDU session related information, and modifying the PDU session related information to the CU-C through the NG interface. Obtained by the core network, where the information about the modified PDU session includes at least one of the following: a session identifier ID, one or more data stream IDs to be added in a single session, and a non-GBR corresponding to one or more data streams to be added.
  • QoS information of the service QoS information of the service, 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, and Non-GBR corresponding to one or more data flows to be modified
  • the user plane configuration information is the user plane configuration information to be deleted in the PDU session deletion process, where the user plane configuration information may include at least one of the following: an index ID of each PDCP entity to be deleted and Reason for deletion.
  • the foregoing apparatus may further include: a sixth sending module, connected to the configuration module 54, 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 the specified information.
  • the user plane configuration deletion success message includes: deleting the index ID of the successful PDCP entity.
  • the foregoing obtaining module 52 may be further configured to obtain the specified information from the CU-C through the Xn interface, where the specifying information includes deleting the PDU session related information, and deleting the PDU session related information is the CU-C through the NG interface.
  • the core network obtains, wherein the information about deleting the PDU session includes at least one of the following information: a session ID and a session deletion reason.
  • the above device may be located in the CU-U, but is not limited thereto.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • FIG. 6 is a structural block diagram of a CU-U according to an embodiment of the present disclosure. As shown in FIG. 6, the CU-U includes:
  • the radio frequency module 62 is configured to acquire, by using an Xn interface, specified information for configuring each packet data convergence protocol PDCP entity that processes the radio bearer of the data, where the Xn interface is the control plane centralized processing unit CU-C and the user plane centralized processing Interface between units CU-U;
  • the processor 64 is connected to the radio frequency module 62, and is configured to perform a configuration operation on each PDCP entity according to the specified information.
  • the above-mentioned CU-U can obtain configuration information for configuring each packet data convergence protocol PDCP entity for processing the data radio bearer through the Xn interface, and further configure the PDCP entity according to the specified information.
  • the configuration of the protocol entity of the CU-U is implemented. Therefore, the problem of how to implement the configuration of the CU-U protocol entity can be solved, and centralized service aggregation is realized.
  • protocol data unit PDU session information may include at least one of the following: protocol data unit PDU session information, user plane configuration information.
  • the processor 64 may be further configured to: according to the acquired PDU session information, the PDU session information, and the user plane configuration information.
  • the corresponding relationship determines the user plane configuration information corresponding to the acquired PDU session information; and performs a configuration operation on each of the PDCP entities according to the user plane configuration information corresponding to the acquired PDU session information.
  • the processor 64 may be further configured to directly perform a configuration operation on each of the PDCP entities according to the user plane configuration information.
  • PDU session information may be PDU session information in one of the following processes: a PDU session establishment procedure, a PDU session modification procedure, and a PDU session deletion procedure.
  • the PDU session information when the PDU session information is information required for establishing a PDU session in the PDU session establishment procedure, the PDU session information includes at least one of: a session identification ID, one or more data flows in a single session. ID, quality of service QoS information of non-guaranteed code rate Non-GBR service corresponding to one or more data streams, QoS information of guaranteed code rate GBR service corresponding to one or more data streams, and flag information of the Xn interface identifying terminal.
  • the radio frequency module 62 may be configured to send a PDU session establishment success message to the CU-C after the configuration operation is performed on each PDCP entity according to the specified information, where the PDU session establishment success message is successfully completed.
  • the configured PDU session information, where the successfully completed PDU session information includes at least one of the following information: a session ID, one or more data stream IDs successfully configured in the user plane in a single session, and an Xn interface.
  • the PDU session information 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: a session identification ID, one or more to be added in a single session.
  • Data stream ID 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 to be modified in a single session
  • the data stream ID, the Xn interface identifies the flag information of the terminal.
  • configuration operations include at least one of the following: configuration addition, configuration modification, and configuration deletion.
  • the radio frequency module 62 may be configured to send a PDU session modification success message to the CU-C after the configuration operation is performed on each PDCP entity according to the specified information, where the PDU session modification success message carries the successful completion.
  • the modified PDU session information is configured.
  • the PDU session information that successfully completes the configuration modification includes at least one of the following: a session ID, one or more data flow IDs that successfully complete the user plane configuration modification in a single session, and a user plane configuration in a single session.
  • the PDU session information 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: a session ID, a session deletion reason, and an Xn interface identifying the terminal's flag information.
  • the radio frequency module 62 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 the specified information, where the PDU session deletion success message includes at least one of the following information. : Delete the successful session ID and the Xn interface to identify the terminal's flag information.
  • the user plane configuration information may also be user plane configuration information in one of the following processes: a PDU session establishment procedure, a PDU session modification procedure, and a PDU session deletion procedure.
  • the user plane configuration information may be transmitted in a clear text by using a newly defined Xn AP message, or may be transmitted through a container through an Xn AP message, but is not limited thereto.
  • the user plane configuration information is user plane configuration information in a PDU session establishment process, where the user plane configuration information includes at least one of the following: an index ID of each PDCP entity to be configured and Configuration information of each PDCP entity to be configured.
  • the configuration information of each PDCP entity to be configured includes at least one of the following: whether the PDCP protocol used by each PDCP entity to be configured requires header compression, data encryption key information, and PDCP service data unit SDU drop timer.
  • the radio frequency module 62 may be configured to send a configuration completion confirmation message to the CU-C after performing a configuration operation on each PDCP entity according to the specified information, where the configuration completion confirmation message includes: one or more The configuration of the PDCP entity index information is configured; or the configuration failure information is sent to the CU-C, where the configuration failure information includes: a configuration failure reason.
  • the radio frequency module 62 may be configured to obtain specified information from the CU-C through the Xn interface, where the specified information includes PDU session related information, and the PDU session related information is the CU-C from the core network through the NG interface.
  • the obtained PDU session related information includes at least one of: a session ID, one or more data stream IDs in a single session, a non-guaranteed code rate corresponding to one or more data streams, and a quality of service QoS information of the Non-GBR service and a Or QoS information of the guaranteed code rate GBR service corresponding to the multiple data flows; wherein the NG interface is an interface between the CU-U and the core network.
  • the user plane configuration information is the user plane configuration information to be modified in the PDU session modification process, where the user plane configuration information may include at least one of the following information: each PDCP entity to be newly configured. The index ID and the configuration information of each PDCP entity to be newly 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.
  • the configuration information of each PDCP entity to be newly added includes at least one of the following information: whether the PDCP protocol used by each PDCP entity to be newly added needs header compression, data encryption key information, and PDCP service data.
  • the unit SDU discards the timer, the radio link layer control protocol, the RLC layer configuration information, the medium access control, the MAC layer configuration information, and the physical layer configuration information.
  • the configuration information of each PDCP entity to be modified includes at least one of the following information: Whether the PDCP protocol used to configure the PDCP entity needs header compression, data encryption key information, PDCP service data unit SDU drop timer, radio link layer control protocol RLC layer configuration information, media access control MAC layer configuration information, and physical layer Configuration information.
  • the radio frequency module 62 may be configured to send a configuration completion confirmation message to the CU-C after performing a configuration operation on each PDCP entity according to the specified information, where the configuration completion confirmation message includes: one or more The configuration of the PDCP entity index information, the one or more PDCP entity index information that fails to be modified, and the reason for the failure of the modification; or the configuration failure information is sent to the CU-C, where the configuration failure information includes: the configuration fails. the reason.
  • the radio frequency module 62 may be configured to obtain the specified information from the CU-C through the Xn interface, where the specified information includes modifying the PDU session related information, and modifying the PDU session related information to the CU-C through the NG interface. Obtained by the core network, where the information about the modified PDU session includes at least one of the following: a session identifier ID, one or more data stream IDs to be added in a single session, and a non-GBR corresponding to one or more data streams to be added.
  • QoS information of the service QoS information of the service, 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, and Non-GBR corresponding to one or more data flows to be modified
  • the user plane configuration information is the user plane configuration information to be deleted in the PDU session deletion process, where the user plane configuration information includes at least one of the following information: an index ID and a deletion of each PDCP entity to be deleted. the reason.
  • the radio frequency module 62 may be configured to send a user plane configuration deletion success message to the CU-C after the configuration operation is performed on each of the PDCP entities according to the specified information, where the user plane configuration deletion success message includes: Delete the index ID of the successful PDCP entity.
  • the radio frequency module 62 may be configured to obtain the specified information from the CU-C through the Xn interface, where the specified information includes deleting the PDU session related information, and deleting the PDU session related information to the CU-C through the NG interface.
  • the core network obtains, wherein the information about deleting the PDU session includes at least one of the following information: a session ID and a session deletion reason.
  • FIG. 7 is a structural block diagram of an entity configuration system according to an embodiment of the present disclosure.
  • the system includes: a control plane centralized processing unit CU-C72, and a user.
  • the central processing unit CU-U74 and the Xn interface 76 wherein the Xn interface 76 is an interface between the CU-C 72 and the CU-U 74; the CU-C 72 is arranged to transmit to the CU-U 74 via the Xn interface 76 for processing data.
  • the specified information of each packet data convergence protocol PDCP entity of the radio bearer is configured; CU-U74 is configured to receive the specified information, and perform a configuration operation on each PDCP entity according to the specified information.
  • the CU-U 74 can obtain the specified information for configuring each packet data convergence protocol PDCP entity that processes the data radio bearer through the Xn interface 76, and then can configure each of the PDCP entities according to the specified information.
  • the operation implements the protocol entity configuration of the CU-U. Therefore, the problem of how to implement the configuration of the CU-U protocol entity can be solved, and centralized service aggregation is realized.
  • protocol data unit PDU session information may include at least one of the following: protocol data unit PDU session information, user plane configuration information.
  • the CU-U 74 may be further configured to: according to the acquired PDU session information, the PDU session information, and the user plane configuration information.
  • the corresponding relationship determines the user plane configuration information corresponding to the acquired PDU session information; and performs a configuration operation on each of the PDCP entities according to the user plane configuration information corresponding to the acquired PDU session information.
  • the CU-U 74 may directly perform a configuration operation on each of the PDCP entities according to the user plane configuration information.
  • PDU session information may be PDU session information in one of the following processes: a PDU session establishment procedure, a PDU session modification procedure, and a PDU session deletion procedure.
  • the PDU session information when the PDU session information is information required for establishing a PDU session in the PDU session establishment procedure, the PDU session information includes at least one of: a session identification ID, one or more data flows in a single session. ID, quality of service QoS information of non-guaranteed code rate Non-GBR service corresponding to one or more data streams, QoS information of guaranteed code rate GBR service corresponding to one or more data streams, and flag information of the Xn interface identifying terminal.
  • the CU-U 74 is further configured to send a PDU session establishment success message to the CU-C72 after the configuration operation is performed on each of the PDCP entities according to the specified information, where the PDU session establishment success message carries the configuration successfully.
  • the successfully completed PDU session information includes at least one of the following: a session ID, one or more data stream IDs successfully configured in the user plane in a single session, and the Xn interface identifies the terminal's flag information, a single One or more data flow IDs and configuration failure reasons in which the user plane configuration fails in the session; or, the CU session establishment failure message is sent to the CU-C72, where the PDU session establishment failure message includes at least one of the following information: user plane configuration The reason for the failure, the Xn interface identifies the flag information of the terminal.
  • the PDU session information 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: a session identification ID, one or more to be added in a single session.
  • Data stream ID 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 to be modified in a single session
  • the data stream ID, the Xn interface identifies the flag information of the terminal.
  • configuration operations include at least one of the following: configuration addition, configuration modification, and configuration deletion.
  • the CU-U 74 sends a PDU session modification success message to the CU-C72, where the PDU session modification success message carries the configuration modification successfully.
  • the successfully completed configuration modification PDU session information includes at least one of the following: a session ID, one or more data stream IDs successfully completed in the user session configuration modification in a single session, and the user plane configuration modification fails in a single session One or more data stream IDs, modifying the reason for the failure and the Xn interface identifying the flag information of the terminal; or sending a PDU session modification failure message to the CU-C 72, wherein the PDU session modification failure message includes: the PDU session user plane configuration failure The reason and the Xn interface identify the flag information of the terminal.
  • the PDU session information 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: a session ID, a session deletion reason, and an Xn interface identifying the terminal's flag information.
  • the CU-U 74 is further configured to send a PDU session deletion success message to the CU-C72 after performing a configuration operation on each PDCP entity according to the specified information, where the PDU session deletion success message includes at least one of the following information. : Delete the successful session ID and the Xn interface to identify the terminal's flag information.
  • the user plane configuration information may also be user plane configuration information in one of the following processes: a PDU session establishment procedure, a PDU session modification procedure, and a PDU session deletion procedure.
  • the user plane configuration information may be transmitted in a clear text by using a newly defined Xn AP message, or may be transmitted through a container through an Xn AP message, but is not limited thereto.
  • the user plane configuration information is user plane configuration information in a PDU session establishment process, where the user plane configuration information includes at least one of the following: an index ID of each PDCP entity to be configured and each Configuration information of the PDCP entity to be configured.
  • the configuration information of each PDCP entity to be configured includes at least one of the following: whether the PDCP protocol used by each PDCP entity to be configured requires header compression, data encryption key information, and PDCP service data unit SDU drop timer.
  • the CU-U 74 is further configured to send a configuration completion confirmation message to the CU-C72 after performing a configuration operation on each PDCP entity according to the specified information, where the configuration completion confirmation message includes: one or more configurations are successful.
  • the PDCP entity indexes the information; or sends the configuration failure information to the CU-C72, where the configuration failure information includes: a configuration failure reason.
  • the CU-C72 is further configured to acquire PDU session related information from the core network through the NG interface, where the specified information includes PDU session related information, and the PDU session related information includes at least one of the following: a session ID. One or more data stream IDs in a single session, quality of service QoS information of the non-guaranteed code rate Non-GBR service corresponding to one or more data streams, and QoS information of the guaranteed code rate GBR service corresponding to one or more data streams;
  • the NG interface is an interface between the CU-U and the core network.
  • the user plane configuration information is the user plane configuration information to be modified in the PDU session modification process, where the user plane configuration information includes at least one of the following information: an index of each PDCP entity to be newly configured. ID and configuration information of each PDCP entity to be newly added; an index ID of each PDCP entity to be modified and configuration information of each PDCP entity to be modified; an index ID of each PDCP entity to be deleted.
  • the configuration information of each PDCP entity to be newly added includes at least one of the following information: whether the PDCP protocol used by each PDCP entity to be newly added needs header compression, data encryption key information, and PDCP service data.
  • the unit SDU discards the timer, the radio link layer control protocol, the RLC layer configuration information, the medium access control, the MAC layer configuration information, and the physical layer configuration information.
  • the configuration information of each PDCP entity to be modified includes at least one of the following information: Whether the PDCP protocol used to configure the PDCP entity needs header compression, data encryption key information, PDCP service data unit SDU drop timer, radio link layer control protocol RLC layer configuration information, media access control MAC layer configuration information, and physical layer Configuration information.
  • the CU-U 74 is further configured to send a configuration completion confirmation message to the CU-C72 after performing a configuration operation on each PDCP entity according to the specified information, where the configuration completion confirmation message includes: one or more configurations are successfully configured.
  • the CU-C72 is further configured to acquire the PDU session related information from the core network through the NG interface, where the specifying information includes modifying the PDU session related information, where the specifying information includes modifying the PDU session related information, where the PDU is modified.
  • the session related information includes at least one of the following: a session identifier ID, one or more data stream IDs to be added in a single session, and QoS information of the Non-GBR service corresponding to one or more data streams to be added, and one to be added.
  • QoS information of the GBR service corresponding to the multiple data flows, one or more data flow IDs to be modified in a single session, and QoS information of the Non-GBR service corresponding to one or more data flows to be modified, and one to be modified The QoS information of the GBR service corresponding to the multiple data streams, and one or more data stream IDs that need to be deleted in a single session.
  • the user plane configuration information is the user plane configuration information to be deleted in the PDU session deletion process, where the user plane configuration information may include at least one of the following: an index ID of each PDCP entity to be deleted and Reason for deletion.
  • the CU-U74 can also be configured to configure each PDCP entity according to the specified information.
  • the user plane configuration deletion success message is sent to the CU-C72, where the user plane configuration deletion success message includes: deleting the index ID of the successful PDCP entity.
  • the CU-C72 may be configured to obtain information about deleting the PDU session from the core network through the NG interface, where the specified information includes deleting the PDU session related information, and deleting the PDU session related information is the CU-C72 from the core through the NG interface.
  • the information obtained by the network includes: at least one of the following information: a session ID and a session deletion reason.
  • Embodiments of the present disclosure also provide a storage medium.
  • the above storage medium may be set to store program code for executing the steps of the method in Embodiment 1.
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the processor performs the steps of the method in Embodiment 1 according to the stored program code in the storage medium.
  • a preferred embodiment of the present disclosure provides two user plane configuration methods, where
  • Method one includes:
  • Step 1 The CU-C obtains PDU session related information from the NGC through the PDU session establishment process of the NG interface, and includes information required for establishing a PDU session, including but not limited to one or more of the following information: a session ID, in a single session.
  • a session ID in a single session.
  • Step 2 The CU-C passes the PDU session information to the CU-U through the PDU session establishment procedure of the Xn interface.
  • the information required to establish a PDU session includes, but is not limited to, one or more of the following: a session ID, one or more flow IDs in a single session, and QoS related information of the Non-GBR service corresponding to the flow, corresponding to the flow.
  • the QoS related information of the GBR service, and the Xn interface identifies the flag information of the UE;
  • Step 3 After receiving the information about the PDU session, the CU-U configures each PDCP entity that carries the user plane data locally.
  • Step 4 After the CU-U successfully completes the local configuration, it can send a PDU session establishment success message to the CU-C.
  • the PDU session information configured to be completed is fed back to the CU-C, including but not limited to one or more of the following: a session ID, one or more flow IDs successfully configured in the user plane in a single session, and the Xn interface identifies the UE's flag. information. If the local processing fails, the PDU session establishment failure message is sent, which may include the user plane configuration failure reason, and the Xn interface identifies the UE's flag information.
  • Step 5 According to the result of step 4, the CU-C sends a PDU session establishment success message or a PDU session establishment failure message to the NGC through the NG interface.
  • the CU-C When the PDU session is modified or deleted, the CU-C also needs to notify the CU-U of the PDU session modification and deletion information through the Xn interface, so that the CU-U can perform local user plane configuration update and deletion.
  • Method two includes:
  • Step 1 The CU-C obtains PDU session related information from the NGC through the PDU session establishment process of the NG interface, and includes information required for establishing a PDU session, including but not limited to one or more of the following information: a session ID, in a single session. One or more flow IDs, QoS related information of the Non-GBR service corresponding to the flow, and QoS related information of the GBR service corresponding to the flow.
  • the CU-C After receiving the information about the PDU session, the CU-C configures the CU-U and configures each PDCP entity that carries the user plane data.
  • Step 2 The CU-C passes the user plane configuration information to the CU-U through the Xn interface.
  • the information includes, but is not limited to, one or more of the following: an index ID of each PDCP entity to be configured, and configuration information of each PDCP entity for the user plane data, including but not limited to one or more of the following information: Header compression, data encryption key information, PDCP SDU drop timer, RLC layer configuration information, MAC layer configuration information, physical layer configuration information.
  • the user plane configuration information can be delivered in the plain text of the newly defined Xn AP message, or can be delivered through the container through the Xn AP message.
  • Step 3 The CU-U implements local configuration of each PDCP entity carrying the user plane data according to the received user plane configuration information.
  • Step 4 the CU-U may send a configuration completion confirmation message to the CU-C after receiving the user plane configuration and successfully completing the local configuration. If the local processing fails, a configuration failure message is fed back.
  • Step 5 Optionally, according to the result of step 4, the CU-C sends a PDU session establishment success message or a PDU session establishment failure message to the NGC through the NG interface.
  • the CU-C When the PDU session is modified or deleted, the CU-C also needs to notify the CU-U of the configuration change of each PDCP entity corresponding to the PDU session modification and deletion through the Xn interface to perform local user plane configuration update and deletion.
  • the user plane configuration method proposed by the preferred embodiment of the present disclosure is used to define the Xn connection between the CU-C and the CU-U.
  • the user plane configuration management is implemented on the interface to implement the CU-U protocol entity configuration, which can realize centralized service aggregation and support independent user plane functions while having centralized RRC/RRM functions.
  • the information exchanges between the first network element and the second network element through the front-end fronthaul interface, and the forward transmission may be an ideal pre-transmission or a non-ideal pre-transmission for different delays.
  • the transmission delay of the ideal preamble is relatively small, such as tens to hundreds of microseconds, and the transmission delay of the non-ideal preamble is relatively large, such as milliseconds.
  • the first network element is caused by the distinction between ideal and non-ideal preamble.
  • the second network element has different functional divisions.
  • Option 1 RRC/PDCP separation, similar to the 1A structure:
  • the functional separation of this option is similar to the 1A structure in dual connectivity (DC).
  • the RRC is located in the CU, and functions such as PDCP, RLC, MAC, PHY, and RF are all located in the DU. That is, the entire UP is located in the DU.
  • Option2 (PDCP/RLC separation): The functional separation of this option is similar to the 3C structure in dual connectivity (DC).
  • RRC and PDCP are located in the CU, and functions such as RLC, MAC, PHY, and RF are all located in the DU.
  • Option 3 (RLC high-level/low-level separation): The underlying RLC (partial functions of the RLC), the MAC, PHY, and the RF part are located in the DU, and the functions of the PDCP and the upper-layer RLC (part of the RLC function) are located in the CU.
  • Option 4 (RLC-MAC separation): The MAC, PHY, and RF parts are located in the DU, and functions such as PDCP and RLC are located in the CU.
  • Option 5 (MAC internal separation): Some MAC functions (such as HARQ), PHY and RF parts are located in the DU, and other upper layer functions are located in the CU.
  • Option 6 (MAC-PHY separation): The MAC, PHY, and RF parts are located within the DU, and functions such as PDCP and RLC are located in the CU.
  • Option 7 PHY internal separation: Some MAC functions (such as HARQ), PHY and RF parts are located in the DU, and other upper layer functions are located in the CU.
  • MAC functions such as HARQ
  • PHY and RF parts are located in the DU, and other upper layer functions are located in the CU.
  • Option 8 (PHY-RF separation): The RF part is located inside the DU, and other upper layer functions are located in the CU.
  • the two PDCPs of the user plane and the control plane are respectively located in two different CUs.
  • the two CUs are referred to as CU-C and CU-U, thereby realizing user plane data and control. Separation of surface data.
  • CU-C and CU-U There is an Xn interface between CU-C and CU-U.
  • NGx There is a forward interface NGx between CU and DU.
  • the interface between CU-C and DU is called NGx-C.
  • the interface between CU-U and DU is called NGx-U. .
  • FIG. 8 is a schematic flowchart of a method according to a preferred embodiment 1 of the present disclosure, when a PDU session is established, CU-U Configure it yourself, as shown in Figure 8, the method includes:
  • Step 1 The CU-C obtains PDU session related information from the NGC through the PDU session establishment process of the NG interface, and includes information required for establishing a PDU session, including but not limited to one or more of the following information: a session ID, in a single session.
  • a session ID in a single session.
  • Step 2 The CU-C passes the PDU session information to the CU-U through the PDU session establishment procedure of the Xn interface.
  • the information required to establish a PDU session includes, but is not limited to, one or more of the following: a session ID, one or more flow IDs in a single session, and QoS related information of the Non-GBR service corresponding to the flow, corresponding to the flow.
  • the QoS related information of the GBR service, and the Xn interface identifies the flag information of the UE;
  • Step 3 After receiving the information about the PDU session, the CU-U configures each PDCP entity that carries the user plane data locally.
  • Step 4 After the CU-U successfully completes the local configuration, it can send a PDU session establishment success message to the CU-C, and feed back the successfully configured PDU session information to the CU-C, including but not limited to one or more of the following information: ID, one or more flow IDs of the user plane configuration successfully completed in a single session, and the Xn interface identifies the UE's flag information. If the local processing fails, the PDU session establishment failure message is sent, which may include the reason for the failure of the user plane configuration and the identifier information of the UE identified by the Xn interface.
  • Step 5 According to the result of step 4, the CU-C sends a PDU session establishment success message or a PDU session establishment failure message to the NGC through the NG interface.
  • FIG. 9 is a schematic flowchart of a method according to a preferred embodiment 2 of the present disclosure.
  • the CU-U configures itself when the PDU session is modified. As shown in FIG. 9, the method includes:
  • Step 1 The CU-C obtains related information of the PDU session modification from the NGC through the PDU session modification process of the NG interface, and includes information required to modify the PDU session, including but not limited to one or more of the following information: session ID, single One or more flow IDs to be added in the session, QoS related information of the corresponding Non-GBR service, QoS related information of the GBR service corresponding to the flow, and one or more flow IDs to be modified in a single session, corresponding to the flow QoS-related information of the Non-GBR service, QoS-related information of the GBR service corresponding to the flow, and one or more flow IDs to be deleted in a single session;
  • session ID single One or more flow IDs to be added in the session
  • QoS related information of the corresponding Non-GBR service QoS related information of the GBR service corresponding to the flow
  • one or more flow IDs to be modified in a single session corresponding to the flow QoS-related information of the Non-GB
  • Step 2 The CU-C passes the modified PDU session information to the CU-U through the PDU session modification process of the Xn interface.
  • the information required to establish a PDU session includes, but is not limited to, one or more of the following: a session ID, one or more flow IDs to be added in a single session, and QoS related information of the Non-GBR service corresponding to the flow, Flow corresponding QoS-related information of the GBR service, 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 to be deleted in a single session or Multiple stream IDs, and the Xn interface identifies the flag information of the UE;
  • Step 3 After receiving the information about the modification of the PDU session, the CU-U performs local configuration modification, such as adding, modifying, or deleting, one or more PDCP entities carrying the user plane data.
  • local configuration modification such as adding, modifying, or deleting, one or more PDCP entities carrying the user plane data.
  • Step 4 After the CU-U successfully completes the local configuration, it can send a PDU session modification success message to the CU-C, and feed back the PDU session information that has been successfully configured and modified to the CU-C, including but not limited to one or more of the following information: Session ID, one or more flow IDs that successfully complete the user plane configuration modification in a single session, one or more flow IDs in which the user plane configuration modification fails in a single session, and the reason for the modification failure. If the local processing fails, the PDU session modification failure message is sent, which may include the reason why the PDU session user plane configuration fails.
  • Step 5 According to the result of step 4, the CU-C sends a PDU session modification success message or a PDU session modification failure message to the NGC through the NG interface.
  • FIG. 10 is a schematic flowchart of a method according to a preferred embodiment 3 of the present disclosure.
  • the CU-U configures itself. As shown in FIG. 10, the method includes:
  • Step 1 The CU-C obtains PDU session related information from the NGC through the PDU session deletion process of the NG interface, and includes information required for deleting the PDU session, including but not limited to one or more of the following information: session ID, reason for session deletion ;
  • Step 2 The CU-C passes the PDU session information to be deleted to the CU-U through the PDU session deletion process of the Xn interface. Including but not limited to one or more of the following information: session ID, reason for session deletion, and Xn interface identifying flag information of the UE;
  • Step 3 After receiving the information about deleting the PDU session, the CU-U deletes the corresponding PDCP entity locally.
  • Step 4 After the CU-U successfully completes the local configuration, the CU-C may send a PDU session deletion success message, including but not limited to one or more of the following information: the successful session ID is deleted, and the Xn interface identifies the UE's flag information.
  • Step 5 According to the result of step 4, the CU-C sends a PDU session deletion confirmation message to the NGC through the NG interface.
  • FIG. 11 is a schematic flowchart of a method according to a preferred embodiment 4 of the present disclosure.
  • the CU-C configures a CU-U at the time of establishing a PDU session. As shown in FIG. 11, the method includes:
  • Step 1 The CU-C obtains PDU session related information from the NGC through the PDU session establishment process of the NG interface.
  • the information required to establish a PDU session includes, but is not limited to, one or more of the following: a session ID, one or more flow IDs in a single session, and QoS related information of the Non-GBR service corresponding to the flow, corresponding to the flow QoS related information of the GBR service.
  • the CU-C configures the CU-U and configures each PDCP entity that carries the user plane data.
  • Step 2 The CU-C passes the user plane configuration information to the CU-U through the Xn interface.
  • the information includes, but is not limited to, one or more of the following: an index ID of each PDCP entity to be configured, and configuration information of each PDCP entity for the user plane data, including but not limited to one or more of the following information: Header compression, data encryption key information, PDCP SDU drop timer, RLC layer configuration information, MAC layer configuration information, physical layer configuration information.
  • the user plane configuration information can be delivered in the plain text of the newly defined Xn AP message, or can be delivered through the container through the Xn AP message.
  • Step 3 The CU-U implements local configuration of each PDCP entity carrying the user plane data according to the received user plane configuration information.
  • Step 4 the CU-U may send a configuration completion confirmation message to the CU-C, including one or more successfully configured PDCP entity index information, so that the CU-C can Locally indexing the stream or session corresponding to the PDCP entity. If the local processing fails, the configuration failure message is fed back, which may include the reason for the configuration failure.
  • Step 5 Optionally, according to the result of step 4, the CU-C sends a PDU session establishment success message or a PDU session establishment failure message to the NGC through the NG interface.
  • FIG. 12 is a schematic flowchart of a method according to a preferred embodiment 5 of the present disclosure.
  • the CU-C configures the CU-U. As shown in FIG. 12, the method includes:
  • Step 1 The CU-C obtains related information of the PDU session modification from the NGC through the PDU session modification process of the NG interface, and includes information required to modify the PDU session, including but not limited to one or more of the following information: session ID, single One or more flow IDs to be added in the session, QoS related information of the corresponding Non-GBR service, QoS related information of the GBR service corresponding to the flow, and one or more flow IDs to be modified in a single session, corresponding to the flow QoS-related information of the Non-GBR service, QoS-related information of the GBR service corresponding to the flow, and one or more flow IDs to be deleted in a single session;
  • session ID single One or more flow IDs to be added in the session
  • QoS related information of the corresponding Non-GBR service QoS related information of the GBR service corresponding to the flow
  • one or more flow IDs to be modified in a single session corresponding to the flow QoS-related information of the Non-GB
  • Step 2 The CU-C transmits the user plane configuration information to be modified to the CU-U through the Xn interface.
  • the information includes: but is not limited to, one or more of the following: an index ID of each PDCP entity to be newly configured, and configuration information of a corresponding PDCP entity, an index ID of each PDCP entity to be modified, and a corresponding PDCP entity.
  • Configuration letter Information the index ID of each PDCP entity to be deleted.
  • the configuration information of each PDCP entity for the user plane data includes but is not limited to one or more of the following information: whether header compression, data encryption key information, PDCP SDU discard timer, RLC layer configuration information, MAC layer are required. Configuration information, physical layer configuration information.
  • the user plane configuration information can be delivered in the plain text of the newly defined Xn AP message, or can be delivered through the container through the Xn AP message.
  • Step 3 The CU-U implements local configuration of each PDCP entity carrying the user plane data according to the received user plane configuration information to be modified.
  • Step 4 the CU-U may send a configuration completion confirmation message to the CU-C, including but not limited to one or more of the following information: one or more configurations Successful PDCP entity index information, including one or more PDCP entity index information whose configuration modification fails, and the reason for the modification failure. If the local processing fails, the configuration failure message is fed back, which may include the reason for the configuration failure.
  • Step 5 Optionally, according to the result of step 4, the CU-C sends a PDU session establishment success message or a PDU session establishment failure message to the NGC through the NG interface.
  • FIG. 13 is a schematic flowchart of a method according to a preferred embodiment 6 of the present disclosure.
  • the CU-C configures the CU-U. As shown in FIG. 13, the method includes:
  • Step 1 The CU-C obtains PDU session related information from the NGC through the PDU session deletion process of the NG interface, and includes information required for deleting the PDU session, including but not limited to one or more of the following information: session ID, reason for session deletion ;
  • Step 2 The CU-C transmits the user plane configuration information to be deleted to the CU-U through the Xn interface. It includes but is not limited to one or more of the following information: an index ID of each PDCP entity to be deleted, and a reason for deletion.
  • the user plane configuration information can be delivered in the plain text of the newly defined Xn AP message, or can be delivered through the container through the Xn AP message.
  • Step 3 The CU-U performs local deletion of the corresponding PDCP entity according to the received user plane configuration information.
  • Step 4 the CU-C may send a user plane configuration deletion success message, including but not limited to one or more of the following information: deleting the index ID of the successful PDCP entity.
  • Step 5 Optionally, according to the result of step 4, the CU-C sends a PDU session deletion confirmation message to the NGC through the NG interface.
  • step 5 may also be performed after the step 2.
  • modules or steps of the present disclosure can be implemented by a general computing device, which can be concentrated on a single computing device, or distributed in a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different than The steps shown or described are performed sequentially, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.

Abstract

本公开提供了一种实体配置方法、装置及系统、用户集中处理单元CU-U；其中，所述实体配置方法包括：通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，其中，Xn接口为控制面集中处理单元CU-C和用户面集中处理单元CU-U之间的接口；根据指定信息对每个PDCP实体进行配置操作。通过本公开，解决了如何实现CU-U协议实体的配置的问题，实现了集中化业务汇聚。

Description

实体配置方法、装置及系统、CU-U
相关申请的交叉引用
本申请要求于2017年01月16日递交的中国专利申请第201710032552.4号的优先权，在此全文引用上述中国专利申请公开的内容以作为本申请的一部分。
技术领域
本公开涉及无线通信领域，具体而言，涉及一种实体配置方法、装置及系统、CU-U。
背景技术
第五代(Fifth Generation，简称5G)移动通信中，海量连接，用户更高的速率要求，对长期演进(Long Term Evolution，简称LTE)中基带处理单元(Building Baseband Unit，简称BBU)与远端射频单元(Remote Radio Unit，简称RRU)之间的前传接口通用公共无线电接口(Common Public Radio Interface，简称CPRI)的传输容量提出了极大挑战，由于CPRI接口传输的是经过物理层编码调制等处理后的IQ信号，CPRI接口对传输时延迟和带宽都有较大的要求。如果在5G空口速率提升到数十Gbps后，CPRI接口的流量需求将上升到Tbps级别，对网络部署成本和部署难度都带来了巨大的压力。因此，在5G中，需要重新定义前传接口的划分方式，在前传接口的划分方式中，从传输容量、传输时延、方便部署等几方面进行考虑，比如考虑到非理想前传(fronthaul)传输，将时延不敏感的网络功能放在第一网元(比如集中处理单元(Centralized Unit，简称CU)中)，将时延敏感的网络功能放在第二网元(比如分布式处理单元(Distributed Unit，简称DU)中)，第一网元与第二网元之间通过理想和/或非理想前传进行传输的接口称为前向接口，图1是第一网元与第二网元间的前传接口示意图，如图1所示。
第一协议实体(如无线资源控制RRC实体)位于第一网元，第一协议实体进行控制信令的生成，维护无线承载的建立和/或修改和/或释放，维护第二协议实体、第三协议实体、第四协议实体和物理层的参数更新。第二协议实体功能与长期演进LTE系统的分组数据汇聚协议(Packet Data Convergence Protocol，简称PDCP)功能类似及其增强，一个用户可以定义多个PDCP实体，可以对携带用户面数据的每个PDCP实体进行配置，每个PDCP实体携带一个无线承载的数据，根据无线承载所携带数据的不同，PDCP实体对应于控制面或者用户面，第三协议实体功能与长期演进LTE的无线链路控制(Radio Link  Control，简称RLC)功能类似及其增强，第四协议实体功能与长期演进LTE的媒体接入控制(Medium Access Control，简称MAC)功能及其增强。第二网元包括至少以下之一：第二协议实体、第三协议实体、第四协议实体、物理层、射频单元。第一网元与第二网元之间通过前传接口通信。图2是第一网元与第二网元之间可能的功能划分图，CU-DU分离可能的功能划分如图2所示。
需要说明的是，CU中控制面PDCP实体和用户面PDCP实体可能是分离的，即用户面和控制面的两个PDCP分别位于两个不同的CU，为了方便描述，把这两个CU称为控制面集中处理单元CU-C和用户面集中处理单元CU-U，从而实现了用户面数据与控制面数据的分离。图3为第一网元控制面数据和用户面数据分离示意图，如图3所示。
假设CU-C与CU-U之间存在Xn接口，CU和DU之间存在前向接口NGx，CU-C和DU之间接口称为NGx-C，CU-U和DU之间接口称为NGx-U。因此，如何实现CU-U协议实体的配置是当前需要解决的问题。
针对相关技术中的上述技术问题，目前尚未提出有效的解决方案。
发明内容
本公开实施例提供了一种实体配置方法、装置及系统、CU-U，以至少解决相关技术中如何实现CU-U协议实体的配置的问题。
根据本公开的一个实施例，提供了一种实体配置方法，包括：通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，其中，Xn接口为控制面集中处理单元CU-C和用户面集中处理单元CU-U之间的接口；根据指定信息对每个PDCP实体进行配置操作。
根据本公开的一个实施例，提供了一种实体配置装置，包括：获取模块，设置为通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，其中，Xn接口为控制面集中处理单元CU-C和用户面集中处理单元CU-U之间的接口；配置模块，设置为根据指定信息对每个PDCP实体进行配置操作。
根据本公开的一个实施例，提供了一种用户面集中处理单元CU-U，包括：射频模块，设置为通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，其中，Xn接口为控制面集中处理单元CU-C和用户面集中处理单元CU-U之间的接口；处理器，设置为根据指定信息对每个PDCP实体进行配置操作。
根据本公开的一个实施例，提供了一种实体配置系统，包括：控制面集中处理单元 CU-C，用户面集中处理单元CU-U和Xn接口，其中，Xn接口为CU-C和CU-U之间的接口；CU-C，设置为通过Xn接口向CU-U发送用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息；CU-U，设置为接收指定信息，以及根据指定信息对每个PDCP实体进行配置操作。
根据本公开的又一个实施例，还提供了一种存储介质。该存储介质设置为存储用于执行以下步骤的程序代码：通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，其中，Xn接口为控制面集中处理单元CU-C和用户面集中处理单元CU-U之间的接口；根据指定信息对每个PDCP实体进行配置操作。
通过本公开，由于可以通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，进而可以根据该指定信息对上述每个PDCP实体进行配置操作，实现了CU-U的协议实体配置，因此，可以解决如何实现CU-U协议实体的配置的问题，实现了集中化业务汇聚。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是第一网元与第二网元间的前传接口示意图；
图2是第一网元与第二网元之间可能的功能划分图；
图3为第一网元控制面数据和用户面数据分离示意图；
图4是根据本公开实施例的实体配置方法的流程图；
图5是根据本公开实施例的实体配置装置的结构框图；
图6是根据本公开实施例提供的CU-U的结构框图；
图7是根据本公开实施例提供的实体配置系统的结构框图；
图8是根据本公开优选实施例1提供的方法的流程示意图；
图9是根据本公开优选实施例2提供的方法的流程示意图；
图10是根据本公开优选实施例3提供的方法的流程示意图；
图11是根据本公开优选实施例4提供的方法的流程示意图；
图12是根据本公开优选实施例5提供的方法的流程示意图；
图13是根据本公开优选实施例6提供的方法的流程示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
在本实施例中提供了一种实体配置方法，其可以运行于上述图3所述的架构中，图4是根据本公开实施例的实体配置方法的流程图，如图4所示，该流程包括如下步骤：
步骤S402，通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，其中，Xn接口为控制面集中处理单元CU-C和用户面集中处理单元CU-U之间的接口；
步骤S404，根据指定信息对每个PDCP实体进行配置操作。
通过上述步骤，由于可以通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，进而可以根据该指定信息对上述每个PDCP实体进行配置操作，实现了CU-U的协议实体配置，因此，可以解决如何实现CU-U协议实体的配置的问题，实现了集中化业务汇聚。
需要说明的是，上述指定信息可以包括以下至少之一：协议数据单元PDU会话信息，用户面配置信息。
需要说明的是，在所述指定信息包括所述PDU会话信息的情况下，上述步骤S404可以表现为：根据获取的所述PDU会话信息以及所述PDU会话信息与所述用户面配置信息的对应关系确定与获取的所述PDU会话信息对应的用户面配置信息；根据与获取的所述PDU会话信息对应的用户面配置信息对所述每个PDCP实体进行配置操作。
可选地，在所述指定信息包括所述用户面配置信息的情况下，上述步骤S404可以表现为：根据所述用户面配置信息直接对所述每个PDCP实体进行配置操作。
需要说明的是，上述PDU会话信息可以是以下之一流程中的PDU会话信息：PDU会话建立流程、PDU会话修改流程和PDU会话删除流程。
在本公开的一个实施例中，在上述PDU会话信息为PDU会话建立流程中建立PDU会话所需要的信息时，上述PDU会话信息可以包括以下至少之一：会话标识ID，单个会话中一个或多个数据流ID，一个或多个数据流对应的非保证码速率Non-GBR业务的服务质量QoS信息，一个或多个数据流对应的保证码速率GBR业务的QoS信息和Xn接口识别终端的标志信息。
需要说明的是，在上述步骤S404之后，上述方法还可以包括：向CU-C发送PDU会话建立成功消息，其中，PDU会话建立成功消息中携带成功完成配置的PDU会话信息；其中，成功完成配置的PDU会话信息包括以下至少之一信息：会话ID，单个会话中成功完成用户面配置的一个或多个数据流ID，Xn接口识别终端的标志信息，单个会话中用户面配置失败的一个或多个数据流ID和配置失败原因；或者，向CU-C发送PDU会话建立失败消息，其中，PDU会话建立失败消息中包括以下至少之一信息：用户面配置失败原因，Xn接口识别终端的标志信息。
在本公开的一个实施例中，在PDU会话信息为PDU会话修改流程中待修改的PDU会话信息时，PDU会话信息可以包括以下至少之一：会话标识ID，单个会话中需要添加的一个或多个数据流ID，需要添加的一个或多个数据流对应的Non-GBR业务的QoS信息，需要添加的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要修改的一个或多个数据流ID，需要修改的一个或多个数据流对应的Non-GBR业务的QoS信息，需要修改的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要删除的一个或多个数据流ID，Xn接口识别终端的标志信息。
需要说明的是，上述配置操作可以包括以下至少之一：配置新增、配置修改和配置删除。
需要说明的是，在上述步骤S404之后，上述方法还可以包括：向CU-C发送PDU会话修改成功消息，其中，PDU会话修改成功消息携带有成功完成配置修改的PDU会话信息；其中，成功完成配置修改的PDU会话信息包括以下至少之一：会话ID，单个会话中成功完成用户面配置修改的一个或多个数据流ID，单个会话中用户面配置修改失败的一个或多个数据流ID，修改失败原因，和所述Xn接口识别终端的标志信息；或者，向CU-C发送PDU会话修改失败消息，其中，PDU会话修改失败消息包括：PDU会话用户面配置失败的原因和所述Xn接口识别终端的标志信息。
在本公开的一个实施例中，在PDU会话信息为PDU会话删除流程中待删除PDU会话信息时，PDU会话信息包括以下至少之一：会话ID，会话删除原因和Xn接口识别终端的标志信息。
需要说明的是，在上述步骤S404之后，上述方法还可以包括：向CU-C发送PDU会话删除成功消息，其中，PDU会话删除成功消息包括以下至少之一信息：删除成功的会话ID和Xn接口识别终端的标志信息。
需要说明的是，上述用户面配置信息也可以是以下之一流程中的用户面配置信息： PDU会话建立流程、PDU会话修改流程和PDU会话删除流程。
需要说明的是，上述用户面配置信息可以通过新定义Xn AP消息明文传递，也可以通过Xn AP消息通过容器的方式传递，但并不限于此。
在本公开的一个实施例中，上述用户面配置信息为PDU会话建立流程中的用户面配置信息，其中，上述用户面配置信息包括以下至少之一信息：每个待配置PDCP实体的索引ID和每个待配置PDCP实体的配置信息。
需要说明的是，每个待配置PDCP实体的配置信息包括以下至少之一：每个待配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息。
需要说明的是，在上述步骤S404之后，上述方法还可以包括：向CU-C发送配置完成确认消息，其中，配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息；或者，向CU-C发送配置失败信息，其中，配置失败信息包括：配置失败原因。
需要说明的是，上述步骤S402可以表现为：通过Xn接口从CU-C中获取指定信息；其中，指定信息包括PDU会话相关信息；PDU会话相关信息为CU-C通过NG接口从核心网获取的，PDU会话相关信息包括以下至少之一：会话ID，单个会话中一个或多个数据流ID，一个或多个数据流对应的非保证码速率Non-GBR业务的服务质量QoS信息和一个或多个数据流对应的保证码速率GBR业务的QoS信息；其中，NG接口为CU-U与核心网之间的接口。
在本公开的一个实施例中，上述用户面配置信息为PDU会话修改流程中待修改的用户面配置信息，其中，用户面配置信息可以包括以下至少之一信息：每个待新增配置PDCP实体的索引ID和每个待新增配置PDCP实体的配置信息；每个待修改配置PDCP实体的索引ID和每个待修改配置PDCP实体的配置信息；每个待删除PDCP实体的索引ID。
需要说明的是，每个待新增配置PDCP实体的配置信息可以包括以下至少之一信息：每个待新增配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息；每个待修改配置PDCP实体的配置信息可以包括以下至少之一信息：每个待新增配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息。
需要说明的是，在上述步骤S404之后，上述方法还可以包括：向CU-C发送配置完成确认消息，其中，配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息，一个或多个配置修改失败的PDCP实体索引信息，修改失败原因；或者，向CU-C发送配置失败信息，其中，配置失败信息包括：配置失败原因。
需要说明的是，上述步骤S402可以表现为：通过Xn接口从CU-C中获取指定信息；其中，指定信息包括修改PDU会话相关信息，修改PDU会话相关信息为CU-C通过NG接口从核心网获取的，其中，修改PDU会话相关信息包括以下至少之一：会话标识ID，单个会话中需要添加的一个或多个数据流ID，需要添加的一个或多个数据流对应的Non-GBR业务的QoS信息，需要添加的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要修改的一个或多个数据流ID，需要修改的一个或多个数据流对应的Non-GBR业务的QoS信息，需要修改的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要删除的一个或多个数据流ID。
在本公开的一个实施例中，用户面配置信息为PDU会话删除流程中待删除用户面配置信息，其中，上述用户面配置信息可以包括以下至少之一信息：每个待删除PDCP实体的索引ID和删除原因。
需要说明的是，在上述步骤S402之后，上述方法还可以包括：向CU-C发送用户面配置删除成功消息，其中，用户面配置删除成功消息包括：删除成功的PDCP实体的索引ID。
需要说明的是，上述步骤S402可以表现为：通过Xn接口从CU-C中获取指定信息，其中，指定信息包括删除PDU会话相关信息，删除PDU会话相关信息为CU-C通过NG接口从核心网获取的，其中，删除PDU会话相关信息中包括以下至少之一信息：会话ID和会话删除原因。
可选地，上述步骤的执行主体可以为CU-U等，但不限于此。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
实施例2
在本实施例中还提供了一种实体配置装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图5是根据本公开实施例的实体配置装置的结构框图，如图5所示，该装置包括：
获取模块52，设置为通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，其中，Xn接口为控制面集中处理单元CU-C和用户面集中处理单元CU-U之间的接口；
配置模块54，与上述获取模块52连接，设置为根据指定信息对每个PDCP实体进行配置操作。
通过上述装置，由于可以通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，进而可以根据该指定信息对上述每个PDCP实体进行配置操作，实现了CU-U的协议实体配置，因此，可以解决如何实现CU-U协议实体的配置的问题，实现了集中化业务汇聚。
需要说明的是，上述指定信息可以包括以下至少之一：协议数据单元PDU会话信息，用户面配置信息。
需要说明的是，在所述指定信息包括所述PDU会话信息的情况下，上述配置模块54，还可以设置为根据获取的所述PDU会话信息以及所述PDU会话信息与所述用户面配置信息的对应关系确定与获取的所述PDU会话信息对应的用户面配置信息；根据与获取的所述PDU会话信息对应的用户面配置信息对所述每个PDCP实体进行配置操作。
需要说明的是，在所述指定信息包括所述用户面配置信息的情况下，上述配置模块54，还可以设置为根据所述用户面配置信息直接对所述每个PDCP实体进行配置操作。
需要说明的是，上述PDU会话信息可以是以下之一流程中的PDU会话信息：PDU会话建立流程、PDU会话修改流程和PDU会话删除流程。
在本公开的一个实施例中，在PDU会话信息为PDU会话建立流程中建立PDU会话所需要的信息时，PDU会话信息可以包括以下至少之一：会话标识ID，单个会话中一个或多个数据流ID，一个或多个数据流对应的非保证码速率Non-GBR业务的服务质量QoS信息，一个或多个数据流对应的保证码速率GBR业务的QoS信息和Xn接口识别终端的标志信息。
需要说明的是，上述装置还可以包括：第一发送模块，与上述配置模块54连接，设 置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C发送PDU会话建立成功消息，其中，PDU会话建立成功消息中携带成功完成配置的PDU会话信息；其中，成功完成配置的PDU会话信息包括以下至少之一信息：会话ID，单个会话中成功完成用户面配置的一个或多个数据流ID，Xn接口识别终端的标志信息，单个会话中用户面配置失败的一个或多个数据流ID和配置失败原因；或者，向CU-C发送PDU会话建立失败消息，其中，PDU会话建立失败消息中包括以下至少之一信息：用户面配置失败原因，Xn接口识别终端的标志信息。
在本公开的一个实施例中，在PDU会话信息为PDU会话修改流程中待修改的PDU会话信息时，PDU会话信息可以包括以下至少之一：会话标识ID，单个会话中需要添加的一个或多个数据流ID，需要添加的一个或多个数据流对应的Non-GBR业务的QoS信息，需要添加的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要修改的一个或多个数据流ID，需要修改的一个或多个数据流对应的Non-GBR业务的QoS信息，需要修改的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要删除的一个或多个数据流ID，Xn接口识别终端的标志信息。
需要说明的是，上述配置操作包括以下至少之一：配置新增、配置修改和配置删除。
需要说明的是，上述装置还可以包括：第二发送模块，与上述配置模块54连接，设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C发送PDU会话修改成功消息，其中，PDU会话修改成功消息携带有成功完成配置修改的PDU会话信息；其中，成功完成配置修改的PDU会话信息包括以下至少之一：会话ID，单个会话中成功完成用户面配置修改的一个或多个数据流ID，单个会话中用户面配置修改失败的一个或多个数据流ID，修改失败原因和所述Xn接口识别终端的标志信息；或者，向CU-C发送PDU会话修改失败消息，其中，PDU会话修改失败消息包括：PDU会话用户面配置失败的原因和所述Xn接口识别终端的标志信息。
在本公开的一个实施例中，在PDU会话信息为PDU会话删除流程中待删除PDU会话信息时，PDU会话信息可以包括以下至少之一：会话ID，会话删除原因和Xn接口识别终端的标志信息。
需要说明的是，上述装置还可以包括：第三发送模块，与上述配置模块54连接，设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C发送PDU会话删除成功消息，其中，PDU会话删除成功消息包括以下至少之一信息：删除成功的会话ID和Xn接口识别终端的标志信息。
需要说明的是，上述用户面配置信息也可以是以下之一流程中的用户面配置信息：PDU会话建立流程、PDU会话修改流程和PDU会话删除流程。
需要说明的是，上述用户面配置信息可以通过新定义Xn AP消息明文传递，也可以通过Xn AP消息通过容器的方式传递，但并不限于此。
在本公开的一个实施例中，用户面配置信息为PDU会话建立流程中的用户面配置信息，其中，用户面配置信息包括以下至少之一信息：每个待配置PDCP实体的索引ID和每个待配置PDCP实体的配置信息。
需要说明的是，每个待配置PDCP实体的配置信息包括以下至少之一：每个待配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息。
需要说明的是，上述装置还可以包括：第四发送模块，与上述配置模块54连接，设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C发送配置完成确认消息，其中，配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息；或者，向CU-C发送配置失败信息，其中，配置失败信息包括：配置失败原因。
需要说明的是，上述获取模块52，还可以设置为通过Xn接口从CU-C中获取指定信息；其中，指定信息包括PDU会话相关信息；PDU会话相关信息为CU-C通过NG接口从核心网获取的，PDU会话相关信息包括以下至少之一：会话ID，单个会话中一个或多个数据流ID，一个或多个数据流对应的非保证码速率Non-GBR业务的服务质量QoS信息和一个或多个数据流对应的保证码速率GBR业务的QoS信息；其中，NG接口为CU-U与核心网之间的接口。
在本公开的一个实施例中，用户面配置信息为PDU会话修改流程中待修改的用户面配置信息，其中，用户面配置信息包括以下至少之一信息：每个待新增配置PDCP实体的索引ID和每个待新增配置PDCP实体的配置信息；每个待修改配置PDCP实体的索引ID和每个待修改配置PDCP实体的配置信息；每个待删除PDCP实体的索引ID。
需要说明的是，每个待新增配置PDCP实体的配置信息包括以下至少之一信息：每个待新增配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息；每个待修改配置PDCP实体的配置信息包括以下至少之一信息：每个待修改配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信 息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息。
需要说明的是，上述装置还可以包括：第五发送模块，与上述配置模块54连接，设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C发送配置完成确认消息，其中，配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息，一个或多个配置修改失败的PDCP实体索引信息，修改失败原因；或者，向CU-C发送配置失败信息，其中，配置失败信息包括：配置失败原因。
需要说明的是，上述获取模块52，还可以设置为通过Xn接口从CU-C中获取指定信息；其中，指定信息包括修改PDU会话相关信息，修改PDU会话相关信息为CU-C通过NG接口从核心网获取的，其中，修改PDU会话相关信息包括以下至少之一：会话标识ID，单个会话中需要添加的一个或多个数据流ID，需要添加的一个或多个数据流对应的Non-GBR业务的QoS信息，需要添加的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要修改的一个或多个数据流ID，需要修改的一个或多个数据流对应的Non-GBR业务的QoS信息，需要修改的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要删除的一个或多个数据流ID。
在本公开的一个实施例中，用户面配置信息为PDU会话删除流程中待删除用户面配置信息，其中，用户面配置信息可以包括以下至少之一信息：每个待删除PDCP实体的索引ID和删除原因。
需要说明的是，上述装置还可以包括：第六发送模块，与上述配置模块54连接，设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C发送用户面配置删除成功消息，其中，用户面配置删除成功消息包括：删除成功的PDCP实体的索引ID。
需要说明的是，上述获取模块52，还可以设置为通过Xn接口从CU-C中获取指定信息，其中，指定信息包括删除PDU会话相关信息，删除PDU会话相关信息为CU-C通过NG接口从核心网获取的，其中，删除PDU会话相关信息中包括以下至少之一信息：会话ID和会话删除原因。
需要说明的是，上述装置可以位于CU-U中，但并不限于此。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本公开实施例还提供了一种用户面集中处理单元CU-U，图6是根据本公开实施例提供的CU-U的结构框图，如图6所示，该CU-U包括：
射频模块62，设置为通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，其中，Xn接口为控制面集中处理单元CU-C和用户面集中处理单元CU-U之间的接口；
处理器64，与上述射频模块62连接，设置为根据指定信息对每个PDCP实体进行配置操作。
通过上述CU-U，由于可以通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，进而可以根据该指定信息对上述每个PDCP实体进行配置操作，实现了CU-U的协议实体配置，因此，可以解决如何实现CU-U协议实体的配置的问题，实现了集中化业务汇聚。
需要说明的是，上述指定信息可以包括以下至少之一：协议数据单元PDU会话信息，用户面配置信息。
可选地，在所述指定信息包括所述PDU会话信息的情况下，上述处理器64，还可以设置为根据获取的所述PDU会话信息以及所述PDU会话信息与所述用户面配置信息的对应关系确定与获取的所述PDU会话信息对应的用户面配置信息；根据与获取的所述PDU会话信息对应的用户面配置信息对所述每个PDCP实体进行配置操作。
需要说明的是，在所述指定信息包括所述用户面配置信息的情况下，上述处理器64，还可以设置为根据所述用户面配置信息直接对所述每个PDCP实体进行配置操作。
需要说明的是，上述PDU会话信息可以是以下之一流程中的PDU会话信息：PDU会话建立流程、PDU会话修改流程和PDU会话删除流程。
在本公开的一个实施例中，在PDU会话信息为PDU会话建立流程中建立PDU会话所需要的信息时，PDU会话信息包括以下至少之一：会话标识ID，单个会话中一个或多个数据流ID，一个或多个数据流对应的非保证码速率Non-GBR业务的服务质量QoS信息，一个或多个数据流对应的保证码速率GBR业务的QoS信息和Xn接口识别终端的标志信息。
需要说明的是，上述射频模块62，还可以设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C发送PDU会话建立成功消息，其中，PDU会话建立成功消息中携带成功完成配置的PDU会话信息；其中，成功完成配置的PDU会话信息包括以下至少之一信息：会话ID，单个会话中成功完成用户面配置的一个或多个数据流ID，Xn接口 识别终端的标志信息，单个会话中用户面配置失败的一个或多个数据流ID和配置失败原因；或者，向CU-C发送PDU会话建立失败消息，其中，PDU会话建立失败消息中包括以下至少之一信息：用户面配置失败原因，Xn接口识别终端的标志信息。
在本公开的一个实施例中，在PDU会话信息为PDU会话修改流程中待修改的PDU会话信息时，PDU会话信息包括以下至少之一：会话标识ID，单个会话中需要添加的一个或多个数据流ID，需要添加的一个或多个数据流对应的Non-GBR业务的QoS信息，需要添加的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要修改的一个或多个数据流ID，需要修改的一个或多个数据流对应的Non-GBR业务的QoS信息，需要修改的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要删除的一个或多个数据流ID，Xn接口识别终端的标志信息。
需要说明的是，上述配置操作包括以下至少之一：配置新增、配置修改和配置删除。
需要说明的是，上述射频模块62，还可以设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C发送PDU会话修改成功消息，其中，PDU会话修改成功消息携带有成功完成配置修改的PDU会话信息；其中，成功完成配置修改的PDU会话信息包括以下至少之一：会话ID，单个会话中成功完成用户面配置修改的一个或多个数据流ID，单个会话中用户面配置修改失败的一个或多个数据流ID，修改失败原因和所述Xn接口识别终端的标志信息；或者，向CU-C发送PDU会话修改失败消息，其中，PDU会话修改失败消息包括：PDU会话用户面配置失败的原因和所述Xn接口识别终端的标志信息。
在本公开的一个实施例中，在PDU会话信息为PDU会话删除流程中待删除PDU会话信息时，PDU会话信息包括以下至少之一：会话ID，会话删除原因和Xn接口识别终端的标志信息。
需要说明的是，上述射频模块62，设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C发送PDU会话删除成功消息，其中，PDU会话删除成功消息包括以下至少之一信息：删除成功的会话ID和Xn接口识别终端的标志信息。
需要说明的是，上述用户面配置信息也可以是以下之一流程中的用户面配置信息：PDU会话建立流程、PDU会话修改流程和PDU会话删除流程。
需要说明的是，上述用户面配置信息可以通过新定义Xn AP消息明文传递，也可以通过Xn AP消息通过容器的方式传递，但并不限于此。
在本公开的一个实施例中，用户面配置信息为PDU会话建立流程中的用户面配置信息，其中，用户面配置信息包括以下至少之一信息：每个待配置PDCP实体的索引ID和 每个待配置PDCP实体的配置信息。
需要说明的是，每个待配置PDCP实体的配置信息包括以下至少之一：每个待配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息。
需要说明的是，上述射频模块62，还可以设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C发送配置完成确认消息，其中，配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息；或者，向CU-C发送配置失败信息，其中，配置失败信息包括：配置失败原因。
需要说明的是，上述射频模块62，还可以设置为通过Xn接口从CU-C中获取指定信息；其中，指定信息包括PDU会话相关信息；PDU会话相关信息为CU-C通过NG接口从核心网获取的，PDU会话相关信息包括以下至少之一：会话ID，单个会话中一个或多个数据流ID，一个或多个数据流对应的非保证码速率Non-GBR业务的服务质量QoS信息和一个或多个数据流对应的保证码速率GBR业务的QoS信息；其中，NG接口为CU-U与核心网之间的接口。
在本公开的一个实施例中，用户面配置信息为PDU会话修改流程中待修改的用户面配置信息，其中，用户面配置信息可以包括以下至少之一信息：每个待新增配置PDCP实体的索引ID和每个待新增配置PDCP实体的配置信息；每个待修改配置PDCP实体的索引ID和每个待修改配置PDCP实体的配置信息；每个待删除PDCP实体的索引ID。
需要说明的是，每个待新增配置PDCP实体的配置信息包括以下至少之一信息：每个待新增配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息；每个待修改配置PDCP实体的配置信息包括以下至少之一信息：每个待修改配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息。
需要说明的是，上述射频模块62，还可以设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C发送配置完成确认消息，其中，配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息，一个或多个配置修改失败的PDCP实体索引信息，修改失败原因；或者，向CU-C发送配置失败信息，其中，配置失败信息包括：配置失败 原因。
需要说明的是，上述射频模块62，还可以设置为通过Xn接口从CU-C中获取指定信息；其中，指定信息包括修改PDU会话相关信息，修改PDU会话相关信息为CU-C通过NG接口从核心网获取的，其中，修改PDU会话相关信息包括以下至少之一：会话标识ID，单个会话中需要添加的一个或多个数据流ID，需要添加的一个或多个数据流对应的Non-GBR业务的QoS信息，需要添加的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要修改的一个或多个数据流ID，需要修改的一个或多个数据流对应的Non-GBR业务的QoS信息，需要修改的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要删除的一个或多个数据流ID。
在本公开的一个实施例中，用户面配置信息为PDU会话删除流程中待删除用户面配置信息，其中，用户面配置信息包括以下至少之一信息：每个待删除PDCP实体的索引ID和删除原因。
需要说明的是，上述射频模块62，还可以设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C发送用户面配置删除成功消息，其中，用户面配置删除成功消息包括：删除成功的PDCP实体的索引ID。
需要说明的是，上述射频模块62，还可以设置为通过Xn接口从CU-C中获取指定信息，其中，指定信息包括删除PDU会话相关信息，删除PDU会话相关信息为CU-C通过NG接口从核心网获取的，其中，删除PDU会话相关信息中包括以下至少之一信息：会话ID和会话删除原因。
实施例4
本申请实施例还提供了一种实体配置系统，图7是根据本公开实施例提供的实体配置系统的结构框图，如图7所示，该系统包括：控制面集中处理单元CU-C72，用户面集中处理单元CU-U74和Xn接口76，其中，Xn接口76为CU-C72和CU-U74之间的接口；CU-C72，设置为通过Xn接口76向CU-U74发送用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息；CU-U74，设置为接收指定信息，以及根据指定信息对每个PDCP实体进行配置操作。
通过上述系统，由于CU-U74可以通过Xn接口76获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，进而可以根据该指定信息对上述每个PDCP实体进行配置操作，实现了CU-U的协议实体配置，因此，可以解决如何实现CU-U协议实体的配置的问题，实现了集中化业务汇聚。
需要说明的是，上述指定信息可以包括以下至少之一：协议数据单元PDU会话信息，用户面配置信息。
需要说明的是，在所述指定信息包括所述PDU会话信息的情况下，上述CU-U74，还可以设置为根据获取的所述PDU会话信息以及所述PDU会话信息与所述用户面配置信息的对应关系确定与获取的所述PDU会话信息对应的用户面配置信息；根据与获取的所述PDU会话信息对应的用户面配置信息对所述每个PDCP实体进行配置操作。
需要说明的是，在所述指定信息包括所述用户面配置信息的情况下，上述CU-U74，还可以根据所述用户面配置信息直接对所述每个PDCP实体进行配置操作。
需要说明的是，上述PDU会话信息可以是以下之一流程中的PDU会话信息：PDU会话建立流程、PDU会话修改流程和PDU会话删除流程。
在本公开的一个实施例中，在PDU会话信息为PDU会话建立流程中建立PDU会话所需要的信息时，PDU会话信息包括以下至少之一：会话标识ID，单个会话中一个或多个数据流ID，一个或多个数据流对应的非保证码速率Non-GBR业务的服务质量QoS信息，一个或多个数据流对应的保证码速率GBR业务的QoS信息和Xn接口识别终端的标志信息。
需要说明的是，上述CU-U74，还设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C72发送PDU会话建立成功消息，其中，PDU会话建立成功消息中携带成功完成配置的PDU会话信息；其中，成功完成配置的PDU会话信息包括以下至少之一信息：会话ID，单个会话中成功完成用户面配置的一个或多个数据流ID，Xn接口识别终端的标志信息，单个会话中用户面配置失败的一个或多个数据流ID和配置失败原因；或者，向CU-C72发送PDU会话建立失败消息，其中，PDU会话建立失败消息中包括以下至少之一信息：用户面配置失败原因，Xn接口识别终端的标志信息。
在本公开的一个实施例中，在PDU会话信息为PDU会话修改流程中待修改的PDU会话信息时，PDU会话信息包括以下至少之一：会话标识ID，单个会话中需要添加的一个或多个数据流ID，需要添加的一个或多个数据流对应的Non-GBR业务的QoS信息，需要添加的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要修改的一个或多个数据流ID，需要修改的一个或多个数据流对应的Non-GBR业务的QoS信息，需要修改的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要删除的一个或多个数据流ID，Xn接口识别终端的标志信息。
需要说明的是，上述配置操作包括以下至少之一：配置新增、配置修改和配置删除。
需要说明的是，上述CU-U74，还在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C72发送PDU会话修改成功消息，其中，PDU会话修改成功消息携带有成功完成配置修改的PDU会话信息；其中，成功完成配置修改的PDU会话信息包括以下至少之一：会话ID，单个会话中成功完成用户面配置修改的一个或多个数据流ID，单个会话中用户面配置修改失败的一个或多个数据流ID，修改失败原因和所述Xn接口识别终端的标志信息；或者，向CU-C72发送PDU会话修改失败消息，其中，PDU会话修改失败消息包括：PDU会话用户面配置失败的原因和所述Xn接口识别终端的标志信息。
在本公开的一个实施例中，在PDU会话信息为PDU会话删除流程中待删除PDU会话信息时，PDU会话信息包括以下至少之一：会话ID，会话删除原因和Xn接口识别终端的标志信息。
需要说明的是，CU-U74，还设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C72发送PDU会话删除成功消息，其中，PDU会话删除成功消息包括以下至少之一信息：删除成功的会话ID和Xn接口识别终端的标志信息。
需要说明的是，上述用户面配置信息也可以是以下之一流程中的用户面配置信息：PDU会话建立流程、PDU会话修改流程和PDU会话删除流程。
需要说明的是，上述用户面配置信息可以通过新定义Xn AP消息明文传递，也可以通过Xn AP消息通过容器的方式传递，但并不限于此。
在本公开的一个实施例中，用户面配置信息为PDU会话建立流程中的用户面配置信息，其中，用户面配置信息包括以下至少之一信息：每个待配置PDCP实体的索引ID和每个待配置PDCP实体的配置信息。
需要说明的是，每个待配置PDCP实体的配置信息包括以下至少之一：每个待配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息。
需要说明的是，CU-U74还设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C72发送配置完成确认消息，其中，配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息；或者，向CU-C72发送配置失败信息，其中，配置失败信息包括：配置失败原因。
需要说明的是，CU-C72还设置为通过NG接口从核心网获取PDU会话相关信息，其中，指定信息包括PDU会话相关信息；PDU会话相关信息包括以下至少之一：会话ID， 单个会话中一个或多个数据流ID，一个或多个数据流对应的非保证码速率Non-GBR业务的服务质量QoS信息和一个或多个数据流对应的保证码速率GBR业务的QoS信息；其中，NG接口为CU-U与核心网之间的接口。
在本公开的一个实施例中，用户面配置信息为PDU会话修改流程中待修改的用户面配置信息，其中，用户面配置信息包括以下至少之一信息：每个待新增配置PDCP实体的索引ID和每个待新增配置PDCP实体的配置信息；每个待修改配置PDCP实体的索引ID和每个待修改配置PDCP实体的配置信息；每个待删除PDCP实体的索引ID。
需要说明的是，每个待新增配置PDCP实体的配置信息包括以下至少之一信息：每个待新增配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息；每个待修改配置PDCP实体的配置信息包括以下至少之一信息：每个待修改配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息。
需要说明的是，CU-U74，还设置为在根据指定信息对每个PDCP实体进行配置操作之后，向CU-C72发送配置完成确认消息，其中，配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息，一个或多个配置修改失败的PDCP实体索引信息，修改失败原因；或者，向CU-C72发送配置失败信息，其中，配置失败信息包括：配置失败原因。
需要说明的是，CU-C72还设置为通过NG接口从核心网获取修改PDU会话相关信息，其中，指定信息包括修改PDU会话相关信息；其中，指定信息包括修改PDU会话相关信息，其中，修改PDU会话相关信息包括以下至少之一：会话标识ID，单个会话中需要添加的一个或多个数据流ID，需要添加的一个或多个数据流对应的Non-GBR业务的QoS信息，需要添加的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要修改的一个或多个数据流ID，需要修改的一个或多个数据流对应的Non-GBR业务的QoS信息，需要修改的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要删除的一个或多个数据流ID。
在本公开的一个实施例中，用户面配置信息为PDU会话删除流程中待删除用户面配置信息，其中，用户面配置信息可以包括以下至少之一信息：每个待删除PDCP实体的索引ID和删除原因。
需要说明的是，CU-U74，还可以设置为在根据指定信息对每个PDCP实体进行配置 操作之后，向CU-C72发送用户面配置删除成功消息，其中，用户面配置删除成功消息包括：删除成功的PDCP实体的索引ID。
需要说明的是，CU-C72还可以设置为通过NG接口从核心网获取删除PDU会话相关信息，其中，指定信息包括删除PDU会话相关信息，删除PDU会话相关信息为CU-C72通过NG接口从核心网获取的，其中，删除PDU会话相关信息中包括以下至少之一信息：会话ID和会话删除原因。
实施例5
本公开的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行实施例1中的方法的步骤的程序代码。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行实施例1中的方法的步骤。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
为了更好的理解本公开实施例，以下结合优选的实施例对本公开做进一步解释。
本公开优选实施例提供了两种用户面配置方法，其中，
方法一包括：
步骤1：CU-C通过NG接口的PDU会话建立流程从NGC获取PDU会话相关信息，其中包含建立PDU会话所需的信息，包括但不限于以下一种或多种信息：会话ID，单个会话中一个或多个流ID，流对应的Non-GBR业务的QoS相关信息，流对应的GBR业务的QoS相关信息；
步骤2：CU-C通过Xn接口的PDU会话建立流程将PDU会话信息传递给CU-U。其中包含建立PDU会话所需的信息，包括但不限于以下一种或多种信息：会话ID，单个会话中一个或多个流ID，流对应的Non-GBR业务的QoS相关信息，流对应的GBR业务的QoS相关信息，Xn接口识别UE的标志信息；
步骤3：CU-U收到PDU会话的相关信息后，实现本地对携带用户面数据的每个PDCP实体进行配置。
步骤4：CU-U成功完成本地配置后可以给CU-C发送PDU会话建立成功消息，把成 功完成配置的PDU会话信息反馈给CU-C，包括但不限于以下一种或多种信息：会话ID，单个会话中成功完成用户面配置的一个或多个流ID，Xn接口识别UE的标志信息。如果本地处理失败，则发送PDU会话建立失败消息，可以包含用户面配置失败原因，Xn接口识别UE的标志信息。
步骤5：根据步骤4的结果，CU-C通过NG接口给NGC发送PDU会话建立成功消息或者PDU会话建立失败消息。
其中，当PDU会话有修改或者删除的时候，CU-C同样需要通过Xn接口将PDU会话修改和删除信息通知给CU-U，使得CU-U可以进行本地用户面配置更新和删除。
方法二包括：
步骤1：CU-C通过NG接口的PDU会话建立流程从NGC获取PDU会话相关信息，其中包含建立PDU会话所需的信息，包括但不限于以下一种或多种信息：会话ID，单个会话中一个或多个流ID，流对应的Non-GBR业务的QoS相关信息，流对应的GBR业务的QoS相关信息。CU-C收到PDU会话的相关信息后，实现对CU-U的配置，对携带用户面数据的每个PDCP实体进行配置；
步骤2：CU-C通过Xn接口将用户面配置信息传递给CU-U。其中包含但不限于以下一种或多种信息：每个待配置PDCP实体的索引ID，针对用户面数据的每个PDCP实体的配置信息，包含但不限于以下一种或多种信息：是否需要头压缩，数据加密秘钥信息，PDCP SDU丢弃定时器,RLC层配置信息，MAC层配置信息，物理层配置信息。用户面配置信息可以通过新定义Xn AP消息明文传递，也可以通过Xn AP消息通过container的方式传递；
步骤3：CU-U根据接收的用户面配置信息实现本地对携带用户面数据的每个PDCP实体配置。
步骤4：可选地，CU-U在接收用户面配置并成功完成本地配置后可以给CU-C发送配置完成确认消息。如果本地处理失败，则反馈配置失败消息。
步骤5：可选地，根据步骤4的结果，CU-C通过NG接口给NGC发送PDU会话建立成功消息或者PDU会话建立失败消息。
其中，当PDU会话有修改或者删除的时候，CU-C同样需要通过Xn接口将PDU会话修改和删除所对应的每个PDCP实体的配置变化通知给CU-U进行本地用户面配置更新和删除。
采用本公开优选实施例提出的用户面配置的方法，用于定义CU-C和CU-U间Xn接 口上实现用户面配置管理，实现CU-U的协议实体配置，可实现集中化业务汇聚，以及在具备集中式的RRC/RRM功能的同时支持独立的用户面功能。
具体实施方式
如图1所示，第一网元与第二网元之间通过前传fronthaul接口进行信息交互，针对不同的时延，这里的前传可以是理想前传或非理想前传。理想前传的传输时延比较小，比如大概为几十到几百微秒，非理想前传的传输时延相对较大，比如为毫秒级，由于理想和非理想前传的区分，导致第一网元、第二网元有不同的功能划分。
如图2所示，可能的功能划分方案如下：
Option 1(RRC/PDCP分离，类似1A结构)：本选项的功能分离类似于双连接(DC)中的1A结构。RRC位于CU之内，PDCP、RLC、MAC、PHY及RF等功能均位于DU。即整个UP都位于DU。
Option2(PDCP/RLC分离)：本选项的功能分离类似于双连接(DC)中的3C结构。RRC和PDCP位于CU之内，RLC、MAC、PHY及RF等功能均位于DU。
Option 3(RLC高层/低层分离)：底层RLC(RLC的部分功能)、MAC、PHY以及RF部分位于DU之内，PDCP和高层RLC(RLC的部分功能)等功能均位于CU。
Option 4(RLC-MAC分离)：MAC、PHY以及RF部分位于DU之内，PDCP和RLC等功能均位于CU。
Option 5(MAC内部分离)：部分MAC功能(如HARQ)、PHY及RF部分均位于DU，其它上层功能位于CU。
Option 6(MAC-PHY分离)：MAC、PHY以及RF部分位于DU之内，PDCP和RLC等功能均位于CU。
Option 7(PHY内部分离)：部分MAC功能(如HARQ)、PHY及RF部分均位于DU，其它上层功能位于CU。
Option 8(PHY-RF分离)：RF部分位于DU之内，其他上层功能均位于CU。
如图3所示，用户面和控制面的两个PDCP分别位于两个不同的CU，为了方便描述，把这两个CU称为CU-C和CU-U，从而实现了用户面数据与控制面数据的分离。假设CU-C与CU-U之间存在Xn接口，CU和DU之间存在前向接口NGx，CU-C和DU之间接口称为NGx-C，CU-U和DU之间接口称为NGx-U。
优选实施例1
图8是根据本公开优选实施例1提供的方法的流程示意图，PDU会话建立时候CU-U 自行配置，如图8所示，该方法包括：
步骤1：CU-C通过NG接口的PDU会话建立流程从NGC获取PDU会话相关信息，其中包含建立PDU会话所需的信息，包括但不限于以下一种或多种信息：会话ID，单个会话中一个或多个流ID，流对应的Non-GBR业务的QoS相关信息，流对应的GBR业务的QoS相关信息；
步骤2：CU-C通过Xn接口的PDU会话建立流程将PDU会话信息传递给CU-U。其中包含建立PDU会话所需的信息，包括但不限于以下一种或多种信息：会话ID，单个会话中一个或多个流ID，流对应的Non-GBR业务的QoS相关信息，流对应的GBR业务的QoS相关信息，Xn接口识别UE的标志信息；
步骤3：CU-U收到PDU会话的相关信息后，实现本地对携带用户面数据的每个PDCP实体进行配置。
步骤4：CU-U成功完成本地配置后可以给CU-C发送PDU会话建立成功消息，把成功完成配置的PDU会话信息反馈给CU-C，包括但不限于以下一种或多种信息：会话ID，单个会话中成功完成用户面配置的一个或多个流ID，Xn接口识别UE的标志信息。如果本地处理失败，则发送PDU会话建立失败消息，可以包含用户面配置失败原因以及Xn接口识别UE的标志信息。
步骤5：根据步骤4的结果，CU-C通过NG接口给NGC发送PDU会话建立成功消息或者PDU会话建立失败消息。
优选实施例2
图9是根据本公开优选实施例2提供的方法的流程示意图，(PDU会话修改时候CU-U自行配置，如图9所示，该方法包括：
步骤1：CU-C通过NG接口的PDU会话修改流程从NGC获取PDU会话修改的相关信息，其中包含修改PDU会话所需的信息，包括但不限于以下一种或多种信息：会话ID，单个会话中需要添加的一个或多个流ID，流对应的Non-GBR业务的QoS相关信息，流对应的GBR业务的QoS相关信息，单个会话中需要修改的一个或多个流ID，流对应的Non-GBR业务的QoS相关信息，流对应的GBR业务的QoS相关信息，单个会话中需要删除的一个或多个流ID；
步骤2：CU-C通过Xn接口的PDU会话修改流程将修改的PDU会话信息传递给CU-U。其中包含建立PDU会话所需的信息，包括但不限于以下一种或多种信息：会话ID，单个会话中需要添加的一个或多个流ID，流对应的Non-GBR业务的QoS相关信息，流对应的 GBR业务的QoS相关信息，单个会话中需要修改的一个或多个流ID，流对应的Non-GBR业务的QoS相关信息，流对应的GBR业务的QoS相关信息，单个会话中需要删除的一个或多个流ID，Xn接口识别UE的标志信息；
步骤3：CU-U收到PDU会话修改的相关信息后，实现本地对携带用户面数据的1个或多个PDCP实体进行配置修改，比如新增、修改或删除。
步骤4：CU-U成功完成本地配置后可以给CU-C发送PDU会话修改成功消息，把成功完成配置修改的PDU会话信息反馈给CU-C，包括但不限于以下一种或多种信息：会话ID，单个会话中成功完成用户面配置修改的一个或多个流ID，单个会话中用户面配置修改失败的一个或多个流ID，以及修改失败原因。如果本地处理失败，则发送PDU会话修改失败消息，可以包含该PDU会话用户面配置失败原因。
步骤5：根据步骤4的结果，CU-C通过NG接口给NGC发送PDU会话修改成功消息或者PDU会话修改失败消息。
优选体实施例3
图10是根据本公开优选实施例3提供的方法的流程示意图，PDU会话删除时候CU-U自行配置，如图10所示，该方法包括：
步骤1：CU-C通过NG接口的PDU会话删除流程从NGC获取PDU会话相关信息，其中包含删除PDU会话所需的信息，包括但不限于以下一种或多种信息：会话ID，会话删除原因；
步骤2：CU-C通过Xn接口的PDU会话删除流程将待删除PDU会话信息传递给CU-U。包括但不限于以下一种或多种信息：会话ID，会话删除原因，Xn接口识别UE的标志信息；
步骤3：CU-U收到删除PDU会话的相关信息后，在本地删除对应的PDCP实体。
步骤4：CU-U成功完成本地配置后可以给CU-C发送PDU会话删除成功消息，包括但不限于以下一种或多种信息：删除成功的会话ID，Xn接口识别UE的标志信息。
步骤5：根据步骤4的结果，CU-C通过NG接口给NGC发送PDU会话删除确认消息。
优选实施例4
图11是根据本公开优选实施例4提供的方法的流程示意图，(PDU会话建立时候CU-C配置CU-U)，如图11所示，该方法包括：
步骤1：CU-C通过NG接口的PDU会话建立流程从NGC获取PDU会话相关信息， 其中包含建立PDU会话所需的信息，包括但不限于以下一种或多种信息：会话ID，单个会话中一个或多个流ID，流对应的Non-GBR业务的QoS相关信息，流对应的GBR业务的QoS相关信息。CU-C收到PDU会话的相关信息后，实现对CU-U的配置，对携带用户面数据的每个PDCP实体进行配置；
步骤2：CU-C通过Xn接口将用户面配置信息传递给CU-U。其中包含但不限于以下一种或多种信息：每个待配置PDCP实体的索引ID，针对用户面数据的每个PDCP实体的配置信息，包含但不限于以下一种或多种信息：是否需要头压缩，数据加密秘钥信息，PDCP SDU丢弃定时器，RLC层配置信息，MAC层配置信息，物理层配置信息。用户面配置信息可以通过新定义Xn AP消息明文传递，也可以通过Xn AP消息通过container的方式传递；
步骤3：CU-U根据接收的用户面配置信息实现本地对携带用户面数据的每个PDCP实体配置。
步骤4：可选地，CU-U在接收用户面配置并成功完成本地配置后可以给CU-C发送配置完成确认消息，包含一个或多个配置成功的PDCP实体索引信息，使得CU-C能在本地索引到该PDCP实体对应的流或会话。如果本地处理失败，则反馈配置失败消息，可以包含配置失败原因。
步骤5：可选地，根据步骤4的结果，CU-C通过NG接口给NGC发送PDU会话建立成功消息或者PDU会话建立失败消息。
优选实施例5
图12是根据本公开优选实施例5提供的方法的流程示意图，PDU会话修改时候CU-C配置CU-U，如图12所示，该方法包括：
步骤1：CU-C通过NG接口的PDU会话修改流程从NGC获取PDU会话修改的相关信息，其中包含修改PDU会话所需的信息，包括但不限于以下一种或多种信息：会话ID，单个会话中需要添加的一个或多个流ID，流对应的Non-GBR业务的QoS相关信息，流对应的GBR业务的QoS相关信息，单个会话中需要修改的一个或多个流ID，流对应的Non-GBR业务的QoS相关信息，流对应的GBR业务的QoS相关信息，单个会话中需要删除的一个或多个流ID；
步骤2：CU-C通过Xn接口将待修改的用户面配置信息传递给CU-U。其中包含但不限于以下一种或多种信息：每个待新增配置PDCP实体的索引ID，以及对应的PDCP实体的配置信息，每个待修改配置PDCP实体的索引ID，以及对应的PDCP实体的配置信 息，每个待删除PDCP实体的索引ID。其中针对用户面数据的每个PDCP实体的配置信息，包含但不限于以下一种或多种信息：是否需要头压缩，数据加密秘钥信息，PDCP SDU丢弃定时器，RLC层配置信息，MAC层配置信息，物理层配置信息。用户面配置信息可以通过新定义Xn AP消息明文传递，也可以通过Xn AP消息通过container的方式传递；
步骤3：CU-U根据接收的待修改的用户面配置信息实现本地对携带用户面数据的每个PDCP实体配置。
步骤4：可选地，CU-U在接收用户面配置并成功完成本地配置后可以给CU-C发送配置完成确认消息，包括但不限于以下一种或多种信息：包含一个或多个配置成功的PDCP实体索引信息，包含一个或多个配置修改失败的PDCP实体索引信息，以及修改失败原因。如果本地处理失败，则反馈配置失败消息，可以包含配置失败原因。
步骤5：可选地，根据步骤4的结果，CU-C通过NG接口给NGC发送PDU会话建立成功消息或者PDU会话建立失败消息。
优选实施例6
图13是根据本公开优选实施例6提供的方法的流程示意图，PDU会话删除时候CU-C配置CU-U，如图13所示，该方法包括：
步骤1：CU-C通过NG接口的PDU会话删除流程从NGC获取PDU会话相关信息，其中包含删除PDU会话所需的信息，包括但不限于以下一种或多种信息：会话ID，会话删除原因；
步骤2：CU-C通过Xn接口将待删除用户面配置信息传递给CU-U。其中包含但不限于以下一种或多种信息：每个待删除PDCP实体的索引ID，删除原因。用户面配置信息可以通过新定义Xn AP消息明文传递，也可以通过Xn AP消息通过container的方式传递；
步骤3：CU-U根据接收的用户面配置信息实现本地删除对应的PDCP实体。
步骤4：可选地，CU-U成功完成本地配置后可以给CU-C发送用户面配置删除成功消息，包括但不限于以下一种或多种信息：删除成功的PDCP实体的索引ID。
步骤5：可选地，根据步骤4的结果，CU-C通过NG接口给NGC发送PDU会话删除确认消息。
其中，具体实施例4、5、6中，如果假设CU-U能完全按照CU-C的请求完成本地配置，则步骤5也可以在步骤2后进行。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网 络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (51)

  1. 一种实体配置方法，包括：
    通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，其中，所述Xn接口为控制面集中处理单元CU-C和用户面集中处理单元CU-U之间的接口；
    根据所述指定信息对所述每个PDCP实体进行配置操作。
  2. 根据权利要求1所述的方法，其中，所述指定信息包括以下至少之一：协议数据单元PDU会话信息，用户面配置信息。
  3. 根据权利要求2所述的方法，其中，在所述指定信息包括所述PDU会话信息的情况下，根据所述指定信息对所述每个PDCP实体进行配置操作包括：
    根据获取的所述PDU会话信息，以及所述PDU会话信息与用户面配置信息的对应关系，确定与获取的所述PDU会话信息对应的用户面配置信息；
    根据与获取的所述PDU会话信息对应的用户面配置信息对所述每个PDCP实体进行配置操作。
  4. 根据权利要求2所述的方法，其中，在所述指定信息包括所述用户面配置信息的情况下，根据所述指定信息对所述每个PDCP实体进行配置操作包括：
    根据所述用户面配置信息直接对所述每个PDCP实体进行配置操作。
  5. 根据权利要求2所述的方法，其中，在所述PDU会话信息为PDU会话建立流程中建立PDU会话所需要的信息时，所述PDU会话信息包括以下至少之一：会话标识ID，单个会话中一个或多个数据流ID，所述一个或多个数据流对应的非保证码速率Non-GBR业务的服务质量QoS信息，所述一个或多个数据流对应的保证码速率GBR业务的QoS信息和所述Xn接口识别终端的标志信息。
  6. 根据权利要求5所述的方法，其中，在根据所述指定信息对所述每个PDCP实体进行配置操作之后，所述方法还包括：
    向所述CU-C发送PDU会话建立成功消息，其中，所述PDU会话建立成功消息中携带成功完成配置的PDU会话信息；其中，所述成功完成配置的PDU会话信息包括以下至少之一信息：所述会话ID，单个会话中成功完成用户面配置的一个或多个数据流ID，所述Xn接口识别终端的标志信息，单个会话中用户面配置失败的一个或多个数据流ID和配置失败原因；或者，
    向所述CU-C发送PDU会话建立失败消息，其中，所述PDU会话建立失败消息中包括以下至少之一信息：用户面配置失败原因，所述Xn接口识别终端的标志信息。
  7. 根据权利要求2所述的方法，其中，在所述PDU会话信息为PDU会话修改流程中待修改的PDU会话信息时，所述PDU会话信息包括以下至少之一：会话标识ID，单个会话中需要添加的一个或多个数据流ID，需要添加的一个或多个数据流对应的Non-GBR业务的QoS信息，需要添加的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要修改的一个或多个数据流ID，需要修改的一个或多个数据流对应的Non-GBR业务的QoS信息，需要修改的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要删除的一个或多个数据流ID，所述Xn接口识别终端的标志信息。
  8. 根据权利要求7所述的方法，其中，在根据所述指定信息对所述每个PDCP实体进行配置操作之后，所述方法还包括：
    向所述CU-C发送PDU会话修改成功消息，其中，所述PDU会话修改成功消息携带有成功完成配置修改的PDU会话信息；其中，所述成功完成配置修改的PDU会话信息包括以下至少之一：所述会话ID，单个会话中成功完成用户面配置修改的一个或多个数据流ID，单个会话中用户面配置修改失败的一个或多个数据流ID，修改失败原因，和所述Xn接口识别终端的标志信息；或者，
    向所述CU-C发送PDU会话修改失败消息，其中，所述PDU会话修改失败消息包括：PDU会话用户面配置失败的原因和所述Xn接口识别终端的标志信息。
  9. 根据权利要求2所述的方法，其中，在所述PDU会话信息为PDU会话删除流程中待删除PDU会话信息时，所述PDU会话信息包括以下至少之一：会话ID，会话删除原因和所述Xn接口识别终端的标志信息。
  10. 根据权利要求9所述的方法，其中，在根据所述指定信息对所述每个PDCP实体进行配置操作之后，所述方法还包括：
    向所述CU-C发送PDU会话删除成功消息，其中，所述PDU会话删除成功消息包括以下至少之一信息：删除成功的会话ID和所述Xn接口识别终端的标志信息。
  11. 根据权利要求2所述的方法，其中，所述用户面配置信息为PDU会话建立流程中的用户面配置信息，其中，所述用户面配置信息包括以下至少之一信息：每个待配置PDCP实体的索引ID和每个待配置PDCP实体的配置信息。
  12. 根据权利要求11所述的方法，其中，所述每个待配置PDCP实体的配置信息包括以下至少之一：每个待配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘 钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息。
  13. 根据权利要求11或12所述的方法，其中，在根据所述指定信息对所述每个PDCP实体进行配置操作之后，所述方法还包括：
    向所述CU-C发送配置完成确认消息，其中，所述配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息；或者，
    向所述CU-C发送配置失败信息，其中，所述配置失败信息包括：配置失败原因。
  14. 根据权利要求5、6、11和12中任一项所述的方法，其中，通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息包括：通过所述Xn接口从所述CU-C中获取所述指定信息；其中，所述指定信息包括PDU会话相关信息；所述PDU会话相关信息为所述CU-C通过NG接口从核心网获取的，所述PDU会话相关信息包括以下至少之一：会话ID，单个会话中一个或多个数据流ID，所述一个或多个数据流对应的非保证码速率Non-GBR业务的服务质量QoS信息和所述一个或多个数据流对应的保证码速率GBR业务的QoS信息；
    其中，所述NG接口为所述CU-C与所述核心网之间的接口。
  15. 根据权利要求2所述的方法，其中，所述用户面配置信息为PDU会话修改流程中待修改的用户面配置信息，其中，所述用户面配置信息包括以下至少之一信息：每个待新增配置PDCP实体的索引ID和每个待新增配置PDCP实体的配置信息；每个待修改配置PDCP实体的索引ID和每个待修改配置PDCP实体的配置信息；每个待删除PDCP实体的索引ID。
  16. 根据权利要求15所述的方法，其中，
    所述每个待新增配置PDCP实体的配置信息包括以下至少之一信息：每个待新增配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息；
    所述每个待修改配置PDCP实体的配置信息包括以下至少之一信息：每个待修改配置PDCP实体所采用的PDCP协议是否需要头压缩，数据加密秘钥信息，PDCP服务数据单元SDU丢弃定时器，无线链路层控制协议RLC层配置信息，媒体访问控制MAC层配置信息和物理层配置信息。
  17. 根据权利要求15或16所述的方法，其中，在根据所述指定信息对所述每个PDCP 实体进行配置操作之后，所述方法还包括：
    向所述CU-C发送配置完成确认消息，其中，所述配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息，一个或多个配置修改失败的PDCP实体索引信息，修改失败原因；或者，
    向所述CU-C发送配置失败信息，其中，所述配置失败信息包括：配置失败原因。
  18. 根据权利要求7、15和16中任一项所述的方法，其中，通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息包括：通过所述Xn接口从所述CU-C中获取所述指定信息；其中，所述指定信息包括修改PDU会话相关信息，所述修改PDU会话相关信息为所述CU-C通过NG接口从核心网获取的，其中，所述修改PDU会话相关信息包括以下至少之一：会话标识ID，单个会话中需要添加的一个或多个数据流ID，需要添加的一个或多个数据流对应的Non-GBR业务的QoS信息，需要添加的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要修改的一个或多个数据流ID，需要修改的一个或多个数据流对应的Non-GBR业务的QoS信息，需要修改的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要删除的一个或多个数据流ID。
  19. 根据权利要求2所述的方法，其中，所述用户面配置信息为PDU会话删除流程中待删除用户面配置信息，其中，所述用户面配置信息包括以下至少之一信息：每个待删除PDCP实体的索引ID和删除原因。
  20. 根据权利要求19所述的方法，其中，在根据所述指定信息对所述每个PDCP实体进行配置操作之后，所述方法还包括：
    向所述CU-C发送用户面配置删除成功消息，其中，所述用户面配置删除成功消息包括：删除成功的PDCP实体的索引ID。
  21. 根据权利要求9、10、19和20中任一项所述的方法，其中，通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息包括：通过所述Xn接口从所述CU-C中获取所述指定信息，其中，所述指定信息包括删除PDU会话相关信息，所述删除PDU会话相关信息为所述CU-C通过NG接口从核心网获取的，其中，所述删除PDU会话相关信息中包括以下至少之一信息：会话ID和会话删除原因。
  22. 一种实体配置装置，包括：
    获取模块，设置为通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，其中，所述Xn接口为控制面集中处理单元CU-C和 用户面集中处理单元CU-U之间的接口；
    配置模块，设置为根据所述指定信息对所述每个PDCP实体进行配置操作。
  23. 根据权利要求22所述的装置，其中，所述指定信息包括以下至少之一：协议数据单元PDU会话信息，用户面配置信息。
  24. 根据权利要求23所述的装置，其中，在所述指定信息包括所述PDU会话信息的情况下，所述配置模块，还设置为根据获取的所述PDU会话信息以及所述PDU会话信息与所述用户面配置信息的对应关系确定与获取的所述PDU会话信息对应的用户面配置信息；根据与获取的所述PDU会话信息对应的用户面配置信息对所述每个PDCP实体进行配置操作。
  25. 根据权利要求23所述的装置，其中，在所述指定信息包括所述用户面配置信息的情况下，所述配置模块，还设置为根据所述用户面配置信息直接对所述每个PDCP实体进行配置操作。
  26. 一种用户面集中处理单元CU-U，包括：
    射频模块，设置为通过Xn接口获取用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息，其中，所述Xn接口为控制面集中处理单元CU-C和用户面集中处理单元CU-U之间的接口；
    处理器，设置为根据所述指定信息对所述每个PDCP实体进行配置操作。
  27. 根据权利要求26所述的CU-U，其中，所述指定信息包括以下至少之一：协议数据单元PDU会话信息，用户面配置信息。
  28. 根据权利要求27所述的CU-U，其中，在所述指定信息包括所述PDU会话信息的情况下，所述处理器，还设置为根据获取的所述PDU会话信息以及所述PDU会话信息与所述用户面配置信息的对应关系确定与获取的所述PDU会话信息对应的用户面配置信息；根据与获取的所述PDU会话信息对应的用户面配置信息对所述每个PDCP实体进行配置操作。
  29. 根据权利要求27所述的CU-U，其中，在所述指定信息包括所述用户面配置信息的情况下，所述处理器，还设置为根据所述用户面配置信息直接对所述每个PDCP实体进行配置操作。
  30. 根据权利要求27所述的CU-U，其中，在所述PDU会话信息为PDU会话建立流程中建立PDU会话所需要的信息时，所述PDU会话信息包括以下至少之一：会话标识ID，单个会话中一个或多个数据流ID，所述一个或多个数据流对应的非保证码速率 Non-GBR业务的服务质量QoS信息，所述一个或多个数据流对应的保证码速率GBR业务的QoS信息和所述Xn接口识别终端的标志信息。
  31. 根据权利要求30所述的CU-U，其中，所述射频模块，还设置为在根据所述指定信息对所述每个PDCP实体进行配置操作之后，向所述CU-C发送PDU会话建立成功消息，其中，所述PDU会话建立成功消息中携带成功完成配置的PDU会话信息；其中，所述成功完成配置的PDU会话信息包括以下至少之一信息：所述会话ID，单个会话中成功完成用户面配置的一个或多个数据流ID，所述Xn接口识别终端的标志信息，单个会话中用户面配置失败的一个或多个数据流ID和配置失败原因；或者，向所述CU-C发送PDU会话建立失败消息，其中，所述PDU会话建立失败消息中包括以下至少之一信息：用户面配置失败原因，所述Xn接口识别终端的标志信息。
  32. 根据权利要求27所述的CU-U，其中，在所述PDU会话信息为PDU会话修改流程中待修改的PDU会话信息时，所述PDU会话信息包括以下至少之一：会话标识ID，单个会话中需要添加的一个或多个数据流ID，需要添加的一个或多个数据流对应的Non-GBR业务的QoS信息，需要添加的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要修改的一个或多个数据流ID，需要修改的一个或多个数据流对应的Non-GBR业务的QoS信息，需要修改的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要删除的一个或多个数据流ID，所述Xn接口识别终端的标志信息。
  33. 根据权利要求32所述的CU-U，其中，所述射频模块，还设置为在根据所述指定信息对所述每个PDCP实体进行配置操作之后，向所述CU-C发送PDU会话修改成功消息，其中，所述PDU会话修改成功消息携带有成功完成配置修改的PDU会话信息；其中，所述成功完成配置修改的PDU会话信息包括以下至少之一：所述会话ID，单个会话中成功完成用户面配置修改的一个或多个数据流ID，单个会话中用户面配置修改失败的一个或多个数据流ID，修改失败原因和所述Xn接口识别终端的标志信息；或者，向所述CU-C发送PDU会话修改失败消息，其中，所述PDU会话修改失败消息包括：PDU会话用户面配置失败的原因和所述Xn接口识别终端的标志信息。
  34. 根据权利要求27所述的CU-U，其中，在所述PDU会话信息为PDU会话删除流程中待删除PDU会话信息时，所述PDU会话信息包括以下至少之一：会话ID，会话删除原因和所述Xn接口识别终端的标志信息。
  35. 根据权利要求34所述的CU-U，其中，所述射频模块，设置为在根据所述指定信息对所述每个PDCP实体进行配置操作之后，向所述CU-C发送PDU会话删除成功消息， 其中，所述PDU会话删除成功消息包括以下至少之一信息：删除成功的会话ID和所述Xn接口识别终端的标志信息。
  36. 根据权利要求27所述的CU-U，其中，所述用户面配置信息为PDU会话建立流程中的用户面配置信息，其中，所述用户面配置信息包括以下至少之一信息：每个待配置PDCP实体的索引ID和每个待配置PDCP实体的配置信息。
  37. 根据权利要求36所述的CU-U，其中，所述射频模块，还设置为在根据所述指定信息对所述每个PDCP实体进行配置操作之后，向所述CU-C发送配置完成确认消息，其中，所述配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息；或者，向所述CU-C发送配置失败信息，其中，所述配置失败信息包括：配置失败原因。
  38. 根据权利要求27所述的CU-U，其中，所述用户面配置信息为PDU会话修改流程中待修改的用户面配置信息，其中，所述用户面配置信息包括以下至少之一信息：每个待新增配置PDCP实体的索引ID和每个待新增配置PDCP实体的配置信息；每个待修改配置PDCP实体的索引ID和每个待修改配置PDCP实体的配置信息；每个待删除PDCP实体的索引ID。
  39. 根据权利要求38所述的CU-U，其中，所述射频模块，设置为在根据所述指定信息对所述每个PDCP实体进行配置操作之后，向所述CU-C发送配置完成确认消息，其中，所述配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息，一个或多个配置修改失败的PDCP实体索引信息，修改失败原因；或者，向所述CU-C发送配置失败信息，其中，所述配置失败信息包括：配置失败原因。
  40. 根据权利要求27所述的CU-U，其中，所述用户面配置信息为PDU会话删除流程中待删除用户面配置信息，其中，所述用户面配置信息包括以下至少之一信息：每个待删除PDCP实体的索引ID和删除原因。
  41. 根据权利要求40所述的CU-U，其中，所述射频模块，还设置为在根据所述指定信息对所述每个PDCP实体进行配置操作之后，向所述CU-C发送用户面配置删除成功消息，其中，所述用户面配置删除成功消息包括：删除成功的PDCP实体的索引ID。
  42. 一种实体配置系统，包括：控制面集中处理单元CU-C，用户面集中处理单元CU-U和Xn接口，其中，所述Xn接口为所述CU-C和所述CU-U之间的接口；
    所述CU-C，设置为通过所述Xn接口向所述CU-U发送用于对处理数据无线承载的每个分组数据汇聚协议PDCP实体进行配置的指定信息；
    所述CU-U，设置为接收所述指定信息，以及根据所述指定信息对所述每个PDCP实 体进行配置操作。
  43. 根据权利要求42所述的系统，其中，所述CU-U，还设置为在根据所述指定信息对所述每个PDCP实体进行配置操作之后，向所述CU-C发送PDU会话建立成功消息，其中，所述PDU会话建立成功消息中携带成功完成配置的PDU会话信息；其中，所述成功完成配置的PDU会话信息包括以下至少之一信息：所述会话ID，单个会话中成功完成用户面配置的一个或多个数据流ID，所述Xn接口识别终端的标志信息，单个会话中用户面配置失败的一个或多个数据流ID和配置失败原因；或者，向所述CU-C发送PDU会话建立失败消息，其中，所述PDU会话建立失败消息中包括以下至少之一信息：用户面配置失败原因，所述Xn接口识别终端的标志信息。
  44. 根据权利要求42所述的系统，其中，所述CU-U，还在根据所述指定信息对所述每个PDCP实体进行配置操作之后，向所述CU-C发送PDU会话修改成功消息，其中，所述PDU会话修改成功消息携带有成功完成配置修改的PDU会话信息；其中，所述成功完成配置修改的PDU会话信息包括以下至少之一：所述会话ID，单个会话中成功完成用户面配置修改的一个或多个数据流ID，单个会话中用户面配置修改失败的一个或多个数据流ID，修改失败原因和所述Xn接口识别终端的标志信息；或者，向所述CU-C发送PDU会话修改失败消息，其中，所述PDU会话修改失败消息包括：PDU会话用户面配置失败的原因和所述Xn接口识别终端的标志信息。
  45. 根据权利要求42所述的系统，其中，所述CU-U，还设置为在根据所述指定信息对所述每个PDCP实体进行配置操作之后，向所述CU-C发送PDU会话删除成功消息，其中，所述PDU会话删除成功消息包括以下至少之一信息：删除成功的会话ID和所述Xn接口识别终端的标志信息。
  46. 根据权利要求42所述的系统，其中，所述CU-U还设置为在根据所述指定信息对所述每个PDCP实体进行配置操作之后，向所述CU-C发送配置完成确认消息，其中，所述配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息；或者，向所述CU-C发送配置失败信息，其中，所述配置失败信息包括：配置失败原因。
  47. 根据权利要求43或46所述的系统，其中，所述CU-C还设置为通过NG接口从核心网获取PDU会话相关信息，其中，所述指定信息包括PDU会话相关信息；所述PDU会话相关信息包括以下至少之一：会话ID，单个会话中一个或多个数据流ID，所述一个或多个数据流对应的非保证码速率Non-GBR业务的服务质量QoS信息和所述一个或多个数据流对应的保证码速率GBR业务的QoS信息；
    其中，所述NG接口为所述CU-C(笔误)与所述核心网之间的接口。
  48. 根据权利要求42所述的系统，其中，所述CU-U，还设置为在根据所述指定信息对所述每个PDCP实体进行配置操作之后，向所述CU-C发送配置完成确认消息，其中，所述配置完成确认消息包括：一个或多个配置成功的PDCP实体索引信息，一个或多个配置修改失败的PDCP实体索引信息，修改失败原因；或者，向所述CU-C发送配置失败信息，其中，所述配置失败信息包括：配置失败原因。
  49. 根据权利要求44或48所述的系统，其中，所述CU-C还设置为通过NG接口从核心网获取修改PDU会话相关信息，其中，所述指定信息包括修改PDU会话相关信息；其中，所述指定信息包括修改PDU会话相关信息，其中，所述修改PDU会话相关信息包括以下至少之一：会话标识ID，单个会话中需要添加的一个或多个数据流ID，需要添加的一个或多个数据流对应的Non-GBR业务的QoS信息，需要添加的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要修改的一个或多个数据流ID，需要修改的一个或多个数据流对应的Non-GBR业务的QoS信息，需要修改的一个或多个数据流对应的GBR业务的QoS信息，单个会话中需要删除的一个或多个数据流ID。
  50. 根据权利要求42所述的系统，其中，所述CU-U，还设置为在根据所述指定信息对所述每个PDCP实体进行配置操作之后，向所述CU-C发送用户面配置删除成功消息，其中，所述用户面配置删除成功消息包括：删除成功的PDCP实体的索引ID。
  51. 根据权利要求42或50所述的系统，其中，所述CU-C还设置为通过NG接口从核心网获取删除PDU会话相关信息，其中，所述指定信息包括所述删除PDU会话相关信息，所述删除PDU会话相关信息为所述CU-C通过NG接口从核心网获取的，其中，所述删除PDU会话相关信息中包括以下至少之一信息：会话ID和会话删除原因。
PCT/CN2017/114952 2017-01-16 2017-12-07 实体配置方法、装置及系统、cu-u WO2018130026A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP17890976.8A EP3570582B1 (en) 2017-01-16 2017-12-07 Entity configuration method, device and system, and cu-u
EP22209835.2A EP4192083A1 (en) 2017-01-16 2017-12-07 Entity configuration method, device and system, and cu-u
FIEP17890976.8T FI3570582T3 (fi) 2017-01-16 2017-12-07 Entiteetin konfigurointimenetelmä, -laite ja -järjestelmä sekä cu-u
US16/511,817 US11019680B2 (en) 2017-01-16 2019-07-15 Entity configuration method, device and system, and CU-U
US17/328,461 US11765787B2 (en) 2017-01-16 2021-05-24 Entity configuration method, device and system, and CU-U

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710032552.4A CN108616910B (zh) 2017-01-16 2017-01-16 实体配置方法、装置及系统、cu-u
CN201710032552.4 2017-01-16

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/511,817 Continuation US11019680B2 (en) 2017-01-16 2019-07-15 Entity configuration method, device and system, and CU-U

Publications (1)

Publication Number Publication Date
WO2018130026A1 true WO2018130026A1 (zh) 2018-07-19

Family

ID=62839765

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/114952 WO2018130026A1 (zh) 2017-01-16 2017-12-07 实体配置方法、装置及系统、cu-u

Country Status (5)

Country Link
US (2) US11019680B2 (zh)
EP (2) EP4192083A1 (zh)
CN (2) CN112637870A (zh)
FI (1) FI3570582T3 (zh)
WO (1) WO2018130026A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11968558B2 (en) 2018-09-28 2024-04-23 Huawei Technologies Co., Ltd. Data transmission method and apparatus

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112637870A (zh) * 2017-01-16 2021-04-09 中兴通讯股份有限公司 实体配置方法、装置及系统、cu-u
CN109246837B (zh) * 2017-06-12 2023-05-05 华为技术有限公司 通信方法和装置以及无线接入网络
CN109565474B (zh) * 2017-07-25 2022-05-06 北京小米移动软件有限公司 数据传输方法及装置、电子设备和计算机可读存储介质
CN111031551B (zh) * 2018-10-09 2021-08-06 大唐移动通信设备有限公司 一种基于集中式基站控制面的系统构架
CN113766461A (zh) * 2020-06-01 2021-12-07 中国电信股份有限公司 用户面数据处理方法和基站

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104519529A (zh) * 2013-09-27 2015-04-15 上海贝尔股份有限公司 一种用于对用户设备进行传输控制的方法、设备与系统
CN104735703A (zh) * 2015-04-15 2015-06-24 北京邮电大学 一种主基站、用户终端和通信系统
CN105813213A (zh) * 2014-12-31 2016-07-27 中国电信股份有限公司 双连接方案中传输数据的方法、基站和系统
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8682243B2 (en) * 2011-07-27 2014-03-25 Intel Mobile Communications GmbH Network selection device and method for selecting a communication network
ES2552251T3 (es) * 2011-08-09 2015-11-26 Telefonaktiebolaget L M Ericsson (Publ) Método y disposición para control de potencia de enlace ascendente
WO2014012248A1 (zh) * 2012-07-20 2014-01-23 华为技术有限公司 一种业务传输方法、设备及系统
EP2922240B1 (en) * 2012-11-19 2018-01-10 Huawei Technologies Co., Ltd. Method for configuring user data monitoring path, monitoring method, apparatus and entity
CN103945559B (zh) * 2013-01-18 2019-02-15 中兴通讯股份有限公司 网络接入系统及方法
KR102059042B1 (ko) * 2013-05-10 2020-02-11 주식회사 팬택 이중연결 시스템에서 멀티 플로우를 고려한 순차적 전달 방법 및 장치
KR102130296B1 (ko) * 2013-07-31 2020-07-08 삼성전자주식회사 단말 대 단말 통신을 지원하는 단말 및 그 동작 방법
US9648514B2 (en) * 2013-08-09 2017-05-09 Blackberry Limited Method and system for protocol layer enhancements in data offload over small cells
EP3923614B1 (en) * 2014-11-10 2024-01-03 LG Electronics Inc. Device and method for transmitting a ciphering indication
US10341466B2 (en) * 2014-11-14 2019-07-02 Qualcomm Incorporated Evolved data compression scheme signaling
GB2534865A (en) * 2015-01-30 2016-08-10 Nec Corp Communication system
CN106211352A (zh) * 2015-05-04 2016-12-07 中兴通讯股份有限公司 数据无线承载的建立方法和装置
EP3113539A1 (en) * 2015-06-30 2017-01-04 Vodafone IP Licensing limited Load balancing user plane traffic in a telecommunication network
CN106102106B (zh) * 2016-06-20 2020-03-24 电信科学技术研究院 一种终端接入的方法、装置及网络架构
CN112637870A (zh) * 2017-01-16 2021-04-09 中兴通讯股份有限公司 实体配置方法、装置及系统、cu-u

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104519529A (zh) * 2013-09-27 2015-04-15 上海贝尔股份有限公司 一种用于对用户设备进行传输控制的方法、设备与系统
CN105813213A (zh) * 2014-12-31 2016-07-27 中国电信股份有限公司 双连接方案中传输数据的方法、基站和系统
CN104735703A (zh) * 2015-04-15 2015-06-24 北京邮电大学 一种主基站、用户终端和通信系统
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11968558B2 (en) 2018-09-28 2024-04-23 Huawei Technologies Co., Ltd. Data transmission method and apparatus

Also Published As

Publication number Publication date
US11765787B2 (en) 2023-09-19
FI3570582T3 (fi) 2023-01-31
EP3570582B1 (en) 2022-11-30
US20200367315A1 (en) 2020-11-19
CN108616910A (zh) 2018-10-02
CN112637870A (zh) 2021-04-09
EP3570582A1 (en) 2019-11-20
US20210282221A1 (en) 2021-09-09
EP3570582A4 (en) 2020-10-21
US11019680B2 (en) 2021-05-25
CN108616910B (zh) 2020-12-01
EP4192083A1 (en) 2023-06-07

Similar Documents

Publication Publication Date Title
WO2018130026A1 (zh) 实体配置方法、装置及系统、cu-u
KR102407078B1 (ko) 사용자 정보 관리를 위한 방법 및 시스템
US11240699B2 (en) Insufficient resources in the UE during PDU session establishment procedure
US20230262557A1 (en) Methods and devices for enhancing integrated access backhaul networks for new radio
US11382152B2 (en) Method and device for configuring GTP transmission channel and storage medium
WO2019140955A1 (zh) 地址发送的方法、装置及存储介质
US20230199879A1 (en) Methods and devices for enhancing integrated access backhaul networks for new radio

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17890976

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017890976

Country of ref document: EP

Effective date: 20190816