WO2019137367A1 - 承载管理方法及承载管理装置 - Google Patents

承载管理方法及承载管理装置 Download PDF

Info

Publication number
WO2019137367A1
WO2019137367A1 PCT/CN2019/070827 CN2019070827W WO2019137367A1 WO 2019137367 A1 WO2019137367 A1 WO 2019137367A1 CN 2019070827 W CN2019070827 W CN 2019070827W WO 2019137367 A1 WO2019137367 A1 WO 2019137367A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
network element
indication information
network side
communication terminal
Prior art date
Application number
PCT/CN2019/070827
Other languages
English (en)
French (fr)
Inventor
王文
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2019137367A1 publication Critical patent/WO2019137367A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H04W36/28—Reselection being triggered by specific parameters by agreed or negotiated communication parameters involving a plurality of connections, e.g. multi-call or multi-bearer connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a bearer management method and a bearer management device.
  • the maximum number of bearers supported by the 5G communication system has been expanded.
  • the 5G communication system is extended from the original maximum of 8 bearers to a maximum of 15 bearers.
  • the number of bearers of the 4G communication system is expected to be extended to 15, so that the coexistence of the network elements supporting the extended number of bearers and the network elements not supporting the extended number of bearers may occur in the network.
  • An object of the present disclosure is to provide a bearer management method and a bearer management apparatus, which are used to standardize information between a network element supporting a number of bearers and a network element that does not support the number of extended bearers, and a network side network element and a mobile communication terminal. Interaction.
  • an embodiment of the present disclosure provides a bearer management method for one of a network side network element and a mobile communication terminal, where the bearer management method includes:
  • the indication information is sent to the other of the network side network element and the mobile communication terminal, where the indication information is used to indicate whether the bearer quantity extension is supported.
  • an embodiment of the present disclosure further provides a bearer management method, which is used in one of a network side network element and a mobile communication terminal, where the bearer management method includes:
  • the embodiment of the present disclosure further provides a bearer management method, where the network side performs a network element, where the bearer management method includes:
  • the part of the bearer is released, and the number of reserved bearers is less than or equal to the predetermined threshold.
  • an embodiment of the present disclosure further provides a bearer management apparatus, which is used in one of a network side network element 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 side network element and the mobile communication terminal, where the indication information is used to indicate whether the bearer quantity extension is supported.
  • an embodiment of the present disclosure further provides a bearer management apparatus, which is used in one of a network side network element and a mobile communication terminal, where the bearer management apparatus includes:
  • the receiving module is configured to receive indication information sent by another one of the network side network element and the mobile communication terminal, where the indication information is used to indicate whether the bearer quantity extension is supported.
  • the embodiment of the present disclosure further provides another bearer management device, configured to execute a network element on a network side, where the bearer management device includes:
  • a release module configured to release a partial bearer when the number of to-be-migrated bearers to be migrated to the target network side network element that does not support the number of bearer extensions is greater than a predetermined threshold, and the number of reserved bearers is less than or equal to The predetermined threshold.
  • an embodiment of the present disclosure further provides a bearer management apparatus including: a processor, a memory, and a computer program stored on the memory and executable on the processor, the computer program being implemented by a processor All the steps in the bearer management method provided by the present disclosure.
  • embodiments of the present disclosure also provide a computer readable storage medium having stored thereon a computer program that, when executed by a processor, implements all of the steps in the bearer management method provided by the present disclosure.
  • the specific embodiment of the present disclosure specifies the information exchange between the network side network element and the mobile communication terminal that support the coexistence of the network element supporting the number of extensions and the network element that does not support the number of extensions, so that the network side network element and the mobile communication terminal can Informing the other party whether the bearer number extension is supported, so that the mobile communication terminal supporting the extended number of bearers can establish the bearer of the extended part with the network side network element supporting the extended number of bearers, and when either of the two parties does not support the bearer number extension, the mobile The communication terminal and/or the network side can perform a reasonable allocation of the bearer resources based on the information of the interaction.
  • FIG. 1 is a schematic diagram of steps of a bearer management method for one of a network side network element and a mobile communication terminal according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of steps of a bearer management method for one of a network side network element and a mobile communication terminal according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of steps of a bearer management method performed on a network side according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram of different implementation manners of a bearer management method according to an embodiment of the present disclosure
  • FIG. 14 is a schematic diagram of a logical structure of a bearer management apparatus for one of a network side network element and a mobile communication terminal according to an embodiment of the present disclosure
  • FIG. 15 is a schematic diagram of a logical structure of a bearer management apparatus for one of a network side network element and a mobile communication terminal according to an embodiment of the present disclosure
  • 16 is a schematic structural diagram of a bearer management apparatus performed on a network side according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram of a bearer management apparatus according to an embodiment of the present disclosure.
  • the present disclosure is used to standardize information interaction between a network side network element and a mobile communication terminal that support the coexistence of a network element supporting the number of extensions and a network element that does not support the number of extensions.
  • an embodiment of the present disclosure provides a bearer management method for one of a network side network element and a mobile communication terminal (for example, a user equipment).
  • the bearer management method includes:
  • Step 11 Send indication information to another one of the network side network element and the mobile communication terminal, where the indication information is used to indicate whether the bearer quantity extension is supported.
  • the indication information sent by the network side network element to the mobile communication terminal is used to indicate whether the network side network element supports the number of bearer extensions.
  • the indication information sent by the communication terminal to the network side network element is used to indicate whether the communication terminal supports The number of bearers is expanded.
  • the specific embodiment of the present disclosure specifies the information exchange between the network side network element and the mobile communication terminal that support the coexistence of the network element supporting the number of extensions and the network element that does not support the number of extensions, so that the network side network element and the mobile communication terminal can Informing the other party whether the bearer number extension is supported, so that the mobile communication terminal supporting the extended number of bearers can establish the bearer of the extended part with the network side network element supporting the extended number of bearers, and when either of the two parties does not support the bearer number extension, the mobile The communication terminal and/or the network side can perform a reasonable allocation of the bearer resources based on the information of the interaction.
  • the mobile communication terminal sends the indication information to the network side network element, where the indication information is used to indicate whether the bearer quantity extension is supported;
  • the network side network element sends indication information to the mobile communication terminal, where the indication information is used to indicate whether the bearer quantity extension is supported.
  • the network side network element When the network side network element sends the indication information to the mobile communication terminal, assuming that the network side network element does not support the number of bearers, when the mobile communication terminal has established eight bearers, even if there are more bearer resource requirements, the mobile communication terminal It is known that the network side network element does not support the number of bearers, so no more bearer resources are requested from the network side network element.
  • the mobile communication terminal sends the indication information to the network side network element, assuming that the mobile communication terminal does not support the number of bearers, when the mobile communication terminal has established eight bearers, even if the network side network element supports more bearer resources, Since the network side network element knows that the mobile communication terminal does not support the number of bearers, it does not allocate more bearer resources that the mobile communication terminal cannot use to the mobile communication terminal.
  • the indication information of the specific embodiments of the present disclosure may be carried by the existing signaling and/or information elements.
  • the mobile communication terminal may send a user equipment network capability information element carrying the indication information to the network side network element, where the indication information is used to indicate whether the mobile communication terminal is Support for the number of bearers to expand.
  • the network capability information element is information related to the EPS provided by the existing network or interacting with the GPRS, and the content may affect the manner in which the network processes the operation of the mobile communication terminal.
  • the structure of the current network capability information is shown in the following table:
  • the network capability information element includes 15 octets, and each octet contains eight bits.
  • the first to eighth bits are respectively used to indicate whether the terminal supports EEA0, 128-EEA1, 128-EEA2, 128-EEA3, EEA4, EEA5, EEA6, EEA7 and the like.
  • the fifth bit (DCNR) is used to indicate whether the terminal supports dual connectivity with the NR communication system.
  • the 8th bit of octet3 has a value of 0 or 1 in the network capability information element, indicating the following information:
  • the 8th bit of octet3 takes a value of 1 to indicate that the Evolved Packet System (EPS) supports the EEA0 algorithm;
  • EPS Evolved Packet System
  • the 8th bit of octet3 takes a value of 0, indicating that the EPS does not support the EEA0 algorithm
  • the 7th bit of octet3 has a value of 0 or 1 in the network capability information element, indicating the following information:
  • the 7th bit of octet3 takes a value of 1 to indicate that the EPS supports the 128-EEA1 algorithm
  • the 7th bit of octet3 takes a value of 0, indicating that the EPS does not support the 128-EEA1 algorithm.
  • the fifth bit of octet9 has a value of 0 or 1 in the network capability information element, indicating the following information:
  • the 5th bit value of Octet9 indicates that the dual connection with the NR communication system is supported
  • the 5th bit of octet9 takes a value of 0 to indicate that dual connectivity to the NR communication system is not supported.
  • any of the 6th, 7th or 8th bit or the 10th to the 15th octet in the ninth octet of the network capability information element is to be Defining bits, the indication information of a particular embodiment of the present disclosure may be defined by one or more of these bits.
  • a specific embodiment of the present disclosure may use the sixth bit in the ninth bit group of the network capability information element to indicate indication information (INOBEAR), and the modified ninth octet structure of the network capability information element is as follows: Show:
  • INOBEAR indicates the indication information, and the value in the network capability information element is 0 or 1.
  • the sixth bit of the ninth bit group takes a value of 1 to indicate that the mobile communication terminal supports the number of bearers, and the sixth bit of the ninth bit group has a value of 0, indicating that the mobile communication terminal does not support The number of bearers is expanded.
  • the use of the existing network capability information element to carry the indication information is only one of the feasible embodiments of the present disclosure.
  • the specific embodiment of the present disclosure may also use other newly defined information elements to carry the indication information. .
  • the indication information may be carried by existing signaling, such as:
  • the mobile communication terminal may carry the foregoing indication information by using an attach request message in the attaching process or a tracking area update message in the tracking area update process, so that the network side network element can receive the foregoing attach request message or the tracking area update message after receiving the above-mentioned indication information.
  • the indication information carried therein can be obtained, thereby knowing whether the mobile communication terminal supports the number of bearers.
  • the network side network element can also carry the foregoing indication information by using the attach accept message in the attaching process or the tracking area accepting message in the tracking area update process, so that the mobile communication terminal can receive the above-mentioned attach accept message or the tracking area. After the message is accepted, the indication information carried in the message can be obtained, and then it is known whether the network side supports the number of bearers.
  • the foregoing information is sent to the other of the network side network element and the mobile communication terminal, and the indication information is used to indicate whether the supported number of extension stations can be:
  • the mobile communication terminal sends a request message to the network side network element, where the request message is an attach request message or a tracking area update request message, and carries the first indication information, where the first indication information is used to indicate whether the mobile communication terminal supports the number of bearers.
  • the network side network element sends an accept message to the mobile communication terminal, where the accept message is an attach accept message or a tracking area update accept message, and carries the second indication information, where the second indication information is used to indicate whether the network side network element supports the bearer.
  • the number is expanding.
  • the indication information mentioned above is only an optional way to transmit by the existing signaling, and is not an essential implementation manner.
  • the indication information of the specific embodiment of the present disclosure may also be a dedicated letter. Carry and/or exclusive information elements.
  • another embodiment of the present disclosure further provides a bearer management method for one of a network side network element and a mobile communication terminal.
  • the bearer management method includes:
  • Step 21 Receive indication information sent by another one of the network side network element and the mobile communication terminal, where the indication information is used to indicate whether the bearer quantity extension is supported.
  • the mobile communication terminal receives the indication information sent by the network element of the network side, where the indication information is used to indicate whether the network element of the network side supports the extension of the number of bearers;
  • the network side network element receives the indication information sent by the mobile communication terminal, where the indication information is used to indicate whether the mobile communication terminal supports the bearer quantity extension.
  • the specific embodiment of the present disclosure specifies the information exchange between the network side network element and the mobile communication terminal that support the coexistence of the network element supporting the number of extensions and the network element that does not support the number of extensions, so that the network side network element and the mobile communication terminal can Informing the other party whether the bearer number extension is supported, so that the mobile communication terminal supporting the extended number of bearers can establish the bearer of the extended part with the network side network element supporting the extended number of bearers, and when either of the two parties does not support the bearer number extension, the mobile The communication terminal and/or the network side can perform a reasonable allocation of the bearer resources based on the information of the interaction.
  • the mobile communication terminal When the mobile communication terminal receives the indication information sent by the network side network element, assuming that the network side network element does not support the number of bearer extensions, when the mobile communication terminal has already established eight bearers, even if there are more bearer resource requirements, due to the mobile The communication terminal knows that the network side network element does not support the number of bearers, and therefore does not request more bearer resources from the network side network element.
  • the network side network element receives the indication information sent by the mobile communication terminal, assuming that the mobile communication terminal does not support the number of bearers, when the mobile communication terminal has established eight bearers, even if the network side network element supports more bearer resources. However, since the network side network element knows that the mobile communication terminal does not support the number of bearers, it does not allocate more bearer resources to the mobile communication terminal.
  • the indication information of the specific embodiments of the present disclosure may be carried by the existing signaling and/or information elements.
  • the indication information of a particular embodiment of the present disclosure may be carried by a user equipment network capability information element.
  • the indication information is defined by any one of the sixth, seventh or eighth bit or the tenth to fifteenth octets in the ninth octet of the user equipment network capability information element.
  • the use of the network capability information element carrying the indication information is only one of the implementation manners of the specific embodiments of the present disclosure.
  • the specific embodiment of the present disclosure may also provide a separate information element to carry the foregoing indication information.
  • the indication information of the embodiment of the present disclosure may also be carried by existing signaling or new signaling.
  • the existing signaling between the mobile communication terminal and the network side network element is used to carry the foregoing indication information, such as:
  • the mobile communication terminal may carry the foregoing indication information by using an attach request message in the attaching process or a tracking area update message in the tracking area update process, so that the network side network element can receive the foregoing attach request message or the tracking area update message, and obtain the The carried indication information further knows whether the mobile communication terminal supports the number of bearers.
  • the network side network element may also carry the foregoing indication information by using an attach accept message in the attaching process or a tracking area accepting message in the tracking area update process, so that the mobile communication terminal can receive the foregoing attach accept message or the tracking area accept message. And obtaining the indication information carried in the network, and then knowing whether the network side supports the number of bearers.
  • the indication information sent by the other one of the network side network element and the mobile communication terminal is received, and the indication information is used to indicate whether the supported number of extensions is supported.
  • the network side network element receives the request message sent by the mobile communication terminal, where the request message carries the first indication information, where the first indication information is used to indicate whether the mobile communication terminal supports the bearer quantity extension; the request message is an attach request message or a tracking Zone update request message;
  • the mobile communication terminal receives the accept message sent by the network side network element, where the accept message carries the second indication information, where the second indication information is used to indicate whether the network side network element supports the bearer quantity extension, and the accept message is an attach accept message or Tracking area update accept message.
  • the indication information of the specific embodiment of the present disclosure may also be transmitted through dedicated signaling.
  • the mobile communication terminal can know the bearer number extension support capability of the network side network element, and/or the network side network element can know the bearer number expansion support capability of the mobile communication terminal, and after knowing the number of bearer extension support capabilities of the peer end,
  • the bearer management can be performed according to the number of bearers of the peer end, which is further explained below.
  • the mobile communication terminal or the network side needs to change the number of bearers between the two in real time according to the service requirement, and the requirement may be implemented by using a bearer resource allocation process or a bearer resource modification process.
  • the network side network element should reject the mobile communication terminal and the mobile communication terminal. Capable resource allocation request or bearer resource modification request.
  • the bearer management method in the specific embodiment of the present disclosure further includes:
  • the network side network element receives the bearer resource allocation request or the bearer resource modification request sent by the mobile communication terminal;
  • the network side network element rejects the bearer resource allocation request or the bearer resource modification request when it is determined that the mobile communication terminal does not support the bearer number extension according to the indication information, and the number of established bearers of the mobile communication terminal reaches a predetermined threshold.
  • the mobile communication terminal does not support the number of bearers, if the number of currently established bearers reaches a maximum of eight, if a bearer resource allocation request or a bearer resource modification request is sent to the network side network element to reallocate more bearers, The network side network element directly rejects the bearer resource allocation request or the bearer resource modification request to avoid resource waste.
  • the mobile communication terminal may move in the connected state (service state) or idle state, and the mobile may trigger the idle state mobile process or the handover process, and in the above process, the network side network
  • the meta-conversion changes, and the support capacity of the NEs before and after the change may change. If the original bearer is directly migrated, the actual number of bearers exceeds the capacity of the target network-side NE. Therefore, it is necessary to regulate the above situation.
  • the idle state mobility procedure in the specific embodiment of the present disclosure refers to a process in which a service network element on the network side may change in an idle state, such as a tracking area update process, and the handover process refers to a network side in a connected state.
  • a process in which a service network element may change such as a hard handover process. If the network side service network element may change, the new network element and the old network element may have different capacity extension support capabilities. It is necessary to standardize this to ensure normal service processing.
  • an embodiment of the present disclosure further provides a bearer management method, where the network side executes a network element.
  • the bearer management method includes:
  • Step 31 When the number of to-be-migrated bearers to be migrated to the target network side network element that does not support the number of bearer extensions is greater than the predetermined threshold, the number of reserved bearers is less than or equal to the number of bearers. Schedule a threshold.
  • the network side performs the network element (which may be the source network side network element or the target network side network element) to actively release part of the bearer of the mobile communication terminal. Therefore, the remaining number of bearers is within the carrying capacity of the target network side network element, and the target network side network element can ensure normal service services for the mobile communication terminal.
  • a priority is set for all bearers.
  • the number of to-be-migrated bearers to be migrated to the target network side network element that does not support the extended number of bearers is greater than the predetermined threshold
  • the number of the bearers to be migrated to the same mobile communication terminal is greater than the predetermined threshold. Partial bearers are released in descending order of priority of the bearers to be migrated.
  • the specific embodiment of the present disclosure may determine the priority of the bearer according to the QoS (Quality of Service) parameter.
  • the QOS parameter can reflect the quality of the bearer network. The better the network quality of the bearer corresponds to the higher priority. Conversely, the poorer the network quality of the bearer corresponds to the lower priority.
  • the network-side performing network element releases part of the bearer according to the order of priority from low to high, which can ensure that the mobile communication terminal preferentially retains the bearer with higher network quality.
  • the foregoing QoS parameters may be parameters such as a QoS classification identifier parameter and an allocation and retention priority parameter.
  • the bearer allocated for web browsing can be preferentially released, and the bearer allocated for the voice service.
  • the foregoing method for determining the bearer priority is for illustrative purposes only and does not limit the scope of protection of the present disclosure.
  • the priority of the bearer may also be determined by weighted summation by multiple reference factors, and is not described herein again.
  • the network side execution network element in the embodiment of the present disclosure may be an idle network mobile flow or a source network side network element in the handover process, that is, the source network side network element switches to the target network side in the mobile communication terminal. Before the network element, release the bearer resources of the mobile communication terminal in advance;
  • the network side execution network element in the specific embodiment of the present disclosure may also be the target network side network element in the idle state mobile flow or the handover process.
  • the target network side network element When the mobile communication terminal switches to the target network side network element, the target network side network The element releases the bearer resources of the mobile communication terminal.
  • the target network side network element Whether it is performed by the source network side network element or the target network side network element, it is necessary to know two pieces of information, that is, whether the target network side network element supports the number of bearers and the number of bearers to be migrated.
  • the network side performs the network element as the target network side network element.
  • the target network side network element knows whether it supports the number of bearer extensions, and only needs to obtain the number of bearers to be migrated for judgment and execution.
  • the target network side network element may determine the number of bearers by using the bearer context information carried in the context request response message.
  • the method further includes:
  • the release part of the bearer is specifically:
  • the partial bearer is released.
  • the bearer context can be obtained through the context request process, that is, when the bearer management method of the specific embodiment of the present disclosure is applied to the tracking area update process, Before releasing part of the bearer, it also includes:
  • the number of the to-be-migrated bearers to be migrated to the target network side network element that does not support the extended number of bearers is greater than the predetermined threshold.
  • the target network side network element determines that the number of bearers to be migrated is greater than a predetermined threshold according to the bearer context information carried in the first context request response message and the bearer number extension support capability of the target network side network element, and the target network side network element does not support When the number of bearers is expanded, part of the bearer is released.
  • the bearer context information may be delivered by the forward relocation request indication message.
  • the source network side network element When the network side performs the network element as the source network side network element, the source network side network element already knows the number of the bearer to be migrated. At this time, it is determined whether the target network side network element supports the number of bearers to perform the judgment and execution.
  • the bearer management method of the specific embodiment of the present disclosure when used for the source network side network element, before releasing the partial bearer, further includes:
  • an indication information where the indication information is used to indicate whether the target network side network element supports a bearer quantity extension
  • the release part of the bearer is specifically:
  • the partial bearer is released.
  • the target network side network element may send a context request message carrying indication information indicating whether the target network side network element supports the bearer number extension.
  • the source network side network element further sends a second context request response message carrying the bearer context to the target network side network element to notify the target network side network element bearer that the release is completed.
  • the foregoing bearer release of the specific embodiment of the present disclosure may be combined with the notification of the previous bearer quantity extension capability support information. For example, after the foregoing migration is completed, if the target network side network element supports the bearer number extension, the handover may be completed.
  • the message, the tracking area update completion message, and the like carry indication information indicating that the target network side network element supports the bearer number extension, and notify the mobile communication terminal that the target network side network element supports the bearer number extension, so that the subsequent mobile communication terminal can carry the bearer based on the foregoing indication information. Management.
  • the UE carries one bit of information indicating "the UE supports the number of bearers to be extended" in the UE Network Capability information element of the Attach Request Message. Where “0" means no support and “1" means support.
  • the corresponding bearer management process is shown in Figure 4 and includes the following steps:
  • the UE sends an attach request message (carrying the user equipment network capability indication information element) to the Mobility Management Entity (MME) through the 3GPP access.
  • the user equipment network capability indication information element information includes the indication information of the “UE support bearer number extension” of the 1 bit, where “0” indicates that the UE does not support the extension of the EPS bearer, and “1” indicates that the UE supports the extension of the EPS bearer.
  • the UE implements the information of whether or not it supports the number of bearers to be extended to the network side.
  • the MME may also carry the indication information to the UE in the attach accept message sent by the 3GPP access, and notify the UE by the information indicating whether the bearer number extension is supported by the indication information.
  • the "network support EPS bearer number extension" may be indicated by the 1 bit bit in the attach accept message.
  • the UE carries a 1-bit information indicating "the UE supports the number of bearers to be extended" in the UE Network Capability information element of the Tracking Area Update (TAU) request message. Where “0" means no support and “1" means support.
  • TAU Tracking Area Update
  • the UE selects an E-UTRAN cell of a TA, and the cell is not in the TAI (Tracking Area Identity) list of the UE registration network, thereby triggering the TAU process (ie, the tracking area update process);
  • TAI Tracking Area Identity
  • the UE sends a Tracking Area Update Request message (carrying the User Equipment Network Capability Indicator Information Element) to the Mobility Management Entity (MME) through the 3GPP access.
  • the user equipment network capability indication information element information includes the indication information of the “UE support bearer number extension” of the 1 bit, where “0” indicates that the UE does not support the extension of the EPS bearer, and “1” indicates that the UE supports the extension of the EPS bearer.
  • the UE implements the information of whether or not it supports the number of bearers to be extended to the network side.
  • the MME may also carry the indication information to the UE in the tracking area update accept message sent by the 3GPP access, and notify the UE by using the indication information whether the information supporting the number of bearers is extended.
  • the "network support EPS bearer number extension" may be indicated by the 1 bit bit in the attach accept message.
  • the target MME determines whether the bearer can be accepted according to the context sent by the source MME (ie, the source network side network element). If not, the partial bearer is released.
  • the UE carries a 1-bit information indicating "the UE supports the number of bearers to be extended" in the UE Network Capability information element of the Tracking Area Update (TAU) request message. Where “0" means no support and “1" means support.
  • TAU Tracking Area Update
  • the UE selects an E-UTRAN cell of a TA, which is not in the TAI (Tracking Area Identity) list of the UE registration network, thereby triggering the TAU process (ie, the tracking area update process);
  • TAI Tracking Area Identity
  • the UE sends a Tracking Area Update (TAU) request message to the target MME through the 3GPP access, and if the UE supports the bearer number extension indication is 0, it indicates that the UE does not support the bearer number extension; If the extension indication is 1, it indicates that the UE supports the number of bearers;
  • TAU Tracking Area Update
  • the target MME sends a Context Request message to the source MME to obtain user information.
  • the source MME returns a context request response (Context Response) message, and carries information such as an IMSI, a five-element authentication group, and a bearer context;
  • Context Response Context Response
  • the target MME determines whether to release part of the bearer according to the bearer context information in the Context Response and its own capability (the ability to support the number of bearers).
  • the target MME does not support the bearer number extension and the number of bearers in the bearer context exceeds 8, the target MME releases the partial bearer according to the QoS parameters of the bearer, such as QCI and ARP, etc., such as priority guarantee voice priority.
  • the bearer corresponding to the service preferentially releases the bearer of the low priority service. If the target MME supports the bearer number extension, the subsequent normal TAU process is continued (refer to 3GPP TS 23.401).
  • the target MME sends a TAU Accept (TAU Accept) message to the UE through 3GPP access.
  • TAU Accept TAU Accept
  • the 1st bit is used in the TAU Accept message to indicate “the network supports the EPS bearer number extension”;
  • the target SGSN determines whether the bearer can be accepted according to the UE context sent by the source MME. If not, the partial bearer is released.
  • the UE is equipped with a 1-bit information indicating that "the UE supports the number of bearers to be extended" in the UE core network Capability information element of the RAU Request message in the RAU procedure. Where “0” means no support and “1” means support.
  • the UE selects an E-UTRAN cell of a TA, and the cell is not in the TAI (Tracking Area Identity) list of the UE registration network, thereby triggering the RAU process (ie, the routing area update process);
  • TAI Tracking Area Identity
  • the UE sends a RAU Request message to the serving GPRS support node SGSN through the UTRAN. If the UE supports the bearer number extension indication is 0, it indicates that the UE does not support the bearer number extension; if the UE supports the bearer number extension indication If 1, it indicates that the UE supports the number of bearers.
  • the SGSN sends a Context Request message to the MME to obtain user information.
  • the MME returns a Context Response message carrying the IMSI, the quintuple authentication group, the bearer context, the S-GW signaling address, and the TEID.
  • the SGSN determines whether to release part of the bearer according to the bearer context information in the Context Response and its own capabilities.
  • the SGSN releases the bearer, for example, the bearer corresponding to the high priority service such as voice priority, and the bearer of the low priority service is preferentially released. If the number of bearers in the bearer context does not exceed 8, Continue the follow-up RAU process (refer to the related introduction in section 5.3.3.3 of TS 23.401)
  • FIG. 6 and FIG. 7 are only differences between the source network and the target network type, but are all determined and executed by the target network side network element.
  • the source MME determines whether the bearer can be accepted according to the UE context and the capability of the target MME. If not, the partial bearer is released.
  • the UE carries the 1-bit indication information in the UE Network Capability information element of the Tracking Area Update (TAU) request message, and is used to indicate the information that the UE supports the bearer number extension. Where “0" means no support and “1" means support.
  • TAU Tracking Area Update
  • the corresponding bearer management process is shown in Figure 8, and includes the following steps:
  • the UE selects an E-UTRAN cell of a TA that is not in the TAI list of the UE registration network, thereby triggering the TAU procedure;
  • the UE sends a TAU Request message to the target MME through the 3GPP access, and if the UE supports the bearer number extension indication is 0, it indicates that the UE does not support the bearer number extension; if the UE supports the bearer number extension indication is 1, the UE indicates Support the number of bearers to expand;
  • the target MME sends a context request (Context Request) message to the source MME, requesting the user information, where the target MME supports the indication information of the bearer number extension;
  • the source MME determines whether to release part of the bearer according to the information of the UE Context.
  • the source MME releases the partial bearer according to the bearer QoS parameters, such as QCI and ARP. (If the bearer corresponding to the high-priority service such as voice is preferentially guaranteed, the bearer of the low-priority service is preferentially released);
  • Context Response a context request response message
  • the message carries an IMSI, a five-element authentication group, a bearer context, an S-GW signaling address, and a TEID;
  • the target MME sends a TAU accept message to the UE through the 3GPP access, and carries the indication information. If the target MME supports the extension of the number of bearers, the TAU Accept message indicates that the network supports the EPS bearer number extension by using one bit indication information. .
  • the source MME determines whether it can accept all bearers according to the capabilities of the UE context and the SGSN. If not, the partial bearer is released.
  • the UE carries 1 bit of information indicating "UE supports bearer number extension" in the UE Network Capability of the RAU request message in the RAU procedure. Where “0" means no support and “1" means support.
  • the UE selects a UTRAN cell that is not in the TAI list of the UE registration network, thereby triggering the RAU procedure;
  • the UE sends the RAU Request message to the SGSN through the UTRAN. If the UE supports the number of bearer extension indications, the UE does not support the bearer number extension. If the UE supports the bearer number extension indication, the UE supports the bearer number extension. ;
  • the SGSN sends a Context Request message to the MME requesting to obtain user information.
  • the MME determines, according to the information of the UE Context, whether to release part of the bearer;
  • the MME determines the bearer priority according to the QoS parameters of the bearer, such as the QCI and the ARP, and releases the bearer corresponding to the high priority service such as voice priority. Bearer of priority service);
  • Context Response a context request response message
  • the message carries an IMSI, a five-element authentication group, a bearer context, an S-GW signaling address, and a TEID;
  • the SGSN sends an RAU accept message to the UE.
  • the target MME can accept all bearers according to the judgment in the user context information sent by the source MME, and if not, release part of the bearer;
  • the corresponding bearer management process is shown in Figure 10 and includes the following steps:
  • the UE is in the connected state, and the source eNodeB determines to initiate the handover process through the S1 interface, and sends a handover request message to the 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 includes the IMSI, the UE security context, the UE network capability, the AMBR, and the bearer context.
  • the target MME determines whether to release part of the bearer according to the bearer context of the UE and its own capability
  • the target MME does not support the extension of the bearer and the current number of bearers exceeds 8
  • the target MME releases the partial bearer according to the QoS parameters of the bearer, such as the priority of the bearer, such as the QCI and the ARP.
  • the bearer which preferentially releases the bearer of the low-priority service, performs the normal handover procedure (refer to 3GPP TS 23.401), otherwise the normal handover procedure is directly performed.
  • the UE initiates a TAU procedure, which can be referred to FIG. 6, FIG. 8, and its corresponding description.
  • the target side SGSN determines whether the bearer can be accepted according to the UE context sent by the source MME, and if not, releases part of the bearer;
  • the UE is in the connected state, and the source eNodeB decides to switch the UE to the UTRAN Iu mode and initiates a handover procedure;
  • the source eNodeB sends a handover request message to the 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 includes the IMSI, the UE security context, the UE network capability, the AMBR, and the bearer context.
  • the target SGSN determines whether to release part of the bearer according to the bearer context of the UE and its own capability
  • the target SGSN releases the bearer according to the QoS parameters of the bearer, such as the QCI and the ARP, and the priority of the bearer is released (for example, the bearer corresponding to the high priority service such as voice priority is preferentially guaranteed, and the low priority is preferentially released.
  • the normal handover procedure is performed after the bearer of the service (refer to 3GPP TS 23.401). If the current number of bearers is less than 8, the normal handover procedure is directly performed.
  • the UE initiates a TAU procedure, which can be referred to FIG. 6, FIG. 8, and its corresponding description.
  • the source MME determines whether it can accept all bearers according to the UE context and the capabilities of the target MME, and if not, releases part of the bearer;
  • the corresponding bearer management process is shown in Figure 12 and includes the following steps:
  • the UE is in the connected state, and the source eNodeB decides to initiate the handover process through the S1 interface.
  • the source eNodeB sends a handover request message to the source MME;
  • the source MME selects a target MME, and the source MME determines whether to release part of the bearer according to the UE context information and the target MME capability.
  • the target MME does not support the bearer number extension, but the UE context indicates that the UE supports the bearer extension and the current bearer number exceeds 8, the source MME releases the partial bearer according to the bearer QoS parameters, such as QCI and ARP, etc. If the bearer corresponding to the high-priority service such as voice is preferentially guaranteed, the bearer of the low-priority service is preferentially released, and the normal handover process is continued, otherwise the subsequent normal handover process is directly continued.
  • the bearer QoS parameters such as QCI and ARP, etc.
  • the source MME sends a forward relocation request message to the target MME, and the UE performs the TAU process. Please refer to the description of the previous TAU process, and details are not described herein.
  • the source MME determines whether the bearer can be accepted according to the UE context and the capability of the target side SGSN, and if not, releases part of the bearer;
  • the corresponding bearer management process is shown in Figure 13, and includes the following steps:
  • the UE is in the connected state, and the source eNodeB decides to switch the UE to the UTRAN Iu mode and initiates a handover procedure;
  • the source eNodeB sends a handover request message to the source MME, requesting the core network to establish resources in the target RNC, the SGSN, and the S-GW;
  • the source MME determines whether to release part of the bearer according to the UE Context information and the capability of the target SGSN.
  • the source MME releases the partial bearer according to the QoS parameters of the bearer, such as the priority of the bearer, such as the QCI and the ARP, and the bearer corresponding to the high priority service such as voice priority is preferentially released, and the low priority service is preferentially released. After the bearer), continue the normal switching process, otherwise continue the normal switching process directly.
  • the QoS parameters of the bearer such as the priority of the bearer, such as the QCI and the ARP
  • the bearer corresponding to the high priority service such as voice priority is preferentially released, and the low priority service is preferentially released.
  • the MME determines whether the number of bearers of the UE exceeds a maximum limit.
  • the corresponding bearer management method includes 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 3GPP access;
  • the MME verifies the EPS bearer identifier, the UE context, and checks whether the bearer resource can be established for the UE (for example, whether the number of UE bearers exceeds the maximum number of bearers);
  • the MME initiates a regular dedicated EPS bearer context activation process or an EPS bearer context modification process
  • the MME sends a reject message to the UE, and the reject information should include an ESM value (such as 65, indicating that the maximum number of bearers has been reached).
  • an ESM value such as 65, indicating that the maximum number of bearers has been reached.
  • another embodiment of the present disclosure further provides a bearer management device for one of a network side network element and a mobile communication terminal.
  • the bearer management device includes:
  • the sending module 141 is configured to send, to the other one of the network side network element and the mobile communication terminal, indication information, where the indication information is used to indicate whether the bearer quantity extension is supported.
  • the bearer management device of the specific embodiment of the present disclosure is the execution body of the bearer management method provided by the present disclosure. Therefore, the bearer management device of the present disclosure can also be implemented.
  • the sending module 141 of the specific embodiment of the present disclosure is specifically configured to:
  • the user equipment network capability information element carrying the indication information is sent to the network side network element, where the indication information is used to indicate whether the mobile communication terminal supports the bearer quantity extension.
  • the sending module 141 is specifically configured to:
  • the request message carries the first indication information, where the first indication information is used to indicate whether the mobile communication terminal supports the bearer quantity extension;
  • the request message is an attach request message or a tracking area update request message.
  • the accept message carries the second indication information, where the second indication information is used to indicate whether the network side network element supports the bearer quantity extension, and the accept message is an attach accept message or a tracking area update accept message.
  • another embodiment of the present disclosure further provides a bearer management apparatus, which is used in one of a network side network element and a mobile communication terminal.
  • the bearer management apparatus includes:
  • the receiving module 151 is configured to receive indication information sent by another one of the network side network element and the mobile communication terminal, where the indication information is used to indicate whether the bearer quantity extension is supported.
  • the bearer management device of the specific embodiment of the present disclosure is the execution subject of the bearer management method provided by the present disclosure. Therefore, the bearer management device of the present disclosure can also be implemented.
  • the receiving module 151 of the specific embodiment of the present disclosure is specifically configured to:
  • the receiving module 151 of the specific embodiment of the present disclosure is specifically configured to:
  • the request message carries the first indication information, where the first indication information is used to indicate whether the mobile communication terminal supports the bearer quantity extension;
  • the request message is an attach request message or a tracking area update request message;
  • another embodiment of the present disclosure further provides a bearer management apparatus, where the network side executes a network element.
  • the bearer management apparatus includes:
  • the release module 161 is configured to release part of the bearer when the number of the to-be-migrated bearers to be migrated to the target network side network element that does not support the extended number of bearers is greater than the predetermined threshold, and the number of reserved bearers is less than or Equal to the predetermined threshold.
  • the bearer management device of the specific embodiment of the present disclosure is an execution body of the bearer management method applied to the network side execution network element provided by the present disclosure, and therefore the technical effect that the bearer management method can achieve, the bearer management device of the present disclosure is also Can be achieved.
  • the release module 161 of the specific embodiment of the present disclosure is specifically configured to:
  • the priority of the bearer to be migrated is released in descending order. Hosted.
  • the network side execution network element is an idle state mobile flow process or a target network side network element in the handover process.
  • the network side further includes:
  • the first obtaining module is configured to obtain bearer context information of the source network side network element.
  • the release module is specifically used to:
  • the first obtaining module is specifically configured to:
  • the network side When the network side performs the idle state mobile process or the source network side network element in the handover process, the network side further includes:
  • the second obtaining module is configured to obtain an indication information, where the indication information is used to indicate whether the target network side network element supports the bearer quantity extension.
  • the releasing module is configured to: when it is determined that the number of the to-be-migrated bearers is greater than a predetermined threshold according to the indication information and the number of the to-be-migrated bearers, and the target network side network element does not support the bearer number extension, the releasing part Hosted.
  • the bearer management device of this example further includes:
  • the response module 162 is configured to send a message carrying the bearer context to the target network side network element after releasing the partial bearer.
  • an embodiment of the present disclosure 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, a network interface 176, and a bus interface. among them:
  • the bearer management device further includes: a computer program stored on the memory 175 and executable on the processor 174, and the computer program is executed by the processor 174 to implement the following steps:
  • the indication information is sent to the other of the network side network element and the mobile communication terminal, where the indication information is used to indicate whether the bearer quantity extension is supported.
  • the part of the bearer is released, and the number of reserved bearers is less than or equal to the predetermined threshold.
  • the specific number is:
  • the bus interface can include any number of interconnected buses and bridges, specifically linked by one or more processors represented by the processor and various circuits of the memory represented by memory 175.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Antenna 171, radio frequency device 172, and baseband device 173 together comprise a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the user interface 176 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 174 is responsible for managing the bus interface and the usual processing, and the memory 175 can store data used by the processor 174 in performing the operations.
  • the computer program of the present disclosure when executed by the processor 174, further implements the following steps:
  • the user equipment network capability information element carrying the indication information is sent to the network side network element, where the indication information is used to indicate whether the mobile communication terminal supports the bearer quantity extension.
  • the indication information is by any one of the sixth, seventh or eighth bit or the tenth to the fifteenth octet in the ninth octet of the user equipment network capability information element. definition.
  • the computer program of the present disclosure when executed by the processor 174, further implements the following steps:
  • the request message carries the first indication information, where the first indication information is used to indicate whether the mobile communication terminal supports the bearer quantity extension;
  • the request message is an attach request Message or tracking area update request message;
  • the accept message carries the second indication information, where the second indication information is used to indicate whether the network side network element supports the bearer quantity extension, and the accept message is an attach accept message or Tracking area update accept message.
  • the bearer management method is used for the network side network element, when the computer program of the specific embodiment of the present disclosure is executed by the processor 174, the following steps are further implemented:
  • a user equipment network capability information element that carries the indication information, where the indication information is used to indicate whether the mobile communication terminal supports a bearer quantity extension.
  • the computer program of the present disclosure when executed by the processor 174, further implements the following steps:
  • the request message carries first indication information, where the first indication information is used to indicate whether the mobile communication terminal supports a bearer quantity extension; and the request message is an attach request message. Or tracking area update request message;
  • the bearer management method when used by the network side network element, when the bearer management method is used by the network side network element, when the computer program of the specific embodiment of the present disclosure is executed by the processor 174, the following steps are further implemented:
  • the bearer management method further includes:
  • the computer program of the present disclosure when executed by the processor 174, further implements the following steps:
  • the priority of the bearer to be migrated is released in descending order. Hosted.
  • the network side execution network element is an idle network mobile flow process or a source network side network element or a target network side network element in the handover process;
  • the computer program of the specific embodiment of the present disclosure is further implemented by the processor 174 before releasing the partial bearer:
  • the specific number is:
  • the network side execution network element is the source network side network element
  • the computer program of the specific embodiment of the present disclosure is further implemented by the processor 174 before releasing the partial bearer:
  • the release part of the bearer is specifically:
  • the bearer management method further includes:
  • another embodiment of the present disclosure further provides a computer readable storage medium having stored thereon a computer program, the computer program being executed by the processor to implement the following steps:
  • the indication information is sent to the other of the network side network element and the mobile communication terminal, where the indication information is used to indicate whether the bearer quantity extension is supported.
  • the part of the bearer is released, and the number of reserved bearers is less than or equal to the predetermined threshold.
  • the specific number is:
  • the user equipment network capability information element carrying the indication information is sent to the network side network element, where the indication information is used to indicate whether the mobile communication terminal supports the bearer quantity extension.
  • the indication information is defined by any one of the sixth, seventh or eighth bit or the tenth to the fifteenth octet in the ninth octet of the user equipment network capability information element. .
  • the request message carries the first indication information, where the first indication information is used to indicate whether the mobile communication terminal supports the bearer quantity extension;
  • the request message is an attach request Message or tracking area update request message;
  • the accept message carries the second indication information, where the second indication information is used to indicate whether the network side network element supports the bearer quantity extension, and the accept message is an attach accept message or Tracking area update accept message.
  • the bearer management method is used by the network side network element, when the computer program of the specific embodiment of the present disclosure is executed by the processor, the following steps are further implemented:
  • a user equipment network capability information element that carries the indication information, where the indication information is used to indicate whether the mobile communication terminal supports a bearer quantity extension.
  • the request message carries first indication information, where the first indication information is used to indicate whether the mobile communication terminal supports a bearer quantity extension; and the request message is an attach request message. Or tracking area update request message;
  • the bearer management method further includes:
  • the priority of the bearer to be migrated is released in descending order. Hosted.
  • the network side execution network element is an idle network mobile process or a source network side network element or a target network side network element in the handover process;
  • network side execution network element is the target network side network element
  • computer program of the specific embodiment of the present disclosure when executed by the processor, the following steps are also implemented:
  • the specific number is:
  • the partial bearer is released.
  • the network side execution network element is the source network side network element
  • the computer program of the specific embodiment of the present disclosure is further implemented by the processor before releasing the partial bearer:
  • the release part of the bearer is specifically:
  • the bearer management method further includes:

