CN110022587B

CN110022587B - Bearing management method and bearing management device

Info

Publication number: CN110022587B
Application number: CN201810023628.1A
Authority: CN
Inventors: 王文
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2018-01-10
Filing date: 2018-01-10
Publication date: 2021-01-08
Anticipated expiration: 2038-01-10
Also published as: CN110022587A; WO2019137367A1

Abstract

The invention provides a bearing management method and a bearing management device. The bearer management method is used for one of a network element and a mobile communication terminal at a network side, and comprises the following steps: and sending indication information to the other one of the network element at the network side and the mobile communication terminal, wherein the indication information is used for indicating whether the bearer number expansion is supported. The invention standardizes the information interaction between the network element at the network side and the mobile communication terminal when the network element supporting the extension of the bearing quantity and the network element not supporting the extension of the bearing quantity coexist, so that the network element at the network side and the mobile communication terminal can inform the other side whether to support the extension of the bearing quantity, thereby the mobile communication terminal supporting the extension of the bearing quantity can establish the bearing of the extension part with the network element supporting the extension of the bearing quantity, and when either one of the two sides does not support the extension of the bearing quantity, the mobile communication terminal and/or the network side can reasonably distribute the bearing resources based on the interactive information.

Description

Bearing management method and bearing management device

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a bearer management method and a bearer management apparatus.

Background

Compared with the 3G communication system and the 4G communication system, the maximum number of the bearers supported by the 5G communication system is expanded, and the 5G communication system is specified to be expanded from the original maximum 8 bearers to the maximum 15 bearers in the 78 th-time full meeting of the TSG SA.

In order to align with the 5G communication system, the number of bearers of the 4G communication system is expected to be extended to 15, so that the network has coexistence phenomena of network elements supporting the extension of the number of bearers and network elements not supporting the extension of the number of bearers.

Therefore, it is necessary to specify the interaction between the mobile communication terminal side and the network side when the network element supporting the extension of the bearer number and the network element not supporting the extension of the bearer number coexist.

Disclosure of Invention

The invention aims to provide a bearing management method and a bearing management device, which are used for standardizing information interaction between a network element at a network side and a mobile communication terminal when a network element supporting bearing quantity expansion and a network element not supporting bearing quantity expansion coexist.

In order to achieve the above object, in one aspect, an embodiment of the present invention provides a bearer management method, used in one of a network element and a mobile communication terminal, where the bearer management method includes:

and sending indication information to the other one of the network element at the network side and the mobile communication terminal, wherein the indication information is used for indicating whether the bearer number expansion is supported.

On the other hand, an embodiment of the present invention further provides a bearer management method, used in one of a network element on a network side and a mobile communication terminal, where the bearer management method includes:

and receiving indication information sent by the other one of the network element at the network side and the mobile communication terminal, wherein the indication information is used for indicating whether the bearer number expansion is supported.

In addition, an embodiment of the present invention further provides a bearer management method, configured to execute a network element on a network side, where the bearer management method includes:

and when the number of the bearers to be migrated to the target network element which does not support the bearer number expansion is larger than a preset threshold, releasing part of the bearers, wherein the number of the reserved bearers is smaller than or equal to the preset threshold.

In addition, an embodiment of the present invention further provides a bearer management apparatus, configured to be used in one of a network element on a network side and a mobile communication terminal, where the bearer management apparatus includes:

a sending module, configured to send indication information to another one of the network element on the network side and the mobile communication terminal, where the indication information is used to indicate whether bearer number extension is supported.

In addition, an embodiment of the present invention further provides a bearer management apparatus, configured to be used in one of a network element and a mobile communication terminal, where the bearer management apparatus includes:

a receiving module, configured to receive indication information sent by another one of the network element on the network side and the mobile communication terminal, where the indication information is used to indicate whether bearer number extension is supported.

In addition, another bearer management device is further provided in an embodiment of the present invention, where the bearer management device is used for a network side to execute a network element, and the bearer management device includes:

and the releasing module is used for releasing part of the bearers when the number of the bearers to be migrated to the target network element which does not support the bearer number expansion is greater than a preset threshold, wherein the number of the reserved bearers is less than or equal to the preset threshold.

In addition, an embodiment of the present invention further provides a bearer management apparatus, including: a processor, a memory and a computer program stored on said memory and executable on said processor, said computer program realizing all the steps of the bearer management method provided by the invention when executed by the processor.

Furthermore, an embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements all the steps in the bearer management method provided by the present invention.

The scheme of the invention has the following beneficial effects:

the specific embodiment of the invention specifies the information interaction between the network element at the network side and the mobile communication terminal when the network element supporting the extension of the bearing quantity and the network element not supporting the extension of the bearing quantity coexist, so that the network element at the network side and the mobile communication terminal can inform the other side whether to support the extension of the bearing quantity, thereby the mobile communication terminal supporting the extension of the bearing quantity can establish the bearing of the extension part with the network element at the network side supporting the extension of the bearing quantity, and when either one of the two sides does not support the extension of the bearing quantity, the mobile communication terminal and/or the network side can reasonably distribute the bearing resources based on the interactive information.

Drawings

Fig. 1 is a schematic diagram illustrating steps of a bearer management method for one of a network element on a network side and a mobile communication terminal according to an embodiment of the present invention;

fig. 2 is a schematic step diagram of a bearer management method for one of a network element on a network side and a mobile communication terminal according to an embodiment of the present invention;

fig. 3 is a schematic diagram illustrating steps of a bearer management method performed at a network side according to an embodiment of the present invention;

fig. 4-fig. 13 are schematic diagrams of different implementations of a bearer management method according to an embodiment of the present invention;

fig. 14 is a schematic logical structure diagram of a bearer management apparatus for one of a network element on a network side and a mobile communication terminal according to an embodiment of the present invention;

fig. 15 is a schematic logical structure diagram of a bearer management apparatus for one of a network element on a network side and a mobile communication terminal according to an embodiment of the present invention;

fig. 16 is a schematic structural diagram of a bearer management apparatus implemented on a network side according to an embodiment of the present invention;

fig. 17 is a schematic view of an actual structure of a bearer management apparatus according to an embodiment of the present invention.

Detailed Description

In order to make the technical problems, technical solutions and advantages of the present invention more apparent, the following detailed description is given with reference to the accompanying drawings and specific embodiments. In the following description, specific details such as specific configurations and components are provided only to help the full understanding of the embodiments of the present invention. Thus, it will be apparent to those skilled in the art that various changes and modifications may be made to the embodiments described herein without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

In various embodiments of the present invention, it should be understood that the sequence numbers of the following processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

The invention is used for standardizing the information interaction between the network element at the network side and the mobile communication terminal when the network element supporting the load number expansion and the network element not supporting the load number expansion coexist.

