Information interaction methods, devices, terminals, and network-side equipment

Abstract

This application discloses an information interaction method, apparatus, terminal and network-side equipment, and belongs to the field of communications technology. An embodiment of the information interaction method of this application includes, when a target event related to a terminal is about to be triggered while a first timer is operating, the terminal sending a request message to the network-side equipment to instruct it to activate a period of time when the terminal is unavailable, and storing context information, wherein the terminal is unavailable during the process in which the target event is executed, and the first timer is a timer related to congestion control.

Description

Technical Field

[0001] (Cross-reference to Related Applications) This application claims the priority of a Chinese patent with application number 202310716455.2 filed in China on June 15, 2023, and all the contents of the said application are incorporated herein by reference.

[0002] This application belongs to the field of communication technology, and specifically relates to an information interaction method, apparatus, terminal, and network-side device.

Background Art

[0003] When a terminal is ready to execute an event that makes the terminal unavailable, a terminal that can store context starts a mobility registration update program to activate the unavailable time, and a terminal that cannot store context starts a deregistration program to activate the unavailable time.

[0004] However, when congestion control at the Non-Access Stratum (NAS) level is activated at this time, that is, when T3346 is operating, a terminal that can store context at this time cannot start the unavailable time for activating the mobility registration update program, thereby extending the time for the terminal to resume normal services after the unavailable time zone of the terminal ends, causing an impact on the user experience.

Summary of the Invention

Problems to be Solved by the Invention

[0005] Embodiments of this application provide an information interaction method, apparatus, terminal, and network-side device that can solve the problem of how to quickly resume normal services of a terminal.

Means for Solving the Problems

[0006] According to the first aspect, an information interaction method is provided which is performed by a terminal, and the method is When the first timer is running, and a target event related to the terminal is about to be triggered, the terminal, Sending a request message to the network-side device to instruct it to attempt to activate the terminal during the period it was unavailable, This includes performing at least one of the following operations: storing context information, Here, the terminal is unavailable during the process in which the target event is executed, and the first timer is a timer related to congestion control.

[0007] According to a second aspect, an information interaction method is provided that is performed by network-side equipment, and this method is: When a network-side device performs congestion control, this includes the network-side device receiving a request message from a terminal. Here, the request message is used to indicate that the unavailable time of the terminal will be activated in the process of executing a target event related to the terminal.

[0008] According to a third aspect, an information interaction device is provided, When the first timer is running, and a target event related to the terminal is about to be triggered, Sending a request message to the network-side device to instruct it to attempt to activate the terminal during the period it was unavailable, Includes an executable module for performing at least one of the following operations: storing context information, Here, the terminal is unavailable during the process in which the target event is executed, and the first timer is a timer related to congestion control.

[0009] According to the fourth aspect, an information interaction device is provided, which is When network-side equipment performs congestion control, it includes a first receiving module for receiving request messages from terminals, Here, the request message is used to indicate that the unavailable time of the terminal will be activated in the process of executing a target event related to the terminal.

[0010] According to the fifth aspect, a terminal is provided which includes a processor and memory, the memory storing a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the steps of the method of the first aspect are realized.

[0011] According to a sixth aspect, a terminal is provided including a processor and a communication interface, wherein the processor is used to store context information when a target event related to the terminal is about to be triggered while a first timer is operating; the communication interface is used to send a request message to a network-side device when a target event related to the terminal is about to be triggered while the network-side device is performing congestion control; the request message is used to instruct the device to activate the time during which the terminal is unavailable, wherein the terminal is unavailable during the process in which the target event is executed, and the first timer is a timer related to congestion control.

[0012] According to the seventh aspect, a network-side device is provided, which includes a processor and memory, the memory storing a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the steps of the method according to the first aspect are realized.

[0013] According to the eighth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is used to receive request messages from a terminal when the network-side device is performing congestion control, wherein the request messages are used to indicate that the terminal's unavailable time is to be activated in the process of a target event related to the terminal being executed.

[0014] According to the ninth aspect, a readable storage medium is provided, the readable storage medium storing a program or instruction, and when the program or instruction is executed by a processor, a step of the method according to the first aspect is realized, or a step of the method according to the second aspect is realized.

[0015] According to the tenth aspect, a wireless communication system is provided which includes a terminal and network-side equipment, wherein the terminal may be used to perform a step of the method according to the first aspect, and the network-side equipment may be used to perform a step of the method according to the second aspect.

[0016] According to the eleventh aspect, a chip is provided, the chip comprising a processor and a communication interface, the communication interface being coupled with the processor, the processor being used to execute a program or instructions, to implement the method according to the first aspect, or to implement the method according to the second aspect.

[0017] According to the twelfth aspect, a computer program / program product is provided, the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to realize the information interaction method described in the first aspect, or to realize the steps of the information interaction method described in the second aspect. [Effects of the Invention]

[0018] In an embodiment of this application, when a first timer related to convergence control is operating and a target event related to the terminal is about to be triggered, the terminal sends a request message to the network-side device to instruct the terminal to attempt to activate the unavailable time. By doing so, the terminal can successfully activate the unavailable time, and the terminal can store context information within the unavailable time period. Or, when the network-side device executes convergence control and a target event related to the terminal is about to be triggered, the terminal directly stores the context information, so that the terminal can reuse the context information after the unavailable time period ends, quickly resume normal services based on the context information, and further improve the user experience.

Brief Description of the Drawings

[0019] [Figure 1] It is a block diagram of a wireless communication system to which the embodiment of this application is applicable. [Figure 2] It is one of the flowcharts of the information interaction method according to the embodiment of this application. [Figure 3] It is the second of the flowcharts of the information interaction method according to the embodiment of this application. [Figure 4] It is the first of the signaling interaction schematic diagrams of the information interaction method according to the embodiment of this application. [Figure 5] It is the second of the signaling interaction schematic diagrams of the information interaction method according to the embodiment of this application. [Figure 6] It is the third of the signaling interaction schematic diagrams of the information interaction method according to the embodiment of this application. [Figure 7] It is the fourth of the signaling interaction schematic diagrams of the information interaction method according to the embodiment of this application. [Figure 8] It is the first of the structural schematic diagrams of the information interaction device according to the embodiment of this application. [Figure 9]This is the second schematic diagram of the structure of an information interaction device according to an embodiment of this application. [Figure 10] This is a schematic diagram of the structure of a communication device according to an embodiment of this application. [Figure 11] This is a schematic diagram of the hardware structure of a terminal according to an embodiment of this application. [Figure 12] This is one of the schematic diagrams of the network-side equipment structure according to the embodiment of this application. [Figure 13] This is the second schematic diagram of the network-side equipment structure according to the embodiment of this application. [Modes for carrying out the invention]

