Processing method, communication device, and storage medium

Abstract

In response to satisfying the first condition, the first network node provides the first information to the second network node; thereby for the IoT-NTN Regenerative payload scenario, the terminal device can obtain the terminal device context when initiating the RRCConnectionResumeRequest, thereby saving signaling overhead and / or reducing power consumption.

Description

Processing method, communication device and storage medium Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a processing method, communication equipment and storage medium. Background Art

[0002] NB-IoT (Narrow Band Internet of Things) is suitable for low-mobility business scenarios. In the existing protocol, the NB-IoT user plane CIoT EPS / 5GS (Cellular Internet of Things Evolved Packet System / 5G system) optimization (NB-IoT User Plane CIoT EPS / 5GS optimisation) supports suspension and resumption of RRC (Radio Resource Control) connections. When the RRC connection is suspended, the terminal device enters the IDLE state and saves the terminal device context. When the RRC connection is resumed, the terminal device and network equipment (such as eNB, satellite) use the saved terminal device context to resume the RRC connection, which helps to reduce signaling overhead.

[0003] During the process of conceiving and implementing this application, the inventors discovered at least the following problems:

[0004] In the IoT-NTN Regenerative payload (Internet of Things Non-Terrestrial Network Regenerative payload, i.e., eNB on satellite) scenario, due to the high-speed satellite movement and short coverage time, when the terminal device with a suspended RRC connection initiates an RRCConnectionResumeRequest, the serving satellite connected to the terminal device has changed. Therefore, the current serving satellite (new eNB) needs to initiate a Retrieve UE Context procedure from the satellite with the suspended RRC connection (old eNB) to obtain the terminal device context. Due to the rapid satellite movement, there may be no inter-satellite link (ISL) / neighborhood relationship / X2 interface between the new eNB and the old eNB. Therefore, the new eNB cannot initiate the Retrieve UE Context procedure to obtain the terminal device context from the old eNB, resulting in the inability to use UP CIoT EPS / 5GS optimisation. At this time, the terminal device needs to fall back to the RRC re-establishment process, which is not conducive to saving signaling overhead and / or reducing power consumption.

[0005] Therefore, for the IoT-NTN Regenerative payload scenario, a solution needs to be provided so that when the terminal device initiates RRCConnectionResumeRequest, the new network node can obtain the terminal device context to save signaling overhead and / or reduce power consumption.

[0006] The preceding description is intended to provide general background information and does not necessarily constitute prior art. Technical Solutions

[0007] The main purpose of this application is to provide a processing method, a communication device, and a storage medium. For the IoT-NTN Regenerative payload scenario, a solution is provided so that when the terminal device initiates an RRCConnectionResumeRequest, the new network node can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0008] The present application provides a processing method, which can be applied to a first network node (such as a network device, specifically a base station or a satellite), comprising the steps of:

[0009] S1: In response to a first condition being met, the first network node provides first information to the second network node.

[0010] Optionally, the first condition is satisfied, including at least one of the following:

[0011] When the first network node receives the context acquisition request sent by the second network node;

[0012] After the first network node suspends the radio resource control connection of the terminal device;

[0013] When the first network node leaves or is about to leave the location area where the terminal device is located.

[0014] Optionally, the first information includes at least one of the following:

[0015] Terminal device context;

[0016] Location information of the terminal device;

[0017] Business information of terminal equipment;

[0018] Network node information for the next service initiated by the terminal device;

[0019] Recovery request identifier;

[0020] Context transfer (Transfer) flag;

[0021] The number of remaining context transfers.

[0022] Optionally, the method further comprises at least one of the following:

[0023] The second network node is the next network node covering the location area of ​​the terminal device;

[0024] The second network node is a network node having an X2 link with the first network node;

[0025] The second network node is a network node that initiates a radio resource control connection recovery request from the terminal device;

[0026] The second network node is a network node that initiates a radio resource control connection recovery request for the next service of the terminal device;

[0027] The context transfer flag indicates that the second network node needs to transfer the first information to the next network node covering the location area of ​​the terminal device when the second network node stops serving the location area of ​​the terminal device;

[0028] The remaining number of context transfers indicates the remaining number of times the first information is transferred between network nodes.

[0029] Optionally, the method further comprises at least one of the following:

[0030] When the second network node is the network node that initiates the radio resource control connection recovery request for the terminal device or the next service, the first information is transferred to the second network node through at least one transfer operation;

[0031] The first network node receives next service information sent by the terminal device;

[0032] The first network node sends radio resource control connection release information to the terminal device.

[0033] Optionally, the radio resource control connection release information includes at least one of the following:

[0034] Reason for radio resource control release;

[0035] Recovery request identifier;

[0036] Network node information.

[0037] Optionally, the method further comprises at least one of the following:

[0038] When the number of remaining context transfers is 0, the second network node triggers radio access network paging;

[0039] The network node information indicates the network node information on which the terminal device needs to initiate a radio resource control connection recovery request or the network node information on which the terminal device does not need to initiate a radio resource control connection recovery request;

[0040] The restoration request identifier carries the second network node information.

[0041] The present application also provides a processing method, which can be applied to a second network node (such as a network device, specifically a base station or a satellite), comprising the steps of:

[0042] S2: The second network node obtains first information provided by the first network node.

[0043] Optionally, the method further comprises at least one of the following:

[0044] The first information is transferred by the first network node to the second network node when a first condition is met, or the first information is obtained from the previous network node when the second network node fails to obtain the first information locally;

[0045] The first information includes at least one of the following: terminal device context, terminal device location information, terminal device service information, network node information for the next service initiated by the terminal device, recovery request identifier, context transfer flag, and number of remaining context transfers.

[0046] Optionally, the first condition is satisfied, including at least one of the following:

[0047] When the first network node receives the context acquisition request sent by the second network node;

[0048] After the first network node suspends the radio resource control connection of the terminal device;

[0049] When the first network node leaves or is about to leave the location area where the terminal device is located.

[0050] Optionally, the method further comprises at least one of the following:

[0051] The second network node is the next network node covering the location area of ​​the terminal device;

[0052] The second network node is a network node having an X2 link with the first network node;

[0053] The second network node is a network node that initiates a radio resource control connection recovery request from the terminal device;

[0054] The second network node is a network node that initiates a radio resource control connection recovery request for the next service of the terminal device;

[0055] The context transfer flag indicates that the second network node needs to transfer the first information to the next network node covering the location area of ​​the terminal device when the second network node stops serving the location area of ​​the terminal device;

[0056] The remaining number of context transfers indicates the remaining number of times the first information is transferred between network nodes.

[0057] Optionally, the method further comprises at least one of the following:

[0058] When the first network node suspends the radio resource control connection of the terminal device, sending radio resource control connection release information to the terminal device;

[0059] When the number of remaining context transfers is 0, the second network node triggers radio access network paging;

[0060] When the second network node suspends the radio resource control connection of the terminal device, the second network node sends radio resource control connection release information to the terminal device;

[0061] When the second network node is the network node that initiates the radio resource control connection recovery request when the terminal device initiates or initiates the next service, the first information is transferred to the second network node through at least one transfer operation.

[0062] Optionally, the radio resource control connection release information includes at least one of the following:

[0063] Reason for radio resource control release;

[0064] Recovery request identifier;

[0065] Network node information.

[0066] Optionally, the method further comprises at least one of the following:

[0067] The network node information indicates the network node information on which the terminal device needs to initiate a radio resource control connection recovery request or the network node information on which the terminal device does not need to initiate a radio resource control connection recovery request;

[0068] The restoration request identifier carries the second network node information.

[0069] This application also provides a processing method that can be applied to a terminal device (such as a mobile phone), comprising the steps of:

[0070] S3: In response to the second condition being met, the terminal device sends a radio resource control connection recovery request to the second network node, so that the second network node obtains the first information based on the radio resource control connection recovery request.

[0071] Optionally, the method further comprises at least one of the following:

[0072] The first information is transferred by the first network node to the second network node when a first condition is met, or the second network node obtains the first information from the previous network node when the second network node fails to obtain the first information locally;

[0073] The second condition is satisfied, including at least one of the following: the second network node is the network node carrying the recovery request identifier, the second network node is the network node where the terminal device needs to initiate the request, and the terminal device has uplink service to send;

[0074] The first information includes at least one of the following: terminal device context, terminal device location information, terminal device service information, network node information for the next service initiated by the terminal device, recovery request identifier, context transfer flag, and number of remaining context transfers.

[0075] Optionally, satisfying the first condition includes at least one of the following:

[0076] When the first network node receives the context acquisition request sent by the second network node;

[0077] After the first network node suspends the radio resource control connection of the terminal device;

[0078] When the first network node leaves or is about to leave the location area where the terminal device is located.

[0079] Optionally, the method further comprises at least one of the following:

[0080] The second network node is the next network node covering the location area of ​​the terminal device;

[0081] The second network node is a network node having an X2 link with the first network node;

[0082] The second network node is a network node that initiates a radio resource control connection recovery request from the terminal device;

[0083] The second network node is the network node that initiates the radio resource control connection recovery request for the next service of the terminal device; the context transfer flag indicates that the second network node needs to transfer the first information to the next network node covering the location area of ​​the terminal device when it stops serving the location area of ​​the terminal device;

[0084] The remaining number of context transfers represents the remaining number of times the first information is transferred between network nodes;

[0085] When the second network node is the network node that initiates the radio resource control connection recovery request for the terminal device or the next service, the first information is transferred to the second network node through at least one transfer operation.

[0086] Optionally, the method further comprises at least one of the following:

[0087] The terminal device sends next service information to the first network node;

[0088] The terminal device receives radio resource control connection release information sent by the first network node and / or the second network node.

[0089] Optionally, the radio resource control connection release information includes at least one of the following:

[0090] Reason for radio resource control release;

[0091] Recovery request identifier;

[0092] Network node information.

[0093] Optionally, the method further comprises at least one of the following:

[0094] The network node information indicates the network node information on which the terminal device needs to initiate a radio resource control connection recovery request or the network node information on which the terminal device does not need to initiate a radio resource control connection recovery request;

[0095] The restoration request identifier carries the second network node information.

[0096] The present application also provides a processing device, comprising:

[0097] Means are provided for providing, via the first network node, first information to the second network node in response to a first condition being satisfied.

[0098] The present application also provides a processing device, comprising:

[0099] The acquisition module is configured to acquire first information provided by the first network node.

[0100] The present application also provides a processing device, comprising:

[0101] The sending module sends a radio resource control connection restoration request to the second network node in response to satisfying the second condition, so that the second network node obtains the first information based on the radio resource control connection restoration request.

[0102] The present application also provides a communication device, comprising: a memory, a processor, and a processing program stored in the memory and executable on the processor, wherein the processing program implements the steps of any of the above-described processing methods when executed by the processor.

[0103] The communication device in this application may be a first network node (such as a network device, specifically a base station, satellite) or a second network node (such as a network device, specifically a base station, satellite) or a terminal device (such as a mobile phone). The specific reference needs to be clarified in combination with the context.

[0104] The present application also provides a storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of any of the above-described processing methods are implemented.

[0105] The technical solution of the present application is that in response to satisfying the first condition, the first network node provides the first information to the second network node. Thus, for the IoT-NTN Regenerative payload scenario, when the terminal device initiates the RRCConnectionResumeRequest, the new network node can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption. BRIEF DESCRIPTION OF THE DRAWINGS

[0106] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification, are used to explain the principles of the present application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for describing the embodiments. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without inventive work.

[0107] FIG1 is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application;

[0108] FIG2 is a diagram of a communication network system architecture provided by an embodiment of the present application;

[0109] FIG3 is a schematic diagram of the hardware structure of a controller 140 provided in this application;

[0110] FIG4 is a schematic diagram of the hardware structure of a network node 150 provided in this application;

