CN116711397A

CN116711397A - Disaster notification method

Info

Publication number: CN116711397A
Application number: CN202180089886.XA
Authority: CN
Inventors: 王梦涵; 周星月; 朱进国
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2021-01-08
Filing date: 2021-01-08
Publication date: 2023-09-05
Also published as: WO2022147737A1

Abstract

The present invention provides a method, apparatus and computer program product for wireless communication. The method comprises the following steps: the wireless communication terminal receives a disaster indication from the wireless communication node; wherein the disaster indication indicates at least one of a disaster condition applied to a first public land mobile network PLMN or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

Description

Disaster notification method

The present invention relates generally to wireless communications, and more particularly to 5G communications.

Terms related to notification of disaster are listed and explained below.

Disaster conditions: the conditions of initiation and termination are decided by authorities, such as conditions caused by natural disasters.

Disaster inbound roamers: a User Equipment (UE), (a) being unable to obtain service from a public land mobile network (Public Land Mobile Network, PLMN) that normally serves the UE due to service failure during a disaster condition, and (b) being able to register with other PLMNs.

Disaster roaming: special roaming policies applied during disaster states.

Minimizing service interruption (Minimization of Service Interruption, MINT): when a disaster condition applies (e.g., fire) to a certain PLMN, the mobile network may not be able to provide service. The network system should be able to handle such situations (i.e. service interruption), e.g. providing services via different PLMNs.

To reduce the negative impact of the network system on supporting disaster roaming, potential congestion due to inflow or outflow of disaster inbound roamers should be considered.

Furthermore, in case that the disaster condition is applicable to PLMNs in the area, when the PLMN is a Home PLMN (HPLMN) of the UE or is selected by the UE for providing network services, it is unclear how to notify the UE of this.

The present disclosure relates to methods, apparatus, and computer program products for wireless communications that are capable of allowing notification of disaster conditions to wireless communications.

An aspect of the disclosure relates to a wireless communication method. In an embodiment, a wireless communication method includes: the wireless communication terminal receives a disaster indication from the wireless communication node; wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

Another aspect of the present disclosure relates to a wireless communication method. In an embodiment, a wireless communication method includes: the access management node sends disaster indication to the wireless communication terminal; wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

Another aspect of the present disclosure relates to a wireless communication method. In an embodiment, a wireless communication method includes: the non-3 GPP interworking node sends disaster indication to the wireless communication terminal; wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

Another aspect of the present disclosure relates to a wireless communication method. In an embodiment, a wireless communication method includes: the trusted non-3 GPP gateway node sends disaster indication to the wireless communication terminal; wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

Another aspect of the present disclosure relates to a wireless communication method. In an embodiment, a wireless communication method includes: the trusted non-3 GPP access node sends disaster indication to the wireless communication terminal; wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

Another aspect of the present disclosure relates to a wireless communication terminal. In an embodiment, a wireless communication terminal includes a communication unit and a processor. The processor is configured to receive a disaster indication from the wireless communication node, wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

Another aspect of the disclosure relates to an access management node. In an embodiment, an access management node comprises a communication unit and a processor. The processor is configured to send a disaster indication to the wireless communication terminal, wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

Another aspect of the disclosure relates to a non-3 GPP interworking node. In an embodiment, the non-3 GPP interworking node includes a communication unit and a processor. The processor is configured to send a disaster indication to the wireless communication terminal, wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

Another aspect of the disclosure relates to a trusted non-3 GPP gateway node. In an embodiment, a trusted non-3 GPP gateway node includes a communication unit and a processor. The processor is configured to send a disaster indication to the wireless communication terminal, wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

Another aspect of the present disclosure relates to a trusted non-3 GPP access node. In an embodiment, a trusted non-3 GPP access node includes a communication unit and a processor. The processor is configured to send a disaster indication to the wireless communication terminal, wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

Various embodiments may preferably implement the following features:

preferably, the disaster indication comprises at least one of: an identification of the first PLMN; an identity of the second PLMN; at least one identification of a third PLMN, wherein the disaster condition applies to the third PLMN; at least one disaster area, wherein the disaster condition applies to the at least one disaster area; the start time of the disaster condition; or at least one recommended PLMN accessible to the wireless communication terminal.

Preferably, the disaster indication is carried in a downlink non-access stratum DLNAS transport message through a non-access stratum NAS transport procedure from an access management function AMF.

Preferably, the disaster indication is carried in a configuration update command message by a user equipment configuration update procedure from the AMF.

Preferably, the disaster indication is carried in an information request message from a non-3 GPP interworking function N3 IWF.

Preferably, the disaster indication is carried in an information request message from a trusted non-3 GPP gateway function TNGF.

Preferably, the wireless communication terminal is arranged to send an information response message indicating receipt of the disaster indication.

Preferably, the disaster indication is received from a trusted non-3 GPP access point TNAP via an access network query protocol ANQP.

Preferably, the disaster indication is received in response to the wireless communication terminal having third generation partnership project 3GPP access unavailable.

The present disclosure relates to a computer program product comprising computer readable program code stored thereon, which when executed by a processor causes the processor to implement a wireless communication method according to any of the preceding claims.

