Special load release method and device, nonvolatile storage medium and electronic equipment

Abstract

The invention discloses a special load release method and device, a nonvolatile storage medium and electronic equipment. The method comprises the following steps: a mobility management entity receives dedicated load release information sent by an evolution type base station, and the dedicated load release information comprises a deactivated dedicated load of terminal equipment; judging whether a to-be-deactivated to-be-processed special load associated with the target call flow exists in the terminal equipment or not according to the special load release information; and under the condition that the judgment result is yes, deactivation indication information is sent to the terminal equipment through the evolution type base station until the judgment result is no, and the deactivation indication information is used for indicating the terminal equipment to perform deactivation processing on the to-be-processed special load indicated by the deactivation indication information. According to the method and the device, the technical problem in the prior art that a plurality of dedicated resources cannot be normally released due to the fact that an interface of a mobility management entity and an evolution type base station only supports and carries a single dedicated deactivation message is solved.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a dedicated carrier release method, device, non-volatile storage medium and electronic device. Background Art

[0002] The EPC (Evolved Packet Core) signaling plane is the core network signaling control plane, which handles the signaling interaction between users and the core network to ensure that users can smoothly access the network, communicate and exchange data.

[0003] The VoLTE (Voice over Long-Term Evolution) video call process includes the stages of establishing a connection, making a video call, and ending the call. During a video call, in order to ensure high-quality transmission of video and voice data, dedicated bearers need to be created for each.

[0004] When the call ends, the network will execute the corresponding process to release the dedicated bearer used for voice and video. However, the current SGW (Serving GateWay) and MME (Mobility Management Entity) S11 interface supports the simultaneous deletion of multiple dedicated bearers. The S1 interface of MME and ENODEB only supports carrying one dedicated bearer at the NAS layer (Non-AccessStratum). MME needs to adapt the multiple dedicated bearer release processes initiated by PGW (Packet Data Network Gateway) to ensure that the terminal can be notified to release multiple dedicated bearer resources normally. Otherwise, the high-priority QoS (Quality of Service) dedicated bearer cannot be established, affecting the subsequent video call process.

[0005] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0006] The embodiments of the present application provide a dedicated carrier release method, device, non-volatile storage medium and electronic device to at least solve the technical problem in the prior art that multiple dedicated carrier resources cannot be released normally because the interface between the mobility management entity and the evolved base station only supports carrying a single dedicated carrier deactivation message.

[0007] According to one aspect of an embodiment of the present application, a dedicated bearer release method is provided, including: a mobility management entity receives dedicated bearer release information sent by an evolved base station, wherein the dedicated bearer release information includes a dedicated bearer that has been deactivated by a terminal device; judging whether there is a pending dedicated bearer to be deactivated associated with a target call process in the terminal device based on the dedicated bearer release information; and if the judgment result is yes, sending a deactivation indication information to the terminal device through the evolved base station until the judgment result is no, wherein the deactivation indication information is used to instruct the terminal device to deactivate the pending dedicated bearer indicated by the deactivation indication information.

[0008] Optionally, the mobility management entity establishes and maintains dedicated bearer record information corresponding to the terminal device, wherein the dedicated bearer record information includes a dedicated bearer identifier, type information and service quality parameters of the dedicated bearer corresponding to the terminal device.

[0009] Optionally, judging whether there is a pending dedicated bearer to be deactivated and associated with the target call process in the terminal device based on the dedicated bearer release information includes: determining the deactivated processed dedicated bearer identifier corresponding to the dedicated bearer release information; deleting the processed dedicated bearer identifier in the dedicated bearer record information; judging that there is a pending dedicated bearer to be deactivated in the terminal device when it is judged that there is an undeleted dedicated bearer identifier in the dedicated bearer record information, and judging that there is no pending dedicated bearer to be deactivated in the terminal device when it is judged that there is no undeleted dedicated bearer identifier in the dedicated bearer record information.

[0010] Optionally, a deactivation indication message is sent to the terminal device through the evolved base station until the judgment result is no, and the dedicated bearer release method also includes: the mobility management entity sends a dedicated bearer success release message to the service gateway, wherein the dedicated bearer success release message is used to indicate that the dedicated bearers associated with the target call process in the terminal device have been deactivated; the service gateway forwards the dedicated bearer success release message to the packet data network gateway; the packet data network gateway sends a session process modification indication message to the policy and charging rules function module, wherein the session process modification indication message is used to indicate that the dedicated bearers associated with the target call process in the terminal device have been deactivated.

[0011] Optionally, the target call process includes a video call process of a long-term evolution voice bearer, wherein the dedicated bearer associated with the target call process in the terminal device includes an audio dedicated bearer for carrying an audio data stream and an image dedicated bearer for carrying an image data stream.