[0020] The following clearly and completely describes the technical concepts in the embodiments of this application, linking them to the drawings of the embodiments. Clearly, the embodiments described are only some, and not all, embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are all within the scope of protection of this application.

[0021] The terms "first," "second," etc., used in this application are intended to distinguish similar objects and not to describe a specific order or sequence. It should be understood that these terms are interchangeable where appropriate, so that the embodiments of this application can be carried out in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same kind and do not limit the number of objects; for example, the first object may be one or more. In this application, "or" represents at least one of the connected objects. For example, "A or B" covers three solutions: Solution 1: includes A but not B, Solution 2: includes B but not A, Solution 3: includes both A and B. The character " / " generally indicates that the preceding and succeeding related objects are in an "or" relationship.

[0022] The term "instruction" as used in this application may be direct (or explicit) or indirect (or implicit). Here, a direct instruction may be understood as the sender clearly informing the receiver of specific information, operations to be performed, or desired results in the instructions sent by the sender, while an indirect instruction may be understood as the receiver determining or judging the corresponding information based on the instructions sent by the sender, and determining the operations to be performed or desired results based on the judgment.

[0023] It should be noted that the technologies described in the embodiments of this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but are also applicable to other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in the embodiments of this application are always used interchangeably, and the technologies described may be used for the systems and radio technologies mentioned above, or for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and uses NR terminology in most of the following description, but these technologies are also applicable to systems other than NR systems, such as sixth-generation (6) radio systems. th It may be applied to 6G (Generation 1) communication systems.

[0024] Figure 1 shows a block diagram of a wireless communication system to which an embodiment of this application can be applied. The wireless communication system includes a terminal 11 and network-side equipment 12. Here, the terminal 11 may be a mobile phone, tablet personal computer, laptop computer, notebook computer, personal digital assistant (PDA), palmtop computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), augmented reality (AR), virtual reality (VR) equipment, robot, wearable device, aircraft (flight vehicle), vehicle user equipment (VUE), shipboard equipment, pedestrian user equipment (PUE), smart home (home equipment with wireless communication capabilities, such as a refrigerator, television, washing machine, or furniture), game console, personal computer (PC), deposit machine, or self-service machine. Wearable devices include smartwatches, smart bands, smart earphones, smart glasses, smart accessories (such as smart bracelets, smart rings, smart necklaces, smart anklets, smart wristbands, and smart clothing). Here, in-vehicle equipment may also be referred to as in-vehicle terminals, in-vehicle controllers, in-vehicle modules, in-vehicle components, in-vehicle chips, or in-vehicle units. It should be noted that the embodiments of this application do not limit the specific type of terminal 11.The network-side equipment 12 may include access network equipment or core network equipment, where access network equipment may also be called radio access network (RAN) equipment, radio access network functions, or radio access network units. Access network equipment may include base stations, wireless local area network (WLAN) access points (APs), or wireless fidelity (WiFi) nodes, etc. Here, a base station may also be called a Node B (NB), an Evolved Node B (eNB), the next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a home Node B (HNB), a home evolved Node B, a Transmission Reception Point (TRP), or any other appropriate term in the art, and as long as the same technical effect is achieved, the base station is not limited to any particular technical term. For the purposes of this explanation, only a base station in an NR system is used as an example in the embodiments of this application, but this does not limit the specific type of base station.

