CN114071594B - Service maintaining method, device, computer equipment and storage medium - Google Patents

Service maintaining method, device, computer equipment and storage medium Download PDF

Info

Publication number
CN114071594B
CN114071594B CN202010761571.2A CN202010761571A CN114071594B CN 114071594 B CN114071594 B CN 114071594B CN 202010761571 A CN202010761571 A CN 202010761571A CN 114071594 B CN114071594 B CN 114071594B
Authority
CN
China
Prior art keywords
network
target service
fallback
service
pdu session
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010761571.2A
Other languages
Chinese (zh)
Other versions
CN114071594A (en
Inventor
范伟
金逸
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Spreadtrum Communications Shanghai Co Ltd
Original Assignee
Spreadtrum Communications Shanghai Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Spreadtrum Communications Shanghai Co Ltd filed Critical Spreadtrum Communications Shanghai Co Ltd
Priority to CN202010761571.2A priority Critical patent/CN114071594B/en
Publication of CN114071594A publication Critical patent/CN114071594A/en
Application granted granted Critical
Publication of CN114071594B publication Critical patent/CN114071594B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection

Landscapes

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

Abstract

The invention provides a service maintaining method, a device, a computer device and a storage medium, wherein the method comprises the following steps: when the network fallback condition is met, acquiring the running target service; judging whether the target service can continue to run after the network falls back according to the PDU session corresponding to the target service; if the target service can continue to run after the network is dropped, a request for activating the PDP context corresponding to the target service is sent to the network side after the network is dropped, otherwise, a request for activating the PDP context corresponding to the target service is not sent to the network side after the network is dropped. The invention can prevent the interruption of the running service caused by network fallback and improve the user experience.

Description

Service maintaining method, device, computer equipment and storage medium
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a service maintenance method, a service maintenance device, a computer device, and a storage medium.
Background
The 3GPP (Third Generation Partnership Project ) introduces SRVCC (Single Radio Voice Call Continuity, voice service continuity) handover technology in Release16 protocol, for smooth handover of voice service in the packet Switched (PACKET SWITCH, PS) domain under 5G NR (New Radio) to voice service in the Circuit Switched (CS) domain of a 3G WCDMA (Wideband Code Division Multiple Access ) network.
In a communication system, service data is transmitted between different devices mainly through session. For example, the service data may be transmitted between the terminal and the network device through PDU (protocol data unit ) session (refer to 3GPP TS 38.415version 15.1.0Release 15 for PDU session).
When the SRVCC handover is over, all PDU sessions (except for the bearer PDU Session for the voice service that has been handed over to the 3G CS domain) will be released. These PDU sessions, when released, will cause interruption of other non-voice services in progress by the user, and may affect the user experience. For example, when the SRVCC handover is finished, the PDU Session carrying the APP networking service is released, so that the APP cannot be networked, and the user cannot conduct APP operation synchronously according to voice guidance of customer service personnel, so that the user experience is poor.
Disclosure of Invention
In view of the foregoing drawbacks of the prior art, an object of the present invention is to provide a service maintenance method, apparatus, computer device, and storage medium, so that an ongoing service is not interrupted by a network fallback.
In order to achieve the above object, the present invention provides a service maintenance method, including:
When the network fallback condition is met, acquiring the running target service;
judging whether the target service can continue to run after the network falls back according to the PDU session corresponding to the target service;
If the target service can continue to run after the network is dropped, a request for activating the PDP context corresponding to the target service is sent to the network side after the network is dropped, otherwise, a request for activating the PDP context corresponding to the target service is not sent to the network side after the network is dropped.
In a preferred embodiment of the invention, the network fallback comprises fallback from a 5G network to a 3G network.
In a preferred embodiment of the present invention, the step of determining whether the target service can continue to operate after the network falls back according to the PDU session corresponding to the target service includes:
Judging whether PDU session corresponding to the target service meets a preset condition, if so, judging that the target service can not continue to run after the network is dropped, otherwise, judging that the target service can continue to run after the network is dropped;
wherein the preset condition is any one of the following conditions:
the user plane of the PDU session corresponding to the target service needs to use integrity protection;
the PDU session corresponding to the target service is of the Ethernet type;
The PDU session corresponding to the target service is of an unstructured data type;
The PDU session corresponding to the target service has QoS Flow with the resource type of DELAY CRITICAL GBR;
The PDU session corresponding to the target service has a QoS Flow with a GBR resource type, and the time delay of a data packet of the QoS Flow is smaller than the preset time delay;
and the PDU session corresponding to the target service has a QoS Flow with the resource type GBR, and the guaranteed stream bit rate or the maximum stream bit rate of the QoS Flow is larger than the preset maximum rate.
In a preferred embodiment of the invention, the method further comprises: and when the target service cannot run continuously after the network fallback, judging whether the priority of the target service is preset to be higher than the priority of the designated service to be carried out by the network fallback, and if so, refusing to execute the network fallback.
In a preferred embodiment of the present invention, the step of refusing to execute the network fallback is implemented by refusing to report the measurement report of the network to which fallback is required or refusing to execute the blind handover of the network configuration.
In order to achieve the above object, the present invention provides a service maintenance apparatus comprising:
the acquisition module is used for acquiring the running target service when the network fallback condition is met;
the first judging module is used for judging whether the target service can continue to run after the network falls back according to the PDU session corresponding to the target service;
The maintenance module is used for sending a request for activating the PDP context corresponding to the target service to the network side after the network fallback when the target service can run subsequently after the network fallback;
And the interruption module is used for not sending a request for activating the PDP context corresponding to the target service to the network side after the network fallback when the target service cannot run subsequently after the network fallback.
In a preferred embodiment of the invention, the network fallback comprises fallback from a 5G network to a 3G network.
In a preferred embodiment of the present invention, the judging module is specifically configured to judge whether a PDU session corresponding to the target service meets a preset condition, if so, determine that the target service cannot continue to operate after the network drops, otherwise, determine that the target service can continue to operate after the network drops;
wherein the preset condition is any one of the following conditions:
the user plane of the PDU session corresponding to the target service needs to use integrity protection;
the PDU session corresponding to the target service is of the Ethernet type;
The PDU session corresponding to the target service is of an unstructured data type;
The PDU session corresponding to the target service has QoS Flow with the resource type of DELAY CRITICAL GBR;
The PDU session corresponding to the target service has a QoS Flow with a GBR resource type, and the time delay of a data packet of the QoS Flow is smaller than the preset time delay;
and the PDU session corresponding to the target service has a QoS Flow with the resource type GBR, and the guaranteed stream bit rate or the maximum stream bit rate of the QoS Flow is larger than the preset maximum rate.
In a preferred embodiment of the invention, the device further comprises:
The second judging module is used for judging whether the priority of the target service is preset to be higher than the priority of the appointed service to be carried out by network fallback or not when the target service cannot be operated subsequently after the network fallback;
and the fallback prohibiting module is used for refusing to execute the network fallback when the priority of the target service is preconfigured to be higher than the priority of the designated service to be executed by the network fallback.
In a preferred embodiment of the present invention, the fallback prohibiting module refuses to execute the step of network fallback by refusing to report a measurement report of the network to which fallback is required or refusing to execute blind handover of network configuration.
To achieve the above object, the present invention also provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, which processor implements the steps of the aforementioned method when executing the computer program.
In order to achieve the above object, the present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the aforementioned method.
Through the technical scheme, the invention has the following beneficial effects:
The invention judges whether the target service can continue to run after the network falls back according to the PDU session corresponding to the target service; if the target service can continue to run after the network falls back, a request for activating the PDP context corresponding to the target service is sent to the network side after the network falls back, so that running service interruption caused by the network falling back is avoided, and user experience is improved.
Drawings
Fig. 1 is a flowchart of a service maintenance method according to embodiment 1 of the present invention;
Fig. 2 is a flowchart of a service maintenance method according to embodiment 2 of the present invention;
fig. 3 is a block diagram of a service maintenance device according to embodiment 3 of the present invention;
Fig. 4 is a block diagram of a service maintenance device according to embodiment 4 of the present invention;
Fig. 5 is a hardware architecture diagram of an electronic device according to embodiment 5 of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
Example 1
The present embodiment provides a service maintenance method, so that a service in progress by a terminal is not interrupted due to network fallback, as shown in fig. 1, including the following steps:
S1, when a network fallback condition is met, acquiring the running target service.
In this embodiment, the network fallback is, for example, fallback from the 5G network to the 3G network according to SRVCC handover technology or the like, so as to complete the specified service, such as the voice service. Of course, besides falling back through the SRVCC handover technology, the network handover may also be performed based on the needs of the user or other various possible application scenarios, which is not limited in any way by the present invention.
When the network fallback condition is met, one or more services may be running. For example, when the voice service of the terminal is started, the SRVCC handover condition is satisfied, the terminal falls back from the 5G network to the 3G network to operate the voice service, and if the networking service of a certain APP is running, the networking service of the APP is taken as the target service. After SRVCC switching is finished, PDU Session carrying the APP networking service is released, if the APP cannot be networked after switching according to the prior art, a user cannot synchronously perform corresponding APP operation according to voice guidance of customer service personnel.
And S2, judging whether the target service can continue to run after the network falls back according to the PDU session corresponding to the target service, if so, executing the step S3, and if not, executing the step S4. When the network fallback refers to fallback from the 5G network to the 3G network, the present embodiment adopts the following policy to determine whether the target service can continue to operate after the network fallback:
(1) When the user plane of the PDU session corresponding to the target service has started integrity protection and an instruction that the application layer explicitly indicates that the user plane of the PDU session does not force to use the integrity protection (i.e., the user plane of the PDU session must use the integrity protection) is not received, it is determined that the target service cannot continue to operate after the network falls back, because the 5G network supports the user plane integrity protection and the 3G network does not support the user plane integrity protection. And when the user plane of the PDU session corresponding to the target service does not start integrity protection or receives an instruction that the application layer explicitly indicates that the user plane of the PDU session does not force to use the integrity protection although the integrity protection is started, judging that the target service can continue to run after the network falls back.
(2) When the PDU Session Type (PDU Session Type) corresponding to the target service is an Ethernet (Ethernet) Type, it is determined that the target service cannot continue to operate after the network drops, because the 3G network does not support the Ethernet Type.
(3) When the PDU session type corresponding to the target service is an Unstructured data (Unstructured) type, the target service is judged to be unable to continue to run after the network drops, because the 3G network does not support the Unstructured data type.
(4) According to standard TS 23.501, section 5.7.3, there are at least three types of QoS (quality of service) resource types in 5G, respectively a guaranteed rate (GBR) type, a Non-guaranteed rate (Non-GBR) type, and a delay critical guaranteed rate (DELAY CRITICAL GBR) type. And when the PDU session corresponding to the target service has QoS Flow (quality service Flow) with the resource type of DELAY CRITICAL GBR, judging that the target service cannot continue to run after the network falls back, wherein the 3G network does not support the QoS Flow with the resource type of DELAY CRITICAL GBR.
(5) And when the PDU session corresponding to the target service has a QoS Flow with the resource type GBR and the data packet delay (PACKET DELAY Budget) of the QoS Flow is smaller than the preset delay (such as 200 ms), judging that the target service cannot continue to run after the network falls back. The preset delay is preferably set to be the minimum delay supported by the 3G network, and when the packet delay of the QoS Flow is smaller than the preset delay, the 3G network will not support.
(6) And when the PDU session corresponding to the target service has a QoS Flow with the resource type GBR, and the guaranteed stream bit rate (Guaranteed Flow Bit Rate, GFBR, one of the uplink and the downlink) or the maximum stream bit rate (Maximum Flow Bit Rate, MFBR, one of the uplink and the downlink) of the QoS Flow is greater than the preset maximum rate (one of the uplink and the downlink), judging that the target service cannot continue to run after the network falls back. Wherein the preset maximum rate is set to be a maximum rate supported by the 3G network, and when the preset maximum rate is greater than the maximum rate, the 3G network will not support.
In summary, all the above six cases determine that the target service cannot continue to operate after the network falls back, and all the other cases determine that the target service can continue to operate after the network falls back.
And S3, when the target service is judged to be capable of running subsequently after the network falls back, a request for activating a PDP (PACKET DATA Protocol ) Context corresponding to the target service is sent to the network side after the network falls back. A PDP context provides a packet connection for exchanging IP packets between the terminal and the network side. The data packet connection can be used for maintaining the continuous operation of the target service.
After receiving the foregoing activation request, the network side will activate the PDP Context corresponding to the target service, and the specific activation process may refer to the standard TS24.008, section 6.1.3.1, and will not be described herein.
And S4, when the target service is judged to be unable to run subsequently after the network falls back, a request for activating the PDP context corresponding to the target service is not sent to the network side after the network falls back.
In this embodiment, whether the target service can continue to run after the network drops is determined according to the PDU session corresponding to the target service, if the target service can continue to run after the network drops, a request for activating the PDP context corresponding to the target service is sent to the network side after the network drops, so that the running service is prevented from being interrupted after the network drops, and the user experience is improved.
Example 2
As shown in fig. 2, this embodiment adds the following steps after step S2 of embodiment 1:
s4', when the target service is judged to be unable to run subsequently after the network fallback, continuing to judge whether the priority of the target service is configured to be higher than the priority of the designated service to be carried out by the network fallback, if so, executing the step S5, otherwise, executing the step S4;
s5, refusing to execute the network fallback. The step of refusing to execute the network fallback is realized by refusing to report the measurement report of the network to which the network needs to fall back or refusing to execute the blind switching of the network configuration.
For example, when the network fallback is from the 5G network to the 3G network according to the SRVCC handover technique, and the designated service to be performed by the network fallback is a voice service, the embodiment determines whether the priority of the target service is configured to be higher than the priority of the voice service after step S2, and if yes, does not perform the SRVCC handover. The step of not performing the SRVCC handover is implemented by refusing to report the measurement report of the 3G neighbor cell or refusing to perform the blind SRVCC handover of the network configuration.
In this embodiment, the priority of the service may be autonomously configured in advance by the terminal, or configured by an operator (configured by a NAS (Non-Access Stratum) signaling configuration policy or pre-configured, for example, in a USIM (Universal Subscriber Identity Module) card/NV (nonvolatile memory) of the terminal), or configured by a service provider (configured by an application layer protocol configuration policy or pre-configured, for example, in a USIM card/NV of the terminal/in a secure memory).
In this embodiment, when the target service cannot continue to run after the network fallback, and the priority of the target service is configured to be higher than the priority of the designated service to be performed by the network fallback, the execution of the network fallback is refused, so as to ensure that the target service with high priority is not interrupted by the network fallback.
Example 3
The present embodiment provides a service maintenance device so that a service in progress by a terminal is not interrupted by network fallback, as shown in fig. 3, the device 1 includes an acquisition module 11, a first determination module 12, a maintenance module 13, and an interruption module 14. The following describes each module in detail:
the acquiring module 11 is configured to acquire the running target service when the network fallback condition is satisfied.
In this embodiment, the network fallback is, for example, fallback from the 5G network to the 3G network according to SRVCC handover technology or the like, so as to complete the specified service, such as the voice service. Of course, besides falling back through the SRVCC handover technology, the network handover may also be performed based on the needs of the user or other various possible application scenarios, which is not limited in any way by the present invention.
When the network fallback condition is met, one or more services may be running. For example, when the voice service of the terminal is started, the SRVCC handover condition is satisfied, the terminal falls back from the 5G network to the 3G network to operate the voice service, and if the networking service of a certain APP is running, the networking service of the APP is taken as the target service. After SRVCC switching is finished, PDU Session carrying the APP networking service is released, if the APP cannot be networked after switching according to the prior art, a user cannot synchronously perform corresponding APP operation according to voice guidance of customer service personnel.
The first judging module 12 is configured to judge whether the target service can continue to operate after the network drops according to the PDU session corresponding to the target service. When the network fallback refers to fallback from the 5G network to the 3G network, the present embodiment adopts the following policy to determine whether the target service can continue to operate after the network fallback:
(1) When the user plane of the PDU session corresponding to the target service has started integrity protection and an instruction that the application layer explicitly indicates that the user plane of the PDU session does not force to use the integrity protection (i.e., the user plane of the PDU session must use the integrity protection) is not received, it is determined that the target service cannot continue to operate after the network falls back, because the 5G network supports the user plane integrity protection and the 3G network does not support the user plane integrity protection. And when the user plane of the PDU session corresponding to the target service does not start integrity protection or receives an instruction that the application layer explicitly indicates that the user plane of the PDU session does not force to use the integrity protection although the integrity protection is started, judging that the target service can continue to run after the network falls back.
(2) When the PDU Session Type (PDU Session Type) corresponding to the target service is an Ethernet (Ethernet) Type, it is determined that the target service cannot continue to operate after the network drops, because the 3G network does not support the Ethernet Type.
(3) When the PDU session type corresponding to the target service is an Unstructured data (Unstructured) type, the target service is judged to be unable to continue to run after the network drops, because the 3G network does not support the Unstructured data type.
(4) According to standard TS 23.501, section 5.7.3, there are at least three types of QoS (quality of service) resource types in 5G, respectively a guaranteed rate (GBR) type, a Non-guaranteed rate (Non-GBR) type, and a delay critical guaranteed rate (DELAY CRITICAL GBR) type. And when the PDU session corresponding to the target service has QoS Flow (quality service Flow) with the resource type of DELAY CRITICAL GBR, judging that the target service cannot continue to run after the network falls back, wherein the 3G network does not support the QoS Flow with the resource type of DELAY CRITICAL GBR.
(5) And when the PDU session corresponding to the target service has a QoS Flow with the resource type GBR and the data packet delay (PACKET DELAY Budget) of the QoS Flow is smaller than the preset delay (such as 200 ms), judging that the target service cannot continue to run after the network falls back. The preset delay is preferably set to be the minimum delay supported by the 3G network, and when the packet delay of the QoS Flow is smaller than the preset delay, the 3G network will not support.
(6) And when the PDU session corresponding to the target service has a QoS Flow with the resource type GBR, and the guaranteed stream bit rate (Guaranteed Flow Bit Rate, GFBR, one of the uplink and the downlink) or the maximum stream bit rate (Maximum Flow Bit Rate, MFBR, one of the uplink and the downlink) of the QoS Flow is greater than the preset maximum rate (one of the uplink and the downlink), judging that the target service cannot continue to run after the network falls back. Wherein the preset maximum rate is set to be a maximum rate supported by the 3G network, and when the preset maximum rate is greater than the maximum rate, the 3G network will not support.
In summary, all the above six cases determine that the target service cannot continue to operate after the network falls back, and all the other cases determine that the target service can continue to operate after the network falls back.
The maintenance module 13 is configured to send, when it is determined that the target service can run subsequently after the network fallback, a request for activating a PDP (PACKET DATA Protocol ) Context corresponding to the target service to the network side after the network fallback.
A PDP context provides a packet connection for exchanging IP packets between the terminal and the network side. The data packet connection can be used for maintaining the continuous operation of the target service. After receiving the foregoing activation request, the network side will activate the PDP Context corresponding to the target service, and the specific activation process may refer to the standard TS24.008, section 6.1.3.1, and will not be described herein.
The interruption module 14 is configured to, when it is determined that the target service can run subsequently after the network fallback, not send a request for activating a PDP context corresponding to the target service to the network side after the network fallback.
In this embodiment, whether the target service can continue to run after the network drops is determined according to the PDU session corresponding to the target service, if the target service can continue to run after the network drops, a request for activating the PDP context corresponding to the target service is sent to the network side after the network drops, so that the running service is prevented from being interrupted after the network drops, and the user experience is improved.
Example 4
As shown in fig. 4, this embodiment is based on embodiment 3, with the addition of a second judging module 15 and a fall-back prohibiting module 16. The second determining module 15 is configured to determine, when the target service cannot be run subsequently to the network fallback, whether the priority of the target service is configured to be higher than the priority of the designated service to be performed by the network fallback, if so, call the fallback prohibiting module 16 to refuse to perform the network fallback, otherwise, perform the network fallback and call the interrupting module 14. The rejection of the network fallback is achieved by rejecting reporting of a measurement report of the network to which fallback is required or rejecting execution of blind handover of network configuration.
For example, when the network fallback is to fall back from the 5G network to the 3G network according to the SRVCC handover technique, the designated service to be performed by the network fallback is a voice service. The second determining module 15 is configured to determine whether the priority of the target service is configured to be higher than the priority of the voice service, and if so, call the fallback prohibiting module 16 to refuse to execute the SRVCC handover. The step of refusing to execute the SRVCC switching is realized by refusing to report the measurement report of the 3G neighbor cell or refusing to execute the blind SRVCC switching of the network configuration.
In this embodiment, the priority of the traffic may be autonomously configured in advance by the terminal, or configured by the operator (by NAS signaling configuration policies or e.g. in the NV of the USIM card/terminal), or configured by the service provider (by application layer protocol configuration policies or e.g. in the NV of the USIM card/terminal/secure memory).
In this embodiment, when the target service cannot continue to run after the network fallback, and the priority of the target service is configured to be higher than the priority of the designated service to be performed by the network fallback, the execution of the network fallback is refused, so as to ensure that the target service with high priority is not interrupted by the network fallback.
Example 5
The present embodiment provides an electronic device, which may be expressed in the form of a computing device (for example, may be a server device), including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor may implement the service maintenance method provided in embodiment 1 or 2 when executing the computer program.
Fig. 5 shows a schematic diagram of the hardware structure of the present embodiment, and as shown in fig. 5, the electronic device 9 specifically includes:
at least one processor 91, at least one memory 92, and a bus 93 for connecting the different system components (including the processor 91 and the memory 92), wherein:
the bus 93 includes a data bus, an address bus, and a control bus.
The memory 92 includes volatile memory such as Random Access Memory (RAM) 921 and/or cache memory 922, and may further include Read Only Memory (ROM) 923.
Memory 92 also includes a program/utility 925 having a set (at least one) of program modules 924, such program modules 924 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
The processor 91 executes various functional applications and data processing such as the service maintaining method provided in embodiment 1 or 2 of the present invention by running a computer program stored in the memory 92.
The electronic device 9 may further communicate with one or more external devices 94 (e.g., keyboard, pointing device, etc.). Such communication may occur through an input/output (I/O) interface 95. Also, the electronic device 9 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through a network adapter 96. The network adapter 96 communicates with other modules of the electronic device 9 via the bus 93. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in connection with the electronic device 9, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, data backup storage systems, and the like.
It should be noted that although several units/modules or sub-units/modules of an electronic device are mentioned in the above detailed description, such a division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more units/modules described above may be embodied in one unit/module in accordance with embodiments of the present application. Conversely, the features and functions of one unit/module described above may be further divided into ones that are embodied by a plurality of units/modules.
Example 6
The present embodiment provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the service maintenance method provided in embodiment 1 or 2.
More specifically, among others, readable storage media may be employed including, but not limited to: portable disk, hard disk, random access memory, read only memory, erasable programmable read only memory, optical storage device, magnetic storage device, or any suitable combination of the foregoing.
In a possible embodiment, the invention may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps of implementing the service maintenance method as described in embodiment 1 or 2, when said program product is run on the terminal device.
Wherein the program code for carrying out the invention may be written in any combination of one or more programming languages, which program code may execute entirely on the user device, partly on the user device, as a stand-alone software package, partly on the user device and partly on the remote device or entirely on the remote device.
While specific embodiments of the invention have been described above, it will be appreciated by those skilled in the art that this is by way of example only, and the scope of the invention is defined by the appended claims. Various changes and modifications to these embodiments may be made by those skilled in the art without departing from the principles and spirit of the invention, but such changes and modifications fall within the scope of the invention.

Claims (12)

1. A service maintenance method, comprising:
When the network fallback condition is met, acquiring the running target service;
judging whether the target service can continue to run after the network falls back according to the PDU session corresponding to the target service;
if the target service can continue to run after the network is dropped, a request for activating the PDP context corresponding to the target service is sent to a network side after the network is dropped, otherwise, a request for activating the PDP context corresponding to the target service is not sent to the network side after the network is dropped;
the step of judging whether the target service can continue to run after the network falls back according to the PDU session corresponding to the target service comprises the following steps:
Judging whether the PDU session corresponding to the target service meets the preset condition, if so, judging that the target service can not continue to run after the network is dropped, otherwise, judging that the target service can continue to run after the network is dropped.
2. The traffic maintenance method according to claim 1, wherein the network fallback comprises fallback from a 5G network to a 3G network.
3. The service maintenance method according to claim 2, wherein the preset condition is any one of the following conditions:
the user plane of the PDU session corresponding to the target service needs to use integrity protection;
the PDU session corresponding to the target service is of the Ethernet type;
The PDU session corresponding to the target service is of an unstructured data type;
The PDU session corresponding to the target service has QoS Flow with the resource type of DELAY CRITICAL GBR;
The PDU session corresponding to the target service has a QoS Flow with a GBR resource type, and the time delay of a data packet of the QoS Flow is smaller than the preset time delay;
and the PDU session corresponding to the target service has a QoS Flow with the resource type GBR, and the guaranteed stream bit rate or the maximum stream bit rate of the QoS Flow is larger than the preset maximum rate.
4. The service maintenance method according to claim 1, characterized in that the method further comprises: and when the target service cannot run continuously after the network fallback, judging whether the priority of the target service is preset to be higher than the priority of the designated service to be carried out by the network fallback, and if so, refusing to execute the network fallback.
5. The service maintenance method according to claim 4, wherein the step of refusing to perform network fallback is performed by refusing to report a measurement report of a network to which fallback is required or refusing to perform blind handover of network configuration.
6. A service maintenance device, comprising:
the acquisition module is used for acquiring the running target service when the network fallback condition is met;
the first judging module is used for judging whether the target service can continue to run after the network falls back according to the PDU session corresponding to the target service;
The maintenance module is used for sending a request for activating the PDP context corresponding to the target service to the network side after the network fallback when the target service can run subsequently after the network fallback;
An interruption module, configured to, when the target service cannot run subsequently after the network fallback, not send a request for activating a PDP context corresponding to the target service to the network side after the network fallback;
The first judging module is specifically configured to judge whether a PDU session corresponding to the target service meets a preset condition, if yes, determine that the target service cannot continue to operate after the network drops, otherwise, determine that the target service can continue to operate after the network drops.
7. The traffic maintenance device according to claim 6, wherein the network fallback comprises fallback from a 5G network to a 3G network.
8. The service maintenance device according to claim 7, wherein the preset condition is any one of the following conditions:
the user plane of the PDU session corresponding to the target service needs to use integrity protection;
the PDU session corresponding to the target service is of the Ethernet type;
The PDU session corresponding to the target service is of an unstructured data type;
The PDU session corresponding to the target service has QoS Flow with the resource type of DELAY CRITICAL GBR;
The PDU session corresponding to the target service has a QoS Flow with a GBR resource type, and the time delay of a data packet of the QoS Flow is smaller than the preset time delay;
and the PDU session corresponding to the target service has a QoS Flow with the resource type GBR, and the guaranteed stream bit rate or the maximum stream bit rate of the QoS Flow is larger than the preset maximum rate.
9. The service maintenance device according to claim 6, wherein the device further comprises:
The second judging module is used for judging whether the priority of the target service is preset to be higher than the priority of the appointed service to be carried out by network fallback or not when the target service cannot be operated subsequently after the network fallback;
and the fallback prohibiting module is used for refusing to execute the network fallback when the priority of the target service is preconfigured to be higher than the priority of the designated service to be executed by the network fallback.
10. The service maintenance device according to claim 9, wherein the fallback prohibition module performs the step of refusing to execute the network fallback by refusing to report the measurement report of the network to which fallback is required or refusing to execute the blind handover of the network configuration.
11. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any one of claims 1 to 5 when the computer program is executed.
12. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method according to any one of claims 1 to 5.
CN202010761571.2A 2020-07-31 2020-07-31 Service maintaining method, device, computer equipment and storage medium Active CN114071594B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010761571.2A CN114071594B (en) 2020-07-31 2020-07-31 Service maintaining method, device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010761571.2A CN114071594B (en) 2020-07-31 2020-07-31 Service maintaining method, device, computer equipment and storage medium

Publications (2)

Publication Number Publication Date
CN114071594A CN114071594A (en) 2022-02-18
CN114071594B true CN114071594B (en) 2024-06-07

Family

ID=80227751

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010761571.2A Active CN114071594B (en) 2020-07-31 2020-07-31 Service maintaining method, device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114071594B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105228207A (en) * 2014-05-27 2016-01-06 中国移动通信集团浙江有限公司 A kind of method and device of verifying LTE network circuit domain dropping CSFB functional configuration
WO2016138695A1 (en) * 2015-03-05 2016-09-09 宇龙计算机通信科技(深圳)有限公司 Vo-LTE TERMINAL DATA SERVICE RECOVERY CONTROL METHOD, SYSTEM, AND TERMINAL
CN110049518A (en) * 2018-01-15 2019-07-23 中兴通讯股份有限公司 A kind of voice fallback processing method and processing device
CN110519808A (en) * 2018-05-21 2019-11-29 维沃移动通信有限公司 The method, apparatus and system of interaction between a kind of network
CN111405682A (en) * 2020-03-19 2020-07-10 中国联合网络通信集团有限公司 Data forwarding method and gateway

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105228207A (en) * 2014-05-27 2016-01-06 中国移动通信集团浙江有限公司 A kind of method and device of verifying LTE network circuit domain dropping CSFB functional configuration
WO2016138695A1 (en) * 2015-03-05 2016-09-09 宇龙计算机通信科技(深圳)有限公司 Vo-LTE TERMINAL DATA SERVICE RECOVERY CONTROL METHOD, SYSTEM, AND TERMINAL
CN110049518A (en) * 2018-01-15 2019-07-23 中兴通讯股份有限公司 A kind of voice fallback processing method and processing device
CN110519808A (en) * 2018-05-21 2019-11-29 维沃移动通信有限公司 The method, apparatus and system of interaction between a kind of network
CN111405682A (en) * 2020-03-19 2020-07-10 中国联合网络通信集团有限公司 Data forwarding method and gateway

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
T-Mobile USA Inc..RP-200607 "Discussion of company CR for Voice fallback triggered by PDU session resource setup (CR to 38.413)".3GPP tsg_ran\tsg_ran.2020,(第tsgr_88e期),全文. *
Vodafone GmbH.C4-190272 "Correction to the SGSN-Initiated Update PDP Context Request".3GPP tsg_ct\wg4_protocollars_ex-cn4.2019,(第tsgct4_89_montreal期),全文. *

Also Published As

Publication number Publication date
CN114071594A (en) 2022-02-18

Similar Documents

Publication Publication Date Title
US8694003B2 (en) LTE RRC connection re-establishment requesting method, cause value setting method and terminal
US8199719B2 (en) Methods and apparatus for performing handover between a long term evolution (LTE) network and another type of radio access network
WO2018045877A1 (en) Network slicing control method and related device
EP2352341B1 (en) Method, network side device and system for congestion control in location updating
US8874112B2 (en) Service dependent inactivity timer
US9578569B2 (en) Transferring a user equipment to a radio access network with a different radio access technology
US20080137536A1 (en) Method for Managing Network Node Overload and System Thereof
US20070129079A1 (en) Method for the allocation and release of channels in a mobile communication system
EP2775661B1 (en) Fault detection method and gateway
RU2677614C1 (en) Method of processing service, related device and system
US20150341443A1 (en) Method for keeping application online, always-online controller, and device
US12034766B2 (en) Method and system for providing edge service, and computing device
US9781763B2 (en) Radio link reestablishment method and controller
EP3197098B1 (en) Heartbeat cycle setting method and terminal
US20130089038A1 (en) Controlling telecommunications channel switching
EP3399801B1 (en) Voice call processing method and terminal device
US8717877B2 (en) Method for completing smooth cut-over, device and equipment for performing cut-over operations
WO2012051961A1 (en) Service processing method and device
US11445422B2 (en) Adaptable network communications
WO2012051893A1 (en) Service processing method and device
US20150036660A1 (en) Method, Device, and System for Identifying Traffic Type Across Devices
EP3930379B1 (en) Voice switching method and apparatus
CN113542098A (en) Method, system, device and storage medium for establishing and switching SD-WAN tunnel
CN114071594B (en) Service maintaining method, device, computer equipment and storage medium
CN111343655B (en) Implementation method of wireless network, implementation device of wireless network and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant