WO2018171696A1 - 建立连接的方法和装置 - Google Patents

建立连接的方法和装置 Download PDF

Info

Publication number
WO2018171696A1
WO2018171696A1 PCT/CN2018/080100 CN2018080100W WO2018171696A1 WO 2018171696 A1 WO2018171696 A1 WO 2018171696A1 CN 2018080100 W CN2018080100 W CN 2018080100W WO 2018171696 A1 WO2018171696 A1 WO 2018171696A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
establishment request
connection establishment
function entity
interface
Prior art date
Application number
PCT/CN2018/080100
Other languages
English (en)
French (fr)
Inventor
罗海燕
张宏卓
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to JP2019546174A priority Critical patent/JP2020508613A/ja
Priority to KR1020197023490A priority patent/KR20190103357A/ko
Priority to BR112019018374A priority patent/BR112019018374A2/pt
Priority to EP18771948.9A priority patent/EP3565372B1/en
Publication of WO2018171696A1 publication Critical patent/WO2018171696A1/zh
Priority to US16/567,385 priority patent/US11082897B2/en

Links

Images

Classifications

    • 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
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • 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/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • 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/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00695—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using split of the control plane or user plane
    • 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/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0072—Transmission or use of information for re-establishing the radio link of resource information of target access point
    • 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/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00837—Determination of triggering parameters for hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • 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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present application relates to communication technologies, and in particular, to a method and apparatus for establishing a connection.
  • the function of the user plane is improved on the basis of the Long Term Evolution (LTE) system.
  • LTE Long Term Evolution
  • the data in the radio bearer RB is offloaded from the master base station (MeNB) to the secondary base station (Secondary eNB, SeNB for short), and the bearer is transmitted through the MeNB and the SeNB and the terminal device UE. .
  • the offloaded data of the NBR needs to pass the transmission delay of the MeNB to the SeNB and the delay of the CU to the DU in the SeNB, and the delay of data transmission is large.
  • Embodiments of the present application provide a method and apparatus for establishing a connection to reduce transmission delay of data in dual connectivity or multiple connections.
  • the method can be applied to a 5G system, which can also be called an NR (new radio) system.
  • 5G system which can also be called an NR (new radio) system.
  • a first aspect of the present application provides a method for establishing a connection, including: when a CU function entity receives a first connection establishment request of a master device, the first connection establishment request includes at least first identifier information of the terminal, and the first DRB.
  • the second connection establishment request is sent to the DU function entity, where the second connection establishment request includes at least the second identifier information of the terminal, the identifier information of the first DRB, and The interface information of the master device, wherein the DU function entity is associated with the target cell; after that, the CU function entity receives the first response message of the DU function entity, and sends a second response message to the master device, where the first response message.
  • the at least the identifier information of the first DRB and the interface information of the DU function entity are included, and the second response message includes at least the identifier information of the first DRB and the interface information of the DU function entity.
  • the interface is allocated by the DU function entity from the row, thereby establishing a connection between the master device and the DU function entity, and the part data of the master device is directly transmitted to the DU function entity through the connection, thereby reducing the data.
  • the transmission delay which reduces the overall data transmission delay.
  • the interface information of the master device includes at least: an interface identifier of the master device and an interface transport address.
  • the interface information of the DU functional entity includes at least an interface identifier and an interface transport address of the DU functional entity.
  • the second connection establishment request further includes identification information of the target cell.
  • the identifier information of the first DRB and the identifier information of the target cell are corresponding to each other in the first connection establishment request.
  • the first connection establishment request includes identification information of multiple cells, and the target cell is one of the multiple cells.
  • the first connection establishment request includes measurement information of each of the multiple cells, and the measurement information of the target cell meets a preset condition.
  • the second aspect of the embodiment of the present application provides a method for establishing a connection, including: when a central node CU function entity receives a first connection establishment request of a master device, the first connection establishment request includes at least first identifier information of the terminal, and the first The identifier information of the DRB, the identifier information of the target cell, and the interface information of the master device; the second response message is sent to the master device, where the second response message includes at least the identifier information of the first DRB and the interface information of the DU function entity, where the DU The function entity is associated with the target cell; the CU function entity sends a second connection establishment request to the DU function entity, and the second connection establishment request includes at least the interface information of the DU function entity, the second identifier information of the terminal, the identifier information of the first DRB, The interface information of the master device; after that, the CU function entity receives the first response message of the DU function entity, where the first response message includes at least the identifier information of the
  • an interface is allocated to the DU functional entity through the CU functional entity, thereby establishing a connection between the primary device and the DU functional entity, and the partial data of the primary device is directly transmitted to the DU functional entity through the connection, thereby reducing the data.
  • the transmission delay which reduces the overall data transmission delay.
  • the interface information of the master device includes at least the interface identifier and the interface transport address of the master device.
  • the interface information of the DU functional entity includes at least an interface identifier and an interface transport address of the DU functional entity.
  • the second connection establishment request includes identification information of the target cell.
  • the identifier information of the first DRB and the identifier information of the target cell are corresponding to each other in the first connection establishment request.
  • the first connection establishment request includes identification information of multiple cells, and the target cell is one of the multiple cells.
  • the first connection establishment request includes measurement information of each of the multiple cells, and the measurement information of the target cell meets a preset condition.
  • a third aspect of the embodiments of the present application provides a method for establishing a connection, where: when the DU function entity receives the second connection establishment request sent by the CU function entity, the second connection establishment request includes at least the second identifier information of the terminal, and the first The ID information of the DRB and the interface information of the master device; the DU function entity sends a first response message to the CU function entity, where the first response message includes at least the identifier information of the first DRB and the interface information of the DU function entity.
  • the interface is allocated by the DU function entity from the row, thereby establishing a connection between the master device and the DU function entity, and the part data of the master device is directly transmitted to the DU function entity through the connection, thereby reducing the data.
  • the transmission delay which reduces the overall data transmission delay.
  • the second connection establishment request includes identification information of the target cell, and the target cell is associated with the DU functional entity.
  • a fourth aspect of the embodiments of the present application provides a device for establishing a connection, including:
  • the receiver is configured to receive a first connection establishment request of the primary device, where the first connection establishment request includes at least first identifier information of the terminal, identifier information of the first data radio bearer DRB, and a target cell.
  • the identification information, the interface information of the master device; the switching circuit is configured to send a second connection establishment request to the distributed node DU function entity, where the second connection establishment request includes at least the second identifier information of the terminal, the identifier information of the first DRB, and the master
  • the switching circuit is configured to receive the first response message of the DU function entity, where the first response message includes at least the identifier information of the first DRB and the interface information of the DU function entity
  • the transmitter is configured to send a second response message to the primary device, where the second response message includes at least the identifier information of the first DRB and the interface information of the DU function entity.
  • the interface information of the master device includes at least: an interface identifier of the master device and an interface transport address.
  • the interface information of the DU functional entity includes at least an interface identifier and an interface transport address of the DU functional entity.
  • the second connection establishment request includes identification information of the target cell.
  • the identifier information of the first DRB and the identifier information of the target cell are corresponding to each other in the first connection establishment request.
  • the first connection establishment request includes identification information of multiple cells, and the target cell is one of the multiple cells.
  • the first connection establishment request includes measurement information of each of the multiple cells, and the measurement information of the target cell meets a preset condition.
  • a fifth aspect of the embodiments of the present application provides a device for establishing a connection, including:
  • the receiver is configured to receive a first connection establishment request of the primary device, where the first connection establishment request includes at least first identifier information of the terminal, identifier information of the first data radio bearer DRB, and a target cell.
  • the switching circuit is configured to receive the first response message of the DU function entity, where the first response message includes at least the identifier information of the first DRB and the identifier information used to indicate whether the DU function entity agrees to establish a connection.
  • the interface information of the master device includes at least: an interface identifier of the master device and an interface transport address.
  • the interface information of the DU functional entity includes at least an interface identifier and an interface transport address of the DU functional entity.
  • the second connection establishment request includes identification information of the target cell.
  • the identifier information of the first DRB and the identifier information of the target cell are corresponding to each other in the first connection establishment request.
  • the first connection establishment request includes identification information of multiple cells, and the target cell is one of the multiple cells.
  • the first connection establishment request includes measurement information of each of the multiple cells, and the measurement information of the target cell meets a preset condition.
  • a sixth aspect of the embodiments of the present application provides a device for establishing a connection, including:
  • the switching circuit is configured to receive a second connection establishment request sent by the CU function entity, where the second connection establishment request includes at least the second identifier information of the terminal, the identifier information of the first DRB, and the interface information of the master device; Sending a first response message to the CU function entity, where the first response message includes at least the identifier information of the first DRB and the interface information of the DU function entity.
  • the second connection establishment request includes identification information of the target cell, and the target cell is associated with the DU functional entity.
  • FIG. 1a is a schematic diagram of a possible division manner between CU-DUs according to an embodiment of the present application
  • Figure 1b is a schematic diagram of the scheme of the fourth method in Figure 1a;
  • Figure 1c is a schematic diagram of the second mode of Figure 1a;
  • FIG. 2 is a schematic diagram of a solution provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a scenario provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of signaling content of a first connection establishment request according to an embodiment of the present disclosure
  • FIG. 5 is a schematic diagram of signaling content of a second connection establishment request according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of a scenario provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of signaling content of a first connection establishment request according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic diagram of a scenario according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic diagram of a scenario according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram of a scenario provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a device 10 for establishing a connection according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a device 20 for establishing a connection according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a device 30 for establishing a connection according to an embodiment of the present application.
  • Multi-connection communication under the CU-DU architecture means that the terminal communicates with one master device and one or more secondary devices, wherein the secondary device has a CU-DU architecture.
  • the CU-DU architecture of the secondary device can be understood as a CU and a DU can be regarded as a secondary device; optionally, multiple secondary devices can share one CU; the primary device can also have a CU-DU architecture. Or does not have a CU-DU architecture.
  • the master device is specifically a primary base station including a CU function entity or a CU function entity and a DU function entity
  • the secondary device is specifically a secondary base station including a CU function entity and a DU function entity.
  • PDCP Packet Data Convergence Protocol
  • PDU Protocol Data Unit
  • the terminal receives the data of the same data radio bearer (DRB) from the primary base station and the secondary base station at the same time.
  • DRB data radio bearer
  • the terminal can also send the same DRB data to the primary base station and the secondary base station at the same time.
  • a terminal also referred to as a user equipment, is a device that provides voice and/or data connectivity to a user, for example, a handheld device having a wireless connection function, an in-vehicle device, and the like.
  • Common terminals include, for example, mobile phones, tablets, notebook computers, PDAs, mobile internet devices (MIDs), wearable devices, such as smart watches, smart bracelets, pedometers, and the like.
  • MIDs mobile internet devices
  • wearable devices such as smart watches, smart bracelets, pedometers, and the like.
  • a base station also known as a radio access network (RAN) device, is a device that connects a terminal to a wireless network.
  • RAN radio access network
  • a base station of a 4G communication system is referred to as an LTE eNB
  • a base station of a 5G communication system is referred to as an NR gNB
  • a base station supporting both a 4G communication system and a 5G communication system is referred to as an eLTE eNB.
  • the primary base station and the secondary base station may be any one of an NR gNB and an eLTE eNB, or may be a base station supporting multiple connections in other communication systems.
  • DRB DRB
  • the bearer between the core network and the terminal is collectively referred to as an Evolved Packet System (EPS) bearer, where the EPS bearer is divided into two segments, and the bearer between the core network and the base station is Called S1 bearer, the bearer between the base station and the terminal is called DRB.
  • the EPS bearer, the S1 bearer, and the DRB are in one-to-one correspondence.
  • the PDU session established between the core network and the base station includes one or more Quality of Service (QoS) flows. Different QoS flows have different QoS requirements. After the QoS flows arrive at the base station, the base station may have one or more QoS sessions. The QoS flow is mapped into one DRB.
  • QoS Quality of Service
  • CU function entity in this application, the functional entity supporting the high-layer protocol stack of the base station is referred to as a CU function entity for convenience of description, but is not the only limitation of its name. In fact, the functional entity can be given in practical applications. Any name.
  • DU functional entity the functional entity supporting the underlying protocol stack of the base station is referred to as a DU functional entity for convenience of description, but is not uniquely limited to its name. In fact, the functional entity may be given in practical applications. Any name. It should be noted that in the embodiment of the present application, one CU function entity may correspond to one DU function entity, or one CU function entity may correspond to multiple DU function entities, and one DU function entity may correspond to one cell, or may correspond to one DU function entity. Multiple cells.
  • Xn is used to refer to the interface between the primary base station and the secondary base station
  • Xx is used to refer to the interface between the CU functional entity and the DU functional entity, but Xn and Xx are not for the above. The unique limit of the interface.
  • FIG. 1a is a schematic diagram of possible division between CU-DUs according to an embodiment of the present application.
  • the NR gNB includes a Radio Resource Control (RRC), a PDCP layer, and a Radio Link Control (RLC), and a Medium Access Control (MAC). And physical layer (Physical Layer, PHY for short) and radio frequency (Radio Frequency, RF) unit.
  • RRC Radio Resource Control
  • RLC Radio Link Control
  • MAC Medium Access Control
  • MAC Medium Access Control
  • physical layer Physical Layer, PHY for short
  • radio frequency Radio Frequency
  • FIG. 1a represents a possible division manner, and the left side of the arrow in each division mode is a part of the CU functional entity, and the right side of the arrow is a part of the DU functional entity.
  • FIG. 1b is a schematic diagram of a scheme of mode 4 in FIG. 1a
  • FIG. 1c is a schematic diagram of a scheme of mode 2 in FIG. 1a.
  • both the primary base station and the secondary base station are specifically base stations of the 5G communication system, which are respectively recorded as MgNB and SgNB.
  • the CU functional entity of the SgNB includes an RRC layer, a PDCP layer, and an RLC layer.
  • the DU functional entity includes a MAC layer and a PHY layer.
  • the CU function of the SgNB The entity includes an RRC layer and a PDCP layer.
  • the DU function entity includes an RLC layer, a MAC layer, and a PHY layer. As shown in FIG. 1b and FIG.
  • the MgNB is directly The connection between the CU function entity of the SgNB and the CU function entity of the SgNB is first sent to the CU function entity of the SgNB, and then sent by the CU function entity of the SgNB to the DU function entity of the SgNB, and finally sent to the terminal by the physical layer of the DU functional entity of the SgNB. That is, regardless of how the CU functional entity and the DU functional entity are divided on the SgNB side, the offloaded data sent by the MgNB to the SgNB needs to pass the transmission delay of the Xn interface and the transmission delay of the Xx interface, and the data transmission delay is large.
  • FIG. 2 is a schematic diagram of a solution provided by an embodiment of the present application.
  • the CU function entity of the SgNB includes RRC and PDCP.
  • DU functional entities include RLC, MAC, and PHY.
  • the division schemes of the CU function entity and the DU function entity shown in FIG. 2 are only an exemplary division scheme, and are not specifically limited thereto. In fact, the embodiments of the present application provide The solution is applicable to any possible partitioning scheme of CU functional entities and DU functional entities.
  • the MgNB not only establishes a first connection with the CU functional entity of the SgNB, but also establishes a second connection with the DU functional entity of the SgNB.
  • the first connection is used for transmitting the data Xn-C of the control plane and the part Xn-U1 of the user plane data for supporting data forwarding at the time of handover.
  • the second connection is used to transmit the portion Xn-U2 of the PDCP PDU in the user plane. Since the part of Xn-U2 in the user plane is directly sent by the MgNB to the DU function entity of the SgNB, the data of this part does not need to pass the transmission delay of the Xx interface, thereby achieving the purpose of reducing the total data transmission delay.
  • FIG. 3 is a schematic diagram of a scenario according to an embodiment of the present disclosure.
  • the signaling interaction between the primary base station MgNB, the CU function entity SgNB-CU of the secondary base station, and the DU functional entity SgNB-DU of the secondary base station includes S11-S14:
  • the MgNB sends a first connection establishment request to the SgNB-CU.
  • the name definition of the "first connection establishment request" is only for convenience and does not have a meaning. For example, it can also be named as a tunnel establishment request, a session establishment request, or a bearer setup request.
  • the first connection setup request is used to request the SgNB to establish a connection between the SgNB-DU and the MgNB, thereby enabling the MgNB to directly offload data to the SgNB-DU.
  • FIG. 4 is a schematic diagram of signaling content of a first connection establishment request according to an embodiment of the present disclosure.
  • the first connection establishment request includes first identifier information of the terminal, and the first DRB. Identification information, identification information of the target cell, and interface information of the MgNB.
  • the first connection establishment request may further include, for example, a traffic classification type, a QoS rule, and the like of the first DRB, where the QoS rule is a packet filter, a precedence order, and a QoS feature. (QoS characteristics) and QoS marking (QoS marking).
  • the QoS characteristic may include a UL and DL maximum flow bit rate, a UL and DL guaranteed flow bit rate, a priority level, and a packet delay budget. (packet delay budget), packet error rate, allocation and retention priority (ARP), and notification control (Notification Control).
  • the split type mainly includes but is not limited to a split bearer type, where the split type may correspond to the DRB one-to-one. It may also be a one-to-many relationship. That is to say, in this embodiment, the first connection establishment request may be exemplarily expressed as at least the first identification information of the terminal, the identification information of the target cell, and the interface information of the MgNB.
  • the interface information of the MgNB includes an interface identifier of the MgNB and an interface transmission address.
  • the interface identifier is used to indicate the identifier of the interface to be established on the MgNB side
  • the interface transport address is used to indicate the transport address of the interface to be established on the MgNB side.
  • the target cell is used to indicate the cell in which the SgNB-DU is located.
  • the first DRB is used to indicate one DRB to be shunted by the MgNB side.
  • the MgNB determines which target cell under the SgNB corresponds to the first DRB.
  • the mapping between the first DRB and the target cell needs to be given in the first connection establishment request, which can be exemplarily expressed as the identification information of the first DRB in the first connection establishment request.
  • the MgNB sends the measurement control information to the terminal before sending the first connection establishment request.
  • the cell selects the cell whose measurement result meets the preset condition as the target cell according to the information fed back by the terminal.
  • the preset conditions may be specifically set according to specific needs, and are not limited herein.
  • the SgNB-CU sends a second connection establishment request to the SgNB-DU.
  • the target cell may include only one DU functional entity, and may also include multiple DU functional entities.
  • the SgNB-CU defaults to the DU functional entity as SgNB-DU.
  • the SgNB-CU may provide other information (such as the DU load, the number of access users, the resource occupancy rate, etc.) provided by different DU functional entities in the target cell or saved by the SgNB itself.
  • One DU functional entity is selected among the DU functional entities.
  • the second connection establishment request is used to request the SgNB-DU to allocate interface information of the connection to be established on the side of the DU function entity, and establish a connection with the MgNB.
  • 5 is a schematic diagram of signaling content of a second connection establishment request according to an embodiment of the present disclosure.
  • the second connection establishment request includes the second identifier information of the terminal, and the first
  • the identifier information of the DRB and the interface information of the primary base station are optional, and may further include a QoS rule, a first identifier information of the terminal, and identifier information of the target cell.
  • the second connection establishment request may be exemplarily described as including at least the second identification information of the terminal, the identification information of the first DRB, and the interface information of the primary base station.
  • the interface information of the DU function entity side can be exemplarily expressed as the interface information of the DU function entity, which includes the interface identifier of the DU function entity and the interface transport address.
  • the SgNB-CU needs to carry the identifier information of the target cell in the second connection establishment request and send it to the second connection establishment request in the actual scenario.
  • SgNB-DU so that the SgNB-DU determines which cell of the first DRB the data is offloaded to.
  • the second identification information of the terminal is the same as the first identification information of the terminal, and may be, for example, an International Mobile Subscriber Identification Number (IMSI) or an International Mobile Station Equipment Identity (International). Mobile Equipment Identity, referred to as IMEI).
  • IMSI International Mobile Subscriber Identification Number
  • International Mobile Station Equipment Identity International Mobile Station Equipment Identity
  • IMEI Mobile Equipment Identity
  • the second identifier information of the terminal is different from the first identifier information of the terminal.
  • the first identifier information of the terminal may be specifically an interface identifier of the terminal on the MgNB side (for example, the general name may be named MgNB).
  • _ terminal XnAPID the second identification information of the terminal may be specifically the interface identifier of the terminal on the SgNB side (for example, may be generally named SgNB_Terminal XnAPID).
  • the SgNB-CU needs to determine the second identification information of the terminal on the SgNB according to the first identification information of the terminal included in the first connection establishment request.
  • the second identification information of the terminal and the first identification information of the terminal are used to indicate the target terminal to be sent after the data is offloaded, regardless of the foregoing relationship between the second identification information of the terminal and the first identification information of the terminal.
  • the SgNB-DU sends a first response message to the SgNB-CU.
  • the SgNB-DU after receiving the second connection establishment request, the SgNB-DU needs to determine whether it needs to allocate the interface information connected to the DU function entity side.
  • SgNB-DU There may be many ways in which SgNB-DU can judge. There are several possible ways to enumerate, but it is not limited to the following:
  • the name of the second connection establishment request may be specifically a DU addition message
  • the name of the second connection establishment request may be specifically a DU multi-connection addition message
  • the specific name of the second connection establishment request is unchanged.
  • the second connection establishment request carries the preset.
  • the identifier information is used to indicate that the SgNB-DU needs to allocate the interface information of the DU function entity side.
  • the second connection establishment request does not carry the identifier information.
  • the specific name of the second connection establishment request is unchanged, and the SgNB-DU only determines whether the interface information of the DU function entity side is carried in the second connection establishment request, for example, when the second connection is performed.
  • the SgNB-DU determines that the interface information of the DU function entity side is not required to be allocated by itself, and when the second connection establishment request does not include the interface information of the DU function entity side, The SgNB-DU determines that it needs to allocate the interface information of the DU function entity side.
  • the SgNB-DU allocates interface information of the DU function entity side.
  • the SgNB-DU establishes a connection with the MgNB according to the interface information of the MgNB and the interface information of the DU function entity side allocated by itself, and the connection is a connection for offloading data in the first DRB.
  • the SgNB-DU sends a first response message to the SgNB-CU, where the first response message includes the identifier information of the first DRB and the interface information of the DU function entity side allocated by the SgNB-DU.
  • the first response message may further include first identifier information of the terminal, second identifier information of the terminal, and the like. That is to say, the first response message can be exemplarily expressed as at least the identification information of the first DRB and the interface information of the DU functional entity.
  • the SgNB-CU sends a second response message to the MgNB.
  • the second response message includes the identifier information of the first DRB and the interface information of the DU function entity.
  • the second response message may further include the first identifier information of the terminal and the second identifier information of the terminal. That is, the second response message may be exemplarily expressed as at least the identification information of the first DRB and the interface information of the DU functional entity.
  • the first identity information of the terminal, the identifier information of the first DRB, the identifier information of the target cell, and the interface information of the MgNB are carried in the first connection establishment request sent by the GNNB, so that the SgNB-CU determines the target cell.
  • the second identifier information of the terminal, the identifier information of the first DRB, and the interface information of the MgNB are carried in the second connection establishment request and sent to the SgNB-DU, so that the SgNB-DU is established according to the second connection.
  • Figure 6 is a schematic diagram of a scenario according to an embodiment of the present disclosure.
  • the signaling interaction between the primary base station MgNB, the CU functional entity SgNB-CU of the secondary base station, and the DU functional entity SgNB-DU of the secondary base station includes S21-S24.
  • the execution mode and the beneficial effects of the S22-S24 are similar to those of the S12-S14 in the scenario of FIG. 3, and are not described herein.
  • FIG. 7 is a schematic diagram of signaling content of a first connection establishment request according to an embodiment of the present disclosure.
  • S21 is compared with S11 in the scenario of FIG. 3, and the difference is that the first connection is established.
  • the request includes a cell list, where the cell list stores identification information of multiple cells, and the target cell in S11 is one of multiple cells in the cell list.
  • the MgNB before transmitting the first connection establishment request, the MgNB first sends the cell measurement control information to the terminal, and then forms a cell list according to the cell identification information returned by the terminal and the measurement result corresponding to the cell identity information, and forms the cell list.
  • the bearer is sent to the SgNB-CU in the first connection setup request.
  • the measurement results involved herein may include one or more of reference signal reception quality, reference signal received power, channel state information, and beam information.
  • the cell list involved in this embodiment may include not only the identity information of the cell and the measurement information of the cell, but also other information, such as access information of the cell, where the cell is connected.
  • the information may be, for example, one or more of a radio access network side terminal identifier, a preamble sequence number, and access time-frequency domain information.
  • the SgNB-CU is required to select a cell from the cell list as the target cell corresponding to the first DRB.
  • the selection strategy may be that the cell whose corresponding measurement result meets the preset condition is used as the target cell. That is to say, the foregoing description about selecting a target cell may be exemplified as that the measurement information of the target cell meets a preset condition.
  • the signal strength of the target cell is the cell with the strongest signal strength in the cell list.
  • the above preset conditions may be specifically configured according to specific needs, rather than being fixed.
  • the SgNB-CU selects the target cell from the cell list carried by the first connection establishment request, and selects the second identifier information of the terminal and the identifier information of the first DRB after selecting the SgNB-DU in the target cell. And the interface information of the interface is sent to the SgNB-DU in the second connection establishment request, so that the SgNB-DU allocates the interface information of the connection to the DU function entity side to be established according to the second connection establishment request, and establishes the relationship with the MgNB.
  • the MgNB primary base station can directly offload part of the data in the first DRB to the SgNB-DU through the connection without going through the transmission delay between the SgNB-CU and the SgNB-DU, thereby achieving a reduction
  • the purpose of the data transmission delay is sent.
  • FIG. 8 is a schematic diagram of a scenario according to an embodiment of the present disclosure.
  • the signaling interaction between the primary base station MgNB, the CU function entity SgNB-CU of the secondary base station, and the DU functional entity SgNB-DU of the secondary base station includes S31-S34:
  • the MgNB sends a first connection establishment request to the SgNB-CU.
  • the SgNB-CU sends a second response message to the MgNB.
  • the interface information to be established on the SgNB side (ie, the interface information of the DU functional entity) to be established in the scenario shown in FIG. 3 is allocated by the SgNB-DU.
  • the interface information on the SgNB side is allocated by the SgNB-CU.
  • the SgNB-CU after receiving the first connection request sent by the GNNB, the SgNB-CU carries the interface information of the SgNB side (ie, the interface information of the DU function entity) that is self-assigned in the S32 in the S32.
  • the response message is sent to the MgNB.
  • the second response message referred to herein is the same as the second response message involved in the embodiment of FIG. 3, and may be different in the optional content.
  • the SgNB-CU sends a second connection establishment request to the SgNB-DU.
  • the second connection establishment request in S33 includes the second in S12.
  • the content that is necessary to include the interface information of the SgNB side allocated by the SgNB-CU ie, the interface information of the DU function entity.
  • the second connection establishment request may be exemplarily expressed as interface information including at least a DU function entity, second identifier information of the terminal, identification information of the first DRB, and interface information of the primary base station. .
  • the SgNB-DU sends a first response message to the SgNB-CU.
  • the first response message of S34 in this embodiment is different from the first response message of S13 in FIG. 3: since the interface information of the SgNB side is allocated by the SgNB-CU in this embodiment, the first response at S34 is The message does not include interface information of the DU function entity, but includes identifier information indicating whether the DU function entity agrees to establish a connection.
  • the first response message of S34 is the same as the first response message of S13. That is to say, in this embodiment, the first response message may be exemplarily expressed as at least the identification information of the first DRB and the first response message.
  • the interface information of the DU functional entity connected to the SgNB side to be established is allocated by the SgNB-CU, and the DU functional entity allocated by the SgNB-DU according to the SgNB-CU
  • the interface information and the interface information of the MgNB establish a connection with the MgNB.
  • the MgNB primary base station can directly offload part of the data in the first DRB to the SgNB-DU through the connection, without the transmission delay between the SgNB-CU and the SgNB-DU, thereby achieving the reduced data transmission.
  • the purpose of the delay is not limited to the delay.
  • FIG. 9 is a schematic diagram of a scenario according to an embodiment of the present disclosure.
  • the signaling interaction between the primary base station MgNB, the CU function entity SgNB-CU of the secondary base station, and the DU functional entity SgNB-DU of the secondary base station includes S41-S44.
  • the execution mode and the beneficial effects of the S42-S44 are similar to those of the S32-S34 in the scenario of FIG. 8, and are not described herein.
  • S41 is different from S31 in the scenario of FIG. 8 in that the first connection establishment request includes a cell list, where the cell list stores identification information of multiple cells, and the target described in S31.
  • the cell is one of a plurality of cells in the cell list.
  • the MgNB before transmitting the first connection establishment request, the MgNB first sends the cell measurement control information to the terminal, and then forms a cell list according to the cell identification information returned by the terminal and the measurement result corresponding to the cell identity information, and carries the cell list in the first A connection establishment request is sent to the SgNB-CU.
  • the cell list involved in this embodiment may include not only the identity information of the cell and the measurement information of the cell, but also other information, such as access information of the cell, where the cell is connected.
  • the information may include, for example, a radio access network side terminal identifier, a preamble sequence number, access time-frequency domain information, and the like.
  • the SgNB-CU is required to select a cell from the cell list as the target cell corresponding to the first DRB.
  • the selection strategy may be that the cell whose corresponding measurement result meets the preset condition is used as the target cell. That is to say, the foregoing description about selecting a target cell may be exemplified as that the measurement information of the target cell meets a preset condition.
  • the signal strength of the target cell is the cell with the strongest signal strength in the cell list.
  • the above preset conditions may be specifically configured according to specific needs, rather than being fixed.
  • the SgNB-CU selects the target cell from the cell list carried by the first connection establishment request, and sets the second identifier information of the terminal, the identifier information of the first DRB, the interface information of the MgNB, and the DU function that is allocated by itself.
  • the interface information of the entity side is sent to the SgNB-DU in the second connection establishment request, so that the SgNB-DU establishes a connection with the MgNB, so that the MgNB primary base station can directly access part of the data in the first DRB through the connection.
  • the traffic is delayed to the SgNB-DU without the transmission delay between the SgNB-CU and the SgNB-DU, thereby achieving the purpose of reducing the data transmission delay.
  • FIG. 10 is a schematic diagram of a scenario according to an embodiment of the present application.
  • the MgNB decides to change the connection established in any of the scenarios in FIG. 3 to FIG. 9 , and the SgNB-DU that has established a connection with the MgNB is called the first.
  • An SgNB-DU, the SgNB-DU to be connected to the MgNB is referred to as a second SgNB-DU.
  • the signaling interaction between the primary base station MgNB, the CU function entity SgNB-CU of the secondary base station, the first SgNB-DU, and the second SgNB-DU includes S51-S54.
  • the MgNB sends a modification request message to the SgNB-CU.
  • the situation in which MgNB changes the current connection may include the following:
  • the MgNB decides to change the interface information currently connected to the MgNB side.
  • the modification request message includes at least the identifier information of the first DRB, and the interface information of the replaced MgNB side.
  • the modification request message may further include an interface identifier of the terminal on the MgNB side and an interface identifier of the terminal on the SgNB side.
  • the MgNB decides to change the target cell on the SgNB side.
  • the MgNB needs to receive the cell measurement information of the SgNB side sent by the terminal or the load information sent by the SgNB side before sending the modification request message. And reselect the target cell based on the information. After the target cell is selected, at least the identifier information of the first DRB and the identifier information of the reselected target cell are carried in the modification request message and sent to the SgNB-CU.
  • the NBNB may send the interface identifier of the terminal on the MgNB side and the interface identifier of the terminal on the SgNB side in the modification request message to the SgNB-CU.
  • the SgNB-CU sends an acknowledgement message for the modification request to the MgNB.
  • the confirmation message includes at least information indicating whether to accept the modification and identification information of the first DRB.
  • the interface identifier of the terminal on the MgNB side and the interface identifier of the terminal on the SgNB side may also be included.
  • the acknowledgement message includes at least the identifier information of the first DRB and the interface information of the DU function entity in the reselected target cell.
  • the interface identifier of the terminal on the MgNB side, the interface identifier of the terminal on the SgNB side, and the access information of the reselected target cell may also be included.
  • the interface information of the DU function entity involved in this embodiment may be allocated by the SgNB-CU, or may be allocated by the second SgNB-DU in the reselected target cell.
  • the method of performing the allocation is similar to the foregoing embodiment and will not be described herein.
  • the SgNB-CU sends a notification message for releasing the connection to the first SgNB-DU, and sends a third connection establishment request to the second SgNB-DU.
  • the first SgNB-DU and the second SgNB-DU may be the same DU functional entity, or may be different functional entities.
  • the notification message and the third connection establishment request are The message may be sent to the DU function entity simultaneously or sequentially as a separate message, or the notification message and the third connection establishment request may be combined into a new request message and sent to the DU function entity.
  • the notification message and the third connection establishment message are respectively sent to the first SgNB-DU and the second SgNB-DU.
  • the notification message is used to notify the first SgNB-DU to release the connection corresponding to the current first DRB, and the notification message may further include a connection address for data forwarding, which is mainly used for the first SgNB-DU to not receive the terminal confirmation. Or the data packets that can be sent in the future are sent back to MgNB.
  • the third connection setup request is for requesting the second SgNB-DU to establish a connection with the MgNB.
  • the content of the third connection establishment request in this embodiment is the same as the content of the second connection establishment request in the foregoing embodiment, and details are not described herein again.
  • the first SgNB-DU sends an acknowledgement message for releasing the connection to the SgNB-CU.
  • the second SgNB-DU sends an acknowledgement message for connection establishment to the SgNB-CU.
  • decision maker who modifies the connection in the actual application may also be the SgNB, and the specific execution method is similar to the execution method in the scenario shown in FIG. 10, and details are not described herein again.
  • This embodiment provides a scheme for changing an existing connection by the MgNB decision, which can make the establishment and change of multiple connections more flexible.
  • FIG. 11 is a schematic structural diagram of a device 10 for establishing a connection according to an embodiment of the present disclosure.
  • the device may be specifically a CU function entity in a secondary base station.
  • the device includes: a receiver 101, and a switch circuit. 102 and the transmitter 103, wherein the switching circuit 102 can be embodied in a practical application as a physical device having a switching circuit such as a switch or a switch board.
  • the receiver 101 is configured to receive a first connection establishment request of the primary device, where the first connection establishment request includes at least the first identifier information of the terminal, the identifier information of the first data radio bearer DRB, the identifier information of the target cell, and the interface information of the master device.
  • the switching circuit 102 is configured to send a second connection establishment request to the distributed node DU function entity, where the second connection establishment request includes at least the second identifier information of the terminal, the identifier information of the first DRB, and the interface information of the master device, where the DU The function entity is associated with the target cell; the switching circuit 102 is configured to receive the first response message of the DU function entity, where the first response message includes at least the identifier information of the first DRB and the interface information of the DU function entity; the transmitter 103 is configured to The device sends a second response message, where the second response message includes at least the identifier information of the first DRB and the interface information of the DU function entity.
  • the interface information of the master device includes at least an interface identifier of the master device and an interface transport address.
  • the interface information of the DU functional entity includes at least an interface identifier and an interface transport address of the DU functional entity.
  • the second connection establishment request may further include identification information of the target cell.
  • the identifier information of the first DRB and the identifier information of the target cell are in a corresponding relationship in the first connection establishment request.
  • the first connection establishment request includes identification information of multiple cells, and the target cell is one of the multiple cells.
  • the first connection establishment request includes measurement information of each of the plurality of cells, and the measurement information of the target cell meets a preset condition.
  • apparatus 10 may include a processor and a memory, wherein the memory is used to store program code that implements the technical solution illustrated in FIG. 3 or FIG. 6, and the processor is configured to execute program code stored in the memory.
  • the device shown in FIG. 11 can perform the technical solution in the scenario shown in FIG. 3 or FIG. 6 , and the execution manner and the beneficial effects thereof are similar to those in FIG.
  • FIG. 12 is a schematic structural diagram of a device 20 for establishing a connection according to an embodiment of the present disclosure.
  • the device may be specifically a CU function entity in a secondary base station.
  • the device includes a receiver 201.
  • the switching circuit 202 and the transmitter 203, wherein the switching circuit 202 can be specifically implemented as a physical device having a switching circuit such as a switch or a switch board in practical applications.
  • the receiver 201 is configured to receive a first connection establishment request of the primary device, where the first connection establishment request includes at least first identifier information of the terminal, identifier information of the first data radio bearer DRB, identifier information of the target cell, and interface information of the master device.
  • the transmitter 203 is configured to send a second response message to the primary device, where the second response message includes at least the identifier information of the first DRB and the interface information of the distributed node DU function entity, where the DU function entity is associated with the target cell.
  • the switching circuit 202 is configured to send a second connection establishment request to the DU function entity, where the second connection establishment request includes at least the interface information of the DU function entity, the second identifier information of the terminal, the identifier information of the first DRB, and the interface information of the master device.
  • the switching circuit is configured to receive the first response message of the DU function entity, where the first response message includes at least the identifier information of the first DRB and the identifier information used to indicate whether the DU function entity agrees to establish a connection.
  • the interface information of the master device includes at least an interface identifier of the master device and an interface transport address.
  • the interface information of the DU functional entity includes at least an interface identifier and an interface transport address of the DU functional entity.
  • the second connection establishment request may further include identification information of the target cell.
  • the identifier information of the first DRB and the identifier information of the target cell are in a corresponding relationship in the first connection establishment request.
  • the first connection establishment request includes identification information of multiple cells, and the target cell is one of the multiple cells.
  • the first connection establishment request includes measurement information of each of the plurality of cells, and the measurement information of the target cell meets a preset condition.
  • the apparatus 20 may include a processor and a memory, wherein the memory is used to store program code for implementing the technical solution shown in FIG. 8 or FIG. 9, and the processor is configured to execute the program code stored in the memory.
  • the device shown in FIG. 12 can perform the technical solution in the scenario shown in FIG. 8 or FIG. 9 , and its execution manner and beneficial effects are similar to those in FIG.
  • FIG. 13 is a schematic structural diagram of a device 30 for establishing a connection according to an embodiment of the present disclosure.
  • the device may be specifically a DU functional entity in a secondary base station.
  • the device includes a switching circuit 301.
  • the switching circuit may be specifically implemented as a physical device having a switching circuit such as a switch or a switch board in practical applications.
  • the switching circuit 301 is configured to receive a second connection establishment request sent by the CU function entity, where the second connection establishment request includes at least the second identifier information of the terminal, the identifier information of the first DRB, and the interface information of the master device; Sending a first response message to the CU function entity, where the first response message includes at least the identifier information of the first DRB and the interface information of the DU function entity.
  • the second connection establishment request may further include identifier information of the target cell, where the target cell is associated with the DU function entity.
  • the apparatus 30 may include a processor and a memory, wherein the memory is used to store program code for implementing the technical solution shown in FIG. 3 or FIG. 6, and the processor is configured to execute the program code stored in the memory.
  • the device shown in FIG. 13 can perform the technical solution in the scenario shown in FIG. 3 or FIG. 6, and the execution manner and the beneficial effects are similar to those in FIG.
  • the disclosed apparatus and method can be implemented in other ways.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above software function parts can be stored in the storage unit.
  • the storage unit includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) or a processor to perform some of the steps of the methods described in various embodiments of the present application.
  • the storage unit includes: one or more memories, such as a read-only memory (ROM), a random access memory (RAM), and an electrically erasable programmable read only memory (EEPROM). and many more.
  • the storage unit may exist independently or may be integrated with the processor.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)) or the like.
  • a magnetic medium eg, a floppy disk, a hard disk, a magnetic tape
  • an optical medium eg, a DVD
  • a semiconductor medium such as a solid state disk (SSD)

