WO2018059147A1 - 用于建立/重配置数据承载的方法和设备 - Google Patents

用于建立/重配置数据承载的方法和设备 Download PDF

Info

Publication number
WO2018059147A1
WO2018059147A1 PCT/CN2017/097490 CN2017097490W WO2018059147A1 WO 2018059147 A1 WO2018059147 A1 WO 2018059147A1 CN 2017097490 W CN2017097490 W CN 2017097490W WO 2018059147 A1 WO2018059147 A1 WO 2018059147A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
drb
scg
reconfiguration
mcg
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2017/097490
Other languages
English (en)
French (fr)
Inventor
肖芳英
刘仁茂
山田升平
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sharp Corp
Original Assignee
Sharp Corp
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 Sharp Corp filed Critical Sharp Corp
Priority to US16/337,340 priority Critical patent/US11057958B2/en
Publication of WO2018059147A1 publication Critical patent/WO2018059147A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • 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/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
    • H04W84/20—Leader-follower arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • 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/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • This application relates to the field of wireless communication technologies. More specifically, it relates to a method and apparatus for establishing/reconfiguring a data bearer.
  • NTT DOCOMO proposed a new research project on 5G technology standards (see Non-patent literature: RP-160671) :New SID Proposal: Study on New Radio Access Technology), and approved.
  • the goal of the research project is to develop a new wireless (New Radio: NR) access technology to meet all 5G application scenarios, requirements and deployment environments.
  • NR mainly has three application scenarios: Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC) and Ultra Reliable and Low Latency Communications (URLLC).
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • URLLC Ultra Reliable and Low Latency Communications
  • the standardization of NR is carried out in two phases: the first phase of standardization will be completed in mid-2018; the second phase of standardization will be completed by the end of 2019.
  • the first-stage standard specification is forward-compatible with the second-stage standard specification, while the second-stage standard specification is based on the first-stage standard specification and meets all the requirements of the 5G NR technical standard.
  • the deployment scenario shown in Figure 1-4 is included in the NR dual connectivity deployment scenario reached at the 3GPP RAN2 #95 conference in August 2016.
  • an NR base station (NR Node B, abbreviated as gNB.
  • the gNB is a logical node, and the logical node is responsible for wireless transmission/reception in one or more cells to/from the user equipment UE) as a master.
  • the base station (called MgNB), that is, the control plane connection is between the MgNB and the next-generation core network (called NextGen Core).
  • An Enhanced Long Term Evolution (eLTE) base station (referred to as an eLTE eNB) serves as a secondary base station.
  • eLTE Enhanced Long Term Evolution
  • the user plane data stream is transmitted through the next generation core network through the NR base station and the eLTE eNB; specifically, there are four user plane data transmission modes: mode a1, user plane data is transmitted between the gNB and the next generation core network, and resources provided by the gNB are utilized.
  • the bearer DRB is called an NR-eLTE Master Cell Group (MCG) bearer; in a mode a2, the user plane data is transmitted between the eLTE eNB and the next-generation core network and utilizes resources provided by the eLTE eNB (the corresponding data bearer is called NR-eLTE secondary cell group (SCG) bearer); mode a3, user plane data is transmitted between the gNB and the next generation core network, and part of the data is transmitted by using the gNB radio resource, and the other data is transmitted by gNB and eLTE.
  • MCG NR-eLTE Master Cell Group
  • the inter-eNB interface is sent to/from the eLTE eNB and uses the radio resource transmission of the eLTE eNB (the corresponding data bearer is called NR-eLTE MCG split bearer); in mode a4, the user plane data is transmitted between the eLTE eNB and the next-generation core network. Part of the data is directly transmitted by the radio resource of the eLTE eNB, and the other data is transmitted to/from the NR gNB through the interface between the gNB and the eLTE eNB and transmitted by using the radio resource of the NR gNB (the corresponding data bearer is called the NR-eLTE SCG split bearer). ). In modes a3 and a4, the user plane data utilizes resources provided by the gNB and the eLTE eNB simultaneously via the next generation core network.
  • the primary base station MgNB and the secondary base station SgNB are both gNBs, that is, the control plane connection is performed between the MgNB and the next generation core network, and the user plane data stream is transmitted through the next generation core network through the MgNB and the SgNB.
  • mode b1 user plane data is transmitted between the MgNB and the next generation core network and utilized for resource transmission provided by the MgNB (the corresponding data bearer is called NR-NR MCG bearer);
  • mode b2 User plane data is transmitted between the SgNB and the next generation core network and utilizes resources provided by the secondary base station SgNB (the corresponding data bearer is called NR-NR SCG bearer);
  • mode b3 user plane data is transmitted between the MgNB and the next generation core network And a part of the data is transmitted by using the radio resource of the primary base station MgNB, and another part of the data is sent to/from the SgNB through the interface between the primary base station MgNB and the secondary base station SgNB and transmitted by using the wireless resource of the SgNB (the corresponding data bearer is called NR-NR).
  • the user plane data is transmitted between the SgNB and the next generation core network, part of the data is directly transmitted by the SgNB wireless resource, and the other data is sent to/from the MgNB through the interface between the SgNB and the MgNB and transmitted by using the wireless resource of the MgNB ( The corresponding data bearer is called NR-NR SCG split bearer).
  • the user plane data is simultaneously transmitted by the resources provided by the MgNB and the SgNB via the next generation core network.
  • a long-term evolved base station LTE eNB is used as a primary base station (referred to as an LTE MeNB), that is, a control plane connection is performed between an LTE eNB and a core network (referred to as an EPC).
  • the gNB acts as a secondary base station.
  • the user plane data stream is transmitted via the EPC through the gNB and the LTE eNB. Specifically, there are four uses.
  • the data transmission mode of the household data mode c1, the user plane data is transmitted between the LTE eNB and the EPC, and the resources provided by the LTE eNB are used (the corresponding data bearer is called LTE-NR MCG bearer); the mode c2, the user plane data is in the gNB and The EPC transmits and uses the resource transmission provided by the gNB (the corresponding data bearer is called LTE-NR SCG bearer); the mode c3, the user plane data is transmitted between the LTE eNB and the EPC, and a part of the data is transmitted by using the radio resource of the LTE eNB, The other data is transmitted to/from the gNB through the interface between the gNB and the LTE eNB and transmitted by the gNB (the corresponding data bearer is called the LTE-NR MCG split bearer).
  • the user plane data is transmitted between the gNB and the EPC, part of the data is directly transmitted by using the radio resource of the gNB, and the other part is transmitted to/from the LTE eNB through the interface between the gNB and the LTE eNB, and the radio resource is transmitted by using the LTE eNB (
  • the corresponding data bearer is called LTE-NR SCG split bearer).
  • the user plane data is simultaneously transmitted by the resources provided by the gNB and the LTE eNB via the EPC.
  • the eLTE eNB functions as a primary base station (referred to as an eLTE MeNB), that is, a control plane connection is performed between the eLTE eNB and the next generation core network.
  • the gNB acts as a secondary base station.
  • the user plane data stream is transmitted through the next generation core network through the gNB and the eLTE eNB.
  • mode d1 user plane data is transmitted between the eLTE eNB and the next generation core network, and resources provided by the eLTE eNB are used (the corresponding data bearer is called an eLTE-NR MCG bearer); D2, user plane data is transmitted between the gNB and the next generation core network and utilizes resources provided by the gNB (the corresponding data bearer is called eLTE-NR SCG bearer); mode d3, user plane data is transmitted between the eLTE eNB and the next generation core network And a part of the data is transmitted by using the radio resource of the eLTE eNB, and another part of the data is sent to/from the gNB through the interface between the gNB and the eLTE eNB and transmitted by using the radio resource of the gNB (the corresponding data bearer is called the eLTE-NR MCG split bearer) .
  • the corresponding data bearer is called the eLTE-NR MCG split bearer
  • the user plane data is transmitted between the gNB and the next generation core network, and part of the data is directly transmitted by using the radio resource of the gNB, and the other part is sent to/from the eLTE eNB through the interface between the gNB and the eLTE eNB and using the eLTE eNB.
  • Radio resource transmission (the corresponding data bearer is called eLTE-NR SCG split bearer).
  • the user plane data is simultaneously transmitted by the resources provided by the gNB and the eLTE eNB via the next generation core network.
  • the present application provides a method for establishing/reconfiguring a data bearer, including: receiving a data bearer setup/reconfiguration request message, where the request message includes a data bearer identifier and a bearer type indication cell,
  • the data bearer identifier is used to identify a data bearer
  • the bearer type indicating cell is used to indicate a type of data bearer to be established/to be reconfigured; and the corresponding data bearer is established/reconfigured according to the request message.
  • the types of data bearers include a primary cell group MCG bearer, a secondary cell group SCG bearer, an MCG split bearer, and an SCG split bearer.
  • the data bearer setup/reconfiguration request message includes a radio resource control RRC reconfiguration message.
  • the RRC reconfiguration message includes RRC messages from two or more radio access technology RATs.
  • the data bearer setup/reconfiguration request message includes a cell indicating the type of the secondary base station.
  • a corresponding process for establishing/reconfiguring a data bearer is performed in accordance with the content of the cell used to indicate the secondary base station type.
  • a user equipment including: a receiving unit, configured to receive a data bearer setup/reconfiguration request message, where the request message includes a data bearer identifier and a bearer type indication cell, and the data bearer identifier
  • the bearer type indicating cell is used to indicate a type of data bearer to be established/to be reconfigured
  • the processing unit is configured to establish/reconfigure a corresponding data bearer according to the request message.
  • the types of data bearers include a primary cell group MCG bearer, a secondary cell group SCG bearer, an MCG split bearer, and an SCG split bearer.
  • the data bearer setup/reconfiguration request message includes a radio resource control RRC reconfiguration message.
  • the RRC reconfiguration message includes RRC messages from two or more radio access technology RATs.
  • the data bearer setup/reconfiguration request message includes a cell indicating the type of the secondary base station.
  • the processing unit is configured to perform a corresponding process for establishing/reconfiguring the data bearer according to the content of the cell indicating the type of the secondary base station.
  • a method for establishing/reconfiguring a data bearer comprising: Sending a data bearer setup/reconfiguration request message, where the request message includes a data bearer identifier and a bearer type indicating cell, where the data bearer identifier is used to identify a data bearer, and the bearer type indicating cell is used to indicate that the data bearer is to be established.
  • the type of data bearer to be reconfigured communicate using the corresponding data bearer for setup/reconfiguration.
  • the types of data bearers include a primary cell group MCG bearer, a secondary cell group SCG bearer, an MCG split bearer, and an SCG split bearer.
  • the data bearer setup/reconfiguration request message includes a radio resource control RRC reconfiguration message.
  • the RRC reconfiguration message includes RRC messages from two or more radio access technology RATs.
  • the data bearer setup/reconfiguration request message includes a cell indicating the type of the secondary base station.
  • a base station including: a sending unit, configured to send a data bearer setup/reconfiguration request message, where the request message includes a data bearer identifier and a bearer type indication cell, where the data bearer identifier is used by And identifying the data bearer, the bearer type indicating cell is used to indicate a type of data bearer to be established/to be reconfigured; and the communication unit is configured to communicate using a corresponding data bearer established/reconfigured.
  • the types of data bearers include a primary cell group MCG bearer, a secondary cell group SCG bearer, an MCG split bearer, and an SCG split bearer.
  • the data bearer setup/reconfiguration request message includes a radio resource control RRC reconfiguration message.
  • the RRC reconfiguration message includes RRC messages from two or more radio access technology RATs.
  • the data bearer setup/reconfiguration request message includes a cell indicating the type of the secondary base station.
  • FIG. 1 is a schematic diagram showing an NR-eLTE dual connectivity deployment scenario
  • Figure 2 shows a schematic diagram of an NR-NR dual connectivity deployment scenario
  • FIG. 3 is a schematic diagram showing an LTE-NR dual connectivity deployment scenario
  • FIG. 4 is a schematic diagram showing an eLTE-NR dual connectivity deployment scenario
  • FIG. 5 is a schematic diagram showing a radio protocol layer 2 entity involved in an LTE dual connectivity deployment manner
  • FIG. 6 shows a flow chart of a method for establishing/reconfiguring a data bearer in accordance with one embodiment of the present application
  • FIG. 7 shows a flow chart of a method for establishing/reconfiguring a data bearer in accordance with another embodiment of the present application
  • Figure 8 shows a block diagram of a user equipment in accordance with one embodiment of the present application.
  • Figure 9 shows a block diagram of a base station in accordance with one embodiment of the present application.
  • the present application takes a dual connection as an example, but the method described in this application is not limited to a dual connectivity scenario, and those skilled in the art can easily extend to a multi-connection scenario.
  • the present application is described by taking LTE, eLTE, NR, and corresponding core network and next generation core network as an example. It should be noted that the present application is not limited to the LTE, eLTE, NR, and corresponding core network and next generation core network, and may also be used in other wireless communication systems, such as a 6G wireless communication system.
  • a base station that connects a control plane to an EPC or a next-generation core network under dual connectivity is referred to as a primary base station MeNB, and may be an NR MgNB, an LTE MeNB, or an eLTE MeNB.
  • a base station whose control plane is not connected to the EPC or the next-generation core network (ie, is not the primary base station) but provides transmission resources for user plane data transmission is referred to as a secondary base station SeNB, and may be an NR SgNB, an LTE SeNB, or an eLTE SeNB.
  • the X-Y MCG bearer refers to a resource in which the MeNB is X, the SeNB is Y, and the bearer's radio protocol layer is located in X and is provided by X.
  • the X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB; the Y may be an NR SgNB, an LTE SeNB, or an eLTE SeNB.
  • the X-Y SCG bearer refers to the MeNB being X, the SeNB being Y, and the bearer's radio protocol layer being located in Y and utilizing the resources provided by Y.
  • the X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB; the Y may be an NR SgNB, an LTE SeNB, or an eLTE SeNB.
  • the XY MCG split bearer means that the primary base station is X, the secondary base station is Y, and the bearer's radio protocol layer is located in X and Y, and the user plane data of the EPC or the next-generation core network ends at X but is provided by X and Y at the same time. resource of.
  • the X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB; the Y may be an NR SgNB, an LTE SeNB, or an eLTE SeNB.
  • the XY SCG split bearer means that the primary base station is X, the secondary base station is Y, and the bearer's radio protocol layer is located in X and Y, and the user plane data of the EPC or the next-generation core network terminates at Y but is provided by X and Y at the same time. resource of.
  • the X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB;
  • the Y may be an NR SgNB, an LTE SeNB, or an eLTE SeNB.
  • the X MCG bearer means that the MeNB is X, and the SeNB may be an NR SgNB, an LTE SeNB or an eLTE SeNB.
  • the bearer's wireless protocol layer is located in X and utilizes the resources provided by X.
  • the X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB.
  • the X SCG bearer refers to the MeNB being X
  • the SeNB may be an NR SgNB, an LTE SeNB, or an eLTE SeNB.
  • the bearer's radio protocol layer is located in the SeNB and utilizes resources provided by the SeNB.
  • the X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB.
  • the X MCG split bearer refers to the MeNB being X
  • the SeNB may be an NR SgNB, an LTE SeNB, or an eLTE SeNB.
  • the bearer's radio protocol layer is located in the X and SeNB, and the user plane data with the EPC or the next generation core network ends at X and utilizes the resources provided by the X and SeNB.
  • the X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB.
  • the X SCG split bearer means that the MeNB is X
  • the SeNB may be an NR SgNB, an LTE SeNB or an eLTE SeNB.
  • the bearer's radio protocol layer is located in the X and SeNB, and the user plane data with the EPC or the next-generation core network terminates at the SeNB and utilizes resources provided by the X and SeNB at the same time.
  • the X may be an NR MgNB, an LTE MeNB, or an eLTE MeNB.
  • NR MCG bearer may include one or more of NR-eLTE MCG bearer, NR-NR MCG bearer, and NR-LTE MCG bearer. The UE may determine which of the listed bearers according to the secondary base station type.
  • LTE MCG bearer may include one or more of LTE-eLTE MCG bearer, LTE-NR MCG bearer, and LTE-LTE MCG bearer.
  • the UE may determine which of the listed bearers according to the secondary base station type.
  • eLTE MCG bearer may include one or more of an eLTE-eLTE MCG bearer, an eLTE-NR MCG bearer, and an eLTE-LTE MCG bearer.
  • the UE may determine which of the listed bearers according to the secondary base station type.
  • NR SCG bearer may include one or more of an NR-eLTE SCG bearer, an NR-NR SCG bearer, and an NR-LTE SCG bearer. The UE may determine which of the listed bearers according to the secondary base station type.
  • LTE SCG bearer may include one or more of LTE-eLTE SCG bearer, LTE-NR SCG bearer, and LTE-LTE SCG bearer.
  • the UE may determine which of the listed bearers according to the secondary base station type.
  • eLTE SCG bearer may include one or more of an eLTE-eLTE SCG bearer, an eLTE-NR SCG bearer, and an eLTE-LTE SCG bearer.
  • the UE may determine which of the listed bearers according to the secondary base station type.
  • NR MCG split bearer may include one or more of NR-eLTE MCG split bearer, NR-NR MCG split bearer, and NR-LTE MCG split bearer. The UE may determine which of the listed bearers according to the secondary base station type.
  • LTE MCG split bearer may include one or more of LTE-eLTE MCG split bearer, LTE-NR MCG split bearer, and LTE-LTE MCG split bearer.
  • the UE may determine which of the listed bearers according to the secondary base station type.
  • the eLTE MCG split bearer may include one or more of an eLTE-eLTE MCG split bearer, an eLTE-NR MCG split bearer, and an eLTE-LTE MCG split bearer.
  • the UE may determine which of the listed bearers according to the secondary base station type.
  • NR SCG split bearer may include one or more of NR-eLTE SCG split bearer, NR-NR SCG split bearer, NR-LTE SCG split bearer. The UE may determine which of the listed bearers according to the secondary base station type.
  • LTE SCG split bearer may include one or more of LTE-eLTE SCG split bearer, LTE-NR SCG split bearer, and LTE-LTE SCG split bearer.
  • the UE may determine which of the listed bearers according to the secondary base station type.
  • the eLTE SCG split bearer may include one or more of an eLTE-eLTE SCG split bearer, an eLTE-NR SCG split bearer, and an eLTE-LTE SCG split bearer.
  • the UE may determine which of the listed bearers according to the secondary base station type.
  • the MCG bearer in the present application may include one or more of the following: NR MCG bearer, LTE MCG bearer, eLTE MCG bearer, unless otherwise specified.
  • the UE may determine which of the listed bearers according to the primary base station type.
  • the SCG bearer may include one or more of the following: an NR SCG bearer, an LTE SCG bearer, and an eLTE SCG bearer.
  • the UE may determine which of the listed bearers according to the primary base station type.
  • the MCG split bearer may include one or more of the following: an NR MCG split bearer, an LTE MCG split bearer, and an eLTE MCG split bearer.
  • the UE may determine which of the listed bearers according to the primary base station type.
  • the SCG split bearer may include one or more of the following: an NR SCG split bearer, an LTE SCG split bearer, and an eLTE SCG split bearer.
  • the UE may determine which of the listed bearers according to the primary base station type.
  • the primary cell group is a group of serving cells associated with the primary base station, and includes one primary cell PCell, and may also include one or more secondary cells SCell.
  • a secondary cell group is a group of serving cells associated with a secondary base station, including a PSCell, and may also include one or more SCells.
  • the PCell is a cell operating on a primary carrier frequency, and the UE performs an initial connection establishment process or initiates a connection re-establishment process on the cell or indicates a PCell during the handover process.
  • the PSCell is an SCG cell, and the UE performs a cell that is immediately accessed when performing the SCG change procedure.
  • the SCell is a cell operating on a secondary carrier frequency, and the SCell may be configured after the RRC connection establishment is established and may provide additional radio resources.
  • each cell involved in the present application is described below. It should be noted that, in this application, the type of the wireless communication system corresponding to each cell is NR, LTE, and eLTE, but is named in the manner used in LTE, but the application is not limited to the naming manner. This application also supports different naming schemes. . However, those skilled in the art can determine, according to the type of MeNB and SeNB involved in the dual connectivity, which entity (cell group) corresponds to the corresponding cell.
  • scg-Configuration cell Contains information about releasing or configuring or modifying the SCG.
  • the names may be different. For example, when the SeNB is LTE, it is denoted as scg-ConfigurationLTE; when the SeNB is eLTE, it is recorded as scg-ConfigurationeLTE; when the SeNB is NR, it is denoted as scg-ConfigurationNR.
  • drb-ToAddModListSCG cell A set of DRBs of SeNBs that need to be added or modified; the DRBs may be SCG DRBs, MCG split DRBs, SCG split DRBs.
  • the E-UTRAN or NR configures at least one SCG DRB or MCG split DRB or SCG split DRB.
  • the drb-ToAddModListSCG cell may be included in a cell radioResourceConfigDedicatedSCG, where the radioResourceConfigDedicatedSCG is used to configure a radio resource of the SCG.
  • drb-ToAddModList cell A set of DRBs that need to be added or modified; the drb-ToAddModList cell can be included in the cell radioResourceConfigDedicated, which is used to create/modify/release RBs, modify the MAC master configuration, and modify the SPS configuration. And modify specific physical layer configurations.
  • pdcp-Config cell Configurable PDCP parameter containing DRB
  • drb-Identity cell data bearer DRB identifier
  • rlc-Config cell includes configuration information of an RLC entity corresponding to the SRB and the DRB;
  • logicalChannelIdentity cell logical channel identifier
  • logicalChannelConfig cell Contains parameters used to configure the logical channel.
  • the naming of the base station, the primary base station, the secondary base station, the cell, the primary cell group, the secondary cell group, the data bearer DRB, the core network, and each entity may be different. This application also applies to different names in different deployment scenarios or different wireless communication systems.
  • FIG. 5 illustrates a radio protocol layer 2 entity involved in an LTE dual connectivity deployment manner, including a packet data convergence protocol PDCP entity, a radio link control RLC entity, and a medium access control MAC entity.
  • the interface between the MeNB and the SeNB is denoted as X2, and the control plane data and the user plane data may be transmitted on the same interface or transmitted on different interfaces.
  • the functions provided by the PDCP entity include assigning sequence numbers SN, header compression ROHC, integrity protection (control plane only), encryption, adding PDCP headers, routing, etc., for data from the EPC. It should be noted that not all bearers require all the functions provided by the PDCP entity.
  • the signaling bearer does not require routing
  • the data bearer does not require integrity protection
  • the split bearer in the dual connectivity deployment does not require head compression.
  • the functions provided by the RLC entity include: transmission data buffering, segmentation/cascading, retransmission, addition of RLC headers, and the like.
  • the functions provided by the RLC entity are also different depending on the configured RLC mode. Such as RLC non-confirmation mode (RLC UM) has no retransmission function, and RLC acknowledgment mode (RLC AM) has a retransmission function.
  • the functions provided by the MAC entity include: multiplexing/demultiplexing, logical channel priority (for uplink only), random access, HARQ, and so on. It should be noted that in the dual connectivity, the UE may include two MACs, one corresponding to the MCG and the other corresponding to the SCG.
  • the radio protocol layer also needs all or part of the functions provided by the PDCP entity, the RLC entity, and the MAC entity, and may also include other functions not provided by the PDCP entity, the RLC entity, and the MAC entity, such as a light beam ( Bean) management functions.
  • the combination of functions and the layering manner may also be different from LTE.
  • the reordering function of the PDCP entity and the RLC entity may be integrated, provided only in one entity, for example, providing reordering function only in PDCP.
  • the application is not limited to the combination of the functions provided by the PDCP entity, the RLC entity, and the MAC entity of the LTE and the layered manner.
  • the present application is applicable to NR or eLTE, there may be more entities (layers) or fewer entities (layers), for example, there may be only two layers in the NR, which are divided into the upper layer of layer 2 and the lower layer of layer 2.
  • the PDCP entity, the RLC entity, and the MAC entity of the LTE are respectively marked as an LTE PDCP entity, an LTE RLC entity, and an LTE MAC entity;
  • the PDCP entity, the RLC entity, and the MAC entity of the eLTE are respectively marked as an eLTE PDCP entity, an eLTE RLC entity, The eLTE MAC entity;
  • the PDCP entity, the RLC entity, and the MAC entity of the NR are respectively marked as an NR PDCP entity, an NR RLC entity, and an NR MAC entity;
  • the entity type of the PDCP entity, the RLC entity, and the MAC entity is not explicitly indicated, that is, the PDCP entity, the RLC entity, and the MAC entity are not corresponding to the LTE, eLTE, and NR entities,
  • the type of the MeNB and the SeNB can infer the configuration information of the corresponding PDCP entity, the RLC entity, the MAC entity,
  • the PDCP entity acts as an entity that implements data separation and/or aggregation in the MeNB and/or the SeNB, that is, the user plane data is processed by the PDCP entity, and a part of the data is transmitted by using the resources provided by the base station where the PDCP entity is located, and another part of the data is transmitted. Sent to/from another base station and utilize the resources provided by the base station for transmission.
  • the data transmitted by the SeNB is further processed by another entity (referred to as an LNAAP entity), and the LNAAP entity is responsible for encapsulating/decapsulating data from/to the PDCP entity in a form required by the dual connectivity deployment. After that, it is sent to/from the SeNB.
  • the LNAAP entity adds a DRB identity and the like to each PDCP PDU from the PDCP entity.
  • the names of entities that implement data separation and aggregation may be different according to different MeNB types (for example, NR MgNB, LTE MeNB, and eLTE MeNB), but are collectively referred to as PDCP entities in the present application.
  • MeNB types for example, NR MgNB, LTE MeNB, and eLTE MeNB
  • the function of data separation and/or aggregation can be realized.
  • FIG. 6 shows a flow diagram of a method for establishing/reconfiguring a data bearer in accordance with one embodiment of the present application.
  • the method shown in Figure 6 can be applied to the process of establishing an MCG bearer, an SCG bearer, an MCG split bearer, and an SCG split bearer in an NR, LTE, and eLTE dual-connection deployment scenario.
  • the following describes the data bearer DRB as a class. It should be noted that the present application is not limited to the naming, and the present application is also applicable to the case where the naming manners that may be adopted in eLTE or NR are different.
  • method 600 begins at step S610.
  • a data bearer setup/reconfiguration request message is received.
  • the request message may include a data bearer identifier and a bearer type indicating cell.
  • the data bearer identifier is used to identify the data bearer
  • the bearer type indicating cell is used to indicate the type of the data bearer to be established/to be reconfigured.
  • a corresponding data bearer is established/reconfigured according to the request message.
  • method 600 ends at step S640.
  • a DRB Setup Request message is received.
  • the request message is used to establish a corresponding bearer.
  • the bearer setup request message may be an LTE or eLTE or NR radio resource control RRC reconfiguration message. This is dependent on the dual-connection deployment scenario: if it is the LTE eNB as the primary base station, it can be called the LTE radio resource control reconfiguration message; if it is the eLTE eNB as the primary base station, it can be called the eLTE radio resource control reconfiguration message; if it is the NR gNB
  • the primary base station may be referred to as an NR radio resource control reconfiguration message.
  • the radio resource control message may include radio resource control messages from two or more radio access technology RATs.
  • the DRB establishment request message is included to include the DRB identifier drb-Identity. Specifically, drb-Identity can be included in the cell ToAddModList. The DRB identity is used to uniquely identify this DRB (eg, uniquely identifies one DRB in the UE).
  • the DRB setup request message can be packaged.
  • the bearer type indicating cell drb-Type LNA is included, and the bearer type indicating cell drb-Type LNA is used to indicate the bearer type to be established.
  • the DRB type that the bearer type indication information element can indicate is: LTE-NR MCG bearer, LTE-NR SCG bearer, LTE-NR MCG split bearer, LTE-NR SCG split Hosted.
  • LTE-NR MCG bearer LTE-NR SCG bearer
  • LTE-NR MCG split bearer LTE-NR SCG split Hosted.
  • a corresponding DRB is established according to the DRB setup request message.
  • the following steps may be performed:
  • the bearer type indicating cell drb-Type LNA indicates that the corresponding DRB is an MCG bearer; then the establishment process of the MCG bearer is performed.
  • the bearer type indicating cell drb-Type LNA indicates that the corresponding DRB is an SCG bearer; then the establishment process of the SCG bearer is performed.
  • the bearer type indicating cell drb-Type LNA indicates that the corresponding DRB is an MCG split bearer; then the establishment process of the MCG split bearer is performed.
  • the bearer type indicating cell drb-Type LNA indicates that the corresponding DRB is an SCG split bearer; then the establishment process of the SCG split bearer is performed.
  • the UE may further determine the SeNB type according to the manner of distinguishing the dual connectivity type according to the cell carried in the DRB setup/reconfiguration request message.
  • the upper layer indicates the establishment of the DRB and its identifier.
  • the following describes the bearer reconfiguration process in the LTE, eLTE, and NR dual-connection scenarios in the description of the LWA bearer setup process in the LTE and WLAN aggregation (LWA).
  • a bearer reconfiguration message is received.
  • the bearer reconfiguration message can be used to modify/reconfigure the configured bearers in the UE.
  • the bearer reconfiguration message may be an LTE or eLTE or NR radio resource control RRC reconfiguration message.
  • the bearer reconfiguration message may include a bearer reconfiguration indication cell drb-TypeChangeLNA indicating the reconfigured bearer type.
  • the bearer reconfiguration may include: MCG bearer reconfiguration to SCG bearer and/or MCG bearer reconfiguration to MCG split bearer and/or MCG bearer reconfiguration to SCG split bearer and/or SCG bearer reconfiguration to MCG bearer and/or SCG bearer reconfiguration to SCG split bearer and/or SCG bearer reconfiguration to MCG split bearer and/or SCG split bearer reconfiguration to MCG bearer and/or SCG split bearer reconfiguration to MCG bearer and/or SCG split bearer reconfiguration to MCG split bearer and/or MCG split bearer reconfiguration to MCG bearer and/or MCG split bearer reconfiguration to SCG bearer and/or MCG split bearer reconfiguration to SCG bearer and/or MCG split bearer reconfiguration to SCG split bearer and/or reconfigure MCG bearer and/or reconfigure SCG Carrying and/or reconfiguring the MCG split bearers and/or reconfiguring the SCG split bearers.
  • the bearer is reconfigured according to the bearer reconfiguration message. Specifically, for the bearer identifier drb-Identity included in the bearer reconfiguration message, and the bearer corresponding to the bearer identifier is a bearer configured by the UE, perform the following steps:
  • the MCG bearer reconfiguration is performed as the MCG split bearer procedure.
  • the MCG bearer reconfiguration is performed as the SCG bearer process.
  • the MCG bearer reconfiguration is performed as the SCG split bearer procedure.
  • the SCG bearer reconfiguration is performed as the MCG bearer process.
  • the SCG bearer reconfiguration is performed as the SCG split bearer procedure.
  • the bearer identifier corresponding to the bearer identifier drb-Identity configured in the UE is the SCG bearer and the reconfiguration bearer type indicated by the bearer reconfiguration indicator cell drb-TypeChangeLNA is the MCG split bearer, and the SCG bearer reconfiguration is performed as the MCG split bearer procedure.
  • the SCG split bearer reconfiguration is performed as the SCG bearer procedure.
  • the SCG split bearer reconfiguration is performed as the MCG bearer procedure.
  • the bearer corresponding to the bearer identifier drb-Identity configured in the UE is the SCG split bearer and the reconfiguration bearer type indicated by the bearer reconfiguration indicator cell drb-TypeChangeLNA is the MCG split bearer, and the SCG split bearer reconfiguration is performed as the MCG split bearer process. .
  • the MCG split bearer reconfiguration is performed as an SCG bearer procedure.
  • the MCG split bearer reconfiguration is performed as the MCG bearer procedure.
  • the MCG split bearer reconfiguration is performed as the SCG split bearer process. .
  • the bearer corresponding to the bearer identifier drb-Identity configured in the UE is the MCG bearer and the reconfiguration bearer type indicated by the bearer reconfiguration indicator cell drb-TypeChangeLNA is the MCG bearer (or the bearer reconfiguration indication cell is not included), Perform the MCG bearer reconfiguration process.
  • the bearer corresponding to the bearer identifier drb-Identity configured in the UE is the SCG bearer and the reconfiguration bearer type indicated by the bearer reconfiguration indicator cell drb-TypeChangeLNA is the SCG bearer (or the bearer reconfiguration indication cell is not included), Perform the SCG bearer reconfiguration process.
  • the bearer corresponding to the bearer identifier drb-Identity configured in the UE is the MCG split bearer and the reconfiguration bearer type indicated by the bearer reconfiguration indicator cell drb-TypeChangeLNA is the MCG split bearer (or the bearer reconfiguration indication cell is not included) Then, the MCG split bearer reconfiguration process is performed.
  • the bearer corresponding to the bearer identifier drb-Identity configured in the UE is the SCG split bearer and the reconfiguration bearer type indicated by the bearer reconfiguration indicator cell drb-TypeChangeLNA is the SCG split bearer (or does not contain the bearer reconfiguration indication cell) Then, the SCG split bearer reconfiguration process is performed.
  • X and Y may be eLTE. eNB or LTE eNB or gNB.
  • the secondary base station (or SCG or RAT) type may be indicated in the DRB Setup Request message and/or the DRB Reconfiguration message, and the DRB Setup Request message and/or the DRB Reconfiguration message may be an RRC Reconfiguration message.
  • the DRB setup request message and/or the DRB reconfiguration message includes a bearer type indication information element (denoted as drb-TypeSCG), and the drb-TypeSCG is used to indicate the secondary base station to be established or reconfigured ( Or SCG or RAT or DRB) type.
  • the bearer type indicating cell drb-TypeSCG value may be from a set ⁇ LTE eNB, eLTE eNB, gNB ⁇ or ⁇ LTE SCG, eLTE SCG, NR SCG ⁇ or ⁇ LTE, eLTE, NR ⁇ or two Bit representation.
  • the hybrid dual connectivity secondary base station type can only be one of the other two base stations. If, for a certain type of primary base station, the dual-connected secondary base station type can only be of a certain type, when the value of the bearer type indicating cell is set to "True” or “Setup” or “1", the secondary base station A hybrid dual connection of a corresponding type of base station; and when the value of the bearer type indicating cell is set to "False” or "Release” or "0" or the indication does not occur, the type of the secondary base station is the same as that of the primary base station. vice versa.
  • the UE may determine the secondary base station (or SCG or RAT) type according to the value of the drb-Type SCG; the UE may determine the type of the primary base station (or MCG or RAT) according to the type of the base station performing the initial random access.
  • the UE determines the corresponding SCG or SCell or SeNB type based on the received cells.
  • the secondary base station is an NR type cell, which is included in the cell sCellToAddModListNR (for indicating the added/modified SCG SCell list) and/or sCellToAddModNR (for indicating the added/modified SCG SCell related information, In the cell identity, etc., when the UE receives the bearer setup or reconfiguration message including sCellToAddModListNR and/or sCellToAddModNR, the UE determines that the type of the SCG or SeNB or SCell is NR.
  • different SCGs correspond to different configuration cells, such as when SeNB When it is NR, the corresponding SCG configuration cell is recorded as scg-ConfigurationNR; when the SeNB is LTE, the corresponding SCG configuration cell is recorded as scg-ConfigurationLTE; when the SeNB is eLTE, the corresponding SCG configuration cell is recorded as scg-
  • the configuration eLTE can determine the type of the secondary base station (or SCG or RAT) according to the carried SCG configuration information element, and the UE can determine the type of the primary base station (or MCG or RAT) according to the type of the base station performing the initial random access.
  • different SCG configuration cells may be uniformly represented as scg-Configuration.
  • the scg-Configuration can be replaced with a corresponding type of SCG configuration cell depending on the type of SeNB.
  • the following describes the establishment and/or reconfiguration process of the MCG bearer, the SCG bearer, the MCG split bearer, and the SCG split bearer in the scenario of the LTE, eLTE, and NR dual-link deployment scenarios.
  • the bearer setup/reconfiguration request message is used to establish/modify/reconfigure the corresponding bearer.
  • the bearer setup/reconfiguration request message may be an LTE or eLTE or NR radio resource control RRC reconfiguration message. This depends on the dual-connection deployment scenario: if LTE is the primary base station, it can be called LTE RRC reconfiguration message; if eLTE is the primary base station, it can be called eLTE RRC reconfiguration message; if NR is the primary base station, it can be called NR RRC heavy Configure the message.
  • the RRC reconfiguration message may include RRC reconfiguration information from two or more radio access technologies (RATs).
  • RATs radio access technologies
  • the corresponding bearer is established/modified/reconfigured according to the DRB setup/reconfiguration request message.
  • scg-configuration is set to release and the UE is configured with one or more MCG split DRBs or SCG DRBs or SCG split DRBs and the received DRB setup/reconfiguration request message includes drb-ToAddModList
  • the DRB establishment or modification or reconfiguration process described in the following steps 9001 to 9020 is performed.
  • the scg-configuration is set to release or the DRB setup/reconfiguration request message contains an indication to change the SCG (denoted as mobilityControlInfoSCG) but does not include a handover indication (denoted as mobilityControlInfo), then the drb-Identity for each configuration in the UE:
  • the corresponding DRB is the MCG DRB and receives the drb-ToAddModListSCG and contains the drb-Identity and the corresponding bearer reconfiguration indication identifier (denoted as drb-TypeChangeLN) indicates SCG DRB, then reconstructs PDCP entity and MCG RLC entity;
  • Re-establishing the PDCP entity (or performing PDCP data if the corresponding DRB is the MCG DRB and receives the drb-ToAddModListSCG and contains the drb-Identity and the corresponding bearer reconfiguration indication flag (denoted as drb-TypeChangeLN) indicates the SCG separation DRB Restore) and/or reconstruct the MCG RLC entity;
  • the reconstructed PDCP entity and/or PDCP data recovery process described in this embodiment of the present application includes at least one of the following operations (and possibly other operations):
  • the PDCP status report is generated and sent to the lower layer as the first PDCP PDU for transmission;
  • the received DRB setup/reconfiguration request message is not for releasing the SCG (eg, scg-Configuration is not set to release) and does not contain a cell indicating the SCG change (denoted as mobilityControlInfoSCG); further, If the DRB setup/reconfiguration request message includes drb-ToAddModListSCG, perform the establishment or modification or reconfiguration process of the DRB described in the following steps 9001 to 9020 for each drb-Identity included in the drb-ToAddModListSCG:
  • Step 9001 If the drb-Identity is not configured in the UE, step 9002 is performed; otherwise, step 9005 is performed;
  • Step 9002 If the received DRB setup/reconfiguration request message includes a drb-ToAddModList and the drb-Identity is included in the drb-ToAddModList. Further, in an embodiment, if the RRC reconfiguration message includes a split bearer type indication identifier (denoted as drb-TypeSplit, each DRB corresponds to one drb-TypeSplit), and the indication identifier indicates establishment of an MCG split bearer. Then, the MCG split DRB is established; otherwise, step 9003a is performed; in another embodiment, the split bearer type is determined according to whether the PDCP-config is included in the drb-ToAddModList or the drb-ToAddModListSCG. Specifically, if PDCP-config In the drb-ToAddModList, the MCG separation DRB is established; otherwise, step 9003b is performed;
  • Step 9003a If the received DRB setup/reconfiguration request message includes a drb-ToAddModList and the drb-Identity is included in the drb-ToAddModList. Further, if the RRC reconfiguration message includes a separate bearer type indication identifier (denoted as drb-typeSplit), the indication identifier indicates that the SCG split bearer is established, then the SCG split DRB is established; otherwise, step 9004 is performed;
  • Step 9003b If the received DRB setup/reconfiguration request message includes a drb-ToAddModList and the drb-Identity is included in the drb-ToAddModList. Further, the PDCP-config is included in the drb-ToAddModList or the drb-ToAddModListSCG to determine the split bearer type. Specifically, if the PDCP-config is included in the drb-ToAddModListSCG, the SCG separation DRB is established; otherwise, step 9004 is performed;
  • Step 9004 establishing an SCG bearer
  • the UE determines that the received DRB setup/reconfiguration request message does not include a drb-ToAddModList, or does not include the drb-ToAddModList, but the drb-Identity is not included in the drb-ToAddModList, or
  • the RRC reconfiguration message includes a split bearer type indication identifier (denoted as drb-TypeSplit), and the indication identifier indicates that the SCG bearer is established, and the SCG bearer is established.
  • Step 9005 if receiving drb-ToAddModList and / or drb-ToAddModListSCG, step 9006;
  • Step 9006 if the DRB indicated by the drb-Identity is the MCG separation DRB, step 9007 is performed; otherwise, step 9010 is performed;
  • Step 9007 If the drb-ToAddModList is received and includes a drb-Identity and includes a corresponding bearer reconfiguration indication identifier (denoted as drb-TypeLN); if the bearer reconfiguration indication identifier is indicated as MCG DRB, performing reconfiguration MCG separation The DRB is the MCG DRB process; otherwise, step 9008 is performed;
  • Step 9008 If the drb-ToAddModList and the drb-ToAddModListSCG are received and both contain the drb-Identity and include the corresponding bearer reconfiguration indication identifier (denoted as drb-TypeLN and/or drb-TypeChangeLN, both can use the same cell. Indicates that drb-TypeLN is included in drb-ToAddModList, and drb-TypeChangeLN is included in drb-ToAddModListSCG.
  • drb-TypeLN is included in drb-ToAddModList
  • drb-TypeChangeLN is included in drb-ToAddModListSCG.
  • the DRB setup/reconfiguration request message may contain only one or two, and if both are included, both indicate If the bearer reconfiguration indication flag indicates that the SCG is a separate DRB, perform the reconfiguration MCG separation DRB as the SCG. Separating the DRB process; otherwise, performing step 9009;
  • Step 9009 If the drb-ToAddModListSCG is received and includes a drb-Identity and includes a corresponding bearer reconfiguration indication identifier (denoted as drb-TypeChangeLN); if the bearer reconfiguration indication identifier is indicated as SCG DRB, performing reconfiguration MCG separation The DRB is the SCG DRB process; otherwise, step 9010 is performed;
  • Step 9010 Perform a reconfiguration MCG separation DRB process.
  • Step 9011 if the DRB indicated by the drb-Identity is the SCG separation DRB, step 9012 is performed; otherwise, step 9016 is performed;
  • Step 9012 If the drb-ToAddModListSCG is received and includes a drb-Identity and includes a corresponding bearer reconfiguration indication identifier (denoted as drb-TypeChangeLN); if the bearer reconfiguration indication identifier indicates an SCG DRB, performing reconfiguration SCG separation DRB is SCG DRB process; otherwise, step 9013 is performed;
  • Step 9013 If the drb-ToAddModList is received and the drb-Identity is included and the corresponding bearer reconfiguration indication identifier is included (denoted as drb-TypeLN); if the bearer reconfiguration indication identifier is indicated as MCG DRB, the reconfiguration SCG separation DRB is performed as MCG DRB process; otherwise, step 9014 is performed;
  • Step 9014 if the drb-ToAddModList and the drb-ToAddModListSCG are received and both contain a drb-Identity and include a corresponding bearer reconfiguration indication identifier (denoted as drb-TypeLN and/or drb-TypeChangeLN); if the bearer reconfiguration indication indicator indicates Separating the DRB for the MCG, performing the reconfiguration SCG separation DRB as the MCG separation DRB process; otherwise, performing step 9015;
  • Step 9015 Perform a reconfiguration SCG separation DRB process.
  • Step 9016 if the DRB indicated by the drb-Identity is the SCG DRB, step 9017 is performed;
  • Step 9017 If the drb-ToAddModList and the drb-ToAddModListSCG are received and both contain the drb-Identity and include the corresponding bearer reconfiguration indication identifier (denoted as drb-TypeLN and/or drb-TypeChangeLN); if the bearer reconfiguration indication indicator indicates Separating the DRB for the SCG, performing the reconfiguration SCG DRB as the SCG separation DRB process; otherwise, performing step 9018;
  • Step 9018 If the drb-ToAddModList is received and includes the drb-Identity and includes the corresponding bearer reconfiguration indication identifier (denoted as drb-TypeLN); if the bearer reconfiguration indication identifier is indicated as MCG DRB, perform reconfiguration SCG DRB as MCG DRB process; otherwise, Step 9019;
  • Step 9019 if the drb-ToAddModList and the drb-ToAddModListSCG are received and both contain a drb-Identity and include a corresponding bearer reconfiguration indication identifier (denoted as drb-TypeLN and/or drb-TypeChangeLN); if the bearer reconfiguration indication indicator indicates Separating the DRB for the MCG, performing the reconfiguration SCG DRB as the MCG separation DRB process; otherwise, performing step 9020;
  • Step 9020 Perform a reconfiguration SCG DRB process.
  • the upper layer indicates the DRB established in step 9002 or 9003 or 9004 and its identifier.
  • the UE before performing the foregoing steps, the UE further needs to determine the SeNB type according to the manner in which the dual connectivity type is differentiated according to the cell carried in the DRB setup/reconfiguration request message message.
  • Steps 9002 to 9004 describe the bearer setup process.
  • Steps 9005 to 9020 describe the bearer modification/reconfiguration process.
  • Steps 9007 to 9009 and/or 9012 to 9014 and/or 9017 to 9019 may also determine the DRB type according to the bearer reconfiguration indication identifier, but according to whether the configuration cell pdcp-Config of the PDCP is located at drb-ToAddModList or drb-ToAddModListSCG. To determine the DRB type. If pdcp-Config is located in drb-ToAddModList, the DRB is separated for MCG; if pdcp-Config is located at drb-ToAddModListSCG, the DRB is separated for SCG.
  • steps 9001 to 9020 can be performed only when the corresponding dual-connection deployment scenario supports the corresponding bearer type and bearer reconfiguration type. For example, if a dual-connection deployment does not support reconfiguration of the MCG split DRB as the SCG. In the case of DRB, step 9009 is not performed.
  • the value of the separated bearer type indication flag drb-TypeSplit in step 9002 and step 9004 is: In one embodiment, when the value of the indication identifier is set to "True” or “Setup” or “1” or “MCGSplit” When the corresponding MCG separates the bearer; and when the value of the indication is set to "False” or “Release” or “0” or “SCGSplit” or the indication does not occur, the corresponding SCG separates the bearer. vice versa.
  • steps 9001-9020 are merely exemplary execution sequences, and execution in other sequences is also within the scope of the present application.
  • the scg-Configuration involved in the embodiment of the present application may be referred to as scg-ConfigurationNR or scg-ConfigurationLTE or scg-ConfigurationeLTE (the specific type depends on the type of the SeNB. ).
  • FIG. 7 shows a flow chart of a method for establishing/reconfiguring a data bearer in accordance with another embodiment of the present application.
  • method 700 begins at step S710.
  • a data bearer setup/reconfiguration request message is transmitted.
  • the request message may include a data bearer identifier and a bearer type indicating cell.
  • the data bearer identifier is used to identify the data bearer, and the bearer type indicating cell is used to indicate the type of the data bearer to be established/to be reconfigured.
  • communication is performed using the corresponding data bearer of the setup/reconfiguration.
  • method 700 ends at step S740.
  • Establishing an MCG DRB involves the following operations:
  • Establishing SCG DRB involves the following operations:
  • Establishing an MCG separation DRB involves the following operations:
  • the MCG bearer reconfiguration to the SCG bearer includes the following operations:
  • the drb-ToAddModListSCG includes a rlc-ConfigSCG and/or a logicalChannelConfigSCG cell, reconfiguring the SCG RLC entity and/or the SCG DTCH logical channel according to the cell;
  • MCG bearer reconfiguration is the MCG split bearer process
  • the MCG bearer reconfiguration to the MCG split bearer includes the following operations:
  • the drb-ToAddModList contains the cell pdcp-Config, reconfigure the PDCP entity according to the pdcp-Config;
  • rlc-ConfigSCG logical channel identifier included in drb-ToAddModListSCG ligicalChannelIdentitySCG and logicalChannelConfigSCG cells, establishing SCG RLC entity and SCG DTCH logical channel;
  • the MCG RLC entity and/or the MCG DTCH logical channel are reconfigured according to the cell.
  • MCG bearer reconfiguration is the SCG separation bearer process
  • the MCG bearer reconfiguration to the SCG split bearer includes the following operations:
  • the drb-ToAddModList contains rlc-Config and/or logicalChannelConfig cells, reconfigure the MCG RLC entity and/or the MCG DTCH logical channel according to the cell;
  • the SCG RLC entity and/or the SCG DTCH logical channel are reconfigured according to the cell.
  • MCG split bearer reconfiguration is the MCG bearer process
  • the MCG split bearer reconfiguration to the MCG bearer includes the following operations:
  • the drb-ToAddModList contains rlc-Config and/or logicalChannelConfig cells, reconfigure the MCG RLC entity and/or the MCG DTCH logical channel according to the cell;
  • the MCG split bearer reconfiguration to the SCG bearer includes the following operations:
  • the SCG RLC entity and/or the SCG DTCH logical channel are reconfigured according to the cell.
  • MCG split bearer reconfiguration is the SCG split bearer process
  • the MCG split bearer reconfiguration to the SCG split bearer includes the following operations:
  • the drb-ToAddModList contains rlc-Config and/or logicalChannelConfig cells, reconfigure the MCG RLC entity and/or the MCG DTCH logical channel according to the cell;
  • the SCG RLC entity and/or the SCG DTCH logical channel are reconfigured according to the cell.
  • SCG bearer reconfiguration is the MCG bearer process
  • the SCG bearer reconfiguration to the MCG bearer includes the following operations:
  • the drb-ToAddModList contains rlc-Config and/or logicalChannelConfig cells, reconfigure the MCG RLC entity and/or the MCG DTCH logical channel according to the cell;
  • SCG bearer reconfiguration is the SCG separation bearer process
  • the SCG bearer reconfiguration to the SCG split bearer includes the following operations:
  • the drb-ToAddModListSCG includes the cell pdcp-Config, reconfigure the PDCP entity according to the pdcp-Config;
  • the SCG RLC entity and/or the SCG DTCH logical channel are reconfigured according to the cell.
  • SCG bearer reconfiguration is the MCG separation bearer process
  • the SCG bearer reconfiguration to the MCG split bearer includes the following operations:
  • the SCG RLC entity and/or the SCG DTCH logical channel are reconfigured according to the cell.
  • SCG split bearer reconfiguration is the MCG bearer process
  • the SCG split bearer reconfiguration to the MCG bearer includes the following operations:
  • the drb-ToAddModList contains rlc-Config and/or logicalChannelConfig cells, reconfigure the MCG RLC entity and/or the MCG DTCH logical channel according to the cell;
  • the SCG split bearer reconfiguration to the SCG bearer includes the following operations:
  • the drb-ToAddModListSCG includes the cell pdcp-Config, reconfigure the PDCP entity according to the pdcp-Config;
  • the drb-ToAddModListSCG includes a rlc-Config and/or a logicalChannelConfig cell, reconfiguring the SCG RLC entity and/or the SCG DTCH logical channel according to the cell;
  • SCG split bearer reconfiguration is the MCG split bearer process
  • the SCG split bearer reconfiguration to the MCG split bearer includes the following operations:
  • the drb-ToAddModList contains rlc-Config and/or logicalChannelConfig cells, reconfigure the MCG RLC entity and/or the MCG DTCH logical channel according to the cell;
  • the SCG RLC entity and/or the SCG DTCH logical channel are reconfigured according to the cell.
  • Reconfiguring an MCG bearer involves the following operations:
  • the drb-ToAddModList contains the cell pdcp-Config, reconfigure the PDCP entity according to the pdcp-Config;
  • the drb-ToAddModList contains rlc-Config and/or logicalChannelConfig cells, reconfigure the MCG RLC entity and/or the MCG DTCH logical channel according to the cell;
  • Reconfiguring an SCG bearer involves the following operations:
  • the drb-ToAddModListSCG includes the cell pdcp-Config, reconfigure the PDCP entity according to the pdcp-Config;
  • the drb-ToAddModListSCG includes a rlc-ConfigSCG and/or a logicalChannelConfigSCG cell, reconfiguring the SCG RLC entity and/or the SCG DTCH logical channel according to the cell;
  • Reconfiguring an MCG split bearer involves the following operations:
  • the drb-ToAddModList contains the cell pdcp-Config, reconfigure the PDCP entity according to the pdcp-Config;
  • the drb-ToAddModList contains rlc-Config and/or logicalChannelConfig cells, reconfigure the MCG RLC entity and/or the MCG DTCH logical channel according to the cell;
  • the SCG RLC entity and/or the SCG DTCH logical channel are reconfigured according to the cell.
  • Reconfiguring an SCG split bearer involves the following operations:
  • the drb-ToAddModListSCG includes the cell pdcp-Config, reconfigure the PDCP entity according to the pdcp-Config;
  • the drb-ToAddModList contains rlc-Config and/or logicalChannelConfig cells, reconfigure the MCG RLC entity and/or the MCG DTCH logical channel according to the cell;
  • the SCG RLC entity and/or the SCG DTCH logical channel are reconfigured according to the cell.
  • the operations on the SCG related entity can be correspondingly described as: the UE indicates NR or / eLTE or LTE related entities (eg RRC entity, determine the corresponding RRC entity type according to the type of SeNB) to establish and / or modify and / or reconfigure and / / Rebuild and / or release the PDCP entity and / or SCG RLC entity and / or SCG DTCH logical channel.
  • the UE indicates NR or / eLTE or LTE related entities (eg RRC entity, determine the corresponding RRC entity type according to the type of SeNB) to establish and / or modify and / or reconfigure and / / Rebuild and / or release the PDCP entity and / or SCG RLC entity and / or SCG DTCH logical channel.
  • the DTCH logical channel may be correspondingly described as: the UE indicates that the NR or /eLTE or LTE related entity (eg RRC entity, determines the corresponding RRC entity type according to the type of MeNB) to establish and/or modify and/or reconfigure and/or reconstruct And/or release the PDCP entity and/or the MCG RLC entity and/or the MCG DTCH logical channel.
  • the NR or /eLTE or LTE related entity eg RRC entity, determines the corresponding RRC entity type according to the type of MeNB
  • the process of establishing or releasing or modifying or reconfiguring the DRB in the embodiment of the present application also involves enabling (establishing) or deactivating (deleting) the DRB or Configure or reconfigure LNAAP entities.
  • FIG. 8 shows a block diagram of a user equipment in accordance with one embodiment of the present application.
  • the user equipment UE 800 includes a receiving unit 810 and a processing unit 820.
  • the receiving unit 810 is configured to receive a data bearer setup/reconfiguration request message.
  • the request message includes a data bearer identifier and a bearer type indicating cell.
  • the data bearer identifier is used to identify the data bearer
  • the bearer type indicating cell is used to indicate the type of the data bearer to be established/to be reconfigured.
  • Processing unit 820 is configured to establish/reconfigure a corresponding data bearer based on the request message. The specific process has been described in detail above with reference to FIG. 6, and is not to be further described herein.
  • FIG. 9 shows a block diagram of a base station in accordance with one embodiment of the present application.
  • the base station BS 900 includes a transmitting unit 910 and a communication unit 920.
  • the transmitting unit 910 is configured to transmit a data bearer setup/reconfiguration request message.
  • the request message includes a data bearer identifier and a bearer type indicating cell.
  • the data bearer identifier is used to identify the data bearer
  • the bearer type indicating cell is used to indicate the type of the data bearer to be established/to be reconfigured.
  • Communication unit 920 is configured to communicate using a respective data bearer that is established/reconfigured. The specific process has been described in detail above with reference to FIG. 7, and will not be further described herein.
  • the UE determines the primary base station type according to the RAT technology used by the initial access, for example, if the UE performs initial random access on the LTE eNB, the corresponding MeNB is an LTE eNB; if the UE performs initial random access on the eLTE eNB, the corresponding The MeNB is an eLTE eNB; if the UE performs initial random access on the gNB, the corresponding MeNB is a gNB.
  • the present application does not specifically specify the primary base station and the secondary base station type.
  • the application may be applicable to the LTE eNB and/or the eLTE eNB and/or the gNB, and the secondary base station may be deployed in any combination of the LTE eNB and/or the eLTE eNB and/or the gNB, and is also applicable to other dual connectivity deployments.
  • Scene such as 6G.
  • the terminology used may vary in different communication systems, but the above process still applies.
  • the program running on the device according to the application can be controlled by the central processing unit (CPU)
  • CPU central processing unit
  • the program or information processed by the program may be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory system.
  • a program for realizing the functions of the embodiments of the present application can be recorded on a computer readable recording medium.
  • the corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs.
  • the so-called "computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware (such as a peripheral device).
  • the "computer readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium of a short-term dynamic storage program, or any other recording medium readable by a computer.
  • circuitry e.g., monolithic or multi-chip integrated circuits.
  • Circuitry designed to perform the functions described in this specification can include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • a general purpose processor may be a microprocessor or any existing processor, controller, microcontroller, or state machine.
  • the above circuit may be a digital circuit or an analog circuit.
  • One or more embodiments of the present application may also be implemented using these new integrated circuit technologies in the context of new integrated circuit technologies that replace existing integrated circuits due to advances in semiconductor technology.
  • present application is not limited to the above embodiment. Although various examples of the described embodiments have been described, the present application is not limited thereto.
  • Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices such as AV devices, kitchen devices, cleaning devices, air conditioners, office equipment, vending machines, and other home appliances.

Landscapes

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

Abstract

本申请提供了一种用于建立/重配置数据承载的方法，包括：接收数据承载建立/重配置请求消息，所述请求消息包括数据承载标识和承载类型指示信元，所述数据承载标识用于标识数据承载，所述承载类型指示信元用于指示要建立的/要重配置的数据承载的类型；根据所述请求消息，建立/重配置相应的数据承载。本申请还提供了一种用于建立/重配置数据承载的用户设备和基站。

Description

用于建立/重配置数据承载的方法和设备 技术领域
本申请涉及无线通信技术领域。更具体地，涉及一种用于建立/重配置数据承载的方法和设备。
背景技术
2016年3月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#71次全会上，NTT DOCOMO提出了一个关于5G技术标准的新的研究项目(参见非专利文献：RP-160671：New SID Proposal：Study on New Radio Access Technology)，并获批准。该研究项目的目的是开发一个新的无线(New Radio：NR)接入技术以满足5G的所有应用场景、需求和部署环境。NR主要有三个应用场景：增强的移动宽带通信(Enhanced Mobile Broadband：eMBB)、大规模机器类通信(massive Machine Type Communication：mMTC)和超可靠低延迟通信(Ultra Reliable and Low Latency Communications：URLLC)。按照该研究项目的规划，NR的标准化分二个阶段进行：第一阶段的标准化工作将于2018年中期完成；第二阶段的标准化工作将于2019年底完成。第一阶段的标准规范要前向兼容于第二阶段的标准规范，而第二阶段的标准规范要建立在第一阶段的标准规范之上，并满足5G NR技术标准的所有要求。
在2016年8月召开的3GPP RAN2#95次会议上达成的NR双连接部署场景中包含图1-4所示的部署场景。
在图1中，NR基站(NR Node B，简称为gNB。所述gNB是逻辑节点，所述逻辑节点负责在去往/来自用户设备UE的一个或多个小区进行无线发送/接收)作为主基站(称为MgNB)，即控制面连接在MgNB和下一代核心网(称为NextGen Core)间进行。增强的长期演进(eLTE)基站(称为eLTE eNB)作为辅基站。用户面数据流通过NR基站和eLTE eNB经由下一代核心网传输；具体地，存在四种用户面数据传输方式：方式a1，用户面数据在gNB和下一代核心网间传输并利用gNB提供的资源(对应的数据 承载DRB称为NR-eLTE主小区组(Master Cell Group：MCG)承载)；方式a2，用户面数据在eLTE eNB和下一代核心网间传输并利用eLTE eNB提供的资源(对应的数据承载称为NR-eLTE辅小区组(Secondary Cell Group：SCG)承载)；方式a3，用户面数据在gNB和下一代核心网间传输，且一部分数据利用gNB的无线资源传输，另一部数据通过gNB和eLTE eNB间的接口发往/来自eLTE eNB并利用eLTE eNB的无线资源传输(对应的数据承载称为NR-eLTE MCG分离承载)；方式a4，用户面数据在eLTE eNB和下一代核心网间传输，部分数据直接利用eLTE eNB的无线资源传输，另一部数据通过gNB和eLTE eNB间的接口发往/来自NR gNB并利用NR gNB的无线资源传输(对应的数据承载称为NR-eLTE SCG分离承载)。在方式a3和a4中，用户面数据经由下一代核心网同时利用gNB和eLTE eNB提供的资源。
在图2中，主基站MgNB和辅基站SgNB都是gNB，即控制面连接在MgNB和下一代核心网间进行，用户面数据流通过MgNB和SgNB经由下一代核心网传输。具体地，存在四种用户面数据传输方式：方式b1，用户面数据在MgNB和下一代核心网间传输并利用MgNB提供的资源传输(对应的数据承载称为NR-NR MCG承载)；方式b2，用户面数据在SgNB和下一代核心网间传输并利用辅基站SgNB提供的资源(对应的数据承载称为NR-NR SCG承载)；方式b3，用户面数据在MgNB和下一代核心网间传输，且一部分数据利用主基站MgNB的无线资源传输，另一部数据通过主基站MgNB和辅基站SgNB间的接口发往/来自SgNB并利用SgNB的无线资源传输(对应的数据承载称为NR-NR MCG分离承载)。方式b4，用户面数据在SgNB和下一代核心网间传输，部分数据直接利用SgNB的无线资源传输，另一部数据通过SgNB和MgNB间的接口发往/来自MgNB并利用MgNB的无线资源传输(对应的数据承载称为NR-NR SCG分离承载)。方式b3和b4中，用户面数据经由下一代核心网同时利用MgNB和SgNB提供的资源传输。
在图3中，长期演进基站LTE eNB作为主基站(称为LTE MeNB)，即控制面连接在LTE eNB和核心网(称为EPC)间进行。gNB作为辅基站。用户面数据流通过gNB和LTE eNB经由EPC传输。具体地，存在四种用 户面数据传输方式：方式c1，用户面数据在LTE eNB和EPC间传输，并利用LTE eNB提供的资源(对应的数据承载称为LTE-NR MCG承载)；方式c2，用户面数据在gNB和EPC间传输，并利用gNB提供的资源传输(对应的数据承载称为LTE-NR SCG承载)；方式c3，用户面数据在LTE eNB和EPC间传输，且一部分数据利用LTE eNB的无线资源传输，另一部数据通过gNB和LTE eNB间的接口发往/来自gNB并利用gNB的无线资源传输(对应的数据承载称为LTE-NR MCG分离承载)。方式c4，用户面数据在gNB和EPC间传输，部分数据直接利用gNB的无线资源传输，另一部数据通过gNB和LTE eNB间的接口发往/来自LTE eNB并利用LTE eNB的无线资源传输(对应的数据承载称为LTE-NR SCG分离承载)。方式c3和c4中，用户面数据经由EPC同时利用gNB和LTE eNB提供的资源传输。
在图4中，eLTE eNB作为主基站(称为eLTE MeNB)，即控制面连接在eLTE eNB和下一代核心网间进行。gNB作为辅基站。用户面数据流通过gNB和eLTE eNB经由下一代核心网传输。具体地，存在四种用户面数据传输方式：方式d1，用户面数据在eLTE eNB和下一代核心网间传输并利用eLTE eNB提供的资源(对应的数据承载称为eLTE-NR MCG承载)；方式d2，用户面数据在gNB和下一代核心网间传输并利用gNB提供的资源(对应的数据承载称为eLTE-NR SCG承载)；方式d3，用户面数据在eLTE eNB和下一代核心网间传输，且一部分数据利用eLTE eNB的无线资源传输，另一部数据通过gNB和eLTE eNB间的接口发往/来自gNB并利用gNB的无线资源传输(对应的数据承载称为eLTE-NR MCG分离承载)。方式d4，用户面数据在gNB和下一代核心网间传输，且一部分数据直接利用gNB的无线资源传输，另一部数据通过gNB和eLTE eNB间的接口发往/来自eLTE eNB并利用eLTE eNB的无线资源传输(对应的数据承载称为eLTE-NR SCG分离承载)。在方式d3和d4中，用户面数据经由下一代核心网同时利用gNB和eLTE eNB提供的资源传输。
发明内容
然而，如何在双连接部署场景下为用户设备UE配置对应的数据承载DRB和进行数据承载重配置，是需要解决的问题。
为了解决上述技术问题，本申请提供了一种用于建立/重配置数据承载的方法，包括：接收数据承载建立/重配置请求消息，所述请求消息包括数据承载标识和承载类型指示信元，所述数据承载标识用于标识数据承载，所述承载类型指示信元用于指示要建立的/要重配置的数据承载的类型；根据所述请求消息，建立/重配置相应的数据承载。
在一个实施例中，数据承载的类型包括主小区组MCG承载、辅小区组SCG承载、MCG分离承载和SCG分离承载。
在一个实施例中，数据承载建立/重配置请求消息包括无线资源控制RRC重配置消息。
在一个实施例中，RRC重配置消息包括来自两种或更多种无线接入技术RAT的RRC消息。
在一个实施例中，数据承载建立/重配置请求消息包括用于指示辅基站类型的信元。
在一个实施例中，根据用于指示辅基站类型的信元的内容，执行相应的用于建立/重配置数据承载的处理。
根据另一方面，提供了一种用户设备，包括：接收单元，被配置为接收数据承载建立/重配置请求消息，所述请求消息包括数据承载标识和承载类型指示信元，所述数据承载标识用于标识数据承载，所述承载类型指示信元用于指示要建立的/要重配置的数据承载的类型；处理单元，被配置为根据所述请求消息建立/重配置相应的数据承载。
在一个实施例中，数据承载的类型包括主小区组MCG承载、辅小区组SCG承载、MCG分离承载和SCG分离承载。
在一个实施例中，数据承载建立/重配置请求消息包括无线资源控制RRC重配置消息。
在一个实施例中，RRC重配置消息包括来自两种或更多种无线接入技术RAT的RRC消息。
在一个实施例中，数据承载建立/重配置请求消息包括用于指示辅基站类型的信元。
在一个实施例中，处理单元被配置为：根据用于指示辅基站类型的信元的内容，执行相应的用于建立/重配置数据承载的处理。
根据另一方面，提供了一种用于建立/重配置数据承载的方法，包括： 发送数据承载建立/重配置请求消息，所述请求消息包括数据承载标识和承载类型指示信元，所述数据承载标识用于标识数据承载，所述承载类型指示信元用于指示要建立的/要重配置的数据承载的类型；使用建立/重配置的相应数据承载进行通信。
在一个实施例中，数据承载的类型包括主小区组MCG承载、辅小区组SCG承载、MCG分离承载和SCG分离承载。
在一个实施例中，数据承载建立/重配置请求消息包括无线资源控制RRC重配置消息。
在一个实施例中，RRC重配置消息包括来自两种或更多种无线接入技术RAT的RRC消息。
在一个实施例中，数据承载建立/重配置请求消息包括用于指示辅基站类型的信元。
根据另一方面，提供了一种基站，包括：发送单元，被配置为发送数据承载建立/重配置请求消息，所述请求消息包括数据承载标识和承载类型指示信元，所述数据承载标识用于标识数据承载，所述承载类型指示信元用于指示要建立的/要重配置的数据承载的类型；通信单元，被配置为使用建立/重配置的相应数据承载进行通信。
在一个实施例中，数据承载的类型包括主小区组MCG承载、辅小区组SCG承载、MCG分离承载和SCG分离承载。
在一个实施例中，数据承载建立/重配置请求消息包括无线资源控制RRC重配置消息。
在一个实施例中，RRC重配置消息包括来自两种或更多种无线接入技术RAT的RRC消息。
在一个实施例中，数据承载建立/重配置请求消息包括用于指示辅基站类型的信元。
附图说明
通过下文结合附图的详细描述，本申请的上述和其它特征将会变得更加明显，其中：
图1示出了NR-eLTE双连接部署场景的示意图；
图2示出了NR-NR双连接部署场景的示意图；
图3示出了LTE-NR双连接部署场景的示意图；
图4示出了eLTE-NR双连接部署场景的示意图；
图5示出了LTE双连接部署方式中涉及的无线协议层2实体的示意图；
图6示出了根据本申请一个实施例的用于建立/重配置数据承载的方法的流程图；
图7示出了根据本申请另一个实施例的用于建立/重配置数据承载的方法的流程图；
图8示出了根据本申请一个实施例的用户设备的框图；以及
图9示出了根据本申请一个实施例的基站的框图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
下面描述本申请涉及的部分术语，如未特别说明，本申请涉及的术语采用此处定义。本申请以双连接为例，但本申请所述方法并不限于双连接场景，本领域技术人员可以容易的扩展到多连接场景。此外，本申请以LTE、eLTE、NR及对应的核心网和下一代核心网为例进行说明。需要说明的是，本申请并不限于所述LTE、eLTE、NR及对应的核心网和下一代核心网，也可以用于其他无线通信系统，例如6G无线通信系统。
本申请中，在双连接下将控制面与EPC或下一代核心网连接的基站称为主基站MeNB，可以为NR MgNB、LTE MeNB或eLTE MeNB。控制面不与EPC或下一代核心网连接(即不是主基站)但为用户面数据传输提供传输资源的基站称为辅基站SeNB，可以为NR SgNB、LTE SeNB或eLTE SeNB。
X-Y MCG承载是指MeNB为X，SeNB为Y且所述承载的无线协议层位于X中并利用X提供的资源。所述X可以是NR MgNB、LTE MeNB或eLTE MeNB；所述Y可以是NR SgNB、LTE SeNB或eLTE SeNB。
X-Y SCG承载是指MeNB为X，SeNB为Y且所述承载的无线协议层位于Y中并利用Y提供的资源。所述X可以是NR MgNB、LTE MeNB或eLTE MeNB；所述Y可以是NR SgNB、LTE SeNB或eLTE SeNB。
X-Y MCG分离承载是指主基站为X，辅基站为Y且所述承载的无线协议层位于X和Y中，与EPC或下一代核心网的用户面数据止于X但同时利用X和Y提供的资源。所述X可以是NR MgNB、LTE MeNB或eLTE MeNB；所述Y可以是NR SgNB、LTE SeNB或eLTE SeNB。
X-Y SCG分离承载是指主基站为X，辅基站为Y且所述承载的无线协议层位于X和Y中，与EPC或下一代核心网的用户面数据止于Y但同时利用X和Y提供的资源。所述X可以是NR MgNB、LTE MeNB或eLTE MeNB；所述Y可以是NR SgNB、LTE SeNB或eLTE SeNB。
X MCG承载是指MeNB为X，SeNB可以是NR SgNB、LTE SeNB或eLTE SeNB。所述承载的无线协议层位于X中并利用X提供的资源。所述X可以是NR MgNB、LTE MeNB或eLTE MeNB。
X SCG承载是指MeNB为X，SeNB可以是NR SgNB、LTE SeNB或eLTE SeNB。所述承载的无线协议层位于SeNB中并利用SeNB提供的资源。所述X可以是NR MgNB、LTE MeNB或eLTE MeNB。
X MCG分离承载是指MeNB为X，SeNB可以是NR SgNB、LTE SeNB或eLTE SeNB。所述承载的无线协议层位于X和SeNB中，与EPC或下一代核心网的用户面数据止于X并同时利用X和SeNB提供的资源。所述X可以是NR MgNB、LTE MeNB或eLTE MeNB。
X SCG分离承载是指MeNB为X，SeNB可以是NR SgNB、LTE SeNB或eLTE SeNB。所述承载的无线协议层位于X和SeNB中，与EPC或下一代核心网的用户面数据止于SeNB并同时利用X和SeNB提供的资源。所述X可以是NR MgNB、LTE MeNB或eLTE MeNB。
NR MCG承载：可以包含NR-eLTE MCG承载、NR-NR MCG承载、NR-LTE MCG承载中的一种或多种。UE可以根据辅基站类型来确定所列承载中的哪种承载。
LTE MCG承载：可以包含LTE-eLTE MCG承载、LTE-NR MCG承载、LTE-LTE MCG承载中的一种或多种。UE可以根据辅基站类型来确定所列承载中的哪种承载。
eLTE MCG承载：可以包含eLTE-eLTE MCG承载、eLTE-NR MCG承载、eLTE-LTE MCG承载中的一种或多种。UE可以根据辅基站类型来确定所列承载中的哪种承载。
NR SCG承载：可以包含NR-eLTE SCG承载、NR-NR SCG承载、NR-LTE SCG承载中的一种或多种。UE可以根据辅基站类型来确定所列承载中的哪种承载。
LTE SCG承载：可以包含LTE-eLTE SCG承载、LTE-NR SCG承载、LTE-LTE SCG承载中的一种或多种。UE可以根据辅基站类型来确定所列承载中的哪种承载。
eLTE SCG承载：可以包含eLTE-eLTE SCG承载、eLTE-NR SCG承载、eLTE-LTE SCG承载中的一种或多种。UE可以根据辅基站类型来确定所列承载中的哪种承载。
NR MCG分离承载：可以包含NR-eLTE MCG分离承载、NR-NR MCG分离承载、NR-LTE MCG分离承载中的一种或多种。UE可以根据辅基站类型来确定所列承载中的哪种承载。
LTE MCG分离承载：可以包含LTE-eLTE MCG分离承载、LTE-NR MCG分离承载、LTE-LTE MCG分离承载中的一种或多种。UE可以根据辅基站类型来确定所列承载中的哪种承载。
eLTE MCG分离承载：可以包含eLTE-eLTE MCG分离承载、eLTE-NR MCG分离承载、eLTE-LTE MCG分离承载中的一种或多种。UE可以根据辅基站类型来确定所列承载中的哪种承载。
NR SCG分离承载：可以包含NR-eLTE SCG分离承载、NR-NR SCG分离承载、NR-LTE SCG分离承载中的一种或多种。UE可以根据辅基站类型来确定所列承载中的哪种承载。
LTE SCG分离承载：可以包含LTE-eLTE SCG分离承载、LTE-NR SCG分离承载、LTE-LTE SCG分离承载中的一种或多种。UE可以根据辅基站类型来确定所列承载中的哪种承载。
eLTE SCG分离承载：可以包含eLTE-eLTE SCG分离承载、eLTE-NR SCG分离承载、eLTE-LTE SCG分离承载中的一种或多种。UE可以根据辅基站类型来确定所列承载中的哪种承载。
如未特别说明，本申请中的MCG承载可以包含以下一种或多种：NR MCG承载、LTE MCG承载、eLTE MCG承载。UE可以根据主基站类型来确定所列承载中的哪种承载。SCG承载可以包含以下一种或多种：NR SCG承载、LTE SCG承载、eLTE SCG承载。UE可以根据主基站类型来确定所列承载中的哪种承载。MCG分离承载可以包含以下一种或多种：NR MCG分离承载、LTE MCG分离承载、eLTE MCG分离承载。UE可以根据主基站类型来确定所列承载中的哪种承载。SCG分离承载可以包含以下一种或多种：NR SCG分离承载、LTE SCG分离承载、eLTE SCG分离承载。UE可以根据主基站类型来确定所列承载中的哪种承载。
主小区组(MCG)是与主基站关联的一组服务小区，包含一个主小区PCell，还可以包含一个或多个辅小区SCell。辅小区组(SCG)是与辅基站关联的一组服务小区，包含一个PSCell，还可以包含一个或多个SCell。所述PCell是一个工作在主载波频率上的小区，UE在所述小区上执行初始连接建立过程或启动连接重建过程或在切换过程中指示为PCell。所述PSCell是SCG小区，当执行SCG改变过程时UE执行随即接入的小区。所述SCell是工作在辅载波频率上的小区，所述SCell可以在无线资源控制连接RRC建立之后配置且可以提供额外的无线资源。
下面描述本申请中涉及的各信元的定义。需要说明的是，本申请中没有明确指出各信元对应的无线通讯系统类型是NR、LTE、eLTE中的哪种，而是采用LTE中使用的方式命名，但是本申请不限于所述命名方式，本申请还支持采用不同的命名方式。。但是，本领域技术人员可以根据双连接所涉及的MeNB和SeNB类型可以判断对应的信元是针对哪类基站(小区组)对应的实体。
scg-Configuration信元：包含释放或配置或修改SCG的相关信息。当辅基站(或辅小区组)的类型不同时，可能其名称也不同。例如，当SeNB为LTE时，记为scg-ConfigurationLTE；当SeNB为eLTE时，记为 scg-ConfigurationeLTE；当SeNB为NR时，记为scg-ConfigurationNR。
drb-ToAddModListSCG信元：一组需要增加或修改的SeNB的DRB；所述DRB可以是SCG DRB、MCG分离DRB、SCG分离DRB。当配置了SCG时，E-UTRAN或NR配置至少一个SCG DRB或MCG分离DRB或SCG分离DRB。所述drb-ToAddModListSCG信元可以包含在信元radioResourceConfigDedicatedSCG中，所述radioResourceConfigDedicatedSCG用于配置SCG的无线资源。
drb-ToAddModList信元：一组需要增加或修改的DRB；所述drb-ToAddModList信元可以包含在信元radioResourceConfigDedicated中，所述radioResourceConfigDedicated用于建立/修改/释放RBs、修改MAC主配置、修改SPS配置和修改特定物理层配置。
pdcp-Config信元：包含DRB的可配置的PDCP参数；
drb-Identity信元：数据承载DRB标识；
rlc-Config信元：包含SRB和DRB对应的RLC实体的配置信息；
logicalChannelIdentity信元：逻辑信道标识；
logicalChannelConfig信元：包含用于配置逻辑信道的参数。
需要说明的是，不同的部署场景下或不同的无线通信系统中，基站、主基站、辅基站、小区、主小区组、辅小区组、数据承载DRB、核心网、各个实体等命名可能不一样，本申请也适用于在不同部署场景或不同的无线通信系统中采用不同名称的方式。
图5示出了LTE双连接部署方式中涉及的无线协议层2实体，包含分组数据汇聚协议PDCP实体、无线链路控制RLC实体和媒体访问控制MAC实体。MeNB和SeNB间的接口记为X2，控制面数据和用户面数据可以在同一接口上传输或在不同的接口上传输。PDCP实体提供的功能包括为来自EPC的数据分配序列号SN、头压缩ROHC、完整性保护(仅控制面)、加密、增加PDCP头、路由等。需要说明的是，并不是所有的承载都需要PDCP实体提供的所有功能。例如，信令承载不需要路由、数据承载不需要完整性保护、双连接部署中的分离承载不需要进行头压缩等。RLC实体提供的功能包括：传输数据缓存、分段/级联、重传、增加RLC头等。根据所配置的RLC模式的不同，RLC实体提供的功能也不同。例如RLC非确认模式 (RLC UM)没有重传功能，而RLC确认模式(RLC AM)具有重传功能。MAC实体提供的功能包括：复用/解复用、逻辑信道优先级(仅用于上行)、随机接入、HARQ等。需要说明的是，在双连接中，UE可以包含两个MAC，一个与MCG对应，另一个与SCG对应。
在NR和/或eLTE通信系统中，无线协议层也需要PDCP实体、RLC实体、MAC实体提供的全部或部分功能，还可能包含PDCP实体、RLC实体、MAC实体未提供的其他功能，例如光束(Bean)管理功能。功能的组合方式以及分层方式也可能不同于LTE，例如，在NR中，可以整合PDCP实体和RLC实体的重排序功能，仅在一个实体中提供，例如仅在PDCP中提供重排序功能。本申请不限于LTE的PDCP实体、RLC实体、MAC实体所提供的功能的组合方式和分层方式。本申请适用于在NR或eLTE中，可能存在更多的实体(层)或更少的实体(层)，例如NR中可能只有两层，分为层2的高层和层2的低层。
本申请中，LTE的PDCP实体、RLC实体、MAC实体分别标记为LTE PDCP实体、LTE RLC实体、LTE MAC实体；eLTE的PDCP实体、RLC实体、MAC实体分别标记为eLTE PDCP实体、eLTE RLC实体、eLTE MAC实体；NR的PDCP实体、RLC实体、MAC实体分别标记为NR PDCP实体、NR RLC实体、NR MAC实体；以示区分。在各个实施例中如果没有明确指出PDCP实体、RLC实体、MAC实体具体对应的实体类型，即没有明确指示PDCP实体、RLC实体、MAC实体对应LTE、eLTE、NR中哪类实体，则根据双连接的MeNB和SeNB的类型可以推断出对应的PDCP实体、RLC实体、MAC实体类型及对应实体的配置信息。
在本申请中，PDCP实体作为MeNB和/或SeNB中实现数据分离和/或汇聚的实体，即用户面数据经过PDCP实体处理，一部分数据利用PDCP实体所在的基站提供的资源进行传输，另一部分数据发往/来自另一基站并利用所述基站提供的资源进行传输。可选的，所述通过SeNB传输的数据还经过另一个实体处理(称为LNAAP实体)，所述LNAAP实体负责将来自/去往PDCP实体的数据按照双连接部署所要求的形式封装/解封装后，并发往/来自SeNB。例如LNAAP实体给每个来自PDCP实体的PDCP PDU增加DRB标识等。
需要说明的是，对应不同的MeNB类型(例如NR MgNB、LTE MeNB和eLTE MeNB)，实现数据分离和或汇聚的实体的名称可能不同，但本申请中将其统一称为PDCP实体，所述实体可以实现数据分离和/或汇聚的功能。
图6示出了根据本申请一个实施例的用于建立/重配置数据承载的方法的流程图。图6所示方法可以应用于在NR、LTE、eLTE双连接部署场景中建立MCG承载、SCG承载、MCG分离承载、SCG分离承载的过程。以下均以数据承载DRB为类说明。需要说明的是，本申请并不限于所述命名，本申请也适用于在eLTE或NR中可能采用的命名方式不同的情况。
如图6所示，方法600在步骤S610处开始。在步骤S620，接收数据承载建立/重配置请求消息。请求消息可以包括数据承载标识和承载类型指示信元。其中，数据承载标识用于标识数据承载，而承载类型指示信元用于指示要建立的/要重配置的数据承载的类型。在步骤S630，根据所述请求消息，建立/重配置相应的数据承载。最后，方法600在步骤S640处结束。
下面，分别按照建立数据承载和重配置数据承载两个方面对图6所示的方法进行具体描述。
建立数据承载
以下采用类似LTE和WLAN聚合(LWA)中LWA承载建立过程的描述方式描述LTE、eLTE、NR双连部署场景中MCG承载、SCG承载、MCG分离承载、SCG分离承载的建立过程。
在步骤S620，接收DRB建立请求消息。该请求消息用于建立相应的承载。承载建立请求消息可以是LTE或eLTE或NR无线资源控制RRC重配置消息。这依赖于双连接部署场景：如果是LTE eNB为主基站，可以称为LTE无线资源控制重配置消息；如果是eLTE eNB为主基站，可以称为eLTE无线资源控制重配置消息；如果是NR gNB为主基站，可以称为NR无线资源控制重配置消息。优选地，无线资源控制消息中可以包含来自两种或两种以上无线接入技术RAT的无线资源控制消息。
DRB建立请求消息中借以包含DRB标识drb-Identity。具体地，drb-Identity可以包含在信元ToAddModList中。DRB标识用于唯一标识这个DRB(例如，在UE中唯一标识一个DRB)。DRB建立请求消息中可以包 含承载类型指示信元drb-TypeLNA，承载类型指示信元drb-TypeLNA用于指示要建立的承载类型。例如，当LTE为主基站，NR为辅基站时，承载类型指示信元可以指示的DRB类型为：LTE-NR MCG承载、LTE-NR SCG承载、LTE-NR MCG分离承载、LTE-NR SCG分离承载。上述过程可以类似的推广到其他的双连接组合的场景。
在步骤S630，根据所DRB建立请求消息来建立相应的DRB。
具体地，对于DRB建立请求消息中包含的承载标识drb-Identity，且承载标识对应的承载不是UE已配置的承载，可以执行以下步骤：
-如果承载类型指示信元drb-TypeLNA指示对应的DRB为MCG承载；则执行MCG承载的建立过程。
-如果承载类型指示信元drb-TypeLNA指示对应的DRB为SCG承载；则执行SCG承载的建立过程。
-如果承载类型指示信元drb-TypeLNA指示对应的DRB为MCG分离承载；则执行MCG分离承载的建立过程。
-如果承载类型指示信元drb-TypeLNA指示对应的DRB为SCG分离承载；则执行SCG分离承载的建立过程。
可选的，在执行上述步骤前，UE还可以根据DRB建立/重配置请求消息携带的信元，按照区别双连接类型的方式确定SeNB类型。
可选的，在建立DRB后向上层指示DRB的建立及其标识。
需要说明的是，上述各个步骤不分先后顺序且都是可选的执行(只有定义了对应类型的承载对应步骤才可能执行)。
重配置数据承载
以下采用类似LTE和WLAN聚合(LWA)中LWA承载建立过程的描述方式描述LTE、eLTE、NR双连部署场景中承载重配置过程。
在步骤S620，接收承载重配置消息。承载重配置消息可以用于修改/重配置UE中已配置的承载。承载重配置消息可以是LTE或eLTE或NR无线资源控制RRC重配置消息。承载重配置消息可以包含承载重配置指示信元drb-TypeChangeLNA，该承载重配置指示信元指示重配置的承载类型。
另外，承载重配置可以包含：MCG承载重配置为SCG承载和/或MCG承载重配置为MCG分离承载和/或MCG承载重配置为SCG分离承载和/或SCG承载重配置为MCG承载和/或SCG承载重配置为SCG分离承载和/或SCG承载重配置为MCG分离承载和/或SCG分离承载重配置为MCG承载和/或SCG分离承载重配置为SCG承载和/或SCG分离承载重配置为MCG分离承载和/或MCG分离承载重配置为MCG承载和/或MCG分离承载重配置为SCG承载和/或MCG分离承载重配置为SCG分离承载和/或重配置MCG承载和/或重配置SCG承载和/或重配置MCG分离承载和/或重配置SCG分离承载。
在步骤S630，根据承载重配置消息重配置承载。具体地，对于承载重配置消息中包含的承载标识drb-Identity，且承载标识对应的承载是UE已配置的承载，则执行以下步骤：
-UE中配置的承载标识drb-Identity对应的承载是MCG承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为MCG分离承载，则执行MCG承载重配置为MCG分离承载过程。
-UE中配置的承载标识drb-Identity对应的承载是MCG承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为SCG承载，则执行MCG承载重配置为SCG承载过程。
-UE中配置的承载标识drb-Identity对应的承载是MCG承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为SCG分离承载，则执行MCG承载重配置为SCG分离承载过程。
-UE中配置的承载标识drb-Identity对应的承载是SCG承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为MCG承载，则执行SCG承载重配置为MCG承载过程。
-UE中配置的承载标识drb-Identity对应的承载是SCG承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为SCG分离承载，则执行SCG承载重配置为SCG分离承载过程。
-UE中配置的承载标识drb-Identity对应的承载是SCG承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为MCG分离承载，则执行SCG承载重配置为MCG分离承载过程。
-UE中配置的承载标识drb-Identity对应的承载是SCG分离承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为SCG承载，则执行SCG分离承载重配置为SCG承载过程。
-UE中配置的承载标识drb-Identity对应的承载是SCG分离承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为MCG承载，则执行SCG分离承载重配置为MCG承载过程。
-UE中配置的承载标识drb-Identity对应的承载是SCG分离承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为MCG分离承载，则执行SCG分离承载重配置为MCG分离承载过程。
-UE中配置的承载标识drb-Identity对应的承载是MCG分离承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为SCG承载，则执行MCG分离承载重配置为SCG承载过程。
-UE中配置的承载标识drb-Identity对应的承载是MCG分离承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为MCG承载，则执行MCG分离承载重配置为MCG承载过程。
-UE中配置的承载标识drb-Identity对应的承载是MCG分离承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为SCG分离承载，则执行MCG分离承载重配置为SCG分离承载过程。
-UE中配置的承载标识drb-Identity对应的承载是MCG承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为MCG承载(或不含所述承载重配置指示信元)，则执行MCG承载重配置过程。
-UE中配置的承载标识drb-Identity对应的承载是SCG承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为SCG承载(或不含所述承载重配置指示信元)，则执行SCG承载重配置过程。
-UE中配置的承载标识drb-Identity对应的承载是MCG分离承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为MCG分离承载(或不含所述承载重配置指示信元)，则执行MCG分离承载重配置过程。
-UE中配置的承载标识drb-Identity对应的承载是SCG分离承载且承载重配置指示信元drb-TypeChangeLNA指示的重配置承载类型为SCG分离承载(或不含所述承载重配置指示信元)，则执行SCG分离承载重配置过程。
需要说明的是，上述步骤不分先后顺序且都是可选的执行(只有定义了对应类型的承载重配置对应步骤才可能执行)。
区别双连接类型的方式
由于双连接分为X-X双连接(主基站和辅基站为同一类型的基站)和X-Y双连接(主基站和辅基站为不同类型的基站，又称为混合双连接)，X和Y可以是eLTE eNB或LTE eNB或gNB。可以在DRB建立请求消息和/或DRB重配置消息中指明辅基站(或SCG或RAT)类型，DRB建立请求消息和/或DRB重配置消息可以为RRC重配置消息。
具体地，在一个实施例中，DRB建立请求消息和/或DRB重配置消息中包含承载类型指示信元(记为drb-TypeSCG)，drb-TypeSCG用于指示所要建立或重配置的辅基站(或SCG或RAT或DRB)类型。在一个实施例中，承载类型指示信元drb-TypeSCG取值可以来自集合{LTE eNB、eLTE eNB、gNB}或{LTE SCG、eLTE SCG、NR SCG}或{LTE、eLTE、NR}或用两比特表示。在另一个实施例中，在UE已经确定主基站类型的情况下，混合双连接辅基站类型只能为另外两种基站之一。如果对于某种类型的主基站，混合双连接的辅基站类型只能是某种类型，当所述承载类型指示信元的值设置为“True”或“Setup”或“1”时，辅基站为对应类型基站的混合双连接；以及当所述承载类型指示信元的值设置为“False”或“Release”或“0”或所述指示不出现时，辅基站的类型与主基站相同。反之亦然。
UE可以根据drb-TypeSCG的取值确定辅基站(或SCG或RAT)类型；UE可以根据执行初始随机接入的基站类型确定主基站(或MCG或RAT)的类型。
在另一个实施例中，不同的类型的SCG(或SCell)包含在不同类型的信元中，UE根据所述接收到的信元来判断对应的SCG或SCell或SeNB类型。例如，在混合双连接中，辅基站为NR类型的小区包含在信元sCellToAddModListNR(用于指示增加/修改的SCG SCell列表)和/或sCellToAddModNR(用于指示增加/修改的SCG SCell的相关信息，如小区标识等)中，当UE接收到承载建立或重配置消息中包含sCellToAddModListNR和/或sCellToAddModNR，则UE确定SCG或SeNB或SCell的类型为NR。
在另一个实施例中，不同的SCG对应不同的配置信元，例如当SeNB 为NR时，对应的SCG配置信元记为scg-ConfigurationNR；当SeNB为LTE时，对应的SCG配置信元记为scg-ConfigurationLTE；当SeNB为eLTE时，对应的SCG配置信元记为scg-ConfigurationeLTE；UE可以根据所携带的SCG配置信元判断辅基站(或SCG或RAT)的类型，UE可以根据执行初始随机接入的基站类型确定主基站(或MCG或RAT)的类型。
在本申请实施例中，可以将不同的SCG配置信元统一表示为scg-Configuration。对于特定的双连接部署场景，根据SeNB的类型可以将scg-Configuration替换为对应类型的SCG配置信元。
以下采用类似LTE双连接中数据承载建立过程的描述方式描述LTE、eLTE、NR双连部署场景中MCG承载、SCG承载、MCG分离承载、SCG分离承载的建立和/或重配置过程。
首先，接收RB建立/重配置请求消息。承载建立/重配置请求消息用于建立/修改/重配置相应的承载。承载建立/重配置请求消息可以是LTE或eLTE或NR无线资源控制RRC重配置消息。这依赖于双连接部署场景：如果LTE为主基站，可以称为LTE RRC重配置消息；如果eLTE为主基站，可以称为eLTE RRC重配置消息；如果NR为主基站，可以称为NR RRC重配置消息。优选地，RRC重配置消息中可以包含来自两种或两种以上无线接入技术(RAT)的RRC重配置信息。
然后，根据DRB建立/重配置请求消息建立/修改/重配置对应的承载。
具体地，在一个实施例中，如果scg-configuration置为release且UE配置了一个或多个MCG分离DRB或SCG DRB或SCG分离DRB且接收到的DRB建立/重配置请求消息中包含drb-ToAddModList，执行以下步骤9001～9020所述的DRB的建立或修改或重配置过程。
如果scg-configuration置为release或DRB建立/重配置请求消息中包含改变SCG的指示(记为mobilityControlInfoSCG)但其中不包含切换指示(记为mobilityControlInfo)，则对UE中每个配置的drb-Identity：
-如果对应的DRB是MCG分离DRB，则执行PDCP数据恢复和重建SCG RLC实体；
-如果对应的DRB是MCG DRB，且接收到drb-ToAddModListSCG且其中包含drb-Identity且对应的承载重配置指示标识(记为 drb-TypeChangeLN)指示SCG DRB，则重建PDCP实体和MCG RLC实体；
-如果对应的DRB是MCG DRB，且接收到drb-ToAddModListSCG且其中包含drb-Identity且对应的承载重配置指示标识(记为drb-TypeChangeLN)指示SCG分离DRB，则重建PDCP实体(或执行PDCP数据恢复)和/或重建MCG RLC实体；
-如果对应的DRB是SCG DRB，则重建PDCP实体和SCG RLC实体；如果对应的DRB是SCG分离DRB，则重建PDCP实体(或执行PDCP数据恢复)和重建SCG RLC实体。
本申请实施例中所述的重建PDCP实体和/或PDCP数据恢复过程至少包含以下操作之一(还可能包含其他操作)：
-如果上层为对应的DRB配置发送PDCP状态报告，则生成所述PDCP状态报告并发送给下层作为第一个PDCP PDU进行传输；
-执行PDCP PDU的重传操作，所述PDCP PDU尚未被低层确认传输成功。
在一个实施例中，如果收到的DRB建立/重配置请求消息不是用于释放SCG(例如，scg-Configuration不置为release)且不包含指示SCG改变的信元(记为mobilityControlInfoSCG)；更进一步，如果DRB建立/重配置请求消息中包含drb-ToAddModListSCG，对drb-ToAddModListSCG中包含的每个drb-Identity，执行以下步骤9001～9020所述的DRB的建立或修改或重配置过程：
步骤9001、如果drb-Identity在UE中未配置，则执行步骤9002；否则，执行步骤9005；
步骤9002、如果接收到的DRB建立/重配置请求消息中包含drb-ToAddModList且所述drb-Identity包含在drb-ToAddModList中。进一步的，在一个实施例中，如果所述RRC重配置消息中包含分离承载类型指示标识(记为drb-TypeSplit，每个DRB对应一个drb-TypeSplit)，且所述指示标识指示建立MCG分离承载，则建立MCG分离DRB；否则，执行步骤9003a；在另一实施例中，根据PDCP-config包含在drb-ToAddModList还是drb-ToAddModListSCG中，判断分离承载类型。具体地，如果PDCP-config 包含在drb-ToAddModList中，则建立MCG分离DRB；否则，执行步骤9003b；
步骤9003a、如果接收到的DRB建立/重配置请求消息中包含drb-ToAddModList且所述drb-Identity包含在drb-ToAddModList中。进一步，如果所述RRC重配置消息中包含分离承载类型指示标识(记为drb-TypeSplit)，所述指示标识指示建立SCG分离承载，则建立SCG分离DRB；否则，执行步骤9004；
步骤9003b、如果接收到的DRB建立/重配置请求消息中包含drb-ToAddModList且所述drb-Identity包含在drb-ToAddModList中。进一步，根据PDCP-config包含在drb-ToAddModList还是drb-ToAddModListSCG中，判断分离承载类型。具体地，如果PDCP-config包含在drb-ToAddModListSCG中，则建立SCG分离DRB；否则，执行步骤9004；
步骤9004、建立SCG承载
具体地，在一个实施例中，UE判断接收到的DRB建立/重配置请求消息中不包含drb-ToAddModList，或者虽然包含drb-ToAddModList，但所述drb-Identity不包含在drb-ToAddModList中，或者RRC重配置消息中包含分离承载类型指示标识(记为drb-TypeSplit)，所述指示标识指示建立SCG承载，则建立SCG承载。步骤9005、如果接收到drb-ToAddModList和/或drb-ToAddModListSCG，执行步骤9006；
步骤9006、如果drb-Identity指示的DRB是MCG分离DRB，执行步骤9007；否则，执行步骤9010；
步骤9007、如果接收到drb-ToAddModList且其中包含drb-Identity且包含对应的承载重配置指示标识(记为drb-TypeLN)；如果所述承载重配置指示标识指示为MCG DRB，执行重配置MCG分离DRB为MCG DRB过程；否则，执行步骤9008；
步骤9008、如果接收到drb-ToAddModList和drb-ToAddModListSCG且其中均包含drb-Identity且包含对应的承载重配置指示标识(记为drb-TypeLN和/或drb-TypeChangeLN，两者可以采用同一个信元表示，drb-TypeLN包含在drb-ToAddModList中，drb-TypeChangeLN包含在drb-ToAddModListSCG中，在DRB建立/重配置请求消息可以仅包含一个或两个均包含，如果两个均包含，则两者指示同一种DRB。下同)；如果承载重配置指示标识指示为SCG分离DRB，执行重配置MCG分离DRB为SCG 分离DRB过程；否则，执行步骤9009；
步骤9009、如果接收到drb-ToAddModListSCG且其中包含drb-Identity且包含对应的承载重配置指示标识(记为drb-TypeChangeLN)；如果所述承载重配置指示标识指示为SCG DRB，执行重配置MCG分离DRB为SCG DRB过程；否则，执行步骤9010；
步骤9010、执行重配置MCG分离DRB过程；
步骤9011、如果drb-Identity指示的DRB是SCG分离DRB，执行步骤9012；否则，执行步骤9016；
步骤9012、如果接收到drb-ToAddModListSCG且其中包含drb-Identity且包含对应的承载重配置指示标识(记为drb-TypeChangeLN)；如果承载重配置指示标识指示为SCG DRB，执行重配置SCG分离DRB为SCG DRB过程；否则，执行步骤9013；
步骤9013、如果接收到drb-ToAddModList且其中包含drb-Identity且包含对应的承载重配置指示标识(记为drb-TypeLN)；如果承载重配置指示标识指示为MCG DRB，执行重配置SCG分离DRB为MCG DRB过程；否则，执行步骤9014；
步骤9014、如果接收到drb-ToAddModList和drb-ToAddModListSCG且其中均包含drb-Identity且包含对应的承载重配置指示标识(记为drb-TypeLN和/或drb-TypeChangeLN)；如果承载重配置指示标识指示为MCG分离DRB，执行重配置SCG分离DRB为MCG分离DRB过程；否则，执行步骤9015；
步骤9015、执行重配置SCG分离DRB过程；
步骤9016、如果drb-Identity指示的DRB是SCG DRB，执行步骤9017；
步骤9017、如果接收到drb-ToAddModList和drb-ToAddModListSCG且其中均包含drb-Identity且包含对应的承载重配置指示标识(记为drb-TypeLN和/或drb-TypeChangeLN)；如果承载重配置指示标识指示为SCG分离DRB，执行重配置SCG DRB为SCG分离DRB过程；否则，执行步骤9018；
步骤9018、如果接收到drb-ToAddModList且其中包含drb-Identity且包含对应的承载重配置指示标识(记为drb-TypeLN)；如果承载重配置指示标识指示为MCG DRB，执行重配置SCG DRB为MCG DRB过程；否则，执 行步骤9019；
步骤9019、如果接收到drb-ToAddModList和drb-ToAddModListSCG且其中均包含drb-Identity且包含对应的承载重配置指示标识(记为drb-TypeLN和/或drb-TypeChangeLN)；如果承载重配置指示标识指示为MCG分离DRB，执行重配置SCG DRB为MCG分离DRB过程；否则，执行步骤9020；
步骤9020、执行重配置SCG DRB过程；
可选的，向上层指示步骤9002或9003或9004中所建立的DRB及其标识。
可选的，在执行上述步骤前，UE还需要根据DRB建立/重配置请求消息消息携带的信元按照区别双连接类型的方式确定SeNB类型。
步骤9002～9004描述了承载建立过程。步骤9005～9020描述了承载修改/重配置过程。
步骤9007～9009和/或9012～9014和/或9017～9019也可以不根据承载重配置指示标识来确定DRB类型，而是根据PDCP的配置信元pdcp-Config是位于drb-ToAddModList还是drb-ToAddModListSCG来确定DRB类型。如果pdcp-Config是位于drb-ToAddModList，则为MCG分离DRB；如果pdcp-Config是位于drb-ToAddModListSCG，则为SCG分离DRB。
需要说明的是，上述步骤9001～9020只有在对应的双连接部署场景支持对应的承载类型和承载重配置类型时才可能执行，例如，如果某种双连接部署不支持重配置MCG分离DRB为SCG DRB时，则不执行步骤9009。步骤9002和步骤9004中所述分离承载类型指示标识drb-TypeSplit的取值说明：在一个实施例中，当所述指示标识的值设置为“True”或“Setup”或“1”或“MCGSplit”时，对应的MCG分离承载；以及当所述指示的值设置为“False”或“Release”或“0”或“SCGSplit”或所述指示不出现时，对应的SCG分离承载。反之亦然。此外，步骤9001～9020只是一种示例执行顺序，按照其他顺序执行也在本申请范围内。
需要说明的是，根据具体的双连接场景中SCG或SeNB的类型，本申请实施例中涉及的scg-Configuration可以记为scg-ConfigurationNR或scg-ConfigurationLTE或scg-ConfigurationeLTE(具体类型依赖于SeNB的类型)。
图7示出了根据本申请另一个实施例的用于建立/重配置数据承载的方法的流程图。如图7所示，方法700在步骤S710处开始。在步骤S720，发送数据承载建立/重配置请求消息。该请求消息可以包括数据承载标识和承载类型指示信元。其中，数据承载标识用于标识数据承载，而承载类型指示信元用于指示要建立的/要重配置的数据承载的类型。在步骤S730，使用建立/重配置的相应数据承载进行通信。最后，方法700在步骤S740处结束。
以下描述本申请中涉及的建立/重配置数据承载的各种具体示例过程。
MCG承载建立过程
建立MCG DRB涉及以下操作：
建立PDCP实体，并根据MCG的安全配置和包含在drb-ToAddModList中的信元pdcp-Config配置所述PDCP实体；
根据drb-ToAddModList中包含的rlc-Config、逻辑信道标识ligicalChannelIdentity和logicalChannelConfig信元，建立MCG RLC实体和MCG DTCH逻辑信道；
SCG承载建立过程
建立SCG DRB涉及以下操作：
建立PDCP实体，并根据SCG的安全配置和包含在drb-ToAddModListSCG中的信元pdcp-Config配置所述PDCP实体；
根据drb-ToAddModListSCG中包含的rlc-ConfigSCG、逻辑信道标识ligicalChannelIdentitySCG和logicalChannelConfigSCG信元，建立SCG RLC实体和SCG DTCH逻辑信道；
MCG分离承载建立过程：
建立MCG分离DRB涉及以下操作：
建立PDCP实体，并根据MCG的安全配置和包含在drb-ToAddModList中的信元pdcp-Config配置所述PDCP实体；
根据drb-ToAddModList中包含的rlc-Config、逻辑信道标识ligicalChannelIdentity和logicalChannelConfig信元，建立MCG RLC实体和 MCG DTCH逻辑信道；
根据drb-ToAddModListSCG中包含的rlc-ConfigSCG、逻辑信道标识ligicalChannelIdentitySCG和logicalChannelConfigSCG信元，建立SCG RLC实体和SCG DTCH逻辑信道；
SCG分离承载建立过程：
建立SCG分离DRB涉及以下操作：
建立PDCP实体，并根据SCG的安全配置和包含在drb-ToAddModListSCG中的信元pdcp-Config配置所述PDCP实体；
根据drb-ToAddModList中包含的rlc-Config、逻辑信道标识ligicalChannelIdentity和logicalChannelConfig信元，建立MCG RLC实体和MCG DTCH逻辑信道；
根据drb-ToAddModListSCG中包含的rlc-ConfigSCG、逻辑信道标识ligicalChannelIdentitySCG和logicalChannelConfigSCG信元，建立SCG RLC实体和SCG DTCH逻辑信道；
MCG承载重配置为SCG承载过程
MCG承载重配置为SCG承载包含以下操作：
根据SCG的安全配置信息重配置PDCP实体，且如果drb-ToAddModListSCG包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
如果drb-ToAddModListSCG包含rlc-ConfigSCG和/或logicalChannelConfigSCG信元，根据所述信元重配置SCG RLC实体和/或SCG DTCH逻辑信道；
释放MCG RLC和MCG DTCH逻辑信道。
MCG承载重配置为MCG分离承载过程
MCG承载重配置为MCG分离承载包含以下操作：
如果drb-ToAddModList包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
根据drb-ToAddModListSCG中包含的rlc-ConfigSCG、逻辑信道标识 ligicalChannelIdentitySCG和logicalChannelConfigSCG信元，建立SCG RLC实体和SCG DTCH逻辑信道；
如果drb-ToAddModList包含rlc-Config和/或logicalChannelConfig信元，根据所述信元重配置MCG RLC实体和/或MCG DTCH逻辑信道。
MCG承载重配置为SCG分离承载过程
MCG承载重配置为SCG分离承载包含以下操作：
根据SCG的安全配置信息重配置PDCP实体，且如果drb-ToAddModListSCG包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
如果drb-ToAddModList包含rlc-Config和/或logicalChannelConfig信元，根据所述信元重配置MCG RLC实体和/或MCG DTCH逻辑信道；
如果drb-ToAddModListSCG包含rlc-ConfigSCG和/或logicalChannelConfigSCG信元，根据所述信元重配置SCG RLC实体和/或SCG DTCH逻辑信道。
MCG分离承载重配置为MCG承载过程
MCG分离承载重配置为MCG承载包含以下操作：
释放SCG RLC和SCG DTCH逻辑信道。
如果drb-ToAddModList包含rlc-Config和/或logicalChannelConfig信元，根据所述信元重配置MCG RLC实体和/或MCG DTCH逻辑信道；
MCG分离承载重配置为SCG承载过程
MCG分离承载重配置为SCG承载包含以下操作：
根据SCG的安全配置信息重配置PDCP实体，且如果drb-ToAddModListSCG包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
如果drb-ToAddModListSCG包含rlc-ConfigSCG和/或logicalChannelConfigSCG信元，根据所述信元重配置SCG RLC实体和/或SCG DTCH逻辑信道。
释放MCG RLC和MCG DTCH逻辑信道。
MCG分离承载重配置为SCG分离承载过程
MCG分离承载重配置为SCG分离承载包含以下操作：
根据SCG的安全配置信息重配置PDCP实体，且如果drb-ToAddModListSCG包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
如果drb-ToAddModList包含rlc-Config和/或logicalChannelConfig信元，根据所述信元重配置MCG RLC实体和/或MCG DTCH逻辑信道；
如果drb-ToAddModListSCG包含rlc-ConfigSCG和/或logicalChannelConfigSCG信元，根据所述信元重配置SCG RLC实体和/或SCG DTCH逻辑信道。
SCG承载重配置为MCG承载过程
SCG承载重配置为MCG承载包含以下操作：
根据MCG的安全配置信息重配置PDCP实体，且如果drb-ToAddModList包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
如果drb-ToAddModList包含rlc-Config和/或logicalChannelConfig信元，根据所述信元重配置MCG RLC实体和/或MCG DTCH逻辑信道；
释放SCG RLC和SCG DTCH逻辑信道。
SCG承载重配置为SCG分离承载过程
SCG承载重配置为SCG分离承载包含以下操作：
如果drb-ToAddModListSCG包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
根据drb-ToAddModList中包含的rlc-Config、逻辑信道标识ligicalChannelIdentity和logicalChannelConfig信元，建立MCG RLC实体和MCG DTCH逻辑信道；
如果drb-ToAddModListSCG包含rlc-ConfigSCG和/或logicalChannelConfigSCG信元，根据所述信元重配置SCG RLC实体和/或SCG DTCH逻辑信道。
SCG承载重配置为MCG分离承载过程
SCG承载重配置为MCG分离承载包含以下操作：
根据MCG的安全配置信息重配置PDCP实体，且如果drb-ToAddModList包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
根据drb-ToAddModList中包含的rlc-Config、逻辑信道标识ligicalChannelIdentity和logicalChannelConfig信元，建立MCG RLC实体和MCG DTCH逻辑信道；
如果drb-ToAddModListSCG包含rlc-ConfiSCGg和/或logicalChannelConfigSCG信元，根据所述信元重配置SCG RLC实体和/或SCG DTCH逻辑信道.
SCG分离承载重配置为MCG承载过程
SCG分离承载重配置为MCG承载包含以下操作：
根据MCG的安全配置信息重配置PDCP实体，且如果drb-ToAddModList包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
如果drb-ToAddModList包含rlc-Config和/或logicalChannelConfig信元，根据所述信元重配置MCG RLC实体和/或MCG DTCH逻辑信道；
释放SCG RLC和SCG DTCH逻辑信道。
SCG分离承载重配置为SCG承载过程
SCG分离承载重配置为SCG承载包含以下操作：
如果drb-ToAddModListSCG包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
如果drb-ToAddModListSCG包含rlc-Config和/或logicalChannelConfig信元，根据所述信元重配置SCG RLC实体和/或SCG DTCH逻辑信道；
释放MCG RLC和MCG DTCH逻辑信道。
SCG分离承载重配置为MCG分离承载过程
SCG分离承载重配置为MCG分离承载包含以下操作：
根据MCG的安全配置信息重配置PDCP实体，且如果drb-ToAddModList包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
如果drb-ToAddModList包含rlc-Config和/或logicalChannelConfig信元，根据所述信元重配置MCG RLC实体和/或MCG DTCH逻辑信道；
如果drb-ToAddModListSCG包含rlc-ConfigSCG和/或logicalChannelConfigSCG信元，根据所述信元重配置SCG RLC实体和/或SCG DTCH逻辑信道。
重配置MCG承载过程
重配置MCG承载包含以下操作：
如果drb-ToAddModList包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
如果drb-ToAddModList包含rlc-Config和/或logicalChannelConfig信元，根据所述信元重配置MCG RLC实体和/或MCG DTCH逻辑信道；
重配置SCG承载过程
重配置SCG承载包含以下操作：
如果drb-ToAddModListSCG包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
如果drb-ToAddModListSCG包含rlc-ConfigSCG和/或logicalChannelConfigSCG信元，根据所述信元重配置SCG RLC实体和/或SCG DTCH逻辑信道；
重配置MCG分离承载过程
重配置MCG分离承载包含以下操作：
如果drb-ToAddModList包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
如果drb-ToAddModList包含rlc-Config和/或logicalChannelConfig信元，根据所述信元重配置MCG RLC实体和/或MCG DTCH逻辑信道；
如果drb-ToAddModListSCG包含rlc-ConfigSCG和/或logicalChannelConfigSCG信元，根据所述信元重配置SCG RLC实体和/或SCG DTCH逻辑信道。
重配置SCG分离承载过程
重配置SCG分离承载包含以下操作：
如果drb-ToAddModListSCG包含信元pdcp-Config，根据所述pdcp-Config重配置PDCP实体；
如果drb-ToAddModList包含rlc-Config和/或logicalChannelConfig信元，根据所述信元重配置MCG RLC实体和/或MCG DTCH逻辑信道；
如果drb-ToAddModListSCG包含rlc-ConfigSCG和/或logicalChannelConfigSCG信元，根据所述信元重配置SCG RLC实体和/或SCG DTCH逻辑信道。
应当说明的是，在UE确定SeNB类型后，本申请实施例中描述的对SCG相关实体的操作(包含建立和/或修改和/或重配置和/或重建PDCP实体和/或SCG RLC实体和/或SCG DTCH逻辑信道)可以相应的描述为：UE指示NR或/eLTE或LTE相关实体(例如RRC实体，根据SeNB的类型确定对应的RRC实体类型)建立和/或修改和/或重配置和/或重建和/或释放PDCP实体和/或SCG RLC实体和/或SCG DTCH逻辑信道。
相应的在UE确定MeNB类型后，本申请实施例中描述的对MCG相关实体的操作(包含建立和/或修改和/或重配置和/或重建PDCP实体和/或MCG RLC实体和/或MCG DTCH逻辑信道)可以相应的描述为：UE指示NR或/eLTE或LTE相关实体(例如RRC实体，根据MeNB的类型确定对应的RRC实体类型)建立和/或修改和/或重配置和/或重建和/或释放PDCP实体和/或MCG RLC实体和/或MCG DTCH逻辑信道。
如果LTE或eLTE与NR的双连接部署中包含LNAAP实体，则UE在本申请实施例DRB建立或释放或修改或重配置过程还涉及为该DRB使能(建立)或去使能(删除)或配置或重配置LNAAP实体。
图8示出了根据本申请一个实施例的用户设备的框图。如图8所示，用户设备UE 800包括接收单元810和处理单元820。
接收单元810被配置为接收数据承载建立/重配置请求消息。请求消息包括数据承载标识和承载类型指示信元。其中，数据承载标识用于标识数据承载，而承载类型指示信元用于指示要建立的/要重配置的数据承载的类型。
处理单元820被配置为根据请求消息建立/重配置相应的数据承载。具体过程上文已经参照图6进行了详细描述，此处不再赘言。
图9示出了根据本申请一个实施例的基站的框图。如图9所示，基站BS 900包括发送单元910和通信单元920。
发送单元910被配置为发送数据承载建立/重配置请求消息。请求消息包括数据承载标识和承载类型指示信元。其中，数据承载标识用于标识数据承载，而承载类型指示信元用于指示要建立的/要重配置的数据承载的类型。
通信单元920被配置为使用建立/重配置的相应数据承载进行通信。具体过程上文已经参照图7进行了详细描述，此处不再赘言。
需要说明的是，本申请实施例中虽未明确指出主基站和辅基站的类型，但适用于LTE eNB、eLTE eNB和gNB任意组合的双连接部署方式。UE根据其初始接入采用的RAT技术判断主基站类型，例如如果UE在LTE eNB上执行初始随机接入，则对应的MeNB为LTE eNB；如果UE在eLTE eNB上执行初始随机接入，则对应的MeNB为eLTE eNB；如果UE在gNB上执行初始随机接入，则对应的MeNB为gNB。
需要说明的是，本申请在描述上述实施例时，没有具体指明主基站和辅基站类型。本申请适用于主基站可以为LTE eNB和/或eLTE eNB和/或gNB，辅基站可以为LTE eNB和/或eLTE eNB和/或gNB任意两个组合部署场景，也适用于其他的双连接部署场景，例如6G。在不同的通信系统中，采用的术语可能不同，但上述流程仍然适用。
运行在根据本申请的设备上的程序可以是通过控制中央处理单元 (CPU)来使计算机实现本申请的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本申请各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本申请的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本申请并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本申请并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本申请的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本申请也包括不偏离本申请主旨的任何设计改动。另外，可以在权利要求的范围内对本申请进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本申请的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (22)

  1. 一种用于建立/重配置数据承载的方法，包括：
    接收数据承载建立/重配置请求消息，所述请求消息包括数据承载标识和承载类型指示信元，所述数据承载标识用于标识数据承载，所述承载类型指示信元用于指示要建立的/要重配置的数据承载的类型；
    根据所述请求消息，建立/重配置相应的数据承载。
  2. 根据权利要求1所述的方法，其中，数据承载的类型包括主小区组MCG承载、辅小区组SCG承载、MCG分离承载和SCG分离承载。
  3. 根据权利要求1所述的方法，其中，所述数据承载建立/重配置请求消息包括无线资源控制RRC重配置消息。
  4. 根据权利要求3所述的方法，其中，所述RRC重配置消息包括来自两种或更多种无线接入技术RAT的RRC消息。
  5. 根据权利要求1所述的方法，其中，所述数据承载建立/重配置请求消息包括用于指示辅基站类型的信元。
  6. 根据权利要求5所述的方法，其中，根据用于指示辅基站类型的信元的内容，执行相应的用于建立/重配置数据承载的处理。
  7. 一种用户设备，包括：
    接收单元，被配置为接收数据承载建立/重配置请求消息，所述请求消息包括数据承载标识和承载类型指示信元，所述数据承载标识用于标识数据承载，所述承载类型指示信元用于指示要建立的/要重配置的数据承载的类型；
    处理单元，被配置为根据所述请求消息建立/重配置相应的数据承载。
  8. 根据权利要求7所述的用户设备，其中，数据承载的类型包括主小区组MCG承载、辅小区组SCG承载、MCG分离承载和SCG分离承载。
  9. 根据权利要求7所述的用户设备，其中，所述数据承载建立/重配置请求消息包括无线资源控制RRC重配置消息。
  10. 根据权利要求9所述的用户设备，其中，所述RRC重配置消息包括来自两种或更多种无线接入技术RAT的RRC消息。
  11. 根据权利要求7所述的用户设备，其中，所述数据承载建立/重配 置请求消息包括用于指示辅基站类型的信元。
  12. 根据权利要求11所述的用户设备，其中，所述处理单元被配置为：根据用于指示辅基站类型的信元的内容，执行相应的用于建立/重配置数据承载的处理。
  13. 一种用于建立/重配置数据承载的方法，包括：
    发送数据承载建立/重配置请求消息，所述请求消息包括数据承载标识和承载类型指示信元，所述数据承载标识用于标识数据承载，所述承载类型指示信元用于指示要建立的/要重配置的数据承载的类型；
    使用建立/重配置的相应数据承载进行通信。
  14. 根据权利要求13所述的方法，其中，数据承载的类型包括主小区组MCG承载、辅小区组SCG承载、MCG分离承载和SCG分离承载。
  15. 根据权利要求13所述的方法，其中，所述数据承载建立/重配置请求消息包括无线资源控制RRC重配置消息。
  16. 根据权利要求15所述的方法，其中，所述RRC重配置消息包括来自两种或更多种无线接入技术RAT的RRC消息。
  17. 根据权利要求13所述的方法，其中，所述数据承载建立/重配置请求消息包括用于指示辅基站类型的信元。
  18. 一种基站，包括：
    发送单元，被配置为发送数据承载建立/重配置请求消息，所述请求消息包括数据承载标识和承载类型指示信元，所述数据承载标识用于标识数据承载，所述承载类型指示信元用于指示要建立的/要重配置的数据承载的类型；
    通信单元，被配置为使用建立/重配置的相应数据承载进行通信。
  19. 根据权利要求18所述的基站，其中，数据承载的类型包括主小区组MCG承载、辅小区组SCG承载、MCG分离承载和SCG分离承载。
  20. 根据权利要求18所述的基站，其中，所述数据承载建立/重配置请求消息包括无线资源控制RRC重配置消息。
  21. 根据权利要求20所述的基站，其中，所述RRC重配置消息包括来自两种或更多种无线接入技术RAT的RRC消息。
  22. 根据权利要求18所述的基站，其中，所述数据承载建立/重配置请求消息包括用于指示辅基站类型的信元。
PCT/CN2017/097490 2016-09-30 2017-08-15 用于建立/重配置数据承载的方法和设备 Ceased WO2018059147A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/337,340 US11057958B2 (en) 2016-09-30 2017-08-15 Method and device for establishing/reconfiguring data bearer

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610873253.9A CN108307538B (zh) 2016-09-30 2016-09-30 用于建立/重配置数据承载的方法和设备
CN201610873253.9 2016-09-30

Publications (1)

Publication Number Publication Date
WO2018059147A1 true WO2018059147A1 (zh) 2018-04-05

Family

ID=61763687

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/097490 Ceased WO2018059147A1 (zh) 2016-09-30 2017-08-15 用于建立/重配置数据承载的方法和设备

Country Status (3)

Country Link
US (1) US11057958B2 (zh)
CN (1) CN108307538B (zh)
WO (1) WO2018059147A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113573423A (zh) * 2018-05-30 2021-10-29 华为技术有限公司 一种通信方法及装置
EP4030827A4 (en) * 2019-09-30 2022-08-31 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND DEVICE

Families Citing this family (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018089803A1 (en) * 2016-11-14 2018-05-17 Intel IP Corporation Dynamic protocol stack reset during radio handover
EP3582541B1 (en) 2017-03-23 2021-09-22 LG Electronics Inc. Method and device for indicating type of bearer used for next message in wireless communication system
US11483891B2 (en) * 2017-08-11 2022-10-25 Samsung Electronics Co., Ltd. Method for performing bearer type change of a plurality of bearers configured for user equipment
WO2019093828A1 (en) 2017-11-10 2019-05-16 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving data in wireless communication system
CN112738912B (zh) * 2017-11-16 2023-03-14 维沃移动通信有限公司 无线承载的处理方法及网络设备
US11032866B2 (en) * 2017-11-27 2021-06-08 FG Innovation Company Limited Methods and related devices for multi-connectivity
WO2020026835A1 (ja) * 2018-08-01 2020-02-06 日本電気株式会社 無線局、無線通信方法、非一時的なコンピュータ可読媒体及び無線通信システム
CN110839267B (zh) 2018-08-17 2022-01-28 维沃移动通信有限公司 服务节点更新方法、终端设备和网络侧设备
CN111132203B (zh) * 2018-10-31 2021-11-16 维沃移动通信有限公司 一种处理方法及终端
US10893561B2 (en) * 2018-11-16 2021-01-12 T-Mobile Usa, Inc. Signaling reduction in dual connectivity networks
JP6864045B2 (ja) * 2019-07-17 2021-04-21 シャープ株式会社 端末装置、基地局装置、および、方法
US11706672B2 (en) * 2019-09-06 2023-07-18 Qualcomm Incorporated Techniques for prioritization associated with a cell group change
JP6968135B2 (ja) * 2019-10-21 2021-11-17 シャープ株式会社 端末装置、基地局装置、および、方法
CN111432469B (zh) * 2020-03-05 2022-04-12 华为技术有限公司 一种通信方法及相关装置
WO2025048869A1 (en) * 2023-08-31 2025-03-06 Rakuten Symphony, Inc. Supporting multiple bearers for ue with limited lcids
WO2026031601A1 (en) * 2025-04-01 2026-02-12 Lenovo (Beijing) Limited Method and apparatus of supporting non-access stratum (nas) message delivery

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102149139A (zh) * 2010-02-10 2011-08-10 中兴通讯股份有限公司 一种mtc系统的上行数据发送方法和系统
CN103096291A (zh) * 2011-11-04 2013-05-08 华为技术有限公司 一种数据传输方法、移动性管理实体和移动终端
CN104349389A (zh) * 2013-08-02 2015-02-11 上海贝尔股份有限公司 用于建立无线承载的方法和装置
CN105228263A (zh) * 2014-06-30 2016-01-06 中兴通讯股份有限公司 Drb转换方法及装置

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3100578B1 (en) * 2014-01-30 2021-11-10 Sharp Kabushiki Kaisha Systems and methods for dual-connectivity operation
KR102184585B1 (ko) * 2014-03-21 2020-11-30 후아웨이 테크놀러지 컴퍼니 리미티드 이중 연결을 고려한 전력 제한 상황에서의 pusch/pucch 전력 스케일링 방법 및 그 장치
JP2020031254A (ja) * 2016-12-27 2020-02-27 シャープ株式会社 端末装置、基地局装置、通信方法、および、集積回路
WO2018128017A1 (ja) * 2017-01-05 2018-07-12 日本電気株式会社 無線アクセスネットワークノード、無線端末、コアネットワークノード並びにこれらの方法及び非一時的なコンピュータ可読媒体
US10448386B2 (en) * 2017-01-06 2019-10-15 Kt Corporation Method and apparatus for controlling redundant data transmission
CN110324848B (zh) * 2017-06-16 2020-10-16 华为技术有限公司 信息处理方法、通信装置以及计算机存储介质
TWI687122B (zh) * 2017-08-04 2020-03-01 聯發科技股份有限公司 多連接配置之方法及其使用者設備
CN110149730B (zh) * 2018-02-13 2021-01-29 华为技术有限公司 一种通信方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102149139A (zh) * 2010-02-10 2011-08-10 中兴通讯股份有限公司 一种mtc系统的上行数据发送方法和系统
CN103096291A (zh) * 2011-11-04 2013-05-08 华为技术有限公司 一种数据传输方法、移动性管理实体和移动终端
CN104349389A (zh) * 2013-08-02 2015-02-11 上海贝尔股份有限公司 用于建立无线承载的方法和装置
CN105228263A (zh) * 2014-06-30 2016-01-06 中兴通讯股份有限公司 Drb转换方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 13", 3GPP TS 36. 331 V13. 2. 0, June 2016 (2016-06-01) - 11 July 2016 (2016-07-11), XP051123115 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113573423A (zh) * 2018-05-30 2021-10-29 华为技术有限公司 一种通信方法及装置
CN113573423B (zh) * 2018-05-30 2024-01-16 华为技术有限公司 一种通信方法及装置
US12127048B2 (en) 2018-05-30 2024-10-22 Huawei Technologies Co., Ltd. Communication method and communications apparatus and system
EP4030827A4 (en) * 2019-09-30 2022-08-31 Huawei Technologies Co., Ltd. COMMUNICATION METHOD AND DEVICE
US12063562B2 (en) 2019-09-30 2024-08-13 Huawei Technologies Co., Ltd. Communication method and apparatus for releasing a packet data convergence protocol entity of a data radio bearer

Also Published As

Publication number Publication date
US20200037382A1 (en) 2020-01-30
CN108307538A (zh) 2018-07-20
CN108307538B (zh) 2023-05-02
US11057958B2 (en) 2021-07-06

Similar Documents

Publication Publication Date Title
CN108307538B (zh) 用于建立/重配置数据承载的方法和设备
JP7318779B2 (ja) マスター無線アクセスネットワークノード、ａｍｆ、及びこれらの方法
JP7243873B2 (ja) 無線アクセスネットワークノード及び無線端末並びにこれらの方法
CN108924871B (zh) 无线配置方法、用户设备和基站
TWI692988B (zh) 基站、使用者設備和相關方法
TWI678124B (zh) 使用者設備和相關方法
CN108924948B (zh) 用户设备和基站处执行的方法及相应的设备
CN107925931B (zh) 基站及其方法
CN109246766B (zh) 无线配置方法和相应的用户设备
EP3637820B1 (en) Base station, user equipment and relevant methods
JP7416201B2 (ja) 無線アクセスネットワークノード、Ｕｓｅｒ Ｅｑｕｉｐｍｅｎｔ、及びこれらの方法
WO2018228283A1 (zh) 无线通信方法和设备
WO2019157985A1 (zh) 一种无线回传通信处理方法和相关设备
JP2019092058A (ja) 端末装置および方法
JP7645333B2 (ja) 端末装置、通信方法、および基地局装置
JP2019092056A (ja) 端末装置および方法
WO2018054185A1 (zh) 用户设备、基站和相关方法
WO2018059148A1 (zh) 一种数据转发的方法及其设备
JP2019121831A (ja) 端末装置、方法、および、集積回路
JP2019092055A (ja) 端末装置および方法
CN111865520B (zh) 基站、用户设备和相关方法
JP2019092057A (ja) 端末装置および方法

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: 17854599

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17854599

Country of ref document: EP

Kind code of ref document: A1