In one aspect, an embodiment of the present invention provides a bearer management method, used in one of a network element and a mobile communication terminal (e.g., a user equipment), as shown in fig. 1, the bearer management method includes:

step 11, sending indication information to the other one of the network element at the network side and the mobile communication terminal, where the indication information is used to indicate whether bearer number extension is supported.

For example: the indication information sent by the network side network element to the mobile communication terminal is used for indicating whether the network side network element supports the load number expansion; correspondingly, the indication information sent by the communication terminal to the network element at the network side is used to indicate whether the communication terminal supports the bearer number extension.

It should be understood that the bearer management method shown in fig. 1 actually includes two technical solutions, that is:

the mobile communication terminal sends indication information to a network side network element, wherein the indication information is used for indicating whether the bearing quantity expansion is supported or not;

and

and the network element at the network side sends indication information to the mobile communication terminal, wherein the indication information is used for indicating whether the bearer number expansion is supported or not.

Of course, both may be present.

The technical effects are explained as follows.

When the network element at the network side sends the indication information to the mobile communication terminal, and assuming that the network element at the network side does not support the extension of the number of bearers, when the mobile communication terminal has established 8 bearers at present, even if more bearer resource requirements exist, the mobile communication terminal knows that the network element at the network side does not support the extension of the number of bearers, so that more bearer resources are not required to be requested from the network element at the network side;

similarly, when the mobile communication terminal sends the indication information to the network element on the network side, and assuming that the mobile communication terminal does not support the bearer quantity extension, when the mobile communication terminal has currently established 8 bearers, even if the network element on the network side supports more bearer resources, the network element on the network side knows that the mobile communication terminal does not support the bearer quantity extension, so that more bearer resources which cannot be used by the mobile communication terminal are not allocated to the mobile communication terminal.

The following describes a bearer management method according to an embodiment of the present invention in detail.

For example, to avoid increasing the signaling overhead of the network, the indication information of the embodiment of the present invention may be carried by an existing signaling and/or information element.

For example, when the bearer management method according to the specific embodiment of the present invention is used in a mobile communication terminal, the mobile communication terminal may send a user equipment network capability information element carrying the indication information to a network element on a network side, where the indication information is used to indicate whether the mobile communication terminal supports bearer number extension.

Wherein the network capability information element is EPS related information or GPRS interactive information provided by the existing network, which may affect the way the network handles the operation of the mobile communication terminal. The structure of the current network capability information is shown in the following table:

wherein the network capability information element comprises 15 octets, each octet comprising eight bits.

Reference is made to octet3, where bit numbers 1 to 8 are used to indicate whether the terminal supports the algorithms EEA0, 128-EEA1, 128-EEA2, 128-EEA3, EEA4, EEA5, EEA6, EEA7, etc., respectively.

Referring to octet9, bit 5 (dcnr) is used to indicate whether the terminal supports dual connectivity with the NR communication system.

The EEA0, 128-EEA1, and DCNR are described below as examples.

Wherein, the value of the 8 th bit of octet3 in the network capability information element is 0 or 1, which represents the following information:

the 8 th bit of the octet3 takes a value of 1 to indicate that the EPS (Evolved Packet System) supports the EEA0 algorithm;

the 8 th bit of octet3 is taken as 0 to indicate that the EPS does not support the EEA0 algorithm;

wherein, the value of the 7 th bit of octet3 in the network capability information element is 0 or 1, which represents the following information:

the 7 th bit of the octet3 with the value of 1 indicates that the EPS supports the 128-EEA1 algorithm;

the 7 th bit value of octet3 of 0 indicates that the EPS does not support the 128-EEA1 algorithm.

Wherein, the value of the 5 th bit of octet9 in the network capability information element is 0 or 1, which represents the following information:

the 5 th bit value of Octet9 represents that double connection with the NR communication system is supported;

the value of the 5 th bit of octet9 of 0 indicates that dual connectivity with the NR communication system is not supported.

In combination with the above table, it can be found that, in the network capability information element, some bits are marked as "0 spare", which means that these bits are not defined and belong to the bits to be defined, and the present implementation may use the spare bits to represent the above indication information.

As can be seen from the above table, the 6 th, 7 th, or 8 th bit in the 9 th octet or any one bit in the 10 th to 15 th octet of the network capability information element is a bit to be defined, and the indication information of the specific embodiment of the present invention may be defined by one or more of these bits.

For example, in the embodiment of the present invention, the indication information (inobe) may be represented by the 6 th bit in the ninth bit group of the network capability information element, and the structure of the 9 th octet of the modified network capability information element is shown in the following table:

wherein inobee represents the indication information, and the value in the network capability information element is 0 or 1.

After the modification, the 6 th bit value 1 of the ninth bit group indicates that the mobile communication terminal supports the bearer quantity expansion, and the 6 th bit value 0 of the ninth bit group indicates that the mobile communication terminal does not support the bearer quantity expansion.

Of course, using the existing network capability information element to carry the indication information is only one possible solution in the embodiment of the present invention, and as another solution, the embodiment of the present invention may also use another newly defined information element to carry the indication information.

In order to save signaling overhead and air interface resources, in the specific embodiment of the present invention, the indication information may be carried by an existing signaling, for example:

the mobile communication terminal can carry the indication information through the attachment request message in the attachment process or the tracking area update message in the tracking area update process, so that the network side network element can obtain the indication information carried in the attachment request message or the tracking area update message after receiving the attachment request message or the tracking area update message, and further know whether the mobile communication terminal supports the extension of the bearing quantity.

And the network element at the network side correspondingly can also carry the indication information through the attachment acceptance message in the attachment process or the tracking area acceptance message in the tracking area updating process, so that the mobile communication terminal can obtain the indication information carried in the attachment acceptance message or the tracking area acceptance message after receiving the attachment acceptance message or the tracking area acceptance message, and further know whether the network side supports the load number expansion.

That is, in the specific embodiment of the present invention, the sending of the indication information to the other one of the network element on the network side and the mobile communication terminal, where the indication information is used to indicate whether the extension office of bearer number is supported may be:

the mobile communication terminal sends a request message to a network element at a network side, wherein the request message is an attachment request message or a tracking area update request message and carries first indication information, and the first indication information is used for indicating whether the mobile communication terminal supports the load number expansion;

or

The network side network element sends an acceptance message to the mobile communication terminal, wherein the acceptance message is an attachment acceptance message or a tracking area update acceptance message and carries second indication information, and the second indication information is used for indicating whether the network side network element supports the load-bearing quantity expansion.