Exemplary embodiments of the present disclosure are intended to provide the obvious features obtained by referring to the following description in conjunction with the accompanying drawings. According to various embodiments, the present disclosure discloses exemplary systems, methods, devices, and computer program products. However, it should be understood that these embodiments are presented by way of example and not limitation, and that various modifications of the disclosed embodiments may be made while remaining within the scope of the disclosure, as will be apparent to those of ordinary skill in the art from reading the disclosure.

Accordingly, the disclosure is not limited to the exemplary embodiments and applications described and illustrated in the present disclosure. Furthermore, the particular order and/or hierarchy of steps in the methods of the present disclosure are exemplary approaches. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes may be rearranged while remaining within the scope of the present disclosure. As such, those of skill in the art will understand that the methods and techniques disclosed in this disclosure present different steps or acts in a sample order, and that the present invention is not limited to the particular order or hierarchy presented, unless explicitly stated otherwise.

The above and other aspects and implementations thereof are described in more detail in the accompanying drawings, detailed description and claims.

Fig. 1 shows a schematic diagram of a non-roaming architecture according to an embodiment of the disclosure.

Fig. 2 shows a schematic diagram of a non-roaming architecture according to an embodiment of the disclosure.

Fig. 3 shows a schematic diagram of a roaming architecture according to an embodiment of the disclosure.

Fig. 4 shows a schematic diagram of a roaming architecture according to an embodiment of the disclosure.

Fig. 5 shows a schematic diagram of a network architecture according to an embodiment of the present disclosure.

Fig. 6 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 7 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 8 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 9 shows a schematic diagram of a network architecture according to an embodiment of the present disclosure.

Fig. 10 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 11 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 12 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 13 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 14 shows a schematic diagram of a network architecture according to an embodiment of the present disclosure.

Fig. 15 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 16 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 17 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 18 shows a schematic diagram of a network architecture according to an embodiment of the present disclosure.

Fig. 19 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 20 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 21 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 22 shows a schematic diagram of a method according to an embodiment of the present disclosure.

Fig. 23 shows a schematic diagram of one example wireless terminal according to an embodiment of the present disclosure.

Fig. 24 shows a schematic diagram of an example of a wireless network node according to an embodiment of the disclosure.

FIG. 1 shows a non-third generation partnership project (3 with untrusted code in accordance with an embodiment of the invention ^rd Generation Partner Project,3 GPP) non-roaming architecture of the 5G core network (5G Core network,5GC) accessed. The network functions shown in fig. 1 are described below.

1) UE: a user equipment.

The UE may register in the PLMN via a 3GPP access (e.g., trusted access) or a non-3 GPP access or both a 3GPP access and a non-3 GPP access.

2) 3GPP access: for example, the 3GPP access can be a New Radio (NR) access or an evolved universal mobile telecommunications system terrestrial Radio access (Evolved Universal Mobile Telecommunications System Terrestrial Radio Access, E-UTRA).

3) Non-3 GPP access: non-3 GPP access includes access from, for example, wi-Fi, wiMAX, fixed, and Code-division multiple access (Code-Division Multiple Access, CDMA) networks. The non-3 GPP access includes an untrusted non-3 GPP access and a trusted non-3 GPP access. For example, untrusted non-3 GPP Wi-Fi access includes any type of Wi-Fi access for which a rover has no control. For example, untrusted non-3 GPP Wi-Fi access includes public hotspots, home Wi-Fi for subscribers, and corporate Wi-Fi.

4) N3IWF (non 3GPP interworking function):

in the case of untrusted Non-3GPP Access, the Non-3GPP interworking function (Non-3GPP Inter Working Function,N3IWF) includes supporting Internet protocol security (Internet Protocol security, IPsec) tunnel establishment with the UE, relaying uplink and downlink control plane Non-Access Stratum (NAS) (N1) signaling between the UE and the Access and mobility functions (Access and Mobility Function, AMF), supporting AMF selection, and the like. The N3IWF may send an information message to the UE. For example, the N3IWF may send an information request message to the UE including a deleted payload to indicate the release of the internet key exchange security association (Internet Key Exchange Security Association, IKESA).

5) AMF (access and mobility management function):

the AMF includes the following functions: registration management, connection management, reachability management, and mobility management. The two N2 interfaces shown in fig. 1 terminate as a single AMF for a UE that is simultaneously connected to the same 5GC (i.e., the data network shown in fig. 1) through both 3GPP access and non-3GPP access. The AMF may provide an information container (e.g., a UE parameter update transparent container) to the UE in a 5G mobility management (5GMobility Management,5GMM) message using network-initiated NAS transport procedures.

6) SMF (session management function)

The session management function (Session Management Function, SMF) includes the following functions: session establishment, modification and release, UE internet protocol (Internet Protocol, IP) address allocation and management, selection and control of User Plane (UP) functions, downlink data notification.

7) UPF (user plane function):

