Disaster roaming method, device, and system
Disaster roaming methods enable terminal devices to seamlessly switch to backup networks during disasters, reducing service interruptions and improving user experience by ensuring continuous communication.
Patent Information
- Application Number
- JP2023548208
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-02-10
- Filing Date
- 2022-01-14
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2042-01-14
AI Technical Summary
Existing communication systems fail to provide continuous service to terminal devices during disasters, leading to service interruptions and degraded user experience.
Implementing disaster roaming methods and systems that allow terminal devices to automatically switch to alternative public land mobile networks (PLMNs) equipped to handle disaster scenarios, utilizing stored information and negotiation protocols to ensure seamless service continuity.
Reduces and minimizes service interruptions, enhancing user experience by maintaining network connectivity during disasters through intelligent network switching and pre-identified backup PLMNs.
Smart Images

Figure 0007586551000001 
Figure 0007586551000002 
Figure 0007586551000003
Abstract
Description
[Technical field]
[0001] This application claims priority to Chinese Patent Application No. 202110185266.8, entitled "Disaster Roaming Method, Apparatus, and System," filed with the State Intellectual Property Office of China on February 10, 2021, the entire contents of which are incorporated herein by reference.
[0002] Technical Field TECHNICAL FIELD Embodiments of the present application relate to the field of communications, and more particularly, to a disaster roaming method, apparatus, and system. [Background technology]
[0003] In the prior art, when a disaster occurs, the home public land mobile network (HPLMN) of a terminal device (user equipment, UE) may not be able to provide service to the UE, in which case the service of the UE is interrupted and cannot be restored. Summary of the Invention [Problem to be solved by the invention]
[0004] SUMMARY OF THE DISCLOSURE The embodiments of the present application provide a disaster roaming method, apparatus, and system for reducing service interruptions for terminal devices, minimizing service interruptions, and improving user experience. [Means for solving the problem]
[0005] According to a first aspect, there is provided a disaster roaming method performed in a terminal device, the method comprising: determining a first public land mobile network PLMN based on stored information about disaster roaming PLMNs, the information about disaster roaming PLMNs including identification information of at least one PLMN that allows the terminal device to perform disaster roaming, the first PLMN being a PLMN of the at least one PLMN; sending a registration request message to the first PLMN, the registration request message including disaster roaming indication information, the disaster roaming indication information indicating that the terminal device requests to perform disaster roaming registration; and receiving a registration accept message sent by the first PLMN.
[0006] According to the method provided in the present application, when a network service failure occurs due to a disaster, the terminal device performs disaster roaming to obtain the service, thus reducing the service interruption of the terminal device, minimizing the service interruption, and improving the user experience.
[0007]
[0013] In relation to the first aspect, in some implementations of the first aspect, the information about the disaster roaming PLMN further includes a disaster roaming service time.
[0008] In relation to the first aspect, in some implementations of the first aspect, after receiving the registration acceptance information sent by the first PLMN, the method further includes performing disaster roaming in the first PLMN at a disaster roaming service time.
[0009] In relation to the first aspect, in some implementations of the first aspect, the method further includes notifying a user that the terminal device is performing disaster roaming.
[0010] In relation to the first aspect, in some implementations of the first aspect, determining the first PLMN includes obtaining information about available PLMNs in a current location area, and selecting a PLMN from the at least one PLMN as the first PLMN from the available PLMNs.
[0011] In relation to the first aspect, in some implementations of the first aspect, before determining the first PLMN, the method further includes learning that a currently serving PLMN has stopped providing service due to a disaster.
[0012] In relation to the first aspect, in some implementations of the first aspect, before knowing that the currently serving PLMN has stopped providing service due to a disaster, the method further includes: sending a first message to a second PLMN, the first message including capability information for supporting disaster roaming by the terminal device; receiving a second message sent by the second PLMN, the second message including information about the disaster roaming PLMN; and storing information about the disaster roaming PLMN based on the second message.
[0013] According to the method provided in the present application, the terminal device performs capability negotiation with the second PLMN, the second PLMN delivers information about the disaster roaming PLMN, and the terminal device stores the information about the disaster roaming PLMN. In this way, it can be ensured that disaster roaming is performed when a subsequent disaster occurs, which further reduces the service interruption of the terminal device, minimizes the service interruption, and improves the user experience.
[0014] In relation to the first aspect, in some implementations of the first aspect, the first message is a registration request message.
[0015] In relation to the first aspect, in some implementations of the first aspect, the second message is one of a registration accept message, a registration reject message, a downlink non-access stratum NAS transport message, or a configuration update command message.
[0016] In relation to the first aspect, in some implementations of the first aspect, the second message further includes indication information indicating that the terminal device is allowed to perform disaster roaming.
[0017] In relation to the first aspect, in some implementations of the first aspect, if the second message is registration rejection information, the method further includes storing an identification information of the second PLMN in the information related to the disaster roaming PLMN.
[0018] According to a second aspect, there is provided a disaster roaming method performed in a first network element, the method including the steps of: receiving a first message sent by a terminal device, the first message including capability information supporting disaster roaming by the terminal device; obtaining information about a disaster roaming PLMN providing disaster roaming service for the terminal device based on the capability information supporting disaster roaming; and sending a second message to the terminal device, the second message including information about the disaster roaming PLMN.
[0019] According to the method provided in the present application, the terminal device performs capability negotiation with the second PLMN, the second PLMN delivers information about the disaster roaming PLMN, and the terminal device stores the information about the disaster roaming PLMN. In this way, it can be ensured that disaster roaming is performed when a subsequent disaster occurs, which further reduces the service interruption of the terminal device, minimizes the service interruption, and improves the user experience.
[0020] With respect to the second aspect, in some implementations of the second aspect, the first message is a registration request message.
[0021] In relation to the second aspect, in some implementations of the second aspect, the second message is one of a registration accept message, a registration reject message, a downlink non-access stratum NAS transport message, or a configuration update command message.
[0022] In relation to the second aspect, in some implementations of the second aspect, the second message further includes indication information indicating that the terminal device is allowed to perform disaster roaming.
[0023] In relation to the second aspect, in some implementations of the second aspect, obtaining information regarding a disaster roaming PLMN that provides disaster roaming service for the terminal device includes determining information regarding the disaster roaming PLMN based on a local configuration.
[0024] In relation to the second aspect, in some implementations of the second aspect, before determining information regarding the disaster roaming PLMN based on the local configuration, the method further includes determining, based on the local configuration, to provide disaster roaming service for the terminal device.
[0025] In relation to the second aspect, in some implementations of the second aspect, before determining information regarding the disaster roaming PLMN based on the local configuration, the method further includes a step of receiving indication information transmitted by the second network element indicating that disaster roaming needs to be performed, wherein the indication information indicating that disaster roaming needs to be performed instructs the first network element to perform a disaster roaming service.
[0026] In relation to the second aspect, in some implementations of the second aspect, obtaining information regarding a disaster roaming PLMN that provides disaster roaming service for the terminal device includes receiving information regarding the disaster roaming PLMN transmitted by the second network element.
[0027] In relation to the second aspect, in some implementations of the second aspect, receiving information about the disaster roaming PLMN sent by the second network element further includes receiving an indication sent by the second network element indicating that disaster roaming needs to be performed, wherein the indication information indicating that disaster roaming needs to be performed indicates to the first network element to perform disaster roaming service.
[0028] In relation to the second aspect, in some implementations of the second aspect, prior to the step of receiving indication information indicating that disaster roaming needs to be performed and transmitted by the second network element, or the step of receiving information regarding the disaster roaming PLMN transmitted by the second network element, the method further includes a step of transmitting capability information supporting disaster roaming by the terminal device to the second network element.
[0029] In relation to the second aspect, in some implementations of the second aspect, the information about the disaster roaming PLMN includes an identification of at least one PLMN that allows the terminal device to perform disaster roaming; or a disaster roaming service time; or an identification of at least one PLMN that allows the terminal device to perform disaster roaming and a disaster roaming service time.
[0030] According to a third aspect, there is provided a disaster roaming method performed in a second network element, the method comprising the steps of receiving capability information supporting disaster roaming by a terminal device, the capability information being transmitted by a first network element, determining that the terminal device is allowed to obtain disaster roaming services based on the capability information supporting disaster roaming by the terminal device, and transmitting information regarding a disaster roaming PLMN of the terminal device to the first network element.
[0031] According to the method provided in the present application, a first network element performs capability negotiation with a second network element by reporting capability information of a terminal device, the second network element distributes information about a disaster roaming PLMN, and the terminal device stores the information about the disaster roaming PLMN. In this way, disaster roaming can be ensured to be performed when a subsequent disaster occurs, which further reduces the service interruption of the terminal device, minimizes the service interruption, and improves the user experience.
[0032] In relation to the third aspect, in some implementations of the third aspect, the method further includes a step of sending instruction information to the first network element indicating that disaster roaming needs to be performed, where the instruction information indicating that disaster roaming needs to be performed instructs the first network element to perform a disaster roaming service.
[0033] In relation to the third aspect, in some implementations of the third aspect, determining that the terminal device is allowed to obtain disaster roaming services includes: determining that the terminal device is allowed to obtain disaster roaming services based on capability information and a local configuration supporting disaster roaming by the terminal device.
[0034] In relation to the third aspect, in some implementations of the third aspect, before transmitting information regarding the disaster roaming PLMN of the terminal device to the first network element, the method further includes a step of determining information regarding the disaster roaming PLMN of the terminal device based on a local configuration.
[0035] In relation to the third aspect, in some implementations of the third aspect, the information about the disaster roaming PLMN includes an identity of at least one PLMN that allows the terminal device to perform disaster roaming; or a disaster roaming service time; or an identity of at least one PLMN that allows the terminal device to perform disaster roaming and a disaster roaming service time.
[0036] According to a fourth aspect, there is provided a disaster roaming method performed in a terminal device, the method including: receiving system information sent by a third PLMN, the system information including indication information indicating that disaster roaming is allowed; sending a registration request message to the third PLMN based on the system information, the registration request message including capability information supporting disaster roaming by the terminal device and disaster roaming indication information; and receiving a registration accept message sent by the third PLMN, the registration accept message including a disaster roaming service time provided by the third PLMN.
[0037] According to the method provided in the present application, after a disaster occurs, the terminal device receives system information sent by the third PLMN, and then selects the third PLMN to perform disaster roaming. In this way, service can be obtained, service interruption of the terminal device can be reduced, service interruption can be minimized, and user experience can be improved.
[0038] In relation to the fourth aspect, in some implementations of the fourth aspect, the method further includes performing disaster roaming in the third PLMN during a disaster roaming service time.
[0039] In relation to the fourth aspect, in some implementations of the fourth aspect, the method further includes notifying a user that the terminal device is performing disaster roaming.
[0040] In relation to the fourth aspect, in some implementations of the fourth aspect, before receiving the system information transmitted by the third PLMN, the method further includes a step of learning that the fourth PLMN has stopped providing services due to the disaster, the fourth PLMN being the PLMN that provided services for the terminal device before the disaster.
[0041] In relation to the fourth aspect, in some implementations of the fourth aspect, after learning that the fourth PLMN has stopped providing service due to a disaster, the method further includes: obtaining information about available PLMNs in the current location area; and selecting a PLMN from the available PLMNs among the at least one PLMN as the third PLMN.
[0042] With respect to the fourth aspect, in some implementations of the fourth aspect, the system information further includes an identity of the fourth PLMN.
[0043] According to a fifth aspect, a disaster roaming apparatus is provided. The apparatus has a function of performing the behavior in the method example of the first aspect. The function may be implemented by hardware, or may be implemented by hardware by executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. In one possible design, the apparatus includes a transceiver unit and a processing unit. The processing unit is configured to determine a first public land mobile network PLMN based on stored information on disaster roaming PLMNs, the information on disaster roaming PLMNs includes identification information of at least one PLMN that allows the terminal device to perform disaster roaming, and the first PLMN is a PLMN of the at least one PLMN. The transceiver unit is configured to send a registration request message to the first PLMN, the registration request message includes disaster roaming indication information, and the disaster roaming indication information indicates that the terminal device requests to perform disaster roaming registration. The transceiver unit is further configured to receive a registration accept message sent by the first PLMN.
[0044] These modules can perform corresponding functions in the method example in the first aspect. For details, please refer to the detailed description in the method example. The details will not be described again here.
[0045] According to a sixth aspect, a disaster roaming apparatus is provided. The apparatus may be a core network device or a chip used in a core network device. The apparatus has a function of performing the behavior in the method example of the second aspect. The function may be implemented by hardware, or may be implemented by hardware by executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. In one possible design, the apparatus includes a transceiver unit and a processing unit. The transceiver unit is configured to receive a first message sent by a terminal device, the first message including capability information supporting disaster roaming by the terminal device. The processing unit is configured to obtain information regarding a disaster roaming PLMN providing a disaster roaming service for the terminal device based on the capability information supporting disaster roaming. The transceiver unit is further configured to send a second message to the terminal device, the second message including information regarding the disaster roaming PLMN.
[0046] These modules can perform corresponding functions in the method example in the second aspect. For details, please refer to the detailed description in the method example. The details will not be described again here.
[0047] According to a seventh aspect, a disaster roaming apparatus is provided. The apparatus may be a core network device or a chip used in a core network device. The apparatus has a function of performing the behavior in the method example of the third aspect. The function may be implemented by hardware or by executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. In one possible design, the apparatus includes a transceiver unit and a processing unit. The transceiver unit is configured to receive capability information supporting disaster roaming by a terminal device, the capability information being transmitted by a first network element. The processing unit is configured to determine that the terminal device is allowed to obtain disaster roaming services based on the capability information supporting disaster roaming by the terminal device. The transceiver unit is further configured to transmit information regarding a disaster roaming PLMN of the terminal device to the first network element.
[0048] These modules can perform corresponding functions in the method examples in the third aspect. For details, please refer to the detailed description in the method examples. The details will not be described again here.
[0049] According to an eighth aspect, a disaster roaming apparatus is provided. The apparatus has a function of performing the behavior in the method example of the fourth aspect. The function may be implemented by hardware, or may be implemented by hardware by executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. In one possible design, the apparatus includes a transceiver unit and a processing unit. The transceiver unit is configured to receive system information sent by a third PLMN, the system information including indication information indicating that disaster roaming is allowed. The transceiver unit is further configured to send a registration request message to the third PLMN based on the system information, the registration request message including capability information supporting disaster roaming by the terminal device and disaster roaming indication information. The transceiver unit is further configured to receive a registration accept message sent by the third PLMN, the registration accept message including a disaster roaming service time provided by the third PLMN.
[0050] These modules can perform corresponding functions in the method examples in the fourth aspect. For details, please refer to the detailed description in the method examples. The details will not be described again here.
[0051] According to a ninth aspect, a disaster roaming system is provided. The system includes a first network element and a second network element. The first network element is configured to transmit capability information supporting disaster roaming by a terminal device. The second network element is configured to receive capability information supporting disaster roaming by the terminal device. The second network element is further configured to determine that the terminal device is allowed to obtain disaster roaming services based on the capability information supporting disaster roaming by the terminal device. The second network element is further configured to transmit information regarding a disaster roaming PLMN of the terminal device. The first network element is further configured to receive information regarding a disaster roaming PLMN of the terminal device.
[0052] According to this implementation, the first network element performs capability negotiation with the second network element by reporting capability information of the terminal device, and the second network element delivers information about the disaster roaming PLMN, so that the terminal device stores the information about the disaster roaming PLMN. In this way, it can be ensured that disaster roaming is performed when a subsequent disaster occurs, which further reduces the service interruption of the terminal device, minimizes the service interruption, and improves the user experience.
[0053] In relation to the ninth aspect, in some implementations of the ninth aspect, the second network element is further configured to send indication information indicating that disaster roaming needs to be performed. The first network element is further configured to receive indication information indicating that disaster roaming needs to be performed, the indication information indicating that disaster roaming needs to be performed instructing the first network element to perform a disaster roaming service.
[0054] In relation to the ninth aspect, in some implementations of the ninth aspect, the second network element is configured to determine that the terminal device is allowed to obtain disaster roaming services, and the second network element is particularly configured to determine that the terminal device is allowed to obtain disaster roaming services based on capability information and a local configuration supporting disaster roaming by the terminal device.
[0055] In relation to the ninth aspect, in some implementations of the ninth aspect, before the second network element is configured to transmit information regarding the disaster roaming PLMN of the terminal device, the second network element is further configured to determine information regarding the disaster roaming PLMN of the terminal device based on a local configuration.
[0056] In relation to the ninth aspect, in some implementations of the ninth aspect, the information about the disaster roaming PLMN includes an identity of at least one PLMN that allows the terminal device to perform disaster roaming; or a disaster roaming service time; or an identity of at least one PLMN that allows the terminal device to perform disaster roaming and a disaster roaming service time.
[0057] According to a tenth aspect, an apparatus is provided. The apparatus includes a processor and a transceiver. The processor is connected to the transceiver. The processor is configured to execute instructions, and the transceiver is configured to communicate with another network element under control of the processor. When the processor executes the instructions, the execution enables the apparatus to perform a method of any one of the aforementioned aspects or any possible implementation of any one of the aforementioned aspects. The apparatus further includes a memory, the memory configured to store the instructions.
[0058] According to an eleventh aspect, there is provided a computer readable medium. The computer readable medium stores a computer program (sometimes called code or instructions). When the computer program is executed on a computer, it causes the computer to perform a method according to any one of the preceding aspects or any possible implementation of any one of the preceding aspects.
[0059] According to a twelfth aspect, there is provided a communications chip storing instructions that, when executed on a computing device, cause the communications chip to perform a method of any one of the preceding aspects or any possible implementation of any one of the preceding aspects.
[0060] According to a thirteenth aspect, there is provided a computer program product comprising instructions which, when executed on a computer, enable the computer to perform a method of any one of the preceding aspects, or any possible implementation of any one of the preceding aspects.
[0061] According to a fourteenth aspect, there is provided a chip system. The chip system includes an input interface, an output interface, at least one processor, and a memory. The input interface, the output interface, the processor, and the memory are connected through an internal connection path. The processor is configured to execute code in the memory, and when the code is executed, the processor is configured to execute the method in the previous aspect.
[0062] Based on the above technical solutions, the service interruption of the terminal device can be reduced, the service interruption can be minimized, and the user experience can be improved. [Brief description of the drawings]
[0063] [Figure 1] 1 is a schematic diagram of the architecture of a 5G mobile communication system.
[0064] [Diagram 2] 2 is a schematic flow chart of a disaster roaming method according to the present application;
[0065] [Diagram 3] 2 is a schematic flow chart of a disaster roaming method according to the present application;
[0066] [Figure 4] 2 is a schematic flow chart of a disaster roaming method according to the present application;
[0067] [Diagram 5] 2 is a schematic flow chart of a disaster roaming method according to the present application;
[0068] [Figure 6] 1 is a schematic flow chart of an example of a disaster roaming method according to the present application;
[0069] [Figure 7] 1 is a schematic flow chart of an example of a disaster roaming method according to the present application;
[0070] [Figure 8] 1 is a schematic flow chart of an example of a disaster roaming method according to the present application;
[0071] [Figure 9] 1 is a schematic flow chart of an example of a disaster roaming method according to the present application;
[0072] [Figure 10] 1 is a schematic flow chart of an example of a disaster roaming method according to the present application;
[0073] [Figure 11] 4 is a schematic flow chart of another disaster roaming method according to the present application;
[0074] [Figure 12]FIG. 1 is a schematic diagram of the structure of a disaster roaming device according to the present application;
[0075] [Figure 13] FIG. 2 is a schematic diagram of the structure of another disaster roaming device according to the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0076] The following describes the technical solutions of the present application with reference to the accompanying drawings.
[0077] The technical solutions in the embodiments of the present application may be applied to various communication systems, such as Global System for Mobile communications (GSM), Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) systems, General Packet Radio Service (GPRS), Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunications System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, future 5th Generation (5G) systems or New Radio (NR) systems, and future evolving communication systems.
[0078] 1 is a schematic diagram of a network architecture of a communication system to which an embodiment of the present application can be applied. The network architecture includes a terminal device, an access network device, an access management network element, a session management network element, a user plane network element, a policy control network element, a network slice selection network element, a network repository function network element, a network data analysis network element, a unified data management network element, a unified data storage network element, an authentication service function network element, a network publishing network element, an application function network element, and a data network (DN) connected to an operator network. The terminal device can transmit service data to the data network and receive service data from the data network through the access network device and the user plane network element.
[0079] A terminal device is a device having radio transceiver capabilities and may be deployed on land, on water (e.g., on a ship), or in the air (e.g., on an aircraft, balloon, or satellite), including indoor, outdoor, handheld, or vehicle-mounted devices. The terminal device may communicate with the core network through a radio access network (RAN) and may exchange voice and / or data with the RAN. The terminal device may be a mobile phone, a tablet computer (pad), a computer with a wireless transceiver function, a mobile internet device (MID), a wearable device, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. The application scenario is not limited in the embodiment of the embodiment application of this application. The terminal device may also be called user equipment (UE), a mobile station, a remote station, etc. The specific technology, device type, and name used by the terminal device are not limited in the embodiment of this application.
[0080] An access network device is a device in a network and configured to connect terminal devices to a wireless network. An access network device may be a node in a wireless access network and may be referred to as a base station or may be referred to as a radio access network (RAN) node (or device). An access network device may include an evolved base station (NodeB or eNB or e-NodeB, evolved NodeB) in a long term evolution (LTE) system or an LTE-Advanced system (LTE-Advanced, LTE-A), such as a conventional macro base station eNB and a micro base station eNB in a heterogeneous network scenario. Alternatively, an access network device may include a next generation NodeB (gNB) in a 5th generation mobile communication technology (5th generation, 5G) new radio (NR) system. Alternatively, the access network device may further include a radio network controller (RNC), a NodeB (NB), a base station controller (BSC), a base transceiver station (BTS), a transmission reception point (TRP), a Home Evolved NodeB (e.g., a Home Evolved NodeB, or Home NodeB, HNB), a baseband unit (BBU), a baseband pool (BBU pool), or a Wi-Fi access point (AP), etc.Alternatively, the access network device may further include a central unit (CU) and a distributed unit (DU) in a cloud radio access network (Cloud RAN) system. This is not limited in the embodiment of the present application. In a scenario in which the CU and DU included in the access network device are deployed separately, the CU supports protocols such as radio resource control (RRC), packet data convergence protocol (PDCP), and service data adaptation protocol (SDAP). The DU mainly supports radio link control layer (RLC) protocol, media access control layer (MAC) protocol, and physical layer protocol.
[0081] The access management network element is mainly used for terminal attachment, mobility management, and tracking area update processes in a mobile network. The access management network element terminates non-access stratum (NAS) messages, completes registration management, connection management, and reachability management, allocates tracking area list (TA list), completes mobility management, etc., and transparently routes session management (SM) messages to the session management network element. In a 5th generation (5G) communication system, the access management network element may be an access and mobility management function (AMF). In a future communication system (e.g., a 6G communication system), the mobility management network element may still be an AMF network element or may have another name. This is not limited in the present application.
[0082] The session management network element is mainly used for session management in mobile networks, for example, session establishment, modification, and release. A specific function is, for example, to assign an internet protocol (IP) address to a terminal or to select a user plane network element that provides a packet forwarding function. In a 5G communication system, the session management network element may be a session management function (SMF). In future communication systems (for example, a 6G communication system), the session management network element may still be an SMF network element or may have another name. This is not limited in the present application.
[0083] The user plane network element is mainly configured to process user packets, for example, forwarding, charging, or lawful interception. The user plane network element may also be called a protocol data unit (PDU) session anchor (PSA). In a 5G communication system, the user plane network element may be a user plane function (UPF). In future communication systems (e.g., 6G communication systems), the user plane network element may still be a UPF network element or may have another name. This is not limited in the present application.
[0084] The policy control network element includes a subscriber subscription data management function, a policy control function, a charging policy control function, a quality of service (QoS) control, etc. In a 5G communication system, the policy control network element may be a policy control function (PCF). In future communication systems (e.g., 6G communication systems), the policy control network element may still be a PCF network element or may have another name. This is not limited in the present application.
[0085] The network slice selection function network element is mainly configured to select a suitable network slice for the service of the terminal device. In a 5G communication system, the network slice selection network element may be a network slice selection function (NSSF) network element. In a future communication system (e.g., a 6G communication system), the network slice selection network element may still be an NSSF network element or may have another name. This is not limited in the present application.
[0086] The network repository function network element is mainly configured to provide registration and discovery functions of the network element or services provided by the network element. In a 5G communication system, the network repository function network element may be a network repository function (NRF). In future communication systems (e.g., 6G communication systems), the network repository function network element may still be an NRF network element or may have another name. This is not limited in the present application.
[0087] The network data analytics network element may collect data (through a network publishing function network element) from each network function (NF), for example, a policy control network element, a session management network element, a user plane network element, an access management network element, and an application function network element, and perform analysis and prediction. In a 5G communication system, the network data analytics network element may be a network data analytics function (NWDAF). In future communication systems (e.g., 6G communication systems), the network data analytics network element may still be an NWDAF network element or may have a different name. This is not limited in this application.
[0088] The unified data management network element is mainly configured to manage subscription information of terminal devices. In a 5G communication system, the unified data management network element may be a unified data management (UDM). In a future communication system (e.g., a 6G communication system), the unified data management network element may still be a UDM network element, or may have another name. This is not limited in the present application.
[0089] The unified data storage network element is configured to store structured data information, mainly including subscription information, policy information, and network data or service data defined in a standard format. In a 5G communication system, the unified data storage network element may be a unified data repository (UDR). In a future communication system (e.g., a 6G communication system), the unified data storage network element may still be a UDR network element or may have another name. This is not limited in the present application.
[0090] The authentication service function network element is mainly configured to perform security authentication for terminal devices. In a 5G communication system, the authentication service function network element may be an authentication server function (AUSF). In a future communication system (e.g., a 6G communication system), the authentication service function network element may still be an AUSF network element or may have another name. This is not limited in the present application.
[0091] The network exposure network element can expose some functions of the network to applications in a controlled manner. In a 5G communication system, the network exposure network element may be a network exposure function (NEF). In future communication systems (e.g., 6G communication systems), the network exposure network element may still be a NEF network element or may have another name. This is not limited in the present application.
[0092] The application function network element may provide service data of various applications to the control plane network element of the operator's communication network, or obtain network control information and data information from the control plane network element of the communication network. In a 5G communication system, the application function network element may be an application function (AF). In future communication systems (e.g., 6G communication systems), the application function network element may still be an AF network element or may have a different name. This is not limited in the present application.
[0093] A data network is primarily configured to provide data transmission services for terminal devices. A data network may be a private network, such as a local area network, or a public data network (PDN) network, such as the Internet, or a private network jointly deployed by operators, such as configured IP multimedia core network subsystem (IMS) services.
[0094] It should be understood that the aforementioned network elements or functions may be network elements in a hardware device, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network elements or functions may be implemented by one device, multiple devices, or one functional module in one device. This is not particularly limited in the embodiments of the present application.
[0095] For ease of explanation, an example in which the access management network element is an AMF network element and the unified data management network element is a UDM network element is used later for explanation in this application. Furthermore, the AMF network element is referred to as AMF for short, and the UDM network element is referred to as UDM for short. In other words, all AMFs described later in this application may be replaced with access management network elements, and all UDMs may be replaced with unified data management network elements.
[0096] The 3rd Generation Partnership Project (3GPP) defines the network function of minimization of service interruption (MINT) in Release 17. The network function of MINT mainly means that when a disaster condition occurs, users in a communication system can perform disaster roaming, so that the network services obtained by the users are not interrupted, i.e., the service interruption and failure caused by the disaster condition are reduced. The users are sometimes called disaster roaming users (disaster inbound roaming).
[0097] It should be understood that a disaster condition refers to a condition that is determined by a government to start or end. That is, the condition is controlled by the government. For example, a disaster condition includes natural disasters including earthquakes, tsunamis, fires, lightning strikes, and floods. In another example, a disaster condition includes man-made disasters including terrorist attacks and wars. A disaster condition may alternatively be a disaster scenario or a disaster. In this application, disaster is used for detailed description to facilitate the explanation.
[0098] It should be understood that disaster roaming refers to a special roaming policy applicable in a disaster. A disaster roaming user refers to a user who, due to a disaster, is unable to obtain service from a public land mobile network (PLMN) that normally serves the user, and who may register with another PLMN to continue to obtain such service, e.g., voice or data services.
[0099] The present application provides a disaster roaming method, apparatus and system, so that a terminal device can perform disaster roaming to obtain services when a network service fault occurs due to a disaster, thereby reducing the service interruption of the terminal device, minimizing the service interruption, and improving the user experience.
[0100] 2 is a schematic flow chart of a disaster roaming method 200 according to the present application. The method includes the following steps.
[0101] S201. A terminal device determines a first PLMN based on stored information on disaster roaming PLMNs, where the information on disaster roaming PLMNs includes identification (PLMN identity, PLMN ID) information of at least one PLMN that allows the terminal device to perform disaster roaming, and the first PLMN is a PLMN of the at least one PLMN.
[0102] Specifically, in this embodiment of the present application, the terminal device can select a PLMN of the at least one PLMN as a first PLMN based on the stored identification information of the at least one PLMN.
[0103] In this embodiment of the present application, the procedure of the terminal device selecting a PLMN is as follows: The terminal device obtains information about available PLMNs in the current location area based on the stored information about disaster roaming PLMNs, and selects the PLMN among the at least one PLMN as the first PLMN from the available PLMNs. For example, the terminal device obtains information about available PLMNs in the current location area through cell scanning, and then selects the PLMN with the highest priority among the at least one PLMN as the first PLMN from the available PLMNs.
[0104] In this embodiment of the present application, the information about the disaster roaming PLMN may further include a disaster roaming service time. Optionally, the disaster roaming service time may be stored by the terminal device based on a local configuration, or may be stored by the terminal device based on allocation information received from the network, or may be stored by the terminal device based on allocation information received from the network and a local configuration. When both the allocation information received from the network and the local configuration exist, which one is used as the disaster roaming service time is based on different implementations of the terminal device. This is not limited in the present invention. Furthermore, optionally, at least one type of disaster roaming service time is determined by the terminal device based on the allocation information received from the network. For example, there is only one type of disaster roaming service time, and specifically, for different disaster roaming PLMNs, the terminal device can obtain the same disaster roaming service time. In another example, for different disaster roaming PLMNs, the terminal device may obtain different disaster roaming service times.
[0105] S202. The terminal device sends a registration request message to a first PLMN, the registration request message includes disaster roaming indication information, and the disaster roaming indication information indicates that the terminal device requests to perform disaster roaming registration. In response, the first PLMN receives the registration request message.
[0106] Specifically, in this embodiment of the present application, the terminal device can send a registration request message to the access management network element of the first PLMN. The registration request message includes disaster roaming indication information, and the disaster roaming indication information indicates that the terminal device requests to perform disaster roaming registration. That is, the terminal device requests the first PLMN to provide a service, and in particular, requests a disaster roaming service.
[0107] Optionally, the disaster roaming indication information may be a registration type, or may be an information element, or may be a value field in an information element.
[0108] S203. The first PLMN sends a registration accept message to the terminal device, and correspondingly, the terminal device receives the registration accept message.
[0109] Therefore, according to the above-mentioned method for requesting disaster roaming service from a network by a terminal device, the terminal device performs disaster roaming when a network service fault is caused by a disaster, thus obtaining the service, reducing the service interruption of the terminal device, minimizing the service interruption, and improving the user experience.
[0110] Optionally, after the terminal device receives the registration acceptance message, the method 200 further includes the following steps S204 to S206.
[0111] S204. After the terminal device receives the registration accept message sent by the first PLMN, the terminal device performs disaster roaming in the first PLMN during a disaster roaming service time.
[0112] Specifically, in this implementation of the present application, when the terminal device receives a registration acceptance message sent by a first PLMN, indicating that the first PLMN agrees to provide disaster roaming service for the terminal device, the terminal device can perform disaster roaming through the first PLMN, and the first PLMN provides the service for the terminal device during a disaster roaming service time. When the disaster roaming service time is exceeded, the terminal device re-executes steps S201 to S203. Specifically, the terminal device re-executes PLMN selection to move away from the first PLMN.
[0113] It should be understood that after the terminal device receives the registration acceptance message sent by the first PLMN, during the disaster roaming service time, the terminal device may perform disaster roaming in the first PLMN in the following two specific implementations. Of course, the present application is not limited thereto.
[0114] Aspect 1: A terminal device starts a timer based on a disaster roaming service time to perform disaster roaming in a time period indicated by the disaster roaming service time, and when the time period is exceeded, the terminal device re-performs PLMN selection to leave the first PLMN.
[0115] Aspect 2: The terminal device records a time for performing disaster roaming, so as to perform disaster roaming in a time period indicated by a disaster roaming service time, when the time period is exceeded, the terminal device re-performs PLMN selection to leave the first PLMN.
[0116] S205. The terminal device notifies the user that the terminal device is performing disaster roaming.
[0117] Specifically, in this embodiment of the present application, the terminal device can output a notification, so that the user knows that disaster roaming is currently being performed.
[0118] S206. Before the terminal device determines the first PLMN, the terminal device learns that the PLMN currently providing service has stopped providing service due to a disaster.
[0119] Optionally, for the information about the disaster roaming PLMN stored by the terminal device, before the terminal device knows that the currently serving PLMN has stopped providing service due to the disaster, the terminal device stores the information about the disaster roaming PLMN by exchanging information with the second PLMN. In other words, the present application further provides a disaster roaming method 300. Figure 3 is a schematic flowchart of the method 300. It should be understood that the currently serving PLMN may be the same as or different from the second PLMN, which is not limited in the present application.
[0120] The method 300 includes the following steps.
[0121] S301. A terminal device sends a first message to a second PLMN, where the first message includes capability information for supporting disaster roaming by the terminal device. In response, the second PLMN receives the first message.
[0122] Specifically, in this embodiment of the present application, the first message is a registration request message, that is, the registration request message includes capability information for supporting disaster roaming by the terminal device.
[0123] It should be understood that the capability information supporting disaster roaming by a terminal device may also be capability information of a terminal device supporting service interruption minimization MINT, and the two capability information may be used interchangeably.
[0124] S302. The second PLMN sends a second message to the terminal device, where the second message includes information about the disaster roaming PLMN. In response, the terminal device receives the second message.
[0125] In this embodiment of the present application, the second message may be a registration accept message, or may be a registration reject message, or may be a downlink non-access stratum NAS transport message, or may be a configuration update command message.
[0126] Optionally, the second message further includes indication information indicating that the terminal device is allowed to perform disaster roaming (disaster roaming allowed), where the indication information indicating that the terminal device is allowed to perform disaster roaming indicates that the UE may perform disaster roaming when a disaster occurs in the PLMN currently providing service.
[0127] S303. The terminal device stores information about the disaster roaming PLMN based on the second message.
[0128] Optionally, the terminal device may store information about the disaster roaming PLMN in a universal subscriber identity module (USIM), or may store information about the disaster roaming PLMN in a non-volatile memory of the terminal device.
[0129] Therefore, in this application, the terminal device performs capability negotiation with the second PLMN, the second PLMN delivers information about the disaster roaming PLMN, and the terminal device stores the information about the disaster roaming PLMN. In this way, it can be ensured that disaster roaming is performed when a subsequent disaster occurs, which further reduces the service interruption of the terminal device, minimizes the service interruption, and improves the user experience.
[0130] Optionally, the method further includes S304 as follows:
[0131] If the second message is a registration rejection message, the terminal device stores the identification information of the second PLMN in the information about the disaster roaming PLMN.
[0132] Specifically, in this embodiment of the present application, if the second message is a registration rejection message, i.e., the second PLMN rejects the registration request of the terminal device, the terminal device marks the second PLMN as a disaster roaming PLMN and stores the identification information of the second PLMN in the information about the disaster roaming PLMN.
[0133] The identity information of the second PLMN is stored in the information about the disaster roaming PLMN, so that the terminal device maintains the original information about the disaster roaming PLMN of the terminal device. In this way, disaster roaming is ensured to be performed when a subsequent disaster occurs, further reducing the service interruption of the terminal device, minimizing the service interruption, and improving the user experience.
[0134] Optionally, the second PLMN may include a first network element and a second network element. In the following, the aforementioned method 300 will be described in detail with reference to the schematic flowcharts of the methods 400 and 500 shown in Figures 4 and 5, using the first network element and the second network element as an example.
[0135] Please note that some steps mentioned below are the same as those in the above-mentioned method 300. The relevant details are not described again here. For the specific process, please refer to the relevant steps in method 300.
[0136] S401. A terminal device sends a first message to a first network element, and the first message includes capability information for supporting disaster roaming by the terminal device. Correspondingly, the first network element receives the first message. For the specific process of this step, please refer to S301 in method 300.
[0137] S402. The first network element obtains information about a disaster roaming PLMN that provides a disaster roaming service for the terminal device based on the capability information supporting disaster roaming.
[0138] For example, in a specific implementation in which the first network element obtains information about the disaster roaming PLMN, the following manner 1 or 2 may be used for implementation. Of course, the specific implementation is not limited to these manners.
[0139] Aspect 1: A first network element determines information about a disaster roaming PLMN based on a local configuration.
[0140] In an optional embodiment of aspect 1, before the first network element determines information about the disaster roaming PLMN based on the local configuration, the first network element may determine to provide a disaster roaming service for the terminal device based on the local configuration or based on indication information sent by the second network element indicating that disaster roaming needs to be performed, where the indication information indicating that disaster roaming needs to be performed instructs the first network element to perform the disaster roaming service.
[0141] Aspect 2: A second network element transmits information about a disaster roaming PLMN, and a first network element receives the information about the disaster roaming PLMN transmitted by the second network element.
[0142] In an optional embodiment of aspect 2, for a process in which a first network element receives information about a disaster roaming PLMN sent by a second network element, the first network element receives indication information sent by the second network element indicating that disaster roaming needs to be performed, and the indication information indicating that disaster roaming needs to be performed instructs the first network element to perform a disaster roaming service. Specifically, the indication information indicating that disaster roaming needs to be performed and the information about the disaster roaming PLMN may be sent simultaneously, or the indication information indicating that disaster roaming needs to be performed may be sent first, and then the information about the disaster roaming PLMN is sent.
[0143] Regarding the above aspect 2, optionally, before the first network element receives instruction information indicating that disaster roaming needs to be performed and sent by the second network element, or information regarding the disaster roaming PLMN sent by the second network element, the first network element sends capability information supporting disaster roaming by the terminal device to the second network element.
[0144] For specific implementations of aspect 2, please refer to the following detailed description of method 500.
[0145] S403. The first network element sends a second message to the terminal device. The second message includes information about the disaster roaming PLMN. The terminal device receives the second message. Correspondingly, the terminal device receives the second message. For a specific process of this step, please refer to S302 in the method 300.
[0146] Optionally, the second message further includes indication information indicating that the terminal device is allowed to perform disaster roaming.
[0147] In this embodiment of the present application, there are three possible cases for the content of the aforementioned information regarding the disaster roaming PLMN.
[0148] Case 1: The information about disaster roaming PLMNs includes identification information of at least one PLMN that allows the terminal device to perform disaster roaming.
[0149] Case 2: The information about the disaster roaming PLMN includes a disaster roaming service time.
[0150] Case 3: The information about the disaster roaming PLMN includes identification information of at least one PLMN that allows the terminal device to perform disaster roaming, and a disaster roaming service time.
[0151] S404. The terminal device stores information about the disaster roaming PLMN according to the second message. For a specific process of this step, see S303 in the method 300.
[0152] Therefore, in this application, the terminal device performs capability negotiation with the first network element, the first network element delivers information about the disaster roaming PLMN, and the terminal device stores the information about the disaster roaming PLMN. In this way, it can be ensured that disaster roaming is performed when a subsequent disaster occurs, which further reduces the service interruption of the terminal device, minimizes the service interruption, and improves the user experience.
[0153] 5 is a schematic flow chart of a disaster roaming method 500 according to the present application. The method 500 includes the following steps.
[0154] S501. A first network element sends capability information for supporting disaster roaming by a terminal device to a second network element. In response, the second network element receives capability information for supporting disaster roaming by the terminal device.
[0155] S502. The second network element determines, based on capability information supporting disaster roaming by the terminal device, that the terminal device is allowed to obtain disaster roaming services.
[0156] In this embodiment of the present application, the second network element determines that the terminal device is allowed to obtain disaster roaming services based on the capability information and local configuration supporting disaster roaming by the terminal device.
[0157] S503. The second network element sends information about the disaster roaming PLMN of the terminal device to the first network element. In response, the first network element receives information about the disaster roaming PLMN of the terminal device.
[0158] Specifically, in this embodiment of the present application, after determining the information about the disaster roaming PLMN of the terminal device based on the local configuration, the second network element sends the information about the disaster roaming PLMN to the first network element.
[0159] Optionally, the second network element may further send indication information indicating that disaster roaming needs to be performed to the first network element, where the indication information indicating that disaster roaming needs to be performed instructs the first network element to perform a disaster roaming service.
[0160] In this embodiment of the present application, there are also three possible cases for the content of the above information about the disaster roaming PLMN.
[0161] Case 1: The information about disaster roaming PLMNs includes identification information of at least one PLMN that allows the terminal device to perform disaster roaming.
[0162] Case 2: The information about the disaster roaming PLMN includes a disaster roaming service time.
[0163] Case 3: The information about the disaster roaming PLMN includes identification information of at least one PLMN that allows the terminal device to perform disaster roaming and a disaster roaming service time.
[0164] With respect to the "local configuration" referred to in the above methods 400 and 500, it should be understood that the local configuration may be an operator policy, or may be a network configuration, or may be an operator policy and a network configuration.
[0165] It should be further understood that the terminal device performing the aforementioned method may alternatively be a chip or chip system disposed in the terminal device. Alternatively, the first network element performing the aforementioned method may be a chip or chip system disposed in the first network element. Alternatively, the second network element performing the aforementioned method may be a chip or chip system disposed in the second network element. This is not limited in the embodiment of the present application. The chip system may include an input interface, an output interface, at least one processor, and a memory. The input interface, the output interface, the processor, and the memory communicate with each other through an internal connection path. The processor is configured to execute the code in the memory.
[0166] Therefore, in this application, the first network element performs capability negotiation with the second network element by reporting capability information of the terminal device, and the second network element distributes information about the disaster roaming PLMN, so that the terminal device stores the information about the disaster roaming PLMN. In this way, it can be ensured that disaster roaming is performed when a subsequent disaster occurs, which further reduces the service interruption of the terminal device, minimizes the service interruption, and improves the user experience.
[0167] Optionally, for the terminal device, the first network element, and the second network element in the aforementioned method, the terminal device may be a UE, the first network element may be an AMF, and the second network element may be a UDM.
[0168] In order to facilitate understanding of the disaster roaming methods 300, 400, and 500 provided in the present application, by way of example and not limitation, the following describes in detail several implementations of the aforementioned methods with reference to the following methods 600, 700, 800, 900, and 1000 using an example in which the terminal device is a UE, the first network element is an AMF, and the second network element is a UDM.
[0169] Please note that some steps mentioned below are the same as those in the above-mentioned methods 300, 400 and 500. The relevant details are not described again here. For the specific process, please refer to the relevant steps in the above-mentioned methods.
[0170] FIG. 6 is a schematic flow chart of a particular exemplary method 600 of a disaster roaming method in accordance with the present application.
[0171] S601. The UE sends a first message to the AMF, and the first message includes capability information for supporting disaster roaming by the UE. Correspondingly, the AMF receives the first message. For a specific process of this step, please refer to S301 in the method 300.
[0172] S602. The AMF determines, based on a local configuration, to provide disaster roaming service for the UE.
[0173] S603. The AMF determines information about the disaster roaming PLMN based on the local configuration.
[0174] S604. The AMF sends a second message to the UE, where the second message includes information about the disaster roaming PLMN. Correspondingly, the UE receives the second message. For a specific process of this step, please refer to S302 in the method 300.
[0175] S605. The UE stores information about the disaster roaming PLMN according to the second message. For a specific process of this step, see S303 in the method 300.
[0176] FIG. 7 is a schematic flow chart of a particular exemplary method 700 of a disaster roaming method in accordance with the present application.
[0177] S701. The UE sends a first message to the AMF, and the first message includes capability information for supporting disaster roaming by the UE. Correspondingly, the AMF receives the first message. For a specific process of this step, please refer to S301 in the method 300.
[0178] S702. The AMF sends capability information supporting disaster roaming by the UE to the UDM. In response, the UDM receives capability information supporting disaster roaming by the UE.
[0179] S703. The UDM determines that the UE is allowed to obtain disaster roaming services based on the capability information supporting disaster roaming by the UE and a local configuration.
[0180] S704. The UDM determines information about the disaster roaming PLMN of the UE based on the local configuration.
[0181] S705. The UDM sends information about the disaster roaming PLMN of the UE to the AMF. In response, the AMF receives information about the disaster roaming PLMN of the UE.
[0182] Specifically, in one implementation, the UDM encapsulates information about the disaster roaming PLMN in a container and transparently transmits the information to the UE through the AMF. The container is transparent and invisible to the AMF.
[0183] S706. The AMF sends a second message to the UE. The second message includes information about the disaster roaming PLMN. Correspondingly, the UE receives the second message. For a specific process of this step, see S302 in the method 300.
[0184] S707. The UE stores information about the disaster roaming PLMN according to the second message. For a specific process of this step, see S303 in the method 300.
[0185] FIG. 8 is a schematic flow chart of a particular exemplary method 800 of a disaster roaming method in accordance with the present application.
[0186] S801. The UE sends a first message to the AMF. The first message includes capability information for supporting disaster roaming by the UE. Correspondingly, the AMF receives the first message. For a specific process of this step, see S301 in the method 300.
[0187] S802. The AMF sends capability information for supporting disaster roaming by the UE to the UDM. In response, the UDM receives capability information for supporting disaster roaming by the UE.
[0188] S803. The UDM determines that the UE is allowed to obtain disaster roaming services based on the capability information supporting disaster roaming by the UE and a local configuration.
[0189] S804. The UDM sends indication information indicating that disaster roaming needs to be performed to the AMF. The indication information indicating that disaster roaming needs to be performed instructs the AMF to perform a disaster roaming service. In response, the AMF receives the indication information indicating that disaster roaming needs to be performed.
[0190] S805. The AMF determines information about the disaster roaming PLMN based on the local configuration.
[0191] S806. The AMF sends a second message to the UE. The second message includes information about the disaster roaming PLMN. Correspondingly, the UE receives the second message. For a specific process of this step, see S302 in the method 300.
[0192] S807. The UE stores information about the disaster roaming PLMN according to the second message. For a specific process of this step, see S303 in the method 300.
[0193] FIG. 9 is a schematic flow chart of a particular exemplary method 900 of a disaster roaming method in accordance with the present application.
[0194] S901. The UE sends a first message to the AMF, and the first message includes capability information for supporting disaster roaming by the UE. Correspondingly, the AMF receives the first message. For a specific process of this step, please refer to S301 in the method 300.
[0195] S902. The AMF sends capability information for supporting disaster roaming by the UE to the UDM. In response, the UDM receives capability information for supporting disaster roaming by the UE.
[0196] S903. The UDM determines that the UE is allowed to obtain disaster roaming services based on the capability information supporting disaster roaming by the UE and a local configuration.
[0197] S904. The UDM sends indication information indicating that disaster roaming needs to be performed to the AMF. The indication information indicating that disaster roaming needs to be performed instructs the AMF to perform a disaster roaming service. In response, the AMF receives the indication information indicating that disaster roaming needs to be performed.
[0198] S905. The AMF sends a second message to the UE. The second message includes indication information indicating that the terminal device is allowed to perform disaster roaming. Correspondingly, the UE receives the second message. For a specific process of this step, please refer to S302 in the method 300.
[0199] S906. The UDM determines information about the disaster roaming PLMN of the UE based on the local configuration.
[0200] S907. The UDM sends a third message to the AMF. The third message includes information about the disaster roaming PLMN. In response, the AMF receives the third message.
[0201] In this embodiment of the present application, step S907 may be a subscriber data management notification service operation provided by the UDM.
[0202] Specifically, if the second message in S905 is a registration accept message, i.e., the UE is successfully registered, step S907 is a UDM UE parameter update procedure initiated by the UDM. The UDM encapsulates information about the disaster roaming PLMN in a container in the third message and transparently transmits the information to the UE through the AMF. The container is transparent and invisible to the AMF.
[0203] S908. The AMF sends a fourth message, the fourth message including information about the disaster roaming PLMN. In response, the UE receives the fourth message.
[0204] Specifically, in this embodiment of the present application, the fourth message includes the container received from the third message in step S907, and the container includes information about the disaster roaming PLMN.
[0205] In this embodiment of the present application, the fourth message may be a downlink non-access stratum NAS transport message or may be a configuration update command message.
[0206] S909. The UE stores information about the disaster roaming PLMN based on the fourth message.
[0207] Specifically, in this embodiment of the present application, the UE includes information about the disaster roaming PLMN according to the information about the disaster roaming PLMN included in the fourth message.
[0208] For a specific process of this step, see S303 in the method 300. The "second message" may be replaced with the "fourth message."
[0209] FIG. 10 is a schematic flow chart of a particular exemplary method 1000 of a disaster roaming method according to the present application.
[0210] S1001. The UE sends a first message to the AMF. The first message includes capability information for supporting disaster roaming by the UE. In response, the AMF receives the first message. For a specific process of this step, see S301 in the method 300.
[0211] S1002. The AMF sends capability information for supporting disaster roaming by the UE to the UDM. In response, the UDM receives capability information for supporting disaster roaming by the UE.
[0212] S1003. The UDM determines that the UE is allowed to obtain disaster roaming services based on the capability information supporting disaster roaming by the UE and a local configuration.
[0213] S1004. The UDM sends indication information indicating that disaster roaming needs to be performed and a disaster roaming service time to the AMF. The indication information indicating that disaster roaming needs to be performed instructs the AMF to perform a disaster roaming service. In response, the AMF receives indication information indicating that disaster roaming needs to be performed and a disaster roaming service time.
[0214] S1005. The AMF sends a second message to the UE, the second message including indication information indicating that the terminal device is allowed to perform disaster roaming and a disaster roaming service time. In response, the AMF receives the second message.
[0215] Specifically, the second message is a registration rejection message. Specifically, in this case, the network rejects the registration request of the UE.
[0216] For a specific process of this step, see S302 in method 300.
[0217] S1006. The UE stores information about the disaster roaming PLMN based on the second message.
[0218] Specifically, after the network rejects the UE's registration request, the UE may mark the network as a disaster roaming PLMN and store the network's identity information and disaster roaming service time.
[0219] For a specific process of this step, please refer to S303 in method 300.
[0220] In addition to the above-mentioned method, the present application further provides another disaster roaming method 1100.
[0221] 11 is a schematic flow chart of another disaster roaming method 1100 according to the present application. The method includes the following steps.
[0222] S1101. A third PLMN transmits system information to a terminal device. The system information includes indication information indicating that disaster roaming is allowed. In response, the terminal device receives the system information.
[0223] It should be understood that the third PLMN is a PLMN that can provide disaster roaming services for the terminal device.
[0224] It should be understood that in this embodiment of the present application, after the PLMN serving the terminal device before the disaster occurs stops providing services due to the disaster due to the impact of the disaster, the PLMN serving the terminal device before the disaster occurs transmits the identity of the PLMN and information about the location area affected by the disaster to the available disaster roaming PLMN. Thus, the available disaster roaming PLMN obtains the identity of the PLMN that stops providing services due to the disaster. It should be further understood that there may be an existing standardized interface or a private interface between the PLMN serving the terminal device before the disaster occurs and the available disaster roaming PLMN. Thus, messages may be exchanged between the two PLMNs.
[0225] Specifically, in this embodiment of the present application, the third PLMN broadcasts system information. The system information includes identification information of the PLMN that has stopped providing services due to a disaster, and indication information indicating that disaster roaming is allowed. That is, the terminal device can know whether there is a PLMN that provides services for the terminal device among the PLMNs that have stopped providing services due to a disaster. In addition, the indication information indicating that disaster roaming is allowed is used by the terminal device to know that the third PLMN can provide disaster roaming services for the terminal device. Therefore, the terminal device can perform the following operations (S 11 02).
[0226] S1102. The terminal device sends a registration request message to a third PLMN based on system information, and the registration request message includes capability information and disaster roaming indication information for supporting disaster roaming by the terminal device. In response, the third PLMN receives the registration request message.
[0227] It should be understood that the capability information of the terminal device supporting disaster roaming may be capability information of the terminal device supporting minimization of service interruption MINT. It should be further understood that the disaster roaming indication information indicates that the terminal device requests to perform disaster roaming registration.
[0228] Specifically, in this embodiment of the present application, the terminal device can perform a cell scan, select the cell with the strongest signal to physically camp on, and read system information broadcasted in the selected cell to learn that a third PLMN is available in the currently selected cell.
[0229] S1103. The third PLMN sends a registration acceptance message to the terminal device, where the registration acceptance message includes a disaster roaming service time provided by the third PLMN. In response, the terminal device receives the registration acceptance message.
[0230] Therefore, after a disaster occurs, the terminal device receives and reads the system information broadcast by the third PLMN, and then selects the third PLMN to perform disaster roaming. In this way, service can be obtained, service interruption of the terminal device can be reduced, service interruption of the terminal device can be minimized, and user experience can be improved.
[0231] Optionally, the method further includes steps S1104 to S1107.
[0232] S1104. The terminal device performs disaster roaming in the third PLMN during a disaster roaming service time.
[0233] After the terminal device receives the registration accept message, it should be understood that since the registration accept message includes a disaster roaming service time, the disaster roaming service time indicates that the third PLMN may be a PLMN that can provide disaster roaming service for the terminal device.
[0234] S1105. The terminal device notifies the user that the terminal device is performing disaster roaming.
[0235] Specifically, in this embodiment of the present application, the terminal device can output a notification, so that the user knows that disaster roaming is currently being performed.
[0236] S1106. Before the terminal device receives system information transmitted by the third PLMN, the terminal device learns that a fourth PLMN has stopped providing services due to a disaster, where the fourth PLMN is a PLMN that provides services to the terminal device before the disaster occurs.
[0237] S1107. After the terminal device learns that the fourth PLMN has stopped providing services due to a disaster, the terminal device obtains information about available PLMNs in a current location area, and selects a PLMN within at least one PLMN from the available PLMNs as a third PLMN.
[0238] Specifically, in this embodiment of the present application, the terminal device can perform a cell scan, select the cell with the strongest signal to physically camp on, and read system information broadcasted in the selected cell to learn that a third PLMN is available in the currently selected cell.
[0239] Optionally, for the system information, the system information may include an identity of the fourth PLMN.
[0240] Optionally, for the above method 1100, it should be understood that the third PLMN may further be an access network device, such as a RAN, within the third PLMN, and the terminal device may be a UE.
[0241] It should be further understood that the terminal device executing the aforementioned method may alternatively be a chip or chip system disposed in the terminal device. The third PLMN executing the aforementioned method may alternatively be a chip or chip system disposed in the third PLMN. This is not limited in the embodiment of the present application. The chip system may include an input interface, an output interface, at least one processor, and a memory. The input interface, the output interface, the processor, and the memory communicate with each other through an internal connection path. The processor is configured to execute the code in the memory.
[0242] 12 and 13 are schematic diagrams of possible disaster roaming device structures according to the embodiments of the present application. These devices can implement the functions of the terminal device or any network element in the above-mentioned method embodiments, and thus can also achieve the beneficial effects of the above-mentioned method embodiments. In the embodiments of the present application, the device can be a terminal device, a first network element, a second network element, or a module (such as a chip) used in the terminal device, the first network element, or the second network element.
[0243] 12 is a schematic diagram of the structure of a disaster roaming device 1200 according to an embodiment of the present application. The device 1200 may include a transceiver unit 1201 and a processing unit 1202.
[0244] When the apparatus 1200 is configured to implement the functions of the terminal device in the method embodiment of FIG. 2 or FIG. 3, the processing unit is configured to determine a first public land mobile network PLMN based on stored information on disaster roaming PLMNs, where the information on disaster roaming PLMNs includes identification information of at least one PLMN that allows the terminal device to perform disaster roaming, and the first PLMN is a PLMN of the at least one PLMN. The transceiver unit is configured to send a registration request message to the first PLMN, the registration request message includes disaster roaming indication information, and the disaster roaming indication information indicates that the terminal device requests to perform disaster roaming registration. The transceiver unit is further configured to receive a registration accept message sent by the first PLMN.
[0245] When the apparatus 1200 is configured to implement the functionality of the first network element in the method embodiment of FIG. 4, the transceiver unit is configured to receive a first message sent by a terminal device, where the first message includes capability information for supporting disaster roaming by the terminal device. The processing unit is configured to obtain information about a disaster roaming PLMN providing disaster roaming service for the terminal device based on the capability information for supporting disaster roaming. The transceiver unit is further configured to send a second message to the terminal device, where the second message includes information about the disaster roaming PLMN.
[0246] When the apparatus 1200 is configured to implement the functionality of the second network element in the method embodiment of FIG. 5, the transceiver unit is configured to receive capability information of the terminal device supporting disaster roaming sent by the first network element. The processing unit is configured to determine that the terminal device is allowed to obtain disaster roaming services based on the capability information supporting disaster roaming by the terminal device. The transceiver unit is further configured to send information regarding the disaster roaming PLMN of the terminal device to the first network element.
[0247] When the apparatus 1200 is configured to implement the functions of the terminal device in the method embodiment of FIG. 11, the transceiver unit is configured to receive system information sent by the third PLMN, the system information including indication information indicating that disaster roaming is allowed. The transceiver unit is further configured to send a registration request message to the third PLMN based on the system information, the registration request message including capability information supporting disaster roaming by the terminal device and disaster roaming indication information. The transceiver unit is further configured to receive a registration accept message sent by the third PLMN, the registration accept message including a disaster roaming service time provided by the third PLMN.
[0248] For more detailed descriptions of the transceiver unit 1201 and the processing unit 1202, please refer to the relevant descriptions in the above method embodiments, and the details will not be described again here.
[0249] 13 is a schematic block diagram of an apparatus 1300 to which an embodiment of the present application is applied. Any network element in any one of the methods 200 to 1100 may be implemented by the apparatus shown in FIG.
[0250] It should be understood that the apparatus 1300 may be a physical device, a component (e.g., an integrated circuit or chip) within a physical device, or a functional module within a physical device.
[0251] As shown in FIG. 13, the device 1300 includes one or more processors 1301. The processor 1301 can store executable instructions used to execute the method in the embodiment of the present application. Optionally, the processor 1301 can call an interface to implement the receiving function and the transmitting function. The interface can be a logical interface or a physical interface. This is not limited. For example, the interface can be a transceiver circuit or an interface circuit. The transceiver circuit and the interface circuit configured to implement the receiving function and the transmitting function may be separate or integrated. The transceiver circuit or the interface circuit may be configured to read or write code / data, or the transceiver circuit or the interface circuit may be configured to transmit or forward a signal.
[0252] Optionally, the interface may be implemented by a transceiver. Optionally, the apparatus 1300 may further include a transceiver 1303. The transceiver 1303 may be referred to as a transceiver unit, a transceiver device, a transceiver circuit, a transceiver, etc., and is configured to implement a receiving function and a transmitting function.
[0253] Optionally, the device 1300 may further include a memory 1302. The specific location of the memory 1302 is not particularly limited in this embodiment of the present application. The memory may be integrated with the processor or may be independent of the processor. If the device 1300 does not include a memory, the device 1300 may have a processing function and the memory may be located in another location (e.g., in a cloud system).
[0254] The processor 1301, memory 1302 and transceiver 1303 communicate with each other through interconnect paths to transmit control and / or data signals.
[0255] Although not shown, it may be understood that the device 1300 may further include other devices, such as an input device, an output device, or a battery.
[0256] Optionally, in some embodiments, the memory 1302 can store execution instructions used to execute the method in the embodiments of the present application. The processor 1301 can execute the instructions stored in the memory 1302 to complete the steps to be executed in the following methods in combination with other hardware (e.g., the transceiver 1303). For specific operation processes and beneficial effects, please refer to the description in the following method embodiments.
[0257] The methods disclosed in the embodiments of the present application may be applied to or implemented by the processor 1301. The processor 1301 may be an integrated circuit chip and has signal processing capabilities. In the implementation process, the steps in the aforementioned methods may be implemented by hardware integrated logic circuits in the processor or by instructions in the form of software. The aforementioned processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc. The steps of the methods disclosed with reference to the embodiments of the present application may be directly executed and achieved through a hardware decoding processor, or may be executed and achieved by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium mature in the art, such as a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in the memory, and the processor reads the instructions in the memory and completes the steps of the aforementioned method in combination with the hardware of the processor.
[0258] It may be understood that the memory 1302 may be volatile or non-volatile memory, or may include both volatile and 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 a random access memory RAM, which acts as an external cache. Throughout the exemplary but non-limiting description, many forms of RAM may be used, such as static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM), and direct rambus random access memory (direct rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein includes, but is not limited to, these and any other suitable types of memory.
[0259] In addition, in this application, the device 1200 is presented in the form of a functional module. A "module" in this specification may be an application specific integrated circuit ASIC, a circuit, a processor and memory executing one or more software or firmware programs, an integrated logic circuit, and / or another device capable of providing the aforementioned functionality. In a simple embodiment, a person skilled in the art may understand that the device 1200 may be in the form shown in FIG. 12. Processing unit 1202 may be implemented by the processor 1301 shown in FIG. 13. Optionally, when the computing device shown in FIG. 13 includes the memory 1302, the processing unit 1202 may be implemented by the processor 1301 and the memory 1302. The transceiver unit 1201 may be implemented by the transceiver 1303 shown in FIG. 13. The transceiver 1303 includes a receiving function and a transmitting function. Specifically, the processor is implemented by executing a computer program stored in the memory. Optionally, when the device 1200 is a chip, the functions and / or implementation processes of the transceiver unit 1201 may alternatively be implemented by pins, circuits, etc. Optionally, the memory may be a storage unit within the chip, for example, a register or cache. Alternatively, the storage unit may be a storage unit that is within the computing device and off-chip, such as the memory 1302 shown in FIG. 13. Alternatively, the storage unit may be a storage unit that is not within the computing device but is deployed in another system or device. Those skilled in the art may recognize that the examples, units and algorithm steps described in the embodiments disclosed herein may be implemented by electronic hardware or by a combination of computer software and electronic hardware. Whether a function is performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions of each specific application, but such implementation should not be considered to go beyond the scope of the present application.
[0260] Various aspects or features of the present application may be implemented as a method, apparatus, or article using standard programming and / or engineering techniques. The term "product" as used herein encompasses a computer program accessible from any computer-readable component, carrier, or medium. For example, computer-readable media may include, but are not limited to, magnetic storage components (e.g., hard disks, floppy disks, or magnetic tapes), optical disks (e.g., compact discs (CDs) or digital versatile discs (DVDs)), smart cards, and flash memory components (e.g., erasable programmable read-only memory (EPROM), cards, sticks, or key drives). In addition, various storage media described herein may represent one or more devices and / or other machine-readable media configured to store information. The term "machine-readable medium" may include, but is not limited to, wireless channels, as well as various other media capable of storing, containing, and / or carrying instructions and / or data.
[0261] The present application further provides a computer readable medium storing a computer program product, which, when executed by a computer, implements the functionality of any one of the aforementioned method embodiments.
[0262] The present application further provides a computer program product. When the computer program product is executed by a computer, the functions of any one of the above-mentioned method embodiments are implemented. All or some of the above-mentioned embodiments may be implemented by software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or some of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (e.g., coaxial cable, fiber optics, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio waves, or microwave) manner. A computer-readable storage medium may be any available medium accessible by a computer, or a data storage device integrating one or more available media, such as a server or a data center. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium (e.g., a high-density digital video disc (DVD)), a semiconductor medium (e.g., a solid state disk (SSD)), etc.
[0263] It should be understood that an "embodiment" referred to throughout this specification means that a particular feature, structure, or characteristic associated with that embodiment is included in at least one embodiment of the present application. Thus, the embodiments throughout this specification do not necessarily refer to the same embodiment. In addition, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that the sequence numbers of the processes described above do not imply an execution sequence in various embodiments of the present application. The execution sequence of the processes should be determined based on the functions and internal logic of the processes, and should not be interpreted as any limitation on the implementation process of the embodiments of the present application.
[0264] In addition, it should be understood that in this application, the terms "when..." and "if..." mean that the UE or base station may perform the corresponding processing in an objective case, but are not intended to limit the time, do not require the UE or base station to perform a decision action during implementation, and do not imply other limitations.
[0265] In addition, the terms "system" and "network" may be used interchangeably herein. The term "and / or" in this specification is merely an association relationship to describe associated objects, and indicates that three relationships may exist. For example, A and / or B may indicate three cases: only A exists, both A and B exist, and only B exists.
[0266] As used herein, the term "at least one of" refers to all or any combination of the listed items. For example, "at least one of A, B, and C" can represent six cases: only A is present, only B is present, only C is present, both A and B are present, both B and C are present, and both A, B, and C are present.
[0267] In this application, unless otherwise specified, "at least one" means one or more, and "multiple" means two or more.
[0268] In the embodiments of the present application, it should be understood that "B corresponding to A" indicates that B is associated with A, and B may be determined based on A. However, it should be further understood that determining B based on A does not mean that B is determined based only on A. B may alternatively be determined based on A and / or other information.
[0269] Those skilled in the art may recognize that the units and algorithm steps may be implemented by electronic hardware or a combination of computer software and electronic hardware in combination with the examples described in the embodiments disclosed herein. Whether a function is performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions of each specific application, but such implementations should not be considered to go beyond the scope of the present application.
[0270] For the sake of convenience, the detailed operation processes of the above-mentioned systems, devices, and units can be clearly understood by those skilled in the art by referring to the corresponding processes in the above-mentioned method embodiments, and the details will not be described again here.
[0271] In some embodiments provided in the present application, it should be understood that the disclosed system, device, and method may be implemented in other manners. For example, the described device embodiment is merely an example. For example, the division into units is merely a logical division of functions, and may be other divisions in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. In addition, the shown or discussed mutual couplings or direct couplings or communication connections may be implemented by some interfaces. Indirect couplings or communication connections between devices or units may be implemented electronically, mechanically, or in other ways.
[0272] The units described as separate parts may or may not be physically separate, and the parts shown as units may or may not be physical units, and may be located in one location or distributed over multiple network units. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.
[0273] In addition, the functional units in the embodiments of the present application may be integrated into one processing unit, or each of the units may exist physically alone, or two or more units may be integrated into one unit.
[0274] When a function is implemented in the form of a software functional unit and sold or used as an independent product, the function may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may essentially, or a part that contributes to the prior art, or a part of the technical solution may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes some instructions for instructing a computer device (which may be a personal computer, a server, a network device, etc.) to execute all or part of the steps of the method described in the embodiments of the present application. The aforementioned storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
[0275] The above description is merely a specific implementation of the present application, and is not intended to limit the scope of protection of the present application. Any variations or replacements that are easily conceived by those skilled in the art within the technical scope disclosed in this application will fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be subject to the scope of protection of the claims.
Claims
1. 1. A disaster roaming method executed in a terminal device, comprising: sending a first message to a second PLMN (Public Land Mobile Network), the first message including capability information for supporting disaster roaming by the terminal device; receiving a second message sent by the second PLMN, the second message including information about a disaster roaming PLMN, the information about the disaster roaming PLMN including identification information of at least one PLMN that allows the terminal device to perform disaster roaming; storing information about the disaster roaming PLMN based on the second message; learning that the PLMN currently providing service has ceased providing service due to the disaster; determining a first PLMN based on stored information about the disaster roaming PLMN, the first PLMN being a PLMN among the at least one PLMN; sending a registration request message to the first PLMN, the registration request message including disaster roaming indication information, the disaster roaming indication information indicating that the terminal device requests to perform disaster roaming registration; receiving a registration accept message sent by the first PLMN; method.
2. The method of claim 1 , wherein the information about the disaster roaming PLMN further includes disaster roaming service hours.
3. After receiving the registration accept message sent by the first PLMN, the method includes: performing disaster roaming in the first PLMN during the disaster roaming service time; The method according to claim 1 or 2.
4. The method comprises: further comprising notifying a user that the terminal device is performing disaster roaming.
4. The method according to any one of claims 1 to 3.
5. Determining the first PLMN includes:
5. The method according to claim 1, further comprising: obtaining information about available PLMNs in a current location area; and selecting, from the available PLMNs, the PLMN of the at least one PLMN as the first PLMN.
6. The method of claim 1 , wherein the first message is a registration request message.
7. The second message comprises: one of a Registration Accept message, a Registration Reject message, a Downlink Non-Access Stratum NAS Transport message, or a Configuration Update Command message; The method of claim 1.
8. The method according to claim 1 , wherein the second message further includes indication information indicating that the terminal device is allowed to perform disaster roaming.
9. If the second message is a registration rejection message, the method comprises: storing an identification of the second PLMN in information about the disaster roaming PLMN; 9. The method according to any one of claims 1 to 8.
10. 1. A disaster roaming method performed in a first network element, comprising: receiving a first message sent by a terminal device, the first message including capability information for supporting disaster roaming by the terminal device; obtaining information about a disaster roaming PLMN that provides disaster roaming services for the terminal device based on the capability information supporting disaster roaming; sending a second message to the terminal device, the second message including information about the disaster roaming PLMN; method.
11. The method of claim 10 , wherein the first message is a registration request message.
12. The second message comprises: one of a Registration Accept message, a Registration Reject message, a Downlink Non-Access Stratum NAS Transport message, or a Configuration Update Command message; The method of claim 10.
13. The method according to claim 11 , wherein the second message further includes indication information indicating that the terminal device is allowed to perform disaster roaming.
14. Obtaining information about a disaster roaming PLMN that provides a disaster roaming service for the terminal device includes: determining information about the disaster roaming PLMN based on a local configuration; The method of claim 11.
15. Before determining information about the disaster roaming PLMN based on a local configuration, the method includes: determining to provide the disaster roaming service for the terminal device based on the local configuration; 15. The method of claim 14.
16. Before determining information about the disaster roaming PLMN based on a local configuration, the method includes: receiving instruction information indicating that disaster roaming needs to be performed and sent by a second network element, the instruction information indicating that disaster roaming needs to be performed instructing the first network element to perform a disaster roaming service; 15. The method of claim 14.
17. Obtaining information about a disaster roaming PLMN that provides a disaster roaming service for the terminal device includes: receiving information about the disaster roaming PLMN sent by a second network element; The method of claim 10.
18. Receiving information about the disaster roaming PLMN sent by a second network element includes: receiving instruction information indicating that disaster roaming needs to be performed and sent by the second network element, wherein the instruction information indicating that disaster roaming needs to be performed instructs the first network element to perform the disaster roaming service; 18. The method of claim 17.
19. Before receiving indication information indicating that disaster roaming needs to be performed and sent by a second network element, or receiving information about the disaster roaming PLMN sent by a second network element, the method includes: and further comprising transmitting, by the terminal device, the capability information supporting disaster roaming to the second network element.
18. The method of claim 16 or 17.
20. The information about the disaster roaming PLMN is: Identification of at least one PLMN that allows the terminal device to perform disaster roaming; or Disaster Roaming Service Hours; or Including identification information of at least one PLMN that allows the terminal device to perform disaster roaming and a disaster roaming service time; 20. The method of any one of claims 10 to 19.
21. 1. A disaster roaming method performed in a second network element, comprising: receiving, by the terminal device, capability information supporting disaster roaming, the capability information being sent by the first network element; determining, based on the capability information supporting disaster roaming by the terminal device, that the terminal device is allowed to obtain disaster roaming services; and transmitting information about the disaster roaming PLMN of the terminal device to the first network element. method.
22. 22. The method of claim 21, further comprising: sending instruction information indicating that disaster roaming needs to be performed to the first network element, wherein the instruction information indicating that disaster roaming needs to be performed instructs the first network element to perform the disaster roaming service.
23. Determining that the terminal device is allowed to obtain disaster roaming service includes: determining that the terminal device is allowed to obtain the disaster roaming service based on capability information and a local configuration supporting disaster roaming by the terminal device; 23. The method of claim 21 or 22.
24. Before transmitting information about the disaster roaming PLMN of the terminal device to the first network element, the method includes: and determining information about the disaster roaming PLMN of the terminal device based on a local configuration.
24. The method of any one of claims 21 to 23.
25. The information about the disaster roaming PLMN is: Identification of at least one PLMN that allows the terminal device to perform disaster roaming; or Disaster Roaming Service Hours; or Including identification information of at least one PLMN that allows the terminal device to perform disaster roaming and a disaster roaming service time; 25. The method of any one of claims 21 to 24.
26. 1. A disaster roaming method executed in a terminal device, comprising: receiving system information broadcasted by a third PLMN, the system information including indication information indicating that disaster roaming is allowed; sending a registration request message to the third PLMN based on the system information, the registration request message including capability information for supporting disaster roaming by the terminal device and disaster roaming indication information; receiving a registration accept message sent by the third PLMN, the registration accept message including a disaster roaming service time provided by the third PLMN; method.
27. The method comprises: performing disaster roaming in the third PLMN during the disaster roaming service time; 27. The method of claim 26.
28. The method comprises: further comprising notifying a user that the terminal device is performing disaster roaming.
28. The method of claim 26 or 27.
29. Before receiving system information transmitted by the third PLMN, the method includes: and determining that a fourth PLMN has stopped providing service due to the disaster, the fourth PLMN being a PLMN providing service for the terminal device before the disaster.
29. The method of any one of claims 26 to 28.
30. After learning that the fourth PLMN has stopped providing service due to the disaster, the method includes: and further comprising: obtaining information about available PLMNs in a current location area; and selecting, from the available PLMNs, a PLMN among at least one PLMN as the third PLMN.
30. The method of claim 29.
31. 31. The method of claim 29 or 30, wherein the system information further includes an identity of the fourth PLMN.
32. 1. A disaster roaming device, the device comprising: Carrying out a method according to any one of claims 1 to 9; or Implementing the method according to any one of claims 26 to 31 The apparatus is configured to:
33. A disaster roaming device, comprising: configured to carry out the method of any one of claims 10 to 20, Device.
34. A disaster roaming device, comprising: configured to carry out the method of any one of claims 21 to 25, Device.
35. A disaster roaming system, the system including a first network element and a second network element; The first network element is configured to transmit capability information supporting disaster roaming by a terminal device; The second network element is configured to receive, by the terminal device, the capability information supporting disaster roaming; The second network element is further configured to determine, based on the capability information supporting disaster roaming by the terminal device, that the terminal device is allowed to obtain disaster roaming service; The second network element is further configured to send information about a disaster roaming PLMN of the terminal device; the first network element is further configured to receive the information regarding the disaster roaming PLMN of the terminal device; system.
36. The second network element is further configured to send indication information indicating that disaster roaming needs to be performed; The first network element is further configured to receive the indication information indicating that disaster roaming needs to be performed; the indication information indicating that disaster roaming needs to be performed instructs the first network element to perform the disaster roaming service; 36. The system of claim 35.
37. The second network element is configured to determine that the terminal device is allowed to obtain the disaster roaming service, and the second network element specifically: configured to determine, based on the capability information and a local configuration supporting disaster roaming by the terminal device, that the terminal device is allowed to obtain the disaster roaming service; 37. A system according to claim 35 or 36.
38. Before the second network element is configured to transmit the information regarding the disaster roaming PLMN of the terminal device, the second network element: and further configured to determine the information regarding the disaster roaming PLMN of the terminal device based on a local configuration.
38. A system according to any one of claims 35 to 37.
39. The information regarding the disaster roaming PLMN includes: Identification of at least one PLMN that allows the terminal device to perform disaster roaming; or Disaster Roaming Service Hours; or Including identification information of at least one PLMN that allows the terminal device to perform disaster roaming and a disaster roaming service time; 39. A system according to any one of claims 35 to 38.
40. A computer-readable storage medium storing a computer program which, when executed, performs the method of any one of claims 1 to 9; or The method according to any one of claims 26 to 31 is carried out. storage medium.
41. A computer-readable storage medium storing a computer program, the computer program, when executed, performing a method according to any one of claims 10 to 20. storage medium.
42. A computer-readable storage medium storing a computer program, the computer program, when executed, performing a method according to any one of claims 21 to 25. storage medium.
43. A chip having a processor configured to read instructions stored in a memory, which, when executed by the processor, enables the chip to perform a method according to any one of claims 1 to 9 or 26 to 31.
44. A chip having a processor configured to read instructions stored in a memory, wherein when the processor executes the instructions, the chip is enabled to perform a method according to any one of claims 10 to 20.
45. A chip having a processor configured to read instructions stored in a memory, wherein when the processor executes the instructions, the chip is enabled to perform a method according to any one of claims 21 to 25.
Citation Information
Patent Citations
Network reselection in the event of a disaster
JP2022539776A
Method for displaying screen after connecting to another PLMN to handle network failure
US20220217519A1
Method for displaying screen after connecting to another PLMN to handle network failure
WO2020213817A1
Network reselection during a disaster
WO2021007447A1