[0012] Optionally, sending the deactivation indication information to the terminal device through the evolved base station includes: sending the deactivation indication information to the terminal device through the evolved base station in a downlink non-access layer transmission manner.

[0013] According to another aspect of an embodiment of the present application, a dedicated carrier release method is also provided, including: an evolved base station receives deactivation indication information sent by a mobility management entity, wherein the deactivation indication information is used to instruct a terminal device to deactivate a pending dedicated carrier indicated by the deactivation indication information; sending the deactivation indication information to the terminal device; receiving response information sent by the terminal device, wherein the response information is used to indicate that the terminal device has deactivated the pending dedicated carrier indicated by the deactivation indication information; after receiving the response information, the evolved base station generates dedicated carrier release information corresponding to the response information, and sends the dedicated carrier release information corresponding to the response information to the mobility management entity.

[0014] According to another aspect of an embodiment of the present application, a dedicated bearer release device is also provided, which is applicable to a mobility management entity, and includes: a first processing module, used to receive dedicated bearer release information sent by an evolved base station, wherein the dedicated bearer release information includes a dedicated bearer that has been deactivated by the terminal device; a second processing module, used to determine whether there is a pending dedicated bearer to be deactivated associated with a target call process in the terminal device based on the dedicated bearer release information; a third processing module, used to send deactivation indication information to the terminal device through the evolved base station if the judgment result is yes, until the judgment result is no, wherein the deactivation indication information is used to instruct the terminal device to deactivate the pending dedicated bearer indicated by the deactivation indication information.

[0015] According to another aspect of an embodiment of the present application, a non-volatile storage medium is provided, in which a program is stored, wherein when the program is running, a device where the non-volatile storage medium is located is controlled to execute a load release method.

[0016] According to another aspect of an embodiment of the present application, there is further provided an electronic device, including: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the dedicated load release method is executed when the program is run.

[0017] According to another aspect of an embodiment of the present application, a computer program product is also provided, including a computer program, and when the computer program is executed by a processor, the dedicated load release method is implemented.

[0018] In the embodiment of the present application, a mobility management entity is used to receive dedicated bearer release information sent by an evolved base station, wherein the dedicated bearer release information includes the dedicated bearer that has been deactivated by the terminal device; based on the dedicated bearer release information, it is determined whether there is a pending dedicated bearer to be deactivated in the terminal device that is associated with the target call process; if the judgment result is yes, a deactivation indication information is sent to the terminal device through the evolved base station until the judgment result is no, wherein the deactivation indication information is used to instruct the terminal device to deactivate the pending dedicated bearer indicated by the deactivation indication information. In this way, the dedicated bearer information that needs to be released is maintained by MEE, and multiple dedicated bearer release information is extended, so as to achieve the purpose of notifying each bearer in multiple messages, thereby achieving the technical effect that ENODEB and the terminal can correctly release the bearer resources after the video call ends, thereby solving the technical problem in the prior art that multiple dedicated bearer resources cannot be released normally because the interface between the mobility management entity and the evolved base station only supports carrying a single dedicated bearer deactivation message. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0020] Figure 1 It is a schematic diagram of a conventional signaling interaction process according to the relevant technology;

[0021] Figure 2 It is a schematic diagram of a conventional signaling interaction process according to the relevant technology;

[0022] Figure 3 is a structural schematic diagram of a computer terminal provided according to an embodiment of the present application;

[0023] Figure 4 It is a flowchart of a dedicated load release method provided according to an embodiment of the present application;

[0024] Figure 5 is a schematic diagram of a dedicated load release process provided according to an embodiment of the present application;

[0025] Figure 6 It is a flowchart of a dedicated load release method provided according to an embodiment of the present application;

[0026] Figure 7 It is a structural schematic diagram of a special load release device provided according to an embodiment of the present invention. DETAILED DESCRIPTION

[0027] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0028] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0029] In order to better understand the embodiments of the present application, the technical terms involved in the embodiments of the present application are explained as follows:

[0030] VOLTE (Voice over Long-Term Evolution): Based on the IP Multimedia Subsystem (IMS) network, control plane and media plane bearers are established on the LTE network, realizing the transmission of voice services (control and media layers) as data streams in the LTE data bearer network.

[0031] EPC (Evolved Packet Core): The core part of the LTE network. It is responsible for processing mobile data traffic, including transmission, routing and switching of user data.

[0032] MME (Mobility Management Entity): Mainly responsible for processing signaling related to mobility management, including user authentication, mobility management, session management, security functions, etc.

[0033] SGW (Serving Gateway): Mainly responsible for forwarding and processing user data, as well as data path management in the process of mobility management, including data forwarding, mobility management, session management, etc.