[0025] The core network equipment includes core network nodes, core network functions, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (or L-NEF), Binding Support Function (BSF), and Application Function (Application It may include, but is not limited to, at least one of the following: Function, AF, etc. For the purposes of explanation, the embodiments of this application only use core network equipment in an NR system as an example, but this does not limit the specific type of core network equipment.

[0026] To facilitate a clearer understanding of the technical concepts presented in each embodiment of this application, some relevant knowledge is first explained below.

[0027] 1. Seamless UE Context Recovery (SUECR) Several internal terminal events can trigger a terminal, such as User Equipment (UE), to become unavailable for a certain period of time, such as during an operating system upgrade or equipment restart. During this time, the terminal may store its context (including mobility management and session management context) in a Universal Subscriber Identity Module (USIM) or non-volatile memory, thereby allowing the context to be reused after the period of unavailability has ended. th It can quickly interact with the Generation Mobile Communication Technology Core (5GC) to restore normal service. Furthermore, the terminal interacts with the network to notify it of periods of network unavailability, allowing the network to determine the terminal's status and avoid operations such as paging during the unavailability period.

[0028] If the device can remember the context before the above events begin, it may indicate a period of unavailability to the network by initiating the mobility registration renewal process. At this time, the network will assume that the device is unreachable until the period of unavailability ends or the device becomes connected. Simultaneously, if the device cannot remember the context, it may indicate a period of unavailability to the network by initiating the deregistration process.

[0029] 2. Congestion control mechanism The network may detect NAS signaling congestion and perform congestion control. When congestion control is activated, the network rejects NAS signaling requests and provides a T3346 value. To avoid timeout synchronization, i.e., when a large number of terminals simultaneously initiate delayed NAS signaling requests, the network should select different T3346 values ​​for terminals. When a terminal turns on a received T3346 value, during the T3346 operation period, the terminal is not permitted to initiate any NAS signaling related to the applied congestion control (including initial registration requests, mobility registration update requests, and service requests), with some exceptions, such as when the terminal receives a paging request from the network or when the terminal initiates an emergency service or high-priority access signal.

[0030] If a terminal is ready to perform an event that renders it unavailable, a terminal that can remember its context will initiate a mobility registration update, network interaction state, and unavailable period. However, if T3346 is active at this time and the terminal is not permitted to initiate the mobility registration update, the terminal will not be able to activate the unavailable period, and during the terminal's unavailable period, the terminal will not be able to use the SUECR property, i.e., it will not be able to remember the terminal context, extending the time it takes for the terminal to recover normal service. At the same time, the network will not be able to determine the terminal's state and may perform unnecessary operations such as paging.

[0031] In summary, the embodiments of this application provide an information interaction method, apparatus, terminal, and network-side equipment to address the problems described above.

[0032] In the following sections, the information interaction method according to the embodiments of this application will be described in detail with reference to several embodiments and their application scenarios, accompanied by drawings.

[0033] Figure 2 is one flowchart of an information interaction method according to an embodiment of the present application, and as shown in Figure 2, the method includes step 201, where: In step 201, when the first timer is running and a target event related to the terminal is about to be triggered, the terminal: Sending a request message to the network-side device to instruct it to attempt to activate the terminal during the period it was unavailable, Perform at least one of the following operations: storing context information, wherein the terminal is unavailable during the process in which the target event is executed, and the first timer is a timer related to congestion control.

[0034] It should be noted that the first timer may be a T3346 timer, and the embodiments of this application can be applied to a scenario of NAS-level congestion control (i.e., the T3346 timer is operating, and hereafter referred to as T3346 operating). The terminals include, but are not limited to, the types of terminals 11 listed above.

[0035] The scenarios in which T3346 operates include at least one of the following: In Scenario 1, the terminal is refused the transmission of a mobility registration update request message to the network-side device, and the mobility registration update request message is used to instruct the terminal to attempt to activate the unavailable period and to attempt to reactivate the unavailable period.

[0036] In Scenario 2, the terminal is denied the opportunity to send a registration request message to the network-side device, and the registration request is not used to instruct the terminal to attempt to activate during the unavailable time. At this point, the terminal's upper layer requests activation during the unavailable time.

[0037] In embodiments of this application, when a network-side device performs congestion control and a target time associated with a terminal is about to be triggered, the terminal may perform at least one of the following operations: In operation 1, the terminal sends a request message to the network-side device instructing it to attempt to activate the terminal during the time it was unavailable.

[0038] Accordingly, network-side equipment can determine that the terminal is unavailable after receiving a request message from the terminal.

[0039] In operation 2, the terminal stores context information.

[0040] In one embodiment, the request message is used to request activation during the period of unavailability, and the network-side equipment may agree to or reject the terminal's request to activate during the period of unavailability.

[0041] In one embodiment, the request message is used to indicate that the terminal is unavailable.

[0042] In one embodiment, activating an unavailable time may be understood as the terminal being unavailable during a period when it is unavailable.

[0043] Selectively, the context information is a) 5G mobility management context information, b) Includes at least one of the following: 5G session management context information.

[0044] Selectively, the storage location of the context information is, a) The USIM of the terminal, b) including at least one of the non-volatile memory of the terminal.

[0045] In the embodiments of this application, when a first timer related to congestion control is operating and a target event related to the terminal is about to be triggered, the terminal can successfully activate the unavailable time by sending a request message to the network-side equipment instructing it to attempt to activate the unavailable time, the terminal can store context information during the unavailable time, or when the network-side equipment is performing congestion control and a target event related to the terminal is about to be triggered, the terminal can directly store the context information so that the context information can be reused after the unavailable time has ended, normal service can be quickly restored based on the context information, and the user experience can be further improved.

[0046] Selectively, the request message includes at least one of the following: a) A mobility registration renewal request message that includes a period of time when the terminal is unavailable.

[0047] Specifically, when a target event related to the terminal is about to be triggered during the T3346 operation period, the terminal is permitted to send a mobility registration renewal request message, which is used to activate unavailable time, and which includes the unavailable time period.

[0048] The terminal has the ability to store the context information selectively if the request message includes the mobility registration update request message.

[0049] In other words, the terminal has the ability to store 5G mobility management context information and 5G session management context information.

[0050] Selectively, when the terminal sends the mobility registration update request message to the network-side device, the terminal stores the context information.

[0051] In other words, the terminal can store 5G mobility management context information and 5G session management context information in the terminal's USIM or non-volatile memory. This method allows the context information to be reused after the period of terminal unavailability has ended, enabling the rapid restoration of normal service based on the context information and further improving the user experience.

[0052] Selectively, before the terminal sends a mobility registration update request message to the network-side device, the network-side device must instruct the terminal to support the unavailable time during the previous registration process.

[0053] Accordingly, the terminal receives a second instruction from the network-side device, and the second instruction is used to instruct the network-side device to provide support during the time it is unavailable.

[0054] It should be explained that when a terminal receives a second instruction from a network-side device, the network-side device has the capability to support the unavailable period, and only when both the terminal and the network-side device support the unavailable period, and a target event related to the terminal is about to be triggered, the terminal can activate the unavailable period, and accordingly, the network-side device can avoid performing operations such as paging during the unavailable period.

[0055] The terminal should include information in the registration request message indicating the time periods when the terminal is unavailable. For example, the terminal may indicate the time periods when it is unavailable using an "unavailable time information element" and set the subsequent request instruction to "no subsequent request".

[0056] Furthermore, even if a terminal has one or more active always-online Protocol Data Unit (PDU) sessions related to 3rd Generation Partnership Project (3GPP) access, the registration request message cannot include an Uplink data status information element (IE) or the Allowed PDU session status IE.

[0057] It should be explained that if a terminal provides a period of unavailability, network equipment should consider the terminal unreachable until it restores normal service or enters a connected state. In this case, network equipment should remember the received period of unavailability and release the NAS signaling connection after completing the mobility registration update program.

[0058] b) A service request message for activating the time period during which the terminal is unavailable, wherein the service request message includes at least one of the time period during which the terminal is unavailable and a first instruction information, the first instruction information being used to indicate that the terminal has no further requests.

[0059] Specifically, when a target event related to the terminal is about to be triggered during the T3346 operation period, the terminal initiates a service request program, and the service request message includes the terminal's unavailable time period, which is used to activate the terminal during the unavailable period.

[0060] Furthermore, the service request message may include a first directive to indicate that the terminal has no subsequent requests, and this first directive may be, for example, a subsequent request directive, and may be specifically expressed as follows: The follow-on request indicator in the SERVICE REQUEST message is set to “No follow-on request pending”.