[0111] FIG5 is a schematic flow chart of a processing method according to the first embodiment of the present application;

[0112] FIG6 is a schematic diagram of a scenario of a processing method according to a second embodiment of the present application;

[0113] FIG7 is a schematic diagram of a scenario of a processing method according to a fourth embodiment of the present application;

[0114] FIG8 is a flow chart of a processing method according to a sixth embodiment of the present application;

[0115] FIG9 is a flow chart of a processing method according to a seventh embodiment of the present application;

[0116] FIG10 is a schematic diagram of the interaction flow between the first network node, the second network node, and the terminal device according to the processing method of the eighth embodiment of the present application;

[0117] FIG11 is a first structural diagram of a processing device provided in an embodiment of the present application;

[0118] FIG12 is a second structural diagram of a processing device provided in an embodiment of the present application;

[0119] FIG13 is a third structural diagram of a processing device provided in an embodiment of the present application;

[0120] FIG14 is a schematic diagram of the structure of the communication device provided in an embodiment of the present application.

[0121] The purpose of this application, its features, and advantages will be further described in conjunction with the embodiments and with reference to the accompanying drawings. The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and the accompanying text are not intended to limit the scope of the present application in any way, but rather to illustrate the concepts of this application to those skilled in the art by reference to specific embodiments.

[0122] Implementation Methods of the Application

[0123] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0124] It should be noted that, in this document, the terms "comprises", "includes" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element, and / or, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the specific embodiment.

[0125] It should be understood that although the terms "first," "second," "third," etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are used solely to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the term "if," as used herein, may be interpreted as "upon," "when," or "in response to a determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It should be further understood that the terms "comprising" and "including" indicate the presence of the recited features, steps, operations, elements, components, items, types, and / or groups, but do not preclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, types, and / or groups. The terms "or," "and / or," "including at least one of the following," etc., as used herein, may be interpreted as inclusive, meaning any one or any combination. For example, “comprising at least one of the following: A, B, C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”; and for another example, “A, B or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A and B and C”. An exception to this definition will occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some manner.

[0126] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are shown in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless clearly stated herein, the execution of these steps is not strictly limited in order, and they can be performed in other orders. Moreover, at least a portion of the steps in the figure may include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with at least a portion of other steps or sub-steps or stages of other steps.

[0127] As used herein, the words "if" and "if" may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to the determination" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)," depending on the context.

[0128] It should be noted that in this article, step codes such as S1 and S2 are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial restriction on the order. When implementing the step, those skilled in the art may execute S2 first and then S1, etc., but these should all be within the scope of protection of this application.

[0129] It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application.

[0130] In the subsequent description, the use of suffixes such as "module", "component" or "unit" to represent elements is only for the purpose of facilitating the description of the present application and has no specific meaning. Therefore, "module", "component" or "unit" can be used interchangeably.

[0131] The communication device in this application may be a first network node (such as a network device, specifically a base station, satellite) or a second network node (such as a network device, specifically a base station, satellite) or a terminal device (such as a mobile phone). The specific reference needs to be clarified in combination with the context.

[0132] Optionally, the terminal device may be implemented in various forms. For example, the terminal device described in this application may include smart terminal devices such as mobile phones, tablet computers, laptop computers, PDAs, portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, and other fixed terminal devices such as digital TVs and desktop computers.

[0133] The subsequent description will be made using a mobile terminal as an example. Those skilled in the art will understand that, in addition to components specifically used for mobile purposes, the configuration according to the embodiments of the present application can also be applied to fixed-type terminal devices.

[0134] Please refer to Figure 1, which is a schematic diagram of the hardware structure of a mobile terminal for implementing various embodiments of the present application. The mobile terminal 100 may include components such as an RF (Radio Frequency) unit 101, a WiFi module 102, an audio output unit 103, an A / V (Audio / Video) input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, a processor 110, and a power supply 111. Those skilled in the art will understand that the mobile terminal structure shown in Figure 1 does not limit the mobile terminal. The mobile terminal may include more or fewer components than shown, or may combine certain components, or arrange the components differently.

[0135] The following is a detailed introduction to the various components of the mobile terminal in conjunction with Figure 1:

[0136] The RF unit 101 can be used to send and receive information or receive signals during calls. Specifically, it receives downlink information from the base station and transmits it to the processor 110 for processing. It also transmits uplink data to the base station. Typically, the RF unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and / or other components. Furthermore, the RF unit 101 can communicate with the network and other devices via wireless communication. The above-mentioned wireless communications can use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA2000 (Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division Duplexing-Long Term Evolution), TDD-LTE (Time Division Duplexing-Long Term Evolution), 5G and 6G, etc.

[0137] WiFi is a short-range wireless transmission technology. A mobile terminal, through WiFi module 102, enables users to send and receive emails, browse web pages, and access streaming media, providing wireless broadband Internet access. Although FIG1 illustrates WiFi module 102, it is understood that it is not a required component of the mobile terminal and can be omitted as needed without altering the essence of the invention.

[0138] The audio output unit 103 can convert audio data received by the RF unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output it as sound when the mobile terminal 100 is in a call signal reception mode, a talk mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Furthermore, the audio output unit 103 can also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, or the like.

[0139] The A / V input unit 104 is used to receive audio or video signals. The A / V input unit 104 may include a graphics processing unit (GPU) 1041 and a microphone 1042. The GPU 1041 processes image data of still images or videos captured by an image capture device (e.g., a camera) in video capture mode or image capture mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the GPU 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the RF unit 101 or the WiFi module 102. The microphone 1042 may receive sound (audio data) in operating modes such as a phone call mode, a recording mode, and a voice recognition mode, and may process such sound into audio data. In the phone call mode, the processed audio (voice) data may be converted into a format that can be transmitted to a mobile communication base station via the RF unit 101. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to eliminate (or suppress) noise or interference generated during the reception and transmission of audio signals.

[0140] The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor and a proximity sensor. Optionally, the ambient light sensor can adjust the brightness of the display panel 1061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 1061 and / or the backlight when the mobile terminal 100 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that recognize the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can be configured in the mobile phone, such as fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be described here.

[0141] The display unit 106 is used to display information input by the user or information provided to the user. The display unit 106 may include a display panel 1061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0142] The user input unit 107 can be used to receive input digital or character information and generate key signal input related to user settings and function control of the mobile terminal. Optionally, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also known as a touch screen, can collect user touch operations on or near it (such as operations performed by the user using a finger, stylus, or any other suitable object or accessory on or near the touch panel 1071) and drive corresponding connected devices according to a pre-set program. The touch panel 1071 may include two parts: a touch detection device and a touch controller. Optionally, the touch detection device detects the user's touch direction and detects the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 110. It can also receive and execute commands sent by the processor 110. And / or, the touch panel 1071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may further include other input devices 1072. Optionally, the other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, power keys, etc.), a trackball, a mouse, a joystick, etc., and the specifics are not limited here.

[0143] Optionally, the touch panel 1071 may overlay the display panel 1061. When the touch panel 1071 detects a touch operation on or near it, it transmits the information to the processor 110 to determine the type of touch event. The processor 110 then provides a corresponding visual output on the display panel 1061 based on the type of touch event. Although in FIG1 , the touch panel 1071 and the display panel 1061 are shown as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, which is not limited to this specific embodiment.

[0144] The interface unit 108 serves as an interface through which at least one external device can be connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, etc. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and an external device.

[0145] Memory 109 can be used to store software programs and various data. Memory 109 may primarily include a program storage area and a data storage area. Optionally, the program storage area may store an operating system and at least one application required for a function (such as a sound playback function or an image playback function); the data storage area may store data generated based on the use of the mobile phone (such as audio data, a phone book, etc.). Furthermore, / or, memory 109 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0146] Processor 110 is the control center of the mobile terminal, connecting all components of the mobile terminal using various interfaces and circuits. By running or executing software programs and / or modules stored in memory 109 and accessing data stored in memory 109, it executes various functions of the mobile terminal and processes data, thereby providing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, processor 110 may integrate an application processor and a modem processor. Optionally, the application processor primarily handles the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into processor 110.

[0147] The mobile terminal 100 may also include a power supply 111 (such as a battery) for supplying power to various components. Preferably, the power supply 111 may be logically connected to the processor 110 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.

[0148] Although not shown in FIG. 1 , the mobile terminal 100 may further include a Bluetooth module, etc., which will not be described in detail here.

[0149] To facilitate understanding of the embodiments of the present application, the communication network system on which the mobile terminal of the present application is based is described below.

[0150] Please refer to Figure 2, which is a communication network system architecture diagram provided in an embodiment of the present application. The communication network system is an NR (New Radio) system of universal mobile communication technology. The NR system includes UE (User Equipment) 201, E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, EPC (Evolved Packet Core) 203 and the operator's IP service 204, which are connected in sequence.

[0151] Optionally, UE201 may be the above-mentioned terminal device 100, which will not be described in detail here.

[0152] E-UTRAN 202 includes eNodeB 2021 and other eNodeBs 2022 . Optionally, eNodeB 2021 may be connected to other eNodeBs 2022 via a backhaul (eg, an X2 interface). eNodeB 2021 is connected to EPC 203 , and eNodeB 2021 may provide access from UE 201 to EPC 203 .

[0153] EPC 203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving Gate Way) 2034, a PGW (PDN Gate Way) 2035, and a PCRF (Policy and Charging Rules Function) 2036. Optionally, MME 2031 is a control node that processes signaling between UE 201 and EPC 203, providing bearer and connection management. HSS 2032 provides registers for managing functions such as the Home Location Register (not shown) and stores user-specific information such as service features and data rates. All user data can be sent through SGW2034, PGW2035 can provide IP address allocation and other functions for UE 201, PCRF2036 is the policy and charging control policy decision point for service data flow and IP bearer resources, and it selects and provides available policy and charging control decisions for the policy and charging execution function unit (not shown in the figure).

[0154] The IP service 204 may include the Internet, an intranet, an IMS (IP Multimedia Subsystem), or other IP services.

[0155] Although the above introduction takes the LTE system as an example, those skilled in the art should know that this application is not only applicable to the LTE system, but can also be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, 5G and future new network systems (such as 6G), etc., which are not limited here.

[0156] FIG3 is a schematic diagram of the hardware structure of a controller 140 provided in this application. The controller 140 includes a memory 1401 and a processor 1402. The memory 1401 is used to store program instructions, and the processor 1402 is used to call the program instructions in the memory 1401 to execute the steps performed by the controller in the first embodiment of the above method. The implementation principles and beneficial effects are similar and will not be repeated here.

[0157] Optionally, the controller further includes a communication interface 1403, which can be connected to the processor 1402 via a bus 1404. The processor 1402 can control the communication interface 1403 to implement the receiving and sending functions of the controller 140.

[0158] Figure 4 is a schematic diagram of the hardware structure of a network node 150 provided in this application. Network node 150 includes: a memory 1501 and a processor 1502. Memory 1501 is used to store program instructions, and processor 1502 is used to call the program instructions in memory 1501 to execute the steps performed by the first node in the first embodiment of the above method. The implementation principles and beneficial effects are similar and will not be repeated here.

[0159] Optionally, the controller further includes a communication interface 1503, which can be connected to the processor 1502 via a bus 1504. The processor 1502 can control the communication interface 1503 to implement the receiving and sending functions of the network node 150.

[0160] The integrated modules implemented in the form of software function modules can be stored in a computer-readable storage medium. The software function modules stored in a storage medium include a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute some of the steps of the methods of various embodiments of the present application.

[0161] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can 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 the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state drive solid state disk, SSD), etc.

[0162] Based on the above-mentioned mobile terminal hardware structure and communication network system, various embodiments of the present application are proposed.

[0163] Technical terms involved in this embodiment:

[0164] RRC: Radio Resource Control;