Landscapes

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

Abstract

本公开提供一种承载管理方法及承载管理装置。承载管理方法用于网络侧网元和移动通信终端中的一个，包括：向网络侧网元和移动通信终端中的另一个发送指示信息，所述指示信息用于指示是否支持承载数量扩展。

Description

承载管理方法及承载管理装置
相关申请的交叉引用
本申请主张在2018年1月10日在中国提交的中国专利申请号No.201810023628.1的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及通信技术领域，特别是指一种承载管理方法及承载管理装置。
背景技术
相比于3G通信系统和4G通信系统，5G通信系统支持的最大承载数量得到了扩展，在TSG SA第78次全会中规定5G通信系统由原来的最大8个承载扩展为最大15个承载。
为了与5G通信系统对齐，4G通信系统的承载数量预计也会扩展到15个，这样网络中就会出现支持承载数量扩展的网元和不支持承载数量扩展的网元的共存现象。
因此有必要就支持承载数量扩展的网元和不支持承载数量扩展的网元的共存时的移动通信终端侧与网络侧的交互进行规范。
发明内容
本公开的目的是提供一种承载管理方法及承载管理装置，用于规范支持承载数量扩展的网元和不支持承载数量扩展的网元的共存时网络侧网元和移动通信终端之间的信息交互。
为实现上述目的，一方面，本公开的实施例提供一种承载管理方法，用于网络侧网元和移动通信终端中的一个，所述承载管理方法包括：
向网络侧网元和移动通信终端中的另一个发送指示信息，所述指示信息用于指示是否支持承载数量扩展。
另一方面，本公开的实施例还提供一种承载管理方法，用于网络侧网元和移动通信终端中的一个，所述承载管理方法包括：
接收网络侧网元和移动通信终端中的另一个发送的指示信息，所述指示信息用于指示是否支持承载数量扩展。
此外，本公开实施例还提供一种承载管理方法，用于网络侧执行网元，所述承载管理方法包括：
当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载，保留的承载的数量小于或等于所述预定门限。
此外，本公开的实施例还提供一种承载管理装置，用于网络侧网元和移动通信终端中的一个，承载管理装置包括：
发送模块，用于向网络侧网元和移动通信终端中的另一个发送指示信息，所述指示信息用于指示是否支持承载数量扩展。
此外，本公开的实施例还提供一种承载管理装置，用于网络侧网元和移动通信终端中的一个，所述承载管理装置包括：
接收模块，用于接收网络侧网元和移动通信终端中的另一个发送的指示信息，所述指示信息用于指示是否支持承载数量扩展。
此外，本公开的实施例还提供另一种承载管理装置，用于网络侧执行网元，所述承载管理装置包括：
释放模块，用于当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载，保留的承载的数量小于或等于所述预定门限。
此外，本公开的实施例还提供一种承载管理装置包括：处理器、存储器以及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述计算机程序被处理器执行时实现本公开提供的承载管理方法中的所有步骤。
此外，本公开的实施例还提供一种计算机可读存储介质，其上存储有计算机程序，述计算机程序被处理器执行时实现本公开提供的承载管理方法中的所有步骤。
本公开的上述方案具有如下有益效果：
本公开具体实施例规范了支持承载数量扩展的网元和不支持承载数量扩展的网元的共存时网络侧网元和移动通信终端之间的信息交互，使得网络侧 网元和移动通信终端能够告知对方是否支持承载数量扩展，从而可以让支持承载数量扩展的移动通信终端能够与支持承载数量扩展的网络侧网元建立扩展部分的承载，而双方有任一者不支持承载数量扩展时，移动通信终端和/或网络侧能够基于交互的信息进行承载资源的合理分配。
附图说明
图1为本公开实施例提供的用于网络侧网元和移动通信终端中的一个的承载管理方法的步骤示意图；
图2为本公开实施例提供的用于网络侧网元和移动通信终端中的一个的承载管理方法的步骤示意图；
图3为本公开实施例的在网络侧执行的承载管理方法的步骤示意图；
图4-图13分别为本公开实施例的承载管理方法的不同实现方式的示意图；
图14为本公开实施例的用于网络侧网元和移动通信终端中的一个的承载管理装置的逻辑结构示意图；
图15为本公开实施例的用于网络侧网元和移动通信终端中的一个的承载管理装置的逻辑结构示意图；
图16为本公开实施例的在网络侧执行的承载管理装置的结构示意图；及
图17为本公开实施例提供的承载管理装置的实际结构示意图。
具体实施方式
为使本公开要解决的技术问题、技术方案和优点更加清楚，下面将结合附图及具体实施例进行详细描述。在下面的描述中，提供诸如具体的配置和组件的特定细节仅仅是为了帮助全面理解本公开的实施例。因此，本领域技术人员应该清楚，可以对这里描述的实施例进行各种改变和修改而不脱离本公开的范围和精神。另外，为了清楚和简洁，省略了对已知功能和构造的描述。
在本公开的各种实施例中，应理解，下述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应 对本公开实施例的实施过程构成任何限定。
本公开用于规范支持承载数量扩展的网元和不支持承载数量扩展的网元的共存时网络侧网元和移动通信终端之间的信息交互。
一方面，本公开的实施例提供一种承载管理方法，用于网络侧网元和移动通信终端(例如用户设备)中的一个，如图1所示，承载管理方法包括：
步骤11，向网络侧网元和移动通信终端中的另一个发送指示信息，该指示信息用于指示是否支持承载数量扩展。
例如：网络侧网元向移动通信终端发送的指示信息则用于指示网络侧网元是否支持承载数量扩展；对应地，通信终端向网络侧网元发送的指示信息则用于指示通信终端是否支持承载数量扩展。
本公开具体实施例规范了支持承载数量扩展的网元和不支持承载数量扩展的网元的共存时网络侧网元和移动通信终端之间的信息交互，使得网络侧网元和移动通信终端能够告知对方是否支持承载数量扩展，从而可以让支持承载数量扩展的移动通信终端能够与支持承载数量扩展的网络侧网元建立扩展部分的承载，而双方有任一者不支持承载数量扩展时，移动通信终端和/或网络侧能够基于交互的信息进行承载资源的合理分配。
应当理解的是，上述图1所示的承载管理方法实际上包括两个技术方案，即：
移动通信终端向网络侧网元发送指示信息，该指示信息用于指示是否支持承载数量扩展；
以及
网络侧网元向移动通信终端发送指示信息，该指示信息用于指示是否支持承载数量扩展。
当然，二者可以同时存在。
对技术效果说明如下。
当网络侧网元向移动通信终端发送指示信息，假定网络侧网元不支持承载数量扩展，则当移动通信终端目前已经建立8个承载时，即使存在更多的承载资源需求，由于移动通信终端知晓网络侧网元不支持承载数量扩展，因此不会再向网络侧网元请求更多的承载资源；
同样当移动通信终端向网络侧网元发送指示信息，假定移动通信终端不支持承载数量扩展，则当移动通信终端目前已经建立8个承载时，即使网络侧网元支持更多的承载资源，但由于网络侧网元知晓移动通信终端不支持承载数量扩展，因此不会再向移动通信终端分配更多的移动通信终端无法使用的承载资源。
下面对本公开具体实施例的承载管理方法进行详细介绍。
示例性地，为避免增加网络的信令开销，本公开具体实施例的指示信息可以由已有信令和/或信息元素负责携带。
例如，本公开具体实施例的承载管理方法用于移动通信终端时，移动通信终端可以向网络侧网元发送携带该指示信息的用户设备网络能力信息元素，该指示信息用于指示移动通信终端是否支持承载数量扩展。
其中，网络能力信息元素是现有网络提供的与EPS有关的信息或与GPRS交互的信息，该内容会影响网络处理移动通信终端操作的方式。目前网络能力信息的结构如下表所示：
Figure PCTCN2019070827-appb-000001
其中网络能力信息元素包括15个八比特组，每个八比特组包含有八个比特。
参考octet3，其中第1-第8个bit分别用于指示终端是否支持EEA0、128-EEA1、128-EEA2、128-EEA3、EEA4、EEA5、EEA6、EEA7等算法。
参考octet9，其中第5个bit(DCNR)用于指示终端是否支持与NR通信 系统的双连接。
以EEA0、128-EEA1以及DCNR为例介绍如下。
其中，octet3的第8个bit在网络能力信息元素中的取值为0或1，表示如下信息：
octet3的第8个bit取值1表示演进的分组系统(Evolved Packet System，EPS)支持EEA0算法；
octet3的第8个bit取值0表示EPS不支持EEA0算法；
其中，octet3的第7个bit在网络能力信息元素中的取值为0或1，表示如下信息：
octet3的第7个bit取值1表示EPS支持128-EEA1算法；
octet3的第7个bit取值0表示EPS不支持128-EEA1算法。
其中，octet9的第5个bit在网络能力信息元素中的取值为0或1，表示如下信息：
Octet9的第5个bit取值1表示支持与NR通信系统的双连接；
octet9的第5个bit取值0表示不支持与NR通信系统的双连接。
结合上表可以发现，在网络能力信息元素有部分bit标记为“0spare”，这表示这些bit没有被定义，属于待定义的比特，本实施可以使用空留比特表示上述的指示信息。
从上表中可以看出，网络能力信息元素的第9个八比特组中的第6、第7或第8个bit或第10个到第15个八比特组中的任意一个bit均为待定义比特，本公开具体实施例的指示信息可以由这些比特中的一个或多个定义。
例如，本公开具体实施例可以使用网络能力信息元素的第九个比特组中的第6个bit表示指示信息(INOBEAR)，则修改后的网络能力信息元素第9个八比特组结构如下表所示：
Figure PCTCN2019070827-appb-000002
其中，INOBEAR表示指示信息，在网络能力信息元素中的取值为0或1。
通过上述修改后，第九个比特组的第6个bit取值1表示表示移动通信终 端支持承载数量扩展，而第九个比特组的第6个bit取值0则表示表示移动通信终端不支持承载数量扩展。
当然，使用现有的网络能力信息元素来携带指示信息仅是本公开具体实施例其中一种可行方案，作为其他方案，本公开具体实施例也可以使用其他新定义的信息元素来携带该指示信息。
为了节约信令开销和空口资源，在本公开具体实施例中，该指示信息可以通过已有的信令来携带，如：
移动通信终端可以通过附着过程中的附着请求消息或者跟踪区更新过程中的跟踪区更新消息携带上述的指示信息，使得网络侧网元能够在接收到上述的附着请求消息或者跟踪区更新消息后，即可获取其中携带的指示信息，进而知晓移动通信终端是否支持承载数量扩展。
而网络侧网元相应的也可以通过附着过程中的附着接受消息或者跟踪区更新过程中的跟踪区接受消息携带上述的指示信息，使得移动通信终端能够在接收到上述的附着接受消息或者跟踪区接受消息后，即可获取其中携带的指示信息，进而知晓网络侧是否支持承载数量扩展。
即本公开具体实施例中，上述的向网络侧网元和移动通信终端中的另一个发送指示信息，该指示信息用于指示是否支持承载数量扩展局可以是：
移动通信终端向网络侧网元发送一请求消息，该请求消息为附着请求消息或跟踪区更新请求消息，且携带有第一指示信息，该第一指示信息用于指示移动通信终端是否支持承载数量扩展；
或者
网络侧网元向移动通信终端发送一接受消息，该接受消息为附着接受消息或跟踪区更新接受消息，且携带有第二指示信息，该第二指示信息用于指示网络侧网元是否支持承载数量扩展。
这里需要进一步强调的是，上述的指示信息由已有信令传输仅是可选的方式，而非必需的实现方式，作为其他可行方案，本公开具体实施例的指示信息也可以由专属的信令和/或专属的信息元素携带。
另一方面，本公开的另一实施例还提供一种承载管理方法，用于网络侧 网元和移动通信终端中的一个，如图2所示，该承载管理方法包括：
步骤21，接收网络侧网元和移动通信终端中的另一个发送的指示信息，该指示信息用于指示是否支持承载数量扩展。
应当理解的是，上述图2所示的承载管理方法实际上包括两个技术方案，即：
移动通信终端接收网络侧网元发送的指示信息，该指示信息用于指示网络侧网元是否支持承载数量扩展；
以及
网络侧网元接收移动通信终端发送的指示信息，该指示信息用于指示移动通信终端是否支持承载数量扩展。
本公开具体实施例规范了支持承载数量扩展的网元和不支持承载数量扩展的网元的共存时网络侧网元和移动通信终端之间的信息交互，使得网络侧网元和移动通信终端能够告知对方是否支持承载数量扩展，从而可以让支持承载数量扩展的移动通信终端能够与支持承载数量扩展的网络侧网元建立扩展部分的承载，而双方有任一者不支持承载数量扩展时，移动通信终端和/或网络侧能够基于交互的信息进行承载资源的合理分配。
当移动通信终端接收到网络侧网元发送的指示信息，假定网络侧网元不支持承载数量扩展，则当移动通信终端目前已经建立8个承载时，即使存在更多的承载资源需求，由于移动通信终端知晓网络侧网元不支持承载数量扩展，因此不会再向网络侧网元请求更多的承载资源；
同样当网络侧网元接收到移动通信终端发送的指示信息，假定移动通信终端不支持承载数量扩展，则当移动通信终端目前已经建立8个承载时，即使网络侧网元支持更多的承载资源，但由于网络侧网元知晓移动通信终端不支持承载数量扩展，因此不会再给移动通信终端分配更多的承载资源。
此外，为避免增加网络的信令开销，本公开具体实施例的指示信息可以由已有信令和/或信息元素负责携带。
示例性地，参考上文介绍，本公开具体实施例的指示信息可以由用户设备网络能力信息元素携带。具体地，指示信息由用户设备网络能力信息元素 的第9个八比特组中的第6、第7或第8个bit或第10个到第15个八比特组中的任意一个bit定义。
当然，使用网络能力信息元素携带指示信息仅是本公开具体实施例其中一种实现方式，作为其他可行方案，本公开具体实施例也可以设置单独的信息元素来携带上述的指示信息。
而从信令角度，本公开实施例的指示信息也可以是通过已有信令或者新信令来携带。
当然，为了节约信令开销和空口资源，本公开具体实施例中，使用移动通信终端与网络侧网元之间的已有信令来携带上述的指示信息，如：
移动通信终端可以通过附着过程中的附着请求消息或者跟踪区更新过程中的跟踪区更新消息携带上述的指示信息，使得网络侧网元能够接收上述的附着请求消息或者跟踪区更新消息，并获取其中携带的指示信息，进而知晓移动通信终端是否支持承载数量扩展。
而网络侧网元相应的也可以通过附着过程中的附着接受消息或者跟踪区更新过程中的跟踪区接受消息携带上述的指示信息，使得移动通信终端能够接收上述的附着接受消息或者跟踪区接受消息，并获取其中携带的指示信息，进而知晓网络侧是否支持承载数量扩展。
即本公开具体实施例中，接收网络侧网元和移动通信终端中的另一个发送的指示信息，所述指示信息用于指示是否支持承载数量扩展具体可以为：
网络侧网元接收移动通信终端发送的请求消息，所述请求消息中携带第一指示信息，该第一指示信息用于指示移动通信终端是否支持承载数量扩展；该请求消息为附着请求消息或跟踪区更新请求消息；
或者，
移动通信终端接收网络侧网元发送的接受消息，所述接受消息中携带第二指示信息，该第二指示信息用于指示网络侧网元是否支持承载数量扩展，该接受消息为附着接受消息或跟踪区更新接受消息。
当然除上述实现方式外，本公开具体实施例的指示信息也可以通过专属信令进行传输。
通过上述的过程，移动通信终端可以知晓网络侧网元的承载数量扩展支持能力，和/或网络侧网元可以知晓移动通信终端的承载数量扩展支持能力，在知晓对端的承载数量扩展支持能力之后，即可依据对端的承载数量扩展支持能力进行相应的承载管理，对此进一步说明如下。
在服务过程中，移动通信终端或者网络侧需要根据业务需求实时改变二者之间的承载数量，而该需求可以是通过承载资源分配流程或承载资源修改流程来实现。为避免分配到的承载资源超出了网元的实际能力，本公开具体实施例的承载管理方法当应用于网络侧网元时，网络侧网元应拒绝移动通信终端发起的超出该移动通信终端承载能力的承载资源分配请求或承载资源修改请求。
即，网络侧网元接收的指示信息用于指示移动通信终端是否支持承载数量扩展，本公开具体实施例的承载管理方法还包括：
网络侧网元接收移动通信终端发送的承载资源分配请求或承载资源修改请求；
网络侧网元在根据指示信息判断出移动通信终端不支持承载数量扩展，且移动通信终端已建立承载的数量达到预定门限时，拒绝承载资源分配请求或承载资源修改请求。
例如，移动通信终端不支持承载数量扩展，其当前已建立承载的数量达到最大上限8个时，若向网络侧网元发送承载资源分配请求或承载资源修改请求以重新分配更多的承载时，网络侧网元直接拒绝该承载资源分配请求或承载资源修改请求，避免资源浪费。
在服务过程中，移动通信终端在连接态(服务状态)或者空闲态都可能会发生移动，而这种移动就可能会触发空闲态移动流程或切换流程，而在上述的流程中，网络侧网元会发生变化，而变化前后的网元的承载数量扩展支持能力则有可能会发生变化，如果直接将原有承载直接迁移，则可能发生实际承载数量超出目标网络侧网元的能力的问题。因此有必要针对上述情况进行规范。
应当理解的是，本公开具体实施例中空闲态移动流程指的是空闲态下网 络侧的服务网元可能发生改变的流程，如跟踪区更新流程，而切换流程指的是连接态下网络侧服务网元可能发生变化的流程，如硬切换流程等。一旦网络侧服务网元可能发生变化，就可能出现新网元和旧网元的承载数量扩展支持能力不同的情况，有必要对此进行规范，以保证业务的正常处理。
这些将在后续结合图6-13进行进一步详细说明。
基于上述需求，本公开的实施例还提供一种承载管理方法，用于网络侧执行网元，如图3所示，该承载管理方法包括：
步骤31，当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载，保留的承载的数量小于或等于所述预定门限。
基于本公开实施例的承载管理方法，当移动通信终端从源网络侧网元切换至目标网络侧网元时，如果目标网络侧网元不支持承载数量扩展，且移动通信终端在源网络侧网元所分配的承载数量超出目标网络侧网元的最大承载数量时，则网络侧执行网元(可能是源网络侧网元，也可以是目标网络侧网元)主动释放移动通信终端的一部分承载，从而保证剩余的承载数量在目标网络侧网元的承载能力范围内，保证目标网络侧网元能够为移动通信终端提供正常的业务服务。
下面对本公开具体实施例的承载管理方法进行详细介绍。
当待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限，需要释放一部分承载，以与目标网络侧网元的能力相匹配，保证服务的正常进行。本公开具体实施例中，为所有的承载设置一优先级，当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，按照待迁移承载的优先级从低到高的顺序释放部分承载。
在实际应用中，本公开具体实施例可以根据QoS(Quantity of Service，服务质量)参数来确定承载的优先级。QOS参数可以反映承载的网络质量，承载的网络质量越好则对应越高的优先级，反之，承载的网络质量越差则对应越低的优先级。显然，网络侧执行网元按照优先级从低到高的顺序释放部 分承载，可以保证移动通信终端优先保留网络质量较高的承载。
而上述的QoS参数可以是QoS分类标识参数和分配和保持优先级参数等参数。
如依据上述的策略，可以优先释放为网页浏览分配的承载，而为语音业务分配的承载。
当然，需要说明的是，上述承载优先级的确定方法仅用于示例性介绍，并不限制本公开的保护范围。作为其他可行方案，承载的优先级也可以由多个参考因素进行加权求和后确定，这里本文不再举例赘述。
此外，在实际应用中，本公开具体实施例的网络侧执行网元可以为空闲态移动流程或切换流程中的源网络侧网元，即源网络侧网元在移动通信终端切换至目标网络侧网元前，提前释放移动通信终端的承载资源；
或者，本公开具体实施例的网络侧执行网元也可以是空闲态移动流程或切换流程中的目标网络侧网元，当移动通信终端在切换至目标网络侧网元后，由目标网络侧网元来释放移动通信终端的承载资源。
不管由源网络侧网元还是目标网络侧网元执行，都需要知晓两个信息，即：目标网络侧网元是否支持承载数量扩展，以及待迁移承载的数量。
以网络侧执行网元为目标网络侧网元为例，此时目标网络侧网元知晓自身是否支持承载数量扩展，只需要获取待迁移承载的数量即可进行判决和执行，这种情况下，本公开具体实施例的承载管理方法中，目标网络侧网元可以通过上下文请求响应消息中携带的承载上下文信息确定承载数量。
即，本公开具体实施例的承载管理方法用于目标网络侧网元时，在释放部分承载之前，还包括：
获取源网络侧网元的承载上下文信息。
所述当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载具体为：
当根据承载上下文信息以及所述目标网络侧网元的承载数量扩展支持能力判断出所述待迁移承载的数量大于预定门限，且所述目标网络侧网元不支持承载数量扩展时，释放部分承载。
上述情况下，本公开具体实施例的承载管理方法应用于跟踪区更新流程时，可以通过上下文请求流程来获取承载上下文，即，本公开具体实施例的承载管理方法应用于跟踪区更新流程时，在释放部分承载之前，还包括：
向源网络侧网元发送第一上下文请求消息；
接收源网络侧网元发送的第一上下文请求响应消息，该第一上下文请求响应消息为源网络侧网元未响应第一上下文请求消息所发送的，该第一上下文请求响应消息中携带有移动通信终端当前的承载上下文信息；
其中，当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时具体为：
目标网络侧网元当根据第一上下文请求响应消息中携带的承载上下文信息以及目标网络侧网元的承载数量扩展支持能力判断出待迁移承载的数量大于预定门限，且目标网络侧网元不支持承载数量扩展时，释放部分承载。
而当应用于切换流程时，则可以通过前向重定位请求指示消息传递上述的承载上下文信息。
而当网络侧执行网元为源网络侧网元时，源网络侧网元已经知晓待迁移承载的数量，此时再确定目标网络侧网元是否支持承载数量扩展即可进行判决和执行。
即，本公开具体实施例的承载管理方法，用于源网络侧网元时，在释放部分承载之前，还包括：
获取一指示信息，所述指示信息用于指示所述目标网络侧网元是否支持承载数量扩展；
所述当归属于同一移动通信终端的待迁移到目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载具体为：
当根据所述指示信息以及所述待迁移承载的数量判断出所述待迁移承载的数量大于预定门限，且所述目标网络侧网元不支持承载数量扩展时，释放部分承载。
上述情况下，本公开具体实施例的承载管理方法应用于跟踪区更新流程时，可以由目标网络侧网元发送携带指示目标网络侧网元是否支持承载数量 扩展的指示信息的上下文请求消息即可实现。在释放部分承载之后，源网络侧网元还发送携带承载上下文的第二上下文请求响应消息到目标网络侧网元，以通知目标网络侧网元承载释放完毕。当然，本公开具体实施例的上述的承载释放可以和之前的承载数量扩展能力支持信息的通知相结合，如在上述迁移完成后，如果目标网络侧网元支持承载数量扩展，则可以通过切换完成消息、跟踪区更新完成消息等携带指示目标网络侧网元支持承载数量扩展的指示信息，通知移动通信终端目标网络侧网元支持承载数量扩展，使得后续移动通信终端能够基于上述的指示信息进行承载的管理。
下面结合不同的实现方式对本公开的承载管理方法进行详细介绍。
实现方式一
UE在附着请求消息(Attach Request Message)的用户设备网络能力(UE Network Capability)信息元素中搭载1bit的用于指示“UE支持承载数量扩展”的信息。其中“0”表示不支持，“1”表示支持。
对应的承载管理流程如图4所示，包括如下步骤：
UE通过3GPP接入发送附着请求消息(携带有用户设备网络能力指示信息元素)给移动性管理实体(Mobility Management Entity，MME)。其中用户设备网络能力指示信息元素信息中包含了1bit的“UE支持承载数量扩展”的指示信息，其中“0”指示UE不支持EPS承载的扩展，“1”指示UE支持EPS承载的扩展。
通过上述过程，UE实现了将其是否支持承载数量扩展的信息告知了网络侧。
而如图4所示，MME也可以在通过3GPP接入发送的附着接受消息中携带指示信息给UE，通过指示信息将其是否支持承载数量扩展的信息告知了UE。
本步骤中，如果MME支持承载数量扩展，则可以在附着接受消息中利用1bit位指示“网络支持EPS承载数扩展”。
图4中常规附着流程并未改变，请参考3GPP TS23.401。
实现方式二
UE在跟踪区更新(Tracking Area Update，TAU)请求消息的用户设备网络能力(UE Network Capability)信息元素中搭载1bit的用于指示“UE支持承载数量扩展”的信息。其中“0”表示不支持，“1”表示支持。
对应的承载管理流程如图5所示，包括如下步骤：
UE选择一个TA的E-UTRAN小区，该小区不在UE注册网络的TAI(跟踪区标识)列表中，从而触发TAU流程(即跟踪区更新流程)；
UE通过3GPP接入发送跟踪区更新请求消息(携带有用户设备网络能力指示信息元素)给移动性管理实体(Mobility Management Entity，MME)。其中用户设备网络能力指示信息元素信息中包含了1bit的“UE支持承载数量扩展”的指示信息，其中“0”指示UE不支持EPS承载的扩展，“1”指示UE支持EPS承载的扩展。
通过上述过程，UE实现了将其是否支持承载数量扩展的信息告知了网络侧。
而如图5所示，MME也可以在通过3GPP接入发送的跟踪区更新接受消息中携带指示信息给UE，通过指示信息将其是否支持承载数量扩展的信息告知了UE。
本步骤中，如果MME支持承载数量扩展，则可以在附着接受消息中利用1bit位指示“网络支持EPS承载数扩展”。
图5中常规跟踪区更新流程以及安全流程并未改变，请参考相关协议。
实现方式三
UE在空闲态移动过程中，目标MME(即目标网络侧网元)根据源MME(即源网络侧网元)传来的上下文判断能否接受所有的承载，不能的话，释放部分承载；
UE在跟踪区更新(Tracking Area Update，TAU)请求消息的用户设备网络能力(UE Network Capability)信息元素中搭载1bit的用于指示“UE支持承载数量扩展”的信息。其中“0”表示不支持，“1”表示支持。
对应的承载管理流程如图6所示，包括如下步骤：
UE选择一个TA的E-UTRAN小区，该小区不在UE注册网络的TAI(跟 踪区标识)列表中，从而触发TAU流程(即跟踪区更新流程)；
UE通过3GPP接入，发送跟踪区更新(Tracking Area Update，TAU)请求消息给目标MME，如果“UE支持承载数量扩展指示”为0，则表示UE不支持承载数量扩展；如果“UE支持承载数量扩展指示”为1，则表示UE支持承载数量扩展；
目标MME发送一个上下文请求(Context Request)消息给源MME以得到用户信息；
源MME返回一个上下文请求响应(Context Response)消息，携带IMSI、五元鉴权组、承载上下文等信息；
目标MME根据Context Response中的承载上下文信息以及自身能力(能否支持承载数量扩展的能力)，判断是否释放部分承载；
如果目标MME不支持承载数量扩展且承载上下文中的承载数量超过8，则目标MME根据承载的QoS参数，如QCI和ARP等判断承载的优先级来释放部分承载，如优先保证话音等高优先级业务对应的承载，优先释放低优先级业务的承载，如果目标MME支持承载数量扩展，则继续后续常规TAU过程(参考3GPP TS23.401)。
目标MME通过3GPP接入，发送TAU接受(TAU Accept)消息给UE。
如果目标MME支持承载数量的扩展，则在TAU Accept信息中利用1个bit位指示“网络支持EPS承载数扩展”；
实现方式四
UE在空闲态移动过程中，目标侧SGSN根据源MME传来的UE context判断能否接受所有承载，不能的话，释放部分承载；
UE在RAU流程中路由区更新请求(RAU Request)消息的用户设备网络能力(UE core Network Capability)信息元素中搭载1bit的用于指示“UE支持承载数量扩展”的信息。其中“0”表示不支持，“1”表示支持。
UE选择一个TA的E-UTRAN小区，该小区不在UE注册网络的TAI(跟踪区标识)列表中，从而触发RAU流程(即路由区更新流程)；
UE通过UTRAN发送RAU Request(路由区更新请求)消息给服务GPRS 支持节点SGSN，如果“UE支持承载数量扩展指示”为0，则表示UE不支持承载数量扩展；如果“UE支持承载数量扩展指示”为1，则表示UE支持承载数量扩展；
SGSN发送一个上下文请求(Context Request)消息给MME得到用户信息。
MME返回一个上下文请求响应(Context Response)消息，消息中携带IMSI、五元鉴权组、承载上下文，S-GW信令地址和TEID等
SGSN根据Context Response中的承载上下文信息以及自身能力，判断是否释放部分承载；
如果承载上下文中的承载数量超过8，则SGSN释放部分承载，如优先保证话音等高优先级业务对应的承载，优先释放低优先级业务的承载，如果承载上下文中的承载数量没有超过8，则继续后续RAU流程(参考TS 23.401的5.3.3.3节中的相关介绍)
应当了解的是，图6和图7仅仅是源网络和目标网络类型的差异，但都是由目标网络侧网元进行判决和执行。
实现方式五
UE在空闲态移动过程中，源MME根据UE context和目标MME的能力判断能否接受所有的承载，不能的话，释放部分承载；
UE在跟踪区更新(Tracking Area Update，TAU)请求消息的用户设备网络能力(UE Network Capability)信息元素中搭载1bit指示信息，用于指示“UE支持承载数量扩展”的信息。其中“0”表示不支持，“1”表示支持。
对应的承载管理流程如图8所示，包括如下步骤：
UE选择一个TA的E-UTRAN小区，该小区不在UE注册网络的TAI列表中，从而触发TAU过程；
UE通过3GPP接入，发送TAU Request消息给目标MME，如果“UE支持承载数量扩展指示”为0，则表示UE不支持承载数量扩展；如果“UE支持承载数量扩展指示”为1，则表示UE支持承载数量扩展；
目标MME发送一个上下文请求(Context Request)消息给源MME，请 求得到用户信息，其中携带目标MME是否支持承载数量扩展的指示信息；
源MME根据UE Context的信息，判断是否释放部分承载；
其中，如果目标MME不支持承载数量扩展，且源MME支持承载数量扩展且当前承载数量超过了8个，则源MME根据承载的QoS参数，如QCI和ARP等判断承载的优先级来释放部分承载(如优先保证话音等高优先级业务对应的承载，优先释放低优先级业务的承载)；
如果目标MME支持承载数量扩展，则返回一个上下文请求响应信息(Context Response)，消息中携带IMSI、五元鉴权组、承载上下文，S-GW信令地址和TEID等；
目标MME通过3GPP接入，发送TAU接受消息给UE，其中携带指示信息，如果目标MME支持承载数量的扩展，则在TAU Accept信息中利用1个bit位指示信息指示“网络支持EPS承载数扩展”。
实现方式六
UE在空闲态移动过程中，源侧MME根据UE context和SGSN的能力判断能否接受所有的承载，不能的话，释放部分承载；
UE在RAU过程中在RAU请求消息的UE Network Capability中搭载1bit的用于指示“UE支持承载数量扩展”的信息。其中“0”表示不支持，“1”表示支持。
对应的承载管理流程如图9所示，包括如下步骤：
UE选择一个UTRAN小区，该小区不在UE注册网络的TAI列表中，从而触发RAU过程；
UE通过UTRAN发送RAU Request消息给SGSN，如果“UE支持承载数量扩展指示”为0，则表示UE不支持承载数量扩展；如果“UE支持承载数量扩展指示”为1，则表示UE支持承载数量扩展；
SGSN发送一个上下文请求(Context Request)消息给MME，请求得到用户信息；
MME根据UE Context的信息，判断是否释放部分承载；
其中，如果当前承载数量超过了8个，则MME根据承载的QoS参数， 如QCI和ARP等判断承载的优先级来释放部分承载(如优先保证话音等高优先级业务对应的承载，优先释放低优先级业务的承载)；
如果当前承载数量小于8个，则返回一个上下文请求响应信息(Context Response)，消息中携带IMSI、五元鉴权组、承载上下文，S-GW信令地址和TEID等；
SGSN发送RAU接受消息给UE。
实现方式七
切换过程，目标MME根据源MME传来的用户上下文信息中的判断能否接受所有的承载，不能的话，释放部分承载；
对应的承载管理流程如图10所示，包括如下步骤：
UE处于连接态，源eNodeB决定通过S1接口发起切换过程，则发送切换请求消息给源MME；
源MME选择一个目标MME，并向目标MME发送前向重定位请求消息Forward Relocation Request(包括UE的上下文)；其中UE的上下文包括IMSI、UE安全上下文、UE网络能力、AMBR及承载上下文等；
目标MME根据UE的承载上下文以及自身能力判定是否释放部分承载；
如果目标MME不支持承载的扩展且当前承载数超过了8，则目标MME根据承载的QoS参数，如QCI和ARP等判断承载的优先级来释放部分承载(如优先保证话音等高优先级业务对应的承载，优先释放低优先级业务的承载)后执行常规切换过程(参考3GPP TS23.401)，否则直接进行常规切换过程。
UE发起TAU流程，可参考图6、图8及其相应描述。
实现方式八
切换过程，目标侧SGSN根据源侧MME发送的UE context判断能否接受所有的承载，不能的话，释放部分承载；
对应的承载管理流程如图11所示，包括如下步骤：
UE处于连接态，源eNodeB决定将UE切换到UTRAN Iu模式并发起切换流程；
源eNodeB发送切换请求消息给源MME；
源MME选择一个目标SGSN，并向目标SGSN发送前向重定位请求消息Forward Relocation Request(包括UE的上下文)；其中UE的上下文包括IMSI、UE安全上下文、UE网络能力、AMBR及承载上下文等；
目标SGSN根据UE的承载上下文以及自身能力判定是否释放部分承载；
如果当前承载数超过了8，则目标SGSN根据承载的QoS参数，如QCI和ARP等判断承载的优先级来释放部分承载(如优先保证话音等高优先级业务对应的承载，优先释放低优先级业务的承载)后执行常规切换过程(参考3GPP TS23.401)，如果当前承载数小于8，则直接进行常规切换过程。
UE发起TAU流程，可参考图6、图8及其相应描述。
实现方式九
切换过程，源侧MME根据UE context和目标MME的能力判断能否接受所有的bearer，不能的话，释放部分承载；
对应的承载管理流程如图12所示，包括如下步骤：
UE处于连接态，源eNodeB决定通过S1接口发起切换过程；
源eNodeB发送切换请求消息给源MME；
源MME选择一个目标MME，源MME根据UE Context信息以及目标MME能力，判定是否释放部分承载；
如果目标MME不支持承载数量扩展，但UE context中指示UE支撑承载扩展且当前承载数量超过了8，则源MME根据承载的QoS参数，如QCI和ARP等判断承载的优先级来释放部分承载(如优先保证话音等高优先级业务对应的承载，优先释放低优先级业务的承载)后继续常规切换过程，否则直接继续后续常规切换过程。
后续常规切换过程中，源MME向目标MME发送前向重定位请求消息，同时UE会执行TAU流程，请参考之前TAU流程的描述，在此不再赘述。
实现方式十
切换过程，源侧MME根据UE context和目标侧SGSN的能力判断能否接受所有的承载，不能的话，释放部分承载；
对应的承载管理流程如图13所示，包括如下步骤：
UE处于连接态，源eNodeB决定将UE切换到UTRAN Iu模式并发起切换流程；
源eNodeB发送切换请求消息给源MME，请求核心网在目标RNC、SGSN和S-GW建立资源；
源MME根据UE Context信息以及目标SGSN的能力，判定是否释放部分承载；
如果当前承载数超过8，源MME根据承载的QoS参数，如QCI和ARP等判断承载的优先级来释放部分承载(如优先保证话音等高优先级业务对应的承载，优先释放低优先级业务的承载)后继续常规切换流程，否则直接继续常规切换流程。
实现方式十一
在UE建立承载时，MME判断UE的承载数是否超过了最大限制；
对应的承载管理方法，包括如下步骤：
UE通过3GPP接入，向MME发送承载资源分配请求(BEARER RESOURCE ALLOCATION REQUEST)或承载资源修改请求消息(BEARER RESOURCE MODIFICATION REQUEST)；
MME验证EPS承载标识，UE上下文，检查是否可以为UE建立承载资源(如UE承载数量是否超过最大承载数量)；
如果网络接受承载资源分配请求，MME发起常规的专用EPS承载上下文激活过程或者EPS承载上下文修改过程；
如果网络没有接受承载资源分配请求，MME发送拒绝消息给UE，拒绝信息中应包含ESM值(如65，表明已达最大承载数量)。
此外，本公开的另一实施例还提供一种承载管理装置用于网络侧网元和移动通信终端中的一个，如图14所示，该承载管理装置包括：
发送模块141，用于向网络侧网元和移动通信终端中的另一个发送指示信息，该指示信息用于指示是否支持承载数量扩展。
显然，本公开具体实施例的承载管理装置是本公开提供的承载管理方法 的执行主体，因此该承载管理方法所能实现的技术效果，本公开的承载管理装置同样能够实现。
可选地，当述承载管理设装置为移动通信终端时，本公开具体实施例的发送模块141具体用于：
向网络侧网元发送携带指示信息的用户设备网络能力信息元素，该指示信息用于指示移动通信终端是否支持承载数量扩展。
可选地，发送模块141具体用于：
向网络侧网元发送一请求消息，该请求消息中携带第一指示信息，该第一指示信息用于指示移动通信终端是否支持承载数量扩展；该请求消息为附着请求消息或跟踪区更新请求消息；
或
向移动通信终端发送一接受消息，该接受消息中携带第二指示信息，该第二指示信息用于指示网络侧网元是否支持承载数量扩展，该接受消息为附着接受消息或跟踪区更新接受消息。
此外，本公开的另一实施例还提供一种承载管理装置，用于网络侧网元和移动通信终端中的一个，如图15所示，所述承载管理装置包括：
接收模块151，用于接收网络侧网元和移动通信终端中的另一个发送的指示信息，所述指示信息用于指示是否支持承载数量扩展。
显然，本公开具体实施例的承载管理装置是本公开提供的承载管理方法的执行主体，因此该承载管理方法所能实现的技术效果，本公开的承载管理装置同样能够实现。
可选地，本公开具体实施例的接收模块151具体用于：
接收移动通信终端发送的携带指示信息的用户设备网络能力信息元素，该指示信息用于指示移动通信终端是否支持承载数量扩展。
可选地，本公开具体实施例的述接收模块151具体用于：
接收移动通信终端发送的请求消息，该请求消息中携带第一指示信息，该第一指示信息用于指示移动通信终端是否支持承载数量扩展；该请求消息为附着请求消息或跟踪区更新请求消息；
或
接收所述网络侧网元发送的接受消息，该接受消息中携带第二指示信息，该第二指示信息用于指示网络侧网元是否支持承载数量扩展，该接受消息为附着接受消息或跟踪区更新接受消息。
此外，本公开的另一实施例还提供一种承载管理装置，用于网络侧执行网元，如图16所示，所述承载管理装置包括：
释放模块161，用于当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载，保留的承载的数量小于或等于所述预定门限。
显然，本公开具体实施例的承载管理装置是本公开提供的应用于网络侧执行网元的承载管理方法的执行主体，因此该承载管理方法所能实现的技术效果，本公开的承载管理装置同样能够实现。
可选地，本公开具体实施例的释放模块161具体用于：
当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，按照所述待迁移承载的优先级从低到高的顺序释放部分承载。
可选地，所述网络侧执行网元为空闲态移动流程或切换流程中的目标网络侧网元。
其中，若网络侧执行网元为空闲态移动流程或切换流程中的目标网络侧网元，则还包括：
第一获取模块，用于获取源网络侧网元的承载上下文信息。
释放模块具体用于：
当根据所述承载上下文信息以及所述目标网络侧网元的承载数量扩展支持能力判断出所述待迁移承载的数量大于预定门限，且所述目标网络侧网元不支持承载数量扩展时，释放部分承载。
其中一种方式下第一获取模块具体用于：
向源网络侧网元发送第一上下文请求消息；
接收源网络侧网元发送的携带承载上下文信息第一上下文请求响应消息；
而当网络侧执行网元为空闲态移动流程或切换流程中的源网络侧网元，则还包括：
第二获取模块，用于获取一指示信息，所述指示信息用于指示所述目标网络侧网元是否支持承载数量扩展。
释放模块具体用于：当根据所述指示信息以及所述待迁移承载的数量判断出所述待迁移承载的数量大于预定门限，且所述目标网络侧网元不支持承载数量扩展时，释放部分承载。
对应地，在上述基础之上，如图16所示，本示例的承载管理装置还包括：
响应模块162，用于在释放部分承载之后，发送携带承载上下文的消息到目标网络侧网元。
此外，本公开的实施例还提供一种承载管理装置，如图17所示，包括：天线171、射频装置172、基带装置173、处理器174、存储器175、网络接口176以及总线接口。其中：
在本公开实施例中，承载管理装置还包括：存储在存储器175上并可在处理器174上运行的计算机程序，计算机程序被处理器174执行时实现如下步骤：
向网络侧网元和移动通信终端中的另一个发送指示信息，所述指示信息用于指示是否支持承载数量扩展。
和/或，
当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载，保留的承载的数量小于或等于所述预定门限。
和/或，
向所述源网络侧网元发送第一上下文请求消息；
接收所述源网络侧网元发送的第一上下文请求响应消息；
所述当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时具体为：
当根据第一上下文请求响应消息中携带的承载上下文信息以及所述目标 网络侧网元的承载数量扩展支持能力判断出所述待迁移承载的数量大于预定门限，且所述目标网络侧网元不支持承载数量扩展时，释放部分承载。
其中，总线接口可以包括任意数量的互联的总线和桥，具体由处理器代表的一个或多个处理器和存储器175代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。天线171、射频装置172、基带装置173共同组成发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元。针对不同的用户设备，用户接口176还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器174负责管理总线接口和通常的处理，存储器175可以存储处理器174在执行操作时所使用的数据。
可选地，本公开具体实施例计算机程序被处理器174执行时还实现如下步骤：
向网络侧网元发送携带所述指示信息的用户设备网络能力信息元素，所述指示信息用于指示所述移动通信终端是否支持承载数量扩展。
可选地，所述指示信息由用户设备网络能力信息元素的第9个八比特组中的第6、第7或第8个bit或第10个到第15个八比特组中的任意一个bit定义。
可选地，本公开具体实施例计算机程序被处理器174执行时还实现如下步骤：
向所述网络侧网元发送一请求消息，所述请求消息中携带第一指示信息，所述第一指示信息用于指示所述移动通信终端是否支持承载数量扩展；所述请求消息为附着请求消息或跟踪区更新请求消息；
或
向移动通信终端发送一接受消息，所述接受消息中携带第二指示信息，所述第二指示信息用于指示所述网络侧网元是否支持承载数量扩展，所述接受消息为附着接受消息或跟踪区更新接受消息。
可选地，若承载管理方法用于网络侧网元时，本公开具体实施例计算机 程序被处理器174执行时还实现如下步骤：
接收所述移动通信终端发送的携带所述指示信息的用户设备网络能力信息元素，所述指示信息用于指示所述移动通信终端是否支持承载数量扩展。
可选地，本公开具体实施例计算机程序被处理器174执行时还实现如下步骤：
接收所述移动通信终端发送的请求消息，所述请求消息中携带第一指示信息，所述第一指示信息用于指示所述移动通信终端是否支持承载数量扩展；所述请求消息为附着请求消息或跟踪区更新请求消息；
或
接收所述网络侧网元发送的接受消息，所述接受消息中携带第二指示信息，所述第二指示信息用于指示所述网络侧网元是否支持承载数量扩展，所述接受消息为附着接受消息或跟踪区更新接受消息。
可选地，所述承载管理方法用于网络侧网元时，所述承载管理方法用于网络侧网元时，本公开具体实施例计算机程序被处理器174执行时还实现如下步骤：
接收所述移动通信终端发送的指示信息，所述指示信息用于指示是否支持承载数量扩展；
所述承载管理方法还包括：
接收所述移动通信终端发送的承载资源分配请求或承载资源修改请求；
在根据所述指示信息判断出所述移动通信终端不支持承载数量扩展，且所述移动通信终端已建立承载的数量达到预定门限时，拒绝所述承载资源分配请求或承载资源修改请求。
可选地，本公开具体实施例计算机程序被处理器174执行时还实现如下步骤：
当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，按照所述待迁移承载的优先级从低到高的顺序释放部分承载。
可选地，所述网络侧执行网元为空闲态移动流程或切换流程中的源网络 侧网元或目标网络侧网元；
若所述网络侧执行网元为目标网络侧网元，则在释放部分承载之前，本公开具体实施例计算机程序被处理器174执行时还实现如下步骤：
向所述源网络侧网元发送第一上下文请求消息；
接收所述源网络侧网元发送的第一上下文请求响应消息；
所述当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时具体为：
当根据第一上下文请求响应消息中携带的承载上下文信息以及所述目标网络侧网元的承载数量扩展支持能力判断出所述待迁移承载的数量大于预定门限，且所述目标网络侧网元不支持承载数量扩展时，释放部分承载。
若所述网络侧执行网元为源网络侧网元，则在释放部分承载之前，本公开具体实施例计算机程序被处理器174执行时还实现如下步骤：
接收所述目标网络侧网元发送携带指示信息的第二上下文请求消息，所述指示信息用于指示所述目标网络侧网元是否支持承载数量扩展；
所述当归属于同一移动通信终端的、待迁移到目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载具体为：
当根据所述指示信息以及所述待迁移承载的数量判断出所述待迁移承载的数量大于预定门限，且所述目标网络侧网元不支持承载数量扩展时，释放部分承载；
所述释放部分承载之后，所述承载管理方法还包括：
发送携带承载上下文的第二上下文请求响应消息到所述目标网络侧网元。
此外，本公开的另一实施例还提供一种计算机可读存储介质，其上存储有计算机程序，计算机程序被处理器执行时实现以下步骤：
向网络侧网元和移动通信终端中的另一个发送指示信息，所述指示信息用于指示是否支持承载数量扩展。
和/或，
当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载，保留的承载 的数量小于或等于所述预定门限。
和/或，
向所述源网络侧网元发送第一上下文请求消息；
接收所述源网络侧网元发送的第一上下文请求响应消息；
所述当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时具体为：
当根据第一上下文请求响应消息中携带的承载上下文信息以及所述目标网络侧网元的承载数量扩展支持能力判断出所述待迁移承载的数量大于预定门限，且所述目标网络侧网元不支持承载数量扩展时，释放部分承载。
可选地，本公开具体实施例的计算机程序被处理器执行时还实现以下步骤：
向网络侧网元发送携带所述指示信息的用户设备网络能力信息元素，所述指示信息用于指示所述移动通信终端是否支持承载数量扩展。
可选地，述指示信息由用户设备网络能力信息元素的第9个八比特组中的第6、第7或第8个bit或第10个到第15个八比特组中的任意一个bit定义。
可选地，本公开具体实施例的计算机程序被处理器执行时还实现以下步骤：
向所述网络侧网元发送一请求消息，所述请求消息中携带第一指示信息，所述第一指示信息用于指示所述移动通信终端是否支持承载数量扩展；所述请求消息为附着请求消息或跟踪区更新请求消息；
或
向移动通信终端发送一接受消息，所述接受消息中携带第二指示信息，所述第二指示信息用于指示所述网络侧网元是否支持承载数量扩展，所述接受消息为附着接受消息或跟踪区更新接受消息。
可选地，若承载管理方法用于网络侧网元时，本公开具体实施例的计算机程序被处理器执行时还实现以下步骤：
接收所述移动通信终端发送的携带所述指示信息的用户设备网络能力信 息元素，所述指示信息用于指示所述移动通信终端是否支持承载数量扩展。
可选地，本公开具体实施例的计算机程序被处理器执行时还实现以下步骤：
接收所述移动通信终端发送的请求消息，所述请求消息中携带第一指示信息，所述第一指示信息用于指示所述移动通信终端是否支持承载数量扩展；所述请求消息为附着请求消息或跟踪区更新请求消息；
或
接收所述网络侧网元发送的接受消息，所述接受消息中携带第二指示信息，所述第二指示信息用于指示所述网络侧网元是否支持承载数量扩展，所述接受消息为附着接受消息或跟踪区更新接受消息。
可选地，所述承载管理方法用于网络侧网元时，本公开具体实施例的计算机程序被处理器执行时还实现以下步骤：
接收所述移动通信终端发送的指示信息，所述指示信息用于指示是否支持承载数量扩展；
所述承载管理方法还包括：
接收所述移动通信终端发送的承载资源分配请求或承载资源修改请求；
在根据所述指示信息判断出所述移动通信终端不支持承载数量扩展，且所述移动通信终端已建立承载的数量达到预定门限时，拒绝所述承载资源分配请求或承载资源修改请求。
可选地，本公开具体实施例的计算机程序被处理器执行时还实现以下步骤：
当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，按照所述待迁移承载的优先级从低到高的顺序释放部分承载。
可选地，所述网络侧执行网元为空闲态移动流程或切换流程中的源网络侧网元或目标网络侧网元；
若所述网络侧执行网元为目标网络侧网元，则本公开具体实施例的计算机程序被处理器执行时还实现以下步骤：
获取源网络侧网元的承载上下文信息；
所述当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时具体为：
当根据承载上下文信息以及所述目标网络侧网元的承载数量扩展支持能力判断出所述待迁移承载的数量大于预定门限，且所述目标网络侧网元不支持承载数量扩展时，释放部分承载。
若所述网络侧执行网元为源网络侧网元，则在释放部分承载之前，本公开具体实施例的计算机程序被处理器执行时还实现以下步骤：
获取一指示信息，所述指示信息用于指示所述目标网络侧网元是否支持承载数量扩展；；
所述当归属于同一移动通信终端的、待迁移到目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载具体为：
当根据所述指示信息以及所述待迁移承载的数量判断出所述待迁移承载的数量大于预定门限，且所述目标网络侧网元不支持承载数量扩展时，释放部分承载；
所述释放部分承载之后，所述承载管理方法还包括：
发送携带承载上下文的第二上下文请求响应消息到所述目标网络侧网元。
以上所述是本公开的可选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本公开所述原理的前提下，还可以作出若干改进和润饰，这些改进和润饰也应视为本公开的保护范围。