the user plane functions (User Plane Function, UPF) include the following functions: serving as anchor points for mobility within/between radio access technologies (Radio Access Technology, RATs) and external session points interconnected to the data network, packet routing and forwarding indicated by SMF, quality-of-Service (QoS) handling for UP, etc. When different PDU sessions are established over 3GPP access and non-3GPP access, the two N3 interfaces shown in fig. 1 may terminate to different UPFs.

Fig. 2 is a schematic diagram of a trusted non-3GPP access 5GC non-roaming architecture according to an embodiment of the present invention.

In contrast to the non-roaming architecture shown in fig. 1, the non-roaming architecture shown in fig. 2 further includes the following functions:

1) TNAP (trusted non-3GPP access point)

In an embodiment, non-3GPP access includes access from, for example, wi-Fi, wiMAX, fixed, and CDMA networks. Non-3GPP access includes untrusted non-3GPP access and trusted non-3GPP access. What should be considered a trusted or untrusted access is typically decided by the home rover. A Trusted Non-3GPP access point (Trusted Non-3GPP Access Point,TNAP) may announce (or send) information (e.g., PLMN with which the TNAP interworks) to the UE by using an access network query protocol (Access Network Query Protocol, ANQP).

2) TNGF (trusted non-3GPP gateway functionality):

in the case of Trusted Non-3GPP access, trusted Non-3GPP gateway functions (Trusted Non-3GPP Gateway Function,TNGF) include transparently relaying NAS messages between the UE and the AMF, implementing AMF selection procedures, terminating the N2 and N3 interfaces, and so forth. The TNGF may send an information message to the UE. For example, when an IKE protocol version 2 (IKE protocol version, IKEv 2) informative request is sent to modify one or more existing QoS flows, the tnff sends an IKE 2 (IKE protocol version 2) informative request that includes additional QoS information.

3) TNAN (trusted non-3GPP access network):

trusted Non-3GPP access networks (Trusted Non-3GPP Access Network,TNAN) include TNAP and TNGF.

Fig. 3 shows a schematic diagram of a 5GC roaming architecture with an untrusted non-3GPP access-N3 IWF in a different PLMN according to an embodiment of the present disclosure. The network functions shown in fig. 3 are the same as those shown in fig. 1. In fig. 3, the UE registers to the data network via a 3GPP access in PLMN1 and via an untrusted non-3GPP access in PLMN2 different from PLMN 1.

Fig. 4 shows a schematic diagram of a roaming architecture for 5GC with trusted non-3GPP access using different PLMNs according to an embodiment of the present disclosure.

The function shown in fig. 4 is the same as that shown in fig. 2. It should be noted that the UE in fig. 4 registers to the data network via a 3GPP access in PLMN1 and via a trusted non-3 GPP access in PLMN2 different from PLMN 1.

In case the disaster condition is applicable to PLMNs in the area, it is unclear how to notify the UE when the PLMN is the Home PLMN (HPLMN) of the UE or is selected by the UE for providing network services.

It is assumed that the disaster mainly hits 3GPP access of a specific PLMN in a specific area. The present disclosure provides a method for supporting notification of disaster situations to a UE when the UE registers to a 5G system through 3GPP access and non-3 GPP access.

In this specification, PLMN D refers to a PLMN that is subject to a disaster, and PLMN a refers to a PLMN that is operating and is not subject to a disaster.

Example 1: registration of a UE in PLMN D via a 3GPP access and an untrusted non-3 GPP access

Fig. 5 shows a schematic diagram of a network architecture according to an embodiment of the present disclosure. In fig. 5, the UE registers in PLMN D via a 3GPP access and an untrusted non-3 GPP access, and the disaster mainly damages the 3GPP access. The UE is in 5GMM connected mode over non-3 GPP access.

Fig. 6 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 6 can be used in the case of fig. 5. Step 601: the N3IWF transmits an information request message to the UE through an untrusted non-3 GPP access. The information request message includes an indication indicating that the disaster condition applies to PLMN D. In one embodiment, the above indication further includes at least one of: PLMNI D of other PLMNs applying the disaster condition, an area applying the disaster condition, a start time of the disaster condition, and/or a recommended PLMN to which the UE may access. In step 602, the UE sends a null information response message to the N3IWF over the untrusted non-3 GPP access to confirm that the received indication may indicate that the disaster condition applies to PLMN D.

Fig. 7 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 7 can be used in the case of fig. 5. In fig. 7, the AMF initiates NAS transport procedure by sending a DLNAS transport message to the UE (step 701). The DLNAS transport message may include a UE parameter update transparent container, and the content of the payload container information element (Information Element, IE) is an indication for indicating that the disaster condition applies to PLMN D. Alternatively, the DLNAS transport message may include an indication to indicate that the disaster condition applies to the PLMND. In one embodiment, the above indication further includes at least one of: PLMN IDs of other PLMNs applying the disaster condition, areas applying the disaster condition, start time of the disaster condition, and/or PLMNs to which the recommended UE may access.

Fig. 8 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 8 can be used in the case of fig. 5. In step 801, the amf initiates a generic UE configuration update procedure by sending a configuration update command message to the UE, the message including an indication to indicate that a disaster condition applies to the PLMND. In one embodiment, the above indication further includes at least one of: PLMN IDs of other PLMNs applying the disaster condition, areas applying the disaster condition, start time of the disaster condition, and/or PLMNs to which the recommended UE may access.