[0165] RAN: Radio Access Network;

[0166] RRCConnectionRelease: RRC connection release message;

[0167] IoT-NTN Regenerative payload: Internet of Things Non-Terrestrial Network, IoT-NTN Regenerative payload;

[0168] NB-IoT: Narrow Band Internet of Things;

[0169] CIoT: Cellular Internet of Things

[0170] EPS: Evolved Packet System;

[0171] 5GS: 5G System, 5G system;

[0172] NB-IoT User Plane CIoT EPS / 5GS optimization: NB-IoT user plane CIoT EPS / 5GS optimization;

[0173] eNB on satellite: satellite base station;

[0174] Retrieve UE Context procedure: Retrieve UE context procedure;

[0175] RRCConnectionResumeRequest: RRC connection resumption request;

[0176] RRC connection resume procedures: RRC connection resume procedures;

[0177] SRB: Signaling Radio Bearer

[0178] DRB: Data Radio Bearer, data radio bearer;

[0179] Resume ID: resume request identifier;

[0180] RRC IDLE state: radio resource control idle state;

[0181] Transfer: transfer or transmit.

[0182] First embodiment

[0183] 5 , which is a flow chart of a processing method according to a first embodiment of the present application, the processing method according to the embodiment of the present application can be applied to a first network node (such as a network device, specifically a base station or a satellite), and includes the following steps:

[0184] S1: In response to a first condition being met, the first network node provides first information to the second network node.

[0185] This embodiment is primarily applicable to IoT-NTN Regenerative Payload scenarios. In these scenarios, due to high satellite speed and short coverage, when a terminal device with a suspended RRC connection initiates an RRCConnectionResumeRequest, the serving satellite to which the terminal device is connected has changed. Therefore, the current serving satellite (new eNB) needs to initiate a Retrieve UE Context procedure from the satellite with the suspended RRC connection (old eNB) to retrieve the terminal device context. Due to the rapid satellite movement, there may be no inter-satellite link (ISL) / neighborhood relationship / X2 interface between the new and old eNBs. Therefore, the new eNB cannot initiate a Retrieve UE Context procedure to retrieve the terminal device context from the old eNB, rendering UP CIoT EPS / 5GS optimization unusable. At this point, the terminal device needs to fall back to the RRC re-establishment process, which is not conducive to saving signaling overhead and / or reducing power consumption.

[0186] Therefore, for the IoT-NTN Regenerative payload scenario, in this embodiment, in response to satisfying the first condition, the first network node provides the first information to the second network node, so that when the terminal device initiates RRCConnectionResumeRequest, the new network node (second network node) can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0187] Optionally, the first network node is an old network node, and the second network node is a new network node.

[0188] Optionally, the first network node is a network node that suspends the RRC connection for the terminal device or a network node that last covers the location area of ​​the terminal device.

[0189] Optionally, the second network node is a next network node covering the location area of ​​the terminal device.

[0190] Optionally, the second network node is a network node having an X2 link with the first network node.

[0191] Optionally, the second network node is a network node that initiates a radio resource control connection recovery request from the terminal device.

[0192] Optionally, the second network node is the network node that initiates a radio resource control connection recovery request for the next service of the terminal device.

[0193] Optionally, the first condition is satisfied, including at least one of the following:

[0194] When the first network node receives the context acquisition request sent by the second network node;

[0195] After the first network node suspends the radio resource control connection of the terminal device;

[0196] When the first network node leaves or is about to leave the location area where the terminal device is located.

[0197] Optionally, the first network node independently determines that the terminal device has left or is about to leave the location area.

[0198] Optionally, the specific situation of the first network node leaving the location area of ​​the terminal device, for example, presetting a certain spatial range or time interval, or instantly calculating the time when the first network node leaves the location area of ​​the terminal device.

[0199] Optionally, the location area where the terminal device is located can be at least one of the location information reported by the terminal device, the mapping cell ID where the terminal device is located, the tracking area of ​​the terminal device, or the coverage area when the network node provides services to the terminal device.

[0200] Optionally, the first information includes at least one of the following: terminal device context, terminal device location information, terminal device service information, network node information for the next service initiated by the terminal device, recovery request identifier, context transfer (Transfer) flag, and number of remaining context transfers (Transfer) times.

[0201] Optionally, the context transfer flag indicates that the second network node needs to transfer the first information to a next network node covering the location area of ​​the terminal device when the second network node stops serving the location area of ​​the terminal device.

[0202] Optionally, the remaining number of context transfers represents the remaining number of times the first information is transferred between network nodes.

[0203] Optionally, when the number of remaining context transfers is 0, the second network node triggers radio access network paging.

[0204] Optionally, when the second network node is the network node that initiates the radio resource control connection recovery request for the terminal device or the next service, the first information is transferred to the second network node through at least one transfer operation.

[0205] Optionally, when the first network node decides to suspend the RRC connection for the terminal device, the first network node sends radio resource control connection release information to the terminal device.

[0206] Optionally, the radio resource control connection release information includes at least one of the following: a radio resource control release reason, a recovery request identifier, and network node information.

[0207] Optionally, the radio resource control release reason includes: RRC connection suspension.

[0208] Optionally, the network node information indicates network node information for which the terminal device needs to initiate a radio resource control connection recovery request or network node information for which the terminal device does not need to initiate a radio resource control connection recovery request.

[0209] Optionally, before deciding to suspend the RRC connection for the terminal device, the first network node receives next service information reported by the terminal device; optionally, the next service information represents the time information of the next service of the terminal device and / or the location of the terminal device.

[0210] Optionally, the first network node confirms information of a second network node that (may) cover the location area of ​​the terminal device when the terminal device performs a next service based on the service information reported by the terminal device.

[0211] Optionally, the recovery request identifier included in the radio resource control connection release information sent by the first network node to the terminal device carries the second network node information.

[0212] Through the technical solution of this embodiment, in response to satisfying the first condition, the first network node provides the first information to the second network node. Therefore, for the IoT-NTN Regenerative payload scenario, when the terminal device initiates RRCConnectionResumeRequest, the new network node can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0213] Second embodiment

[0214] Based on the first embodiment, the second embodiment of the present application proposes a processing method, in which the first network node (old network node) transfers the terminal device context to the next location area covering the terminal device through one or more transfer operations, so that the new network node where the terminal device initiates RRCConnectionResumeRequest can obtain the terminal device context.

[0215] Optionally, in response to the first condition being met, the first network node provides the first information to the second network node.

[0216] Optionally, the first network node is an old network node, and the second network node is a new network node.

[0217] Optionally, the first network node is a network node that suspends the RRC connection for the terminal device or a network node that last covers the location area of ​​the terminal device.

[0218] Optionally, the second network node is a next network node covering the location area of ​​the terminal device.

[0219] Optionally, the second network node is a network node having an X2 link with the first network node.

[0220] Optionally, the first condition is satisfied, including at least one of the following:

[0221] After the first network node suspends the radio resource control connection of the terminal device;

[0222] When the first network node leaves or is about to leave the location area where the terminal device is located.

[0223] Optionally, the first network node independently determines that the terminal device has left or is about to leave the location area.

[0224] Optionally, the specific situation of the first network node leaving the location area of ​​the terminal device, for example, presetting a certain spatial range or time interval, or instantly calculating the time when the first network node leaves the location area of ​​the terminal device.

[0225] Optionally, the location area where the terminal device is located can be at least one of the location information reported by the terminal device, the mapping cell ID where the terminal device is located, the tracking area of ​​the terminal device, or the coverage area when the network node provides services to the terminal device.

[0226] Optionally, the first information includes at least one of the following: terminal device context, terminal device location information, resume request identifier (Resume ID), context transfer flag (context_transfer_flag), and context remaining transfer count (context_transfer_num).

[0227] Optionally, the context transfer flag indicates that the second network node needs to transfer the first information to a next network node covering the location area of ​​the terminal device when the second network node stops serving the location area of ​​the terminal device.

[0228] Optionally, the remaining number of context transfers represents the remaining number of times the first information is transferred between network nodes.

[0229] Optionally, when the number of remaining context transfers is 0, the second network node triggers radio access network paging.

[0230] Optionally, when the first network node decides to suspend the RRC connection for the terminal device, the first network node sends radio resource control connection release information to the terminal device.

[0231] Optionally, the radio resource control connection release information includes at least one of the following: a radio resource control release reason and a recovery request identifier.

[0232] Optionally, the radio resource control release reason includes: RRC connection suspension.

[0233] The following describes this embodiment in detail with reference to specific scenarios:

[0234] As shown in Figure 6, for the IoT-NTN Regenerative payload scenario, the satellite moves at high speed, and the direction of satellite movement is shown by the arrow in Figure 6. For example, if the current satellite serving the terminal device area is satellite A, the next satellites serving the area in turn are satellite B, satellite C, satellite D, satellite E, and satellite F. The specific processing flow includes:

[0235] Step 1: The current satellite (old eNB, such as Satellite A in Figure 6 ) decides to suspend the RRC connection and sends an RRCConnectionRelease message to the terminal device with the releaseCause being rrc-Suspend. Optionally, the RRCConnectionRelease message also carries a Resume ID, which is used to identify the terminal device context.

[0236] Step 2: After receiving the RRCConnectionRelease message, the terminal device retains the AS context (access layer context), suspends all SRBs (signaling radio bearers) and DRBs (data radio bearers), and enters the RRC_IDLE state.

[0237] Step 3: The satellite (eNB) continues to move. When the current satellite (old eNB) moves out of the location area where the terminal device is located, the following information is sent to the next satellite covering the area (Satellite B as shown in Figure 6):

[0238] Terminal device context, terminal device location information, Resume ID sent to the terminal device, context transfer flag context_transfer_flag, and context remaining transfer count context_transfer_num.

[0239] Optionally, the context transfer identifier is used to inform the next satellite (eNB) that it needs to transfer the terminal device context to the next satellite covering the location area when it stops serving the location area of ​​the terminal device.

[0240] Optionally, the number of remaining context transfers indicates the number of times the terminal device context can be transferred between satellites, to prevent the terminal device context from being transferred between satellites for a long time, which may cause a mismatch with the satellite that actually serves the terminal device.

[0241] Step 4. When the next satellite (satellite B as shown in Figure 6) moves out of the area where the terminal device is located, the terminal device context, terminal device location information, Resume ID, context transfer identifier context_transfer_flag, and the number of remaining context transfers context_transfer_num-1 are sent to the next satellite covering the area (such as satellite C as shown in Figure 6).

[0242] Repeat step 4. When the number of remaining context transfers is 0, the satellite (eNB) needs to actively trigger RAN (Radio Access Network) paging to update the terminal device context.

[0243] Step 5: Due to satellite movement, the satellite covering the terminal device location changes, and the terminal device reselects a cell.

[0244] Optionally, when the terminal device has uplink data to send, the terminal device initiates an RRCConnectionResumeRequest to the current satellite (new eNB, such as satellite D shown in FIG6 ), and the RRCConnectionResumeRequest carries a resume ID.

[0245] Optionally, after the current satellite (new eNB) receives the request, the current satellite directly obtains the terminal device context from the local through the resume ID. If the acquisition fails, it falls back to the RRC establishment process.

[0246] Optionally, when the current satellite (satellite D as shown in Figure 6) fails to obtain the terminal device context from the local area, it attempts to request the terminal device context from the last satellite covering the area (satellite C as shown in Figure 6). If the acquisition fails, it falls back to the RRC establishment process.

[0247] Through the technical solution of this embodiment, in response to satisfying the first condition, the first network node provides the first information to the second network node, and the first network node (the old network node) transfers the terminal device context to the next covering terminal device location area through one or more transfer operations, so that the new network node to which the terminal device initiates the RRCConnectionResumeRequest can obtain the terminal device context. Therefore, for the IoT-NTN Regenerative payload scenario NB-IoT User Plane CIoT EPS / 5GS optimization, the satellite moves rapidly. When the terminal device initiates the RRCConnectionResumeRequest, the new network node can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0248] Third embodiment