[0034] PGW (Packet Data Network Gateway): Mainly responsible for providing user equipment with access to external data networks, while also assuming security control and billing functions for user data.

[0035] In the related art, the call process is as follows:

[0036] (I) The EPC signaling plane is the signaling control plane of the 4G core network, which handles the signaling interaction between users and the core network to ensure that users can smoothly access the network, communicate and exchange data.

[0037] After successfully attaching, the VoLTE user initiates the establishment of a PDN connection supporting IMS services and establishes a signaling bearer with a QCI (QoS Class Identifier) ​​of 5 for subsequent SIP (Session Initiation Protocol) signaling transmission.

[0038] When a UE (User Equipment) initiates a VoLTE video call, it first sends an INVITE request to the IMS through the SIP signaling bearer, which contains the called number and the media capability information of the video call. After receiving the INVITE request, the IMS parses the called number and makes routing decisions, and sends a paging message to the called UE through the EPC to notify it of the video call request. The called UE responds to the paging and returns an INVITE response message, which contains its media capability information.

[0039] The two UEs negotiate media capabilities to determine common parameters such as media codecs, resolution, etc. After the negotiation is successful, the two UEs establish a media connection (such as an RTP (Real-time Transport Protocol) / RTCP (Real-time Transport Control Protocol) connection) through the EPC to transmit video and audio data.

[0040] The establishment time of voice and video dedicated bearers is determined by the configuration of IMS. If the dedicated bearer is established after the ringing, it is early ringing; if the dedicated bearer is established before the ringing, it is late ringing.

[0041] PGW receives the RAR (Reauthorization Request) message from PCRF (Policy and Charging Rules Function) and initiates the dedicated bearer establishment process. PGW allocates necessary resources for the dedicated bearer, including IP address, TEID (Tunnel Endpoint Identifier), etc., which are used to establish a data channel between PGW and SGW and MME.

[0042] The PGW sends a Create Bearer Request message to the SGW, requesting to establish a dedicated bearer.

[0043] After receiving the message, the SGW performs necessary resource allocation and configuration, and sends a corresponding signaling message to the MME.

[0044] After receiving the Create Bearer Request message, the MME performs necessary resource allocation and configuration, including allocating EBI (bearer identifier), updating the user's bearer context information, and sending signaling messages to the ENODEB (evolved base station) and UE to notify them to establish a dedicated bearer and allocate corresponding wireless resources.

[0045] After ENODEB and UE reply with successful responses to MME respectively, MME sends a Create Bearer Respons message to SGW, SGW updates the corresponding information, sends a Create Bearer Respons message to PGW, PGW updates the corresponding information, and sends a CCR (Credit Control Request) to PCRF.

[0046] When all necessary signaling interactions and resource allocation are completed, the dedicated bearer is successfully established. At this point, service data flows can be efficiently and reliably transmitted between the PGW and the external data network through the dedicated bearer.

[0047] (ii) The calling user also needs to initiate a dedicated bearer establishment process, which is similar to the dedicated bearer establishment process of the called user. After the dedicated bearers of the calling and called user are successfully established, they can start transmitting video and audio data to realize a video call.

[0048] The VoLTE video call process includes stages such as connection establishment, video call and call ending. When making a video call, in order to ensure high-quality transmission of video and voice data, dedicated bearers need to be created for video and voice data respectively.

[0049] (III) When the calling or called party decides to end the call, it sends a BYE request (session termination request) to the IMS to terminate the session, and the network sends a request to release the bearer to the UE. After receiving the request, the UE will execute the corresponding process to release the dedicated bearer used by voice and video. This includes stopping the encoding and decoding of voice and video, releasing network resources, and performing signaling interaction with the network side to confirm the release of the bearer. Figure 1 and 2 shows part of the flow of conventional signaling interaction, such as Figure 1 and 2 As shown:

[0050] 1. PCRF initiates the IP-CAN Session Modification process and sends the QOS policy to PGW.

[0051] 2PGW sends a Delete Bearer Request to SGW, carrying at least one BearerContext, indicating the bearer information that needs to be released.

[0052] 3. The SGW sends a Delete Bearer Request to the MME, which carries an indication of whether to delete all bearers under the PDN connection, or carries the Bearer Context that needs to be released.

[0053] 4. The MME sends an E-RAB Release Command to the eNodeB, fills in the E-RAB To Be Released List according to the Bearer Context information, and constructs the NAS message Deactivate EPS Bearer Context Request.

[0054] 5. The eNodeB sends an RRC Connection Reconfiguration message to the UE, including the radio bearers to be released and the NAS bearer deactivation message.

[0055] 6. The UE releases the radio bearer and deactivates the bearer, and sends an RRC ConnectionReconfiguration Complete message to the eNodeB.