Example 2: registration of UE in PLMN D via 3GPP access and trusted non-3 GPP access

Fig. 9 shows a schematic diagram of a network architecture according to an embodiment of the present disclosure. In fig. 9, the UE registers in the PLMND via a 3GPP access and a trusted non-3 GPP access. Furthermore, the disaster mainly compromises 3GPP access.

Fig. 10 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 10 can be used in the case shown in fig. 9. In fig. 10, the UE is in a 5GMM idle mode or a 5GMM connected mode through a non-3 GPP access. Step 1001: the TNAP announces (or transmits) information to the UE through the ANQP protocol. The information includes an indication indicating that the disaster condition applies to PLMN D. In one embodiment, the above indication further includes at least one of: PLMN IDs of other PLMNs applying the disaster condition, areas applying the disaster condition, start time of the disaster condition, and/or PLMNs to which the recommended UE may access.

Fig. 11 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 11 can be used in the case shown in fig. 9. In fig. 11, the UE is in 5GMM connected mode through non-3 GPP access. Step 1101, the TNGF sends an information request message to the UE via TNAP, for example. The information request message includes an indication indicating that the disaster condition applies to PLMN D. In one embodiment, the above indication further includes at least one of: PLMN IDs of other PLMNs applying the disaster condition, areas applying the disaster condition, start time of the disaster condition, and/or PLMNs to which the recommended UE may access. Next, the UE sends a null information response message to the TNGF to acknowledge receipt of the indication of the disaster condition applied to the PLMND (step 1102).

Fig. 12 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 12 can be used in the case shown in fig. 9. In fig. 12, the UE is in 5GMM connected mode through non-3 GPP access. In step 1201, the AMF initiates NAS transport procedure by sending a DLNAS transport message to the UE over the TNGF and TNAP, for example. The DLNAS transport message may include a UE parameter update transparent container and the contents of the payload container IE are (e.g., include) an indication to indicate that the disaster condition applies to PLMN D. Alternatively, the DLNAS transport message may include an indication indicating that the disaster condition applies to PLMN D. In one embodiment, the above indication further includes at least one of: PLMN IDs of other PLMNs applying the disaster condition, areas applying the disaster condition, start time of the disaster condition, and/or PLMNs to which the recommended UE may access.

Fig. 13 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 13 can be used in the case shown in fig. 9. In fig. 13, the UE is in 5GMM connected mode through non-3 GPP access. In step 1301, the AMF initiates a generic UE configuration update procedure by sending a configuration update command message to the UE via TNAP and TNGF, for example. The configuration update command message may include an indication to indicate that the disaster condition applies to PLMN D. In one embodiment, the above indication further includes at least one of: PLMN IDs of other PLMNs applying the disaster condition, areas applying the disaster condition, start time of the disaster condition, and/or PLMNs to which the recommended UE may access.

Embodiment 3: UE registers in PLMN D via 3GPP access and in PLMN a via untrusted non-3 GPP access

Fig. 14 shows a schematic diagram of a network architecture according to an embodiment of the present disclosure. In fig. 14, the UE registers in PLMN D via a 3GPP access and in PLMN a via an untrusted non-3 GPP access. The disaster mainly destroys the 3GPP access and/or the whole PLMN D. In this embodiment, the UE is in 5GMM connected mode when untrusted non-3 GPP access.

Fig. 15 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 15 can be used for the case shown in fig. 14. Step 1501: the N3IWF of the PLMNA transmits an information request message to the UE through an untrusted non-3 GPP access. The information request message includes an indication indicating that the disaster condition applies to PLMN D and/or an indication indicating that PLMN a may accept disaster inbound roamers from PLMN D. In one embodiment, each indication further comprises at least one of: PLMN IDs of other PLMNs applying the disaster condition, areas applying the disaster condition, start time of the disaster condition, and/or PLMNs to which the recommended UE can access. In step 1502, the ue sends a null information response message to the N3IWF to acknowledge receipt of the indication.

Fig. 16 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 16 can be used in the case shown in fig. 14. In step 1601, an AMF, e.g., PLMN a, initiates NAS transport procedure by sending a DLNAS transport message to the UE through the N3IWF and untrusted non-3 GPP access. The DLNAS transport message may include a UE parameter update transparent container and the contents of the payload container IE include an indication to indicate that the disaster condition applies to PLMN D and/or an indication that PLMN a may accept disaster inbound roamers from PLMN D. Alternatively, the DLNAS transport message may include an indication to indicate that the disaster condition applies to PLMN D and/or an indication to indicate that PLMN a may accept a disaster inbound roamer from PLMN D. The indication carried in the payload container IE or DLNAS transport message may further comprise: at least one of the PLMN IDs of other PLMNs for which the disaster condition applies, the area for which the disaster condition applies, the time at which the disaster condition starts, and/or the PLMN to which the UE recommends access.