Landscapes

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

Abstract

本申请实施例提供一种建立连接的方法和装置，通过CU功能实体接收主设备的第一连接建立请求，第一连接建立请求中至少包括终端的第一标识信息、第一DRB的标识信息、目标小区的标识信息、主设备的接口信息；并通过CU功能实体向DU功能实体发送第二连接建立请求，第二连接建立请求至少包括终端的第二标识信息、第一DRB的标识信息、主设备的接口信息，以请求DU功能实体建立与主设备之间的连接，从而，通过将主设备的部分数据通过该连接直接传输到DU功能实体上，能够降低总的数据传输时延。

Description

建立连接的方法和装置
本申请要求于2017年03月24日提交中国专利局、申请号为201710184022.1、申请名称为“建立连接的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术，尤其涉及一种建立连接的方法和装置。
背景技术
在无线通信技术中，为了支持更高的业务速率和更大的数据吞吐量，在长期演进(Long Term Evolution，简称：LTE)系统的基础上，对用户面的功能做了改进。
现有技术中，通过将无线承载RB中的数据从主基站(Master eNB，简称MeNB)分流到辅基站(Secondary eNB，简称SeNB),同时通过MeNB和SeNB与终端设备UE进行传输的承载来实现。
然而，当SeNB是中央节点CU-分布式节点DU的架构时，NBR的分流数据需要经过MeNB到SeNB的传输时延以及SeNB中CU到DU的时延，数据传输的时延较大。
发明内容
本申请实施例提供一种建立连接的方法和装置，以降低双连接或多连接中数据的传输时延。该方法可以应用与5G系统，其中5G系统也可以称为NR(new radio，新无线)系统。
本申请实施例第一方面提供一种建立连接的方法，包括：当CU功能实体接收到主设备的第一连接建立请求时，第一连接建立请求至少包括终端的第一标识信息、第一DRB的标识信息、目标小区的标识信息、主设备的接口信息，则向DU功能实体发送第二连接建立请求，第二连接建立请求至少包括终端的第二标识信息、第一DRB的标识信息、和主设备的接口信息，其中，DU功能实体与目标小区有关联；在此之后，CU功能实体接收DU功能实体的第一响应消息，并向主设备发送第二响应消息，其中，第一响应消息至少包括第一DRB的标识信息和DU功能实体的接口信息，第二响应消息至少包括第一DRB的标识信息和DU功能实体的接口信息。即，通过DU功能实体来自行分配其上的接口，从而，建立主设备与DU功能实体之间的连接，通过该连接将主设备的部分数据直接传输到DU功能实体上，能够减少此部分数据的传输时延，从而降低总的数据传输时延。
在一种可能的设计中，主设备的接口信息至少包括：主设备的接口标识和接口传输地址。
在一种可能的设计中，DU功能实体的接口信息至少包括DU功能实体的接口标识 和接口传输地址。
在一种可能的设计中，第二连接建立请求还包括目标小区的标识信息。
在一种可能的设计中，在第一连接建立请求中第一DRB的标识信息与目标小区的标识信息存在对应关系。
在一种可能的设计中，第一连接建立请求中包括多个小区的标识信息，目标小区为所述多个小区中的一个。
在一种可能的设计中，第一连接建立请求中包括所述多个小区中每个小区的测量信息，目标小区的测量信息符合预设条件。
本申请实施例第二方面提供一种建立连接的方法，包括：当中央节点CU功能实体接收主设备的第一连接建立请求时，第一连接建立请求至少包括终端的第一标识信息、第一DRB的标识信息、目标小区的标识信息、主设备的接口信息；则向主设备发送第二响应消息，第二响应消息至少包括第一DRB的标识信息和DU功能实体的接口信息，其中，DU功能实体与目标小区有关联；CU功能实体向DU功能实体发送第二连接建立请求，第二连接建立请求至少包括DU功能实体的接口信息、终端的第二标识信息、第一DRB的标识信息、主设备的接口信息；在此之后，CU功能实体接收DU功能实体的第一响应消息，第一响应消息至少包括第一DRB的标识信息和用于表示所述DU功能实体是否同意建立连接的标识信息。即，通过CU功能实体来为DU功能实体分配接口，从而，建立主设备与DU功能实体之间的连接，通过该连接将主设备的部分数据直接传输到DU功能实体上，能够减少此部分数据的传输时延，从而降低总的数据传输时延。
在一种可能的设计中，主设备的接口信息至少包括主设备的接口标识和接口传输地址。
在一种可能的设计中，DU功能实体的接口信息至少包括DU功能实体的接口标识和接口传输地址。
在一种可能的设计中，第二连接建立请求包括目标小区的标识信息。
在一种可能的设计中，在第一连接建立请求中第一DRB的标识信息与目标小区的标识信息存在对应关系。
在一种可能的设计中，第一连接建立请求中包括多个小区的标识信息，目标小区为所述多个小区中的一个。
在一种可能的设计中，第一连接建立请求中包括所述多个小区中每个小区的测量信息，目标小区的测量信息符合预设条件。
本申请实施例第三方面提供一种建立连接的方法，包括：当DU功能实体接收CU功能实体发送的第二连接建立请求时，第二连接建立请求至少包括终端的第二标识信息、第一DRB的标识信息、主设备的接口信息主设备；DU功能实体向CU功能实体发送第一响应消息，第一响应消息至少包括第一DRB的标识信息、DU功能实体的接口信息。即，通过DU功能实体来自行分配其上的接口，从而，建立主设备与DU功能实体之间的连接，通过该连接将主设备的部分数据直接传输到DU功能实体上，能够减少此部分数据的传输时延，从而降低总的数据传输时延。
在一种可能的设计中，第二连接建立请求包括目标小区的标识信息，目标小区与DU功能实体有关联。
本申请实施例第四方面提供一种建立连接的装置，包括：
接收器、交换电路和发送器，其中，接收器用于接收主设备的第一连接建立请求，第一连接建立请求至少包括终端的第一标识信息、第一数据无线承载DRB的标识信息、目标小区的标识信息、主设备的接口信息；交换电路用于向分布式节点DU功能实体发送第二连接建立请求，第二连接建立请求至少包括终端的第二标识信息、第一DRB的标识信息、主设备的接口信息，其中，DU功能实体与目标小区有关联；交换电路用于接收DU功能实体的第一响应消息，第一响应消息至少包括第一DRB的标识信息和DU功能实体的接口信息；发送器用于向主设备发送第二响应消息，第二响应消息至少包括第一DRB的标识信息和DU功能实体的接口信息。
在一种可能的设计中，主设备的接口信息至少包括：主设备的接口标识和接口传输地址。
在一种可能的设计中，DU功能实体的接口信息至少包括DU功能实体的接口标识和接口传输地址。
在一种可能的设计中，第二连接建立请求包括目标小区的标识信息。
在一种可能的设计中，在第一连接建立请求中第一DRB的标识信息与目标小区的标识信息存在对应关系。
在一种可能的设计中，第一连接建立请求中包括多个小区的标识信息，目标小区为所述多个小区中的一个。
在一种可能的设计中，第一连接建立请求中包括所述多个小区中每个小区的测量信息，目标小区的测量信息符合预设条件。
本申请实施例第五方面提供一种建立连接的装置，包括：
接收器、交换电路和发送器，其中，接收器用于接收主设备的第一连接建立请求，第一连接建立请求至少包括终端的第一标识信息、第一数据无线承载DRB的标识信息、目标小区的标识信息、主设备的接口信息；发送器用于向主设备发送第二响应消息，第二响应消息至少包括第一DRB的标识信息和分布式节点DU功能实体的接口信息，其中，DU功能实体与所述目标小区有关联；交换电路用于向DU功能实体发送第二连接建立请求，第二连接建立请求至少包括DU功能实体的接口信息、终端的第二标识信息、第一DRB的标识信息、主设备的接口信息；交换电路用于接收DU功能实体的第一响应消息，第一响应消息至少包括第一DRB的标识信息和用于表示DU功能实体是否同意建立连接的标识信息。
在一种可能的设计中，主设备的接口信息至少包括：主设备的接口标识和接口传输地址。
在一种可能的设计中，DU功能实体的接口信息至少包括DU功能实体的接口标识和接口传输地址。
在一种可能的设计中，第二连接建立请求包括目标小区的标识信息。
在一种可能的设计中，在第一连接建立请求中第一DRB的标识信息与目标小区的标识信息存在对应关系。
在一种可能的设计中，第一连接建立请求中包括多个小区的标识信息，目标小区为所述多个小区中的一个。
在一种可能的设计中，第一连接建立请求中包括所述多个小区中每个小区的测量信息，目标小区的测量信息符合预设条件。
本申请实施例第六方面提供一种建立连接的装置，包括：
交换电路，交换电路用于接收CU功能实体发送的第二连接建立请求，第二连接建立请求至少包括终端的第二标识信息、第一DRB的标识信息、主设备的接口信息；交换电路用于向CU功能实体发送第一响应消息，第一响应消息至少包括第一DRB的标识信息、DU功能实体的接口信息。
在一种可能的设计中，第二连接建立请求包括目标小区的标识信息，目标小区与DU功能实体有关联。
附图说明
图1a为本申请实施例提供的CU-DU之间可能的划分方式示意图；
图1b为图1a中方式四的方案示意图；
图1c为图1a中方式二的方案示意图；
图2为本申请实施例提供的一种解决方案示意图；
图3为本申请实施例提供的一种场景示意图；
图4为本申请实施例提供的一种第一连接建立请求的信令内容示意图；
图5为本申请实施例提供的一种第二连接建立请求的信令内容示意图；
图6为本申请实施例提供的一种场景示意图；
图7为本申请实施例提供的一种第一连接建立请求的信令内容示意图；
图8为本申请实施例提供的一种场景示意图；
图9为本申请实施例提供的一种场景示意图；
图10为本申请实施例提供的一种场景示意图；
图11为本申请实施例提供的一种建立连接的装置10的结构示意图；
图12为本申请实施例提供的一种建立连接的装置20的结构示意图；
图13为本申请实施例提供的一种建立连接的装置30的结构示意图。
具体实施方式
本申请实施例的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请实施例例如能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
本申请实施例应用于中央节点(Central Unit，简称CU)-分布式节点(Distributed Unit，简称DU)架构下的多连接通信系统。CU-DU架构下的多连接通信是指终端与一个主设备以及一个或多个辅设备进行通信，其中辅设备具有CU-DU架构。在该场景下， 辅设备具有CU-DU架构可以理解为一个CU和一个DU可以视为一个辅设备；可选的，多个辅设备可以共享一个CU；主设备也可以具有CU-DU架构，或者不具有CU-DU架构。在本申请实施例中为了叙述方便，将主设备具体为包含CU功能实体或者包含CU功能实体和DU功能实体的主基站；将辅设备具体为包含CU功能实体和DU功能实体的辅基站。在该通信系统下，主基站产生的全部或部分分组数据汇聚协议(Packet Data Convergence Protocol，简称PDCP)协议数据单元(Protocol Data Unit，简称PDU)分流到与其连接的一个或多个辅基站上，此时终端同时从主基站和辅基站上接收同一个数据无线承载(Data Radio Bearer，简称DRB)的数据，此时终端也可以同时向主基站和辅基站发送同一个DRB的数据。以下对本申请中的部分用语进行解释说明，以便于本领域技术人员理解。
1)终端，又称之为用户设备，是一种向用户提供语音和/或数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。常见的终端例如包括：手机、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，简称MID)、可穿戴设备，例如智能手表、智能手环、计步器等。
2)基站，又称为无线接入网(Radio Access Network，简称RAN)设备是一种将终端接入到无线网络的设备。在本申请实施例中，为了区别起见，将4G通信系统的基站称为LTE eNB，将5G通信系统的基站称为NR gNB，将既支持4G通信系统又支持5G通信系统的基站称为eLTE eNB。本申请实施例中，主基站和辅基站可以是NR gNB、eLTE eNB中的任意一种，也可以其他通信制式中支持多连接的基站。
3)DRB，本申请实施例中将核心网与终端之间承载统称为演进分组系统(Evolved Packet System，简称EPS)承载，其中，EPS承载分为两段，核心网和基站之间的承载被称为S1承载，基站和终端之间的承载称为DRB。其中，EPS承载、S1承载和DRB一一对应。核心网和基站之间建立的PDU会话中包含一个或多个服务质量(Quality of Service，简称QoS)流，不同QoS流有不同的QoS要求，QoS流到达基站后，基站可能将一个或多个QoS流映射到一个DRB内。
4)CU功能实体，本申请中为了便于叙述将支持基站高层协议栈的功能实体称为CU功能实体，但并不是对其名称的唯一限定，实际上，该功能实体在实际应用中可以被赋予任意名称。
5)DU功能实体，本申请中为了便于叙述将支持基站底层协议栈的功能实体称为DU功能实体，但并不是对其名称的唯一限定，实际上，该功能实体在实际应用中可以被赋予任意名称。需要说明的是在本申请实施例中一个CU功能实体可能对应一个DU功能实体，也可能一个CU功能实体对应多个DU功能实体，一个DU功能实体可能对应一个小区，也可能一个DU功能实体对应多个小区。
另外，本申请实施例中为了便于叙述用Xn来指代主基站与辅基站之间的接口，用Xx来指代CU功能实体与DU功能实体之间的接口，但是Xn和Xx并不是对上述接口的唯一限定。
在5G通信系统的基站中CU功能实体和DU功能实体之间的划分方式可能有多种，如图1a所示，图1a为本申请实施例提供的CU-DU之间可能的划分方式示意图，在图 1a中，NR gNB包括无线资源控制层(Radio Resource Control，简称RRC)、PDCP层和无线链路控制层(Radio Link Control，简称RLC)、媒质接入控制层(Medium Access Control，简称MAC)和物理层(Physical Layer，简称PHY)和射频(Radio Frequency，简称RF)单元。其中，图1a中每个箭头所在的位置均代表一种可能的划分方式，每种划分方式中箭头的左侧为CU功能实体的部分，箭头的右侧为DU功能实体的部分。特别的，图1b为图1a中方式四的方案示意图，图1c为图1a中方式二的方案示意图。在图1b和图1c中，主基站和辅基站均被具体为5G通信系统的基站，分别记为MgNB和SgNB。其中，在图1b所示的方案中，SgNB的CU功能实体包括RRC层、PDCP层和RLC层(。DU功能实体包括MAC层和PHY层。在图1c所示的方案中，SgNB的CU功能实体包括RRC层和PDCP层。DU功能实体包括RLC层、MAC层和PHY层。如图1b和图1c所示，在现有技术中，无论CU功能实体和DU功能实体如何划分，MgNB均直接与SgNB的CU功能实体建立连接，MgNB的分流数据先发送给SgNB的CU功能实体，再由SgNB的CU功能实体发送至SgNB的DU功能实体，最终由SgNB的DU功能实体的物理层发送给终端，即无论在SgNB侧CU功能实体和DU功能实体如何划分，由MgNB发送给SgNB的分流数据均需经过Xn接口的传输时延和Xx接口的传输时延，数据传输时延较大。
针对上述问题，图2为本申请实施例提供的一种解决方案示意图，在图2中，SgNB的CU功能实体包括RRC和PDCP。DU功能实体包括RLC、MAC和PHY。这里需要说明的是，图2中示出的CU功能实体和DU功能实体的划分方案仅为一种示例性的划分方案，而不是对其进行的具体限定，实际上，本申请实施例提供的解决方案适用于任意一种CU功能实体和DU功能实体的可能的划分方案。在图2所示的解决方案中，MgNB不仅与SgNB的CU功能实体建立第一连接，同时还与SgNB的DU功能实体建立第二连接。其中，第一连接用于传输控制面的数据Xn-C和用户面数据中用于支持切换时的数据转发的部分Xn-U1。第二连接用于传输用户面中PDCP PDU的部分Xn-U2。由于用户面中Xn-U2的部分是由MgNB直接发送给SgNB的DU功能实体的，因此，此部分的数据不需经过Xx接口的传输时延，从而达到了降低总数据传输时延的目的。
针对图2所示的解决方案，本申请提供了如下几种实施例，下面结合具体场景对实施例进行说明：
图3为本申请实施例提供的一种场景示意图，如图3所示，主基站MgNB、辅基站的CU功能实体SgNB-CU、辅基站的DU功能实体SgNB-DU之间的信令交互包括S11-S14：
S11、MgNB向SgNB-CU发送第一连接建立请求。
其中，“第一连接建立请求”的名称定义仅为了方便区别，而不具有限制意义。例如其还可以命名为隧道建立请求、会话建立请求或承载建立请求等。该第一连接建立请求用于请求SgNB建立SgNB-DU与MgNB之间的连接，从而使得MgNB能够将数据直接分流到SgNB-DU上。
图4为本申请实施例提供的一种第一连接建立请求的信令内容示意图，如图4所示，在本实施例中第一连接建立请求中包括终端的第一标识信息、第一DRB的标识信息、目标小区的标识信息、MgNB的接口信息。可选的，第一连接建立请求中还可以包括例如第一DRB的分流类型、QoS规则等信息，其中，QoS规则由数据包滤波规则 (packet filter)、优先级顺序(precedence order)、QoS特性(QoS characteristics)以及QoS标记(QoS marking)等组成。其中，QoS characteristic可能包括上行和下行最大流量比特率(UL and DL maximum flow bit rate)，上行和下行保证流量比特率(UL and DL guaranteed flow bit rate)，优先级(priority level)，包延迟预算(packet delay budget)，误包率(packet error rate),分配与保持优先级(Allocation and Retention Priority,简称ARP)以及通知控制(Notification Control)等。分流类型主要包括但不仅限于分流承载(split bearer)类型，其中分流类型可能和DRB一一对应。也可能是一对多的关系。也就是说，在本实施例中，第一连接建立请求可示例性的表述为至少包括终端的第一标识信息、目标小区的标识信息、MgNB的接口信息。其中，MgNB的接口信息包括MgNB的接口标识和接口传输地址。该接口标识用于表示待建立的连接在MgNB侧的接口的标识，该接口传输地址用于表示待建立的连接在MgNB侧的接口的传输地址。目标小区用于表示SgNB-DU所在的小区。第一DRB用于表示MgNB侧待分流的一个DRB。
另外，在本实施例中，第一DRB对应SgNB下的哪个目标小区是由MgNB确定的。在这种情况下，MgNB在第一连接建立请求中需要给出第一DRB与目标小区的对应关系，即可示例性的将其表述为在第一连接建立请求中存在第一DRB的标识信息与目标小区的标识信息的对应关系。比如，MgNB在发送第一连接建立请求之前向终端发送测量控制信息，待终端反馈测量信息后，根据终端反馈的信息选择测量结果符合预设条件的小区作为目标小区。其中预设条件可以根据具体需求具体设置，在这里不做限定。
S12、SgNB-CU向SgNB-DU发送第二连接建立请求。
实际场景中目标小区下可能仅包括一个DU功能实体，也可能包括多个DU功能实体。
在目标小区仅对应一个DU功能实体的情况中，SgNB-CU默认该DU功能实体为SgNB-DU。在目标小区对应多个DU功能实体的情况中，SgNB-CU可以根据目标小区下不同DU功能实体提供或SgNB自己保存的其他信息(比如DU负载，接入用户数目，资源占用率等)从多个DU功能实体中选择一个DU功能实体。在确定DU功能实体即SgNB-DU之后，SgNB-CU向SgNB-DU发送第二连接建立请求。在这里，“第二连接建立请求”的命名仅为与上述“第一连接建立请求”进行区别，而不具备限制意义。第二连接建立请求用于请求SgNB-DU分配待建立的连接在DU功能实体侧的接口信息，并建立与MgNB之间的连接。其中，图5为本申请实施例提供的一种第二连接建立请求的信令内容示意图，如图5所示，本实施例中第二连接建立请求中包括终端的第二标识信息、第一DRB的标识信息和主基站的接口信息，可选的，还可以包括QoS规则，终端的第一标识信息、目标小区的标识信息等。也就是说，第二连接建立请求示例性的可表述为至少包括终端的第二标识信息、第一DRB的标识信息和主基站的接口信息。而在上述表述中，DU功能实体侧的接口信息则可以示例性的表述为DU功能实体的接口信息，其包括DU功能实体的接口标识和接口传输地址。
这里需要说明的是，由于在实际场景中一个DU功能实体下可能存在多个小区，因此，在这种情况下，SgNB-CU需要将目标小区的标识信息携带在第二连接建立请求中发送给SgNB-DU，以使SgNB-DU确定第一DRB的数据分流到其下的哪一个小区中。
另外，在本实施例中，终端的第二标识信息与终端的第一标识信息之间可能存在两种关系：
在一种可能的关系中，终端的第二标识信息与终端的第一标识信息相同，比如可以为国际移动客户识别码(International Mobile Subscriber Identification Number，简称IMSI)或国际移动台设备识别码(International Mobile Equipment Identity，简称IMEI)等。
在另一种可能的关系中，终端的第二标识信息与终端的第一标识信息不相同，比如，终端的第一标识信息可以被具体为终端在MgNB侧的接口标识(例如一般可能命名MgNB_终端XnAPID)，而终端的第二标识信息则可以被具体为终端在SgNB侧的接口标识(例如一般可能命名为SgNB_终端XnAPID)。在这种情况下，SgNB-CU需要根据第一连接建立请求中所包含的终端的第一标识信息，确定终端在SgNB上的第二标识信息。
但是，不论终端的第二标识信息与终端的第一标识信息之间是上述种关系，终端的第二标识信息和终端的第一标识信息均用于指示数据分流后待发送的目标终端。
S13、SgNB-DU向SgNB-CU发送第一响应消息。
在本实施例中，SgNB-DU在接收到第二连接建立请求后，需要判断其是否需要自行分配连接在DU功能实体侧的接口信息。在这其中SgNB-DU判断的方式可能有多种，下面列举几种可能的方式，但并不局限于下述所列举的方式：
在一种可能的方式中，根据第二连接建立请求的具体名称的不同进行判断，比如，当不需要SgNB-DU自行分配时，第二连接建立请求的名称可以被具体为DU增加消息，而当需要SgNB-DU自行分配时，第二连接建立请求的名称可以被具体为DU多连接增加消息。当然，此处仅为示例说明，并不具有限定意义。
在另一种可能的方式中，第二连接建立请求的具体名称不变，当需要SgNB-DU自行分配待建立的连接在DU功能实体侧的接口信息时，第二连接建立请求中携带预设的标识信息，该标识信息用于表示需要SgNB-DU自行分配DU功能实体侧的接口信息，当不需要SgNB-DU自行分配时，则第二连接建立请求中不携带该标识信息。
在又一种可能的方式中，第二连接建立请求的具体名称不变，SgNB-DU仅根据第二连接建立请求中是否携带DU功能实体侧的接口信息来进行判断，比如，当第二连接建立请求中包含DU功能实体侧的接口信息时，则SgNB-DU判断不需要其自行分配DU功能实体侧的接口信息，当第二连接建立请求中不包含DU功能实体侧的接口信息时，则SgNB-DU判断需要其自行分配DU功能实体侧的接口信息。
值得说明的是，本实施例中采用的是SgNB-DU自行分配DU功能实体侧的接口信息的方案。在这种方案下，SgNB-DU根据MgNB的接口信息以及其自行分配的DU功能实体侧的接口信息，建立与MgNB之间的连接，该连接即为用于分流第一DRB中数据的连接。
在此之后或与此同时，SgNB-DU向SgNB-CU发送第一响应消息，该第一响应消息包括第一DRB的标识信息和SgNB-DU自行分配的DU功能实体侧的接口信息。可选的，第一响应消息还可以包括终端的第一标识信息和终端的第二标识信息等。也就是说第一响应消息可以示例性的表述为至少包括第一DRB的标识信息和DU功能实体的接口信息。
S14、SgNB-CU向MgNB发送第二响应消息。
其中，第二响应消息包括第一DRB的标识信息和DU功能实体的接口信息，可选的，第二响应消息还可以包括终端的第一标识信息和终端的第二标识信息。也就是说，第二响应消息示例性的可以表述为至少包括第一DRB的标识信息和DU功能实体的接口信息。
本实施例，通过在MgNB发送的第一连接建立请求中携带终端的第一标识信息、第一DRB的标识信息、目标小区的标识信息，以及MgNB的接口信息，使得SgNB-CU在确定目标小区下的SgNB-DU后，将终端的第二标识信息、第一DRB的标识信息和MgNB的接口信息携带在第二连接建立请求中发送给SgNB-DU，从而使得SgNB-DU根据第二连接建立请求自行分配待建立的连接在DU功能实体侧的接口信息，并建立与MgNB之间的连接，这样MgNB主基站就能够通过该连接将第一DRB中的部分数据直接分流至SgNB-DU上，而无需经过SgNB-CU与SgNB-DU之间的传输时延，从而达到了降低送的数据传输时延的目的。
图6为本申请实施例提供的一种场景示意图，如图6所示，主基站MgNB、辅基站的CU功能实体SgNB-CU、辅基站的DU功能实体SgNB-DU之间的信令交互包括S21-S24。其中，S22-S24的执行方式和有益效果与图3场景中S12-S14的执行方式和有益效果类似，在这里不做赘述。
图7为本申请实施例提供的一种第一连接建立请求的信令内容示意图，如图7所示，在本实施例中S21与图3场景中S11相比，其区别在于第一连接建立请求中包括小区列表，其中，该小区列表中存放有多个小区的标识信息，而S11中所述的目标小区为小区列表中的多个小区中的一个。
另外，在第一连接建立请求中不存在第一DRB的标识信息与目标小区的标识信息的对应关系。而是在小区列表中携带有每个小区对应的测量信息。在这种场景下，MgNB在发送第一连接建立请求之前，先向终端发送小区测量控制信息，之后再根据终端返回的小区标识信息以及小区标识信息对应的测量结果形成小区列表，并将小区列表携带在第一连接建立请求中发送给SgNB-CU。其中，这里涉及的测量结果可能包括参考信号接收质量、参考信号接收功率、信道状态信息以及波束(beam)信息中的一种或多种。
这里需要说明的是，在实际应用中本实施例所涉及的小区列表中可能不只包括小区的标识信息和小区的测量信息，可能还包括其他信息，比如小区的接入信息等，其中小区的接入信息，例如可以是无线接入网侧终端标识、前导码(Preamble)序列号，接入的时频域信息中的一种或多种。
在这种场景下，需要SgNB-CU从小区列表中选择小区作为第一DRB对应的目标小区。其选择策略可以是将对应测量结果符合预设条件的小区作为目标小区。也就是说，上述关于选择目标小区的表述，示例性的可以表述为目标小区的测量信息符合预设条件。比如，目标小区的信号强度为小区列表中信号强度最强的小区。当然此处仅为示例说明，而不是对本申请的具体限定。实际上，在实际应用中，上述预设条件可以根据具体需求具体配置，而不是固定不变的。
本实施例，SgNB-CU自行从第一连接建立请求携带的小区列表中选择目标小区，并在选定目标小区下的SgNB-DU后，将终端的第二标识信息、第一DRB的标识信息和MgNB的接口信息携带在第二连接建立请求中发送给SgNB-DU，从而使得SgNB-DU根据第二连接建立请求自行分配待建立的连接在DU功能实体侧的接口信息，并建立与MgNB之间的连接，这样MgNB主基站就能够通过该连接将第一DRB中的部分数据直接分流至SgNB-DU上，而无需经过SgNB-CU与SgNB-DU之间的传输时延，从而达到了降低送的数据传输时延的目的。
图8为本申请实施例提供的一种场景示意图，如图8所示，主基站MgNB、辅基站的CU功能实体SgNB-CU、辅基站的DU功能实体SgNB-DU之间的信令交互包括S31-S34：
S31、MgNB向SgNB-CU发送第一连接建立请求。
其中，本实施例中S31与图3场景中S11的执行方式和有益效果相同，这里不再赘述。
S32、SgNB-CU向MgNB发送第二响应消息。
在本实施例中与图3所示场景不同的是，在图3所示的场景中待建立的连接在SgNB侧的接口信息(即DU功能实体的接口信息)是由SgNB-DU自行分配的，而在本实施例中SgNB侧的接口信息是由SgNB-CU分配的。
在本实施例的场景下，SgNB-CU在接收到MgNB发送的第一连接请求之后，即在S32中将其自行分配的SgNB侧的接口信息(即DU功能实体的接口信息)携带在第二响应消息中发送给MgNB。这里涉及的第二响应消息与图3实施例中所涉及的第二响应消息在包含的内容上是相同的，而在可选内容上可以不同。
S33、SgNB-CU向SgNB-DU发送第二连接建立请求。
由于本实施例中SgNB侧的接口信息是由SgNB-CU分配的，因此，在本实施例中，S33与图3中S12不同的是：S33中的第二连接建立请求除了包括S12中第二连接建立请求的内容之外，其必要包含的内容还包括SgNB-CU分配的SgNB侧的接口信息(即DU功能实体的接口信息)。也就是说，在本实施例中第二连接建立请求可以示例性的表述为至少包括DU功能实体的接口信息、终端的第二标识信息、第一DRB的标识信息、所述主基站的接口信息。
S34、SgNB-DU向SgNB-CU发送第一响应消息。
本实施例中S34的第一响应消息与图3中S13的第一响应消息不同的是：由于本实施例中SgNB侧的接口信息是由SgNB-CU分配的，因此，在S34的第一响应消息中不包含DU功能实体的接口信息，而包含用于表示所述DU功能实体是否同意建立连接的标识信息。除此之外，S34的第一响应消息与S13的第一响应消息相同。也就是说，在本实施例中，第一响应消息示例性的可表述为至少包括第一DRB的标识信息和第一响应消息。
本实施例，在MgNB向SgNB-CU发送第一连接建立请求之后，通过SgNB-CU分配待建立的连接在SgNB侧的DU功能实体的接口信息，SgNB-DU根据SgNB-CU分配的DU功能实体的接口信息以及MgNB的接口信息，建立与MgNB之间的连接。这样MgNB主基站就能够通过该连接将第一DRB中的部分数据直接分流至SgNB-DU上，而无需经过 SgNB-CU与SgNB-DU之间的传输时延，从而达到了降低送的数据传输时延的目的。
图9为本申请实施例提供的一种场景示意图，如图9所示，主基站MgNB、辅基站的CU功能实体SgNB-CU、辅基站的DU功能实体SgNB-DU之间的信令交互包括S41-S44。其中，S42-S44的执行方式和有益效果与图8场景中S32-S34的执行方式和有益效果类似，在这里不做赘述。
在本实施例中S41与图8场景中S31相比，其区别在于第一连接建立请求中包括小区列表，其中，该小区列表中存放有多个小区的标识信息，而S31中所述的目标小区为小区列表中的多个小区中的一个。
另外，在第一连接建立请求中不存在第一DRB的标识信息与目标小区的标识信息的对应关系。而是在小区列表中携带有每个小区对应的测量信息。比如，在MgNB在发送第一连接建立请求之前，先向终端发送小区测量控制信息，之后再根据终端返回的小区标识信息以及小区标识信息对应的测量结果形成小区列表，并将小区列表携带在第一连接建立请求中发送给SgNB-CU。这里需要说明的是，在实际应用中本实施例所涉及的小区列表中可能不只包括小区的标识信息和小区的测量信息，可能还包括其他信息，比如小区的接入信息等，其中小区的接入信息，例如可以包括无线接入网侧终端标识、前导码(Preamble)序列号，接入的时频域信息等。
在这种场景下，需要SgNB-CU从小区列表中选择小区作为第一DRB对应的目标小区。其选择策略可以是将对应测量结果符合预设条件的小区作为目标小区。也就是说，上述关于选择目标小区的表述，示例性的可以表述为目标小区的测量信息符合预设条件。比如，目标小区的信号强度为小区列表中信号强度最强的小区。当然此处仅为示例说明，而不是对本申请的具体限定。实际上，在实际应用中，上述预设条件可以根据具体需求具体配置，而不是固定不变的。
本实施例，SgNB-CU自行从第一连接建立请求携带的小区列表中选择目标小区，并将终端的第二标识信息、第一DRB的标识信息、MgNB的接口信息以及其自行分配的DU功能实体侧的接口信息携带在第二连接建立请求中发送给SgNB-DU，从而使得SgNB-DU建立与MgNB之间的连接，这样MgNB主基站就能够通过该连接将第一DRB中的部分数据直接分流至SgNB-DU上，而无需经过SgNB-CU与SgNB-DU之间的传输时延，从而达到了降低送的数据传输时延的目的。
图10为本申请实施例提供的一种场景示意图，在该场景中MgNB决策更改上述图3-图9中任一场景所建立的连接，姑且将已与MgNB建立连接的SgNB-DU称为第一SgNB-DU，将待与MgNB建立连接的SgNB-DU称为第二SgNB-DU。如图10所述，主基站MgNB、辅基站的CU功能实体SgNB-CU、第一SgNB-DU、第二SgNB-DU之间的信令交互包括S51-S54。
S51、MgNB向SgNB-CU发送修改请求消息。
实际应用中，MgNB更改当前连接的情况可能包括如下几种：
在一种可能的情况中，MgNB决策更改当前连接在MgNB侧的接口信息，在这种情况下，修改请求消息至少包括第一DRB的标识信息，更换后的MgNB侧的接口信息，可 选的，修改请求消息还可以包括终端在MgNB侧的接口标识和终端在SgNB侧的接口标识。
在一种可能的情况中，MgNB决策更改SgNB侧的目标小区，在这种情况下，MgNB在发送修改请求消息之前需要先接收终端发送的SgNB侧的小区测量信息，或者SgNB侧发送的负载信息，并根据该些信息重新选定目标小区。在选定目标小区之后，至少将第一DRB的标识信息和重新选定的目标小区的标识信息携带在修改请求消息发送给SgNB-CU。可选的，MgNB还可以将终端在MgNB侧的接口标识和终端在SgNB侧的接口标识携带在修改请求消息中发送给SgNB-CU。
S52、SgNB-CU给MgNB发送上述修改请求的确认消息。
针对S51中所述的第一中可能的情况，该确认消息中至少包括用于表示是否接受修改的信息以及第一DRB的标识信息。可选的，还可以包括终端在MgNB侧的接口标识和终端在SgNB侧的接口标识。
针对S51中所述的第二中可能的情况，该确认消息中至少包括第一DRB的标识信息以及重新选定的目标小区中DU功能实体的接口信息。可选的，还可以包括终端在MgNB侧的接口标识、终端在SgNB侧的接口标识，以及重新选定的目标小区的接入信息。
这里需要说明的是，本实施例中所涉及的DU功能实体的接口信息其可以是由SgNB-CU分配的，也可以是由重新选定的目标小区中的第二SgNB-DU分配的，不同分配方式的执行方法与前述实施例类似在这里不再赘述。
S53、SgNB-CU给第一SgNB-DU发送释放连接的通知消息，给第二SgNB-DU发送第三连接建立请求。
其中，第一SgNB-DU和第二SgNB-DU可能是同一个DU功能实体，也可能是不同的功能实体。
当第一SgNB-DU和第二SgNB-DU是同一个DU功能实体，即重新选定的目标小区和旧目标小区同属于一个DU功能实体时，此时，上述通知消息和第三连接建立请求可以作为各自独立的消息，同时或依次发送给该DU功能实体，也可以将通知消息和第三连接建立请求合并为一个新的请求消息发送给该DU功能实体。
当第一SgNB-DU和第二SgNB-DU不是同一个DU功能实体，则将通知消息和第三连接建立消息发送分别给第一SgNB-DU和第二SgNB-DU。
其中，上述通知消息用于通知第一SgNB-DU释放当前第一DRB对应的连接，并且该通知消息中还可能包含数据转发的连接地址，主要用于第一SgNB-DU将未收到终端确认或未来得及发送的数据包回传给MgNB。第三连接建立请求用于请求第二SgNB-DU建立与MgNB的连接。本实施例中第三连接建立请求中的内容与前述实施例中第二连接建立请求的内容相同，在这里不再赘述。
S54：第一SgNB-DU给SgNB-CU发送释放连接的确认消息。
S55：第二SgNB-DU给SgNB-CU发送连接建立的确认消息。
其中，S54与S55之间不具有顺序。
另外，值得说明的是，在实际应用中修改连接的决策者也可以是SgNB，其具体的执行方法与图10所示场景下的执行方法类似，在这里不再赘述。
本实施例提供了由MgNB决策改变已有连接的方案，该方案能够使得多连接的建立和改变更加灵活。另外，能够始终确保MgNB与小区情况或负载情况较好的DU功能实体建立连接。从而，使得多连接在通信质量上具有较好的保障。
这里需要说明的是，上述实施例仅是从对DRB分流的角度来对本申请的技术方案进行的阐述，然而，实际应用中，本申请的技术方案还可以用于对信令无线承载(signalling radio bearer，简称SRB)进行分流。其执行过程与有益效果类似，在这里不再赘述。
图11为本申请实施例提供的一种建立连接的装置10的结构示意图，该装置可以被具体为辅基站中的CU功能实体，如图11所示，该装置包括：接收器101、交换电路102和发送器103，其中，交换电路102在实际应用中可以被具体为交换机或交换板等具有交换电路的实体设备。接收器101用于接收主设备的第一连接建立请求，第一连接建立请求至少包括终端的第一标识信息、第一数据无线承载DRB的标识信息、目标小区的标识信息、主设备的接口信息；交换电路102用于向分布式节点DU功能实体发送第二连接建立请求，第二连接建立请求至少包括终端的第二标识信息、第一DRB的标识信息、主设备的接口信息，其中，DU功能实体与目标小区有关联；交换电路102用于接收DU功能实体的第一响应消息，第一响应消息至少包括第一DRB的标识信息和DU功能实体的接口信息；发送器103用于向主设备发送第二响应消息，第二响应消息至少包括第一DRB的标识信息和DU功能实体的接口信息。在本实施例中，主设备的接口信息至少包括主设备的接口标识和接口传输地址。
在本实施例中，DU功能实体的接口信息至少包括DU功能实体的接口标识和接口传输地址。
在本实施例中，第二连接建立请求还可以包括目标小区的标识信息。
在本实施例中，在第一连接建立请求中第一DRB的标识信息与目标小区的标识信息存在对应关系。
在本实施例中，第一连接建立请求中包括多个小区的标识信息，目标小区为所述多个小区中的一个。
在本实施例中，第一连接建立请求中包括多个小区中每个小区的测量信息，目标小区的测量信息符合预设条件。
作为一种可选的设计，装置10可以包括处理器和存储器，其中，存储器用于存储实现图3或图6所示的技术方案的程序代码，处理器用于运行存储器所存储的程序代码。
图11所示的装置能够执行图3或图6所示场景下的技术方案，其执行方式和有益效果类似在这里不再赘述。
图12为本申请实施例提供的一种建立连接的装置20的结构示意图，本实施例中该装置可以被具体为辅基站中的CU功能实体，如图12所示，该装置包括接收器201、交换电路202和发送器203，其中，交换电路202在实际应用中可以被具体为交换机或交换板等具有交换电路的实体设备。接收器201用于接收主设备的第一连接建立请 求，第一连接建立请求至少包括终端的第一标识信息、第一数据无线承载DRB的标识信息、目标小区的标识信息、主设备的接口信息；发送器203用于向主设备发送第二响应消息，第二响应消息至少包括第一DRB的标识信息和分布式节点DU功能实体的接口信息，其中，DU功能实体与所述目标小区有关联；交换电路202用于向DU功能实体发送第二连接建立请求，第二连接建立请求至少包括DU功能实体的接口信息、终端的第二标识信息、第一DRB的标识信息、主设备的接口信息；交换电路用于接收DU功能实体的第一响应消息，第一响应消息至少包括第一DRB的标识信息和用于表示DU功能实体是否同意建立连接的标识信息。
在本实施例中，主设备的接口信息至少包括主设备的接口标识和接口传输地址。
在本实施例中，DU功能实体的接口信息至少包括DU功能实体的接口标识和接口传输地址。
在本实施例中，第二连接建立请求还可以包括目标小区的标识信息。
在本实施例中，在第一连接建立请求中第一DRB的标识信息与目标小区的标识信息存在对应关系。
在本实施例中，第一连接建立请求中包括多个小区的标识信息，目标小区为所述多个小区中的一个。
在本实施例中，第一连接建立请求中包括多个小区中每个小区的测量信息，目标小区的测量信息符合预设条件。
作为一种可选的设计，装置20可以包括处理器和存储器，其中，存储器用于存储实现图8或图9所示的技术方案的程序代码，处理器用于运行存储器所存储的程序代码。
图12所示的装置能够执行图8或图9所示场景下的技术方案，其执行方式和有益效果类似在这里不再赘述。
图13为本申请实施例提供的一种建立连接的装置30的结构示意图，本实施例中该装置可以被具体为辅基站中的DU功能实体，如图12所示，该装置包括交换电路301，该交换电路在实际应用中可以被具体为交换机或交换板等具有交换电路的实体设备。该交换电路301用于接收CU功能实体发送的第二连接建立请求，第二连接建立请求至少包括终端的第二标识信息、第一DRB的标识信息、主设备的接口信息；该交换电路用于向CU功能实体发送第一响应消息，第一响应消息至少包括第一DRB的标识信息、DU功能实体的接口信息。
本实施例中，第二连接建立请求中还可以包括目标小区的标识信息，目标小区与DU功能实体有关联。
作为一种可选的设计，装置30可以包括处理器和存储器，其中，存储器用于存储实现图3或图6所示的技术方案的程序代码，处理器用于运行存储器所存储的程序代码。
图13所示的装置能够执行图3或图6所示场景下的技术方案，其执行方式和有益效果类似在这里不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过 其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述软件功能部分可以存储在存储单元中。所述存储单元包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的部分步骤。所述存储单元包括：一个或多个存储器，如只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)，电可擦写可编程只读存储器(EEPROM)，等等。所述存储单元可以独立存在，也可以和处理器集成在一起。
本领域技术人员可以清楚地了解到，为描述的方便和简洁，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将装置的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。上述描述的装置的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
本领域普通技术人员可以理解：本文中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围。
本领域普通技术人员可以理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、 硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
最后应说明的是：以上各实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述各实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (32)

  1. 一种建立连接的方法，其特征在于，包括：
    中央节点CU功能实体接收主设备的第一连接建立请求，所述第一连接建立请求至少包括终端的第一标识信息、第一数据无线承载DRB的标识信息、目标小区的标识信息、主设备的接口信息；
    所述CU功能实体向分布式节点DU功能实体发送第二连接建立请求，所述第二连接建立请求至少包括所述终端的第二标识信息、所述第一DRB的标识信息、所述主设备的接口信息，其中，所述DU功能实体与所述目标小区有关联；
    所述CU功能实体接收所述DU功能实体的第一响应消息，所述第一响应消息至少包括所述第一DRB的标识信息和所述DU功能实体的接口信息；
    所述CU功能实体向所述主设备发送第二响应消息，所述第二响应消息至少包括所述第一DRB的标识信息和所述DU功能实体的接口信息。
  2. 根据权利要求1所述的方法，其特征在于，所述主设备的接口信息至少包括：所述主设备的接口标识和接口传输地址。
  3. 根据权利要求2所述的方法，其特征在于，所述DU功能实体的接口信息至少包括所述DU功能实体的接口标识和接口传输地址。
  4. 根据权利要求1所述的方法，其特征在于，所述第二连接建立请求包括所述目标小区的标识信息。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，在所述第一连接建立请求中所述第一DRB的标识信息与所述目标小区的标识信息存在对应关系。
  6. 根据权利要求1-4中任一项所述的方法，其特征在于，所述第一连接建立请求中包括多个小区的标识信息，所述目标小区为所述多个小区中的一个。
  7. 根据权利要求6所述的方法，其特征在于，所述第一连接建立请求中包括所述多个小区中每个小区的测量信息，所述目标小区的测量信息符合预设条件。
  8. 一种建立连接的方法，其特征在于，包括：
    中央节点CU功能实体接收主设备的第一连接建立请求，所述第一连接建立请求至少包括终端的第一标识信息、第一数据无线承载DRB的标识信息、目标小区的标识信息、主设备的接口信息；
    所述CU功能实体向所述主设备发送第二响应消息，所述第二响应消息至少包括所述第一DRB的标识信息和分布式节点DU功能实体的接口信息，其中，所述DU功能实体与所述目标小区有关联；
    所述CU功能实体向所述DU功能实体发送第二连接建立请求，所述第二连接建立请求至少包括所述DU功能实体的接口信息、所述终端的第二标识信息、所述第一DRB的标识信息、所述主设备的接口信息；
    所述CU功能实体接收所述DU功能实体的第一响应消息，所述第一响应消息至少包括所述第一DRB的标识信息和用于表示所述DU功能实体是否同意建立连接的标识信息。
  9. 根据权利要求8所述的方法，其特征在于，所述主设备的接口信息至少包括：所述主设备的接口标识和接口传输地址。
  10. 根据权利要求9所述的方法，其特征在于，所述DU功能实体的接口信息至少包括所述DU功能实体的接口标识和接口传输地址。
  11. 根据权利要求8所述的方法，其特征在于，所述第二连接建立请求包括所述目标小区的标识信息。
  12. 根据权利要求8-11中任一项所述的方法，其特征在于，在所述第一连接建立请求中所述第一DRB的标识信息与所述目标小区的标识信息存在对应关系。
  13. 根据权利要求8-11中任一项所述的方法，其特征在于，所述第一连接建立请求中包括多个小区的标识信息，所述目标小区为所述多个小区中的一个。
  14. 根据权利要求13所述的方法，其特征在于，所述第一连接建立请求中包括所述多个小区中每个小区的测量信息，所述目标小区的测量信息符合预设条件。
  15. 一种建立连接的方法，其特征在于，包括：
    DU功能实体接收CU功能实体发送的第二连接建立请求，所述第二连接建立请求至少包括终端的第二标识信息、第一DRB的标识信息、主基站的接口信息；
    所述DU功能实体向所述CU功能实体发送第一响应消息，所述第一响应消息至少包括所述第一DRB的标识信息、所述DU功能实体的接口信息。
  16. 根据权利要求15所述的方法，其特征在于，所述第二连接建立请求中包括目标小区的标识信息，所述目标小区与所述DU功能实体有关联。
  17. 一种建立连接的装置，其特征在于，包括：
    接收器、交换电路和发送器，其中，
    所述接收器用于接收主设备的第一连接建立请求，所述第一连接建立请求至少包括终端的第一标识信息、第一数据无线承载DRB的标识信息、目标小区的标识信息、主设备的接口信息；
    所述交换电路用于向分布式节点DU功能实体发送第二连接建立请求，所述第二连接建立请求至少包括所述终端的第二标识信息、所述第一DRB的标识信息、所述主设备的接口信息，其中，所述DU功能实体与所述目标小区有关联；
    所述交换电路用于接收所述DU功能实体的第一响应消息，所述第一响应消息至少包括所述第一DRB的标识信息和所述DU功能实体的接口信息；
    所述发送器用于向所述主设备发送第二响应消息，所述第二响应消息至少包括所述第一DRB的标识信息和所述DU功能实体的接口信息。
  18. 根据权利要求17所述的装置，其特征在于，所述主设备的接口信息至少包括：所述主设备的接口标识和接口传输地址。
  19. 根据权利要求18所述的装置，其特征在于，所述DU功能实体的接口信息至少包括所述DU功能实体的接口标识和接口传输地址。
  20. 根据权利要求17所述的装置，其特征在于，所述第二连接建立请求包括所述目标小区的标识信息。
  21. 根据权利要求17-20中任一项所述的装置，其特征在于，在所述第一连接建立请求中所述第一DRB的标识信息与所述目标小区的标识信息存在对应关系。
  22. 根据权利要求17-20中任一项所述的装置，其特征在于，所述第一连接建立请求中包括多个小区的标识信息，所述目标小区为所述多个小区中的一个。
  23. 根据权利要求22所述的装置，其特征在于，所述第一连接建立请求中包括所述多个小区中每个小区的测量信息，所述目标小区的测量信息符合预设条件。
  24. 一种建立连接的装置，其特征在于，包括：
    接收器、交换电路和发送器，其中，
    所述接收器用于接收主设备的第一连接建立请求，所述第一连接建立请求至少包括终端的第一标识信息、第一数据无线承载DRB的标识信息、目标小区的标识信息、主设备的接口信息；
    所述发送器用于向所述主设备发送第二响应消息，所述第二响应消息至少包括所述第一DRB的标识信息和分布式节点DU功能实体的接口信息，其中，所述DU功能实体与所述目标小区有关联；
    所述交换电路用于向所述DU功能实体发送第二连接建立请求，所述第二连接建立请求至少包括所述DU功能实体的接口信息、所述终端的第二标识信息、所述第一DRB的标识信息、所述主设备的接口信息；
    所述交换电路用于接收所述DU功能实体的第一响应消息，所述第一响应消息至少包括所述第一DRB的标识信息和用于表示所述DU功能实体是否同意建立连接的标识信息。
  25. 根据权利要求24所述的装置，其特征在于，所述主设备的接口信息至少包括：所述主设备的接口标识和接口传输地址。
  26. 根据权利要求24所述的装置，其特征在于，所述DU功能实体的接口信息至少包括所述DU功能实体的接口标识和接口传输地址。
  27. 根据权利要求24所述的装置，其特征在于，所述第二连接建立请求包括所述目标小区的标识信息。
  28. 根据权利要求24-27中任一项所述的装置，其特征在于，在所述第一连接建立请求中所述第一DRB的标识信息与所述目标小区的标识信息存在对应关系。
  29. 根据权利要求24-27中任一项所述的装置，其特征在于，所述第一连接建立请求中包括多个小区的标识信息，所述目标小区为所述多个小区中的一个。
  30. 根据权利要求29所述的装置，其特征在于，所述第一连接建立请求中包括所述多个小区中每个小区的测量信息，所述目标小区的测量信息符合预设条件。
  31. 一种建立连接的装置，其特征在于，包括：
    交换电路；
    所述交换电路用于接收CU功能实体发送的第二连接建立请求，所述第二连接建立请求至少包括终端的第二标识信息、第一DRB的标识信息、主设备的接口信息；
    所述交换电路用于向所述CU功能实体发送第一响应消息，所述第一响应消息至少包括所述第一DRB的标识信息、所述DU功能实体的接口信息。
  32. 根据权利要求31所述的装置，其特征在于，所述第二连接建立请求中包括目标小区的标识信息，所述目标小区与所述DU功能实体有关联。
