WO2020200103A1 - 确定承载类型的方法和通信装置 - Google Patents

确定承载类型的方法和通信装置 Download PDF

Info

Publication number
WO2020200103A1
WO2020200103A1 PCT/CN2020/081709 CN2020081709W WO2020200103A1 WO 2020200103 A1 WO2020200103 A1 WO 2020200103A1 CN 2020081709 W CN2020081709 W CN 2020081709W WO 2020200103 A1 WO2020200103 A1 WO 2020200103A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
qos flow
network device
bearer type
message
Prior art date
Application number
PCT/CN2020/081709
Other languages
English (en)
French (fr)
Inventor
彭文杰
王瑞
仇力炜
胡星星
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2020200103A1 publication Critical patent/WO2020200103A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • This application relates to the field of communications, and more specifically, to a method and communication device for determining a bearer type.
  • the master node In a dual connectivity (DC) scenario, the master node (MN) can determine the bearer types of all bearers, and notify the secondary node (SN) after determining the bearer type. If the SN accepts the MN's decision, it generates the corresponding configuration according to the bearer type indicated by the MN.
  • DC dual connectivity
  • the service data adaptation protocol (SDAP) entity is established in the bearer of the SN, and the bearer type can be determined by the SN itself.
  • the MN has a high load, so it tends to build the entire bearer on the SN, and avoid using the master cell group (master cell group, MCG), and the SN may not have a low load. Therefore, based on its own algorithm, the bearer type is set as split bearer, that is, part of the data of the bearer is transmitted by MCG, and part of the data is transmitted by the secondary cell group (SCG). )transmission. This will cause the bearer type determined by the SN to not adapt to the operating conditions of the MN, and affect data transmission.
  • SCG secondary cell group
  • This application provides a method for determining the bearer type, so that the secondary network device can more reasonably determine the quality of service (QoS) or the data radio bearer (DRB) bearer type, thereby helping to improve data Transmission efficiency.
  • QoS quality of service
  • DRB data radio bearer
  • a method for determining a bearer type includes: a secondary network device receives a first message sent by a primary network device; the secondary network device determines the bearer of the first QoS flow according to whether the first message includes auxiliary information Types of.
  • the SDAP entity corresponding to the first QoS flow is established on the secondary network device, or in other words, the packet data convergence protocol (PDCP) corresponding to the bearer corresponding to the first QoS flow is established on the secondary network device.
  • the bearer type includes MCG bearer, SCG bearer or split bearer.
  • the bearer type of the first QoS flow may be understood as the bearer type of the bearer corresponding to the first QoS flow.
  • the primary network device can assist the secondary network in determining the bearer type of the QoS flow by whether the secondary information is included in the first message. Accordingly, the secondary network device
  • the bearer type of the QoS flow can be reasonably determined according to whether the first message provided by the main network device includes auxiliary information, so that the QoS requirements of the QoS flow can be guaranteed as much as possible, and the data transmission efficiency can be improved. Further, by setting a reasonable bearer type for the QoS flow, the problem of a long negotiation process between the auxiliary network device and the main network device caused by the inappropriate decision of the auxiliary network device on the QoS flow bearer type can also be avoided.
  • the first QoS flow is a guaranteed bit rate (guaranteed bit rate, GBR) QoS flow
  • the auxiliary information is the first GBR QoS parameter.
  • the first GBR QoS parameter is the GBR QoS parameter that the main network device provides for the first QoS flow
  • the first GBR QoS parameter is the GBR QoS parameter that the main network device can provide for the first QoS flow
  • the auxiliary The network device determines the bearer type of the first quality of service QoS flow according to whether the first message includes auxiliary information, including: if the first message includes auxiliary information, the auxiliary network device determines that the bearer type of the first QoS flow is MCG bearer, SCG Bearer or separate bearer; and/or, if the first message does not include auxiliary information, the secondary network device determines that the bearer type of the first QoS flow is an SCG bearer.
  • the primary network device if the primary network device carries the first GBR QoS parameter in the first message, it means that the primary network device allows the secondary network device to determine (or configure) the bearer type of the first QoS flow as a bearer type involving MCG air interface resources , Namely MCG bearer or separate bearer. Therefore, when the first message carries the first GBR QoS parameter, the secondary network device may consider determining (or configuring) the bearer type of the first QoS flow as a bearer type involving MCG air interface resources, that is, MCG bearer or separate Bearer. However, the bearer type of the first QoS flow finally determined by the auxiliary network device can be determined autonomously.
  • the primary network device can assist the secondary network device in determining the bearer type of the GBR QoS flow by whether it carries the GBR QoS parameters provided for the GBR QoS flow in the first message. Accordingly, the secondary network device can determine the bearer type of the GBR QoS flow. Whether the first message provided by the network device includes the GBR QoS parameters provided by the main network device for the GBR QoS flow, and reasonably determine the bearer type of the GBR QoS flow.
  • the GBR QoS parameter may include one or more of an uplink maximum bit rate (MBR), a downlink maximum bit rate, an uplink GBR, and a downlink GBR.
  • MLR uplink maximum bit rate
  • the first GBR QoS parameter may be one or more of the uplink maximum bit rate, the downlink maximum bit rate, the uplink GBR, and the downlink GBR provided by the main network device for the first QoS flow.
  • the first message may also include the second GBR QoS parameter of the first QoS flow.
  • the second GBR QoS parameter is the GBR QoS parameter of the first QoS flow received by the main network device from the core network device.
  • the auxiliary network device can combine the second GBR QoS parameters to more reasonably determine the bearer type of the first QoS flow.
  • the first QoS flow is a non-guaranteed bit rate (non-GBR) QoS flow
  • the auxiliary information is the first user equipment (user equipment, UE) aggregates maximum bit rate (aggregated maximum bit rate, AMBR) and first protocol data unit (protocol data unit, PDU) session (session) AMBR.
  • the first UE AMBR is the AMBR provided by the primary network device for the target UE to establish a non-GBR QoS flow on the secondary network device
  • the target UE is the UE corresponding to the first QoS flow.
  • the first PDU session AMBR is the AMBR provided by the primary network device for the non-GBR QoS flow established in the secondary network device in the target PDU session, and the target PDU session is corresponding to the first QoS flow PDU session;
  • determining the bearer type of the first quality of service QoS flow by the auxiliary network device according to whether the first message includes auxiliary information includes:
  • the secondary network device determines that the bearer type of the first QoS flow is the MCG bearer, the SCG bearer, or the Separate bearer; and/or
  • the secondary network device determines that the bearer type of the first QoS flow is the SCG bearer; and/or
  • the secondary network device determines that the bearer type of the first QoS flow is the MCG bearer, the SCG bearer Or said separate bearer; and/or
  • the secondary network device determines that the bearer type of the first QoS flow is the MCG bearer, the SCG bearer Or the separate bearer.
  • the auxiliary network device may determine the bearer type of the first QoS flow according to whether the first message includes auxiliary information.
  • the basic idea of the above solution is that when designing the format of the first message, two cell positions can be reserved in the first message, that is, the cell corresponding to the AMBR of the first UE corresponds to the AMBR of the first PDU session. ⁇ .
  • the main network device may not fill any or both of these two cells, so as to achieve the above four situations.
  • whether the first QoS flow can be configured as a bearer type involving MCG air interface resources depends on whether the secondary network device receives the first network device provided by the primary network device for the PDU session corresponding to the first QoS flow. PDU session AMBR.
  • the secondary network device may consider determining the bearer type of the first QoS flow as (or configure ) Is the bearer type involving MCG air interface resources, that is, MCG bearer or separated bearer, which can be MCG bearer, SCG bearer, or separated bearer; if not received, the auxiliary network device determines that the bearer type of the first QoS flow is SCG bearer.
  • the non-GBR QoS flow established on the auxiliary network device refers to the non-GBR QoS flow established on the auxiliary network device by the corresponding SDAP entity.
  • the non-GBR QoS flow established on the main network device refers to the non-GBR QoS flow established on the main network device by the corresponding SDAP entity.
  • the non-GBR QoS flow in the PDU session indicates the non-GBR QoS flow corresponding to the PDU session.
  • the first QoS flow is a non-guaranteed bit rate non-GBR QoS flow
  • the auxiliary information is the first user equipment aggregated maximum bit rate UE AMBR
  • the first UE AMBR is the AMBR provided by the primary network device for the target UE to establish a non-GBR QoS flow on the secondary network device, and the target UE is the UE corresponding to the first QoS flow
  • the secondary network device determines the bearer type of the first quality of service QoS flow according to whether the first message includes auxiliary information, including: if the first message includes the auxiliary information, the auxiliary network device determines the second
  • the bearer type of a QoS flow is the MCG bearer, the SCG bearer, or the separated bearer; and/or, if the first message does not include the auxiliary information, the secondary network device determines the first QoS
  • the bearer type of the stream is the SCG bearer.
  • the primary network device if the primary network device carries the first UE AMBR in the first message, it means that the primary network device allows the secondary network device to determine (or configure) the bearer type of the first QoS flow as a bearer type involving MCG air interface resources. That is, MCG bearer or separate bearer. Therefore, in the case where the first UE AMBR parameters are carried in the first message, the secondary network device may consider determining (or configuring) the bearer type of the first QoS flow as the bearer type involving MCG air interface resources, that is, MCG bearer or separate Bearer. However, the bearer type of the first QoS flow finally determined by the auxiliary network device can be determined autonomously.
  • the secondary network device can reasonably determine the bearer type of the first QoS flow according to whether the first message includes the first UE AMBR.
  • the first QoS flow is a non-guaranteed bit rate non-GBR QoS flow
  • the auxiliary information is a first protocol data unit PDU session AMBR, where all The first PDU session AMBR is the AMBR provided by the primary network device for the non-GBR QoS flow established in the secondary network device in the target PDU session, and the target PDU session is corresponding to the first QoS flow PDU session; and, the secondary network device determines the bearer type of the first quality of service QoS flow according to whether the first message includes auxiliary information, including: if the first message includes the auxiliary information, the secondary network The device determines that the bearer type of the first QoS flow is the MCG bearer, the SCG bearer, or the separated bearer; and/or
  • the secondary network device determines that the bearer type of the first QoS flow is the SCG bearer.
  • the primary network device if the primary network device carries the first PDU session AMBR in the first message, it means that the primary network device allows the secondary network device to determine (or configure) the bearer type of the first QoS flow as a bearer type involving MCG air interface resources , Namely MCG bearer or separate bearer. Therefore, when the first message carries the AMBR of the first PDU session, the secondary network device may consider determining (or configuring) the bearer type of the first QoS flow as a bearer type involving MCG air interface resources, that is, MCG bearer or separate Bearer. However, the bearer type of the first QoS flow finally determined by the auxiliary network device can be determined autonomously.
  • the secondary network device can reasonably determine the bearer type of the first QoS flow according to whether the first message includes the first PDU session AMBR.
  • the method may further include: the secondary network device sends bearer type indication information to the primary network device, where the bearer type indication information is used to indicate the The bearer type of the first QoS flow determined by the secondary network device.
  • the bearer type indication information may be explicit information, that is, the bearer type indication information is the bearer type of the first QoS flow, or the bearer type indication information is whether the bearer type of the first QoS flow involves an MCG air interface Resource information. That is, the secondary network device explicitly tells the primary network device the bearer type of the first QoS flow, or informs the primary network device whether the bearer type of the first QoS flow involves MCG air interface resources.
  • the bearer type indication information can be implicit information.
  • the bearer type indication information may be uplink transmission network layer (UL TNL) information allocated by the auxiliary network device for the bearer corresponding to the first QoS flow to receive uplink data.
  • UL TNL uplink transmission network layer
  • the bearer type indication information is the uplink transmission network layer information, it indicates that the bearer type of the first QoS flow determined by the secondary network device is a bearer type involving MCG air interface resources.
  • the uplink transmission network layer information may include an internet protocol (IP) address and/or a tunnel endpoint identifier (TEID).
  • IP internet protocol
  • TEID tunnel endpoint identifier
  • the bearer type indication information may also indicate or include the identity of the first QoS flow or the identity of the bearer corresponding to the first QoS flow.
  • the method may further include: the secondary network device generates a modification request message, where the modification request message is used to apply for modification of the first QoS flow corresponding to the first QoS flow. 1.
  • the bearer type of the bearer the secondary network device sends the modification request message to the primary network device.
  • the auxiliary network device can trigger the modification of the bearer type. Therefore, when the state of the air interface on the side of the auxiliary network device changes, the auxiliary network device can modify the bearer type to a bearer type that is more suitable for the state of the air interface on the side of the auxiliary network device.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first bearer and an indication of the first bearer Information about the type of bearer that needs to be modified
  • the bearer deletion list includes the identifier of the first bearer
  • the secondary network device can implement the modification of the bearer type triggered by the secondary network device by carrying the same bearer identifier in the bearer establishment list and the bearer deletion list.
  • a method for determining a bearer type which is characterized in that it includes: a primary network device generates a first message according to whether auxiliary information is included in the first message; and the primary network device sends all the information to the secondary network device.
  • the first message is used by the secondary network device to determine the bearer type of the first quality of service QoS flow, wherein the service data adaptation protocol SDAP entity corresponding to the first QoS flow is established in the secondary network
  • the bearer type includes MCG bearer of the primary cell group, SCG bearer of the secondary cell group or separated bearer.
  • the primary network device can assist the secondary network in determining the bearer type of the QoS flow by whether the secondary information is included in the first message. Accordingly, the secondary network device
  • the bearer type of the QoS flow can be reasonably determined according to whether the first message provided by the main network device includes auxiliary information, so that the QoS requirements of the QoS flow can be guaranteed as much as possible, and the data transmission efficiency can be improved. Further, by setting a reasonable bearer type for the QoS flow, the problem of a long negotiation process between the auxiliary network device and the main network device caused by the inappropriate decision of the auxiliary network device on the QoS flow bearer type can also be avoided.
  • the first QoS flow is a guaranteed bit rate GBR QoS flow
  • the auxiliary information is a first GBR QoS parameter
  • the first GBR QoS parameter is a GBR QoS parameters provided by the main network device for the first QoS flow
  • the first message includes the auxiliary information
  • the first message is used to indicate that the secondary network device is allowed to configure the bearer type of the first QoS flow as a bearer type involving MCG air interface resources, so
  • the bearer types related to MCG air interface resources include the MCG bearer or the separated bearer;
  • the first message is used to instruct the secondary network device to configure the bearer type of the first QoS flow as the SCG bearer.
  • the first QoS flow is a non-guaranteed bit rate non-GBR QoS flow
  • the auxiliary information is the first user equipment aggregated maximum bit rate UE AMBR and the second A protocol data unit PDU session AMBR, where the first UE AMBR is the AMBR provided by the primary network device for the target UE to establish a non-GBR QoS flow on the secondary network device, and the target UE is the second network device.
  • the first PDU session AMBR is the AMBR provided by the primary network device for the non-GBR QoS flow established in the secondary network device in the target PDU session, and the target PDU session is The PDU session corresponding to the first QoS flow;
  • the first message includes the first UE AMBR and the first PDU session AMBR, the first message is used to indicate that the secondary network device is allowed to configure the bearer type of the first QoS flow Into the bearer type involving MCG air interface resources; and/or
  • the first message does not include the first UE AMBR and the first PDU session AMBR, the first message is used to instruct the secondary network device to configure the bearer type of the first QoS flow as the SCG bearer; and/or
  • the first message includes the first UE AMBR and does not include the first PDU session AMBR, the first message is used to indicate that the secondary network device is allowed to use the bearer type of the first QoS flow Configured as a bearer type involving MCG air interface resources; and/or
  • the first message includes the AMBR of the first PDU session and does not include the AMBR of the first UE, the first message is used to indicate that the secondary network device is allowed to use the bearer type of the first QoS flow Configured as a bearer type involving MCG air interface resources;
  • the bearer type related to the MCG air interface resource includes the MCG bearer or the separated bearer.
  • the first QoS flow is a non-guaranteed bit rate non-GBR QoS flow
  • the auxiliary information is the first user equipment aggregated maximum bit rate UE AMBR
  • the first UE AMBR is an AMBR provided by the primary network device for a target UE to establish a non-GBR QoS flow on the secondary network device, and the target UE is a UE corresponding to the first QoS flow;
  • the first message is used to indicate that the secondary network device is allowed to configure the bearer type of the first QoS flow as a bearer type involving MCG air interface resources, where ,
  • the bearer type related to the MCG air interface resource includes the MCG bearer or the separated bearer;
  • the first message is used to instruct the secondary network device to configure the bearer type of the first QoS flow as the SCG bearer.
  • the first QoS flow is a non-guaranteed bit rate non-GBR QoS flow
  • the auxiliary information is the first protocol data unit PDU session AMBR
  • the second A PDU session AMBR is the AMBR provided by the primary network device for the non-GBR QoS flow of the secondary network device in the target PDU session
  • the target PDU session is the PDU session corresponding to the first QoS flow
  • the first message is used to indicate that the secondary network device is allowed to configure the bearer type of the first QoS flow as a bearer type involving MCG air interface resources, where ,
  • the bearer type related to the MCG air interface resource includes the MCG bearer or the separated bearer;
  • the first message is used to instruct the secondary network device to configure the bearer type of the first QoS flow as the SCG bearer.
  • the method further includes: the primary network device receives bearer type indication information sent by the secondary network device, and the bearer type indication information is used to indicate all The bearer type of the first QoS flow determined by the secondary network device; the primary network device determines the bearer type of the first QoS flow according to the bearer type indication information.
  • the bearer type indication information is uplink transmission network layer information for receiving uplink data allocated by the auxiliary network device to the bearer corresponding to the first QoS flow.
  • the method further includes: the primary network device receiving a modification request message sent by the secondary network device, the modification request message being used to apply for modifying the The bearer type of the first bearer corresponding to the first QoS flow; the primary network device sends a modification request message to the secondary network device, and the modification request message is used to instruct the primary network device to agree to modify the first bearer Bearer type.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first bearer and an indication of the first bearer Information about the type of bearer that needs to be modified
  • the bearer deletion list includes the identifier of the first bearer
  • a method for determining a bearer type includes: a secondary network device receives recommended information sent by a primary network device; and the secondary network device determines the bearer type of the first QoS flow according to the recommended information.
  • the suggestion information is used to indicate the bearer type of the first QoS flow suggested by the primary network device, and the meaning of the first QoS flow is as described above.
  • the bearer type includes MCG bearer, SCG bearer or separate bearer.
  • the primary network device may suggest the bearer type of the first QoS flow to the secondary network device, and the secondary network device may determine the bearer type of the first QoS flow according to the recommendation of the primary network device.
  • the auxiliary network device can determine the bearer type of the QoS flow more reasonably according to the bearer type suggested by the main network device.
  • the secondary network device can independently determine the bearer type of the first QoS flow. That is, the bearer type finally determined by the secondary network device may be the bearer type suggested by the primary network device, or may not be the bearer type suggested by the primary network device. For example, if the bearer type recommended by the primary network device is a separate bearer, but the secondary network device can meet the QoS requirements of the first QoS flow, the secondary network device may determine the bearer type of the first QoS flow as an SCG bearer.
  • the method may further include: the secondary network device sends bearer type indication information to the primary network device, where the bearer type indication information is used to indicate all The bearer type of the first QoS flow determined by the auxiliary network device.
  • the meaning of the bearer type indication information is as described above.
  • the method may further include: the secondary network device generates a modification request message, where the modification request message is used to apply for modification of the first QoS flow corresponding to the first QoS flow. 1.
  • the bearer type of the bearer the secondary network device sends the modification request message to the primary network device.
  • the auxiliary network device can trigger the modification of the bearer type. Therefore, when the state of the air interface on the side of the auxiliary network device changes, the auxiliary network device can modify the bearer type to a bearer type that is more suitable for the state of the air interface on the side of the auxiliary network device.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first bearer and an indication of the first bearer Information about the type of bearer that needs to be modified
  • the bearer deletion list includes the identifier of the first bearer
  • the secondary network device can implement the modification of the bearer type triggered by the secondary network device by carrying the same bearer identifier in the bearer establishment list and the bearer deletion list.
  • a method for determining a bearer type includes: a primary network device generates suggestion information; the primary network device sends the suggestion information to a secondary network device.
  • the suggestion information is used to indicate the bearer type of the first QoS flow suggested by the primary network device, and the meaning of the first QoS flow is as described above.
  • the bearer type includes MCG bearer, SCG bearer or separate bearer.
  • the primary network device may suggest the bearer type of the first QoS flow to the secondary network device, and the secondary network device may determine the bearer type of the first QoS flow according to the recommendation of the primary network device.
  • the auxiliary network device can determine the bearer type of the QoS flow more reasonably according to the bearer type suggested by the main network device.
  • the method may further include: the primary network device receiving bearer type indication information sent by the secondary network device, where the bearer type indication information is used to indicate The bearer type of the first QoS flow determined by the secondary network device; the primary network device determines the bearer type of the first QoS flow according to the bearer type indication information.
  • the primary network device can learn the bearer type of the first QoS flow determined by the secondary network device.
  • the bearer type indication information is uplink transmission network layer information for receiving uplink data allocated by the auxiliary network device for the bearer corresponding to the first QoS flow.
  • the method further includes: the primary network device receiving a modification request message sent by the secondary network device, the modification request message being used to apply to modify the The bearer type of the first bearer corresponding to the first QoS flow; the primary network device sends a modification request message to the secondary network device, and the modification request message is used to instruct the primary network device to agree to modify the first bearer Bearer type.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first bearer and an indication of the first bearer Information about the type of bearer that needs to be modified
  • the bearer deletion list includes the identifier of the first bearer
  • a method for determining a bearer type includes: a secondary network device receives a first message sent by a primary network device; and the secondary network device determines a first data radio bearer according to whether the first message includes auxiliary information ( data radio bearer (DRB) bearer type.
  • DRB data radio bearer
  • the PDCP entity corresponding to the first DRB is established on the secondary network device. It should be understood that the SDAP entity corresponding to the QoS corresponding to the first DRB is established on the secondary network device.
  • the bearer type includes MCG bearer, SCG bearer or split bearer.
  • the primary network device can assist the secondary network device in determining the bearer type of the DRB by whether the first message includes auxiliary information
  • the auxiliary network device can reasonably determine the bearer type of the DRB according to whether the first message provided by the main network device includes auxiliary information, so as to ensure the QoS requirements of the DRB as much as possible and improve the data transmission efficiency. Further, by setting a reasonable bearer type for the DRB, it is also possible to avoid the problem of a long negotiation process between the secondary network device and the primary network device caused by the inappropriate decision of the secondary network device on the DRB's bearer type.
  • the auxiliary information is a first parameter
  • the first parameter is a QoS parameter provided by the main network device for the first DRB.
  • the secondary network device determines the bearer type of the first DRB according to whether the first message includes auxiliary information, including: if the first message includes the auxiliary information, the auxiliary network device determines that the bearer type of the first DRB is MCG bearer, SCG bearer or separate bearer; and/or, if the first message does not include auxiliary information, the secondary network device determines that the bearer type of the first DRB is an SCG bearer.
  • the primary network device carries the first parameter in the first message, it means that the primary network device allows the secondary network device to determine (or configure) the bearer type of the first DRB as a bearer type involving MCG air interface resources, that is, MCG Bearer or separate bearer. Therefore, when the first parameter is carried in the first message, the secondary network device may consider determining (or configuring) the bearer type of the first DRB as a bearer type involving MCG air interface resources, that is, MCG bearer or separate bearer. However, the bearer type of the first DRB finally determined by the auxiliary network device can be determined autonomously.
  • the primary network device can assist the secondary network device to determine the bearer type of the first DRB by whether it carries the QoS parameters provided for the first DRB in the first message. Accordingly, the secondary network device can determine the bearer type of the first DRB. Whether the provided first message includes the QoS parameters provided by the primary network device for the first DRB, and reasonably determine the bearer type of the first DRB.
  • the first parameter may include one or more of uplink MBR, downlink MBR, uplink GBR, and downlink GBR.
  • the method may further include: the secondary network device sending bearer type indication information to the primary network device, where the bearer type indication information is used to indicate the The bearer type of the first DRB determined by the secondary network device.
  • the bearer type indication information may be explicit information, that is, the bearer type indication information is the bearer type of the first DRB, or the bearer type indication information is whether the bearer type of the first DRB involves MCG air interface resources information. That is, the secondary network device explicitly tells the primary network device the bearer type of the first DRB, or informs the primary network device whether the bearer type of the first DRB involves MCG air interface resources.
  • the bearer type indication information can be implicit information.
  • the bearer type indication information may be uplink transmission network layer information allocated by the secondary network device for the first DRB to receive uplink data. It should be understood that if the bearer type indication information is the uplink transmission network layer information, it means that the bearer type of the first DRB determined by the secondary network device is a bearer type involving MCG air interface resources.
  • the uplink transmission network layer information may include an IP address and/or a tunnel endpoint identifier.
  • the bearer type indication information may also indicate or include the identity of the first DRB.
  • the method may further include: the secondary network device generates a modification request message, where the modification request message is used to apply for modification of the bearer type of the first DRB; The secondary network device sends the modification request message to the primary network device.
  • the auxiliary network device can trigger the modification of the bearer type. Therefore, when the state of the air interface on the side of the auxiliary network device changes, the auxiliary network device can modify the bearer type to a bearer type that is more suitable for the state of the air interface on the side of the auxiliary network device.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first DRB and an indication of the first DRB Information about the type of bearer that needs to be modified
  • the bearer deletion list includes the identifier of the first bearer
  • the secondary network device can implement the modification of the bearer type triggered by the secondary network device by carrying the same bearer identifier in the bearer establishment list and the bearer deletion list.
  • a method for determining a bearer type which is characterized in that it includes: a primary network device generates a first message according to whether auxiliary information is included in the first message; and the primary network device sends all the information to the secondary network device.
  • the first message is used by the secondary network device to determine the bearer type of the first DRB, wherein the PDCP entity corresponding to the first DRB is established on the secondary network device, and the bearer type includes Primary cell group MCG bearer, secondary cell group SCG bearer or separate bearer.
  • the primary network device can assist the secondary network device in determining the bearer type of the DRB by whether the first message includes auxiliary information
  • the auxiliary network device can reasonably determine the bearer type of the DRB according to whether the first message provided by the main network device includes auxiliary information, so as to ensure the QoS requirements of the DRB as much as possible and improve the data transmission efficiency. Further, by setting a reasonable bearer type for the DRB, it is also possible to avoid the problem of a long negotiation process between the secondary network device and the primary network device caused by the inappropriate decision of the secondary network device on the DRB's bearer type.
  • the auxiliary information is a first parameter
  • the first parameter is a QoS parameter provided by the main network device for the first DRB.
  • the first message includes auxiliary information
  • the first message is used to indicate that the secondary network device is allowed to configure the bearer type of the first DRB as a bearer type involving MCG air interface resources, and the MCG air interface resources are involved
  • the bearer type includes the MCG bearer or the separated bearer; and/or, if the first message does not include the auxiliary information, the first message is used to instruct the secondary network device to use the first DRB
  • the bearer type is configured as the SCG bearer.
  • the method further includes: the primary network device receives bearer type indication information sent by the secondary network device, and the bearer type indication information is used to indicate all The bearer type of the first DRB determined by the secondary network device; the primary network device determines the bearer type of the first DRB according to the bearer type indication information.
  • the bearer type indication information is uplink transmission network layer information allocated by the secondary network device for the first DRB to receive uplink data.
  • the method further includes: the primary network device receiving a modification request message sent by the secondary network device, the modification request message being used to apply to modify the The bearer type of the first DRB; the primary network device sends a modification request message to the secondary network device, where the modification request message is used to indicate that the primary network device agrees to modify the bearer type of the first DRB.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first DRB and an indication of the first DRB Information about the type of bearer that needs to be modified
  • the bearer deletion list includes the identifier of the first DRB
  • a method for determining a bearer type includes: a secondary network device receives recommended information sent by a primary network device; and the secondary network device determines the bearer type of the first DRB according to the recommended information.
  • the suggestion information is used to indicate the bearer type of the first DRB suggested by the primary network device, and the meaning of the first DRB is as described in the fifth aspect.
  • the bearer type includes MCG bearer, SCG bearer or separate bearer.
  • the primary network device may suggest the bearer type of the first DRB to the secondary network device, and the secondary network device may determine the bearer type of the first DRB according to the recommendation of the primary network device.
  • the secondary network device can determine the bearer type of the DRB more reasonably according to the bearer type suggested by the primary network device.
  • the secondary network device can autonomously determine the bearer type of the first DRB. That is, the bearer type finally determined by the secondary network device may be the bearer type suggested by the primary network device, or may not be the bearer type suggested by the primary network device. For example, if the bearer type recommended by the primary network device is a separate bearer, but the secondary network device can meet the QoS requirements of the first DRB, the bearer type of the first DRB may be determined as an SCG bearer.
  • the method may further include: the secondary network device sends bearer type indication information to the primary network device, where the bearer type indication information is used to indicate all The bearer type of the first DRB determined by the secondary network device.
  • the meaning of the bearer type indication information is as described in the fifth aspect.
  • the method may further include: the secondary network device generating a modification request message, the modification request message being used to apply for modification of the bearer type of the first DRB; The secondary network device sends the modification request message to the primary network device.
  • the auxiliary network device can trigger the modification of the bearer type. Therefore, when the state of the air interface on the side of the auxiliary network device changes, the auxiliary network device can modify the bearer type to a bearer type that is more suitable for the state of the air interface on the side of the auxiliary network device.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first DRB and an indication of the first DRB Information about the type of bearer that needs to be modified
  • the bearer deletion list includes the identifier of the first DRB
  • the secondary network device can implement the modification of the bearer type triggered by the secondary network device by carrying the same bearer identifier in the bearer establishment list and the bearer deletion list.
  • a method for determining a bearer type includes: a primary network device generates suggestion information; and the primary network device sends the suggestion information to a secondary network device.
  • the suggestion information is used to indicate the bearer type of the first DRB suggested by the primary network device, and the meaning of the first DRB is as described in the fifth aspect.
  • the bearer type includes MCG bearer, SCG bearer or separate bearer.
  • the primary network device may suggest the bearer type of the first DRB to the secondary network device, and the secondary network device may determine the bearer type of the first DRB according to the recommendation of the primary network device.
  • the auxiliary network device can determine the bearer type of the DRB more reasonably according to the bearer type suggested by the main network device.
  • the method may further include: the primary network device receiving bearer type indication information sent by the secondary network device, where the bearer type indication information is used to indicate The bearer type of the first DRB determined by the secondary network device; the primary network device determines the bearer type of the first DRB according to the bearer type indication information.
  • the bearer type indication information is uplink transmission network layer information allocated by the secondary network device for the first DRB to receive uplink data.
  • the method further includes: the primary network device receiving a modification request message sent by the secondary network device, the modification request message being used to apply to modify the The bearer type of the first DRB; the primary network device sends a modification request message to the secondary network device, where the modification request message is used to indicate that the primary network device agrees to modify the bearer type of the first DRB.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first DRB and an indication of the first bearer Information about the type of bearer that needs to be modified
  • the bearer deletion list includes the identifier of the first DRB
  • a method for modifying a bearer type which includes: a secondary network device generates a modification request (required) message, where the modification request message is used to apply to modify the bearer type of the first bearer; The network device sends the modification request message.
  • the secondary network device may request to modify the bearer type of the first bearer by sending a modification request message to the primary network device.
  • the secondary network device can trigger the modification (or change) of the bearer type by sending a modification request message to the main network device, and further realize the modification of the bearer type.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first bearer and an indication of the first bearer
  • the indication information of the bearer type that needs to be modified (referred to as indication information for short), and the bearer deletion list includes the identifier of the first bearer.
  • the secondary network device can implement the modification of the bearer type triggered by the secondary network device by carrying the same bearer identifier in the bearer establishment list and the bearer deletion list.
  • the bearer deletion list may also include the current bearer type of the first bearer.
  • the bearer type that needs to be modified indicated by the indication information is the new bearer type of the first bearer determined by the secondary network device.
  • the current bearer type of the first bearer is the original bearer type of the first bearer. That is, the secondary network device expects to modify the first bearer from the original bearer type to the new bearer type.
  • the indication information may be an explicit bearer type, such as MCG bearer, SCG bearer or separate bearer.
  • the indication information may also be implicit information, and the implicit information may indicate the new bearer type of the first bearer.
  • the implicit information may be uplink transmission network layer (UL TNL) information, and the uplink transmission network layer information is allocated by the secondary network device for the first bearer to receive the uplink transmitted by the primary network device. Transmission layer information of the data, wherein the uplink data is the uplink data of the first bearer received by the main network device from the terminal device. It should be understood that if the indication information is the uplink transmission network layer information, it indicates that the new bearer type is a bearer type involving MCG air interface resources, that is, MCG bearer or separated bearer.
  • the uplink transmission network layer information may include an Internet Protocol (IP) address and a tunnel endpoint identifier (TEID). It should be understood that, according to the uplink transmission network layer information, the auxiliary network device may receive the uplink data of the first bearer sent by the main network device.
  • IP Internet Protocol
  • TEID tunnel endpoint identifier
  • the method further includes: the secondary network device receiving a modification request (request) message sent by the primary network device, the modification request message being used to indicate The primary network device agrees to modify the bearer type of the first bearer; the secondary network device sends a modification request acknowledgement (acknowledge) message to the primary network device, and the modification request acknowledgement message includes air interface radio resource control (radio resource control).
  • request a modification request
  • acknowledgement acknowledgement
  • the air interface RRC configuration (denoted as: air interface RRC configuration #1) is the air interface RRC configuration generated by the secondary network device for the terminal device, and the air interface RRC configuration is used for the terminal device to configure the The first bearer; the secondary network device receives a modification confirmation message (confirm) sent by the primary network device, and the modification confirmation message is used to indicate that the modification of the bearer type of the first bearer is completed.
  • the main network device after the main network device accepts the modification request of the auxiliary network device, it can send a modification request message to the auxiliary network device, notifying the auxiliary network device that the main network device has accepted the modification request of the auxiliary network device on the one hand, and requesting on the other hand
  • the secondary network device generates a corresponding air interface RRC configuration for the first bearer.
  • the secondary network device After the secondary network device generates the corresponding air interface RRC configuration #1 for the first bearer, it sends the configuration to the primary network device through a modification request confirmation message.
  • the main network device After receiving the modification request confirmation message, the main network device generates air interface RRC configuration #2, and sends air interface RRC configuration #1 and air interface RRC configuration #2 to the terminal device together to complete the configuration of the first bearer.
  • the primary network device informs the secondary network device that the primary network device has completed the configuration of the first bearer by sending a modification confirmation message to the secondary network device.
  • the secondary network device needs to generate a PDCP recovery configuration for the terminal device (ie, an example of air interface RRC configuration #1). Instruct the PDCP entity of the first bearer to perform data recovery; the main network device needs to generate an MCG radio link control (radio link control, RLC) bearer deletion configuration for the terminal device (ie, an example of air interface RRC configuration #2).
  • a PDCP recovery configuration for the terminal device
  • RLC radio link control
  • the secondary network device needs to generate an SCG RLC bearer release configuration for the terminal device (ie, an example of air interface RRC configuration #1), and the primary network device needs Generate MCG RLC bearer addition configuration for the terminal device (ie, an example of air interface RRC configuration #2).
  • the modification request message includes the uplink transmission network layer information.
  • the main network device may also carry the above-mentioned uplink transmission network layer information in the modification request message. Or, if the above indication information is uplink transmission network layer information, the main network device may not carry the uplink transmission network layer information in the modification request message.
  • the modification request message further includes an air interface RRC configuration (denoted as: air interface RRC configuration #1), and the air interface RRC configuration is that the secondary network device is a terminal
  • the RRC configuration generated by the device, the air interface RRC configuration is used for the terminal device to configure the first bearer; and, the method further includes: the secondary network device receives the modification confirmation message sent by the primary network device, and The modification confirmation message is used to indicate that the modification of the bearer type of the first bearer is completed.
  • the primary network device cannot reject the bearer modification request initiated by the secondary network device for the first bearer.
  • the secondary network device may carry the air interface RRC configuration #1 in the modification request message.
  • the primary network device receives the air interface RRC configuration #1 sent by the secondary network device, it generates the air interface RRC configuration #2, and sends the air interface RRC configuration #1 and the air interface RRC configuration #2 to the terminal device to complete the configuration of the first bearer .
  • the primary network device informs the secondary network device that the primary network device has completed the configuration of the first bearer by sending a modification confirmation message to the secondary network device.
  • the main network device may also carry the above-mentioned uplink transmission network layer information in the modification confirmation message. Or, if the above indication information is uplink transmission network layer information, the main network device may not carry the uplink transmission network layer information in the modification confirmation message.
  • a method for modifying a bearer type including: a primary network device receives a modification request message sent by a secondary network device, where the modification request message is used to apply to modify the bearer type of a first bearer; the primary network device Send a modification request message to the secondary network device.
  • the modification request message is used to instruct the primary network device to agree to the modification request of the secondary network device.
  • the secondary network device when the secondary network device desires to modify the bearer type of the first bearer, it can send a modification request message to the primary network device. If the primary network device accepts the request of the secondary network device to modify the bearer type of the first bearer, it sends the request to the secondary network The device sends a modification request message. Furthermore, the secondary network device can implement modification of the bearer type of the first bearer.
  • the secondary network device can trigger the modification (or change) of the bearer type by sending a modification request message to the primary network device, and further realize the modification of the bearer type.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first bearer and an indication of the first bearer
  • the indication information of the bearer type that needs to be modified (referred to as indication information for short), and the bearer deletion list includes the identifier of the first bearer.
  • the secondary network device can implement the modification of the bearer type triggered by the secondary network device by carrying the same bearer identifier in the bearer establishment list and the bearer deletion list.
  • the bearer deletion list may also include the current bearer type of the first bearer.
  • the bearer type that needs to be modified indicated by the indication information is the new bearer type of the first bearer determined by the secondary network device.
  • the current bearer type of the first bearer is the original bearer type of the first bearer. That is, the secondary network device expects to modify the first bearer from the original bearer type to the new bearer type.
  • the indication information may be an explicit bearer type, such as MCG bearer, SCG bearer or separate bearer.
  • the indication information may also be implicit information, and the implicit information may indicate the new bearer type of the first bearer.
  • the implicit information may be uplink transmission network layer (UL TNL) information, and the uplink transmission network layer information is allocated by the secondary network device for the first bearer to receive the uplink transmitted by the primary network device. Transmission layer information of the data, wherein the uplink data is the uplink data of the first bearer received by the main network device from the terminal device. It should be understood that if the indication information is the uplink transmission network layer information, it indicates that the new bearer type is a bearer type involving MCG air interface resources, that is, MCG bearer or separated bearer.
  • the uplink transmission network layer information may include an Internet Protocol (IP) address and a tunnel endpoint identifier (TEID), and the secondary network device can receive the first bearer sent by the primary network device according to the uplink transmission network layer information Upstream data.
  • IP Internet Protocol
  • TEID tunnel endpoint identifier
  • the modification request message includes the uplink transmission network layer information.
  • the main network device may also carry the above-mentioned uplink transmission network layer information in the modification request message. Or, if the above indication information is uplink transmission network layer information, the main network device may not carry the uplink transmission network layer information in the modification request message.
  • the method may further include: the primary network device receiving a modification request confirmation message sent by the secondary network device, where the modification request confirmation message includes air interface RRC Configuration, the air interface RRC configuration is the RRC configuration generated by the secondary network device for the terminal device, and the air interface RRC configuration is used by the terminal device to configure the first bearer; the primary network device sends the primary network device to the secondary network device Sending a modification confirmation message, where the modification confirmation message is used to indicate that the modification of the bearer type of the first bearer is completed.
  • the bearer type of the first bearer can be modified.
  • a method for modifying a bearer type including: a primary network device receives a modification request message sent by a secondary network device, the modification request message is used to apply to modify the bearer type of the first bearer, and the modification request
  • the message includes the air interface RRC configuration (denoted as: air interface RRC configuration #1), the air interface RRC configuration is the RRC configuration generated by the secondary network device for the terminal device, and the air interface RRC configuration is used for the terminal device to configure the first A bearer; the primary network device sends a modification confirmation message to the secondary network device.
  • the modification confirmation message is used to indicate that the modification of the bearer type of the first bearer is completed.
  • the primary network device cannot reject the bearer modification request initiated by the secondary network device for the first bearer.
  • the secondary network device may carry the air interface RRC configuration #1 in the modification request message.
  • the primary network device receives the air interface RRC configuration #1 sent by the secondary network device, it generates the air interface RRC configuration #2, and sends the air interface RRC configuration #1 and the air interface RRC configuration #2 to the terminal device to complete the configuration of the first bearer .
  • the primary network device informs the secondary network device that the primary network device has completed the configuration of the first bearer by sending a modification confirmation message to the secondary network device.
  • the secondary network device can trigger the modification (or change) of the bearer type by sending a modification request message to the main network device, and further realize the modification of the bearer type.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first bearer and an indication of the first bearer.
  • Indication information (referred to as indication information for short) of the bearer type to be modified by the bearer
  • the bearer deletion list includes the identifier of the first bearer.
  • the secondary network device can implement the modification of the bearer type triggered by the secondary network device by carrying the same bearer identifier in the bearer establishment list and the bearer deletion list.
  • the bearer deletion list may also include the current bearer type of the first bearer.
  • the bearer type that needs to be modified indicated by the indication information is the new bearer type of the first bearer determined by the secondary network device.
  • the current bearer type of the first bearer is the original bearer type of the first bearer. That is, the secondary network device expects to modify the first bearer from the original bearer type to the new bearer type.
  • the indication information may be an explicit bearer type, such as MCG bearer, SCG bearer or separate bearer.
  • the indication information may also be implicit information, and the implicit information may indicate the new bearer type of the first bearer.
  • the implicit information may be uplink transmission network layer (UL TNL) information, and the uplink transmission network layer information is allocated by the secondary network device for the first bearer to receive the uplink transmitted by the primary network device. Transmission layer information of the data, wherein the uplink data is the uplink data of the first bearer received by the main network device from the terminal device. It should be understood that if the indication information is the uplink transmission network layer information, it indicates that the new bearer type is a bearer type involving MCG air interface resources, that is, MCG bearer or separated bearer.
  • the uplink transmission network layer information may include an Internet Protocol (IP) address and a tunnel endpoint identifier (TEID), and the secondary network device can receive the first bearer sent by the primary network device according to the uplink transmission network layer information Upstream data.
  • IP Internet Protocol
  • TEID tunnel endpoint identifier
  • the main network device may also carry the above-mentioned uplink transmission network layer information in the modification confirmation message. Or, if the above indication information is uplink transmission network layer information, the main network device may not carry the uplink transmission network layer information in the modification confirmation message.
  • a communication method includes: a secondary network device receives time domain configuration information from a primary network device; and the secondary network device determines a hybrid automatic repeat request according to the time domain configuration information. , HARQ offset (offset); the secondary network device sends the first HARQ offset to the primary network device.
  • the SN can determine the first HARQ offset for the MN or the terminal in combination with its own operating conditions, thereby improving the accuracy of the MN or the terminal equipment in the uplink and downlink time domain allocation, thereby improving the communication quality.
  • the method further includes: the auxiliary network device determines a time division multiplexing mode configuration according to the time domain configuration information; The time division multiplexing mode configuration is notified to the terminal device, and the time division multiplexing mode configuration includes the first HARQ offset.
  • the auxiliary network device may directly send the time division multiplexing mode configuration to the terminal device.
  • the auxiliary network device may forward the time division multiplexing mode configuration to the terminal device through the main network device.
  • the first HARQ offset is 0.
  • the secondary network device determines the first HARQ offset according to the time domain configuration information includes: the secondary network device adjusts the first HARQ offset to 0 according to the time domain configuration information.
  • the time domain configuration information includes a second HARQ offset
  • the secondary network device determines the first HARQ offset according to the time domain configuration information, including: the secondary network device determines the first HARQ offset It is different from the second HARQ offset.
  • a communication method includes: a primary network device sends time domain configuration information to a secondary network device, where the time domain configuration information is used by the secondary network device to determine a first HARQ offset; the primary network The device receives the first HARQ offset from the secondary network device.
  • the method further includes: the main network device adjusts the uplink and downlink subframe ratio according to the first HARQ offset.
  • the method further includes: the primary network device receives from the secondary network device a time division multiplexing mode configuration determined by the secondary network device, and the time division multiplexing mode configuration Includes the first HARQ offset; the main network device sends the time division multiplexing mode configuration to the terminal device.
  • the secondary network device may send the time division multiplexing mode configuration to the main network device in an RRC container, and the main network device sends the RRC container including the time division multiplexing mode configuration to the terminal device.
  • a communication device including a transceiving unit, configured to receive a first message sent by a main network device; a processing unit, configured to determine a first quality of service QoS according to whether the first message includes auxiliary information
  • the bearer type of the flow wherein the service data adaptation protocol SDAP entity corresponding to the first QoS flow is established on the communication device, and the bearer type includes a primary cell group MCG bearer, a secondary cell group SCG bearer, or a separate bearer.
  • the first QoS flow is a guaranteed bit rate GBR QoS flow
  • the auxiliary information is a first GBR QoS parameter
  • the first GBR QoS parameter GBR QoS parameters provided by the primary network device for the first QoS flow
  • the processing unit is specifically configured to: if the first message includes the auxiliary information, determine that the bearer type of the first QoS flow is the MCG bearer, the SCG bearer, or the separated bearer; and/ or
  • the bearer type of the first QoS flow is the SCG bearer.
  • the first QoS flow is a non-guaranteed bit rate non-GBR QoS flow
  • the auxiliary information is the first user equipment aggregated maximum bit rate UE AMBR Conversing AMBR with the first protocol data unit PDU
  • the first UE AMBR is the AMBR provided by the primary network equipment for the target UE to establish a non-GBR QoS flow on the communication device
  • the target UE is the For the UE corresponding to the first QoS flow
  • the first PDU session AMBR is the AMBR provided by the primary network device for the non-GBR QoS flow established in the communication device in the target PDU session
  • the target PDU session is The PDU session corresponding to the first QoS flow
  • processing unit is specifically configured to:
  • the bearer type of the first QoS flow is the MCG bearer, the SCG bearer, or the separated bearer; and/ or
  • the bearer type of the first QoS flow is the SCG bearer
  • the bearer type of the first QoS flow is the MCG bearer, the SCG bearer, or the separated bearer ;and / or
  • the bearer type of the first QoS flow is the MCG bearer, the SCG bearer, or the separated bearer .
  • the first QoS flow is a non-guaranteed bit rate non-GBR QoS flow
  • the auxiliary information is the first user equipment aggregated maximum bit rate UE AMBR
  • the first UE AMBR is an AMBR provided by the primary network device for a target UE to establish a non-GBR QoS flow in the communication device, and the target UE is a UE corresponding to the first QoS flow;
  • processing unit is specifically configured to:
  • the bearer type of the first QoS flow is the MCG bearer, the SCG bearer, or the separated bearer
  • the bearer type of the first QoS flow is the SCG bearer.
  • the first QoS flow is a non-guaranteed bit rate non-GBR QoS flow
  • the auxiliary information is the first protocol data unit PDU session AMBR
  • the first PDU session AMBR is the AMBR provided by the primary network device for the non-GBR QoS flow established in the communication device in the target PDU session, and the target PDU session corresponds to the first QoS flow PDU session;
  • processing unit is specifically configured to:
  • the bearer type of the first QoS flow is the MCG bearer, the SCG bearer, or the separated bearer
  • the bearer type of the first QoS flow is the SCG bearer.
  • the transceiver unit is further configured to: send bearer type indication information to the primary network device, where the bearer type indication information is used to indicate the communication The bearer type of the first QoS flow determined by the apparatus.
  • the bearer type indication information is the uplink transmission network layer information allocated by the communication device for the bearer corresponding to the first QoS flow to receive uplink data .
  • the processing unit is further configured to generate a modification request message, where the modification request message is used to apply for modification of the first corresponding to the first QoS flow.
  • the bearer type of the bearer; the transceiver unit is further configured to send the modification request message to the main network device.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first bearer and an indication of the first bearer.
  • a bearer needs to modify bearer type information
  • the bearer deletion list includes the identity of the first bearer.
  • a communication device including a processing unit, configured to generate a first message according to whether auxiliary information is included in the first message; a transceiver unit, configured to send the first message to an auxiliary network device, The first message is used by the auxiliary network device to determine the bearer type of the first quality of service QoS flow, wherein the service data adaptation protocol SDAP entity corresponding to the first QoS flow is established on the auxiliary network device, and the The bearer type includes MCG bearer of primary cell group, SCG bearer of secondary cell group or separated bearer.
  • the first QoS flow is a guaranteed bit rate GBR QoS flow
  • the auxiliary information is a first GBR QoS parameter
  • the first GBR QoS parameter GBR QoS parameters provided by the communication device for the first QoS flow
  • the first message includes the auxiliary information
  • the first message is used to indicate that the secondary network device is allowed to configure the bearer type of the first QoS flow as a bearer type involving MCG air interface resources, so
  • the bearer types related to MCG air interface resources include the MCG bearer or the separated bearer;
  • the first message is used to instruct the secondary network device to configure the bearer type of the first QoS flow as the SCG bearer.
  • the first QoS flow is a non-guaranteed bit rate non-GBR QoS flow
  • the auxiliary information is the first user equipment aggregated maximum bit rate UE AMBR Conversing AMBR with the first protocol data unit PDU
  • the first UE AMBR is the AMBR provided by the communication device for the target UE to establish a non-GBR QoS flow on the secondary network device
  • the target UE is the For the UE corresponding to the first QoS flow
  • the first PDU session AMBR is the AMBR provided by the communication device for the non-GBR QoS flow QoS flow established in the secondary network device in the target PDU session
  • the target PDU session is The PDU session corresponding to the first QoS flow
  • the first message includes the first UE AMBR and the first PDU session AMBR, the first message is used to indicate that the secondary network device is allowed to configure the bearer type of the first QoS flow Into the bearer type involving MCG air interface resources; and/or
  • the first message does not include the first UE AMBR and the first PDU session AMBR, the first message is used to instruct the secondary network device to configure the bearer type of the first QoS flow as the SCG bearer; and/or
  • the first message includes the first UE AMBR and does not include the first PDU session AMBR, the first message is used to indicate that the secondary network device is allowed to use the bearer type of the first QoS flow Configured as a bearer type involving MCG air interface resources; and/or
  • the first message includes the AMBR of the first PDU session and does not include the AMBR of the first UE, the first message is used to indicate that the secondary network device is allowed to use the bearer type of the first QoS flow Configured as a bearer type involving MCG air interface resources;
  • the bearer type related to the MCG air interface resource includes the MCG bearer or the separated bearer.
  • the first QoS flow is a non-guaranteed bit rate non-GBR QoS flow
  • the auxiliary information is the first user equipment aggregated maximum bit rate UE AMBR
  • the first UE AMBR is the AMBR provided by the communication apparatus for the non-GBR QoS flow established on the secondary network device for the target UE, and the target UE is the UE corresponding to the first QoS flow;
  • the first message is used to indicate that the secondary network device is allowed to configure the bearer type of the first QoS flow as a bearer type involving MCG air interface resources, where ,
  • the bearer type related to the MCG air interface resource includes the MCG bearer or the separated bearer;
  • the first message is used to instruct the secondary network device to configure the bearer type of the first QoS flow as the SCG bearer.
  • the first QoS flow is a non-guaranteed bit rate non-GBR QoS flow
  • the auxiliary information is the first protocol data unit PDU session AMBR
  • the first PDU session AMBR is the AMBR provided by the communication device for the non-GBR QoS flow established in the secondary network device in the target PDU session
  • the target PDU session is the PDU corresponding to the first QoS flow Conversation
  • the first message is used to indicate that the secondary network device is allowed to configure the bearer type of the first QoS flow as a bearer type involving MCG air interface resources, where ,
  • the bearer type related to the MCG air interface resource includes the MCG bearer or the separated bearer;
  • the first message is used to instruct the secondary network device to configure the bearer type of the first QoS flow as the SCG bearer.
  • the transceiver unit is further configured to: receive bearer type indication information sent by the secondary network device, where the bearer type indication information is used to indicate the The bearer type of the first QoS flow determined by the secondary network device; the processing unit is further configured to determine the bearer type of the first QoS flow.
  • the bearer type indication information is the uplink transmission network layer that is allocated by the secondary network device to the bearer corresponding to the first QoS flow to receive uplink data information.
  • the transceiver unit is further configured to: receive a modification request message sent by the auxiliary network device, where the modification request message is used to apply for modification of the first aspect A bearer type of the first bearer corresponding to a QoS flow; sending a modification request message to the secondary network device, where the modification request message is used to indicate that the communication device agrees to modify the bearer type of the first bearer.
  • the modification request message includes a bearer establishment list and a bearer deletion list
  • the bearer establishment list includes an identifier of the first bearer and an indication of the first bearer A bearer needs to modify bearer type information
  • the bearer deletion list includes the identity of the first bearer
  • a communication device which includes units or units for executing the method in the third aspect to the thirteenth aspect and any one of the third aspect to the thirteenth aspect.
  • a communication device including a processor.
  • the processor is coupled to the memory and can be used to execute instructions in the memory to implement the method in any one of the first aspect to the thirteenth aspect and any one of the first aspect to the thirteenth aspect.
  • the communication device further includes a memory.
  • the communication device further includes an interface circuit, and the processor is coupled with the interface circuit.
  • the interface circuit may be a transceiver, or an input/output interface.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • a processor including: an input circuit, an output circuit, and a processing circuit.
  • the processing circuit is used to receive a signal through the input circuit, and transmit a signal through the output circuit, so that the processor executes any one of the possible implementation manners of the first aspect to the thirteenth aspect and the first aspect to the thirteenth aspect method.
  • the foregoing processor may be a chip
  • the input circuit may be an input pin
  • the output circuit may be an output pin
  • the processing circuit may be a transistor, a gate circuit, a flip-flop, and various logic circuits.
  • the input signal received by the input circuit may be received and input by, for example, but not limited to, a receiver
  • the signal output by the output circuit may be, for example, but not limited to, output to and transmitted by the transmitter
  • the circuit can be the same circuit, which is used as an input circuit and an output circuit at different times.
  • the embodiments of the present application do not limit the specific implementation manners of the processor and various circuits.
  • a processing device including a processor and a memory.
  • the processor is used to read instructions stored in the memory, and can receive signals through a receiver, and transmit signals through a transmitter to execute the first aspect to the thirteenth aspect. Any one of the first to the thirteenth aspects can be implemented The method in the way.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory and the processor may be provided separately.
  • the memory can be a non-transitory (non-transitory) memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be set in different On the chip, the embodiment of the present application does not limit the type of memory and the setting mode of the memory and the processor.
  • ROM read only memory
  • sending the first message may be a process of outputting the first message from the processor
  • receiving information may be a process of the processor receiving information.
  • the processed output data may be output to the transmitter, and the input data received by the processor may come from the receiver.
  • the transmitter and receiver can be collectively referred to as a transceiver.
  • the processing device in the aforementioned nineteenth aspect may be a chip, and the processor may be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software
  • the processor may be a general-purpose processor, which is implemented by reading software codes stored in the memory.
  • the memory may be integrated in the processor, may be located outside the processor, and exist independently.
  • a computer program product includes: a computer program (also called code, or instruction), when the computer program is executed, the computer executes the first to tenth aspects.
  • a computer program also called code, or instruction
  • the method in any one of the possible implementation manners of the first aspect to the thirteenth aspect.
  • a computer-readable medium stores a computer program (also called code, or instruction) when it runs on a computer, so that the computer executes the first aspect to
  • the thirteenth aspect adopts the method in any one of the possible implementation modes of the first aspect to the thirteenth aspect.
  • a communication system including the aforementioned primary network equipment and auxiliary network equipment,
  • the communication system further includes a core network device for sending QoS parameters to the main network device.
  • the communication system further includes terminal equipment.
  • Figure 1 is a schematic diagram of a communication system applicable to the present application
  • FIGS. 2 to 5 are schematic diagrams of the DC architecture applicable to this application.
  • Figure 6 is a schematic diagram of multiple bearer types supported under the DC architecture
  • FIG. 7 is a schematic flowchart of a method for determining a bearer type provided in this application.
  • FIG. 8 is a schematic flowchart of another method for determining a bearer type provided in this application.
  • FIG. 9 is a schematic flowchart of another method for determining a bearer type provided in this application.
  • FIG. 10 is a schematic flowchart of yet another method for determining a bearer type provided in this application.
  • Fig. 11 is a schematic flowchart of a method for modifying a bearer type provided by the present application.
  • FIG. 12 is a schematic flowchart of the communication method provided by the present application.
  • FIG. 13 is a schematic structural diagram of a communication device provided by the present application.
  • Fig. 14 is a schematic structural diagram of a network device provided by the present application.
  • GSM global system for mobile communications
  • CDMA code division multiple access
  • WCDMA broadband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • LTE frequency division duplex FDD
  • TDD LTE Time division duplex
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • the terminal equipment in the embodiments of this application may refer to user equipment, access terminals, user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile equipment, user terminals, terminals, wireless communication equipment, user agents, or User device.
  • the terminal device can also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), and a wireless communication Functional handheld devices, computing devices, or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in the future 5G network or future evolution of the public land mobile network (PLMN) Terminal equipment, etc., this embodiment of the present application does not limit this.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • PLMN public land mobile network
  • the network device in the embodiment of the application may be a device used to communicate with terminal devices.
  • the network device may be a global system for mobile communications (GSM) system or a code division multiple
  • the evolved NodeB (eNB or eNodeB) in the LTE system can also be a wireless controller in the cloud radio access network (CRAN) scenario, or the network equipment can be a relay station or an access point , In-vehicle equipment, wearable equipment, network equipment in the future 5G network, network equipment in the future evolution of the PLMN network, etc., the embodiment of the present application is not limited.
  • the network equipment in the 5G network may be, for example, a gNB or a transmission point (trasmission point, TRP).
  • the network equipment in the embodiment of the present application may be composed of a centralized unit (CU) and a distributed unit (DU), where the CU may also be called a control unit (control unit), which adopts CU-DU
  • the structure can separate the protocol layer of the base station, part of the protocol layer functions are placed under the centralized control of the CU, and the remaining part or all of the protocol layer functions are distributed in the DU, and the CU centrally controls the DU.
  • network equipment in the future evolved PLMN network, etc. which are not limited in the embodiment of the present application.
  • the terminal device or the network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also referred to as main memory).
  • the operating system may be any one or more computer operating systems that implement business processing through processes, for example, Linux operating system, Unix operating system, Android operating system, iOS operating system, or windows operating system.
  • the application layer includes applications such as browsers, address books, word processing software, and instant messaging software.
  • the embodiments of the present application do not specifically limit the specific structure of the execution body of the method provided in the embodiments of the present application, as long as the program that records the code of the method provided in the embodiments of the present application can be provided according to the embodiments of the present application.
  • the execution subject of the method provided in the embodiment of the present application may be a terminal device or a network device, or a functional unit in the terminal device or network device that can call and execute the program.
  • computer-readable media may include, but are not limited to: magnetic storage devices (for example, hard disks, floppy disks, or tapes, etc.), optical disks (for example, compact discs (CDs), digital versatile discs (digital versatile discs, DVDs) Etc.), smart cards and flash memory devices (for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.).
  • magnetic storage devices for example, hard disks, floppy disks, or tapes, etc.
  • optical disks for example, compact discs (CDs), digital versatile discs (digital versatile discs, DVDs) Etc.
  • smart cards and flash memory devices for example, erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.
  • various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, wireless channels and various other media capable of storing, containing, and/or carrying instructions and/or data.
  • Figure 1 is a schematic diagram of a communication system suitable for this application.
  • the communication system 100 may include at least two network devices, such as a network device 110 and a network device 120, and the communication system 100 may also include at least one terminal device, such as a terminal device 130.
  • the communication system 100 may also include at least one core network device, such as a core network device 140.
  • FIG. 1 is only a schematic diagram, and the communication system may also include other network devices, such as wireless relay devices and wireless backhaul devices.
  • the embodiments of the present application do not limit the number of network devices and terminal devices included in the mobile communication system.
  • the terminal device 130 can connect the network device 110 and the network device 120 through an air interface, the network device 110 and the network device 120 can be connected in a wired or wireless manner, and the network device 110 and the network device 120 can be connected through a wired Connect to the core network device 140 in a way.
  • the core network device 140 may be a 4G core network device or a 5G core network device.
  • the network device 110 may be an LTE base station or an NR base station; the network device 120 may be an LTE base station or an NR base station.
  • the terminal device 130 can communicate with the network devices 110 and 120 by adopting the DC technology.
  • One of the network devices 110 and 120 is MN, and the other is SN.
  • the core network is the EPC (evolved packet core, EPC), the LTE base station serves as the MN, and the NR base station serves as the SN.
  • EPC evolved packet core
  • the LTE base station and the NR base station can be connected through the X2 interface, at least the control plane connection, and there may be a user plane connection;
  • the LTE base station and the EPC can be connected through the S1 interface, at least the control plane connection, There may also be a user plane connection;
  • the NR base station and the EPC can be connected through the S1-U interface, that is, there can only be a user plane connection.
  • the LTE base station may provide air interface resources for the UE through at least one LTE cell, and at this time, the at least one LTE cell is called MCG.
  • the NR base station may also provide air interface resources for the UE through at least one NR cell.
  • the at least one NR cell is called an SCG.
  • the core network is a 5G core network (5G core, 5GC), with LTE base stations as MN and NR base stations as SN.
  • 5G core 5G core, 5GC
  • the LTE base station and the NR base station can be connected through the Xn interface at this time, at least there is a control plane connection, and there may be a user plane connection;
  • the LTE base station and 5GC can be connected through an NG interface, at least there is a control plane connection, There may also be a user plane connection;
  • the NR base station and 5GC can be connected through an NG-U interface, that is, there can only be a user plane connection.
  • the LTE base station may provide air interface resources for the UE through at least one LTE cell, and at this time, the at least one LTE cell is called MCG.
  • the NR base station may also provide air interface resources for the UE through at least one NR cell.
  • the at least one NR cell is called an SCG.
  • NR base station serves as MN
  • LTE base station serves as SN.
  • the NR base station and the LTE base station can be connected through the Xn interface, at least there is a control plane connection, and there may be a user plane connection; the NR base station and 5GC can be connected through an NG interface, at least there is a control plane connection, There may be a user plane connection; there is an NG-U interface between the LTE station and the 5GC, that is, there can only be a user plane connection.
  • the NR base station can provide air interface resources for the UE through at least one NR cell.
  • the at least one NR cell is called an MCG.
  • the LTE base station may also provide air interface resources for the UE through at least one LTE cell, and in this case, the at least one LTE cell is called an SCG.
  • both MN and SN are NR base stations.
  • the NR primary base station and the NR secondary base station can be connected through an Xn interface, at least a control plane connection, and optionally a user plane connection; there is an NG interface between the NR primary base station and 5GC, and at least a control plane connection is possible.
  • the NR primary base station can provide air interface resources for the UE through at least one NR cell, and at this time, the at least one NR cell is called MCG.
  • the NR secondary base station may also provide air interface resources for the UE through at least one NR cell. In this case, the at least one NR cell is called an SCG.
  • the LTE base station is an eNB and the NR base station is a gNB as an example for description, but this should not constitute any limitation to this application.
  • the DC architecture supports multiple bearer types, including:
  • MN terminated MCG bearer that is, the MCG bearer terminated on the MN;
  • MN terminated SCG bearer, that is, the SCG bearer terminated in MN;
  • MN terminated split bearer, that is, terminate the split bearer in MN;
  • SN terminated MCG bearer that is, the MCG bearer terminated in SN
  • SN terminated split bearer that is, terminates the split bearer in the SN.
  • the MCG bearer refers to a bearer involving only MCG air interface resources
  • an SCG bearer refers to a bearer involving only SCG air interface resources
  • a separate bearer refers to a bearer involving both MCG air interface resources and SCG air interface resources.
  • MN termination or termination at MN means that the packet data convergence protocol (PDCP) entity is in the MN
  • SN termination or termination at the SN means that the PDCP entity is in the SN.
  • MN RLC refers to a radio link control (radio link control, RLC) entity on the MN side.
  • SN RLC refers to the RLC entity on the SN side.
  • MN MAC refers to a media access control (MAC) entity on the MN side.
  • MAC media access control
  • SN MAC refers to the MAC entity on the SN side.
  • the MN can determine the bearer types of all bearers, and inform the SN after deciding the bearer types. If the SN accepts the bearer type, it generates the corresponding configuration according to the bearer type indicated by the MN.
  • the SN can determine the bearer type by itself. However, if the SN determines the bearer type of the bearer that terminates in the SN, the bearer type determined by the SN may not be able to adapt to the operating conditions of the MN, and affect data transmission. Therefore, the SN needs to more reasonably set the bearer type of the SDAP entity established on the SN.
  • this application provides multiple methods for determining the bearer type.
  • the SN can determine the bearer type of the QoS flow or the bearer type of the DRB more reasonably according to whether the MN provides auxiliary information.
  • the SN can more reasonably determine the bearer type of the QoS flow or the bearer type of the DRB according to the suggested information provided by the MN.
  • the recommended information may be the QoS flow of the SDAP entity in the SN or the DRB bearer type suggested by the MN.
  • the bearer type of the QoS flow described in this application actually refers to the bearer type of the bearer corresponding to the QoS flow, or the bearer type of the bearer to which the QoS flow belongs.
  • the following mainly uses the MN as the main network device and the SN as the auxiliary network device as an example to illustrate the method of the present application. It should be noted that, in fact, the operations performed by the MN can also be performed by the chip in the MN, and similarly, the operations performed by the SN can also be performed by the chip in the SN.
  • the first method provided in this application mainly includes: the primary network device generates a first message according to whether the first message includes auxiliary information; the primary network device sends the first message to the secondary network device.
  • the auxiliary network device receives the first message sent by the main network device, and determines the bearer type of the QoS flow according to whether the first message includes the auxiliary information.
  • the SDAP entity corresponding to the QoS flow is established on the auxiliary network device.
  • the primary network device can assist the secondary network in determining the bearer type of the QoS flow by whether the secondary information is included in the first message. Accordingly, the secondary network device
  • the bearer type of the QoS flow can be reasonably determined according to whether the first message provided by the main network device includes auxiliary information. Therefore, the purpose of the auxiliary network device to reasonably set the bearer type of the QoS flow can be achieved.
  • the problem of a long negotiation process between the auxiliary network device and the main network device caused by the inappropriate decision of the auxiliary network device on the bearer type of the QoS flow can also be avoided.
  • the method will be described in detail with reference to FIG. 7.
  • FIG. 7 shows an exemplary flowchart of a method 200 for determining a bearer type provided by the present application.
  • the method 200 mainly includes S210 to S230. The steps are described below.
  • S210 The MN generates a first message according to whether auxiliary information is included in the first message.
  • the first message is used by the SN to determine the bearer type of the first QoS flow.
  • the result of whether the first message includes auxiliary information is used by the SN to determine the bearer type of the first QoS flow. That is, the SN can determine the bearer type of the first QoS flow according to whether the first message includes auxiliary information.
  • the first QoS flow may be any QoS flow established on the SN by the corresponding SDAP entity. It should be understood that the SDAP entity corresponding to the first QoS flow is established in the SN, and it can also be understood that the PDCP entity corresponding to the bearer corresponding to the first QoS flow is established in the SN.
  • the bearer types described herein include MCG bearers, SCG bearers or separate bearers.
  • MCG bearer and separated bearer are bearers involving MCG air interface resources.
  • the bearers related to MCG air interface resources include MCG bearers or separate bearers.
  • the bearer type of the first QoS flow is actually an SCG bearer terminated at the SN, an MCG bearer terminated at the SN, or a separate bearer terminated at the SN.
  • the MN may include auxiliary information in the first message.
  • the MN may not include auxiliary information in the first message.
  • the air interface resource is used to provide the transmission bit rate of the first QoS flow.
  • S220 The MN sends the first message to the SN.
  • the SN receives the first message.
  • the SN determines the bearer type of the first QoS flow according to whether the first message includes auxiliary information.
  • the MN can assist the SN in determining the bearer type of the QoS flow by including auxiliary information in the first message. Accordingly, the SN The bearer type of the QoS flow can be reasonably determined according to whether the first message provided by the MN includes auxiliary information. Therefore, the SN can achieve the purpose of reasonably setting the bearer type of the QoS flow. Moreover, it can also avoid the problem of a long negotiation process between the MN and the SN caused by the inappropriate decision of the auxiliary network device on the bearer type of the QoS flow.
  • the first QoS flow is a GBR QoS flow
  • the auxiliary information is the first GBR QoS parameter.
  • the first GBR QoS parameter is the GBR QoS parameter provided by the MN for the first QoS flow, or in other words, the first GBR QoS parameter is the GBR QoS parameter that the MN can provide for the first QoS flow.
  • the first message may indicate that the SN is allowed to configure the bearer type of the first QoS flow as a bearer type involving MCG air interface resources; in other words, if the first message includes auxiliary information SN may consider configuring the first QoS flow as a bearer type involving MCG air interface resources.
  • the first message may instruct the SN to determine the bearer type of the first QoS flow as an SCG bearer; or, if the first new message does not include auxiliary information, the SN may The first QoS flow is configured as an SCG bearer, or the SN may determine that the bearer type of the first QoS flow is an SCG bearer.
  • S230 specifically includes: if the first message includes auxiliary information, the SN determines that the bearer type of the first QoS flow is MCG bearer, SCG bearer, or separate bearer; if the first message does not include auxiliary information, the SN determines the status of the first QoS flow The bearer type is SCG bearer.
  • the MN carries the first GBR QoS parameters in the first message, it means that the MN can provide GBR QoS parameters for the first QoS flow, or the MN can allocate MCG air interface resources for the first QoS flow, so that the SN can Consider determining (or configuring) the bearer type of the first QoS flow as a bearer type involving MCG air interface resources, that is, MCG bearer or separate bearer.
  • the SN may or has the opportunity to determine the bearer type of the first QoS flow as an MCG bearer or a separate bearer.
  • the bearer type of the first QoS flow finally determined by the SN can be independently determined.
  • the bearer type of the first QoS flow finally determined by the SN may not be an MCG bearer or a separate bearer, that is, it may be an SCG bearer.
  • the SN can provide the GBR QoS parameters required by the first QoS flow for the first QoS flow, the SN may determine that the bearer type of the first QoS flow is an SCG bearer. It should be understood that the GBR QoS parameters required by the first QoS flow have the same meaning as the second GBR QoS parameters described below.
  • the SN can determine the bearer type of the first QoS flow as the SCG bearer.
  • the MN can assist the SN in determining the bearer type of the GBR QoS flow by whether it carries the GBR QoS parameters provided for the GBR QoS flow in the first message.
  • the SN can be based on the first message provided by the MN. Whether to include the GBR QoS parameters provided by the MN for the GBR QoS flow, reasonably determine the bearer type of the GBR QoS flow.
  • GBR QoS parameters may include one or more of uplink maximum bit rate, downlink maximum bit rate, uplink GBR, and downlink GBR.
  • the first GBR QoS parameter may be one or more of the uplink maximum bit rate, the downlink maximum bit rate, the uplink GBR, and the downlink GBR provided by the MN for the first QoS flow.
  • the MN may also carry the second GBR QoS parameter of the first QoS flow in the first message.
  • the second GBR QoS parameter is the GBR QoS parameter of the first QoS flow received by the MN from the core network device. It should be understood that the second GBR QoS parameter may be one or more of the uplink maximum bit rate, the downlink maximum bit rate, the uplink GBR, and the downlink GBR of the first QoS flow received by the MN from the core network device. It should also be understood that the parameter type included in the second GBR QoS parameter may be the same as the parameter type included in the first GBR QoS parameter.
  • the parameters included in the first GBR QoS parameter are the uplink maximum bit rate and the downlink maximum bit rate
  • the parameters included in the second GBR QoS parameter may also be the uplink maximum bit rate and the downlink maximum bit rate.
  • this application does not limit this.
  • the types of parameters included in the second GBR QoS parameter may also be more than the types of parameters included in the first GBR QoS parameter.
  • the SN can determine the bearer type of the first QoS flow in combination with the second GBR QoS parameter.
  • the SN may determine the bearer type of the first QoS flow as a separate bearer.
  • the SN may not provide SCG air interface resources. In this case, the SN may determine the bearer type of the first QoS flow as the MCG bearer.
  • the SN can also determine the bearer type of the first QoS flow in combination with its ability to provide GBR QoS parameters for the first QoS flow.
  • the SN may determine the bearer type of the QoS flow as an SCG bearer.
  • the SN can combine more information, such as the GBR QoS parameters of the first QoS flow received by the MN from the core network equipment and/or the SN can provide GBR QoS parameters for the first QoS flow, which is more reasonable Determine the bearer type of the first QoS flow.
  • the second GBR QoS parameter and the first GBR QoS parameter include The parameter types of are the same, and the parameters of the same type are compared.
  • the value of the second GBR QoS parameter is equal to the value of the second GBR QoS parameter, which means that any parameter of the same type
  • the values of the second GBR QoS parameters are the same; similarly, the value of the second GBR QoS parameter is greater than the value of the second GBR QoS parameter.
  • the second GBR QoS parameter is The value is greater than the value of the parameter of this type in the first GBR QoS parameter; the value of the second GBR QoS parameter is smaller than the value of the second GBR QoS parameter.
  • the second GBR The value of the parameter of this type in the QoS parameter is smaller than the value of the parameter of this type in the first GBR QoS parameter.
  • the parameters included in the first GBR QoS parameter and the second GBR QoS parameter are both the uplink maximum bit rate and the downlink maximum bit rate, then if the uplink maximum bit rate in the first GBR QoS parameter is equal to the second GBR QoS The maximum uplink bit rate in the parameter, and the maximum downlink bit rate in the first GBR QoS parameter is equal to the downlink maximum bit rate in the second GBR QoS parameter, then the value of the first GBR QoS parameter and the value of the second GBR QoS parameter are considered The values are equal.
  • the uplink maximum bit rate in the first GBR QoS parameter is greater than the uplink maximum bit rate in the second GBR QoS parameter, and the downlink maximum bit rate in the first GBR QoS parameter is greater than the downlink maximum bit rate in the second GBR QoS parameter, It is considered that the value of the first GBR QoS parameter is greater than the value of the second GBR QoS parameter.
  • the uplink maximum bit rate in the first GBR QoS parameter is less than the uplink maximum bit rate in the second GBR QoS parameter, and the downlink maximum bit rate in the first GBR QoS parameter is less than the downlink maximum bit rate in the second GBR QoS parameter, It is considered that the value of the first GBR QoS parameter is smaller than the value of the second GBR QoS parameter.
  • the first QoS flow is a non-GBR QoS flow
  • the auxiliary information is the AMBR of the first UE and the AMBR of the first PDU session.
  • the first UE AMBR is the AMBR provided by the MN for the target UE to establish a non-GBR QoS flow in the SN, and the target UE is the UE corresponding to the first QoS flow.
  • all non-GBR QoS flows of the target UE are composed of the non-GBR QoS flows established in the MN (denoted as: the first part of non-GBR QoS flows) and the non-GBR QoS flows established in the SN (denoted as: Two parts of non-GBR QoS flow), the first UE AMBR is the AMBR provided by the MN for the second part of non-GBR QoS flow. It should be understood that the second part of the non-GBR QoS flow includes the first QoS flow.
  • the UE AMBR may include one or both of the UE downlink AMBR and the UE uplink AMBR.
  • the first PDU session AMBR is the AMBR provided by the MN for the non-GBR QoS flow established in the SN in the target PDU session.
  • the first QoS flow corresponds to the target PDU session, that is, the non-GBR QoS flow established in the SN in the target PDU session includes the first QoS flow.
  • the non-GBR QoS flow established in the SN in the target PDU session is all or part of the second part of the non-GBR QoS flow.
  • the PDU session AMBR may include one or both of the PDU session downlink AMBR and the PDU session uplink AMBR.
  • the non-GBR QoS flow established in the SN refers to the non-GBR QoS flow established in the SN by the corresponding SDAP entity.
  • the non-GBR QoS flow in the MN refers to the non-GBR QoS flow established in the MN by the corresponding SDAP entity.
  • the first message (or auxiliary information) includes the first UE AMBR and the first PDU session AMBR.
  • the first message may indicate that the SN is allowed to configure the bearer type of the first QoS flow as a bearer type involving MCG air interface resources.
  • the SN may consider configuring the first QoS flow as a bearer type involving MCG air interface resources.
  • S230 specifically includes: if the first message (or auxiliary information) includes the first UE AMBR and the first PDU session AMBR, the SN determines that the bearer type of the first QoS flow is MCG bearer, SCG bearer or separated bearer.
  • the MN can provide MCG air interface resources for the second part of the non-GBR QoS flow including the first QoS flow, that is, the MN It can provide MCG air interface resources for the non-GBR QoS flow including the first QoS flow.
  • the MN can provide MCG air interface resources for the non-GBR QoS flow established in the SN in the target PDU session, and the non-GBR QoS flow established in the SN in the target PDU session also includes the first QoS flow.
  • the MN may allocate MCG air interface resources for the first QoS flow, so that the SN may consider determining (or configuring) the bearer type of the first QoS flow as a bearer type involving MCG air interface resources, that is, MCG bearer or separate bearer.
  • the SN may or is allowed to determine the bearer type of the first QoS flow as an MCG bearer or a separate bearer.
  • the bearer type of the first QoS flow finally determined by the SN may not be an MCG bearer or a separate bearer, that is, it may be an SCG bearer.
  • the first message does not include the first UE AMBR and the first PDU session AMBR.
  • the first message may instruct the SN to determine the bearer type of the first QoS flow as an SCG bearer.
  • S230 specifically includes: if the first message does not include the first UE AMBR and the first PDU session AMBR, the SN determines that the bearer type of the first QoS flow is an SCG bearer.
  • the MN may consider determining the bearer type of the first QoS flow as an SCG bearer.
  • the first message includes the first UE AMBR, and does not include the first PDU session AMBR.
  • the first message may indicate that the SN is allowed to configure the bearer type of the first QoS flow as a bearer type involving MCG air interface resources.
  • S230 specifically includes: if the first message includes the first UE AMBR and does not include the first PDU session AMBR, the SN determines that the bearer type of the first QoS flow is MCG bearer, SCG bearer, or separate bearer.
  • the MN may also consider the first
  • the bearer type of the QoS flow is determined (or configured) as a bearer type involving MCG air interface resources, that is, MCG bearer or separate bearer.
  • the bearer type of the first QoS flow finally determined by the SN may not be an MCG bearer or a separate bearer, that is, it may be an SCG bearer.
  • the first message includes the first PDU session AMBR, and does not include the first UE AMBR.
  • the first message may indicate that the SN is allowed to configure the bearer type of the first QoS flow as a bearer type involving MCG air interface resources.
  • S230 specifically includes: if the first message includes the first PDU session AMBR, and does not include the first UE AMBR, the SN determines that the bearer type of the first QoS flow is MCG bearer, SCG bearer, or separate bearer.
  • the MN does not carry the AMBR of the first UE in the first message
  • the MN carries the AMBR of the first PDU session in the first message, which means that the MN can be a non-GBR QoS flow containing the first QoS flow.
  • the SN may determine the bearer type of the non-GBR QoS flow as an SCG bearer, but this application does not limit this.
  • the SN can determine the bearer type of the first QoS flow according to whether the first message includes auxiliary information, and further, according to the content included in the auxiliary information.
  • the basic idea of the second method is that when designing the format of the first message, two cell positions can be reserved in the first message, that is, the cell corresponding to the AMBR of the first UE corresponds to the AMBR of the first PDU session. ⁇ .
  • the MN may not fill any one or both of these two information elements, so as to achieve the meaning represented by the above cases 1 to 4.
  • whether the first QoS flow can be configured as a bearer type involving MCG air interface resources depends on whether the SN receives the first PDU session AMBR provided by the MN for the target PDU session corresponding to the first QoS flow. .
  • the SN may consider determining (or configuring) the bearer type of the first QoS flow as involving the MCG air interface
  • the bearer type of the resource that is, MCG bearer or separated bearer, can be MCG bearer, SCG bearer, or separated bearer; if it is not received, the SN can determine that the bearer type of the first QoS flow is SCG bearer.
  • the first QoS flow is a non-GBR QoS flow
  • the auxiliary information is the first UE AMBR.
  • the meaning of the first UE AMBR is referred to the above description, and will not be repeated.
  • the first message may indicate that the SN is allowed to configure the bearer type of the first QoS flow as a bearer type involving MCG air interface resources; in other words, if the first message includes auxiliary information, The SN may consider configuring the first QoS flow as a bearer type involving MCG air interface resources. And/or, if the first message does not include auxiliary information, the first message may instruct the SN to configure the bearer type of the first QoS flow as an SCG bearer.
  • S230 specifically includes: if the first message includes auxiliary information, the SN determines that the bearer type of the first QoS flow is MCG bearer, SCG bearer, or separated bearer. If the first message does not include auxiliary information, the SN determines that the bearer type of the first QoS flow is an SCG bearer.
  • the SN may consider determining (or configuring) the bearer type of the first QoS flow as a bearer type involving MCG air interface resources. In other words, the SN may or has the opportunity to determine the bearer type of the first QoS flow as an MCG bearer or a separate bearer. However, the bearer type of the first QoS flow finally determined by the SN may not be an MCG bearer or a separate bearer, that is, it may be an SCG bearer.
  • the MN does not carry the first UE AMBR in the first message, it means that the MN cannot provide MCG air interface resources for the second part of the non-GBR QoS flow containing the first QoS flow, so the SN can consider adding the first UE AMBR
  • the bearer type of a QoS flow is determined as the SCG bearer.
  • the SN can reasonably determine the bearer type of the first QoS flow according to whether the first message includes auxiliary information.
  • the first QoS flow is a non-GBR QoS flow
  • the auxiliary information is the AMBR of the first PDU session. Refer to the above description for the meaning of AMBR of the first PDU session, and will not be repeated.
  • the first message may indicate that the SN is allowed to configure the bearer type of the first QoS flow as a bearer type involving MCG air interface resources; in other words, if the first message includes auxiliary information, The SN may consider configuring the first QoS flow as a bearer type involving MCG air interface resources. And/or, if the first message does not include auxiliary information, the first message may instruct the SN to configure the bearer type of the first QoS flow as an SCG bearer.
  • S230 specifically includes: if the first message includes auxiliary information, the SN determines that the bearer type of the first QoS flow is MCG bearer, SCG bearer, or separated bearer. And/or, if the first message does not include auxiliary information, the SN determines that the bearer type of the first QoS flow is an SCG bearer.
  • the MN carries the AMBR of the first PDU session in the first message, it means that the MN can provide MCG air interface resources for the non-GBR QoS flow established in the SN in the target PDU session, so the SN can consider adding the first QoS
  • the bearer type of the flow is determined (or configured) as the bearer type involving the MCG air interface resources.
  • the SN may or has the opportunity to determine the bearer type of the first QoS flow as an MCG bearer or a separate bearer.
  • the bearer type of the first QoS flow finally determined by the SN may not be an MCG bearer or a separate bearer, that is, it may be an SCG bearer.
  • the MN does not carry the AMBR of the first PDU session in the first message, it means that the MN cannot provide MCG air interface resources for the non-GBR QoS flow established in the SN in the target PDU session, so that the SN can determine the first
  • the bearer type of the QoS flow is SCG bearer.
  • the SN can reasonably determine the bearer type of the first QoS flow according to whether the first message includes auxiliary information.
  • the MN may also carry the second UE AMBR of the first QoS flow and/or the second PDU session AMBR in the first message.
  • the second UE AMBR may be determined by the MN according to the UE AMBR received from the core network device.
  • the second PDU session AMBR may be determined by the MN according to the PDU session AMBR received from the core network device.
  • the second UE AMBR is the AMBR that the SN needs to provide for the second part of the non-GBR QoS flow.
  • the second PDU session AMBR is the AMBR that the SN needs to provide for the non-GBR QoS flow in the target PDCP entity.
  • the SN may combine the second UE AMBR and/or the second PDU session AMBR to determine the bearer type of the first QoS flow.
  • the SN may determine the bearer type of the first QoS flow as the MCG bearer.
  • the SN may determine the bearer type of the first QoS flow as the MCG bearer.
  • the SN may determine the bearer type of the first QoS flow as a separate bearer.
  • the SN may determine the bearer type of the first QoS flow as a separate bearer.
  • the relationship between the AMBR of the first UE and the AMBR of the second UE, and the meaning of the relationship between the AMBR of the first PDU session and the AMBR of the second PDU session are related to the relationship between the size of the first GBR QoS parameter and the second GBR QoS parameter The meaning is similar, so I won't repeat them here.
  • the first message includes auxiliary information, but the value of the auxiliary information is 0, this is equivalent to a solution in which the first message does not include auxiliary information.
  • the method may further include:
  • S240 The SN sends bearer type indication information to the MN.
  • the MN receives the bearer type indication information sent by the SN.
  • the MN determines the bearer type of the first QoS flow according to the bearer type indication information.
  • the bearer type indication information is used to indicate the bearer type of the first QoS flow determined by the SN.
  • the SN may inform the MN of the bearer type of the first QoS flow determined by it through the bearer type indication information. Therefore, the MN can determine the bearer type of the first QoS flow according to the bearer type indication information.
  • the bearer type indication information may be explicit information, that is, the bearer type indication information is the bearer type of the first QoS flow, or the bearer type indication information is whether the bearer type of the first QoS flow involves an MCG air interface Resource information. That is to say, the SN clearly tells the MN the bearer type of the first QoS flow, or informs the MN whether the bearer type of the first QoS flow involves MCG air interface resources.
  • the bearer type indication information can be implicit information.
  • the bearer type indication information may be uplink transmission network layer (UL TNL) information allocated by the SN for the bearer corresponding to the first QoS flow to receive uplink data.
  • the uplink transmission network layer information may include an internet protocol (IP) address and/or a tunnel endpoint identifier (TEID).
  • IP internet protocol
  • TEID tunnel endpoint identifier
  • the bearer type indication information is the uplink transmission network layer information, it indicates that the bearer type of the first QoS flow determined by the SN is a bearer type involving MCG air interface resources.
  • the MN may generate the RLC configuration and the logical channel configuration for the first QoS flow or the bearer corresponding to the first QoS flow.
  • the bearer type indication information may also indicate or include the identifier of the first QoS flow or the identifier of the bearer corresponding to the first QoS flow.
  • this application also provides three other methods for determining the bearer type. The description will be given below with reference to FIGS. 8 to 10 respectively.
  • FIG. 8 shows an exemplary flowchart of another method 300 for determining a bearer type provided by the present application.
  • the method 300 mainly includes S310 to S330. The steps are described below.
  • the MN generates suggestion information.
  • the suggestion information is used to indicate the bearer type of the first QoS flow suggested by the MN.
  • the definition of the first QoS flow is the same as the definition of the first QoS flow in the method 200, and will not be repeated here.
  • the MN sends the suggestion information to the SN.
  • the SN receives the suggestion information sent by the MN.
  • the SN determines the bearer type of the first QoS flow according to the recommendation information.
  • the MN may suggest the bearer type of the first QoS flow to the SN, and the SN may determine the bearer type of the first QoS flow according to the MN's recommendation.
  • the SN can more reasonably determine the bearer type of the QoS flow according to the bearer type suggested by the MN.
  • the SN can independently determine the bearer type of the first QoS flow. That is, the bearer type finally determined by the SN may be the bearer type suggested by the MN or not the bearer type suggested by the MN. For example, if the bearer type recommended by the MN is a separate bearer, but the SN can meet the QoS requirements of the first QoS flow, the bearer type of the first QoS flow may be determined as an SCG bearer.
  • the method may further include:
  • S340 The SN sends bearer type indication information to the MN.
  • the MN receives the bearer type indication information sent by the SN.
  • the bearer type indication information is used to indicate the bearer type of the first QoS flow determined by the SN.
  • the MN determines the bearer type of the first QoS flow according to the bearer type indication information.
  • the SN may notify the network device of the determined bearer type of the first QoS flow through the bearer type indication information. Therefore, the network device can determine the bearer type of the first QoS flow according to the bearer type indication information.
  • FIG. 9 shows an exemplary flowchart of another method 400 for determining a bearer type provided by the present application.
  • the method 400 mainly includes S410 to S430. The steps are described below.
  • S410 The MN generates a first message according to whether auxiliary information is included in the first message.
  • the first message is used by the SN to determine the bearer type of the first DRB.
  • the result of whether the first message includes auxiliary information is used by the SN to determine the bearer type of the first DRB. That is, the SN can determine the bearer type of the first DRB according to whether the first message includes auxiliary information.
  • the first DRB may be any DRB established on the SN by the corresponding PDCP entity.
  • the MN may include auxiliary information in the first message.
  • the MN may not include auxiliary information in the first message.
  • the air interface resource is used to provide the transmission bit rate of the first DRB.
  • the MN sends the first message to the SN.
  • the SN receives the first message sent by the MN.
  • the SN determines the bearer type of the first DRB according to whether the first message includes auxiliary information.
  • the MN can assist the SN in determining the bearer type of the DRB by whether the first message includes auxiliary information. Accordingly, the SN can be based on Whether the first message provided by the MN includes auxiliary information, and reasonably determine the bearer type of the DRB. Therefore, the purpose of the SN to reasonably set the bearer type of the DRB can be achieved, and the problem of a long protocol process caused by the inappropriate decision of the SN on the bearer type of the DRB in the prior art can be avoided.
  • the auxiliary information is a first parameter
  • the first parameter is a QoS parameter provided by the MN for the first DRB.
  • the QoS parameter may include one or more of uplink MBR, downlink MBR, uplink GBR, and downlink GBR.
  • the first message may indicate that the SN is allowed to configure the bearer type of the first DRB as a bearer type involving MCG air interface resources.
  • the SN may consider configuring the first DRB as a bearer type involving MCG air interface resources.
  • the first message may instruct the SN to determine the bearer type of the first DRB as an SCG bearer.
  • S430 specifically includes: if the first message includes auxiliary information, the SN determines that the bearer type of the first DRB is MCG bearer, SCG bearer or separated bearer; if the first message does not include auxiliary information, the SN determines the bearer type of the first DRB Carried by SCG.
  • the MN carries the first parameter in the first message, it means that the MN can provide QoS parameters for the first DRB, or it means that the MN can allocate the air interface resources related to the MCG for the first DRB, so the SN can consider adding the first DRB.
  • the bearer type of a DRB is determined (or configured) as a bearer type involving MCG air interface resources, that is, MCG bearer or separated bearer. That is, the SN may or has the opportunity to determine the bearer type of the first DRB as the MCG bearer or the separated bearer.
  • the bearer type of the first DRB finally determined by the SN may not be an MCG bearer or a separate bearer, that is, it may be an SCG bearer.
  • the SN can provide the first DRB with the QoS parameters required by the first DRB, it can be determined that the bearer type of the first DRB is an SCG bearer.
  • the MN does not carry the first parameter in the first message, it means that the MN cannot allocate the MCG-related air interface resources for the first DRB, so the SN can determine the bearer type of the first DRB as an SCG bearer.
  • the MN can assist the SN to determine the bearer type of the first DRB by whether it carries the QoS parameters provided for the DRB in the first message.
  • the SN can determine whether the MN is included in the first message provided by the MN.
  • the QoS parameter provided for the first DRB reasonably determines the bearer type of the first DRB.
  • the method may further include:
  • the SN sends bearer type indication information to the MN.
  • the MN receives the bearer type indication information sent by the SN.
  • the MN determines the bearer type of the first DRB according to the bearer type indication information.
  • the bearer type indication information is used to indicate the bearer type of the first DRB determined by the SN.
  • the SN may notify the MN of the determined bearer type of the first DRB through the bearer type indication information. Therefore, the MN can learn the bearer type of the first DRB determined by the SN.
  • the bearer type indication information may be explicit information, that is, the bearer type indication information is the bearer type of the first DRB, or the bearer type indication information is whether the bearer type of the first DRB involves MCG air interface resources information.
  • the SN explicitly tells the MN the bearer type of the first DRB, or informs the MN whether the bearer type of the first DRB involves MCG air interface resources.
  • the bearer type indication information can be implicit information.
  • the bearer type indication information may be uplink transmission network layer information allocated by the SN for the first DRB to receive uplink data.
  • the uplink transmission network layer information may include an Internet Protocol (IP) address and a tunnel endpoint identifier (TEID), and the SN can receive the uplink data of the first DRB sent by the MN according to the uplink transmission network layer information.
  • IP Internet Protocol
  • TEID tunnel endpoint identifier
  • the bearer type indication information is the transport layer information, it indicates that the bearer type of the first DRB determined by the SN is a bearer type involving MCG air interface resources.
  • the MN may generate RLC entity and logical channel configuration for the first DRB.
  • the bearer type indication information may also include or indicate the identity of the first DRB.
  • FIG. 10 shows an exemplary flowchart of another method 500 for determining a bearer type provided by the present application.
  • the method 500 mainly includes S510 to S530. The steps are described below.
  • the MN generates suggestion information.
  • the suggestion information is used to indicate the bearer type of the first DRB suggested by the MN.
  • the definition of the first DRB is the same as the definition of the first DRB in the method 400, and will not be repeated here.
  • the MN may generate recommendation information according to whether it can provide air interface resources for the first DRB.
  • the air interface resource is used to provide the transmission bit rate of the first DRB. For example, if the MN can provide air interface resources for the first DRB, it may suggest that the SN determine the bearer type as separate bearer or MCG bearer. For another example, if the MN cannot provide air interface resources for the first DRB, it may suggest that the SN determine the bearer type as an SCG bearer.
  • the MN sends the suggestion information to the SN.
  • the SN receives the suggestion information sent by the MN.
  • the SN determines the bearer type of the first DRB according to the suggestion information.
  • the MN may suggest the bearer type of the first DRB to the SN, and the SN may determine the bearer type of the DRB according to the MN's suggestion.
  • the SN can more reasonably determine the bearer type of the DRB according to the recommended bearer type provided by the MN.
  • the bearer type finally determined by the SN may be the bearer type suggested by the MN or not the bearer type suggested by the MN.
  • the bearer type recommended by the MN is a separate bearer, but the SN can meet the QoS requirements of the first DRB, the bearer type of the first DRB may be determined as an SCG bearer.
  • the method may further include:
  • S540 The SN sends bearer type indication information to the MN.
  • the MN receives the bearer type indication information sent by the SN.
  • S550 The MN determines the bearer type of the first DRB according to the bearer type indication information.
  • the bearer type indication information is used to indicate the bearer type of the first DRB determined by the SN.
  • the SN may notify the network device of the determined bearer type of the first DRB through the bearer type indication information. Therefore, the network device can determine the bearer type of the first DRB according to the bearer type indication information.
  • this application also provides a method for modifying the bearer type.
  • This method provides the possibility for the SN to modify the bearer type of the bearer.
  • the method of modifying the bearer type will be described with reference to FIG. 11.
  • the method shown in FIG. 11 may be executed after any one of the methods shown in FIG. 7 to FIG. 10.
  • the first bearer in the method shown in FIG. 11 may be a bearer corresponding to the first QoS flow in the methods shown in FIG. 7 and FIG. 8.
  • the bearer type is determined according to the method shown in FIG. 7 or FIG. 8, and after the bearer is further established, when the SN needs to modify the bearer type, the method shown in FIG. 11 can be used to modify the bearer type.
  • the first bearer in the method shown in FIG. 11 may be the first DRB in the method shown in FIG. 9 and FIG. 10.
  • the bearer type is determined according to the method shown in FIG. 9 or FIG. 10, and after the bearer is further established, when the SN needs to modify the bearer type, the method shown in FIG. 11 can be used to modify the bearer type.
  • Fig. 11 shows a schematic flowchart of a method for modifying a bearer type.
  • the method mainly includes S610 to S620. The steps are described in detail below.
  • the SN generates a modification request (required) message.
  • the modification request message is used to apply for modification of the bearer type of the first bearer.
  • the PDCP entity corresponding to the first bearer is established in the SN.
  • the SDAP entity corresponding to the first bearer of the QoS flow is established in the SN.
  • S620 The SN sends the modification request message to the MN.
  • the MN receives the modification request message sent by the SN.
  • the SN may request to modify the bearer type of the first bearer by sending a modification request message to the MN.
  • the modification request message may include a bearer establishment list and a bearer deletion list.
  • the bearer establishment list includes the identity of the first bearer and indication information (referred to as indication information for short) indicating the type of bearer that the first bearer needs to modify;
  • the bearer deletion list may include the identity of the first bearer.
  • the bearer deletion list may also include the current bearer type of the first bearer.
  • the bearer type that needs to be modified indicated by the indication information is the new bearer type of the first bearer determined by the SN.
  • the current bearer type of the first bearer is the original bearer type of the first bearer. That is, the SN expects to modify the first bearer from the original bearer type to the new bearer type.
  • the bearer type of the first bearer can be modified.
  • the indication information may be an explicit bearer type, such as MCG bearer, SCG bearer or separate bearer.
  • the indication information may also be implicit information, and the implicit information may indicate the new bearer type of the first bearer.
  • the implicit information may be uplink transmission network layer (UL TNL) information, and the uplink transmission network layer information is the transmission layer allocated by the SN for the first bearer to receive uplink data sent by the MN Information, where the uplink data is the uplink data of the first bearer received by the MN from the terminal device.
  • UL TNL uplink transmission network layer
  • the indication information is the uplink transmission network layer information, it means that the new bearer type is a bearer type involving MCG air interface resources, that is, MCG bearer or separate bearer.
  • the uplink transmission network layer information may include an Internet Protocol (IP) address and a tunnel endpoint identifier (TEID), and the SN can receive the uplink data of the first bearer sent by the MN according to the uplink transmission network layer information.
  • IP Internet Protocol
  • TEID tunnel endpoint identifier
  • the SN can trigger the modification (or change) of the bearer type by sending a modification request message to the MN, and further can realize the modification of the bearer type.
  • the SN can implement the modification of the bearer type triggered by the SN by carrying the same bearer identifier in the bearer establishment list and the bearer deletion list.
  • the MN can independently decide whether to accept the SN modification application.
  • the MN After receiving the SN, the MN can independently decide whether to accept the SN modification application. If the MN decides to accept the SN's application for modifying the first bearer, the method may further include S630 to S650.
  • S630 The MN sends a modification request (request) message to the SN.
  • the SN receives the modification request message sent by the MN.
  • the modification request message is used to indicate that the MN agrees to modify the bearer type of the first bearer.
  • the SN receives the modification request message sent by the MN, it can learn that the MN agrees to modify the bearer type of the first bearer.
  • the MN may also carry the above-mentioned uplink transmission network layer information in the modification request message. Or, if the above indication information is uplink transmission network layer information, the MN may not carry the uplink transmission network layer information in the modification request message.
  • the SN sends an acknowledgement (acknowledge) message to the MN.
  • the MN receives the modification request confirmation message sent by the SN.
  • the modification request confirmation message includes air interface RRC configuration #1, which is air interface RRC configuration #1 generated by the SN for the terminal device, and the air interface RRC configuration #1 is used for the terminal device to configure the first bearer.
  • the MN can send the air interface RRC configuration #1 and air interface RRC configuration #2 to the terminal device.
  • the terminal device receives the air interface RRC configuration #1 and the air interface RRC configuration #2.
  • the SN needs to generate a PDCP recovery configuration for the UE (that is, an example of air interface RRC configuration #1), and instruct the PDCP entity of the bearer to perform data recovery.
  • the MN needs to generate a MCG RLC bearer deletion configuration for the UE (ie, an example of air interface RRC configuration #2).
  • the new bearer type is MCG bearer
  • SN needs to generate SCG and RLC bearer release configuration for UE (ie, an example of air interface RRC configuration #1)
  • MN needs to generate MCG and RLC bearer for UE Added configuration (ie, an example of air interface RRC configuration #2).
  • the MN sends a modification confirmation (confirm) message to the SN.
  • the SN receives the modification confirmation message sent by the MN.
  • the modification confirmation message is used to indicate that the modification of the bearer type of the first bearer is completed.
  • the MN after the MN accepts the SN modification request, it can send a modification request message to the SN. On the one hand, it informs the SN that the MN has accepted the modification request. On the other hand, it requests the SN to generate the corresponding air interface RRC configuration for the first bearer. #1. After the SN generates the first bearer to generate the corresponding air interface RRC configuration #1, it sends the configuration to the MN through a modification request confirmation message. After receiving the modification request confirmation message, the MN generates air interface RRC configuration #2, and sends air interface RRC configuration #1 and air interface RRC configuration #2 to the terminal device together to complete the configuration of the first bearer. In addition, the MN informs the SN that the MN has completed the configuration of the first bearer by sending a modification confirmation message to the SN.
  • MN must accept the application for modification of SN. That is, the MN cannot reject the bearer modification request initiated by the SN for the first bearer.
  • the SN may carry air interface RRC configuration #1 in the modification request message.
  • the method may also include the foregoing S650 and S660. That is, in the second scenario, S630 and S640 may not be executed, and S650 and S660 are executed after S620.
  • the MN after receiving the air interface RRC configuration #1 sent by the SN, the MN generates an air interface RRC configuration #2, and sends the air interface RRC configuration #1 and the air interface RRC configuration #2 to the terminal device together to complete the configuration of the first bearer.
  • the MN informs the SN that the MN has completed the configuration of the first bearer by sending a modification confirmation message to the SN.
  • the MN may also carry the above-mentioned uplink transmission network layer information in the modification confirmation message in S660.
  • the MN may not carry the uplink transmission network layer information in the modification confirmation message.
  • the auxiliary network device can modify the bearer type to a bearer type that is more suitable for the air interface state on the auxiliary network device side.
  • the MN and the SN can also negotiate the uplink transmission time of the terminal device in the MN or SN after the bearer type is determined by the method for determining the bearer type as shown in FIGS. 6 to 11, for example.
  • the following description will be made with reference to FIG. 13. It should be understood that the communication method shown in FIG. 13 may be applicable to various DC scenarios shown in FIG. 2 to FIG. 5, for example, a NE-DC scenario where the primary base station is a 5G base station and the secondary base station is an LTE base station.
  • FIG. 13 is a schematic flowchart of a communication method 700 provided in this application.
  • the method 700 mainly includes S710 to S730. The steps are described below.
  • S710 The MN sends time domain configuration information to the SN.
  • the SN receives the time domain configuration information.
  • the MN when the MN confirms that the terminal device needs the terminal device to perform single uplink transmission due to power control or intermodulation interference (intermodulation interference), the MN sends time domain configuration information to the SN.
  • the time domain configuration information may be the uplink and downlink time domain allocation of the terminal equipment in the SN.
  • the single uplink transmission means that the terminal device only sends data or signals to the cells of the MN or SN in a time unit, that is, it cannot send data or signals through the cells of the MN or SN at the same time in the same time unit.
  • the time unit may be a subframe or a time slot, or a mini subframe, etc., which is not limited. In this embodiment, a subframe is taken as an example for description.
  • the uplink and downlink time domain allocation is in the form of uplink and downlink time domain allocation corresponding to the radio access technology (RAT) of the SN, or may be in the form of uplink and downlink time domain allocation corresponding to the RAT of the MN , Not limited.
  • the uplink and downlink time domain allocation can be the uplink and downlink time domain assignment (subframe assignment) defined by the LTE protocol TS36.331, and the uplink and downlink time domain allocation is the uplink and downlink time domain allocation form corresponding to LTE.
  • the uplink and downlink time domain allocation may also be TDD-UL-DL-Pattern or TDD-UL-DL-ConfigCommon defined in TS 38.331, indicating the uplink and downlink time division duplex (TDD) configuration.
  • the time domain configuration information includes the second HARQ offset.
  • the SN determines the first HARQ offset according to the time domain configuration information.
  • the SN can also determine the uplink and downlink time domain allocation according to the time domain configuration information.
  • the uplink and downlink time domain allocation may be subframe allocation.
  • the SN uses the time domain configuration information received from the MN as the uplink and downlink time domain allocation.
  • the first HARQ offset may be preset to 0.
  • the SN may combine the time domain configuration information with other information, such as the cell load under the SN, and the uplink resource usage of one or more terminal devices accessed under the SN to determine the first HARQ offset.
  • the SN may adjust the first HARQ offset to 0, so that the uplink and downlink time domain allocation of the SN is the same as the uplink and downlink time domain allocation sent by the MN.
  • the SN determines the first HARQ offset as a value different from the second HARQ offset, and sends it to the MN.
  • the SN may adjust the first HARQ offset to a non-zero constant, so that the uplink and downlink time domain allocation of the SN is the same as the uplink and downlink time domain allocation sent by the MN.
  • the HARQ offset described in this application is used to indicate the HARQ subframe offset, and the HARQ offset refers to the HARQ subframe offset performed by the terminal device on the basis of the uplink subframe corresponding to the uplink and downlink time domain allocation.
  • HARQ offset is used to indicate HARQ subframe offset, which can be used in the design of uplink subframe-related subframe allocation. For details, please refer to the related content in 3GPP TS 36.213 [23].
  • the SN sends the first HARQ offset to the MN.
  • the MN receives the first HARQ offset. Furthermore, the MN can obtain the uplink time domain information that the terminal device can use in the serving cell under the MN according to the first HARQ offset and the time domain configuration information previously sent to the SN.
  • the uplink time domain information includes the TDD ratio of the uplink time unit.
  • the MN may use the first HARQ offset obtained from the SN for uplink and downlink time domain allocation.
  • the SN may not send the first HARQ offset to the MN. Then the MN may use the original time domain configuration information for up and down Time domain allocation.
  • the SN may send the uplink and downlink time domain allocation and the first HARQ offset confirmed for the terminal device to the MN.
  • the MN may obtain the uplink time domain information that the terminal device can use in the serving cell under the MN according to the uplink and downlink time domain allocation and the first HARQ offset.
  • the SN may send a time domain allocation information to the MN, and the time domain configuration information may be the uplink and downlink time domain allocation used by the terminal device in the SN or the MN.
  • the method further includes:
  • the SN determines a time division multiplexing pattern configuration (TDM-patternConfig) for the terminal according to the time domain configuration information received from the MN.
  • TDM-patternConfig time division multiplexing pattern configuration
  • the SN after receiving the time domain configuration information sent by the MN, the SN can determine the time division multiplexing mode configuration provided to the terminal device for the terminal device.
  • the time division multiplexing mode configuration may include uplink and downlink time domain allocation and the first HARQ offset.
  • the uplink and downlink time domain allocation is the uplink and downlink time domain allocation form corresponding to the RAT of the SN.
  • the terminal device will only send uplink information on the subframe after the corresponding uplink subframe in the uplink and downlink time domain allocation is offset by using the first HARQ offset.
  • S750 SN informs the terminal device of the time division multiplexing mode configuration determined by the terminal device.
  • the SN may first send the time division multiplexing mode configuration to the MN, and then the MN transparently transmits it to the terminal device.
  • the terminal may be notified of the time division multiplexing mode configuration in an implicit indication manner.
  • the SN may encapsulate the time division multiplexing mode configuration in a container, and carry the container in the first message sent to the MN, so as to send the time division multiplexing mode configuration to the MN.
  • the MN receives the message containing the container, and then carries the container in the second message sent by the MN for the terminal device, thereby sending the time division multiplexing mode configuration to the terminal.
  • the first message or the second message may be a radio resource control connection reconfiguration (RRC Connection Reconfiguration) message.
  • RRC Connection Reconfiguration radio resource control connection reconfiguration
  • the terminal device may be notified of the time division multiplexing mode configuration in a display indication manner.
  • the SN may directly send the time division multiplexing mode configuration or a message containing the time division multiplexing mode configuration to the MN, and the MN reads the time division multiplexing mode configuration before sending it to the terminal.
  • the SN can directly send the time division multiplexing mode configuration to the terminal device.
  • the SN may allocate the time division multiplexing mode configuration sent to the terminal and the first HARQ offset sent by the SN to the MN and/or the uplink and downlink time domains determined for the terminal device in the same message. Send to MN.
  • the terminal device receives the time division multiplexing mode configuration.
  • the terminal device may send the uplink information on the subframe after the first HARQ offset is performed on the corresponding uplink subframe in the uplink and downlink time domain allocation.
  • FIG. 12 can be implemented separately or combined with any one or more of the embodiments shown in FIG. 7 to FIG. 11, which is not limited.
  • the SN can determine the first HARQ offset for the MN or the terminal in combination with its own operating conditions, thereby improving the accuracy of the MN or the terminal equipment in the uplink and downlink time domain allocation, thereby improving the communication quality.
  • FIG. 13 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • the communication device 800 may include a processing unit 810 and a transceiver unit 820.
  • the communication device 800 may correspond to the auxiliary network device in the above method embodiment, for example, it may be an SN or a chip configured in the SN.
  • the processing unit may be a processor
  • the transceiver unit may be a transceiver.
  • the communication device may further include a storage unit, and the storage unit may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit, so that the communication device executes the foregoing method.
  • the processing unit can be a processor, and the transceiver unit can be an interface circuit, an input/output interface, a pin or a circuit, etc.; the processing unit executes the instructions stored in the storage unit to make The communication device executes the operations performed by the SN in the above-mentioned methods, and the storage unit may be a storage unit in the chip (for example, a register, a cache, etc.), or a storage unit located outside the chip in the communication device (For example, read only memory, random access memory, etc.)
  • each unit in the communication device 800 and other operations and/or functions described above are for implementing the corresponding process of the method in FIG. 7.
  • the processing unit 810 may be used to perform S230 in the method shown in FIG. 7
  • the transceiving unit 820 may be used to perform S220 and S240 in the method shown in FIG. 7.
  • each unit in the communication device 800 and other operations and/or functions described above are for implementing the corresponding process of the method in FIG. 8.
  • the processing unit 810 may be used to perform S330 in the method shown in FIG. 8
  • the transceiving unit 820 may be used to perform S320 and S340 in the method shown in FIG. 8.
  • each unit in the communication device 800 and other operations and/or functions described above are used to implement the corresponding process of the method in FIG. 9.
  • the processing unit 810 may be used to perform S430 in the method shown in FIG. 9, and the transceiving unit 820 may be used to perform S420 and S440 in the method shown in FIG. 9.
  • each unit in the communication device 800 and other operations and/or functions described above are for implementing the corresponding process of the method in FIG. 10.
  • the processing unit 810 may be used to perform S530 in the method shown in FIG. 10
  • the transceiving unit 820 may be used to perform S520 and S540 in the method shown in FIG. 10.
  • each unit in the communication device 800 and other operations and/or functions described above are for implementing the corresponding process of the method in FIG. 11.
  • the processing unit 810 may be used to perform S610 in the method shown in FIG. 11, and the transceiver unit 820 may be used to perform S620 to S650 in the method shown in FIG. 11.
  • each unit in the communication device 800 and other operations and/or functions described above are for implementing the corresponding process of the method in FIG. 12.
  • the processing unit 810 may be used to perform S720 and S740 in the method shown in FIG. 12, and the transceiving unit 820 may be used to perform S710, S730, and S750 in the method shown in FIG.
  • the communication device 800 may correspond to the main network device in the above method embodiment, for example, it may be an MN, or a chip configured in the MN.
  • the processing unit may be a processor
  • the transceiving unit may be a transceiver.
  • the communication device may further include a storage unit, and the storage unit may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit, so that the communication device executes the foregoing method.
  • the processing unit may be a processor, the transceiver unit may be an interface circuit, an input/output interface, a pin or a circuit, etc.; the processing unit executes instructions stored in the storage unit to To cause the communication device to perform the operations performed by the MN in the above method, the storage unit may be a storage unit in the chip (for example, a register, cache, etc.), or a storage unit located outside the chip in the communication device (For example, read only memory, random access memory, etc.).
  • each unit in the communication device 800 and other operations and/or functions described above are for implementing the corresponding process of the method in FIG. 7.
  • the processing unit 810 may be used to perform S210 and S250 in the method shown in FIG. 7
  • the transceiving unit 820 may be used to perform S220 and S240 in the method shown in FIG. 7.
  • each unit in the communication device 800 and other operations and/or functions described above are for implementing the corresponding process of the method in FIG. 8.
  • the processing unit 810 may be used to perform S310 and S350 in the method shown in FIG. 8
  • the transceiving unit 820 may be used to perform S320 and S340 in the method shown in FIG. 8.
  • each unit in the communication device 800 and other operations and/or functions described above are used to implement the corresponding process of the method in FIG. 9.
  • the processing unit 810 may be used to perform S410 and S450 in the method shown in FIG. 9, and the transceiving unit 820 may be used to perform S420 and S440 in the method shown in FIG. 9.
  • each unit in the communication device 800 and other operations and/or functions described above are for implementing the corresponding process of the method in FIG. 10.
  • the processing unit 810 may be used to perform S510 and S550 in the method shown in FIG. 10
  • the transceiving unit 820 may be used to perform S520 and S540 in the method shown in FIG. 10.
  • each unit in the communication device 800 and other operations and/or functions described above are for implementing the corresponding process of the method in FIG. 11.
  • the transceiving unit 820 may be used to perform S620 to S650 in the method shown in FIG. 11.
  • each unit in the communication device 800 and other operations and/or functions described above are for implementing the corresponding process of the method in FIG. 12.
  • the transceiver unit 820 may be used to perform S710 and S730 in the method shown in FIG. 12.
  • the main network equipment in the above-mentioned various device embodiments completely corresponds to the MN or SN in the auxiliary network equipment and method embodiments, and the corresponding units or units execute the corresponding steps, for example, the transceiver unit (transceiver) method is executed in the method embodiment. And/or the steps of receiving, other steps except sending and receiving may be executed by the processing unit (processor).
  • the transceiving unit may include a transmitting unit and/or a receiving unit, the transceiver may include a transmitter and/or a receiver, which respectively implement the transceiving function; there may be one or more processors.
  • the above-mentioned main network device or auxiliary network device may be a chip, and the processing unit may be realized by hardware or software.
  • the processing unit may be a logic circuit, integrated circuit, etc.; when realized by software
  • the processing unit may be a general-purpose processor, which is implemented by reading the software code stored in the storage unit.
  • the storage unit may be integrated in the processor, or may be located outside the processing unit and exist independently.
  • FIG. 14 is a schematic structural diagram of a network device provided by the present application.
  • the network device may be a base station, for example. As shown in FIG. 14, the base station can be applied to the communication system shown in FIG. 1, to perform the functions of the primary network device or the secondary network device in the foregoing method embodiment.
  • the base station 20 may include one or more radio frequency units, such as a remote radio unit (RRU) 201 and one or more baseband units (BBU) (also known as digital units (DU)) ) 202.
  • RRU 201 may be called a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., and it may include at least one antenna 2011 and a radio frequency unit 2012.
  • the RRU 201 part is mainly used for receiving and sending of radio frequency signals and conversion of radio frequency signals and baseband signals, for example, for transmitting the BFR configuration of the foregoing method embodiment.
  • the BBU 202 part is mainly used for baseband processing, control of the base station, and so on.
  • the RRU 201 and the BBU 202 may be physically set together, or may be physically separated, that is, a distributed base station.
  • the BBU 202 is the control center of the base station, and may also be called a processing unit, which is mainly used to complete baseband processing functions, such as channel coding, multiplexing, modulation, and spreading.
  • the BBU (processing unit) 202 may be used to control the base station to execute the operation procedure of the network device in the foregoing method embodiment.
  • the BBU 202 may be composed of one or more single boards, and multiple single boards may jointly support a radio access network (such as an LTE network) with a single access indication, or may respectively support different access standards Wireless access network (such as LTE network, 5G network or other network).
  • the BBU 202 further includes a memory 2021 and a processor 2022, and the memory 2021 is used to store necessary instructions and data.
  • the processor 2022 is used to control the base station to perform necessary actions, for example, used to control the base station to execute the operation procedure of the network device in the foregoing method embodiment.
  • the memory 2021 and the processor 2022 may serve one or more single boards. In other words, the memory and the processor can be set separately on each board. It can also be that multiple boards share the same memory and processor. In addition, necessary circuits can be provided on each board.
  • the network equipment is not limited to the above forms, and may also be in other forms: for example: including BBU and adaptive radio unit (ARU), or BBU and active antenna unit (AAU); or Customer premises equipment (CPE) may also be in other forms, which is not limited by this application.
  • ARU adaptive radio unit
  • AAU BBU and active antenna unit
  • CPE Customer premises equipment
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the aforementioned processor may be a general-purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • Programming logic devices discrete gates or transistor logic devices, discrete hardware components.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed by a combination of hardware and software units in the decoding processor.
  • the software unit may be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable only Read memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • Access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory Take memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer executes the above-described method.
  • the present application also provides a computer-readable medium storing program code, which when the program code runs on a computer, causes the computer to execute the above-described square.
  • the present application also provides a system, which includes the aforementioned one or more terminal devices and one or more network devices.
  • the foregoing embodiments can be implemented in whole or in part by software, hardware, firmware or any other combination.
  • the above-mentioned embodiments may be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more sets of available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a digital versatile disc (DVD)), or a semiconductor medium.
  • the semiconductor medium may be a solid state drive.
  • the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, rather than corresponding to the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • At least one of York or “at least one of York or “at least one of" herein means all or any combination of the listed items, for example, "A, At least one of B and C" can mean: A alone, B alone, C alone, A and B, B and C, and A, B and C.
  • B corresponding to A means that B is associated with A, and B can be determined according to A.
  • determining B according to A does not mean that B is determined only according to A, and B can also be determined according to A and/or other information.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

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

Abstract

本申请提供了一种确定承载类型的方法和通信装置，使得SN可以更合理的确定QoS或者DRB的承载类型，从而提高数据传输效率。具体地，对于对应的SDAP实体建立在SN的QoS流，或者对应的PDCP实体建立在SN的DRB，SN可以根据MN发送的第一消息中是否包括辅助信息，确定该QoS流或者DRB的承载类型。

Description

确定承载类型的方法和通信装置
本申请要求于2019年03月29日提交中国专利局、申请号为201910252564.7、申请名称为“确定承载类型的方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种确定承载类型的方法和通信装置。
背景技术
在双连接(dual connectivity，DC)场景下，可以由主节点(master node，MN)决定所有承载(bearer)的承载类型，并在决定承载的承载类型后告知辅节点(secondary node，SN)。若SN接受MN的决定，则按照MN指示的承载类型生成相应的配置。
为了提高SN的配置的灵活性，针对服务数据适应协议(service data adaptation protocol，SDAP)实体建立在SN的承载，可以由SN自己决定承载类型。但是，如果完全由SN决定终结于SN的承载的承载类型，就可能会出现下述情况：MN负载很高，因此倾向于将整个承载都建立在SN，避免使用主小区组(master cell group，MCG)，而SN可能负载也不低，因此基于自己的算法，将承载类型定为分离(split)承载，即该承载的一部分数据由MCG传输，一部分数据由辅小区组(secondary cell group，SCG)传输。这会导致SN决定的承载类型不能适应MN的运行情况，影响数据传输。
发明内容
本申请提供了一种确定承载类型的方法，使得辅网络设备可以更合理的确定服务质量(quality of service，QoS)或者数据无线承载(data radio bearer，DRB)的承载类型，从而有利于提高数据传输效率。
第一方面，提供了一种确定承载类型的方法，该方法包括：辅网络设备接收主网络设备发送的第一消息；辅网络设备根据第一消息是否包括辅助信息，确定第一QoS流的承载类型。
其中，第一QoS流对应的SDAP实体建立在辅网络设备上，或者说，第一QoS流所对应的承载对应的分组数据汇聚协议(packet data convergence protocol，PDCP)建立在辅网络设备上。所述承载类型包括MCG承载、SCG承载或分离(split)承载。
应理解，第一QoS流的承载类型可以理解为第一QoS流对应的承载的承载类型。
基于该方法，对于对应的SDAP实体建立在辅网络设备上的QoS流，主网络设备可以通过是否在第一消息中包括辅助信息辅助辅网络确定该QoS流的承载类型，相应地，辅网络设备可以根据主网络设备提供的第一消息中是否包括辅助信息，合理地确定该QoS流的承载类型，从而能够尽可能的保证该QoS流的QoS需求，提高数据传输效率。进一 步地，通过为该QoS流设置合理的承载类型，还能够避免由于辅网络设备对QoS流的承载类型决策不合适而造成的辅网络设备和主网络设备之间协商过程较长的问题。
结合第一方面，在第一方面的某些实现方式中，第一QoS流为保证比特速率(guaranteed bit rate，GBR)QoS流，辅助信息为第一GBR QoS参数。其中，第一GBR QoS参数为主网络设备为第一QoS流提供的GBR QoS参数，或者，第一GBR QoS参数为主网络设备能够为第一QoS流提供的GBR QoS参数；以及，所述辅网络设备根据所述第一消息是否包括辅助信息，确定第一服务质量QoS流的承载类型，包括：若第一消息包括辅助信息，辅网络设备确定第一QoS流的承载类型为MCG承载、SCG承载或者分离承载；和/或，若第一消息不包括辅助信息，辅网络设备确定所述第一QoS流的承载类型为SCG承载。
应理解，若主网络设备在第一消息中携带了第一GBR QoS参数，则表示主网络设备允许辅网络设备将第一QoS流的承载类型确定(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。从而，在第一消息中携带了第一GBR QoS参数的情况下，辅网络设备可以考虑将第一QoS流的承载类型确定(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。但是，辅网络设备最终所确定的第一QoS流的承载类型可以自主决定。
基于上述技术方案，主网络设备可以通过是否在第一消息中携带其为该GBR QoS流提供的GBR QoS参数，辅助辅网络设备确定GBR QoS流的承载类型，相应地，辅网络设备可以根据主网络设备提供的第一消息中是否包括主网络设备为该GBR QoS流提供的GBR QoS参数，合理地确定GBR QoS流的承载类型。
本申请中，可选地，GBR QoS参数可以包括上行最大比特速率(maximum bit rate，MBR)、下行最大比特速率、上行GBR和下行GBR中的一种或多种。关于这四个参数的含义具体可以参见现有技术，这里不再赘述。应理解，第一GBR QoS参数可以为主网络设备为第一QoS流提供的上行最大比特速率、下行最大比特速率、上行GBR和下行GBR中的一种或多种。
进一步地，第一消息还可以包括第一QoS流的第二GBR QoS参数。其中，第二GBR QoS参数为主网络设备从核心网设备接收到的第一QoS流的GBR QoS参数。
从而，辅网络设备可以结合第二GBR QoS参数，更为合理地确定第一QoS流的承载类型。
结合第一方面，在第一方面的某些实现方式中，所述第一QoS流为非保证比特速率(non-guaranteed bit rate，non-GBR)QoS流，辅助信息为第一用户设备(user equipment，UE)聚合最大比特速率(aggregated maximum bit rate，AMBR)和第一协议数据单元(protocol data unit，PDU)会话(session)AMBR。其中，所述第一UE AMBR为所述主网络设备为目标UE建立在所述辅网络设备的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE，所述第一PDU会话AMBR为所述主网络设备为目标PDU会话中建立在所述辅网络设备的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
以及，所述辅网络设备根据所述第一消息是否包括辅助信息，确定第一服务质量QoS流的承载类型，包括：
若所述第一消息包括所述第一UE AMBR和所述第一PDU会话AMBR，所述辅网络设备确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
若所述第一消息不包括所述第一UE AMBR和所述第一PDU会话AMBR，所述辅网络设备确定所述第一QoS流的承载类型为所述SCG承载；和/或
若所述第一消息包括所述第一UE AMBR，且不包括所述第一PDU会话AMBR，所述辅网络设备确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
若所述第一消息包括所述第一PDU会话AMBR，且不包括所述第一UE AMBR，所述辅网络设备确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载。
基于上述技术方案，辅网络设备可以根据第一消息是否包括辅助信息，确定第一QoS流的承载类型。
应理解，上述方案的基本思想是，在设计第一消息的格式时，可以在第一消息中预留两个信元的位置，即第一UE AMBR对应的信元和第一PDU会话AMBR对应的信元。但在具体传输时，主网络设备可以不填充这两个信元中的任意一个或两个均不填充，从而实现上述四种情况。
在另外一种可能的实现方式中，第一QoS流是否能配置成涉及MCG空口资源的承载类型，取决于辅网络设备是否收到主网络设备为第一QoS流对应的PDU会话提供的第一PDU会话AMBR。具体的，如果辅网络设备收到了主网络设备为所述第一Qos流对应的PDU会话提供的第一PDU会话AMBR，则辅网络设备可以考虑将第一QoS流的承载类型确定为(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载，即可以是MCG承载、SCG承载或者分离承载；如果没有收到，则辅网络设备确定第一QoS流的承载类型为SCG承载。
需要说明的是，在本申请中，建立在辅网络设备的non-GBR QoS流指对应的SDAP实体建立在辅网络设备的non-GBR QoS流。类似地，建立在主网络设备的non-GBR QoS流指对应的SDAP实体建立在主网络设备的non-GBR QoS流。另外，PDU会话中的non-GBR QoS流表示该PDU会话所对应的non-GBR QoS流。
结合第一方面，在第一方面的某些实现方式中，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR，其中，所述第一UE AMBR为所述主网络设备为目标UE建立在所述辅网络设备的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE；以及，所述辅网络设备根据所述第一消息是否包括辅助信息，确定第一服务质量QoS流的承载类型，包括：若所述第一消息包括所述辅助信息，所述辅网络设备确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或，若所述第一消息不包括所述辅助信息，所述辅网络设备确定所述第一QoS流的承载类型为所述SCG承载。
应理解，若主网络设备在第一消息中携带了第一UE AMBR，则表示主网络设备允许辅网络设备将第一QoS流的承载类型确定(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。从而，在第一消息中携带了第一UE AMBR参数的情况下， 辅网络设备可以考虑将第一QoS流的承载类型确定(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。但是，辅网络设备最终所确定的第一QoS流的承载类型可以自主决定。
基于上述方案，辅网络设备可以根据第一消息是否包括第一UE AMBR，合理地确定第一QoS流的承载类型。
结合第一方面，在第一方面的某些实现方式中，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一协议数据单元PDU会话AMBR，其中，所述第一PDU会话AMBR为所述主网络设备为目标PDU会话中建立在所述辅网络设备的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；以及，所述辅网络设备根据所述第一消息是否包括辅助信息，确定第一服务质量QoS流的承载类型，包括：若所述第一消息包括所述辅助信息，所述辅网络设备确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
若所述第一消息不包括所述辅助信息，所述辅网络设备确定所述第一QoS流的承载类型为所述SCG承载。
应理解，若主网络设备在第一消息中携带了第一PDU会话AMBR，则表示主网络设备允许辅网络设备将第一QoS流的承载类型确定(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。从而，在第一消息中携带了第一PDU会话AMBR的情况下，辅网络设备可以考虑将第一QoS流的承载类型确定(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。但是，辅网络设备最终所确定的第一QoS流的承载类型可以自主决定。
基于上述方案，辅网络设备可以根据第一消息是否包括第一PDU会话AMBR，合理地确定第一QoS流的承载类型。
结合第一方面，在第一方面的某些实现方式中，该方法还可以包括：所述辅网络设备向所述主网络设备发送承载类型指示信息，所述承载类型指示信息用于指示所述辅网络设备确定的所述第一QoS流的承载类型。
可选地，该承载类型指示信息可以显式的信息，即该承载类型指示信息为该第一QoS流的承载类型，或者该承载类型指示信息为该第一QoS流的承载类型是否涉及MCG空口资源的信息。也就是说，辅网络设备明确告诉主网络设备第一QoS流的的承载类型，或者告知主网络设备第一QoS流的承载类型是否涉及MCG空口资源。
此外，承载类型指示信息可以隐式的信息。比如，承载类型指示信息可以是辅网络设备为第一QoS流对应的承载分配的接收上行数据的上行传输网络层(uplink transmission nerwork layer，UL TNL)信息。应理解，若该承载类型指示信息为该上行传输网络层信息，则表示辅网络设备确定的第一QoS流的承载类型为涉及MCG空口资源的承载类型。可选地，该上行传输网络层信息可以包括互联网协议(internet protocol，IP)地址和/或隧道端点标识(tunnel endpoint identifier，TEID)。
还应理解，该承载类型指示信息还可以指示或者包括第一QoS流的标识或者第一QoS流对应的承载的标识。
结合第一方面，在第一方面的某些实现方式中，该方法还可以包括：所述辅网络设备生成修改申请消息，所述修改申请消息用于申请修改所述第一QoS流对应的第一承载的 承载类型；所述辅网络设备向主网络设备发送所述修改申请消息。
基于上述技术方案，辅网络设备可以触发对承载类型的修改。从而，在辅网络设备侧空口状态变化时，辅网络设备可以将承载类型修改为更适合辅网络设备侧空口状态的承载类型。
结合第一方面，在第一方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修改的承载类型的信息，所述承载删除列表包括所述第一承载的标识。
基于上述技术方案，辅网络设备可以通过在承载建立列表和承载删除列表中携带同一个承载标识来实现辅网络设备触发的承载类型修改。
第二方面，提供了一种确定承载类型的方法，其特征在于，包括：主网络设备根据是否在第一消息中包括辅助信息，生成第一消息；所述主网络设备向辅网络设备发送所述第一消息，所述第一消息用于所述辅网络设备确定第一服务质量QoS流的承载类型，其中，所述第一QoS流对应的服务数据适应协议SDAP实体建立在所述辅网络设备上，所述承载类型包括主小区组MCG承载、辅小区组SCG承载或分离承载。
基于该方法，对于对应的SDAP实体建立在辅网络设备上的QoS流，主网络设备可以通过是否在第一消息中包括辅助信息辅助辅网络确定该QoS流的承载类型，相应地，辅网络设备可以根据主网络设备提供的第一消息中是否包括辅助信息，合理地确定该QoS流的承载类型，从而能够尽可能的保证该QoS流的QoS需求，提高数据传输效率。进一步地，通过为该QoS流设置合理的承载类型，还能够避免由于辅网络设备对QoS流的承载类型决策不合适而造成的辅网络设备和主网络设备之间协商过程较长的问题。
结合第二方面，在第二方面的某些实现方式中，所述第一QoS流为保证比特速率GBR QoS流，所述辅助信息为第一GBR QoS参数，所述第一GBR QoS参数为所述主网络设备为所述第一QoS流提供的GBR QoS参数；
以及，若所述第一消息包括所述辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或
若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成所述SCG承载。
结合第二方面，在第二方面的某些实现方式中，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR和第一协议数据单元PDU会话AMBR，其中，所述第一UE AMBR为所述主网络设备为目标UE建立在所述辅网络设备的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE，所述第一PDU会话AMBR为所述主网络设备为目标PDU会话中建立在所述辅网络设备的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
以及，若所述第一消息包括所述第一UE AMBR和所述第一PDU会话AMBR，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；和/或
若所述第一消息不包括所述第一UE AMBR和所述第一PDU会话AMBR，所述第一 消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成为所述SCG承载；和/或
若所述第一消息包括所述第一UE AMBR，且不包括所述第一PDU会话AMBR，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；和/或
若所述第一消息包括所述第一PDU会话AMBR，且不包括所述第一UE AMBR，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；
其中，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载。
结合第二方面，在第二方面的某些实现方式中，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR，其中，所述第一UE AMBR为所述主网络设备为目标UE建立在所述辅网络设备的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE；
以及，若所述第一消息包括所述辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型，其中，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或
若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成为所述SCG承载。
结合第二方面，在第二方面的某些实现方式中，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一协议数据单元PDU会话AMBR，所述第一PDU会话AMBR为所述主网络设备为目标PDU会话中建立在所述辅网络设备的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
以及，若所述第一消息包括所述辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型，其中，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或
若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成为所述SCG承载。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：所述主网络设备接收所述辅网络设备发送的承载类型指示信息，所述承载类型指示信息用于指示所述辅网络设备确定的所述第一QoS流的承载类型；所述主网络设备根据所述承载类型指示信息，确定所述第一QoS流的承载类型。
结合第二方面，在第二方面的某些实现方式中，所述承载类型指示信息为所述辅网络设备为所述第一QoS流对应的承载分配的接收上行数据的上行传输网络层信息。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：所述主网络设备接收所述辅网络设备发送的修改申请消息，所述修改申请消息用于申请修改所述第一QoS流对应的第一承载的承载类型；所述主网络设备向所述辅网络设备发送修改请求消息，所述修改请求消息用于指示所述主网络设备同意修改所述第一承载的承载类型。
结合第二方面，在第二方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修 改的承载类型的信息，所述承载删除列表包括所述第一承载的标识。
关于第二方面提供的各种实现方式的具体细节以及有益效果，可以参照上文中对第一方面的各种实现方式所作的说明，第二方面中不再赘述。
第三方面，提供了一种确定承载类型的方法，该方法包括：辅网络设备接收主网络设备发送的建议信息；辅网络设备根据该建议信息，确定第一QoS流的承载类型。其中，该建议信息用于指示该主网络设备所建议的第一QoS流的承载类型，第一QoS流的含义如前文所述。承载类型包括MCG承载、SCG承载或者分离承载。
具体地，主网络设备可以向辅网络设备建议第一QoS流的承载类型，辅网络设备可以根据主网络设备的建议，确定第一QoS流的承载类型。
因此，根据本申请提供的确定承载类型的方法，辅网络设备可以根据主网络设备建议的承载类型，更合理的确定QoS流的承载类型。
应理解，辅网络设备可以自主的确定第一QoS流的承载类型。即，辅网络设备最终所确定的承载类型可以是主网络设备建议的承载类型，也可以不是主网络设备建议的承载类型。比如，若主网络设备建议的承载类型是分离承载，但是辅网络设备能够满足第一QoS流的QoS需求，则辅网络设备可以将第一QoS流的承载类型确定为SCG承载。
结合第三方面，在第三方面的某些实现方式中，所述方法还可以包括：所述辅网络设备向所述主网络设备发送承载类型指示信息，所述承载类型指示信息用于指示所述辅网络设备确定的所述第一QoS流的承载类型。其中，该承载类型指示信息的含义如前文所述。
结合第三方面，在第三方面的某些实现方式中，该方法还可以包括：所述辅网络设备生成修改申请消息，所述修改申请消息用于申请修改所述第一QoS流对应的第一承载的承载类型；所述辅网络设备向主网络设备发送所述修改申请消息。
基于上述技术方案，辅网络设备可以触发对承载类型的修改。从而，在辅网络设备侧空口状态变化时，辅网络设备可以将承载类型修改为更适合辅网络设备侧空口状态的承载类型。
结合第三方面，在第三方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修改的承载类型的信息，所述承载删除列表包括所述第一承载的标识。
基于上述技术方案，辅网络设备可以通过在承载建立列表和承载删除列表中携带同一个承载标识来实现辅网络设备触发的承载类型修改。
第四方面，提供了一种确定承载类型的方法，该方法包括：主网络设备生成建议信息；主网络设备向辅网络设备发送该建议信息。其中，该建议信息用于指示该主网络设备所建议的第一QoS流的承载类型，第一QoS流的含义如前文所述。承载类型包括MCG承载、SCG承载或者分离承载。
具体地，主网络设备可以向辅网络设备建议第一QoS流的承载类型，辅网络设备可以根据主网络设备的建议，确定第一QoS流的承载类型。
因此，根据本申请提供的确定承载类型的方法，辅网络设备可以根据主网络设备建议的承载类型，更合理的确定QoS流的承载类型。
结合第四方面，在第四方面的某些实现方式中，所述方法还可以包括：所述主网络设备接收所述辅网络设备发送的承载类型指示信息，所述承载类型指示信息用于指示所述辅 网络设备确定的所述第一QoS流的承载类型；所述主网络设备根据所述承载类型指示信息，确定所述第一QoS流的承载类型。
基于上述技术方案，主网络设备可以获知辅网络设备确定的第一QoS流的承载类型。
结合第四方面，在第四方面的某些实现方式中，所述承载类型指示信息为所述辅网络设备为所述第一QoS流对应的承载分配的接收上行数据的上行传输网络层信息。
结合第四方面，在第四方面的某些实现方式中，所述方法还包括：所述主网络设备接收所述辅网络设备发送的修改申请消息，所述修改申请消息用于申请修改所述第一QoS流对应的第一承载的承载类型；所述主网络设备向所述辅网络设备发送修改请求消息，所述修改请求消息用于指示所述主网络设备同意修改所述第一承载的承载类型。
结合第四方面，在第四方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修改的承载类型的信息，所述承载删除列表包括所述第一承载的标识。
关于第四方面提供的各种实现方式的具体细节以及有益效果，可以参照上文中对第三方面的各种实现方式所作的说明，第四方面中不再赘述。
第五方面，提供了一种确定承载类型的方法，该方法包括：辅网络设备接收主网络设备发送的第一消息；辅网络设备根据第一消息是否包括辅助信息，确定第一数据无线承载(data radio bearer，DRB)的承载类型。
其中，第一DRB对应的PDCP实体建立在辅网络设备上。应理解，第一DRB对应的QoS所对应的SDAP实体建立在辅网络设备上。所述承载类型包括MCG承载、SCG承载或分离(split)承载。
根据本申请提供的确定承载类型的方法，对于对应的PDCP实体建立在辅网络设备上的DRB，主网络设备可以通过是否在第一消息中包括辅助信息辅助辅网络设备确定该DRB的承载类型，相应地，辅网络设备可以根据主网络设备提供的第一消息中是否包括辅助信息，合理地确定该DRB的承载类型，从而能够尽可能的保证该DRB的QoS需求，提高数据传输效率。进一步地，通过为该DRB设置合理的承载类型，还能够避免由于辅网络设备对DRB的承载类型决策不合适而造成的辅网络设备和主网络设备之间协商过程较长的问题。
结合第五方面，在第五方面的某些实现方式中，该辅助信息为第一参数，第一参数为主网络设备为第一DRB提供的QoS参数。以及，所述辅网络设备根据所述第一消息是否包括辅助信息，确定第一DRB的承载类型，包括：若第一消息包括辅助信息，辅网络设备确定第一DRB的承载类型为MCG承载、SCG承载或者分离承载；和/或，若第一消息不包括辅助信息，辅网络设备确定所述第一DRB的承载类型为SCG承载。
应理解，若主网络设备在第一消息中携带了第一参数，则表示主网络设备允许辅网络设备将第一DRB的承载类型确定(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。从而，在第一消息中携带了第一参数的情况下，辅网络设备可以考虑将第一DRB的承载类型确定(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。但是，辅网络设备最终所确定的第一DRB的承载类型可以自主决定。
基于上述技术方案，主网络设备可以通过是否在第一消息中携带其为第一DRB提供的QoS参数，辅助辅网络设备确定第一DRB的承载类型，相应地，辅网络设备可以根据 主网络设备提供的第一消息中是否包括主网络设备为该第一DRB提供的QoS参数，合理地确定第一DRB的承载类型。
可选地，该第一参数可以包括上行MBR、下行MBR、上行GBR和下行GBR中的一种或多种。
结合第五方面，在第五方面的某些实现方式中，该方法还可以包括：所述辅网络设备向所述主网络设备发送承载类型指示信息，所述承载类型指示信息用于指示所述辅网络设备确定的所述第一DRB的承载类型。
可选地，该承载类型指示信息可以显式的信息，即该承载类型指示信息为该第一DRB的承载类型，或者该承载类型指示信息为该第一DRB的承载类型是否涉及MCG空口资源的信息。也就是说，辅网络设备明确告诉主网络设备第一DRB的的承载类型，或者告知主网络设备第一DRB的承载类型是否涉及MCG空口资源。
此外，承载类型指示信息可以隐式的信息。比如，承载类型指示信息可以是辅网络设备为第一DRB分配的接收上行数据的上行传输网络层信息。应理解，若该承载类型指示信息为该上行传输网络层信息，则表示辅网络设备确定的第一DRB的承载类型为涉及MCG空口资源的承载类型。可选地，该上行传输网络层信息可以包括IP地址和/或隧道端点标识。
还应理解，该承载类型指示信息还可以指示或者包括第一DRB的标识。
结合第五方面，在第五方面的某些实现方式中，该方法还可以包括：所述辅网络设备生成修改申请消息，所述修改申请消息用于申请修改所述第一DRB的承载类型；所述辅网络设备向主网络设备发送所述修改申请消息。
基于上述技术方案，辅网络设备可以触发对承载类型的修改。从而，在辅网络设备侧空口状态变化时，辅网络设备可以将承载类型修改为更适合辅网络设备侧空口状态的承载类型。
结合第五方面，在第五方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一DRB的标识和指示所述第一DRB需要修改的承载类型的信息，所述承载删除列表包括所述第一承载的标识。
基于上述技术方案，辅网络设备可以通过在承载建立列表和承载删除列表中携带同一个承载标识来实现辅网络设备触发的承载类型修改。
第六方面，提供了一种确定承载类型的方法，其特征在于，包括：主网络设备根据是否在第一消息中包括辅助信息，生成第一消息；所述主网络设备向辅网络设备发送所述第一消息，所述第一消息用于所述辅网络设备确定第一DRB的承载类型，其中，所述第一DRB对应的PDCP实体建立在所述辅网络设备上，所述承载类型包括主小区组MCG承载、辅小区组SCG承载或分离承载。
根据本申请提供的确定承载类型的方法，对于对应的PDCP实体建立在辅网络设备上的DRB，主网络设备可以通过是否在第一消息中包括辅助信息辅助辅网络设备确定该DRB的承载类型，相应地，辅网络设备可以根据主网络设备提供的第一消息中是否包括辅助信息，合理地确定该DRB的承载类型，从而能够尽可能的保证该DRB的QoS需求，提高数据传输效率。进一步地，通过为该DRB设置合理的承载类型，还能够避免由于辅网络设备对DRB的承载类型决策不合适而造成的辅网络设备和主网络设备之间协商过程 较长的问题。
结合第六方面，在第六方面的某些实现方式中，该辅助信息为第一参数，第一参数为主网络设备为第一DRB提供的QoS参数。以及，若第一消息包括辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一DRB的承载类型配置成涉及MCG空口资源的承载类型，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或，若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一DRB的承载类型配置成所述SCG承载。
结合第六方面，在第六方面的某些实现方式中，所述方法还包括：所述主网络设备接收所述辅网络设备发送的承载类型指示信息，所述承载类型指示信息用于指示所述辅网络设备确定的所述第一DRB的承载类型；所述主网络设备根据所述承载类型指示信息，确定所述第一DRB的承载类型。
结合第六方面，在第六方面的某些实现方式中，所述承载类型指示信息为所述辅网络设备为所述第一DRB分配的接收上行数据的上行传输网络层信息。
结合第六方面，在第六方面的某些实现方式中，所述方法还包括：所述主网络设备接收所述辅网络设备发送的修改申请消息，所述修改申请消息用于申请修改所述第一DRB的承载类型；所述主网络设备向所述辅网络设备发送修改请求消息，所述修改请求消息用于指示所述主网络设备同意修改所述第一DRB的承载类型。
结合第六方面，在第六方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一DRB的标识和指示所述第一DRB需要修改的承载类型的信息，所述承载删除列表包括所述第一DRB的标识。
关于第六方面提供的各种实现方式的具体细节以及有益效果，可以参照上文中对第五方面的各种实现方式所作的说明，第六方面中不再赘述。
第七方面，提供了一种确定承载类型的方法，该方法包括：辅网络设备接收主网络设备发送的建议信息；辅网络设备根据该建议信息，确定第一DRB的承载类型。其中，该建议信息用于指示该主网络设备所建议的第一DRB的承载类型，第一DRB的含义如第五方面所述。承载类型包括MCG承载、SCG承载或者分离承载。
具体地，主网络设备可以向辅网络设备建议第一DRB的承载类型，辅网络设备可以根据主网络设备的建议，确定第一DRB的承载类型。
因此，根据本申请提供的确定承载类型的方法，辅网络设备可以根据主网络设备建议的承载类型，更合理的确定DRB的承载类型。
应理解，辅网络设备可以自主的确定第一DRB的承载类型。即，辅网络设备最终所确定的承载类型可以是主网络设备建议的承载类型，也可以不是主网络设备建议的承载类型。比如，若主网络设备建议的承载类型是分离承载，但是辅网络设备能够满足第一DRB的QoS需求，则可以将第一DRB的承载类型确定为SCG承载。
结合第七方面，在第七方面的某些实现方式中，所述方法还可以包括：所述辅网络设备向所述主网络设备发送承载类型指示信息，所述承载类型指示信息用于指示所述辅网络设备确定的所述第一DRB的承载类型。其中，该承载类型指示信息的含义如第五方面所述。
结合第七方面，在第七方面的某些实现方式中，该方法还可以包括：所述辅网络设备 生成修改申请消息，所述修改申请消息用于申请修改所述第一DRB的承载类型；所述辅网络设备向主网络设备发送所述修改申请消息。
基于上述技术方案，辅网络设备可以触发对承载类型的修改。从而，在辅网络设备侧空口状态变化时，辅网络设备可以将承载类型修改为更适合辅网络设备侧空口状态的承载类型。
结合第七方面，在第七方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一DRB的标识和指示所述第一DRB需要修改的承载类型的信息，所述承载删除列表包括所述第一DRB的标识。
基于上述技术方案，辅网络设备可以通过在承载建立列表和承载删除列表中携带同一个承载标识来实现辅网络设备触发的承载类型修改。
第八方面，提供了一种确定承载类型的方法，该方法包括：主网络设备生成建议信息；主网络设备向辅网络设备发送该建议信息。其中，该建议信息用于指示该主网络设备所建议的第一DRB的承载类型，第一DRB的含义如第五方面所述。承载类型包括MCG承载、SCG承载或者分离承载。
具体地，主网络设备可以向辅网络设备建议第一DRB的承载类型，辅网络设备可以根据主网络设备的建议，确定第一DRB的承载类型。
因此，根据本申请提供的确定承载类型的方法，辅网络设备可以根据主网络设建议的承载类型，更合理的确定DRB的承载类型。
结合第八方面，在第八方面的某些实现方式中，所述方法还可以包括：所述主网络设备接收所述辅网络设备发送的承载类型指示信息，所述承载类型指示信息用于指示所述辅网络设备确定的所述第一DRB的承载类型；所述主网络设备根据所述承载类型指示信息，确定所述第一DRB的承载类型。
结合第八方面，在第八方面的某些实现方式中，所述承载类型指示信息为所述辅网络设备为所述第一DRB分配的接收上行数据的上行传输网络层信息。
结合第八方面，在第八方面的某些实现方式中，所述方法还包括：所述主网络设备接收所述辅网络设备发送的修改申请消息，所述修改申请消息用于申请修改所述第一DRB的承载类型；所述主网络设备向所述辅网络设备发送修改请求消息，所述修改请求消息用于指示所述主网络设备同意修改所述第一DRB的承载类型。
结合第八方面，在第八方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一DRB的标识和指示所述第一承载需要修改的承载类型的信息，所述承载删除列表包括所述第一DRB的标识。
关于第八方面提供的各种实现方式的具体细节以及有益效果，可以参照上文中对第七方面的各种实现方式所作的说明，第八方面中不再赘述。
第九方面，提供了一种修改承载类型的方法，包括：辅网络设备生成修改申请(required)消息，所述修改申请消息用于申请修改第一承载的承载类型；所述辅网络设备向主网络设备发送所述修改申请消息。
具体来说，辅网络设备期望修改第一承载的承载类型时，可以通过向主网络设备发送修改申请消息，请求修改第一承载的承载类型。
因此，根据本申请提供的修改承载类型的方法，辅网络设备通过向主网络设备发送修 改申请消息，可以触发承载类型的修改(或者变更)，进一步地可以实现承载类型的修改。
结合第九方面，在第九方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修改的承载类型的指示信息(简称为：指示信息)，所述承载删除列表包括所述第一承载的标识。
基于上述技术方案，辅网络设备可以通过在承载建立列表和承载删除列表中携带同一个承载标识来实现辅网络设备触发的承载类型修改。
可选地，该承载删除列表还可以包括该第一承载当前的承载类型。
应理解，该指示信息指示的需要修改的承载类型为辅网络设备所确定的第一承载的新的承载类型。第一承载当前的承载类型为第一承载原来的承载类型。即，辅网络设备期望将第一承载从原来的承载类型修改为新的承载类型。
所述指示信息，可以是显式的承载类型，例如MCG承载、SCG承载或者分离承载。该指示信息也可以是隐式的信息，该隐式的信息可以指示该第一承载的新的承载类型。比如，该隐式的信息可以是上行传输网络层(uplink transmission nerwork layer，UL TNL)信息，该上行传输网络层信息为辅网络设备为该第一承载分配的用于接收主网络设备发送的上行数据的传输层信息，其中，所述上行数据为主网络设备从终端设备接收的所述第一承载的上行数据。应理解，如果指示信息为该上行传输网络层信息，则表示新的承载类型为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。
该上行传输网络层信息可以包括互联网协议(internet protocol，IP)地址和隧道端点标识(tunnel endpoint identifier，TEID)。应理解，辅网络设备根据该上行传输网络层信息，可以接收主网络设备发送的该第一承载的上行数据。
结合第九方面，在第九方面的某些实现方式中，所述方法还包括：所述辅网络设备接收所述主网络设备发送的修改请求(request)消息，所述修改请求消息用于指示所述主网络设备同意修改所述第一承载的承载类型；所述辅网络设备向所述主网络设备发送修改请求确认(acknowledge)消息，所述修改请求确认消息包括空口无线资源控制(radio resource control，RRC)配置，所述空口RRC配置(记作：空口RRC配置#1)为所述辅网络设备为终端设备生成的空口RRC配置，所述空口RRC配置用于所述终端设备配置所述第一承载；所述辅网络设备接收所述主网络设备发送的修改确认消息(confirm)，所述修改确认消息用于指示所述第一承载的承载类型修改完成。
具体来讲，在主网络设备接受辅网络设备的修改申请后，可以向辅网络设备发送修改请求消息，一方面告知辅网络设备该主网络设备接受了辅网络设备的修改申请，另一方面请求辅网络设备为该第一承载生成相应的空口RRC配置。辅网络设备为该第一承载生成相应的空口RRC配置#1后，通过修改请求确认消息将该配置发送给主网络设备。主网络设备接收到修改请求确认消息后，生成空口RRC配置#2，并将空口RRC配置#1和空口RRC配置#2一起发送给终端设备，完成该第一承载的配置。进一步地，主网络设备通过向辅网络设备发送修改确认消息，告知辅网络设备该主网络设备已经完成了对该第一承载的配置。
本申请中，示例性的，若原来的承载类型是分离承载，新的承载类型为SCG承载，则辅网络设备需要为终端设备生成PDCP恢复的配置(即，空口RRC配置#1的一例)， 指示该第一承载的PDCP实体执行数据恢复；主网络设备需要为终端设备生成MCG无线链路控制(radio link control，RLC)承载删除的配置(即，空口RRC配置#2的一例)。或者，若原来的承载类型为SCG承载，新的承载类型为MCG承载，则辅网络设备需要为终端设备生成SCG RLC承载释放的配置(即，空口RRC配置#1的一例)，主网络设备需要为终端设备生成MCG RLC承载增加的配置(即，空口RRC配置#2的一例)。
结合第九方面，在第九方面的某些实现方式中，所述修改请求消息包括所述上行传输网络层信息。
如果第一承载的新的承载类型为MCG承载或者分离承载，主网络设备还可以在修改请求消息中携带上述上行传输网络层信息。或者，若上述指示信息为上行传输网络层信息，主网络设备也可以不在修改请求消息中携带上行传输网络层信息。
结合第九方面，在第九方面的某些实现方式中，所述修改申请消息还包括空口RRC配置(记作：空口RRC配置#1)，所述空口RRC配置为所述辅网络设备为终端设备生成的RRC配置，所述空口RRC配置用于所述终端设备配置所述第一承载；以及，所述方法还包括：所述辅网络设备接收所述主网络设备发送的修改确认消息，所述修改确认消息用于指示所述第一承载的承载类型修改完成。
具体来讲，主网络设备不能拒绝辅网络设备为第一承载发起的承载修改请求。此时，辅网络设备可以在修改申请消息中携带空口RRC配置#1。主网络设备在接收到辅网络设备发送的空口RRC配置#1后，生成空口RRC配置#2，将空口RRC配置#1和空口RRC配置#2一起发送给终端设备，完成该第一承载的配置。进一步地，主网络设备通过向辅网络设备发送修改确认消息，告知辅网络设备该主网络设备已经完成了对该第一承载的配置。
可选地，如果第一承载原来的承载类型为SCG承载，新的承载类型为MCG承载或者分离承载，主网络设备还可以在修改确认消息中携带上述上行传输网络层信息。或者，若上述指示信息为上行传输网络层信息，主网络设备也可以不在修改确认消息中携带上行传输网络层信息。
第十方面，提供了一种修改承载类型的方法，包括：主网络设备接收辅网络设备发送的修改申请消息，所述修改申请消息用于申请修改第一承载的承载类型；所述主网络设备向辅网络设备发送修改请求消息。该修改请求消息用于指示主网络设备同意所述辅网络设备的修改请求。
具体来说，辅网络设备期望修改第一承载的承载类型时，可以通过向主网络设备发送修改申请消息，若主网络设备接受辅网络设备修改第一承载的承载类型的请求，则向辅网络设备发送修改请求消息。进而，辅网络设备可以实现对第一承载的承载类型的修改。
因此，根据本申请提供的修改承载类型的方法，辅网络设备通过向主网络设备发送修改申请消息，可以触发承载类型的修改(或者变更)，进一步地可以实现承载类型的修改。
结合第十方面，在第十方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修改的承载类型的指示信息(简称为：指示信息)，所述承载删除列表包括所述第一承载的标识。
基于上述技术方案，辅网络设备可以通过在承载建立列表和承载删除列表中携带同一 个承载标识来实现辅网络设备触发的承载类型修改。
可选地，该承载删除列表还可以包括该第一承载当前的承载类型。
应理解，该指示信息指示的需要修改的承载类型为辅网络设备所确定的第一承载的新的承载类型。第一承载当前的承载类型为第一承载原来的承载类型。即，辅网络设备期望将第一承载从原来的承载类型修改为新的承载类型。
所述指示信息，可以是显式的承载类型，例如MCG承载、SCG承载或者分离承载。该指示信息也可以是隐式的信息，该隐式的信息可以指示该第一承载的新的承载类型。比如，该隐式的信息可以是上行传输网络层(uplink transmission nerwork layer，UL TNL)信息，该上行传输网络层信息为辅网络设备为该第一承载分配的用于接收主网络设备发送的上行数据的传输层信息，其中，所述上行数据为主网络设备从终端设备接收的所述第一承载的上行数据。应理解，如果指示信息为该上行传输网络层信息，则表示新的承载类型为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。
该上行传输网络层信息可以包括互联网协议(internet protocol，IP)地址和隧道端点标识(tunnel endpoint identifier，TEID)，辅网络设备根据该上行传输网络层信息可以接收主网络设备发送的该第一承载的上行数据。
结合第十方面，在第十方面的某些实现方式中，所述修改请求消息包括所述上行传输网络层信息。
如果第一承载的新的承载类型为MCG承载或者分离承载，主网络设备还可以在修改请求消息中携带上述上行传输网络层信息。或者，若上述指示信息为上行传输网络层信息，主网络设备也可以不在修改请求消息中携带上行传输网络层信息。
结合第十方面，在第十方面的某些实现方式中，所述方法还可以包括：所述主网络设备接收所述辅网络设备发送的修改请求确认消息，所述修改请求确认消息包括空口RRC配置，所述空口RRC配置为所述辅网络设备为终端设备生成的RRC配置，所述空口RRC配置用于所述终端设备配置所述第一承载；所述主网络设备向所述辅网络设备发送修改确认消息，所述修改确认消息用于指示所述第一承载的承载类型修改完成。
基于上述技术方案，可以实现对第一承载的承载类型的修改。
第十一方面，提供了一种修改承载类型的方法，包括：主网络设备接收辅网络设备发送的修改申请消息，所述修改申请消息用于申请修改第一承载的承载类型，所述修改申请消息包括空口RRC配置(记作：空口RRC配置#1)，所述空口RRC配置为所述辅网络设备为终端设备生成的RRC配置，所述空口RRC配置用于所述终端设备配置所述第一承载；所述主网络设备向辅网络设备发送修改确认消息。该修改确认消息用于指示所述第一承载的承载类型修改完成。
具体来讲，主网络设备不能拒绝辅网络设备为第一承载发起的承载修改请求。此时，辅网络设备可以在修改申请消息中携带空口RRC配置#1。主网络设备在接收到辅网络设备发送的空口RRC配置#1后，生成空口RRC配置#2，将空口RRC配置#1和空口RRC配置#2一起发送给终端设备，完成该第一承载的配置。进一步地，主网络设备通过向辅网络设备发送修改确认消息，告知辅网络设备该主网络设备已经完成了对该第一承载的配置。
因此，根据本申请提供的修改承载类型的方法，辅网络设备通过向主网络设备发送修 改申请消息，可以触发承载类型的修改(或者变更)，进一步地可以实现承载类型的修改。
结合第十一方面，在第十一方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修改的承载类型的指示信息(简称为：指示信息)，所述承载删除列表包括所述第一承载的标识。
基于上述技术方案，辅网络设备可以通过在承载建立列表和承载删除列表中携带同一个承载标识来实现辅网络设备触发的承载类型修改。
可选地，该承载删除列表还可以包括该第一承载当前的承载类型。
应理解，该指示信息指示的需要修改的承载类型为辅网络设备所确定的第一承载的新的承载类型。第一承载当前的承载类型为第一承载原来的承载类型。即，辅网络设备期望将第一承载从原来的承载类型修改为新的承载类型。
所述指示信息，可以是显式的承载类型，例如MCG承载、SCG承载或者分离承载。该指示信息也可以是隐式的信息，该隐式的信息可以指示该第一承载的新的承载类型。比如，该隐式的信息可以是上行传输网络层(uplink transmission nerwork layer，UL TNL)信息，该上行传输网络层信息为辅网络设备为该第一承载分配的用于接收主网络设备发送的上行数据的传输层信息，其中，所述上行数据为主网络设备从终端设备接收的所述第一承载的上行数据。应理解，如果指示信息为该上行传输网络层信息，则表示新的承载类型为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。
该上行传输网络层信息可以包括互联网协议(internet protocol，IP)地址和隧道端点标识(tunnel endpoint identifier，TEID)，辅网络设备根据该上行传输网络层信息可以接收主网络设备发送的该第一承载的上行数据。
可选地，如果第一承载原来的承载类型为SCG承载，新的承载类型为MCG承载或者分离承载，主网络设备还可以在修改确认消息中携带上述上行传输网络层信息。或者，若上述指示信息为上行传输网络层信息，主网络设备也可以不在修改确认消息中携带上行传输网络层信息。
第十二方面，提供了一种通信方法，该方法包括：辅网络设备从主网络设备接收时域配置信息；辅网络设备根据所述时域配置信息确定混合自动重传请求(hybrid automatic repeat request，HARQ)偏移(offset)；所述辅网络设备向主网络设备发送所述第一HARQ offset。
采用本申请实施例提供的通信方法，SN可以结合自身的运行情况为MN或者终端确定第一HARQ offset，从而能够提升MN或者终端设备在进行上下行时域分配的准确性，从而提升通信质量。
结合第十二方面，在第十二方面的某些实现方式中，所述方法还包括：所述辅网络设备根据所述时域配置信息确定时分复用模式配置；所述辅网络设备将所述时分复用模式配置通知给终端设备，所述时分复用模式配置包含所述第一HARQ offset。
可选地，辅网络设备可以直接将所述时分复用模式配置发送给终端设备。
可选地，辅网络设备可以通过主网络设备向所述终端设备转发所述时分复用模式配置。
可选地，所述第一HARQ offset为0。
可选地，所述辅网络设备根据所述时域配置信息确定第一HARQ offset，包括：所述辅网络设备根据所述时域配置信息，将所述第一HARQ offset调整为0。
可选地，所述时域配置信息包括第二HARQ offset，所述辅网络设备根据所述时域配置信息确定所述第一HARQ offset，包括：所述辅网络设备确定所述第一HARQ offset与所述第二HARQ offset不同。
第十三方面，提供了一种通信方法，该方法包括：主网络设备向辅网络设备发送时域配置信息，所述时域配置信息用于辅网络设备确定第一HARQ offset；所述主网络设备从所述辅网络设备接收所述第一HARQ offset。
结合第十三方面，在第十三方面的某些实现方式中，所述方法还包括：主网络设备根据所述第一HARQ offset调整上下行子帧配比。
结合第十三方面，在第十三方面的某些实现方式中，所述方法还包括：主网络设备从辅网络设备接收辅网络设备确定的时分复用模式配置，所述时分复用模式配置中包含所述第一HARQ offset；主网络设备向终端设备发送所述时分复用模式配置。其中，辅网络设备可以将所述时分复用模式配置通过RRC container的方式向主网络设备发送，主网络设备将包含该时分复用模式配置的RRC container发送给终端设备。
第十四方面，提供了一种通信装置，包括收发单元，用于接收主网络设备发送的第一消息；处理单元，用于根据所述第一消息是否包括辅助信息，确定第一服务质量QoS流的承载类型，其中，所述第一QoS流对应的服务数据适应协议SDAP实体建立在所述通信装置上，所述承载类型包括主小区组MCG承载、辅小区组SCG承载或分离承载。
结合第十四方面，在第十四方面的某些实现方式中，所述第一QoS流为保证比特速率GBR QoS流，所述辅助信息为第一GBR QoS参数，所述第一GBR QoS参数为所述主网络设备为所述第一QoS流提供的GBR QoS参数；
以及，所述处理单元具体用于：若所述第一消息包括所述辅助信息，确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
若所述第一消息不包括所述辅助信息，确定所述第一QoS流的承载类型为所述SCG承载。
结合第十四方面，在第十四方面的某些实现方式中，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR和第一协议数据单元PDU会话AMBR，其中，所述第一UE AMBR为所述主网络设备为目标UE建立在所述通信装置的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE，所述第一PDU会话AMBR为所述主网络设备为目标PDU会话中建立在所述通信装置的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
以及，所述处理单元具体用于：
若所述第一消息包括所述第一UE AMBR和所述第一PDU会话AMBR，确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
若所述第一消息不包括所述第一UE AMBR和所述第一PDU会话AMBR，确定所述第一QoS流的承载类型为所述SCG承载；和/或
若所述第一消息包括所述第一UE AMBR，且不包括所述第一PDU会话AMBR，确 定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
若所述第一消息包括所述第一PDU会话AMBR，且不包括所述第一UE AMBR，确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载。
结合第十四方面，在第十四方面的某些实现方式中，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR，其中，所述第一UE AMBR为所述主网络设备为目标UE建立在所述通信装置的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE；
以及，所述处理单元具体用于：
若所述第一消息包括所述辅助信息，确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
若所述第一消息不包括所述辅助信息，确定所述第一QoS流的承载类型为所述SCG承载。
结合第十四方面，在第十四方面的某些实现方式中，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一协议数据单元PDU会话AMBR，其中，所述第一PDU会话AMBR为所述主网络设备为目标PDU会话中建立在所述通信装置的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
以及，所述处理单元具体用于：
若所述第一消息包括所述辅助信息，确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
若所述第一消息不包括所述辅助信息，确定所述第一QoS流的承载类型为所述SCG承载。
结合第十四方面，在第十四方面的某些实现方式中，所述收发单元还用于：向所述主网络设备发送承载类型指示信息，所述承载类型指示信息用于指示所述通信装置确定的所述第一QoS流的承载类型。
结合第十四方面，在第十四方面的某些实现方式中，所述承载类型指示信息为所述通信装置为所述第一QoS流对应的承载分配的接收上行数据的上行传输网络层信息。
结合第十四方面，在第十四方面的某些实现方式中，所述处理单元还用于，生成修改申请消息，所述修改申请消息用于申请修改所述第一QoS流对应的第一承载的承载类型；所述收发单元还用于：向主网络设备发送所述修改申请消息。
结合第十四方面，在第十四方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修改的承载类型的信息，所述承载删除列表包括所述第一承载的标识。
第十五方面，提供了一种通信装置，包括处理单元，用于根据是否在第一消息中包括辅助信息，生成第一消息；收发单元，用于向辅网络设备发送所述第一消息，所述第一消息用于所述辅网络设备确定第一服务质量QoS流的承载类型，其中，所述第一QoS流对应的服务数据适应协议SDAP实体建立在所述辅网络设备上，所述承载类型包括主小区组MCG承载、辅小区组SCG承载或分离承载。
结合第十五方面，在第十五方面的某些实现方式中，所述第一QoS流为保证比特速率GBR QoS流，所述辅助信息为第一GBR QoS参数，所述第一GBR QoS参数为所述通信装置为所述第一QoS流提供的GBR QoS参数；
以及，若所述第一消息包括所述辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或
若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成所述SCG承载。
结合第十五方面，在第十五方面的某些实现方式中，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR和第一协议数据单元PDU会话AMBR，其中，所述第一UE AMBR为所述通信装置为目标UE建立在所述辅网络设备的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE，所述第一PDU会话AMBR为所述通信装置为目标PDU会话中建立在所述辅网络设备的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
以及，若所述第一消息包括所述第一UE AMBR和所述第一PDU会话AMBR，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；和/或
若所述第一消息不包括所述第一UE AMBR和所述第一PDU会话AMBR，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成为所述SCG承载；和/或
若所述第一消息包括所述第一UE AMBR，且不包括所述第一PDU会话AMBR，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；和/或
若所述第一消息包括所述第一PDU会话AMBR，且不包括所述第一UE AMBR，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；
其中，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载。
结合第十五方面，在第十五方面的某些实现方式中，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR，其中，所述第一UE AMBR为所述通信装置为目标UE建立在所述辅网络设备的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE；
以及，若所述第一消息包括所述辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型，其中，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或
若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成为所述SCG承载。
结合第十五方面，在第十五方面的某些实现方式中，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一协议数据单元PDU会话AMBR，所述第一 PDU会话AMBR为所述通信装置为目标PDU会话中建立在所述辅网络设备的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
以及，若所述第一消息包括所述辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型，其中，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或
若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成为所述SCG承载。
结合第十五方面，在第十五方面的某些实现方式中，所述收发单元还用于：接收所述辅网络设备发送的承载类型指示信息，所述承载类型指示信息用于指示所述辅网络设备确定的所述第一QoS流的承载类型；所述处理单元还用于，确定所述第一QoS流的承载类型。
结合第十五方面，在第十五方面的某些实现方式中，所述承载类型指示信息为所述辅网络设备为所述第一QoS流对应的承载分配的接收上行数据的上行传输网络层信息。
结合第十五方面，在第十五方面的某些实现方式中，所述收发单元还用于：接收所述辅网络设备发送的修改申请消息，所述修改申请消息用于申请修改所述第一QoS流对应的第一承载的承载类型；向所述辅网络设备发送修改请求消息，所述修改请求消息用于指示所述通信装置同意修改所述第一承载的承载类型。
结合第十五方面，在第十五方面的某些实现方式中，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修改的承载类型的信息，所述承载删除列表包括所述第一承载的标识。
第十六方面，提供了一种通信装置，包括用于执行第三方面至第十三方面以第三方面至第十三方面中任一种可能实现方式中的方法的各个单元或单元。
第十七方面，提供了一种通信装置，包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第一方面至第十三方面以第一方面至第十三方面中任一种可能实现方式中的方法。可选地，该通信装置还包括存储器。可选地，该通信装置还包括接口电路，处理器与接口电路耦合。
可选地，该接口电路可以是收发器，或，输入/输出接口。
可选地，该收发器可以为收发电路。可选地，该输入/输出接口可以为输入/输出电路。
第十八方面，提供了一种处理器，包括：输入电路、输出电路和处理电路。该处理电路用于通过该输入电路接收信号，并通过该输出电路发射信号，使得该处理器执行第一方面至第十三方面以及第一方面至第十三方面任一种可能实现方式中的方法。
在具体实现过程中，上述处理器可以为芯片，输入电路可以为输入管脚，输出电路可以为输出管脚，处理电路可以为晶体管、门电路、触发器和各种逻辑电路等。输入电路所接收的输入的信号可以是由例如但不限于接收器接收并输入的，输出电路所输出的信号可以是例如但不限于输出给发射器并由发射器发射的，且输入电路和输出电路可以是同一电路，该电路在不同的时刻分别用作输入电路和输出电路。本申请实施例对处理器及各种电路的具体实现方式不做限定。
第十九方面，提供了一种处理装置，包括处理器和存储器。该处理器用于读取存储器中存储的指令，并可通过接收器接收信号，通过发射器发射信号，以执行第一方面至第十 三方面以第一方面至第十三方面任一种可能实现方式中的方法。
可选地，该处理器为一个或多个，该存储器为一个或多个。
可选地，该存储器可以与该处理器集成在一起，或者该存储器与处理器分离设置。
在具体实现过程中，存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(read only memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
应理解，相关的数据交互过程例如发送第一消息可以为从处理器输出第一消息的过程，接收信息可以为处理器接收信息的过程。具体地，处理输出的数据可以输出给发射器，处理器接收的输入数据可以来自接收器。其中，发射器和接收器可以统称为收发器。
上述第十九方面中的处理装置可以是一个芯片，该处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，该存储器可以集成在处理器中，可以位于该处理器之外，独立存在。
第二十方面，提供了一种计算机程序产品，该计算机程序产品包括：计算机程序(也可以称为代码，或指令)，当该计算机程序被运行时，使得计算机执行上述第一方面至第十三方面以第一方面至第十三方面中任一种可能实现方式中的方法。
第二十一方面，提供了一种计算机可读介质，该计算机可读介质存储有计算机程序(也可以称为代码，或指令)当其在计算机上运行时，使得计算机执行上述第一方面至第十三方面以第一方面至第十三方面中任一种可能实现方式中的方法。
第二十二方面，提供了一种通信系统，包括前述的主网络设备和辅网络设备，
可选地，所述通信系统还包括核心网设备，用于向所述主网络设备发送QoS参数。
可选地，所述通信系统还包括终端设备。
附图说明
图1是适用于本申请的一个通信系统的示意图；
图2至图5是适用于本申请的DC架构的示意图；
图6是DC架构下支持的多种承载类型的示意图；
图7本申请提供的一种确定承载类型的方法的示意性流程图；
图8本申请提供的另一种确定承载类型的方法的示意性流程图；
图9本申请提供的又一种确定承载类型的方法的示意性流程图；
图10本申请提供的再一种确定承载类型的方法的示意性流程图；
图11本申请提供的修改承载类型的方法的示意性流程图；
图12是本申请提供的通信方法的示意性流程图；
图13本申请提供的一种通信装置的示意性结构示意图；
图14是本申请提供的一种网络设备的结构示意图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通信(global system for mobile communications，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、例如新无线(new radio，NR)系统等第五代(5th generation，5G)系统或新无线(new radio，NR)其他新型无线通信系统等。
本申请实施例中的终端设备可以指用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
本申请实施例中的网络设备(主网络设备或辅网络设备)可以是用于与终端设备通信的设备，该网络设备可以是全球移动通信(global system for mobile communications，GSM)系统或码分多址(code division multiple access，CDMA)中的基站(base transceiver station，BTS)，也可以是宽带码分多址(wideband code division multiple access，WCDMA)系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(evolved NodeB，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备未来演进的PLMN网络中的网络设备等，本申请实施例并不限定。5G网络中的网络设备例如可以是gNB或者传输点(trasmission point，TRP)等。或者本申请实施例中的网络设备可以由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将基站的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。)或者未来演进的PLMN网络中的网络设备等，本申请实施例并不限定。
在本申请实施例中，终端设备或网络设备(主网络设备或辅网络设备)包括硬件层、运行在硬件层之上的操作系统层，以及运行在操作系统层上的应用层。该硬件层包括中央处理器(central processing unit，CPU)、内存管理单元(memory management unit，MMU)和内存(也称为主存)等硬件。该操作系统可以是任意一种或多种通过进程(process)实现业务处理的计算机操作系统，例如，Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。该应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。并且，本申请实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序， 以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端设备或网络设备，或者，是终端设备或网络设备中能够调用程序并执行程序的功能单元。
另外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于:磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，无线信道和能够存储、包含和/或承载指令和/或数据的各种其它介质。
图1是适用于本申请的一个通信系统的示意图。如图1所示，该通信系统100可以包括至少两个网络设备，例如网络设备110和网络设备120，该通信系统100还可以包括至少一个终端设备，例如终端设备130。此外，通信系统100还可以包括至少一个核心网设备，例如核心网设备140。应理解，图1只是示意图，该通信系统中还可以包括其它网络设备，如还可以包括无线中继设备和无线回传设备等。此外，本申请的实施例对该移动通信系统中包括的网络设备和终端设备的数量不做限定。
在图1中，终端设备130可以通过空中接口连接网络设备110和网络设备120，网络设备110和网络设备120之间可以通过有线或者无线的方式连接，网络设备110和网络设备120可以通过有线的方式连接至核心网设备140。核心网设备140可以是4G核心网设备，也可以是5G核心网设备。网络设备110可以是LTE基站，也可以是NR基站；网络设备120可以是LTE基站，也可以是NR基站。终端设备130可以通过采用DC技术，与网络设备110和120进行通信。网络设备110和120中其中一个是MN，另一个是SN。
其中，DC存在多种组合：
(1)核心网为分组核心网EPC(evolved packet core，EPC)，LTE基站做MN，NR基站做SN。参见图2，此时LTE基站和NR基站之间可以通过X2接口连接，至少有控制面连接，可以还有用户面连接；LTE基站和EPC之间可以通过S1接口连接，至少有控制面连接，可以还有用户面连接；NR基站和EPC之间可以通过S1-U接口连接，即只可以有用户面连接。此时LTE基站可以通过至少一个LTE小区为UE提供空口资源，此时所述至少一个LTE小区称为MCG。相应的，NR基站也可以通过至少一个NR小区为UE提供空口资源，此时所述至少一个NR小区称为SCG。
(2)核心网为5G核心网(5G core，5GC)，LTE基站做MN，NR基站做SN。参见图3，此时LTE基站和NR基站之间可以通过Xn接口连接，至少有控制面连接，可以还有用户面连接；LTE基站和5GC之间可以通过NG接口连接，至少有控制面连接，可以还有用户面连接；NR基站和5GC之间可以通过NG-U接口连接，即只可以有用户面连接。此时LTE基站可以通过至少一个LTE小区为UE提供空口资源，此时所述至少一个LTE小区称为MCG。相应的，NR基站也可以通过至少一个NR小区为UE提供空口资源，此时所述至少一个NR小区称为SCG。
(3)核心网为5GC时，NR基站做MN，LTE基站做SN。参见图4，此时NR基站 和LTE基站之间可以通过Xn接口连接，至少有控制面连接，可以还有用户面连接；NR基站和5GC之间可以通过NG接口连接，至少有控制面连接，可以还有用户面连接；LTE站和5GC之间存在NG-U接口，即只可以有用户面连接。此时NR基站可以通过至少一个NR小区为UE提供空口资源，此时所述至少一个NR小区称为MCG。相应的，LTE基站也可以通过至少一个LTE小区为UE提供空口资源，此时所述至少一个LTE小区称为SCG。
(4)核心网为5GC时，MN和SN都是NR基站。参见图5，NR主基站和NR辅基站之间可以通过Xn接口连接，至少有控制面连接，可以还有用户面连接；NR主基站和5GC之间存在NG接口，至少有控制面连接，可以还有用户面连接；NR辅基站和5GC之间存在NG-U接口，即只可以有用户面连接。此时NR主基站可以通过至少一个NR小区为UE提供空口资源，此时所述至少一个NR小区称为MCG。相应的，NR辅基站也可以通过至少一个NR小区为UE提供空口资源，此时所述至少一个NR小区称为SCG。
应理解，图2至图5中，均以LTE基站为eNB，NR基站为gNB为例进行说明，但这并不应对本申请构成任何限定。
如图6所示，DC架构下支持多种承载类型，包括：
MN terminated MCG bearer，即，终结在MN的MCG承载；
MN terminated SCG bearer，即，终结在MN的SCG承载；
MN terminated split bearer，即，终结在MN的分离承载；
SN terminated MCG bearer，即，终结在SN的MCG承载；
SN terminated SCG bearer，即，终结在SN的SCG承载；
SN terminated split bearer，即，终结在SN的分离承载。
其中，MCG承载是指只涉及MCG空口资源的承载，SCG承载是指只涉及SCG空口资源的承载，分离承载是指MCG空口资源和SCG空口资源都涉及的承载。MN终结或者终结在MN是指分组数据汇聚协议(packet data convergence protocol，PDCP)实体在MN，SN终结或者终结在SN是指PDCP实体在SN。
应理解，图6中，MN RLC表示MN侧的无线链路控制(radio link control，RLC)实体。相应地，SN RLC表示SN侧的RLC实体。MN MAC表示MN侧的媒体接入控制(media access control，MAC)实体。相应地，SN MAC表示SN侧的MAC实体。
当前技术中，可以由MN决定所有承载的承载类型，并在决定承载的承载类型后告知SN。若SN接受该承载类型，则按照MN指示的承载类型生成相应的配置。
提高SN的配置的灵活性，针对SDAP实体建立在SN的承载，可以由SN自己决定承载类型。但是，如果完全由SN决定终结于SN的承载的承载类型，可能会导致SN决定的承载类型不能适应MN的运行情况，影响数据传输。因此，需要SN更合理的设置SDAP实体建立在SN的承载的承载类型。
有鉴于此，本申请提供了多种确定承载类型的方法。其中，在一种方法中，SN可以根据MN是否提供了辅助信息，更合理地确定QoS流的承载类型或者DRB的承载类型。在另一种方法中，SN可以根据MN提供的建议信息，更合理地确定QoS流的承载类型或者DRB的承载类型。其中，该建议信息可以是MN所建议的SDAP实体在SN的QoS流或者DRB的承载类型。
应理解，本申请所描述的QoS流的承载类型实际是指，该QoS流对应的承载的承载类型，或者说该QoS流所属的承载的承载类型。
应理解，本申请提供的方法可以应用但不限定于图2至图5所示的DC架构。下面对本申请的方法进行说明。
还应理解，为便于理解，下文主要以MN为主网络设备，SN为辅网络设备为例，对本申请的方法进行说明。需要说明的是，实际上，MN所执行的操作还可以由MN中的芯片执行，类似地，SN所执行的操作还可以由SN中的芯片执行。
本申请提供的第一种方法主要包括：主网络设备根据是否在第一消息中包括辅助信息，生成第一消息；该主网络设备向该辅网络设备发送该第一消息。相应地，该辅网络设备接收主网络设备发送的第一消息，并且根据该第一消息是否包括该辅助信息，确定QoS流的承载类型。其中，该QoS流对应的SDAP实体建立在该辅网络设备上。
基于该方法，对于对应的SDAP实体建立在辅网络设备上的QoS流，主网络设备可以通过是否在第一消息中包括辅助信息辅助辅网络确定该QoS流的承载类型，相应地，辅网络设备可以根据主网络设备提供的第一消息中是否包括辅助信息，合理地确定该QoS流的承载类型。从而，可以实现辅网络设备合理设置QoS流的承载类型的目的。并且，还能够避免由于辅网络设备对QoS流的承载类型决策不合适而造成的辅网络设备和主网络设备之间协商过程较长的问题。以下，结合图7，对该方法进行详细说明。
图7示出了本申请提供的确定承载类型的方法200的示例性流程图。该方法200主要包括S210至S230。以下对各步骤进行说明。
S210，MN根据是否在第一消息中包括辅助信息，生成第一消息。
第一消息用于SN确定第一QoS流的承载类型。或者说，第一消息是否包括辅助信息的结果，用于SN确定第一QoS流的承载类型。即，SN可以根据第一消息是否包括辅助信息，确定第一QoS流的承载类型。第一QoS流可以是对应的SDAP实体建立在该SN上的任一QoS流。应理解，第一QoS流对应的SDAP实体建立在SN，也可以理解为，第一QoS流对应的承载所对应的PDCP实体建立在SN。
其中，本文所描述的承载类型包括MCG承载、SCG承载或者分离承载。MCG承载和分离承载为涉及MCG空口资源的承载。或者说，涉及MCG空口资源的承载包括MCG承载或分离承载。
应理解，由于第一QoS流对应的SDAP实体建立在该SN上，因此第一QoS流的承载类型实际上是终结在SN的SCG承载、终结在SN的MCG承载或者终结在SN的分离承载。
示例性的，MN如果能够为该第一QoS流提供空口资源，则MN可以在第一消息中包括辅助信息。再如，若MN不能够为该第一QoS流提供空口资源，则MN可以不在第一消息中包括辅助信息。其中，空口资源用于提供第一QoS流的传输比特速率。
S220，MN向SN发送第一消息。相应地，SN接收该第一消息。
S230，SN根据第一消息是否包括辅助信息，确定第一QoS流的承载类型。
根据本申请提供的确定承载类型的方法，对于对应的SDAP实体建立在SN上的QoS流，MN可以通过是否在第一消息中包括辅助信息辅助SN确定该QoS流的承载类型，相应地，SN可以根据MN提供的第一消息中是否包括辅助信息，合理地确定该QoS流的承 载类型。从而，可以实现SN合理设置QoS流的承载类型的目的。并且，还能够避免由于辅网络设备对QoS流的承载类型决策不合适而造成的MN和SN之间协商过程较长的问题。
下面对本申请可能的实现方式进行说明。其中，下文中的方式一针对GBR QoS流，方式二至方式四针对non-GBR QoS流。
方式一
第一QoS流为GBR QoS流，辅助信息为第一GBR QoS参数。其中，第一GBR QoS参数为MN为第一QoS流提供的GBR QoS参数，或者说，第一GBR QoS参数为MN能够为第一QoS流提供的GBR QoS参数。
在此场景下，若第一消息包括辅助信息，则第一消息可以指示SN被允许将第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；或者说，若第一消息包括辅助信息，SN可以考虑将第一QoS流配置成涉及MCG空口资源的承载类型。和/或，若第一消息不包括辅助信息，则第一消息可以指示SN将第一QoS流的承载类型确定为SCG承载；或者说，若第一新消息不包括辅助信息，则SN可以将第一QoS流配置成SCG承载，或者，SN可以确定第一QoS流的承载类型为SCG承载。
相应地，S230具体包括：若第一消息包括辅助信息，SN确定第一QoS流的承载类型为MCG承载、SCG承载或者分离承载；若第一消息不包括辅助信息，SN确定第一QoS流的承载类型为SCG承载。
具体来讲，若MN在第一消息中携带了第一GBR QoS参数，则表示MN能够为第一QoS流提供GBR QoS参数，或者说MN能够为第一QoS流分配MCG空口资源，从而SN可以考虑将第一QoS流的承载类型确定(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。也就是说，SN可以或者有机会将第一QoS流的承载类型确定为MCG承载或者分离承载。但是，SN最终所确定的第一QoS流的承载类型可以自主决定，比如SN最终所确定的第一QoS流的承载类型也可能不是MCG承载或者分离承载，即可以是SCG承载。比如，若SN能够为第一QoS流提供该第一QoS流所需的GBR QoS参数，则SN可以确定第一QoS流的承载类型为SCG承载。应理解，第一QoS流所需的GBR QoS参数与下文中描述的第二GBR QoS参数的含义相同。
与此相对地，若MN在第一消息中没有携带第一GBR QoS参数，则表示MN不能够为第一QoS流提供GBR QoS参数，或者说MN不能够为第一QoS流分配涉及MCG空口资源，从而SN可以将第一QoS流的承载类型确定为SCG承载。
基于上述技术方案，MN可以通过是否在第一消息中携带其为该GBR QoS流提供的GBR QoS参数，辅助SN确定GBR QoS流的承载类型，相应地，SN可以根据MN提供的第一消息中是否包括MN为该GBR QoS流提供的GBR QoS参数，合理地确定GBR QoS流的承载类型。
本申请中，GBR QoS参数可以包括上行最大比特速率、下行最大比特速率、上行GBR和下行GBR中的一种或多种。关于这里这四个参数的含义具体可以参见现有技术，这里不再赘述。应理解，第一GBR QoS参数可以为MN为第一QoS流提供的上行最大比特速率、下行最大比特速率、上行GBR和下行GBR中的一种或多种。
可选地，在一个示例中，MN还可以在第一消息中携带第一QoS流的第二GBR QoS 参数。
其中，第二GBR QoS参数为MN从核心网设备接收到的第一QoS流的GBR QoS参数。应理解，第二GBR QoS参数可以是MN从核心网设备接收到的第一QoS流的上行最大比特速率、下行最大比特速率、上行GBR和下行GBR中的一种或多种。还应理解，第二GBR QoS参数所包含的参数类型可以和第一GBR QoS参数所包含的参数类型相同。比如，第一GBR QoS参数所包含的参数为上行最大比特速率和下行最大比特速率，那么第二GBR QoS参数所包含的参数也可以为上行最大比特速率和下行最大比特速率。但本申请对此不作限定，比如第二GBR QoS参数所包含的参数的类型也可以多于第一GBR QoS参数所包含的参数的类型。
相应地，在S230中，SN可以结合第二GBR QoS参数，确定第一QoS流的承载类型。
比如，若第二GBR QoS参数的取值大于第一GBR QoS参数的取值，则说明需要SN提供SCG空口资源，此时SN可以将第一QoS流的承载类型确定为分离承载。
再如，若第二GBR QoS参数的取值等于第一GBR QoS参数的取值，则说明SN可以不提供SCG空口资源，此时SN可以将第一QoS流的承载类型确定为MCG承载。
此外，SN还可以结合其能够为该第一QoS流提供GBR QoS参数，确定第一QoS流的承载类型。
比如，虽然第一消息中包括了第一GBR QoS参数，但SN能够提供大于第二GBR QoS参数的取值的GBR QoS参数，则SN可以将QoS流的承载类型确定为SCG承载。
基于上述技术方案，SN可以结合更多的信息，比如MN从核心网设备接收到的第一QoS流的GBR QoS参数和/或SN能够为该第一QoS流提供GBR QoS参数，更为合理地确定第一QoS流的承载类型。
需要说明的是，上述实施方式中，在进行第二GBR QoS参数的取值与第一GBR QoS参数的取值的大小关系比较时，我们假设第二GBR QoS参数和第一GBR QoS参数所包含的参数类型相同，并且是对同一类型的参数进行比较。以及，在第二GBR QoS参数和第一GBR QoS参数包含多种类型的参数时，第二GBR QoS参数的取值与第二GBR QoS参数的取值相等的含义是，任一相同类型的参数的取值都相同；类似地，第二GBR QoS参数的取值大于第二GBR QoS参数的取值相等的含义是，对于任一相同类型的参数，第二GBR QoS参数中该类型的参数的取值大于第一GBR QoS参数中该类型的参数的取值；第二GBR QoS参数的取值小于第二GBR QoS参数的取值相等的含义是，对于任一相同类型的参数，第二GBR QoS参数中该类型的参数的取值小于第一GBR QoS参数中该类型的参数的取值。
举例来说，若第一GBR QoS参数和第二GBR QoS参数所包含的参数都为上行最大比特速率和下行最大比特速率，则若第一GBR QoS参数中的上行最大比特速率等于第二GBR QoS参数中的上行最大比特速率，且第一GBR QoS参数中的下行最大比特速率等于第二GBR QoS参数中的下行最大比特速率，则认为第一GBR QoS参数的取值和第二GBR QoS参数的取值相等。若第一GBR QoS参数中的上行最大比特速率大于第二GBR QoS参数中的上行最大比特速率，且第一GBR QoS参数中的下行最大比特速率大于第二GBR QoS参数中的下行最大比特速率，则认为第一GBR QoS参数的取值大于第二GBR QoS参数的取值。若第一GBR QoS参数中的上行最大比特速率小于第二GBR QoS参数中的上 行最大比特速率，且第一GBR QoS参数中的下行最大比特速率小于第二GBR QoS参数中的下行最大比特速率，则认为第一GBR QoS参数的取值小于第二GBR QoS参数的取值。
方式二
第一QoS流为non-GBR QoS流，辅助信息为第一UE AMBR和第一PDU会话AMBR。
其中，第一UE AMBR为MN为目标UE建立在SN的non-GBR QoS流提供的AMBR，目标UE为第一QoS流对应的UE。也就是说，目标UE的所有non-GBR QoS流由建立在MN的non-GBR QoS流(记作：第一部分non-GBR QoS流)和建立在SN的non-GBR QoS流(记作：第二部分non-GBR QoS流)组成，第一UE AMBR即为MN为所述第二部分non-GBR QoS流提供的AMBR。应理解，第二部分non-GBR QoS流包括第一QoS流。其中，UE AMBR可以包括UE下行AMBR和UE上行AMBR中的一种或者两种都包括。
第一PDU会话AMBR为MN为目标PDU会话中建立在SN的non-GBR QoS流提供的AMBR。其中第一QoS流对应目标PDU会话，即目标PDU会话中建立在SN的non-GBR QoS流包括第一QoS流。应理解，目标PDU会话中建立在SN的non-GBR QoS流为第二部分non-GBR QoS流的全部或一部分。其中，PDU会话AMBR可以包括PDU会话下行AMBR和PDU会话上行AMBR中的一种或者两种都包括。
需要说明的是，在本申请中，建立在SN的non-GBR QoS流指对应的SDAP实体建立在SN的non-GBR QoS流。类似地，在MN的non-GBR QoS流指对应的SDAP实体建立在MN的non-GBR QoS流。
在上述场景下，可以有下述四种情况，下面进行详细说明。
情况1
第一消息(或者辅助信息)包括第一UE AMBR和第一PDU会话AMBR。
此时，第一消息可以指示SN被允许将第一QoS流的承载类型配置成涉及MCG空口资源的承载类型。或者说，若第一消息包括第一UE AMBR和第一PDU会话AMBR，SN可以考虑将第一QoS流配置成涉及MCG空口资源的承载类型。
相应地，S230具体包括：若第一消息(或者辅助信息)包括第一UE AMBR和第一PDU会话AMBR，SN确定第一QoS流的承载类型为MCG承载、SCG承载或者分离承载。
具体来讲，若MN在第一消息中携带了第一UE AMBR和第一PDU会话AMBR，则表示MN能够为包含第一QoS流的第二部分non-GBR QoS流提供MCG空口资源，即MN能够为包含第一QoS流的non-GBR QoS流提供MCG空口资源。并且，MN能够为目标PDU会话中建立在SN的non-GBR QoS流提供MCG空口资源，而该目标PDU会话中建立在SN的non-GBR QoS流也包括该第一QoS流。那么MN可以为第一QoS流分配MCG空口资源，从而SN可以考虑将第一QoS流的承载类型确定(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。也就是说，SN可以或者被允许将第一QoS流的承载类型确定为MCG承载或者分离承载。但是，SN最终所确定的第一QoS流的承载类型也可能不是MCG承载或者分离承载，即可以是SCG承载。
情况2
第一消息不包括第一UE AMBR和第一PDU会话AMBR。
此时，第一消息可以指示SN将第一QoS流的承载类型确定为SCG承载。
相应地，S230具体包括：若第一消息不包括第一UE AMBR和第一PDU会话AMBR， SN确定第一QoS流的承载类型为SCG承载。
具体来讲，若MN没有在第一消息中携带第一UE AMBR和第一PDU会话AMBR，则表示MN不能够为包含第一QoS流的第二部分non-GBR QoS流提供MCG空口资源，从而SN可以考虑将第一QoS流的承载类型确定为SCG承载。
情况3
第一消息包括第一UE AMBR，且不包括第一PDU会话AMBR。
此时，第一消息可以指示SN被允许将第一QoS流的承载类型配置成涉及MCG空口资源的承载类型。
相应地，S230具体包括：若第一消息包括第一UE AMBR，且不包括第一PDU会话AMBR，SN确定第一QoS流的承载类型为MCG承载、SCG承载或者分离承载。
具体来讲，若MN在第一消息中携带了第一UE AMBR，则表示MN能够为包含第一QoS流的第二部分non-GBR QoS流提供MCG空口资源。此时，虽然MN在第一消息中没有携带第一PDU会话AMBR，但第一UE AMBR适用于包含第一QoS流的第二部分non-GBR QoS流，所以此时MN也可以考虑将第一QoS流的承载类型确定为(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。但是，SN最终所确定的第一QoS流的承载类型也可能不是MCG承载或者分离承载，即可以是SCG承载。
情况4
第一消息包括第一PDU会话AMBR，且不包括第一UE AMBR。
此时，第一消息可以指示SN被允许将第一QoS流的承载类型配置成涉及MCG空口资源的承载类型。
相应地，S230具体包括：若第一消息包括第一PDU会话AMBR，且不包括第一UE AMBR，SN确定第一QoS流的承载类型为MCG承载、SCG承载或者分离承载。
具体来讲，虽然MN在第一消息中没有携带第一UE AMBR，但是，MN在第一消息中携带了第一PDU会话AMBR，则表示MN能够为包含第一QoS流的non-GBR QoS流提供MCG空口资源。由于第一QoS流属于目标PDU会话，那么MN有可能保证第一QoS流的QoS需求，从而SN可以考虑将第一QoS流的承载类型确定(或者配置)为涉及MCG空口资源的承载类型。也就是说，SN可以或者有机会将第一QoS流的承载类型确定为MCG承载或者分离承载。但是，SN最终所确定的第一QoS流的承载类型也可能不是MCG承载或者分离承载，即可以是SCG承载。
另外，对于不属于目标PDU会话的non-GBR QoS流，SN可以将该non-GBR QoS流的承载类型确定为SCG承载，但本申请对此不作限定。
综上，通过方式二的方法，SN可以根据第一消息是否包括辅助信息，进一步地还可以根据辅助信息所包括的内容，确定第一QoS流的承载类型。
应理解，方式二的基本思想是，在设计第一消息的格式时，可以在第一消息中预留两个信元的位置，即第一UE AMBR对应的信元和第一PDU会话AMBR对应的信元。但在具体传输时，MN可以不填充这两个信元中的任意一个或两个均不填充，从而实现上述情况1至情况4所表示的含义。
在另外一种可能的实现方式中，第一QoS流是否能配置成涉及MCG空口资源的承载类型，取决于SN是否收到MN为第一QoS流对应的目标PDU会话提供的第一PDU会话 AMBR。具体的，如果SN收到了MN为所述第一Qos流对应的目标PDU会话提供的第一PDU会话AMBR，则SN可以考虑将第一QoS流的承载类型确定为(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载，即可以是MCG承载、SCG承载或者分离承载；如果没有收到，则SN可以确定第一QoS流的承载类型为SCG承载。
方式三
第一QoS流为non-GBR QoS流，辅助信息为第一UE AMBR。其中，第一UE AMBR的含义参见上文描述，不再赘述。
在此场景下，若第一消息包括辅助信息，第一消息可以指示SN被允许将第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；或者说，若第一消息包括辅助信息，SN可以考虑将第一QoS流配置成涉及MCG空口资源的承载类型。和/或，若第一消息不包括辅助信息，第一消息可以指示SN将第一QoS流的承载类型配置成SCG承载。
相应地，S230具体包括：若第一消息包括辅助信息，SN确定第一QoS流的承载类型为MCG承载、SCG承载或者分离承载。若第一消息不包括辅助信息，SN确定第一QoS流的承载类型为SCG承载。
具体地，若MN在第一消息中携带了第一UE AMBR，则表示MN能够为包含第一QoS流的第二部分non-GBR QoS流提供MCG空口资源。从而，SN可以考虑将第一QoS流的承载类型确定(或者配置)为涉及MCG空口资源的承载类型。也就是说，SN可以或者有机会将第一QoS流的承载类型确定为MCG承载或者分离承载。但是，SN最终所确定的第一QoS流的承载类型也可能不是MCG承载或者分离承载，即可以是SCG承载。
与此相对的，若MN没有在第一消息中携带第一UE AMBR，则表示MN不能够为包含第一QoS流的第二部分non-GBR QoS流提供MCG空口资源，从而SN可以考虑将第一QoS流的承载类型确定为SCG承载。
综上，通过方式三的方法，SN可以根据第一消息是否包括辅助信息，合理地确定第一QoS流的承载类型。
方式四
第一QoS流为non-GBR QoS流，辅助信息为第一PDU会话AMBR。第一PDU会话AMBR的含义参见上文描述，不再赘述。
在此场景下，若第一消息包括辅助信息，第一消息可以指示SN被允许将第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；或者说，若第一消息包括辅助信息，SN可以考虑将第一QoS流配置成涉及MCG空口资源的承载类型。和/或，若第一消息不包括辅助信息，第一消息可以指示SN将第一QoS流的承载类型配置成SCG承载。
相应地，S230具体包括：若第一消息包括辅助信息，SN确定第一QoS流的承载类型为MCG承载、SCG承载或者分离承载。和/或，若第一消息不包括辅助信息，SN确定第一QoS流的承载类型为SCG承载。
具体地，若MN在第一消息中携带了第一PDU会话AMBR，则表示MN能够为该目标PDU会话中建立在SN的non-GBR QoS流提供MCG空口资源，从而SN可以考虑将第一QoS流的承载类型确定(或者配置)为涉及MCG空口资源的承载类型。也就是说，SN可以或者有机会将第一QoS流的承载类型确定为MCG承载或者分离承载。但是，SN最终所确定的第一QoS流的承载类型也可能不是MCG承载或者分离承载，即可以是SCG 承载。
与此相对的，若MN没有在第一消息中携带第一PDU会话AMBR，则表示MN不能为该目标PDU会话中建立在SN的non-GBR QoS流提供MCG空口资源，从而SN可以确定第一QoS流的承载类型为SCG承载。
综上，通过方式四的方法，SN可以根据第一消息是否包括辅助信息，合理地确定第一QoS流的承载类型。
可选地，在一个示例中，MN还可以在第一消息中携带第一QoS流的第二UE AMBR和/或第二PDU会话AMBR。
其中，第二UE AMBR可以是MN根据从核心网设备接收到的UE AMBR确定的。第二PDU会话AMBR可以是MN根据从核心网设备接收到的PDU会话AMBR确定的。第二UE AMBR为SN需要为第二部分non-GBR QoS流提供的AMBR。第二PDU会话AMBR为SN需要为目标PDCP实体中的non-GBR QoS流提供的AMBR。
相应地，在S230中，SN可以结合第二UE AMBR和/或第二PDU会话AMBR，确定第一QoS流的承载类型。
比如，若第一UE AMBR等于第二UE AMBR，SN可以将第一QoS流的承载类型确定为MCG承载。或者，若第一PDU会话AMBR等于第二PDU会话AMBR，SN可以将第一QoS流的承载类型确定为MCG承载。
再如，若第一UE AMBR小于第二UE AMBR，SN可以将第一QoS流的承载类型确定为分离承载。或者，若第一PDU会话AMBR小于第二PDU会话AMBR，SN可以将第一QoS流的承载类型确定为分离承载。
应理解，第一UE AMBR和第二UE AMBR的大小关系，以及第一PDU会话AMBR与第二PDU会话AMBR的大小关系的含义，与第一GBR QoS参数和第二GBR QoS参数的大小关系的含义类似，这里不再赘述。
可选地，作为另一种实现方式，如果第一消息包括辅助信息，但辅助信息的取值为0，此时等价于第一消息没有包括辅助信息的方案。
可选地，该方法还可以包括：
S240，SN向MN发送承载类型指示信息。相应地，MN接收SN发送的承载类型指示信息。
S250，MN根据承载类型指示信息，确定第一QoS流的承载类型。
其中，该承载类型指示信息用于指示SN确定的第一QoS流的承载类型。
具体地，SN在确定第一QoS流的承载类型后，可以通过承载类型指示信息将其所确定的第一QoS流的承载类型告知MN。从而，MN可以根据承载类型指示信息，确定第一QoS流的承载类型。
可选地，该承载类型指示信息可以显式的信息，即该承载类型指示信息为该第一QoS流的承载类型，或者该承载类型指示信息为该第一QoS流的承载类型是否涉及MCG空口资源的信息。也就是说，SN明确告诉MN第一QoS流的的承载类型，或者告知MN第一QoS流的承载类型是否涉及MCG空口资源。
此外，承载类型指示信息可以隐式的信息。比如，承载类型指示信息可以是SN为第一QoS流对应的承载分配的接收上行数据的上行传输网络层(uplink transmission nerwork  layer，UL TNL)信息。可选地，该上行传输网络层信息可以包括互联网协议(internet protocol，IP)地址和/或隧道端点标识(tunnel endpoint identifier，TEID)。
应理解，若该承载类型指示信息为该上行传输网络层信息，则表示SN确定的第一QoS流的承载类型为涉及MCG空口资源的承载类型。在此情况下，MN可以为第一QoS流或者第一QoS流对应的承载，生成RLC配置和逻辑信道配置。具体如何生成RLC配置和逻辑信道配置可以参见现有技术，这里不再赘述。
应理解，该承载类型指示信息还可以指示或者包括第一QoS流的标识或者第一QoS流对应的承载的标识。
针对前文描述的现有技术中的问题，本申请还提供了另外三种确定承载类型的方法。下面分别结合图8至图10进行说明。
图8示出了本申请提供的另一种确定承载类型的方法300的示例性流程图。该方法300主要包括S310至S330。以下对各步骤进行说明。
S310，MN生成建议信息。其中，该建议信息用于指示该MN所建议的第一QoS流的承载类型。第一QoS流的定义与方法200中的第一QoS流的定义相同，这里不再赘述。
S320，MN向SN发送该建议信息。相应地，SN接收MN发送的该建议信息。
S330，SN根据该建议信息，确定第一QoS流的承载类型。
具体地，MN可以向SN建议第一QoS流的承载类型，SN可以根据MN的建议，确定第一QoS流的承载类型。
因此，根据本申请提供的确定承载类型的方法，SN可以根据MN建议的承载类型，更合理的确定QoS流的承载类型。
应理解，SN可以自主的确定第一QoS流的承载类型。即，SN最终所确定的承载类型可以是MN建议的承载类型，也可以不是MN建议的承载类型。比如，若MN建议的承载类型是分离承载，但是SN能够满足第一QoS流的QoS需求，则可以将第一QoS流的承载类型确定为SCG承载。
可选地，该方法还可以包括：
S340，SN向MN发送承载类型指示信息。相应地，MN接收SN发送的承载类型指示信息。
其中，该承载类型指示信息用于指示SN确定的第一QoS流的承载类型。
S350，MN根据承载类型指示信息，确定第一QoS流的承载类型。
具体地，SN在确定第一QoS流的承载类型后，可以通过承载类型指示信息将其所确定的第一QoS流的承载类型告知网络设备。从而，网络设备可以根据承载类型指示信息，确定第一QoS流的承载类型。
关于S340和S350，具体可以参见方法200中对S240和S250所作的说明，这里不再赘述。
上文中结合图7和图8，描述了确定QoS流的承载类型的方法。下面结合图9和图10，详细说明确定DBR的承载类型的方法。
图9示出了本申请提供的又一种确定承载类型的方法400的示例性流程图。该方法400主要包括S410至S430。以下对各步骤进行说明。
S410，MN根据是否在第一消息中包括辅助信息，生成第一消息。
第一消息用于SN确定第一DRB的承载类型。或者说，第一消息是否包括辅助信息的结果，用于SN确定第一DRB的承载类型。即，SN可以根据第一消息是否包括辅助信息，确定第一DRB的承载类型。第一DRB可以是对应的PDCP实体建立在该SN上的任一DRB。
示例性的，MN如果能够为该第一DRB提供空口资源，则MN可以在第一消息中包括辅助信息。再如，若MN不能够为该第一DRB提供空口资源，则MN可以不在第一消息中包括辅助信息。其中，空口资源用于提供第一DRB的传输比特速率。
S420，MN向SN发送该第一消息。相应地，SN接收MN发送的第一消息。
S430，SN根据第一消息是否包括辅助信息，确定第一DRB的承载类型。
根据本申请提供的确定承载类型的方法，对于对应的PDCP实体建立在SN上的DRB，MN可以通过是否在第一消息中包括辅助信息辅助SN确定该DRB的承载类型，相应地，SN可以根据MN提供的第一消息中是否包括辅助信息，合理地确定该DRB的承载类型。从而，可以实现SN合理设置DRB的承载类型的目的，进而能够避免现有技术中由于SN对DRB的承载类型决策不合适而造成的协议过程较长的问题。
在一种可能的实现方式中，该辅助信息为第一参数，第一参数为MN为第一DRB提供的QoS参数。可选地，该QoS参数可以包括上行MBR、下行MBR、上行GBR和下行GBR中的一种或多种。
在此场景下，若第一消息包括辅助信息，则第一消息可以指示SN被允许将第一DRB的承载类型配置成涉及MCG空口资源的承载类型。或者说，若第一消息包括辅助信息，SN可以考虑将第一DRB配置成涉及MCG空口资源的承载类型。和/或，若第一消息不包括辅助信息，则第一消息可以指示SN将第一DRB的承载类型确定为SCG承载。
相应地，S430具体包括：若第一消息包括辅助信息，SN确定第一DRB的承载类型为MCG承载、SCG承载或者分离承载；若第一消息不包括辅助信息，SN确定第一DRB的承载类型为SCG承载。
具体来讲，若MN在第一消息中携带了第一参数，则表示MN能够为第一DRB提供QoS参数，或者表示MN能够为第一DRB分配涉及MCG的空口资源，从而SN可以考虑将第一DRB的承载类型确定(或者配置)为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。也就是说，SN可以或者有机会将第一DRB的承载类型确定为MCG承载或者分离承载。但是，SN最终所确定的第一DRB的承载类型也可能不是MCG承载或者分离承载，即可以是SCG承载。比如，若SN能够为第一DRB提供该第一DRB所需的QoS参数，可以确定第一DRB的承载类型为SCG承载。
于此相对地，若MN在第一消息中没有携带第一参数，则表示MN不能够为第一DRB分配涉及MCG的空口资源，从而SN可以将第一DRB的承载类型确定为SCG承载。
基于上述技术方案，MN可以通过是否在第一消息中携带其为该DRB提供的QoS参数，辅助SN确定第一DRB的承载类型，相应地，SN可以根据MN提供的第一消息中是否包括MN为该第一DRB提供的QoS参数，合理地确定第一DRB的承载类型。
可选地，该方法还可以包括：
S440，SN向MN发送承载类型指示信息。相应地，MN接收SN发送的承载类型指示信息。
S450，MN根据承载类型指示信息，确定第一DRB的承载类型。
其中，该承载类型指示信息用于指示SN确定的第一DRB的承载类型。
具体地，SN在确定第一DRB的承载类型后，可以通过承载类型指示信息将其所确定的第一DRB的承载类型告知MN。从而，MN可以获知SN所确定的第一DRB的承载类型。
可选地，该承载类型指示信息可以显式的信息，即该承载类型指示信息为该第一DRB的承载类型，或者该承载类型指示信息为该第一DRB的承载类型是否涉及MCG空口资源的信息。也就是说，SN明确告诉MN第一DRB的的承载类型，或者告知MN第一DRB的承载类型是否涉及MCG空口资源。
此外，承载类型指示信息可以隐式的信息。比如，承载类型指示信息可以是SN为第一DRB分配的接收上行数据的上行传输网络层信息。该上行传输网络层信息可以包括互联网协议(internet protocol，IP)地址和隧道端点标识(tunnel endpoint identifier，TEID)，SN根据该上行传输网络层信息可以接收MN发送的该第一DRB的上行数据。
应理解，若该承载类型指示信息为该传输层信息，则表示SN确定的第一DRB的承载类型为涉及MCG空口资源的承载类型。在此情况下，MN可以为第一DRB生成RLC实体和逻辑信道配置。
应理解，该承载类型指示信息还可以包括或者指示第一DRB的标识。
图10示出了本申请提供的另一种确定承载类型的方法500的示例性流程图。该方法500主要包括S510至S530。以下对各步骤进行说明。
S510，MN生成建议信息。其中，该建议信息用于指示该MN所建议的第一DRB的承载类型。第一DRB的定义与方法400中的第一DRB的定义相同，这里不再赘述。
示例性的，MN可以根据其是否能够为该第一DRB提供空口资源，生成建议信息。其中，空口资源用于提供第一DRB的传输比特速率。比如，若MN能够为该第一DRB提供空口资源，则可以建议SN将承载类型确定为分离承载或者MCG承载。再如，若MN不能够为该第一DRB提供空口资源，则可以建议SN将承载类型确定为SCG承载。
S520，MN向SN发送该建议信息。相应地，SN接收MN发送的该建议信息。
S530，SN根据该建议信息，确定第一DRB的承载类型。
具体地，MN可以向SN建议第一DRB的承载类型，SN可以根据MN的建议，确定DRB的承载类型。
因此，根据本申请提供的确定承载类型的方法，SN可以根据MN提供的建议的承载类型，更合理的确定DRB的承载类型。
应理解，SN最终所确定的承载类型可以是MN建议的承载类型，也可以不是MN建议的承载类型。比如，若MN建议的承载类型是分离承载，但是SN能够满足为第一DRB的QoS需求，则可以将第一DRB的承载类型确定为SCG承载。
可选地，该方法还可以包括：
S540，SN向MN发送承载类型指示信息。相应地，MN接收SN发送的承载类型指示信息。
S550，MN根据承载类型指示信息，确定第一DRB的承载类型。
其中，该承载类型指示信息用于指示SN确定的第一DRB的承载类型。
具体地，SN在确定第一DRB的承载类型后，可以通过承载类型指示信息将其所确定的第一DRB的承载类型告知网络设备。从而，网络设备可以根据承载类型指示信息，确定第一DRB的承载类型。
关于S540和S550，具体可以参见方法400中对S440和S450所作的说明，这里不再赘述。
上文主要结合图7至图10，描述了本申请提供的确定承载类型的方法。除此之外，本申请还提供了一种修改承载类型的方法。该方法为SN修改承载的承载类型提供了可能。下面，结合图11，对该修改承载类型的方法进行说明。
需要说明的是，图11所示的方法可以在图7至图10所示的方法中的任一方法之后执行。比如，图11所示的方法中的第一承载可以是图7和图8所示的方法中的第一QoS流对应的承载。根据图7或者图8所示的方法确定承载类型，并且进一步地建立承载后，在SN需要修改承载类型时，可以采用图11所示的方法进行承载类型的修改。再如，图11所示的方法中的第一承载可以是图9和图10所示的方法中的第一DRB。根据图9或者图10所示的方法确定承载类型，并且进一步地建立承载后，在SN需要修改承载类型时，可以采用图11所示的方法进行承载类型的修改。
图11示出了一种修改承载类型的方法的示意性流程图。该方法主要包括S610至S620。以下对各步骤进行详细说明。
S610，SN生成修改申请(required)消息。该修改申请消息用于申请修改第一承载的承载类型。
其中，第一承载对应的PDCP实体建立在SN。或者可以说，第一承载对应的QoS流的SDAP实体建立在SN。
S620，SN向MN发送该修改申请消息。相应地，MN接收SN发送的该修改申请消息。
具体来说，SN期望修改第一承载的承载类型时，可以通过向MN发送修改申请消息，请求修改第一承载的承载类型。
在一种实现方式中，该修改申请消息可以包括承载建立列表和承载删除列表。承载建立列表包括该第一承载的标识和指示该第一承载需要修改的承载类型的指示信息(简称为：指示信息)；承载删除列表可以包括该第一承载的标识。
可选地，该承载删除列表还可以包括该第一承载当前的承载类型。
应理解，该指示信息指示的需要修改的承载类型为SN所确定的第一承载的新的承载类型。第一承载当前的承载类型为第一承载原来的承载类型。即，SN期望将第一承载从原来的承载类型修改为新的承载类型。
通过删除为原来的承载类型的第一承载，将第一承载建立成新的承载类型的承载，可以实现对该第一承载的承载类型的修改。
所述指示信息，可以是显式的承载类型，例如MCG承载、SCG承载或者分离承载。该指示信息也可以是隐式的信息，该隐式的信息可以指示该第一承载的新的承载类型。比如，该隐式的信息可以是上行传输网络层(uplink transmission nerwork layer，UL TNL)信息，该上行传输网络层信息为SN为该第一承载分配的用于接收MN发送的上行数据的传输层信息，其中，所述上行数据为MN从终端设备接收的所述第一承载的上行数据。应理 解，如果指示信息为该上行传输网络层信息，则表示新的承载类型为涉及MCG空口资源的承载类型，即MCG承载或者分离承载。
该上行传输网络层信息可以包括互联网协议(internet protocol，IP)地址和隧道端点标识(tunnel endpoint identifier，TEID)，SN根据该上行传输网络层信息可以接收MN发送的该第一承载的上行数据。
因此，根据本申请提供的修改承载类型的方法，SN通过向MN发送修改申请消息，可以触发承载类型的修改(或者变更)，进一步地可以实现承载类型的修改。
进一步地，SN可以通过在承载建立列表和承载删除列表中携带同一个承载标识来实现SN触发的承载类型修改。
下面针对不同场景进行说明。
场景一
MN可以自主决定是否接受SN的修改申请。
MN在接收到SN后，可以自主决定是否接受SN的修改申请。若MN决定接受SN对该第一承载的修改申请，该方法还可以包括S630至S650。
S630，MN向SN发送修改请求(request)消息。相应地，SN接收MN发送的修改请求消息。
该修改请求消息用于指示MN同意修改该第一承载的承载类型。也就是说，SN接收到MN发送的修改请求消息，则可以获知MN同意修改该第一承载的承载类型。
可选地，如果第一承载的新的承载类型为MCG承载或者分离承载，MN还可以在修改请求消息中携带上述上行传输网络层信息。或者，若上述指示信息为上行传输网络层信息，MN也可以不在修改请求消息中携带上行传输网络层信息。
S640，SN向MN发送修改请求确认(acknowledge)消息。相应地，MN接收SN发送的修改请求确认消息。
该修改请求确认消息包括空口RRC配置#1，该空口RRC配置#1为SN为终端设备生成的空口RRC配置#1，该空口RRC配置#1用于该终端设备配置该第一承载。
在此之后，MN可以向终端设备发送该空口RRC配置#1和空口RRC配置#2。相应地，终端设备接收该空口RRC配置#1和空口RRC配置#2。
例如，原本的承载类型是分离承载，新的承载类型为SCG承载，则SN需要为UE生成PDCP恢复的配置(即，空口RRC配置#1的一例)，指示该承载的PDCP实体执行数据恢复，MN需要为UE生成MCG RLC承载删除的配置(即，空口RRC配置#2的一例)。
例如，原本的承载类型为SCG承载，新的承载类型为MCG承载，则SN需要为UE生成SCG RLC承载释放的配置(即，空口RRC配置#1的一例)，MN需要为UE生成MCG RLC承载增加的配置(即，空口RRC配置#2的一例)。
S650，MN向SN发送修改确认(confirm)消息。相应地，SN接收MN发送的该修改确认消息。
其中，该修改确认消息用于指示该第一承载的承载类型修改完成。
具体来讲，在MN接受SN的修改申请后，可以向SN发送修改请求消息，一方面告知SN该MN接受了SN的修改申请，另一方面请求SN为该第一承载生成相应的空口RRC配置#1。SN在生成该第一承载生成相应的空口RRC配置#1后，通过修改请求确认消息 将该配置发送给MN。MN接收到修改请求确认消息后，生成空口RRC配置#2，将空口RRC配置#1和空口RRC配置#2一起发送给终端设备，完成该第一承载的配置。并且，MN通过向SN发送修改确认消息，告知SN该MN已经完成了对该第一承载的配置。
场景二
MN必须接受SN的修改申请。即MN不能拒绝SN为第一承载发起的承载修改请求。
在此场景下，SN可以在修改申请消息中携带空口RRC配置#1。在此场景下，该方法还可以包括上述S650和S660。即，在场景二下，可以不执行S630和S640，在S620之后执行S650和S660。
即，MN在接收到SN发送的空口RRC配置#1后，生成空口RRC配置#2，将空口RRC配置#1和空口RRC配置#2一起发送给终端设备，完成该第一承载的配置。并且，MN通过向SN发送修改确认消息，告知SN该MN已经完成了对该第一承载的配置。
可选地，如果第一承载原来的承载类型为SCG承载，新的承载类型为MCG承载或者分离承载，MN还可以在S660中的修改确认消息中携带上述上行传输网络层信息。或者，若上述指示信息为上行传输网络层信息，MN也可以不在修改确认消息中携带上行传输网络层信息。
综上，基于上述方法，在辅网络设备侧空口状态变化时，辅网络设备可以将承载类型修改为更适合辅网络设备侧空口状态的承载类型。
在本申请中，MN与SN在采用例如图6至图11所示的确定承载类型的方法，协商确定承载类型之后，还可以协商终端设备在MN或者SN的上行发送时刻。以下结合图13进行说明。应理解，图13所示的该通信方法可以适用于图2至图5所示的各种DC场景，例如以主基站为5G基站，且辅基站为LTE基站的NE-DC场景。
图13是本申请提供的一个通信方法700的示意性流程图。该方法700主要包括S710至S730。以下对各步骤进行说明。
S710，MN向SN发送时域配置信息。相应的，SN接收所述时域配置信息。
可选地，当MN确认终端设备由于功率控制或者交调干扰(inter modulation interference)需要终端设备进行单上行传输时，MN发送时域配置信息给SN。该时域配置信息可以是终端设备在SN的上下行时域分配。其中，所述单上行传输是指终端设备在一个时间单元上只向MN或者SN的小区发送数据或信号，即在同一个时间单元上不能同时通过MN或者SN的小区发送数据或信号。其中，时间单元可以是子帧或者时隙，或者迷你子帧等，不做限定。本实施例中以子帧为例进行说明。
可选地，所述上下行时域分配是以SN的无线接入制式(radio access technology，RAT)对应的上下行时域分配形式，也可能是以MN的RAT对应的上下行时域分配形式，不做限定。例如，该上下行时域分配可以是LTE协议TS36.331定义的上下行时域分配(subframe Assignment)，上下行时域分配为LTE对应的上下行时域分配形式，具体形式可参见TS36.211中的uplink-downlink configuration。该上下行时域分配还可以是TS 38.331中定义的TDD-UL-DL-Pattern或TDD-UL-DL-ConfigCommon，指示上下行的时分复用(time division duplex，TDD)配置。
可选地，所述时域配置信息包括第二HARQ offset。
S720，SN根据所述时域配置信息确定第一HARQ offset。
此外，SN还可以根据所述时域配置信息确定上下行时域分配。其中，上下行时域分配可以是子帧分配。可选地，SN把从MN收到的时域配置信息作为上下行时域分配。
可选地，第一HARQ offset可以被预设为0。
可选地，SN可以结合所述时域配置信息与其他信息，例如该SN下的小区负载，该SN下接入的一个或多个终端设备的上行资源使用情况，来确定所述第一HARQ offset。
在一个实现方式中，所述SN可以将所述第一HARQ offset调整为0，以使得SN的上下行时域分配和MN发送的上下行时域分配相同。
在一个实现方式中，若所述时域配置信息包括第二HARQ offset，所述SN将所述第一HARQ offset确定为与所述第二HARQ offset不同的值，并发送给MN。
在一个实现方式中，所述SN可以将所述第一HARQ offset调整为非0的常数，以使得SN的上下行时域分配和MN发送的上下行时域分配相同。
本申请所述的HARQ offset用于指示HARQ子帧偏移，HARQ offset指终端设备在上下行时域分配对应的上行子帧基础上进行的HARQ子帧的偏移。HARQ offset用于指示HARQ子帧偏移，可以用于上行子帧相关的子帧分配中的设计，详细内容可以参见3GPP TS 36.213[23]中的相关内容。
S730，所述SN向MN发送所述第一HARQ offset。
相应地，MN接收所述第一HARQ offset。进而，MN可以根据该第一HARQ offset和之前发送给SN的时域配置信息获得该终端设备在MN下的服务小区可以使用的上行时域信息。所述上行时域信息包括上行时间单元的TDD配比。
MN可以将从SN获取的第一HARQ offset用于上下行时域分配。
可选地，在本申请的一个实施方式中，如果SN将第一HARQ offset设置为0，SN可以不将该第一HARQ offset发送给MN.则MN可以将原先的时域配置信息用于上下行时域分配。
在另一个实施方式中，SN可以把为终端设备确认的上下行时域分配和第一HARQ offset发送给MN。MN可以根据该上下行时域分配和第一HARQ offset获得该终端设备在MN下的服务小区可以使用的上行时域信息。
在另一个实施方式中，SN可以给MN发送一个时域分配信息，该时域配置信息可以是终端设备在SN或MN使用的上下行时域分配。
可选地，在另一个实施方式中，所述方法还包括：
S740，SN根据从MN收到的时域配置信息为终端确定时分复用模式配置(time division multiplexing pattern configuration，TDM-patternConfig)。
具体地，SN收到MN发送的时域配置信息之后，可以为终端设备确定提供给该终端设备使用的时分复用模式配置。
所述时分复用模式配置可以包括上下行时域分配和所述第一HARQ offset。其中上下行时域分配为SN的RAT对应的上下行时域分配形式。对于该终端设备而言，终端设备只会在对上下行时域分配中对应的上行子帧采用所述第一HARQ offset进行偏置之后的子帧上发送上行信息。
S750，SN为终端设备确定的时分复用模式配置通知给终端设备。
在一个实施方式中，SN可以先把该时分复用模式配置发送给MN，MN再透传给终 端设备。例如，可以采用隐式指示的方式向终端通知所述时分复用模式配置。具体地，SN可以将时分复用模式配置封装在一个容器(container)中，在向MN发送的第一消息中携带该容器，从而将该时分复用模式配置发送给MN。MN接收包含所述容器的消息，进而在MN为终端设备发送的第二消息中携带该容器，从而将时分复用模式配置发送给终端。其中，所述第一消息或第二消息可以是无线资源控制连接重配置(RRC Connection Reconfiguration)消息。又例如，可以采用显示指示的方式向终端设备通知所述时分复用模式配置。具体地，SN可以直接向MN发送时分复用模式配置或者包含所述时分复用模式配置的消息，MN读取所述时分复用模式配置后再发送给终端。
在另一个实施方式中，SN可以直接将所述时分复用模式配置发给终端设备。
可选地，在一个实施方式中，SN可以把发给终端的时分复用模式配置和SN给MN发送的第一HARQ offset和/或为终端设备确定的上下行时域分配在同一条消息中发送给MN。
相应地，终端设备接收所述时分复用模式配置。
具体地，终端设备收到该时分复用模式配置之后，终端设备可以在对上下行时域分配中对应的上行子帧进行第一HARQ offset之后的子帧上发送上行信息。
需要说明的是，图12所示实施例可以单独实施，也可以与图7至图11所示的任一一个或多个实施例结合，对此不做限定。
采用本申请实施例提供的通信方法，SN可以结合自身的运行情况为MN或者终端确定第一HARQ offset，从而能够提升MN或者终端设备在进行上下行时域分配的准确性，从而提升通信质量。
上文中主要结合图2至图12，描述了本申请提供的方法。下面将介绍本申请提供的装置。
图13是本申请实施例提供的通信装置的示意性框图。如图13所示，该通信装置800可以包括处理单元810和收发单元820。
在一种可能的设计中，该通信装置800可对应于上文方法实施例中的辅网络设备，例如，可以为SN，或者配置于SN中的芯片。当该通信装置是SN时，该处理单元可以是处理器，收发单元可以是收发器。该通信装置还可以包括存储单元，该存储单元可以是存储器。该存储单元用于存储指令，该处理单元执行该存储单元所存储的指令，以使该通信装置执行上述方法。当该通信装置是SN内的芯片时，该处理单元可以是处理器，收发单元可以是接口电路、输入/输出接口、管脚或电路等；该处理单元执行存储单元所存储的指令，以使该通信装置执行上述各方法中由SN所执行的操作，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该通信装置内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)
在一种实现方式中，该通信装置800中的各单元和上述其他操作和/或功能为了实现图7中的方法的相应流程。具体地，处理单元810可用于执行图7所示的方法中的S230，收发单元820可用于执行图7所示的方法中的S220和S240。
在一种实现方式中，该通信装置800中的各单元和上述其他操作和/或功能为了实现图8中的方法的相应流程。具体地，处理单元810可用于执行图8所示的方法中的S330，收发单元820可用于执行图8所示的方法中的S320和S340。
在又一种实现方式中，该通信装置800中的各单元和上述其他操作和/或功能为了实现图9中的方法的相应流程。具体地，处理单元810可用于执行图9所示的方法中的S430，收发单元820可用于执行图9所示的方法中的S420和S440。
在又一种实现方式中，该通信装置800中的各单元和上述其他操作和/或功能为了实现图10中的方法的相应流程。具体地，处理单元810可用于执行图10所示的方法中的S530，收发单元820可用于执行图10所示的方法中的S520和S540。
在又一种实现方式中，该通信装置800中的各单元和上述其他操作和/或功能为了实现图11中的方法的相应流程。具体地，处理单元810可用于执行图11所示的方法中的S610，收发单元820可用于执行图11所示的方法中的S620至S650。
在又一种实现方式中，该通信装置800中的各单元和上述其他操作和/或功能为了实现图12中的方法的相应流程。具体地，处理单元810可用于执行图12所示的方法中的S720和S740，收发单元820可用于执行图12所示的方法中的S710、S730和S750。
在另一种可能的设计中，该通信装置800可对应于上文方法实施例中的主网络设备，例如，可以为MN，或者配置于MN中的芯片。当该通信装置是MN时，该处理单元可以是处理器，收发单元可以是收发器。该通信装置还可以包括存储单元，该存储单元可以是存储器。该存储单元用于存储指令，该处理单元执行该存储单元所存储的指令，以使该通信装置执行上述方法。当该通信装置是MN内的芯片时，该处理单元可以是处理器，该收发单元可以是接口电路、输入/输出接口、管脚或电路等；该处理单元执行存储单元所存储的指令，以使该通信装置执行上述方法中由MN所执行的操作，该存储单元可以是该芯片内的存储单元(例如，寄存器、缓存等)，也可以是该通信装置内的位于该芯片外部的存储单元(例如，只读存储器、随机存取存储器等)。
在一种实现方式中，该通信装置800中的各单元和上述其他操作和/或功能为了实现图7中的方法的相应流程。具体地，处理单元810可用于执行图7所示的方法中的S210和S250，收发单元820可用于执行图7所示的方法中的S220和S240。
在一种实现方式中，该通信装置800中的各单元和上述其他操作和/或功能为了实现图8中的方法的相应流程。具体地，处理单元810可用于执行图8所示的方法中的S310和S350，收发单元820可用于执行图8所示的方法中的S320和S340。
在又一种实现方式中，该通信装置800中的各单元和上述其他操作和/或功能为了实现图9中的方法的相应流程。具体地，处理单元810可用于执行图9所示的方法中的S410和S450，收发单元820可用于执行图9所示的方法中的S420和S440。
在又一种实现方式中，该通信装置800中的各单元和上述其他操作和/或功能为了实现图10中的方法的相应流程。具体地，处理单元810可用于执行图10所示的方法中的S510和S550，收发单元820可用于执行图10所示的方法中的S520和S540。
在又一种实现方式中，该通信装置800中的各单元和上述其他操作和/或功能为了实现图11中的方法的相应流程。具体地，收发单元820可用于执行图11所示的方法中的S620至S650。
在又一种实现方式中，该通信装置800中的各单元和上述其他操作和/或功能为了实现图12中的方法的相应流程。具体地，收发单元820可用于执行图12所示的方法中的S710和S730。
上述各个装置实施例中主网络设备与辅网络设备和方法实施例中的MN或SN完全对应，由相应的单元或单元执行相应的步骤，例如收发单元(收发器)方法执行方法实施例中发送和/或接收的步骤，除发送接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。收发单元可以包括发送单元和/或接收单元，收发器可以包括发射器和/或接收器，分别实现收发功能；处理器可以为一个或多个。
应理解，上述各个单元的划分仅仅是功能上的划分，实际实现时可能会有其它的划分方法。
上述主网络设备或者辅网络设备可以是一个芯片，处理单元可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理单元可以是逻辑电路、集成电路等；当通过软件来实现时，该处理单元可以是一个通用处理器，通过读取存储单元中存储的软件代码来实现，该存储单元可以集成在处理器中，也可以位于所述处理单元之外，独立存在。
图14是本申请提供的一种网络设备的结构示意图，该网络设备例如可以为基站。如图14所示，该基站可应用于如图1所示的通信系统中，执行上述方法实施例中主网络设备或者辅网络设备的功能。基站20可包括一个或多个射频单元，如远端射频单元(remote radio unit,RRU)201和一个或多个基带单元(baseband unit，BBU)(也可称为数字单元(digital unit，DU))202。所述RRU 201可以称为收发单元、收发机、收发电路、或者收发器等等，其可以包括至少一个天线2011和射频单元2012。所述RRU 201部分主要用于射频信号的收发以及射频信号与基带信号的转换，例如用于发送上述方法实施例BFR配置。所述BBU 202部分主要用于进行基带处理，对基站进行控制等。所述RRU 201与BBU 202可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。
所述BBU 202为基站的控制中心，也可以称为处理单元，主要用于完成基带处理功能，如信道编码，复用，调制，扩频等等。例如所述BBU(处理单元)202可以用于控制基站执行上述方法实施例中关于网络设备的操作流程。
在一个实施例中，所述BBU 202可以由一个或多个单板构成，多个单板可以共同支持单一接入指示的无线接入网(如LTE网络)，也可以分别支持不同接入制式的无线接入网(如LTE网，5G网或其它网)。所述BBU 202还包括存储器2021和处理器2022，所述存储器2021用于存储必要的指令和数据。所述处理器2022用于控制基站进行必要的动作，例如用于控制基站执行上述方法实施例中关于网络设备的操作流程。所述存储器2021和处理器2022可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板共用相同的存储器和处理器。此外每个单板上还可以设置有必要的电路。
另外，网络设备不限于上述形态，也可以是其它形态：例如：包括BBU和自适应无线单元(adaptive radio unit，ARU)，或BBU和有源天线单元(active antenna unit，AAU)；也可以为客户终端设备(customer premises equipment，CPE)，还可以为其它形态，本申请不限定。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现场可 编程门阵列(field programmable gate array，FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请各实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件单元组合执行完成。软件单元可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序代码，当该计算机程序代码在计算机上运行时，使得该计算机执行上文所描述的各方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读介质，该计算机可读介质存储有程序代码，当该程序代码在计算机上运行时，使得该计算机执行上文所描述的各方。
根据本申请实施例提供的方法，本申请还提供一种系统，其包括前述的一个或多个终端设备以及一个或多个网络设备。
上述实施例，可以全部或部分地通过软件、硬件、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载或执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字通用光盘(digital versatile disc，DVD))、或者半导体 介质。半导体介质可以是固态硬盘。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
还应理解，在本申请中，“当…时”、“若”以及“如果”均指在某种客观情况下终端设备或者网络设备会做出相应的处理，并非是限定时间，且也不要求终端设备或网络设备实现时一定要有判断的动作，也不意味着存在其它限定。
本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。
本文中术语“……中的至少一个”或“……中的至少一种”或“……中的至少一项”，表示所列出的各项的全部或任意组合，例如，“A、B和C中的至少一种”，可以表示：单独存在A，单独存在B，单独存在C，同时存在A和B，同时存在B和C，同时存在A、B和C这六种情况。
应理解，在本申请各实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而 前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。

Claims (47)

  1. 一种确定承载类型的方法，其特征在于，包括：
    辅网络设备接收主网络设备发送的第一消息；
    所述辅网络设备根据所述第一消息是否包括辅助信息，确定第一服务质量QoS流的承载类型，其中，所述第一QoS流对应的服务数据适应协议SDAP实体建立在所述辅网络设备上，所述承载类型包括主小区组MCG承载、辅小区组SCG承载或分离承载。
  2. 如权利要求1所述的方法，其特征在于，所述第一QoS流为保证比特速率GBR QoS流，所述辅助信息为第一GBR QoS参数，所述第一GBR QoS参数为所述主网络设备为所述第一QoS流提供的GBR QoS参数；
    以及，所述辅网络设备根据所述第一消息是否包括辅助信息，确定第一服务质量QoS流的承载类型，包括：
    若所述第一消息包括所述辅助信息，所述辅网络设备确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述辅助信息，所述辅网络设备确定所述第一QoS流的承载类型为所述SCG承载。
  3. 如权利要求2所述的方法，其特征在于，所述GBR QoS参数包括下述中的一种或多种：上行最大比特速率MBR、下行最大比特速率、上行GBR或者下行GBR。
  4. 如权利要求2或3所述的方法，其特征在于，所述第一消息还包括所述第一QoS流的第二GBR QoS参数，所述第二GBR QoS参数为所述主网络设备从核心网设备接收到的所述第一QoS流的GBR QoS参数。
  5. 如权利要求1所述的方法，其特征在于，所述第一QoS流为非保证比特速率
    non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR和第一协议数据单元PDU会话AMBR，其中，所述第一UE AMBR为所述主网络设备为目标UE建立在所述辅网络设备的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE，所述第一PDU会话AMBR为所述主网络设备为目标PDU会话中建立在所述辅网络设备的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
    以及，所述辅网络设备根据所述第一消息是否包括辅助信息，确定第一服务质量QoS流的承载类型，包括：
    若所述第一消息包括所述第一UE AMBR和所述第一PDU会话AMBR，所述辅网络设备确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述第一UE AMBR和所述第一PDU会话AMBR，所述辅网络设备确定所述第一QoS流的承载类型为所述SCG承载；和/或
    若所述第一消息包括所述第一UE AMBR，且不包括所述第一PDU会话AMBR，所述辅网络设备确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
    若所述第一消息包括所述第一PDU会话AMBR，且不包括所述第一UE AMBR，所述辅网络设备确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载。
  6. 如权利要求1所述的方法，其特征在于，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR，其中，所述第一UE AMBR为所述主网络设备为目标UE建立在所述辅网络设备的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE；
    以及，所述辅网络设备根据所述第一消息是否包括辅助信息，确定第一服务质量QoS流的承载类型，包括：
    若所述第一消息包括所述辅助信息，所述辅网络设备确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述辅助信息，所述辅网络设备确定所述第一QoS流的承载类型为所述SCG承载。
  7. 如权利要求1所述的方法，其特征在于，所述第一QoS流为非保证比特速率
    non-GBR QoS流，所述辅助信息为第一协议数据单元PDU会话AMBR，其中，所述第一PDU会话AMBR为所述主网络设备为目标PDU会话中建立在所述辅网络设备的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
    以及，所述辅网络设备根据所述第一消息是否包括辅助信息，确定第一服务质量QoS流的承载类型，包括：
    若所述第一消息包括所述辅助信息，所述辅网络设备确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述辅助信息，所述辅网络设备确定所述第一QoS流的承载类型为所述SCG承载。
  8. 如权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    所述辅网络设备向所述主网络设备发送承载类型指示信息，所述承载类型指示信息用于指示所述辅网络设备确定的所述第一QoS流的承载类型。
  9. 如权利要求8所述的方法，其特征在于，所述承载类型指示信息为所述辅网络设备为所述第一QoS流对应的承载分配的接收上行数据的上行传输网络层信息。
  10. 如权利要求1至9中任一项所述的方法，其特征在于，所述方法还包括：
    所述辅网络设备生成修改申请消息，所述修改申请消息用于申请修改所述第一QoS流对应的第一承载的承载类型；
    所述辅网络设备向主网络设备发送所述修改申请消息。
  11. 如权利要求10所述的方法，其特征在于，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修改的承载类型的信息，所述承载删除列表包括所述第一承载的标识。
  12. 一种确定承载类型的方法，其特征在于，包括：
    主网络设备根据是否在第一消息中包括辅助信息，生成第一消息；
    所述主网络设备向辅网络设备发送所述第一消息，所述第一消息用于所述辅网络设备确定第一服务质量QoS流的承载类型，其中，所述第一QoS流对应的服务数据适应协议 SDAP实体建立在所述辅网络设备上，所述承载类型包括主小区组MCG承载、辅小区组SCG承载或分离承载。
  13. 如权利要求12所述的方法，其特征在于，所述第一QoS流为保证比特速率GBR QoS流，所述辅助信息为第一GBR QoS参数，所述第一GBR QoS参数为所述主网络设备为所述第一QoS流提供的GBR QoS参数；
    以及，若所述第一消息包括所述辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成所述SCG承载。
  14. 如权利要求13所述的方法，其特征在于，所述GBR QoS参数包括下述中的一种或多种：上行最大比特速率MBR、下行最大比特速率、上行GBR或者下行GBR。
  15. 如权利要求13或14所述的方法，其特征在于，所述第一消息还包括所述第一QoS流的第二GBR QoS参数，所述第二GBR QoS参数为所述主网络设备从核心网设备接收到的所述第一QoS流的GBR QoS参数。
  16. 如权利要求12所述的方法，其特征在于，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR和第一协议数据单元PDU会话AMBR，其中，所述第一UE AMBR为所述主网络设备为目标UE建立在所述辅网络设备的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE，所述第一PDU会话AMBR为所述主网络设备为目标PDU会话中建立在所述辅网络设备的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
    以及，若所述第一消息包括所述第一UE AMBR和所述第一PDU会话AMBR，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；和/或
    若所述第一消息不包括所述第一UE AMBR和所述第一PDU会话AMBR，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成为所述SCG承载；和/或
    若所述第一消息包括所述第一UE AMBR，且不包括所述第一PDU会话AMBR，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；和/或
    若所述第一消息包括所述第一PDU会话AMBR，且不包括所述第一UE AMBR，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；
    其中，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载。
  17. 如权利要求12所述的方法，其特征在于，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR，其中，所述第一UE AMBR为所述主网络设备为目标UE建立在所述辅网络设备的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE；
    以及，若所述第一消息包括所述辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型，其中，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成为所述SCG承载。
  18. 如权利要求12所述的方法，其特征在于，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一协议数据单元PDU会话AMBR，所述第一PDU会话AMBR为所述主网络设备为目标PDU会话中建立在所述辅网络设备的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
    以及，若所述第一消息包括所述辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型，其中，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成为所述SCG承载。
  19. 如权利要求12至18中任一项所述的方法，其特征在于，所述方法还包括：
    所述主网络设备接收所述辅网络设备发送的承载类型指示信息，所述承载类型指示信息用于指示所述辅网络设备确定的所述第一QoS流的承载类型；
    所述主网络设备根据所述承载类型指示信息，确定所述第一QoS流的承载类型。
  20. 如权利要求19所述的方法，其特征在于，所述承载类型指示信息为所述辅网络设备为所述第一QoS流对应的承载分配的接收上行数据的上行传输网络层信息。
  21. 如权利要求12至20中任一项所述的方法，其特征在于，所述方法还包括：
    所述主网络设备接收所述辅网络设备发送的修改申请消息，所述修改申请消息用于申请修改所述第一QoS流对应的第一承载的承载类型；
    所述主网络设备向所述辅网络设备发送修改请求消息，所述修改请求消息用于指示所述主网络设备同意修改所述第一承载的承载类型。
  22. 如权利要求21所述的方法，其特征在于，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修改的承载类型的信息，所述承载删除列表包括所述第一承载的标识。
  23. 一种通信装置，其特征在于，包括：
    收发单元，用于接收主网络设备发送的第一消息；
    处理单元，用于根据所述第一消息是否包括辅助信息，确定第一服务质量QoS流的承载类型，其中，所述第一QoS流对应的服务数据适应协议SDAP实体建立在所述装置上，所述承载类型包括主小区组MCG承载、辅小区组SCG承载或分离承载。
  24. 如权利要求23所述的装置，其特征在于，所述第一QoS流为保证比特速率GBR QoS流，所述辅助信息为第一GBR QoS参数，所述第一GBR QoS参数为所述主网络设备为所述第一QoS流提供的GBR QoS参数；
    以及，所述处理单元具体用于：若所述第一消息包括所述辅助信息，确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述辅助信息，确定所述第一QoS流的承载类型为所述SCG 承载。
  25. 如权利要求24所述的装置，其特征在于，所述GBR QoS参数包括下述中的一种或多种：上行最大比特速率MBR、下行最大比特速率、上行GBR或者下行GBR。
  26. 如权利要求24或25所述的装置，其特征在于，所述第一消息还包括所述第一QoS流的第二GBR QoS参数，所述第二GBR QoS参数为所述主网络设备从核心网设备接收到的所述第一QoS流的GBR QoS参数。
  27. 如权利要求23所述的装置，其特征在于，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR和第一协议数据单元PDU会话AMBR，其中，所述第一UE AMBR为所述主网络设备为目标UE建立在所述通信装置的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE，所述第一PDU会话AMBR为所述主网络设备为目标PDU会话中建立在所述通信装置的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
    以及，所述处理单元具体用于：
    若所述第一消息包括所述第一UE AMBR和所述第一PDU会话AMBR，确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述第一UE AMBR和所述第一PDU会话AMBR，确定所述第一QoS流的承载类型为所述SCG承载；和/或
    若所述第一消息包括所述第一UE AMBR，且不包括所述第一PDU会话AMBR，确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
    若所述第一消息包括所述第一PDU会话AMBR，且不包括所述第一UE AMBR，确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载。
  28. 如权利要求23所述的装置，其特征在于，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR，其中，所述第一UE AMBR为所述主网络设备为目标UE建立在所述通信装置的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE；
    以及，所述处理单元具体用于：
    若所述第一消息包括所述辅助信息，确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述辅助信息，确定所述第一QoS流的承载类型为所述SCG承载。
  29. 如权利要求23所述的装置，其特征在于，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一协议数据单元PDU会话AMBR，其中，所述第一PDU会话AMBR为所述主网络设备为目标PDU会话中建立在所述通信装置的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
    以及，所述处理单元具体用于：
    若所述第一消息包括所述辅助信息，确定所述第一QoS流的承载类型为所述MCG承载、所述SCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述辅助信息，确定所述第一QoS流的承载类型为所述SCG承载。
  30. 如权利要求23至29中任一项所述的装置，其特征在于，所述收发单元还用于：向所述主网络设备发送承载类型指示信息，所述承载类型指示信息用于指示所述通信装置确定的所述第一QoS流的承载类型。
  31. 如权利要求30所述的装置，其特征在于，所述承载类型指示信息为所述通信装置为所述第一QoS流对应的承载分配的接收上行数据的上行传输网络层信息。
  32. 如权利要求23至31中任一项所述的装置，其特征在于，所述处理单元还用于，生成修改申请消息，所述修改申请消息用于申请修改所述第一QoS流对应的第一承载的承载类型；所述收发单元还用于：向主网络设备发送所述修改申请消息。
  33. 如权利要求32所述的装置，其特征在于，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修改的承载类型的信息，所述承载删除列表包括所述第一承载的标识。
  34. 一种通信装置，其特征在于，包括：
    处理单元，用于根据是否在第一消息中包括辅助信息，生成第一消息；
    收发单元，用于向辅网络设备发送所述第一消息，所述第一消息用于所述辅网络设备确定第一服务质量QoS流的承载类型，其中，所述第一QoS流对应的服务数据适应协议SDAP实体建立在所述辅网络设备上，所述承载类型包括主小区组MCG承载、辅小区组SCG承载或分离承载。
  35. 如权利要求34所述的装置，其特征在于，所述第一QoS流为保证比特速率GBR QoS流，所述辅助信息为第一GBR QoS参数，所述第一GBR QoS参数为所述通信装置为所述第一QoS流提供的GBR QoS参数；
    以及，若所述第一消息包括所述辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成所述SCG承载。
  36. 如权利要求35所述的装置，其特征在于，所述GBR QoS参数包括下述中的一种或多种：上行最大比特速率MBR、下行最大比特速率、上行GBR或者下行GBR。
  37. 如权利要求35或36所述的装置，其特征在于，所述第一消息还包括所述第一QoS流的第二GBR QoS参数，所述第二GBR QoS参数为所述装置从核心网设备接收到的所述第一QoS流的GBR QoS参数。
  38. 如权利要求34所述的装置，其特征在于，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR和第一协议数据单元PDU会话AMBR，其中，所述第一UE AMBR为所述通信装置为目标UE建立在所述辅网络设备的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE，所述第一PDU会话AMBR为所述通信装置为目标PDU会话中建立在所述辅网络设备的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
    以及，若所述第一消息包括所述第一UE AMBR和所述第一PDU会话AMBR，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；和/或
    若所述第一消息不包括所述第一UE AMBR和所述第一PDU会话AMBR，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成为所述SCG承载；和/或
    若所述第一消息包括所述第一UE AMBR，且不包括所述第一PDU会话AMBR，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；和/或
    若所述第一消息包括所述第一PDU会话AMBR，且不包括所述第一UE AMBR，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型；
    其中，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载。
  39. 如权利要求34所述的装置，其特征在于，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一用户设备聚合最大比特速率UE AMBR，其中，所述第一UE AMBR为所述通信装置为目标UE建立在所述辅网络设备的non-GBR QoS流提供的AMBR，所述目标UE为所述第一QoS流对应的UE；
    以及，若所述第一消息包括所述辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型，其中，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成为所述SCG承载。
  40. 如权利要求34所述的装置，其特征在于，所述第一QoS流为非保证比特速率non-GBR QoS流，所述辅助信息为第一协议数据单元PDU会话AMBR，所述第一PDU会话AMBR为所述通信装置为目标PDU会话中建立在所述辅网络设备的non-GBR QoS流QoS流提供的AMBR，所述目标PDU会话为所述第一QoS流对应的PDU会话；
    以及，若所述第一消息包括所述辅助信息，所述第一消息用于指示所述辅网络设备被允许将所述第一QoS流的承载类型配置成涉及MCG空口资源的承载类型，其中，所述涉及MCG空口资源的承载类型包括所述MCG承载或者所述分离承载；和/或
    若所述第一消息不包括所述辅助信息，所述第一消息用于指示所述辅网络设备将所述第一QoS流的承载类型配置成为所述SCG承载。
  41. 如权利要求34至40中任一项所述的装置，其特征在于，所述收发单元还用于：
    接收所述辅网络设备发送的承载类型指示信息，所述承载类型指示信息用于指示所述辅网络设备确定的所述第一QoS流的承载类型；所述处理单元还用于，确定所述第一QoS流的承载类型。
  42. 如权利要求41所述的装置，其特征在于，所述承载类型指示信息为所述辅网络设备为所述第一QoS流对应的承载分配的接收上行数据的上行传输网络层信息。
  43. 如权利要求34至42中任一项所述的装置，其特征在于，所述收发单元还用于：
    接收所述辅网络设备发送的修改申请消息，所述修改申请消息用于申请修改所述第一 QoS流对应的第一承载的承载类型；向所述辅网络设备发送修改请求消息，所述修改请求消息用于指示所述通信装置同意修改所述第一承载的承载类型。
  44. 如权利要求43所述的装置，其特征在于，所述修改申请消息包括承载建立列表和承载删除列表，所述承载建立列表包括所述第一承载的标识和指示所述第一承载需要修改的承载类型的信息，所述承载删除列表包括所述第一承载的标识。
  45. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至11中任一项或12至22中任一项所述的方法。
  46. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有程序或指令，当所述程序或指令被运行时，实现如权利要求1至11中任一项或12至22中任一项所述的方法。
  47. 一种通信系统，其特征在于，包括如权利要求23至33中任一项，和/或，如权利要求34至44中任一项所述的通信装置。
PCT/CN2020/081709 2019-03-29 2020-03-27 确定承载类型的方法和通信装置 WO2020200103A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910252564.7 2019-03-29
CN201910252564.7A CN111757347B (zh) 2019-03-29 2019-03-29 确定承载类型的方法和通信装置

Publications (1)

Publication Number Publication Date
WO2020200103A1 true WO2020200103A1 (zh) 2020-10-08

Family

ID=72664716

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/081709 WO2020200103A1 (zh) 2019-03-29 2020-03-27 确定承载类型的方法和通信装置

Country Status (2)

Country Link
CN (1) CN111757347B (zh)
WO (1) WO2020200103A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114286384A (zh) * 2021-12-30 2022-04-05 中国联合网络通信集团有限公司 服务质量协商方法和装置
WO2024082361A1 (en) * 2022-11-11 2024-04-25 Lenovo (Beijing) Limited Method and apparatus of data transmission

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019004396A1 (ja) * 2017-06-28 2019-01-03 シャープ株式会社 端末装置、基地局装置、通信方法、および、集積回路

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4114131A1 (en) * 2017-03-24 2023-01-04 Samsung Electronics Co., Ltd. Methods, primary base station and secondary base station for data transmission in a wireless communication system
CN109246833B (zh) * 2017-05-04 2024-02-06 中兴通讯股份有限公司 承载配置确定、信息发送方法及装置、主基站和辅基站
CN109151914B (zh) * 2017-06-16 2024-04-12 华为技术有限公司 一种通信方法及接入网设备

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019004396A1 (ja) * 2017-06-28 2019-01-03 シャープ株式会社 端末装置、基地局装置、通信方法、および、集積回路

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
HUAWEI.: "3GPP TSG-RAN3 Meeting #103bis, R3-191603.", DETERMINATION OF BEARER TYPE BY SN., 30 March 2019 (2019-03-30), XP051695054, DOI: 20200526155018PX *
SAMSUNG.: "3GPP TSG-RAN WG3 #98, R3-174565.", STAGE 2TP FOR SCG CHANGE RELATED TO BEARER TYPE CHANGE., 17 November 2017 (2017-11-17), XP051373163, DOI: 20200526155723Y *
ZTE CORPORATION.: "3GPP TSG-RAN WG2 Meeting #103, R2-1811736.", DISCUSSION ON THE QOS ASPECTS FOR MR-DC., 10 August 2018 (2018-08-10), XP051521375, DOI: 20200526155033PX *
ZTE CORPORATION.: "3GPP TSG-RAN WG2 Meeting #103, R2-1811736.", DISCUSSION ON THE QOS ASPECTS FOR MR-DC., 10 August 2018 (2018-08-10), XP051521375, DOI: 20200526155707X *

Also Published As

Publication number Publication date
CN111757347B (zh) 2023-07-18
CN111757347A (zh) 2020-10-09

Similar Documents

Publication Publication Date Title
US11917450B2 (en) Data transmission method and data transmission apparatus
JP6904419B2 (ja) 無線アクセスネットワークノード、コアネットワークノード、及び無線端末並びにこれらの方法
WO2022016401A1 (zh) 通信方法和通信装置
US20160234851A1 (en) Data transmission apparatus and method
US11265755B2 (en) Communication methods, apparatuses, and systems for managing quality of service flows
WO2013075602A1 (zh) 实现载波聚合的方法、基站和用户设备
WO2020164615A1 (zh) 一种通信方法及相关设备
EP3664507A1 (en) Communication method, base station, terminal device and system
WO2021218888A1 (zh) 通信方法和装置
CN114071564B (zh) 用户终端与网络进行通信的方法、终端、网络设备及装置
WO2020200103A1 (zh) 确定承载类型的方法和通信装置
US20230086410A1 (en) Communication method and communication apparatus
US20240154715A1 (en) Wireless communication method and apparatus
US20220369154A1 (en) Method and apparatus for indicating qos flow information
US20220217549A1 (en) Communication Method, Apparatus, and System
WO2022236681A1 (zh) 通信方法及装置
CN112020056B (zh) 切换的方法、装置和通信系统
WO2019153210A1 (zh) 用于上行和下行的数据传输的方法和装置
WO2022228389A1 (zh) 一种通信方法及通信装置
WO2024016141A1 (zh) 一种计算隧道的建立方法及相关装置
WO2023015950A1 (zh) 一种通信方法和通信装置
WO2024082361A1 (en) Method and apparatus of data transmission
WO2022148205A1 (zh) 多连接下的切换方法和装置
WO2023005887A1 (zh) QoS参数配置方法、设备、装置及存储介质
US20230254859A1 (en) Downlink Transmission Method and Communication Apparatus

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

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

Country of ref document: EP

Kind code of ref document: A1