WO2024255736A1 - 信息交互方法、装置、终端及网络侧设备 - Google Patents

信息交互方法、装置、终端及网络侧设备 Download PDF

Info

Publication number
WO2024255736A1
WO2024255736A1 PCT/CN2024/098472 CN2024098472W WO2024255736A1 WO 2024255736 A1 WO2024255736 A1 WO 2024255736A1 CN 2024098472 W CN2024098472 W CN 2024098472W WO 2024255736 A1 WO2024255736 A1 WO 2024255736A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
request message
side device
network side
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2024/098472
Other languages
English (en)
French (fr)
Inventor
王慧
康艳超
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to EP24822686.2A priority Critical patent/EP4730861A1/en
Priority to KR1020267001464A priority patent/KR20260019651A/ko
Publication of WO2024255736A1 publication Critical patent/WO2024255736A1/zh
Priority to US19/417,678 priority patent/US20260101170A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/02—Access restriction performed under specific conditions
    • H04W48/06—Access restriction performed under specific conditions based on traffic conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/001—Registration rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment

Definitions

  • the present application belongs to the field of communication technology, and specifically relates to an information interaction method, device, terminal and network side equipment.
  • 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.
  • NAS non-access stratum
  • 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 the terminal.
  • an information interaction method which is executed by a terminal, and the method includes:
  • the terminal performs at least one of the following operations:
  • the terminal is unavailable during the execution of the target event, and the first timer is a timer related to congestion control.
  • an information interaction method is provided, which is performed by a network side device, and the method includes:
  • 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.
  • an information interaction device including:
  • the execution module is used for, when the first timer is running, when the target event associated with the terminal is to be triggered When it occurs, do at least one of the following:
  • the terminal is unavailable during the execution of the target event, and the first timer is a timer related to congestion control.
  • 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.
  • a network side device 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 a target event associated with the terminal.
  • a readable storage medium on which a program or instruction is stored.
  • 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.
  • a wireless communication system including: 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.
  • a chip comprising a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run a program or instruction to implement the method according to the first aspect, Or implement the method as described in the second aspect.
  • a computer program/program product is provided, wherein the computer program/program product is stored in a storage medium, and the program/program product 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.
  • the terminal when a first timer related to congestion control is running, when a target event associated with the terminal is to be triggered, the terminal sends a request message to the network side device to indicate that the terminal wants 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 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.
  • FIG1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied;
  • FIG3 is a second flow chart of the information interaction method provided in an embodiment of the present application.
  • FIG4 is one of the signaling interaction schematic diagrams of the information interaction method provided in an embodiment of the present application.
  • FIG5 is a second schematic diagram of signaling interaction of the information interaction method provided in an embodiment of the present application.
  • FIG6 is a third schematic diagram of signaling interaction of the information interaction method provided in an embodiment of the present application.
  • FIG7 is a fourth schematic diagram of signaling interaction of the information interaction method provided in an embodiment of the present application.
  • FIG8 is a schematic diagram of a structure of an information interaction device provided in an embodiment of the present application.
  • FIG9 is a second structural diagram of the information interaction device provided in an embodiment of the present application.
  • FIG10 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • FIG. 11 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application.
  • FIG12 is a schematic diagram of a structure of a network side device provided in an embodiment of the present application.
  • FIG. 13 is a second schematic diagram of the structure of a network side device provided in an embodiment of the present application.
  • 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 the number of objects is not limited.
  • the first object can be one or more.
  • “or” in this application means at least one of the connected objects.
  • “A or B” covers three schemes, namely, Scheme 1: including A and excluding B; Scheme 2: including B and excluding A; Scheme 3: Includes both A and B.
  • the character "/" generally indicates that the objects before and after are in an "or” relationship.
  • indication in this application can be 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, operations to be performed, or request results in the sent indication;
  • an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • 6G 6th Generation
  • FIG1 shows 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 (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle user equipment (VUE), a shipborne equipment, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (a home appliance with wireless communication function, such as a refrigerator, a television, a washing machine or furniture, etc.), a game console, a personal computer
  • 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.
  • 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 referred to as 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 (Wireless Local Area Network, WLAN) access point (Access Point, AP) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.
  • WLAN wireless Local Area Network
  • AP Access Point
  • WiFi wireless Fidelity, WiFi
  • the base station may be referred to as a Node B (Node B, NB), an Evolved Node B (Evolved Node B, eNB), next generation Node B (the next generation Node B, gNB), new radio Node B (New Radio Node B, NR Node B), access point, relay station (Relay Base Station, RBS), serving base station (Serving Base Station, SBS), base transceiver station (Base Transceiver Station, BTS), radio base station, radio transceiver, basic service set (Basic Service Set, BSS), extended service set (Extended Service Set, ESS), home Node B (home Node B, HNB), home evolved Node B (home evolved Node B), transmission reception point (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 taken as an example for
  • the core network equipment may include but is not limited to at least one of the following: core network nodes, core network functions, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery ...
  • MME mobility management entity
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • Policy Control Function Policy Control Function
  • PCRF Policy and Charging Rules Function
  • edge application service discovery function Edge Application Server Discovery ...
  • SUECR Seamless UE context recovery
  • 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, etc.
  • 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 it can quickly interact with the fifth generation mobile communication technology core network ( 5th Generation Mobile Communication Technology Core, 5GC) to restore normal service.
  • the terminal will interact with the network to inform the network of the unavailable period so that the network can determine the status of the terminal and avoid paging and other operations during the unavailable period of the terminal.
  • the terminal may indicate the unavailable period to the network by initiating a mobility registration update process. At this time, the network will consider the terminal unreachable until the unavailable period ends or the terminal enters the connected state. At the same time, if the terminal cannot store the context, the terminal may initiate a deregistration process to indicate the unavailable period to the network. The registration process indicates to the network the period of unavailability.
  • the network may detect NAS signaling congestion and perform congestion control. When congestion control is activated, the network will reject NAS signaling requests and provide T3346 values. In order 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 the terminals. When the terminal turns on the received T3346 value, during the operation of T3346, the terminal is not allowed to initiate any NAS signaling related to the applied congestion control (including initial registration request, mobility registration update request and service request), with some exceptions, such as the terminal receives a paging request from the network, or the terminal initiates signaling for emergency services or high priority access.
  • congestion control When congestion control is activated, the network will reject NAS signaling requests and provide T3346 values. In order 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 the terminals.
  • the terminal turns on the received T3346 value, during the operation
  • the terminal If the terminal is ready to execute an event that makes the terminal unavailable, the terminal that can store the context can initiate a mobile registration update to interact with the network status and unavailable time period. However, if T3346 is running at this time, the terminal is not allowed to initiate a mobility registration update procedure. At this time, the terminal cannot activate the unavailable time. During the terminal unavailable time period, the terminal cannot use the SUECR feature, that is, it cannot store the terminal context, which will extend the time it takes for the terminal to resume normal service. At the same time, the network cannot determine the status of the terminal and may perform unnecessary operations such as paging.
  • the embodiments of the present application provide an information interaction method, apparatus, terminal and network-side equipment.
  • FIG. 2 is a flow chart of an information interaction method according to an embodiment of the present application. As shown in FIG. 2 , the method includes step 201; wherein:
  • 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:
  • the first timer may be a T3346 timer
  • the embodiment of the present application may be applied to a scenario of NAS-level congestion control (i.e., the T3346 timer is running, hereinafter referred to as T3346 is running).
  • the terminal includes but is not limited to the types of terminal 11 listed above; the present application does not limit this.
  • T3346 The scenario being run includes at least one of the following:
  • Scenario 1 The terminal sends a mobility registration update request message to the network side device and 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.
  • Scenario 2 The terminal sends a registration request message to the network side device and is rejected.
  • the registration request is not used to indicate that the terminal wants to activate the unavailable time.
  • the terminal upper layer requests to activate the unavailable time.
  • the terminal when the network side device performs congestion control, when the target time associated with the terminal is to be triggered, the terminal may perform at least one of the following operations:
  • Operation 1 The terminal sends a request message to the network side device to indicate that the terminal wants to activate the unavailable time.
  • the network side device can determine that the terminal is in an unavailable state.
  • Operation 2 The terminal stores the context information.
  • 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.
  • the request message is used to indicate that the terminal is unavailable.
  • the activation unavailable time may be understood as the terminal being unavailable during the unavailable time period.
  • the context information includes at least one of the following:
  • the storage location of the context information includes at least one of the following:
  • the terminal when a first timer related to congestion control is running, when a target event associated with the terminal is to be triggered, the terminal sends a request message to the network side device to indicate that the terminal wants 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 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.
  • the request message includes at least one of the following:
  • the terminal 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.
  • the terminal is capable of storing the context information.
  • the terminal has the ability to store 5G mobility management context information and 5G session management context information.
  • the terminal when the terminal sends the mobility registration update request message to the network side device, the terminal stores the context information.
  • the terminal can store the 5G mobility management context information and the 5G session management context information in the USIM or non-volatile memory of the terminal.
  • the context information can be reused after the terminal is unavailable for a certain period of time, and normal services can be quickly restored based on the context information, thereby improving the user experience.
  • the network side device needs to indicate to the terminal that an unavailable time is supported in the last registration procedure.
  • 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.
  • the terminal 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.
  • the terminal can 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.
  • 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 is set to "no subsequent request”.
  • 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.
  • PDU always-On Protocol Data Unit
  • 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.
  • 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.
  • 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 expressed as follows:
  • the service request message does not include at least one of the following:
  • the terminal is capable of storing the context information.
  • the terminal has the ability to store 5G mobility management context information and 5G session management context information. interest.
  • the terminal when the terminal sends the service request message to the network side device, the terminal stores the context information.
  • the terminal can store the 5G mobility management context information and the 5G session management context information in the USIM or non-volatile memory of the terminal.
  • the context information can be reused after the terminal is unavailable for a certain period of time, and normal services can be quickly restored based on the context information, thereby improving the user experience.
  • the network side device needs to indicate to the terminal that it supports unavailable time in the last registration procedure.
  • 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.
  • the terminal sends a request message to the network side device to indicate that the terminal wants to activate the unavailable time, so that the terminal can synchronize the unavailable time period with the network side device 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.
  • the request message includes:
  • a deregistration request message wherein the deregistration request message does not include an unavailable time period of the terminal.
  • the terminal sends a deregistration request message to the network side device to indicate that the terminal wants to activate the unavailable time, but the deregistration request message does not include the unavailable time period of the terminal.
  • the terminal 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.
  • the terminal initiates a deregistration request procedure to activate the unavailable time; however, the terminal does not include the unavailable time period.
  • the terminal does not need to synchronize the unavailable time period to the network side device, thereby saving signaling overhead; at the same time, the network side device can determine the status of the terminal through the deregistration request message, avoiding unnecessary operations such as paging.
  • the terminal when the terminal sends the deregistration request message to the network side device, the terminal is unable to store the context information.
  • the terminal is not capable of storing 5G mobility management context information and 5G session management context information.
  • the network side device needs to indicate to the terminal that an unavailable time is supported in the last registration procedure.
  • 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.
  • the specific implementation process of the terminal storing the context information is as follows:
  • 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.
  • the terminal when the terminal initiates local deregistration and stores context information, the terminal is capable of storing the context information.
  • 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 USIM or non-volatile memory of the terminal.
  • the network-side device needs to indicate to the terminal that unavailable time is supported in the last registration procedure.
  • 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.
  • FIG. 3 is a second flow chart of the information interaction method provided in an embodiment of the present application. As shown in FIG. 3 , the method includes step 301; wherein:
  • 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.
  • the network side device when the network side device performs congestion control, when the target event associated with the terminal is to be triggered, the network side device needs to receive a request message from the terminal.
  • the request message includes at least one of the following:
  • 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.
  • 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.
  • the request message includes:
  • a deregistration request message wherein the deregistration request message does not include an unavailable time period of the terminal.
  • the network side device receives the deregistration request message from the terminal to indicate that the terminal wants to activate the unavailable time, but the deregistration request message does not include the unavailable time period of the terminal.
  • the network side device in addition to receiving a mobility registration update request message or a service request message from a terminal, can also receive a deregistration request message from the terminal, wherein 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.
  • 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.
  • the network side device performs at least one of the following operations:
  • FIG. 4 is one of the signaling interaction diagrams of the information interaction method provided in an embodiment of the present application. As shown in FIG. 4 , FIG. 4 shows that when T3346 is running, the terminal is not allowed to initiate a mobility registration update except for the case where the terminal needs to activate the unavailable time; specifically including steps 401 to 404, wherein:
  • Step 401, T3346 is running.
  • T3346 is running includes at least one of the following:
  • Scenario 1 The terminal sends a mobility registration update request message to the network side device and 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.
  • Scenario 2 The terminal sends a registration request message to the network side device and is rejected.
  • the registration request is not used to indicate that the terminal wants to activate the unavailable time.
  • the terminal upper layer requests to activate the unavailable time.
  • 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.
  • Step 403 During the operation of 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.
  • the network side device 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 has the ability to store 5G mobility management and 5G session management context.
  • the terminal should include information in the registration request to indicate the period of time during which the terminal is unavailable, for example, the "unavailable period information element" can be used to indicate the period of time during which the terminal is unavailable, and the subsequent request indication is set to "no subsequent request”.
  • the uplink data status IE or the allowed PDU session status IE cannot be included in the registration request message.
  • Step 404 When the UE provides an unavailable time period, the AMF considers the UE to be unreachable.
  • the received unavailable time period is stored and the NAS signaling connection is released after completing the mobility registration update procedure.
  • FIG. 5 is a second schematic diagram of signaling interaction of the information interaction method provided in an embodiment of the present application. As shown in FIG. 5 , FIG. 5 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, steps 501 to 503 are included, wherein:
  • Step 501 T3346 is running.
  • the scenario in which T3346 is running includes at least one of the following:
  • Scenario 1 The terminal sends a mobility registration update request message to the network side device and 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.
  • Scenario 2 The terminal sends a registration request message to the network side device and is rejected.
  • the registration request is not used to indicate that the terminal wants to activate the unavailable time.
  • the terminal upper layer requests to activate the unavailable time.
  • 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.
  • Step 503 The UE stores the context information, initiates local deregistration, and does not initiate a mobility registration update request; that is, does not send a mobility registration update request message to the AMF.
  • the UE can reuse the context after the unavailable time period ends, and can quickly resume normal service.
  • the context information includes mobility management context information and session management context information, and the context information is stored in the USIM or a non-volatile memory.
  • the network Before the UE stores the context information, the network needs to indicate in the last registration procedure that the unavailable period is supported and the UE is capable of storing 5G mobility management context information and 5G session management context information.
  • FIG. 6 is a third signaling interaction diagram of the information interaction method provided in an embodiment of the present application. As shown in FIG. 6 , FIG. 6 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:
  • Step 601, T3346 is running.
  • T3346 is running includes at least one of the following:
  • Scenario 1 The terminal sends a mobility registration update request message to the network side device and 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.
  • Scenario 2 The terminal sends a registration request message to the network side device and is rejected.
  • the registration request is not used to indicate that the terminal wants to activate the unavailable time.
  • the terminal upper layer requests to activate the unavailable time.
  • 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.
  • Step 603 The UE cannot store the context and initiates a deregistration procedure, but does not include an unavailable time period.
  • Step 604 The UE sends a deregistration request message to the AMF, which does not include an unavailable time period.
  • Step 605 AMF considers the UE to be unreachable.
  • FIG. 7 is a fourth schematic diagram of signaling interaction of the information interaction method provided in an embodiment of the present application. As shown in FIG. 7 , FIG. 7 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:
  • Step 701, T3346 is running.
  • T3346 is running includes at least one of the following:
  • Scenario 1 The terminal sends a mobility registration update request message to the network side device and 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.
  • Scenario 2 The terminal sends a registration request message to the network side device and is rejected.
  • the registration request is not used to indicate that the terminal wants to activate the unavailable time.
  • the terminal upper layer requests to activate the unavailable time.
  • 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.
  • Step 703 The UE initiates a service request procedure.
  • 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.
  • the terminal does not include at least one of the following in the service request message:
  • the terminal is capable of containing context information
  • 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.
  • the network 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.
  • Step 705 AMF considers the UE to be unreachable.
  • the information interaction method provided in the embodiment of the present application can be executed by an information interaction device.
  • 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.
  • FIG8 is one of the structural diagrams of the information interaction device provided in the embodiment of the present application. As shown in FIG8 , the information interaction device 800 includes:
  • the execution module 801 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:
  • the terminal is unavailable during the execution of the target event, and the first timer is a timer related to congestion control.
  • the first timer related to congestion control when running, when the target event associated with the terminal is to be triggered, a request message is sent to the network side device to indicate that the terminal wants 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 to be triggered, the context information is directly stored 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.
  • 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 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 the first indication information; the first indication information is used to indicate that the terminal has no subsequent request.
  • the terminal has the capability to store the context information.
  • the device further comprises:
  • the first storage module is used to store the context information.
  • the request message includes:
  • a deregistration request message wherein the deregistration request message does not include an unavailable time period of the terminal.
  • the terminal is not capable of storing the context information.
  • the device further comprises:
  • 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.
  • the storage location of the context information includes at least one of the following:
  • USB Universal Subscriber Identity Module
  • a non-volatile memory of the terminal A non-volatile memory of the terminal.
  • the context information includes at least one of the following:
  • the fifth generation mobile communication technology 5G mobility management context information The fifth generation mobile communication technology 5G mobility management context information
  • the first timer includes: a T3346 timer.
  • FIG. 9 is a second structural diagram of an information interaction device provided in an embodiment of the present application. As shown in FIG. 9 , the information interaction device 900 includes:
  • a first receiving module 901 is used 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.
  • the network side device when the network side device performs congestion control, it is determined 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.
  • 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 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.
  • the request message includes:
  • a deregistration request message wherein the deregistration request message does not include an unavailable time period of the terminal.
  • the device further comprises:
  • 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.
  • the device further comprises at least one of the following:
  • a second storage module used to store the unavailable time period of the terminal
  • 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.
  • the information interaction device in the embodiment 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 a chip.
  • the electronic device can be a terminal, or it can be other devices other than a terminal.
  • the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.
  • the information interaction device provided in the embodiment of the present application can implement each process implemented by the method embodiments of Figures 2 to 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • FIG10 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.
  • the program or instruction is executed by the processor 1001 to implement the various steps of the method embodiment shown in FIG2 above, and can achieve the same technical effect.
  • 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 FIG3 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application also provides a terminal, including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps in the method embodiment shown in Figure 2.
  • This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation of the above-mentioned method embodiment The above methods are applicable to the terminal embodiment and can achieve the same technical effect.
  • FIG11 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application.
  • 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 a processor 1110.
  • the terminal 1100 can also include a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected to the processor 1110 through a power management system, so as to implement functions such as charging, discharging, and power consumption management through the power management system.
  • a power supply such as a battery
  • the terminal structure shown in FIG11 does not constitute a limitation on the terminal, and the terminal can include more or fewer components than shown in the figure, or combine certain components, or arrange components differently, which will not be described in detail here.
  • 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 the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the 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 a volume control key, a switch key, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
  • the RF unit 1101 can transmit the data to the processor 1110 for processing; in addition, the RF unit 1101 can send uplink data to the network side device.
  • the RF unit 1101 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
  • the memory 1109 can be used to store software programs or instructions and various data.
  • the memory 1109 can mainly include a first storage area 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 instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc.
  • the memory x09 can include a volatile memory or a non-volatile memory.
  • the non-volatile memory can 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.
  • Volatile memory can 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 internal Direct Rambus RAM (DRRAM) and the like.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • DDRSDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • DRRAM direct internal Direct Rambus RAM
  • the processor 1110 may include one or more processing units; optionally, the processor 1110 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1110.
  • the embodiment of the present application also provides a network side device, including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the method embodiment shown in Figure 3.
  • the network side device embodiment corresponds to the above-mentioned network side device method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the network side device embodiment, and can achieve the same technical effect.
  • the embodiment of the present application also provides a network side device.
  • Figure 12 is one of the structural schematic diagrams of a network side device provided in the 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.
  • the radio frequency device 122 receives information through the antenna 121 and sends the received information to the baseband device 123 for processing.
  • 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.
  • 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.
  • 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 which 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.
  • the network side device may also include a network interface 126, which is, for example, a Common Public Radio Interface (CPRI).
  • CPRI Common Public Radio Interface
  • 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 Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • FIG13 is a second structural schematic diagram of a network side device provided in the embodiment of the present application; the network side device 1300 includes: a processor 1301, a network interface 1302 and a memory 1303. Among them, the network interface 1302 is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • 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 Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored.
  • the program or instruction is executed by a processor, each process of the above-mentioned information interaction method embodiment is implemented, and the corresponding The same technical effects are achieved, and will not be described here to avoid repetition.
  • 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.
  • the readable storage medium may be a non-transient readable storage medium.
  • 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.
  • 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.
  • the embodiments of the present application further provide a computer program/program product, which is stored in a storage medium and 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 described here.
  • 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 FIG. 2 above, and the network side device can be used to execute the steps of the information interaction method shown in FIG. 3 above.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种信息交互方法、装置、终端及网络侧设备，属于通信技术领域，本申请实施例的信息交互方法包括：在第一定时器正在运行的情况下，在终端关联的目标事件要被触发时，所述终端执行以下至少一项操作：向所述网络侧设备发送请求消息，所述请求消息用于指示所述终端要激活不可用时间；存储上下文信息；其中，在所述目标事件被执行的过程中所述终端不可用，所述第一定时器为与拥塞控制相关的定时器。

Description

信息交互方法、装置、终端及网络侧设备
相关申请的交叉引用
本申请主张在2023年06月15日在中国提交的申请号为202310716455.2的中国专利的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种信息交互方法、装置、终端及网络侧设备。
背景技术
如果终端准备好执行使得终端不可用的事件时，可以存储上下文的终端发起移动注册更新程序激活不可用时间，不可以存储上下文的终端发起去注册程序激活不可用时间。
但是，如果此时非接入层(Non-Access Stratum，NAS)级别拥塞控制激活，即T3346正在运行，此时可以存储上下文的终端无法发起移动性注册更新程序激活不可用时间，从而会导致在终端不可用时间段结束后延长终端恢复正常服务的时间，影响用户体验。
发明内容
本申请实施例提供一种信息交互方法、装置、终端及网络侧设备，能够解决如何使终端快速恢复正常服务的问题。
第一方面，提供了一种信息交互方法，由终端执行，该方法包括：
在第一定时器正在运行的情况下，在终端关联的目标事件要被触发时，所述终端执行以下至少一项操作：
向所述网络侧设备发送请求消息，所述请求消息用于指示所述终端要激活不可用时间；
存储上下文信息；
其中，在所述目标事件被执行的过程中所述终端不可用，所述第一定时器为与拥塞控制相关的定时器。
第二方面，提供了一种信息交互方法，由网络侧设备执行，该方法包括：
在网络侧设备执行拥塞控制的情况下，所述网络侧设备接收来自终端的请求消息；
其中，所述请求消息用于指示在所述终端关联的目标事件被执行的过程中所述终端的不可用时间要被激活。
第三方面，提供了一种信息交互装置，包括：
执行模块，用于在第一定时器正在运行的情况下，在终端关联的目标事件要被触 发时，执行以下至少一项操作：
向所述网络侧设备发送请求消息，所述请求消息用于指示所述终端要激活不可用时间；
存储上下文信息；
其中，在所述目标事件被执行的过程中所述终端不可用，所述第一定时器为与拥塞控制相关的定时器。
第四方面，提供了一种信息交互装置，包括：
第一接收模块，用于在网络侧设备执行拥塞控制的情况下，接收来自终端的请求消息；
其中，所述请求消息用于指示在所述终端关联的目标事件被执行的过程中所述终端的不可用时间要被激活。
第五方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种终端，包括处理器及通信接口，其中，所述处理器用于在第一定时器正在运行的情况下，在终端关联的目标事件要被触发时，存储上下文信息，所述通信接口用于在网络侧设备执行拥塞控制的情况下，在终端关联的目标事件要被触发时，向所述网络侧设备发送请求消息，所述请求消息用于指示所述终端要激活不可用时间；其中，在所述目标事件被执行的过程中所述终端不可用，所述第一定时器为与拥塞控制相关的定时器。
第七方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第八方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述通信接口用于在网络侧设备执行拥塞控制的情况下，接收来自终端的请求消息；其中，所述请求消息用于指示在所述终端关联的目标事件被执行的过程中所述终端的不可用时间要被激活。
第九方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第十方面，提供了一种无线通信系统，包括：终端及网络侧设备，所述终端可用于执行如第一方面所述的方法的步骤，所述网络侧设备可用于执行如第二方面所述的方法的步骤。
第十一方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法， 或实现如第二方面所述的方法。
第十二方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述程序/程序产品被至少一个处理器执行以实现如第一方面所述的信息交互方法，或实现如第二方面所述的信息交互方法的步骤。
在本申请实施例中，在与拥塞控制相关的第一定时器正在运行的情况下，在终端关联的目标事件要被触发时，终端通过向网络侧设备发送用于指示终端要激活不可用时间的请求消息，使终端可以成功激活不可用时间，终端在不可用时间段内可以存储上下文信息，或者，在网络侧设备执行拥塞控制的情况下，在终端关联的目标事件要被触发时，终端直接存储上下文信息，以便终端可以在不可用时间段结束后重用上下文信息，基于上下文信息可以快速恢复正常服务，进而提高用户体验。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例提供的信息交互方法的流程示意图之一；
图3是本申请实施例提供的信息交互方法的流程示意图之二；
图4是本申请实施例提供的信息交互方法的信令交互示意图之一；
图5是本申请实施例提供的信息交互方法的信令交互示意图之二；
图6是本申请实施例提供的信息交互方法的信令交互示意图之三；
图7是本申请实施例提供的信息交互方法的信令交互示意图之四；
图8是本申请实施例提供的信息交互装置的结构示意图之一；
图9是本申请实施例提供的信息交互装置的结构示意图之二；
图10是本申请实施例提供的通信设备的结构示意图；
图11是本申请实施例提供的一种终端的硬件结构示意图；
图12是本申请实施例提供的一种网络侧设备的结构示意图之一；
图13是本申请实施例提供的一种网络侧设备的结构示意图之二。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，本申请中的“或”表示所连接对象的至少其中之一。例如“A或B”涵盖三种方案，即，方案一：包括A且不包括B；方案二：包括B且不包括A；方案三： 既包括A又包括B。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请的术语“指示”既可以是一个直接的指示(或者说显式的指示)，也可以是一个间接的指示(或者说隐含的指示)。其中，直接的指示可以理解为，发送方在发送的指示中明确告知了接收方具体的信息、需要执行的操作或请求结果等内容；间接的指示可以理解为，接收方根据发送方发送的指示确定对应的信息，或者进行判断并根据判断结果确定需要执行的操作或请求结果等。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)或其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统以外的系统，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)、笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(Ultra-mobile Personal Computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(Augmented Reality，AR)、虚拟现实(Virtual Reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、飞行器(flight vehicle)、车载设备(Vehicle User Equipment，VUE)、船载设备、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(Personal Computer，PC)、柜员机或者自助机等终端侧设备。可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。其中，车载设备也可以称为车载终端、车载控制器、车载模块、车载部件、车载芯片或车载单元等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网(Radio Access Network,RAN)设备、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点(Access Point，AP)或无线保真(Wireless Fidelity，WiFi)节点等。其中，基站可被称为节点B(Node B，NB)、演进节点B(Evolved  Node B，eNB)、下一代节点B(the next generation Node B，gNB)、新空口节点B(New Radio Node B，NR Node B)、接入点、中继站(Relay Base Station，RBS)、服务基站(Serving Base Station，SBS)、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点(home Node B，HNB)、家用演进型B节点(home evolved Node B)、发送接收点(Transmission Reception Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。
核心网设备可以包含但不限于如下至少一项：核心网节点、核心网功能、移动管理实体(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)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
为了便于更加清晰地理解本申请各实施例提供的技术方案，首先对一些相关的知识进行如下介绍。
1、无缝UE上下文恢复(Seamless UE context recovery，SUECR)
一些终端内部事件的触发可以使得终端例如用户设备(User Equipment，UE)在一段时间内不可用，例如操作系统升级或设备重启等，此时终端可能会将其上下文(包括移动性管理和会话管理上下文)存储在全球用户身份模块(Universal Subscriber Identity Module，USIM)或非易失性存储器中，以便能够在不可用时间段结束后重用上下文，能够快速与第五代移动通信技术核心网(5th Generation Mobile Communication Technology Core，5GC)进行交互恢复正常服务。并且终端会与网络进行交互，告知网络不可用时间段，以便网络确定终端的状态，在终端不可用期间避免寻呼等操作。
在上述事件开始前，如果终端可以存储上下文，则终端可能通过发起移动性注册更新过程给网络指示不可用时间段，此时网络将认为该终端不可达，直到不可用时间段结束或终端进入连接态。同时如果终端不能存储上下文，则终端可能通过发起去注 册过程给网络指示不可用时间段。
2、拥塞控制机制
网络可能检测到NAS信令拥塞并执行拥塞控制，当拥塞控制激活时，网络会拒绝NAS信令请求并提供T3346值。为了避免超时同步，即大量终端同时发起被延迟的NAS信令请求，网络应该为终端选择不同的T3346值。当终端开启接收到的T3346值，在T3346运行期间，终端不被允许发起与所应用的拥塞控制相关的任何NAS信令(包括初始注册请求，移动性注册更新请求和服务请求)，除了一些例外，例如终端接收到来自网络的寻呼请求，或终端发起紧急服务或高优先级访问的信令等。
如果终端准备好执行使得终端不可用的事件时，可以存储上下文的终端发起移动注册更新与网络交互状态和不可用时间段。但是如果此时T3346正在运行，终端不被允许发起移动性注册更新程序，此时终端无法激活不可用时间，在终端不可用时间段内，终端无法使用SUECR这个特性，即无法存储终端上下文，会延长终端恢复正常服务的时间。同时网络无法确定终端的状态，可能进行寻呼等不必要操作。
综上所述，针对上述存在的问题，本申请实施例提供了一种信息交互方法、装置、终端及网络侧设备。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的信息交互方法进行详细地说明。
图2是本申请实施例提供的信息交互方法的流程示意图之一，如图2所示，该方法包括步骤201；其中：
步骤201、在第一定时器正在运行的情况下，在终端关联的目标事件要被触发时，所述终端执行以下至少一项操作：
向所述网络侧设备发送请求消息，所述请求消息用于指示所述终端要激活不可用时间；
存储上下文信息；其中，在所述目标事件被执行的过程中所述终端不可用，所述第一定时器为与拥塞控制相关的定时器。
需要说明的是，第一定时器可以是T3346定时器，本申请实施例可应用于NAS级别拥塞控制(即T3346定时器正在运行，下述称T3346正在运行)的场景中。所述终端包括但不限于上述所列举的终端11的类型；本申请对此并不限定。
T3346正在运行的场景包括以下至少一项：
场景1、终端向网络侧设备发送移动性注册更新请求消息被拒绝，移动性注册更新请求消息用于指示终端要激活不可用时间；终端想要再次激活不可用时间。
场景2、终端向网络侧设备发送注册请求消息被拒绝，注册请求不用于指示终端要激活不可用时间，此时终端上层请求激活不可用时间。
在本申请实施例中，在网络侧设备执行拥塞控制的情况下，在终端关联的目标时间要被触发时，终端可以执行以下至少一项操作：
操作1、终端向网络侧设备发送用于指示终端要激活不可用时间的请求消息。
相应地，网络侧设备接收到来自终端的请求消息后，即可确定终端处于不可用状态。
操作2、终端存储上下文信息。
一种实施方式中，所述请求消息用于请求激活不可用时间，网络侧设备可以同意或拒绝终端请求激活不可用时间的请求。
一种实施方式中，请求消息用于指示终端不可用。
一种实施方式，激活不可用时间可以理解为终端在不可用时间段内不可用。
可选地，所述上下文信息包括以下至少一项：
a)5G移动性管理上下文信息。
b)5G会话管理上下文信息。
可选地，所述上下文信息的存储位置包括以下至少一项：
a)所述终端的USIM。
b)所述终端的非易失性存储器。
在本申请实施例中，在与拥塞控制相关的第一定时器正在运行的情况下，在终端关联的目标事件要被触发时，终端通过向网络侧设备发送用于指示终端要激活不可用时间的请求消息，使终端可以成功激活不可用时间，终端在不可用时间段内可以存储上下文信息，或者，在网络侧设备执行拥塞控制的情况下，在终端关联的目标事件要被触发时，终端直接存储上下文信息，以便终端可以在不可用时间段结束后重用上下文信息，基于上下文信息可以快速恢复正常服务，进而提高用户体验。
可选地，所述请求消息，包括以下至少一项：
a)移动性注册更新请求消息，所述移动性注册更新请求消息中包含所述终端的不可用时间段。
具体地，在T3346运行期间，在终端关联的目标事件要被触发时，终端被允许发送移动性注册更新请求消息，所述移动性注册更新请求消息用于激活不可用时间，所述移动性注册更新请求消息包含不可用时间段。
可选地，在所述请求消息包括所述移动性注册更新请求消息的情况下，所述终端有能力存储所述上下文信息。
也就是说，终端有能力存储5G移动性管理上下文信息和5G会话管理上下文信息。
可选地，在所述终端向所述网络侧设备发送所述移动性注册更新请求消息的情况下，所述终端存储所述上下文信息。
也就是说，终端可以将5G移动性管理上下文信息和5G会话管理上下文信息存储至终端的USIM或非易失性存储器中。通过上述方法，可以在终端不可用时间段结束后重用上下文信息，基于上下文信息可以快速恢复正常服务，进而提高用户体验。
可选地，在所述终端向所述网络侧设备发送移动性注册更新请求消息之前，所述网络侧设备在上次注册程序中，需要向终端指示支持不可用时间。
相应地，所述终端接收来自所述网络侧设备的第二指示信息，所述第二指示信息用于指示所述网络侧设备支持不可用时间。
需要说明的是，终端在接收到来自网络侧设备的第二指示信息的情况下，表明网络侧设备具备支持不可用时间的能力，在终端和网络侧设备均支持不可用时间的情况下，在终端关联的目标事件要被触发时，终端才可以激活不可用时间；相应地，网络侧设备可以在不可用时间段内避免进行寻呼等操作。
所述终端应该在注册请求消息中包含用于指示终端不可用时间段的信息，例如可以通过“不可用时间段信息元素”指示终端不可用时间段的信息，将后续请求指示设置为“没有后续请求”。
此外，即使终端具有一个或多个与第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)访问相关的活动的始终在线协议数据单元(Protocol Data Unit，PDU)会话，也不能在注册请求消息中包含上行链路数据状态(Uplink data status)信息元素(Information Element，IE)或允许的PDU会话状态(the Allowed PDU session status)IE。
需要说明的是，如果终端提供了不可用时间段，网络侧设备应该认为终端不可达直到终端恢复正常业务或进入连接态；此时，网络侧设备需要存储收到的不可用时间段，并且在完成移动性注册更新程序后释放NAS信令连接。
b)服务请求消息，用于激活所述终端的不可用时间；所述服务请求消息中包含所述终端的不可用时间段及第一指示信息中至少一项；所述第一指示信息用于指示所述终端没有后续请求。
具体地，在T3346运行期间，在终端关联的目标事件要被触发时，终端发起服务请求程序，在服务请求消息中包含终端的不可用时间段，用于激活不可用时间。
进一步地，服务请求消息中还包含用于指示终端没有后续请求的第一指示信息，第一指示信息例如可以是后续请求指示信息，具体可以表示如下：
Follow-on request indicator to"No follow-on request pending"in the SERVICE REQUEST message。即，在服务请求消息中将后续请求指示信息设置为“没有后续请求”。
可选地，在所述服务请求消息中不包含以下至少一项：
[1]、上行链路数据状态IE。
[2]、允许的PDU会话状态IE。
可选地，在所述请求消息包括所述服务请求消息的情况下，所述终端有能力存储所述上下文信息。
也就是说，终端有能力存储5G移动性管理上下文信息和5G会话管理上下文信 息。
可选地，在所述终端向所述网络侧设备发送所述服务请求消息的情况下，所述终端存储所述上下文信息。
也就是说，终端可以将5G移动性管理上下文信息和5G会话管理上下文信息存储至终端的USIM或非易失性存储器中。通过上述方法，可以在终端不可用时间段结束后重用上下文信息，基于上下文信息可以快速恢复正常服务，进而提高用户体验。
可选地，在所述终端向所述网络侧设备发送服务请求消息之前，所述网络侧设备在上次注册程序中，需要向终端指示支持不可用时间。
相应地，所述终端接收来自所述网络侧设备的第二指示信息，所述第二指示信息用于指示所述网络侧设备支持不可用时间。
在上述实施方式中，终端通过向网络侧设备发送用于指示终端要激活不可用时间的请求消息，使终端在网络侧设备执行拥塞控制的情况下，也能够与网络侧设备同步不可用时间段，给与终端足够的灵活性且能够避免网络侧设备在终端不可用期间发送信令。
可选地，所述请求消息包括：
去注册请求消息，所述去注册请求消息中不包含所述终端的不可用时间段。
可以理解，终端向网络侧设备发送去注册请求消息以指示终端要激活不可用时间，但去注册请求消息中不包含所述终端的不可用时间段。
一种实施方式中，终端除了可以向网络侧设备发送移动性注册更新请求消息或服务请求消息之外，还可以向网络侧设备发送去注册请求消息，所述去注册请求消息中不包含所述终端的不可用时间段。
具体地，在T3346运行期间，在所述终端关联的目标事件要被触发时，所述终端发起去注册请求程序，用于激活不可用时间；但是终端不包含不可用时间段。通过上述方法，使终端不需要向网络侧设备同步不可用时间段，从而节省了信令开销；同时，网络侧设备可以通过去注册请求消息确定终端的状态，避免进行寻呼等不必要操作。
可选地，在所述终端向所述网络侧设备发送所述去注册请求消息的情况下，所述终端没有能力存储所述上下文信息。
也就是说，终端没有能力存储5G移动性管理上下文信息和5G会话管理上下文信息。
可选地，在所述终端向所述网络侧设备发送去注册请求消息之前，所述网络侧设备在上次注册程序中，需要向终端指示支持不可用时间。
相应地，所述终端接收来自所述网络侧设备的第二指示信息，所述第二指示信息用于指示所述网络侧设备支持不可用时间。
可选地，在网络侧设备执行拥塞控制的情况下，在终端关联的目标事件要被触发时，终端存储上下文信息的具体实现过程如下：
在T3346运行期间，在终端关联的目标事件要被触发时，终端发起本地去注册，所述终端存储上下文，用于在不可用时间段结束后重用上下文，能够快速恢复正常服务。
可选地，在所述终端发起本地去注册，存储上下文信息的情况下，所述终端有能力存储所述上下文信息。
也就是说，终端有能力存储5G移动性管理上下文信息和5G会话管理上下文信息。终端可以将5G移动性管理上下文信息和5G会话管理上下文信息存储至终端的USIM或非易失性存储器中。通过上述方法，可以在终端不可用时间段结束后重用上下文信息，基于上下文信息可以快速恢复正常服务，进而提高用户体验。
可选地，在所述终端发起本地去注册，存储上下文信息之前，所述网络侧设备在上次注册程序中，需要向终端指示支持不可用时间。
相应地，所述终端接收来自所述网络侧设备的第二指示信息，所述第二指示信息用于指示所述网络侧设备支持不可用时间。
图3是本申请实施例提供的信息交互方法的流程示意图之二，如图3所示，该方法包括步骤301；其中：
步骤301、在网络侧设备执行拥塞控制的情况下，所述网络侧设备接收来自终端的请求消息；其中，所述请求消息用于指示在所述终端关联的目标事件被执行的过程中所述终端的不可用时间要被激活。
需要说明的是，本申请实施例可应用于NAS级别拥塞控制(即T3346正在运行)的场景中。
在本申请实施例中，在网络侧设备执行拥塞控制的情况下，在终端关联的目标事件要被触发时，网络侧设备需要接收来自终端的请求消息。
可选地，所述请求消息，包括以下至少一项：
a)移动性注册更新请求消息，所述移动性注册更新请求消息中包含所述终端的不可用时间段。
b)服务请求消息，用于激活所述终端的不可用时间；所述服务请求消息中包含所述终端的不可用时间段及第一指示信息中至少一项，所述第一指示信息用于指示所述终端没有后续请求。
在本申请实施例中，在网络侧设备执行拥塞控制的情况下，网络侧设备通过接收来自终端的请求消息确定终端的不可用时间要被激活，从而可以使终端在不可用时间段内可以存储上下文信息，以便终端在不可用时间段结束后可以重用上下文信息，基于上下文信息可以快速恢复正常服务，进而提高用户体验。
可选地，所述请求消息包括：
去注册请求消息，所述去注册请求消息中不包含所述终端的不可用时间段。
可以理解，网络侧设备接收来自终端的去注册请求消息以指示终端要激活不可用 时间，但去注册请求消息中不包含所述终端的不可用时间段。
一种实施方式中，网络侧设备除了可以接收来自终端的移动性注册更新请求消息或服务请求消息之外，还可以接收来自所述终端的去注册请求消息，所述去注册请求消息用于激活所述终端的不可用时间；所述去注册请求消息中不包含所述终端的不可用时间段。
可选地，所述网络侧设备还需要向所述终端发送第二指示信息，所述第二指示信息用于指示所述网络侧设备支持不可用时间。
可选地，在所述请求消息包括所述移动性注册更新请求消息及所述服务请求消息中至少一项的情况下，在经过所述终端的不可用时间段或所述终端进入连接态之后，所述网络侧设备执行以下至少一项操作：
a)存储所述终端的不可用时间段。
b)在完成移动性注册更新程序及服务请求程序之后，释放非接入层NAS信令连接。
下面结合图4至图7对本申请实施例提供的信息交互方法进行进一步说明。
图4是本申请实施例提供的信息交互方法的信令交互示意图之一，如图4所示，图4示出了当T3346运行时，终端不被允许发起移动性注册更新除了终端需要激活不可用时间的情形；具体包括步骤401至步骤404，其中：
步骤401、T3346正在运行。
具体地，T3346正在运行的场景包括以下至少一项：
场景1、终端向网络侧设备发送移动性注册更新请求消息被拒绝，移动性注册更新请求消息用于指示终端要激活不可用时间；终端想要再次激活不可用时间。
场景2、终端向网络侧设备发送注册请求消息被拒绝，注册请求不用于指示终端要激活不可用时间，此时终端上层请求激活不可用时间。
步骤402、UE准备执行使得终端不可用的事件，即，使UE不可用的事件要被触发。
步骤403、在T3346运行期间，UE被允许发送移动性注册更新请求消息，移动性注册更新请求消息用于激活不可用时间；即，UE向AMF发送移动性注册更新请求消息，包含不可用时间段。
在发送移动性注册更新请求消息之前，网络侧设备在上次注册程序中指示支持不可用时间段，且终端有能力存储5G移动性管理和5G会话管理上下文。
终端应该在注册请求中包含用于指示终端不可用时间段的信息，例如可以通过“不可用时间段信息元素”指示终端不可用时间段的信息，将后续请求指示设置为“没有后续请求”。此外，即使终端具有一个或多个与3GPP访问相关的活动的始终在线PDU会话，也不能在注册请求消息中包含上行链路数据状态IE或允许的PDU会话状态IE。
步骤404、在UE提供了不可用时间段的情况下，AMF认为UE不可达。
直到UE恢复正常业务或进入连接态，存储收到的不可用时间段且在完成移动性注册更新程序后释放NAS信令连接。
图5是本申请实施例提供的信息交互方法的信令交互示意图之二，如图5所示，图5示出了UE只存储上下文信息，不发起移动性注册更新过程激活不可用时间的情形；具体包括步骤501至步骤503，其中：
步骤501、T3346正在运行。具体地，T3346正在运行的场景包括以下至少一项：
场景1、终端向网络侧设备发送移动性注册更新请求消息被拒绝，移动性注册更新请求消息用于指示终端要激活不可用时间；终端想要再次激活不可用时间。
场景2、终端向网络侧设备发送注册请求消息被拒绝，注册请求不用于指示终端要激活不可用时间，此时终端上层请求激活不可用时间。
步骤502、UE准备执行使得终端不可用的事件，即，使UE不可用的事件要被触发。
步骤503、UE存储上下文信息，发起本地去注册，不发起移动性注册更新请求；即，不向AMF发送移动性注册更新请求消息。
具体地，UE通过存储上下文信息，可以在不可用时间段结束后重用上下文，能够快速恢复正常服务。
上下文信息包括移动性管理上下文信息和会话管理上下文信息，上下文信息存储在USIM或非易失性存储器中。
在UE存储上下文信息之前，网络需要在上次注册程序中指示支持不可用时间段，且UE有能力存储5G移动性管理上下文信息和5G会话管理上下文信息。
图6是本申请实施例提供的信息交互方法的信令交互示意图之三，如图6所示，图6示出了当T3346运行时，UE不能存储上下文时，发起去注册过程与网络交互但不包含不可用时间段的情形；具体包括步骤601至步骤605，其中：
步骤601、T3346正在运行。
具体地，T3346正在运行的场景包括以下至少一项：
场景1、终端向网络侧设备发送移动性注册更新请求消息被拒绝，移动性注册更新请求消息用于指示终端要激活不可用时间；终端想要再次激活不可用时间。
场景2、终端向网络侧设备发送注册请求消息被拒绝，注册请求不用于指示终端要激活不可用时间，此时终端上层请求激活不可用时间。
步骤602、UE准备执行使得终端不可用的事件，即，使UE不可用的事件要被触发。
步骤603、UE不能存储上下文，发起去注册程序，但不包含不可用时间段。
步骤604、UE向AMF发送去注册请求消息，不包含不可用时间段。
步骤605、AMF认为UE不可达。
图7是本申请实施例提供的信息交互方法的信令交互示意图之四，如图7所示， 图7示出了当T3346运行时，UE发起服务请求过程激活不可用时间的情形；具体包括步骤701至步骤705，其中：
步骤701、T3346正在运行。
具体地，T3346正在运行的场景包括以下至少一项：
场景1、终端向网络侧设备发送移动性注册更新请求消息被拒绝，移动性注册更新请求消息用于指示终端要激活不可用时间；终端想要再次激活不可用时间。
场景2、终端向网络侧设备发送注册请求消息被拒绝，注册请求不用于指示终端要激活不可用时间，此时终端上层请求激活不可用时间。
步骤702、UE准备执行使得终端不可用的事件，即，使UE不可用的事件要被触发。
步骤703、UE发起服务请求程序。
步骤704、UE向AMF发送服务请求消息，在服务请求消息中包含不可用时间段，用于激活不可用时间。
进一步地，终端在服务请求消息中不包含以下至少一项：
a)UE上下文信息。
b)上行链路数据状态IE(Uplink data status IE)。
c)允许的PDU会话状态IE(the Allowed PDU session status IE)。
并且，设置Follow-on request indicator to"No follow-on request pending"in the SERVICE REQUEST message。
需要说明的是，终端有能力包含上下文信息，上下文信息包括移动性管理上下文信息和会话管理上下文信息，上下文信息存储在USIM或非易失性存储器中。
在UE存储上下文之前，网络需要在上次注册程序中指示支持不可用时间段，且终端有能力存储5G移动性管理上下文信息和5G会话管理上下文信息。
步骤705、AMF认为UE不可达。
本申请实施例提供的信息交互方法，执行主体可以为信息交互装置。本申请实施例中以信息交互装置执行信息交互方法为例，说明本申请实施例提供的信息交互装置。
图8是本申请实施例提供的信息交互装置的结构示意图之一，如图8所示，该信息交互装置800，包括：
执行模块801，用于在第一定时器正在运行的情况下，在终端关联的目标事件要被触发时，执行以下至少一项操作：
向所述网络侧设备发送请求消息，所述请求消息用于指示所述终端要激活不可用时间；
存储上下文信息；
其中，在所述目标事件被执行的过程中所述终端不可用，所述第一定时器为与拥塞控制相关的定时器。
在本申请实施例提供的信息交互装置中，在与拥塞控制相关的第一定时器正在运行的情况下，在终端关联的目标事件要被触发时，通过向网络侧设备发送用于指示终端要激活不可用时间的请求消息，使终端可以成功激活不可用时间，终端在不可用时间段内可以存储上下文信息，或者，在网络侧设备执行拥塞控制的情况下，在终端关联的目标事件要被触发时，直接存储上下文信息，以便终端可以在不可用时间段结束后重用上下文信息，基于上下文信息可以快速恢复正常服务，进而提高用户体验。
可选地，包括以下至少一项：
移动性注册更新请求消息，所述移动性注册更新请求消息中包含所述终端的不可用时间段；
服务请求消息，用于激活所述终端的不可用时间；所述服务请求消息中包含所述终端的不可用时间段及第一指示信息中至少一项；所述第一指示信息用于指示所述终端没有后续请求。
可选地，所述终端有能力存储所述上下文信息。
可选地，所述装置还包括：
第一存储模块，用于存储所述上下文信息。
可选地，所述请求消息包括：
去注册请求消息，所述去注册请求消息中不包含所述终端的不可用时间段。
可选地，在所述请求消息包括所述去注册请求消息的情况下，所述终端没有能力存储所述上下文信息。
可选地，所述装置还包括：
第二接收模块，用于接收来自所述网络侧设备的第二指示信息，所述第二指示信息用于指示所述网络侧设备支持不可用时间。
可选地，所述上下文信息的存储位置包括以下至少一项：
所述终端的全球用户身份模块USIM；
所述终端的非易失性存储器。
可选地，所述上下文信息包括以下至少一项：
第五代移动通信技术5G移动性管理上下文信息；
5G会话管理上下文信息。
可选地，所述第一定时器包括：T3346定时器。
图9是本申请实施例提供的信息交互装置的结构示意图之二，如图9所示，该信息交互装置900，包括：
第一接收模块901，用于在网络侧设备执行拥塞控制的情况下，接收来自终端的请求消息；
其中，所述请求消息用于指示在所述终端关联的目标事件被执行的过程中所述终端的不可用时间要被激活。
在本申请实施例提供的信息交互装置中，在网络侧设备执行拥塞控制的情况下，通过接收来自终端的请求消息确定终端的不可用时间要被激活，从而可以使终端在不可用时间段内可以存储上下文信息，以便终端在不可用时间段结束后可以重用上下文信息，基于上下文信息可以快速恢复正常服务，进而提高用户体验。
可选地，所述请求消息，包括以下至少一项：
移动性注册更新请求消息，所述移动性注册更新请求消息中包含所述终端的不可用时间段；
服务请求消息，用于激活所述终端的不可用时间；所述服务请求消息中包含所述终端的不可用时间段及第一指示信息中至少一项，所述第一指示信息用于指示所述终端没有后续请求。
可选地，所述请求消息包括：
去注册请求消息，所述去注册请求消息中不包含所述终端的不可用时间段。
可选地，所述装置还包括：
发送模块，用于向所述终端发送第二指示信息，所述第二指示信息用于指示所述网络侧设备支持不可用时间。
可选地，所述装置还包括以下至少一项：
第二存储模块，用于存储所述终端的不可用时间段；
释放模块，用于在完成移动性注册更新程序及服务请求程序之后，释放非接入层NAS信令连接。
本申请实施例中的信息交互装置可以是电子设备，例如具有操作系统的电子设备，也可以是电子设备中的部件，例如集成电路或芯片。该电子设备可以是终端，也可以为除终端之外的其他设备。示例性的，终端可以包括但不限于上述所列举的终端11的类型，其他设备可以为服务器、网络附属存储器(Network Attached Storage，NAS)等，本申请实施例不作具体限定。
本申请实施例提供的信息交互装置能够实现图2至图3的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
图10是本申请实施例提供的通信设备的结构示意图，本申请实施例提供的通信设备1000，包括处理器1001和存储器1002，存储器1002上存储有可在所述处理器1001上运行的程序或指令，例如，该通信设备1000为终端时，该程序或指令被处理器1001执行时实现如上述图2所示方法实施例的各个步骤，且能达到相同的技术效果。该通信设备1000为网络侧设备时，该程序或指令被处理器1001执行时实现上述图3所示方法实施例的各个步骤，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如图2所示方法实施例中的步骤。该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现 方式均可适用于该终端实施例中，且能达到相同的技术效果。具体地，图11是本申请实施例提供的一种终端的硬件结构示意图。
该终端1100包括但不限于：射频单元1101、网络模块1102、音频输出单元1103、输入单元1104、传感器1105、显示单元1106、用户输入单元1107、接口单元1108、存储器1109以及处理器1110等中的至少部分部件。
本领域技术人员可以理解，终端1100还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1110逻辑相连，从而通过电源管理系统实现管理充电、放电以及功耗管理等功能。图11中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1104可以包括图形处理单元(Graphics Processing Unit，GPU)11041和麦克风11042，图形处理器11041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1106可包括显示面板11061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板11061。用户输入单元1107包括触控面板11071以及其他输入设备11072中的至少一种。触控面板11071，也称为触摸屏。触控面板11071可包括触摸检测装置和触摸控制器两个部分。其他输入设备11072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1101接收来自网络侧设备的下行数据后，可以传输给处理器1110进行处理；另外，射频单元1101可以向网络侧设备发送上行数据。通常，射频单元1101包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1109可用于存储软件程序或指令以及各种数据。存储器1109可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器x09可以包括易失性存储器或非易失性存储器。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内 存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器1109包括但不限于这些和任意其它适合类型的存储器。
处理器1110可包括一个或多个处理单元；可选的，处理器1110集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1110中。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如图3所示的方法实施例的步骤。该网络侧设备实施例与上述网络侧设备方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图12所示，图12是本申请实施例提供的一种网络侧设备的结构示意图之一；该网络侧设备1200包括：天线121、射频装置122、基带装置123、处理器124和存储器125。天线121与射频装置122连接。在上行方向上，射频装置122通过天线121接收信息，将接收的信息发送给基带装置123进行处理。在下行方向上，基带装置123对要发送的信息进行处理，并发送给射频装置122，射频装置122对收到的信息进行处理后经过天线121发送出去。
以上实施例中网络侧设备执行的方法可以在基带装置123中实现，该基带装置123包括基带处理器。
基带装置123例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图12所示，其中一个芯片例如为基带处理器，通过总线接口与存储器125连接，以调用存储器125中的程序，执行以上方法实施例中所示的网络设备操作。
该网络侧设备还可以包括网络接口126，该接口例如为通用公共无线接口(Common Public Radio Interface，CPRI)。
具体地，本申请实施例的网络侧设备1200还包括：存储在存储器125上并可在处理器124上运行的指令或程序，处理器124调用存储器125中的指令或程序执行图3所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
具体地，本申请实施例还提供了一种网络侧设备。如图13所示，图13是本申请实施例提供的一种网络侧设备的结构示意图之二；该网络侧设备1300包括：处理器1301、网络接口1302和存储器1303。其中，网络接口1302例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本申请实施例的网络侧设备1300还包括：存储在存储器1303上并可在处理器1301上运行的指令或程序，处理器1301调用存储器1303中的指令或程序执行图3所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述信息交互方法实施例的各个过程，且能达到相 同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。在一些示例中，可读存储介质可以是非瞬态的可读存储介质。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述信息交互方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述信息交互方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种信息交互系统，包括：终端及网络侧设备，所述终端可用于执行如上述图2所示的信息交互方法的步骤，所述网络侧设备可用于执行如上述图3所示的信息交互方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助计算机软件产品加必需的通用硬件平台的方式来实现，当然也可以通过硬件。该计算机软件产品存储在存储介质(如ROM、RAM、磁碟、光盘等)中，包括若干指令，用以使得终端或者网络侧设备执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式的实施方式，这些实施方式均属于本申请的保护之内。