[0249] Based on any of the above embodiments of the present application, the third embodiment of the present application proposes a processing method, in which the first network node (old network node) transfers the terminal device context to the new network node that (may) cover the terminal device location area when the terminal device next services through one or more transfer operations based on the information of the new network node that (may) cover the terminal device location area when the terminal device next services, so that the new network node to which the terminal device initiates RRCConnectionResumeRequest can obtain the terminal device context.

[0250] Optionally, in response to the first condition being met, the first network node provides the first information to the second network node.

[0251] Optionally, the first network node is an old network node, and the second network node is a new network node.

[0252] Optionally, the first network node is a network node that suspends the RRC connection for the terminal device or a network node that last covers the location area of ​​the terminal device.

[0253] Optionally, the second network node is a next network node covering the location area of ​​the terminal device.

[0254] Optionally, the second network node is a network node having an X2 link with the first network node.

[0255] Optionally, the second network node is the network node that initiates a radio resource control connection recovery request for the next service of the terminal device.

[0256] Optionally, the first condition is satisfied, including at least one of the following:

[0257] After the first network node suspends the radio resource control connection of the terminal device;

[0258] When the first network node leaves or is about to leave the location area where the terminal device is located.

[0259] Optionally, the first network node independently determines that the terminal device has left or is about to leave the location area.

[0260] Optionally, the specific situation of the first network node leaving the location area of ​​the terminal device, for example, presetting a certain spatial range or time interval, or instantly calculating the time when the first network node leaves the location area of ​​the terminal device.

[0261] Optionally, the location area where the terminal device is located can be at least one of the location information reported by the terminal device, the mapping cell ID where the terminal device is located, the tracking area of ​​the terminal device, or the coverage area when the network node provides services to the terminal device.

[0262] Optionally, the first information includes at least one of the following: terminal device context, terminal device location information, terminal device service information, and network node information for the terminal device to initiate a service next time.

[0263] Optionally, the first information is transferred to the second network node through at least one transfer operation.

[0264] Optionally, when the first network node decides to suspend the RRC connection for the terminal device, the first network node sends radio resource control connection release information to the terminal device.

[0265] Optionally, the radio resource control connection release information includes at least one of the following: a radio resource control release reason, a recovery request identifier, and network node information.

[0266] Optionally, the radio resource control release reason includes: RRC connection suspension.

[0267] Optionally, before deciding to suspend the RRC connection for the terminal device, the first network node receives next service information reported by the terminal device; optionally, the next service information represents the time information of the next service of the terminal device and / or the location of the terminal device.

[0268] Optionally, the first network node confirms information of a second network node that (may) cover the location area of ​​the terminal device when the terminal device performs a next service based on the service information reported by the terminal device.

[0269] Optionally, the recovery request identifier included in the radio resource control connection release information sent by the first network node to the terminal device carries the second network node information.

[0270] The following describes this embodiment in detail with reference to specific scenarios:

[0271] Step 1: The terminal device sends the next service information to the current satellite (old eNB). The service information indicates the time information of the next service of the terminal device and the location of the terminal device.

[0272] Step 2: The current satellite (old eNB) confirms the satellite (new eNB) information that (may) cover the terminal device's location area during the next service of the terminal device based on the service information reported by the terminal device.

[0273] Step 3: The current satellite (old eNB) decides to suspend the RRC connection and sends an RRCConnectionRelease message to the terminal device with the releaseCause set to rrc-Suspend. The RRCConnectionRelease message also carries the Resume ID, which contains information about the satellite (new eNB) that will cover the terminal device's location area during the next terminal service.

[0274] Step 4: After receiving the RRCConnectionRelease message, the terminal device retains the AS context, suspends all SRBs and DRBs, and enters the RRC_IDLE state.

[0275] Step 5: The current satellite (old eNB) transfers the following information to the next satellite covering the terminal device location area:

[0276] Terminal device context, terminal device location information, terminal device service information, and satellite (new eNB) information covering the terminal device location area during the next service.

[0277] Optionally, the next satellite covering the terminal device location area may be the next satellite or the next-next satellite, as long as there is an X2 interface between the satellite and the current satellite. The specific satellite to be transferred to is independently implemented by the current satellite.

[0278] Step 6: After receiving the above information, the next satellite transfers the same information to the next satellite.

[0279] Repeat step 6 until the above information is transferred to the satellite (new eNB) that covers the terminal device's location area when the terminal device performs the next service.

[0280] Step 7: The terminal device initiates an RRCConnectionResumeRequest to the satellite (new eNB) carried by the Resume ID. The message carries the Resume ID.

[0281] Step 8: The current satellite obtains the terminal device context directly from the local through the resume ID. If the acquisition fails, it falls back to the RRC establishment process.

[0282] Through the technical solution of this embodiment, in response to satisfying the first condition, the first network node provides the first information to the second network node, and the first network node (old network node) transfers the terminal device context to the satellite (new eNB) that (may) cover the terminal device location area when the terminal device next services through one or more transfer operations based on the satellite (new eNB) information that (may) cover the terminal device location area when the terminal device next services, so that the new network node where the terminal device initiates RRCConnectionResumeRequest can obtain the terminal device context. Therefore, for the IoT-NTN Regenerative payload scenario, when the terminal device initiates RRCConnectionResumeRequest, the new network node can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0283] Fourth embodiment

[0284] Based on any of the above embodiments of the present application, the fourth embodiment of the present application proposes a processing method, where the first network node (old network node) knows the network node information (new network node, i.e., the second network node) that has an X2 connection with the first network node and will next serve the terminal device area. When the terminal device initiates an RRCConnectionResumeRequest to the second network node, the second network node obtains the terminal device context from the first network node, so that the new network node (second network node) to which the terminal device initiates the RRCConnectionResumeRequest can obtain the terminal device context.

[0285] Optionally, in response to the first condition being met, the first network node provides the first information to the second network node.

[0286] Optionally, the first network node is an old network node, and the second network node is a new network node.

[0287] Optionally, the first network node is a network node that suspends the RRC connection for the terminal device or a network node that last covers the location area of ​​the terminal device.

[0288] Optionally, the second network node is a network node having an X2 link with the first network node.

[0289] Optionally, the second network node is a network node that initiates a radio resource control connection recovery request from the terminal device.

[0290] Optionally, the first condition is satisfied, including when the first network node receives a context acquisition request sent by the second network node.

[0291] Optionally, the first information includes: terminal device context.

[0292] Optionally, when the first network node decides to suspend the RRC connection for the terminal device, the first network node sends radio resource control connection release information to the terminal device.

[0293] Optionally, the radio resource control connection release information includes at least one of the following: a radio resource control release reason, a recovery request identifier, and network node information.

[0294] Optionally, the radio resource control release reason includes: RRC connection suspension.

[0295] Optionally, the network node information represents the network node information to which the terminal device needs to initiate a radio resource control connection recovery request.

[0296] Optionally, the network node to which the terminal device needs to initiate a radio resource control connection recovery request is a second network node having an X2 link with the first network node.

[0297] Optionally, the first network node is the current network node. The first network node knows information about the network node that has an X2 connection with the first network node and will subsequently serve the terminal device area. As shown in Figure 7, for example, the first network node is satellite A. The network nodes that subsequently serve the area are satellite B, satellite C, satellite D, satellite E, satellite F, etc. Optionally, satellite A has X2 connections with satellites B, C, and D, but not with satellite E. Satellites B, C, and D can directly obtain the terminal device context from satellite A. The terminal device does not need to initiate a radio resource control connection recovery request to satellites B and C. The network node to which the terminal device needs to initiate the radio resource control connection recovery request is satellite D (i.e., the second network node), so that satellite E can subsequently obtain the terminal device context from satellite D.

[0298] In this embodiment, when the first network node decides to suspend the RRC connection for the terminal device, the radio resource control connection release information sent by the first network node to the terminal device carries the network node information that the terminal device needs to initiate a radio resource control connection recovery request, for example, the information of satellite D is provided to the terminal device through RRCConnectionRelease.

[0299] The following describes this embodiment in detail with reference to specific scenarios:

[0300] As shown in Figure 7, for the IoT-NTN Regenerative payload scenario, assuming that the satellite can establish X2 connections with multiple nearby satellites through ISL, the specific processing flow includes:

[0301] Step 1: The current satellite (old eNB) decides to suspend the RRC connection and sends an RRCConnectionRelease message to the terminal device with the releaseCause set to rrc-Suspend. The RRCConnectionRelease message also carries the Resume ID and information about the satellite (new eNB) for which the terminal device needs to initiate the RRC connection resume procedures.

[0302] Optionally, the current satellite knows the satellite information that has an X2 connection with the satellite and will serve the terminal device area next. For example, the current satellite is satellite A, and the satellites that serve the area next are satellite B, satellite C, satellite D, satellite E, satellite F...., where satellite A has an X2 connection with satellites B, C, and D, but does not have an X2 connection with satellite E. Then satellite A provides the information of satellite D to the terminal device through RRCConnectionRelease.

[0303] Step 2: After receiving the RRCConnectionRelease message, the terminal device retains the AS context, suspends all SRBs and DRBs, and enters the RRC_IDLE state.

[0304] Step 3. When the terminal device reselects a cell, if the terminal device reselects the satellite (new eNB, such as satellite D) provided by the RRCConnectionRelease message, the terminal device initiates an RRCConnectionResumeRequest message to the satellite (new eNB) currently covering the area, such as satellite D. The RRCConnectionResumeRequest message carries Resume ID and resumeCause. ResumeCause is ue_context_transfer (terminal device context transfer), indicating that the terminal device context needs to be obtained / transferred from the satellite (old eNB) identified by resumeID.

[0305] Step 4: The current satellite (new eNB) initiates the Retrieve UEContext procedure to the old eNB identified by the Resume ID to obtain the terminal device context.

[0306] Step 5: When there is no downlink data to send, the current satellite (new eNB) directly suspends the RRC connection and sends an RRCConnectionRelease message to the terminal device with the releaseCause set to rrc-Suspend. The message also carries the Resume ID and information about the satellite (eNB) for which the terminal device needs to initiate the RRC connection resume procedures.

[0307] That is, when the resumeCause received is ue_context_transfer, the new eNB directly suspends the RRC connection after obtaining the terminal device context and does not enter the RRC resume process, thereby saving signaling overhead.

[0308] Through the technical solution of this embodiment, in response to the first condition being met, the first network node provides the first information to the second network node. The first network node (old network node) knows the network node information (new network node, i.e., second network node) that has an X2 connection with the first network node and will next serve the terminal device area. When the terminal device initiates an RRCConnectionResumeRequest to the second network node, the second network node obtains the terminal device context from the first network node, thereby enabling the new network node (second network node) to which the terminal device initiates the RRCConnectionResumeRequest to obtain the terminal device context. Therefore, for the IoT-NTN Regenerative payload scenario, when the terminal device initiates the RRCConnectionResumeRequest, the new network node can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0309] Fifth embodiment

[0310] Based on any of the above embodiments of the present application, the fifth embodiment of the present application proposes a processing method, in which the RRCConnectionRelease message provided by the first network node (old network node) to the terminal device carries an eNB list, and the eNB list indicates that when the terminal device reselects these eNBs, the terminal device does not need to execute RRCConnectionResumeRequest (RRC connection resumption request). When the terminal device reselects an eNB outside the eNB list (that is, the second network node), it initiates RRCConnectionResumeRequest to the second network node, and the second network node obtains the terminal device context from the first network node according to the request, so that the new network node (second network node) to which the terminal device initiates RRCConnectionResumeRequest can obtain the terminal device context.