It should be further emphasized that the above-mentioned indication information is transmitted by the existing signaling only in an optional manner, and is not a necessary implementation manner, and as another possible solution, the indication information of the embodiment of the present invention may also be carried by dedicated signaling and/or dedicated information elements.

On the other hand, another embodiment of the present invention further provides a bearer management method, used in one of a network element and a mobile communication terminal on a network side, as shown in fig. 2, the bearer management method includes:

step 21, receiving indication information sent by the other one of the network element at the network side and the mobile communication terminal, where the indication information is used to indicate whether bearer number extension is supported.

It should be understood that the bearer management method shown in fig. 2 actually includes two technical solutions, that is:

the mobile communication terminal receives indication information sent by a network side network element, wherein the indication information is used for indicating whether the network side network element supports the load-bearing quantity expansion or not;

and

the network element at the network side receives indication information sent by the mobile communication terminal, wherein the indication information is used for indicating whether the mobile communication terminal supports the load number expansion.

When the mobile communication terminal receives the indication information sent by the network side network element, and supposing that the network side network element does not support the bearer quantity expansion, when the mobile communication terminal has established 8 bearers at present, even if more bearer resource requirements exist, the mobile communication terminal knows that the network side network element does not support the bearer quantity expansion, so that more bearer resources are not required to the network side network element;

similarly, when the network element on the network side receives the indication information sent by the mobile communication terminal, and assuming that the mobile communication terminal does not support bearer quantity extension, when the mobile communication terminal has currently established 8 bearers, even if the network element on the network side supports more bearer resources, the network element on the network side knows that the mobile communication terminal does not support bearer quantity extension, so that more bearer resources are not allocated to the mobile communication terminal.

In addition, to avoid increasing signaling overhead of the network, the indication information of the embodiment of the present invention may be carried by an existing signaling and/or information element.

Illustratively, with reference to the above description, the indication information of the specific embodiment of the present invention may be carried by the ue network capability information element. Specifically, the indication information is defined by the 6 th, 7 th or 8 th bit in the 9 th octet or any one bit in the 10 th to 15 th octet of the network capability information element of the user equipment.

Of course, using the network capability information element to carry the indication information is only one implementation manner of the embodiment of the present invention, and as another feasible solution, the embodiment of the present invention may also set a separate information element to carry the indication information.

From the signaling aspect, the indication information of the embodiment of the present invention may also be carried through an existing signaling or a new signaling.

Certainly, in order to save signaling overhead and air interface resources, in the specific embodiment of the present invention, the existing signaling between the mobile communication terminal and the network element on the network side is used to carry the indication information, for example:

the mobile communication terminal can carry the indication information through the attachment request message in the attachment process or the tracking area update message in the tracking area update process, so that the network side network element can receive the attachment request message or the tracking area update message and acquire the indication information carried in the attachment request message or the tracking area update message, and further know whether the mobile communication terminal supports the extension of the bearing quantity.

And the network element at the network side correspondingly can also carry the indication information through the attachment acceptance message in the attachment process or the tracking area acceptance message in the tracking area updating process, so that the mobile communication terminal can receive the attachment acceptance message or the tracking area acceptance message and acquire the indication information carried in the attachment acceptance message or the tracking area acceptance message, and further know whether the network side supports the load number expansion.

That is, in the specific embodiment of the present invention, receiving indication information sent by another one of the network element on the network side and the mobile communication terminal, where the indication information is used to indicate whether bearer number extension is supported may specifically be:

a network side network element receives a request message sent by a mobile communication terminal, wherein the request message carries first indication information which is used for indicating whether the mobile communication terminal supports the load number expansion; the request message is an attachment request message or a tracking area update request message;

alternatively, the first and second electrodes may be,

the mobile communication terminal receives an acceptance message sent by a network side network element, wherein the acceptance message carries second indication information, the second indication information is used for indicating whether the network side network element supports bearer quantity expansion, and the acceptance message is an attachment acceptance message or a tracking area update acceptance message.

Of course, in addition to the foregoing implementation manners, the indication information according to the embodiment of the present invention may also be transmitted through dedicated signaling.

Through the above process, the mobile communication terminal may know the bearer number expansion support capability of the network side network element, and/or the network side network element may know the bearer number expansion support capability of the mobile communication terminal, and after knowing the bearer number expansion support capability of the opposite terminal, corresponding bearer management may be performed according to the bearer number expansion support capability of the opposite terminal, which is further described below.

In the service process, the mobile communication terminal or the network side needs to change the bearer number between the two in real time according to the service requirement, and the requirement can be realized through a bearer resource allocation flow or a bearer resource modification flow. In order to avoid that the allocated bearer resource exceeds the actual capability of the network element, when the bearer management method of the embodiment of the present invention is applied to the network element on the network side, the network element on the network side should reject the bearer resource allocation request or the bearer resource modification request which is initiated by the mobile communication terminal and exceeds the bearer capability of the mobile communication terminal.

That is, the indication information received by the network element on the network side is used to indicate whether the mobile communication terminal supports the bearer number extension, and the bearer management method according to the embodiment of the present invention further includes:

a network side network element receives a bearer resource allocation request or a bearer resource modification request sent by a mobile communication terminal;

and the network element at the network side refuses the request for allocating the bearer resources or the request for modifying the bearer resources when the network element judges that the mobile communication terminal does not support the expansion of the bearer quantity according to the indication information and the quantity of the established bearers of the mobile communication terminal reaches a preset threshold.

For example, the mobile communication terminal does not support bearer number extension, and when the number of currently established bearers reaches the maximum upper limit of 8, if a bearer resource allocation request or a bearer resource modification request is sent to the network element on the network side to reallocate more bearers, the network element on the network side directly rejects the bearer resource allocation request or the bearer resource modification request, thereby avoiding resource waste.

In the service process, the mobile communication terminal may move in a connected state (service state) or an idle state, and the movement may trigger an idle state moving process or a handover process, and in the above process, a network element on the network side may change, and the bearer number expansion support capability of the network elements before and after the change may change, and if the original bearer is directly migrated, a problem that the actual bearer number exceeds the capability of the network element on the target network side may occur. It is therefore necessary to make specifications for the above-mentioned cases.

It should be understood that, in the embodiment of the present invention, the idle mobile procedure refers to a procedure in which a serving network element on the network side may change in an idle state, such as a tracking area update procedure, and the handover procedure refers to a procedure in which a serving network element on the network side may change in a connected state, such as a hard handover procedure. Once the serving network element on the network side may change, the situation that the extension support capability of the bearer number of the new network element is different from that of the old network element may occur, and it is necessary to standardize the extension support capability to ensure normal processing of the service.

These will be described in further detail later in connection with fig. 6-13.