[0061] Selectively, the service request message does not contain at least one of the following: [1] Uplink data status IE.

[0062] [2] Allowed PDU session state IE.

[0063] The terminal has the ability to store the context information selectively if the request message includes the service request message.

[0064] In other words, the terminal has the ability to store 5G mobility management context information and 5G session management context information.

[0065] When the terminal selectively sends the service request message to the network-side device, the terminal stores the context information.

[0066] In other words, the terminal can store 5G mobility management context information and 5G session management context information in the terminal's USIM or non-volatile memory. This method allows the context information to be reused after the period of terminal unavailability has ended, enabling the rapid restoration of normal service based on the context information and further improving the user experience.

[0067] Selectively, before the terminal sends a service request message to the network-side device, the network-side device must instruct the terminal in the previous registration program to support the unavailable time.

[0068] Accordingly, the terminal receives a second instruction from the network-side device, and the second instruction is used to instruct the network-side device to provide support during the time it is unavailable.

[0069] In the above embodiment, the terminal sends a request message to the network-side device instructing it to attempt to activate the time when the terminal is unavailable. This allows the terminal to synchronize its unavailable time with the network-side device even when the network-side device is performing congestion control, providing the terminal with sufficient flexibility and preventing the network-side device from sending signaling during the time the terminal is unavailable.

[0070] Selectively, the request message is, This includes a deregistration request message that does not include the time period when the terminal is unavailable.

[0071] To make it clear, the terminal sends a deregistration request message to the network-side device instructing it to attempt to activate the device during the time it is unavailable, but the deregistration request message does not include the time period during which the terminal is unavailable.

[0072] In one embodiment, the terminal can send mobility registration renewal request messages or service request messages to network-side equipment, and can also send deregistration request messages to network-side equipment, wherein the deregistration request messages do not include periods when the terminal is unavailable.

[0073] Specifically, when a target event related to the terminal is about to be triggered during the T3346 operation period, the terminal initiates a deregistration request program to activate the unavailable time, but the terminal does not include the unavailable time period. This method eliminates the need for the terminal to synchronize its unavailable time period with network-side equipment, thereby saving signaling overhead, and simultaneously allows network-side equipment to determine the terminal's state based on the deregistration request message and avoid unnecessary operations such as paging.

[0074] When the terminal selectively sends the deregistration request message to the network-side device, the terminal does not have the ability to store the context information.

[0075] In other words, the terminal does not have the ability to store 5G mobility management context information and 5G session management context information.

[0076] Selectively, before the terminal sends a deregistration request message to the network-side device, the network-side device must instruct the terminal in the previous registration program to support the period of unavailability.

[0077] Accordingly, the terminal receives a second instruction from the network-side device, and the second instruction is used to instruct the network-side device to provide support during the time it is unavailable.

[0078] When a network-side device selectively performs congestion control and a target event related to the terminal is about to be triggered, the specific implementation process by which the terminal stores context information is as follows: During the T3346 operation period, when a target event related to the terminal is about to be triggered, the terminal initiates local deregistration, and the terminal remembers the context, which is used to reuse the context after the period of unavailability has ended, enabling a rapid restoration of normal service.

[0079] Selectively, when the terminal initiates local deregistration and stores context information, the terminal has the capability to store the context information.

[0080] In other words, the terminal has the ability to store 5G mobility management context information and 5G session management context information. The terminal can store the 5G mobility management context information and 5G session management context information in the terminal's USIM or non-volatile memory. By this method, the context information can be reused after the period of terminal unavailability has ended, normal service can be quickly restored based on the context information, and the user experience can be further improved.

[0081] Selectively, before the terminal initiates local deregistration and stores context information, the network-side device must instruct the terminal to support the unavailable time in the previous registration program.

[0082] Accordingly, the terminal receives a second instruction from the network-side device, and the second instruction is used to instruct the network-side device to provide support during the time it is unavailable.

[0083] Figure 3 is the second flowchart of an information interaction method according to an embodiment of the present application, and as shown in Figure 3, the method includes step 301, where In step 301, when the network-side device performs congestion control, the network-side device receives a request message from the terminal, which is used to indicate that the terminal's unavailable time will be activated in the process of a target event related to the terminal being executed.

[0084] It should be noted that the embodiments of this application can be applied to scenarios involving NAS-level congestion control (i.e., T3346 is in operation).

[0085] In the embodiments of this application, when a network-side device performs congestion control, the network-side device needs to receive a request message from the terminal when a target event related to the terminal is about to be triggered.

[0086] Selectively, the request message includes at least one of the following: a) A mobility registration renewal request message that includes a period of time when the terminal is unavailable.

[0087] b) A service request message for activating the time period during which the terminal is unavailable, wherein the service request message includes at least one of the time period during which the terminal is unavailable and a first instruction information, the first instruction information being used to indicate that the terminal has no further requests.

[0088] In the embodiments of this application, when a network-side device performs congestion control, the network-side device determines that the terminal's unavailable period will be activated upon receiving a request message from the terminal. This allows the terminal to store context information during the unavailable period, and thus allows the terminal to reuse the context information after the unavailable period ends. Based on the context information, normal service can be quickly restored, further improving the user experience.

[0089] Selectively, the request message is, This includes a deregistration request message that does not include the time period when the terminal is unavailable.

[0090] To make it clear, the network-side equipment receives a deregistration request message from the terminal and instructs it to attempt to activate the terminal during the time it is unavailable, but the deregistration request message does not include the time period during which the terminal is unavailable.

[0091] In one embodiment, the network-side equipment can receive mobility registration update request messages or service request messages from the terminal, as well as deregistration request messages from the terminal, the deregistration request messages being used to activate the terminal during periods when it is unavailable, and the deregistration request messages do not include periods when the terminal is unavailable.

[0092] Selectively, the network-side device may further transmit a second instruction to the terminal, which is used to instruct the network-side device to provide support during the period when it is unavailable.

[0093] Selectively, if the request message includes at least one of the mobility registration update request message and the service request message, the network-side equipment shall, after the period during which the terminal is unavailable has elapsed or after the terminal has entered a connected state, a) To remember the time periods when the terminal is unavailable, b) After completing the mobility registration update program and the service request program, perform at least one of the following operations: release the non-access tier NAS signaling connectivity.