[0311] Optionally, in response to the first condition being met, the first network node provides the first information to the second network node.

[0312] Optionally, the first network node is an old network node, and the second network node is a new network node.

[0313] Optionally, the first network node is a network node that suspends the RRC connection for the terminal device or a network node that last covers the location area of ​​the terminal device.

[0314] Optionally, the second network node is a network node having an X2 link with the first network node.

[0315] Optionally, the second network node is a network node that initiates a radio resource control connection recovery request from the terminal device.

[0316] Optionally, the first condition is satisfied, including when the first network node receives a context acquisition request sent by the second network node.

[0317] Optionally, the first information includes: terminal device context.

[0318] Optionally, when the first network node decides to suspend the RRC connection for the terminal device, the first network node sends radio resource control connection release information to the terminal device.

[0319] Optionally, the radio resource control connection release information includes at least one of the following: a radio resource control release reason, a recovery request identifier, and network node information.

[0320] Optionally, the radio resource control release reason includes: RRC connection suspension.

[0321] Optionally, the network node information indicates network node information that the terminal device does not need to initiate a radio resource control connection recovery request.

[0322] Optionally, the network node to which the terminal device needs to initiate a radio resource control connection recovery request is a second network node having an X2 link with the first network node.

[0323] Optionally, the first network node is the current network node. The first network node knows information about the network node that has an X2 connection with the first network node and will subsequently serve the terminal device area. As shown in Figure 7, for example, the first network node is satellite A. The network nodes that subsequently serve the area are satellite B, satellite C, satellite D, satellite E, satellite F, etc. Optionally, satellite A has X2 connections with satellites B, C, and D, but not with satellite E. Satellites B, C, and D can directly obtain the terminal device context from satellite A. The terminal device does not need to initiate a radio resource control connection recovery request to satellites B and C. The network node to which the terminal device needs to initiate the radio resource control connection recovery request is satellite D (i.e., the second network node), so that satellite E can subsequently obtain the terminal device context from satellite D.

[0324] In this embodiment, when the first network node decides to suspend the RRC connection for the terminal device, the radio resource control connection release information sent by the first network node to the terminal device carries network node information that the terminal device does not need to initiate a radio resource control connection recovery request, for example, the information of satellites B and C is provided to the terminal device through RRCConnectionRelease.

[0325] The following describes this embodiment in detail with reference to specific scenarios:

[0326] As shown in Figure 7, for the IoT-NTN Regenerative payload scenario, assuming that the satellite can establish X2 connections with multiple nearby satellites through ISL, the specific processing flow includes:

[0327] Step 1: The current satellite (old eNB) decides to suspend the RRC connection and sends an RRCConnectionRelease message to the terminal device with the releaseCause set to rrc-Suspend. The RRCConnectionRelease message carries both the Resume ID and the eNB list. The eNB list indicates that when the terminal device reselects to these eNBs, it does not need to perform an RRC connection resume request.

[0328] Step 2: After receiving the RRCConnectionRelease message, the terminal device retains the AS context, suspends all SRBs and DRBs, and enters the RRC_IDLE state.

[0329] Step 3: Due to satellite movement, the terminal device reselects a cell:

[0330] When the cell reselected by the terminal device belongs to the eNB list provided by the RRCConnectionRelease message, the terminal device does not initiate an RRCConnectionResumeRequest.

[0331] When the cell reselected by the terminal device does not belong to the eNB list provided by the RRCConnectionRelease message, the terminal device initiates RRCConnectionResumeRequest, which carries the Resume ID and resumeCause. If resumeCause is ue_context_transfer, it means that the terminal device context needs to be obtained / transferred from the satellite (old eNB) identified by resumeID.

[0332] Step 4: The current satellite (new eNB) initiates the Retrieve UE Context procedure to the old eNB identified by the Resume ID to obtain the terminal device context.

[0333] Step 5: When there is no downlink data to send, the current satellite (new eNB) decides to suspend the RRC connection and sends an RRCConnectionRelease message to the terminal device with the releaseCause set to rrc-Suspend. The RRCConnectionRelease message also carries the Resume ID and the eNB list, triggering the process in Step 1.

[0334] Through the technical solution of this embodiment, in response to the first condition being met, the first network node provides the first information to the second network node, and the RRCConnectionRelease message provided by the first network node (old network node) to the terminal device carries an eNB list. The eNB list indicates that when the terminal device reselects to these eNBs, the terminal device does not need to execute RRCConnectionResumeRequest (RRC connection recovery request). When the terminal device reselects to an eNB outside the eNB list (i.e., the second network node), it initiates RRCConnectionResumeRequest to the second network node. The second network node obtains the terminal device context from the first network node according to the request, so that the new network node (second network node) to which the terminal device initiates RRCConnectionResumeRequest can obtain the terminal device context. Therefore, for the IoT-NTN Regenerative payload scenario, when the terminal device initiates RRCConnectionResumeRequest, the new network node can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0335] Sixth embodiment

[0336] 8 is a flow chart of a processing method according to a sixth embodiment of the present application. The processing method according to the embodiment of the present application can be applied to a network device (such as a base station or a satellite), which can be a second network node. The method includes the following steps:

[0337] S2: The second network node obtains first information provided by the first network node.

[0338] This embodiment is primarily applicable to IoT-NTN Regenerative Payload scenarios. In these scenarios, due to high satellite speed and short coverage, when a terminal device with a suspended RRC connection initiates an RRCConnectionResumeRequest, the serving satellite to which the terminal device is connected has changed. Therefore, the current serving satellite (new eNB) needs to initiate a Retrieve UE Context procedure from the satellite with the suspended RRC connection (old eNB) to retrieve the terminal device context. Due to the rapid satellite movement, there may be no inter-satellite link (ISL) / neighborhood relationship / X2 interface between the new and old eNBs. Therefore, the new eNB cannot initiate a Retrieve UE Context procedure to retrieve the terminal device context from the old eNB, rendering UP CIoT EPS / 5GS optimization unusable. At this point, the terminal device needs to fall back to the RRC re-establishment process, which is not conducive to saving signaling overhead and / or reducing power consumption.

[0339] Therefore, for the IoT-NTN Regenerative payload scenario, in this embodiment, the second network node obtains the first information provided by the first network node, so that when the terminal device initiates RRCConnectionResumeRequest, the new network node can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0340] Optionally, the first information is transferred by the first network node to the second network node when a first condition is met, or the first information is acquired from a previous network node when the second network node fails to acquire the first information locally.

[0341] Optionally, the first network node is an old network node, and the second network node is a new network node.

[0342] Optionally, the first network node is a network node that suspends the RRC connection for the terminal device or a network node that last covers the location area of ​​the terminal device.

[0343] Optionally, the second network node is a next network node covering the location area of ​​the terminal device.

[0344] Optionally, the second network node is a network node having an X2 link with the first network node.

[0345] Optionally, the second network node is a network node that initiates a radio resource control connection recovery request from the terminal device.

[0346] Optionally, the second network node is the network node that initiates a radio resource control connection recovery request for the next service of the terminal device.

[0347] Optionally, satisfying the first condition includes at least one of the following:

[0348] When the first network node receives the context acquisition request sent by the second network node;

[0349] After the first network node suspends the radio resource control connection of the terminal device;

[0350] When the first network node leaves or is about to leave the location area where the terminal device is located.

[0351] Optionally, the first network node independently determines that the terminal device has left or is about to leave the location area.

[0352] Optionally, the specific situation of the first network node leaving the location area of ​​the terminal device, for example, presetting a certain spatial range or time interval, or instantly calculating the time when the first network node leaves the location area of ​​the terminal device.

[0353] Optionally, the location area where the terminal device is located can be at least one of the location information reported by the terminal device, the mapping cell ID where the terminal device is located, the tracking area of ​​the terminal device, or the coverage area when the network node provides services to the terminal device.

[0354] Optionally, the first information includes at least one of the following: terminal device context, terminal device location information, terminal device service information, network node information for the next service initiated by the terminal device, recovery request identifier, context transfer flag, and remaining context transfer times.

[0355] Optionally, the context transfer flag indicates that the second network node needs to transfer the first information to a next network node covering the location area of ​​the terminal device when the second network node stops serving the location area of ​​the terminal device.

[0356] Optionally, the remaining number of context transfers represents the remaining number of times the first information is transferred between network nodes.

[0357] Optionally, when the number of remaining context transfers is 0, the second network node triggers radio access network paging.

[0358] Optionally, when the second network node is the network node that initiates the radio resource control connection recovery request for the terminal device or the next service, the first information is transferred to the second network node through at least one transfer operation.

[0359] Optionally, when the first network node decides to suspend the RRC connection for the terminal device, the first network node sends radio resource control connection release information to the terminal device.

[0360] Optionally, the radio resource control connection release information includes at least one of the following: a radio resource control release reason, a recovery request identifier, and network node information.

[0361] Optionally, the radio resource control release reason includes: RRC connection suspension.

[0362] Optionally, the network node information indicates network node information for which the terminal device needs to initiate a radio resource control connection recovery request or network node information for which the terminal device does not need to initiate a radio resource control connection recovery request.

[0363] Optionally, before deciding to suspend the RRC connection for the terminal device, the first network node receives next service information reported by the terminal device; optionally, the next service information represents the time information of the next service of the terminal device and / or the location of the terminal device.

[0364] Optionally, the first network node confirms information of a second network node that (may) cover the location area of ​​the terminal device when the terminal device performs a next service based on the service information reported by the terminal device.

[0365] Optionally, the recovery request identifier included in the radio resource control connection release information sent by the first network node to the terminal device carries the second network node information.

[0366] The specific process of the second network node acquiring the first information provided by the first network node in the processing method of this embodiment can refer to the above embodiments and will not be described in detail here.

[0367] Through the technical solution of this embodiment, the second network node obtains the first information provided by the first network node. The first information is transferred to the second network node by the first network node when the first condition is met, or the first information is obtained from the previous network node when the second network node fails to obtain it locally. Therefore, for the IoT-NTN Regenerative payload scenario, when the terminal device initiates RRCConnectionResumeRequest, the new network node can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0368] Seventh embodiment

[0369] 9 is a flow chart of a processing method according to a seventh embodiment of the present application. The processing method according to the embodiment of the present application can be applied to a terminal device (such as a mobile phone). The method includes the following steps:

[0370] S3: In response to the second condition being met, the terminal device sends a radio resource control connection recovery request to the second network node, so that the second network node obtains the first information based on the radio resource control connection recovery request.

[0371] This embodiment is primarily applicable to IoT-NTN Regenerative Payload scenarios. In these scenarios, due to high satellite speed and short coverage, when a terminal device with a suspended RRC connection initiates an RRCConnectionResumeRequest, the serving satellite to which the terminal device is connected has changed. Therefore, the current serving satellite (new eNB) needs to initiate a Retrieve UE Context procedure from the satellite with the suspended RRC connection (old eNB) to retrieve the terminal device context. Due to the rapid satellite movement, there may be no inter-satellite link (ISL) / neighborhood relationship / X2 interface between the new and old eNBs. Therefore, the new eNB cannot initiate a Retrieve UE Context procedure to retrieve the terminal device context from the old eNB, rendering UP CIoT EPS / 5GS optimization unusable. At this point, the terminal device needs to fall back to the RRC re-establishment process, which is not conducive to saving signaling overhead and / or reducing power consumption.

[0372] Therefore, for the IoT-NTN Regenerative payload scenario, in this embodiment, in response to meeting the second condition, the terminal device sends a radio resource control connection recovery request to the second network node, so that the second network node obtains the first information based on the radio resource control connection recovery request, so that when the terminal device initiates RRCConnectionResumeRequest, the new network node can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0373] Optionally, the first network node is an old network node, and the second network node is a new network node.