Based on the above requirement, an embodiment of the present invention further provides a bearer management method, configured to execute a network element on a network side, where as shown in fig. 3, the bearer management method includes:

and step 31, when the number of the bearers to be migrated to the target network element which does not support the bearer number expansion and belongs to the same mobile communication terminal is greater than a predetermined threshold, releasing part of the bearers, wherein the number of the reserved bearers is less than or equal to the predetermined threshold.

Based on the bearer management method of the embodiment of the invention, when the mobile communication terminal is switched from the source network side network element to the target network side network element, if the target network side network element does not support bearer quantity expansion and the bearer quantity allocated by the mobile communication terminal at the source network side network element exceeds the maximum bearer quantity of the target network side network element, the network side execution network element (possibly the source network side network element or the target network side network element) actively releases a part of bearers of the mobile communication terminal, thereby ensuring that the residual bearer quantity is within the bearer capacity range of the target network side network element and ensuring that the target network side network element can provide normal service for the mobile communication terminal.

When the number of bearers to be migrated to the target network element which does not support the extension of the bearer number is greater than a predetermined threshold, a part of the bearers need to be released to match with the capability of the target network element, so as to ensure the normal operation of the service. In the embodiment of the invention, a priority is set for all the bearers, and when the number of the bearers to be migrated to the target network element which does not support the bearer number expansion and belongs to the same mobile communication terminal is greater than a preset threshold, part of the bearers are released according to the sequence from low to high of the priorities of the bearers to be migrated.

In practical applications, the embodiments of the present invention may determine the priority of the bearer according to a QoS (quality of Service) parameter. The QOS parameter may reflect the network quality of the bearer, and the better the network quality of the bearer, the higher the priority, and conversely, the worse the network quality of the bearer, the lower the priority. Obviously, the network side executing network element releases part of the bearers according to the sequence from low priority to high priority, which can ensure that the mobile communication terminal preferentially reserves the bearers with higher network quality.

The QoS parameters may be QoS class identification parameters and allocation and retention priority parameters.

As per the above-mentioned policies, the bearer allocated for web browsing, but the bearer allocated for voice traffic, can be released preferentially.

Of course, it should be noted that the method for determining the bearer priority is only used for exemplary description, and does not limit the scope of the present invention. As another possible solution, the priority of the bearer may also be determined by performing weighted summation on multiple reference factors, which is not described herein again by way of example.

In addition, in practical applications, the network side execution network element of the specific embodiment of the present invention may be a source network side network element in an idle-state mobile flow or a handover flow, that is, the source network side network element releases the bearer resource of the mobile communication terminal in advance before the mobile communication terminal is handed over to the target network side network element;

or, the network side executing network element in the embodiment of the present invention may also be a target network side network element in an idle mobile flow or a handover flow, and when the mobile communication terminal is handed over to the target network side network element, the target network side network element releases the bearer resource of the mobile communication terminal.

Whether performed by the source network side network element or the target network side network element, two pieces of information need to be known, namely: and whether the target network side network element supports the bearer number expansion and the number of the bearers to be migrated.

Taking a network side execution network element as a target network side network element as an example, at this time, the target network side network element knows whether the target network side network element supports bearer quantity expansion, and can perform judgment and execution only by acquiring the quantity of bearers to be migrated.

That is, when the bearer management method according to the specific embodiment of the present invention is used in a target network element, before releasing a part of bearers, the method further includes:

and acquiring the bearing context information of the network element at the source network side.

When the number of bearers to be migrated to the target network element which does not support bearer number extension is greater than a predetermined threshold, releasing part of the bearers specifically comprises:

and when the number of the bearers to be migrated is judged to be larger than a preset threshold according to the bearer context information and the bearer number expansion support capability of the target network side network element and the target network side network element does not support bearer number expansion, releasing part of the bearers.

In the foregoing case, when the bearer management method according to the specific embodiment of the present invention is applied to a tracking area update procedure, a bearer context may be obtained through a context request procedure, that is, when the bearer management method according to the specific embodiment of the present invention is applied to a tracking area update procedure, before releasing a part of bearers, the method further includes:

sending a first context request message to a source network side network element;

receiving a first context request response message sent by a source network side network element, wherein the first context request response message is sent by the source network side network element without responding to the first context request message, and the first context request response message carries the current bearing context information of the mobile communication terminal;

the method comprises the following steps that when the number of bearers to be migrated to a target network element which does not support bearer number expansion is greater than a preset threshold, the number of the bearers to be migrated belonging to the same mobile communication terminal is specifically:

and when the target network side network element judges that the number of the bearers to be migrated is greater than the preset threshold and the target network side network element does not support the bearer number expansion according to the bearer context information carried in the first context request response message and the bearer number expansion support capability of the target network side network element, releasing part of the bearers.

When the method is applied to a handover process, the above-mentioned bearer context information may be transferred through a forward relocation request indication message.

And when the network side execution network element is the source network side network element, the source network side network element already knows the number of the bearers to be migrated, and then whether the target network side network element supports the bearer number expansion or not can be judged and executed.

That is, when the bearer management method in the specific embodiment of the present invention is used in a network element on a source network side, before releasing a part of bearers, the method further includes:

acquiring indication information, wherein the indication information is used for indicating whether the target network side network element supports the load number expansion or not;

when the number of bearers to be migrated to the target network element is greater than a predetermined threshold, the releasing of the bearers specifically comprises:

and when the number of the bearers to be migrated is judged to be larger than a preset threshold according to the indication information and the number of the bearers to be migrated, and the target network side network element does not support bearer number expansion, releasing part of the bearers.

In the foregoing situation, when the bearer management method according to the specific embodiment of the present invention is applied to the tracking area update process, it can be implemented by the target network side network element sending a context request message carrying indication information indicating whether the target network side network element supports bearer quantity expansion. After releasing part of the bearer, the source network side network element also sends a second context request response message carrying the bearer context to the target network side network element so as to inform the target network side network element that the bearer release is completed. Of course, the above bearer release in the specific embodiment of the present invention may be combined with the notification of the previous bearer number expansion capability support information, for example, after the migration is completed, if the target network side network element supports the bearer number expansion, the mobile communication terminal may be notified that the target network side network element supports the bearer number expansion by carrying indication information indicating that the target network side network element supports the bearer number expansion through a handover completion message, a tracking area update completion message, and the like, so that the subsequent mobile communication terminal can perform bearer management based on the indication information.

The bearer management method of the present invention is described in detail below with reference to different implementations.

Implementation mode one

The UE carries 1bit of information indicating that "the UE supports bearer number extension" in a user equipment Network Capability (UE Network Capability) information element of an Attach Request Message (Attach Request Message). Wherein "0" indicates not supported and "1" indicates supported.