[0094] The information interaction method according to the embodiment of this application will be further explained below, linking Figures 4 to 7.

[0095] Figure 4 is one of the schematic diagrams of the signaling interaction of an information interaction method according to an embodiment of the present application, and as shown in Figure 4, Figure 4 shows a situation in which, when T3346 is in operation, the terminal is not permitted to initiate mobility registration update, except that the terminal needs to activate during unavailable time, and specifically includes steps 401 to 404, where, In step 401, T3346 is operating.

[0096] Specifically, the scenarios in which T3346 operates include at least one of the following: In Scenario 1, the terminal is refused the transmission of a mobility registration update request message to the network-side device, and the mobility registration update request message is used to instruct the terminal to attempt to activate the unavailable period and to attempt to reactivate the unavailable period.

[0097] In Scenario 2, the terminal is denied the opportunity to send a registration request message to the network-side device, and the registration request is not used to instruct the terminal to attempt to activate during the unavailable time. At this point, the terminal's upper layer requests activation during the unavailable time.

[0098] In step 402, the UE prepares to execute an event that disables the terminal, i.e., an event that disables the UE is triggered.

[0099] In step 403, during the T3346 operation period, the UE is permitted to send a mobility registration renewal request message, which is used to activate the unavailable time, i.e., the UE sends a mobility registration renewal request message to the AMF that includes the unavailable time period.

[0100] Before sending a mobility registration update request message, the network-side equipment is instructed to support the time periods that were unavailable in the previous registration program, and the terminal has the ability to remember the 5G mobility management context and the 5G session management context.

[0101] The terminal should include information in the registration request indicating the times when the terminal is unavailable. For example, the terminal may indicate the times when it is unavailable using an "unavailable time information element" and set the subsequent request instruction to "no subsequent request". Note that even if the terminal has one or more active always-online PDU sessions related to 3GPP access, it cannot include the upstream link data status IE or the permitted PDU session status IE in the registration request message.

[0102] In step 404, if the UE provides a period of time during which it is unavailable, the AMF will consider the UE to be unreachable.

[0103] The UE remembers the received period of unavailability and releases the NAS signaling connection after completing the mobility registration update, until it restores normal service or enters a connected state.

[0104] Figure 5 is a second schematic diagram of the signaling interaction of an information interaction method according to an embodiment of the present application, and as shown in Figure 5, Figure 5 illustrates a situation in which the UE activates unavailable time without initiating the mobility registration update process, by simply storing context information, and specifically includes steps 501 to 503, where In step 501, T3346 is operational. Specifically, the scenarios in which T3346 is operational include at least one of the following: In Scenario 1, the terminal is refused the transmission of a mobility registration update request message to the network-side device, and the mobility registration update request message is used to instruct the terminal to attempt to activate the unavailable period and to attempt to reactivate the unavailable period.

[0105] In Scenario 2, the terminal is denied the opportunity to send a registration request message to the network-side device, and the registration request is not used to instruct the terminal to attempt to activate during the unavailable time. At this point, the terminal's upper layer requests activation during the unavailable time.

[0106] In step 502, the UE prepares to execute an event that disables the terminal, i.e., an event that disables the UE is triggered.

[0107] In step 503, the UE stores the context information, initiates local deregistration, and does not initiate a mobility registration renewal request, i.e., does not send a mobility registration renewal request message to the AMF.

[0108] Specifically, by storing context information, the UE can reuse the context after the period of unavailability has ended, enabling a rapid recovery of normal service.

[0109] Context information includes mobility management context information and session management context information, and the context information is stored in USIM or non-volatile memory.

[0110] Before the UE stores context information, the network must be instructed in the previous registration program to support unavailable time periods, and the UE must have the ability to store 5G mobility management context information and 5G session management context information.

[0111] Figure 6 is the third schematic diagram of the signaling interaction of the information interaction method according to an embodiment of the present application, and as shown in Figure 6, Figure 6 shows a situation in which, when T3346 is operating, the UE is unable to remember the context, initiates a deregistration process to interact with the network, but does not include any unavailable time periods, and specifically includes steps 601 to 605, where In step 601, T3346 is operating.

[0112] Specifically, the scenarios in which T3346 operates include at least one of the following: In Scenario 1, the terminal is refused the transmission of a mobility registration update request message to the network-side device, and the mobility registration update request message is used to instruct the terminal to attempt to activate the unavailable period and to attempt to reactivate the unavailable period.

[0113] In Scenario 2, the terminal is denied the opportunity to send a registration request message to the network-side device, and the registration request is not used to instruct the terminal to attempt to activate during the unavailable time. At this point, the terminal's upper layer requests activation during the unavailable time.

[0114] In step 602, the UE prepares to execute an event that disables the terminal, i.e., an event that disables the UE is triggered.

[0115] In step 603, the UE fails to remember the context and initiates the deregistration program, but it does not include the period of unavailability.

[0116] In step 604, the UE sends a deregistration request message to the AMF, which does not include any unavailable time periods.

[0117] In step 605, AMF concludes that the UE is unreachable.

[0118] Figure 7 is the fourth schematic diagram of the signaling interaction of the information interaction method according to an embodiment of the present application, and as shown in Figure 7, Figure 7 shows the situation in which the UE initiates a service request process to activate the unavailable time when T3346 is in operation, specifically including steps 701 to 705, where In step 701, T3346 is operational.

[0119] Specifically, the scenarios in which T3346 operates include at least one of the following: In Scenario 1, the terminal is refused the transmission of a mobility registration update request message to the network-side device, and the mobility registration update request message is used to instruct the terminal to attempt to activate the unavailable period and to attempt to reactivate the unavailable period.

[0120] In Scenario 2, the terminal is denied the opportunity to send a registration request message to the network-side device, and the registration request is not used to instruct the terminal to attempt to activate during the unavailable time. At this point, the terminal's upper layer requests activation during the unavailable time.

[0121] In step 702, the UE prepares to execute an event that will disable the terminal, that is, an event that will disable the UE is about to be triggered.

[0122] In step 703, the UE starts the service request program.