[0374] Optionally, the first network node is a network node that suspends the RRC connection for the terminal device or a network node that last covers the location area of ​​the terminal device.

[0375] Optionally, the second network node is a next network node covering the location area of ​​the terminal device.

[0376] Optionally, the second network node is a network node having an X2 link with the first network node.

[0377] Optionally, the second network node is a network node that initiates a radio resource control connection recovery request from the terminal device.

[0378] Optionally, the second network node is the network node that initiates a radio resource control connection recovery request for the next service of the terminal device.

[0379] Optionally, satisfying the second condition includes at least one of the following: the second network node is the network node carrying the recovery request identifier, the second network node is the network node to which the terminal device needs to initiate the request, and the terminal device has uplink services that need to be sent.

[0380] Optionally, the first information includes at least one of the following: terminal device context, terminal device location information, terminal device service information, network node information for the next service initiated by the terminal device, recovery request identifier, context transfer flag, and remaining context transfer times.

[0381] Optionally, the context transfer flag indicates that the second network node needs to transfer the first information to a next network node covering the location area of ​​the terminal device when the second network node stops serving the location area of ​​the terminal device.

[0382] Optionally, the remaining number of context transfers represents the remaining number of times the first information is transferred between network nodes.

[0383] Optionally, when the number of remaining context transfers is 0, the second network node triggers radio access network paging.

[0384] Optionally, when the second network node is the network node that initiates the radio resource control connection recovery request for the terminal device or the next service, the first information is transferred to the second network node through at least one transfer operation.

[0385] Optionally, the first information is transferred by the first network node to the second network node when a first condition is met, or the second network node obtains the first information from a previous network node when the second network node fails to obtain the first information locally.

[0386] Optionally, satisfying the first condition includes at least one of the following:

[0387] When the first network node receives the context acquisition request sent by the second network node;

[0388] After the first network node suspends the radio resource control connection of the terminal device;

[0389] When the first network node leaves or is about to leave the location area where the terminal device is located.

[0390] Optionally, the first network node independently determines that the terminal device has left or is about to leave the location area.

[0391] Optionally, the specific situation of the first network node leaving the location area of ​​the terminal device, for example, presetting a certain spatial range or time interval, or instantly calculating the time when the first network node leaves the location area of ​​the terminal device.

[0392] Optionally, the location area where the terminal device is located can be at least one of the location information reported by the terminal device, the mapping cell ID where the terminal device is located, the tracking area of ​​the terminal device, or the coverage area when the network node provides services to the terminal device.

[0393] Optionally, the terminal device sends next service information to the first network node. Optionally, the next service information indicates time information of the next service of the terminal device and / or the location of the terminal device.

[0394] Optionally, the first network node receives the next service information reported by the terminal device, and confirms the second network node information that (may) cover the location area of ​​the terminal device during the next service of the terminal device according to the service information reported by the terminal device.

[0395] Optionally, when deciding to suspend the RRC connection for the terminal device, the first network node sends radio resource control connection release information to the terminal device.

[0396] Optionally, when the first network node decides to suspend the RRC connection for the terminal device, the first network node sends radio resource control connection release information to the terminal device.

[0397] Optionally, the terminal device receives radio resource control connection release information sent by the first network node.

[0398] Optionally, the radio resource control connection release information includes at least one of the following: a radio resource control release reason, a recovery request identifier, and network node information.

[0399] Optionally, the radio resource control release reason includes: RRC connection suspension.

[0400] Optionally, the network node information indicates network node information for which the terminal device needs to initiate a radio resource control connection recovery request or network node information for which the terminal device does not need to initiate a radio resource control connection recovery request.

[0401] Optionally, the recovery request identifier included in the radio resource control connection release information sent by the first network node to the terminal device carries the second network node information.

[0402] Optionally, when the terminal device has uplink data to send, the terminal device initiates an RRCConnectionResumeRequest to the second network node, where the RRCConnectionResumeRequest carries a resume ID.

[0403] Optionally, when the second network node receives the RRCConnectionResumeRequest, it directly obtains the terminal device context locally according to the resume ID. If the acquisition fails, it falls back to the RRC establishment process.

[0404] Optionally, when the second network node fails to obtain the terminal device context locally, it attempts to request the terminal device context from the last network node covering the area, and if the acquisition fails, it falls back to the RRC establishment process.

[0405] Optionally, when the terminal device has no downlink data to send, the second network node directly suspends the RRC connection and sends an RRCConnectionRelease message to the terminal device with the releaseCause being rrc-Suspend. The message also carries the Resume ID and information about the network node indicating whether the terminal device needs to initiate RRC connection resume procedures. The terminal device receives the RRCConnectionRelease message sent by the second network node.

[0406] The specific process of the second network node acquiring the first information provided by the first network node in the processing method of this embodiment can refer to the above embodiments and will not be described in detail here.

[0407] Through the technical solution of this embodiment, in response to satisfying the second condition, the terminal device sends a radio resource control connection recovery request to the second network node, so that the second network node obtains the first information based on the radio resource control connection recovery request. Therefore, for the IoT-NTN Regenerative payload scenario, when the terminal device initiates RRCConnectionResumeRequest, the new network node can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0408] Eighth embodiment

[0409] 10 , which is a schematic diagram of an interaction flow between a first network node, a second network node, and a terminal device according to a processing method according to an eighth embodiment, the eighth embodiment of the present application proposes a processing method, comprising the steps of:

[0410] S1: In response to a first condition being met, the first network node provides first information to the second network node;

[0411] S2: The second network node obtains first information provided by the first network node;

[0412] S3: In response to the second condition being met, the terminal device sends a radio resource control connection recovery request to the second network node, so that the second network node obtains the first information based on the radio resource control connection recovery request.

[0413] This embodiment is primarily applicable to IoT-NTN Regenerative Payload scenarios. In these scenarios, due to high satellite speed and short coverage, when a terminal device with a suspended RRC connection initiates an RRCConnectionResumeRequest, the serving satellite to which the terminal device is connected has changed. Therefore, the current serving satellite (new eNB) needs to initiate a Retrieve UE Context procedure from the satellite with the suspended RRC connection (old eNB) to retrieve the terminal device context. Due to the rapid satellite movement, there may be no inter-satellite link (ISL) / neighborhood relationship / X2 interface between the new and old eNBs. Therefore, the new eNB cannot initiate a Retrieve UE Context procedure to retrieve the terminal device context from the old eNB, rendering UP CIoT EPS / 5GS optimization unusable. At this point, the terminal device needs to fall back to the RRC re-establishment process, which is not conducive to saving signaling overhead and / or reducing power consumption.

[0414] Therefore, for the IoT-NTN Regenerative payload scenario, in this embodiment, in response to satisfying the first condition, the first network node provides the first information to the second network node, and in response to satisfying the second condition, the terminal device sends a radio resource control connection recovery request to the second network node, so that the second network node obtains the first information based on the radio resource control connection recovery request, so that when the terminal device initiates RRCConnectionResumeRequest, the new network node (second network node) can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0415] Optionally, the first network node is an old network node, and the second network node is a new network node.

[0416] Optionally, the first network node is a network node that suspends the RRC connection for the terminal device or a network node that last covers the location area of ​​the terminal device.

[0417] Optionally, the second network node is a next network node covering the location area of ​​the terminal device.

[0418] Optionally, the second network node is a network node having an X2 link with the first network node.

[0419] Optionally, the second network node is a network node that initiates a radio resource control connection recovery request from the terminal device.

[0420] Optionally, the second network node is the network node that initiates a radio resource control connection recovery request for the next service of the terminal device.

[0421] Optionally, satisfying the second condition includes at least one of the following: the second network node is the network node carrying the recovery request identifier, the second network node is the network node to which the terminal device needs to initiate the request, and the terminal device has uplink services that need to be sent.

[0422] Optionally, the first information includes at least one of the following: terminal device context, terminal device location information, terminal device service information, network node information for the next service initiated by the terminal device, recovery request identifier, context transfer flag, and remaining context transfer times.

[0423] Optionally, the context transfer flag indicates that the second network node needs to transfer the first information to a next network node covering the location area of ​​the terminal device when the second network node stops serving the location area of ​​the terminal device.

[0424] Optionally, the remaining number of context transfers represents the remaining number of times the first information is transferred between network nodes.

[0425] Optionally, when the number of remaining context transfers is 0, the second network node triggers radio access network paging.

[0426] Optionally, when the second network node is the network node that initiates the radio resource control connection recovery request for the terminal device or the next service, the first information is transferred to the second network node through at least one transfer operation.

[0427] Optionally, the first information is transferred by the first network node to the second network node when a first condition is met, or the second network node obtains the first information from a previous network node when the second network node fails to obtain the first information locally.

[0428] Optionally, satisfying the first condition includes at least one of the following:

[0429] When the first network node receives the context acquisition request sent by the second network node;

[0430] After the first network node suspends the radio resource control connection of the terminal device;

[0431] When the first network node leaves or is about to leave the location area where the terminal device is located.

[0432] Optionally, the first network node independently determines that the terminal device has left or is about to leave the location area.

[0433] Optionally, the specific situation of the first network node leaving the location area of ​​the terminal device, for example, presetting a certain spatial range or time interval, or instantly calculating the time when the first network node leaves the location area of ​​the terminal device.

[0434] Optionally, the location area where the terminal device is located can be at least one of the location information reported by the terminal device, the mapping cell ID where the terminal device is located, the tracking area of ​​the terminal device, or the coverage area when the network node provides services to the terminal device.

[0435] Optionally, the terminal device sends next service information to the first network node. Optionally, the next service information indicates time information of the next service of the terminal device and / or the location of the terminal device.

[0436] Optionally, the first network node receives the next service information reported by the terminal device, and confirms the second network node information that (may) cover the location area of ​​the terminal device during the next service of the terminal device according to the service information reported by the terminal device.

[0437] Optionally, when deciding to suspend the RRC connection for the terminal device, the first network node sends radio resource control connection release information to the terminal device.

[0438] Optionally, when the first network node decides to suspend the RRC connection for the terminal device, the first network node sends radio resource control connection release information to the terminal device.

[0439] Optionally, the terminal device receives radio resource control connection release information sent by the first network node.

[0440] Optionally, the radio resource control connection release information includes at least one of the following: a radio resource control release reason, a recovery request identifier, and network node information.

[0441] Optionally, the radio resource control release reason includes: RRC connection suspension.

[0442] Optionally, the network node information indicates network node information for which the terminal device needs to initiate a radio resource control connection recovery request or network node information for which the terminal device does not need to initiate a radio resource control connection recovery request.

[0443] Optionally, the recovery request identifier included in the radio resource control connection release information sent by the first network node to the terminal device carries the second network node information.

[0444] Optionally, when the terminal device has uplink data to send, the terminal device initiates an RRCConnectionResumeRequest to the second network node, where the RRCConnectionResumeRequest carries a resume ID.

[0445] Optionally, when the second network node receives the RRCConnectionResumeRequest, it directly obtains the terminal device context locally according to the resume ID. If the acquisition fails, it falls back to the RRC establishment process.

[0446] Optionally, when the second network node fails to obtain the terminal device context locally, it attempts to request the terminal device context from the last network node covering the area (ie, the first network node). If the acquisition fails, it falls back to the RRC establishment process.

[0447] Optionally, when the terminal device has no downlink data to send, the second network node directly suspends the RRC connection and sends an RRCConnectionRelease message to the terminal device with the releaseCause being rrc-Suspend. The message also carries the Resume ID and information about the network node indicating whether the terminal device needs to initiate RRC connection resume procedures. The terminal device receives the RRCConnectionRelease message sent by the second network node.

[0448] The specific process of the second network node acquiring the first information provided by the first network node in the processing method of this embodiment can refer to the above embodiments and will not be described in detail here.