The corresponding bearer management flow is shown in fig. 4, and includes the following steps:

the UE sends an attach request message (carrying a UE network capability indication information element) to an MME (Mobility Management entity) through a 3GPP access. Wherein, the network capability indication information element information of the user equipment comprises indication information of 'UE supports the expansion of the bearing quantity' of 1bit, wherein, 0 'indicates that the UE does not support the expansion of the EPS bearing, and 1' indicates that the UE supports the expansion of the EPS bearing.

Through the above process, the UE informs the network side of the information whether the UE supports the bearer number extension.

As shown in fig. 4, the MME may also carry indication information to the UE in an attach accept message sent through the 3GPP access, and inform the UE of whether the MME supports bearer number extension through the indication information.

In this step, if the MME supports bearer number extension, the "network supports EPS bearer number extension" may be indicated by using 1bit in the attach accept message.

The conventional attach procedure in fig. 4 is not changed, please refer to 3GPP TS 23.401.

Implementation mode two

The UE carries 1bit of information indicating that "the UE supports bearer number extension" in a user equipment Network Capability (UE Network Capability) information element of a TAU (Tracking Area Update) request message. Wherein "0" indicates not supported and "1" indicates supported.

The corresponding bearer management flow is shown in fig. 5, and includes the following steps:

the UE selects an E-UTRAN cell of a TA, which is not in a TAI (tracking area identification) list of a UE registration network, thereby triggering a TAU flow (namely a tracking area updating flow);

the UE sends a tracking area update request message (carrying a UE network capability indication information element) to an MME (Mobility Management entity) through a 3GPP access. Wherein, the network capability indication information element information of the user equipment comprises indication information of 'UE supports the expansion of the bearing quantity' of 1bit, wherein, 0 'indicates that the UE does not support the expansion of the EPS bearing, and 1' indicates that the UE supports the expansion of the EPS bearing.

As shown in fig. 5, the MME may also carry indication information to the UE in a tracking area update accept message sent by the 3GPP access, and inform the UE of whether the MME supports bearer number extension through the indication information.

In fig. 5, the conventional tracking area update procedure and the security procedure are not changed, please refer to the related protocol.

Implementation mode three

In the idle-state moving process of the UE, a target MME (namely a target network side network element) judges whether all the bearers can be received or not according to the context transmitted by a source MME (namely a source network side network element), and if not, partial bearers are released;

The corresponding bearer management flow is shown in fig. 6, and includes the following steps:

the UE accesses through 3GPP and sends TAU (Tracking Area Update) request information to a target MME, if 'UE supports the extension indication of the bearing quantity' is 0, the UE does not support the extension of the bearing quantity; if the 'UE supports the bearer number extension indication' is 1, the UE supports the bearer number extension;

the target MME sends a Context Request (Context Request) message to the source MME so as to obtain user information;

the source MME returns a Context request Response (Context Response) message carrying information such as IMSI, a quintuple authentication group, a bearer Context and the like;

the target MME judges whether to release part of the load according to the load Context information in the Context Response and the self capacity (the capacity of supporting load quantity expansion or not);

if the target MME does not support bearer number extension and the bearer number in the bearer context exceeds 8, the target MME determines the priority of the bearer according to the QoS parameter of the bearer, such as QCI and ARP, to release part of the bearer, such as to preferentially guarantee the bearer corresponding to the high priority service of voice and preferentially release the bearer of the low priority service, and if the target MME supports bearer number extension, the subsequent conventional TAU procedure is continued (refer to 3GPP TS 23.401).

The target MME sends a TAU Accept message to the UE through the 3GPP access.

If the target MME supports the expansion of the bearer number, 1bit is used for indicating 'the network supports the expansion of the EPS bearer number' in the TAU Accept information;

implementation mode four

In the idle-state moving process of the UE, the target side SGSN judges whether all the bearers can be accepted or not according to the UE context transmitted by the source MME, and if not, partial bearers are released;

the UE carries information indicating that "the UE supports bearer number extension" with 1bit in a user equipment Network Capability (UE core Network Capability) information element of an RAU Request message in an RAU flow. Wherein "0" indicates not supported and "1" indicates supported.

The UE selects an E-UTRAN cell of a TA, the cell is not in a TAI (tracking area identification) list of a UE registration network, thereby triggering an RAU flow (namely a routing area updating flow);

UE sends RAU Request message to service GPRS support node SGSN through UTRAN, if 'UE supports load quantity expansion indication' is 0, it represents UE does not support load quantity expansion; if the 'UE supports the bearer number extension indication' is 1, the UE supports the bearer number extension;

the SGSN sends a Context Request (Context Request) message to the MME to obtain the user information.

MME returns a Context request Response (Context Response) message, wherein the message carries IMSI, quintuple authentication group, bearing Context, S-GW signaling address, TEID and the like

The SGSN judges whether to release part of the load according to the load Context information in the Context Response and the self capability;

if the number of bearers in the bearer context exceeds 8, the SGSN releases part of the bearers, e.g. preferentially guarantees bearers corresponding to high priority services such as voice, and preferentially releases bearers for low priority services, if the number of bearers in the bearer context does not exceed 8, the subsequent RAU procedure is continued (see the relevant introduction in section 5.3.3.3 of TS23.401)

It should be understood that fig. 6 and 7 are only the difference between the source network and the target network types, but are both decided and executed by the target network side network element.

Implementation mode five

In the idle-state moving process of the UE, the source MME judges whether all the bearers can be accepted or not according to the context of the UE and the capability of the target MME, and if not, releases part of the bearers;

the UE carries 1bit indication information in a user equipment Network Capability (UE Network Capability) information element of a TAU (Tracking Area Update) request message, for indicating information that "the UE supports extension of the bearer number". Wherein "0" indicates not supported and "1" indicates supported.

The corresponding bearer management flow is shown in fig. 8, and includes the following steps:

UE selects an E-UTRAN cell of TA, the cell is not in TAI list of UE registration network, thus triggering TAU process;

the UE is accessed through the 3GPP, a TAU Request message is sent to the target MME, if the 'UE supports the extension indication of the number of the load bearing' is 0, the UE does not support the extension of the number of the load bearing; if the 'UE supports the bearer number extension indication' is 1, the UE supports the bearer number extension;

the target MME sends a Context Request (Context Request) message to the source MME to Request to obtain user information, wherein the user information carries indication information of whether the target MME supports the load quantity expansion;

the source MME judges whether to release part of the load according to the information of the UE Context;

if the target MME does not support the extension of the number of the bearers, the source MME supports the extension of the number of the bearers and the number of the current bearers exceeds 8, the source MME releases part of the bearers according to the priorities of the bearers judged by QoS parameters of the bearers, such as QCI, ARP and the like (for example, the bearers corresponding to high-priority services such as priority guarantee voice and the bearers of low-priority services are released preferentially);