[0123] In step 704, the UE sends a service request message to the AMF, which includes a period of unavailability, and is used to activate the unavailability period.

[0124] Furthermore, the terminal must not include at least one of the following in its service request message: a) UE context information.

[0125] b) Uplink data status IE.

[0126] c) The Allowed PDU session status IE.

[0127] Additionally, set the Follow-on request indicator to “No follow-on request pending” in the SERVICE REQUEST message.

[0128] It should be explained that the terminal has the capability to store context information, which includes mobility management context information and session management context information, and that the context information is stored in USIM or non-volatile memory.

[0129] Before the UE can store the context, the network must be instructed to support the time periods that were unavailable in the previous registration program, and the terminal must have the ability to store 5G mobility management context information and 5G session management context information.

[0130] In step 705, AMF concludes that UE is unreachable.

[0131] In the information interaction method according to the embodiments of this application, the implementing entity may be an information interaction device. In the embodiments of this application, the information interaction device according to the embodiments of this application will be described, taking as an example that the information interaction device executes the information interaction method.

[0132] Figure 8 is one of the schematic diagrams of the structure of an information interaction device according to an embodiment of this application. As shown in Figure 8, this information interaction device 800 is: When the first timer is running, and a target event related to the terminal is about to be triggered, Sending a request message to the network-side device to instruct it to attempt to activate the terminal during the period it was unavailable, Includes an executable module 801 for performing at least one of the following operations: storing context information, Here, the terminal is unavailable during the process in which the target event is executed, and the first timer is a timer related to congestion control.

[0133] In the information interaction device according to the embodiment of this application, when a first timer related to congestion control is operating and a target event related to the terminal is about to be triggered, the terminal can successfully activate the unavailable time by sending a request message to the network-side device instructing it to activate the unavailable time, the terminal can store context information during the unavailable time, or when the network-side device is performing congestion control and a target event related to the terminal is about to be triggered, the terminal can reuse the context information after the unavailable time has ended by directly storing the context information, thereby enabling the rapid restoration of normal service based on the context information and further improving the user experience.

[0134] Selectively, A mobility registration update request message that includes the time period when the aforementioned terminal is unavailable, The system includes at least one of the following: a service request message for activating the time period during which the terminal is unavailable, the service request message including at least one of the time period during which the terminal is unavailable and first instruction information, the first instruction information being used to indicate that there are no further requests for the terminal.

[0135] Selectively, the terminal has the ability to store the context information.

[0136] Selectively, the apparatus, The system further includes a first memory module for storing the aforementioned context information.

[0137] Selectively, the request message is, This includes a deregistration request message that does not include the time period when the terminal is unavailable.

[0138] If the request message selectively includes the deregistration request message, the terminal does not have the ability to store the context information.

[0139] Selectively, the apparatus, The system further includes a second receiving module for receiving a second instruction information from the network-side device, the second instruction information being used to instruct the network-side device to provide support during times when it is unavailable.

[0140] Selectively, the storage location of the context information is, The aforementioned terminal's general-purpose subscriber identification module USIM, It includes at least one of the following: the terminal's non-volatile memory.

[0141] Selectively, the context information is Fifth-generation mobile communication technology 5G mobility management context information, It includes at least one of the following: 5G session management context information.

[0142] Selectively, the first timer includes a T3346 timer.

[0143] Figure 9 is the second schematic diagram of the structure of an information interaction device according to an embodiment of this application. As shown in Figure 9, this information interaction device 900 is: When network-side equipment performs congestion control, it includes a first receiving module 901 for receiving request messages from terminals, Here, the request message is used to indicate that the unavailable time of the terminal will be activated in the process of executing a target event related to the terminal.

[0144] In the information interaction device according to the embodiment of this application, when a network-side device performs congestion control, it decides to activate the terminal's unavailable period upon receiving a request message from the terminal. As a result, the terminal can store context information during the unavailable period, and as a result, the terminal can reuse the context information after the unavailable period ends, quickly restore normal service based on the context information, and further improve the user experience.

[0145] Selectively, the request message is, A mobility registration update request message that includes the time period when the aforementioned terminal is unavailable, The system includes at least one of the following: a service request message for activating the time period during which the terminal is unavailable, the service request message including at least one of the time period during which the terminal is unavailable and first instruction information, the first instruction information being used to indicate that there are no further requests for the terminal.

[0146] Selectively, the request message is, This includes a deregistration request message that does not include the time period when the terminal is unavailable.

[0147] Selectively, the apparatus, The system further includes a transmission module for transmitting a second instruction to the terminal, the second instruction being used to instruct the network-side equipment to provide support during the period when it is unavailable.

[0148] Selectively, the apparatus, A second memory module for storing the time periods when the aforementioned terminal is unavailable, It further includes at least one of the following: a mobility registration update program and a release module for releasing non-access tier NAS signaling connectivity after the completion of the service request program.

[0149] The information interaction device in the embodiments of this application may be an electronic device, such as an electronic device having an operating system, or a component of an electronic device, such as an integrated circuit or a chip. This electronic device may be a terminal or other device. Exemplarily, a terminal may include, but is not limited to, the types of terminals 11 listed above, and other devices may be servers, network-attached storage (NAS), etc., and the embodiments of this application are not specifically limited.

[0150] The information interaction device according to the embodiment of this application can realize each process realized by the embodiment of the method shown in Figures 2 to 3 and achieve the same technical effects, and to avoid repetition of explanation, it will not be explained further here.

[0151] Figure 10 is a schematic diagram of the structure of a communication device according to an embodiment of this application. The communication device 1000 according to an embodiment of this application includes a processor 1001 and a memory 1002. The memory 1002 stores a program or instruction that can be executed on the processor 1001. For example, if this communication device 1000 is a terminal, when this program or instruction is executed by the processor 1001, each step of the embodiment of the method shown in Figure 2 can be realized, and the same technical effect can be achieved. If this communication device 1000 is a network-side device, when this program or instruction is executed by the processor 1001, each step of the embodiment of the method shown in Figure 3 can be realized, and the same technical effect can be achieved. To avoid repetition, no further explanation is provided here.

