WO2019137519A1 - 一种cu-du架构下重复模式的通信处理方法和设备 - Google Patents

一种cu-du架构下重复模式的通信处理方法和设备 Download PDF

Info

Publication number
WO2019137519A1
WO2019137519A1 PCT/CN2019/071563 CN2019071563W WO2019137519A1 WO 2019137519 A1 WO2019137519 A1 WO 2019137519A1 CN 2019071563 W CN2019071563 W CN 2019071563W WO 2019137519 A1 WO2019137519 A1 WO 2019137519A1
Authority
WO
WIPO (PCT)
Prior art keywords
radio bearer
message
signaling radio
identifier
primary channel
Prior art date
Application number
PCT/CN2019/071563
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
Priority to KR1020217031958A priority Critical patent/KR102352184B1/ko
Priority to JP2019543879A priority patent/JP6900495B2/ja
Priority to AU2019207254A priority patent/AU2019207254B2/en
Priority to EP19738568.5A priority patent/EP3570626B1/en
Priority to KR1020197022576A priority patent/KR102311647B1/ko
Priority to RU2019126510A priority patent/RU2779030C2/ru
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to BR112019018068-0A priority patent/BR112019018068A2/pt
Priority to CA3049053A priority patent/CA3049053C/en
Priority to EP23158759.3A priority patent/EP4221443A3/en
Priority to US16/454,397 priority patent/US10925103B2/en
Publication of WO2019137519A1 publication Critical patent/WO2019137519A1/zh
Priority to US17/155,798 priority patent/US11483883B2/en

Links

Images