if the target MME supports the extension of the bearing quantity, returning a Context request Response message (Context Response), wherein the message carries IMSI, a quintuple authentication group, a bearing Context, an S-GW signaling address, a TEID and the like;

and the target MME sends a TAU acceptance message to the UE through 3GPP access, wherein the TAU acceptance message carries indication information, and if the target MME supports the extension of the bearing number, the 1bit indication information is used for indicating that the network supports the EPS bearing number extension in the TAU Accept message.

Implementation mode six

In the idle state moving process of the UE, the source side MME judges whether all the bearers can be accepted or not according to the context of the UE and the capability of the SGSN, and releases part of the bearers if the bearers cannot be accepted;

in the process of RAU, UE carries 1bit of information for indicating that UE supports the extension of the bearing quantity in UE Network Capability of an RAU request message. Wherein "0" indicates not supported and "1" indicates supported.

The corresponding bearer management flow is shown in fig. 9, and includes the following steps:

UE selects a UTRAN subdistrict which is not in TAI list of UE register network, thereby triggering RAU process;

UE sends RAU Request message to SGSN through UTRAN, if 'UE supports load quantity expansion indication' is 0, it represents UE does not support load quantity expansion; if the 'UE supports the bearer number extension indication' is 1, the UE supports the bearer number extension;

SGSN sends a Context Request (Context Request) message to MME to Request user information;

the MME judges whether to release part of the load according to the information of the UE Context;

if the number of the current bearers exceeds 8, the MME determines the priority of the bearers according to QoS parameters of the bearers, such as QCI, ARP and the like, so as to release part of the bearers (such as bearers corresponding to high priority services such as priority guaranteed voice and bearers of low priority services preferentially released);

if the current bearing number is less than 8, returning a Context request Response message (Context Response) which carries IMSI, quintuple authentication set, bearing Context, S-GW signaling address, TEID and the like;

the SGSN sends an RAU accept message to the UE.

Implementation mode seven

In the switching process, the target MME can receive all the bearers according to the judgment in the user context information transmitted by the source MME, and if the user context information cannot receive all the bearers, partial bearers are released;

the corresponding bearer management flow is shown in fig. 10, and includes the following steps:

when the UE is in a connected state, the source eNodeB decides to initiate a switching process through an S1 interface, and then sends a switching request message to a source MME;

the source MME selects a target MME and sends a Forward Relocation Request message (including the context of the UE) to the target MME; the context of the UE comprises IMSI, UE security context, UE network capability, AMBR, bearer context and the like;

the target MME judges whether to release partial load according to the load context of the UE and the self capacity;

if the target MME does not support the extension of the bearer and the current number of bearers exceeds 8, the target MME determines the priority of the bearer according to the QoS parameters of the bearer, such as QCI and ARP, to release part of the bearers (e.g., the bearers corresponding to the high priority services such as priority guaranteed voice, and the bearers of the low priority services are preferentially released), and then performs a conventional handover procedure (refer to 3GPP TS23.401), otherwise, performs the conventional handover procedure directly.

The UE initiates the TAU procedure, which may refer to fig. 6, fig. 8 and their corresponding descriptions.

Implementation mode eight

In the switching process, a target side SGSN judges whether all the bearers can be accepted or not according to UE context sent by a source side MME, and if not, partial bearers are released;

the corresponding bearer management flow is shown in fig. 11, and includes the following steps:

the UE is in a connection state, and the source eNodeB decides to switch the UE to a UTRAN Iu mode and initiates a switching process;

the source eNodeB sends a switching request message to a source MME;

the source MME selects a target SGSN and sends a Forward Relocation Request message (including the context of the UE) to the target SGSN; the context of the UE comprises IMSI, UE security context, UE network capability, AMBR, bearer context and the like;

the target SGSN judges whether to release partial load according to the load context of the UE and the self capability;

if the current bearing number exceeds 8, the target SGSN judges the priority of the bearing according to the QoS parameters of the bearing, such as QCI, ARP and the like, and then releases part of the bearing (such as the bearing corresponding to high priority service with priority guaranteed voice and the bearing corresponding to low priority service with priority released) and then executes the conventional switching process (refer to 3GPP TS23.401), and if the current bearing number is less than 8, the conventional switching process is directly executed.

Implementation mode nine

In the switching process, the source side MME judges whether all the bearers can be accepted or not according to the context of the UE and the capability of the target MME, and releases part of the load if the bearers cannot be accepted;

the corresponding bearer management flow is shown in fig. 12, and includes the following steps:

the UE is in a connected state, and the source eNodeB decides to initiate a handover process through an S1 interface;

the source eNodeB sends a switching request message to a source MME;

the source MME selects a target MME, and whether to release part of the load is judged by the source MME according to the UE Context information and the target MME capability;

if the target MME does not support the extension of the bearer number, but the UE context indicates that the UE supports the extension of the bearer and the current bearer number exceeds 8, the source MME determines the priority of the bearer according to the QoS parameters of the bearer, such as QCI, ARP and the like, so as to release part of bearers (such as bearers corresponding to high priority services such as priority guaranteed voice and the bearers of low priority services preferentially released) and then continues the conventional switching process, otherwise, the source MME directly continues the conventional switching process.

In the subsequent conventional handover process, the source MME sends a forward relocation request message to the target MME, and the UE may execute the TAU procedure at the same time, please refer to the description of the TAU procedure before, which is not described herein again.

Implementation method ten

In the switching process, the source side MME judges whether all the bearers can be received or not according to the UE context and the capability of the target side SGSN, and releases part of the bearers if the bearers cannot be received;

the corresponding bearer management flow is shown in fig. 13, and includes the following steps:

a source eNodeB sends a switching request message to a source MME, and requests a core network to establish resources at a target RNC, SGSN and S-GW;

the source MME judges whether to release part of the load according to the UE Context information and the capability of the target SGSN;

if the current bearing number exceeds 8, the source MME judges the priority of the bearing according to the QoS parameters of the bearing, such as QCI, ARP and the like, releases part of the bearing (such as the bearing corresponding to high priority service with priority guaranteed voice and the bearing of low priority service with priority released) and then continues the conventional switching process, otherwise, the conventional switching process is directly continued.

Implementation eleven

When the UE establishes the load, the MME judges whether the load number of the UE exceeds the maximum limit;

the corresponding bearing management method comprises the following steps:

the UE sends a BEARER RESOURCE ALLOCATION REQUEST (BEARER RESOURCE ALLOCATION REQUEST) or a BEARER RESOURCE MODIFICATION REQUEST message (BEARER RESOURCE MODIFICATION REQUEST) to the MME through the 3GPP access;