Claims (25)

  1. 一种承载管理方法，用于网络侧网元和移动通信终端中的一个，所述承载管理方法包括：
    向网络侧网元和移动通信终端中的另一个发送指示信息，所述指示信息用于指示是否支持承载数量扩展。
  2. 根据权利要求1所述的承载管理方法，其中，所述承载管理用于移动通信终端时，所述向网络侧网元或移动通信终端中的另一个发送指示信息，所述指示信息用于指示是否支持承载数量扩展具体为：
    向网络侧网元发送携带所述指示信息的用户设备网络能力信息元素，所述指示信息用于指示所述移动通信终端是否支持承载数量扩展。
  3. 根据权利要求2所述的承载管理方法，其中，所述指示信息由用户设备网络能力信息元素的第9个八比特组中的第6、第7或第8个bit或第10个到第15个八比特组中的任意一个bit定义。
  4. 根据权利要求1所述的承载管理方法，其中，所述向网络侧网元或移动通信终端中的另一个发送指示信息具体为：
    向所述网络侧网元发送一请求消息，所述请求消息中携带第一指示信息，所述第一指示信息用于指示所述移动通信终端是否支持承载数量扩展；所述请求消息为附着请求消息或跟踪区更新请求消息；
    或
    向移动通信终端发送一接受消息，所述接受消息中携带第二指示信息，所述第二指示信息用于指示所述网络侧网元是否支持承载数量扩展，所述接受消息为附着接受消息或跟踪区更新接受消息。
  5. 一种承载管理方法，用于网络侧网元和移动通信终端中的一个，所述承载管理方法包括：
    接收网络侧网元和移动通信终端中的另一个发送的指示信息，所述指示信息用于指示是否支持承载数量扩展。
  6. 根据权利要求5所述的承载管理方法，其中，所述承载管理方法用于网络侧网元时，所述接收网络侧网元和移动通信终端中的另一个发送的指示 信息，所述指示信息用于指示是否支持承载数量扩展具体为：
    接收所述移动通信终端发送的携带所述指示信息的用户设备网络能力信息元素，所述指示信息用于指示所述移动通信终端是否支持承载数量扩展。
  7. 根据权利要求6所述的承载管理方法，其中，所述指示信息由用户设备网络能力信息元素的第9个八比特组中的第6、第7或第8个bit或第10个到第15个八比特组中的任意一个bit定义。
  8. 根据权利要求5所述的承载管理方法，其中，所述接收网络侧网元和移动通信终端中的另一个发送的指示信息，所述指示信息用于指示是否支持承载数量扩展具体为：
    接收所述移动通信终端发送的请求消息，所述请求消息中携带第一指示信息，所述第一指示信息用于指示所述移动通信终端是否支持承载数量扩展；所述请求消息为附着请求消息或跟踪区更新请求消息；
    或，
    接收所述网络侧网元发送的接受消息，所述接受消息中携带第二指示信息，所述第二指示信息用于指示所述网络侧网元是否支持承载数量扩展，所述接受消息为附着接受消息或跟踪区更新接受消息。
  9. 根据权利要求5所述的承载管理方法，其中，所述承载管理方法用于网络侧网元时，所述接收网络侧网元和移动通信终端中的另一个发送的指示信息，所述指示信息用于指示是否支持承载数量扩展具体为：
    接收所述移动通信终端发送的指示信息，所述指示信息用于指示是否支持承载数量扩展；
    所述承载管理方法还包括：
    接收所述移动通信终端发送的承载资源分配请求或承载资源修改请求；
    在根据所述指示信息判断出所述移动通信终端不支持承载数量扩展，且所述移动通信终端已建立承载的数量达到预定门限时，拒绝所述承载资源分配请求或承载资源修改请求。
  10. 一种承载管理方法，用于网络侧执行网元，所述承载管理方法包括：
    当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载，保留的承载 的数量小于或等于所述预定门限。
  11. 根据权利要求10所述的承载管理方法，其中，所述当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载具体为：
    当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，按照所述待迁移承载的优先级从低到高的顺序释放部分承载。
  12. 根据权利要求11所述的承载管理方法，其中，所述网络侧执行网元为空闲态移动流程或切换流程中的源网络侧网元或目标网络侧网元。
  13. 根据权利要求12所述的承载管理方法，其中，所述网络侧执行网元为目标网络侧网元，在释放部分承载之前，所述承载管理方法还包括：
    获取源网络侧网元的承载上下文信息；
    所述当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载具体为：
    当根据所述承载上下文信息以及所述目标网络侧网元的承载数量扩展支持能力判断出所述待迁移承载的数量大于预定门限，且所述目标网络侧网元不支持承载数量扩展时，释放部分承载。
  14. 根据权利要求12所述的承载管理方法，其中，所述网络侧执行网元为源网络侧网元，在释放部分承载之前，所述承载管理方法还包括：
    获取一指示信息，所述指示信息用于指示所述目标网络侧网元是否支持承载数量扩展；
    所述当归属于同一移动通信终端的、待迁移到目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载具体为：
    当根据所述指示信息以及所述待迁移承载的数量判断出所述待迁移承载的数量大于预定门限，且所述目标网络侧网元不支持承载数量扩展时，释放部分承载；
    所述释放部分承载之后，所述承载管理方法还包括：
    发送携带承载上下文的第二上下文请求响应消息到所述目标网络侧网元。
  15. 一种承载管理装置，用于网络侧网元和移动通信终端中的一个，所 述承载管理装置包括：
    发送模块，用于向网络侧网元和移动通信终端中的另一个发送指示信息，所述指示信息用于指示是否支持承载数量扩展。
  16. 根据权利要求15所述的承载管理装置，其中，所述承载管理设装置为移动通信终端时，所述发送模块具体用于：
    向网络侧网元发送携带所述指示信息的用户设备网络能力信息元素，所述指示信息用于指示所述移动通信终端是否支持承载数量扩展。
  17. 根据权利要求15所述的承载管理装置，其中，所述发送模块具体用于：
    向所述网络侧网元发送一请求消息，所述请求消息中携带第一指示信息，所述第一指示信息用于指示所述移动通信终端是否支持承载数量扩展；所述请求消息为附着请求消息或跟踪区更新请求消息；
    或，
    向移动通信终端发送一接受消息，所述接受消息中携带第二指示信息，所述第二指示信息用于指示所述网络侧网元是否支持承载数量扩展，所述接受消息为附着接受消息或跟踪区更新接受消息。
  18. 一种承载管理装置，用于网络侧网元和移动通信终端中的一个，所述承载管理装置包括：
    接收模块，用于接收网络侧网元和移动通信终端中的另一个发送的指示信息，所述指示信息用于指示是否支持承载数量扩展。
  19. 根据权利要求18所述的承载管理装置，其中，所述接收模块具体用于：
    接收所述移动通信终端发送的携带所述指示信息的用户设备网络能力信息元素，所述指示信息用于指示所述移动通信终端是否支持承载数量扩展。
  20. 根据权利要求18所述的承载管理装置，其中，所述接收模块具体用于：
    接收所述移动通信终端发送的请求消息，所述请求消息中携带第一指示信息，所述第一指示信息用于指示所述移动通信终端是否支持承载数量扩展；所述请求消息为附着请求消息或跟踪区更新请求消息；
    或，
    接收所述网络侧网元发送的接受消息，所述接受消息中携带第二指示信息，所述第二指示信息用于指示所述网络侧网元是否支持承载数量扩展，所述接受消息为附着接受消息或跟踪区更新接受消息。
  21. 一种承载管理装置，用于网络侧执行网元，所述承载管理装置包括：
    释放模块，用于当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，释放部分承载，保留的承载的数量小于或等于所述预定门限。
  22. 根据权利要求21所述的承载管理装置，其中，所述释放模块具体用于：当归属于同一移动通信终端的、待迁移到不支持承载数量扩展的目标网络侧网元的待迁移承载的数量大于预定门限时，按照所述待迁移承载的优先级从低到高的顺序释放部分承载。
  23. 根据权利要求22所述的承载管理装置，其中，所述网络侧执行网元为空闲态移动流程或切换流程中的目标网络侧网元。
  24. 一种承载管理装置，包括：处理器、存储器以及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述计算机程序被处理器执行时实现如权利要求1-4中任一项所述的承载管理方法中的步骤，或5-9中任一项所述的承载管理方法中的步骤，或10-14中任一项所述的承载管理方法中的步骤。
  25. 一种计算机可读存储介质，其上存储有计算机程序，其中，所述计算机程序被处理器执行时实现如权利要求1-4中任一项所述的承载管理方法中的步骤，或实现如权利要求5-9中任一项所述的承载管理方法的步骤，或实现如权利要求10-14中任一项所述的承载管理方法的步骤。
