CN112969244B - Session recovery method and device - Google Patents
Session recovery method and device Download PDFInfo
- Publication number
- CN112969244B CN112969244B CN202110310764.0A CN202110310764A CN112969244B CN 112969244 B CN112969244 B CN 112969244B CN 202110310764 A CN202110310764 A CN 202110310764A CN 112969244 B CN112969244 B CN 112969244B
- Authority
- CN
- China
- Prior art keywords
- session
- application
- data
- parameters
- creating
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/19—Connection re-establishment
Abstract
The embodiment of the application discloses a session recovery method and a device for realizing the same, wherein the method comprises the following steps: creating a first session for transmitting data of an application, detecting whether data transmission of the first session is abnormal or not, and creating a second session under the condition that the data transmission of the first session is detected to be abnormal; sending the uplink data of the application through a second session; and if the downlink data corresponding to the uplink data is received through the second session within a preset time period, transmitting the subsequent data of the application through the second session. By implementing the embodiment of the application, under the condition that the data transmission abnormality of the first session is detected, the second session can be created, and the data transmission of the application can be recovered through the second session.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a session recovery method and an apparatus thereof.
Background
With the advent of the fifth-generation mobile communication technology (5G), applications based on mobile networks are becoming more and more abundant. In order to implement 5G applications, a 5G network needs to be deployed first, where the deployment mode of the 5G network includes an independent network (SA), and the independent network is to newly establish an existing network, including a new base station, a new backhaul link, a new core network, and the like.
Data traffic under the SA network can be transmitted via different network slices, which include three types: the method for transmitting the data in the internet of things can be used for enhancing mobile broadband (eMBB), low-latency and low-latency communications (URLLC), large-scale internet of things (mMTC), and flexibly coping with different network application scenes by selecting different types of network slices for data transmission. Multiple Data Network Names (DNNs) can be established under one network slice. Under one DNN, multiple Protocol Data Unit (PDU) sessions may be established, and the PDU sessions may be used for transmitting application data.
When data transmission of a session (for example, a session such as a PDU session) is abnormal, application data corresponding to the abnormal session cannot be normally transmitted. Therefore, how to quickly recover the normal transmission of the application data when the data transmission of the session is abnormal becomes an urgent technical problem to be solved.
Disclosure of Invention
The embodiment of the application provides a session recovery method and a session recovery device, which can quickly recover data transmission of an application under the condition that data transmission of a first session is abnormal.
In a first aspect, an embodiment of the present application provides a session recovery method, where the method includes: under the condition that the data transmission abnormality of a first session is detected, a second session is created, wherein the first session is used for transmitting the data of the application; sending the uplink data of the application through a second session; and if the downlink data corresponding to the uplink data is received through the second session within a preset time period, transmitting the subsequent data of the application through the second session.
In the technical scheme, under the condition that the data transmission abnormality of the first session is detected, the second session is created, that is, a data transmission channel between the terminal device and the application server corresponding to the application is reestablished, the uplink data of the application is sent through the second session, so as to detect whether the data transmission of the second session is in a normal state, and under the condition that the downlink data corresponding to the uplink data is received through the second session within a preset time period, that is, under the condition that the data transmission of the second session is in the normal state, the data transmission of the application corresponding to the first session can be quickly recovered through the second session for transmitting the subsequent data of the application, so that the influence of the occurrence of the abnormality of the data transmission of the first session on the data transmission of the application corresponding to the first session is reduced.
In one implementation, the specific implementation of creating the second session may be: and acquiring the transmission parameters of the application, and creating a second session matched with the transmission parameters of the application, wherein the session parameters of the second session are different from the session parameters of the first session.
In this technical solution, the reason that the data transmission of the first session is abnormal may be that the first session is not matched with the transmission parameter of the application, that is, the session parameter of the first session is not matched with the transmission parameter of the application, and therefore, when the data transmission of the first session is detected to be abnormal, by creating the second session which is matched with the transmission parameter of the application and has the session parameter different from the session parameter of the first session, the probability that the application data is successfully transmitted through the second session is high, thereby facilitating to quickly recover the data transmission of the application corresponding to the first session.
In one implementation, the method may further include: if downlink data corresponding to the uplink data is received through a second session within a preset time period, updating the session score of the first session and/or the session score of the second session; the session matched with the transmission parameter may be plural, and the second session may be a session having a highest session score among the sessions matched with the transmission parameter.
In the technical scheme, the higher the session score is, the better the transmission performance of the session is, and by updating the session score of the first session and/or the session score of the second session, when a new session is subsequently created, a session with a higher session creation score can be selected, which is beneficial to improving the data transmission performance.
In one implementation, the first session may also be released before the second session is created.
In the technical scheme, due to the fact that data transmission of the first session is abnormal, application data cannot be transmitted through the first session, and overhead can be reduced by releasing the first session.
In one implementation, the method may further include: sending uplink data of the application through a first session; if the downlink data corresponding to the uplink data is received through the second session within the preset time period, a specific implementation manner of transmitting the subsequent data of the application through the second session may be: and if the downlink data corresponding to the uplink data is received through the second session within a preset time period, and the time for receiving the downlink data through the second session is earlier than the time for receiving the downlink data through the first session, transmitting the subsequent data of the application through the second session.
In the technical scheme, under the condition that the data transmission abnormality of the first session is detected, the uplink data of the application are respectively sent through the first session and the second session, and then the subsequent data of the session transmission application of the downlink data are received preferentially, so that the data to be transmitted corresponding to the application can be sent as soon as possible, and the condition that the data volume of the data to be transmitted corresponding to the application is too large, and further the data backlog of the terminal equipment is serious, and even the data is lost is avoided.
In one implementation manner, if downlink data corresponding to the uplink data is not received through a second session within a preset time period, a third session is created, and session parameters of the third session are different from session parameters of the second session; sending the uplink data of the application through a third session; and if the downlink data corresponding to the uplink data is received through the third session within a preset time period, transmitting subsequent data of the application through the third session.
In the technical scheme, under the condition that data transmission of the first session is detected to be abnormal, if data transmission of the application cannot be successfully recovered through the second session, a third session with session parameters different from those of the second session can be created again, uplink data of the application can be sent through the third session, so as to detect whether data transmission of the third session is in a normal state, and under the condition that downlink data corresponding to the uplink data is received through the third session within a preset time period, that is, under the condition that the data transmission of the third session is in the normal state, subsequent data of the application can be transmitted through the third session. Since the data transmission of the application cannot be recovered through the second session, if the session parameter of the third session re-created by the terminal device is the same as the session parameter of the second session, the probability of successfully recovering the data transmission of the application through the third session is low, and therefore, the probability of successfully recovering the data transmission of the application through the third session is improved by re-creating the third session with a session parameter different from the session parameter of the second session.
In a second aspect, an embodiment of the present application provides a session recovery apparatus, where the apparatus has a function of implementing the session recovery method provided in the first aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.
In a third aspect, an embodiment of the present application provides a computer-readable storage medium for storing computer program instructions for a session recovery apparatus according to the second aspect, which includes a program for executing the above-mentioned first aspect.
In a fourth aspect, an embodiment of the present application provides a terminal device, where the terminal device includes a memory and a processor, where the memory stores program instructions, the processor is connected to the memory through a bus, and the processor calls the program instructions stored in the memory to enable the terminal device to execute the method according to the first aspect.
In a fifth aspect, the present application provides a computer program product, which includes a program that, when executed, implements the method of the first aspect.
Drawings
Fig. 1 is a schematic flowchart of a session recovery method disclosed in an embodiment of the present application;
fig. 2 is a schematic flowchart of another session recovery method disclosed in an embodiment of the present application;
fig. 3 is a schematic flowchart of another session recovery method disclosed in an embodiment of the present application;
fig. 4 is a schematic structural diagram of a session recovery apparatus disclosed in an embodiment of the present application;
fig. 5 is a schematic structural diagram of a terminal device disclosed in an embodiment of the present application.
Detailed Description
The session recovery method and the device thereof provided by the present application are described in detail below with reference to the accompanying drawings.
Referring to fig. 1, fig. 1 is a schematic flowchart of a session recovery method provided in an embodiment of the present application, where the method may include, but is not limited to, the following steps:
step S101: and the terminal equipment creates a second session under the condition of detecting that the data transmission of the first session is abnormal, wherein the first session is used for transmitting the data of the application.
In this embodiment of the present application, various types of applications may be installed in the terminal device, and when data generated by each application is sent to the base station through the terminal device, the data can be implemented through a session corresponding to the application, that is, when some application in the terminal device needs to perform network communication, a session may be created to transmit the data of the application. It should be noted that the session corresponding to the application may be used to transmit uplink data that needs to be sent to the base station, and may also be used to transmit downlink data that is sent by the base station to the application installed in the terminal device. In other words, after the session corresponding to the application is created, it is equivalent to successfully establishing a data transmission channel between the terminal device corresponding to the application and the application server corresponding to the application.
In one implementation, each application in the terminal device may correspond to 1 or more sessions. When a first application in the terminal equipment only corresponds to 1 session, all data of the first application are transmitted through the session; when a first application in a terminal device corresponds to multiple sessions, each session may be used to transmit different data of the first application, for example, each session may be used to transmit different types of data (such as voice, video, picture, text, and the like) of the first application, and this embodiment of the application is described by taking 1 session corresponding to each application in the terminal device as an example.
In the embodiment of the application, the terminal device may detect whether data transmission of each session is abnormal, so that data transmission of the application corresponding to the first session is resumed as soon as possible under the condition that the data transmission of the first session is detected to be abnormal, thereby reducing the influence of the abnormal data transmission of the first session on the data transmission of the application corresponding to the first session.
In an implementation manner, a specific implementation manner of the terminal device detecting whether data transmission of the first session is abnormal may be: when the terminal equipment sends the uplink data through the first session, timing through the timer (the initial value of the timer is 0), and if the terminal equipment does not receive the downlink data corresponding to the uplink data through the first session until the timing duration of the timer is greater than or equal to the preset duration, the data transmission of the first session is abnormal; if the timing duration of the timer is less than the preset duration when the terminal device receives the downlink data corresponding to the uplink data through the first session, it is indicated that the data transmission of the first session is not abnormal. In an implementation manner, a specific implementation manner of the terminal device sending the uplink data through the first session may be that: and the application corresponding to the first session sends the uplink data to a modem in the terminal equipment, and after the modem receives the uplink data, the modem modulates the uplink data and sends the modulated uplink data to the base station through an antenna.
In an implementation manner, the reason for the data transmission abnormality of the first session may be that a communication connection between the base station and the terminal device is disconnected, or that the base station fails and does not send data, or other common reasons, which is not limited in this embodiment of the present application.
Specifically, when the terminal device detects that data transmission of the first session is abnormal, in order to quickly recover data transmission of the application corresponding to the first session, a data transmission channel between the terminal device and the application server corresponding to the application may be reestablished, that is, the terminal device may create the second session, and transmit data of the application corresponding to the first session through the second session when data transmission of the second session is normal. In one implementation, when a second session needs to be created, an application corresponding to the first session in the terminal device may send a create session request to the modem, so that the modem sends the create session request to the base station through the antenna, thereby creating the second session.
In an implementation manner, a specific implementation manner of the terminal device creating the second session may be: and acquiring the session parameters of the first session, and creating a second session with the session parameters identical to the session parameters of the first session. In the embodiment of the present application, the session corresponding to each application may have session parameters, and the session parameters may be used to describe which service requirement (such as latency, bandwidth, security, reliability, and the like) data the session is suitable for transmitting, and/or describe which type (such as voice, video, picture, text, and the like) data the session is suitable for transmitting, and the like. In one implementation, the sessions mentioned in the embodiment of the present application (such as the first session, the second session, and a third session to be mentioned later) may be PDU sessions in 5G.
When the first session is a PDU session in 5G, the session parameters of the first session may include, but are not limited to: s-nssai (single network slice selection establishment information), Data Network Name (DNN), PDU session type, and Session and Service Continuity (SSC) mode.
The S-NSSAI is used for identifying a network slice, and if the type of the network slice identified by the S-NSSAI in the session parameters of the first session is URLLC, the first session is indicated to be suitable for transmitting data with low delay and high reliable service requirements. DNN is a network access technology, which is a parameter that needs to be configured when a terminal device accesses the Internet, and determines which access method the terminal device accesses the network through, for a terminal device user, there are many types of external networks that can be accessed (such as Internet, WAP website, group enterprise intranet, and industry intranet), and different access points have different access ranges and access methods, and a network side can determine which network the terminal device needs to access after being activated through the DNN, and further allocate an Internet Protocol (IP) address corresponding to a network segment to the terminal device. The PDU session type is used to indicate the type of PDU session, different types of PDU sessions carry different types of protocols, and the PDU session type may include, but is not limited to, internet protocol version4 (internet protocol version4, IPv4), internet protocol version 6 (internet protocol version 6, IPv6), ethernet, and untransfructured. For example, when the PDU session type is IPv4, the PDU session may carry data of IPv 4; when the PDU session type is untransformed, the PDU session may carry data of other protocols than IPv4, IPv6, and ethernet. The SSC pattern can satisfy different continuity requirements of the terminal device, and the SSC pattern can include, but is not limited to, SSC pattern 1, SSC pattern 2, and SSC pattern 3. When SSC mode 1 is adopted, the network reserves the connection with the terminal equipment; when the SSC mode 2 is adopted, the network can release the corresponding PDU session, and in one implementation, the network can trigger the PDU session release and instruct the terminal device to establish a new PDU session; with SSC mode 3, the network allows a new PDU session to be established before the old PDU session is released.
In the embodiment of the application, by creating the second session with the session parameters identical to those of the first session, the data suitable for transmission by the second session is identical to the data suitable for transmission by the first session. In an implementation manner, a specific implementation manner of the terminal device creating the first session may be: the terminal equipment acquires the transmission parameters of the application, calls a User Routing Selection Policy (URSP) to determine first session parameters matched with the transmission parameters of the application, and creates a first session according to the first session parameters. Wherein, the transmission parameter of the application is used to characterize the transmission requirement of the application, and the transmission parameter of the application may include but is not limited to: the type of data that an application needs to transmit (e.g., voice, video, pictures, text, etc.) and the service requirements (e.g., latency, bandwidth, security, reliability, etc.) that the application needs to transmit data. The first session parameters matching the transmission parameters of the application may indicate necessary parameters that the session for transmitting the data of the application should have. In one implementation manner, there may be one or more sessions with the first session parameters, and when there are multiple sessions with the first session parameters, the specific implementation manner of the terminal device creating the first session according to the first session parameters may be: and the terminal equipment acquires the session set matched with the first session parameters, determines the first session in the sessions included in the session set and creates the first session. Each session in the set of sessions may be used to transfer data for an application, but the performance of each session in transferring data for the application may be different. The session parameters of each session in the session set may include, in addition to the first session parameters, other session parameters (e.g., second session parameters), and the specific implementation of the terminal device in determining the first session in the sessions included in the session set may be: the terminal device may determine the session with the highest matching degree between the second session parameter and the applied transmission parameter as the first session. The higher the matching degree between the session parameter and the transmission parameter of the application is, the better the performance when the session corresponding to the session parameter transmits the data of the application is, because the session parameters of each session in the session set include the first session parameter, and the matching degree between the second session parameter in the session parameters of the first session and the transmission parameters is higher than the matching degree between the second session parameter in the session parameters of other sessions in the session set and the transmission parameters, the degree of match between the session parameters and the transmission parameters of the first session is higher than the degree of match between the session parameters and the transmission parameters of the other sessions in the set of sessions, that is, when the data transmission of the first conversation is not abnormal, the performance of the first conversation is better when the application data is transmitted, since the session parameters of the second session are the same as those of the first session, the performance of the second session in transmitting the data of the application is considered to be better.
It should be noted that, when the terminal device acquires the session set, the session in the session set is not actually created, and only after the terminal device determines the first session, the first session is actually created, which can avoid that, after all the sessions in the session set are created, only the first session in the session set is subsequently used, and other created sessions are not used, thus avoiding resource waste.
In an implementation manner, a specific implementation manner of the terminal device creating the second session may further be that: and acquiring the transmission parameters of the application, and creating a second session matched with the transmission parameters, wherein the session parameters of the second session are different from the session parameters of the first session. The number of the sessions matched with the transmission parameters can be one or more, and the terminal device can select one session as the second session from the sessions matched with the transmission parameters. When the session matched with the transmission parameters is one and the session parameters of the session are different from the session parameters of the first session, the terminal device may regard the session as a second session. In one implementation, when there are a plurality of sessions matching the transmission parameters, the terminal device may arbitrarily select, as the second session, a session with session parameters different from those of the first session from among the sessions matching the transmission parameters. In an implementation manner, a specific implementation manner of the terminal device creating the second session matched with the transmission parameter may further be that: calling the URSP to determine first session parameters matched with the transmission parameters of the application, acquiring a session set matched with the first session parameters, determining a second session in the sessions included in the session set except the first session, and creating the second session. In one implementation, when the session set matching the first session parameter includes a plurality of sessions, the matching degree between the session parameters and the transmission parameters of the second session is higher than the matching degree between the session parameters and the transmission parameters of other sessions in the session set. In an implementation manner, the reason why the data transmission of the first session is abnormal may be that the first session is not matched with the transmission parameters of the application, that is, the session parameters of the first session are not matched with the transmission parameters of the application, and therefore, in the embodiment of the present application, when the data transmission of the first session is detected to be abnormal, by creating the second session which is matched with the transmission parameters of the application and of which the session parameters are different from the session parameters of the first session, the probability that the application data is successfully transmitted through the second session is higher, thereby facilitating to quickly recover the data transmission of the application corresponding to the first session.
In one implementation, each session has a session score, with a higher session score indicating better transmission performance for that session. In one implementation, when the number of the sessions matched with the transmission parameters is multiple, the terminal device may screen out the sessions matched with the transmission parameters, the session parameters of which are different from those of the first session, and select the session with the highest session score as the second session from the sessions with the session parameters different from those of the first session. In this way, on one hand, the probability of successful transmission of the application data through the second session is higher, and on the other hand, the performance of transmission of the application data through the second session is better.
In one implementation manner, the terminal device may release the first session when detecting that data transmission of the first session is abnormal, and then trigger execution of the step of creating the second session, because the data transmission of the first session is abnormal, application data cannot be transmitted through the first session, and unnecessary overhead of the terminal device may be saved by releasing the first session.
In an implementation manner, the reason why the data transmission of the first session is abnormal (that is, the terminal device still does not receive the downlink data corresponding to the uplink data through the first session until the timing duration of the timer is greater than or equal to the preset duration) may be network delay. In one implementation, the terminal device may release the first session after the second session is successfully created, and in this way, before the second session is successfully created, if downlink data corresponding to the uplink data is received through the first session (that is, the reason why the data transmission of the first session is abnormal is network delay), the terminal device may stop creating the second session, and continue to transmit subsequent data of the application through the first session; if the terminal device does not receive the downlink data corresponding to the uplink data through the first session after the second session is successfully created, the terminal device may release the first session and transmit the subsequent data of the application through the second session. By the method, the situation that the received downlink data is lost due to the fact that the terminal equipment releases the first session and then the lost downlink data needs to be acquired through the established second session when the downlink data corresponding to the uplink data is received through the first session before the second session is successfully established can be avoided, and waste of resources is facilitated.
In one implementation, the terminal device may be a User Equipment (UE), a remote terminal, a mobile terminal, a wireless communication device, or a user equipment, and the user device may be a mobile phone, a desktop computer, a notebook computer, or a wearable device.
Step S102: and the terminal equipment sends the uplink data of the application through the second session.
Specifically, after the terminal device creates the second session, the uplink data of the application may be sent through the second session, so as to detect whether the uplink data of the application may be successfully transmitted through the second session, and in a case that the uplink data of the application may be successfully transmitted through the second session, the subsequent data of the application may be transmitted through the second session. In one implementation, if downlink data corresponding to the uplink data is received through a second session within a preset time period, it indicates that the data of the application can be successfully transmitted through the second session; and if the downlink data corresponding to the uplink data is not received through the second session within a preset time period, indicating that the data of the application cannot be successfully transmitted through the second session.
In one implementation, the uplink data sent by the terminal device through the second session may be service data generated by the application and to be transmitted, or may be test data generated by the application and used for testing validity of the second session. For example, the uplink data sent by the second session may be user data, or when the data of the application needs to be transmitted through a TCP connection, the uplink data sent by the second session may be a handshake data packet (such as synchronization Sequence Numbers (SYN)) sent in the process of establishing the TCP connection.
In one implementation manner, the data volume of the uplink data sent by the terminal device through the second session is smaller than the preset data volume threshold, and by this way, on one hand, the purpose of testing the validity of the second session can be achieved; on the other hand, the waste of excessive resources of the terminal equipment when the data volume of the transmitted uplink data is large and the corresponding downlink data is not received can be avoided. The preset data amount threshold may be set by default by the terminal device, or may be set by the terminal device according to a user operation, which is not limited in the embodiment of the present application.
Step S103: and if the downlink data corresponding to the uplink data is received through the second session within a preset time period, the terminal equipment transmits the subsequent data of the application through the second session.
Specifically, if the downlink data corresponding to the uplink data is received through the second session within the preset time period, it indicates that the data transmission of the second session is in a normal state, and therefore, the terminal device may transmit the subsequent data of the application through the second session. In an implementation manner, the preset time period may be set by default by the terminal device, or may be set by the terminal device according to an operation of a user, which is not limited in the embodiment of the present application.
In one implementation, the terminal device may initialize the session score of each session corresponding to the application to the same score (for example, a preset reference score), and if the data transmission abnormality of the first session is detected, reduce the session score of the first session; and if the abnormality does not occur in the data transmission process from the creation of the first session to the normal release of the first session after the application has no data transmission requirement, the session score of the first session is increased.
In an implementation manner, if downlink data corresponding to the aforementioned uplink data is received through a second session within a preset time period, the terminal device may update a session score of the first session and/or a session score of the second session, specifically, the terminal device may decrease the session score of the first session and/or increase the session score of the second session, so that when the application subsequently creates a new session, a session with a higher session score may be selected to be created, and since a higher session score indicates better transmission performance of the session, this is beneficial to improving data transmission performance. In one implementation manner, in the process of creating the second session, if there are a plurality of sessions that match the transmission parameters, the second session created by the terminal device may be a session with the highest session score in the sessions that match the transmission parameters.
It can be seen that, by implementing the embodiment of the present application, when it is detected that data transmission of the first session is abnormal, the second session is created, that is, a data transmission channel between the terminal device and the application server corresponding to the application is reestablished, and the uplink data of the application is sent through the second session, so as to detect whether data transmission of the second session is in a normal state, and when the downlink data corresponding to the uplink data is received through the second session within a preset time period, that is, when it is indicated that data transmission of the second session is in a normal state, data transmission of the application corresponding to the first session can be quickly resumed through the second session transmitting subsequent data of the application, thereby reducing an influence on data transmission of the application corresponding to the first session due to occurrence of abnormal data transmission of the first session.
Referring to fig. 2, fig. 2 is a flowchart illustrating another session recovery method provided in this embodiment of the present application, in which, in a case that a data transmission abnormality of a first session is detected, after a second session is created, how to select one session from the first session and the second session for transmitting subsequent data of an application is described in detail, where the method includes, but is not limited to the following steps:
step S201: and the terminal equipment creates a second session under the condition of detecting that the data transmission of the first session is abnormal, wherein the first session is used for transmitting the data of the application.
Specifically, when detecting that data transmission of the first session is abnormal, the terminal device may maintain the first session, create the second session, and select one session from the first session and the second session for transmitting subsequent data of the application. It should be noted that, the execution process of step S201 can refer to the detailed description of step S101 in fig. 1, and is not described herein again.
Step S202: and the terminal equipment sends the uplink data of the application through the second session and sends the uplink data of the application through the first session.
Specifically, the terminal device may send the uplink data of the application through the second session, send the same uplink data through the first session, and transmit subsequent data of the application through a session that preferentially receives the downlink data corresponding to the uplink data, when the downlink data corresponding to the uplink data is preferentially received through which session.
In an implementation manner, the terminal device may send the uplink data of the application through the first session and the second session at the same time, or the terminal device may send the uplink data of the application through the first session first and then send the uplink data of the application through the second session, or the terminal device may send the uplink data of the application through the second session first and then send the uplink data of the application through the first session, which is not limited in this embodiment of the application.
Step S203: and if the downlink data corresponding to the uplink data is received through the second session within a preset time period, and the time for receiving the downlink data through the second session is earlier than the time for receiving the downlink data through the first session, the terminal equipment transmits the subsequent data of the application through the second session.
Specifically, if the downlink data corresponding to the uplink data is received through the second session within the preset time period, and the time for receiving the downlink data through the second session is earlier than the time for receiving the downlink data through the first session, the terminal device may transmit the subsequent data of the application through the second session. That is, regardless of which session (first session or second session) the terminal device first transmits the upstream data of the application, the terminal device may use the session that first receives the downstream data corresponding to the upstream data as a session for transmitting the subsequent data of the application, that is, if the downstream data corresponding to the upstream data is received through the first session within a preset time period and the time for receiving the downstream data through the first session is earlier than the time for receiving the downstream data through the second session, the terminal device transmits the subsequent data of the application through the first session. By the method, the data to be transmitted corresponding to the application can be sent as soon as possible, and the situation that the data backlog of the terminal equipment is serious and even the data is lost due to overlarge data amount of the data to be transmitted corresponding to the application is avoided.
In one implementation, the terminal device may obtain a time interval between sending the uplink data and receiving the corresponding downlink data in the first session, obtain a time interval between sending the uplink data and receiving the corresponding downlink data in the second session, and use the session with a shorter time interval as a session for transmitting subsequent data of the application. The shorter the time interval is, the better the transmission performance of the corresponding session can be shown, and the session with the shorter time interval is used as the session for transmitting the subsequent data of the application, which is beneficial to improving the data transmission performance of the terminal equipment.
In an implementation manner, if downlink data corresponding to the uplink data is not received in both the first session and the second session within a preset time period, it indicates that data transmission of the application cannot be resumed through both the first session and the second session, and at this time, the terminal device may release the newly-established session (i.e., the second session) to reduce power consumption of the terminal device.
By implementing the embodiment of the application, under the condition that the data transmission abnormality of the first session is detected, the uplink data of the application can be respectively sent through the first session and the second session, and then the subsequent data of the session transmission application of the downlink data is received preferentially.
Referring to fig. 3, fig. 3 is a flowchart illustrating a method for recovering a session according to an embodiment of the present application, in which, when a data transmission abnormality of a first session is detected, after a second session is created, if a data transmission of an application cannot be successfully recovered through the second session, the method may include, but is not limited to, the following steps:
step S301: and the terminal equipment releases the first session under the condition of detecting that the data transmission of the first session is abnormal, wherein the first session is used for transmitting the data of the application.
Specifically, the terminal device may release the first session and re-create a new session (i.e., a second session) when detecting that data transmission of the first session is abnormal, and determine whether data transmission of the application can be successfully resumed through the newly created second session.
Step S302: the terminal device creates a second session.
Step S303: and the terminal equipment sends the uplink data of the application through the second session.
Step S304: and if the downlink data corresponding to the uplink data is received through the second session within a preset time period, the terminal equipment transmits the subsequent data of the application through the second session.
It should be noted that the execution processes of step S302 to step S304 can be referred to the specific descriptions of step S101 to step S103 in fig. 1, which are not described herein again.
Step S305: and if the downlink data corresponding to the uplink data is not received through the second session within a preset time period, releasing the second session.
Specifically, if the downlink data corresponding to the uplink data is not received through the second session within the preset time period, it is indicated that data transmission of the second session is abnormal, or the data transmission performance of the second session is low, and if the terminal device transmits the subsequent uplink data applied through the second session, it may be caused that the downlink data corresponding to the subsequent uplink data cannot be received through the second session, or the performance of the subsequent data applied through the second session is low. In order to avoid the above situation, the terminal device may not transmit the subsequent data of the application through the second session, but in order to successfully resume the data transmission of the application, the terminal device needs to re-create a new session (for example, a third session) and determine whether the data transmission of the application can be successfully resumed through the newly created third session, and since the terminal device does not transmit the subsequent data of the application through the second session, the terminal device may release the second session, so as to reduce the overhead of the terminal device.
Step S306: the terminal device creates a third session, the session parameters of the third session being different from the session parameters of the second session.
Specifically, since the data transmission of the application cannot be recovered through the second session, if the session parameter of the third session re-created by the terminal device is the same as the session parameter of the second session, the probability that the data transmission of the application is successfully recovered through the third session is low, and therefore, the terminal device can re-create a third session with session parameters different from the session parameters of the second session, which is beneficial to improving the probability that the data transmission of the application is successfully recovered through the third session. In other words, when the session parameters of the second session are the same as the session parameters of the first session, the session parameters of the third session are different from the session parameters of the first session; when the session parameter of the second session is different from the session parameter of the first session, the session parameter of the third session may be the same as the session parameter of the first session, or may be different from the session parameter of the first session, which is not limited in this embodiment of the application.
Step S307: and the terminal equipment sends the uplink data of the application through a third session.
Specifically, after the terminal device creates the third session, the uplink data of the application may be sent through the third session, so as to detect whether the uplink data of the application may be successfully transmitted through the third session, and in a case that the uplink data of the application may be successfully transmitted through the third session, the subsequent data of the application may be transmitted through the third session. In one implementation, if downlink data corresponding to the uplink data is received through a third session within a preset time period, it indicates that the data of the application can be successfully transmitted through the third session; and if the downlink data corresponding to the uplink data is not received through the third session within the preset time period, indicating that the data of the application cannot be successfully transmitted through the third session.
In one implementation, the uplink data sent by the terminal device through the third session may be service data generated by the application and to be transmitted, or may be test data generated by the application and used for testing validity of the third session. In one implementation manner, the data volume of the uplink data sent by the terminal device through the third session is smaller than the preset data volume threshold, and through this manner, on one hand, the purpose of testing the validity of the third session can be achieved; on the other hand, the waste of excessive resources of the terminal equipment when the data volume of the transmitted uplink data is large and the corresponding downlink data is not received can be avoided.
Step S308: and if the downlink data corresponding to the uplink data is received through the third session within a preset time period, the terminal equipment transmits the subsequent data of the application through the third session.
Specifically, if the downlink data corresponding to the uplink data is received through the third session within the preset time period, it indicates that the data transmission of the third session is in a normal state, and therefore, the terminal device may transmit the subsequent data of the application through the third session.
By implementing the embodiment of the application, under the condition that the data transmission of the first session is detected to be abnormal, if the data transmission of the application cannot be successfully recovered through the second session, a third session with session parameters different from those of the second session can be created again, the uplink data of the application can be sent through the third session, so as to detect whether the data transmission of the third session is in a normal state, and under the condition that the downlink data corresponding to the uplink data is received through the third session within a preset time period, that is, under the condition that the data transmission of the third session is in a normal state, the subsequent data of the application can be transmitted through the third session. Since the data transmission of the application cannot be recovered through the second session, if the session parameter of the third session re-created by the terminal device is the same as the session parameter of the second session, the probability of successfully recovering the data transmission of the application through the third session is low, and therefore, the probability of successfully recovering the data transmission of the application through the third session is improved by re-creating the third session with a session parameter different from the session parameter of the second session.
The method of the embodiments of the present application is set forth above in detail and the apparatus of the embodiments of the present application is provided below.
Referring to fig. 4, fig. 4 is a schematic structural diagram of a session recovery apparatus according to an embodiment of the present application, where the session recovery apparatus 40 is configured to execute steps executed by a terminal device in the method embodiments corresponding to fig. 1 to fig. 3, and the session recovery apparatus 40 may include:
a creating module 401, configured to create a second session when data transmission abnormality of a first session is detected, where the first session is used to transmit data of an application;
a communication module 402, configured to send uplink data of the application through a second session;
the communication module 402 is further configured to transmit subsequent data of the application through the second session if the downlink data corresponding to the uplink data is received through the second session within a preset time period.
In an implementation manner, when the creating module 401 is configured to create the second session, it may specifically be configured to: and acquiring the session parameters of the first session, and creating a second session with the session parameters identical to the session parameters of the first session.
In an implementation manner, when the creating module 401 is configured to create the second session, it may specifically be configured to: and acquiring the transmission parameters of the application, and creating a second session matched with the transmission parameters, wherein the session parameters of the second session are different from the session parameters of the first session.
In one implementation, session recovery apparatus 40 may further include an update module 403; the updating module 403 may be configured to update the session score of the first session and/or the session score of the second session if the downlink data corresponding to the uplink data is received through the second session within a preset time period; the session matched with the transmission parameter may be plural, and the second session may be a session having a highest session score among the sessions matched with the transmission parameter.
In one implementation, the session recovering apparatus 40 may further include a releasing module 404, and the releasing module 404 may be configured to release the first session.
In one implementation, the communication module 402 may be further configured to send uplink data of the application through the first session; the 402 communication module is configured to, if downlink data corresponding to the uplink data is received through a second session within a preset time period, when subsequent data of an application is transmitted through the second session, specifically: and if the downlink data corresponding to the uplink data is received through the second session within a preset time period, and the time for receiving the downlink data through the second session is earlier than the time for receiving the downlink data through the first session, transmitting the subsequent data of the application through the second session.
In an implementation manner, the creating module 401 may be further configured to create a third session if downlink data corresponding to the uplink data is not received through the second session within a preset time period, where session parameters of the third session are different from session parameters of the second session; the communication module 402 may be further configured to send uplink data of the application through a third session; the communication module 402 may further be configured to transmit subsequent data of the application through the third session if the downlink data corresponding to the uplink data is received through the third session within a preset time period.
It should be noted that details that are not mentioned in the embodiment corresponding to fig. 4 and specific implementation manners of the steps executed by each module may refer to the embodiments shown in fig. 1 to fig. 3 and the foregoing details, and are not described again here.
In one implementation, the relevant functions implemented by the various modules in fig. 4 may be implemented in conjunction with a processor and a transceiver. Referring to fig. 5, fig. 5 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure, where the terminal device 50 may include a transceiver 501, a processor 502, and a memory 503, and the transceiver 501, the processor 502, and the memory 503 may be connected to each other through one or more communication buses, or may be connected through other manners. The related functions implemented by the creation module 401, the communication module 402, the update module 403 and the release module 404 shown in fig. 4 may be implemented by the same processor 502, or may be implemented by a plurality of different processors 502.
The transceiver 501 may be used to transmit data and/or signaling as well as receive data and/or signaling. In this embodiment, the transceiver 501 may be used to transmit uplink data of an application, and may also be used to receive downlink data corresponding to the uplink data.
The processor 502 is configured to perform the corresponding functions of the terminal device in the methods described in fig. 1-3. The processor 502 may include one or more processors, for example, the processor 502 may be one or more Central Processing Units (CPUs), Network Processors (NPs), hardware chips, or any combination thereof. In the case where the processor 502 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.
The memory 503 is used to store program codes and the like. The memory 503 may include a volatile memory (volatile memory), such as a Random Access Memory (RAM); the memory 503 may also include a non-volatile memory (non-volatile memory), such as a read-only memory (ROM), a flash memory (flash memory), a Hard Disk Drive (HDD) or a solid-state drive (SSD); the memory 503 may also comprise a combination of the above kinds of memories.
The processor 502 may call the program code stored in the memory 503 to perform the following operations:
under the condition that the data transmission abnormality of a first session is detected, a second session is created, wherein the first session is used for transmitting the data of the application;
sending the uplink data of the application through a second session;
and if the downlink data corresponding to the uplink data is received through the second session within a preset time period, transmitting the subsequent data of the application through the second session.
In one implementation, when the processor 502 executes creating the second session, the following operations may be specifically executed: and acquiring the session parameters of the first session, and creating a second session with the session parameters identical to the session parameters of the first session.
In one implementation, when the processor 502 executes creating the second session, the following operations may be specifically executed: and acquiring the transmission parameters of the application, and creating a second session matched with the transmission parameters, wherein the session parameters of the second session are different from the session parameters of the first session.
In one implementation, the processor 502 may also perform the following operations: if downlink data corresponding to the uplink data is received through a second session within a preset time period, updating the session score of the first session and/or the session score of the second session; the session matched with the transmission parameter may be plural, and the second session may be a session having a highest session score among the sessions matched with the transmission parameter.
In one implementation, before creating the second session, the processor 502 may further perform the following operations: the first session is released.
In one implementation, the processor 502 may also perform the following operations: sending uplink data of the application through a first session; if the processor 502 receives the downlink data corresponding to the uplink data through the second session within the preset time period, the following operations may be specifically performed when the subsequent data of the application is transmitted through the second session: and if the downlink data corresponding to the uplink data is received through the second session within a preset time period, and the time for receiving the downlink data through the second session is earlier than the time for receiving the downlink data through the first session, transmitting the subsequent data of the application through the second session.
In one implementation, the processor 502 may also perform the following operations: if the downlink data corresponding to the uplink data is not received through the second session within a preset time period, a third session is created, and session parameters of the third session are different from those of the second session; sending the uplink data of the application through a third session; and if the downlink data corresponding to the uplink data is received through the third session within a preset time period, transmitting the subsequent data of the application through the third session.
Further, the processor 502 may also execute operations corresponding to the terminal device in the embodiments shown in fig. 1 to fig. 3, which may specifically refer to the description in the method embodiment and will not be described herein again.
An embodiment of the present application further provides a computer-readable storage medium, which can be used to store computer software instructions for the session recovery apparatus in the embodiment shown in fig. 4, and which contains a program designed for the terminal device in the foregoing embodiment.
The computer readable storage medium includes, but is not limited to, flash memory, hard disk, solid state disk.
Embodiments of the present application further provide a computer program product, which, when executed by a computing device, can execute the method designed for the terminal device in the foregoing embodiments of fig. 1 to 3.
There is also provided in an embodiment of the present application a chip including a processor and a memory, where the memory includes the processor and the memory, and the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, and the computer program is used to implement the method in the above method embodiment.
Those of ordinary skill in the art would appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in or transmitted over a computer-readable storage medium. The computer instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (15)
1. A method for session recovery, comprising:
creating a first session, wherein the first session is used for transmitting data of an application; the first session is created according to first session parameters matched with the transmission parameters of the application; the transmission parameters comprise time delay; the first session parameters comprise S-NSSAI for identifying a network slice type of the first session;
detecting whether the data transmission of the first session is abnormal or not;
under the condition that the data transmission abnormality of the first session is detected, creating a second session; the second session is created according to second session parameters; the second session parameter comprises S-NSSAI used for identifying the network slice type of the second session;
sending uplink data of the application through the second session;
and if downlink data corresponding to the uplink data is received through the second session within a preset time period, transmitting subsequent data of the application through the second session.
2. The method of claim 1, wherein the creating a second session comprises:
acquiring session parameters of the first session;
creating a second session having session parameters identical to the session parameters of the first session.
3. The method of claim 1, wherein the creating a second session comprises:
acquiring transmission parameters of the application;
and creating a second session matched with the transmission parameters, wherein the session parameters of the second session are different from the session parameters of the first session.
4. The method of claim 3, further comprising:
if downlink data corresponding to the uplink data is received through the second session within the preset time period, updating the session score of the first session and/or the session score of the second session;
the number of the sessions matched with the transmission parameters is multiple, and the second session is the session with the highest session score in the sessions matched with the transmission parameters.
5. The method according to any of claims 1-4, wherein before creating the second session, the method further comprises:
releasing the first session.
6. The method according to any one of claims 1 to 4, further comprising:
sending the uplink data of the application through the first session;
if downlink data corresponding to the uplink data is received through the second session within a preset time period, transmitting subsequent data of the application through the second session, including:
and if downlink data corresponding to the uplink data is received through the second session within a preset time period, and the time for receiving the downlink data through the second session is earlier than the time for receiving the downlink data through the first session, transmitting subsequent data of the application through the second session.
7. The method according to any one of claims 1 to 4, further comprising:
if downlink data corresponding to the uplink data is not received through the second session within the preset time period, a third session is created, and session parameters of the third session are different from session parameters of the second session;
sending uplink data of the application through the third session;
and if downlink data corresponding to the uplink data is received through the third session within the preset time period, transmitting subsequent data of the application through the third session.
8. A session recovery apparatus, comprising:
the device comprises a creating module, a transmitting module and a receiving module, wherein the creating module is used for creating a first session which is used for transmitting data of an application; the first session is created according to first session parameters matched with the transmission parameters of the application; the transmission parameters comprise time delay; the first session parameters comprise S-NSSAI for identifying a network slice type of the first session;
the creating module is further configured to detect whether data transmission of the first session is abnormal, and create a second session when the data transmission of the first session is detected to be abnormal; the second session is created according to second session parameters; the second session parameter comprises S-NSSAI used for identifying the network slice type of the second session;
a communication module, configured to send uplink data of the application through the second session;
the communication module is further configured to transmit subsequent data of the application through the second session if downlink data corresponding to the uplink data is received through the second session within a preset time period.
9. The apparatus according to claim 8, wherein the creating module, when creating the second session, is specifically configured to: and acquiring the session parameters of the first session, and creating a second session with the session parameters identical to the session parameters of the first session.
10. The apparatus according to claim 8, wherein the creating module, when creating the second session, is specifically configured to: and acquiring the transmission parameters of the application, and creating a second session matched with the transmission parameters, wherein the session parameters of the second session are different from the session parameters of the first session.
11. The apparatus of claim 10, further comprising an update module;
the updating module is configured to update the session score of the first session and/or the session score of the second session if downlink data corresponding to the uplink data is received through the second session within the preset time period; the number of the sessions matched with the transmission parameters is multiple, and the second session is the session with the highest session score in the sessions matched with the transmission parameters.
12. The device according to any one of claims 8 to 11, further comprising a release module;
the release module is used for releasing the first session.
13. The apparatus according to any one of claims 8 to 11,
the communication module is further configured to send uplink data of the application through the first session;
the communication module is configured to, if downlink data corresponding to the uplink data is received through the second session within a preset time period, when subsequent data of the application is transmitted through the second session, specifically: and if downlink data corresponding to the uplink data is received through the second session within a preset time period, and the time for receiving the downlink data through the second session is earlier than the time for receiving the downlink data through the first session, transmitting subsequent data of the application through the second session.
14. The apparatus according to any one of claims 8 to 11,
the creating module is further configured to create a third session if downlink data corresponding to the uplink data is not received through the second session within the preset time period, where session parameters of the third session are different from session parameters of the second session;
the communication module is further configured to send uplink data of the application through the third session;
the communication module is further configured to transmit subsequent data of the application through the third session if downlink data corresponding to the uplink data is received through the third session within the preset time period.
15. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program comprising program instructions which, when executed by a processor, cause the processor to carry out the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110310764.0A CN112969244B (en) | 2019-04-02 | 2019-04-02 | Session recovery method and device |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910275451.9A CN109996349B (en) | 2019-04-02 | 2019-04-02 | Session recovery method and device |
| CN202110310764.0A CN112969244B (en) | 2019-04-02 | 2019-04-02 | Session recovery method and device |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910275451.9A Division CN109996349B (en) | 2019-04-02 | 2019-04-02 | Session recovery method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112969244A CN112969244A (en) | 2021-06-15 |
| CN112969244B true CN112969244B (en) | 2022-06-07 |
Family
ID=67132402
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910275451.9A Active CN109996349B (en) | 2019-04-02 | 2019-04-02 | Session recovery method and device |
| CN202110310764.0A Active CN112969244B (en) | 2019-04-02 | 2019-04-02 | Session recovery method and device |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910275451.9A Active CN109996349B (en) | 2019-04-02 | 2019-04-02 | Session recovery method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN109996349B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114124873B (en) * | 2020-08-26 | 2023-07-18 | 腾讯科技（深圳）有限公司 | Account abnormity processing method, device, computer equipment and storage medium |
| CN117478645A (en) * | 2022-07-22 | 2024-01-30 | 维沃移动通信有限公司 | Call negotiation method, device, communication equipment and readable storage medium |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10412778B2 (en) * | 2015-03-31 | 2019-09-10 | Huawei Technologies Co., Ltd. | Data transmission method and apparatus for data service |
| KR102537960B1 (en) * | 2016-01-20 | 2023-05-31 | 삼성전자주식회사 | Apparatus and method for controlling transmission in a high thoughput werelless network |
| CN108377577B (en) * | 2016-11-21 | 2021-03-30 | 华为技术有限公司 | Method and device for recovering downlink radio link failure |
| WO2018090386A1 (en) * | 2016-11-21 | 2018-05-24 | 华为技术有限公司 | Method, device and system for processing abnormities of nf modules |
| CN108738082B (en) * | 2017-04-13 | 2020-06-16 | 华为技术有限公司 | Session processing method, device and system |
| CN107197473B (en) * | 2017-06-15 | 2020-05-15 | 三星电子（中国）研发中心 | Terminal abnormal state determination method and device |
| CN109246172A (en) * | 2017-07-11 | 2019-01-18 | 华为技术有限公司 | A kind of method, apparatus and computer storage medium for restoring session |
| CN109429361B (en) * | 2017-07-18 | 2021-01-01 | 华为技术有限公司 | Session processing method and device |
| CN111491345B (en) * | 2017-08-11 | 2021-04-20 | 华为技术有限公司 | Communication method, access network device, and computer-readable storage medium |
-
2019
- 2019-04-02 CN CN201910275451.9A patent/CN109996349B/en active Active
- 2019-04-02 CN CN202110310764.0A patent/CN112969244B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN109996349A (en) | 2019-07-09 |
| CN109996349B (en) | 2021-03-23 |
| CN112969244A (en) | 2021-06-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR20200087231A (en) | Method and apparatus for processing asynchronous buffer | |
| EP1193924B1 (en) | Radio communications system using timeout control with flexible timeout interval settings | |
| CN111586807B (en) | Network access method and communication device | |
| WO2022017529A1 (en) | Data transmission method and system, electronic device, and storage medium | |
| CN112969244B (en) | Session recovery method and device | |
| CN104601541A (en) | Data transmission method, server and user equipment | |
| WO2018228193A1 (en) | Service data unit segmentation processing method and data receiving end | |
| EP3593516B1 (en) | Method and control node for managing cloud resources in a communications network | |
| WO2016154921A1 (en) | Data transmission method and device for data service | |
| RU2693903C1 (en) | Method, apparatus and processing system for expanded port | |
| CN102932820A (en) | Link processing method, device and system | |
| CN116192863B (en) | Micro-service flow processing method, DPU service grid deployment method and system | |
| WO2018094873A1 (en) | Method and device for establishing multicast cluster | |
| EP3334227B1 (en) | Paging method and apparatus for distributed gateway | |
| CN108024350B (en) | Dynamic time allocation method and device | |
| JP2016162324A (en) | Information processing system, control program and control method | |
| CN112866133B (en) | Method and device for acquiring MSS (maximum segment size) | |
| CN109688085B (en) | Transmission control protocol proxy method, storage medium and server | |
| RU2742721C1 (en) | Method of processing paging failures, network access device and core network device | |
| CN113891499A (en) | Method and device for solving inconsistency of user plane states of core network and base station | |
| KR102000162B1 (en) | Apparatus and method for supporting software update of low specification device | |
| CN110572465B (en) | Message transmission method and device | |
| CN106209733B (en) | A kind of data processing method and device | |
| CN111049754B (en) | Data communication method, device, equipment and computer readable storage medium | |
| EP4181554A1 (en) | Traffic control server and method |
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 | ||
| GR01 | Patent grant |