CN110139324B - Message transmission method and device and computer storage medium - Google Patents

Message transmission method and device and computer storage medium Download PDF

Info

Publication number
CN110139324B
CN110139324B CN201810129034.9A CN201810129034A CN110139324B CN 110139324 B CN110139324 B CN 110139324B CN 201810129034 A CN201810129034 A CN 201810129034A CN 110139324 B CN110139324 B CN 110139324B
Authority
CN
China
Prior art keywords
bearer
request message
configuration
negotiation request
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201810129034.9A
Other languages
Chinese (zh)
Other versions
CN110139324A (en
Inventor
许萌
陈瑞卡
梁靖
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Datang Mobile Communications Equipment Co Ltd
Original Assignee
Datang Mobile Communications Equipment Co Ltd
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 Datang Mobile Communications Equipment Co Ltd filed Critical Datang Mobile Communications Equipment Co Ltd
Priority to CN201810129034.9A priority Critical patent/CN110139324B/en
Publication of CN110139324A publication Critical patent/CN110139324A/en
Application granted granted Critical
Publication of CN110139324B publication Critical patent/CN110139324B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • 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

Landscapes

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

Abstract

The application discloses a message transmission method and device and a computer storage medium, which are used for realizing bearing configuration negotiation between MN and SN, thereby improving the flexibility of bearing processing and the resource utilization rate of SN and MN. The application provides a message sending method, which comprises the following steps: the auxiliary node SN determines that bearing configuration negotiation needs to be carried out with the main node MN; and the SN sends a bearing configuration negotiation request message to the MN.

Description

Message transmission method and device and computer storage medium
Technical Field
The present application relates to the field of communications technologies, and in particular, to a message transmission method and apparatus, and a computer storage medium.
Background
In an EN-DC Dual Connectivity (E-UTRA-NR Dual Connectivity) scenario, each rb is determined by a Master Node (MN) for its Packet Data Convergence Protocol (PDCP) entity location and for which cell group the radio resource is configured, i.e., the MN determines the bearer type. The MN determines an Aggregate Maximum Bit Rate (AMBR) limit for uplink/downlink aggregation of a User Equipment (UE) between the MN and a Secondary Node (SN). The establishment of the Secondary Cell Group (SCG) side related Bearer may be implemented through an SN addition process or an SN modification process initiated by the MN, where, taking the SN addition process as an example, the MN decides to request the SN to allocate a Radio resource to a specific Evolved Radio Access Bearer (E-RAB), and provides a corresponding E-RAB characteristic to the SN, and for a Bearer requiring SCG Radio configuration, the MN provides requested SCG configuration information including a UE capability and a UE capability negotiation result. For those requiring X2-U interface resources between the MN and the SN, the MN will provide corresponding address information, and for the split bearer terminated at the SN, the MN provides the maximum Quality of Service (QoS) level supported by the SN. The SN may reject the request. If the SN can accept the resource request of the MN, the wireless resource is allocated according to the bearer type and the characteristic.
Disclosure of Invention
The embodiment of the application provides a message transmission method and device and a computer storage medium, which are used for realizing bearer configuration negotiation between an MN and an SN (service number) so as to improve the flexibility of bearer processing and the resource utilization rate of the SN and the MN.
On the SN side, a message sending method provided in an embodiment of the present application includes:
the auxiliary node SN determines that bearing configuration negotiation with the main node MN is required;
and the SN sends a bearing configuration negotiation request message to the MN.
Therefore, when the SN determines that the bearing configuration negotiation with the main node MN is needed, the SN sends a bearing configuration negotiation request message to the MN, thereby realizing the bearing configuration negotiation between the MN and the SN, and improving the flexibility of bearing processing and the resource utilization rate of the SN and the MN.
Optionally, the bearer configuration negotiation request message specifically includes one or a combination of the following information:
the bearer type suggested by the SN;
the SN proposed bearer split ratio;
requiring the MN to adjust a bearer ID of bearer configuration;
the SN is capable of supporting transmission capabilities.
Therefore, the SN can negotiate with the MN to change the type, the bearer separation ratio and the like of the bearer corresponding to the bearer ID allocated to the SN, so that the MN can acquire the transmission capability of the SN and further allocate a proper bearer to the SN according to the transmission capability of the SN.
Optionally, the bearer type suggested by the SN specifically includes:
the SN suggests the MN to reconfigure the bearer requested to be configured or the type of configured bearer to be a split bearer type, a secondary cell group, SCG, bearer type, or a master cell group, MCG, bearer type.
Thus, the SN may suggest that the MN will reconfigure the bearer requested to be configured or the type of configured bearer as a split bearer type, a secondary cell group SCG bearer type, or a master cell group MCG bearer type.
Optionally, the bearer configuration negotiation request message is sent in one or more of the following flows:
SN addition process;
SN modification flow;
includes SN load building or content modifying flow;
the SN determines the flow of independent trigger.
Thus, in the SN adding flow or SN modifying flow or the flow containing SN bearer setup or modification content or the flow triggered independently by the SN decision, the SN may send a bearer configuration negotiation request message to the MN.
Optionally, the SN determining that bearer configuration negotiation with the MN is required specifically includes:
the SN determines that the bearer allocated to the SN by the MN cannot be assumed; or,
the SN determines that the MN can be assumed to allocate more bearers for the SN.
Thus, bearer configuration negotiation with the MN is possible whether the SN cannot bear the bearer assigned to the SN by the MN or the SN can bear more bearers.
Optionally, the method further comprises:
and the SN receives the bearing configuration negotiation response message replied by the MN.
So that the SN can know configuration information of bearers reallocated for the SN by the MN or a response message for confirmation or rejection of a request for SN bearer negotiation, etc.
Correspondingly, on the MN side, a message receiving method provided in the embodiment of the present application includes:
a main node MN receives a bearing configuration negotiation request message sent by an auxiliary node SN;
and the MN processes the bearing configuration negotiation request message.
Therefore, the MN receives the bearing configuration negotiation request message sent by the auxiliary node SN and processes the bearing configuration negotiation request message, thereby realizing the bearing configuration negotiation between the MN and the SN and improving the flexibility of bearing processing and the resource utilization rate of the SN and the MN.
Optionally, the bearer configuration negotiation request message specifically includes one or a combination of the following information:
the bearer type suggested by the SN;
a bearer split ratio suggested by the SN;
requiring the MN to adjust a bearer ID of bearer configuration;
the SN is capable of supporting transmission capabilities.
Optionally, the bearer type suggested by the SN specifically includes:
the SN suggests the MN to reconfigure the type of bearer requested to be configured or configured as a split bearer type, an SCG bearer type, or an MCG bearer type.
Optionally, the bearer configuration negotiation request message is sent in one or more of the following flows:
SN addition process;
SN modification flow;
the process comprises SN bearing establishment or content modification;
the SN determines the flow of independent trigger.
Optionally, the processing, by the MN, the bearer configuration negotiation request message includes:
the MN allocates a new bearer for the SN or adjusts the configuration of the bearer allocated or already allocated to the SN according to the bearer configuration negotiation request message, and replies a bearer configuration negotiation response message to the SN, wherein the bearer configuration message carries the bearer configuration information of the SN or receives a response indication message of the SN bearer configuration negotiation request;
or, the MN replies a bearer configuration negotiation response message rejecting the SN negotiation to the SN according to the bearer configuration negotiation request message.
Therefore, the MN can allocate a new bearer to the SN or adjust the configuration of the bearer allocated to the SN according to the bearer configuration negotiation request message, and reply a bearer configuration negotiation response message to the SN, where the bearer configuration message requesting the SN is carried, so that the SN can know the configuration information of the bearer reallocated by the MN for the SN, and the like; or carrying a confirmation message for accepting the SN negotiation request, so that the SN can know that the MN accepts the bearing configuration negotiation request of the SN, and the SN can configure corresponding bearing according to the configuration of the SN bearing in the negotiation request; or, the MN replies a bearer configuration negotiation response message for rejecting SN negotiation to the SN according to the bearer configuration negotiation request message, and further informs the SN that the request is not accepted by the MN.
On the SN side, a message sending apparatus provided in an embodiment of the present application includes:
a memory for storing program instructions;
a processor for calling the program instructions stored in the memory and executing according to the obtained program:
determining that the auxiliary node SN needs to carry out bearing configuration negotiation with the main node MN;
and sending a bearing configuration negotiation request message to the MN.
Optionally, the bearer configuration negotiation request message specifically includes one or a combination of the following information:
the bearer type suggested by the SN;
the SN proposed bearer split ratio;
the MN is required to adjust the bearer ID of the bearer configuration;
the SN is capable of supporting transmission capabilities.
Optionally, the bearer type suggested by the SN specifically includes:
the SN suggests the MN to reconfigure the bearer requested to be configured or the type of configured bearer to be a split bearer type, a secondary cell group, SCG, bearer type, or a master cell group, MCG, bearer type.
Optionally, the bearer configuration negotiation request message is sent in one or more of the following flows:
SN addition process;
SN modification flow;
the process comprises SN bearing establishment or content modification;
the SN determines the flow of independent trigger.
Optionally, determining that the SN needs to perform bearer configuration negotiation with the MN specifically includes:
determining that the SN cannot assume a bearer assigned to the SN by the MN; or,
determining that the SN can assume that the MN allocates more bearers for the SN.
Optionally, the processor is further configured to:
and receiving a bearer configuration negotiation response message replied by the MN.
On the MN side, a message receiving apparatus provided in an embodiment of the present application includes:
a memory for storing program instructions;
a processor for calling the program instructions stored in the memory, executing according to the obtained program:
receiving a bearing configuration negotiation request message sent to a main node MN by an auxiliary node SN;
and processing the bearing configuration negotiation request message.
Optionally, the bearer configuration negotiation request message specifically includes one or a combination of the following information:
the bearer type suggested by the SN;
a bearer split ratio suggested by the SN;
the MN is required to adjust the bearer ID of the bearer configuration;
the SN is capable of supporting transmission capabilities.
Optionally, the bearer type suggested by the SN specifically includes:
the SN suggests the MN to reconfigure the type of bearer requested to be configured or configured as a split bearer type, an SCG bearer type, or an MCG bearer type.
Optionally, the bearer configuration negotiation request message is sent in one or more of the following processes:
SN addition process;
SN modification flow;
the process comprises SN bearing establishment or content modification;
the SN determines the flow of independent trigger.
Optionally, the processing the bearer configuration negotiation request message specifically includes:
the MN allocates a new bearer for the SN or adjusts the configuration of the bearer allocated or already allocated to the SN according to the bearer configuration negotiation request message, and replies a bearer configuration negotiation response message to the SN, wherein the bearer configuration message carries the bearer configuration information of the SN or receives a response indication message of the SN bearer configuration negotiation request;
or replying a bearer configuration negotiation response message for rejecting SN negotiation to the SN according to the bearer configuration negotiation request message.
Another message sending apparatus provided in an embodiment of the present application includes:
a determining unit, configured to determine that the secondary node SN needs to perform bearer configuration negotiation with the primary node MN;
a sending unit, configured to send a bearer configuration negotiation request message to the MN.
Another message receiving apparatus provided in an embodiment of the present application includes:
the receiving unit is used for receiving a bearing configuration negotiation request message sent to the main node MN by the auxiliary node SN;
and the processing unit is used for processing the bearer configuration negotiation request message.
Another embodiment of the present application provides a computer storage medium having stored thereon computer-executable instructions for causing a computer to perform any of the methods described above.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a schematic flowchart of a message sending method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a message receiving method according to an embodiment of the present application;
fig. 3 is a schematic diagram of a bearer type negotiation process provided in an embodiment of the present application;
fig. 4 is a schematic structural diagram of a message sending apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a message receiving apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of another message sending apparatus according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of another message receiving apparatus according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a message transmission method and device and a computer storage medium, which are used for realizing bearing configuration negotiation between an MN and an SN (service node), thereby improving the flexibility of bearing processing and the resource utilization rate of the SN and the MN.
In a Multi-access network Dual Connectivity (MR-DC) protocol architecture, an MN side determines allocation of bearer types, and the MN side initiates a request for an SN side to establish a corresponding bearer, but the MN side does not fully know resource availability of the SN side in a bearer allocation process, so the SN side may reject the request of the MN because the resource availability of the SN side cannot bear attribute requirements of the configured bearer, so that the bearer establishment fails. The current technology does not support the capability of the SN side and the MN side to negotiate the bearer. There is no flexibility in the SCG related bearer handling.
Specifically, in the MR-DC protocol architecture, in order to perform load sharing, the MN determines the final bearer type. For example, to reduce MN-side load stress, the MN may decide to share a bearer to the SN for transmission by the SN. And the SN selects to accept or reject the bearer shared by the MN according to the bearer characteristics requested by the MN and the availability of the SN side resources. Since negotiation of bearer type is not currently supported, this means that in the above example, if the SN has insufficient resources to accommodate bearers shared by the MN, the SN cannot choose to use split bearer type or to use a smaller bearer sharing ratio. Currently, bearer negotiation is a limitation, when a MN requests to share a bearer to an SN, the SN is allowed to negotiate a bearer type, and a split bearer is proposed to be used as a response, which can provide better resource utilization and flexibility of bearer processing.
In order to improve the flexibility of bearer processing and the resource utilization rate of the SN and the MN, the embodiments of the present application provide a scheme for bearer type negotiation. The SN may suggest the MN to modify the type of allocated bearer or the allocated bearer proportion according to the availability of its own resources, bearer attributes, etc.
Referring to fig. 1, on an SN side, a message sending method provided in an embodiment of the present application includes:
s101, the auxiliary node SN determines that bearing configuration negotiation with the main node MN is required;
s102, the SN sends a bearing configuration negotiation request message to the MN.
The bearer configuration negotiation request message may be an interface message (X2/Xn) code between the MN and the SN, or a Radio Resource Control (RRC) signaling code. The message may be a separate interface message process or a message content defined in the interface message. The MN adjusts the bearing distribution of the SN according to the negotiation request message of the SN and replies a message to the SN, wherein the reply message can carry the configuration information of the bearing distributed to the SN or the confirmation/rejection message.
The bearer configuration negotiation request message includes: the SN-suggested bearer type, and/or the SN-suggested bearer split ratio, and/or the bearer ID, and/or the supported transport capabilities of the SN side.
The bearer configuration negotiation request message may be a suggested value provided for each bearer, that is, the bearer configuration negotiation request message may provide a negotiation request for multiple bearers, and then the bearer configuration negotiation request message includes a bearer ID of each suggested modified configuration and corresponding suggested bearer configuration information.
The information content carried in the bearer configuration negotiation request message is specifically introduced as follows:
1) bearer ID
Since the MN may request the SN to establish multiple bearers during the SN addition process, in order to inform the MN which bearer or bearers configuration to adjust, the bearer ID should be included in the message to inform the MN that a modified bearer is proposed. The bearer configuration negotiation request message is not limited to requesting the MN to modify one bearer, and may request the MN to reconfigure a plurality of bearers at the same time.
2) Type of bearer
The bearer type may be a split (split) bearer type, or may be a Secondary Cell Group (SCG) bearer type or a Master Cell Group (MCG) bearer type. I.e. the SN suggests, according to the current capabilities, that the MN will request the configured bearer or the configured bearer to be reconfigured to split type or SCG type or MCG type.
3) Bearing separation ratio
The bearer split ratio may be the split ratio of the bearer that the SN side wishes to bear when suggesting the use of the split bearer type, or may be a relative proportion value of the SN's desired bearer to request the SN to establish the SCG part of the bearer, i.e. if the MN requests the SN to establish the split bearer, the SN side bears 50% of the overall bearer, which if 80% indicates that the SN recommends to bear 50% 80% or 40% of the bearer, or the proportion value of the proportion allocated to all SCG part bearers of the SN by the SN's desired bearer.
4) Transmission capability supported by SN side
The message may also contain the transmission capacity that the SN-proposed SN side wants the bearer SN to assume, such as the Maximum Aggregated Maximum Bit Rate (AMBR) or the Maximum transmission Bit (Bit) Rate.
The bearer configuration negotiation request message is not limited to request negotiation configuration for each bearer, but may also be request negotiation configuration for all bearers currently established by the MN, that is, the bearer configuration negotiation request message includes the maximum capability that the SN can bear, or the MN that the SN can bear requests the proportion of all bearers that the SN bears, and the MN may readjust the configuration of the bearers at the SN side according to the negotiation request message at the SN side, so that the SN can bear.
The bearer configuration negotiation process may occur in the SN addition process or in the SN modification process initiated by the MN, which is not limited to the above two processes, and may occur in any process in which the MN requests the SN configuration or modifies the bearer. This procedure is of course not a procedure necessarily occurring in the above-described procedure. Whether a bearer configuration negotiation request needs to be initiated is determined by the SN.
The bearer configuration negotiation process can be initiated by the SN when the MN requests the SN to establish the bearer, and the SN can also actively and independently initiate the negotiation, and the MN is proposed to modify the bearer resource allocation already configured on the SN side.
The bearer configuration negotiation process may be initiated by the SN not only when the SN cannot bear the bearer allocated by the MN, but also when the SN can bear the bearer allocated by the MN, that is, when the SN has sufficient resources, the SN is recommended to allocate more bearers, for example, the SN is recommended to switch from a split bearer to an SCG bearer, or the bearer split ratio is increased. Or actively request the MN to reallocate bearers when a reduction in link quality occurs at the SN side.
The MN adjusts the corresponding bearer according to the request message of the SN and requests the SN to establish, and the MN replies the configuration message carrying the corresponding bearer to the SN, or the MN accepts or rejects the bearer configuration negotiation request (replies a confirmation/rejection message) of the SN.
Accordingly, referring to fig. 2, on the MN side, a message receiving method provided in an embodiment of the present application includes:
s201, a main node MN receives a bearing configuration negotiation request message sent by an auxiliary node SN;
s202, the MN processes the bearing configuration negotiation request message.
Therefore, the MN receives the bearing configuration negotiation request message sent by the auxiliary node SN and processes the bearing configuration negotiation request message, thereby realizing the bearing configuration negotiation between the MN and the SN and improving the flexibility of bearing processing and the resource utilization rate of the SN and the MN.
Optionally, the bearer configuration negotiation request message specifically includes one or a combination of the following information:
the bearer type suggested by the SN;
the SN proposed bearer split ratio;
the MN is required to adjust the bearer ID of the bearer configuration;
the SN is capable of supporting transmission capabilities.
Optionally, the bearer type suggested by the SN specifically includes:
the SN suggests the MN to reconfigure the type of bearer requested to be configured or configured as a split bearer type, an SCG bearer type, or an MCG bearer type.
Optionally, the bearer configuration negotiation request message is sent in one or more of the following flows:
SN addition process;
SN modification flow;
the process comprises SN bearing establishment or content modification;
the SN determines the flow of independent trigger.
Optionally, the processing, by the MN, the bearer configuration negotiation request message includes:
the MN allocates a new bearer for the SN or adjusts the configuration of the bearer allocated or already allocated to the SN according to the bearer configuration negotiation request message, and replies a bearer configuration negotiation response message to the SN, wherein the bearer configuration message carries the bearer configuration information of the SN or receives a response indication message of the SN bearer configuration negotiation request;
or, the MN replies a bearer configuration negotiation response message rejecting the SN negotiation to the SN according to the bearer configuration negotiation request message.
Therefore, the MN can allocate a new bearer to the SN or adjust the configuration of the bearer allocated to the SN according to the bearer configuration negotiation request message, and reply a bearer configuration negotiation response message to the SN, where the bearer configuration response message carries configuration information of the bearer requested to be established by the SN, so that the SN can know the configuration information of the bearer reallocated to the SN by the MN, and the like; or carrying a confirmation message for accepting the SN negotiation request, so that the SN can know that the MN accepts the bearing configuration negotiation request of the SN, and the SN can configure corresponding bearing according to the configuration of the SN bearing in the negotiation request; or, the MN replies a bearer configuration negotiation response message for rejecting SN negotiation to the SN according to the bearer configuration negotiation request message, and informs the SN that the request is not accepted.
Taking the SN modification process as an example, referring to fig. 3, a specific message transmission process includes:
and S301, the MN sends a secondary base station modification request message to the SN, wherein the secondary base station modification request message comprises the establishment or modification message of the SCG bearer.
The SN determines whether to initiate a bearer negotiation process according to the self resource capability, in the example, the SN can not bear the bearer requested to be established or modified by the MN, and the SN initiates a bearer configuration negotiation request message, wherein the bearer configuration negotiation request message comprises the split bearer type and the separation proportion suggested by the SN.
And 1b, the MN receives the bearing configuration negotiation request message of the SN and replies a response message to the SN.
S302, SN collocates corresponding load bearing and sends the modification request confirmation information of the auxiliary base station to MN.
And S303, the MN sends an RRC reconfiguration message to the UE.
And S304, performing a random access process between the MN and the UE.
S305. the ue sends an RRC reconfiguration complete message to the MN.
And S306, the MN sends the secondary base station reconfiguration completion to the SN.
And S307, performing a random access process between the SN and the UE.
S308. the mn sends a state transfer of the SN to the SN.
S309. data forwarding is performed between the mn and the serving gateway (S-GW).
S310. the sn sends a secondary Radio Access Technology (RAT) data value report to the MN.
And S311, executing a path updating process among the MN, the SN, the S-GW and a Mobility Management Entity (MME).
Taking the above message name and the suggested message content as examples, the negotiation process is not limited to the message name in the example of fig. 3, nor to the suggested split bearer (bearer), nor to the use of a separate message, but also to the defined message content, which is included in other existing messages.
Example 1: the MN requests the SN to establish and/or modify a bearer, and the SN cannot undertake the MN's bearer assignment request, on a single bearer basis.
The specific flow of message transmission between the MN and the SN includes:
step 1: the MN allocates SCG bearers and/or split bearers for the SN and requests the SN to establish or modify the bearers.
Step 2: the SN receives the message containing the MN request for establishing or modifying the bearer, and judges that the bearer establishment request of the MN cannot be completely born according to the bearer requirement and the available resources of the SN.
And step 3: the SN calculates the current bearable bearing size and the bearable proportion aiming at the current bearing according to the availability of the self resource, and initiates a bearing configuration negotiation request message.
The bearer configuration negotiation request message may only modify one bearer or modify multiple bearers, and then the bearer configuration negotiation request message includes a bearer ID and a suggested bearer type of a suggested modified bearer. Taking the proposed split bearer as an example, the bearer configuration negotiation request message further includes a proportion that the bearer can bear, where the proportion may be a split proportion of the entire bearer that the SN wishes to bear, or may be a relative proportion of the bearer that the SN wishes to bear the MN requesting the SN to share, and/or the bearer configuration negotiation request message includes a capability that the SN proposes the bearer to bear, such as a maximum rate or an AMBR.
And 4, step 4: the MN receives the bearing type negotiation request message of the SN side, reconfigures the bearing of the SN side according to the capability of the SN according to the information provided by the SN in the bearing type negotiation request message, and sends the modified bearing configuration request message of the SN side to the SN; or, the MN sends an acknowledgement or rejection message to the SN according to whether to accept the negotiation request of the SN side.
And 5: and the SN receives a response message which is sent by the MN and contains the adjusted SN side bearing configuration, and configures the corresponding bearing according to the request of the MN. And sends a response message for step 1 to continue the corresponding flow initiated by the MN. If the SN can not satisfy all the request messages of the MN, the SN can reply a rejection message aiming at the request message of the step 1; or the SN receives the confirmation message sent by the MN, performs corresponding SCG configuration and sends a response message aiming at step 1 to continue the corresponding flow initiated by the MN, or receives a rejection message sent by the MN, and the SN stops the flow.
Example 2: the MN requests the SN to establish and/or modify the bearer, the SN cannot bear the bearer allocation request of the MN, and the configuration message is negotiated aiming at all the bearers.
The specific flow of message transmission between the MN and the SN includes:
step 1: the MN allocates SCG bearers and/or split bearers for the SN and requests the SN to establish or modify the bearers.
Step 2: the SN receives the message containing the MN request to establish or modify the bearer, and determines that the MN cannot be completely undertaken the bearer establishment request according to the bearer requirement and the available resources of the SN.
And step 3: the SN calculates the current bearable bearing size and the bearable proportion aiming at the current bearing according to the availability of the resource of the SN, and initiates a bearing configuration negotiation request message.
The bearer configuration negotiation request message includes the proportion of bearers allocated by the MN side that the SN can undertake, where the proportion may be the proportion of all bearers related to the SCG side in the MN request message that the SN wishes to undertake, or may be the relative proportion of the bearers that the SN wishes to undertake the MN request SN sharing; and/or
The bearer configuration negotiation request message contains the capabilities that the SN suggests the SN wishes to assume, such as maximum rate or AMBR.
And 4, step 4: and the MN receives the bearing type negotiation request message of the SN side, reconfigures the bearing of the SN side according to the capability of the SN according to the information provided by the SN in the bearing type negotiation request message, and sends the modified bearing configuration request message of the SN side to the SN. Or the MN sends an acknowledgement or rejection message to the SN according to whether the negotiation request of the SN side is accepted or not.
And 5: and the SN receives a response message which is sent by the MN and contains the adjusted SN side bearing configuration, and configures the corresponding bearing according to the request of the MN. And sends a response message for step 1 to continue the corresponding flow initiated by the MN. If the SN can not satisfy all the request messages of the MN, the SN can reply a rejection message aiming at the request message of the step 1; or the SN receives the confirmation message sent by the MN, then carries out corresponding SCG configuration and sends a response message aiming at the step 1 to continue the corresponding flow initiated by the MN, or receives a rejection message sent by the MN, and the SN stops the flow.
Example 3: the MN requests to establish or modify the split bearer, and the SN suggests taking on a larger proportion.
The specific flow of message transmission between the MN and the SN includes:
step 1: the MN allocates a split bearer for the SN and requests the SN to establish or modify the bearer.
Step 2: the SN receives the message containing the MN request for establishing the bearing, and determines that the SN can share more bearing proportions according to the bearing requirements and the available resources of the SN.
And step 3: the SN calculates the current bearable bearing size and the bearable proportion aiming at the current bearing according to the availability of the resource of the SN, and initiates a bearing configuration negotiation request message.
The bearer configuration negotiation request message may only modify one bearer or modify multiple bearers, and the bearer configuration negotiation request message includes a bearer ID and a suggested bearer type that suggest modifying the bearer, and the SN may suggest modifying a split bearer to an SCG bearer, or may adjust a ratio of the split bearer, taking increasing the split bearer as an example, the bearer configuration negotiation request message also needs to include a ratio that the bearer can bear, where the ratio may be a separation ratio of the entire bearer that the SN wishes to bear, or may be a multiple that the SN wishes to bear the bearer that the MN requests the SN to share; and/or
The bearer configuration negotiation request message contains the capabilities that the SN recommends the bearer is desired to assume, e.g., maximum rate or AMBR. Or
The bearer configuration negotiation request message includes the proportion of all SCG bearers that are desired to be assumed.
And 4, step 4: and the MN receives the bearing type negotiation request message of the SN side, reconfigures the bearing of the SN side according to the capability of the SN according to the information provided by the SN in the bearing type negotiation request message, and sends the modified bearing configuration request message of the SN side to the SN. Or the MN sends an acknowledgement or rejection message to the SN according to whether the negotiation request of the SN side is accepted or not.
And 5: and the SN receives a response message which is sent by the MN and contains the adjusted SN side bearing configuration, and configures the corresponding bearing according to the request of the MN. And sends a response message for step 1 to continue the corresponding flow initiated by the MN. The SN may reply with a reject message for the request message of step 1 if the SN cannot satisfy all request messages of the MN. Or the SN receives the confirmation message sent by the MN, performs corresponding SCG configuration and sends a response message aiming at the step 1 to continue the corresponding flow initiated by the MN, or receives a rejection message sent by the MN, and the SN stops the flow.
Example 4: the SN proactively requests to take up fewer bearers for the already configured bearers.
The specific flow of message transmission between the MN and the SN includes:
step 1: the SN detects that the link quality is damaged, the bearing capacity is reduced or the available resources are reduced, and the bearing capacity is reduced.
Step 2: the SN calculates the current bearable bearing size and the bearable proportion aiming at the current bearing according to the availability of the resource of the SN, and initiates a bearing configuration negotiation request message.
The bearer configuration negotiation request message may only modify one bearer or modify multiple bearers, and the bearer configuration negotiation request message includes a bearer ID and a bearer type suggested to modify the bearer, the SN may suggest to modify an SCG bearer into a split bearer type or an MCG type, or may adjust a ratio of split bearers, and the bearer configuration negotiation request message further includes a ratio that can be borne by the bearer, where the ratio may be a split ratio of the entire bearer that the SN desires to bear, or a relative ratio of bearers that the SN desires to bear the currently shared bearer, and/or
The bearer configuration negotiation request message contains the capabilities that the SN recommends the bearer is desired to assume, e.g., maximum rate or AMBR. Or
The bearer configuration negotiation request message includes the proportion of all SCG bearers that are desired to be assumed.
And step 3: and the MN receives the bearing type negotiation request message of the SN side, reconfigures the bearing of the SN side according to the capability of the SN according to the information provided by the SN in the bearing type negotiation request message, and sends the modified bearing configuration request message of the SN side to the SN. And the subsequent relevant processes are completed. The reconfiguration of SCG bearers can also be rejected in the response message if the MN decides not to adjust the configuration at the SN side. Or the MN sends an acknowledgement or rejection message to the SN according to whether the negotiation request of the SN side is accepted or not.
And 5: and the SN receives a response message which is sent by the MN and contains the adjusted SN side bearing configuration, configures the corresponding bearing according to the request of the MN or receives a confirmation message sent by the MN, performs the corresponding SCG configuration and completes the subsequent related flow. If MN refuses to adjust SN side load configuration, SN continues current load transmission.
Example 5: the SN actively requests more bearers to be taken.
Step 1: the SN detects that there are sufficient resources available to take on more bearers.
Step 2: the SN calculates the size of the bearer that can be currently borne and the ratio that can be borne for the current bearer according to the availability of its own resources, and initiates a bearer configuration negotiation request message, where the bearer configuration negotiation request message may only modify one bearer or modify multiple bearers, and then the bearer configuration negotiation request message includes the bearer ID and the suggested bearer type that suggest modifying the bearer, and the SN may suggest modifying the split bearer into an SCG bearer type, or may adjust the ratio of the split bearer, taking the split bearer type as an example, and the bearer configuration negotiation request message also needs to include the ratio that the bearer can bear, where the ratio may be the separation ratio of the entire bearer that the SN wants to bear, or may be a multiple of the bearer that the SN wants to bear the current shared bearer. Or the bearer configuration negotiation request message contains the SN suggesting the capability the bearer wishes to assume, e.g., maximum rate or AMBR.
And step 3: and the MN receives the bearing type negotiation request message of the SN side, reconfigures the bearing of the SN side according to the capability of the SN according to the information provided by the SN, sends the modified bearing configuration request message of the SN side to the SN or sends a confirmation message to the SN, and completes the subsequent related flow. The reconfiguration of SCG bearers can also be rejected in the response message if the MN decides not to adjust the configuration at the SN side. Or the MN sends an acknowledgement or rejection message to the SN according to whether the negotiation request at the SN side is accepted or not.
And 5: and the SN receives a response message which is sent by the MN and contains the adjusted SN side bearing configuration, configures the corresponding bearing according to the request of the MN or receives a confirmation message sent by the MN, and completes the configuration according to the configuration information in the negotiation request message. And the subsequent relevant processes are completed. If MN refuses to adjust SN side load configuration, SN continues current load transmission.
The bearer configuration negotiation request messages in embodiments 4 and 5 are not limited to be negotiated on a per bearer basis, but may also be negotiated with the MN on the basis of all bearers or capabilities that can be assumed by the SN. The above embodiments are not limited to changing a split bearer type application to SCG type or SCG type request to split type, any type conversion that can implement SN capabilities and be understood by the MN can be supported.
The method is not limited to an EN-DC scenario, any double-connection or multi-connection scenario can equivalently use the process, and the method takes an SN modification process as an example for description, but the method is not limited to embedding the process in the SN modification process, the method is also applicable to an SN addition process initiated by an MN, and is not limited to the two processes, and any process requiring the SN to perform bearer negotiation with the MN can trigger the process.
The following describes the apparatus provided in the embodiments of the present application.
Referring to fig. 4, on the SN side, a message sending apparatus provided in an embodiment of the present application includes:
a memory 520 for storing program instructions;
a processor 500 for calling the program instructions stored in the memory, and executing, according to the obtained program:
determining that the auxiliary node SN needs to carry out bearing configuration negotiation with the main node MN;
a bearer configuration negotiation request message is sent to the MN via transceiver 510.
Optionally, the bearer configuration negotiation request message specifically includes one or a combination of the following information:
the bearer type suggested by the SN;
a bearer split ratio suggested by the SN;
the MN is required to adjust the bearer ID of the bearer configuration;
the SN is capable of supporting transmission capabilities.
Optionally, the bearer type suggested by the SN specifically includes:
the SN suggests the MN to reconfigure the bearer requested to be configured or the type of configured bearer to be a split bearer type, a secondary cell group, SCG, bearer type, or a master cell group, MCG, bearer type.
Optionally, the bearer configuration negotiation request message is sent in one or more of the following flows:
SN addition process;
SN modification flow;
the process comprises SN bearing establishment or content modification;
the SN determines the flow of independent trigger.
Optionally, determining that the SN needs to perform bearer configuration negotiation with the MN specifically includes:
determining that the SN cannot assume a bearer assigned to the SN by the MN; or,
determining that the SN can assume that the MN allocates more bearers for the SN.
Optionally, the processor 500 is further configured to:
and receiving a bearer configuration negotiation response message replied by the MN.
A transceiver 510 for receiving and transmitting data under the control of the processor 500.
Wherein in fig. 4 the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 500 and various circuits of memory represented by memory 520 being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 510 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 500 in performing operations.
The processor 500 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD).
Referring to fig. 5, on the MN side, a message receiving apparatus provided in an embodiment of the present application includes:
a memory 505 for storing program instructions;
a processor 504 for calling the program instructions stored in the memory, and executing:
receiving a bearer configuration negotiation request message sent by the secondary node SN to the primary node MN through the transceiver 501;
and processing the bearing configuration negotiation request message.
Optionally, the bearer configuration negotiation request message specifically includes one or a combination of the following information:
the bearer type suggested by the SN;
a bearer split ratio suggested by the SN;
the MN is required to adjust the bearer ID of the bearer configuration;
the SN is capable of supporting transmission capabilities.
Optionally, the bearer type suggested by the SN specifically includes:
the SN suggests the MN to reconfigure the type of bearer requested to be configured or configured as a split bearer type, an SCG bearer type, or an MCG bearer type.
Optionally, the bearer configuration negotiation request message is sent in one or more of the following flows:
SN addition process;
SN modification flow;
the process comprises SN bearing establishment or content modification;
the SN determines the flow of independent trigger.
Optionally, the processing the bearer configuration negotiation request message specifically includes:
the MN allocates a new bearer for the SN or adjusts the configuration of the bearer allocated or already allocated to the SN according to the bearer configuration negotiation request message, and replies a bearer configuration negotiation response message to the SN, wherein the bearer configuration message carries the bearer configuration information of the SN or receives a response indication message of the SN bearer configuration negotiation request;
or replying a bearer configuration negotiation response message for rejecting SN negotiation to the SN according to the bearer configuration negotiation request message.
A transceiver 501 for receiving and transmitting data under the control of a processor 504.
In FIG. 5, a bus architecture (represented by bus 506), the bus 506 may include any number of interconnected buses and bridges, with the bus 506 linking together various circuits including one or more processors, represented by the processor 504, and memory, represented by the memory 505. The bus 500 may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface 503 provides an interface between the bus 506 and the transceiver 501. The transceiver 501 may be one element or may be multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. Data processed by processor 504 is transmitted over a wireless medium via antenna 502, and further, antenna 502 receives data and transmits data to processor 504.
The processor 504 is responsible for managing the bus 506 and general processing, and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 505 may be used to store data used by processor 504 in performing operations.
Alternatively, the processor 504 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device).
Referring to fig. 6, on the SN side, another message sending apparatus provided in the embodiment of the present application includes:
a determining unit 11, configured to determine that the secondary node SN needs to perform bearer configuration negotiation with the primary node MN;
a sending unit 12, configured to send a bearer configuration negotiation request message to the MN.
Referring to fig. 7, on the MN side, another message receiving apparatus provided in this embodiment of the present application includes:
a receiving unit 21, configured to receive a bearer configuration negotiation request message sent by the secondary node SN to the primary node MN;
a processing unit 22, configured to process the bearer configuration negotiation request message.
The SN and the MN may both be base stations on the access network side, and thus any device provided in the embodiments of the present application may be a base station.
Embodiments of the present application provide a computer storage medium for storing computer program instructions for the above-mentioned computing device, which includes a program for executing any one of the methods provided in the above-mentioned embodiments of the present application.
The computer storage media may be any available media or data storage device that can be accessed by a computer, including, but not limited to, magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.
The method provided by the embodiment of the application is applied to network equipment.
A network device may be a base station (e.g., access point) that refers to a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminals. The base station may be configured to interconvert received air frames and IP packets as a router between the wireless terminal and the rest of the access network, which may include an Internet Protocol (IP) network. The base station may also coordinate management of attributes for the air interface. For example, the Base Station may be a Base Transceiver Station (BTS) in GSM or CDMA, a Base Station (NodeB) in WCDMA, an evolved Node B (NodeB or eNB or e-NodeB) in LTE, or a Base Station gNB in NR system, which is not limited in the embodiment of the present invention.
To sum up, in the technical solution provided in this embodiment, the bearer negotiation function is supported in dual connectivity or multi connectivity, the SN suggests the MN to configure the SN according to its available resources and bearer characteristics, and provides corresponding information for the MN to refer to, and the MN reconfigures the bearer according to the information in the bearer type negotiation request sent by the SN. I.e. allowing negotiation of bearer types during bearer sharing, makes operation of bearer types more flexible and makes resource utilization more efficient.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims (25)