PCT/CN2019/070827 2018-01-10 2019-01-08 承载管理方法及承载管理装置 WO2019137367A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810023628.1 2018-01-10
CN201810023628.1A CN110022587B (zh) 2018-01-10 2018-01-10 一种承载管理方法及承载管理装置

Publications (1)

Publication Number Publication Date
WO2019137367A1 true WO2019137367A1 (zh) 2019-07-18

Family

ID=67188093

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/070827 WO2019137367A1 (zh) 2018-01-10 2019-01-08 承载管理方法及承载管理装置

Country Status (2)

Country Link
CN (1) CN110022587B (zh)
WO (1) WO2019137367A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021218715A1 (zh) * 2020-04-30 2021-11-04 华为技术有限公司 网络资源管理的方法、系统及相关装置

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112449400B (zh) * 2019-08-15 2022-03-29 大唐移动通信设备有限公司 一种通信方法、装置及系统
EP3883298B1 (en) 2019-09-23 2023-11-29 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Method and apparatus for system interoperation
WO2021237395A1 (en) * 2020-05-25 2021-12-02 Qualcomm Incorporated Triggering an attach procedure after disablement of dual connectivity with new radio mode

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104641682A (zh) * 2011-10-28 2015-05-20 黑莓有限公司 在电路交换回退操作期间处理承载的方法和装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3202212B1 (en) * 2014-09-29 2022-03-02 Nokia Solutions and Networks Oy Local breakout in small cell architecture
CN107257553B (zh) * 2017-05-04 2020-10-09 上海华为技术有限公司 用户面链路建立方法、基站及移动性管理设备

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104641682A (zh) * 2011-10-28 2015-05-20 黑莓有限公司 在电路交换回退操作期间处理承载的方法和装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SAMSUNG ET AL.: "Further considerations on extended number of dedicated rad bearers for E-UTRAN", 3GPP TSG RAN WG2 #100 R2-1712198, 1 December 2017 (2017-12-01), XP051372575 *
SAMSUNG ET AL.: "Motivation for WI on increased number of E-UTRAN bearers", 3GPP TSG-RAN #78 RP-172251, 21 December 2017 (2017-12-21), XP051364939 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021218715A1 (zh) * 2020-04-30 2021-11-04 华为技术有限公司 网络资源管理的方法、系统及相关装置