Classifications

    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • the embodiments of the present application relate to the field of wireless communications, and in particular, to a communication processing technology in a duplication mode in a CU-DU architecture.
  • the terminal side device and the access network side device pass through various protocol layers established by the 3rd generation partnership project (3GPP) on the uplink and downlink.
  • a radio bearer (RB) transmits various data, such as transmitting control signaling on a signaling radio bearer or transmitting service data on a data radio bearer.
  • These protocol layers include a physical (PHY) layer, a media access control (MAC) layer, a radio link control (RLC), and a Packet Data Convergence Protocol (PDCP) layer. And a radio resource control (RRC) layer or the like.
  • the access network side device may further be divided into a centralized unit (CU) and a distributed unit (DU) according to a protocol layer, where the CU and the DU include a control plane connection and User plane connection, which is also called user plane (UP) tunnel.
  • a user plane tunnel is determined by an upstream tunnel endpoint on the CU and a downstream tunnel endpoint on the DU.
  • the CU is used to implement the functions of the PDCP layer and the functions of the RRC layer
  • the DU is used to implement the functions of the PHY layer, the functions of the MAC layer, and the functions of the RLC layer.
  • one PDCP entity that is radio bearer in the PDCP layer corresponds to at least two RLC entities of the RLC layer; part or all of the data on the one PDCP entity is on the at least two RLC entities. Repeated transmission, this processing is called repeat mode.
  • a repeating pattern is specific to a radio bearer.
  • the embodiment of the present application provides a communication processing method in a repeat mode of a CU-DU architecture, which implements establishment of a connection between CU-DUs in a repeat mode.
  • a first aspect of the embodiments of the present application provides a communication processing method in a repeat mode of a CU-DU architecture, including the following content.
  • the CU sends a first message to the DU, where the first message indicates information of at least two uplink tunnel endpoints on the interface between the CU and the DU in a repeating mode of the data radio bearer; the CU receiving station a second message sent by the DU, where the information indicating that the data radio bears at least two downlink tunnel endpoints on an interface between the CU and the DU and a primary channel of the data radio bearer are indicated in the second message Logo.
  • each of the at least two downlink tunnel endpoints corresponds to each of the at least two uplink tunnel endpoints.
  • the DU in the process of establishing at least two user plane tunnels between the CU and the DU through the interaction between the information of the uplink tunnel endpoint and the information of the downlink tunnel endpoint, the DU provides the primary channel to the CU. Identifying, so that the CU and the DU know which user plane tunnel corresponding to the primary channel is, thereby establishing a connection between the primary channel and the user plane tunnel corresponding to the primary channel, and implementing the connection from the CU to the DU The repeat mode of the data radio bearer.
  • the DU since the information of the at least two uplink endpoints is indicated in the first message (indicating that at least two user plane tunnels are to be established), the DU may default to the said radio bearer for the data. Repeat mode for configuration.
  • one of the CU and the DU may determine which user plane tunnel corresponds to the primary channel, but the identity of the primary channel is notified by the DU to the CU through the second message.
  • the first message further indicates that the repeating mode is configured for the data radio bearer.
  • the CU indicates, by using the first message, that the repeat mode of the data radio bearer of the DU needs to be configured.
  • the identifier of the primary channel is the at least two downlinks indicated in the second message. ID of the channel corresponding to only one downstream tunnel endpoint in the tunnel endpoint.
  • the DU may notify the identifier of the channel corresponding to only one downlink tunnel endpoint, and the identifier of the channel corresponding to the only one downlink tunnel endpoint is the identifier of the primary channel.
  • the first message further includes an uplink tunnel endpoint corresponding to the primary channel of the at least two uplink tunnel endpoints; or the second message further indicates that the at least two downlink tunnel endpoints correspond to the primary a downlink tunnel endpoint of the channel; or, the uplink tunnel endpoint corresponding to the primary channel of the at least two uplink tunnel endpoints is a protocol pre-defined; or the corresponding one of the at least two downlink tunnel endpoints
  • the downstream tunnel endpoint is predefined for the protocol.
  • the user plane tunnel corresponding to the primary channel may be clarified by a CU, a DU, or a protocol predefined manner.
  • the method further includes: the CU passing the DU to the terminal side device Notifying the identity of the primary channel of the data radio bearer.
  • the fourth possible implementation manner of the first aspect may enable the terminal side device to learn the primary channel, thereby completing determination of the primary channel between the CU, the DU, and the terminal side device.
  • a second aspect of the embodiments of the present application provides a communication processing method for a repeat mode in a CU-DU architecture, including the following.
  • the CU sends an identifier of the signaling radio bearer to the DU and indication information for indicating a repetition mode of the signaling radio bearer; the CU receives the repetition mode of the signaling radio bearer sent by the DU The configuration and the identity of the primary channel of the signaling radio bearer.
  • the DU may perform configuration of a signaling radio bearer under the indication of the CU, and enable the CU to know where the main channel of the signaling radio bearer is.
  • the method further includes: the CU sending a CU-DU interface message to the DU;
  • the CU-DU interface message includes an RRC message belonging to the signaling radio bearer;
  • the CU-DU interface message contains at least two RRC messages having the same PDCP number belonging to the signaling radio bearer.
  • a first possible implementation of the second aspect provides an implementation in which the CU sends an RRC message if the repeat mode is activated or deactivated.
  • the method further includes: the CU sending a CU-DU interface message to the DU, where the CU-DU interface message includes at least one RRC And an identifier of a message to which each RRC message of the at least one RRC message is sent.
  • the second possible implementation of the second aspect provides another implementation manner in which the CU sends an RRC message, and the DU may determine, according to the identifier of the channel to which each RRC message is sent, the sending of each RRC message.
  • the method further includes:
  • the CU notifies the terminal side device of the identifier of the primary channel of the signaling radio bearer by using the DU.
  • the third possible implementation manner of the second aspect may enable the terminal side device to learn the primary channel, thereby completing the determination of the primary channel between the CU, the DU, and the terminal side device.
  • a third aspect of the embodiments of the present application provides a communication processing method in a repeat mode of a CU-DU architecture, including the following content.
  • the DU receives a first message sent by the CU, where the first message indicates information of at least two uplink tunnel endpoints on a interface between the CU and the DU in a repeating mode of a data radio bearer; a second message sent by the CU, where the information indicating that the data radio bears at least two downlink tunnel endpoints on an interface between the CU and the DU and a primary channel of the data radio bearer Logo.
  • each of the at least two downlink tunnel endpoints corresponds to each of the at least two uplink tunnel endpoints.
  • the third aspect corresponds to the first aspect and has similar advantageous effects in the first aspect.
  • the first message further indicates that the repeating mode is configured for the data radio bearer.
  • the first possible implementation of the third aspect corresponds to the first possible implementation of the first aspect, with similar advantages to the first possible implementation of the first aspect.
  • the identifier of the primary channel is the at least two downlinks indicated in the second message ID of the channel corresponding to only one downstream tunnel endpoint in the tunnel endpoint.
  • the second possible implementation manner of the third aspect corresponds to the second possible implementation manner of the first aspect, and has the similar beneficial effects of the second possible implementation manner of the third aspect
  • the third message further includes the at least two uplink tunnel endpoints And corresponding to the uplink tunnel endpoint of the primary channel; or, the second message further indicates a downlink tunnel endpoint corresponding to the primary channel of the at least two downlink tunnel endpoints; or the at least two uplink tunnel endpoints
  • the uplink tunnel endpoint corresponding to the primary channel is predefined by a protocol; and the uplink tunnel endpoint corresponding to the primary channel of the at least two downlink tunnel endpoints is predefined by a protocol.
  • a third possible implementation of the third aspect corresponds to the third possible implementation of the first aspect, having similar benefits to the third possible implementation of the first aspect.
  • a fourth aspect of the embodiments of the present application provides a communication processing method in a repeat mode of a CU-DU architecture, including the following content.
  • the fourth aspect corresponds to the second aspect and has similar advantageous effects in the second aspect.
  • the method further includes:
  • the CU-DU interface message includes an RRC message belonging to the signaling radio bearer; the DU passes the one through the main channel The RRC message is sent to the terminal side device; or
  • the CU-DU interface message includes at least two RRC messages having the same PDCP number belonging to the signaling radio bearer;
  • the primary channel and the at least one secondary channel respectively send the at least two RRC messages to the terminal side device.
  • the first possible implementation of the fourth aspect corresponds to the first possible implementation of the second aspect, with similar advantages to the first possible implementation of the second aspect.
  • the method further includes:
  • the CU-DU interface message is sent by the CU, where the CU-DU interface message includes at least one RRC message and an identifier of a channel to which each RRC message of the at least one RRC message is sent.
  • the second possible implementation of the fourth aspect corresponds to the second possible implementation of the second aspect, and has the similar beneficial effects of the first possible implementation of the second aspect.
  • the method further includes: the DU receiving a CU-DU interface message sent by the CU, where the CU-DU interface message includes an RRC message ; among them,
  • the DU sends the RRC message to the terminal side device through the secondary channel; or if the PDCP number of the RRC message is not repeated, the DU passes the primary channel. Sending the RRC message to the terminal side device.
  • the DU may determine whether to send the RRC message to the primary channel or the secondary channel by determining whether the PDCP number of the received RRC message is repeatedly generated.
  • the fifth aspect of the embodiment of the present application provides an access network side device, where the access network side device includes a receiving unit and a sending unit.
  • the receiving unit is configured to perform the foregoing first aspect, the second aspect, the third aspect, the fourth aspect, or the receiving action in various possible implementation manners, where the sending unit is configured to execute the foregoing first aspect and each A possible action in a transmission.
  • the access network side device provided by the fifth aspect may be an independent CU or a separate DU, or may be a chip system in the CU or a chip system in the DU, where the chip system includes at least one door.
  • a memory consisting of a processor and at least one gate, each gate comprising at least one transistor (eg, a field effect transistor) connected by wires, each transistor being fabricated from a semiconductor material.
  • the receiving unit and the sending unit are respectively a receiving circuit and a transmitting circuit in a specific implementation.
  • the access network side device may further include other electronic circuits such as a line connecting the receiving circuit and the transmitting circuit, a radio frequency antenna used to transmit the signal, and the like.
  • a sixth aspect of the embodiments of the present application provides a computer storage medium, wherein the computer storage medium includes program code, where the program code is used to implement the first aspect, the second aspect, the third aspect, the fourth aspect, or each A technical solution provided in a possible implementation.
  • the technical solution provided by the sixth aspect has the technical effects of the foregoing corresponding implementation manners, and may be specifically referred to the foregoing implementation manner.
  • a seventh aspect of the present application provides a communication system, where the communication system includes a CU and a DU, and the CU is used to implement the first aspect, the second aspect, or a method of various possible implementation manners thereof, the DU.
  • the technical solution provided by the seventh aspect has the technical effects of the foregoing corresponding implementation manners, and may be specifically referred to the foregoing implementation manner.
  • FIG. 1 is a schematic structural diagram of a repeating mode specific to a radio bearer according to an embodiment of the present application
  • 2A-2C are schematic structural diagrams of a repetition mode in a CU-DU architecture according to an embodiment of the present application.
  • 3A-3C are another schematic structural diagram of a repeating mode in a CU-DU architecture according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a communication processing method in a repeat mode of a CU-DU architecture according to an embodiment of the present disclosure
  • FIG. 5 is a schematic flowchart of a communication processing method in a repeat mode of a CU-DU architecture according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of an access network side device according to an embodiment of the present disclosure.
  • the wireless communication system includes a terminal side device and an access network side device.
  • the terminal side device may be an independent terminal or a chip system in the terminal.
  • the terminal is also called a user equipment (UE) or a mobile station, and includes a mobile phone, a handheld Internet of things device, a wearable device, and the like.
  • UE user equipment
  • the access network side device may be an independent wireless access device or a chip system in the wireless access device.
  • the wireless access device may be a base station or a wireless local area network access point, and the like, including an RRC layer, a PDCP layer, an RLC layer, a MAC layer, a PHY layer, and the like.
  • the base station can be divided into two categories: a macro base station and a small base station, and the small base station is further divided into a micro base station, a pico base station, and the like.
  • the WLAN access point can be a router, a switch, or the like.
  • the wireless local area network access point can provide coverage of wireless fidelity (Wi-Fi) signals.
  • the terminal side device and the access network side device transmit data by establishing at least one radio bearer (RB).
  • the data may include signaling data or service data.
  • a radio bearer that is mainly used for transmitting signaling data is a signaling radio bearer (SRB), and a radio bearer that is mainly used for transmitting service data is a data radio bearer (DRB).
  • the service data includes enhanced mobile broadband (eMBB) data, massive machine type communication (mMTC) data, and ultra reliable and low latency communication (URLLC) data. Wait.
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • URLLC ultra reliable and low latency communication
  • the transmitting end is the terminal side device, and the receiving end is the access network side device; for the downlink transmission, the sending end is the The network side device is accessed, and the receiving end is the terminal side device.
  • the repeat mode of the radio bearer includes a configuration of a set of peer protocol layer entities that are peered between the sender and the receiver.
  • the set of protocol layer entities includes a PDCP entity, at least two RLC entities corresponding to the PDCP entity, at least one MAC entity corresponding to the at least two RLC entities, and at least one PHY entity corresponding to the at least one MAC entity.
  • the set of protocol layer entities further includes an RRC entity corresponding to the PDCP entity.
  • the set of protocol layer entity sets may further include a SDAP entity corresponding to the PDCP entity in a Service Data Adaptation Protocol (SDAP) layer.
  • SDAP Service Data Adaptation Protocol
  • a channel is established between each RLC entity and the MAC entity.
  • the identity of an RLC entity can be used to indicate this channel.
  • the identity of a channel can be used to indicate this RLC entity. Therefore, the identity of this channel and the identity of this RLC entity can be interchanged.
  • one channel in the repeating pattern is also referred to as a leg.
  • the different channels in the repeat mode of one radio bearer are different logical channels, and different logical channel identifiers are used respectively, and the radio bearer corresponds to at least two logical channels.
  • the two logical channels may belong to the same logical channel group (LCG) or may belong to different logical channel groups.
  • at least two channels in a repeat mode of a radio bearer belong to the same logical channel and have the same logical channel identifier, and the radio bearer corresponds to one logical channel.
  • different channels may have the same logical channel identifier but different channel identifiers.
  • the transmitting end and the receiving end respectively include at least the same PDCP entity, a first RLC entity corresponding to the same PDCP entity, and a second RLC entity corresponding to the same PDCP entity.
  • the first RLC entity corresponds to the first channel
  • the second RLC entity corresponds to the second channel.
  • the transmitting end sends the data on the first channel to the receiving end in the cell 1b or the cell group 1 corresponding to the first channel
  • the receiving end receives the data of the first channel sent by the transmitting end in the cell 1b or the cell group 1 corresponding to the first channel.
  • the transmitting end sends the data of the second channel to the receiving end in the cell 2b or the cell group 2 corresponding to the second channel, and the receiving end receives the data in the second channel in the cell 2b or the cell group 2 corresponding to the second channel.
  • data from the same PDCP entity is repeatedly transmitted on the second RLC entity of the transmitting end and the first RLC entity of the transmitting end.
  • the PDCP entity copies the data and sends the data to the first RLC entity and the second RLC entity for repeated transmission; or, the RLC entity of the first RLC entity and the second RLC entity will use the data.
  • After replication it is repeatedly transmitted with another RLC entity.
  • the carrier aggregation technology is further introduced in the CU-DU architecture, and the channel corresponding to the primary cell group (including the cell set of the primary cell) is the primary channel, and correspondingly, the RLC entity on the primary channel is the primary RLC entity;
  • the channel corresponding to the cell set that includes only the at least one secondary cell is the secondary channel.
  • the RLC entity on the secondary channel is a secondary RLC entity.
  • the access group side device may include a cell group identifier (CellGroupId) and the cell group identifier included in a primary path cell indicated in a PDCP configuration of a radio bearer sent to the terminal side device.
  • CellGroupId cell group identifier
  • the cell group indicated by the cell group identifier is the main channel group and the channel indicated by the channel identifier is the main channel.
  • the channel that is not indicated in the primary path cell is the secondary channel of the radio bearer; the cell group that is not indicated in the primary path cell is the secondary cell group.
  • the access network side device is a CU and a DU architecture
  • the PDCP layer is located at the CU
  • the RLC layer, the MAC layer, and the PHY layer are located at the DU
  • the PDCP layer is located
  • the various data sent by the RLC layer are sent by the CU to the DU.
  • at least two RLC entities of a radio bearer repeat pattern are located on the same DU.
  • a repeat mode of one radio bearer exists in at least two RLC entities where two RLC entities are located on different DUs.
  • the connection between the CU and the DU includes a CU-DU control plane connection for implementing SRB, DRB, and user context establishment, and a CU-DU user plane connection for implementing service data transmission on the DRB.
  • the CU-DU user plane connection is also called a user plane tunnel because it adopts the General Packet Radio Service (GPRS) tunneling protocol.
  • GPRS General Packet Radio Service
  • a user plane tunnel is a path between an uplink tunnel endpoint and a downlink tunnel endpoint corresponding to the uplink tunnel endpoint. After the establishment of a user plane tunnel, the uplink tunnel endpoint or the downlink tunnel endpoint of the user plane tunnel may be used for identification.
  • the transmission from the DU to the CU is an uplink transmission
  • the transmission from the CU to the DU is a downlink transmission.
  • the connection between the CU and the DU is called an F1 connection
  • the CU-DU user plane connection is an F1-U connection
  • the CU-DU control plane connection is an F1-C connection; accordingly, the The CU may include a CU user plane and a CU control plane, and the connection between the CU user plane and the CU control plane is referred to as an E1 connection in some documents.
  • the CU in a case where the CU determines to configure a repetition mode of a radio bearer, the CU notifies the DU in which the at least one RLC entity in the repetition mode of the radio bearer is located, and performs the The radio bearer can activate or deactivate the determination of the repeat mode.
  • the DU that receives the notification determines whether to activate or deactivate the repeat mode of the radio bearer based on the signal measurement result or other information, and notifies the terminal side device to activate or deactivate the repeat mode of the radio bearer by using a MAC layer message.
  • the CU determines whether to activate the repeat mode of the radio bearer, the CU notifies the DU in which the RLC entities in the repeat mode of the radio bearer are located (eg, at least including DU1 and DU2) The repeat mode of this radio bearer is activated or deactivated.
  • the DU in the case that a certain DU determines whether to activate the repeat mode of the radio bearer, the DU notifies the CU and other DUs where other RLC entities are located that the repeat mode of the radio bearer is activated or go activate.
  • the following embodiments of the present application respectively describe a repetition mode implementation of a data radio bearer in a CU-DU architecture and a repetition mode implementation of a signaling radio bearer in a CU-DU architecture.
  • the first embodiment of the present application provides a communication processing method in a CU-DU architecture, which is applied to a repeating mode scenario of a data radio bearer (DBR) in a CU-DU architecture, and a schematic diagram of a communication processing method shown in FIG.
  • the first embodiment of the present application includes the following.
  • the CU sends a first message to the DU, where the first message indicates information of at least two uplink tunnel endpoints on a interface between the CU and the DU.
  • the CU may determine that a repetition mode of the data radio bearer needs to be configured, and then the CU sends a first message (eg, UE context setup/modification request) to the DU on the CU-DU interface.
  • the CU may carry the information of the at least two uplink tunnel endpoints and the identifier of the data radio bearer in the first message, where the information of the at least two uplink tunnel endpoints includes the at least two uplink tunnel endpoints
  • Each of the addresses such as an internet protocol (IP) address and an identifier of each of the at least two upstream tunnel endpoints, such as a tunnel endpoint identifier (TEID).
  • IP internet protocol
  • TEID tunnel endpoint identifier
  • the structure of the first message on the CU-DU interface is as follows:
  • the CU receives a second message sent by the DU, where the second message indicates that the data radio bears information and information of at least two downlink tunnel endpoints on an interface between the CU and the DU.
  • the identifier of the primary channel of the data radio bearer As an implementation manner, each of the at least two downlink tunnel endpoints corresponds to each of the at least two uplink tunnel endpoints.
  • the DU may be learned according to the first message.
  • the repetition mode of the data radio bearer needs to be configured.
  • the first message may further carry indication information, where the indication information indicates that a repetition mode of the data radio bearer needs to be configured.
  • the DU learns that the repeat mode of the data radio bearer needs to be configured according to the indication of the first message.
  • the DU sends a second message (eg, UE context setup/modification response) to the CU on the CU-DU interface, in order to complete the repeated mode of the data radio bearer in the CU and the DU
  • a second message eg, UE context setup/modification response
  • the DU may carry information of at least two downlink tunnel endpoints in a second message, where each of the at least two downlink tunnel endpoints corresponds to each of the at least two uplink tunnel endpoints An upstream tunnel endpoint.
  • the information of the at least two downlink tunnel endpoints includes an address (eg, an internet protocol address) of the at least two downlink tunnel endpoints and an identifier (eg, TEID) of each of the at least two downlink tunnel endpoints.
  • the second message further indicates the identifier of the channel corresponding to at least one of the at least two downlink tunnel endpoints, in order to further the CU-DU user plane tunnel endpoint corresponding to the channel corresponding to the at least two RLC entities in the DU.
  • the second message further indicates a cell group corresponding to the channel corresponding to at least one of the at least two downlink tunnel endpoints. In this way, the CU can learn the correspondence between any one of the uplink tunnel endpoint, the downlink tunnel endpoint, the channel, and the cell group in the repeated mode.
  • the control plane of the CU allocates information of the at least two uplink tunnel endpoints, and carries the information
  • the first message is sent to the DU through a CU-DU control plane connection.
  • the control plane of the CU also sends information of the at least two uplink tunnel endpoints to the user plane of the CU.
  • the user plane of the CU determines that the configuration of the repeat mode of the data radio bearer is to be performed, allocates information of the at least two uplink tunnel endpoints, and The information of the at least two uplink tunnel endpoints is sent to the control plane of the CU.
  • the control plane of the CU carries the information of the at least two uplink tunnel endpoints in the first message and sends the information to the DU through a CU-DU control plane connection.
  • the control plane of the CU after receiving the information of the at least two downlink tunnel endpoints notified by the DU in the second message, notifies the CU of the information of the at least two downlink tunnel endpoints User side.
  • the CU control plane receives the second message sent by the DU on the CU-DU control plane interface.
  • a 401 and 402 establish a user plane tunnel between an uplink tunnel endpoint and the corresponding one of the downlink tunnel endpoints between the CU and the DU. In the repeating mode, at least two user plane tunnels are established between the CU and the DU.
  • the DU includes the downlink tunnel endpoint 1 and the downlink tunnel endpoint 2 corresponding to the data radio bearer in the second message, and the channel identifier associated with the endpoint 1 of the downlink tunnel is given. Then, the channel identifier associated with the endpoint 1 of the downlink tunnel is the primary channel identifier.
  • the one downstream tunnel endpoint may be referred to as a primary tunnel endpoint.
  • the primary channel may also be determined by the CU and carried in the first message to the DU.
  • the identifier of the primary channel may not be carried in the second message.
  • the first message or the second message carries the identifier of the primary channel, which user plane tunnel corresponding to the explicit primary channel between the CU and the DU may be implemented. Thereby establishing a repeat mode connection between the user plane tunnel and the main channel.
  • other user plane tunnels can establish a connection with the secondary channel.
  • the second message may include an identifier of at least two channels corresponding to the at least two downlink tunnel endpoints, wherein the identifiers of the at least two channels include the identifier of the primary channel .
  • the second message includes, in addition to the identifier of the at least two channels, which channel is the main channel.
  • the second message may include an identifier of a channel corresponding to one of the at least two downlink tunnel endpoints.
  • the CU can know that the channel corresponding to the downlink tunnel endpoint is the primary channel.
  • the identifier of the channel corresponding to the downlink tunnel endpoint may be explicitly identified in the second message as the identifier of the primary channel.
  • which of the at least two downlink tunnel endpoints or which of the at least two uplink tunnel endpoints corresponds to the primary channel is pre-defined by the protocol.
  • the second message indicates an identifier of a channel corresponding to each of the at least two downlink tunnel endpoints, and the CU and the DU are predefined according to the protocol to learn the predefined
  • the downstream tunnel endpoint corresponds to the channel as the primary channel.
  • the first uplink tunnel endpoint that appears in the tunnel endpoint to be created list corresponding to the data radio bearer identifier in the first message corresponds to the primary channel.
  • the list includes an uplink tunnel endpoint 1 and an uplink tunnel endpoint 2, and the uplink tunnel endpoint 1 corresponds to the primary channel.
  • the DU establishes the first user plane tunnel in the first downlink tunnel endpoint that appears in the tunnel to be established list and the first uplink tunnel endpoint that appears in the first message, and the user plane The tunnel corresponds to the main channel.
  • the DU in the second message is for the data radio bearer identifier, corresponding to the downlink tunnel endpoint 1 and the downlink tunnel endpoint 2.
  • the downlink tunnel endpoint 1 and the uplink tunnel endpoint 1 implement a first user plane tunnel, and the user plane tunnel associates with the master channel. That is, the channel identifier corresponding to the endpoint 1 of the downlink tunnel, that is, the primary channel identifier. For example, if the downlink tunnel end identifier 1 corresponds to the logical channel identifier 1, the logical channel identifier 1 is the primary channel identifier.
  • the CU may indicate, in the first message, which of the at least two uplink tunnel endpoints needs to correspond to the primary channel (but the CU does not know the identity of the primary channel at this time).
  • the CU specifies that the upstream tunnel endpoint 1 corresponds to the primary channel.
  • the DU learns that the uplink tunnel endpoint 1 needs to correspond to the primary channel, and therefore, the identifier of the primary channel corresponding to the uplink tunnel endpoint 1 is indicated in the second message.
  • the DU includes a downlink tunnel endpoint 1 and a downlink tunnel endpoint 2 in the second message.
  • the downstream tunnel endpoint 1 corresponds to the upstream tunnel endpoint 1, and therefore, the user plane tunnel 1 is established.
  • the downstream tunnel endpoint 2 corresponds to the upstream tunnel endpoint 2, and therefore, the user plane tunnel 2 is established.
  • the DU learns the downlink tunnel endpoint 1 corresponding to the uplink tunnel endpoint 1 according to the indication of the CU, and needs to correspond to the primary channel, and associates the identifier of the primary channel with the downlink tunnel endpoint 1 and carries the
  • the second message is sent to the CU, so that the CU knows the identity of the primary channel.
  • the CU parses the downlink tunnel endpoint 1 corresponding to the uplink tunnel endpoint 1 from the second message, and the channel identifier associated with the endpoint 1 of the downlink tunnel is the identifier of the primary channel.
  • the DU may determine, in the second message, which of the at least two downlink tunnel endpoints needs to correspond to the primary channel, where the second message indicates that the at least two downlink tunnel endpoints correspond to the primary channel
  • the downstream tunnel endpoint For example, the DU includes the downlink tunnel endpoint 1 and the downlink tunnel endpoint 2 corresponding to the data radio bearer in the second message, and indicates that the downlink tunnel endpoint 1 is the primary channel, and the channel identifier associated with the downlink tunnel endpoint 1 is That is, the main channel is identified.
  • the method further includes: 403, the CU notifying the terminal side device of the identifier of the primary channel of the data radio bearer by using the DU.
  • the CU may also notify the terminal side device of the identifier of the cell group (ie, the primary cell group) corresponding to the primary channel.
  • the content that is notified by the CU in the 403 may be carried in the PDCP layer configuration of the data radio bearer.
  • the DU transparently transmits the PDCP configuration to the terminal side device. .
  • the control plane of the CU completes the PDCP layer configuration
  • the user plane of the CU completes the PDCP layer configuration and notifies Give the control surface of the CU.
  • the CU obtains the cell group identifier (CellGroupId) therein by acquiring the cell group configuration (CellGroupConfig) included in the second message sent by the DU.
  • the cell group identifier may appear as an independent cell in the second message, and the CU does not need to acquire the cell group identifier by reading the cell group configuration.
  • the CU obtains the primary channel identifier by the above method, for example, the logical channel identifier of the primary channel.
  • the CU adds the cell group identity and the primary channel identity to the PDCP configuration.
  • the CU control plane sends the acquired cell group identifier and the primary channel identifier to the CU user plane along with the corresponding data radio bearer identifier.
  • the CU user plane writes the cell group identifier and the primary channel identifier into the PDCP configuration.
  • the CU user plane sends the PDCP configuration to the CU control plane, so that the CU control plane sends the PDCP configuration to the terminal side device through the DU.
  • the CU determines that the DRB1 of the terminal side device performs a repeating mode, and a user plane tunnel is established between the CU and the DU1 for the DRB1, and a user plane tunnel is established between the CU and the DU2 for the DRB1.
  • the CU may notify the DU1 and the DU2DRB1 that the repeat mode is performed, so that the DU1 or the DU2 further instructs the terminal side device to perform activation or deactivation of the repeated mode by using a MAC layer message.
  • the technical solution provided by the first embodiment of the present application establishes the correspondence between the uplink tunnel endpoint, the downlink tunnel endpoint, and the channel in the repeated mode, and clarifies the determining manner of the primary channel, and implements the data radio bearer in the CU-DU architecture. Repeat mode.
  • the second embodiment of the present application provides a communication processing method in a CU-DU architecture, which is applied to a repeated mode scenario of a signaling radio bearer (SBR) in a CU-DU architecture, and a schematic diagram of a communication processing method shown in FIG. .
  • the second embodiment of the present application includes the following.
  • the CU sends, to the DU, an identifier of the signaling radio bearer and indication information used to indicate that the repeated mode of the signaling radio bearer is configured.
  • the CU determines that the signaling radio bearer needs to be configured in a repeating mode, and generates the third message (for example, a UE context setup/modification request) in the third message, including the identifier of the signaling radio bearer. And indication information for indicating a repetition mode of the signaling radio bearer. For example, the CU instructs the DU to establish SRB1 and SRB2 in the third message, and instructs the DU to perform repetitive mode configuration on SRB1.
  • the CU may further indicate an activation time of the signaling radio bearer, so that the DU activates the signaling radio bearer in the activation time.
  • the CU receives, by the CU, a configuration of the repetition mode of the signaling radio bearer sent by the DU, and an identifier of a primary channel of the signaling radio bearer.
  • the configuration of the repetition mode sent by the DU includes: identifier of at least two channels of the signaling radio bearer.
  • the identifier of the at least two channels of the signaling radio bearer or the primary channel identifier of the signaling radio bearer may be notified by the DU to the CU in 502, or may be determined by the CU.
  • the DU is notified in 501.
  • the DU generates a fourth message (eg, a UE context setup/modification response), and carries a configuration of the repeating mode of the signaling radio bearer in the RLC layer, the MAC layer, and the PHY layer in a fourth message, further And carrying an identifier of at least two channels of the signaling radio bearer to establish a repetition mode of the signaling radio bearer.
  • the configuration of the repeating mode further includes an identifier of a cell group corresponding to each channel of the signaling radio bearer.
  • the fourth message further includes an identifier of a primary channel corresponding cell group (ie, a primary cell group) of the signaling radio bearer.
  • the DU includes a cell group configuration CellGroupConfig in the fourth message, where the cell group configuration includes identifiers of at least two channels of the signaling radio bearer.
  • the fourth message may also include an identifier of the primary channel, and the identifier of the primary channel appears in a fourth message in the form of an independent cell.
  • the CU obtains the cell group identifier therein by acquiring the cell group configuration included in the second message sent by the DU.
  • the cell group identifier may appear as an independent cell in the second message, and the CU does not need to acquire the cell group identifier by reading the cell group configuration.
  • the CU obtains the primary channel identifier by using the foregoing method, for example, the logical channel identifier of the primary channel.
  • the CU adds the cell group identity and the primary channel identity to the PDCP configuration.
  • the CU generates a radio bearer configuration (RadioBearerConfig) in which the radio bearer configuration includes a PDCP configuration.
  • the CU finally generates an RRC reconfiguration message, including the radio bearer configuration and the cell group configuration sent by the DU.
  • the CU forwards the RRC reconfiguration message to the UE through the DU.
  • the repeating mode is activated.
  • the CU may send the RRC message to the DU after the PDCP layer replicates the generated RRC message. After the configuration of the repeat mode fails or exceeds the activation time of the repeat mode, the repeat mode is not activated, and the CU does not copy the generated RRC message.
  • the method further includes 503, and the possible manners for the CU to send an RRC message to the DU includes the following:
  • the CU sends a fifth message to the DU; if the repeated mode of the signaling radio bearer is not activated, the fifth message includes an RRC message belonging to the signaling radio bearer; In a case where the repetition mode of the signaling radio bearer is activated, the fifth message includes at least two RRC messages having the same PDCP number belonging to the signaling radio bearer.
  • the DU receives only one RRC message in the message received on the CU-DU interface, for example, only one RRC message is included in the DL RRC message transfer message. And the DU sends the only one RRC message to the terminal device through any one of the at least two channels, such as a primary channel. If the message received by the DU on the CU-DU control plane interface includes at least two RRC messages having the same PDCP number, the DU sends the at least two RRC messages through the at least two channels respectively To the terminal side device.
  • the CU sends a fifth message to the DU, where the fifth message includes at least one RRC message and an identifier of a channel to which each RRC message of the at least one RRC message is sent.
  • the CU may indicate an identifier of a channel to which each RRC message is to be sent, so that the DU separately sends each RRC message to the terminal through the channel to be sent according to the channel identifier indicated by the CU.
  • the side device sends.
  • the CU sends a fifth message to the DU, where the fifth message includes an RRC message.
  • the DU determines whether the PDCP number of the RRC message is repeatedly displayed. If the repetition occurs, the DU sends the RRC message to the terminal side device through the secondary channel. If not repeated, the DU sends the RRC message to the terminal side device through the primary channel.
  • the DU may record a PDCP number of each RRC message received from the CU, so that a certain RRC message is received again in the DU, and the RRC message is determined by comparing the recorded PDCP numbers. Whether the PDCP number has been repeated.
  • the CU may further generate configuration information of the repetition mode sent to the terminal side according to the configuration of the repetition mode acquired from the DU.
  • the method further includes: the CU transmitting the configuration information of the repetition mode to the terminal side device by using the DU, where the configuration information of the repetition mode includes an identifier and a location of at least two channels of the signaling radio bearer At least one of the identifiers of the primary channels of the signaling radio bearers.
  • the primary channel identifier of the signaling radio bearer may be part of a PDCP layer configuration of the repeating mode.
  • the configuration information of the repeating mode further includes an RLC layer configuration, a MAC layer configuration, a PHY layer configuration, and the like of the repeated mode.
  • the CU instructs the DU to perform the configuration of the signaling radio bearer, thereby acquiring the configuration of the signaling radio bearer by the DU, and implementing the CU-DU The repeating mode of the signaling radio bearer under the architecture.
  • a third embodiment of the present application provides a structure of an access network side device, such as the access network side device shown in FIG. 6, including a receiving unit 601 and a sending unit 602.
  • the access network side device may be the CU in the foregoing first embodiment or a chip in the CU.
  • the sending unit 602 is configured to send a first message to the DU, where the first message indicates information of at least two uplink tunnel endpoints on a interface between the CU and the DU in a repeating mode of the data radio bearer.
  • the receiving unit 601 is configured to receive a second message sent by the DU, where the second message indicates that the data radio bearer is at least two downlink tunnel endpoints on an interface between the CU and the DU. Information and the identity of the primary channel of the data radio bearer.
  • each of the at least two downlink tunnel endpoints corresponds to each of the at least two uplink tunnel endpoints.
  • the receiving unit 601 and the sending unit 602 may perform the receiving action and the sending action of the CU in the foregoing first embodiment, and specifically refer to the action of the CU in the first embodiment, and details are not described herein again.
  • the access network side device may be the DU in the foregoing first embodiment or the chip in the DU.
  • the receiving unit 601 is configured to receive a first message sent by the CU, where the information indicating the repeat mode of the data radio bearer is at least two uplink tunnel endpoints on the interface between the CU and the DU.
  • the sending unit 602 is configured to send, to the CU, a second message, where the second message indicates that the data radio bearers at least two downlink tunnel endpoints on an interface between the CU and the DU.
  • the information and the identity of the primary channel of the data radio bearer As an implementation manner, each of the at least two downlink tunnel endpoints corresponds to each of the at least two uplink tunnel endpoints.
  • the receiving unit 601 and the transmitting unit 602 can respectively perform the receiving action and the transmitting action of the DU in the foregoing first embodiment.
  • the receiving unit 601 and the transmitting unit 602 can respectively perform the receiving action and the transmitting action of the DU in the foregoing first embodiment.
  • the receiving unit 601 and the transmitting unit 602 can respectively perform the receiving action and the transmitting action of the DU in the foregoing first embodiment.
  • the access network side device may be the CU in the foregoing second embodiment or a chip in the CU.
  • the sending unit 602 is configured to send, to the DU, an identifier of the signaling radio bearer and indication information for indicating a repetition mode of the signaling radio bearer, where the receiving unit 601 is configured to receive the DU sending
  • the configuration of the repeating mode of the signaling radio bearer and the identity of the primary channel of the signaling radio bearer can respectively perform the receiving action and the transmitting action of the CU in the foregoing second embodiment.
  • the action of the CU in the second embodiment and details are not described herein again.
  • the access network side device may be the DU in the foregoing second embodiment or the chip in the DU.
  • the receiving unit 601 is configured to receive an identifier of a signaling radio bearer sent by the CU, and indication information for indicating a repetition mode of the signaling radio bearer, where the sending unit 602 is configured to send the CU to the CU. And transmitting, by the configuration of the repeating mode of the signaling radio bearer, and the identifier of the primary channel of the signaling radio bearer.
  • the receiving unit 601 and the transmitting unit 602 can respectively perform the receiving action and the transmitting action of the DU in the foregoing second embodiment.
  • the action of the CU in the second embodiment and details are not described herein again.
  • the receiving unit 601 and the sending unit 602 are respectively a receiving circuit and a transmitting circuit.
  • the access network side device may further include processing circuitry, for example, in the form of at least one processor, to implement generation and processing of the foregoing various messages.
  • the access network side device may further include other electronic circuits, such as a line connecting the receiving circuit and the transmitting circuit.
  • the access network side device may further include a radio frequency antenna to send various information to the terminal side device.
  • the access network side device may include a processor and a memory, where the memory stores code, when the code is invoked by the processor, may execute a CU or a DU in each of the foregoing method embodiments.
  • the code includes a plurality of data structures, each of which is used to implement the functions of the foregoing respective protocol layers.
  • the access network side device is a control plane device of a CU or a CU or a user plane device of a CU or a chip in a CU
  • the data structure included in the code is at least used to implement a function of the PDCP layer.
  • the receiving unit 601 can be an input interface of the data structure, and the sending unit 602 is an output interface of the data structure.
  • the access network side device is a control plane device of a DU or a DU or a user plane device of a DU or a chip in a DU
  • the code includes a data structure at least for implementing a function of an RLC layer, wherein the receiving unit 601 can be an input interface of the data structure, and the transmitting unit is an output interface of the data structure.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the present invention can take the form of a computer program product embodied on one or more chip systems or computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code. .
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种集中式单元-分布式单元(CU-DU)架构下重复(duplication)模式的通信处理方法。在一种可能实现方法中，CU和DU之间通过上行隧道端点的信息和下行隧道端点的信息的交互建立用户面隧道的过程中，由DU向CU给出主通道的标识，来实现数据无线承载的重复模式。