[0056] 7. The eNodeB sends an E-RAB Release Response (Evolved Radio Access Bearer Release Response) to the MME to notify the bearer release result.

[0057] 8. The MME sends a Delete Bearer Response to the SGW to notify the bearer release result.

[0058] 9.W sends a Delete Bearer Response to PGW to notify the bearer release result.

[0059] 10. Reply IP-CAN Session Modification to PCRF, indicating that the PCC policy was successfully executed.

[0060] After the video call ends, PGW initiates the dedicated bearer release process. When carrying multiple dedicated bearers such as voice and video, the bearer deletion request sent by SGW to MME carries multiple bearer contexts. However, the E-RAB release command (E-RAB RELEASE COMMAND) sent by MME to ENODEB can only carry one NAS PDU (Network Access Stratum Protocol Data Unit). Since NAS PDU can only carry one Deactivate EPS Bearer Context Request, the E-RAB Release Command cannot carry all NAS messages Deactivate EPS Bearer Context Request at once, and cannot indicate multiple deactivation bearer context requests, resulting in the terminal (UE) being unable to deactivate all bearer contexts, causing some bearer context resources to remain. If MME cannot notify the terminal to release all bearer resources, subsequent dedicated bearer creation will fail, affecting the video and voice call process and bringing a bad experience to VOLTE users.

[0061] In order to solve the above problems, relevant solutions are provided in the embodiments of the present application, which are described in detail below.

[0062] According to an embodiment of the present application, a method embodiment of a dedicated load release method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0063] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 3 FIG. 1 shows a hardware structure block diagram of a computer terminal (or mobile device) for implementing a dedicated load release method. Figure 3 As shown, the computer terminal 30 (or mobile device 30) may include one or more (302a, 302b, ..., 302n are used to illustrate) processors 302 (the processor 302 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 304 for storing data, and a transmission device 306 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 3 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 3 More or fewer components as shown, or with Figure 3 Different configurations are shown.

[0064] It should be noted that the one or more processors 302 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 30 (or mobile device). As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0065] The memory 304 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the dedicated load release method in the embodiment of the present application. The processor 302 executes various functional applications and data processing by running the software programs and modules stored in the memory 304, that is, realizing the above-mentioned dedicated load release method. The memory 304 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 304 may further include a memory remotely arranged relative to the processor 302, and these remote memories may be connected to the computer terminal 30 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0066] The transmission device 306 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 30. In one example, the transmission device 306 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 306 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0067] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 30 (or mobile device).

[0068] In the above operating environment, the embodiment of the present application provides a dedicated load release method, such as Figure 4 As shown, the method comprises the following steps:

[0069] Step S402: The mobility management entity receives dedicated bearer release information sent by the evolved base station, wherein the dedicated bearer release information includes the dedicated bearer that has been deactivated by the terminal equipment.

[0070] Optionally, Figure 1 It shows part of the process of conventional signaling interaction. Figure 5 A special load release process of this application is shown, such as Figure 1 and Figure 5 As shown, before the mobility management entity receives the dedicated bearer release information sent by the evolved base station, the method further includes:

[0071] 1. If dynamic PCC is not deployed, PCRF initiates the IP-CAN Session Modification process and sends the QOS policy to PGW.

[0072] 2. PGW sends a Delete Bearer Request to SGW, carrying at least one Bearer Context, indicating the dedicated bearer information that needs to be released.

[0073] 3. The SGW sends a Delete Bearer Request to the MME (i.e., mobility management entity), carrying an indication of whether to delete all dedicated bearers under the PDN connection, or carrying the Bearer Context that needs to be released.

[0074] 4. The MME sends an E-RAB Release Command to the eNodeB (i.e., evolved base station), fills in the E-RAB To Be Released List according to the BearerContext information, and constructs the NAS message Deactivate EPS BearerContext Request.

[0075] 5. The eNodeB sends an RRC Connection Reconfiguration message to the UE, including the dedicated wireless bearer to be released and the NAS dedicated bearer deactivation message.

[0076] 6. The UE releases the dedicated wireless bearer and deactivates the dedicated bearer, and sends an RRC ConnectionReconfiguration Complete message to the eNodeB.

[0077] 7. The eNodeB sends an E-RAB Release Response to the MME to notify the dedicated bearer release result (i.e., dedicated bearer release information).

[0078] That is, the mobility management entity maintains the dedicated bearer information that needs to be released according to the BearerContext carried in the Delete Bearer Request sent by the SGW. If multiple dedicated bearers need to be released, the Deactivate EPS Bearer Context Request message is filled in separately according to the maintained dedicated bearer information. For the first dedicated bearer, it is carried by the NAS PDU of the E-RAB ReleaseCommand to notify the evolved base station to release the dedicated bearer (step 4).

