Information interaction method and apparatus, and terminal and network-side device

Abstract

The present application belongs to the technical field of communications. Disclosed are an information interaction method and apparatus, and a terminal and a network-side device. The information interaction method in the embodiments of the present application comprises: when a first timer is running and a target event associated with a terminal is to be triggered, the terminal executing at least one of the following operations: sending a request message to a network-side device, wherein the request message is used for indicating that the terminal is to activate an unavailability time; and storing context information, wherein the terminal is unavailable during the process of the target event being executed, and the first timer is a timer related to congestion control.

Description

Information interaction method, device, terminal and network side equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application number 202310716455.2 filed in China on June 15, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to an information interaction method, apparatus, terminal, and network-side equipment. Background Art

[0004] If the terminal is ready to execute an event that makes the terminal unavailable, the terminal that can store the context initiates a mobile registration update procedure to activate the unavailable time, and the terminal that cannot store the context initiates a deregistration procedure to activate the unavailable time.

[0005] However, if the non-access stratum (NAS) level congestion control is activated at this time, that is, T3346 is running, the terminal that can store the context cannot initiate the mobility registration update procedure to activate the unavailable time, which will extend the time for the terminal to resume normal service after the terminal unavailable period ends, affecting the user experience.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide an information interaction method, apparatus, terminal, and network-side equipment, which can solve the problem of how to quickly restore normal service of a terminal.

[0008] In a first aspect, an information interaction method is provided, which is executed by a terminal, and the method includes:

[0009] When the first timer is running and a target event associated with the terminal is about to be triggered, the terminal performs at least one of the following operations:

[0010] Sending a request message to the network side device, where the request message is used to instruct the terminal to activate the unavailable time;

[0011] Store context information;

[0012] The terminal is unavailable during the execution of the target event, and the first timer is a timer related to congestion control.

[0013] In a second aspect, an information interaction method is provided, which is performed by a network-side device. The method includes:

[0014] In a case where the network side device performs congestion control, the network side device receives a request message from the terminal;

[0015] The request message is used to indicate that the unavailable time of the terminal is to be activated during the execution of the target event associated with the terminal.

[0016] In a third aspect, an information interaction device is provided, comprising:

[0017] The execution module is configured to, when the first timer is running and a target event associated with the terminal is about to be triggered, perform at least one of the following operations:

[0018] Sending a request message to the network side device, where the request message is used to instruct the terminal to activate the unavailable time;

[0019] Store context information;

[0020] The terminal is unavailable during the execution of the target event, and the first timer is a timer related to congestion control.

[0021] In a fourth aspect, an information interaction device is provided, comprising:

[0022] A first receiving module, configured to receive a request message from a terminal when the network side device performs congestion control;

[0023] The request message is used to indicate that the unavailable time of the terminal is to be activated during the execution of the target event associated with the terminal.

[0024] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0025] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is used to store context information when a target event associated with the terminal is to be triggered when a first timer is running, and the communication interface is used to send a request message to the network side device when a target event associated with the terminal is to be triggered when the network side device performs congestion control, wherein the request message is used to instruct the terminal to activate an unavailable time; wherein the terminal is unavailable during the execution of the target event, and the first timer is a timer related to congestion control.

[0026] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0027] In the eighth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive a request message from a terminal when the network side device performs congestion control; wherein the request message is used to indicate that the unavailable time of the terminal is to be activated during the execution of the target event associated with the terminal.

[0028] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0029] In the tenth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0030] In an eleventh aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to run a program or instruction to implement the method described in the first aspect or the method described in the second aspect.

[0031] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the information interaction method as described in the first aspect, or to implement the steps of the information interaction method as described in the second aspect.

[0032] In an embodiment of the present application, when the first timer related to congestion control is running, when the target event associated with the terminal is about to be triggered, the terminal sends a request message to the network side device to instruct the terminal to activate the unavailable time, so that the terminal can successfully activate the unavailable time. The terminal can store context information during the unavailable time period, or, when the network side device performs congestion control, when the target event associated with 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, and normal service can be quickly restored based on the context information, thereby improving user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0034] FIG2 is a flow chart of an information interaction method according to an embodiment of the present invention;

[0035] FIG3 is a second flow chart of the information interaction method provided in an embodiment of the present application;

[0036] FIG4 is a schematic diagram of signaling interaction of an information interaction method according to an embodiment of the present application;

[0037] FIG5 is a second schematic diagram of signaling interaction of the information interaction method provided in an embodiment of the present application;

[0038] FIG6 is a third schematic diagram of signaling interaction of the information interaction method provided in an embodiment of the present application;

[0039] FIG7 is a fourth schematic diagram of signaling interaction of the information interaction method provided in an embodiment of the present application;