Fig. 17 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 17 can be used for the case shown in fig. 14. In step 1701, the AMF of PLMN a initiates a generic UE configuration update procedure by sending a configuration update command message to the UE, e.g. through the N3IWF and untrusted non-3 GPP access. In this embodiment, the configuration update command message includes an indication to indicate that the disaster condition applies to PLMN D and/or an indication to indicate that PLMN a may accept disaster inbound roamers from PLMN D. The indication contained in the configuration update command message may further include: at least one of PLMNID of other PLMNs for which disaster conditions apply, area for which disaster conditions apply, time at which disaster conditions start, and/or PLMNs to which recommended UE can access.

Embodiment four: UE registers with PLMN D through 3GPP access, and registers with PLMN A through trusted non-3 GPP access

Fig. 18 shows a schematic diagram of a network architecture according to an embodiment of the present disclosure. In this embodiment, the UE registers with PLMN D through a 3GPP access and with PLMN a through a trusted non-3 GPP access. Note that the disaster mainly compromises 3GPP access or the entire PLMN D.

Fig. 19 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 19 can be used in the case shown in fig. 18. In step 1901, the TNAP of PLMN a announces (or sends) information to the UE using ANQP protocol. The information includes an indication indicating that the disaster condition applies to PLMN D (i.e., a disaster condition indication) and/or an indication indicating that PLMN a may accept a disaster inbound roamer from PLMN D (i.e., a disaster inbound roamer acceptance indication). The indication may further comprise: at least one of PLMNID of other PLMNs applying the disaster condition, area applying the disaster condition, start time of the disaster condition, and/or PLMNs to which the recommended UE can access.

Fig. 20 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 20 can be used in the case shown in fig. 18. Step 2001: the TNGF of PLMN A sends an information request message to the UE via TNAP. The information request message includes an indication indicating that the disaster condition applies to PLMN D and/or an indication indicating that PLMN a may accept disaster inbound roamers from PLMN D. The indication carried in the information request may further comprise: at least one of the PLMN IDs of other PLMNs for which the disaster condition applies, the area for which the disaster condition applies, the time at which the disaster condition starts, and/or the PLMN to which the recommended UE can access. In step 2002, the UE sends a null information response message to the TNGF to acknowledge receipt of the indication.

Fig. 21 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 21 can be used in the case shown in fig. 18. Step 2101: the AMF of PLMN a initiates NAS transport procedures by sending a DLNAS transport message to the UE over TNAP and TNGF. The DLNAS transport message may include a UE parameter update transparent container and the contents of the payload container IE include an indication to indicate that the disaster condition applies to PLMN D and/or an indication to indicate that PLMN a may accept disaster inbound roamers from PLMN D. Alternatively, the DLNAS transport message may include an indication to indicate that the disaster condition applies to PLMN D and/or an indication to indicate that PLMN a may accept a disaster inbound roamer from PLMN D. The indication carried in the payload container IE or DLNAS transport message may further comprise: at least one of the PLMNID of the other PLMN to which the disaster condition applies, the area to which the disaster condition applies, the time at which the disaster condition starts, and/or the PLMN to which the UE recommends access.

Fig. 22 shows a schematic diagram of a method according to an embodiment of the present disclosure. The method shown in fig. 22 can be used in the case shown in fig. 18. In step 2201, the AMF of PLMN a initiates a generic UE configuration update procedure by sending a configuration update command message to the UE through TNAP and TNGF. The configuration update command message includes an indication to indicate that the disaster condition applies to PLMN D and/or an indication to indicate that PLMN a may accept disaster inbound roamers from PLMN D. The indication contained in the configuration update command message may further include: at least one of PLMNID of other PLMNs for which disaster conditions apply, area for which disaster conditions apply, time at which disaster conditions start, and/or PLMNs to which recommended UE can access.

In some aspects, the operations in the foregoing embodiments may be described as follows.

According to one embodiment, the AMF may:

an indication is sent to the UE that,

wherein the indication is used to indicate that the disaster condition application (e.g., occurrence) and/or disaster entry roamers may be accepted.

It should be noted that the indication may further include at least one of PLMNID of other PLMNs applying the disaster condition, application area of the disaster condition, start time of the disaster condition, and/or recommended PLMNs to which the UE may access.

In one embodiment, the indication is sent to the UE via NAS transport procedure by using a DLNAS transport message. Alternatively or additionally, the indication is transmitted to the UE using a configuration update command message through a generic UE configuration update procedure.

According to one embodiment, the N3IWF may:

an indication is sent to the UE that,

wherein the indication is used to indicate that the disaster condition application and/or disaster inbound roamers may be accepted.

In this embodiment, the indication may further include: at least one of PLMNID of other PLMNs applying the disaster condition, area applying the disaster condition, start time of the disaster condition, and/or PLMNs to which the recommended UE can access.

In addition, the N3IWF may also send the indication to the UE via an information request message and receive an information response message for acknowledging receipt of the indication of the UE

According to one embodiment, the TNGF may:

an indication is sent to the UE that,

In one embodiment, the above indication further includes at least one of: the PLMNID of the other PLMNs applying the disaster condition, the area applying the disaster condition, the start time of the disaster condition, and/or the recommended PLMNs that the UE can access.