[0079] Step S404: determine whether there is a pending dedicated bearer to be deactivated in the terminal device that is associated with the target call flow according to the dedicated bearer release information.

[0080] In the technical solution provided in step S404, the mobility management entity establishes and maintains dedicated bearer record information corresponding to the terminal device, wherein the dedicated bearer record information includes a dedicated bearer identifier, type information and service quality parameters of the dedicated bearer corresponding to the terminal device.

[0081] In the technical solution provided in step S404, judging whether there is a pending dedicated bearer to be deactivated and associated with the target call process in the terminal device based on the dedicated bearer release information includes: determining the deactivated processed dedicated bearer identifier corresponding to the dedicated bearer release information; deleting the processed dedicated bearer identifier in the dedicated bearer record information; judging that there is a pending dedicated bearer to be deactivated in the terminal device when it is judged that there is an undeleted dedicated bearer identifier in the dedicated bearer record information; and judging that there is no pending dedicated bearer to be deactivated in the terminal device when it is judged that there is no undeleted dedicated bearer identifier in the dedicated bearer record information.

[0082] Optionally, the MME (mobility management entity) analyzes the dedicated bearer release information and identifies the dedicated bearer identifiers that the UE has deactivated. These identifiers are previously assigned when establishing dedicated bearers and are used to uniquely identify each dedicated bearer, including dedicated bearers used for video and voice data streams. Through these identifiers, the MME can accurately understand which dedicated bearers have been released by the UE and are no longer used for data transmission.

[0083] Next, the MME updates the dedicated bearer record information it has established and maintained, which contains all the dedicated bearer details of the UE, including the dedicated bearer identifier, type information, and Quality of Service (QoS) parameters of each dedicated bearer. The MME deletes the dedicated bearers marked as deactivated in the dedicated bearer record information.

[0084] Subsequently, the MME checks the updated dedicated bearer record information to determine whether there are any dedicated bearers associated with the target video call process but not yet marked as deactivated. If there are still dedicated bearer identifiers that have not been deleted in the dedicated bearer record information, this indicates that there are dedicated bearers related to the video call in the UE that are waiting to be deactivated and need further processing. Conversely, if all relevant dedicated bearer identifiers in the dedicated bearer record information are deleted, there are no dedicated bearers associated with the video call process that need to be deactivated in the UE.

[0085] Through this mechanism, MME can effectively track and manage the dedicated bearer status of UE, ensuring that all related dedicated bearers are correctly released after the VoLTE video call ends, thereby avoiding the waste of network resources and improving the overall efficiency of the network and the quality of user services. This meticulous management process is the key to ensuring that the network can quickly respond to user needs while maintaining good resource allocation and management.

[0086] In the technical solution provided in step S404, the target call process includes a video call process over a long-term evolution voice bearer, wherein the dedicated bearer associated with the target call process in the terminal device includes an audio dedicated bearer for carrying an audio data stream and an image dedicated bearer for carrying an image data stream.

[0087] Optionally, the VoLTE video call (video call over long term evolution voice bearer) process includes stages such as establishing a connection, making a video call, and ending the call. When making a video call, in order to ensure high-quality transmission of video and voice data, it is necessary to create dedicated bearers for video and voice data respectively (i.e., a dedicated audio bearer for carrying audio data streams and a dedicated image bearer for carrying image data streams).

[0088] When the call ends, the network will execute the corresponding process to release the dedicated bearer used for voice and video. However, in the existing technology, the S11 interface of SGW and MME supports the simultaneous deletion of multiple dedicated bearers, and the S1 interface of MME and ENODEB only supports carrying one dedicated bearer at the NAS layer. MME needs to adapt the multiple dedicated bearer release processes initiated by PGW to ensure that the terminal can be notified to release multiple dedicated bearer resources normally. Otherwise, the high-priority QoS dedicated bearer cannot be established, affecting the subsequent video call process.

[0089] Step S406, when the judgment result is yes, a deactivation indication message is sent to the terminal device through the evolved base station until the judgment result is no, wherein the deactivation indication message is used to instruct the terminal device to deactivate the dedicated bearer to be processed indicated by the deactivation indication message.

[0090] In the technical solution provided in step S406, sending the deactivation indication information to the terminal device through the evolved base station includes: sending the deactivation indication information to the terminal device through the evolved base station in a downlink non-access layer transmission manner.

[0091] Alternatively, if Figure 5 As shown, in the case where the judgment result is yes, the deactivation indication information is sent to the terminal device through the evolved base station until the judgment result is no, including:

[0092] 7.1. The MME determines that the terminal needs to be notified to deactivate the dedicated bearer, constructs a Deactivate EPS BearerContext Request, and notifies the terminal through DownLink Nas Transport (downlink non-access layer transmission).