[0040] FIG8 is a schematic diagram of a structure of an information interaction device according to an embodiment of the present application;

[0041] FIG9 is a second structural diagram of the information interaction device provided in an embodiment of the present application;

[0042] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0043] FIG11 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application;

[0044] FIG12 is a schematic diagram of a structure of a network side device according to an embodiment of the present application;

[0045] FIG13 is a second structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0046] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0047] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0048] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0049] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in 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 the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. thGeneration, 6G) communication system.

[0050] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0051] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0052] In order to facilitate a clearer understanding of the technical solutions provided by the embodiments of the present application, some relevant knowledge is first introduced as follows.

[0053] 1. Seamless UE context recovery (SUECR)

[0054] The triggering of some terminal internal events may make the terminal, such as User Equipment (UE), unavailable for a period of time, such as operating system upgrade or device restart. At this time, the terminal may store its context (including mobility management and session management context) in the Universal Subscriber Identity Module (USIM) or non-volatile memory so that the context can be reused after the unavailable period ends and the fifth generation mobile communication technology core network (5G core network) can be quickly connected. th The terminal will also interact with the network to inform it of the unavailable period so that the network can determine the terminal's status and avoid paging and other operations during the period of terminal unavailability.

[0055] Before the above events occur, if the terminal can store context, it may indicate an unavailable period to the network by initiating a mobility registration update procedure. The network will then consider the terminal unreachable until the unavailable period ends or the terminal enters the connected state. If the terminal cannot store context, it may indicate an unavailable period to the network by initiating a deregistration procedure.

[0056] 2. Congestion Control Mechanism

[0057] The network may detect NAS signaling congestion and implement congestion control. When congestion control is activated, the network will reject NAS signaling requests and provide a T3346 value. To avoid timeout synchronization, that is, a large number of terminals simultaneously initiate delayed NAS signaling requests, the network should select different T3346 values ​​for terminals. When the terminal turns on the received T3346 value, the terminal is not allowed to initiate any NAS signaling related to the applied congestion control (including initial registration requests, mobility registration update requests, and service requests) during the period when T3346 is in operation, with some exceptions, such as when the terminal receives a paging request from the network or when the terminal initiates signaling for emergency services or high-priority access.

[0058] If a terminal is ready to execute an event that renders it unavailable, it can initiate a mobility registration update to update its network interaction status and unavailable time period. However, if T3346 is running at this time, the terminal is not allowed to initiate the mobility registration update procedure and cannot activate the unavailable time period. During the unavailable time period, the terminal cannot use the SUECR feature, meaning that the terminal context cannot be stored, which prolongs the time it takes to resume normal service. Furthermore, the network cannot determine the terminal's status and may perform unnecessary operations such as paging.

[0059] In summary, in order to address the above-mentioned problems, the embodiments of the present application provide an information interaction method, apparatus, terminal, and network-side device.

[0060] The information interaction method provided by the embodiments of the present application is described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0061] FIG2 is a flow chart of an information interaction method according to an embodiment of the present application. As shown in FIG2 , the method includes step 201 , wherein:

[0062] Step 201: When a first timer is running and a target event associated with a terminal is about to be triggered, the terminal performs at least one of the following operations:

[0063] Sending a request message to the network side device, where the request message is used to instruct the terminal to activate the unavailable time;

[0064] Storing context information; wherein, the terminal is unavailable during the execution of the target event, and the first timer is a timer related to congestion control.

[0065] It should be noted that the first timer may be a T3346 timer, and the embodiment of the present application may be applied to scenarios of NAS-level congestion control (i.e., the T3346 timer is running, hereinafter referred to as T3346 running). The terminal includes but is not limited to the types of terminal 11 listed above; this application is not limited to this.

[0066] The T3346 scenario being run includes at least one of the following:

[0067] Scenario 1: The terminal sends a mobility registration update request message to the network-side device, but the message is rejected. The mobility registration update request message is used to indicate that the terminal wants to activate the unavailable time; the terminal wants to activate the unavailable time again.

[0068] Scenario 2: The terminal sends a registration request message to the network device and is rejected. The registration request is not used to instruct the terminal to activate the unavailable time. At this time, the upper layer of the terminal requests to activate the unavailable time.

[0069] In an embodiment of the present application, when a network-side device performs congestion control, when a target time associated with a terminal is about to be triggered, the terminal may perform at least one of the following operations:

[0070] Operation 1: The terminal sends a request message to the network-side device, indicating that the terminal wants to activate the unavailable time.

[0071] Accordingly, after receiving the request message from the terminal, the network side device can determine that the terminal is in an unavailable state.

[0072] Operation 2: The terminal stores the context information.