The TNGF may send the indication to the UE using an information request message and receive an information response message acknowledging receipt of the indication from the UE.

According to one embodiment, the TNAP may:

an indication is announced (or sent) to the UE,

wherein the indication is used to indicate that the disaster condition application or disaster inbound roamers are acceptable.

The indication may further comprise: at least one of PLMNID of other PLMNs applying the disaster condition, area applying the disaster condition, start time of the disaster condition, and/or PLMNs to which the recommended UE can access.

In one embodiment, the TNAP may announce (or send) the indication to the UE by using the ANQP protocol.

Fig. 23 relates to a schematic diagram of a wireless communication terminal 230 according to an embodiment of the present disclosure. The wireless communication terminal 230 may be a User Equipment (UE), a mobile phone, a notebook computer, a tablet computer, an electronic book, or a portable computer system, which is not limited herein. The wireless communication terminal 230 may include a processor 2300, such as a microprocessor or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a storage unit 2310, and a communication unit 2320. The storage unit 2310 may be any data storage device that stores program code 2312 accessed and executed by the processor 2300. Examples of the storage unit 2312 include, but are not limited to, a subscriber identity module (Subscriber Identity Module, SIM), a Read-Only Memory (ROM), a flash Memory, a Random-Access Memory (RAM), a hard disk, and an optical data storage device. The communication unit 2320 may be a transceiver and is configured to transmit and receive signals (e.g., messages or data packets) according to a processing result of the processor 2300. In one embodiment, communication unit 2320 transmits and receives signals via at least one antenna 2322 as shown in fig. 23.

In one embodiment, the storage unit 2310 and the program code 2312 may be omitted, and the processor 2300 may include a storage unit having stored program code.

The processor 2300 may implement any of the steps of the exemplary embodiments on the wireless communication terminal 230, for example, by executing program code 2312.

Communication unit 2320 may be a transceiver. The communication unit 2320 may alternatively or additionally be provided as a transmitting unit and a receiving unit that transmit and receive signals to and from the wireless communication node, respectively.

Fig. 24 is a schematic diagram of a wireless communication node 240 (e.g., an access management node, a non-3 GPP interworking node, a trusted non-3 GPP gateway node, or a trusted non-3 GPP access node) according to an embodiment of the present disclosure. The wireless communication node 240 may be a satellite, a Base Station (BS), a network entity, a mobility management entity (Mobility Management Entity, MME), a Serving Gateway (S-GW), a packet data network (Packet Data Network, PDN) Gateway (Packet Data Network Gateway, P-GW), a radio access network (Radio Access Network, RAN), a Next Generation RAN (NG-RAN), a data network, a core network, or a radio network controller (Radio Network Controller, RNC), and is not limited herein. Further, the wireless communication node 240 may include (perform as) at least one network function, such as an access and mobility management function (AMF), a Session Management Function (SMF), a user location function (UPF), a policy control function (Policy Control Function, PCF), an application function (Application Function, AF), N3IWF, TNAP, TNGF, and the like. The wireless communication node 240 may include a processor 2400 such as a microprocessor or ASIC, a storage unit 2410, and a communication unit 2420. The storage unit 2410 may be any data storage device that stores program code 2412 accessed and executed by the processor 2400. Examples of storage unit 2412 include, but are not limited to, a subscriber identity module, read-only memory, flash memory, random access memory, hard disk, and optical data storage device. The communication unit 2420 may be a transceiver and is configured to transmit and receive signals (e.g., messages or data packets) according to the processing result of the processor 2400. In one example, the communication unit 2420 transmits and receives signals via at least one antenna 2422 shown in fig. 24.

In one embodiment, the storage unit 2410 and the program code 2412 may be omitted. The processor 2400 may include a memory unit with stored program code.

Processor 2400 may implement any of the steps described in the exemplary embodiment on wireless communication node 240, e.g., via execution of program code 2412.

The communication unit 2420 may be a transceiver. The communication unit 2420 may alternatively or additionally combine a transmitting unit and a receiving unit arranged to transmit and receive signals to and from a wireless communication terminal (e.g. user equipment), respectively.

According to an embodiment of the present invention, there is also provided a wireless communication method. In one embodiment, the wireless communication method may be performed by using a wireless communication terminal (e.g., UE). In one embodiment, the location management node may be implemented using the wireless communication node 230 described above, but is not limited thereto.

In one embodiment, a wireless communication method includes receiving, by a wireless communication terminal, a disaster indication from a wireless communication node. In one embodiment, the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network PLMN or a disaster condition of a second PLMN accepting disaster entry roamers from the first PLMN.

In one embodiment, the disaster indication comprises at least one of: an identification of the first PLMN (e.g., PLMN ID of PLMN D described above); an identification of a second PLMN (e.g., PLMN ID of PLMN a above); at least one identification of a third PLMN, wherein the disaster condition applies to the third PLMN; at least one disaster area, wherein the disaster condition is applied to the at least one disaster area (e.g., an area corresponding to the above PLMN D); the start time of the disaster condition; and/or at least one recommended PLMN (e.g., PLMN ID of PLMN a described above) that is capable of being accessed by the wireless communication terminal.