the MME verifies the EPS bearing identification and the UE context, and checks whether bearing resources can be established for the UE (for example, whether the bearing quantity of the UE exceeds the maximum bearing quantity);

if the network accepts the bearing resource allocation request, MME initiates a conventional special EPS bearing context activation process or an EPS bearing context modification process;

if the network does not accept the bearer resource allocation request, the MME sends a reject message to the UE, which should include an ESM value (e.g., 65, indicating that the maximum number of bearers has been reached).

In addition, another embodiment of the present invention further provides a bearer management apparatus for use in one of a network element on a network side and a mobile communication terminal, as shown in fig. 14, the bearer management apparatus including:

a sending module 141, configured to send indication information to the other one of the network element on the network side and the mobile communication terminal, where the indication information is used to indicate whether bearer number extension is supported.

Obviously, the bearer management apparatus according to the embodiment of the present invention is an execution main body of the bearer management method provided by the present invention, and therefore, the technical effects that can be achieved by the bearer management method can also be achieved by the bearer management apparatus according to the present invention.

Optionally, when the bearer management apparatus is a mobile communication terminal, the sending module 141 according to the embodiment of the present invention is specifically configured to:

and sending a user equipment network capability information element carrying indication information to a network element at a network side, wherein the indication information is used for indicating whether the mobile communication terminal supports the load number expansion.

Optionally, the sending module 141 is specifically configured to:

sending a request message to a network element at a network side, wherein the request message carries first indication information which is used for indicating whether a mobile communication terminal supports the load number expansion; the request message is an attachment request message or a tracking area update request message;

or

Sending an acceptance message to the mobile communication terminal, wherein the acceptance message carries second indication information, the second indication information is used for indicating whether the network side network element supports the bearer quantity expansion, and the acceptance message is an attachment acceptance message or a tracking area update acceptance message.

In addition, another embodiment of the present invention further provides a bearer management apparatus, configured to be used in one of a network element on a network side and a mobile communication terminal, as shown in fig. 15, where the bearer management apparatus includes:

a receiving module 151, configured to receive indication information sent by the other one of the network element on the network side and the mobile communication terminal, where the indication information is used to indicate whether bearer number extension is supported.

Optionally, the receiving module 151 of the specific embodiment of the present invention is specifically configured to:

and receiving a user equipment network capability information element which is sent by the mobile communication terminal and carries indication information, wherein the indication information is used for indicating whether the mobile communication terminal supports the load number expansion.

Optionally, the receiving module 151 in the embodiment of the present invention is specifically configured to:

receiving a request message sent by a mobile communication terminal, wherein the request message carries first indication information which is used for indicating whether the mobile communication terminal supports the load number expansion; the request message is an attachment request message or a tracking area update request message;

or

Receiving an acceptance message sent by the network element at the network side, wherein the acceptance message carries second indication information, the second indication information is used for indicating whether the network element at the network side supports bearer quantity expansion, and the acceptance message is an attachment acceptance message or a tracking area update acceptance message.

In addition, another embodiment of the present invention further provides a bearer management apparatus, configured to execute a network element on a network side, as shown in fig. 16, where the bearer management apparatus includes:

a releasing module 161, configured to release a part of bearers when the number of bearers to be migrated to a target network element that does not support bearer number extension is greater than a predetermined threshold, where the number of reserved bearers is less than or equal to the predetermined threshold, where the number of bearers to be migrated to the target network element belongs to the same mobile communication terminal.

Obviously, the bearer management apparatus according to the embodiment of the present invention is an execution main body of the bearer management method applied to the network side execution network element provided in the present invention, and therefore, the technical effect that can be achieved by the bearer management method can also be achieved by the bearer management apparatus according to the present invention.

Optionally, the releasing module 161 according to the specific embodiment of the present invention is specifically configured to:

and when the number of the bearers to be migrated to the target network element which does not support the bearer number expansion is greater than a preset threshold, releasing part of the bearers according to the sequence from low to high of the priority of the bearers to be migrated, wherein the bearers to be migrated belong to the same mobile communication terminal.

Optionally, the network side execution network element is a target network side network element in an idle-state mobility procedure or a handover procedure.

If the network side execution network element is a target network side network element in an idle state mobile flow or a handover flow, the method further includes:

the first obtaining module is used for obtaining the bearing context information of the network element at the source network side.

The release module is specifically configured to:

and when the number of the bearers to be migrated is judged to be larger than a preset threshold according to the bearer context information and the bearer number expansion support capability of the target network side network element, and the target network side network element does not support bearer number expansion, releasing part of the bearers.

In one embodiment, the first obtaining module is specifically configured to:

receiving a first context request response message carrying the bearing context information sent by a network element at a source network side;

when the network element executed by the network side is a source network element in an idle mobile flow or a handover flow, the method further includes:

a second obtaining module, configured to obtain an indication information, where the indication information is used to indicate whether the target network side network element supports bearer quantity extension.

The release module is specifically configured to: and when the number of the bearers to be migrated is judged to be larger than a preset threshold according to the indication information and the number of the bearers to be migrated, and the target network side network element does not support bearer number expansion, releasing part of the bearers.

Correspondingly, on the basis, as shown in fig. 16, the bearer management apparatus of this example further includes:

a response module 162, configured to send a message carrying a bearer context to the target network element after releasing the partial bearer.

In addition, an embodiment of the present invention further provides a bearer management apparatus, as shown in fig. 17, including

An antenna 171, a radio frequency device 172, a baseband device 173, a processor 174, a memory 175, and a network interface 176 and bus interface. Wherein:

in this embodiment of the present invention, the network side device 600 further includes: a computer program stored on the memory 175 and executable on the processor 174, the computer program when executed by the processor 174 performing the steps of:

And/or the presence of a gas in the gas,

sending a first context request message to the network element at the source network side;

receiving a first context request response message sent by the network element at the source network side;

the angelica belongs to the same mobile communication terminal, and when the number of bearers to be migrated to the target network side network element which does not support bearer number expansion is greater than a predetermined threshold, the method specifically comprises the following steps:

and when the number of the bearers to be migrated is judged to be larger than a preset threshold according to the bearer context information carried in the first context request response message and the bearer number expansion support capability of the target network side network element, and the target network side network element does not support the bearer number expansion, releasing part of the bearers.

The bus interface may comprise, among other things, any number of interconnected buses and bridges, with one or more processors, represented by a processor, and various circuits of memory, represented by memory 175, 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 antenna 171, the radio frequency device 172, and the baseband device 173 collectively constitute a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium. For different user devices, the user interface 176 may also be an interface capable of interfacing with a desired device externally, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 174 is responsible for managing bus interfaces and general processing, and the memory 175 may store data used by the processor 174 in performing operations.