1. A method for sending a message, the method comprising:
the auxiliary node SN determines that bearing configuration negotiation with the main node MN is required; the bearing configuration negotiation refers to the negotiation of the bearing capacity borne by the SN according to the resource availability of the SN;
and the SN sends a bearing configuration negotiation request message to the MN, so that the MN adjusts the bearing configuration according to the bearing configuration negotiation request message of the SN, and the SN can bear the allocated bearing.
2. The method according to claim 1, wherein the bearer configuration negotiation request message specifically includes one or a combination of the following information:
the bearer type suggested by the SN;
a bearer split ratio suggested by the SN;
the MN is required to adjust the bearer ID of the bearer configuration;
the SN is capable of supporting transmission capabilities.
3. The method according to claim 2, wherein the bearer type suggested by the SN specifically includes:
the SN suggests the MN to reconfigure the bearer requested to be configured or the type of configured bearer to be a split bearer type, a secondary cell group, SCG, bearer type, or a master cell group, MCG, bearer type.
4. The method of claim 1, wherein the bearer configuration negotiation request message is sent in one or more of the following procedures:
SN addition process;
SN modification flow;
the process comprises SN bearing establishment or content modification;
the SN determines the flow of independent trigger.
5. The method according to any one of claims 1 to 4, wherein the SN determining that bearer configuration negotiation with the MN is required specifically comprises:
the SN determines that the bearer allocated to the SN by the MN cannot be assumed; or,
the SN determines that the MN can be assumed to allocate more bearers for the SN.
6. The method of any one of claims 1 to 4, further comprising:
and the SN receives the bearing configuration negotiation response message replied by the MN.
7. A method for receiving a message, the method comprising:
a main node MN receives a bearing configuration negotiation request message sent by an auxiliary node SN; the bearer configuration negotiation request message is a negotiation request message of the SN about the bearing capacity assumed by the SN according to the resource availability of the SN;
and the MN adjusts the bearer configuration according to the bearer configuration negotiation request message of the SN so that the SN can bear the allocated bearer.
8. The method according to claim 7, wherein the bearer configuration negotiation request message specifically includes one or a combination of the following information:
the bearer type suggested by the SN;
a bearer split ratio suggested by the SN;
the MN is required to adjust the bearer ID of the bearer configuration;
the SN is capable of supporting transmission capabilities.
9. The method according to claim 8, wherein the bearer type suggested by the SN specifically includes:
the SN suggests the MN to reconfigure the type of bearer requested to be configured or configured as a split bearer type, an SCG bearer type, or an MCG bearer type.
10. The method of claim 7, wherein the bearer configuration negotiation request message may be sent in one or more of the following procedures:
SN addition process;
SN modification flow;
the process comprises SN bearing establishment or content modification;
the SN determines the flow of independent trigger.
11. The method according to any of claims 7 to 10, wherein the MN adjusting the bearer configuration according to the bearer configuration negotiation request message of the SN specifically comprises:
and the MN allocates a new bearer for the SN or adjusts the configuration of the bearer allocated to the SN or allocated to the SN according to the bearer configuration negotiation request message, and replies a bearer configuration negotiation response message to the SN, wherein the bearer configuration message carries the bearer configuration information of the SN or a response indication message for receiving the SN bearer configuration negotiation request.
12. A message transmission apparatus, characterized in that the apparatus comprises:
a memory for storing program instructions;
a processor for calling the program instructions stored in the memory, executing according to the obtained program:
determining that the auxiliary node SN needs to carry out bearing configuration negotiation with the main node MN; the bearer configuration negotiation refers to the negotiation of the bearer capability assumed by the SN according to the resource availability of the SN;
and sending a bearer configuration negotiation request message to the MN, so that the MN adjusts the bearer configuration according to the bearer configuration negotiation request message of the SN, and the SN can bear the allocated bearer.
13. The apparatus according to claim 12, wherein the bearer configuration negotiation request message specifically includes one or a combination of the following information:
the bearer type suggested by the SN;
a bearer split ratio suggested by the SN;
the MN is required to adjust the bearer ID of the bearer configuration;
the SN is capable of supporting transmission capabilities.
14. The apparatus according to claim 13, wherein the bearer type suggested by the SN specifically includes:
the SN suggests the MN to reconfigure the bearer requested to be configured or the type of configured bearer to be a split bearer type, a secondary cell group, SCG, bearer type, or a master cell group, MCG, bearer type.
15. The apparatus of claim 12,
the bearer configuration negotiation request message is sent in one or more of the following flows:
SN addition process;
SN modification flow;
the process comprises SN bearing establishment or content modification;
the SN determines the flow of independent trigger.
16. The apparatus according to any of claims 12 to 15, wherein determining that the SN needs to perform bearer configuration negotiation with the MN specifically comprises:
determining that the SN is unable to afford the bearer assigned to the SN by the MN; or,
determining that the SN can assume that the MN allocates more bearers for the SN.
17. The apparatus of any of claims 12 to 15, wherein the processor is further configured to:
and receiving a bearer configuration negotiation response message replied by the MN.
18. A message receiving apparatus, comprising:
a memory for storing program instructions;
a processor for calling the program instructions stored in the memory and executing according to the obtained program:
receiving a bearing configuration negotiation request message sent to a main node MN by an auxiliary node SN; the bearer configuration negotiation request message is a negotiation request message of the bearer capability assumed by the SN according to the resource availability of the SN;
and adjusting the bearer configuration according to the bearer configuration negotiation request message of the SN so that the SN can bear the allocated bearer.
19. The apparatus according to claim 18, wherein the bearer configuration negotiation request message specifically includes one or a combination of the following information:
a bearer type suggested by the SN;
a bearer split ratio suggested by the SN;
the MN is required to adjust the bearer ID of the bearer configuration;
the SN is capable of supporting transmission capabilities.
20. The apparatus according to claim 19, wherein the bearer type suggested by the SN specifically includes:
the SN suggests the MN to reconfigure the type of bearer requested to be configured or configured as a split bearer type, an SCG bearer type, or an MCG bearer type.
21. The apparatus of claim 18, wherein the bearer configuration negotiation request message is sent in one or more of the following procedures:
SN adding flow;
SN modification flow;
includes SN load building or content modifying flow;
the SN determines the flow of independent trigger.
22. The apparatus according to any one of claims 18 to 21, wherein adjusting bearer configuration according to the bearer configuration negotiation request message of the SN, so that the SN can bear the allocated bearer specifically includes:
and allocating a new bearer to the SN or adjusting the configuration of the bearer allocated to the SN or already allocated to the SN according to the bearer configuration negotiation request message, and replying a bearer configuration negotiation response message to the SN, wherein the bearer configuration message carries the configuration information of the bearer requesting the SN or the response indication message for receiving the SN bearer configuration negotiation request.
23. A message transmission apparatus, comprising:
a determining unit, configured to determine that the secondary node SN needs to perform bearer configuration negotiation with the primary node MN; the bearer configuration negotiation refers to the negotiation of the bearer capability assumed by the SN according to the resource availability of the SN;
a sending unit, configured to send a bearer configuration negotiation request message to the MN, so that the MN adjusts bearer configuration according to the bearer configuration negotiation request message of the SN, so that the SN can bear the allocated bearer.
24. A message receiving apparatus, comprising:
the receiving unit is used for receiving a bearing configuration negotiation request message sent to the main node MN by the auxiliary node SN; the bearer configuration negotiation request message is a negotiation request message of the SN about the bearing capacity assumed by the SN according to the resource availability of the SN;
and the processing unit is used for adjusting the bearer configuration according to the bearer configuration negotiation request message of the SN, so that the SN can bear the allocated bearer.
25. A computer storage medium having computer-executable instructions stored thereon for causing a computer to perform the method of any one of claims 1 to 11.
CN201810129034.9A 2018-02-08 2018-02-08 Message transmission method and device and computer storage medium Active CN110139324B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810129034.9A CN110139324B (en) 2018-02-08 2018-02-08 Message transmission method and device and computer storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810129034.9A CN110139324B (en) 2018-02-08 2018-02-08 Message transmission method and device and computer storage medium