[0073] In one implementation, the request message is used to request activation of the unavailable time, and the network-side device may approve or reject the terminal's request to activate the unavailable time.

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

[0075] In one implementation manner, the activation unavailable time may be understood as the terminal being unavailable during the unavailable time period.

[0076] Optionally, the context information includes at least one of the following:

[0077] a) 5G mobility management context information.

[0078] b) 5G session management context information.

[0079] Optionally, the storage location of the context information includes at least one of the following:

[0080] a) The USIM of the terminal.

[0081] b) a non-volatile memory of the terminal.

[0082] In an embodiment of the present application, when the first timer related to congestion control is running, when the target event associated with the terminal is about to be triggered, the terminal sends a request message to the network side device to instruct the terminal to activate the unavailable time, so that the terminal can successfully activate the unavailable time. The terminal can store context information during the unavailable time period, or, when the network side device performs congestion control, when the target event associated with 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, and normal service can be quickly restored based on the context information, thereby improving user experience.

[0083] Optionally, the request message includes at least one of the following:

[0084] a) A mobility registration update request message, wherein the mobility registration update request message includes an unavailable time period of the terminal.

[0085] Specifically, during the operation of T3346, when a target event associated with the terminal is to be triggered, the terminal is allowed to send a mobility registration update request message, wherein the mobility registration update request message is used to activate the unavailable time, and the mobility registration update request message includes the unavailable time period.

[0086] Optionally, in a case where the request message includes the mobility registration update request message, the terminal is capable of storing the context information.

[0087] That is, the terminal is capable of storing 5G mobility management context information and 5G session management context information.

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

[0089] 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. Through the above method, the context information can be reused after the terminal unavailable period ends, and normal service can be quickly restored based on the context information, thereby improving the user experience.

[0090] Optionally, before the terminal sends a mobility registration update request message to the network-side device, the network-side device needs to indicate to the terminal that it supports unavailable time in the last registration procedure.

[0091] Correspondingly, the terminal receives second indication information from the network side device, where the second indication information is used to indicate that the network side device supports unavailable time.

[0092] It should be noted that when the terminal receives the second indication information from the network side device, it indicates that the network side device has the ability to support unavailable time. When both the terminal and the network side device support unavailable time, the terminal can only activate the unavailable time when the target event associated with the terminal is to be triggered; accordingly, the network side device can avoid performing operations such as paging during the unavailable time period.

[0093] The terminal should include information indicating the unavailable period of the terminal in the registration request message, for example, the "unavailable period information element" may be used to indicate the unavailable period of the terminal, and the subsequent request indication may be set to "no subsequent request".

[0094] Furthermore, the Uplink data status Information Element (IE) or the Allowed PDU session status IE MUST NOT be included in the Registration Request message even if the terminal has one or more active always-on Protocol Data Unit (PDU) sessions associated with 3rd Generation Partnership Project (3GPP) access.

[0095] It should be noted that if the terminal provides an unavailable time period, the network-side device should consider the terminal unreachable until the terminal resumes normal service or enters the connected state; at this time, the network-side device needs to store the received unavailable time period and release the NAS signaling connection after completing the mobility registration update procedure.

[0096] b) a service request message, used to activate the unavailable time of the terminal; the service request message includes at least one of the unavailable time period of the terminal and first indication information; the first indication information is used to indicate that the terminal has no subsequent request.

[0097] Specifically, during the operation of T3346, when a target event associated with the terminal is about to be triggered, the terminal initiates a service request procedure, and includes the unavailable time period of the terminal in the service request message for activating the unavailable time.

[0098] Furthermore, the service request message further includes first indication information for indicating that the terminal has no subsequent request. The first indication information may be, for example, subsequent request indication information, which may be specifically represented as follows:

[0099] That is, the follow-on request indicator information in the service request message is set to "No follow-on request pending".

[0100] Optionally, the service request message does not include at least one of the following:

[0101] [1] Uplink Data Status IE.

[0102] [2] Allowed PDU Session Status IE.

[0103] Optionally, in a case where the request message includes the service request message, the terminal is capable of storing the context information.

[0104] That is, the terminal is capable of storing 5G mobility management context information and 5G session management context information.

[0105] Optionally, when the terminal sends the service request message to the network side device, the terminal stores the context information.

[0106] 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. Through the above method, the context information can be reused after the terminal unavailable period ends, and normal service can be quickly restored based on the context information, thereby improving the user experience.

[0107] Optionally, before the terminal sends a service request message to the network-side device, the network-side device needs to indicate to the terminal that it supports unavailable time during the last registration procedure.

[0108] Correspondingly, the terminal receives second indication information from the network side device, where the second indication information is used to indicate that the network side device supports unavailable time.

