Connection processing methods, systems and related equipment
By dynamically adjusting the service bearer of the terminal in the NB-IoT system of GEO satellites, suspending or deactivating low-priority services to establish voice service bearer, the problem of insufficient DRB resources is solved, and the priority processing of high-priority services and the effective utilization of resources are realized.
Patent Information
- Application Number
- CN202510600070.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-17
AI Technical Summary
In GEO satellite NB-IoT technology, the number of data wireless bearers is limited, resulting in insufficient DRB resources when voice services are started, which affects the service quality and stability of voice communication.
By suspending or deactivating low-priority service bearers on the terminal, high-priority voice service bearers are established, and DRB resource allocation is dynamically adjusted.
Within the limited DRB resources, priority should be given to meeting the needs of voice services, ensuring the processing of high-priority services, and minimizing the impact on other services.
Smart Images

Figure CN123124134A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to a connection processing method, system and related equipment. Background Technology
[0002] With the continuous development of communication technology, utilizing satellites to provide voice communication services for User Equipment (UE) has become an important direction for industry development. Among the many satellite orbit types, geostationary orbit (GEO) satellites, with their unique advantages, have become a research hotspot for providing basic voice services for UEs. Compared to medium Earth orbit (MEO) and low Earth orbit (LEO) satellites, GEO satellites can provide wide-coverage basic voice capabilities with minimal network deployment costs.
[0003] However, GEO satellites typically use Narrowband Internet of Things (NB-IoT) technology to support voice communication. Due to the inherent characteristics of NB-IoT technology, the number of Data Radio Bearers (DRBs) can be limited (maximum of two). In real-world applications, UEs often run multiple services simultaneously, and may have already used DRB resources for other services such as internet access before using voice services. This can easily lead to insufficient DRB resources when voice services are initiated, severely impacting the quality and stability of voice communication.
[0004] Therefore, how to dynamically and flexibly adjust the number of DRB bearers to adapt to the resource requirements of different business scenarios has become an urgent problem to be solved in this field.
[0005] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention
[0006] This disclosure provides a connection processing method, system, and related equipment to prioritize voice service processing needs within limited DRB resources.
[0007] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part from practice of this disclosure.
[0008] According to one aspect of this disclosure, a connection processing method is provided, applied to a terminal, comprising: suspending / deactivating / releasing a bearer of a second service on the terminal to establish a bearer of a first service on the terminal.
[0009] In some embodiments, suspending / deactivating / releasing the second service bearer on the terminal includes: receiving a bearer deactivation request from the network side for the second service; suspending / deactivating the bearer of the second service.
[0010] In some embodiments, suspending / deactivating / releasing the bearer of a second service on the terminal to establish the bearer of a first service on the terminal includes: receiving a bearer release request for the second service from a base station; suspending / releasing the bearer of the second service.
[0011] In some embodiments, the bearer deactivation request includes indication information and / or a reason value, which is used to notify the terminal that the bearer of the second service will no longer be activated.
[0012] In some embodiments, the bearer release request includes indication information and / or a reason value, which is used to notify the terminal that the bearer of the second service will no longer be activated.
[0013] In some embodiments, the indication information and / or reason value are used to indicate that a bearer needs to suspend / deactivate / release data services due to the transmission of voice service data.
[0014] In some embodiments, after suspending / deactivating / releasing the bearer of the second service on the terminal to establish the bearer of the first service on the terminal, the method further includes: deactivating the bearer of the first service on the terminal.
[0015] In some embodiments, after deactivating the bearer of the first service on the terminal, the method further includes: receiving a bearer activation request for a second service from the network side; and activating the bearer of the second service on the terminal.
[0016] In some embodiments, the first service is a voice service, and the second service is a data service.
[0017] According to another aspect of this disclosure, a connection processing method is also provided, applied to a mobility management entity (MME), comprising: receiving a bearer activation request for a first service on a terminal; suspending / deactivating / releasing a bearer for a second service on the terminal, so that the terminal establishes a bearer for the first service.
[0018] In some embodiments, suspending / deactivating / releasing the bearer of the second service on the terminal to enable the terminal to establish the bearer of the first service includes: monitoring whether the total number of active bearers on the terminal has reached the bearer limit threshold; if the total number of active bearers on the terminal has reached the bearer limit threshold, suspending / deactivating / releasing the bearer of the second service on the terminal to enable the terminal to establish the bearer of the first service.
[0019] In some embodiments, the method further includes: determining the bearer of a second service that needs to be suspended / deactivated / released on the terminal based on configuration information and / or policy information.
[0020] In some embodiments, suspending / deactivating / releasing the bearer of a second service on the terminal to enable the terminal to establish a bearer of a first service includes: sending a bearer deactivation request for the second service to the terminal to request the terminal to deactivate the bearer of the second service.
[0021] In some embodiments, suspending / deactivating / releasing the bearer of a second service on the terminal to enable the terminal to establish a bearer of a first service includes: sending a bearer release request for the second service to the base station to request the base station to release the resources allocated for the bearer of the second service.
[0022] In some embodiments, the bearer deactivation request includes indication information and / or a reason value, which is used to notify the terminal that the bearer of the second service will no longer be activated.
[0023] In some embodiments, the bearer release request includes indication information and / or a reason value, which is used to notify the terminal that the bearer of the second service will no longer be activated.
[0024] In some embodiments, the indication information and / or reason value are used to indicate that a bearer needs to suspend / deactivate / release data services due to the transmission of voice service data.
[0025] In some embodiments, the method further includes sending a notification message to the Serving Gateway (SGW) and / or the Packet Data Network Gateway (PGW) to suspend the bearer of the second service.
[0026] In some embodiments, the notification message is used to notify the SGW and / or PGW to perform at least one of the following operations: cache the received downlink data packets of the second service; not notify the Mobility Management Entity (MME) after receiving the downlink data packets of the second service; delete the received downlink data packets of the second service.
[0027] In some embodiments, after suspending / deactivating / releasing the bearer of the second service on the terminal to enable the terminal to establish the bearer of the first service, the method further includes: upon receiving a bearer deactivation request for the first service, restoring and / or activating the bearer of the second service on the terminal.
[0028] In some embodiments, after suspending / deactivating / releasing the bearer of the second service on the terminal to enable the terminal to establish the bearer of the first service, the method further includes: if the total number of bearers activated on the terminal does not reach the upper limit threshold of the bearer, restoring and / or activating the bearer of the second service on the terminal.
[0029] In some embodiments, restoring and / or activating the bearer of the second service on the terminal includes: sending a bearer activation request for the second service to the terminal to request the terminal to activate the bearer of the second service.
[0030] In some embodiments, restoring and / or activating the bearer of the second service on the terminal includes: sending a bearer establishment request for the second service to the base station to request the base station to allocate resources for the bearer of the second service.
[0031] In some embodiments, restoring and / or activating the bearer of the second service on the terminal includes sending a notification message to the SGW and / or PGW to restore the bearer of the second service.
[0032] In some embodiments, the first service is a voice service; the second service is a data service.
[0033] According to another aspect of this disclosure, a terminal is also provided, comprising: a bearer management module for suspending / deactivating / releasing the bearer of a second service on the terminal to establish the bearer of a first service on the terminal.
[0034] According to another aspect of this disclosure, a network-side device is also provided, comprising: a first bearer processing module, configured to receive a bearer activation request for a first service on a terminal; and a second bearer processing module, configured to suspend / deactivate / release the bearer of a second service on the terminal, so that the terminal establishes a bearer for the first service.
[0035] According to another aspect of this disclosure, a communication system is also provided, comprising: a terminal and a network-side device; wherein the network-side device is used to suspend / deactivate / release a bearer of a second service on the terminal; and the terminal is used to establish a bearer of a first service.
[0036] According to another aspect of this disclosure, an electronic device is also provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the connection processing method described in any of the preceding claims by executing the executable instructions.
[0037] According to another aspect of this disclosure, a computer-readable storage medium is also provided, on which a computer program is stored, which, when executed by a processor, implements the connection processing method described in any of the preceding claims.
[0038] According to another aspect of this disclosure, a computer program product is also provided, comprising: a computer program or instructions that, when executed by a processor, implement the link processing method described in any of the preceding claims.
[0039] The connection processing method, system, and related devices provided in the embodiments of this disclosure suspend / deactivate / release the bearer of the second service when the terminal needs to process the first service, thereby establishing the bearer of the first service. Through the embodiments of this disclosure, the terminal can suspend / deactivate / release the bearer of the low-priority service when processing high-priority services, in order to establish the bearer of the high-priority service, thereby ensuring that high-priority services are processed first, utilizing limited resources to meet different service needs.
[0040] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0041] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.
[0042] Figure 1 This diagram illustrates a communication system architecture according to an embodiment of the present disclosure;
[0043] Figure 2 This diagram illustrates a flowchart of a connection processing method according to an embodiment of the present disclosure;
[0044] Figure 3 This diagram illustrates a flowchart of a suspended / deactivated service bearer embodiment in this disclosure.
[0045] Figure 4 This diagram illustrates a flowchart of suspending / releasing a service bearer according to an embodiment of this disclosure;
[0046] Figure 5 This diagram illustrates an optional connection processing method according to an embodiment of the present disclosure.
[0047] Figure 6 This diagram illustrates another optional connection processing method in an embodiment of the present disclosure.
[0048] Figure 7 This diagram illustrates a flowchart of yet another connection processing method according to an embodiment of the present disclosure;
[0049] Figure 8 This diagram illustrates a flowchart of yet another instance of suspending / releasing a service bearer in an embodiment of this disclosure;
[0050] Figure 9 This diagram illustrates a flowchart of yet another optional connection processing method in an embodiment of this disclosure;
[0051] Figure 10 This diagram illustrates a flowchart of a request for a terminal to deactivate a service bearer, as shown in an embodiment of this disclosure.
[0052] Figure 11 This diagram illustrates a flowchart of a request for a base station to release a service bearer according to an embodiment of this disclosure;
[0053] Figure 12 This diagram illustrates a flowchart of a request service gateway and / or packet data network gateway suspending a service bearer according to an embodiment of this disclosure.
[0054] Figure 13 This diagram illustrates a flowchart of a method for restoring and / or activating a service bearer according to an embodiment of this disclosure;
[0055] Figure 14 This diagram illustrates a flowchart of yet another embodiment of restoring and / or activating a service bearer according to this disclosure.
[0056] Figure 15 This illustration shows a flowchart of a request for a terminal to restore and / or activate service bearer according to an embodiment of this disclosure;
[0057] Figure 16 This diagram illustrates a flowchart of a request for a base station to restore and / or activate a service bearer, as described in an embodiment of this disclosure.
[0058] Figure 17 This diagram illustrates a flowchart of a request service gateway to restore and / or activate a service bearer according to an embodiment of this disclosure;
[0059] Figure 18 This diagram illustrates a specific implementation flowchart of a connection processing method according to an embodiment of the present disclosure.
[0060] Figure 19 This diagram illustrates a terminal according to an embodiment of the present disclosure;
[0061] Figure 20 This diagram illustrates a network-side device according to an embodiment of the present disclosure;
[0062] Figure 21 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown. Detailed Implementation
[0063] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[0064] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.
[0065] To facilitate understanding, before introducing the embodiments of this disclosure, the following explanations are provided for several terms involved in the embodiments of this disclosure:
[0066] UE: User Equipment. It can be any terminal device that can access a mobile communication network, such as a mobile phone, tablet, or IoT device, and is the tool for users to interact with the network.
[0067] MME: Mobility Management Entity. It is responsible for managing the mobility of User Equipment (UE), including functions such as tracking area updates, paging, and handover, and controlling and managing UE mobility within the LTE network.
[0068] SGW: Serving Gateway. As a forwarding node for user plane data, it is responsible for forwarding user data between different base stations, and also participates in functions such as packet routing and mobility management.
[0069] PGW: PDN Gateway. It connects to external data networks (such as the Internet) and is responsible for data transmission, address allocation, billing, and other functions between the UE and the external network.
[0070] RAN: Radio Access Network. Composed of base stations and other equipment, it is responsible for connecting the UE to the core network, enabling the transmission and reception of wireless signals and data, and providing wireless access services to users.
[0071] EPS: Evolved Packet System. It is the core network architecture in 3GPP Long Term Evolution (LTE) technology, designed to provide higher data transmission rates and lower latency, support multiple access technologies, and achieve efficient transmission and management of packet data.
[0072] NAS: Non-Access Stratum. Located between the UE and the core network, it is mainly responsible for signaling interaction between the UE and the core network, including mobility management, session management, authentication and other functions. It is independent of the access layer and provides support for higher-level applications.
[0073] RAT stands for Radio Access Technology. It refers to various technologies used to achieve wireless communication, such as LTE, WCDMA, and GSM. Different RATs have different characteristics and performance to meet different communication needs.
[0074] DRB: Data Radio Bearer. It is used to transmit user data between the UE and the network, defining the parameters and methods for data transmission to ensure reliable data transmission over the radio link.
[0075] GEO: Geostationary Earth Orbit. This refers to a circular orbit around the Earth's surface, approximately 36,000 kilometers above the equatorial plane. The satellite's angular velocity in this orbit is the same as the Earth's rotational angular velocity. From Earth's perspective, the satellite appears stationary at a point in the sky. It is commonly used for communication and meteorological satellites.
[0076] MEO: Medium Earth Orbit. This is the orbital region located between 2,000 and 36,000 kilometers above the Earth's surface. Satellites operating in this orbit have moderate altitudes and speeds, and can be used for various purposes, including the Global Positioning System (GPS). They offer wide signal coverage and relatively stable communication and positioning services.
[0077] LEO stands for Low Earth Orbit. It generally refers to an orbit between 200 and 2000 kilometers above the Earth's surface. Satellites in LEO orbit travel at high speeds and experience low signal transmission delays, making them suitable for Earth observation, manned spaceflight, and satellite communications. For example, some near-Earth observation satellites and certain communication satellite constellations are located in LEO. Due to the low orbital altitude, satellites are significantly affected by Earth's gravity, requiring regular orbit maintenance.
[0078] IMS: IP Multimedia Subsystem. It is a multimedia service control architecture based on IP networks, capable of providing rich multimedia services such as voice and video calls, instant messaging, online games, etc., supporting multiple access methods, and realizing unified control and management of multimedia services.
[0079] The specific implementation methods of the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.
[0080] Figure 1 A schematic diagram of an exemplary communication system architecture to which the connection processing method of the embodiments of this disclosure can be applied is shown. Figure 1 As shown, the system architecture may include terminal 10 and network-side equipment; wherein, the network-side equipment includes, but is not limited to: terrestrial base station 20, satellite base station 30, terrestrial gateway station 40, and network elements such as the Mobility Management Entity (MME), Serving Gateway (SGW), and Packet Data Network Gateway (PGW) within the core network 50.
[0081] In this disclosed example, the network-side device (Mobility Management Entity MME) is used to suspend / deactivate / release the bearer of the second service on the terminal; the terminal 10 is used to establish the bearer of the first service.
[0082] In this disclosed example, terminal 10 can communicate with core network 50 via terrestrial base station 20 or via satellite base station 30.
[0083] Optionally, the terminal in this embodiment may also be referred to as UE (User Equipment). In specific implementation, the terminal may be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), mobile internet device (MID), wearable device, or vehicle-mounted device, etc. It should be noted that the specific type of terminal is not limited in the embodiments of the present invention.
[0084] The base station in this embodiment can be any type of network base station, such as a 3G base station, a 4G base station, a 5G base station, a 6G base station, or a later version base station. It should be noted that this embodiment does not limit the specific type of base station.
[0085] Those skilled in the art will know that Figure 1 The number of terminals, base stations, gateway stations, and core network elements shown in this embodiment is merely illustrative. Any number of terminals, base stations, gateway stations, and core network elements can be included as needed. This disclosure does not limit the number of such components.
[0086] Under the above system architecture, this disclosure provides a connection processing method that can be executed by any electronic device with computing capabilities.
[0087] In some embodiments, the connection processing method provided in this disclosure can be executed by a terminal of the above-described system architecture; in other embodiments, the connection processing method provided in this disclosure can be implemented by the terminal and network-side devices (including but not limited to one or more of mobility management entities, service gateways, packet data network gateways, and base stations) in the above-described system architecture through interaction.
[0088] Figure 2 This diagram illustrates a flowchart of a connection processing method according to an embodiment of the present disclosure, such as... Figure 2 As shown, the connection processing method may include the following steps:
[0089] S202, suspend / deactivate / release the bearer of the second service on the terminal in order to establish the bearer of the first service on the terminal.
[0090] In this embodiment of the disclosure, the first service and the second service can be any two different services. In one embodiment, the first service can be a voice service and the second service can be a data service.
[0091] When GEO satellites provide voice services to terminals via NB-IoT technology, the number of DRB bearers for NB-IoT is limited (maximum 2). If the terminal is using other services such as the Internet before using the voice service, it may lead to insufficient DRB resources. The connection processing method provided in this embodiment suspends / deactivates / releases the DRB bearers of other services on the terminal when a voice service is triggered; when the voice service ends, the bearers of the corresponding services are restored. Through this dynamic adjustment, high-priority processing of voice services can be satisfied within the limited DRB range, and the impact on other services can be reduced.
[0092] In some embodiments, such as Figure 3 As shown, the connection processing method provided in this embodiment can suspend / deactivate the second service bearer on the terminal through the following steps:
[0093] S302, Receive a bearer deactivation request for the second service from the network side;
[0094] S304, Suspend / Deactivate the bearer of the second service.
[0095] It should be noted that the aforementioned bearer deactivation request may be sent by the Mobility Management Entity (MME). This request must contain at least the bearer identifier of the service to be deactivated, i.e., the bearer identifier of the second service. When the terminal receives the bearer deactivation request from the MME, it suspends / deactivates the corresponding service's bearer. In one embodiment, the bearer deactivation request may include indication information and / or a reason value, which is used to notify the terminal that the bearer of the second service will no longer be activated.
[0096] Furthermore, in one embodiment, the indication information and / or cause value can also be used to indicate the bearer that needs to be suspended / deactivated / released due to the transmission of voice service data.
[0097] In some embodiments, such as Figure 4 As shown, the connection processing method provided in this embodiment can suspend / release the bearer of the second service on the terminal through the following steps:
[0098] S402, Receive a bearer release request for the second service from the base station;
[0099] S404, Suspend / Release the bearer for the second service.
[0100] It should be noted that the aforementioned bearer release request can be sent by the base station based on an instruction from the MME. This bearer release request must at least include the bearer identifier for the deactivated service, i.e., the bearer identifier for the second service. When the terminal receives the bearer release request from the base station, it suspends / releases the bearer for the corresponding service. In one embodiment, the bearer release request may include indication information and / or a reason value, which is used to notify the terminal that the bearer for the second service will no longer be activated.
[0101] Furthermore, in one embodiment, the indication information and / or cause value can also be used to indicate the bearer that needs to be suspended / deactivated / released due to the transmission of voice service data.
[0102] In some embodiments, such as Figure 5 As shown, after suspending / deactivating / releasing the bearer of the second service on the terminal to establish the bearer of the first service on the terminal, the connection processing method provided in this embodiment may further include the following steps:
[0103] S502, deactivate the bearer of the first service on the terminal.
[0104] When the first service ends, the MME will receive a deactivation bearer request from the service gateway of the first service, and send it to the terminal through the base station so that the terminal can deactivate the bearer of the first service.
[0105] In some embodiments, such as Figure 6 As shown, after deactivating the bearer of the first service on the terminal, the connection processing method provided in this embodiment may further include the following steps:
[0106] S602, Receive bearer activation request for the second service from the network side;
[0107] S604 activates the carrying of the second service on the terminal.
[0108] When the bearer of the first service is deactivated, the bearer of the second service can be activated according to the bearer activation request sent by the network side, so that the terminal can continue to process the second service through the previously suspended / deactivated / released bearer.
[0109] Based on the same inventive concept, this disclosure also provides a connection processing method, which can be executed by any electronic device with computing capabilities.
[0110] In some embodiments, the connection processing method provided in this disclosure can be executed by network-side devices (including but not limited to one or more of Mobility Management Entity (MME), Serving Gateway (SGW), Packet Data Network Gateway (PGW), and base stations) in the above system architecture; in other embodiments, the connection processing method provided in this disclosure can be implemented by the network-side devices (including but not limited to one or more of Mobility Management Entity, Serving Gateway, Packet Data Network Gateway, and base stations) in the above system architecture and the terminal through interaction.
[0111] Figure 7 This diagram illustrates another connection processing method according to an embodiment of the present disclosure, such as... Figure 7 As shown, the connection processing method may include the following steps:
[0112] S702, Received a bearer activation request for the first service of the terminal;
[0113] S704 suspends / deactivates / releases the bearer of the second service on the terminal so that the terminal can establish the bearer of the first service.
[0114] It should be noted that the bearer activation request in S702 above can be sent by the service gateway SGW of the first service to the mobility management entity MME. After receiving the bearer activation request of the first service, the MME suspends / deactivates / releases the bearer of the second service on the terminal so that the terminal can establish the bearer of the first service.
[0115] In this embodiment of the disclosure, the first service and the second service can be any two different services. In one embodiment, the first service can be a voice service and the second service can be a data service.
[0116] In some embodiments, such as Figure 8 As shown, the connection processing method provided in this embodiment can suspend / deactivate / release the bearer of the second service on the terminal through the following steps:
[0117] S802, monitor whether the total number of active bearers on the monitoring terminal has reached the upper limit threshold;
[0118] S804: When the total number of active bearers on the terminal has reached the upper limit threshold, suspend / deactivate / release the bearer of the second service on the terminal so that the terminal can establish the bearer of the first service.
[0119] It should be noted that the upper limit threshold for bearer capacity in this embodiment of the present disclosure can be either the upper limit threshold for bearer capacity supported by the terminal or the upper limit threshold for bearer capacity supported by the network.
[0120] In some embodiments, such as Figure 9 As shown, the connection processing method provided in this embodiment may further include the following steps:
[0121] S902, based on configuration information and / or policy information, determines the bearer of the second service that needs to be suspended / deactivated / released on the terminal.
[0122] It should be noted that the specific content of the configuration information and policy information is not limited in this embodiment. The configuration information and policy information here can be, but is not limited to, service priority. Since there may be multiple active service bearers on the terminal, the configuration information and / or policy information can be used to determine when to suspend / deactivate / release a service bearer.
[0123] In some embodiments, such as Figure 10 As shown, the connection processing method provided in this embodiment of the disclosure can request the terminal to deactivate the service bearer through the following steps:
[0124] S102, send a second service bearer deactivation request to the terminal to request the terminal to deactivate the second service bearer.
[0125] It should be noted that the bearer deactivation request in S102 above can be sent by the MME to the terminal.
[0126] In some embodiments, the bearer deactivation request includes indication information and / or a reason value, which is used to notify the terminal that the bearer for the second service will no longer be activated.
[0127] In some embodiments, such as Figure 11 As shown, the connection processing method provided in this embodiment of the disclosure can request the base station to release the service bearer through the following steps:
[0128] S112, send a bearer release request for the second service to the base station to request the base station to release the resources allocated for the bearer of the second service.
[0129] It should be noted that the bearer deactivation request in S112 above can be sent by the MME to the base station.
[0130] In some embodiments, the bearer release request includes indication information and / or a reason value, which is used to notify the terminal that the bearer for the second service will no longer be activated.
[0131] In some embodiments, the indication information and / or reason value included in the bearer deactivation request or bearer release request are used to indicate a bearer that needs to suspend / deactivate / release data service due to the transmission of voice service data.
[0132] In some embodiments, such as Figure 12 As shown, the connection processing method provided in this embodiment may further include the following steps:
[0133] S122, send a notification message to the Serving Gateway (SGW) and / or Packet Data Network Gateway (PGW) to suspend the bearer of the second service.
[0134] It should be noted that the bearer deactivation request in S122 above can be sent by the MME to the SGW and / or PGW.
[0135] In some embodiments, the above notification message is used to notify the SGW and / or PGW to perform at least one of the following operations:
[0136] Buffer the received downlink data packets for the second service;
[0137] Upon receiving the downlink data packet for the second service, the Mobility Management Entity (MME) is not notified.
[0138] Delete the received downlink data packets for the second service.
[0139] In some embodiments, after suspending / deactivating / releasing the bearer of the second service on the terminal to enable the terminal to establish the bearer of the first service, such as Figure 13 As shown, the connection processing method provided in this embodiment may further include the following steps:
[0140] S132, upon receiving a request to deactivate the bearer of the first service, restore and / or activate the bearer of the second service on the terminal.
[0141] In this embodiment of the disclosure, to prioritize the processing of the first service, upon receiving a bearer activation request for the first service, the bearer of the second service on the terminal is suspended / deactivated / released. When the processing of the first service ends and a bearer deactivation request for the first service is received, the suspended / deactivated / released bearer of the second service on the terminal can be restored and / or activated so that the restored and / or activated bearer can be used to process the second service.
[0142] In some embodiments, after suspending / deactivating / releasing the bearer of the second service on the terminal to enable the terminal to establish the bearer of the first service, such as Figure 14 As shown, the connection processing method provided in this embodiment may further include the following steps:
[0143] S142, if the total number of active bearers on the terminal does not reach the upper limit threshold, restore and / or activate the bearer of the second service on the terminal.
[0144] Since the terminal suspends / deactivates / releases the bearer of the second service on the terminal in order to process the first service, when it is detected that the total number of active bearers on the terminal has not reached the upper limit threshold, restoring and / or activating the bearer of the second service on the terminal can reduce the impact of the first service processing on the second service.
[0145] In some embodiments, such as Figure 15 As shown, the connection processing method provided in this embodiment may further include the following steps: restoring and / or activating the bearer of the second service on the terminal:
[0146] S152, send a bearer activation request for the second service to the terminal to request the terminal to activate the bearer of the second service.
[0147] It should be noted that the bearer activation request in S152 above can be sent by the MME to the terminal.
[0148] In some embodiments, such as Figure 16 As shown, the connection processing method provided in this embodiment may further include the following steps: restoring and / or activating the bearer of the second service on the terminal:
[0149] S162, a bearer establishment request for the second service is sent to the base station to request the base station to allocate resources for the bearer of the second service.
[0150] It should be noted that the bearer establishment request in S162 above can be sent by the MME to the base station.
[0151] In some embodiments, such as Figure 17 As shown, the connection processing method provided in this embodiment may further include the following steps: restoring and / or activating the bearer of the second service on the terminal:
[0152] S172, send a notification message to the SGW and / or PGW to restore the bearer for the second service.
[0153] It should be noted that the notification message in S172 above can be sent by the MME to the SGW and / or PGW.
[0154] Figure 18 This diagram illustrates a specific implementation flowchart of a connection processing method according to an embodiment of the present disclosure, such as... Figure 18 As shown, it includes the following steps:
[0155] S1802, PGW1 sends a private bearer establishment request to the MME.
[0156] S1804, the MME sends a deactivation bearer request (indication information) to the UE.
[0157] S1806, the UE returns a deactivation bearer response to the MME.
[0158] S1808a, the MME sends a suspended bearer notification (bearer identifier) to the PGW2.
[0159] S1808b, PGW2 returns a suspended bearer confirmation to MME.
[0160] S1810, PGW1 sends a request to the MME to delete the dedicated bearer.
[0161] S1812, the MME sends an activation default bearer request to the UE.
[0162] S1814a, the MME sends a bearer recovery / activation notification (bearer identifier) to the PGW2.
[0163] S1814b, PGW2 returns a confirmation of bearer recovery / activation to MME.
[0164] Taking the UE accessing the core network via a base station using NB-IoT technology as an example, when triggering IMS voice service, a bearer within the IMSPDN needs to be established. The connection processing includes the following steps:
[0165] 1) The MME receives a private bearer establishment request from the IMS PDN (assuming an IMS PDN connection on PGW1) from PGW1. This request can be for establishing a GBR bearer or a Non-GBR bearer.
[0166] 2) If the number of currently activated user plane DRB bearers for the UE has reached the terminal / network supported limit (e.g., the maximum limit is 2 under NB-IoT access), the MME determines to establish a dedicated IMS bearer and suspends one of the UE's other bearers to ensure the priority of voice services. The MME can determine which PDN connection's user plane bearer to suspend based on a policy (e.g., a PDN connection on PGW2). The MME initiates a bearer deactivation request to the UE, which includes the bearer ID corresponding to the bearer determined to be suspended in S1804, and an indication (or reason value). The indication (or reason value) can be, for example: IMS voice service is in progress.
[0167] 3) The UE returns a deactivation bearer response (deactivation bearer acceptance). Based on the indication (or reason value), the UE no longer activates this bearer. The execution of S1804 and S1806 also includes the 3GPP standard procedure where the MME requests the base station to release the bearer R-RAB.
[0168] 4) The MME sends a suspension instruction to the SGW / PGW, including the EPS bearer ID determined in S1804; the SGW / PGW confirms that subsequent downlink data packets for this bearer will be buffered by the SGW / PGW and will no longer be sent to the base station or notified to the MME. To reduce the execution time of the entire communication process, especially considering that the UE is accessing via GEO satellite at this time, the MME can initiate S1804 and S1806 simultaneously.
[0169] 5) After the UE completes the IMS voice service, the MME receives a request to deactivate the dedicated bearer from PGW1. The MME then completes the process of deactivating the dedicated bearer.
[0170] 6) When the MME discovers that the number of active user plane DRB bearers of the UE is lower than the upper limit supported by the terminal / network (e.g., the maximum upper limit is 2 under NB-IoT access), the MME initiates a default bearer activation procedure to the UE, which also includes the 3GPP standard procedure for the MME to request the base station to establish an R-RAB.
[0171] 7) The MME sends a recovery instruction to the SGW / PGW, including the EPS bearer ID from S1808a; the SGW / PGW confirms, and subsequently the SGW / PGW sends the downlink data packets of this bearer to the base station or notifies the MME. After completing the above process, the UE can continue to use the previously suspended EPS user plane bearer.
[0172] With the connection processing method provided in this embodiment, when the UE performs voice calls via GEO satellite in the future, high priority of voice calls can be guaranteed within the limitations of wireless technology, and other services can be restored after the voice call ends, reducing the impact on the UE's voice + Internet combined service.
[0173] Based on the same inventive concept, this disclosure also provides a terminal, as described in the following embodiments. Since the principle by which this terminal embodiment solves the problem is similar to that of the above-described method embodiments, the implementation of this terminal embodiment can refer to the implementation of the above-described method embodiments, and repeated details will not be elaborated further.
[0174] Figure 19 This illustration shows a terminal schematic diagram according to an embodiment of the present disclosure, such as... Figure 19 As shown, the terminal includes: a bearer management module 191, used to suspend / deactivate / release the bearer of the second service on the terminal in order to establish the bearer of the first service on the terminal.
[0175] In this embodiment of the disclosure, the first service and the second service can be any two different services. In one embodiment, the first service can be a data service and the second service can be a voice service.
[0176] In some embodiments, the bearer management module 191 is further configured to: receive a bearer deactivation request from the network side for a second service; suspend / deactivate the bearer of the second service.
[0177] It should be noted that the above bearer deactivation request includes indication information and / or reason value, which is used to notify the terminal that the bearer for the second service will no longer be activated.
[0178] In some embodiments, the indication information and / or reason value included in the bearer deactivation request are used to indicate the bearer that needs to suspend / deactivate / release data service due to the transmission of voice service data.
[0179] In some embodiments, the bearer management module 191 is further configured to: receive a bearer release request for a second service from a base station; suspend / release the bearer of the second service.
[0180] It should be noted that the aforementioned bearer release request includes indication information and / or reason value, which is used to notify the terminal that the bearer for the second service will no longer be activated.
[0181] In some embodiments, the indication information and / or reason value included in the bearer release request are used to indicate the bearer that needs to be suspended / deactivated / released for data service due to the transmission of voice service data.
[0182] In some embodiments, the bearer management module 191 is further configured to: deactivate the bearer of the first service on the terminal.
[0183] In some embodiments, the bearer management module 191 is further configured to: receive a bearer activation request for a second service from the network side; and activate the bearer of the second service on the terminal.
[0184] Based on the same inventive concept, this disclosure also provides a network-side device, as described in the following embodiments. Since the principle by which this network-side device solves the problem is similar to that of the above-described method embodiments, the implementation of this network-side device embodiment can refer to the implementation of the above-described method embodiments, and repeated details will not be elaborated further.
[0185] Figure 20 A schematic diagram of a network-side device according to an embodiment of this disclosure is shown below. Figure 20As shown, the terminal includes: a first bearer processing module 201, used to receive a bearer activation request for a first service on the terminal; and a second bearer processing module 202, used to suspend / deactivate / release the bearer of a second service on the terminal, so that the terminal can establish a bearer for the first service.
[0186] In this embodiment of the disclosure, the first service and the second service can be any two different services. In one embodiment, the first service can be a voice service and the second service can be a data service.
[0187] In some embodiments, the second bearer processing module 202 is further configured to: monitor whether the total number of bearers activated on the terminal has reached the bearer limit threshold; and if the total number of bearers activated on the terminal has reached the bearer limit threshold, suspend / deactivate / release the bearer of the second service on the terminal so that the terminal can establish the bearer of the first service.
[0188] In some embodiments, the second bearer processing module 202 is further configured to: determine the bearer of the second service that needs to be suspended / deactivated / released on the terminal based on configuration information and / or policy information.
[0189] In some embodiments, the second bearer processing module 202 is further configured to: send a bearer deactivation request for the second service to the terminal, so as to request the terminal to deactivate the bearer of the second service.
[0190] In some embodiments, the second bearer processing module 202 is further configured to: send a bearer release request for the second service to the base station, so as to request the base station to release the resources allocated for the bearer of the second service.
[0191] In some embodiments, the bearer deactivation request includes indication information and / or a reason value, which is used to notify the terminal that the bearer for the second service will no longer be activated.
[0192] In some embodiments, the bearer release request includes indication information and / or a reason value, which is used to notify the terminal that the bearer for the second service will no longer be activated.
[0193] In some embodiments, indication information and / or reason values are used to indicate bearers that need to be suspended / deactivated / released for data services due to the transmission of voice service data.
[0194] In some embodiments, the second bearer processing module 202 is further configured to: send a notification message to the Serving Gateway (SGW) and / or the Packet Data Network Gateway (PGW) to suspend the bearer of the second service.
[0195] In some embodiments, the notification message is used to notify the SGW and / or PGW to perform at least one of the following operations:
[0196] Buffer the received downlink data packets for the second service;
[0197] Upon receiving the downlink data packet for the second service, the Mobility Management Entity (MME) is not notified.
[0198] Delete the received downlink data packets for the second service.
[0199] In some embodiments, the second bearer processing module 202 is further configured to: restore and / or activate the bearer of the second service on the terminal when a bearer deactivation request for the first service is received.
[0200] In some embodiments, the second bearer processing module 202 is further configured to: restore and / or activate the bearer of the second service on the terminal when the total number of bearers activated on the terminal does not reach the upper limit threshold of the bearer.
[0201] In some embodiments, the second bearer processing module 202 is further configured to: send a bearer activation request for the second service to the terminal, so as to request the terminal to activate the bearer of the second service.
[0202] In some embodiments, the second bearer processing module 202 is further configured to: send a bearer establishment request for the second service to the base station to request the base station to allocate resources for the bearer of the second service.
[0203] In some embodiments, the second bearer processing module 202 is further configured to: send a notification message to the SGW and / or PGW to restore the bearer for the second service.
[0204] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the content disclosed in the above method embodiments. The above modules, as part of an apparatus, can be executed in a computer system such as a set of computer-executable instructions.
[0205] Those skilled in the art will understand that various aspects of this disclosure can be implemented as a system, method, or program product. Therefore, various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, collectively referred to herein as a "circuit," "module," or "system."
[0206] The following reference Figure 21 To describe an electronic device 2100 according to such an embodiment of the present disclosure. Figure 21 The electronic device 2100 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.
[0207] like Figure 21As shown, the electronic device 2100 is manifested in the form of a general-purpose computing device. The components of the electronic device 2100 may include, but are not limited to: at least one processing unit 2110, at least one storage unit 2120, and a bus 2130 connecting different system components (including storage unit 2120 and processing unit 2110).
[0208] The storage unit stores program code that can be executed by the processing unit 2110, causing the processing unit 2110 to perform the steps described in the "Exemplary Methods" section above according to various exemplary embodiments of this disclosure.
[0209] In some embodiments, when the electronic device is a terminal, the processing unit 2110 may perform the following steps of the above method embodiment: suspend / deactivate / release the bearer of the second service on the terminal to establish the bearer of the first service on the terminal.
[0210] In other embodiments, when the electronic device is a network-side device, the processing unit 2110 may perform the following steps of the above method embodiments: receiving a bearer activation request for a first service on the terminal; suspending / deactivating / releasing the bearer of a second service on the terminal, so that the terminal establishes the bearer of the first service.
[0211] Storage unit 2120 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 21201 and / or a cache memory unit 21202, and may further include a read-only memory unit (ROM) 21203.
[0212] Storage unit 2120 may also include a program / utility 21204 having a set (at least one) program module 21205, such program module 21205 including but not limited to: operating system, one or more application programs, other program modules and program data, each or some combination of these examples may include an implementation of a network environment.
[0213] Bus 2130 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.
[0214] Electronic device 2100 can also communicate with one or more external devices 2140 (e.g., keyboard, pointing device, Bluetooth device, etc.), one or more devices that enable a user to interact with electronic device 2100, and / or any device that enables electronic device 2100 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 2150. Furthermore, electronic device 2100 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 2160. As shown, network adapter 2160 communicates with other modules of electronic device 2100 via bus 2130. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with electronic device 2100, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0215] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.
[0216] Based on the same inventive concept, this disclosure also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the link processing method described above. Since the principle by which this computer-readable storage medium embodiment solves the problem is similar to that of the above method embodiments, the implementation of this computer-readable storage medium embodiment can refer to the implementation of the above method embodiments, and repeated details will not be elaborated further.
[0217] More specific examples of computer-readable storage media in this disclosure may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.
[0218] In this disclosure, a computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of transmitting, propagating, or transmitting a program for use by or in connection with an instruction execution system, apparatus, or device.
[0219] Optionally, the program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.
[0220] In practical implementation, program code for performing the operations of this disclosure can be written in any combination of one or more programming languages, including object-oriented programming languages such as Java and C++, and conventional procedural programming languages such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).
[0221] Based on the same inventive concept, this disclosure also provides a computer program product, including a computer program or instructions, which, when executed by a processor, implements the linking processing method of any one of the above method embodiments. Since the principle by which this computer program product embodiment solves the problem is similar to that of the above method embodiments, the implementation of this computer program product embodiment can refer to the implementation of the above method embodiments, and repeated details will not be elaborated further.
[0222] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.
[0223] Furthermore, although the steps of the method in this disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or a step may be broken down into multiple steps.
[0224] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or network device, etc.) to execute the methods according to the embodiments of this disclosure.
[0225] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the appended claims.
Claims
1. A connection processing method, characterized in that, Applied to terminals, including: Suspend / deactivate / release the bearer of the second service on the terminal to establish the bearer of the first service on the terminal.
2. The connection processing method according to claim 1, characterized in that, Suspending / deactivating / releasing the second service bearer on the terminal includes: Receive a bearer deactivation request for the second service from the network side; Suspend / deactivate the bearer of the second service.
3. The connection processing method according to claim 1, characterized in that, Suspend / deactivate / release the bearer of the second service on the terminal to establish the bearer of the first service on the terminal, including: Receive a bearer release request for the second service from the base station; Suspend / release the bearer of the second service.
4. The connection processing method according to claim 2, characterized in that, The bearer deactivation request includes indication information and / or a reason value, which is used to notify the terminal that the bearer of the second service will no longer be activated.
5. The connection processing method according to claim 3, characterized in that, The bearer release request includes indication information and / or a reason value, which is used to notify the terminal that the bearer of the second service will no longer be activated.
6. The connection processing method according to claim 4 or 5, characterized in that, The indication information and / or reason value are used to indicate the bearer that needs to suspend / deactivate / release data services due to the transmission of voice service data.
7. The connection processing method according to claim 1, characterized in that, After suspending / deactivating / releasing the bearer of the second service on the terminal to establish the bearer of the first service on the terminal, the method further includes: Deactivate the bearer of the first service on the terminal.
8. The connection processing method according to claim 7, characterized in that, After deactivating the bearer of the first service on the terminal, the method further includes: Receive a bearer activation request for the second service from the network side; Activate the carrying of the second service on the terminal.
9. The connection processing method according to any one of claims 1 to 8, characterized in that, The first service is a voice service, and the second service is a data service.
10. A connection processing method, characterized in that, Applied to the Mobility Management Entity (MME), including: Received a bearer activation request for the first service on the terminal; Suspend / deactivate / release the bearer of the second service on the terminal so that the terminal can establish the bearer of the first service.
11. The connection processing method according to claim 10, characterized in that, Suspending / deactivating / releasing the bearer of the second service on the terminal, so that the terminal can establish the bearer of the first service, includes: Monitor whether the total number of active bearers on the terminal has reached the upper limit threshold; If the total number of active bearers on the terminal has reached the upper limit threshold of the bearer, the bearer of the second service on the terminal is suspended / deactivated / released so that the terminal can establish the bearer of the first service.
12. The connection processing method according to claim 10, characterized in that, The method further includes: Based on configuration information and / or policy information, determine the bearer of the second service that needs to be suspended / deactivated / released on the terminal.
13. The connection processing method according to claim 10, characterized in that, Suspending / deactivating / releasing the bearer of the second service on the terminal, so that the terminal can establish the bearer of the first service, includes: Send a second service bearer deactivation request to the terminal to request the terminal to deactivate the second service bearer.
14. The connection processing method according to claim 10, characterized in that, Suspending / deactivating / releasing the bearer of the second service on the terminal, so that the terminal can establish the bearer of the first service, includes: Send a bearer release request for the second service to the base station to request the base station to release the resources allocated for the bearer of the second service.
15. The connection processing method according to claim 13, characterized in that, The bearer deactivation request includes indication information and / or a reason value, which is used to notify the terminal that the bearer of the second service will no longer be activated.
16. The connection processing method according to claim 14, characterized in that, The bearer release request includes indication information and / or a reason value, which is used to notify the terminal that the bearer of the second service will no longer be activated.
17. The connection processing method according to claim 15 or 16, characterized in that, The indication information and / or reason value are used to indicate the bearer that needs to suspend / deactivate / release data services due to the transmission of voice service data.
18. The connection processing method according to claim 10, characterized in that, The method further includes: Send a notification message to the Serving Gateway (SGW) and / or Packet Data Network Gateway (PGW) to suspend the bearer of the second service.
19. The connection processing method according to claim 18, characterized in that, The notification message is used to notify the SGW and / or PGW to perform at least one of the following operations: Buffer the received downlink data packets of the second service; Upon receiving the downlink data packet of the second service, the Mobility Management Entity (MME) is not notified. Delete the received downlink data packets of the second service.
20. The connection processing method according to claim 10, characterized in that, After suspending / deactivating / releasing the bearer of the second service on the terminal to enable the terminal to establish the bearer of the first service, the method further includes: Upon receiving a request to deactivate the bearer of the first service, the bearer of the second service on the terminal is restored and / or activated.
21. The connection processing method according to claim 11, characterized in that, After suspending / deactivating / releasing the bearer of the second service on the terminal to enable the terminal to establish the bearer of the first service, the method further includes: If the total number of active bearers on the terminal does not reach the upper limit threshold, the bearer of the second service on the terminal shall be restored and / or activated.
22. The connection processing method according to claim 20 or 21, characterized in that, Restoring and / or activating the bearer of the second service on the terminal includes: Send a second service bearer activation request to the terminal to request the terminal to activate the bearer of the second service.
23. The connection processing method according to claim 20 or 21, characterized in that, Restoring and / or activating the bearer of the second service on the terminal includes: Send a bearer establishment request for the second service to the base station to request the base station to allocate resources for the bearer of the second service.
24. The connection processing method according to claim 20 or 21, characterized in that, Restoring and / or activating the bearer of the second service on the terminal includes: Send a notification message to the SGW and / or PGW to restore the bearer of the second service.
25. The connection processing method according to any one of claims 10 to 24, characterized in that, The first service is a voice service; the second service is a data service.
26. A terminal, characterized in that, include: The bearer management module is used to suspend / deactivate / release the bearer of the second service on the terminal in order to establish the bearer of the first service on the terminal.
27. A network-side device, characterized in that, include: The first bearer processing module is used to receive a bearer activation request for the first service on the terminal; The second bearer processing module is used to suspend / deactivate / release the bearer of the second service on the terminal so that the terminal can establish the bearer of the first service.
28. A communication system, characterized in that, include: Terminal and network-side equipment; The network-side device is used to suspend / deactivate / release the bearer of the second service on the terminal; The terminal is used to establish the bearer for the first service.
29. An electronic device, characterized in that, include: processor; as well as Memory for storing the executable instructions of the processor; The processor is configured to execute the connection processing method according to any one of claims 1 to 25 by executing the executable instructions.
30. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the connection processing method according to any one of claims 1 to 25.
31. A computer program product, comprising: A computer program or instruction, characterized in that, when executed by a processor, the computer program or instruction implements the connection processing method according to any one of claims 1 to 25.