Also Published As

Publication number Publication date
CN110022587B (zh) 2021-01-08
CN110022587A (zh) 2019-07-16

Similar Documents

Publication Publication Date Title
US11197216B2 (en) Handling of collision between SR procedure and PDU session establishment procedure for PDU session handover
US10972945B2 (en) Method for handover between secondary base stations, network device, and user equipment
JP6696580B2 (ja) データ伝送のための制御プレーンおよびユーザプレーンの選択
WO2019137367A1 (zh) 承载管理方法及承载管理装置
US11129054B2 (en) Methods, systems and devices for supporting local breakout in small cell architecture
US10779357B2 (en) Method for avoiding handover failure
US11582656B2 (en) 5GSM handling on invalid PDU session
KR20200024363A (ko) 데이터 흐름을 운영하고 제어하는 방법 및 디바이스
US9572039B2 (en) Mobile communication system, control apparatus, communication control method, and non-transitory computer readable medium
WO2019076306A1 (zh) 数据传输通道的处理方法、装置和系统
CN110167142B (zh) 无线资源控制rrc连接方法、重连接方法和装置
US11856413B2 (en) Coverage enhancement CE function implementation method and device
WO2009111931A1 (zh) 基于切换的承载建立方法及系统
WO2014005536A1 (zh) 临近终端的通信方法及装置、系统
CN113079586B (zh) 处理多址协议数据单元会话切换的方法及其用户设备
KR102484223B1 (ko) Pdu 세션 활성화 방법, 페이징 방법 및 그의 장치
CN112637963B (zh) 多址接入协议数据单元会话释放的方法及其用户设备
EP3445081A1 (en) Flow-based bearer management method, and data transmission method and device
US11246064B2 (en) PDN connection supports interworking to 5GS
US20220353941A1 (en) Ma pdu reactivation requested handling
TWI805328B (zh) 處理ma pdu會話釋放過程的衝突的方法及使用者設備
KR101449720B1 (ko) 베어러 설정 시간을 단축하기 위한 방법 및 장치
EP4240058A1 (en) Enhanced handling for session continuity
CN112400341B (zh) 处理多址协议数据单元会话的方法及其用户设备
WO2017128048A1 (zh) 通知方法、通知装置及系统

Legal Events

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

Ref document number: 19738777

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19738777

Country of ref document: EP

Kind code of ref document: A1