Specific technical details may be determined with reference to the above description and will not be described here in detail.

According to an embodiment of the present invention, there is also provided a wireless communication method. In one embodiment, the wireless communication method may be performed by using a wireless communication node. In one embodiment, the location management node may be implemented using the wireless communication node 240 described above, but is not limited thereto.

In one embodiment, a wireless communication method includes transmitting, by an access management node, a disaster indication to a wireless communication terminal. In one embodiment, the disaster indication indicates at least one of a disaster condition applied to the first public land mobile network PLMN or a second PLMN accepting disaster inbound roamers from the first PLMN.

In one embodiment, a wireless communication method includes transmitting, by a non-3 GPP interworking node, a disaster indication to a wireless communication terminal. In one embodiment, the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network PLMN or a disaster condition of a second PLMN accepting disaster entry roamers from the first PLMN.

In one embodiment, a wireless communication method includes transmitting, by a trusted non-3 GPP gateway node, a disaster indication to a wireless communication terminal. In one embodiment, the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network PLMN or a disaster condition of a second PLMN accepting disaster entry roamers from the first PLMN.

In one embodiment, a wireless communication method includes transmitting, by a trusted non-3 GPP access node, a disaster indication to a wireless communication terminal. In one embodiment, the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network PLMN or a disaster condition of a second PLMN accepting disaster entry roamers from the first PLMN.

While various embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. Likewise, the different diagrams may depict example architectures or configurations provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present disclosure. However, such persons will appreciate that the present disclosure is not limited to the example architectures or configurations shown, but may be implemented using a variety of alternative architectures and configurations. In addition, one or more features of one embodiment may be combined with one or more features of another embodiment described herein, as will be appreciated by those of ordinary skill in the art. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments.

It should also be understood that any reference to an element using names such as "first," "second," etc. in embodiments of the present invention generally does not limit the number or order of those elements. Rather, these designations may be used in embodiments of the invention as a convenient means of distinguishing between two or more elements or instances of an element. Thus, reference to first and second elements does not mean that only two elements may be employed, or that the first element must somehow precede the second element.

In addition, those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of skill would further appreciate that any of the different illustrative logical blocks, units, processors, devices, circuits, methods, and functions described in connection with the aspects disclosed in the embodiments of the invention may be implemented with electronic hardware (e.g., digital embodiments, analog embodiments, or a combination of both), firmware, different forms of program or design code incorporating instructions (which may be referred to as "software" or "software units" in the embodiments of the invention) or any combination of these techniques.

To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, units, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of such techniques depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions do not result in a departure from the scope of the present disclosure. According to various implementations, processors, devices, components, circuits, structures, machines, units, etc. may be provided to perform one or more of the functions described in embodiments of the invention. The term "configured to" or "configured to" as used in embodiments of the present invention with respect to a specified operation or function refers to a processor, device, component, circuit, structure, machine, unit, or the like that is physically constructed, programmed, and/or arranged to perform the specified operation or function.

Moreover, those of skill in the art will appreciate that the various illustrative logical blocks, units, devices, components, and circuits described in the embodiments of the invention may be implemented within or performed by an integrated circuit (Integrated Circuit, IC) that may comprise a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA), or other programmable logic device, or any combination thereof. Logic blocks, units, and circuits may also include antennas and/or transceivers to communicate with various components within the network or within the device. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of DSP cores or the above microprocessors, or any other suitable configuration for performing the functions described by embodiments of the invention. If implemented in software, the functions may be stored on a computer-readable medium as one or more instructions or code. Thus, the steps of a method or algorithm disclosed in embodiments of the present invention may be embodied as software stored on a computer readable medium.

Computer-readable media includes both computer storage media and communication media including any medium that can transfer a computer program or code from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise random access memory, read only memory, electrically erasable programmable read only memory, read only or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In this disclosure, the term "unit" as used in this disclosure refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described in this disclosure. Furthermore, for purposes of discussion, the various units are described as discrete units; however, as will be apparent to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the associated functions in accordance with embodiments of the present disclosure.

Further, memory or other storage, as well as communication components, may be employed in embodiments of the present disclosure. It should be appreciated that for clarity, the above description has described embodiments of the disclosure with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processing logic elements, or domains may be used without detracting from the disclosure. For example, functions illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Thus, references to specific functional units are only references to suitable means for providing the described functionality rather than indicative of a strict logical or physical structure or organization.

Various modifications to the embodiments described in the disclosure will be readily apparent to those skilled in the art, and the generic principles defined in this disclosure may be applied to other embodiments without departing from the scope of the disclosure. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the novel features and principles disclosed herein, as recited in the claims of the present disclosure.

Claims

1. A method of wireless communication, comprising:

the wireless communication terminal receives a disaster indication from the wireless communication node;

wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

2. The wireless communication method of claim 1, wherein the disaster indication comprises at least one of:

an identity of the first PLMN;

an identity of the second PLMN;

at least one identification of a third PLMN, wherein the disaster condition applies to the third PLMN;

at least one disaster area, wherein disaster conditions are applied to the at least one disaster area;