PCT/CN2018/080100 2017-03-24 2018-03-23 建立连接的方法和装置 WO2018171696A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2019546174A JP2020508613A (ja) 2017-03-24 2018-03-23 接続確立方法および装置
KR1020197023490A KR20190103357A (ko) 2017-03-24 2018-03-23 연결 설정 방법 및 장치
BR112019018374A BR112019018374A2 (pt) 2017-03-24 2018-03-23 métodos e aparelhos de estabelecimento de conexão
EP18771948.9A EP3565372B1 (en) 2017-03-24 2018-03-23 Connection establishment method and apparatus
US16/567,385 US11082897B2 (en) 2017-03-24 2019-09-11 Connection establishment method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710184022.1 2017-03-24
CN201710184022.1A CN108924958B (zh) 2017-03-24 2017-03-24 建立连接的方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/567,385 Continuation US11082897B2 (en) 2017-03-24 2019-09-11 Connection establishment method and apparatus

Publications (1)

Publication Number Publication Date
WO2018171696A1 true WO2018171696A1 (zh) 2018-09-27

Family

ID=63584945

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/080100 WO2018171696A1 (zh) 2017-03-24 2018-03-23 建立连接的方法和装置

Country Status (7)

Country Link
US (1) US11082897B2 (zh)
EP (1) EP3565372B1 (zh)
JP (1) JP2020508613A (zh)
KR (1) KR20190103357A (zh)
CN (1) CN108924958B (zh)
BR (1) BR112019018374A2 (zh)
WO (1) WO2018171696A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI755657B (zh) * 2018-12-06 2022-02-21 財團法人工業技術研究院 集中管理節點、分散式節點以及封包延遲控制方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统
WO2017034269A1 (ko) * 2015-08-21 2017-03-02 삼성전자 주식회사 무선 통신 시스템에서 데이터 송수신 방법 및 장치

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8843112B2 (en) * 2010-07-02 2014-09-23 Blackberry Limited Method and system for data session establishment
WO2014040259A1 (zh) * 2012-09-13 2014-03-20 华为技术有限公司 一种rrc连接重建方法、设备和网络系统
KR102106134B1 (ko) * 2015-05-15 2020-05-04 주식회사 케이티 단말의 무선연결 구성방법 및 그 장치
KR102564318B1 (ko) * 2015-08-21 2023-08-07 삼성전자주식회사 무선 통신 시스템에서 다중 연결을 이용한 핸드오버를 지원하는 장치 및 방법
WO2018236867A2 (en) * 2017-06-19 2018-12-27 Intel Corporation CONTROL PANEL AND USER PLANE SEPARATION IN NEW RADIO (NR) SYSTEMS

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017034269A1 (ko) * 2015-08-21 2017-03-02 삼성전자 주식회사 무선 통신 시스템에서 데이터 송수신 방법 및 장치
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CATT ET AL.: "Considerations on RAN Function Split between CU and DU", R3-162863. 3GPP TSG RAN WG3 MEETING #94, 18 November 2016 (2016-11-18), XP051178962 *
See also references of EP3565372A4
ZTE ET AL.: "Discussion on the Higher Layer CU /DU Function Splits", R3-170595. 3GPP TSG RAN WG3 MEETING #95., 17 February 2017 (2017-02-17), XP051213175 *
ZTE: "Consideration on RRC Message Transmission", R3-170586. 3GPP TSG RAN WG3 MEETING #95, 17 February 2017 (2017-02-17), XP051213167 *