[0449] Through the technical solution of this embodiment, in response to satisfying the first condition, the first network node provides the first information to the second network node; the second network node obtains the first information provided by the first network node; in response to satisfying the second condition, the terminal device sends a radio resource control connection recovery request to the second network node, so that the second network node obtains the first information based on the radio resource control connection recovery request. Therefore, for the IoT-NTN Regenerative payload scenario, when the terminal device initiates the RRCConnectionResumeRequest, the new network node can obtain the terminal device context, thereby saving signaling overhead and / or reducing power consumption.

[0450] Please refer to Figure 11, which is a schematic diagram of the structure of the processing device provided in an embodiment of the present application. The device can be installed in or is the first network node in the above method embodiment. As shown in Figure 11, the device 150 includes:

[0451] The providing module 1501 is configured to provide first information to a second network node via a first network node in response to a first condition being met.

[0452] Optionally, satisfying the first condition includes at least one of the following:

[0453] When the first network node receives the context acquisition request sent by the second network node;

[0454] After the first network node suspends the radio resource control connection of the terminal device;

[0455] When the first network node leaves or is about to leave the location area where the terminal device is located.

[0456] Optionally, the first network node independently determines that the terminal device has left or is about to leave the location area.

[0457] Optionally, the specific situation of the first network node leaving the location area of ​​the terminal device, for example, presetting a certain spatial range or time interval, or instantly calculating the time when the first network node leaves the location area of ​​the terminal device.

[0458] Optionally, the location area where the terminal device is located can be at least one of the location information reported by the terminal device, the mapping cell ID where the terminal device is located, the tracking area of ​​the terminal device, or the coverage area when the network node provides services to the terminal device.

[0459] Optionally, the first information includes at least one of the following:

[0460] Terminal device context;

[0461] Location information of the terminal device;

[0462] Business information of terminal equipment;

[0463] Network node information for the next service initiated by the terminal device;

[0464] Recovery request identifier;

[0465] context transfer flag;

[0466] The number of remaining context transfers.

[0467] Optionally, the device further comprises at least one of the following:

[0468] The second network node is the next network node covering the location area of ​​the terminal device;

[0469] The second network node is a network node having an X2 link with the first network node;

[0470] The second network node is a network node that initiates a radio resource control connection recovery request from the terminal device;

[0471] The second network node is a network node that initiates a radio resource control connection recovery request for the next service of the terminal device;

[0472] The context transfer flag indicates that the second network node needs to transfer the first information to the next network node covering the location area of ​​the terminal device when the second network node stops serving the location area of ​​the terminal device;

[0473] The remaining number of context transfers indicates the remaining number of times the first information is transferred between network nodes.

[0474] Optionally, the device further comprises at least one of the following:

[0475] When the second network node is the network node that initiates the radio resource control connection recovery request for the terminal device or the next service, the first information is transferred to the second network node through at least one transfer operation;

[0476] The first network node receives next service information sent by the terminal device;

[0477] The first network node sends radio resource control connection release information to the terminal device.

[0478] Optionally, the radio resource control connection release information includes at least one of the following:

[0479] Reason for radio resource control release;

[0480] Recovery request identifier;

[0481] Network node information.

[0482] Optionally, the device further comprises at least one of the following:

[0483] When the number of remaining context transfers is 0, the second network node triggers radio access network paging;

[0484] The network node information indicates the network node information on which the terminal device needs to initiate a radio resource control connection recovery request or the network node information on which the terminal device does not need to initiate a radio resource control connection recovery request;

[0485] The restoration request identifier carries the second network node information.

[0486] The processing device provided in the embodiment of the present application can execute the technical solution shown in the above-mentioned corresponding method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0487] Please refer to Figure 12, which is a second structural diagram of a processing device provided in an embodiment of the present application. The device can be installed in or is the second network node in the above method embodiment. As shown in Figure 12, the device 160 includes:

[0488] The acquisition module 1601 is configured to acquire first information provided by a first network node.

[0489] Optionally, the device further comprises at least one of the following:

[0490] The first information is transferred by the first network node to the second network node when a first condition is met, or the first information is obtained from the previous network node when the second network node fails to obtain the first information locally;

[0491] The first information includes at least one of the following: terminal device context, terminal device location information, terminal device service information, network node information for the next service initiated by the terminal device, recovery request identifier, context transfer flag, and remaining context transfer times.

[0492] Optionally, the first condition is satisfied, including at least one of the following:

[0493] When the first network node receives the context acquisition request sent by the second network node;

[0494] After the first network node suspends the radio resource control connection of the terminal device;

[0495] When the first network node leaves or is about to leave the location area where the terminal device is located.

[0496] Optionally, the first network node independently determines that the terminal device has left or is about to leave the location area.

[0497] Optionally, the specific situation of the first network node leaving the location area of ​​the terminal device, for example, presetting a certain spatial range or time interval, or instantly calculating the time when the first network node leaves the location area of ​​the terminal device.

[0498] Optionally, the location area where the terminal device is located can be at least one of the location information reported by the terminal device, the mapping cell ID where the terminal device is located, the tracking area of ​​the terminal device, or the coverage area when the network node provides services to the terminal device.

[0499] Optionally, the device further comprises at least one of the following:

[0500] The second network node is the next network node covering the location area of ​​the terminal device;

[0501] The second network node is a network node having an X2 link with the first network node;

[0502] The second network node is a network node that initiates a radio resource control connection recovery request from the terminal device;

[0503] The second network node is the network node that initiates the radio resource control connection recovery request for the next service of the terminal device; the context transfer flag indicates that the second network node needs to transfer the first information to the next network node covering the location area of ​​the terminal device when it stops serving the location area of ​​the terminal device;

[0504] The remaining number of context transfers indicates the remaining number of times the first information is transferred between network nodes.

[0505] Optionally, the device further comprises at least one of the following:

[0506] When the first network node suspends the radio resource control connection of the terminal device, sending radio resource control connection release information to the terminal device;

[0507] When the number of remaining context transfers is 0, the second network node triggers radio access network paging;

[0508] When the second network node suspends the radio resource control connection of the terminal device, the second network node sends radio resource control connection release information to the terminal device;

[0509] When the second network node is the network node that initiates the radio resource control connection recovery request when the terminal device initiates or initiates the next service, the first information is transferred to the second network node through at least one transfer operation.

[0510] Optionally, the radio resource control connection release information includes at least one of the following:

[0511] Reason for radio resource control release;

[0512] Recovery request identifier;

[0513] Network node information.

[0514] Optionally, the device further comprises at least one of the following:

[0515] The network node information indicates the network node information on which the terminal device needs to initiate a radio resource control connection recovery request or the network node information on which the terminal device does not need to initiate a radio resource control connection recovery request;

[0516] The restoration request identifier carries the second network node information.

[0517] The processing device provided in the embodiment of the present application can execute the technical solution shown in the above-mentioned corresponding method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0518] Please refer to Figure 13, which is a third structural diagram of a processing device provided in an embodiment of the present application. The device can be installed in or is the terminal device in the above method embodiment. As shown in Figure 13, the device 170 includes:

[0519] The sending module 1701 is configured to send a radio resource control connection recovery request to the second network node in response to satisfying a second condition, so that the second network node obtains first information based on the radio resource control connection recovery request.

[0520] Optionally, the device further comprises at least one of the following:

[0521] The first information is transferred by the first network node to the second network node when a first condition is met, or the second network node obtains the first information from the previous network node when the second network node fails to obtain the first information locally;

[0522] The second condition is satisfied including at least one of the following: the second network node is the network node carrying the recovery request identifier, the second network node is the network node where the terminal device needs to initiate the request, and the terminal device has uplink services to send;

[0523] The first information includes at least one of the following: terminal device context, terminal device location information, terminal device service information, network node information for the next service initiated by the terminal device, recovery request identifier, context transfer flag, and remaining context transfer times.

[0524] Optionally, the first condition is satisfied, including at least one of the following:

[0525] When the first network node receives the context acquisition request sent by the second network node;

[0526] After the first network node suspends the radio resource control connection of the terminal device;

[0527] When the first network node leaves or is about to leave the location area where the terminal device is located.

[0528] Optionally, the first network node independently determines that the terminal device has left or is about to leave the location area.

[0529] Optionally, the specific situation of the first network node leaving the location area of ​​the terminal device, for example, presetting a certain spatial range or time interval, or instantly calculating the time when the first network node leaves the location area of ​​the terminal device.

[0530] Optionally, the location area where the terminal device is located can be at least one of the location information reported by the terminal device, the mapping cell ID where the terminal device is located, the tracking area of ​​the terminal device, or the coverage area when the network node provides services to the terminal device.

[0531] Optionally, the device further comprises at least one of the following:

[0532] The second network node is the next network node covering the location area of ​​the terminal device;

[0533] The second network node is a network node having an X2 link with the first network node;

[0534] The second network node is a network node that initiates a radio resource control connection recovery request from the terminal device;

[0535] The second network node is the network node that initiates the radio resource control connection recovery request for the next service of the terminal device; the context transfer flag indicates that the second network node needs to transfer the first information to the next network node covering the location area of ​​the terminal device when it stops serving the location area of ​​the terminal device;

[0536] The remaining number of context transfers represents the remaining number of times the first information is transferred between network nodes;

[0537] When the second network node is the network node that initiates the radio resource control connection recovery request when the terminal device initiates or initiates the next service, the first information is transferred to the second network node through at least one transfer operation.

[0538] Optionally, the device further comprises at least one of the following:

[0539] The terminal device sends next service information to the first network node;

[0540] The terminal device receives radio resource control connection release information sent by the first network node and / or the second network node.

[0541] Optionally, the radio resource control connection release information includes at least one of the following:

[0542] Reason for radio resource control release;

[0543] Recovery request identifier;

[0544] Network node information.

[0545] Optionally, the device further comprises at least one of the following:

[0546] The network node information indicates the network node information on which the terminal device needs to initiate a radio resource control connection recovery request or the network node information on which the terminal device does not need to initiate a radio resource control connection recovery request;

[0547] The restoration request identifier carries the second network node information.

[0548] The processing device provided in the embodiment of the present application can execute the technical solution shown in the above-mentioned corresponding method embodiment. Its implementation principle and beneficial effects are similar and will not be repeated here.

[0549] Refer to Figure 14, which is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. As shown in Figure 14, the communication device 180 described in this embodiment can be the terminal device (or component that can be used for a terminal device) or network device (or component that can be used for a network device) mentioned in the aforementioned method embodiment. Communication device 180 can be used to implement the methods corresponding to the terminal device or network device described in the aforementioned method embodiment. For details, please refer to the description of the aforementioned method embodiment.

[0550] The communication device 180 may include one or more processors 1801, also referred to as processing units, which may implement certain control or processing functions. Processor 1801 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, while the central processing unit may be used to control the communication device, execute software programs, and process software program data.

[0551] Optionally, the processor 1801 may also store instructions 1803 or data (eg, intermediate data). Optionally, the instructions 1803 may be executed by the processor 1801, so that the communication device 180 executes the method corresponding to the terminal device or network device described in the above method embodiment.

[0552] Optionally, the communication device 180 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments.

[0553] Optionally, the communication device 180 may include one or more memories 1802 , on which instructions 1804 may be stored. The instructions may be executed on the processor 1801 , so that the communication device 180 performs the method described in the above method embodiment.

[0554] Optionally, data may also be stored in the memory 1802. The processor 1801 and the memory 1802 may be provided separately or integrated together.

[0555] Optionally, the communication device 180 may further include a transceiver 1805 and / or an antenna 1806. The processor 1801 may be referred to as a processing unit, and controls the communication device 180 (terminal device, core network device, or wireless access network device). The transceiver 1805 may be referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, and is used to implement the transceiver functions of the communication device 180.