[0109] In the above embodiment, the terminal sends a request message to the network side device to instruct the terminal to activate the unavailable time, so that the terminal can synchronize the unavailable time period with the network side device even when the network side device performs congestion control, giving the terminal sufficient flexibility and avoiding the network side device from sending signaling during the period when the terminal is unavailable.

[0110] Optionally, the request message includes:

[0111] A deregistration request message, wherein the deregistration request message does not include an unavailable time period of the terminal.

[0112] It can be understood that the terminal sends a deregistration request message to the network-side device to instruct the terminal to activate the unavailable time, but the deregistration request message does not include the unavailable time period of the terminal.

[0113] In one embodiment, in addition to sending a mobility registration update request message or a service request message to the network side device, the terminal may also send a deregistration request message to the network side device, wherein the deregistration request message does not include the unavailable time period of the terminal.

[0114] Specifically, during T3346, when the target event associated with the terminal is about to be triggered, the terminal initiates a deregistration request procedure to activate the unavailable time; however, the terminal does not include the unavailable time period. This method eliminates the need for the terminal to synchronize the unavailable time period with the network device, thus saving signaling overhead. Furthermore, the network device can determine the terminal's status through the deregistration request message, avoiding unnecessary operations such as paging.

[0115] Optionally, when the terminal sends the deregistration request message to the network-side device, the terminal is unable to store the context information.

[0116] That is to say, the terminal is not capable of storing 5G mobility management context information and 5G session management context information.

[0117] Optionally, before the terminal sends a deregistration request message to the network-side device, the network-side device needs to indicate to the terminal that it supports unavailable time in the last registration procedure.

[0118] Correspondingly, the terminal receives second indication information from the network side device, where the second indication information is used to indicate that the network side device supports unavailable time.

[0119] Optionally, in the case where the network side device performs congestion control, when a target event associated with the terminal is about to be triggered, the specific implementation process of the terminal storing the context information is as follows:

[0120] During the operation of T3346, when the target event associated with the terminal is about to be triggered, the terminal initiates local deregistration. The terminal stores the context for reusing the context after the unavailable period ends, so that normal service can be quickly restored.

[0121] Optionally, when the terminal initiates local deregistration and stores context information, the terminal is capable of storing the context information.

[0122] In other words, the terminal is capable of storing 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. Through the above method, the context information can be reused after the terminal unavailable period ends. Based on the context information, normal service can be quickly restored, thereby improving the user experience.

[0123] Optionally, before the terminal initiates local deregistration and stores context information, the network-side device needs to indicate to the terminal that it supports unavailable time in the last registration procedure.

[0124] Correspondingly, the terminal receives second indication information from the network side device, where the second indication information is used to indicate that the network side device supports unavailable time.

[0125] FIG3 is a second flow chart of the information interaction method provided in an embodiment of the present application. As shown in FIG3 , the method includes step 301; wherein:

[0126] Step 301: When a network side device performs congestion control, the network side device receives a request message from a terminal; wherein the request message is used to indicate that the unavailable time of the terminal is to be activated during the execution of a target event associated with the terminal.

[0127] It should be noted that the embodiments of the present application can be applied to scenarios of NAS-level congestion control (i.e., T3346 is running).

[0128] In the embodiment of the present application, when the network side device performs congestion control, when a target event associated with a terminal is to be triggered, the network side device needs to receive a request message from the terminal.

[0129] Optionally, the request message includes at least one of the following:

[0130] a) A mobility registration update request message, wherein the mobility registration update request message includes an unavailable time period of the terminal.

[0131] b) a service request message, used to activate the unavailable time of the terminal; the service request message includes at least one of the unavailable time period of the terminal and first indication information, where the first indication information is used to indicate that the terminal has no subsequent request.

[0132] In an embodiment of the present application, when the network side device performs congestion control, the network side device determines that the unavailable time of the terminal is to be activated by receiving a request message from the terminal, so that the terminal can store context information during the unavailable time period, so that the terminal can reuse the context information after the unavailable time period ends, and normal service can be quickly restored based on the context information, thereby improving the user experience.

[0133] Optionally, the request message includes:

[0134] A deregistration request message, wherein the deregistration request message does not include an unavailable time period of the terminal.

[0135] It can be understood that the network-side device receives the deregistration request message from the terminal to instruct the terminal to activate the unavailable time, but the deregistration request message does not include the unavailable time period of the terminal.

[0136] In one embodiment, in addition to receiving a mobility registration update request message or a service request message from a terminal, the network side device can also receive a deregistration request message from the terminal, where the deregistration request message is used to activate the unavailable time of the terminal; the deregistration request message does not include the unavailable time period of the terminal.

[0137] Optionally, the network side device also needs to send second indication information to the terminal, where the second indication information is used to indicate that the network side device supports unavailable time.