Optionally, when executed by the processor 174, the computer program according to the embodiment of the present invention further implements the following steps:

and sending a user equipment network capability information element carrying the indication information to a network element at a network side, wherein the indication information is used for indicating whether the mobile communication terminal supports the load number expansion.

Optionally, the indication information is defined by the 6 th, 7 th or 8 th bit in the 9 th octet or any one bit in the 10 th to 15 th octet of the network capability information element of the user equipment.

sending a request message to the network element at the network side, wherein the request message carries first indication information, and the first indication information is used for indicating whether the mobile communication terminal supports the bearer quantity expansion; the request message is an attachment request message or a tracking area update request message;

or

Sending an acceptance message to the mobile communication terminal, where the acceptance message carries second indication information, where the second indication information is used to indicate whether the network side network element supports bearer quantity expansion, and the acceptance message is an attachment acceptance message or a tracking area update acceptance message.

Optionally, if the bearer management method is used in a network element on a network side, the computer program according to the embodiment of the present invention further implements the following steps when executed by the processor 174:

and receiving a user equipment network capability information element which is sent by the mobile communication terminal and carries the indication information, wherein the indication information is used for indicating whether the mobile communication terminal supports the load number expansion.

receiving a request message sent by the mobile communication terminal, wherein the request message carries first indication information, and the first indication information is used for indicating whether the mobile communication terminal supports bearer quantity expansion; the request message is an attachment request message or a tracking area update request message;

or

Optionally, when the bearer management method is used in a network element on a network side, and when the bearer management method is used in a network element on a network side, the computer program according to the specific embodiment of the present invention further implements the following steps when being executed by the processor 174:

receiving indication information sent by the mobile communication terminal, wherein the indication information is used for indicating whether the bearer number expansion is supported or not;

the bearer management method further comprises:

receiving a bearer resource allocation request or a bearer resource modification request sent by the mobile communication terminal;

and rejecting the bearer resource allocation request or the bearer resource modification request when the mobile communication terminal does not support bearer quantity expansion and the quantity of the established bearers of the mobile communication terminal reaches a preset threshold according to the indication information.

Optionally, the network side execution network element is a source network side network element or a target network side network element in an idle-state mobile flow or a handover flow;

if the network side execution network element is a target network side network element, before releasing part of the bearers, the computer program according to the embodiment of the present invention further implements the following steps when being executed by the processor 174:

If the network side execution network element is a source network side network element, before releasing part of the bearer, the computer program according to the embodiment of the present invention further implements the following steps when being executed by the processor 174:

receiving a second context request message carrying indication information sent by the target network side network element, wherein the indication information is used for indicating whether the target network side network element supports bearer quantity expansion;

when the number of the bearers to be migrated is judged to be larger than a preset threshold according to the indication information and the number of the bearers to be migrated, and the target network side network element does not support bearer number expansion, releasing part of the bearers;

after the partial bearer is released, the bearer management method further includes:

and sending a second context request response message carrying the bearer context to the target network side network element.

Furthermore, another embodiment of the present invention also provides a computer-readable storage medium having a computer program stored thereon, the computer program, when executed by a processor, implementing the steps of:

And/or the presence of a gas in the gas,

Optionally, when executed by a processor, the computer program of the embodiment of the present invention further implements the following steps:

or

Optionally, if the bearer management method is used for a network element on a network side, the computer program according to the specific embodiment of the present invention further implements the following steps when executed by the processor:

or

Optionally, when the bearer management method is used in a network element on a network side, the computer program according to the specific embodiment of the present invention further implements the following steps when executed by the processor:

the bearer management method further comprises:

if the network side execution network element is a target network side network element, the computer program of the embodiment of the present invention further implements the following steps when executed by the processor:

acquiring the bearing context information of a network element at a source network side;

If the network side execution network element is a source network side network element, before releasing part of the bearers, the computer program of the embodiment of the present invention further implements the following steps when executed by the processor:

acquiring indication information, wherein the indication information is used for indicating whether the target network side network element supports the load number expansion or not; (ii) a

While the foregoing is directed to the preferred embodiment of the present invention, it will be understood by those skilled in the art that various changes and modifications may be made without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A bearer management method, configured to be used by a network side to execute a network element, where the bearer management method includes:

when the number of bearers to be migrated to a target network element which does not support bearer number expansion is greater than a predetermined threshold, releasing part of the bearers, wherein the number of reserved bearers is less than or equal to the predetermined threshold;

the network side executing network element is a target network side network element, and before releasing part of the bearer, the bearer management method further includes:

when the number of the bearers to be migrated is judged to be larger than a preset threshold according to the bearer context information and the bearer number expansion support capability of the target network side network element, and the target network side network element does not support bearer number expansion, releasing part of the bearers;

alternatively, the first and second electrodes may be,

the network side executing network element is a source network side network element, and before releasing part of the bearer, the bearer management method further includes:

2. The bearer management method according to claim 1, wherein the releasing of the part of the bearers when the number of bearers to be migrated to the target network element that does not support bearer number extension is greater than the predetermined threshold, which belongs to the same mobile communication terminal, specifically is:

3. The bearer management method according to claim 2, wherein the network side performing element is a source network side element or a target network side element in an idle mobility procedure or a handover procedure.

4. A bearer management apparatus, configured to execute a network element on a network side, where the bearer management apparatus includes:

a releasing module, configured to release a part of bearers when the number of bearers to be migrated to a target network element that does not support bearer number expansion is greater than a predetermined threshold, where the number of reserved bearers is less than or equal to the predetermined threshold, where the number of bearers to be migrated to the target network element belongs to the same mobile communication terminal;

the network side executing network element is a target network side network element, and before releasing part of the bearer, the bearer management device is further configured to:

alternatively, the first and second electrodes may be,

the network side executing network element is a source network side network element, and before releasing part of the bearer, the bearer management device is further configured to:

5. The bearer management apparatus according to claim 4, wherein the release module is specifically configured to: and when the number of the bearers to be migrated to the target network element which does not support the bearer number expansion is greater than a preset threshold, releasing part of the bearers according to the sequence from low to high of the priority of the bearers to be migrated, wherein the bearers to be migrated belong to the same mobile communication terminal.

6. The bearer management apparatus according to claim 5, wherein the network-side performing element is a target network-side element in an idle mobility procedure or a handover procedure.

7. A bearer management apparatus comprising: processor, memory and a computer program stored on the memory and executable on the processor, characterized in that the computer program, when executed by the processor, implements the bearer management method according to any of claims 1-3.

8. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the bearer management method according to any one of claims 1-3.