Description

一种CU-DU架构下重复模式的通信处理方法和设备
本申请要求2018年1月12日递交的，申请号为“201810032653.6”的中国在先申请的优先权，所述在先申请通过引用结合在本申请中。
技术领域
本申请实施例涉及无线通信领域，尤其涉及CU-DU架构下重复(duplication)模式的通信处理技术。
背景技术
在无线通信系统中，终端侧设备和接入网侧设备之间在上行链路和下行链路上按照第三代合作伙伴计划(the 3rd generation partnership project,3GPP)组织制定的各种协议层通过无线承载(radio bearer,RB)传输各种数据，例如在信令无线承载上传输控制信令或在数据无线承载上传输业务数据。这些协议层包括物理(physical，PHY)层、媒体接入控制(media access control,MAC)层、无线链路控制(radio link control,RLC)、分组数据汇聚协议(Packet Data Convergence Protocol,PDCP)层以及无线资源控制(radio resource control，RRC)层等。
所述接入网侧设备可以按照协议层进一步划分为集中式单元(central unit，CU)和分布式单元(distributed unit,DU)的架构，所述CU和所述DU之间包括控制面连接和用户面连接，其中，所述用户面连接又称为用户面隧道(user plane(UP)tunnel)。一个用户面隧道由CU上的一个上行隧道端点和DU上的一个下行隧道端点来确定。其中，所述CU用于实现PDCP层的功能和RRC层的功能，所述DU用于实现PHY层的功能、MAC层的功能以及RLC层的功能。
随着第五代通信技术的发展，一个无线承载在PDCP层的一个PDCP实体对应RLC层的至少两个RLC实体；这一个PDCP实体上的部分或全部数据，在所述至少两个RLC实体上重复传输，这种处理方式称为重复模式。一个重复模式特定于(specific to)一个无线承载。
如何实现CU-DU架构下无线承载的重复模式，是亟待解决的问题。
发明内容
本申请实施例提供一种CU-DU架构下重复模式的通信处理方法，实现了重复模式下CU-DU之间连接的建立。
本申请实施例第一方面提供一种CU-DU架构下重复模式的通信处理方法，包括以下内容。
CU向DU发送第一消息，其中，所述第一消息中指示数据无线承载的重复模式在所述CU与所述DU之间接口上的至少两个上行隧道端点的信息；所述CU接收所述DU发送的第二消息，所述第二消息中指示所述数据无线承载在所述CU 与所述DU之间接口上的至少两个下行隧道端点的信息和所述数据无线承载的主通道的标识。作为一种实现方式，所述至少两个下行隧道端点中每一个下行隧道端点一一对应于所述至少两个上行隧道端点中每一个上行隧道端点。
应用第一方面提供的技术方案，在通过上行隧道端点的信息和下行隧道端点的信息的交互而建立CU和DU之间至少两个用户面隧道的过程中，由DU向CU给出主通道的标识，从而使得所述CU和所述DU获知对应主通道的用户面隧道为哪个，进而能够建立起主通道和与所述主通道对应的用户面隧道之间的连接，实现了从CU到DU的数据无线承载的重复模式。
在第一方面中，由于第一消息中指示了至少两个上行端点的信息(表明要建立至少两个用户面隧道)，因而所述DU可以默认这是要对所述数据无线承载的所述重复模式进行配置。
在第一方面中，CU和DU之一可以确定哪个用户面隧道对应主通道，但所述主通道的标识由所述DU通过所述第二消息通知到所述CU。
基于第一方面，在第一方面的第一种可能实现方式中，所述第一消息中还指示对所述数据无线承载配置所述重复模式。应用第一种可能实现方式提供的方案，所述CU通过所述第一消息明示所述DU这个数据无线承载的重复模式需要进行配置。
基于第一方面或第一方面的第一种可能实现方式，在第一方面的第二种可能实现方式中，所述主通道的标识为所述第二消息中指示的所述至少两个下行隧道端点中仅一个下行隧道端点对应的通道的标识。在第一方面的第二种可能实现方式中，DU可以通知仅一个下行隧道端点对应的通道的标识，则所述仅一个下行隧道端点对应的通道的标识即为所述主通道的标识。
基于第一方面至第一方面的第二种可能实现方式的任意一种，在第一方面的第三种可能实现方式中，
所述第一消息中还指示所述至少两个上行隧道端点中对应所述主通道的上行隧道端点；或者，所述第二消息中还指示所述至少两个下行隧道端点中对应所述主通道的下行隧道端点；或者，所述至少两个上行隧道端点中的对应所述主通道的上行隧道端点为协议预定义；或者，所述至少两个下行隧道端点中的对应所述主通道的下行隧道端点为协议预定义。
在第一方面的第三种可能实现方式中可通过CU，DU或者协议预定义的方式明确所述主通道所对应的用户面隧道。
基于第一方面至第一方面的第三种可能实现方式的任意一种，在第一方面的第四种可能实现方式中，所述方法还包括：所述CU通过所述DU向终端侧设备通知所述数据无线承载的主通道的标识。
在第一方面的第四种可能实现方式可以使得终端侧设备获知所述主通道，从而完成所述CU，所述DU以及所述终端侧设备之间主通道的确定。
本申请实施例第二方面提供一种CU-DU架构下重复模式的通信处理方法，包 括以下内容。
CU向DU发送信令无线承载的标识和用于指示对所述信令无线承载的重复模式进行配置的指示信息；所述CU接收所述DU发送的所述信令无线承载的所述重复模式的配置和所述信令无线承载的主通道的标识。
应用第二方面提供的技术方案，所述DU可在所述CU的指示下进行信令无线承载的配置，并使得所述CU获知所述信令无线承载的主通道在哪里。
基于第二方面，在第二方面的第一种可能实现方式中，所述方法还包括：所述CU向所述DU发送CU-DU接口消息；
在所述信令无线承载的重复模式未被激活的情况下，所述CU-DU接口消息中包含属于所述信令无线承载的一个RRC消息；或者，
在所述信令无线承载的重复模式被激活的情况下，所述CU-DU接口消息包含属于所述信令无线承载的具有相同PDCP编号的至少两个RRC消息。
第二方面的第一种可能实现方式提供了所述CU在所述重复模式被激活或被去激活的情况下，发送RRC消息的实现方式。
基于第二方面，在第二方面的第二种可能实现方式中，所述方法还包括：所述CU向所述DU发送CU-DU接口消息，所述CU-DU接口消息中包含至少一个RRC消息和所述至少一个RRC消息的每一个RRC消息发往的通道的标识。
第二方面的第二种可能实现方式提供了所述CU发送RRC消息的另一种实现方式，所述DU可根据每个RRC消息发往的通道的标识，确定出每个RRC消息的发送。
基于第二方面，在第二方面的第三种可能实现方式中，所述方法还包括：
所述CU通过所述DU向终端侧设备通知所述信令无线承载的主通道的标识。
在第二方面的第三种可能实现方式可以使得终端侧设备获知所述主通道，从而完成所述CU，所述DU以及所述终端侧设备之间主通道的确定。
本申请实施例第三方面提供一种CU-DU架构下重复模式的通信处理方法，包括以下内容。
DU接收CU发送的第一消息，所述第一消息中指示数据无线承载的重复模式在所述CU与所述DU之间接口上的至少两个上行隧道端点的信息；所述DU向所述CU发送的第二消息，所述第二消息中指示所述数据无线承载在所述CU与所述DU之间接口上的至少两个下行隧道端点的信息和所述数据无线承载的主通道的标识。作为一种实现方式，所述至少两个下行隧道端点中每一个下行隧道端点一一对应于所述至少两个上行隧道端点中每一个上行隧道端点。
第三方面对应第一方面，具有第一方面相似的有益效果。
基于第三方面，在第三方面的第一种可能实现方式中，所述第一消息中还指示对所述数据无线承载配置所述重复模式。第三方面的第一种可能实现方式对应第一方面的第一种可能实现方式，具有第一方面的第一种可能实现方式相似的有益效果。
基于第三方面或第三方面的第一种可能实现方式，在第三方面的第二种可能实现方式中，所述主通道的标识为所述第二消息中指示的所述至少两个下行隧道端点中仅一个下行隧道端点对应的通道的标识。第三方面的第二种可能实现方式对应第一方面的第二种可能实现方式，具有第三方面的第二种可能实现方式相似的有益效果
基于第三方面至第三方面的第二种可能实现方式中的任意一种，在第三方面的第三种可能实现方式中，所述第一消息中还指示所述至少两个上行隧道端点中对应所述主通道的上行隧道端点；或者，所述第二消息中还指示所述至少两个下行隧道端点中对应所述主通道的下行隧道端点；或者，所述至少两个上行隧道端点中对应所述主通道的上行隧道端点为协议预定义；所述至少两个下行隧道端点中对应所述主通道的上行隧道端点为协议预定义。
第三方面的第三种可能实现方式对应第一方面的第三种可能实现方式，具有第一方面的第三种可能实现方式相似的有益效果。
本申请实施例第四方面提供一种CU-DU架构下重复模式的通信处理方法，包括以下内容。
DU接收CU发送的信令无线承载的标识和用于指示对所述信令无线承载的重复模式进行配置的指示信息；所述DU向所述CU发送所述信令无线承载的重复模式的配置，和所述信令无线承载的主通道的标识。
第四方面对应第二方面，具有第二方面相似的有益效果。
基于第四方面，在第四方面的第一种可能实现方式中，所述方法还包括：
所述DU接收所述CU发送的CU-DU接口消息；其中，
在所述信令无线承载的重复模式未被激活的情况下，所述CU-DU接口消息中包含属于所述信令无线承载的一个RRC消息；所述DU通过所述主通道将所述一个RRC消息发送给终端侧设备；或者，
在所述信令无线承载的重复模式被激活的情况下，所述CU-DU接口消息中包含属于所述信令无线承载的具有相同PDCP编号的至少两个RRC消息；所述DU将通过所述主通道和至少一个辅通道将所述至少两个RRC消息分别发送给所述终端侧设备。
第四方面的第一种可能实现方式对应第二方面的第一种可能实现方式，具有第二方面的第一种可能实现方式相似的有益效果。
基于第四方面，在第四方面的第二种可能实现方式中，所述方法还包括：
所述DU接收所述CU发送的CU-DU接口消息，所述CU-DU接口消息中包括至少一个RRC消息和所述至少一个RRC消息的每个RRC消息发往的通道的标识。
第四方面的第二种可能实现方式对应第二方面的第二种可能实现方式，具有第二方面的第一种可能实现方式相似的有益效果。
基于第四方面，在第四方面的第三种可能实现方式中，所述方法还包括：所述DU接收所述CU发送的CU-DU接口消息,所述CU-DU接口消息中包含RRC消息； 其中，
如果所述RRC消息的PDCP编号重复出现，则所述DU通过辅通道将所述RRC消息发送给终端侧设备；或者，如果所述RRC消息的PDCP编号未重复过，则所述DU通过主通道将所述RRC消息发送给终端侧设备。
应用第四方面第三种可能实现方式，DU可以通过判断接收到的RRC消息的PDCP编号是否重复出现过，来确定将所述RRC消息发送到主通道还是辅通道上。
本申请实施例第五方面提供接入网侧设备，所述接入网侧设备包括接收单元和发送单元。其中，所述接收单元用于执行前述第一方面，第二方面，第三方面，第四方面或者各种可能实现方式中的接收动作，所述发送单元用于执行前述第一方面及其各种可能实现方式中的发送动作。
第五方面提供的所述接入网侧设备可以为独立的CU或者独立的DU，还可以是所述CU中的芯片系统或所述DU中的芯片系统，所述芯片系统包含有至少一个门电路组成的处理器和至少一个门电路组成的存储器，每个门电路包含通过导线连接的至少一个晶体管(例如场效应管)，每个晶体管由半导体材料制作而成。进一步地，所述接收单元和所述发送单元在具体实现中分别为接收电路和发送电路。所述接入网侧设备还可以包括其它电子线路，例如连接所述接收电路和所述发送电路的线路，以及发送信号所使用的射频天线等等。第五方面提供的技术方案具有前述对应实现方式的技术效果，具体可参考前述实现方式。
本申请实施例第六方面提供一种计算机存储介质，其中，所述计算机存储介质中包括程序代码，所述程序代码用于实现第一方面，第二方面，第三方面，第四方面或者各种可能实现方式中提供的技术方案。第六方面提供的技术方案具有前述对应实现方式的技术效果，具体可参考前述实现方式。
本申请实施例第七方面提供一种通信系统，所述通信系统中包含CU和DU，所述CU用于实现第一方面，第二方面或及其各种可能实现方式的方法，所述DU用于实现第三方面，第四方面及其各种可能实现方式中提供的技术方案。第七方面提供的技术方案具有前述对应实现方式的技术效果，具体可参考前述实现方式。
附图说明
图1为本申请实施例提供的特定于一个无线承载的重复模式的架构示意图；
图2A-图2C为本申请实施例提供一种CU-DU架构下重复模式的示意结构图；
图3A-图3C为本申请实施例提供一种CU-DU架构下重复模式另一示意结构图；
图4为本申请实施例提供的一种CU-DU架构下重复模式的通信处理方法流程示意图；
图5为本申请实施例提供的一种CU-DU架构下重复模式的通信处理方法流程示意图；
图6为本申请实施例提供的一种接入网侧设备的结构示意图。
具体实施方式
图1所示的无线通信系统协议栈架构示意图中，无线通信系统包括终端侧设备和接入网侧设备。
所述终端侧设备可以为独立的终端或所述终端中的芯片系统。其中，所述终端又称用户设备(user equipment,UE)或移动台(mobile station),包括手机，手持物联网设备，穿戴设备(wearable devices)等等。
所述接入网侧设备可以为一个独立的无线接入设备或所述无线接入设备中的芯片系统。其中，所述无线接入设备可以为一个基站或一个无线局域网接入点等，包括RRC层、PDCP层，RLC层、MAC层和PHY层等等。基站可分为宏基站(macro base station)和小基站两大类，而小基站又分为微基站(micro base station),微微基站(pico base station)等等。无线局域网接入点可以为路由器，交换机等。所述无线局域网接入点可以提供无线保真(wireless fidelity,Wi-Fi)信号的覆盖。
所述终端侧设备和所述接入网侧设备之间通过建立至少一个无线承载(radio bearer,RB)来传输数据。其中，所述数据可包括信令数据或业务数据。主要用于传输信令数据的无线承载为信令无线承载(signaling radio bearer,SRB)，主要用于传输业务数据的无线承载为数据无线承载(data radio bearer,DRB)。所述业务数据包括增强型移动宽带(enhanced mobile broadband,eMBB)数据，大量机器类型通信(massive machine type communication,mMTC)数据以及高可靠低时延通信(ultra reliable and low latency communication,URLLC)数据等等。
在图1所示的无线通信系统架构图中，对于上行传输来说，发送端为所述终端侧设备，接收端为所述接入网侧设备；对于下行传输来说，发送端为所述接入网侧设备，接收端为所述终端侧设备。
对于发送端和接收端之间的某个无线承载，所述无线承载的重复模式包含所述发送端和所述接收端之间对等的一组协议层实体集合的配置。这组协议层实体集合包括一个PDCP实体，所述PDCP实体对应的至少两个RLC实体，所述至少两个RLC实体对应的至少一个MAC实体，所述至少一个MAC实体对应的至少一个PHY实体。对于信令无线承载，这组协议层实体集合还包括所述PDCP实体对应的一个RRC实体。可选地，对于数据无线承载，这组协议层实体集合还可以包括所述PDCP实体在服务数据适应协议(Service Data Adaptation Protocol,SDAP)层对应的一个SDAP实体。
在图1中，同一个无线承载的重复模式中，每个RLC实体与MAC实体之间分别建立了一个通道。一个RLC实体的标识可用来指示这个的通道。相应的，一个通道的标识可用来指示这个RLC实体。因此，这个通道的标识和这个RLC实体的标识可以互换。在某些技术文献中，所述重复模式中一个通道还被称为一条腿(leg)。
可选地，一个无线承载的重复模式下的不同通道分别为不同逻辑信道(logical channel)，分别使用不同逻辑信道标识，则这个无线承载对应至少两个逻辑信道。这两个逻辑信道可以属于同一逻辑信道组(logical channel group,LCG)，也可以属于不同逻辑信道组。可选地，一个无线承载的重复模式下的至少两个通道属于同一逻辑信道，具有相同的逻辑信道标识，则这个无线承载对应一个逻辑信道。这种情况下为了区分不同通道，不同通道可具有同一逻辑信道标识，但不同通道标识。
在图1中，对于同一无线承载的重复模式，发送端和接收端分别至少包含同一PDCP实体以及所述同一PDCP实体对应的第一RLC实体和所述同一PDCP实体对应的第二RLC实体。其中，第一RLC实体对应第一通道，第二RLC实体对应第二通道。发送端在第一通道对应的小区1b或小区组1向接收端发送第一通道上的数据，接收端在第一通道对应的小区1b或小区组1接收发送端发送的第一通道的数据。发送端在第二通道对应的小区2b或小区组2向接收端发送第二通道的数据，接收端在第二通道对应的小区2b或小区组2接收第二通道上的数据。在重复模式被激活后，在发送端的第二RLC实体和发送端的第一RLC实体上对来自同一PDCP实体的数据进行重复传输。例如，所述PDCP实体将所述数据复制后分别发送到所述第一RLC实体和第二RLC实体进行重复传输；或者，第一RLC实体和第二RLC实体中的一个RLC实体将所述数据复制后，与另一RLC实体进行重复传输。
在CU-DU架构下进一步引入载波聚合技术，则主小区组(包含主小区的小区集合)对应的通道为主通道，相应地，所述主通道上的RLC实体为主RLC实体；辅小区组(仅包含至少一个辅小区的小区集合)对应的通道为辅通道，相应地，所述辅通道上的RLC实体为辅RLC实体。
可选地，接入网侧设备可以在发送给终端侧设备的某个无线承载的PDCP配置中指示的主路径(primary path)信元中包含的小区组标识(CellGroupId)和所述小区组标识对应的通道标识，则这个小区组标识所指示的小区组为主小区组和所述通道标识所指示的通道为所述主通道。未在主路径信元中指示出的通道为所述无线承载的辅通道；未在主路径信元中指示出的小区组为辅小区组。
如图2A-2C和图3A-3C所示，在接入网侧设备为CU和DU架构时，PDCP层位于CU，而RLC层、MAC层以及PHY层位于DU，因而所述PDCP层向所述RLC层发送的各种数据，由所述CU发送给所述DU。图2A-2C中，一个无线承载的重复模式的至少两个RLC实体位于同一DU上。图3A-3C中，一个无线承载的重复模式至少两个RLC实体中存在两个RLC实体位于不同DU上。
所述CU与所述DU之间的连接包括用于实现SRB、DRB以及用户上下文建立的CU-DU控制面连接和用于实现DRB上业务数据传输的CU-DU用户面连接。其中，CU-DU用户面连接由于采用通用分组无线服务(General Packet Radio Service，GPRS)隧道协议，因而又被称为用户面隧道(tunnel)。一个用户面隧道为一个上行隧道端点和与所述上行隧道端点一一对应的下行隧道端点之间的路径。在一个用户面隧道建立完成后，可使用这个用户面隧道的上行隧道端点或下行隧道端点进行标识。
在所述接入网侧设备为CU-DU架构时，从所述DU到所述CU的传输为上行传输，从所述CU到所述DU的传输为下行传输。在某些技术文献，所述CU和所述DU之间连接称为F1连接，CU-DU用户面连接为F1-U连接，CU-DU控制面连接为F1-C连接；相应地，所述CU可包括CU用户面和CU控制面，所述CU用户面和所述CU控制面之间的连接在某些文献中称为E1连接。
可选地，在图3A-3C中，在CU确定对某个无线承载的重复模式进行配置的情况下，所述CU通知这个无线承载的重复模式中至少一个RLC实体所在的DU，进行所述无线承载可以激活或去激活重复模式的确定。收到所述通知的DU，基于信号测量结果或其他信息决定是否激活或去激活所述无线承载的重复模式，并通过MAC层消息通知终端侧设备激活或去激活所述无线承载的重复模式。
可选地，在图3A-3C中，在CU确定是否激活无线承载的重复模式的情况下，所述CU通知这个无线承载的重复模式中所有RLC实体所在的DU(例如至少包括DU1和DU2)这个无线承载的重复模式被激活或被去激活。
可选地，在图3A-3C中，在某个DU确定是否激活无线承载的重复模式的情况下，所述DU通知CU以及其它RLC实体所在的其它DU这个无线承载的重复模式被激活或被去激活。
本申请下述实施例分别描述了CU-DU架构下数据无线承载的重复模式实现和CU-DU架构下信令无线承载的重复模式实现。
本申请第一实施例提供一种CU-DU架构下的通信处理方法，应用于在CU-DU架构下数据无线承载(DBR)的重复模式场景，如图4所示的通信处理方法流程示意图。本申请第一实施例包括以下内容。
401，CU向DU发送第一消息，所述第一消息中指示数据无线承载的重复模式在所述CU与所述DU之间接口上的至少两个上行隧道端点的信息。
所述CU可确定需要对所述数据无线承载的重复模式进行配置，于是所述CU在CU-DU接口上向DU发送第一消息(例如UE context setup/modification request)。所述CU可以在第一消息中携带所述至少两个上行隧道端点的信息和所述数据无线承载的标识，所述至少两个上行隧道端点的信息中包括了所述至少两个上行隧道端点每一个的地址，例如网际协议(internet protocol,IP)地址和所述至少两个上行隧道端点每一个的标识，例如隧道端点标识(tunnel endpoint identifier,TEID)。
作为一种可选实现方式，CU-DU接口上的第一消息的结构如下：
Figure PCTCN2019071563-appb-000001
402，所述CU接收所述DU发送的第二消息，所述第二消息中指示所述数据无线承载在所述CU与所述DU之间接口上的至少两个下行隧道端点的信息和所述数据无线承载的主通道的标识。作为一种实现方式，所述至少两个下行隧道端点中每一个下行隧道端点一一对应于所述至少两个上行隧道端点中每一个上行隧道端点。
在所述DU接收到所述第一消息后，由于在第一消息中同一个数据无线承载的标识对应了至少两个上行隧道端点的信息，因而，所述DU可以根据所述第一消息获知需要对所述数据无线承载的重复模式进行配置。可选地，所述第一消息中还可以携带指示信息，所述指示信息明示需要对所述数据无线承载的重复模式进行配置。DU根据第一消息的指示，获知需要对所述数据无线承载的重复模式进行配置。
在402中，所述DU在CU-DU接口上向所述CU发送第二消息(例如UE context setup/modification response)，以便完成所述数据无线承载的重复模式在所述CU和所述DU之间接口上建立至少两条CU-DU用户面隧道。作为一种实现方式，所述DU可在第二消息中携带至少两个下行隧道端点的信息，所述至少两个下行隧道端点每一个一一对应于所述至少两个上行隧道端点中的每一个上行隧道端点。所述至少两个下行隧道端点的信息包括所述至少两个下行隧道端点的地址(例如网际协议地址)和所述至少两个下行隧道端点每一个的标识(例如TEID)。为了进一步将CU-DU用户面隧道端点对应到所述DU中的至少两个RLC实体分别对应的通道，所述第二消息中还指示至少两个下行隧道端点中至少一个分别对应的通道的标识。可选地，所述第二消息中还指示所述至少两个下行隧道端点中至少一个分别对应的通道所对应的小区组。通过这种方式，CU可以获知所述重复模式中上行隧道端点、下行隧道端点、通道以及小区组之间任意一组的对应关系。
作为一种可能实现方式，所述CU的控制面确定出要进行所述数据无线承载的重复模式的配置后，所述CU的控制面分配所述至少两个上行隧道端点的信息，并携带在所述第一消息中通过CU-DU控制面连接发送到所述DU。所述CU的控制 面还将所述至少两个上行隧道端点的信息发送给所述CU的用户面。
作为另一种可能实现方式，所述CU的用户面确定出要进行所述数据无线承载的重复模式的配置后，所述CU的用户面分配所述至少两个上行隧道端点的信息，并将所述至少两个上行隧道端点的信息发送给所述CU的控制面。所述CU的控制面将所述至少两个上行隧道端点的信息携带在所述第一消息中通过CU-DU控制面连接发送给所述DU。进一步，在所述CU的控制面在接收到所述DU在第二消息中通知的所述至少两个下行隧道端点的信息后，将所述至少两个下行隧道端点的信息通知给所述CU的用户面。可选地，所述CU控制面在所述CU-DU控制面接口上接收所述DU发送的第二消息。
通过401和402，所述CU和所述DU之间一个上行隧道端点和所对应的一个下行隧道端点之间建立起一个用户面隧道。在所述重复模式下，所述CU和所述DU之间建立起至少两条用户面隧道。
可选地，在所述第二消息中指示了所述主通道对应于所述至少两个下行隧道端点中的某一个下行隧道端点，从而使得这个下行隧道端点所在的用户面隧道对应所述主通道，而其它用户面隧道则对应辅通道。例如DU在第二消息中包含数据无线承载对应的下行隧道端点1和下行隧道端点2，并给出了下行隧道端点1关联的通道标识。则所述下行隧道端点1关联的通道标识即为主通道标识。这种情况下，所述一个下行隧道端点可被称为主隧道端点。当重复模式被去激活时，所述CU和所述DU在所述主隧道端点以及所述主隧道端点对应的所述主通道上传输业务数据，而不在其它隧道端点以及其它隧道端点所对应的通道上重复传输所述业务数据。
作为一种401和402可替换的实现方式，所述主通道也可由所述CU确定，并携带在第一消息中发送给所述DU。这种情况下，第二消息中可不携带所述主通道的标识。无论是第一消息还是第二消息携带所述主通道的标识，均可实现所述CU和所述DU之间明确主通道对应哪个用户面隧道。从而建立起重复模式在用户面隧道和主通道的连接。相应地，其它用户面隧道则可与辅通道建立连接。
可选地，所述第二消息中可以包含所述至少两个下行隧道端点分别一一对应的至少两个通道的标识，其中，所述至少两个通道的标识中包含所述主通道的标识。为了使得CU获知所述所述至少两个通道中哪个通道为所述主通道，则所述第二消息中除了包含所述至少两个通道的标识，还具体指示哪个通道为所述主通道。
可选地，所述第二消息中可以包括所述至少两个下行隧道端点中某一个下行隧道端点对应通道的标识。这种情况下，由于在所述第二消息中仅有一个下行隧道端点被对应到了一个通道，所述CU可以获知这个下行隧道端点对应的这个通道为所述主通道。可选地，所述第二消息中可以明示这个下行隧道端点对应的通道的标识为主通道的标识。
可选地，所述至少两个下行隧道端点中哪个下行隧道端点或者所述至少两个上行隧道端点中哪个上行隧道端点对应主通道由协议预定义。一种可能实现方 式，所述至少两个上行隧道端点中预定义某个上行隧道端点或预定义某个下行隧道端点对应有通道，而无需指示其它隧道端点所对应通道；这种情况下，所述CU和所述DU根据协议预定义获知所述预定义的上行隧道端点或所述预定义的下行隧道端点对应的通道为主通道。另一种可能实现方式，所述第二消息中指示所述至少两个下行隧道端点中所有下行隧道端点分别对应的通道的标识，所述CU和所述DU根据协议预定义获知所述预定义下行隧道端点对应通道为主通道。
一种可能实现方式，所述第一消息中的数据无线承载标识对应的隧道端点待建立列表中出现的第一个上行隧道端点对应为主通道。例如所述列表包含上行隧道端点1和上行隧道端点2，则上行隧道端点1对应主通道。则DU在发送第二消息时，在隧道待建立列表中出现的第一个下行隧道端点和第一消息中第一个出现的上行隧道端点，共同建立起第一个用户面隧道，该用户面隧道对应主通道。例如DU在第二消息中针对所述数据无线承载标识，对应下行隧道端点1和下行隧道端点2。则所述下行隧道端点1和上行隧道端点1实现了第一用户面隧道，该用户面隧道关联主通道。即对应下行隧道端点1出现的通道标识，即主通道标识。例如下行隧道端点标识1对应逻辑信道标识1，则所述逻辑信道标识1即主通道标识。
可选地，所述CU可以在所述第一消息中指示所述至少两个上行隧道端点中哪个上行隧道端点需要对应主通道(但此时CU并不知道主通道的标识)。例如CU指定了上行隧道端点1对应主通道。所述DU则获知所述上行隧道端点1需要对应所述主通道，因而，在所述第二消息中指示出对应所述上行隧道端点1的主通道的标识。例如，DU在第二消息中包含下行隧道端点1和下行隧道端点2。下行隧道端点1和上行隧道端点1对应，因此，用户面隧道1被建立起来。下行隧道端点2和上行隧道端点2对应，因此，用户面隧道2被建立起来。所述DU根据所述CU的指示获知与上行隧道端点1对应的下行隧道端点1，需要对应所述主通道，进而将所述主通道的标识与所述下行隧道端点1关联，携带在所述第二消息中发送给所述CU，从而使得所述CU获知所述主通道的标识。例如CU从所述第二消息中解析出与上行隧道端点1对应的下行隧道端点1，则下行隧道端点1关联的通道标识，即为所述主通道的标识。
可选地，所述DU可以确定所述至少两个下行隧道端点中哪个下行隧道端点需要对应主通道，在所述第二消息中指示所述至少两个下行隧道端点中对应所述主通道的所述下行隧道端点。例如，所述DU在第二消息中包含所述数据无线承载对应的下行隧道端点1和下行隧道端点2，并指示下行隧道端点1为主通道，则所述下行隧道端点1关联的通道标识，即为主通道标识。
可选地，所述方法还包括：403，所述CU通过所述DU向终端侧设备通知所述数据无线承载的主通道的标识。所述CU还可以通知所述终端侧设备所述主通道对应的小区组(即主小区组)的标识。其中，所述CU在403中所通知的内容可以携带在所述数据无线承载的PDCP层配置中，所述DU接收到所述PDCP配置后，将所述PDCP配置透传给所述终端侧设备。当所述CU包含CU的控制面和CU 的用户面时，一种情况是所述CU的控制面完成所述PDCP层配置，另一种情况是所述CU的用户面完成PDCP层配置并通知给所述CU的控制面。
例如CU通过获取DU发送的第二消息中包含的小区组配置(CellGroupConfig)，获取其中的小区组标识(CellGroupId)。特别地，小区组标识可以在所述第二消息中以独立信元的方式出现，则CU不需要通过读取小区组配置获取所述小区组标识。CU通过上述方法获取主通道标识，例如主通道的逻辑信道标识。CU将所述小区组标识和主通道标识添加到PDCP配置中。
可选的，CU控制面将获取的小区组标识和主通道标识，连同对应的数据无线承载标识，发给CU用户面。CU用户面将所述小区组标识和主通道标识写入PDCP配置中。CU用户面将所述PDCP配置发送给CU控制面，以便CU控制面将所述PDCP配置通过DU发送给所述终端侧设备。
作为一个示例，CU确定为所述终端侧设备的DRB1进行重复模式，则CU和DU1之间为DRB1建立一个用户面隧道，CU和DU2之间为DRB1建立一个用户面隧道。CU可通知DU1和DU2DRB1进行了重复模式，以便DU1或DU2进一步通过MAC层消息指示所述终端侧设备进行所述重复模式的激活或去激活。
本申请第一实施例提供的技术方案建立了重复模式下上行隧道端点、下行隧道端点以及通道之间的对应关系，并且明示了主通道的确定方式，实现了CU-DU架构下数据无线承载的重复模式。
本申请第二实施例提供一种CU-DU架构下的通信处理方法，应用于在CU-DU架构下信令无线承载(SBR)的重复模式场景，如图5所示的通信处理方法流程示意图。本申请第二实施例包括以下内容。
501，CU向DU发送信令无线承载的标识和用于指示对所述信令无线承载的重复模式进行配置的指示信息。
在501中，CU判断出所述信令无线承载需要进行重复模式的配置，生成所述第三消息(例如UE context setup/modification request)在所述第三消息中，包含信令无线承载的标识和用于指示对所述信令无线承载的重复模式进行配置的指示信息。例如CU在第三消息中指示所述DU建立SRB1和SRB2，并指示DU对SRB1进行重复模式配置。可选地，所述CU还可以指示所述信令无线承载的激活时间，以便所述DU在所述激活时间内激活所述信令无线承载。
502，所述CU接收所述DU发送的所述信令无线承载的所述重复模式的配置，和所述信令无线承载的主通道的标识。
可选地，所述DU发送的所述重复模式的配置包括：所述信令无线承载的至少两个通道的标识。
可选地，所述信令无线承载的至少两个通道的标识或所述信令无线承载的主通道标识可由所述DU确定后在502中通知给所述CU，也可以由CU确定后在在501中通知给所述DU。
在502中，所述DU生成第四消息(例如UE context setup/modification  response)，并在第四消息中携带所述信令无线承载的重复模式在RLC层、MAC层和PHY层的配置，进一步携带所述信令无线承载的至少两个通道的标识,以便建立所述信令无线承载的重复模式。所述重复模式的配置中还包括所述信令无线承载的每个通道对应小区组的标识。所述第四消息还包括所述信令无线承载的主通道对应小区组(即主小区组)的标识。例如DU在第四消息中包含小区组配置CellGroupConfig，所述小区组配置包含所述信令无线承载的至少两个通道的标识。所述第四消息中还可能包含所述主通道的标识，该主通道的标识以独立信元的方式出现在第四消息中。例如CU通过获取DU发送的第二消息中包含的小区组配置，获取其中的小区组标识。特别地，小区组标识可以在所述第二消息中以独立信元的方式出现，则CU不需要通过读取小区组配置获取所述小区组标识。以及CU通过上述方法获取主通道标识，例如主通道的逻辑信道标识。CU将所述小区组标识和主通道标识添加到PDCP配置中。CU生成无线承载配置(RadioBearerConfig)，其中无线承载配置中包含PDCP配置。CU最终生成RRC重配置消息，包含所述无线承载配置和DU发送的小区组配置。CU将所述RRC重配置消息通过DU转发给UE。在501和502对所述信令无线承载的重复模式的配置后，(可选地在所述重复模式的激活时间内)，所述重复模式被激活。所述CU可以在PDCP层对产生RRC消息进行复制后，再向所述DU发送。所述重复模式的配置失效后或超过所述重复模式的激活时间，则所述重复模式未被激活，所述CU则不对产生的RRC消息进行复制。
因此，基于501和502，所述方法还包括503，所述CU向所述DU发送RRC消息的可能方式包括以下几种：
503A，所述CU向所述DU发送第五消息；在所述信令无线承载的重复模式未被激活的情况下，所述第五消息中包含属于所述信令无线承载的一个RRC消息；在所述信令无线承载的重复模式被激活的情况下，所述第五消息中包含属于所述信令无线承载的具有相同PDCP编号的至少两个RRC消息。
在503A中，如果所述DU在CU-DU接口上接收的消息中包含了仅一个RRC消息，例如在DL RRC message transfer消息中包含仅一个RRC消息。则所述DU将所述仅一个RRC消息通过所述至少两个通道中任一通道(例如主通道)发送给终端设备。如果所述DU在CU-DU控制面接口上接收的消息中包含了具有相同PDCP编号的至少两个RRC消息，则所述DU将所述至少两个RRC消息分别通过所述至少两个通道发送给所述终端侧设备。
503B，所述CU向所述DU发送第五消息，所述第五消息中包含至少一个RRC消息和所述至少一个RRC消息的每一个RRC消息发往的通道的标识。
在503B中，所述CU可以指示每个RRC消息所要发往的通道的标识，以便所述DU根据所述CU指示的通道标识，分别将每个RRC消息通过所要发往的通道向所述终端侧设备发送。
503C，所述CU向所述DU发送第五消息，所述第五消息中包含RRC消息。所述DU判断所述RRC消息的PDCP编号是否重复出现过。如果重复出现过，则所述 DU通过辅通道将所述RRC消息发送给所述终端侧设备。如果未重复过，则所述DU通过主通道将所述RRC消息发送给所述终端侧设备。
在503C中，所述DU可以记录从所述CU接收到的每个RRC消息的PDCP编号，从而在所述DU再次接收到某个RRC消息，通过比较所记录的PDCP编号，确定这个RRC消息的PDCP编号是否重复出现过。
进一步地，为了使得终端侧设备获知所述重复模式的配置，所述CU可根据从DU获取的所述重复模式的配置，进一步生成发送给所述终端侧的所述重复模式的配置信息。所述方法还包括：所述CU通过所述DU向终端侧设备发送所述重复模式的配置信息，所述重复模式的配置信息中包括所述信令无线承载的至少两个通道的标识和所述信令无线承载的主通道的标识的至少一种。其中，所述信令无线承载的主通道标识可作为所述重复模式的PDCP层配置的一部分。可选地，所述重复模式的配置信息中还包括所述重复模式的RLC层配置，MAC层配置以及PHY层配置等等。
本申请第二实施例提供的技术方案中，所述CU指示所述DU进行所述信令无线承载的配置，从而获取了所述DU对所述信令无线承载的配置，实现了CU-DU架构下信令无线承载的重复模式。
本申请第三实施例提供一种接入网侧设备，如图6所示的接入网侧设备的结构示意图，包括接收单元601和发送单元602。
所述接入网侧设备可以为前述第一实施例中的CU或所述CU中的芯片。所述发送单元602，用于向DU发送第一消息，所述第一消息中指示数据无线承载的重复模式在所述CU与所述DU之间接口上的至少两个上行隧道端点的信息。所述接收单元601，用于接收所述DU发送的第二消息，所述第二消息中指示所述数据无线承载在所述CU与所述DU之间接口上的至少两个下行隧道端点的信息和所述数据无线承载的主通道的标识。作为一种实现方式，所述至少两个下行隧道端点中每一个下行隧道端点一一对应于所述至少两个上行隧道端点中每一个上行隧道端点。在这种情况下，所述接收单元601和所述发送单元602可以分别执行前述第一实施例中CU的接收动作和发送动作，具体参照第一实施例中CU的动作，这里不再赘述。
所述接入网侧设备可以为前述第一实施例中的DU或所述DU中的芯片。所述接收单元601，用于接收CU发送的第一消息，所述第一消息中指示数据无线承载的重复模式在所述CU与所述DU之间接口上的至少两个上行隧道端点的信息；所述发送单元602，用于向所述CU发送的第二消息，所述第二消息中指示所述数据无线承载在所述CU与所述DU之间接口上的至少两个下行隧道端点的信息和所述数据无线承载的主通道的标识。作为一种实现方式，所述至少两个下行隧道端点中每一个下行隧道端点一一对应于所述至少两个上行隧道端点中每一个上行隧道端点。在这种情况下，所述接收单元601和所述发送单元602可以分别执行前述第一实施例中DU的接收动作和发送动作。具体参照第一实施例中DU的动 作，这里不再赘述。
所述接入网侧设备可以为前述第二实施例中的CU或所述CU中的芯片。所述发送单元602，用于向DU发送信令无线承载的标识和用于指示对所述信令无线承载的重复模式进行配置的指示信息；所述接收单元601，用于接收所述DU发送的所述信令无线承载的所述重复模式的配置和所述信令无线承载的主通道的标识。在这种情况下，所述接收单元601和所述发送单元602可以分别执行前述第二实施例中CU的接收动作和发送动作。具体参照第二实施例中CU的动作，这里不再赘述。
所述接入网侧设备可以为前述第二实施例中的DU或所述DU中的芯片。所述接收单元601，用于接收CU发送的信令无线承载的标识和用于指示对所述信令无线承载的重复模式进行配置的指示信息；所述发送单元602，用于向所述CU发送所述信令无线承载的重复模式的配置，和所述信令无线承载的主通道的标识。在这种情况下，所述接收单元601和所述发送单元602可以分别执行前述第二实施例中DU的接收动作和发送动作。具体参照第二实施例中CU的动作，这里不再赘述。
在一种具体实现中，所述接收单元601和所述发送单元602分别为接收电路和发送电路。所述接入网侧设备还可以包括处理电路，例如以至少一个处理器(processor)的形式，实现前述各个消息的产生和处理。所述接入网侧设备还可以包括其它电子线路，例如连接所述接收电路和所述发送电路的线路。在所述接入网侧设备为DU时，所述接入网侧设备还可以包括射频天线，以向终端侧设备发送各种信息。
在另一种具体实现中，所述接入网侧设备可以包括处理器和存储器，所述存储器存储代码，所述代码被所述处理器调用时，可以执行上述各个方法实施例中CU或DU所执行的方法。具体地，所述代码，包含多个数据结构，每个数据结构用于实现前述各个协议层的功能。在所述接入网侧设备为CU或CU的控制面设备或CU的用户面设备或CU中的芯片时，所述代码包括的数据结构至少用于实现PDCP层的功能，这种情况下，所述接收单元601可以为所述数据结构的输入接口，所述发送单元602为所述数据结构的输出接口。在所述接入网侧设备为DU或DU的控制面设备或DU的用户面设备或DU中的芯片时,所述代码包括的数据结构至少用于实现RLC层的功能，其中所述接收单元601可以为所述数据结构的输入接口，所述发送单元为所述数据结构的输出接口。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的芯片系统或计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、装置(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或 方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。

Claims (46)

  1. 一种集中式单元-分布式单元CU-DU架构下重复模式的通信处理方法，其特征在于，包括：
    CU向DU发送第一消息，所述第一消息中指示数据无线承载的重复模式在所述CU与所述DU之间接口上的至少两个上行隧道端点的信息；
    所述CU接收所述DU发送的第二消息，所述第二消息中指示所述数据无线承载在所述CU与所述DU之间接口上的至少两个下行隧道端点的信息和所述数据无线承载的主通道的标识。
  2. 如权利要求1所述的方法，其特征在于，所述至少两个下行隧道端点中每一个下行隧道端点一一对应于所述至少两个上行隧道端点中每一个上行隧道端点。
  3. 如权利要求1或2所述的方法，其特征在于，所述数据无线承载的重复模式为：所述数据无线承载在PDCP层的一个PDCP实体对应RLC层的至少两个RLC实体，且所述PDCP实体上的部分或全部数据在所述至少两个RLC实体上重复传输。
  4. 如权利要求1-3任意一项所述的方法，其特征在于，所述第一消息中还指示对所述数据无线承载配置所述重复模式。
  5. 如权利要求1-4任意一项所述的方法，其特征在于，所述主通道的标识为所述第二消息中指示的所述至少两个下行隧道端点中仅一个下行隧道端点对应的通道的标识。
  6. 如权利要求1-5任意一项所述的方法，其特征在于，
    所述第一消息中还指示所述至少两个上行隧道端点中对应所述主通道的上行隧道端点；或者，
    所述第二消息中还指示所述至少两个下行隧道端点中对应所述主通道的下行隧道端点；或者，
    所述至少两个上行隧道端点中的对应所述主通道的上行隧道端点为协议预定义；或者，
    所述至少两个下行隧道端点中的对应所述主通道的下行隧道端点为协议预定义。
  7. 如权利要求1-6任意一项所述的方法，其特征在于，所述方法还包括：
    所述CU通过所述DU向终端侧设备通知所述数据无线承载的主通道的标识。
  8. 一种集中式单元-分布式单元CU-DU架构下重复模式的通信处理方法，其特征在于，包括：
    CU向DU发送信令无线承载的标识和用于指示对所述信令无线承载的重复模式进行配置的指示信息；
    所述CU接收所述DU发送的所述信令无线承载的所述重复模式的配置和所述 信令无线承载的主通道的标识。
  9. 如权利要求8所述的通信处理方法，其特征在于，所述信令无线承载的重复模式为：所述信令无线承载在PDCP层的一个PDCP实体对应RLC层的至少两个RLC实体，且所述PDCP实体上的部分或全部数据在所述至少两个RLC实体上重复传输。
  10. 如权利要求8或9所述的通信处理方法，其特征在于，所述方法还包括：
    所述CU向所述DU发送CU-DU接口消息；
    在所述信令无线承载的重复模式未被激活的情况下，所述CU-DU接口消息中包含属于所述信令无线承载的一个RRC消息；或者，
    在所述信令无线承载的重复模式被激活的情况下，所述CU-DU接口消息包含属于所述信令无线承载的具有相同PDCP编号的至少两个RRC消息。
  11. 如权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述CU向所述DU发送CU-DU接口消息，所述CU-DU接口消息中包含至少一个RRC消息和所述至少一个RRC消息的每一个RRC消息发往的通道的标识。
  12. 如权利要求8-11任意一项所述的方法，其特征在于，所述方法还包括：
    所述CU通过所述DU向终端侧设备通知所述信令无线承载的主通道的标识。
  13. 一种集中式单元-分布式单元CU-DU架构下重复模式的通信处理方法，其特征在于，包括：
    DU接收CU发送的第一消息，所述第一消息中指示数据无线承载的重复模式在所述CU与所述DU之间接口上的至少两个上行隧道端点的信息；
    所述DU向所述CU发送的第二消息，所述第二消息中指示所述数据无线承载在所述CU与所述DU之间接口上的至少两个下行隧道端点的信息和所述数据无线承载的主通道的标识。
  14. 如权利要求13所述的方法，其特征在于，所述至少两个下行隧道端点中每一个下行隧道端点一一对应于所述至少两个上行隧道端点中每一个上行隧道端点。
  15. 如权利要求13或14所述的方法，其特征在于，所述数据无线承载的重复模式为：所述数据无线承载在PDCP层的一个PDCP实体对应RLC层的至少两个RLC实体，且所述PDCP实体上的部分或全部数据在所述至少两个RLC实体上重复传输。
  16. 如权利要求13-15任意一项所述的方法，其特征在于，所述第一消息中还指示对所述数据无线承载配置所述重复模式。
  17. 如权利要求13-16任意一项所述的方法，其特征在于，所述主通道的标识为所述第二消息中指示的所述至少两个下行隧道端点中仅一个下行隧道端点对应的通道的标识。
  18. 如权利要求13-17任意一项所述的方法，其特征在于，
    所述第一消息中还指示所述至少两个上行隧道端点中对应所述主通道的上 行隧道端点；或者，
    所述第二消息中还指示所述至少两个下行隧道端点中对应所述主通道的下行隧道端点；或者，
    所述至少两个上行隧道端点中对应所述主通道的上行隧道端点为协议预定义；
    所述至少两个下行隧道端点中对应所述主通道的上行隧道端点为协议预定义。
  19. 一种集中式单元-分布式单元CU-DU架构下重复模式的通信处理方法，其特征在于，包括：
    DU接收CU发送的信令无线承载的标识和用于指示对所述信令无线承载的重复模式进行配置的指示信息；
    所述DU向所述CU发送所述信令无线承载的重复模式的配置，和所述信令无线承载的主通道的标识。
  20. 如权利要求19所述的方法，其特征在于，所述信令无线承载的重复模式为：所述信令无线承载在PDCP层的一个PDCP实体对应RLC层的至少两个RLC实体，且所述PDCP实体上的部分或全部数据在所述至少两个RLC实体上重复传输。
  21. 如权利要求19或20所述的方法，其特征在于，所述方法还包括：
    所述DU接收所述CU发送的CU-DU接口消息；其中，
    在所述信令无线承载的重复模式未被激活的情况下，所述CU-DU接口消息中包含属于所述信令无线承载的一个RRC消息；所述DU通过所述主通道将所述一个RRC消息发送给终端侧设备；或者，
    在所述信令无线承载的重复模式被激活的情况下，所述CU-DU接口消息中包含属于所述信令无线承载的具有相同PDCP编号的至少两个RRC消息；所述DU将通过所述主通道和至少一个辅通道将所述至少两个RRC消息分别发送给所述终端侧设备。
  22. 如权利要求19或20所述的方法，其特征在于，所述方法还包括：
    所述DU接收所述CU发送的CU-DU接口消息，所述CU-DU接口消息中包括至少一个RRC消息和所述至少一个RRC消息的每个RRC消息发往的通道的标识。
  23. 如权利要求19或20所述的方法，其特征在于，所述方法还包括：所述DU接收所述CU发送的CU-DU接口消息,所述CU-DU接口消息中包含RRC消息；其中，
    如果所述RRC消息的PDCP编号重复出现，则所述DU通过辅通道将所述RRC消息发送给终端侧设备；或者，
    如果所述RRC消息的PDCP编号未重复过，则所述DU通过主通道将所述RRC消息发送给终端侧设备。
  24. 一种集中式单元CU，其特征在于，包括：发送单元和接收单元；其中，
    所述发送单元，用于向DU发送第一消息，所述第一消息中指示数据无线承载的重复模式在所述CU与所述DU之间接口上的至少两个上行隧道端点的信息；
    所述接收单元，用于接收所述DU发送的第二消息，所述第二消息中指示所述数据无线承载在所述CU与所述DU之间接口上的至少两个下行隧道端点的信息和所述数据无线承载的主通道的标识。
  25. 如权利要求24所述的CU，其特征在于，所述至少两个下行隧道端点中每一个下行隧道端点一一对应于所述至少两个上行隧道端点中每一个上行隧道端点。
  26. 如权利要求24或25所述的CU，其特征在于，所述数据无线承载的重复模式为：所述数据无线承载在PDCP层的一个PDCP实体对应RLC层的至少两个RLC实体，且所述PDCP实体上的部分或全部数据在所述至少两个RLC实体上重复传输。
  27. 如权利要求24-26任意一项所述的CU，其特征在于，所述第一消息中还指示对所述数据无线承载配置所述重复模式。
  28. 如权利要求24-26任意一项所述的CU，其特征在于，所述主通道的标识为所述第二消息中指示的所述至少两个下行隧道端点中仅一个下行隧道端点对应的通道的标识。
  29. 如权利要求24-26任意一项所述的CU，其特征在于，
    所述发送单元，还用于通过所述DU向终端侧设备通知所述数据无线承载的主通道的标识。
  30. 一种集中式单元CU，其特征在于，包括：发送单元和接收单元，其中，
    所述发送单元，用于向DU发送信令无线承载的标识和用于指示对所述信令无线承载的重复模式进行配置的指示信息；
    所述接收单元，用于接收所述DU发送的所述信令无线承载的所述重复模式的配置和所述信令无线承载的主通道的标识。
  31. 如权利要求30所述的CU，其特征在于，所述信令无线承载的重复模式为：所述信令无线承载在PDCP层的一个PDCP实体对应RLC层的至少两个RLC实体，且所述PDCP实体上的部分或全部数据在所述至少两个RLC实体上重复传输。
  32. 如权利要求30或31所述的CU，其特征在于，
    所述发送单元，还用于向所述DU发送CU-DU接口消息；
    在所述信令无线承载的重复模式未被激活的情况下，所述CU-DU接口消息中包含属于所述信令无线承载的一个RRC消息；或者，
    在所述信令无线承载的重复模式被激活的情况下，所述CU-DU接口消息包含属于所述信令无线承载的具有相同PDCP编号的至少两个RRC消息。
  33. 如权利要求30或31所述的CU，其特征在于，
    所述发送单元，还用于向所述DU发送CU-DU接口消息，所述CU-DU接口消息中包含至少一个RRC消息和所述至少一个RRC消息的每一个RRC消息发往的通道的标识。
  34. 如权利要求30-33任意一项所述的CU，其特征在于，
    所述发送单元，还用于通过所述DU向终端侧设备通知所述信令无线承载的主通道的标识。
  35. 一种分布式单元DU，其特征在于，包括：接收单元和发送单元，其中，
    所述接收单元，用于接收CU发送的第一消息，所述第一消息中指示数据无线承载的重复模式在所述CU与所述DU之间接口上的至少两个上行隧道端点的信息；
    所述发送单元，用于向所述CU发送的第二消息，所述第二消息中指示所述数据无线承载在所述CU与所述DU之间接口上的至少两个下行隧道端点的信息和所述数据无线承载的主通道的标识。
  36. 如权利要求35所述的DU，其特征在于，所述至少两个下行隧道端点中每一个下行隧道端点一一对应于所述至少两个上行隧道端点中每一个上行隧道端点。
  37. 如权利要求35或36所述的DU，其特征在于，所述数据无线承载的重复模式为：所述数据无线承载在PDCP层的一个PDCP实体对应RLC层的至少两个RLC实体，且所述PDCP实体上的部分或全部数据在所述至少两个RLC实体上重复传输。
  38. 如权利要求35-37任意一项所述的DU，其特征在于，所述第一消息中还指示对所述数据无线承载配置所述重复模式。
  39. 如权利要求35-38任意一项所述的DU，其特征在于，所述主通道的标识为所述第二消息中指示的所述至少两个下行隧道端点中仅一个下行隧道端点对应的通道的标识。
  40. 一种分布式单元DU，其特征在于，包括：接收单元和发送单元，其中，
    所述接收单元，用于接收CU发送的信令无线承载的标识和用于指示对所述信令无线承载的重复模式进行配置的指示信息；
    所述发送单元，用于向所述CU发送所述信令无线承载的重复模式的配置，和所述信令无线承载的主通道的标识。
  41. 如权利要求40所述的DU，其特征在于，所述信令无线承载的重复模式为：所述信令无线承载在PDCP层的一个PDCP实体对应RLC层的至少两个RLC实体，且所述PDCP实体上的部分或全部数据在所述至少两个RLC实体上重复传输。
  42. 如权利要求40或41所述的DU，其特征在于，
    所述接收单元，还用于接收所述CU发送的CU-DU接口消息；其中，
    在所述信令无线承载的重复模式未被激活的情况下，所述CU-DU接口消息中包含属于所述信令无线承载的一个RRC消息；所述发送单元还用于通过所述主通道将所述一个RRC消息发送给终端侧设备；或者，
    在所述信令无线承载的重复模式被激活的情况下，所述CU-DU接口消息中包含属于所述信令无线承载的具有相同PDCP编号的至少两个RRC消息；所述发送单元，还用于将通过所述主通道和至少一个辅通道将所述至少两个RRC消息分别发送给所述终端侧设备。
  43. 如权利要求40或41所述的DU，其特征在于，
    所述接收单元，还用于接收所述CU发送的CU-DU接口消息，所述CU-DU接口消息中包括至少一个RRC消息和所述至少一个RRC消息的每个RRC消息发往的通道的标识。
  44. 如权利要求40或41所述的DU，其特征在于，所述接收单元，还用于接收所述CU发送的CU-DU接口消息,所述CU-DU接口消息中包含RRC消息；其中，
    所述发送单元，还用于在所述RRC消息的PDCP编号重复出现时，通过辅通道将所述RRC消息发送给终端侧设备；或者，
    所述发送单元，还用于在所述RRC消息的PDCP编号未重复过时，通过主通道将所述RRC消息发送给终端侧设备。
  45. 一种接入网侧设备，所述接入网侧设备包括存储器和处理器，所述存储器中存储代码，当所述代码被所述处理器调用时，所述接入网侧设备执行如权利要求1-23任意一项所述的方法。
  46. 一种计算机存储介质，其特征在于，所述计算机存储介质包括程序代码，所述程序代码被调用时实现如权利要求1-23任意一项所述的方法。
PCT/CN2019/071563 2018-01-12 2019-01-14 一种cu-du架构下重复模式的通信处理方法和设备 WO2019137519A1 (zh)

Priority Applications (11)

Application Number Priority Date Filing Date Title
JP2019543879A JP6900495B2 (ja) 2018-01-12 2019-01-14 Ｃｕ−ｄｕアーキテクチャにおける重複モード通信処理方法およびデバイス
AU2019207254A AU2019207254B2 (en) 2018-01-12 2019-01-14 Duplication mode communication processing method in cu-du architecture, and device
EP19738568.5A EP3570626B1 (en) 2018-01-12 2019-01-14 Duplication-mode communication processing methods and devices under cu-du architecture
KR1020197022576A KR102311647B1 (ko) 2018-01-12 2019-01-14 Cu-du 아키텍처에서의 복제 모드 통신 처리 방법, 및 디바이스
RU2019126510A RU2779030C2 (ru) 2018-01-12 2019-01-14 Устройство и способ передачи данных в режиме дублирования в cu-du архитектуре
KR1020217031958A KR102352184B1 (ko) 2018-01-12 2019-01-14 Cu-du 아키텍처에서의 복제 모드 통신 처리 방법, 및 디바이스
BR112019018068-0A BR112019018068A2 (pt) 2018-01-12 2019-01-14 método de processamento de comunicação de modo de duplicação em arquitectura cu-du, e dispositivo
CA3049053A CA3049053C (en) 2018-01-12 2019-01-14 Duplication mode communication processing method in cu-du architecture, and device
EP23158759.3A EP4221443A3 (en) 2018-01-12 2019-01-14 Duplication mode communication processing method in cu-du architecture, and device
US16/454,397 US10925103B2 (en) 2018-01-12 2019-06-27 Duplication mode communication processing method in CU-DU architecture, and device
US17/155,798 US11483883B2 (en) 2018-01-12 2021-01-22 Duplication mode communication processing method in CU-DU architecture, and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810032653.6 2018-01-12
CN201810032653.6A CN110035563B (zh) 2018-01-12 2018-01-12 一种cu-du架构下重复模式的通信处理方法和设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/454,397 Continuation US10925103B2 (en) 2018-01-12 2019-06-27 Duplication mode communication processing method in CU-DU architecture, and device

Publications (1)

Publication Number Publication Date
WO2019137519A1 true WO2019137519A1 (zh) 2019-07-18

Family

ID=67219390

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/071563 WO2019137519A1 (zh) 2018-01-12 2019-01-14 一种cu-du架构下重复模式的通信处理方法和设备

Country Status (9)

Country Link
US (2) US10925103B2 (zh)
EP (2) EP4221443A3 (zh)
JP (1) JP6900495B2 (zh)
KR (2) KR102352184B1 (zh)
CN (2) CN110035563B (zh)
AU (1) AU2019207254B2 (zh)
BR (1) BR112019018068A2 (zh)
CA (1) CA3049053C (zh)
WO (1) WO2019137519A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220158785A1 (en) * 2017-05-05 2022-05-19 Samsung Electronics Co., Ltd. System, data transmission method and network equipment supporting pdcp duplication function method and device for transferring supplementary uplink carrier configuration information and method and device for performing connection mobility adjustment
WO2022188160A1 (en) * 2021-03-12 2022-09-15 Nokia Shanghai Bell Co., Ltd. Offline network security configuration
US12096292B2 (en) 2017-05-05 2024-09-17 Samsung Electronics Co., Ltd. System, data transmission method and network equipment supporting PDCP duplication function method and device for transferring supplementary uplink carrier configuration information and method and device for performing connection mobility adjustment

Families Citing this family (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10772008B2 (en) * 2018-01-11 2020-09-08 Comcast Cable Communications, Llc Cell configuration for packet duplication
CN110072276B (zh) * 2018-01-22 2021-04-27 中国移动通信有限公司研究院 无线网元协同方法、分布式单元及集中式单元
CA3095941C (en) * 2018-04-04 2023-10-10 Zte Corporation Method and systems for exchanging messages in a wireless network
WO2020006653A1 (zh) * 2018-07-02 2020-01-09 华为技术有限公司 一种双连接下基于链路质量的分流方法和设备
JP7262941B2 (ja) * 2018-08-06 2023-04-24 シャープ株式会社 端末装置、基地局装置、および方法
CN113366882A (zh) * 2019-01-28 2021-09-07 中兴通讯股份有限公司 动态分组复制汇聚协议配置
EP4012958A4 (en) * 2019-08-14 2022-08-31 Huawei Technologies Co., Ltd. COMMUNICATION PROCESS AND ASSOCIATED MECHANISM
US11122491B2 (en) * 2019-09-05 2021-09-14 Cisco Technology, Inc. In-situ best path selection for mobile core network
CN113596914B (zh) * 2020-04-30 2024-10-15 华为技术有限公司 一种通信方法及装置
EP4066562A4 (en) * 2020-05-19 2023-07-26 ZTE Corporation UPLINK PACKET DUPLICATION METHOD
CN114126085B (zh) * 2022-01-28 2022-04-26 深圳艾灵网络有限公司 工业现场总线通信方法、装置、电子设备及存储介质
WO2024026625A1 (en) * 2022-08-01 2024-02-08 Zte Corporation Multi-path communications for user equipment in centralized unit and distributed unit split architecture
CN118175655A (zh) * 2022-12-09 2024-06-11 维沃移动通信有限公司 传输控制方法、装置、网络侧设备及终端设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170041943A1 (en) * 2011-11-25 2017-02-09 Nec Corporation Radio station and method of processing user data with radio station
CN107342849A (zh) * 2017-06-15 2017-11-10 电信科学技术研究院 一种进行数据处理的方法和设备

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9167498B2 (en) * 2011-06-23 2015-10-20 Telefonaktiebolaget L M Ericsson (Publ) Caching over an interface between a radio access network and a core network
KR101860811B1 (ko) 2012-08-23 2018-05-24 인터디지탈 패튼 홀딩스, 인크 무선 시스템에서의 다중 스케줄러들을 이용한 동작
KR101568310B1 (ko) * 2013-02-01 2015-11-12 주식회사 케이티 스몰 셀 환경에서의 사용자 플레인 데이터 전송 방법 및 장치
US9578593B2 (en) * 2013-06-11 2017-02-21 Futurewei Technologies, Inc. System and method for coordinated remote control of network radio nodes and core network elements
US9980303B2 (en) * 2015-12-18 2018-05-22 Cisco Technology, Inc. Establishing a private network using multi-uplink capable network devices
CN106941733B (zh) * 2016-01-04 2022-05-13 中兴通讯股份有限公司 双连接中实现重配置的方法、主服务基站及辅服务基站
WO2017193344A1 (zh) * 2016-05-12 2017-11-16 华为技术有限公司 访问资源的方法、装置和系统
WO2018044354A1 (en) * 2016-09-01 2018-03-08 Intel IP Corporation Apparatus, system and method of communicating an enhanced directional multi-gigabit (edmg) physical layer protocol data unit (ppdu)
US10750410B2 (en) * 2016-09-30 2020-08-18 Huawei Technologies Co., Ltd. Ultra reliable low latency connection support in radio access networks
US10405231B2 (en) * 2017-04-24 2019-09-03 Motorola Mobility Llc Switching between packet duplication operating modes
EP3399724B1 (en) * 2017-05-05 2022-10-05 ASUSTek Computer Inc. Method and apparatus of transmitting data duplication in a wireless communication system
EP3941153B1 (en) * 2017-05-05 2023-06-07 Samsung Electronics Co., Ltd. Data transmission method and network equipment supporting pdcp duplication function
WO2018228557A1 (zh) 2017-06-15 2018-12-20 华为技术有限公司 一种通信处理方法和通信装置
CN107342851B (zh) * 2017-06-15 2020-05-26 电信科学技术研究院 一种重复传输的配置及重复传输方法及装置
EP3737014B1 (en) * 2017-09-28 2021-12-08 Honda Motor Co., Ltd. Packet duplication activation signaling
US10716096B2 (en) * 2017-11-07 2020-07-14 Apple Inc. Enabling network slicing in a 5G network with CP/UP separation
US11368362B2 (en) * 2017-11-07 2022-06-21 Apple Inc. Transport network layer associations on the FI interface
EP3738249B1 (en) * 2018-01-10 2023-03-01 FG Innovation Company Limited Methods and devices for packet data convergence protocol (pdcp) data transmission in wireless communication systems
US11025456B2 (en) * 2018-01-12 2021-06-01 Apple Inc. Time domain resource allocation for mobile communication
CA3045804A1 (en) * 2018-05-10 2019-11-10 Comcast Cable Communications, Llc Packet duplication control
US11089513B2 (en) * 2018-06-21 2021-08-10 Telefonaktiebolaget Lm Ericsson (Publ) Duplication of traffic of a radio bearer over multiple paths

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170041943A1 (en) * 2011-11-25 2017-02-09 Nec Corporation Radio station and method of processing user data with radio station
CN107342849A (zh) * 2017-06-15 2017-11-10 电信科学技术研究院 一种进行数据处理的方法和设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
KT CORP: "Discussion on Inter DU mobility", 3GPP TSG-RAN WG2 #100, no. R2-1712946, 16 November 2017 (2017-11-16), XP051371073 *
ZTE CORPORATION: "Consideration on the ECN in NR", 3GPP TSG RAN WG2 MEETING #99, no. R2-1708149, 20 August 2017 (2017-08-20), XP051318052 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220158785A1 (en) * 2017-05-05 2022-05-19 Samsung Electronics Co., Ltd. System, data transmission method and network equipment supporting pdcp duplication function method and device for transferring supplementary uplink carrier configuration information and method and device for performing connection mobility adjustment
US11855917B2 (en) * 2017-05-05 2023-12-26 Samsung Electronics Co., Ltd. System, data transmission method and network equipment supporting PDCP duplication function method and device for transferring supplementary uplink carrier configuration information and method and device for performing connection mobility adjustment
US12096292B2 (en) 2017-05-05 2024-09-17 Samsung Electronics Co., Ltd. System, data transmission method and network equipment supporting PDCP duplication function method and device for transferring supplementary uplink carrier configuration information and method and device for performing connection mobility adjustment
WO2022188160A1 (en) * 2021-03-12 2022-09-15 Nokia Shanghai Bell Co., Ltd. Offline network security configuration

Also Published As

Publication number Publication date
JP2020511818A (ja) 2020-04-16
CN110691424A (zh) 2020-01-14
EP4221443A3 (en) 2023-10-11
KR102352184B1 (ko) 2022-01-18
KR20190100375A (ko) 2019-08-28
RU2019126510A (ru) 2021-02-24
BR112019018068A2 (pt) 2020-07-21
CN110035563B (zh) 2023-08-22
US11483883B2 (en) 2022-10-25
CN110691424B (zh) 2020-09-18
AU2019207254B2 (en) 2021-02-25
CN110035563A (zh) 2019-07-19
US10925103B2 (en) 2021-02-16
AU2019207254A1 (en) 2020-01-30
US20190327772A1 (en) 2019-10-24
KR20210126144A (ko) 2021-10-19
EP4221443A2 (en) 2023-08-02
RU2019126510A3 (zh) 2022-02-16
EP3570626A1 (en) 2019-11-20
EP3570626A4 (en) 2020-03-11
JP6900495B2 (ja) 2021-07-07
US20210227600A1 (en) 2021-07-22
CA3049053A1 (en) 2019-07-12
CA3049053C (en) 2022-03-15
EP3570626B1 (en) 2023-03-29
KR102311647B1 (ko) 2021-10-13

Similar Documents

Publication Publication Date Title
WO2019137519A1 (zh) 一种cu-du架构下重复模式的通信处理方法和设备
JP6962350B2 (ja) 無線通信システム、無線局、無線端末、及び制御方法
WO2018171512A1 (zh) 无线配置方法、用户设备和基站
EP4250867A2 (en) Communication method and apparatus for device-to-device system, and storage medium
KR20230118849A (ko) 멀티 링크 피어 투 피어 통신을 위한 통신 장치 및 통신 방법
WO2021027435A1 (zh) 一种安全保护方式确定方法及装置
JP6568585B2 (ja) 無線リソース制御ｒｒｃメッセージ処理方法、装置、及びシステム
JP2018514139A (ja) Ｄ２ｄ中継ノードの確定方法、使用方法及び装置
WO2019157985A1 (zh) 一种无线回传通信处理方法和相关设备
CN110891324A (zh) 一种rrc连接方法、设备及系统
WO2020063438A1 (zh) 一种协调重复传输的方法
CN110662299A (zh) 通信方法、装置及存储介质
WO2017132954A1 (zh) 一种数据传输方法、装置及相关设备
WO2020164620A1 (zh) 一种终端信息的通信处理方法和相关设备
JP7390149B2 (ja) 端末装置、基地局装置、方法、および、集積回路
CN114710525B (zh) 一种新空口车联网终端侧行链路的一致性测试方法和系统
WO2021047443A1 (zh) 一种业务数据包转发的方法及装置
RU2779030C2 (ru) Устройство и способ передачи данных в режиме дублирования в cu-du архитектуре
WO2013071850A1 (zh) 上行链路变更的方法、装置及系统
CN107466074B (zh) 一种处理数据链路的方法和装置
JP6550913B2 (ja) 通信システム
WO2023011345A1 (zh) 数据路由方法、装置、节点及存储介质
WO2021174457A1 (zh) 一种确定复制传输资源的方法、终端设备和网络设备
WO2019036843A1 (zh) 传输数据的方法和设备
CN114846900A (zh) 一种rrc连接方法、设备及系统

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 20197022576

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019543879

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019738568

Country of ref document: EP

Effective date: 20190812

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

Ref document number: 19738568

Country of ref document: EP

Kind code of ref document: A1

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019018068

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2019207254

Country of ref document: AU

Date of ref document: 20190114

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112019018068

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190830