Claims (20)

  1. 一种信息交互方法，包括：
    在第一定时器正在运行的情况下，在终端关联的目标事件要被触发时，所述终端执行以下至少一项操作：
    向所述网络侧设备发送请求消息，所述请求消息用于指示所述终端要激活不可用时间；
    存储上下文信息；
    其中，在所述目标事件被执行的过程中所述终端不可用，所述第一定时器为与拥塞控制相关的定时器。
  2. 根据权利要求1所述的信息交互方法，其中，所述请求消息，包括以下至少一项：
    移动性注册更新请求消息，所述移动性注册更新请求消息中包含所述终端的不可用时间段；
    服务请求消息，所述服务请求消息中包含所述终端的不可用时间段及第一指示信息中至少一项；所述第一指示信息用于指示所述终端没有后续请求。
  3. 根据权利要求1或2所述的信息交互方法，其中，所述终端有能力存储所述上下文信息。
  4. 根据权利要求1至3任一项所述的信息交互方法，其中，所述方法还包括：
    所述终端存储所述上下文信息。
  5. 根据权利要求1所述的信息交互方法，其中，所述请求消息，包括：
    去注册请求消息，所述去注册请求消息中不包含所述终端的不可用时间段。
  6. 根据权利要求5所述的信息交互方法，其中，在所述请求消息包括所述去注册请求消息的情况下，所述终端没有能力存储所述上下文信息。
  7. 根据权利要求1至6中任一项所述的信息交互方法，其中，所述方法还包括：
    所述终端接收来自所述网络侧设备的第二指示信息，所述第二指示信息用于指示所述网络侧设备支持不可用时间。
  8. 根据权利要求1至7中任一项所述的信息交互方法，其中，所述上下文信息的存储位置包括以下至少一项：
    所述终端的全球用户身份模块USIM；
    所述终端的非易失性存储器。
  9. 根据权利要求1至8中任一项所述的信息交互方法，其中，所述上下文信息包括以下至少一项：
    第五代移动通信技术5G移动性管理上下文信息；
    5G会话管理上下文信息。
  10. 根据权利要求1至9中任一项所述的信息交互方法，其中，所述第一定时器 包括：T3346定时器。
  11. 一种信息交互方法，包括：
    在网络侧设备执行拥塞控制的情况下，所述网络侧设备接收来自终端的请求消息；
    其中，所述请求消息用于指示在所述终端关联的目标事件被执行的过程中所述终端的不可用时间要被激活。
  12. 根据权利要求11所述的信息交互方法，其中，所述请求消息，包括以下至少一项：
    移动性注册更新请求消息，所述移动性注册更新请求消息中包含所述终端的不可用时间段；
    服务请求消息，所述服务请求消息中包含所述终端的不可用时间段及第一指示信息中至少一项，所述第一指示信息用于指示所述终端没有后续请求。
  13. 根据权利要求11所述的信息交互方法，其中，所述请求消息，包括：
    去注册请求消息，所述去注册请求消息中不包含所述终端的不可用时间段。
  14. 根据权利要求11至13任一项所述的信息交互方法，其中，所述方法还包括：
    所述网络侧设备向所述终端发送第二指示信息，所述第二指示信息用于指示所述网络侧设备支持不可用时间。
  15. 根据权利要求12所述的信息交互方法，其中，在所述终端向所述网络侧设备发送所述请求消息的情况下，在经过所述终端的不可用时间段或所述终端进入连接态之后，所述网络侧设备执行以下至少一项操作：
    存储所述终端的不可用时间段；
    在完成移动性注册更新程序及服务请求程序之后，释放非接入层NAS信令连接。
  16. 一种信息交互装置，包括：
    执行模块，用于在第一定时器正在运行的情况下，在终端关联的目标事件要被触发时，执行以下至少一项操作：
    向所述网络侧设备发送请求消息，所述请求消息用于指示所述终端要激活不可用时间；
    存储上下文信息；
    其中，在所述目标事件被执行的过程中所述终端不可用，所述第一定时器为与拥塞控制相关的定时器。
  17. 一种信息交互装置，包括：
    第一接收模块，用于在网络侧设备执行拥塞控制的情况下，接收来自终端的请求消息；
    其中，所述请求消息用于指示在所述终端关联的目标事件被执行的过程中所述终端的不可用时间要被激活。
  18. 一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程 序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至10任一项所述的信息交互方法的步骤。
  19. 一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求11至15任一项所述的信息交互方法的步骤。
  20. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至10任一项所述的信息交互方法，或者实现如权利要求11至15任一项所述的信息交互方法的步骤。