[0093] 7.2. The eNodeB sends an RRC Connection Reconfiguration message to the UE, including a NAS Deactivate Dedicated Bearer message.

[0094] 7.3. The UE deactivates the dedicated bearer and sends an RRC Connection Reconfiguration Complete message to the eNodeB.

[0095] 7.4. The eNodeB sends an Uplink Nas Transport message to the MME to notify the dedicated bearer release result.

[0096] If the MME determines that there are still dedicated bearers that need to be deactivated, the above 7.1-7.4 processes are repeated until all dedicated bearer contexts that need to be deactivated have been notified to the terminal and released successfully.

[0097] That is, for the remaining dedicated bearers that need to be released, the Deactivate EPS Bearer Context Request is carried by the DownLink NAS Transport, and the Deactivate EPS Bearer Context Response carried by the Uplink NAS Transport is waited for to complete the deactivation process of the current dedicated bearer. For all dedicated bearers that need to be released, the above process is repeated until the terminal is notified that the deactivation process of all dedicated bearers is completed.

[0098] It should be noted that the eNodeB is only used to forward messages in the above steps 7.1-7.4. It is only responsible for forwarding NAS messages received from the MME, and does not process or interpret the contents of these messages. Specifically, when the MME sends a Deactivate EPS Bearer Context Request message through the DownLink Nas Transport, the eNodeB receives these messages, encapsulates them in the RRC Connection Reconfiguration signaling, and then sends the signaling to the UE. The purpose of this is to use the connection between the eNodeB and the UE to ensure that the NAS message can be accurately transmitted to the terminal.

[0099] After the UE receives the RRC Connection Reconfiguration message containing the NAS Deactivate Dedicated Bearer message, it will execute the dedicated bearer deactivation process to release the network and radio resources related to the video call. After the UE completes the deactivation, it will send an RRC Connection Reconfiguration Complete message to the eNodeB to confirm that it has executed the dedicated bearer deactivation.

[0100] Subsequently, the eNodeB forwards the message again, and it sends the UE's confirmation message back to the MME through the Uplink Nas Transport mechanism. In this case, the eNodeB also does not process the message content, but simply forwards it to the upper layer network entity MME as part of the RRC signaling. After receiving the confirmation message in the Uplink Nas Transport, the MME can confirm that the UE has successfully deactivated the specified dedicated bearer, and then update its internal status to reflect the current status of the dedicated bearer.

[0101] Through this forwarding mechanism of eNodeB, the end process of VOLTE video call can be executed more efficiently, ensuring the timely release of network resources. The key role of eNodeB is to maintain the transmission channel of NAS messages between UE and MME, so that high-level management instructions can be issued quickly and UE's response can be uploaded in time.

[0102] In the technical solution provided in step S406, a deactivation indication message is sent to the terminal device through the evolved base station until the judgment result is no, and the dedicated bearer release method also includes: the mobility management entity sends a dedicated bearer success release message to the service gateway, wherein the dedicated bearer success release message is used to indicate that the dedicated bearers associated with the target call process in the terminal device have been deactivated; the service gateway forwards the dedicated bearer success release message to the packet data network gateway; the packet data network gateway sends a session process modification indication message to the policy and charging rules function module, wherein the session process modification indication message is used to indicate that the dedicated bearers associated with the target call process in the terminal device have been deactivated.

[0103] Alternatively, if Figure 5 As shown, the deactivation indication information is sent to the terminal device by the evolved base station until the judgment result is no, and the dedicated bearer release method further includes:

[0104] 8. The MME (mobility management entity) sends a Delete Bearer Response (i.e., dedicated bearer successful release information) to the SGW (serving gateway) to notify the dedicated bearer release result.

[0105] 9. SGW sends Delete BearerResponse to PGW (Packet Data Network Gateway) to notify the result of the dedicated bearer release.

[0106] 10. PGW replies IP-CAN Session Modification (i.e., session process modification indication information) to PCRF (i.e., policy and charging rules function module), indicating that the PCC policy is successfully executed, that is, all dedicated bearers associated with the target call process in the terminal equipment (UE) have been deactivated.

[0107] In the above operating environment, the embodiment of the present application provides a dedicated load release method, such as Figure 6 As shown, the method comprises the following steps:

[0108] Step S602: The evolved base station receives deactivation indication information sent by the mobility management entity, wherein the deactivation indication information is used to instruct the terminal device to deactivate the dedicated bearer to be processed indicated by the deactivation indication information.

[0109] Step S604: Send deactivation instruction information to the terminal device.

[0110] Step S606: receiving response information sent by the terminal device, wherein the response information is used to indicate that the terminal device has deactivated the dedicated bearer to be processed indicated by the deactivation indication information.