[0138] Optionally, when the request message includes at least one of the mobility registration update request message and the service request message, after the unavailable time period of the terminal has passed or the terminal enters the connected state, the network side device performs at least one of the following operations:

[0139] a) Storing the unavailable time period of the terminal.

[0140] b) After completing the mobility registration update procedure and service request procedure, release the non-access stratum NAS signaling connection.

[0141] The information interaction method provided in the embodiment of the present application is further described below with reference to Figures 4 to 7.

[0142] FIG4 is one of the signaling interaction diagrams of the information interaction method provided in an embodiment of the present application. As shown in FIG4 , FIG4 shows that when T3346 is running, the terminal is not allowed to initiate a mobility registration update except when the terminal needs to activate the unavailable time; specifically, steps 401 to 404 are included, wherein:

[0143] Step 401, T3346 is running.

[0144] Specifically, the T3346 is running in at least one of the following scenarios:

[0145] Scenario 1: The terminal sends a mobility registration update request message to the network-side device, but the message is rejected. The mobility registration update request message is used to indicate that the terminal wants to activate the unavailable time; the terminal wants to activate the unavailable time again.

[0146] Scenario 2: The terminal sends a registration request message to the network device and is rejected. The registration request is not used to instruct the terminal to activate the unavailable time. At this time, the upper layer of the terminal requests to activate the unavailable time.

[0147] Step 402: The UE prepares to execute an event that makes the terminal unavailable, that is, an event that makes the UE unavailable is to be triggered.

[0148] Step 403: During T3346, the UE is allowed to send a mobility registration update request message, which is used to activate the unavailable time; that is, the UE sends a mobility registration update request message to the AMF, including the unavailable time period.

[0149] Before sending the mobility registration update request message, the network side device indicates support for the unavailable time period in the last registration procedure, and the terminal is capable of storing 5G mobility management and 5G session management context.

[0150] The terminal should include information in the registration request to indicate the period of unavailability of the terminal. For example, the terminal can be unavailable for a period of time by using the "unavailable period information element" to indicate the period of unavailability of the terminal and set the subsequent request indication to "no subsequent request". In addition, even if the terminal has one or more active always-on PDU sessions related to 3GPP access, it shall not include the uplink data status IE or the allowed PDU session status IE in the registration request message.

[0151] Step 404: If the UE provides an unavailable time period, the AMF considers the UE unreachable.

[0152] Until the UE resumes normal service or enters the connected state, the received unavailable time period is stored and the NAS signaling connection is released after completing the mobility registration update procedure.

[0153] FIG5 is a second schematic diagram of signaling interaction of the information interaction method provided in an embodiment of the present application. As shown in FIG5 , FIG5 shows a situation where the UE only stores context information and does not initiate a mobility registration update process to activate the unavailable time; specifically, the method includes steps 501 to 503, wherein:

[0154] Step 501: T3346 is running. Specifically, the scenario in which T3346 is running includes at least one of the following:

[0155] Scenario 1: The terminal sends a mobility registration update request message to the network-side device, but the message is rejected. The mobility registration update request message is used to indicate that the terminal wants to activate the unavailable time; the terminal wants to activate the unavailable time again.

[0156] Scenario 2: The terminal sends a registration request message to the network device and is rejected. The registration request is not used to instruct the terminal to activate the unavailable time. At this time, the upper layer of the terminal requests to activate the unavailable time.

[0157] Step 502: The UE prepares to execute an event that makes the terminal unavailable, that is, an event that makes the UE unavailable is to be triggered.

[0158] Step 503: The UE stores the context information, initiates local deregistration, and does not initiate a mobility registration update request; that is, it does not send a mobility registration update request message to the AMF.

[0159] Specifically, by storing the context information, the UE can reuse the context after the unavailable period ends, and can quickly resume normal service.

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

[0161] Before the UE stores the context information, the network needs to indicate support for the unavailable period in the last registration procedure and the UE is capable of storing 5G mobility management context information and 5G session management context information.

[0162] FIG6 is a third signaling interaction diagram of the information interaction method provided in an embodiment of the present application. As shown in FIG6 , FIG6 shows a situation where, when T3346 is running and the UE cannot store the context, a deregistration process is initiated to interact with the network but does not include an unavailable time period; specifically, steps 601 to 605 are included, wherein:

[0163] Step 601, T3346 is running.

[0164] Specifically, the T3346 is running in at least one of the following scenarios:

[0165] Scenario 1: The terminal sends a mobility registration update request message to the network-side device, but the message is rejected. The mobility registration update request message is used to indicate that the terminal wants to activate the unavailable time; the terminal wants to activate the unavailable time again.