PCT/CN2024/098472 2023-06-15 2024-06-11 信息交互方法、装置、终端及网络侧设备 Ceased WO2024255736A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP24822686.2A EP4730861A1 (en) 2023-06-15 2024-06-11 Information interaction method and apparatus, and terminal and network-side device
KR1020267001464A KR20260019651A (ko) 2023-06-15 2024-06-11 정보 인터랙션 방법, 장치, 단말 및 네트워크 측 기기
US19/417,678 US20260101170A1 (en) 2023-06-15 2025-12-12 Information exchange method and apparatus, terminal, and network-side device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310716455.2A CN119155730A (zh) 2023-06-15 2023-06-15 信息交互方法、装置、终端及网络侧设备
CN202310716455.2 2023-06-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/417,678 Continuation US20260101170A1 (en) 2023-06-15 2025-12-12 Information exchange method and apparatus, terminal, and network-side device

Publications (1)

Publication Number Publication Date
WO2024255736A1 true WO2024255736A1 (zh) 2024-12-19

Family

ID=93811653

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/098472 Ceased WO2024255736A1 (zh) 2023-06-15 2024-06-11 信息交互方法、装置、终端及网络侧设备

Country Status (5)

Country Link
US (1) US20260101170A1 (zh)
EP (1) EP4730861A1 (zh)
KR (1) KR20260019651A (zh)
CN (1) CN119155730A (zh)
WO (1) WO2024255736A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150256961A1 (en) * 2012-10-05 2015-09-10 Lg Electronics Inc. Method and device for controlling multipriority in wireless communication system
CN110719607A (zh) * 2018-07-12 2020-01-21 维沃移动通信有限公司 一种网络拥塞指示方法、装置及设备
CN113383574A (zh) * 2019-02-14 2021-09-10 瑞典爱立信有限公司 Amf和smf中的拥塞控制

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150256961A1 (en) * 2012-10-05 2015-09-10 Lg Electronics Inc. Method and device for controlling multipriority in wireless communication system
CN110719607A (zh) * 2018-07-12 2020-01-21 维沃移动通信有限公司 一种网络拥塞指示方法、装置及设备
CN113383574A (zh) * 2019-02-14 2021-09-10 瑞典爱立信有限公司 Amf和smf中的拥塞控制

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LALITH KUMAR, SAMSUNG, QUALCOMM, LG ELECTRONICS, APPLE: "Support of unavailability period", 3GPP DRAFT; S2-2209160; TYPE CR; CR 3749; SUECR, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 30 September 2022 (2022-09-30), XP052208917 *