[0111] Step S608: After receiving the response information, the evolved base station generates dedicated bearer release information corresponding to the response information, and sends the dedicated bearer release information corresponding to the response information to the mobility management entity.

[0112] Through the above steps, it is possible to implement the interaction of the Deactivate EPS bearer context message process by MME and the terminal on the basis of the existing PGW-initiated bearer deactivation process to adapt to the multi-bearer deactivation scenario. After obtaining the Bearer Context of the Delete Bearer Request message, the MME notifies ENODEB and UE to release the dedicated bearer resources based on the specific EBI (dedicated bearer identifier) ​​information. This solution does not add new messages and fields, nor does it modify the existing process. It only adds the Deactivate EPS bearer context message process corresponding to each dedicated bearer. The method embodiment of the present application is the same as the PGW-initiated bearer deactivation process in the existing 3GPP standard. It does not modify the existing process, does not add new network elements, and does not modify the existing network architecture. By expanding the PGW-initiated bearer deactivation process, it can support the simultaneous release of multiple dedicated bearers, simplifying the bearer release process at the end of the VOLTE video call. Ensure that ENODEB and the terminal can correctly release the dedicated bearer resources after the video call ends.

[0113] The embodiment of the present application provides a dedicated carrier release device, which is applicable to a mobility management entity. Figure 7 is a schematic diagram of the structure of the device, such as Figure 7As shown, the device includes: a first processing module 70, used to receive dedicated bearer release information sent by the evolved base station, wherein the dedicated bearer release information includes the dedicated bearer that has been deactivated by the terminal device; a second processing module 72, used to determine whether there is a pending dedicated bearer to be deactivated associated with the target call process in the terminal device based on the dedicated bearer release information; a third processing module 74, used to send deactivation indication information to the terminal device through the evolved base station if the judgment result is yes, until the judgment result is no, wherein the deactivation indication information is used to instruct the terminal device to deactivate the pending dedicated bearer indicated by the deactivation indication information.

[0114] In some embodiments of the present application, the mobility management entity establishes and maintains dedicated bearer record information corresponding to the terminal device, wherein the dedicated bearer record information includes a dedicated bearer identifier, type information and service quality parameters of the dedicated bearer corresponding to the terminal device.

[0115] In some embodiments of the present application, the second processing module 72 determines whether there is a pending dedicated bearer to be deactivated and associated with the target call process in the terminal device based on the dedicated bearer release information, including: determining the deactivated processed dedicated bearer identifier corresponding to the dedicated bearer release information; deleting the processed dedicated bearer identifier in the dedicated bearer record information; if it is determined that there is an undeleted dedicated bearer identifier in the dedicated bearer record information, it is determined that there is a pending dedicated bearer to be deactivated in the terminal device; and if it is determined that there is no undeleted dedicated bearer identifier in the dedicated bearer record information, it is determined that there is no pending dedicated bearer to be deactivated in the terminal device.

[0116] In some embodiments of the present application, the third processing module 74 sends a deactivation indication message to the terminal device through the evolved base station until the judgment result is no, and the dedicated bearer release method also includes: the mobility management entity sends a dedicated bearer success release message to the service gateway, wherein the dedicated bearer success release message is used to indicate that the dedicated bearers associated with the target call process in the terminal device have been deactivated; the service gateway forwards the dedicated bearer success release message to the packet data network gateway; the packet data network gateway sends a session process modification indication message to the policy and charging rules function module, wherein the session process modification indication message is used to indicate that the dedicated bearers associated with the target call process in the terminal device have been deactivated.

[0117] In some embodiments of the present application, the target call process includes a video call process over a long-term evolution voice bearer, wherein the dedicated bearer associated with the target call process in the terminal device includes an audio dedicated bearer for carrying an audio data stream and an image dedicated bearer for carrying an image data stream.

[0118] In some embodiments of the present application, the third processing module 74 sends the deactivation indication information to the terminal device through the evolved base station, including: sending the deactivation indication information to the terminal device through the evolved base station in a downlink non-access layer transmission manner.

[0119] It should be noted that the various modules in the above-mentioned dedicated release device can be program modules (for example, a set of program instructions that implement a certain specific function) or hardware modules. For the latter, it can be expressed in the following forms, but is not limited to this: the expression form of each of the above-mentioned modules is a processor, or the functions of each of the above-mentioned modules are implemented by a processor.

[0120] An embodiment of the present application provides a non-volatile storage medium, in which a program is stored. When the program is running, a device where the non-volatile storage medium is located is controlled to execute the above-mentioned dedicated load release method.

[0121] An embodiment of the present application provides an electronic device, including: a memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the above-mentioned dedicated load release method is executed when the program is running.