[0152] Embodiments of this application further provide a terminal comprising a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used to execute a program or instruction and to implement the steps in the embodiment of the method shown in Figure 2. Embodiments of this terminal correspond to embodiments of the terminal-side method described above, and each implementation process and implementation method of the embodiment of the method described above can be applied to embodiments of this terminal and achieve the same technical effects. Specifically, Figure 11 is a schematic diagram of the hardware structure of a terminal according to embodiments of this application.

[0153] This terminal 1100 includes, but is not limited to, some of the following components: a radio frequency unit 1101, a network module 1102, an audio output unit 1103, an input unit 1104, a sensor 1105, a display unit 1106, a user input unit 1107, an interface unit 1108, a memory 1109, and a processor 1110.

[0154] As those skilled in the art will understand, the terminal 1100 may further include a power supply (e.g., a battery) to power each component, and the power supply may be logically connected to the processor 1110 by a power management system, thereby enabling functions such as charge / discharge management and power consumption management by the power management system. The terminal structure shown in Figure 11 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than the number shown, or combinations of some components, or different arrangements of components, which will not be described further here.

[0155] It should be understood that, in the embodiments of this application, the input unit 1104 may include a graphics processing unit (GPU) 11041 and a microphone 11042, and the graphics processor 11041 processes still images or video image data obtained by an image capture device (e.g., a camera) in video capture mode or image capture mode. The display unit 1106 may include a display panel 11061, which may be configured in the form of a liquid crystal display, organic light-emitting diodes, etc. The user input unit 1107 includes at least one of a touch panel 11071 and other input devices 11072. The touch panel 11071 is also called a touchscreen. The touch panel 11071 may include two parts: a touch detection device and a touch controller. The other input devices 11072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control buttons, switch buttons, etc.), a trackball, a mouse, or an operating lever, and will not be described further here.

[0156] In the embodiments of this application, the radio frequency unit 1101 can receive downlink data from network-side equipment and transmit it to the processor 1110 for processing, and the radio frequency unit 1101 can also transmit uplink data to network-side equipment. Generally, the radio frequency unit 1101 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low-noise amplifier, duplexer, etc.

[0157] Memory 1109 may be used to store software programs or instructions and various types of data. Memory 1109 may include a first storage area mainly for storing programs or instructions and a second storage area for storing data, wherein the first storage area can store an operating system, an application program or instructions necessary for at least one function (e.g., audio playback function, image playback function, etc.). Memory x09 may also include volatile memory or non-volatile memory. Here, non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), or flash memory. The volatile memory may be Random Access Memory (RAM), Static Random Access Memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (Double Data Rate SDRAM, DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced SDRAM, ESDRAM), Synch-link Dynamic Random Access Memory (Synch-link DRAM, SLDRAM), and Direct Rambus Random Access Memory (DRRAM). The memory 1109 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0158] The processor 1110 may include one or more processing units, and optionally, the processor 1110 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface and application programs or instructions, and the modem processor mainly handles wireless communication signals, such as a baseband processor. To be clear, the above modem processor does not have to be integrated into the processor 1110.

[0159] Embodiments of this application further provide network-side equipment including a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor executes a program or instruction to realize the steps of the embodiment of the method shown in Figure 3. This embodiment of network-side equipment corresponds to the embodiment of the network-side equipment method described above, and each implementation process and implementation method of the embodiment of the method described above can be applied to this embodiment of network-side equipment and achieve the same technical effects.

[0160] Specifically, embodiments of this application further provide network-side equipment. As shown in Figure 12, Figure 12 is one schematic diagram of the structure of network-side equipment according to embodiments of this application, and this network-side equipment 1200 includes an antenna 121, a radio frequency device 122, a baseband device 123, a processor 124, and a memory 125. The antenna 121 and the radio frequency device 122 are connected. In the uplink direction, the radio frequency device 122 receives information via the antenna 121 and transmits the received information to the baseband device 123 for processing. In the downlink direction, the baseband device 123 processes the information to be transmitted and transmits it to the radio frequency device 122, which processes the received information and then transmits it via the antenna 121.

[0161] The method performed by the network-side equipment in the above embodiment may also be implemented in the baseband device 123, which includes a baseband processor.

[0162] The baseband device 123 may include, for example, at least one baseband board on which multiple chips are installed, and as shown in Figure 12, one of the chips is, for example, a baseband processor, which is connected to memory 125 via a bus interface, calls a program in memory 125, and performs the network equipment operations shown in the embodiment of the above method.

[0163] This network-side device may further include a network interface 126, which is, for example, a Common Public Radio Interface (CPRI).

[0164] Specifically, the network-side device 1200 of the embodiment of this application further includes instructions or programs stored in memory 125 and executable on processor 124, the processor 124 can call instructions or programs in memory 125 and execute in the manner shown by each module in Figure 3, and achieve the same technical effect, which will not be described further here in order to avoid repetition of the explanation.

[0165] Specifically, embodiments of this application further provide network-side equipment. As shown in Figure 13, Figure 13 is a second schematic diagram of the structure of network-side equipment according to embodiments of this application, and this network-side equipment 1300 includes a processor 1301, a network interface 1302, and memory 1303. Here, the network interface 1302 is, for example, a common public radio interface (CPRI).

[0166] Specifically, the network-side device 1300 of the embodiment of this application further includes instructions or programs stored in memory 1303 and executable on processor 1301, the processor 1301 can call instructions or programs in memory 1303 and execute in the manner shown by each module in Figure 3, and achieve the same technical effect, which will not be described further here in order to avoid repetition of the explanation.

[0167] Embodiments of this application further provide a readable storage medium on which a program or instruction is stored, and when this program or instruction is executed by a processor, each process of the embodiment of the information interaction method described above can be realized and the same technical effects can be achieved. To avoid repetition, no further explanation is provided here.

[0168] Here, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes computer-readable storage media such as computer read-only memory ROM, random access memory RAM, magnetic disk, or optical disk. In some examples, the readable storage medium may be a non-temporarily readable storage medium.

[0169] Embodiments of this application further provide a chip including a processor and a communication interface, wherein the communication interface is coupled with the processor, and the processor is used to execute programs or instructions and implement each process of the embodiment of the information interaction method described above, and can achieve the same technical effects. To avoid repetition, no further explanation is provided here.