Also Published As

Publication number Publication date
US11082897B2 (en) 2021-08-03
US20200008114A1 (en) 2020-01-02
BR112019018374A2 (pt) 2020-04-07
KR20190103357A (ko) 2019-09-04
CN108924958A (zh) 2018-11-30
CN108924958B (zh) 2023-05-16
EP3565372B1 (en) 2021-02-03
JP2020508613A (ja) 2020-03-19
EP3565372A1 (en) 2019-11-06
EP3565372A4 (en) 2020-02-12

Similar Documents

Publication Publication Date Title
US10727925B2 (en) Method and apparatus for supporting movement of user equipment in wireless communications
US11224079B2 (en) Method and apparatus for operating wireless communication system having separated mobility management and session management
US11838958B2 (en) UE access method and apparatus
KR102452940B1 (ko) 무선 통신 시스템에서 이동성 향상을 위한 방법 및 장치
US11470658B2 (en) Method for data offloading, method for DRB identifier allocating, method for resource releasing, and device
US20180279390A1 (en) Method and device for establishing an auxiliary signaling link, base station and user equipment
US11229077B2 (en) Data transmission method, access network device, and terminal
US11172491B2 (en) Data transmission method, apparatus and system, network element, storage medium and processor
US20200229258A1 (en) Method and device for network access
KR102645345B1 (ko) 네트워크 액세스를 위한 방법 및 장치
CN111328140A (zh) 侧链通信方法和装置
WO2022067818A1 (zh) 一种数据传输方法及装置
US20140140286A1 (en) Method of direct communication by terminal
CN115699816A (zh) 用于在双连接下进行侧行链路中继通信的方法
WO2018171696A1 (zh) 建立连接的方法和装置
CN112449384B (zh) 数据处理方法、装置和系统
WO2019096117A1 (zh) 消息、策略发送方法及装置，存储介质，处理器
WO2021097678A1 (zh) 一种接入回传控制方法及装置
WO2023274127A1 (zh) 路由选择、重路由及路由配置方法、iab节点和cu节点
WO2024077600A1 (en) Systems and methods for device-to-device communications
WO2024031698A1 (en) Systems and methods for authorization configuration in device-to-device communications
WO2024012066A1 (zh) 一种通信连接建立方法、装置及可读存储介质
WO2024026625A1 (en) Multi-path communications for user equipment in centralized unit and distributed unit split architecture
WO2024055322A1 (en) Systems and methods for device-to-device communications
CN116567606A (zh) 通信方法及相关装置

Legal Events

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

Ref document number: 18771948

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20197023490

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018771948

Country of ref document: EP

Effective date: 20190729

Ref document number: 2019546174

Country of ref document: JP

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112019018374

Country of ref document: BR

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112019018374

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20190904