WO2019096117A1 - 消息、策略发送方法及装置，存储介质，处理器 - Google Patents

消息、策略发送方法及装置，存储介质，处理器 Download PDF

Info

Publication number
WO2019096117A1
WO2019096117A1 PCT/CN2018/115197 CN2018115197W WO2019096117A1 WO 2019096117 A1 WO2019096117 A1 WO 2019096117A1 CN 2018115197 W CN2018115197 W CN 2018115197W WO 2019096117 A1 WO2019096117 A1 WO 2019096117A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
network element
data radio
cause value
radio bearer
Prior art date
Application number
PCT/CN2018/115197
Other languages
English (en)
French (fr)
Inventor
王昕�
黄河
马子江
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP18877695.9A priority Critical patent/EP3713337B1/en
Publication of WO2019096117A1 publication Critical patent/WO2019096117A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/32—Release of transport tunnels

Definitions

  • the present disclosure relates to the field of communications, and in particular to a message, a policy sending method and apparatus, a storage medium, and a processor.
  • the communication network in the related art has a widely deployed fourth generation (4G) communication system and a fifth generation (5G) communication system initially deployed.
  • the core network of the 4G system is an evolved packet core network (Evolved Packet Core, EPC for short), and the radio access network (Radio Access Network, RAN for short) is deployed on the radio interface to use the evolved universal terrestrial radio access.
  • the core network of the 5G system is a 5G core network (5G Core Network, 5GC for short), and the RAN is deployed in the wireless network.
  • a next generation base station (Generation Node B, gNB for short), which is connected to the new radio (NR), is also deployed with a Next Generation eNB (hereinafter referred to as ng-eNB).
  • ng-eNB Next Generation eNB
  • FIG. 1 is a schematic structural diagram of a dual connectivity network in the related art.
  • the type and configuration of the DRB has evolved and expanded.
  • the base station service mode and the control plane signaling procedure in the related art still maintain the original concept.
  • the second network element establishes at least one lower layer entity (RLC entity and MAC entity) of the DRB, and the second network element also establishes at least one serving cell for the UE; Further, the second network element may also establish an SRB (referred to as SRB3) with the UE.
  • RLC entity and MAC entity lower layer entity
  • SRB3 SRB
  • the second network element when the second network element decides to release at least one DRB, the second network element may instruct to release the SCG bearer or the SCG split bearer in all L2 protocol stacks of the second network element. Drop it. From the perspective of the UE, after accessing the second network element, the UE also maintains monitoring of the second network element serving cell to detect possible radio link failure. It can be seen that the existing communication mode and the signaling procedure do not match the evolved bearer type (such as the bearer type separated by the upper and lower protocol entities), and the access network is also difficult to implement hierarchical and highly flexible wireless. Resource management.
  • the evolved bearer type such as the bearer type separated by the upper and lower protocol entities
  • the embodiments of the present disclosure provide a message, a policy sending method, and a device, a storage medium, and a processor, to at least solve the problem that the radio resource management on the network element is not flexible enough in the related art.
  • a message sending method including: determining to release or modify a first data radio bearer or a designated network element; and sending a first message to a first network element, where the first message carries a release Or modifying the cause value of the first data radio bearer or the designated network element; the cause value is used by the first network element to reconfigure the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the specified network element.
  • the cause value includes at least one of the following: a first cause value, where the first cause value is used to indicate that the quality of the wireless channel between the specified network element and the terminal is lower than a first predetermined threshold; the second cause value, the second cause value The load of the packet data convergence protocol PDCP entity and/or the service data adaptation protocol SDAP entity of the specified network element is greater than a second predetermined threshold; the third cause value is used to indicate that the radio resource load of the designated network element is greater than a third predetermined threshold; wherein the designated network element is the sender of the first message.
  • the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the designated network element is one of the following: the secondary cell group carries the SCG bearer, and the secondary cell The group splits the bearer SCG split bearer, the primary cell group separates the bearer MCG split bearer, and the primary cell group carries the MCG inter-NB bearer across the station; if the cause value includes the second cause value, the bearer type or designation of the first data radio bearer
  • the bearer type of the data radio bearer on the network element is one of the following: SCG bearer, SCG split bearer, SCG inter-NB bearer; in the case where the cause value includes the third cause value, the bearer type or designation of the first data radio bearer
  • the bearer type of the data radio bearer on the NE is one of the following: SCG bearer, MCG inter-NB bearer.
  • the method further includes: receiving the second message sent by the first network element, where the second message carries the bearer of the first data element to the first data radio bearer The type or the policy of the reconfiguration management of the bearer type of the data radio bearer on the specified NE.
  • the policy includes at least one of the following: the bearer type of the first data radio bearer or the bearer of the data radio bearer on the designated network element if the specified network element needs to be reserved and the cause value includes the first cause value
  • the type is reconfigured as the SCG inter-NB bearer or the MCG bearer; if the specified network element needs to be reserved and the cause value includes the second cause value, the bearer type of the first data radio bearer or the data radio bearer on the designated network element
  • the bearer type is reconfigured to one of the following three bearer types: MCG bearer, MCG split bearer, MCG inter-NB bearer; in the case where the specified network element needs to be reserved and the cause value includes the third reason, the first data is wireless.
  • the bearer type of the bearer or the bearer type of the data radio bearer on the specified network element is reconfigured as the MCG split bearer or the SCG split bearer; the bearer type of the data radio bearer of the first data radio bearer or the designated network element is released; the specified network element is released. ;Switch the specified network element.
  • the method further includes: determining, in the case that the bearer type of all data radio bearers established by the specified network element for the specified user equipment is an SCG inter-NB bearer, whether to establish or delete at least one of the following objects: a lower layer entity, a serving cell, a signaling radio bearer between the user equipment and the designated user equipment; wherein the lower layer entity includes: a radio link control RLC entity, and a medium access control MAC entity.
  • determining whether to establish or delete an object by using at least one of: determining whether to establish or delete an object according to the indication information sent by the first network element for indicating whether to establish or delete an object; determining whether to establish or according to a communication protocol Delete an object; only the specified NE determines whether to create or delete an object.
  • the establishment object is determined; if the target cell information is not included in the indication information, it is determined that the object is not established.
  • a method for sending a policy including: receiving a first message sent by a specified network element, where the first message carries a release or modification of the first data radio bearer or specified by the specified network element.
  • the reason for the reconfiguration of the bearer type of the data radio bearer on the first data radio bearer or the specified network element is determined according to the cause value; the determined policy is sent to the designated network element.
  • the cause value includes at least one of the following: a first cause value, where the first cause value is used to indicate that the quality of the wireless channel between the specified network element and the terminal is lower than a first predetermined threshold; the second cause value, the second cause value The load of the packet data convergence protocol PDCP entity and/or the service data adaptation protocol SDAP entity of the specified network element is greater than a second predetermined threshold; the third cause value is used to indicate that the radio resource load of the designated network element is greater than The third predetermined threshold.
  • the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the designated network element is one of the following: the secondary cell group carries the SCG bearer, and the secondary cell The group splits the bearer SCG split bearer, the primary cell group separates the bearer MCG split bearer, and the primary cell group carries the MCG inter-NB bearer across the station; if the cause value includes the second cause value, the bearer type or designation of the first data radio bearer
  • the bearer type of the data radio bearer on the network element is one of the following: SCG bearer, SCG split bearer, SCG inter-NB bearer; in the case where the cause value includes the third cause value, the bearer type or designation of the first data radio bearer
  • the bearer type of the data radio bearer on the NE is one of the following: SCG bearer, MCG inter-NB bearer.
  • the policy for determining reconfiguration management of the bearer type of the data radio bearer on the first data radio bearer or the designated network element includes at least one of the following: the specified network element needs to be reserved and the cause value includes the first cause value
  • the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the designated network element is reconfigured as an SCG inter-NB bearer or an MCG bearer; the specified network element needs to be reserved and the reason If the value includes the second cause value, the determining policy is: reconfiguring the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the specified network element into one of the following three bearer types: MCG bearer, MCG
  • the determining policy is: the bearer type of the first data radio bearer or the radio bearer of the data on the designated network element.
  • the bearer type is reconfigured as an MCG split bearer or an SCG split bearer; the policy is determined to release the first data radio bearer or the designated network element.
  • the method further includes: if the bearer type of all the data radio bearers established by the specified network element for the specified user equipment is an SCG inter-NB bearer, sending, to the designated network element, indicating whether the specified network element is established. Or deleting the message of at least one of the following objects: a lower layer entity, a serving cell, and a signaling radio bearer between the specified user equipment; wherein the lower layer entity includes: a radio link control RLC entity, and a medium access control MAC entity.
  • a message sending apparatus including: a first determining module, configured to determine to release or modify a first data radio bearer or a designated network element; and a sending module configured to send to the first network element a first message, where the first message carries a cause value for releasing or modifying the first data radio bearer or the designated network element; the cause value is used by the first network element for the bearer type of the first data radio bearer or the designated network element
  • the bearer type of the data radio bearer is reconfigured.
  • the device further includes: a receiving module, configured to receive the second message sent by the first network element, where the second message carries the bearer type of the first data element to the first data radio bearer or the designated network element A policy for reconfiguration management of the bearer type of the data radio bearer.
  • a receiving module configured to receive the second message sent by the first network element, where the second message carries the bearer type of the first data element to the first data radio bearer or the designated network element A policy for reconfiguration management of the bearer type of the data radio bearer.
  • the device further includes: a second determining module, configured to determine whether to establish or delete the following if the bearer type of all data radio bearers established by the specified network element for the specified user equipment is SCG inter-NB bearer At least one object: a lower layer entity, a serving cell, and a signaling radio bearer between the specified user equipment; wherein the lower layer entity includes: a radio link control RLC entity, and a medium access control MAC entity.
  • a second determining module configured to determine whether to establish or delete the following if the bearer type of all data radio bearers established by the specified network element for the specified user equipment is SCG inter-NB bearer At least one object: a lower layer entity, a serving cell, and a signaling radio bearer between the specified user equipment; wherein the lower layer entity includes: a radio link control RLC entity, and a medium access control MAC entity.
  • a policy sending apparatus including: a receiving module, configured to receive a first message sent by a specified network element, where the first message carries a release or modification determined by the specified network element.
  • the determining module is configured to determine, according to the cause value, a policy for reconfiguring the bearer type of the data radio bearer of the first data radio bearer or the designated network element;
  • the first sending The module is set to send the determined policy to the specified network element.
  • the device further includes: a second sending module, configured to send, to the designated network element, the bearer type of all the data radio bearers established by the specified network element for the specified user equipment is the SCG inter-NB bearer Indicates whether the specified network element establishes or deletes at least one of the following objects: a lower layer entity, a serving cell, and a signaling radio bearer between the specified user equipment; wherein the lower layer entity includes: a radio link control RLC entity, and media access control MAC entity.
  • a second sending module configured to send, to the designated network element, the bearer type of all the data radio bearers established by the specified network element for the specified user equipment is the SCG inter-NB bearer Indicates whether the specified network element establishes or deletes at least one of the following objects: a lower layer entity, a serving cell, and a signaling radio bearer between the specified user equipment; wherein the lower layer entity includes: a radio link control RLC entity, and media access control MAC entity.
  • a storage medium comprising a stored program, wherein the program is executed to perform the method of any of the above.
  • a processor for running a program wherein the program is executed to perform the method of any of the above.
  • the first message is sent to the first network element by transmitting or modifying the first data radio bearer or the designated network element, wherein the first message carries the release or modification of the first data radio bearer or the designated network element.
  • the cause value is such that the first network element can reconfigure the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the specified network element based on the cause value, and can be applied to the evolution and expansion of the data radio bearer.
  • the flexible management of the radio resource of the specified network element or the sender of the first message is implemented. Therefore, the problem that the radio resource management on the network element is not flexible enough in the related art can be solved, and the specified network element or the first is improved. The effect of the utilization of the resource of the sender of the message.
  • FIG. 1 is a schematic structural diagram of a dual connectivity network in the related art
  • 2(a) is a schematic diagram of a DRB bearer type MCG Split bearer and SCG Split bearer
  • 2(b) is a schematic diagram of the DRB bearer type MCG bearer and SCG bearer;
  • 2(c) is a schematic diagram of the DRB bearer type MCG inter-NB bearer and SCG inter-NB bearer;
  • FIG. 3 is a flowchart of a method for sending a message according to an embodiment of the present disclosure
  • FIG. 4 is a flowchart of a method for sending a policy according to an embodiment of the present disclosure
  • FIG. 5 is a structural block diagram of a message sending apparatus according to an embodiment of the present disclosure.
  • FIG. 6 is a structural block diagram of a policy sending apparatus according to an embodiment of the present disclosure.
  • FIG. 7 is a flow chart showing a method according to a preferred embodiment 1 of the present disclosure.
  • FIG. 8 is a flow chart showing a method according to a preferred embodiment 2 of the present disclosure.
  • FIG. 9 is a flow chart showing a method according to a preferred embodiment 3 of the present disclosure.
  • FIG. 10 is a flow diagram of a method provided in accordance with a preferred embodiment 4 of the present disclosure.
  • a base station that establishes a Control Plane (CP) interface for the UE with the core network is called a Master Node (MN), which may also be called a first network element, and the other is only
  • MN Master Node
  • a base station that provides additional radio resources for the UE is called a secondary node (SN), and may also be called a second network element.
  • At least one of the first and second network elements establishes a user plane interface (UP) for the UE with the core network, and the two network elements usually have a non-ideal wired interface (called The X2 or Xn interface is connected; on the wireless interface, the two network elements can use the same or different Radio Access Technology (RAT), wherein the network mode using different RATs is called multi-RAT dual Multi RAT Dual Connectivity (MR-DC) network.
  • UP user plane interface
  • RAT Radio Access Technology
  • a Layer 2 (L2) protocol stack of a Radio Bearer mainly includes a Packet Data Convergence Protocol (PDCP) entity and a wireless chain. Radio Link Control (RLC) entity and Medium Access Control (MAC) entity.
  • RLC Radio Link Control
  • MAC Medium Access Control
  • RRC Radio Resource Control
  • the complete L2 protocol stack further includes a Service Data Adaptation Protocol (SDAP) entity located above the PDCP entity.
  • SDAP Service Data Adaptation Protocol
  • the DRBs can be classified into different bearer types.
  • the L2 protocol stack of a DRB can be configured on two service network elements respectively, as shown in Figure 2(a), where Figure 2(a) shows that the bearer type of the DRB is MCG Split bearer and SCG.
  • a schematic diagram of a split bearer where the DRB is configured with two sets of RLC entities and MAC entities, and are relatively independent, respectively located in two service network elements, wherein the UP interface is terminated in the first network element and the PDCP entity (optional, The DRB of the first network element is also referred to as a primary cell group split bearer (MCG split bearer), and the UP interface is terminated by the second network element and the PDCP entity (optional, The DRB of the second network element is also referred to as a secondary cell group split bearer (SCG split bearer).
  • MCG split bearer primary cell group split bearer
  • SCG split bearer secondary cell group split bearer
  • the L2 protocol stack of a certain DRB may be completely configured on only one service network element, as shown in FIG. 2(b), wherein FIG.
  • the DRB bearer type is MCG bearer and SCG bearer.
  • the schematic diagram wherein the UP interface is terminated in the first network element, and the DRB of the L2 protocol stack only in the first network element is called a primary cell group bearer (MCG bearer), and the UP interface is terminated in the second network element. And the DRB of the L2 protocol stack only in the second network element is called a secondary cell group bearer (SCG bearer).
  • MCG bearer primary cell group bearer
  • SCG bearer secondary cell group bearer
  • the above four DRB bearer types are designed by the Bearer Type Harmonisation, that is, the UE does not distinguish the access network corresponding to the PDCP entity (and the optional SDAP entity).
  • the network element and the bearer type can be configured with the NR PDCP entity, which means that the MCG split bearer and the SCG split bearer belong to the same bearer type for the UE; from another perspective, the PDCP entity (and
  • the selected SDAP which is referred to as the upper layer entity in this patent, is decoupled to some extent from the RLC entity and the MAC entity (referred to as the underlying entity in this patent).
  • FIG. 2(c) is a schematic diagram of the bearer type of the DRB being MCG inter-NB bearer and SCG inter-NB bearer, wherein the UP interface is terminated in the first network element, and The lower layer entity in the L2 protocol stack is only the DRB of the second network element, which is called the primary cell group cross-station bearer (MCG inter-NB bearer), and the UP interface is terminated by the second network element and the L2 protocol stack.
  • MCG inter-NB bearer primary cell group cross-station bearer
  • the lower layer entity in the middle only the DRB located in the first network element is called the SCG inter-NB bearer.
  • FIG. 3 is a flowchart of a message sending method according to an embodiment of the present disclosure. As shown in FIG. 3, the process includes the following steps. :
  • Step S302 determining to release or modify the first data radio bearer or the designated network element
  • Step S304 the first message is sent to the first network element, where the first message carries the cause value of releasing or modifying the first data radio bearer or the designated network element; the cause value is used by the first network element to the first data radio bearer.
  • the bearer type or the bearer type of the data radio bearer on the specified network element is reconfigured.
  • the first message is sent to the first network element by releasing or modifying the first data radio bearer or the designated network element by using the foregoing step, by determining to release or modify the first data radio bearer or the designated network element.
  • the cause value is such that the first network element can reconfigure the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the specified network element based on the cause value, and can be applied to the evolution and expansion of the data radio bearer.
  • the flexible management of the radio resource of the specified network element or the sender of the first message is implemented. Therefore, the problem that the radio resource management on the network element is not flexible enough in the related art can be solved, and the specified network element or the first is improved. The effect of the utilization of the resource of the sender of the message.
  • the data radio bearer on the specified network element may refer to a part of the data radio bearer or all data radio bearers on the specified network element, and is not limited thereto. It should be noted that the foregoing partial data radio bearers may be one or more data radio bearers.
  • the foregoing cause value may include at least one of the following: a first cause value, where the first cause value is used to indicate that a quality of a radio channel between the specified network element and the terminal is lower than a first predetermined threshold; a second cause value, The second cause value is used to indicate that the load of the packet data convergence protocol PDCP entity and/or the service data adaptation protocol SDAP entity of the specified network element is greater than a second predetermined threshold; the third cause value is used to indicate the wireless of the specified network element.
  • the resource load is greater than a third predetermined threshold; wherein the designated network element is the sender of the first message.
  • the specified network element may be the second network element shown in FIG. 1 .
  • the quality of the radio channel between the specified network element and the terminal is lower than the first predetermined threshold, and the quality of the radio channel is poor (the air interface quality is poor), and the packet data convergence protocol PDCP entity and/or service of the designated network element is required.
  • the load of the data adaptation protocol SDAP entity is greater than the second predetermined threshold.
  • the PDCP overload or the SDAP overload may be considered.
  • the radio resource load of the designated network element is greater than the third predetermined threshold, and may be considered as UE lost. That is, the first cause value may be a poor air interface quality, and the second cause value may be a PDCP overload or a SDAP overload, and the third cause value may be a UE lost.
  • the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the designated network element is one of the following: the secondary cell group carries the SCG bearer, The secondary cell group separates the bearer of the SCG split bearer, and the primary cell group separates the bearer MCG split bearer, and the primary cell group carries the MCG inter-NB bearer; if the cause value includes the second cause value, the bearer of the first data radio bearer
  • the bearer type of the data radio bearer of the type or the specified network element is one of the following: SCG bearer, SCG split bearer, SCG inter-NB bearer; in the case where the above cause value includes the third cause value, the first data radio bearer
  • the bearer type or the bearer type of the data radio bearer on the specified NE is one of the following: SCG bearer, MCG inter-NB bearer.
  • the method may further include: receiving a second message sent by the first network element, where the second message carries the first network element to the first data radio bearer A policy of reconfiguration management for the bearer type or the bearer type of the data radio bearer on the specified network element.
  • the foregoing policy includes at least one of the following: when the specified network element needs to be reserved and the cause value includes the first cause value, the bearer type of the first data radio bearer or the data radio bearer on the designated network element.
  • the bearer type of the bearer is reconfigured as the SCG inter-NB bearer or the MCG bearer; if the specified network element needs to be reserved and the cause value includes the second cause value, the bearer type of the first data radio bearer or the data on the specified network element
  • the bearer type of the radio bearer is reconfigured to one of the following three types of bearers: MCG bearer, MCG split bearer, MCG inter-NB bearer; in the case where the specified network element needs to be reserved and the cause value includes the third cause, the first
  • the bearer type of the data radio bearer or the bearer type of the data radio bearer on the specified network element is reconfigured as an MCG split bearer or SCG split bearer; the bearer type of the data radio bearer of the first data radio bearer or the
  • the reconfiguration of the bearer type may be performed by releasing or reconfiguring an entity in a specified network element, for example, reconfiguring a bearer type of a data radio bearer from an SCG bearer to an SCG inter-NB bearer. If the data radio bearer is located in the upper layer entity of the specified network element, the upper layer entity is reconfigured to the first network element; the reconfiguration of the bearer type of the other data radio bearers is similar, and details are not described herein again.
  • the method may further include: determining, in the case that the bearer type of all data radio bearers established by the specified network element for the specified user equipment is an SCG inter-NB bearer, whether to establish or delete at least the following: One object: a lower layer entity, a serving cell, and a signaling radio bearer between the specified user equipment; wherein the lower layer entity includes: a radio link control RLC entity, and a medium access control MAC entity.
  • execution order of determining whether to create or delete the above object may be performed before or after the above step S304, or may be performed simultaneously with step S304, but is not limited thereto.
  • the foregoing establishment may be performed to establish the foregoing object again on the basis that the specified network element does not establish the foregoing object, and may also be expressed as that the foregoing object needs to be added on the specified network element, but is not limited to this.
  • whether to establish or delete an object may be determined according to at least one of the following: determining whether to establish or delete an object according to the indication information sent by the first network element for indicating whether to establish or delete an object; determining whether according to a communication protocol Create or delete an object; determine whether to create or delete an object only by the specified NE.
  • whether the object is established by using the foregoing indication information, or whether the object is established by using an implicit manner, for example, whether the target cell information is found in the indication information may be used to determine whether to establish an object, specifically, When the target information includes the target cell information (target cell information), the establishment object is determined; if the target information is not included in the indication information, it is determined that the object is not established.
  • execution body of the above steps may be the second network element shown in FIG. 1 above, but is not limited thereto.
  • FIG. 4 is a flowchart of a method for sending a policy according to an embodiment of the present disclosure. As shown in FIG. 4, the process includes the following steps:
  • Step S402 receiving a first message sent by the specified network element, where the first message carries a reason value for releasing or modifying the first data radio bearer or the designated network element determined by the specified network element;
  • Step S404 determining, according to the cause value, a policy for reconfiguring a bearer type of a data radio bearer on a first data radio bearer or a designated network element;
  • Step S406 the determined policy is sent to the designated network element.
  • the reconfiguration management of the bearer type of the data radio bearer or the bearer type of the data radio bearer on the specified network element can be applied to the evolution and extension of the data radio bearer, and realizes the wireless of the specified network element or the sender of the first message.
  • the flexible management of the resources can solve the problem that the radio resource management on the network element is not flexible enough in the related art, and the effect of utilizing the resources of the designated network element is improved.
  • the specified network element may be the second network element.
  • the data radio bearer on the specified network element may refer to a part of the data radio bearer or all data radio bearers on the specified network element, and is not limited thereto. It should be noted that the foregoing partial data radio bearers may be one or more data radio bearers.
  • the foregoing cause value includes at least one of the following: a first cause value, where the first cause value is used to indicate that a quality of a radio channel between the specified network element and the terminal is lower than a first predetermined threshold; a second cause value, and a second The cause value is used to indicate that the load of the packet data convergence protocol PDCP entity and/or the service data adaptation protocol SDAP entity of the specified network element is greater than a second predetermined threshold; the third cause value is used to indicate the radio resource of the designated network element. The load is greater than the third predetermined threshold.
  • the quality of the radio channel between the specified network element and the terminal is lower than the first predetermined threshold, and the quality of the radio channel is poor (the air interface quality is poor), and the packet data convergence protocol PDCP entity and/or service of the designated network element is required.
  • the load of the data adaptation protocol SDAP entity is greater than the second predetermined threshold.
  • the PDCP overload or the SDAP overload may be considered.
  • the radio resource load of the designated network element is greater than the third predetermined threshold, and may be considered as UE lost. That is, the first cause value may be a poor air interface quality, and the second cause value may be a PDCP overload or a SDAP overload, and the third cause value may be a UE lost.
  • the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the designated network element is one of the following: the secondary cell group carries the SCG bearer, The secondary cell group separates the bearer SCG split bearer, the primary cell group separates the bearer MCG split bearer, and the primary cell group carries the MCG inter-NB bearer across the station; if the cause value includes the second cause value, the bearer type of the first data radio bearer Or the bearer type of the data radio bearer on the specified network element is one of the following: SCG bearer, SCG split bearer, SCG inter-NB bearer; in the case that the reason value includes the third cause value, the bearer of the first data radio bearer
  • the bearer type of the data radio bearer of the type or the specified network element is one of the following: SCG bearer, MCG inter-NB bearer.
  • the foregoing step S404 may include at least one of the following: in the case that the specified network element needs to be reserved and the cause value includes the first cause value, determining that the policy is: carrying the first data radio bearer
  • the type or the bearer type of the data radio bearer on the specified NE is reconfigured to SCG inter-NB bearer or MCG bearer. If the specified NE needs to be reserved and the cause value includes the second cause value, the policy is:
  • the bearer type of the data radio bearer or the bearer type of the data radio bearer on the specified network element is reconfigured into one of the following three bearer types: MCG bearer, MCG split bearer, MCG inter-NB bearer; the specified NE needs to be reserved.
  • the determining policy is: reconfiguring the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the designated network element as an MCG split bearer or an SCG split bearer; Release the bearer type of the data radio bearer of the first data radio bearer or the designated network element; determine the policy to release the designated network ; Determining policy for the specified switching network elements.
  • the reconfiguration of the bearer type may be performed by releasing or reconfiguring an entity in a specified network element, for example, reconfiguring a bearer type of a data radio bearer from an SCG bearer to an SCG inter-NB bearer. If the data radio bearer is located in the upper layer entity of the specified network element, the upper layer entity is reconfigured to the network element of the receiver of the first message; the reconfiguration of the bearer type of other data radio bearers is similar. I won't go into details here.
  • the method may further include: sending, to the designated network element, that the bearer type of all data radio bearers established by the specified network element for the specified user equipment is SCG inter-NB bearer The message indicating whether the specified network element establishes or deletes at least one of the following objects: a lower layer entity, a serving cell, and a signaling radio bearer between the specified user equipment; wherein the lower layer entity includes: a radio link control RLC entity, media access Control the MAC entity.
  • the foregoing establishment may be performed to establish the foregoing object again on the basis that the specified network element does not establish the foregoing object, and may also be expressed as that the foregoing object needs to be added on the specified network element, but is not limited to this.
  • whether the object is created or deleted is directly indicated by the foregoing message, and whether the object is created or deleted is determined in an implicit manner. For example, whether the object is created or deleted may be determined by determining whether the target cell information appears in the message. Specifically, in the case that the target cell information (target cell information) is included in the foregoing message, the designated network element determines the establishment or deletion object; if the target cell information is not included in the message, the designated network element determines not to establish or delete Object.
  • target cell information target cell information
  • the specified network element may further determine whether to establish or delete an object by using at least one of the following: determining whether to create or delete an object according to a specification of a communication protocol; determining whether to create or delete an object only by the second network element.
  • execution body of the above steps may be the first network element shown in FIG. 1 above, but is not limited thereto.
  • a message sending device is also provided, which is used to implement the foregoing embodiments and preferred embodiments, and has not been described again.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 5 is a structural block diagram of a message sending apparatus according to an embodiment of the present disclosure. As shown in FIG. 5, the apparatus includes:
  • the first determining module 52 is configured to determine to release or modify the first data radio bearer or the designated network element
  • the sending module 54 is connected to the first determining module 52, and is configured to send a first message to the first network element, where the first message carries a reason value for releasing or modifying the first data radio bearer or the designated network element;
  • the first network element performs reconfiguration management on the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the designated network element.
  • the first message is sent to the first network element by releasing or modifying the first data radio bearer or the designated network element by using the foregoing apparatus, by determining to release or modify the first data radio bearer or the designated network element;
  • the cause value is such that the first network element can reconfigure the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the specified network element based on the cause value, and can be applied to the evolution and expansion of the data radio bearer.
  • the data radio bearer on the specified network element may refer to a part of the data radio bearer or all data radio bearers on the specified network element, and is not limited thereto. It should be noted that the foregoing partial data radio bearers may be one or more data radio bearers.
  • the foregoing cause value may include at least one of the following: a first cause value, where the first cause value is used to indicate that a quality of a radio channel between the specified network element and the terminal is lower than a first predetermined threshold; a second cause value, The second cause value is used to indicate that the load of the packet data convergence protocol PDCP entity and/or the service data adaptation protocol SDAP entity of the specified network element is greater than a second predetermined threshold; the third cause value is used to indicate the wireless of the specified network element.
  • the resource load is greater than a third predetermined threshold; wherein the designated network element is the sender of the first message.
  • the sender of the first message may be the foregoing device, or may be the second network element shown in FIG. 1 .
  • the quality of the radio channel between the specified network element and the terminal is lower than the first predetermined threshold, and the quality of the radio channel is poor (the air interface quality is poor), and the packet data convergence protocol PDCP entity and/or service of the designated network element is required.
  • the load of the data adaptation protocol SDAP entity is greater than the second predetermined threshold.
  • the PDCP overload or the SDAP overload may be considered.
  • the radio resource load of the designated network element is greater than the third predetermined threshold, and may be considered as UE lost. That is, the first cause value may be a poor air interface quality, and the second cause value may be a PDCP overload or a SDAP overload, and the third cause value may be a UE lost.
  • the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the designated network element is one of the following: the secondary cell group carries the SCG bearer, The secondary cell group separates the bearer of the SCG split bearer, and the primary cell group separates the bearer MCG split bearer, and the primary cell group carries the MCG inter-NB bearer; if the cause value includes the second cause value, the bearer of the first data radio bearer
  • the bearer type of the data radio bearer of the type or the specified network element is one of the following: SCG bearer, SCG split bearer, SCG inter-NB bearer; in the case where the above cause value includes the third cause value, the first data radio bearer
  • the bearer type or the bearer type of the data radio bearer on the specified NE is one of the following: SCG bearer, MCG inter-NB bearer.
  • the apparatus may further include: a receiving module, connected to the sending module 54, configured to receive a second message sent by the first network element, where the second message carries the first network element pair A policy of reconfiguration management of the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the specified network element.
  • the foregoing policy includes at least one of the following: when the specified network element needs to be reserved and the cause value includes the first cause value, the bearer type of the first data radio bearer or the data radio bearer on the designated network element.
  • the bearer type of the bearer is reconfigured as the SCG inter-NB bearer or the MCG bearer; if the specified network element needs to be reserved and the cause value includes the second cause value, the bearer type of the first data radio bearer or the data on the specified network element
  • the bearer type of the radio bearer is reconfigured to one of the following three types of bearers: MCG bearer, MCG split bearer, MCG inter-NB bearer; in the case where the specified network element needs to be reserved and the cause value includes the third cause, the first
  • the bearer type of the data radio bearer or the bearer type of the data radio bearer on the specified network element is reconfigured as an MCG split bearer or SCG split bearer; the bearer type of the data radio bearer of the first data radio bearer or the
  • the reconfiguration of the bearer type may be performed by releasing or reconfiguring an entity in a specified network element, for example, reconfiguring a bearer type of a data radio bearer from an SCG bearer to an SCG inter-NB bearer. If the data radio bearer is located in the upper layer entity of the specified network element, the upper layer entity is reconfigured to the first network element; the reconfiguration of the bearer type of the other data radio bearers is similar, and details are not described herein again.
  • the apparatus may further include: a second determining module, configured to: when the bearer type of all data radio bearers established by the specified network element for the specified user equipment is SCG inter-NB bearer And determining whether to establish or delete at least one of the following objects: a lower layer entity, a serving cell, and a signaling radio bearer between the specified user equipment; wherein the lower layer entity includes: a radio link control RLC entity, and a medium access control MAC entity.
  • the second determining module may be connected to the sending module 54 or may not be connected to the sending module 54, and is not limited thereto.
  • the foregoing establishment may be performed to establish the foregoing object again on the basis that the specified network element does not establish the foregoing object, and may also be expressed as that the foregoing object needs to be added on the specified network element, but is not limited to this.
  • the foregoing second determining module may determine whether to establish or delete an object by using at least one of: determining whether to establish or delete an object according to the indication information sent by the first network element for indicating whether to establish or delete an object;
  • the provisions of the protocol determine whether to create or delete an object; only the specified network element determines whether to create or delete an object.
  • whether the object is established by using the foregoing indication information, or whether the object is established by using an implicit manner, for example, whether the target cell information is found in the indication information may be used to determine whether to establish an object, specifically, When the target information includes the target cell information (target cell information), the establishment object is determined; if the target information is not included in the indication information, it is determined that the object is not established.
  • the above device may be located in the second network element shown in FIG. 1 above, but is not limited thereto.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • FIG. 6 is a structural block diagram of a policy sending apparatus according to an embodiment of the present disclosure. As shown in FIG. 6, the apparatus includes:
  • the receiving module 62 is configured to receive a first message that is sent by the specified network element, where the first message carries a cause value of the first data radio bearer or the specified network element that is determined by the specified network element to release or modify the first data radio bearer;
  • the determining module 64 is connected to the receiving module 62, and is configured to determine, according to the cause value, a policy for reconfiguring a bearer type of a data radio bearer on a first data radio bearer or a designated network element;
  • the first sending module 66 is connected to the determining module 64, and configured to send the determined policy to the specified network element.
  • the reconfiguration management of the bearer type of the data radio bearer or the bearer type of the data radio bearer on the specified network element can be applied to the evolution and extension of the data radio bearer, and realizes the wireless of the specified network element or the sender of the first message.
  • the flexible management of the resources can solve the problem that the radio resource management on the network element is not flexible enough in the related art, and the effect of utilizing the resources of the designated network element is improved.
  • the specified network element may be the second network element.
  • the data radio bearer on the specified network element may refer to a part of the data radio bearer or all data radio bearers on the specified network element, and is not limited thereto. It should be noted that the foregoing partial data radio bearers may be one or more data radio bearers.
  • the foregoing cause value includes at least one of the following: a first cause value, where the first cause value is used to indicate that a quality of a radio channel between the specified network element and the terminal is lower than a first predetermined threshold; a second cause value, and a second The cause value is used to indicate that the load of the packet data convergence protocol PDCP entity and/or the service data adaptation protocol SDAP entity of the specified network element is greater than a second predetermined threshold; the third cause value is used to indicate the radio resource of the designated network element. The load is greater than the third predetermined threshold.
  • the quality of the radio channel between the specified network element and the terminal is lower than the first predetermined threshold, and the quality of the radio channel is poor (the air interface quality is poor), and the packet data convergence protocol PDCP entity and/or service of the designated network element is required.
  • the load of the data adaptation protocol SDAP entity is greater than the second predetermined threshold.
  • the PDCP overload or the SDAP overload may be considered.
  • the radio resource load of the designated network element is greater than the third predetermined threshold, and may be considered as UE lost. That is, the first cause value may be a poor air interface quality, and the second cause value may be a PDCP overload or a SDAP overload, and the third cause value may be a UE lost.
  • the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the designated network element is one of the following: the secondary cell group carries the SCG bearer, The secondary cell group separates the bearer SCG split bearer, the primary cell group separates the bearer MCG split bearer, and the primary cell group carries the MCG inter-NB bearer across the station; if the cause value includes the second cause value, the bearer type of the first data radio bearer Or the bearer type of the data radio bearer on the specified network element is one of the following: SCG bearer, SCG split bearer, SCG inter-NB bearer; in the case that the reason value includes the third cause value, the bearer of the first data radio bearer
  • the bearer type of the data radio bearer of the type or the specified network element is one of the following: SCG bearer, MCG inter-NB bearer.
  • the determining module 64 is further configured to: at least one of: if the specified network element needs to be reserved and the cause value includes the first cause value, determining that the policy is: the first data radio bearer
  • the bearer type or the bearer type of the data radio bearer on the specified network element is reconfigured as an SCG inter-NB bearer or an MCG bearer; if the specified network element needs to be reserved and the cause value includes the second cause value, the determining policy is:
  • the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the specified network element is reconfigured into one of the following three bearer types: MCG bearer, MCG split bearer, MCG inter-NB bearer; If the reason is that the cause value includes the third cause, the determining policy is: reconfiguring the bearer type of the first data radio bearer or the bearer type of the data radio bearer on the specified network element as an MCG split bearer or an SCG split bearer; The policy is to release the bearer type of the data
  • the reconfiguration of the bearer type may be performed by releasing or reconfiguring an entity in a specified network element, for example, reconfiguring a bearer type of a data radio bearer from an SCG bearer to an SCG inter-NB bearer. If the data radio bearer is located in the upper layer entity of the specified network element, the upper layer entity is reconfigured to the network element of the receiver of the first message; the reconfiguration of the bearer type of other data radio bearers is similar. I won't go into details here.
  • the foregoing apparatus may further include: a second sending module, configured to: when the bearer type of all data radio bearers established by the designated network element for the specified user equipment is an SCG inter-NB bearer, Sending, to the designated network element, a message indicating whether the specified network element establishes or deletes at least one of the following objects: a lower layer entity, a serving cell, and a signaling radio bearer between the specified user equipment; wherein the lower layer entity includes: radio link control RLC entity, media access control MAC entity.
  • connection relationship between the second sending module, the receiving module 62, the determining module 64, and the first sending module 66 is not limited.
  • the foregoing establishment may be performed to establish the foregoing object again on the basis that the specified network element does not establish the foregoing object, and may also be expressed as that the foregoing object needs to be added on the specified network element, but is not limited to this.
  • whether the object is created or deleted is directly indicated by the foregoing message, and whether the object is created or deleted is determined in an implicit manner. For example, whether the object is created or deleted may be determined by determining whether the target cell information appears in the message. Specifically, in the case that the target cell information (target cell information) is included in the foregoing message, the designated network element determines the establishment or deletion object; if the target cell information is not included in the message, the designated network element determines not to establish or delete Object.
  • target cell information target cell information
  • the specified network element may further determine whether to establish or delete an object by using at least one of the following: determining whether to create or delete an object according to a specification of a communication protocol; determining whether to create or delete an object only by the second network element.
  • the foregoing policy sending apparatus may be located in the first network element shown in FIG. 1 above, but is not limited thereto.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • Embodiments of the present disclosure also provide a storage medium including a stored program, wherein the program described above executes the method of any of the above.
  • the foregoing storage medium may include, but is not limited to, a USB flash drive, a Read-Only Memory (ROM), and a Random Access Memory (RAM).
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • Embodiments of the present disclosure also provide a processor for running a program, wherein the program executes the steps of any of the above methods when executed.
  • the preferred embodiment provides a method, where the method includes:
  • the first network element sends an add request message to the second network element, where the role of the add request message is a request.
  • the second network element agrees to establish an upper layer entity of the SCG inter-NB bearer.
  • the second network element may acquire resources that need to be provided for establishing the upper layer entity of the SCG inter-NB bearer. If the second network element agrees to establish, the second network element makes a radio resource configuration for the upper layer entity of the SCG inter-NB bearer and replies to the first network element by adding a response message.
  • the second network element needs to specify whether the lower layer entity can also be established (or whether at least one serving cell can be established. Or, it is possible to establish SRB3.
  • This patent regards the three established objects described in this scenario as the same kind, and the following layer entities are referred to as the following reference objects, and no specific enumeration is made. "Is the establishment of the underlying entity" can be determined by the first network element, and the result of the decision will be determined by the interface message (such as the addition of the request message, or other X2/Xn interface messages, the patent does not limit, only the role of the message is stated).
  • the second network element Indicated to the second network element; or may be explicitly defined in the communication protocol; or determined by the second network element.
  • the second network element needs to use the determined result as part of the second network element radio resource configuration, and reply to the first network element by using an interface message (such as adding the response message). .
  • the first network element generates the RRC signaling by using the received second network element radio resource configuration information, and sends the RRC signaling to the UE.
  • the message described in the preferred embodiment is only to explain the effect achieved by the message, and is not limited by the message name.
  • the foregoing signaling procedure may occur in an existing second network element adding procedure or in a second network element modifying procedure.
  • the second network element When the second network element triggers the release or modification of the at least one DRB, optionally, the second network element indicates the reason value of the release or modification to the first network element (corresponding to the above reason value) (Cause, or Special Value Or other), the reason values include but are not limited to:
  • a first cause value (corresponding to the first cause value in the foregoing embodiment): the role of the first cause value is that the wireless channel quality between the second network element and the UE can no longer bear the effective transmission of the data packet (eg Indicates that the quality of the wireless channel is degraded or below a certain threshold).
  • the first cause value is applicable to the DRB type in which the lower layer entity is established in the second network element, that is, at least one of the SCG/SCG split/MCG split/MCG inter-NB bearer.
  • a second cause value (corresponding to the second cause value in the foregoing embodiment): the second cause value is used to indicate that the PDCP and/or the SDAP processing load of the second network element is too heavy (eg, indicating that the upper layer entity handles the high load) ).
  • the second cause value is applicable to the DRB type in which the upper layer entity is established in the second network element, that is, at least one of the SCG/SCG split/SCG inter-NB bearer.
  • a third cause value (corresponding to the third cause value in the foregoing embodiment): the third cause value is used to indicate that the radio resource load of the second network element is too heavy, and it is difficult to maintain the throughput required by the DRB (such as an indication) The wireless resource is overloaded or does not meet the quality of service requirements).
  • the third cause value is applicable to the DRB type in which the lower layer entity is established only in the second network element, that is, at least one of the SCG/MCG inter-NB bearers.
  • the cause value may be a UE level granularity or a DRB level granularity.
  • the second network element Transmitting, by the second network element, the release/modification of the DRB and the cause value thereof to the first network element by using an interface message (such as a second network element modification request message) (corresponding to the first message in the foregoing embodiment);
  • a network element accepts release/modification of the DRB and reconfigures the DRB according to the cause value.
  • the DRB reconfiguration management decision of the first network element may be:
  • the first network element may decide to reconfigure the DRB as one of the SCG inter-NB/MCG bearers.
  • the first network element may decide to reconfigure the DRB as one of the MCG/MCG split/MCG inter-NB bearers.
  • the first network element may decide to reconfigure the DRB as one of the MCG split/SCG split bearers.
  • the determining of the first network element may further include releasing the DRB.
  • the first network element may also decide to release the second network element or switch the second network element; under these two decisions, the reconfiguration type of the DRB is not limited.
  • the first network element replies the determined result to the second network element through the interface message.
  • the above signaling procedure may occur in the existing second network element modification procedure, or may occur in the second network element release procedure or other procedures.
  • the foregoing method can enable the serving network element to implement hierarchical and highly flexible radio resource management on the radio bearer, so as to adapt to the evolution and expansion of the radio data bearer, realize full use of the second network element resource, and improve the access network. Service performance and perfect user communication experience.
  • the first network element decides to add at least one DRB to the second network element in the bearer type of the SCG inter-NB bearer, and indicates that the second network element does not need to establish any lower layer entity.
  • 7 is a schematic flow chart of a method according to a preferred embodiment 1 of the present disclosure. As illustrated in FIG. 7, the method includes:
  • Step 1 According to current information such as radio channel quality and resource usage, the first network element makes a radio resource management decision, and the determining is to select an access network node to be added as a second network element to the designated UE, and the The two network elements only need to establish an upper layer entity for one radio bearer, that is, provide PDCP (optionally, also includes SDAP) encapsulation processing for the radio bearer.
  • the radio resource management decision is based on a scenario in which the radio channel quality between the second network element and the UE does not meet a certain threshold, or the radio channel quality between the first network element and the UE fully satisfies the radio bearer.
  • the quality of service is required; however, the PDCP processing load of the first network element is heavy, and the second network element is required to share part of the load.
  • the radio bearer may be a DRB that has been established on the first network element and the UE, or may be a core network that indicates that the first network element needs to be newly established.
  • the DRB is all user plane transmissions that the second network element needs to bear for the UE (that is, only the upper layer entity is established), then the first network element is further
  • the radio resource management operation that needs to be performed determines whether the second network element can establish an underlying entity, and indicates the result of the decision to the second network element.
  • the fact that the second network element is not allowed to establish the lower layer entity means that the second network element does not have to establish any serving cell for the UE, nor can the SRB3 be established.
  • the "whether or not to establish an underlying entity" may also be explicitly specified in the communication protocol; or, may be determined by the second network element.
  • the first network element sends the radio resource management decision to the second network element by using an interface message, such as a SN Addition Request message, where the message is to request the second network element to accept the location.
  • the upper layer entity of the DRB establishes and makes corresponding radio resource configuration, and does not need to establish any lower layer entity.
  • the information carried by the interface message is similar to the existing message, and the focus is on enabling the second network element to explicitly establish an upper layer entity that meets the quality of service requirement for the DRB, which may be by indicating the bearer type (such as SCG inter -NB bearer) or other information with the same effect (such as not carrying any information related to the target cell).
  • the first network element needs to provide a transport layer address and a tunnel port address allocated for receiving the downlink PDCP data packet of the DRB.
  • Step 2 According to the received second network element adding request message, the second network element may obtain the resource that needs to be provided for establishing the upper layer entity of the DRB, and determine whether to agree to accept according to the resource. If it is determined to be admitted, the second network element performs radio resource configuration for the upper layer entity of the DRB and carries it in the interface message, such as the “SN Addition Request ACK” message. , reply to the first network element.
  • the other information carried in the second network element adding request acknowledgement message is the same as the existing message, such as a transport layer address and a tunnel port address allocated for receiving the uplink/downlink data packet.
  • step 1 determines whether or not to establish the lower layer entity. If the "whether or not to establish the lower layer entity" described in step 1 is determined by the second network element, then the second network element needs to determine the result (and if it is decided to establish, then the radio resource configuration made by the establishment) ) is also carried in the message to reply to the first network element.
  • the second network element is added, and the lower layer entity is not established.
  • the access network may decide to establish the lower layer entity again.
  • the first network element notifies the second network element of the indication of establishing the lower layer entity by using the second network element modification procedure.
  • Step 3 The user equipment performs an RRC connection reconfiguration procedure with the first network element.
  • Step 4 The second network element reconfiguration is completed.
  • Step 5 performing random access
  • Step 6 Perform a state transmission and data forwarding process between the first network element and the second network element.
  • Step 7 The path conversion process between the first network element and the core network.
  • the signaling process of steps 3-7 is similar to the prior art; for example, if the radio bearer is a DRB that has been established between the first network element and the UE, then the first network element and the core network are required.
  • the second network element does not establish any lower layer entity, the random access procedure of step 5 does not have to be performed, and the UE does not have to listen to the carrier of the second network element.
  • the second network element transmits the processed data packet to the first network element, so that the first network element can send the data packet to the wireless network interface.
  • UE User Service
  • FIG. 8 is a schematic flowchart of a method according to a preferred embodiment 2 of the present disclosure. As shown in FIG. 8, the method includes:
  • Step 1 For the second network element that has assumed at least one type of DRB transmission in the SCG/SCG split/SCG inter-NB bearer, when the PDCP processing load of the second network element is too heavy, the second network element may decide to at least The upper entity of a DRB is released. The second network element notifies the first network element of the identifier and the reason of the DRB to be released by using an interface message, such as a SN Modification Required message.
  • an interface message such as a SN Modification Required message.
  • the reason for the reason is that the first network element indicates that the second network element can no longer bear the upper layer encapsulation process of the part or all of the DRBs; the reason may be the UE level (that is, the reason is shared for the UE) All DRBs transmitted by the second network element, in this manner, the DRB identifier may be omitted, or may be a DRB level (that is, the reason is only for the UE to share part of the DRB transmitted in the second network element).
  • Step 2 After receiving the message described in step 1, the first network element first determines that the second network element is still reserved. Further, the first network element determines a reconfiguration bearer type of the DRB released for the request.
  • the reconfiguration bearer type includes at least agreeing to release an upper layer entity of the DRB located in the second network element (that is, reconfiguring the upper layer entity of the DRB to the first network element), specifically, for the original SCG or SCG split bearer,
  • the reconfiguration type may be an MCG or MCG split or an MCG inter-NB bearer; for the original SCG inter-NB bearer, the reconfiguration type may be an MCG bearer.
  • the retaining the second network element means that the second network element further establishes at least one lower layer entity of the DRB (ie, the first network element does not all the DRBs of the UE. Configured as MCG bearer).
  • the first network element needs to pass the result of the reconfiguration decision through an interface message, such as “Second NE Modification Request”.
  • the message is sent to the second network element, and the function of the message is to enable the second network element to perform necessary lower layer entity reconfiguration according to the change of the location of the network element where the upper layer entity of the DRB is located; the information carried by the message Similar to existing messages.
  • Steps 3 to 8 The subsequent signaling procedures and functions of the program are similar to the prior art, and are not described here.
  • the second network element determines to release at least the lower layer entity of each DRB; the second network element sends the released request to the first network element.
  • the first network element decides to release the second network element.
  • Step 1 For the second network element that has assumed at least one type of DRB transmission in the SCG/SCG split/MCG split/MCG inter-NB bearer, when the quality of the wireless channel between the second network element and the UE is below a certain threshold or When the second network element obtains that the quality of the wireless channel is not good, the second network element may decide to release at least the lower layer entity of each DRB that the UE bears to transmit. The second network element notifies the first network element of the DRB identifier (and/or the identifier of the UE) and the reason to be released by using an interface message, such as a “second network element modification request” message.
  • an interface message such as a “second network element modification request” message.
  • the reason for the reason is that the first network element indicates that the second network element can no longer bear the lower layer entity of part or all of the DRB; the reason may be the UE level or the DRB level (that is, the DRB released at each request) Indicate in the relevant cell).
  • Step 2 After receiving the message in step 1, the first network element decides to release the second network element, that is, not only agrees to release the second network element to the lower layer entity, but also determines that the first network element releases the second network element. All the contexts of the UE on the network element (ie, if the second network element is configured with the upper layer entity of the DRB, the upper layer entity is also released).
  • the first network element passes the interface message, such as the “second network element modification response” message, to at least confirm the release requested by the second network element in step 1 (ie, release of the downlink entity).
  • the preferred embodiment 2 is an example in which the first network element decides to release the second network element.
  • the first network element may also decide to reserve the second network element. If the first network element decides to reserve the second network element, the reconfiguration type of the DRB requested to be released by the second network element may be an MCG/SCG inter-NB bearer; and the first network element as described in the preferred embodiment In the example of deciding to release the second network element, the DRB can only be reconfigured as an MCG bearer unless the first network element decides to release the DRB completely (ie, indicates the release to the core network).
  • Step 3 Optional (if the message of step 2 has completed the release of the UE context, step 3 may be omitted), the first network element triggers the second network element release procedure to release the UE context on the second network element. .
  • Steps 4-6 In the RRC signaling sent to the UE, the first network element instructs the UE to release the radio resource configuration of the second network element, and reconfigures the DRB as an MCG bearer.
  • the subsequent signaling flow of this procedure is similar to the prior art and will not be described here.
  • Step 1 For the second network element that has already undertaken the transmission of the SCG/MCG inter-NB bearer, when the radio resource of the second network element is relatively tight, that is, the radio resource load is heavy, the second network element passes the interface message, such as The second network element modifies the request message and notifies the first network element of this information. Further, the message may further carry the UE identifier and the DRB identifier suggested by the second network element, so that the first network element can preferentially reconfigure the recommended DRB, such as bearer type conversion or release (if the first network element Still want to keep the second network element).
  • Step 2 After receiving the message described in step 1, the first network element decides to switch the second network element, that is, it is determined that the second network element is not reserved, but the original network is shared with the second network element.
  • the DRB transfers to the target second network element to continue the transmission.
  • the first network element by using an interface message, such as a second network element modification response message, indicates the result of the determination to the second network element, that is, releases the second network element.
  • the preferred embodiment 3 is an example in which the first network element decides to switch the second network element.
  • the first network element may also decide to reserve the second network element.
  • the reconfiguration bearer type of the DRB may be arbitrarily selected according to the radio condition; and if the first network element decides to reserve the second network element, at least the recommended DRB for the second network element
  • the reconfiguration type can be MCG Split or SCG Split bearer.
  • Steps 3 to 10 Starting from the second network element release procedure of step 3, the subsequent signaling process can be regarded as a signaling process similar to the existing procedure "Second Network Element Switching (SN Change)", which is no longer Repeated.
  • modules or steps of the present disclosure described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module. As such, the disclosure is not limited to any specific combination of hardware and software.

Landscapes

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

Abstract

本公开提供了一种消息、策略发送方法及装置，存储介质，处理器；其中，消息发送方法包括：确定释放或修改第一数据无线承载或指定网元；向第一网元发送第一消息，其中，第一消息中携带释放或修改第一数据无线承载或指定网元的原因值；原因值用于第一网元对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理。通过本公开，解决了相关技术中对网元上无线资源管理不够灵活的问题，达到提高了对指定网元或第一消息的发送方的资源的利用率的效果。

Description

消息、策略发送方法及装置，存储介质，处理器 技术领域
本公开涉及通信领域，具体而言，涉及一种消息、策略发送方法及装置，存储介质，处理器。
背景技术
相关技术中的通信网络，具有广泛部署的第四代(the fourth Generation，简称4G)通信系统和初步部署的第五代(the fifth Generation，简称5G)通信系统。其中，4G系统的核心网为演进的分组核心网(Evolved Packet Core，简称EPC)，其无线接入网(Radio Access Network，简称RAN)中部署有在无线接口上使用演进型通用陆地无线接入(Evolved Universal Terrestrial Radio Access，简称E-UTRA)的演进型基站(Evolved Node B，简称eNB)；5G系统的核心网为5G核心网(5G Core Network，简称5GC)，其RAN中部署有在无线接口上使用新型无线(New Radio，简称NR)接入的下一代基站(Generation Node B，简称gNB)、也部署有下一代演进型基站(Next Generation eNB，简称ng-eNB)。
在现有的接入网中，将两个基站以紧耦合的方式联合为用户设备(User Equipment，简称UE)提供通信服务的网络模式称为双连接(Dual Connectivity，简称DC)网络。如图1所示，其中，图1是相关技术中双连接网络的架构示意图。
而在DC网络中，DRB的类型与配置有了演进与扩展。但是，相关技术中的基站服务方式与控制面信令程序都还是保持着原有的概念。例如，只要第二网元分担了UE的数据传输，那么第二网元至少会建立一个DRB的下层实体(RLC实体和MAC实体)，同时，第二网元也至少为UE建立一个服务小区；进一步的，第二网元还可能建立与UE间的SRB(称为SRB3)。对于SCG bearer与SCG Split bearer类型而言，当第二网元决定释放至少一个DRB时，第二网元会指示将所述SCG bearer或SCG Split bearer位于第二网元的全部L2协议栈都释放掉。而从UE的角度来讲，在接入第二网元后，UE也会保持对第二网元服务小区的监听、以便检测可能的无线链路失败。由此可见，现有的通信方式与信令程序没有实现对演进的承载类型(如所述上、下层协议实体分离的承载类型)的匹配，接入网也难以实现分层次、高灵活的无线资源管理。
针对相关技术中的上述技术问题，目前尚未提出有效的解决方案。
发明内容
本公开实施例提供了一种消息、策略发送方法及装置，存储介质，处理器，以至少解决相关技术中对网元上无线资源管理不够灵活的问题。
根据本公开的一个实施例，提供了一种消息发送方法，包括：确定释放或修改第一数据无线承载或指定网元；向第一网元发送第一消息，其中，第一消息中携带释放或修改第一数 据无线承载或指定网元的原因值；原因值用于第一网元对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理。
可选地，原因值包括以下至少之一：第一原因值，第一原因值用于指示指定网元与终端间的无线信道质量低于第一预定门限；第二原因值，第二原因值用于指示指定网元的分组数据汇聚协议PDCP实体和/或服务数据适应协议SDAP实体的负荷大于第二预定门限；第三原因值，第三原因值用于指示指定网元的无线资源负荷大于第三预定门限；其中，指定网元为第一消息的发送方。
可选地，在原因值包括第一原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：辅小区组承载SCG bearer，辅小区组分离承载SCG split bearer，主小区组分离承载MCG split bearer,主小区组跨站承载MCG inter-NB bearer；在原因值包括第二原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，SCG split bearer，SCG inter-NB bearer；在原因值包括第三原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，MCG inter-NB bearer。
可选地，在向第一网元发送第一消息之后，方法还包括：接收第一网元发送的第二消息，其中，第二消息中携带第一网元对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理的策略。
可选地，策略包括以下至少之一：在指定网元需要被保留且原因值包括第一原因值的情况下，将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为SCG inter-NB bearer或MCG bearer；在指定网元需要被保留且原因值包括第二原因值的情况下，将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为以下三种承载类型之一：MCG bearer，MCG split bearer，MCG inter-NB bearer；在指定网元需要被保留且原因值包括第三原因的情况下，将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为MCG split bearer或SCG split bearer；释放第一数据无线承载或指定网元上的数据无线承载的承载类型；释放指定网元；切换指定网元。
可选地，方法还包括：在指定网元针对指定用户设备建立的所有数据无线承载的承载类型都是SCG inter-NB bearer的情况下，确定是否建立或删除以下至少之一对象：下层实体，服务小区，与指定用户设备间的信令无线承载；其中，下层实体包括：无线链路控制RLC实体，媒体接入控制MAC实体。
可选地，通过以下至少之一确定是否建立或删除对象：根据第一网元发送的用于指示是否建立或删除对象的指示信息确定是否建立或删除对象；按照通信协议的规定确定是否建立或删除对象；仅由指定网元确定是否建立或删除对象。
可选地，在指示信息中包括目标小区信息的情况下，确定建立对象；在指示信息中没有包括目标小区信息的情况下，确定不建立对象。
根据本公开的一个实施例，提供了一种策略发送方法，包括：接收指定网元发送的第一消息，其中，第一消息中携带指定网元确定的释放或修改第一数据无线承载或指定网元的原 因值；根据原因值确定对第一数据无线承载或指定网元上的数据无线承载的承载类型进行重配置管理的策略；将确定的策略发送给指定网元。
可选地，原因值包括以下至少之一：第一原因值，第一原因值用于指示指定网元与终端间的无线信道质量低于第一预定门限；第二原因值，第二原因值用于指示指定网元的分组数据汇聚协议PDCP实体和/或服务数据适应协议SDAP实体的负荷大于第二预定门限；第三原因值，第三原因值用于指示指定网元的无线资源负荷大于第三预定门限。
可选地，在原因值包括第一原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：辅小区组承载SCG bearer，辅小区组分离承载SCG split bearer，主小区组分离承载MCG split bearer,主小区组跨站承载MCG inter-NB bearer；在原因值包括第二原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，SCG split bearer，SCG inter-NB bearer；在原因值包括第三原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，MCG inter-NB bearer。
可选地，确定对第一数据无线承载或指定网元上的数据无线承载的承载类型进行重配置管理的策略包括以下至少之一：在指定网元需要被保留且原因值包括第一原因值的情况下，确定策略为：将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为SCG inter-NB bearer或MCG bearer；在指定网元需要被保留且原因值包括第二原因值的情况下，确定策略为：将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为以下三种承载类型之一：MCG bearer，MCG split bearer，MCG inter-NB bearer；在指定网元需要被保留且原因值包括第三原因的情况下，确定策略为：将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为MCG split bearer或SCG split bearer；确定策略为释放第一数据无线承载或指定网元上的数据无线承载的承载类型；确定策略为释放指定网元；确定策略为切换指定网元。
可选地，方法还包括：在所指定网元针对指定用户设备建立的所有数据无线承载的承载类型都是SCG inter-NB bearer的情况下，向指定网元发送用于指示指定网元是否建立或删除以下至少之一对象的消息：下层实体，服务小区，与指定用户设备间的信令无线承载；其中，下层实体包括：无线链路控制RLC实体，媒体接入控制MAC实体。
根据本公开的一个实施例，提供了一种消息发送装置，包括：第一确定模块，设置为确定释放或修改第一数据无线承载或指定网元；发送模块，设置为向第一网元发送第一消息，其中，第一消息中携带释放或修改第一数据无线承载或指定网元的原因值；原因值用于第一网元对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理。
可选地，装置还包括：接收模块，设置为接收第一网元发送的第二消息，其中，第二消息中携带第一网元对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理的策略。
可选地，装置还包括：第二确定模块，设置为在所指定网元针对指定用户设备建立的所 有数据无线承载的承载类型都是SCG inter-NB bearer的情况下，确定是否建立或删除以下至少之一对象：下层实体，服务小区，与指定用户设备间的信令无线承载；其中，下层实体包括：无线链路控制RLC实体，媒体接入控制MAC实体。
根据本公开的一个实施例，提供了一种策略发送装置，包括：接收模块，设置为接收指定网元发送的第一消息，其中，第一消息中携带指定网元确定的释放或修改第一数据无线承载或指定网元的原因值；确定模块，设置为根据所述原因值确定对第一数据无线承载或指定网元上的数据无线承载的承载类型进行重配置管理的策略；第一发送模块，设置为将确定的策略发送给指定网元。
可选地，装置还包括：第二发送模块，设置为在指定网元针对指定用户设备建立的所有数据无线承载的承载类型都是SCG inter-NB bearer的情况下，向指定网元发送用于指示指定网元是否建立或删除以下至少之一对象的消息：下层实体，服务小区，与指定用户设备间的信令无线承载；其中，下层实体包括：无线链路控制RLC实体，媒体接入控制MAC实体。
根据本公开的又一个实施例，还提供了一种存储介质，存储介质包括存储的程序，其中，所述程序运行时执行上述任一项所述的方法。
根据本公开的又一个实施例，还提供了一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行上述任一项所述的方法。
通过本公开，由于通过在确定释放或修改第一数据无线承载或指定网元；向第一网元发送第一消息，其中，第一消息中携带释放或修改第一数据无线承载或指定网元的原因值，使得第一网元可以基于该原因值对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理，能够适用于数据无线承载的演进与扩展，实现了对指定网元或第一消息的发送方的无线资源的灵活管理，因此，可以解决相关技术中对网元上无线资源管理不够灵活的问题，达到提高了对指定网元或第一消息的发送方的资源的利用率的效果。
附图说明
此处所说明的附图用来提供对本公开的进一步理解，构成本申请的一部分，本公开的示意性实施例及其说明用于解释本公开，并不构成对本公开的不当限定。在附图中：
图1是相关技术中双连接网络的架构示意图；
图2(a)是DRB的承载类型为MCG Split bearer和SCG Split bearer的示意图；
图2(b)是DRB的承载类型为MCG bearer和SCG bearer的示意图；
图2(c)是DRB的承载类型为MCG inter-NB bearer和SCG inter-NB bearer的示意图；
图3是根据本公开实施例提供的消息发送方法的流程图；
图4是根据本公开实施例提供的策略发送方法的流程图；
图5是根据本公开实施例提供的消息发送装置的结构框图；
图6是根据本公开实施例提供的策略发送装置的结构框图；
图7是根据本公开优选实施例1提供的方法的流程示意图；
图8是根据本公开优选实施例2提供的方法的流程示意图；
图9是根据本公开优选实施例3提供的方法的流程示意图；
图10是根据本公开优选实施例4提供的方法的流程示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在DC网络中，与核心网间为所述UE建立控制面(Control Plane，简称CP)接口的基站称为主基站(Master Node，简称MN)、也可称为第一网元，另一个仅为所述UE提供额外的无线资源的基站称为辅基站(Secondary Node，简称SN)、也可称为第二网元。其中，第一、第二网元中至少有一个会与核心网间为所述UE建立用户面接口(User Plane，简称UP)，而两个网元间通常以非理想的有线接口(称为X2或Xn接口)进行连接；在无线接口上，两个网元可以使用相同或不同的无线接入技术(Radio Access Technology，简称RAT)，其中，将使用不同RAT的网络模式称为多RAT双连接(Multi RAT Dual Connectivity，简称MR-DC)网络。
从无线协议栈的角度来看，一个无线承载(Radio Bearer，简称RB)的层2(Layer 2，简称L2)协议栈主要包括分组数据汇聚协议(Packet Data Convergence Protocol，简称PDCP)实体、无线链路控制(Radio Link Control，简称RLC)实体与媒体接入控制(Medium Access Control，简称MAC)实体。对于CP的信令RB(Signalling RB，简称SRB)而言，其L2协议栈之上还有一个无线资源控制(Radio Resource Control，简称RRC)实体；如果UE当前接入的核心网为5GC，那么对于UP的数据RB(Data RB，简称DRB)而言，其完整的L2协议栈还包括一个位于所述PDCP实体之上的服务数据适应协议(Service Data Adaptation Protocol，简称SDAP)实体。
在DC网络中，依据L2协议栈的分布配置不同，DRB可以被分为不同的承载类型。例如，可以将某DRB的L2协议栈分别配置在两个服务网元上，具体的，如图2(a)所示，其中，图2(a)是DRB的承载类型为MCG Split bearer和SCG Split bearer的示意图，所述DRB配置有两套RLC实体与MAC实体、并相对独立的分别位于两个服务网元，其中，将UP接口终结在第一网元、且PDCP实体(可选的，还包括SDAP实体)位于第一网元的DRB称为主小区组分离承载(Master Cell Group split bearer，简称MCG split bearer)，将UP接口终结于第二网元、且PDCP实体(可选的，还包括SDAP实体)位于第二网元的DRB称为辅小区组分离承载(Secondary Cell Group split bearer，简称SCG split bearer)。或者，某一DRB的L2协议栈也可以完整的仅配置在一个服务网元上，如图2(b)所示，其中，图2(b)是DRB的承载类型为MCG bearer和SCG bearer的示意图，其中，将UP接口终结在第一网元、且所述L2协议栈仅完整的位于第一网元的DRB称为主小区组承载(MCG bearer)，将 UP接口终结于第二网元、且所述L2协议栈仅完整的位于第二网元的DRB称为辅小区组承载(SCG bearer)。
出于市场与研发的考量，对上述的四种DRB承载类型进行了归一化(Bearer Type Harmonisation)的设计，即UE不会区分PDCP实体(以及可选的SDAP实体)所对应的接入网网元、且所述的承载类型都可以被配置NR PDCP实体，这也就意味着MCG Split bearer与SCG Split bearer对于UE而言属于同一种承载类型；换一个角度来讲，PDCP实体(以及可选的SDAP，本专利中将这两种实体称为上层实体)与RLC实体和MAC实体(本专利中将这两种实体称为下层实体)实现了一定程度上的解耦。
进一步的，随着SCG Split bearer的出现与上/下层实体解耦概念的产生，另有至少两种DRB承载类型有了应用的空间。如图2(c)所示，其中，图2(c)是DRB的承载类型为MCG inter-NB bearer和SCG inter-NB bearer的示意图，其中，将UP接口终结在第一网元、且所述L2协议栈中的下层实体仅完整的位于第二网元的DRB称为主小区组跨站承载(MCG inter-NB bearer)，将UP接口终结于第二网元、且所述L2协议栈中的下层实体仅完整的位于第一网元的DRB称为辅小区组跨站承载(SCG inter-NB bearer)。
基于上述数据无线承载的类型的扩展，本申请提供了以下几种实施例的方案。
实施例1
在本实施例中提供了一种运行于图1所示的架构的消息发送方法，图3是根据本公开实施例提供的消息发送方法的流程图，如图3所示，该流程包括如下步骤：
步骤S302，确定释放或修改第一数据无线承载或指定网元；
步骤S304，向第一网元发送第一消息，其中，第一消息中携带释放或修改第一数据无线承载或指定网元的原因值；原因值用于第一网元对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理。
通过上述步骤，由于通过在确定释放或修改第一数据无线承载或指定网元；向第一网元发送第一消息，其中，第一消息中携带释放或修改第一数据无线承载或指定网元的原因值，使得第一网元可以基于该原因值对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理，能够适用于数据无线承载的演进与扩展，实现了对指定网元或第一消息的发送方的无线资源的灵活管理，因此，可以解决相关技术中对网元上无线资源管理不够灵活的问题，达到提高了对指定网元或第一消息的发送方的资源的利用率的效果。
需要说明的是，上述指定网元上的数据无线承载可以是指上述指定网元上的部分数据无线承载或全部数据无线承载，并不限于此。需要说明的是，上述部分数据无线承载可以是一个或多个数据无线承载。
需要说明的是，上述原因值可以包括以下至少之一：第一原因值，第一原因值用于指示指定网元与终端间的无线信道质量低于第一预定门限；第二原因值，第二原因值用于指示指定网元的分组数据汇聚协议PDCP实体和/或服务数据适应协议SDAP实体的负荷大于第二预定门限；第三原因值，第三原因值用于指示指定网元的无线资源负荷大于第三预定门限； 其中，指定网元为第一消息的发送方。
需要说明的是，上述指定网元可以是图1所示的第二网元。
需要说明的是，在上述指定网元与终端间的无线信道质量低于第一预定门限可以认为是无线信道质量差(空口质量差)，指定网元的分组数据汇聚协议PDCP实体和/或服务数据适应协议SDAP实体的负荷大于第二预定门限可以认为PDCP过载或SDAP过载，指定网元的无线资源负荷大于第三预定门限可以认为是UE lost。即上述第一原因值可以是空口质量差，上述第二原因值可以是PDCP过载或SDAP过载，上述第三原因值可以是UE lost。
需要说明的是，在上述原因值包括第一原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：辅小区组承载SCG bearer，辅小区组分离承载SCG split bearer，主小区组分离承载MCG split bearer,主小区组跨站承载MCG inter-NB bearer；在上述原因值包括第二原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，SCG split bearer，SCG inter-NB bearer；在上述原因值包括第三原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，MCG inter-NB bearer。
在本公开的一个实施例中，在上述步骤S304之后，上述方法还可以包括：接收第一网元发送的第二消息，其中，第二消息中携带第一网元对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理的策略。
需要说明的是，上述策略包括以下至少之一：在指定网元需要被保留且原因值包括第一原因值的情况下，将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为SCG inter-NB bearer或MCG bearer；在指定网元需要被保留且原因值包括第二原因值的情况下，将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为以下三种承载类型之一：MCG bearer，MCG split bearer，MCG inter-NB bearer；在指定网元需要被保留且原因值包括第三原因的情况下，将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为MCG split bearer或SCG split bearer；释放第一数据无线承载或指定网元上的数据无线承载的承载类型；释放指定网元；切换指定网元。
需要说明的是，对上述承载类型进行重配置可以表现为对指定网元内的实体进行释放或重配置，比如将数据无线承载的承载类型从SCG bearer重配置为SCG inter-NB bearer,可以表现为：将该数据无线承载位于指定网元的上层实体进行释放，将该上层实体重配置到第一网元中；对于其他的数据无线承载的承载类型的重配置类似，此处不再赘述。
在本公开的一个实施例中，上述方法还可以包括：在指定网元针对指定用户设备建立的所有数据无线承载的承载类型都是SCG inter-NB bearer的情况下，确定是否建立或删除以下至少之一对象：下层实体，服务小区，与指定用户设备间的信令无线承载；其中，下层实体包括：无线链路控制RLC实体，媒体接入控制MAC实体。
需要说明的是，确定是否建立或删除上述对象的执行顺序可以在上述步骤S304之前或之后，也可以与步骤S304同时执行，但并不限于此。
需要说明的是，上述建立可以表现为在指定网元没有建立上述对象的基础上再次建立上 述对象，也可以表现为在指定网元上已经建立了上述对象还需要添加上述对象，但并不限于此。
需要说明的是，可以通过以下至少之一确定是否建立或删除对象：根据第一网元发送的用于指示是否建立或删除对象的指示信息确定是否建立或删除对象；按照通信协议的规定确定是否建立或删除对象；仅由指定网元确定是否建立或删除对象。
需要说明的是，可以通过上述指示信息直接指示是否建立对象，也可以通过隐式方式来指示是否建立对象，比如可以通过确定指示信息中是否出现目标小区信息来确定是否建立对象，具体地，在上述指示信息中包括目标小区信息(target cell信息)的情况下，确定建立对象；在指示信息中没有包括目标小区信息的情况下，确定不建立对象。
需要说明的是，上述步骤可以发送在第二网元添加或修改程序中，但并不限于此。
需要说明的是，上述步骤的执行主体可以是上述图1所示的第二网元，但并不限于此。
本公开实施例提供了一种策略发送方法，图4是根据本公开实施例提供的策略发送方法的流程图，如图4所示，该流程包括如下步骤：
步骤S402，接收指定网元发送的第一消息，其中，第一消息中携带指定网元确定的释放或修改第一数据无线承载或指定网元的原因值；
步骤S404，根据所述原因值确定对第一数据无线承载或指定网元上的数据无线承载的承载类型进行重配置管理的策略；
步骤S406，将确定的策略发送给指定网元。
通过上述步骤，由于接收指定网元发送的第一消息，其中，第一消息中携带指定网元确定的释放或修改第一数据无线承载或指定网元的原因值；进而基于该原因值对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理，能够适用于数据无线承载的演进与扩展，实现了对指定网元或第一消息的发送方的无线资源的灵活管理，因此，可以解决相关技术中对网元上无线资源管理不够灵活的问题，达到提高了对指定网元的资源的利用率的效果。
需要说明的是，上述指定网元可以是上述第二网元。
需要说明的是，上述指定网元上的数据无线承载可以是指上述指定网元上的部分数据无线承载或全部数据无线承载，并不限于此。需要说明的是，上述部分数据无线承载可以是一个或多个数据无线承载。
需要说明的是，上述原因值包括以下至少之一：第一原因值，第一原因值用于指示指定网元与终端间的无线信道质量低于第一预定门限；第二原因值，第二原因值用于指示指定网元的分组数据汇聚协议PDCP实体和/或服务数据适应协议SDAP实体的负荷大于第二预定门限；第三原因值，第三原因值用于指示指定网元的无线资源负荷大于第三预定门限。
需要说明的是，在上述指定网元与终端间的无线信道质量低于第一预定门限可以认为是无线信道质量差(空口质量差)，指定网元的分组数据汇聚协议PDCP实体和/或服务数据适应协议SDAP实体的负荷大于第二预定门限可以认为PDCP过载或SDAP过载，指定网元 的无线资源负荷大于第三预定门限可以认为是UE lost。即上述第一原因值可以是空口质量差，上述第二原因值可以是PDCP过载或SDAP过载，上述第三原因值可以是UE lost。
需要说明的是，在上述原因值包括第一原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：辅小区组承载SCG bearer，辅小区组分离承载SCG split bearer，主小区组分离承载MCG split bearer,主小区组跨站承载MCG inter-NB bearer；在原因值包括第二原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，SCG split bearer，SCG inter-NB bearer；在上述原因值包括第三原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，MCG inter-NB bearer。
在本公开的一个实施例中，上述步骤S404可以包括以下至少之一：在指定网元需要被保留且原因值包括第一原因值的情况下，确定策略为：将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为SCG inter-NB bearer或MCG bearer；在指定网元需要被保留且原因值包括第二原因值的情况下，确定策略为：将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为以下三种承载类型之一：MCG bearer，MCG split bearer，MCG inter-NB bearer；在指定网元需要被保留且原因值包括第三原因的情况下，确定策略为：将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为MCG split bearer或SCG split bearer；确定策略为释放第一数据无线承载或指定网元上的数据无线承载的承载类型；确定策略为释放指定网元；确定策略为切换指定网元。
需要说明的是，对上述承载类型进行重配置可以表现为对指定网元内的实体进行释放或重配置，比如将数据无线承载的承载类型从SCG bearer重配置为SCG inter-NB bearer,可以表现为：将该数据无线承载位于指定网元的上层实体进行释放，将该上层实体重配置到第一消息的接收方的网元中；对于其他的数据无线承载的承载类型的重配置类似，此处不再赘述。
在本公开的一个实施例中，上述方法还可以包括：在所指定网元针对指定用户设备建立的所有数据无线承载的承载类型都是SCG inter-NB bearer的情况下，向指定网元发送用于指示指定网元是否建立或删除以下至少之一对象的消息：下层实体，服务小区，与指定用户设备间的信令无线承载；其中，下层实体包括：无线链路控制RLC实体，媒体接入控制MAC实体。
需要说明的是，上述建立可以表现为在指定网元没有建立上述对象的基础上再次建立上述对象，也可以表现为在指定网元上已经建立了上述对象还需要添加上述对象，但并不限于此。
需要说明的是，可以通过上述消息直接指示是否建立或删除对象，也可以通过隐式方式来指示是否建立或删除对象，比如可以通过确定消息中是否出现目标小区信息来确定是否建立或删除对象，具体地，在上述消息中包括目标小区信息(target cell信息)的情况下，指定网元确定建立或删除对象；在消息中没有包括目标小区信息的情况下，指定网元确定不建立或不删除对象。
需要说明的是，上述指定网元还可以通过以下至少之一确定是否建立或删除对象：按照通信协议的规定确定是否建立或删除对象；仅由第二网元确定是否建立或删除对象。
需要说明的是，上述步骤可以发送在第二网元添加或修改程序中，但并不限于此。
需要说明的是，上述步骤的执行主体可以是上述图1所示的第一网元，但并不限于此。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本公开各个实施例所述的方法。
实施例2
在本实施例中还提供了一种消息发送装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图5是根据本公开实施例提供的消息发送装置的结构框图，如图5所示，该装置包括：
第一确定模块52，用于确定释放或修改第一数据无线承载或指定网元；
发送模块54，与上述第一确定模块52连接，用于向第一网元发送第一消息，其中，第一消息中携带释放或修改第一数据无线承载或指定网元的原因值；原因值用于第一网元对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理。
通过上述装置，由于通过在确定释放或修改第一数据无线承载或指定网元；向第一网元发送第一消息，其中，第一消息中携带释放或修改第一数据无线承载或指定网元的原因值，使得第一网元可以基于该原因值对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理，能够适用于数据无线承载的演进与扩展，实现了对指定网元或第一消息的发送方的无线资源的灵活管理，因此，可以解决相关技术中对网元上无线资源管理不够灵活的问题，达到提高了对指定网元或第一消息的发送方的资源的利用率的效果。
需要说明的是，上述指定网元上的数据无线承载可以是指上述指定网元上的部分数据无线承载或全部数据无线承载，并不限于此。需要说明的是，上述部分数据无线承载可以是一个或多个数据无线承载。
需要说明的是，上述原因值可以包括以下至少之一：第一原因值，第一原因值用于指示指定网元与终端间的无线信道质量低于第一预定门限；第二原因值，第二原因值用于指示指定网元的分组数据汇聚协议PDCP实体和/或服务数据适应协议SDAP实体的负荷大于第二预定门限；第三原因值，第三原因值用于指示指定网元的无线资源负荷大于第三预定门限；其中，指定网元为第一消息的发送方。
需要说明的是，上述第一消息的发送方可以是上述装置，也可以是图1所示的第二网元。
需要说明的是，在上述指定网元与终端间的无线信道质量低于第一预定门限可以认为是无线信道质量差(空口质量差)，指定网元的分组数据汇聚协议PDCP实体和/或服务数据适应协议SDAP实体的负荷大于第二预定门限可以认为PDCP过载或SDAP过载，指定网元的无线资源负荷大于第三预定门限可以认为是UE lost。即上述第一原因值可以是空口质量差，上述第二原因值可以是PDCP过载或SDAP过载，上述第三原因值可以是UE lost。
需要说明的是，在上述原因值包括第一原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：辅小区组承载SCG bearer，辅小区组分离承载SCG split bearer，主小区组分离承载MCG split bearer,主小区组跨站承载MCG inter-NB bearer；在上述原因值包括第二原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，SCG split bearer，SCG inter-NB bearer；在上述原因值包括第三原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，MCG inter-NB bearer。
在本公开的一个实施例中，上述装置还可以包括：接收模块，与上述发送模块54连接，用于接收第一网元发送的第二消息，其中，第二消息中携带第一网元对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理的策略。
需要说明的是，上述策略包括以下至少之一：在指定网元需要被保留且原因值包括第一原因值的情况下，将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为SCG inter-NB bearer或MCG bearer；在指定网元需要被保留且原因值包括第二原因值的情况下，将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为以下三种承载类型之一：MCG bearer，MCG split bearer，MCG inter-NB bearer；在指定网元需要被保留且原因值包括第三原因的情况下，将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为MCG split bearer或SCG split bearer；释放第一数据无线承载或指定网元上的数据无线承载的承载类型；释放指定网元；切换指定网元。
需要说明的是，对上述承载类型进行重配置可以表现为对指定网元内的实体进行释放或重配置，比如将数据无线承载的承载类型从SCG bearer重配置为SCG inter-NB bearer,可以表现为：将该数据无线承载位于指定网元的上层实体进行释放，将该上层实体重配置到第一网元中；对于其他的数据无线承载的承载类型的重配置类似，此处不再赘述。
在本公开的一个实施例中，上述装置还可以包括：第二确定模块，用于在所指定网元针对指定用户设备建立的所有数据无线承载的承载类型都是SCG inter-NB bearer的情况下，确定是否建立或删除以下至少之一对象：下层实体，服务小区，与指定用户设备间的信令无线承载；其中，下层实体包括：无线链路控制RLC实体，媒体接入控制MAC实体。
需要说明的是，上述第二确定模块可以与上述发送模块54连接，也可以不与上述发送模块54连接，并不限于此。
需要说明的是，上述建立可以表现为在指定网元没有建立上述对象的基础上再次建立上述对象，也可以表现为在指定网元上已经建立了上述对象还需要添加上述对象，但并不限于此。
需要说明的是，上述第二确定模块可以通过以下至少之一确定是否建立或删除对象：根据第一网元发送的用于指示是否建立或删除对象的指示信息确定是否建立或删除对象；按照通信协议的规定确定是否建立或删除对象；仅由指定网元确定是否建立或删除对象。
需要说明的是，可以通过上述指示信息直接指示是否建立对象，也可以通过隐式方式来指示是否建立对象，比如可以通过确定指示信息中是否出现目标小区信息来确定是否建立对象，具体地，在上述指示信息中包括目标小区信息(target cell信息)的情况下，确定建立对象；在指示信息中没有包括目标小区信息的情况下，确定不建立对象。
需要说明的是，上述装置可以位于上述图1所示的第二网元，但并不限于此。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
本公开实施例还提供了一种策略发送装置，图6是根据本公开实施例提供的策略发送装置的结构框图，如图6所示，该装置包括：
接收模块62，用于接收指定网元发送的第一消息，其中，第一消息中携带指定网元确定的释放或修改第一数据无线承载或指定网元的原因值；
确定模块64，与上述接收模块62连接，用于根据所述原因值确定对第一数据无线承载或指定网元上的数据无线承载的承载类型进行重配置管理的策略；
第一发送模块66，与上述确定模块64连接，用于将确定的策略发送给指定网元。
通过上述装置，由于接收指定网元发送的第一消息，其中，第一消息中携带指定网元确定的释放或修改第一数据无线承载或指定网元的原因值；进而基于该原因值对第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型进行重配置管理，能够适用于数据无线承载的演进与扩展，实现了对指定网元或第一消息的发送方的无线资源的灵活管理，因此，可以解决相关技术中对网元上无线资源管理不够灵活的问题，达到提高了对指定网元的资源的利用率的效果。
需要说明的是，上述指定网元可以是上述第二网元。
需要说明的是，上述指定网元上的数据无线承载可以是指上述指定网元上的部分数据无线承载或全部数据无线承载，并不限于此。需要说明的是，上述部分数据无线承载可以是一个或多个数据无线承载。
需要说明的是，上述原因值包括以下至少之一：第一原因值，第一原因值用于指示指定网元与终端间的无线信道质量低于第一预定门限；第二原因值，第二原因值用于指示指定网元的分组数据汇聚协议PDCP实体和/或服务数据适应协议SDAP实体的负荷大于第二预定门限；第三原因值，第三原因值用于指示指定网元的无线资源负荷大于第三预定门限。
需要说明的是，在上述指定网元与终端间的无线信道质量低于第一预定门限可以认为是无线信道质量差(空口质量差)，指定网元的分组数据汇聚协议PDCP实体和/或服务数据适应协议SDAP实体的负荷大于第二预定门限可以认为PDCP过载或SDAP过载，指定网元 的无线资源负荷大于第三预定门限可以认为是UE lost。即上述第一原因值可以是空口质量差，上述第二原因值可以是PDCP过载或SDAP过载，上述第三原因值可以是UE lost。
需要说明的是，在上述原因值包括第一原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：辅小区组承载SCG bearer，辅小区组分离承载SCG split bearer，主小区组分离承载MCG split bearer,主小区组跨站承载MCG inter-NB bearer；在原因值包括第二原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，SCG split bearer，SCG inter-NB bearer；在上述原因值包括第三原因值的情况下，第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，MCG inter-NB bearer。
在本公开的一个实施例中，上述确定模块64还用于以下至少之一：在指定网元需要被保留且原因值包括第一原因值的情况下，确定策略为：将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为SCG inter-NB bearer或MCG bearer；在指定网元需要被保留且原因值包括第二原因值的情况下，确定策略为：将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为以下三种承载类型之一：MCG bearer，MCG split bearer，MCG inter-NB bearer；在指定网元需要被保留且原因值包括第三原因的情况下，确定策略为：将第一数据无线承载的承载类型或指定网元上的数据无线承载的承载类型重配置为MCG split bearer或SCG split bearer；确定策略为释放第一数据无线承载或指定网元上的数据无线承载的承载类型；确定策略为释放指定网元；确定策略为切换指定网元。
需要说明的是，对上述承载类型进行重配置可以表现为对指定网元内的实体进行释放或重配置，比如将数据无线承载的承载类型从SCG bearer重配置为SCG inter-NB bearer,可以表现为：将该数据无线承载位于指定网元的上层实体进行释放，将该上层实体重配置到第一消息的接收方的网元中；对于其他的数据无线承载的承载类型的重配置类似，此处不再赘述。
在本公开的一个实施例中，上述装置还可以包括：第二发送模块，用于在指定网元针对指定用户设备建立的所有数据无线承载的承载类型都是SCG inter-NB bearer的情况下，向指定网元发送用于指示指定网元是否建立或删除以下至少之一对象的消息：下层实体，服务小区，与指定用户设备间的信令无线承载；其中，下层实体包括：无线链路控制RLC实体，媒体接入控制MAC实体。
需要说明的是，上述第二发送模块与上述接收模块62，确定模块64，第一发送模块66的连接关系并不限定。
需要说明的是，上述建立可以表现为在指定网元没有建立上述对象的基础上再次建立上述对象，也可以表现为在指定网元上已经建立了上述对象还需要添加上述对象，但并不限于此。
需要说明的是，可以通过上述消息直接指示是否建立或删除对象，也可以通过隐式方式来指示是否建立或删除对象，比如可以通过确定消息中是否出现目标小区信息来确定是否建立或删除对象，具体地，在上述消息中包括目标小区信息(target cell信息)的情况下，指定 网元确定建立或删除对象；在消息中没有包括目标小区信息的情况下，指定网元确定不建立或不删除对象。
需要说明的是，上述指定网元还可以通过以下至少之一确定是否建立或删除对象：按照通信协议的规定确定是否建立或删除对象；仅由第二网元确定是否建立或删除对象。
需要说明的是，上述策略发送装置可以位于上述图1所示的第一网元中，但并不限于此。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例3
本公开的实施例还提供了一种存储介质，该存储介质包括存储的程序，其中，上述程序运行时执行上述任一项所述的方法。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本公开的实施例还提供了一种处理器，该处理器用于运行程序，其中，该程序运行时执行上述任一项方法中的步骤。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
为了更好的理解本公开实施例，以下结合优选的实施例对本公开做进一步解释。
基于上述图1所示的架构、UP与CP的承载类型与模式，本优选实施例提供了一种方法，该方法包括：
在决定将至少一个DRB添加到第二网元、且所述DRB需配置为SCG inter-NB bearer时，第一网元向第二网元发送添加请求消息，所述添加请求消息的作用是请求第二网元同意建立所述SCG inter-NB bearer的上层实体。根据所述添加请求消息，第二网元可获取到为建立所述SCG inter-NB bearer上层实体而需要提供的资源。如果第二网元同意建立，那么第二网元作出针对所述SCG inter-NB bearer上层实体的无线资源配置并通过添加响应消息回复给第一网元。
进一步的，如果第二网元针对指定UE建立的所有DRB的类型都是SCG inter-NB bearer，那么，第二网元需明确是否还可以建立下层实体(或者说，是否可以建立至少一个服务小区；或者说，是否可以建立SRB3。本专利将这一场景中所述的三个建立对象视作同类，下述提及所述的建立对象以下层实体进行代表，不再进行具体的列举)。“是否建立下层实体”可以由第一网元决定，并通过接口消息(如所述添加请求消息、或其他X2/Xn接口消息，本专利不做限定，只陈述消息的作用)将决定的结果指示给第二网元；或者可以在通信协议中对是否建立进行明确的规定；或者由第二网元进行决定。其中，当仅由第二网元进行决定时，第二网元需将决定的结果作为第二网元无线资源配置的一部分、通过接口消息(如所述添加响应消息)回复给第一网元。
第一网元将接收到的第二网元无线资源配置信息生成RRC信令并发送给UE。
需要说明的是，本优选实施例所述的消息仅在于说明消息所实现的作用、而不以消息名称实施局限。例如，上述信令流程可以发生在现有的第二网元添加程序中、也可以发生在第二网元修改程序中。
在第二网元触发至少一个DRB的释放或修改时，可选的，第二网元向第一网元指示释放或修改的原因值(相当于上述原因值)(Cause、或称为Special Value、或其他)，所述原因值包括但不限于：
第一原因值(相当于上述实施例中的第一原因值)：所述第一原因值的作用是表示第二网元与UE间的无线信道质量不再能够承担数据包的有效传输(如指示无线信道质量下降或低于一定门限)。所述第一原因值适用于在第二网元建立有下层实体的DRB类型，即至少包括SCG/SCG split/MCG split/MCG inter-NB bearer其中之一。
第二原因值(相当于上述实施例中的第二原因值)：所述第二原因值的作用是表示第二网元的PDCP和/或SDAP处理负荷过重(如指示上层实体处理高负荷)。所述第二原因值适用于在第二网元建立有上层实体的DRB类型，即至少包括SCG/SCG split/SCG inter-NB bearer其中之一。
第三原因值(相当于上述实施例中的第三原因值)：所述第三原因值的作用是表示第二网元的无线资源负荷过重，难以保持DRB所需的吞吐量(如指示无线资源负荷过重或不满足服务质量需求)。所述第三原因值适用于仅在第二网元建立有下层实体的DRB类型，即至少包括SCG/MCG inter-NB bearer其中之一。
所述原因值可以是UE级别的粒度、也可以是DRB级别的粒度。
第二网元通过接口消息(如第二网元修改请求消息)(相当于上述实施例中的第一消息)将对所述DRB的释放/修改及其原因值传输给第一网元；第一网元接受对DRB的释放/修改、并根据原因值对所述DRB进行重配置管理。相应于上述原因值，在保留第二网元的前提下，第一网元的DRB重配置管理决策(相当于上述实施例中的策略)可以是：
针对第一原因值，第一网元可决定将所述DRB重配置为SCG inter-NB/MCG bearer其中之一。
针对第二原因值，第一网元可决定将所述DRB重配置为MCG/MCG split/MCG inter-NB bearer其中之一。
针对第三原因值，第一网元可决定将所述DRB重配置为MCG split/SCG Split bearer其中之一。
可选的，第一网元的决策还可以包括释放所述DRB。另外，第一网元还可以决定释放第二网元、或切换第二网元；在这两种决定下，所述DRB的重配置类型不做限定。第一网元将决定的结果通过接口消息回复给第二网元。
上述信令流程可以发生在现有的第二网元修改程序中、也可以发生在第二网元释放程序或其他程序中。
通过上述方法可使得服务网元对无线承载实施分层次的、高灵活的无线资源管理，从而适配于无线数据承载的演进与拓展，实现对第二网元资源的充分使用，提高接入网的服务性能、完善用户的通信体验。
优选实施例1
第一网元决定将至少一个DRB以SCG inter-NB bearer的承载类型方式添加给第二网元、并指示第二网元不需要建立任何下层实体。图7是根据本公开优选实施例1提供的方法的流程示意图，如图7所述，该方法包括：
步骤1：根据当前的无线信道质量与资源使用情况等信息，第一网元作出无线资源管理决定，所述决定是选择一个接入网节点作为第二网元添加给指定UE，且所述第二网元只需要为一个无线承载建立上层实体，即提供针对所述无线承载的PDCP(可选的，还包括SDAP)封装处理。举例来讲，所述无线资源管理决定所依据的场景是第二网元与UE间的无线信道质量尚未满足一定的门限、或第一网元与UE间的无线信道质量充分满足所述无线承载的服务质量要求；但同时，第一网元的PDCP处理负荷较重、需要第二网元分担部分负荷。其中，所述无线承载可以是已经建立在第一网元与UE的DRB、也可以是核心网指示第一网元需要新建立的DRB。
在本优选实施例所述的场景中，所述DRB是第二网元为所述UE所需要承担的全部用户面传输(也就是说，仅建立有上层实体)，那么，第一网元还需要执行的无线资源管理操作是决定第二网元是否可建立下层实体、并将所述决定结果指示给第二网元。其中，第二网元不被允许建立下层实体意味着第二网元不必为所述UE建立任何服务小区、也不可以建立SRB3。另外，所述“是否建立下层实体”还可以在通信协议中进行明确的规定；或者，由第二网元进行决定。
第一网元通过接口消息，如“第二网元添加请求(SN Addition Request)”消息将所述无线资源管理决定发送给第二网元，所述消息的作用是请求第二网元接纳所述DRB的上层实体建立并作出相应的无线资源配置、且不需要建立任何下层实体。其中，所述接口消息携带的信息与现有消息类似，重点在于能够使得第二网元明确只需要为所述DRB建立满足服务质量需求的上层实体，这可以是通过指示承载类型(如SCG inter-NB bearer)或其他具有相同作用的信息(如没有携带任何与目标小区相关的信息)来实现。另外，第一网元需提供为接收所述DRB的下行PDCP数据包而分配的传输层地址与隧道端口地址。
步骤2：根据接收到的第二网元添加请求消息，第二网元可获取为建立所述DRB的上层实体而需提供的资源、并据此进行是否同意接纳的判断。如果判断为同意接纳，那么第二网元作出针对所述DRB的上层实体的无线资源配置并将其携带在接口消息中，如“第二网元添加请求确认(SN Addition Request ACK)”消息中，回复给第一网元。其中，所述第二网元添加请求确认消息中所携带的其他信息与现有消息相同，如为接收上/下行数据包而分配的传输层地址与隧道端口地址。另外，如果步骤1中所述的“是否建立下层实体”是由第二网元决定的，那么第二网元需将决定的结果(以及如果决定建立的话，那么因建立所作出的 无线资源配置)也携带在所述消息中回复给第一网元。
需要说明的是，本优选实施例以第二网元的添加程序、且没有建立下层实体的情况进行举例的，在为UE提供服务的过程中，接入网可以决定再建立所述下层实体，如第一网元通过第二网元修改程序将建立所述下层实体的指示通知给第二网元。
步骤3，用户设备与第一网元执行RRC连接重配置程序；
步骤4，第二网元重配置完成；
步骤5，进行随机接入；
步骤6，执行第一网元与第二网元间的状态传输与数据转发流程；
步骤7，第一网元与核心网间的路径转换流程。
需要说明的是，步骤3～7的信令流程与现有技术类似；例如，如果所述无线承载是第一网元与UE间已经建立的DRB，那么就需要第一网元与核心网间的路径转换流程(步骤7)，以及可选的，第一网元与第二网元间的状态传输与数据转发流程(步骤6)。需要注意的是，如果第二网元没有建立任何下层实体，那么步骤5的随机接入程序不必执行，UE也不必监听第二网元的载波。在建立的上层实体对接收到的下行数据包进行封装处理后，第二网元将所述处理后的数据包传递给第一网元，从而第一网元能够通过无线接口将数据包发送给UE。
优选实施例2
因为PDCP的处理负荷过重，因此第二网元决定释放至少一个DRB的上层实体；第二网元将释放的请求发送给第一网元。第一网元决定仍保留所述第二网元、并对所述请求释放的DRB进行无线资源重配置决策。图8是根据本公开优选实施例2提供的方法的流程示意图，如图8所示，该方法包括：
步骤1：对于已经承担了SCG/SCG Split/SCG inter-NB bearer中至少一种DRB传输的第二网元，当第二网元的PDCP处理负荷过重时，第二网元可决定将至少一个DRB的上层实体进行释放。第二网元通过接口消息，如“第二网元修改请示(SN Modification Required)”消息，将所要释放的DRB的标识以及原因通知给第一网元。其中，所述原因的作用是向第一网元指示第二网元不再能够承担部分或全部DRB的上层实体封装处理；所述原因可以是UE级别(即所述原因针对所述UE分担在第二网元传输的所有DRB，在这种方式下，所述DRB标识可以省略)、也可以是DRB级别(即所述原因仅针对所述UE分担在第二网元传输的部分DRB)。
步骤2：接收到步骤1所述的消息后，第一网元首先决定仍保留所述第二网元，进一步的，第一网元决定对所述请求释放的DRB的重配置承载类型。所述重配置承载类型至少包括同意释放所述DRB位于第二网元的上层实体(即将所述DRB的上层实体重配置到第一网元)，具体的，对于原SCG或SCG Split bearer，所述重配置类型可以是MCG或MCG Split或MCG inter-NB bearer；对于原SCG inter-NB bearer，所述重配置类型可以是MCG bearer。另一方面，对于本优选实施例所述方案，保留所述第二网元意味着第二网元至少还建立一个DRB的下层实体(即第一网元不会将所述UE的所有DRB都配置为MCG bearer)。
在至少一个DRB的重配置类型为MCG Split或MCG inter-NB bearer时，第一网元需将所述重配置决定的结果通过接口消息，如“第二网元修改请求(SN Modification Request)”消息，通知给第二网元，所述消息的作用是使得第二网元根据所述DRB的上层实体所位于网元位置的改变而进行必要的下层实体重配置；所述消息所携带的信息与现有消息类似。
步骤3～8：此程序的后续信令流程及作用与现有技术类似，此处不再累述。
优选实施例3
因为第二网元与UE间的无线信道质量低于门限，因此第二网元决定至少释放各DRB的下层实体；第二网元将释放的请求发送给第一网元。第一网元决定释放第二网元。图9是根据本公开优选实施例3提供的方法的流程示意图，如图9所示，该方法包括：
步骤1：对于已经承担了SCG/SCG Split/MCG Split/MCG inter-NB bearer中至少一种DRB传输的第二网元，当第二网元与UE间的无线信道质量低于一定的门限或第二网元获取到所述无线信道质量不佳时，第二网元可决定至少释放其为所述UE承担传输的各DRB的下层实体。第二网元通过接口消息，如“第二网元修改请示”消息将所要释放的DRB标识(和/或UE的标识)以及原因通知给第一网元。其中，所述原因的作用是向第一网元指示第二网元不再能够承担部分或全部DRB的下层实体；所述原因可以是UE级别、或者是DRB级别(即在各个请求释放的DRB的相关信元中进行指示)。
步骤2：接收到步骤1所述的消息后，第一网元决定释放所述第二网元，即不仅同意第二网元对所述下层实体的释放，而且第一网元决定释放第二网元上关于所述UE的所有上下文(即如果第二网元配置有DRB的上层实体，那么也将上层实体进行释放)。第一网元通过接口消息，如“第二网元修改响应”消息，以至少确认第二网元在步骤1中请求的释放(即对所述下行实体的释放)。
需要说明的是，优选实施例2是以第一网元决定释放第二网元进行举例，但与优选实施例1类似的，第一网元也可以决定保留第二网元。如果第一网元决定保留第二网元，那么对第二网元所请求释放的DRB的重配置类型可以是MCG/SCG inter-NB bearer；而在本优选实施例所阐述的第一网元决定释放第二网元的示例下，所述DRB只能被重配置为MCG bearer，除非第一网元决定将所述DRB进行彻底的释放(即向核心网指示释放)。
步骤3：可选的(如果步骤2的消息已完成了对UE上下文的释放，那么步骤3可以省略)，第一网元触发第二网元释放程序、以释放第二网元上的UE上下文。
步骤4～6：在发送给UE的RRC信令中，第一网元指示UE释放第二网元的无线资源配置、并将所述DRB重配置为MCG bearer。此程序的后续信令流程与现有技术类似，此处不再累述。
优选实施例4
当第二网元的无线资源负荷较重时，第二网元将这一信息通知给第一网元，以辅助第一网元进行有效的无线资源管理。根据接收到的消息，第一网元可决定切换第二网元。图10 是根据本公开优选实施例4提供的方法的流程示意图，如图10所示，该方法包括：
步骤1：对于已经承担了SCG/MCG inter-NB bearer传输的第二网元，当第二网元的无线资源比较紧张、即无线资源负荷较重时，第二网元通过接口消息，如第二网元修改请示消息，将这一信息通知给第一网元。进一步的，所述消息中还可以携带第二网元建议的UE标识与DRB标识，以便第一网元能够优先对所建议的DRB进行重配置，如承载类型转换或释放(如果第一网元仍想保留所述第二网元的话)。
步骤2：接收到步骤1所述的消息后，第一网元决定切换所述第二网元，即决定不再保留所述第二网元、而是将原本分担给第二网元传输的DRB转移到目标第二网元去继续传输。第一网元通过接口消息，如第二网元修改响应消息，将所述决定结果指示给第二网元、即释放所述第二网元。
需要说明的是，优选实施例3是以第一网元决定切换第二网元进行举例，但与优选实施例1类似的，第一网元也可以决定保留第二网元。只要第一网元没有决定对所述DRB进行彻底的释放，那么第一网元就需要决定对所述DRB的重配置。在切换第二网元的决定下，所述DRB的重配置承载类型可以视无线条件而任意选择；而如果第一网元决定保留第二网元，那么至少对第二网元所建议的DRB的重配置类型可以是MCG Split或SCG Split bearer。
步骤3～10：从步骤3的第二网元释放程序开始，后续信令流程都可看作与现有程序“第二网元切换(SN Change)”类似的信令流程，此处不再累述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (20)

  1. 一种消息发送方法，包括：
    确定释放或修改第一数据无线承载或指定网元；
    向第一网元发送第一消息，其中，所述第一消息中携带释放或修改所述第一数据无线承载或指定网元的原因值；所述原因值用于所述第一网元对所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型进行重配置管理。
  2. 根据权利要求1所述的方法，其中，所述原因值包括以下至少之一：
    第一原因值，所述第一原因值用于指示所述指定网元与终端间的无线信道质量低于第一预定门限；
    第二原因值，所述第二原因值用于指示所述所述指定网元的分组数据汇聚协议PDCP实体和/或服务数据适应协议SDAP实体的负荷大于第二预定门限；
    第三原因值，所述第三原因值用于指示所述所述指定网元的无线资源负荷大于第三预定门限；
    其中，所述指定网元为所述第一消息的发送方。
  3. 根据权利要求2所述的方法，其中，
    在所述原因值包括所述第一原因值的情况下，所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型为以下之一：辅小区组承载SCG bearer，辅小区组分离承载SCG split bearer，主小区组分离承载MCG split bearer,主小区组跨站承载MCG inter-NB bearer；
    在所述原因值包括第二原因值的情况下，所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，SCG split bearer，SCG inter-NB bearer；
    在所述原因值包括第三原因值的情况下，所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，MCG inter-NB bearer。
  4. 根据权利要求2所述的方法，其中，在向第一网元发送第一消息之后，所述方法还包括：
    接收所述第一网元发送的第二消息，其中，所述第二消息中携带所述第一网元对所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型进行重配置管理的策略。
  5. 根据权利要求4所述的方法，其中，所述策略包括以下至少之一：
    在所述指定网元需要被保留且所述原因值包括所述第一原因值的情况下，将所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型重配置为SCG inter-NB bearer或MCG bearer；
    在所述指定网元需要被保留且所述原因值包括所述第二原因值的情况下，将所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型重配置为以下三 种承载类型之一：MCG bearer，MCG split bearer，MCG inter-NB bearer；
    在所述指定网元需要被保留且所述原因值包括所述第三原因的情况下，将所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型重配置为MCG split bearer或SCG split bearer；
    释放所述第一数据无线承载或所述指定网元上的数据无线承载的承载类型；
    释放所述指定网元；
    切换所述指定网元。
  6. 根据权利要求1所述的方法，其中，所述方法还包括：
    在所述指定网元针对指定用户设备建立的所有数据无线承载的承载类型都是SCG inter-NB bearer的情况下，确定是否建立或删除以下至少之一对象：下层实体，服务小区，与所述指定用户设备间的信令无线承载；其中，所述下层实体包括：无线链路控制RLC实体，媒体接入控制MAC实体。
  7. 根据权利要求6所述的方法，其中，通过以下至少之一确定是否建立或删除所述对象：
    根据所述第一网元发送的用于指示是否建立或删除所述对象的指示信息确定是否建立或删除所述对象；
    按照通信协议的规定确定是否建立或删除所述对象；
    仅由所述指定网元确定是否建立或删除所述对象。
  8. 根据权利要求7所述的方法，其中，在所述指示信息中包括目标小区信息的情况下，确定建立所述对象；在所述指示信息中没有包括所述目标小区信息的情况下，确定不建立所述对象。
  9. 一种策略发送方法，包括：
    接收指定网元发送的第一消息，其中，所述第一消息中携带所述指定网元确定的释放或修改第一数据无线承载或所述指定网元的原因值；
    根据所述原因值确定对所述第一数据无线承载或所述指定网元上的数据无线承载的承载类型进行重配置管理的策略；
    将确定的所述策略发送给所述指定网元。
  10. 根据权利要求9所述的方法，其中，所述原因值包括以下至少之一：
    第一原因值，所述第一原因值用于指示所述指定网元与终端间的无线信道质量低于第一预定门限；
    第二原因值，所述第二原因值用于指示所述指定网元的分组数据汇聚协议PDCP实体和/或服务数据适应协议SDAP实体的负荷大于第二预定门限；
    第三原因值，所述第三原因值用于指示所述指定网元的无线资源负荷大于第三预定门限。
  11. 根据权利要求10所述的方法，其中，
    在所述原因值包括所述第一原因值的情况下，所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型为以下之一：辅小区组承载SCG bearer，辅小区组分离承载SCG split bearer，主小区组分离承载MCG split bearer,主小区组跨站承载MCG inter-NB bearer；
    在所述原因值包括第二原因值的情况下，所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，SCG split bearer，SCG inter-NB bearer；
    在所述原因值包括第三原因值的情况下，所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型为以下之一：SCG bearer，MCG inter-NB bearer。
  12. 根据权利要求10所述的方法，其中，确定对所述第一数据无线承载或所述指定网元上的数据无线承载的承载类型进行重配置管理的策略包括以下至少之一：
    在所述指定网元需要被保留且所述原因值包括所述第一原因值的情况下，确定所述策略为：将所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型重配置为SCG inter-NB bearer或MCG bearer；
    在所述指定网元需要被保留且所述原因值包括所述第二原因值的情况下，确定所述策略为：将所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型重配置为以下三种承载类型之一：MCG bearer，MCG split bearer，MCG inter-NB bearer；
    在所述指定网元需要被保留且所述原因值包括所述第三原因的情况下，确定所述策略为：将所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型重配置为MCG split bearer或SCG split bearer；
    确定所述策略为释放所述第一数据无线承载或所述指定网元上的数据无线承载的承载类型；
    确定所述策略为释放所述指定网元；
    确定所述策略为切换所述指定网元。
  13. 根据权利要求9所述的方法，其中，所述方法还包括：
    在所指定网元针对指定用户设备建立的所有数据无线承载的承载类型都是SCG inter-NB bearer的情况下，向所述指定网元发送用于指示所述指定网元是否建立或删除以下至少之一对象的消息：下层实体，服务小区，与所述指定用户设备间的信令无线承载；其中，所述下层实体包括：无线链路控制RLC实体，媒体接入控制MAC实体。
  14. 一种消息发送装置，包括：
    第一确定模块，设置为确定释放或修改第一数据无线承载或指定网元；
    发送模块，设置为向第一网元发送第一消息，其中，所述第一消息中携带释放或修改所述第一数据无线承载或指定网元的原因值；所述原因值用于所述第一网元对所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型进行重配置管理。
  15. 根据权利要求14所述的装置，其中，所述装置还包括：
    接收模块，设置为接收所述第一网元发送的第二消息，其中，所述第二消息中携带所述第一网元对所述第一数据无线承载的承载类型或所述指定网元上的数据无线承载的承载类型进行重配置管理的策略。
  16. 根据权利要求14所述的装置，其中，所述装置还包括：
    第二确定模块，设置为在所指定网元针对指定用户设备建立的所有数据无线承载的承载类型都是SCG inter-NB bearer的情况下，确定是否建立或删除以下至少之一对象：下层实体，服务小区，与所述指定用户设备间的信令无线承载；其中，所述下层实体包括：无线链路控制RLC实体，媒体接入控制MAC实体。
  17. 一种策略发送装置，包括：
    接收模块，设置为接收指定网元发送的第一消息，其中，所述第一消息中携带所述指定网元确定的释放或修改第一数据无线承载或所述指定网元的原因值；
    确定模块，设置为根据所述原因值确定对所述第一数据无线承载或所述指定网元上的数据无线承载的承载类型进行重配置管理的策略；
    第一发送模块，设置为将确定的所述策略发送给所述指定网元。
  18. 根据权利要求17所述的装置，其中，所述装置还包括：
    第二发送模块，设置为在所述指定网元针对指定用户设备建立的所有数据无线承载的承载类型都是SCG inter-NB bearer的情况下，向所述指定网元发送用于指示所述指定网元是否建立或删除以下至少之一对象的消息：下层实体，服务小区，与所述指定用户设备间的信令无线承载；其中，所述下层实体包括：无线链路控制RLC实体，媒体接入控制MAC实体。
  19. 一种存储介质，其中，所述存储介质包括存储的程序，其中，所述程序运行时执行权利要求1至8,9-13中任一项所述的方法。
  20. 一种处理器，其中，所述处理器用于运行程序，其中，所述程序运行时执行权利要求1至8,9-13中任一项所述的方法。
PCT/CN2018/115197 2017-11-17 2018-11-13 消息、策略发送方法及装置，存储介质，处理器 WO2019096117A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP18877695.9A EP3713337B1 (en) 2017-11-17 2018-11-13 Message sending method and device, policy sending method and device, storage medium, and processor

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711145908.1 2017-11-17
CN201711145908.1A CN109803390B (zh) 2017-11-17 2017-11-17 消息、策略发送方法及装置，存储介质，处理器

Publications (1)

Publication Number Publication Date
WO2019096117A1 true WO2019096117A1 (zh) 2019-05-23

Family

ID=66538521

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/115197 WO2019096117A1 (zh) 2017-11-17 2018-11-13 消息、策略发送方法及装置，存储介质，处理器

Country Status (3)

Country Link
EP (1) EP3713337B1 (zh)
CN (1) CN109803390B (zh)
WO (1) WO2019096117A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113347694B (zh) * 2021-06-30 2022-12-06 锐迪科微电子科技（上海）有限公司 无线承载释放方法、装置、设备和介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103703859A (zh) * 2012-07-31 2014-04-02 华为技术有限公司 链路失败的恢复方法及装置
CN105228263A (zh) * 2014-06-30 2016-01-06 中兴通讯股份有限公司 Drb转换方法及装置
CN106100816A (zh) * 2011-11-25 2016-11-09 华为技术有限公司 实现载波聚合的方法、基站和用户设备

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101472312B (zh) * 2008-01-31 2010-07-07 华为技术有限公司 一种资源释放控制方法及通讯系统以及相关设备
GB2520923B (en) * 2013-11-01 2017-07-26 Samsung Electronics Co Ltd Bearer reconfiguration
JP6151801B2 (ja) * 2013-12-24 2017-06-21 京セラ株式会社 マスタ基地局
JP2015177548A (ja) * 2014-03-14 2015-10-05 宏達國際電子股▲ふん▼有限公司 ユーザ機器及び基地局に適用しうる接続変更方法
KR102022157B1 (ko) * 2014-03-28 2019-09-17 후지쯔 가부시끼가이샤 베어러 관리 장치, 방법 및 통신 시스템
PL3190846T3 (pl) * 2014-09-03 2021-01-25 Ntt Docomo, Inc. Stacja bazowa i sposób przesyłania danych
CN106304398B (zh) * 2015-05-15 2021-08-27 夏普株式会社 用于重配置数据承载的方法和用户设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106100816A (zh) * 2011-11-25 2016-11-09 华为技术有限公司 实现载波聚合的方法、基站和用户设备
CN103703859A (zh) * 2012-07-31 2014-04-02 华为技术有限公司 链路失败的恢复方法及装置
CN105228263A (zh) * 2014-06-30 2016-01-06 中兴通讯股份有限公司 Drb转换方法及装置

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN109803390A (zh) 2019-05-24
EP3713337B1 (en) 2022-08-31
CN109803390B (zh) 2023-05-02
EP3713337A1 (en) 2020-09-23
EP3713337A4 (en) 2021-08-04

Similar Documents

Publication Publication Date Title
US10972945B2 (en) Method for handover between secondary base stations, network device, and user equipment
US10945179B2 (en) Communication path switching method and device
US11323911B2 (en) Radio bearer configuration method and apparatus for configuring a dual connectivity terminal
CN112715055B (zh) 无线电接入网络和用于加速的网络接入的方法
EP3637846B1 (en) Method and device for use in configuring novel quality of service architecture in dual connectivity system
WO2017054538A1 (zh) 建立辅助信令链路的方法及其装置、基站及终端
US11172491B2 (en) Data transmission method, apparatus and system, network element, storage medium and processor
CN110636580B (zh) 一种切换方法及装置
USRE48316E1 (en) Communications system, base station, user equipment, and signaling transmission method
KR102467066B1 (ko) 네트워크 액세스를 위한 방법 및 장치
KR102645345B1 (ko) 네트워크 액세스를 위한 방법 및 장치
WO2017177950A1 (zh) 连接的建立方法、装置及系统
WO2019140955A1 (zh) 地址发送的方法、装置及存储介质
CN114731723A (zh) 一种通信方法及装置
CN115699816A (zh) 用于在双连接下进行侧行链路中继通信的方法
WO2021026706A1 (zh) 一种f1接口管理方法及装置
WO2019096117A1 (zh) 消息、策略发送方法及装置，存储介质，处理器
WO2018171696A1 (zh) 建立连接的方法和装置
CN111836402A (zh) 一种数据传输方法及装置
WO2023124822A1 (zh) 一种通信协作方法及装置
WO2022156785A1 (zh) 一种通信方法及通信装置
WO2022047749A1 (zh) 通信方法及装置

Legal Events

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

Ref document number: 18877695

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018877695

Country of ref document: EP

Effective date: 20200617