The start time of the disaster condition; or (b)

At least one recommended PLMN accessible to the wireless communication terminal.

3. The wireless communication method according to claim 1 or 2, wherein the disaster indication is carried in a downlink non-access stratum, DLNAS, transport message by a non-access stratum, NAS, transport procedure of an access management function, AMF.

4. The wireless communication method according to claim 1 or 2, wherein the disaster indication is carried in a configuration update command message by a user equipment configuration update procedure of the AMF.

5. The wireless communication method according to claim 1 or 2, wherein the disaster indication is carried in an information request message from a non-3 GPP interworking function, N3 IWF.

6. The wireless communication method according to claim 1 or 2, wherein the disaster indication is carried in an information request message from a trusted non-3 GPP gateway function, TNGF.

7. The wireless communication method according to any one of claims 1 to 2, 5 and 6, wherein the wireless communication terminal is arranged to send an information response message indicating receipt of the disaster indication.

8. The wireless communication method of claim 1 or 2, wherein the disaster indication is received from a trusted non-3 GPP access point, TNAP, via an access network query protocol, ANQP.

9. The wireless communication method of any of claims 1-8, wherein the disaster indication is received in response to a third generation partnership project, 3GPP, access wireless communication terminal being unavailable.

10. A method of wireless communication, comprising:

the access management node sends disaster indication to the wireless communication terminal;

wherein the disaster indication indicates at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

11. The wireless communication method of claim 10, wherein the disaster indication comprises at least one of:

an identity of the first PLMN;

an identity of the second PLMN;

at least one disaster area, wherein the disaster condition applies to the disaster area;

the start time of the disaster condition; or (b)

12. The wireless communication method of claim 10 or 11, wherein the disaster indication is transmitted in a downlink non-access stratum, DL, NAS, transport message via non-access stratum, NAS, transport procedure.

13. The wireless communication method according to claim 10 or 11, wherein the disaster indication is transmitted in a configuration update command message through a configuration update procedure of the user equipment.

14. A method of wireless communication, comprising:

the non-3 GPP interworking node sends disaster indication to the wireless communication terminal;

wherein the disaster indication indicates at least one of a disaster condition applied to a first public land mobile network PLMN or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

15. The wireless communication method of claim 14, wherein the disaster indication comprises at least one of:

an identity of the first PLMN;

an identity of the second PLMN;

the start time of the disaster condition; or (b)

16. The wireless communication method according to claim 14 or 15, wherein the disaster indication is sent in an information request message.

17. The wireless communication method according to any of claims 14 to 16, wherein the non-3 GPP interworking node is arranged to receive an information response message from the wireless communication terminal indicating the disaster indication reception.

18. A method of wireless communication, comprising:

the trusted non-3 GPP gateway node sends disaster indication to the wireless communication terminal;

19. The wireless communication method of claim 18, wherein the disaster indication comprises at least one of:

an identity of the first PLMN;

an identity of the second PLMN;

the start time of the disaster condition; or (b)

20. The wireless communication method according to claim 18 or 19, wherein the disaster indication is sent in an information request message.

21. A wireless communication method according to any of claims 18 to 20, wherein the trusted non-3 GPP gateway node is arranged to receive an information response message from the wireless communication terminal indicating the disaster indication reception.

22. A method of wireless communication, comprising:

the trusted non-3 GPP access node sends disaster indication to the wireless communication terminal;

23. The wireless communication method of claim 22, wherein the disaster indication comprises at least one of:

an identity of the first PLMN;

an identity of the second PLMN;

the start time of the disaster condition; or (b)

24. The wireless communication method of claim 22 or 23, wherein the disaster indication is sent by an access network query protocol, ANQP.

25. A wireless communication terminal, comprising:

a communication unit;

a processor configured to receive a disaster indication from the wireless communication node, wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

26. The wireless communication terminal of claim 25, wherein the processor is further configured to perform the wireless communication method of any of claims 2 to 9.

27. An access management node, comprising:

a communication unit;

a processor configured to send a disaster indication to the wireless communication terminal, wherein the disaster indication is for indicating at least one of a disaster condition applied to a first public land mobile network, PLMN, or a disaster condition of a second PLMN accepting a disaster inbound roamer from the first PLMN.

28. The access management node according to claim 27, characterized in that the processor is further arranged to perform the wireless communication method of any of claims 11 to 13.

29. A non-3 GPP interworking node, comprising:

A communication unit;

30. The non-3 GPP interworking node of claim 29, wherein the processor is further configured to perform the wireless communication method of any one of claims 15 to 17.

31. A trusted non-3 GPP gateway node comprising:

a communication unit;

32. The trusted non-3 GPP gateway node of claim 31, wherein said processor is further arranged to perform the wireless communication method of any one of claims 19 to 21.

33. A trusted non-3 GPP access node comprising:

a communication unit;

34. The trusted non-3 GPP access node of claim 33, wherein the processor is further arranged to perform the wireless communication method of any one of claims 23 to 24.

35. A computer program product comprising computer readable program code stored thereon, which when executed by a processor causes the processor to implement the wireless communication method of any of claims 1 to 24.