[0166] Scenario 2: The terminal sends a registration request message to the network device and is rejected. The registration request is not used to instruct the terminal to activate the unavailable time. At this time, the upper layer of the terminal requests to activate the unavailable time.

[0167] Step 602: The UE prepares to execute an event that makes the terminal unavailable, that is, an event that makes the UE unavailable is to be triggered.

[0168] Step 603: The UE cannot store the context and initiates a deregistration procedure, but does not include an unavailable time period.

[0169] Step 604: The UE sends a deregistration request message to the AMF, which does not include the unavailable time period.

[0170] Step 605: AMF considers the UE unreachable.

[0171] FIG7 is a fourth signaling interaction diagram of the information interaction method provided in an embodiment of the present application. As shown in FIG7 , FIG7 shows a situation where the UE initiates a service request process to activate the unavailable time when T3346 is running; specifically, steps 701 to 705 are included, wherein:

[0172] Step 701, T3346 is running.

[0173] Specifically, the T3346 is running in at least one of the following scenarios:

[0174] Scenario 1: The terminal sends a mobility registration update request message to the network-side device, but the message is rejected. The mobility registration update request message is used to indicate that the terminal wants to activate the unavailable time; the terminal wants to activate the unavailable time again.

[0175] Scenario 2: The terminal sends a registration request message to the network device and is rejected. The registration request is not used to instruct the terminal to activate the unavailable time. At this time, the upper layer of the terminal requests to activate the unavailable time.

[0176] Step 702: The UE prepares to execute an event that makes the terminal unavailable, that is, an event that makes the UE unavailable is to be triggered.

[0177] Step 703: The UE initiates a service request procedure.

[0178] Step 704: The UE sends a service request message to the AMF, where the service request message includes an unavailable time period for activating the unavailable time.

[0179] Furthermore, the terminal does not include at least one of the following in the service request message:

[0180] a) UE context information.

[0181] b) Uplink data status IE (Uplink data status IE).

[0182] c) the Allowed PDU session status IE.

[0183] Also, set the Follow-on request indicator to "No follow-on request pending" in the SERVICE REQUEST message.

[0184] It should be noted that the terminal is capable of containing context information, and the context information includes mobility management context information and session management context information. The context information is stored in the USIM or non-volatile memory.

[0185] Before the UE stores the context, the network needs to indicate support for the unavailable period in the last registration procedure and the terminal is capable of storing 5G mobility management context information and 5G session management context information.

[0186] Step 705: AMF considers the UE unreachable.

[0187] The information interaction method provided in the embodiment of the present application can be executed by an information interaction device. In the embodiment of the present application, the information interaction device provided in the embodiment of the present application is described by taking the information interaction method executed by the information interaction device as an example.

[0188] FIG8 is a schematic diagram of a structure of an information interaction device provided in an embodiment of the present application. As shown in FIG8 , the information interaction device 800 includes:

[0189] The execution module 801 is configured to, when the first timer is running and a target event associated with the terminal is about to be triggered, perform at least one of the following operations:

[0190] Sending a request message to the network side device, where the request message is used to instruct the terminal to activate the unavailable time;

[0191] Store context information;

[0192] The terminal is unavailable during the execution of the target event, and the first timer is a timer related to congestion control.

[0193] In the information interaction device provided in an embodiment of the present application, when the first timer related to congestion control is running, when the target event associated with the terminal is about to be triggered, a request message is sent to the network side device to instruct the terminal to activate the unavailable time, so that the terminal can successfully activate the unavailable time. The terminal can store context information during the unavailable time period, or, when the network side device performs congestion control, when the target event associated with the terminal is about to be triggered, the context information is directly stored so that the terminal can reuse the context information after the unavailable time period ends. Normal service can be quickly restored based on the context information, thereby improving user experience.

[0194] Optionally, include at least one of the following:

[0195] A mobility registration update request message, wherein the mobility registration update request message includes an unavailable time period of the terminal;

[0196] A service request message is used to activate the unavailable time of the terminal; the service request message includes at least one of the unavailable time period of the terminal and first indication information; the first indication information is used to indicate that the terminal has no subsequent request.

[0197] Optionally, the terminal is capable of storing the context information.

[0198] Optionally, the device further comprises:

[0199] The first storage module is configured to store the context information.

[0200] Optionally, the request message includes:

[0201] A deregistration request message, wherein the deregistration request message does not include an unavailable time period of the terminal.

[0202] Optionally, in a case where the request message includes the deregistration request message, the terminal is unable to store the context information.

[0203] Optionally, the device further comprises:

[0204] The second receiving module is used to receive second indication information from the network side device, where the second indication information is used to indicate that the network side device supports unavailable time.

[0205] Optionally, the storage location of the context information includes at least one of the following:

