WO2019129197A1 - 一种通信方法，设备及其系统 - Google Patents

一种通信方法，设备及其系统 Download PDF

Info

Publication number
WO2019129197A1
WO2019129197A1 PCT/CN2018/124826 CN2018124826W WO2019129197A1 WO 2019129197 A1 WO2019129197 A1 WO 2019129197A1 CN 2018124826 W CN2018124826 W CN 2018124826W WO 2019129197 A1 WO2019129197 A1 WO 2019129197A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration information
cell group
indication
unit
distributed unit
Prior art date
Application number
PCT/CN2018/124826
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 KR1020207021487A priority Critical patent/KR102357070B1/ko
Priority to EP18896533.9A priority patent/EP3734908A4/en
Priority to JP2020536218A priority patent/JP7150854B2/ja
Priority to BR112020012890A priority patent/BR112020012890A8/pt
Publication of WO2019129197A1 publication Critical patent/WO2019129197A1/zh
Priority to US16/912,122 priority patent/US20200329365A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/27—Control channels or signalling for resource management between access points
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the present application relates to the field of communications, and more specifically to a communication method, device, system thereof and the like.
  • the base station In a next-generation mobile communication system, such as the 5th generation mobile communication technology (5G) system, the base station is called a gNB or an ng-eNB, wherein the ng-eNB is derived from long term evolution (long term)
  • the evolved, LTE) base station (LTE eNB) subsequent evolved base station for convenience of description, the gNB is used herein to represent the base station.
  • the system 100 shown in FIG. 1 is a schematic block diagram of a 5G system in which ng-eNB and ng-eNB are between gNB and gNB in a next generation radio access network (NG-RAN). Between, and between the gNB and the ng-eNB are interconnected through the Xn interface.
  • NG-RAN next generation radio access network
  • the gNB and the 5G core network (5G core, 5GC) devices are interconnected through the NG interface, and the ng-eNB and the 5GC device are interconnected through the NG interface.
  • the 5GC device may be an access and mobility management function (AMF) or a user plane function (UPF).
  • AMF access and mobility management function
  • UPF user plane function
  • the AMF is mainly responsible for access management functions
  • the UPF is mainly responsible for the session ( Session) management aspects.
  • the base station usually includes a radio resource control (RRC) layer, a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, and a radio link control ( A radio link control (RLC) layer, a media access control (MAC) layer, and a logical layer (PHY) layer such as a physical layer (PHY).
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC media access control
  • PHY logical layer
  • Next generation base stations e.g., gNBs
  • 2 is a schematic block diagram of a 5G system including a 5GC and an NG-RAN.
  • the base station gNB can be a centralized unit (CU) and a distributed unit (DU).
  • the CU and DU architecture can be understood as splitting the functions of the base stations in the traditional access network.
  • Some functions of the traditional base station are deployed in the CU, and other functions are deployed in the DU. Multiple DUs can share one CU to save costs. It is easy to expand the network, and the information exchange between the CU and the DU through the F1 interface. For a gBN composed of a CU and a DU, it is a base station for other external network elements.
  • the centralized unit CU can also be divided into a CU control plane (CU-CP) and a CU user plane (CU user). Plane, CU-CP).
  • the CU-CP is responsible for the control plane function, mainly including the RRC and PDCP control plane parts (PDCP-C).
  • the PDCP-C is mainly responsible for the encryption and decryption of the control plane data, integrity protection, and data transmission; the CU-UP is responsible for the user.
  • the surface function mainly includes SDAP and PDCP-U.
  • the SDAP is mainly responsible for processing the data of the core network and mapping the flow to the radio bearer.
  • the PDCP-U is mainly responsible for encryption and decryption of the data plane, integrity protection, and header compression. , serial number maintenance, and data transfer.
  • the CU-CP and the CU-UP are connected through the E1 interface, the CU-CP represents the gNB connected to the core network through the Ng interface, the CU-CP is connected to the DU through the F1-C (F1 control plane) interface, and the CU-UP passes the F1- U (F1 user plane) interface and DU connection.
  • F1-C F1 control plane
  • the CU-UP passes the F1- U (F1 user plane) interface and DU connection.
  • Yet another design is that both PDCP-C and PDCP-C are at CU-UP and RRC is at CU-CP (not shown in Figure 3).
  • a dual connectivity (DC) scenario when a base station with a CU and a DU architecture is used as a secondary node (SN), the DU cannot correctly parse the secondary cell group (SCG) sent by the CU to the DU.
  • SCG secondary cell group
  • the present application provides a communication method, a device, a system thereof, and the like, to solve the problem in the background that when a base station having a CU and a DU architecture is used as a secondary base station, the DU cannot correctly parse the configuration information of the secondary cell group that the CU sends to the DU. The problem that caused the system to go wrong.
  • an embodiment of the present application provides a communication method, where the communication method runs in a communication system, where the communication system includes a centralized unit and a distributed unit. When the communication system is running, the following operations are performed:
  • the distributed unit DU sends the configuration information and/or the first indication of the cell group to the centralized unit CU, where the configuration information of the cell group may be configuration information of the fully configured cell group, and the first indication may be used to notify the
  • the centralized unit CU performs full configuration in the distributed unit DU, or the distributed unit DU can trigger the centralized unit CU to generate full configuration related information by using the first indication, for example, the CU receives the first After an indication, configuration information of the fully configured radio bearer is generated.
  • the distributed unit DU and the centralized unit CU form a secondary base station in a multi-connection scenario, and the distributed unit sends a second indication sent by the CU to the terminal device, where the second indication It can be used to notify the terminal device to perform a secondary base station configuration update operation.
  • the distributed unit DU sends a control message from the centralized unit CU to the terminal device, for example, the control message may be a radio resource control reconfiguration message, and the radio resource controls the reconfiguration message.
  • the configuration information of the fully configured radio bearer and/or the configuration information of the fully configured radio group is included, where the configuration information of the fully configured radio bearer includes configuration information of the service data adaptation protocol layer and a packet data convergence layer protocol. At least one of the configuration information of the layer; the configuration information of the fully configured radio bearer is generated by the centralized unit CU based on the first indication; and the configuration information of the fully configured cell group includes a radio link control layer. At least one of configuration information, configuration information of the medium access control layer, and configuration information of the physical layer.
  • the configuration information of the fully configured cell group and the first indication are sent in a message defined on a communication interface between the distributed unit and the centralized unit, or the fully configured The configuration information of the cell group and the first indication are sent in an uplink data packet between the distributed unit and the centralized unit.
  • the distributed unit DU sends the configuration information and/or the first indication of the fully configured cell group to the centralized unit CU, and needs to satisfy at least one of the following:
  • the distributed unit DU receives the reference configuration information of the secondary cell group SCG sent by the centralized unit, but the distributed unit DU cannot correctly parse or understand the secondary cell group SCG in the reference configuration information of the secondary cell group SCG.
  • Configuration information
  • the distributed unit DU (optionally, within a predetermined time) does not receive the configuration information of the secondary cell group SCG from the centralized unit; or the distributed unit DU receives the auxiliary from the centralized unit Reference configuration information of the cell group SCG, but the reference configuration information of the secondary cell group SCG does not include configuration information of all or part of the secondary cell group SCG;
  • the distributed unit DU receives an indication from the centralized unit, the indication being used to notify the distributed unit DU that a full configuration needs to be performed.
  • the design may be applicable to when the CU sends the reference configuration information of the SCG to the DU, and the DU cannot correctly identify the configuration information of the SCG, the DU may determine the configuration information of the fully configured cell group (such as CellGroupConfig), DU.
  • the CU is notified by sending the indication information, so that the CU also generates configuration information (for example, radioBearerConfig) based on the fully configured radio bearer, which also helps solve the problem that the secondary base station cannot understand the configuration information of the source secondary base station and causes the system to go wrong.
  • the distributed unit has or only includes: a radio link control layer, a medium access control layer, and a physical layer; the centralized unit has or includes only: a radio resource control layer, and service data adaptation. Protocol layer, and packet data aggregation layer protocol layer.
  • the communication method provided by the foregoing first aspect and the various feasible designs thereof are provided to help solve the problem that the DU cannot correctly parse the configuration information of the secondary cell group sent by the CU to the DU, thereby causing a system error.
  • the present application provides a communication device, including: at least one processor and a communication interface, the communication interface is used for information interaction between the communication device and other communication devices, when the program instruction is in the at least one process When executed in the device, the communication device is enabled to implement the first aspect and its various optional designs in a centralized unit or a distributed unit.
  • the present application provides a computer program product having program instructions that, when executed directly or indirectly, cause the first aspect and its various alternative designs to be in a centralized unit Or the functionality on the distributed unit is implemented.
  • the present application provides a computer program storage medium having program instructions that, when executed directly or indirectly, cause the first aspect and various alternative designs thereof to be concentrated The functions on the unit or distributed unit are implemented.
  • the present application provides a chip system including at least one processor, when program instructions are executed in the at least one processor, such that the first aspect and various alternative designs thereof are concentrated The functions on the unit or distributed unit are implemented.
  • the present application provides a communication system comprising the communication device of the second aspect.
  • FIG. 1 is a schematic block diagram of a 5G system provided by an embodiment of the present application.
  • FIG. 2 is a schematic block diagram of a 5G system provided by an embodiment of the present application.
  • FIG. 3 is a schematic block diagram of a 5G system according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic diagram of a communication system and method according to an embodiment of the present application.
  • FIG. 5 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • first, “second” and the like in the present application are only intended to distinguish different objects, and “first” and “second” do not limit the actual order or function of the objects to which they are modified.
  • first and “second” in “first indication” and “second indication” are merely meant to distinguish that the two are different indications, and “first” and “second” themselves are not The actual sequence or function is limited.
  • the expressions “exemplary”, “example”, “such as”, “optional design” or “a design” appearing in the present application are merely used to denote examples, illustrations or illustrations. Any embodiment or design described in the application as “exemplary”, “example”, “such as”, “optional design” or “a design” should not be construed as The design is more preferred or more advantageous.
  • upstream and downstream appearing in this application are used to describe the direction of data/information transmission in a specific scenario.
  • uplink generally refers to the direction in which data/information is transmitted from the terminal device to the network side, or The direction in which the distributed unit transmits to the centralized unit
  • downstream generally refers to the direction in which data/information is transmitted from the network side to the terminal device, or the direction in which the centralized unit transmits to the distributed unit.
  • upstream and Downlink is only used to describe the transmission direction of data/information, and the specific starting and ending devices of the data/information transmission are not limited.
  • the terminal device may include the following forms: user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal , a wireless communication device, a user agent, or a user device.
  • the terminal device can be a station in the WLAN (STAION, ST), which can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, and a personal digital processing.
  • WLAN STAION, ST
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, and next-generation communication system, for example, a terminal device in a 5G network or Terminal equipment in the future evolution of the Public Land Mobile Network (PLMN) network.
  • PLMN Public Land Mobile Network
  • the terminal device can also be a wearable device.
  • a wearable device which can also be called a wearable smart device, is a general term for applying wearable technology to intelligently design and wear wearable devices such as glasses, gloves, watches, clothing, and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories.
  • the terminal device can also be a terminal device in the Internet of Things (IoT) system.
  • IoT Internet of Things
  • Its main technical feature is to connect items to the network through communication technology, thereby realizing mutual interaction. Even, the intelligent network of physical interconnection.
  • the terminal device uses the UE as an example to describe the solution in the embodiment, but it can be understood that the terminal device in the embodiment of the present application is not limited to the UE.
  • the UE performs DC at the source base station, and the UE performs the handover.
  • the target base station also performs the DC
  • the source-side base station transmits the configuration information related to the source base station to the target-side base station in the handover process, and the master node (MN) in the target-side base station can correctly parse the master in the target base station.
  • MN master node
  • the configuration information of the cell group (MCG), the target MN sends the secondary cell group (SCG) configuration information to the secondary node (SN) in the target side base station, if the target SN If the configuration information of the SCG cannot be correctly parsed, the target SN notifies that the target MN will adopt the full configuration of the SCG by sending the indication information, and the target MN receives the indication of the target SN, and the control message sent by the target MN to the UE (
  • the RRC reconfiguration message of the LTE system includes a full configuration indication, where the full configuration indication may specifically be an en-DC-release indication or an scg-ConfigReleaseNR indication.
  • the CU sets the reference configuration information of the secondary cell group (SCG) provided by the primary base station (for example, SCG-ConfigInfo). Send to DU.
  • the reference configuration information of the SCG includes at least one of the following: configuration information of a master cell group (MCG), configuration information of the SCG, and capability information of the UE.
  • the configuration information of the MCG includes at least one of the following: radioResourceConfigDedMCG defined in the long term evolution (LTE) system protocol, sCellToAddModListMCG defined in the LTE protocol, and mcg defined in the 5G new radio (NR) protocol. - RB-Config;
  • the configuration information of the SCG includes at least one of the following: scg-RadioConfig defined in the LTE protocol, and sourceConfigSCG defined in the NR protocol.
  • the UE capability information includes, for example, UECapabilityInformation defined in the LTE or NR protocol.
  • the reference configuration information of the SCG may include: capability information of the UE and configuration information of the MCG.
  • the reference configuration information of the SCG may also carry the SCG configuration of the source SN.
  • One purpose of the MN to provide reference configuration information for the SCG is to enable the SN to be referenced when configuring the SCG. Both the MCG configuration information and the SCG configuration information contain two parts.
  • the configuration information of the MCG or the configuration information of the SCG includes: configuration information of the PDCP layer, configuration information of the RLC layer, configuration information of the MAC layer, and configuration information of the PHY layer;
  • the configuration information of the MCG or the configuration information of the SCG includes: configuration information of the SDAP and/or PDCP (for example, radioBearerConfig), configuration information of the RLC layer, configuration of the MAC layer, and configuration information of the PHY layer. At least one of them (specifically, CellGroupConfig).
  • the configuration of the reference configuration information of the SCG sent by the CU to the DU may be as follows:
  • the protocol version supported by the DU is different from the protocol version corresponding to the configuration information of the SCG sent by the CU, for example, the protocol version supported by the DU is 3GPP R15, but the protocol version corresponding to the SCG configuration information sent by the CU is 3GPP R16, then the DU There is a case where the configuration information of the SCG transmitted by the CU cannot be correctly analyzed. For example, the DU can parse most of the configuration information of the SCG, but the newly introduced cell for the 3GPP R16 protocol version cannot be correctly parsed, or the DU cannot be parsed. The configuration information of the part or the entire SCG sent by the CU.
  • the DU Due to the limited capacity of the DU support or the protocol version supported by the DU and the protocol version corresponding to the SCG configuration information sent by the CU, the DU cannot correctly parse the configuration information of the SCG sent by the CU, which may cause a system error.
  • this embodiment illustrates a communication system and/or method 400 that includes:
  • Operation 401 The CU sends the reference configuration information of the SCG to the DU.
  • reference configuration information of the SCG may be SCG-ConfigInfo.
  • a configuration of the reference configuration information of the SCG refer to Table 1.
  • the reference configuration information of the SCG may include configuration information of the SCG and the like.
  • the CU may carry an indication for notifying that the DU needs to perform full configuration by sending a message to the DU.
  • the CU includes the indication (specifically, a full confiurationg indication) in the UE context setup request message and/or the UE context modification request message, to indicate that the DU performs full configuration.
  • the DU receives the trigger of the indication information, and the DU generates a fully configured cell group configuration (for example, CellGroupConfig). If the CU can not correctly identify the configuration information of the SCG, the CU can determine the configuration information of the fully configured radio bearer (for example, radioBearerConfig). Specifically, the CU can send the indication information to notify the DU to generate the full information. Configuration information of the configured cell group (specifically, CellGroupConfig).
  • Operation 402 The DU sends configuration information and/or a first indication of the fully configured cell group to the CU.
  • the DU may not correctly parse the configuration information of the SCG sent by the CU.
  • the DU may parse most of the content of the SCG configuration information, but the newly introduced cell for the 3GPP R16 protocol version cannot be correctly parsed, or The DU cannot parse the configuration information of the part or the entire SCG sent by the CU.
  • the DU may generate the configuration information of the fully configured cell group (the specific form may be: CellGroupConfig), and send the configuration information of the fully configured cell group to the CU.
  • the configuration information (CellGroupConfig) of the fully configured cell group may specifically include at least one of configuration information of the RLC layer, configuration information of the MAC layer, and configuration information of the PHY layer.
  • the DU may also generate a first indication, where the first indication may be used to notify the CU that the DU performs a full configuration.
  • the first indication may be a first full configuration indication (the specific form may be: full Config), and the DU may send the first full configuration indication to the CU.
  • the DU may send a message to the CU on the F1 interface or the DU.
  • the first full configuration indication is sent to the CU in the uplink data packet.
  • the DU may carry the first full configuration indication in at least one of the following types of messages in the F1AP message: UE context setup response (UE context setup)
  • the message, the UE context modification response message is sent to the CU by the type of the message, which is not limited herein.
  • the design is applicable to when the CU sends the reference configuration information of the SCG to the DU, and the DU cannot correctly identify the configuration information of the SCG, the DU can determine the configuration information of the fully configured cell group (such as CellGroupConfig), and the DU passes.
  • the CU is sent to notify the CU, so that the CU also generates configuration information (for example, radioBearerConfig) based on the fully configured radio bearer, which helps solve the problem that the secondary base station cannot understand the configuration information of the source secondary base station and causes a system error.
  • the first indication generated by the DU and the configuration information of the fully configured cell group generated by the DU may be included in the same message and sent to the CU, where the first indication and the configuration of the fully configured cell group are configured. Information can also be sent to the CU in separate messages.
  • the DU may also be instructed to perform full configuration by an implicit method.
  • the distributed unit DU (optionally, within a predetermined time) does not receive the secondary cell group SCG from the centralized unit.
  • Configuration information; or the distributed unit DU receives the reference configuration information of the secondary cell group SCG from the centralized unit, but the reference configuration information of the secondary cell group SCG does not include configuration information of all or part of the secondary cell group SCG
  • the DU can perform a full configuration operation, for example, the DU generates the configuration information of the fully configured cell group (such as CellGroupConfig), and the DU notifies the CU by sending the indication information, so that the CU also generates the configuration information of the radio bearer based on the full configuration.
  • the DU sends configuration information (for example, CellGroupConfig) of the fully configured cell group to the CU. For example, if the DU receives a message (such as a UE context setup request message) that includes E-URTAN quality of service (QoS) information, the DU can learn that the base station where the DU is located is in the process of performing EN-DC, The base station where the CU-DU is located is a secondary base station.
  • a message such as a UE context setup request message
  • QoS quality of service
  • the DU may be triggered to generate cell group full configuration information (CellGroupConfig).
  • CellGroupConfig new air interface dual connectivity
  • NR-DC new air interface dual connectivity
  • MR DC multi-RAT/Radio Dual Connectivity
  • NE-DC NE-DC
  • LTE DC LTE dual connectivity
  • Operation 403 The CU sends a second indication to the UE.
  • the CU generates configuration information of the radio bearer based on the full configuration (specifically, radioBearerConfig).
  • the CU may receive the first indication sent by the DU (such as the first full configuration indication). Then, the configuration information of the radio bearer based on the full configuration is generated.
  • the CU may also determine the configuration information of the radio bearer based on the full configuration. In this case, the DU may not send the first indication to the CU.
  • the CU may generate a control message based on the full configuration based on configuration information of the fully configured radio bearer (such as radioBearerConfig) and/or configuration information of the fully configured cell group (such as CellGroupConfig) from the DU.
  • the control message includes configuration information of the fully configured radio bearer and/or configuration information of the fully configured cell group from the DU, and the control message may be an RRC reconfiguration (specifically, an RRC reconfiguraiton) message.
  • the configuration information of the fully configured radio bearer and/or the configuration information of the fully configured cell group from the DU may be sent to the UE by using a control message on an interface between the MN and the SN.
  • the configuration information of the radio bearer may include at least one of configuration information of the SDAP and the PDCP.
  • the CU may carry the second indication by using a control message, such as an RRC reconfiguration (such as RRCReconfiguration) message, where the second indication may be a second full configuration indication (specifically, fullconfig), and the CU may also The second indication is sent to the UE by using another separate signaling.
  • the CU may send the second indication to the MN, and the MN sends the indication information to the UE according to the second indication, so that the UE The secondary base station configuration update operation is performed.
  • the CU may directly send an RRC reconfiguration message to the UE, where the RRC reconfiguration message may include the second indication, and notify the UE to perform a secondary base station configuration update operation, where the CU acts as
  • the second indication may be sent to the UE by other signaling, and the UE is notified to perform the secondary base station configuration update operation.
  • the configuration update operation performed by the UE includes at least one of the following: deleting the basic information except For example, other proprietary configurations than the MCG cell radio network temporary identifier (C-RNTI) and/or MCG security related configuration; enabling new configuration in the RRC reconfiguration message (eg, measuring configuration MeasConfig, OtherConfig, etc.).
  • C-RNTI MCG cell radio network temporary identifier
  • MCG security related configuration e.g, measuring configuration MeasConfig, OtherConfig, etc.
  • the configuration update operation performed by the UE includes at least one of the following: replacing the old configuration with the new configuration carried in the RRC reconfiguration message, if Some of the old configuration cannot be replaced by the new configuration. For example, some cells do not exist in the new configuration. For this part of the cell, the following operations can be performed according to the 3GPP protocol: the UE continues to use the value of the corresponding parameter in the previous configuration, and the UE behavior is unchanged. Alternatively, the UE deletes the parameter and stops the related behavior.
  • a full configuration indication of an air interface is defined.
  • a full configuration indication (specifically en-DC-release or scg-ConfigReleaseNR) for the configuration of the SCG in the air interface is added.
  • the basic meaning is similar to fullconfig.
  • the difference is in the EN-DC scenario for SCG.
  • the configured full configuration indication is only for the SCG configuration.
  • the UE receives a full configuration indication for the configuration of the SCG, and can delete other proprietary configurations other than SCG basic information such as SCG C-RNTI, SCG security related configuration, etc., enabling the RRC received by the UE. Reconfigure new configurations in messages, and more.
  • the UE may also delete all configurations of the SCG, enable new configuration in the RRC reconfiguration message, and the like. For other dual or multiple connections, a full configuration indication of the configuration of the SCG for the SCG may be introduced in the future. This program is equally applicable.
  • the CU when the gNB formed by the CU-DU is used as the secondary base station (the CU represents the secondary base station to communicate with other network elements), the CU sends a third full configuration indication to the primary base station, so that the primary base station is in its RRC reconfiguration.
  • the message carries a full configuration indication of the secondary base station (specifically, an en-DC-release indication or an scg-ConfigReleaseNR indication).
  • the CU sends the second indication and/or the RRC reconfiguration message to the UE, and the CU sends the second indication to the UE, for example, the CU passes the F1 interface between the CU and the DU.
  • the second indication and/or the RRC reconfiguration message is sent to the DU, and the DU is sent to the UE through the air interface, and the DU can use the method of not parsing the message content when sending the second indication and/or the RRC reconfiguration message to the UE.
  • Sending, the DU may also be sent by means of parsing part or all of the message content, which is not limited herein.
  • the base station has the system architecture as shown in FIG. 3, that is, when the centralized unit CU includes a centralized unit control plane (CU-CP) and a centralized unit user plane (CU-UP), the foregoing
  • CU-CP centralized unit control plane
  • CU-UP centralized unit user plane
  • the functions of the CU in an embodiment and any of its designs may be performed by the CU-CP, the operation between the CU-CP and the DU being similar to the operation between the CU and the DU in any of the foregoing embodiments and any of the designs.
  • Optional operation 1 The CU-CP sends the SCG reference configuration information to the DU. For details, refer to operation 401.
  • Optional operation 2 The DU sends the fully configured cell group configuration and/or the first indication to the CU-CP. For details, refer to operation 402.
  • Optional operation 3 The CU-CP sends the reference configuration information of the SCG to the CU-UP.
  • the CU-CP adds a fourth indication to the E1 interface message (for example, the UE context setup request or the UE context modification request message), for example, the fourth indication may be the fourth full
  • the configuration indicator is used to notify the CU-UP to generate configuration information of the fully configured radio bearer (specifically: radioBearerConfig).
  • the CU-UP may be instructed to perform full configuration by using an implicit method, for example, the CU-CP does not send reference configuration information of the SCG (specifically, may be SCG-ConfigInfo) or If the reference configuration information of the SCG sent by the CU-CP (which may be SCG-ConfigInfo) does not include part or does not include all SCG configurations, the CU-UP may be triggered to perform a full configuration operation. For example, if the CU-UP received message (such as the UE context setup request message) contains E-URTAN quality of service (QoS) information, the CU-UP can learn that the base station where the DU is located performs EN-DC.
  • the CU-CP does not send reference configuration information of the SCG (specifically, may be SCG-ConfigInfo) or If the reference configuration information of the SCG sent by the CU-CP (which may be SCG-ConfigInfo) does not include part or does not include all SCG configurations, the CU-UP may be triggered to perform a
  • the base station where the CP-UP is located is a secondary base station.
  • the CP-UP does not receive the reference configuration information of the SCG (specifically, it may be SCG-ConfigInfo) or the reference configuration information of the SCG sent by the CU-CP ( Specifically, the CG-UP may be configured to include the radio bearer configuration information of the fully configured radio bearer (specifically, radioBearerConfig).
  • Optional operation 4 The CU-UP sends the configuration information of the fully configured radio bearer (specifically: radioBearerConfig) and/or the fifth indication to the CU-CP.
  • the fifth indication may be used to notify the CU-CP that the CU-UP performs the full configuration.
  • the fifth indication may be a fifth full configuration indication (the specific form may be: full Config), and the CU-UP will be the fifth.
  • the full configuration indication is sent to the CU-CP.
  • the CU-UP may send the fifth full configuration indication to the CU-CP in the uplink data packet sent by the CU-CP to the CU-CP.
  • the CU-UP may carry the fifth full configuration indication in at least one of the following types of messages in the E1AP message: a UE context setup response message, a UE context modification response message,
  • the fifth full configuration indication is sent to the CU-CP by using a specific type of message, which is not limited herein.
  • the CU-UP if the CU-UP cannot correctly parse the configuration information of the SCG from the CU-CP, the CU-UP generates configuration information of the fully configured radio bearer (such as radioBearerConfig), specifically including SDAP and/or Or PDCP configuration.
  • the fully configured radio bearer such as radioBearerConfig
  • Optional operation 5 The CU-CP sends a second indication to the UE.
  • the CU-CP generates configuration information (such as radioBearerConfig) of the fully configured radio bearer sent by the CU-UP and/or configuration information of the fully configured cell group (such as CellGroupConfig) from the DU.
  • the control message may be an RRC reconfiguration (specifically, an RRC reconfiguraiton) message.
  • the configuration information of the radio bearer may include at least one of configuration information of the SDAP and the PDCP.
  • the CU-CP receives the first indication sent by the DU (such as the first full configuration indication) and/or the fifth indication sent by the CU-UP (such as the fifth full configuration indication), and generates a configuration based on the full configuration.
  • the RRC reconfiguration message includes configuration information of the fully configured radio bearer sent by the CU-UP and/or configuration information of the fully configured cell group from the DU.
  • the configuration information of the fully configured radio bearer sent by the CU-UP and/or the configuration information of the fully configured cell group from the DU may be sent to the UE by using a control message on an interface between the MN and the SN.
  • the operations are sequentially numbered in the foregoing embodiment, but it is understood that the sequence numbering is merely for convenience of writing, and does not mean that operations must be sequentially performed in order of sequential numbers.
  • the above operation sequence may be changed according to requirements.
  • the CU-CP may first interact with the CU-UP, and then interact with the DU, according to operation 1, operation 3, operation 4, operation 2, and operation. The order of 5 is executed. There is no limit here.
  • the CU-UP can be physically deployed separately from the CU-CP and the DU, or can be deployed in a centralized manner.
  • any of the designs shown above may be understood as a technical solution designed for a specific scenario or a specific technical problem, but it is not necessary to implement the technical content described in the present application, and any one of the designs may be required according to needs. Implemented in conjunction with other designs to more specifically address specific objective technical issues.
  • the distributed unit DU has the functions of the RLC, MAC, and PHY protocol layers
  • the centralized unit CU has the functions of the RRC, SDAP, and/or PDCP protocol layers
  • the DU and CU The protocol layers that are formed together constitute the RRC, SDAP, PDCP, RLC, MAC and PHY or RRC, PDCP, RLC, MAC and PHY protocol layer architecture settings that the base station has.
  • RRC Secure Digital Access
  • PDCP Radio Resource Control Protocol
  • RLC radio link control protocol
  • MAC and PHY protocol layer architecture settings that the base station has.
  • the DU has a MAC and a PHY
  • the CU has RRC, SDAP, PDCP and RLC or RRC, PDCP and RLC, where Not limited.
  • the DU can be physically integrated with the radio system as two parts of a communication device, and the DU and CU can also be physically part of a communication device to integrate the two, or The RF system and the DU and CU can also be physically part of the same network node so that the three can be integrated.
  • the embodiment of the present application provides a schematic block diagram of a communication device 500, where the communication device 500 includes:
  • At least one processor 501 optionally including a communication interface 502 for supporting communication interaction between the communication device 500 and other devices; when the program instructions are executed in the at least one processor 501, the foregoing embodiment of the present application
  • the functions of any of the following devices operating on any of the following devices are implemented: CU, DU, CP, and UP.
  • the communication device 500 may further include a memory 503 for storing program instructions necessary for implementing the above-described device functions or process data generated during program execution.
  • the communication device 500 may further include internal interconnection lines to implement communication interaction between the at least one processor 501, the communication interface 502, and the memory 503.
  • the at least one processor 501 can be implemented by a dedicated processing chip, a processing circuit, a processor, or a general purpose chip.
  • a dedicated circuit/chip may be provided in the at least one processor.
  • the implementation can also be implemented by using a general-purpose processor provided in the at least one processor 501 to execute a program instruction related to a PHY function, an F1 port or an E1 port communication function; for example, the embodiment of the present application relates to a MAC in the device.
  • the at least one processor 501 may comprise a communication processing chip, by performing a MAC layer, an RLC layer, a PDCP layer, an SDAP layer and an RRC layer.
  • the relevant functions of the program instructions are implemented. It can be understood that the various methods, processes, operations or steps involved in the embodiments of the present application can be combined in one-to-one correspondence by computer software, electronic hardware, or a combination of computer software and electronic hardware. A corresponding implementation. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution.
  • the communication interface 502 generally has a function of performing information interaction between two communication peers.
  • the communication interface may be designed as an interface circuit or include the same.
  • the hardware module of the interface circuit supports the wired form communication interaction between the communication peers.
  • the F1 port between the DU and the CU involved in the present application and the communication function of the E1 port between the CP and the UP can be adopted.
  • This type of interface design for the case where the wireless communication information interaction is performed between the communication peers, the communication interface may be an interface circuit having a radio frequency transceiving function, or a hardware system including the interface circuit having the radio frequency transceiving function.
  • the communication interface of the DU and the UE can adopt this design.
  • the CU, DU, the CP, or the UP can also be implemented by directly or indirectly executing the implementation program instructions of the embodiment related design by using a general hardware platform (having processing resources and storage resources). Or the function of UP in each design of the embodiment of the present application.
  • An actual deployment method may be that the CU, the CP, or the UP may be close to the core network device, or may be deployed cooperatively, and may be physically separated or combined; the functions of the CU, CP, or UP may also be used as part of the core network device.
  • the embodiment of the present application further provides a computer program product having program instructions, when the program instructions are directly or indirectly executed, for example, when executed in the communication device 500 in the foregoing embodiment,
  • the functions of any of the following devices in any of the design embodiments are implemented: CU, CP, UP, and DU.
  • the program instructions may 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 program instructions may be from a website site, a computer
  • the server or data center is transported to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line) or wireless (eg, infrared, wireless, microwave, etc.).
  • a program instruction When a program instruction is executed, considering that a specific network device generally includes a hardware layer, an operating system layer running on the hardware layer, or an intermediate layer, when the program instructions related to the embodiment of the present application are executed, the multi-layer is often The invocation and execution of software, so the program instructions can be an indirect execution process in a hardware device (general purpose processing circuit or dedicated processing circuit).
  • the embodiment of the present application further provides a chip system, the chip system including at least one processor, when program instructions are executed in the at least one processor, such that the design is as described in the first aspect and any of the The functions on any of the following devices are implemented: CU, DU, CP, and UP.

Landscapes

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

Abstract

本申请实施例提供了一种通信方法，以解决当具有CU和DU架构的基站作为辅基站时，DU无法正确解析CU向DU发送的SCG的配置信息，从而导致系统出错的问题。该方法包括：分布式单元DU向集中式单元CU发送全配置的小区组的配置信息和/或第一指示，该第一指示用于通知该集中式单元CU该分布式单元DU执行了全配置的情况；该分布式单元将来自于CU的第二指示发送给终端设备，该第二指示用于通知该终端设备执行配置更新操作。

Description

一种通信方法，设备及其系统
本申请要求于2017年12月29日提交中国专利局、申请号为201711483393.6、发明名称为“一种通信方法，设备及其系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，更具体的，涉及一种通信方法，设备及其系统等。
背景技术
在下一代移动通信系统中，比如第五代移动通信(the 5th generation mobile communication technology，5G)系统中，基站被称为gNB或ng-eNB，其中，ng-eNB是源于长期演进(long term evolution，LTE)系统基站(LTE eNB)的后续演进基站，仅为便于描述，本文采用gNB来表示基站。图1所示系统100为一种5G系统的示意性框图，其中，下一代无线接入网(next generation radio access network，NG-RAN)中的gNB和gNB之间，ng-eNB和ng-eNB之间，以及gNB和ng-eNB之间通过Xn接口互连。gNB和5G核心网(5G core，5GC)设备之间通过NG接口互连，ng-eNB和5GC设备之间通过NG接口互连。其中，5GC设备可以是接入和移动性管理功能实体(access and mobility management function，AMF)或用户面功能实体(user plane function，UPF)，AMF主要负责接入管理方面功能，UPF主要负责会话(session)管理方面功能。基站通常包括无线资源控制(radio resource control，RRC)层，业务数据适配协议(service data adaptation protocol，SDAP)层，分组数据汇聚层协议(packet data convergence protocol，PDCP)层，无线链路控制(radio link control，RLC)层，媒体接入控制(media access control，MAC)层，以及物理层(physical layer，PHY)等逻辑功能协议层。下一代基站(例如gNB)对传统基站架构进行了演进。图2为一种5G系统的示意性框图，该系统200包括5GC和NG-RAN，在NG-RAN中，基站gNB可以由集中式单元(centralized unit,CU)和分布式单元(distributed unit,DU)构成，CU和DU架构可以理解为是对传统接入网中的基站的功能进行拆分，传统基站的一部分功能部署在CU，其余功能部署在DU，多个DU可共用一个CU以节省成本并易于网络扩容，CU和DU之间通过F1接口进行信息交互。对于由CU和DU构成的gBN，对于外部其他网元而言是一个基站。
进一步的，如图3所示的一种5G系统的示意性框图中，在gNB中，集中式单元CU还可以划分为CU控制面(CU control plane,CU-CP)和CU用户面(CU user plane，CU-CP)。其中，CU-CP负责控制面功能，主要包含RRC和PDCP控制面部分(PDCP-C)，PDCP-C主要负责控制面数据的加解密，完整性保护，以及数据传输等；CU-UP负责用户面功能，主要包含SDAP和PDCP-U，其中SDAP主要负责将核心网的数据进行处理并将流(flow)映射到无线承载，PDCP-U主要负责数据面的加解密，完整性保护，头压缩，序列号维护，以及数据传输等。其中，CU-CP和CU-UP通过E1接口连接，CU-CP代表gNB通过Ng接口和核心网连接，CU-CP通过F1-C(F1控制面)接口和DU连接，CU-UP通过F1-U(F1用户面)接口和DU连接。还有一种设计是PDCP-C和PDCP-C都在CU-UP，RRC在CU-CP(图3中未示出)。
在双连接(dual connectivity，DC)场景下，当具有CU和DU架构的基站作为辅基站(secondary node，SN)时，DU存在不能正确解析CU向DU发送的辅小区组(secondary cell group，SCG)的配置信息的问题，从而导致系统出错。
发明内容
本申请提供一种通信方法，设备及其系统等，以解决背景技术中当具有CU和DU架构的基站作为辅基站时，DU存在不能正确解析CU向DU发送的辅小区组的配置信息，从而导致系统出错的问题。
第一方面，本申请实施例提供了一种通信方法，该通信方法运行在通信系统中，该通信系统包括集中式单元和分布式单元，在该通信系统运行时，执行如下操作：
该分布式单元DU向该集中式单元CU发送小区组的配置信息和/或第一指示，所述小区组的配置信息可以是全配置的小区组的配置信息，该第一指示可用于通知该集中式单元CU在该分布式单元DU执行了全配置的情况，或者，该分布式单元DU可通过该第一指示触发该集中式单元CU生成全配置相关的信息，例如，CU收到该第一指示后，生成全配置的无线承载的配置信息。
一种可选设计中，该分布式单元DU和该集中式单元CU构成多连接场景中的辅基站，该分布式单元将来自于CU发送的第二指示发送给终端设备，所述第二指示可用于通知所述终端设备执行辅基站配置更新操作。
一种可选设计中，该分布式单元DU将来自于所述集中式单元CU的控制消息发送给终端设备，比如，该控制消息可以是无线资源控制重配置消息，该无线资源控制重配置消息中包含该全配置的无线承载的配置信息和/或全配置的小区组的配置信息；其中，该全配置的无线承载的配置信息包括业务数据适配协议层的配置信息和分组数据汇聚层协议层的配置信息中的至少一种；该全配置的无线承载的配置信息是该集中式单元CU基于所述第一指示触发生成；该全配置的小区组的配置信息包括无线链路控制层的配置信息，媒体接入控制层的配置信息，以及物理层的配置信息中的至少一种。
一种可选设计中，该全配置的小区组的配置信息和该第一指示被包含在该分布式单元和该集中式单元之间通信接口上定义的一个消息中发送，或者该全配置的小区组的配置信息和该第一指示被携带在所述分布式单元和所述集中式单元之间的上行数据包中发送。
一种可选设计中，该分布式单元DU向该集中式单元CU发送全配置的小区组的配置信息和/或第一指示，需要满足如下中至少一种：
1、该分布式单元DU接收到该集中式单元发送的辅小区组SCG的参考配置信息，但该分布式单元DU无法正确解析或者理解该辅小区组SCG的参考配置信息中的辅小区组SCG的配置信息；
2、该分布式单元DU(可选的，在预定时间内)未从该集中式单元接收到辅小区组SCG的配置信息；或者，该分布式单元DU接收到来自于该集中式单元的辅小区组SCG的参考配置信息，但该辅小区组SCG的参考配置信息未包含全部或部分辅小区组SCG的配置信息；以及，
3、该分布式单元DU接收到来自于所述集中式单元的指示，所述指示用于通知所述分布式单元DU需要执行全配置。
本设计方案可适用于当CU将SCG的参考配置信息发送给DU，而DU无法正确识别其中的SCG的配置信息时，DU可以决定生成全配置的小区组的配置信息(具体如CellGroupConfig)，DU通过发送指示信息通知CU，以便CU也产生基于全配置的无线承载的配置信息(具体如radioBearerConfig)，也有助于解决辅基站无法理解源辅基站的配置信息从而导致系统出错的问题。
一种可选设计中，该分布式单元具有或者仅包括：无线链路控制层，媒体接入控制层，以及物理层；该集中式单元具有或者仅包括：无线资源控制层，业务数据适配协议层，以及分组数据汇聚层协议层。
通过前述第一方面提供的一种通信方法及其各种可行的设计，以有助于解决DU存在不能正确解析CU向DU发送的辅小区组的配置信息，从而导致系统出错的问题。
第二方面，本申请提供了一种通信设备，该通信设备包括：至少一个处理器和通信接 口，该通信接口用于该通信设备与其他通信设备进行信息交互，当程序指令在该至少一个处理器中执行时，使得通信设备实现第一方面及其各种可选的设计在集中式单元或分布式单元的功能。
第三方面，本申请提供了一种计算机程序产品，该计算机程序产品具有程序指令，当该程序指令被直接或者间接执行时，使得如第一方面及其各种可选的设计在集中式单元或分布式单元上的功能得以实现。
第四方面，本申请提供了一种计算机程序存储介质，该计算机程序存储介质具有程序指令，当该程序指令被直接或者间接执行时，使得如第一方面及其各种可选的设计在集中式单元或分布式单元上的功能得以实现。
第五方面，本申请提供了一种芯片系统，该芯片系统包括至少一个处理器，当程序指令在该至少一个处理器中执行时，使得如第一方面及其各种可选的设计在集中式单元或分布式单元上的功能得以实现。
第六方面，本申请提供了一种通信系统，该通信系统包括如第二方面所述的通信设备。
附图说明
图1是本申请实施例提供的一种5G系统的示意性框图；
图2是本申请实施例提供的一种5G系统的示意性框图；
图3为本申请实施例提供的一种5G系统的示意性框图；
图4为本申请实施例提供的一种通信系统及方法的示意图；
图5为本申请实施例提供的一种通信设备的示意性框图。
具体实施方式
首先对本申请各实施例出现的术语进行具有共性部分技术含义的描述。
本申请中的术语“第一”、“第二”等仅是为了区分不同的对象，“第一”、“第二”并不对其修饰的对象的实际顺序或功能进行限定。例如，“第一指示”和“第二指示”中的“第一”、“第二”，仅仅是为了区分这两者是不同的指示，“第一”和“第二”本身并不对其实际先后顺序或者功能进行限定。本申请中出现的“示例性的”，“示例”，“例如”，“可选的设计”或者“一种设计”等表述，仅用于表示举例子、例证或说明。本申请中被描述为“示例性的”，“示例”，“例如”，“可选的设计”或者“一种设计”的任何实施例或设计方案都不应被解释为比其他实施例或设计方案更优选或更具优势。确切而言，使用这些词旨在以具体方式呈现相关概念。本申请中出现的术语“上行”和“下行”，用于在特定场景描述数据/信息传输的方向，比如，“上行”方向一般是指数据/信息从终端设备向网络侧传输的方向，或者分布式单元向集中式单元传输的方向，“下行”方向一般是指数据/信息从网络侧向终端设备传输的方向，或者集中式单元向分布式单元传输的方向，可以理解，“上行”和“下行”仅用于描述数据/信息的传输方向，该数据/信息传输的具体起止的设备都不作限定。
本申请中出现的术语“和/或”，仅仅是一种描述对象之间的关联关系，表示对象间可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本申请中字符“/”，如无特别说明，则一般表示前后对象之间是一种“或”的关系。本申请中出现的字符“-”，一般用来表示该字符前后的对象两者之间具有对应/关联/映射/协作关系。例如，对于表述“分组数据汇聚协议处理的用户面功能(PDCP-U)”中“-”，可理解为表示PDCP功能中对应的用户面部分功能。
本申请中出现的类似于“项目包括如下中至少一种：A，B，以及C”表述的含义，如无特别说明，通常是指该项目可以为如下中任一个：A；B；C；A和B；A和C；B和C；A， B和C；A和A；A，A和A；A，A和B；A，A和C，A，B和B；A，C和C；B和B，B，B和B，B，B和C，C和C；C，C和C，以及其他A，B和C的组合。以上是以A，B和C共3个元素进行举例来说明该项目的可选用条目，当该表达为“项目包括如下中至少一种：A，B，……，以及X”时，即该表达中具有更多元素时，那么该项目可以适用的条目也可以按照前述规则获得。
在本申请中可能出现的对各种消息/信息/设备/网元/系统/装置/动作/操作/流程/概念等各类客体进行了赋名，可以理解的是，这些具体的名称并不构成对相关客体的限定，所赋名称可随着场景，语境或者使用习惯等因素而变更，对本申请中技术术语的技术含义的理解，应主要从其在技术方案中所体现/执行的功能和技术效果来确定。
在本申请中，终端设备可以包含如下形式：用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备可以是WLAN中的站点(STAION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及下一代通信系统，例如，5G网络中的终端设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备等。终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。终端设备还可以是物联网(internet of things，IoT)系统中的终端设备，IoT是未来信息技术发展的重要组成部分，其主要技术特点是将物品通过通信技术与网络连接，从而实现人机互连，物物互连的智能化网络。在本申请实施例中，终端设备以UE为例进行实施例方案的描述，但可以理解的是，本申请实施例中终端设备不限于UE。
本申请实施例描述的网络架构以及业务场景是为了便于读者清楚理解本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
基于演进的通用陆基无线接入及新空口的双连接(evolved universal terrestrial radio access-new radio dual connectivity，EN-DC)的场景下UE进行切换过程中，例如，UE在源基站执行DC，UE到目标基站也执行DC的情况下，源侧基站在切换过程中将源基站相关的配置信息发送给目标侧基站，目标侧基站中的主基站(master node,MN)如能正确解析其中的主小区组(master cell group，MCG)的配置信息，则该目标MN将辅小区组(secondary cell group，SCG)配置信息发送给目标侧基站中的辅基站(secondary node，SN)，若该目标SN如果无法正确解析SCG的配置信息，则该目标SN通过发送指示信息通知该目标MN将采用SCG的全配置，目标MN收到该目标SN的该指示，该目标MN在给UE发送的控制消息(比如LTE系统的RRC重配置消息)中包含全配置指示，此处该全配置指示具体可以是en-DC-release指示或者scg-ConfigReleaseNR指示。
针对逻辑基站具有CU和DU架构的场景，当具有CU和DU架构的基站作为辅基站时，CU将主基站提供的辅小区组(secondary cell group，SCG)的参考配置信息(例如SCG-ConfigInfo)发给DU。SCG的参考配置信息包括如下中至少一种：主小区组(master cell group，MCG)的配置信息，SCG的配置信息，以及UE的能力信息等。MCG的配置信息包括如下中至少一种：长期演进(long term evolution，LTE)系统协议中定义的radioResourceConfigDedMCG，LTE协议中定义的sCellToAddModListMCG，以及基于5G新空口(new radio，NR)协议中定义的mcg-RB-Config；SCG的配置信息包括如下中至少一种：LTE协议中定义的scg-RadioConfig，以及NR协议中定义的sourceConfigSCG。UE能力 信息包括：例如LTE或NR协议中定义的UECapabilityInformation。
一般的，SCG的参考配置信息可以包括：UE的能力信息和MCG的配置信息。针对SCG发生改变的情况，比如在MN保持不变的情况下从源SN切换到目标SN，或者MN和SN同时改变的切换场景，那么SCG的参考配置信息中还可以携带源SN的SCG配置。MN提供SCG的参考配置信息的一个目的是使得SN在配置SCG时能够得到参考。MCG的配置信息和SCG的配置信息均包含两部分内容。例如，对于LTE系统而言，MCG的配置信息或SCG的配置信息均包含：PDCP层的配置信息，以及RLC层的配置信息，MAC层的配置信息和PHY层的配置信息中的至少一种；对于NR系统而言，MCG的配置信息或SCG的配置信息均包含：SDAP和/或PDCP的配置信息(具体如，radioBearerConfig)，以及RLC层的配置信息，MAC层的配置和PHY层的配置信息中的至少一种(具体如，CellGroupConfig)。示例性的，以NR为例，CU给DU发送的SCG的参考配置信息的构成可以如下表一所示：
表一：
Figure PCTCN2018124826-appb-000001
当DU支持的协议版本和CU发送的SCG的配置信息对应的协议版本不同时，例如，DU支持的协议版本是3GPP R15，但CU发送的SCG的配置信息对应的协议版本为3GPP R16，那么DU存在无法正确解析该CU发送的SCG的配置信息的情况，比如，DU可以解析SCG的配置信息中的大部分内容，但是对于3GPP R16协议版本新引入的信元则无法正确解析，或者DU无法解析该CU发送的部分或者整个SCG的配置信息。由于DU支持的能力有限或者DU支持的协议版本和CU发送的SCG的配置信息对应的协议版本有差异，导致DU存在无法正确解析该CU发送的SCG的配置信息的情况，进而导致系统出错。
有鉴于此，以下结合附图，对本申请中的技术方案进一步进行描述。
如图4所示，本实施例示出了一种通信系统和/或方法400，包括：
操作401：CU将SCG的参考配置信息发送给DU。
示例性的，SCG的参考配置信息的一种具体形式可以是SCG-ConfigInfo。该SCG的参考配置信息的一种构成可以参考表一，例如，该SCG的参考配置信息可以包括SCG的配置信息等。
一种可选设计中，CU可以通过在发给DU的消息中携带用于通知DU需要执行全配置的一个指示。比如，CU在UE上下文建立请求消息(UE context setup request message)和/或UE上下文修改请求消息(UE context modification requestmessage)中包含该指示(具体可以为full confiurationg指示)，以指示DU执行全配置，例如，DU收到该指示信息的触发，DU生成全配置的小区组配置(具体如：CellGroupConfig)。本设计方案可以适用于CU无法正确识别SCG的配置信息的情况下，CU可以决定生成全配置的无线承载的配置信息(具体如radioBearerConfig)，具体的，CU可以发送指示信息，以通知DU产生全配置的小区组的配置信息(具体如CellGroupConfig)。通过本设计方案，解决了辅基站(SN)无法理解源辅基站的配置信息从而导致系统出错的问题。
需要说明的是，本操作401的全部或者部分均为可选。
操作402：DU将全配置的小区组的配置信息和/或第一指示发送给CU。
一种可选设计中，若存在DU无法正确解析来自CU发送的SCG的配置信息的情况，例如，DU支持的协议版本是3GPP R15，但CU发送的SCG的配置信息对应的协议版本为3GPP R16，那么DU存在无法正确解析该CU发送的SCG的配置信息的情况，如，DU可以解析SCG的配置信息中大部分的内容，但是对于3GPP R16协议版本新引入的信元则无法正确解析，或者DU无法解析该CU发送的部分或者整个SCG的配置信息。可选的，DU可以产生全配置的小区组的配置信息(具体形式可以为：CellGroupConfig)，将该全配置的小区组的配置信息发送给CU。其中，该全配置的小区组的配置信息(CellGroupConfig)具体可以包括RLC层的配置信息，MAC层的配置信息和PHY层的配置信息中的至少一种。
一种可选设计中，DU还可以产生第一指示，该第一指示可用于通知CU该DU执行了全配置的情况。该第一指示可以是第一全配置指示(具体形式可以为：full Config)，DU可以将该第一全配置指示发送给CU，例如，DU可以在F1接口上的消息或者DU给CU发的上行数据包中携带该第一全配置指示发送给CU，示例性的，DU可以在F1AP消息中的如下类型消息中的至少一个中携带该第一全配置指示：UE上下文建立响应(UE context setup response)消息，UE上下文修改响应消息(UE context modification response)，具体通过哪些类型的消息将该第一全配置指示发送给CU，此处不做限定。本设计方案适用于当CU将SCG的参考配置信息发送给DU，而DU无法正确识别其中的SCG的配置信息时，DU可以决定生成全配置的小区组的配置信息(具体如CellGroupConfig)，DU通过发送指示信息通知CU，以便CU也产生基于全配置的无线承载的配置信息(具体如radioBearerConfig)，有助于解决辅基站无法理解源辅基站的配置信息从而导致系统出错的问题。
一种可选设计中，DU产生的第一指示和DU产生的全配置的小区组的配置信息可以被包含在同一个消息中发送给CU，该第一指示和该全配置的小区组的配置信息也可以在不同的消息中分别发送给CU。
一种可选设计中，还可以通过隐式的方法指示DU执行全配置，例如，该分布式单元DU(可选的，在预定时间内)未从该集中式单元接收到辅小区组SCG的配置信息；或者，该分布式单元DU接收到来自于该集中式单元的辅小区组SCG的参考配置信息，但该辅小区组SCG的参考配置信息未包含全部或部分辅小区组SCG的配置信息；，则DU可以执行全配置操作，具体如：DU生成全配置的小区组的配置信息(具体如CellGroupConfig)，DU通过发送指示信息通知CU，以便CU也产生基于全配置的无线承载的配置信息，和或，DU将全配置的小区组的配置信息(具体如CellGroupConfig)发送给CU。还例如，若DU收到消息中(如UE context setup request message)包含E-URTAN服务质量(quality of servie，QoS)信息，则DU可以获知该DU所在的基站处于执行EN-DC的过程，该CU-DU所在的基站是辅基站，可选的，此时若该DU未收到SCG的参考配置信息(具体可以为SCG-ConfigInfo)或者CU发送的SCG的参考配置信息(具体可以为SCG-ConfigInfo)中不包含部分或者不包含全部SCG配置，则可以触发DU产生小区组全配置信息(CellGroupConfig)。对于其他双连接或多连接场景，例如新空口双连接(NR-DC)，多制式/空口双连接(Multi-RAT/Radio Dual Connectivity,MR DC)，NE-DC，LTE双连接(LTE DC)，以及其他各种多连接(Multi-Connectivity)，也可以参考本实施例提出的操作。
操作403：CU向UE发送第二指示。
一种可选设计中，CU产生基于全配置的无线承载的配置信息(具体可以为：radioBearerConfig)，可选的，CU可在收到DU发送的第一指示(如该第一全配置指示)后产生基于全配置的无线承载的配置信息；另一可选的，CU也可以自主决定产生基于全配置的无线承载的配置信息，此时，DU可不用向CU发送该第一指示。具体的，CU可以基于该全配置的无线承载的配置信息(如radioBearerConfig)和/或来自于DU的该全配置的小区组的配置信息(如CellGroupConfig)生成基于全配置的一个控制消息，可选的，该控制消息中包含该全配置的无线承载的配置信息和/或来自于DU的该全配置的小区组的配置信息，该控制消息可以是RRC重配置(具体可以为：RRCreconfiguraiton)消息，或者该全配置的 无线承载的配置信息和/或来自于DU的该全配置的小区组的配置信息可以通过MN和SN之间接口上的控制消息向UE发送。其中，该无线承载的配置信息可以包括SDAP和PDCP的配置信息中的至少一种。
一种可选设计中，CU可以通过控制消息，比如RRC重配置(如RRCReconfiguration)消息中携带该第二指示，该第二指示可以为第二全配置指示(具体可以为fullconfig)，CU也可以通过其他单独的信令将该第二指示发送给UE，可选的，还例如，CU可以将该第二指示发给MN，MN基于该第二指示，再发送指示信息给UE，以使得UE进行辅基站配置更新操作。还例如，当CU作为辅基站SN的一部分时，则CU可以直接发送RRC重配置消息给UE，该RRC重配置消息中可以包含所述第二指示，通知UE执行辅基站配置更新操作，CU作为辅基站SN的一部分时，也可以通过其他信令将第二指示发送给UE，通知UE执行辅基站配置更新操作。
当UE收到该第二全配置指示，比如通过接收RRC重配置消息中包含的该第二全配置指示(如fullconfig)，则UE执行的配置更新操作包括如下中至少一种：删除除了基本信息例如与MCG小区无线网络临时标识(cell radio network temporary identifier，C-RNTI)和/或MCG安全相关的配置之外的其他专有配置；启用RRC重配置消息中的新配置(例如测量配置MeasConfig，OtherConfig等)。当UE收到RRC重配置消息中不包含该第二全配置指示(如fullconfig)，则UE执行的配置更新操作包括如下至少一种：用RRC重配置消息中携带的新配置代替旧配置，如果旧配置有部分无法被新配置代替，例如新配置中不存在部分信元，对这部分信元可以根据3GPP协议规定如下操作：UE继续使用以前旧配置中相应参数的值，UE行为不变，或者，UE删除该参数并停止相关行为。
在LTE系统中，仅定义了一个空口的全配置指示。对于EN-DC场景，增加了一个在空口针对SCG的配置的全配置指示(具体可以是en-DC-release或scg-ConfigReleaseNR)，基本含义和fullconfig类似，区别在于EN-DC场景中针对SCG的配置的全配置指示只是针对SCG的配置。EN-DC场景中，UE收到针对SCG的配置的全配置指示，可以删除除了SCG基本信息例如SCG C-RNTI，SCG安全相关的配置等之外的其他专有配置，启用UE收到的RRC重配置消息中的新配置等。UE也可以删除SCG的所有配置，启用RRC重配置消息中的新配置等。对于其他双连接或多连接的情况，未来也可能引入一个空口针对SCG的配置的全配置指示。本方案同样适用。
一种可选设计中，当CU-DU构成的gNB作为辅基站时(CU代表该辅基站与其他网元通信)，CU发送第三全配置指示给主基站，以便主基站在其RRC重配置消息中携带辅基站全配置指示(具体可以为：en-DC-release指示或scg-ConfigReleaseNR指示)。
一种可选设计中，CU向UE发送该第二指示和/或RRC重配置消息(携带该第二指示)，具体可以是CU通过DU发送给UE，比如CU通过和DU之间的F1接口将该第二指示和/或RRC重配置消息发送给DU，DU在通过空口发送给UE，DU在发送该第二指示和/或RRC重配置消息给UE时，可以用不解析消息内容的方式发送，DU也可以采用解析部分或者全部消息内容的方式来发送，此处不做限定。
一种可选设计中，当基站具有如图3所示的系统架构时，即集中式单元CU包含集中式单元控制面(CU-CP)和集中式单元用户面(CU-UP)时，前述实施例及其任一种设计中CU的功能可以由CU-CP来执行，CU-CP和DU之间的操作和前述实施例及其任一种设计中的CU和DU之间的操作类似。以下通过简要的方式对设计方案进行描述，包括：
可选操作1：CU-CP将SCG的参考配置信息发送给DU。本操作具体可参考操作401。
可选操作2：DU将全配置的小区组配置和/或第一指示发送给CU-CP；本操作具体可参考操作402。
可选操作3：CU-CP将SCG的参考配置信息发送给CU-UP。
基于图3的系统架构，一种可选设计中，CU-CP在E1接口消息(例如UE context setup request或者UE context modification request消息)中增加第四指示，比如该第四指示可以是 第四全配置指示，该指示用于通知CU-UP产生全配置的无线承载的配置信息(具体可以为：radioBearerConfig)。
基于图3的系统架构，一种可选设计中，还可以通过隐式的方法指示CU-UP执行全配置，例如，CU-CP不发送SCG的参考配置信息(具体可以为SCG-ConfigInfo)或者CU-CP发送的SCG的参考配置信息(具体可以为SCG-ConfigInfo)中不包含部分或者不包含全部SCG配置，则可以触发CU-UP执行全配置操作。还例如，若CU-UP收到消息中(如UE context setup request message)包含E-URTAN服务质量(quality of servie，QoS)信息，则CU-UP可以获知该DU所在的基站执行EN-DC，该CP-UP所在的基站是辅基站，可选的，此时若该CP-UP未收到SCG的参考配置信息(具体可以为SCG-ConfigInfo)或者CU-CP发送的SCG的参考配置信息(具体可以为SCG-ConfigInfo)中不包含部分或者不包含全部SCG配置，则可以触发CU-UP产生全配置的无线承载的配置信息(具体可以为：radioBearerConfig)。
可选操作4：CU-UP将全配置的无线承载的配置信息(具体可以为：radioBearerConfig)和/或第五指示发送给CU-CP。该第五指示可用于通知CU-CP该CU-UP执行了全配置的情况，比如该第五指示可以是第五全配置指示(具体形式可以为：full Config)，CU-UP将该第五全配置指示发送给CU-CP，例如，CU-UP可以在E1接口上的消息或者CU-UP给CU-CP发的上行数据包中携带该第五全配置指示发送给CU-CP，举例如，CU-UP可以在E1AP消息中的如下类型消息中的至少一个中携带该第五全配置指示：UE上下文建立响应(UE context setup response)消息，UE上下文修改响应消息(UE context modification response)，具体通过哪些类型的消息将该第五全配置指示发送给CU-CP，此处不做限定。
一种可选设计中，若存在CU-UP无法正确解析来自CU-CP的该SCG的配置信息的情况，CU-UP产生全配置的无线承载的配置信息(如radioBearerConfig)，具体包含SDAP和/或PDCP配置。
可选操作5：CU-CP向UE发送第二指示。
一种可选设计中，CU-CP基于CU-UP发送的该全配置的无线承载的配置信息(如radioBearerConfig)和/或来自于DU的该全配置的小区组的配置信息(如CellGroupConfig)生成基于全配置的一个控制消息，该控制消息可以是RRC重配置(具体可以为：RRCreconfiguraiton)消息。其中，该无线承载的配置信息可以包括SDAP和PDCP的配置信息中的至少一种。可选的，CU-CP收到DU发送的第一指示(如该第一全配置指示)和/或CU-UP发送的第五指示(如该第五全配置指示)后产生基于全配置的一个控制消息，例如RRC重配置消息，可选的，该RRC重配置消息包括CU-UP发送的该全配置的无线承载的配置信息和/或来自于DU的该全配置的小区组的配置信息。或者该CU-UP发送的全配置的无线承载的配置信息和/或该来自于DU的该全配置的小区组的配置信息可以通过MN和SN之间接口上的控制消息向UE发送。
本可选操作5中所需的其他过程，还可参考操作403。
前述实施例中对操作进行了顺序编号，但可理解的是，该顺序编号仅为了便于行文，并不意味着必须按照顺序编号来依次执行操作。在一种可选设计中，上述操作顺序可以根据需要发生变化，例如CU-CP可以先和CU-UP交互，再和DU交互，则按照操作1，操作3，操作4，操作2，以及操作5的顺序执行。此处不做限定。
一种可选设计中，CU-UP在物理上可以和CU-CP，DU分开部署，也可以集中部署。例如存在CU-CP，CU-UP，DU三个在物理上全部单独部署，或者CU-CP和DU在物理上集中部署，但是CU-UP单独部署，或者CU-CP和CU-UP在物理上集中部署，但是DU单独部署，或者CU-CP单独部署，CU-UP和DU集中部署等可能情况。
以上所示出的任一种设计，可以理解为针对特定场景或者特定技术问题而设计的技术方案，但并不能理解为实施本申请所记载技术内容所必须，其中的任一种设计可根据需要和其他设计相结合实施，以更有针对性的解决特定的客观技术问题。
一种可选设计中，在本申请实施例中，分布式单元DU具有RLC，MAC和PHY协议层 的功能，集中式单元CU具有RRC，SDAP和/或PDCP协议层的功能，DU和CU所具有的协议层共同构成了基站所具有的RRC，SDAP，PDCP，RLC，MAC以及PHY或者RRC，PDCP，RLC，MAC以及PHY协议层架构设置。当然，在基站中对CU和DU之间的协议层划分也可以有其他的方式，举例如，DU具有MAC和PHY，则CU具有RRC，SDAP，PDCP和RLC或RRC，PDCP和RLC，此处不做限定。DU在物理上可以和射频系统为一个通信设备的两个部分从而实现两者集成在一起，所述DU和CU也可以物理上作为同属于一个通信设备的部分从而实现两者集成在一起，或者，射频系统和DU以及CU物理上也可以作为同属于一个网络节点的部分从而实现三者可以集成在一起。
可以理解的是，对于前述实施例所涉及的CU，DU，CP，以及UP，可通过具有处理器和通信接口的硬件平台执行程序指令来分别实现其在本申请前述实施例中任一设计中涉及的功能，基于此，如图5所示出的，本申请实施例提供了一种通信设备500的示意性框图，所述通信设备500包括：
至少一个处理器501，可选包括通信接口502，该通信接口用于支持该通信设备500和其他设备进行通信交互；当程序指令在所述至少一个处理器501中执行时，本申请前述实施例任一设计中在如下任一设备上操作的功能得以实现：CU，DU，CP以及UP。一种可选设计中，该通信设备500还可以包含存储器503，以存储实现上述设备功能所必须的程序指令或者程序执行过程中所产生的过程数据。可选的，该通信设备500还可以包含内部的互联线路，以实现该至少一个处理器501，通信接口502以及存储器503之间的通信交互。该至少一个处理器501可以考虑通过专用处理芯片、处理电路、处理器或者通用芯片实现。例如，对于实施例中涉及的DU中PHY功能的全部或者部分的处理，或者涉及的F1口或者E1口上的全部或者部分的协议通信功能，可以在该至少一个处理器中设置专用电路/芯片来实现，当然也可以通过该至少一个处理器501中设置的通用处理器执行具有PHY功能，F1口或者E1口通信功能相关的程序指令来实现；又例如，对于本申请实施例涉及设备中的MAC层，RLC层，PDCP层，SDAP层以及RRC层的相关功能的全部或者部分处理，该至少一个处理器501可以包含通信处理芯片，通过执行MAC层，RLC层，PDCP层，SDAP层以及RRC层的相关功能的程序指令来实现。可以理解的是，本申请实施例描述的各种设计涉及的的方法，流程，操作或者步骤，能够以一一对应的方式，通过计算机软件，电子硬件，或者计算机软件和电子硬件的结合来一一对应实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件，比如，考虑通用性好成本低软硬件解耦等方面，可以采纳执行程序指令的方式来实现，又比如，考虑系统性能和可靠性等方面，可以采纳使用专用电路来实现。普通技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，此处不做限定。
该通信接口502，通常具有为两个通信对端之间执行进行信息交互的功能，对于通信对端之间执行的是有线形式的信息交互的情况，通信接口可以设计成接口电路，或者包含该接口电路的硬件模块，以支持通信对端之间进行的有线形式的通信交互，比如本申请中涉及的DU和CU之间的F1口，CP和UP之间的E1口的通信功能，可以采纳这种形式的接口设计；对于通信对端之间执行的是无线形式的信息交互的情况，通信接口可以是具有射频收发功能的接口电路，或者是包含该具有射频收发功能的接口电路的硬件系统，比如在DU和UE之间进行无线通信时，那么DU和UE的通信接口可以采纳这种设计。
可选的，对于CU，DU，CP或者UP的实现，也可以通过采用通用硬件平台(具有处理资源，存储资源)直接或者间接执行实施例相关设计的实现性程序指令来完成CU，DU，CP或者UP在本申请实施例各设计中的功能。一种实际部署方式可以是，CU，CP或者UP可以和核心网设备就近，或者协同部署，物理上可以分开也可以合一；CU，CP或者UP的功能也可以作为核心网设备的一部分。
本申请实施例还提供了一种计算机程序产品，该计算机程序产品具有程序指令，当该程序指令被直接或者间接执行时，比如，在前述实施例中的通信设备500中被执行时，使 得本申请实施例任一设计中在如下任一设备的功能得以实现：CU，CP，UP以及DU。可以理解的是，所述程序指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述程序指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。程序指令被执行时，考虑到具体的网络设备中一般包括硬件层、运行在硬件层之上的操作系统层和或中间层，与本申请实施例相关的程序指令被执行时，往往经过多层软件的调用和执行，因此该程序指令在硬件设备(通用处理电路或者专用处理电路)可以是一种间接的执行过程。
本申请实施例还提供了一种芯片系统，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得如第一方面及其任一所述的设计中在如下任一设备上的功能得到实现：CU，DU，CP，以及UP。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (27)

  1. 一种通信方法，其特征在于，包括：
    分布式单元DU向集中式单元CU发送全配置的小区组的配置信息和/或第一指示，所述第一指示用于通知所述集中式单元CU所述分布式单元DU执行了全配置的情况。
  2. 如权利要求1所述的通信方法，其特征在于，包括：
    所述分布式单元DU和所述集中式单元CU构成多连接场景中的辅基站，所述分布式单元将来自于CU的第二指示发送给终端设备，所述第二指示用于通知所述终端设备执行所述辅基站配置更新操作。
  3. 如权利要求1或2所述的通信方法，其特征在于，包括：
    所述分布式单元DU将来自于所述集中式单元CU的无线资源控制重配置消息发送给所述终端设备，所述无线资源控制重配置消息包含全配置的无线承载的配置信息和/或全配置的小区组的配置信息；
    其中，
    所述全配置的无线承载的配置信息包括业务数据适配协议层的配置信息和/或分组数据汇聚层协议层的配置信息，所述全配置的无线承载的配置信息是所述集中式单元CU基于所述第一指示触发生成；
    所述全配置的小区组的配置信息包括无线链路控制层的配置信息，媒体接入控制层的配置信息，或者物理层的配置信息中的任一种或任多种。
  4. 如权利要求1-3中任一所述的通信方法，其特征在于，所述全配置的小区组的配置信息和所述第一指示被包含在所述分布式单元DU和所述集中式单元CU之间通信接口上定义的一个消息中发送，或者所述全配置的小区组的配置信息和所述第一指示被携带在所述分布式单元DU和所述集中式单元CU之间的上行数据包中发送。
  5. 如权利要求1-4中任一所述的通信方法，其特征在于，所述分布式单元DU向所述集中式单元CU发送全配置的小区组的配置信息和/或第一指示，满足如下中任一种或任多种：
    所述分布式单元DU接收到来自于所述集中式单元CU的辅小区组SCG的参考配置信息，所述分布式单元DU不能正确解析所述辅小区组SCG的参考配置信息中的辅小区组SCG的配置信息；
    所述分布式单元DU接收到来自于所述集中式单元CU的辅小区组SCG的参考配置信息，所述辅小区组SCG的参考配置信息未包含全部或部分辅小区组SCG的配置信息；或者，
    所述分布式单元DU接收到来自于所述集中式单元的指示，所述指示用于通知所述分布式单元DU需要执行全配置。
  6. 一种通信方法，其特征在于，包括：
    集中式单元CU接收来自于分布式单元DU的全配置的小区组的配置信息和/或第一指示，所述第一指示用于通知所述集中式单元CU所述分布式单元DU执行了全配置的情况。
  7. 如权利要求6所述的通信方法，其特征在于，包括：
    所述分布式单元DU和所述集中式单元CU构成多连接场景中的辅基站，所述集中式单元CU通过所述分布式单元DU将第二指示发送给终端设备，所述第二指示用于通知所述终端设备执行所述辅基站配置更新操作。
  8. 如权利要求6或7所述的通信方法，其特征在于，包括：
    所述集中式单元CU通过所述分布式单元DU将无线资源控制重配置消息发送给所述终端设备，所述无线资源控制重配置消息包含全配置的无线承载的配置信息和/或全配置的小区组的配置信息；
    其中，
    所述全配置的无线承载的配置信息包括业务数据适配协议层的配置信息和/或分组数据汇聚层协议层的配置信息；所述全配置的无线承载的配置信息是所述集中式单元CU收到所述第一指示触发生成；
    所述全配置的小区组的配置信息包括无线链路控制层的配置信息，媒体接入控制层的配置信息，或者物理层的配置信息中的任一种或任多种。
  9. 如权利要求6-8中任一所述的通信方法，其特征在于，所述全配置的小区组的配置信息和所述第一指示被包含在所述集中式单元CU和所述分布式单元DU之间通信接口上定义的一个消息中接收，或者所述全配置的小区组的配置信息和所述第一指示被携带在所述集中式单元CU和所述分布式单元DU之间的上行数据包中接收。
  10. 如权利要求6-9中任一所述的通信方法，其特征在于，包括：
    所述集中式单元CU收到来自于所述分布式单元DU的所述全配置的小区组的配置信息和/或所述第一指示，满足如下中任一种或任多种：
    所述集中式单元向所述分布式单元DU发送辅小区组SCG的参考配置信息，所述辅小区组SCG的参考配置信息中的辅小区组SCG的配置信息不能被所述分布式单元DU正确解析；
    所述集中式单元CU接收到来自于主基站的辅小区组SCG的参考配置信息，所述集中式单元向所述分布式单元DU发送辅小区组SCG的参考配置信息，所述辅小区组SCG的参考配置信息中未包含全部或者部分所述辅小区组SCG的配置信息；或者，
    所述集中式单元CU向所述分布式单元DU发送指示，所述指示用于通知所述分布式单元DU需要执行全配置。
  11. 如权利要求1-10中任一所述的通信方法，其特征在于，
    所述分布式单元DU具有：无线链路控制层，媒体接入控制层，以及物理层；
    所述集中式单元CU具有：无线资源控制层，业务数据适配协议层，以及分组数据汇聚层协议层。
  12. 一种通信设备，其特征在于，所述通信设备包括：至少一个处理器和通信接口，所述通信接口用于所述通信设备与其他通信设备进行信息交互，当程序指令在所述至少一个处理器中执行时，使得所述通信设备实现如权利要求1-11中任一所述的方法中在如下任一设备上的功能：所述分布式单元DU和所述集中式单元CU。
  13. 一种计算机程序存储介质，其特征在于，所述计算机程序存储介质具有程序指令，当所述程序指令被直接或者间接执行时，使得如权利要求1-11中任一所述的方法中在如下任一设备上的功能得以实现：所述分布式单元DU和所述集中式单元CU。
  14. 一种芯片系统，其特征在于，所述芯片系统包括至少一个处理器，当程序指令在所述至少一个处理器中执行时，使得如权利要求1-11中任一所述的方法中在如下任一设备上的功能得以实现：所述分布式单元DU和所述集中式单元CU。
  15. 一种通信系统，其特征在于，所述通信系统包括：如权利要求12所述的通信设备。
  16. 一种通信装置，应用于分布式单元DU，其特征在于，所述通信装置包括：
    用于向集中式单元CU发送全配置的小区组的配置信息和/或第一指示的装置，
    所述第一指示用于通知所述CU所述通信设备执行了全配置的情况。
  17. 如权利要求16所述的通信装置，其特征在于，所述分布式单元DU和所述集中式单元CU构成多连接场景中的辅基站，所述通信装置包括：用于将来自于所述CU的第二指示发送给终端设备的装置，所述第二指示用于通知所述终端设备执行所述辅基站配置更新操作。
  18. 如权利要求16或17所述的通信装置，其特征在于，所述通信装置包括：
    用于将来自于所述CU的无线资源控制重配置消息发送给所述终端设备的装置，所述无线资源控制重配置消息包含全配置的无线承载的配置信息和/或全配置的小区组的配置 信息；
    其中，
    所述全配置的无线承载的配置信息包括业务数据适配协议层的配置信息和/或分组数据汇聚层协议层的配置信息，所述全配置的无线承载的配置信息是所述集中式单元CU基于所述第一指示触发生成；
    所述全配置的小区组的配置信息包括无线链路控制层的配置信息，媒体接入控制层的配置信息，或者物理层的配置信息中的任一种或任多种。
  19. 如权利要求16-18中任一所述的通信装置，其特征在于，所述全配置的小区组的配置信息和所述第一指示被包含在所述分布式单元DU和所述集中式单元CU之间通信接口上定义的一个消息中发送，或者所述全配置的小区组的配置信息和所述第一指示被携带在所述分布式单元DU和所述集中式单元CU之间的上行数据包中发送。
  20. 如权利要求16-19中任一所述的通信装置，其特征在于，所述通信装置向所述集中式单元CU发送全配置的小区组的配置信息和/或第一指示，满足如下中任一种或任多种：
    所述通信装置接收到来自于所述集中式单元CU的辅小区组SCG的参考配置信息，所述通信装置不能正确解析所述辅小区组SCG的参考配置信息中的辅小区组SCG的配置信息；
    所述通信装置接收到来自于所述集中式单元CU的辅小区组SCG的参考配置信息，所述辅小区组SCG的参考配置信息未包含全部或部分辅小区组SCG的配置信息；或者，
    所述通信装置接收到来自于所述集中式单元CU的指示，所述指示用于通知所述通信装置DU需要执行全配置。
  21. 一种通信装置，应用于集中式单元CU，其特征在于，所述通信装置包括：
    用于接收来自于分布式单元DU的全配置的小区组的配置信息和/或第一指示的装置，所述第一指示用于通知所述集中式单元CU所述分布式单元DU执行了全配置的情况。
  22. 如权利要求21所述的通信装置，其特征在于，所述分布式单元DU和所述集中式单元CU构成多连接场景中的辅基站，所述通信装置包括：用于通过所述分布式单元DU将第二指示发送给终端设备的装置，所述第二指示用于通知所述终端设备执行所述辅基站配置更新操作。
  23. 如权利要求21或22所述的通信装置，其特征在于，所述通信装置包括：用于通过所述分布式单元DU将无线资源控制重配置消息发送给所述终端设备的装置，所述无线资源控制重配置消息包含全配置的无线承载的配置信息和/或全配置的小区组的配置信息；
    其中，
    所述全配置的无线承载的配置信息包括业务数据适配协议层的配置信息和/或分组数据汇聚层协议层的配置信息；所述全配置的无线承载的配置信息是所述集中式单元CU收到所述第一指示触发生成；
    所述全配置的小区组的配置信息包括无线链路控制层的配置信息，媒体接入控制层的配置信息，或者物理层的配置信息中的任一种或任多种。
  24. 如权利要求21-23中任一所述的通信装置，其特征在于，所述全配置的小区组的配置信息和所述第一指示被包含在所述集中式单元CU和所述分布式单元DU之间通信接口上定义的一个消息中接收，或者所述全配置的小区组的配置信息和所述第一指示被携带在所述集中式单元CU和所述分布式单元DU之间的上行数据包中接收。
  25. 如权利要求21-24中任一所述的通信装置，其特征在于，所述集中式单元CU收到来自于所述分布式单元DU的所述全配置的小区组的配置信息和/或所述第一指示，满足如下中任一种或任多种：
    所述集中式单元向所述分布式单元DU发送辅小区组SCG的参考配置信息，所述辅小区组SCG的参考配置信息中的辅小区组SCG的配置信息不能被所述分布式单元DU正确解析；
    所述集中式单元CU接收到来自于主基站的辅小区组SCG的参考配置信息，所述集中式单元向所述分布式单元DU发送辅小区组SCG的参考配置信息，所述辅小区组SCG的参考配置信息中未包含全部或者部分所述辅小区组SCG的配置信息；或者，
    所述集中式单元CU向所述分布式单元DU发送指示，所述指示用于通知所述分布式单元DU需要执行全配置。
  26. 如权利要求16-25中任一所述的通信装置，其特征在于，
    所述分布式单元DU具有：无线链路控制层，媒体接入控制层，以及物理层；
    所述集中式单元CU具有：无线资源控制层，业务数据适配协议层，以及分组数据汇聚层协议层。
  27. 一种计算机程序产品，其特征在于，所述计算机程序产品包含程序指令，当所述程序指令被直接或者间接执行时，使得如权利要求1-11中任一所述的方法中在如下任一设备上的功能得以实现：所述分布式单元DU和所述集中式单元CU。
PCT/CN2018/124826 2017-12-29 2018-12-28 一种通信方法，设备及其系统 WO2019129197A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
KR1020207021487A KR102357070B1 (ko) 2017-12-29 2018-12-28 통신 방법, 디바이스 및 시스템
EP18896533.9A EP3734908A4 (en) 2017-12-29 2018-12-28 COMMUNICATION METHOD, DEVICE AND SYSTEM
JP2020536218A JP7150854B2 (ja) 2017-12-29 2018-12-28 通信方法、デバイス、およびシステム
BR112020012890A BR112020012890A8 (pt) 2017-12-29 2018-12-28 método de comunicação, aparelho, mídia de armazenamento legível por computador, e sistema
US16/912,122 US20200329365A1 (en) 2017-12-29 2020-06-25 Communication method, device, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711483393.6A CN109995553B (zh) 2017-12-29 2017-12-29 一种通信方法，设备及其系统
CN201711483393.6 2017-12-29

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/912,122 Continuation US20200329365A1 (en) 2017-12-29 2020-06-25 Communication method, device, and system

Publications (1)

Publication Number Publication Date
WO2019129197A1 true WO2019129197A1 (zh) 2019-07-04

Family

ID=67066634

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/124826 WO2019129197A1 (zh) 2017-12-29 2018-12-28 一种通信方法，设备及其系统

Country Status (7)

Country Link
US (1) US20200329365A1 (zh)
EP (1) EP3734908A4 (zh)
JP (1) JP7150854B2 (zh)
KR (1) KR102357070B1 (zh)
CN (1) CN109995553B (zh)
BR (1) BR112020012890A8 (zh)
WO (1) WO2019129197A1 (zh)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112867037A (zh) * 2017-08-10 2021-05-28 中兴通讯股份有限公司 一种连接方法、配置更新方法、控制面设备和用户面设备
EP3813433B1 (en) * 2018-06-21 2024-05-15 Ntt Docomo, Inc. Communication device and communication method
US11363656B2 (en) * 2019-08-14 2022-06-14 Qualcomm Incorporated Techniques for indicating full configuration to a secondary node in dual connectivity
CN112448932B (zh) * 2019-09-02 2022-09-27 成都鼎桥通信技术有限公司 消息处理的方法及装置
CN112788619B (zh) * 2019-11-06 2023-04-14 大唐移动通信设备有限公司 一种辅小区组配置方法、主基站、辅基站和终端
CN110913409B (zh) * 2019-11-21 2022-08-26 中国联合网络通信集团有限公司 网络配置方法、装置及系统
CN113141284B (zh) * 2020-01-17 2022-07-19 大唐移动通信设备有限公司 一种接入网设备及数据传输方法
EP4090066A4 (en) * 2020-02-03 2023-01-04 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND APPARATUS
CN111586815B (zh) * 2020-04-28 2022-05-27 珠海格力电器股份有限公司 一种功耗优化方法、装置、电子设备及存储介质
CN113766461B (zh) * 2020-06-01 2024-09-06 中国电信股份有限公司 用户面数据处理方法和基站
WO2022082688A1 (zh) * 2020-10-22 2022-04-28 华为技术有限公司 一种通信方法、装置及系统
CN116965142A (zh) * 2021-03-19 2023-10-27 中兴通讯股份有限公司 用于无线通信中的配置的方法

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105101312A (zh) * 2014-05-15 2015-11-25 中兴通讯股份有限公司 一种上行数据处理的方法及装置
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102547848B (zh) * 2011-01-04 2015-08-05 华为技术有限公司 一种处理业务数据流的方法和装置
CN104780017B (zh) * 2014-01-10 2018-07-24 中国移动通信集团公司 一种数据处理方法及装置
KR101571055B1 (ko) * 2014-07-29 2015-11-23 (주)씨맥스와이어리스 분산형 무선 기지국
GB2528913B (en) * 2014-08-04 2017-03-01 Samsung Electronics Co Ltd Signalling in dual connectivity mobile communication networks
US10462841B2 (en) * 2015-01-14 2019-10-29 Nokia Solutions And Networks Oy Efficient secondary cell group change procedure for dual connectivity
US20170295524A1 (en) * 2016-04-08 2017-10-12 Nokia Technologies Oy Apparatuses and methods for indication of full configuration in handover signaling
US10251099B2 (en) * 2016-07-22 2019-04-02 Lg Electronics Inc. Method and apparatus for enhancing inter-MeNB handover without SeNB change in wireless communication system
US10470204B2 (en) * 2016-08-10 2019-11-05 Ofinno, Llc Multiple semi persistent scheduling in a wireless network
CN107734568A (zh) * 2016-08-11 2018-02-23 北京三星通信技术研究有限公司 在无线通信中支持用户设备移动的方法、装置及设备
CN106538037B (zh) * 2016-09-26 2019-10-15 北京小米移动软件有限公司 无线承载的配置方法、装置及系统
CN109005601B (zh) * 2017-06-07 2021-02-09 宏达国际电子股份有限公司 处理次要节点改变中的小区群组配置的通信装置与基站
US10805856B2 (en) * 2017-09-22 2020-10-13 Telefonaktiebolaget Lm Ericsson (Publ) Methods and units in a network node for handling communication with a wireless device

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105101312A (zh) * 2014-05-15 2015-11-25 中兴通讯股份有限公司 一种上行数据处理的方法及装置
CN106162730A (zh) * 2016-07-12 2016-11-23 上海华为技术有限公司 一种通信的方法、设备及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3734908A4

Also Published As

Publication number Publication date
CN109995553A (zh) 2019-07-09
BR112020012890A8 (pt) 2020-12-22
EP3734908A4 (en) 2021-03-03
US20200329365A1 (en) 2020-10-15
KR20200098686A (ko) 2020-08-20
BR112020012890A2 (pt) 2020-12-08
KR102357070B1 (ko) 2022-02-08
EP3734908A1 (en) 2020-11-04
JP7150854B2 (ja) 2022-10-11
CN109995553B (zh) 2022-03-25
JP2021508984A (ja) 2021-03-11

Similar Documents

Publication Publication Date Title
WO2019129197A1 (zh) 一种通信方法，设备及其系统
WO2019096281A1 (zh) 一种通信方法，通信设备及其通信系统
WO2019137434A1 (zh) 一种通信方法，设备及其系统
WO2019137471A1 (zh) 通信方法、接入网设备和终端设备
EP3624530A1 (en) Information processing method and related apparatus
TWI733216B (zh) 無效協定資料單元會話之處理方法及其使用者設備
WO2018171398A1 (zh) QoS处理方法和设备
CN112889258B (zh) 一种通信方法及装置
WO2019242749A1 (zh) 一种切换方法及装置
TWI768291B (zh) 處理操作錯誤的方法及使用者設備
WO2022041249A1 (zh) 一种节点的切换方法以及相关设备
EP4185005A1 (en) Communication method and communication apparatus for integrated access and backhaul (iab) system
WO2020192438A1 (zh) 通信方法、装置及系统
WO2021238318A1 (zh) 一种通信方法及装置
WO2019057042A1 (zh) 一种用户设备跟踪方法和设备
WO2021056703A1 (zh) 信息更新方法、设备及系统
US20190082500A1 (en) Ran Server, Wireless Communications System, And Terminal Attach Method
US20210204341A1 (en) Association handling method and device
WO2021062677A1 (zh) 通信方法和装置
CN105612809B (zh) 信息交互装置、基站和通信系统
EP4221338A1 (en) Communication method for integrated access and backhaul (iab) system, and related device
WO2023246746A1 (zh) 一种通信方法及相关设备
WO2024169931A1 (zh) 一种条件主辅小区变更方法及装置
WO2020220795A1 (zh) 一种数据传输方法及装置
CN117014980A (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: 18896533

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020536218

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20207021487

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018896533

Country of ref document: EP

Effective date: 20200728

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112020012890

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112020012890

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20200624