Publications (2)

Publication Number Publication Date
CN110139324A CN110139324A (en) 2019-08-16
CN110139324B true CN110139324B (en) 2022-07-12

Family

ID=67567462

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810129034.9A Active CN110139324B (en) 2018-02-08 2018-02-08 Message transmission method and device and computer storage medium

Country Status (1)

Country Link
CN (1) CN110139324B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822698B (en) * 2019-11-15 2022-04-05 大唐移动通信设备有限公司 Uplink data distribution method and device

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104105221B (en) * 2013-04-15 2019-05-21 中兴通讯股份有限公司 A kind of implementation method of dual link and base station
EP2836012B1 (en) * 2013-08-09 2016-03-30 Alcatel Lucent Method and system for setup or modification of data flows, primary node, secondary node, UE and computer program product
US20170071023A1 (en) * 2014-03-14 2017-03-09 Nec Europe Ltd. Method, user equipment, master evolved node b and communication system for dual connectivity

Also Published As

Publication number Publication date
CN110139324A (en) 2019-08-16

Similar Documents

Publication Publication Date Title
KR102221747B1 (en) Switching method and device
US11706829B2 (en) Method for data forwarding in a small cell system
CN110972107B (en) Load balancing method and device
KR102330739B1 (en) Radio bearer configuration method and device
EP2739082B1 (en) Load sharing method, device, and system
JP6785346B2 (en) Methods and equipment for establishing paths for data offload
US20180279390A1 (en) Method and device for establishing an auxiliary signaling link, base station and user equipment
CN109429368B (en) Message sending method, system, device, network element, storage medium and processor
EP3858086A1 (en) Methods and apparatuses for handling dual connectivity in redundancy transmission
CN108924961B (en) Terminal capability negotiation method and device
CN109151896B (en) Transmission rate control method and device
US20220150763A1 (en) Methods and apparatus for optimized inter-system handover
CN114009076A (en) Communication method, device and system
CN110139324B (en) Message transmission method and device and computer storage medium
CN109803316B (en) Method, device and system for processing data stream
CN109803390B (en) Message and strategy sending method and device, storage medium and processor
CN109963315A (en) A kind of prothetic group station distribution method and device
US20240314679A1 (en) Method and device for session establishment and control
CN103491580A (en) Method, system and device for transmitting user plane data
CN115942404A (en) Session establishment and control method and device
CN108810926B (en) Data transmission method and related equipment
CN117545086A (en) Wireless resource allocation method, network element, device and storage medium
CN116980999A (en) Method for supporting switching
CN114390623A (en) Method for supporting switching

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20210531

Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing

Applicant after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd.

Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road

Applicant before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY

GR01 Patent grant
GR01 Patent grant