[0206] A Universal Subscriber Identity Module (USIM) of the terminal;

[0207] The non-volatile memory of the terminal.

[0208] Optionally, the context information includes at least one of the following:

[0209] 5G mobility management context information for the fifth generation mobile communication technology;

[0210] 5G session management context information.

[0211] Optionally, the first timer includes: a T3346 timer.

[0212] FIG9 is a second structural diagram of an information interaction device provided in an embodiment of the present application. As shown in FIG9 , the information interaction device 900 includes:

[0213] A first receiving module 901 is configured to receive a request message from a terminal when the network side device performs congestion control;

[0214] The request message is used to indicate that the unavailable time of the terminal is to be activated during the execution of the target event associated with the terminal.

[0215] In the information interaction device provided in the embodiment of the present application, when the network side device performs congestion control, the unavailable time of the terminal is determined to be activated by receiving a request message from the terminal, so that the terminal can store context information during the unavailable time period, so that the terminal can reuse the context information after the unavailable time period ends, and normal service can be quickly restored based on the context information, thereby improving the user experience.

[0216] Optionally, the request message includes at least one of the following:

[0217] A mobility registration update request message, wherein the mobility registration update request message includes an unavailable time period of the terminal;

[0218] A service request message is used to activate the unavailable time of the terminal; the service request message includes at least one of the unavailable time period of the terminal and first indication information, and the first indication information is used to indicate that the terminal has no subsequent request.

[0219] Optionally, the request message includes:

[0220] A deregistration request message, wherein the deregistration request message does not include an unavailable time period of the terminal.

[0221] Optionally, the device further comprises:

[0222] A sending module is used to send second indication information to the terminal, where the second indication information is used to indicate that the network side device supports unavailable time.

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

[0224] A second storage module, configured to store the unavailable time period of the terminal;

[0225] The release module is used to release the non-access layer NAS signaling connection after completing the mobility registration update procedure and the service request procedure.

[0226] The information interaction device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and the other device can be a server, a network attached storage (NAS), etc., which is not specifically limited in the embodiments of the present application.

[0227] The information interaction device provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 2 to 3 and achieve the same technical effects. To avoid repetition, they will not be described here.

[0228] Figure 10 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 1000 provided in an embodiment of the present application includes a processor 1001 and a memory 1002. The memory 1002 stores a program or instruction that can be run on the processor 1001. For example, when the communication device 1000 is a terminal, the program or instruction is executed by the processor 1001 to implement the various steps of the method embodiment shown in Figure 2 above, and can achieve the same technical effect. When the communication device 1000 is a network-side device, the program or instruction is executed by the processor 1001 to implement the various steps of the method embodiment shown in Figure 3 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0229] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG2 . This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, FIG11 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application.

[0230] The terminal 1100 includes but is not limited to: 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 at least some of the components of the processor 1110.

[0231] Those skilled in the art will appreciate that the terminal 1100 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1110 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG11 does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0232] It should be understood that in an embodiment of the present application, the input unit 1104 may include a graphics processing unit (GPU) 11041 and a microphone 11042, and the graphics processor 11041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1106 may include a display panel 11061, and the display panel 11061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1107 includes a touch panel 11071 and at least one of other input devices 11072. The touch panel 11071 is also called a touch screen. The touch panel 11071 may include two parts: a touch detection device and a touch controller. Other input devices 11072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0233] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1101 may transmit the data to the processor 1110 for processing. Furthermore, the RF unit 1101 may send uplink data to the network-side device. Typically, the RF unit 1101 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0234] Memory 1109 can be used to store software programs or instructions and various data. Memory 1109 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). Furthermore, memory x09 may include volatile memory or non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1109 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0235] Processor 1110 may include one or more processing units. Optionally, processor 1110 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1110.

[0236] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG3 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0237] Specifically, an embodiment of the present application also provides a network-side device. As shown in Figure 12, Figure 12 is one of the structural diagrams of a network-side device provided in an embodiment of the present application; the network-side device 1200 includes: an antenna 121, a radio frequency device 122, a baseband device 123, a processor 124, and a memory 125. The antenna 121 is connected to the radio frequency device 122. In the uplink direction, the radio frequency device 122 receives information through the antenna 121 and sends the received information to the baseband device 123 for processing. In the downlink direction, the baseband device 123 processes the information to be sent and sends it to the radio frequency device 122. The radio frequency device 122 processes the received information and sends it out through the antenna 121.

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

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

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

[0241] Specifically, the network side device 1200 of the embodiment of the present application also includes: instructions or programs stored in the memory 125 and executable on the processor 124. The processor 124 calls the instructions or programs in the memory 125 to execute the methods executed by the modules shown in FIG3 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0242] Specifically, an embodiment of the present application further provides a network-side device. As shown in Figure 13, Figure 13 is a second structural diagram of a network-side device provided in an embodiment of the present application. The network-side device 1300 includes a processor 1301, a network interface 1302, and a memory 1303. The network interface 1302 is, for example, a common public radio interface (CPRI).