[0556] Optionally, if the communication device 180 is used to implement operations corresponding to the terminal device in the above-mentioned embodiments, for example, the transceiver 1805 can send a wireless resource control connection recovery request to the second network node in response to satisfying the second condition, so that the second network node obtains the first information based on the wireless resource control connection recovery request.

[0557] Optionally, the specific implementation process of the processor 1801 and the transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0558] Optionally, if the communication device 180 is used to implement operations corresponding to the first network node in the above embodiments, for example, the transceiver 1805 may provide the first information to the second network node through the first network node in response to the first condition being met.

[0559] Optionally, the specific implementation process of the processor 1801 and the transceiver 1805 can be found in the relevant descriptions of the above embodiments, and will not be repeated here.

[0560] The processor 1801 and transceiver 1805 described in this application can be implemented on an IC (Integrated Circuit), an analog integrated circuit, an RFIC (Radio Frequency Integrated Circuit), a mixed-signal integrated circuit, an ASIC (Application Specific Integrated Circuit), a PCB (Printed Circuit Board), an electronic device, etc. The processor 1801 and transceiver 1805 can also be manufactured using various integrated circuit process technologies, such as CMOS (Complementary Metal Oxide Semiconductor), NMOS (N Metal-Oxide-Semiconductor), PMOS (Positive Channel Metal Oxide Semiconductor), BJT (Bipolar Junction Transistor), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0561] The communication device in this application may be a first network node (such as a network device, specifically a base station or a satellite) or a second network node (such as a network device, specifically a base station or a satellite) or a terminal device (such as a mobile phone). The specific reference needs to be clarified in conjunction with the context. In addition, the terminal device can be implemented in various forms. For example, the terminal device described in this application may include mobile terminals such as mobile phones, tablet computers, laptop computers, PDAs, portable media players (PMPs), navigation devices, wearable devices, smart bracelets, pedometers, etc., as well as fixed terminal devices such as digital TVs and desktop computers.

[0562] Although the communication device is described above by taking a terminal device or a network device as an example, the scope of the communication device described in this application is not limited to the above-mentioned terminal device or network device, and the structure of the communication device may not be limited to Figure 14. The communication device may be an independent device or may be part of a larger device.

[0563] An embodiment of the present application also provides a communication system, including: a terminal device as in any of the above embodiments; and / or a network device as in any of the above embodiments (which may be a first network node and / or a second network node).

[0564] An embodiment of the present application also provides a communication device, including a memory and a processor, wherein a processing program is stored in the memory, and when the processing program is executed by the processor, the steps of the processing method in any of the above embodiments are implemented.

[0565] The communication device in this application may be a first network node (such as a network device, specifically a base station, satellite) or a second network node (such as a network device, specifically a base station, satellite) or a terminal device (such as a mobile phone). The specific reference needs to be clarified in combination with the context.

[0566] An embodiment of the present application further provides a storage medium having a processing program stored thereon. When the processing program is executed by a processor, the steps of the processing method in any of the above embodiments are implemented.

[0567] In the embodiments of the communication device and storage medium provided in the embodiments of the present application, all technical features of any of the above-mentioned processing method embodiments may be included. The expanded and explained contents of the specification are basically the same as those of the embodiments of the above-mentioned methods and will not be repeated here.

[0568] An embodiment of the present application further provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the computer executes the methods in the various possible implementation modes described above.

[0569] An embodiment of the present application also provides a chip, including a memory and a processor, wherein the memory is used to store computer programs, and the processor is used to call and run the computer programs from the memory, so that a device equipped with the chip executes the methods in the various possible implementation modes as described above.

[0570] It is understood that the above scenarios are merely examples and do not limit the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, those skilled in the art will appreciate that with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application will also be applicable to similar technical problems.

[0571] The serial numbers of the embodiments of the present application are for description only and do not represent the advantages and disadvantages of the embodiments. The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs. The units in the device of the embodiment of the present application can be combined, divided and deleted according to actual needs. In this application, the same or similar terminology, technical solutions and / or application scenario descriptions are generally only described in detail the first time they appear. When they appear again later, they are generally not repeated for the sake of brevity. When understanding the technical solutions and other contents of the present application, for the same or similar terminology, technical solutions and / or application scenario descriptions that are not described in detail later, you can refer to the previous related detailed descriptions.

[0572] In this application, the descriptions of various embodiments have their own emphasis. For parts that are not described or recorded in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The various technical features of the technical solution of this application can be combined arbitrarily. To keep the description concise, not all possible combinations of the various technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0573] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as above, and includes a number of instructions for enabling a terminal device (which can be a mobile phone, computer, server, controlled terminal device, or network device, etc.) to execute the method of each embodiment of the present application.

[0574] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can 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 the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a storage medium or transmitted from one storage medium to another storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium can be a magnetic medium (e.g., a floppy disk, a storage disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state storage disk Solid State Disk (SSD)).

[0575] The above are only preferred embodiments of the present application and do not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A processing method, wherein, Including the steps: S1: In response to meeting the first condition, the first network node provides the first information to the second network node.

2. The method according to claim 1, wherein, The meeting of the first condition includes at least one of the following: When the first network node receives a context acquisition request sent by the second network node; After the first network node suspends the radio resource control connection of the terminal device; When the first network node leaves or is about to leave the location area where the terminal device is located.

3. The method according to claim 1, wherein, The first information includes at least one of the following: Terminal device context; Location information of the terminal device; Service information of the terminal device; Network node information for the terminal device to initiate the next service; Recovery request identifier; Context transfer flag; Remaining context transfer times.

4. The method according to claim 3, wherein, It also includes at least one of the following: The second network node is the network node that will cover the location area of the terminal device next; The second network node is the network node that has an X2 link with the first network node; The second network node is the network node for which the terminal device initiates a radio resource control connection recovery request; The second network node is the network node for which the terminal device initiates a radio resource control connection recovery request for the next service; The context transfer flag indicates that the second network node needs to transfer the first information to the network node that will cover the location area of the terminal device next when stopping serving the location area of the terminal device; The remaining context transfer times indicate the remaining number of times the first information is transferred between network nodes.

5. The method according to claim 4, wherein, It also includes at least one of the following: When the second network node is the network node for which the terminal device initiates or initiates a radio resource control connection recovery request for the next service, the first information is transferred to the second network node through at least one transfer operation; The first network node receives the next service information sent by the terminal device; The first network node sends radio resource control connection release information to the terminal device.

6. The method according to claim 5, wherein, The radio resource control connection release information includes at least one of the following: Radio resource control release reason; Recovery request identifier; Network node information.

7. The method according to claim 6, wherein, It also includes at least one of the following: When the remaining context transfer times is 0, the second network node triggers radio access network paging; The network node information represents the network node information for which the terminal device needs to initiate a radio resource control connection recovery request or the network node information for which the terminal device does not need to initiate a radio resource control connection recovery request; The recovery request identifier carries the second network node information.

8. A processing method, wherein,Including the steps: S2: The second network node acquires the first information provided by the first network node.

9. The method according to claim 8, wherein, It also includes at least one of the following: The first information is transferred by the first network node to the second network node when meeting the first condition or the first information is acquired from the previous network node when the local acquisition of the second network node fails; The first information includes at least one of the following: terminal device context, location information of the terminal device, service information of the terminal device, network node information for the terminal device to initiate the next service, recovery request identifier, context transfer flag, remaining context transfer times.

10. The method according to claim 9, wherein, The meeting of the first condition includes at least one of the following: When the first network node receives a context acquisition request sent by the second network node; After the first network node suspends the radio resource control connection of the terminal device; When the first network node leaves or is about to leave the location area where the terminal device is located.

11. The method according to claim 10, wherein, It further includes at least one of the following: The second network node is the network node that will cover the location area of the terminal device next; The second network node is the network node that has an X2 link with the first network node; The second network node is the network node to which the terminal device initiates a radio resource control connection restoration request; The second network node is the network node to which the terminal device initiates a radio resource control connection restoration request for the next service; The context transfer flag indicates that when the second network node stops serving the location area of the terminal device, it needs to transfer the first information to the network node of the location area that will cover the terminal device next; Location area; The remaining context transfer times indicate the remaining number of times the first information is transferred between network nodes.

12. The method according to claim 11, wherein, It further includes at least one of the following: When the first network node suspends the radio resource control connection of the terminal device, it sends radio resource control connection release information to the terminal device; When the remaining context transfer times is 0, the second network node triggers radio access network paging; When the second network node suspends the radio resource control connection of the terminal device, it sends radio resource control connection release information to the terminal device; When the second network node is the network node to which the terminal device initiates or the next service initiates a radio resource control connection restoration request, the first information is transferred to the second network node through at least one transfer operation.

13. The method according to claim 12, wherein, The radio resource control connection release information includes at least one of the following: Radio resource control release reason; Restoration request identifier; Network node information.

14. The method according to claim 13, wherein, It further includes at least one of the following: The network node information represents the network node information for which the terminal device needs to initiate a radio resource control connection restoration request or the network node information for which the terminal device does not need to initiate a radio resource control connection restoration request; The restoration request identifier carries the second network node information.

15. A processing method, wherein, It includes the steps: S3: In response to satisfying the second condition, the terminal device sends a radio resource control connection restoration request to the second network node, so that the second network node obtains the first information based on the radio resource control connection restoration request.

16. The method according to claim 15, wherein, It further includes at least one of the following: The first information is transferred by the first network node to the second network node when the first condition is satisfied or the second network node obtains it from the previous network node when the local acquisition of the first information fails; The satisfaction of the second condition includes at least one of the following: the second network node is the network node carried by the restoration request identifier, the second network node is the network node for which the terminal device needs to initiate a request, and there is an uplink service to be sent by the terminal device; The first information includes at least one of the following: terminal device context, location information of the terminal device, service information of the terminal device, network node information of the network node to which the terminal device initiates the next service, restoration request identifier, context transfer flag, remaining context transfer times.

17. The method according to claim 16, wherein The satisfaction of the first condition includes at least one of the following: When the first network node receives a context acquisition request sent by the second network node; After the first network node suspends the radio resource control connection of the terminal device; When the first network node leaves or is about to leave the location area where the terminal device is located.

18. The method according to claim 17, wherein It further includes at least one of the following: The second network node is the network node that covers the location area of the next terminal device; The second network node is the network node that has an X2 link with the first network node; The second network node is the network node to which the terminal device sends a radio resource control connection restoration request; The second network node is the network node to which the terminal device sends a radio resource control connection restoration request for the next service; The context transfer flag indicates that when the second network node stops serving the location area of the terminal device, it needs to transfer the first information to the network node that covers the location area of the next terminal device; The remaining context transfer times indicate the remaining number of times the first information is transferred between network nodes; When the second network node is the network node to which the terminal device sends a radio resource control connection restoration request for the current or next service, the first information is transferred to the second network node through at least one transfer operation.

19. The method according to claim 18, wherein It further includes at least one of the following: The terminal device sends next service information to the first network node; The terminal device receives radio resource control connection release information sent by the first network node and / or the second network node.

20. The method according to claim 19, wherein The radio resource control connection release information includes at least one of the following: Radio resource control release cause; Restoration request identifier; Network node information.

21. The method according to claim 20, wherein It further includes at least one of the following: The network node information indicates the network node information for which the terminal device needs to send a radio resource control connection restoration request or the network node information for which the terminal device does not need to send a radio resource control connection restoration request; The restoration request identifier carries the second network node information.

22. A communication device, wherein It includes: A memory and a processor, where a processing program is stored on the memory, and when the processing program is executed by the processor, the processing method described in claim 1, 8, or 15 is implemented.

23. A storage medium, wherein A computer program is stored on the storage medium, and when the computer program is executed by a processor, the processing method described in claim 1, 8, or 15 is implemented.

Images