[0170] It should be understood that the chips referred to in the embodiments of this application may also be called system-level chips, system chips, chip systems, or system-on-a-chip, etc.

[0171] Embodiments of this application further provide a computer program / program product in which the computer program / program product is stored on a storage medium and executed by at least one processor to realize each process of the embodiment of the information interaction method described above and to achieve the same technical effects. To avoid repetition, no further explanation is provided here.

[0172] Embodiments of this application further provide an information interaction system including a terminal and network-side equipment, wherein the terminal may be used to perform steps of the information interaction method shown in Figure 2, and the network-side equipment may be used to perform steps of the information interaction method shown in Figure 3.

[0173] It should be noted that in this specification, the terms “including,” “contains,” or any other variation thereof are intended to cover the non-exclusive “including,” thereby including not only those elements but also other elements not explicitly listed, or elements specific to such process, method, article, or apparatus. Unless otherwise specified, an element limited by the phrase “including one of…” is not excluded from the existence of other identical elements in a process, method, article, or apparatus containing that element. It should also be noted that the scope of methods and apparatus in embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions in a manner that is essentially simultaneous or in reverse order based on the functions involved, for example, performing methods described in a different procedure than that described, and adding, omitting, or combining various steps. Furthermore, features described by reference to some examples may be combined with other examples.

[0174] As will be clearly apparent to those skilled in the art from the above description of embodiments, the methods of the above embodiments may be implemented by a computer software product and a necessary general-purpose hardware platform, or of course, by hardware. This computer software product is stored in a storage medium (e.g., ROM, RAM, magnetic disk, optical disk, etc.) and includes some instructions for causing a terminal or network-side device to perform the methods of each embodiment of this application.

[0175] The above describes embodiments of this application, accompanied by drawings; however, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. A person skilled in the art can create many forms of embodiments by the suggestion of this application, as long as they do not deviate from the spirit and scope protected by the claims of this application, and all of these embodiments fall within the scope of protection of this application.

Claims

1. An information interaction method, When the first timer is running, and a target event related to the terminal is about to be triggered, the terminal, Sending a request message to the network-side device to instruct it to attempt to activate the terminal during the period it was unavailable, This includes performing at least one of the following operations: storing context information, Herein, an information interaction method wherein the terminal is unavailable during the process in which the target event is executed, and the first timer is a timer related to congestion control.

2. The aforementioned request message is: A mobility registration update request message that includes the time period when the aforementioned terminal is unavailable, The information interaction method according to claim 1, comprising at least one of a service request message, wherein the service request message comprises at least one of a time period during which the terminal is unavailable and a first instruction information, the first instruction information being used to indicate that the terminal has no further requests.

3. The information interaction method according to claim 1 or 2, wherein the terminal has the capability to store the context information.

4. The aforementioned method, The information interaction method according to any one of claims 1 to 3, further comprising the terminal storing the context information.

5. The aforementioned request message is: The information interaction method according to claim 1, comprising a deregistration request message that does not include the time period when the terminal is unavailable.

6. The information interaction method according to claim 5, wherein the terminal does not have the ability to store the context information when the request message includes the deregistration request message.

7. The aforementioned method, The information interaction method according to any one of claims 1 to 6, further comprising the terminal receiving second instruction information from the network-side device, the second instruction information being used to instruct the network-side device to support a period of time when it is unavailable.

8. The storage location of the aforementioned context information is, The general-purpose subscriber identification module (USIM) of the aforementioned terminal, The information interaction method according to any one of claims 1 to 7, comprising at least one of the following: the terminal's non-volatile memory.

9. The aforementioned context information is, Fifth-generation mobile communication technology 5G mobility management context information, An information interaction method according to any one of claims 1 to 8, comprising at least one of the following: 5G session management context information.

10. The information interaction method according to any one of claims 1 to 9, wherein the first timer includes a T3346 timer.

11. An information interaction method, When a network-side device performs congestion control, this includes the network-side device receiving a request message from a terminal. Herein, the request message is used to indicate that the time of the terminal's unavailability will be activated in the process of a target event related to the terminal being executed, as an information interaction method.

12. The aforementioned request message is: A mobility registration update request message that includes the time period when the aforementioned terminal is unavailable, The information interaction method according to claim 11, comprising at least one of a service request message, wherein the service request message comprises at least one of a time period during which the terminal is unavailable and a first instruction information, the first instruction information being used to indicate that the terminal has no further requests.

13. The aforementioned request message is: The information interaction method according to claim 11, comprising a deregistration request message that does not include the time period when the terminal is unavailable.

14. The aforementioned method, The information interaction method according to any one of claims 11 to 13, further comprising the network-side device transmitting a second instruction information to the terminal, the second instruction information being used to instruct the network-side device to provide support during an unavailable period.

15. When the terminal sends the request message to the network-side device, after the time period during which the terminal is unavailable has elapsed or after the terminal has entered a connected state, the network-side device shall The terminal is to remember the period of time when it is unavailable, The information interaction method according to claim 12, which performs at least one of the following operations: completing a mobility registration update program and a service request program, and then releasing an access-layer NAS signaling connection.

16. An information interaction device, When the first timer is running, and a target event related to the terminal is about to be triggered, Sending a request message to the network-side device to instruct it to attempt to activate the terminal during the period it was unavailable, Includes an executable module for performing at least one of the following operations: storing context information, Herein, the terminal is unavailable during the process in which the target event is executed, and the first timer is a timer related to congestion control, in this information interaction device.

17. An information interaction device, When network-side equipment performs congestion control, it includes a first receiving module for receiving request messages from terminals, Herein, the request message is used to indicate that the time of the terminal's unavailability will be activated in the process of a target event related to the terminal being executed, in an information interaction device.

18. A terminal comprising a processor and memory, wherein the memory stores a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the terminal realizes a step of the information interaction method described in any one of claims 1 to 10.

19. Network-side device comprising a processor and memory, wherein the memory stores a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, a step of the information interaction method described in any one of claims 11 to 15 is realized.

20. A readable storage medium that stores a program or instruction, and when the program or instruction is executed by a processor, realizes a step of the information interaction method described in any one of claims 1 to 10, or realizes a step of the information interaction method described in any one of claims 11 to 15.

Images