[0243] Specifically, the network side device 1300 of the embodiment of the present application also includes: instructions or programs stored in the memory 1303 and executable on the processor 1301. The processor 1301 calls the instructions or programs in the memory 1303 to execute the methods executed by the modules shown in FIG3 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0244] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned information interaction method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0246] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned information interaction method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0247] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0248] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned information interaction method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0249] An embodiment of the present application also provides an information interaction system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the information interaction method shown in Figure 2 above, and the network side device can be used to execute the steps of the information interaction method shown in Figure 3 above.

[0250] It should be noted that, in this article, the terms "comprise", "include" or any other variants 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. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0251] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0252] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. An information interaction method, comprising: In the case where the first timer is running, when a target event associated with the terminal is to be triggered, the terminal performs at least one of the following operations: Sending a request message to the network side device, where the request message is used to indicate that the terminal wants to activate the unavailable time; Store context information; Wherein, the terminal is unavailable during the execution of the target event, and the first timer is a timer related to congestion control.

2. The information interaction method according to claim 1, wherein: The request message includes at least one of the following: A mobility registration update request message, wherein the mobility registration update request message includes an unavailable time period of the terminal; A service request message, wherein the service request message includes at least one of an unavailable time period of the terminal and first indication information; the first indication information is used to indicate that the terminal has no subsequent request.

3. The information interaction method according to claim 1 or 2, wherein: The terminal is capable of storing the context information.

4. The information interaction method according to any one of claims 1 to 3, wherein: The method further comprises: The terminal stores the context information.

5. The information interaction method according to claim 1, wherein: The request message includes: A deregistration request message, wherein the deregistration request message does not include an unavailable time period of the terminal.

6. The information interaction method according to claim 5, wherein: In case the request message includes the deregistration request message, the terminal is not capable of storing the context information.

7. The information interaction method according to any one of claims 1 to 6, wherein: The method further comprises: The terminal receives second indication information from the network side device, where the second indication information is used to indicate that the network side device supports unavailable time.

8. The information interaction method according to any one of claims 1 to 7, wherein: The storage location of the context information includes at least one of the following: A Universal Subscriber Identity Module (USIM) of the terminal; A non-volatile memory of the terminal.

9. The information interaction method according to any one of claims 1 to 8, wherein: The context information includes at least one of the following: The fifth generation mobile communication technology 5G mobility management context information; 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, comprising: In the case where the network side device performs congestion control, the network side device receives a request message from the terminal; The request message is used to indicate that the unavailable time of the terminal is to be activated during the execution of the target event associated with the terminal.

12. The information interaction method according to claim 11, wherein: The request message includes at least one of the following: A mobility registration update request message, wherein the mobility registration update request message includes an unavailable time period of the terminal; A service request message, wherein the service request message includes at least one of an unavailable time period of the terminal and first indication information, wherein the first indication information is used to indicate that the terminal has no subsequent request.

13. The information interaction method according to claim 11, wherein: The request message includes: A deregistration request message, wherein the deregistration request message does not include an unavailable time period of the terminal.

14. The information interaction method according to any one of claims 11 to 13, wherein: The method further comprises: The network side device sends second indication information to the terminal, where the second indication information is used to indicate that the network side device supports unavailable time.

15. The information interaction method according to claim 12, wherein: In the case where the terminal sends the request message to the network side device, after the unavailable time period of the terminal has passed or the terminal enters the connected state, the network side device performs at least one of the following operations: storing an unavailable time period of the terminal; After completing the mobility registration update procedure and service request procedure, the non-access stratum NAS signaling connection is released.

16. An information interaction device, comprising: The execution module is configured to, when the first timer is running and the target event associated with the terminal is about to be triggered, perform at least one of the following operations: Sending a request message to the network side device, where the request message is used to indicate that the terminal wants to activate the unavailable time; Store context information; Wherein, the terminal is unavailable during the execution of the target event, and the first timer is a timer related to congestion control.

17. An information interaction device, comprising: A first receiving module, configured to receive a request message from a terminal when the network side device performs congestion control; The request message is used to indicate that the unavailable time of the terminal is to be activated during the execution of the target event associated with the terminal.

18. A terminal comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the information interaction method according to any one of claims 1 to 10 are implemented.

19. A network side device, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the information interaction method according to any one of claims 11 to 15 are implemented.

20. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the information interaction method according to any one of claims 1 to 10, or implements the steps of the information interaction method according to any one of claims 11 to 15.

Images