Also Published As

Publication number Publication date
KR20260019651A (ko) 2026-02-10
EP4730861A1 (en) 2026-04-22
US20260101170A1 (en) 2026-04-09
CN119155730A (zh) 2024-12-17

Similar Documents

Publication Publication Date Title
US20250193787A1 (en) Communication method, terminal, and network-side device
WO2024022440A1 (zh) 小区切换方法、装置及相关设备
WO2023131286A1 (zh) 资源控制方法、装置、终端、网络侧设备及可读存储介质
WO2023208048A1 (zh) 小区切换方法、装置、终端及网络侧设备
EP4503742A1 (en) Resource control method and apparatus, terminal, and network side device
WO2023185845A1 (zh) 通信方法、装置及相关设备
WO2024027638A1 (zh) Ue能力控制方法、装置、终端及网络侧设备
WO2024017244A1 (zh) 信息发送方法、信息接收方法、装置及相关设备
WO2024255736A1 (zh) 信息交互方法、装置、终端及网络侧设备
WO2023202560A1 (zh) 辅小区组信息发送方法、接收方法、终端、设备和介质
WO2023207947A1 (zh) 小区重配置方法、装置、终端及网络侧设备
WO2023165481A1 (zh) 网络故障的处理方法、终端、接入网设备及核心网设备
CN117500009A (zh) 网络回落、指示方法、装置、终端及设备
EP4712597A1 (en) Time synchronization state processing method and apparatus, terminal, and network-side device
JP7670870B2 (ja) リソース処理方法、装置、電子機器及び記憶媒体
WO2025082292A1 (zh) 通信方法、装置及通信设备
WO2025055800A1 (zh) 网络注册处理方法、装置、系统及通信设备
WO2024022389A1 (zh) 小区连接方法、装置及相关设备
WO2025148880A1 (zh) Ntn的通信方法、装置终端及网络侧设备
CN119629773A (zh) 通信处理、信息传输方法、装置及通信设备
WO2025092789A1 (zh) 传输方法、装置、终端及网络侧设备
WO2023143436A1 (zh) 数据转发的方法、装置、终端设备和网络设备
WO2025055801A1 (zh) 注册方法、网络信息记录方法、装置、终端及网络侧设备
WO2023185728A1 (zh) 业务处理方法、装置、终端、网络侧设备及可读存储介质
WO2024169805A1 (zh) 配置更新方法、配置更新装置、终端及网络侧设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24822686

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 1020267001464

Country of ref document: KR

Free format text: ST27 STATUS EVENT CODE: A-0-1-A10-A15-NAP-PA0105 (AS PROVIDED BY THE NATIONAL OFFICE)

WWE Wipo information: entry into national phase

Ref document number: 2024822686

Country of ref document: EP

Ref document number: 1020267001464

Country of ref document: KR

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2024822686

Country of ref document: EP

Effective date: 20260115

ENP Entry into the national phase

Ref document number: 2024822686

Country of ref document: EP

Effective date: 20260115

ENP Entry into the national phase

Ref document number: 2024822686

Country of ref document: EP

Effective date: 20260115

ENP Entry into the national phase

Ref document number: 2024822686

Country of ref document: EP

Effective date: 20260115

WWP Wipo information: published in national office

Ref document number: 1020267001464

Country of ref document: KR

WWP Wipo information: published in national office

Ref document number: 2024822686

Country of ref document: EP