[0122] An embodiment of the present application provides a computer program product, including a computer program, which implements the above-mentioned dedicated load release method when executed by a processor.

[0123] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0124] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0125] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0126] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0127] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0128] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A dedicated load release method, characterized in that: include: The mobility management entity receives dedicated bearer release information sent by the evolved base station, wherein the dedicated bearer release information includes a dedicated bearer that has been deactivated by the terminal device; Determining whether there is a pending dedicated bearer to be deactivated associated with the target call process in the terminal device according to the dedicated bearer release information; When the judgment result is yes, a deactivation indication message is sent to the terminal device through the evolved base station until the judgment result is no, wherein the deactivation indication message is used to instruct the terminal device to deactivate the dedicated carrier to be processed indicated by the deactivation indication message.

2. The dedicated load release method according to claim 1, characterized in that: The method further comprises: The mobility management entity establishes and maintains dedicated bearer record information corresponding to the terminal device, wherein the dedicated bearer record information includes a dedicated bearer identifier, type information and service quality parameters of the dedicated bearer corresponding to the terminal device.

3. The dedicated load release method according to claim 2, characterized in that: Judging whether there is a pending dedicated bearer to be deactivated in the terminal device and associated with the target call process according to the dedicated bearer release information includes: Determine a deactivated processed dedicated bearer identifier corresponding to the dedicated bearer release information; Deleting the processed dedicated carriage identifier from the dedicated carriage record information; When it is determined that the dedicated carrier identifier exists in the dedicated carrier record information and has not been deleted, it is determined that there is a pending dedicated carrier to be deactivated in the terminal device; and when it is determined that the dedicated carrier identifier does not exist in the dedicated carrier record information and has not been deleted, it is determined that there is no pending dedicated carrier to be deactivated in the terminal device.

4. The dedicated load release method according to claim 1, characterized in that: Sending deactivation indication information to the terminal device by the evolved base station until the judgment result is no, the dedicated bearer release method further includes: The mobility management entity sends dedicated bearer successful release information to the serving gateway, wherein the dedicated bearer successful release information is used to indicate that all dedicated bearers associated with the target call flow in the terminal device have been deactivated; The serving gateway forwards the dedicated bearer successful release information to the packet data network gateway; The packet data network gateway sends session flow modification indication information to the policy and charging rule function module, wherein the session flow modification indication information is used to indicate that all dedicated bearers associated with the target call flow in the terminal device have been deactivated.

5. The dedicated load release method according to claim 1, characterized in that: The target call process includes a video call process over a long term evolution voice bearer, wherein the dedicated bearer associated with the target call process in the terminal device includes an audio dedicated bearer for carrying an audio data stream and an image dedicated bearer for carrying an image data stream.

6. The dedicated load release method according to claim 1, characterized in that: Sending deactivation indication information to the terminal device by the evolved base station includes: The deactivation indication information is sent to the terminal device through the evolved base station in a downlink non-access layer transmission manner.

7. A dedicated load release method, characterized in that: include: The evolved base station receives deactivation indication information sent by the mobility management entity, wherein the deactivation indication information is used to instruct the terminal device to deactivate the dedicated bearer to be processed indicated by the deactivation indication information; Sending the deactivation instruction information to the terminal device; receiving response information sent by the terminal device, wherein the response information is used to indicate that the terminal device has deactivated the dedicated bearer to be processed indicated by the deactivation indication information; After receiving the response information, the evolved base station generates dedicated bearer release information corresponding to the response information, and sends the dedicated bearer release information corresponding to the response information to the mobility management entity.

8. A dedicated load release device, applicable to a mobility management entity, characterized in that: include: A first processing module is configured to receive dedicated bearer release information sent by the evolved base station, wherein the dedicated bearer release information includes a dedicated bearer that has been deactivated by the terminal device; A second processing module, configured to determine whether there is a dedicated bearer to be deactivated in the terminal device that is associated with the target call process according to the dedicated bearer release information; The third processing module is used to send a deactivation indication message to the terminal device through the evolved base station when the judgment result is yes, until the judgment result is no, wherein the deactivation indication message is used to instruct the terminal device to deactivate the dedicated carrier to be processed indicated by the deactivation indication message.

9. A non-volatile storage medium, characterized in that: The non-volatile storage medium stores a program, wherein when the program is running, the device where the non-volatile storage medium is located is controlled to execute the dedicated load release method described in any one of claims 1 to 6 or 7.

10. An electronic device, characterized in that: include: A memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the program executes the dedicated load release method described in any one of claims 1 to 6 or 7 when running.

11. A computer program product, characterized in that It comprises a computer program, which, when executed by a processor, implements the dedicated load release method according to any one of claims 1 to 6 or 7.

Images