Communication method and device

Abstract

This application discloses a communication method and apparatus. The method includes: a UE sends a registration request message to an AMF, where the registration request message includes indication information, and the indication information indicates whether a disaster scenario exists; the AMF receives the registration request message, and sends a registration response message to the UE based on the indication information and a load situation; the UE receives the registration response message. Through the method provided in this application, it is possible to explicitly indicate whether a disaster scenario exists, thereby improving the efficiency of information exchange.

Description

[Technical Field]

[0001] This application claims priority to Chinese Patent Application No. 202110184233.1, entitled "COMMUNICATION METHOD AND APPARATUS," filed with the State Intellectual Property Office of China on February 10, 2021, which is incorporated herein by reference in its entirety.

[0002] TECHNICAL FIELD This application relates to the field of communications technology, and more particularly to communications methods and devices. [Background technology]

[0003] In a mobile communication system, when a terminal device needs to access a network, the terminal device sends a registration request message to an associated network element, such as an access and mobility management function (AMF), so that the AMF obtains the registration request message and then determines whether the UE is allowed to access the associated network, for example, the network corresponding to the AMF.

[0004] It will be appreciated that there is an urgent need to find a way to explicitly indicate relevant information using the registration request message. Summary of the Invention [Problem to be solved by the invention]

[0005] The present application provides a communication method and apparatus that uses indicator information to effectively indicate whether a disaster scenario exists, thereby improving the efficiency of information exchange. [Means for solving the problem]

[0006] According to a first aspect, an embodiment of the present application provides a communication method, the method including:

[0007] The terminal device sends a registration request message to an access and mobility management function (AMF) (also referred to as an access and mobility management network element, etc.), where the registration request message includes indication information, and the indication information indicates whether a disaster scenario exists. The UE receives a registration response message from the AMF.

[0008] In this embodiment of the present application, the indication information indicating whether a disaster scenario exists may be understood as indicating whether a terminal device (e.g., a terminal device may be referred to as a UE for short) is in a disaster scenario. Generally, in a disaster scenario, a home public land mobile network (HPLMN) corresponding to the UE is usually damaged, and therefore the UE cannot effectively access the HPLMN. In this case, to avoid service interruption, the UE needs to roam to another network, such as a roaming PLMN. Therefore, the UE needs to interact with the AMF to ensure that the UE can access the roaming PLMN.

[0009] According to the method provided in this embodiment of the present application, the registration request message includes indication information. On the one hand, the AMF explicitly learns whether the UE is in a disaster scenario, thereby improving the efficiency of information exchange. On the other hand, the AMF may further learn the reason for the UE to access a roaming network (e.g., a roaming PLMN or a network corresponding to the AMF). In addition, if the registration request message does not include indication information, the AMF may not distinguish whether the registration request message is a registration request message sent by a local user or a registration request message sent by a UE in a disaster scenario, which may affect the subsequent registration process of the AMF.

[0010] In a possible implementation, the indication information is a first value, and the indication information indicates that the terminal device is in a disaster scenario, or the indication information is a second value, and the indication information indicates that the terminal device is not in a disaster scenario.

[0011] For example, the first value may be 1 and the second value may be 0.

[0012] According to the method provided in this embodiment of the present application, through one-bit information, the AMF can learn whether the UE is in a disaster scenario, and can effectively support the registration process of the UE regardless of whether the UE is in a disaster scenario.

[0013] In a possible implementation, the registration request message further includes a registration type, which includes any one of an initial registration, a mobility registration updating, a periodic registration updating, or an emergency registration.

[0014] According to a second aspect, an embodiment of the present application provides a communication method, the method including:

[0015] The AMF receives a registration request message from the terminal device, where the registration request message includes indication information, and the indication information indicates whether a disaster scenario exists. The AMF sends a registration response message to the terminal device based on the indication information and a load situation.

[0016] In this embodiment of the present application, since the registration request message includes indication information, the AMF can send a registration response message to the UE based on the indication information and the load situation of the AMF. Therefore, the AMF can perform different processing for the UE based on the actual scenario in which the UE is located. For example, the AMF can send a registration accept message or a registration reject message to the UE based on the scenario in which the UE is located.

[0017] In a possible implementation, the AMF sending a registration response message to the terminal device based on the indication information and the load situation includes: the AMF determining a threshold based on the indication information; and the AMF sending a registration accept message or a registration reject message to the UE based on the load situation and the threshold.

[0018] In this embodiment of the present application, the load condition may include the load condition of the AMF or the load condition of the network corresponding to the AMF.

[0019] In a possible implementation, the threshold is a first threshold when the indication information indicates that a disaster scenario exists, or the threshold is a second threshold when the indication information indicates that a disaster scenario does not exist.

[0020] In this embodiment of the present application, the AMF may determine different thresholds based on whether the UE is in a disaster scenario. Therefore, the AMF sends a registration allowance message or a registration rejection message to the UE based on the load situation of the AMF, so the AMF may use different control methods on the UE based on the scenario in which the UE is located.

[0021] According to a third aspect, an embodiment of the present application provides a communication method, the method including:

[0022] A terminal device receives a system message from a base station in a roaming network, where the system message includes a maximum waiting time. The terminal device determines a waiting time for sending a registration request message based on a value of an identifier of the terminal device mod the maximum waiting duration. After the waiting time has elapsed, the terminal device sends the registration request message to an AMF.

[0023] In this embodiment of the present application, the maximum waiting time is used to determine the waiting time for the UE to send a registration request message. For example, the maximum waiting time may also be understood as the maximum period for the UE to wait. For example, the maximum waiting time may also be called the maximum network access waiting time (inbound-waiting-max-time), disaster roaming waiting range, maximum roaming waiting time, etc. The specific name of the maximum waiting time is not limited in this embodiment of the present application.

[0024] According to the method provided in this embodiment of the present application, the waiting time is determined by using the value of the UE identifier modulo the maximum waiting time, which can mitigate the case where a large number of UEs simultaneously access a network that supports AMF, thereby ensuring the randomness of UE access while minimizing the amount of calculation.

[0025] In a possible implementation, the terminal device sending a registration request message to the AMF includes:

[0026] If the terminal device determines that a disaster scenario exists, the terminal device sends a registration request message to the AMF.

[0027] In a possible implementation, the registration request message includes indication information, which indicates whether a disaster scenario exists.

[0028] According to the method provided in this embodiment of the present application, based on both the instruction information and the waiting time, network congestion resulting from a large number of UEs simultaneously accessing the network in a disaster scenario is avoided as much as possible.

[0029] According to a fourth aspect, an embodiment of the present application provides a communication method, the method including:

[0030] A base station in a roaming network determines the maximum waiting time based on the load situation.

[0031] The base station sends a system message to the terminal device, where the system message includes a maximum waiting time.

[0032] According to the method provided in this embodiment of the present application, when a UE needs to access a roaming network, a base station in the roaming network determines the maximum waiting time based on the load situation, so that the time at which the UE accesses the roaming network can be effectively balanced, thereby mitigating the case where a large number of UEs access the roaming network.

[0033] According to a fifth aspect, an embodiment of the present application provides a communication method, the method including:

[0034] A terminal device sends a registration request message to an access and mobility management network element (AMF) and receives a registration rejection message from the AMF. The terminal device determines a list based on the registration rejection message, where the list includes networks that support the AMF and that are not allowed to be accessed in a disaster scenario.

[0035] According to the method provided in this embodiment of the present application, the UE may add a network corresponding to the AMF to the list after receiving a registration rejection message from the AMF through the list. In this way, the UE can mitigate the case where the UE repeatedly accesses the AMF, thereby effectively alleviating the deterioration of network congestion. For example, generally, after the UE receives a registration rejection message, the UE adds a network corresponding to the AMF to another list. However, in a disaster scenario, the UE is permitted to access a network corresponding to another AMF again. When the above method is used, even if the UE receives a registration rejection message, the UE still continues to access a network to which it is not permitted to access, which not only affects the communication status of the UE but also worsens network congestion.

[0036] In a possible implementation, the network comprises any one or more of a public land mobile network (PLMN), a tracking area or a portion of a tracking area.

[0037] According to a sixth aspect, an embodiment of the present application provides a communications device configured to perform the method of the first aspect or any possible implementation of the first aspect. Alternatively, the communications device is configured to perform the method of the second aspect or any possible implementation of the second aspect. Alternatively, the communications device is configured to perform the method of the third aspect or any possible implementation of the third aspect. Alternatively, the communications device is configured to perform the method of the fourth aspect. Alternatively, the communications device is configured to perform the method of the fifth aspect or any possible implementation of the fifth aspect.

[0038] For example, the communication device may include a transceiver unit and a processing unit. For a specific description of the transceiver unit and the processing unit, please refer to the device embodiments provided below.

[0039] According to a seventh aspect, an embodiment of the present application provides a communications device. The communications device includes a processor configured to perform a method as set forth in the first, second, third, fourth, fifth, or any possible implementation. Alternatively, the processor is configured to execute a program stored in a memory. When the program is executed, the method as set forth in the first, second, third, fourth, fifth, or any possible implementation is performed.

[0040] During the execution of the above method, the information transmission process in the above method may be understood as a process in which the processor outputs information or a process in which the processor receives input information. During the output of information, the processor outputs information to the transceiver, which then transmits the information. After the information is output by the processor, other processing may need to be performed before the information arrives at the transceiver. Similarly, during the reception of input information by the processor, the transceiver receives the information and inputs it to the processor. Furthermore, after the transceiver receives information, other processing may need to be performed on the information before it is input to the processor.

[0041] Based on this principle, for example, the sending of a registration request message in the above-described method may be understood as the processor outputting the registration request message. In another example, the receiving of a registration request message in the above-described method may be understood as the processor receiving an input registration request message.

[0042] Unless otherwise specified, or where operations such as transmitting, sending and receiving associated with a processor do not contradict the actual function or internal logic of the operations in the associated description, all operations may be more generally understood as operations such as output, receiving and input of a processor instead of operations such as transmitting, sending and receiving performed directly by radio frequency circuits and antennas.

[0043] During implementation, the processor may be a processor specially configured to execute these methods, or may be a processor configured to execute computer instructions in memory to execute these methods, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM). The memory and the processor may be integrated on the same chip or located on different chips. The type of memory and the arrangement of the memory and the processor are not limited to the embodiments of the present application. It may be understood that the description of the processor and memory is also applicable to the sixth aspect described below. For ease of explanation, details will not be described in the sixth aspect.

[0044] In a possible implementation, the memory is located external to the communication device.

[0045] In a possible implementation, the memory is located within the communication device.

[0046] In this embodiment of the present application, the processor and the memory may alternatively be integrated into one device. In other words, the processor and the memory may alternatively be integrated together. In a possible implementation, the communication device further includes a transceiver, the transceiver being configured to receive signals or transmit signals.

[0047] For specific descriptions of each communication device, please refer to the following embodiments, and details will not be described here.

[0048] According to an eighth aspect, an embodiment of the present application provides a communication device, the communication device including a logic circuit and an interface, the logic circuit coupled to the interface.

[0049] In some embodiments of the present application, the communications device may be configured to perform steps performed by a UE. For example, the interface is configured to output a registration request message and input a registration response message. In another example, the logic circuit is configured to determine a wait time for transmitting the registration request message. In another example, the logic circuit is configured to determine that a disaster scenario exists.

[0050] In some other embodiments of the present application, the communication device may be configured to perform steps performed by the AMF. For example, the interface may be configured to input a registration request message and output a registration response message. As another example, the logic circuit may be configured to determine the registration response message, etc., based on the indication information and the load situation.

[0051] In some further embodiments of the present application, the communications device may be configured to perform steps performed by a base station, e.g., the logic circuitry is configured to determine a maximum waiting time based on a load situation, the interface is configured to output a system message, etc.

[0052] For descriptions of the registration request message, the registration response message, the instruction information, the waiting time, the maximum waiting time, the UE identifier, etc., please refer to the descriptions of the first to fifth aspects or the embodiments shown below, and details will not be described here.

[0053] According to a ninth aspect, an embodiment of the present application provides a computer-readable storage medium configured to store a computer program, which, when executed on a computer, performs the method described in the first aspect or any possible implementation of the first aspect, or the method described in the second aspect or any possible implementation of the second aspect, or the method described in the third aspect or any possible implementation of the third aspect, or the method described in the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possible implementation of the fifth aspect.

[0054] According to a tenth aspect, an embodiment of the present application provides a computer program product. The computer program product includes a computer program or computer code. When the computer program product is run on a computer, it performs the method illustrated in the first aspect or any possible implementation of the first aspect, or the method illustrated in the second aspect or any possible implementation of the second aspect, or the method illustrated in the third aspect or any possible implementation of the third aspect, or the method illustrated in the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possible implementation of the fifth aspect.

[0055] According to an eleventh aspect, an embodiment of the present application provides a computer program which, when run on a computer, performs the method set forth in the first aspect or any possible implementation of the first aspect, or the method set forth in the second aspect or any possible implementation of the second aspect, or the method set forth in the third aspect or any possible implementation of the third aspect, or the method set forth in the fourth aspect or any possible implementation of the fourth aspect, or the fifth aspect or any possible implementation of the fifth aspect.

[0056] According to a twelfth aspect, an embodiment of the present application provides a wireless communication system. The wireless communication system includes a UE and an AMF. The UE is configured to perform the method described in the first aspect or any possible implementation of the first aspect, and the AMF is configured to perform the method described in the second aspect or any possible implementation of the second aspect. Alternatively, the wireless communication system includes a UE and a base station. The UE is configured to perform the method described in the third aspect or any possible implementation of the third aspect, and the base station is configured to perform the method described in the fourth aspect. Alternatively, the wireless communication system includes a UE and an AMF connected to the UE. The UE is configured to perform the fifth aspect or any possible implementation of the fifth aspect. [Brief explanation of the drawings]

[0057] [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0058] [Figure 2] 1 is a schematic flowchart of a communication method according to an embodiment of the present application; [Figure 3] 1 is a schematic flowchart of a communication method according to an embodiment of the present application; [Figure 4] 1 is a schematic flowchart of a communication method according to an embodiment of the present application; [Figure 5] 1 is a schematic flowchart of a communication method according to an embodiment of the present application;

[0059] [Figure 6] 1 is a schematic structural diagram of a communication device according to an embodiment of the present application; [Figure 7] 1 is a schematic structural diagram of a communication device according to an embodiment of the present application; [Figure 8] 1 is a schematic structural diagram of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0060] To make the objectives, technical solutions and advantages of the present application clearer, the present application will be further described with reference to the accompanying drawings.

[0061] The terms "first," "second," etc. in the specification, claims, and accompanying drawings of this application are merely used to distinguish different objects and are not used to describe a particular order. In addition, terms such as "comprise" and "have," and any other variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or device comprising a series of steps or units is not limited to the recited steps or units, but instead optionally further includes unrecited steps or units, or optionally further includes other steps or units inherent to those processes, methods, products, or devices.

[0062] The term "embodiment" as used herein means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. Phrases appearing in various places within the present specification do not necessarily refer to the same embodiment, nor are they exclusive independent or alternative embodiments to another embodiment. It may be explicitly or implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0063] In this application, "at least one (item)" means one or more, "multiple" means two or more, "at least two (items)" means two, three, or more, and "and / or" is used to describe an association relationship between related objects and indicates that three relationships may exist. For example, "A and / or B" may indicate that only A is present, that only B is present, or that both A and B are present. A and B may be singular or plural. The character " / " generally indicates that related objects are in an "or" relationship. "At least one of" or similar phrases refers to any combination of these items. For example, at least one of a, b, or c may represent a, b, c, "a and b," "a and c," "b and c," or "a, b, and c."

[0064] The technical solutions provided in the present application may be applied to various communication systems, such as a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, an internet of things (IoT) system, a narrow band-internet of things (NB-IoT) system, wireless fidelity (Wi-Fi), a fifth generation (5G) communication system or new radio (NR), or another future communication system.

[0065] The technical solutions provided in the present application may be further applied to machine-type communication (MTC), Long Term Evolution-machine (LTE-M) technology, and device-to-device (D2D) networks, machine-to-machine (M2M) networks, Internet of things (IoT) networks, or other networks. IoT networks may include, for example, Internet of Vehicles. Communication methods in Internet of Vehicle systems are collectively referred to as vehicle-to-X (V2X, where X can be anything). For example, V2X may include vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, or vehicle-to-network (V2N) communication.

[0066] The terms used in this application are described in detail below.

[0067] 1. Terminal Device

[0068] A terminal device in this application is a device having a radio transceiver function, and may communicate with one or more core network (CN) devices (also referred to as core devices) via access network devices (also referred to as access devices) in a radio access network (RAN).

[0069] A terminal device may also be referred to as user equipment (UE), access terminal, terminal, subscriber unit, subscriber station, mobile station, mobile console, remote station, remote terminal, mobile device, user terminal, user agent, user equipment, etc. In a possible implementation, the terminal device may be deployed on land, for example, indoors or outdoors, in a handheld form, or in a vehicle. Alternatively, the terminal device may be deployed on water (for example, on a boat). Alternatively, the terminal device may be deployed in the air (for example, on an aircraft, a balloon, a satellite, etc.). In a possible implementation, the terminal device may be any form of terminal device having wireless communication capabilities, such as a handheld device, an in-vehicle device, a wearable device, a terminal in the Internet of Things or the Internet of Vehicles, a fifth-generation (5G) network, a future network, etc. This is not a limitation in this application.

[0070] It should be noted that the terminal device referred to in this application may include not only a vehicle (for example, the entire vehicle) in the Internet of Vehicles, but also an in-vehicle device or an in-vehicle terminal in the Internet of Vehicles, etc. When applied to the Internet of Vehicles, the specific form of the terminal device is not limited in this application.

[0071] It can be understood that the terminal devices shown in this application can further communicate with each other by using technologies such as device to device (D2D), vehicle to everything (V2X) or machine to machine (M2M). The communication method between the terminal devices is not limited in this application.

[0072] 2.AMF

[0073] As mobile bandwidth access services expand, mobile networks will also evolve to better support diverse business models and meet the requirements of more diverse application services and industries. For example, to provide better and more complete services to more industries, the network architecture of 5G networks will be adjusted compared to that of 4G networks. For example, in 5G networks, the mobility management entity (MME) in 4G networks will be divided into multiple network elements (sometimes called network functions), such as the access and mobility management function (AMF) and the session management function (SMF).

[0074] The AMF in this application is a control plane network function provided by a PLMN, and is involved in access control and mobility management when a UE accesses a PLMN, including functions such as mobility state management, temporary user identity allocation, and user authentication and authorization. Therefore, even if the AMF evolves into other forms, names, etc. as mobile networks evolve, the AMF falls within the scope of protection of this application as long as it can implement the methods disclosed in this application.

[0075] 3.Base station

[0076] A base station may be a device deployed in a wireless access network and providing wireless communication services to terminal devices. In this application, a base station may also be referred to as an access network device, an access device, a RAN device, etc.

[0077] For example, the base station referred to in this application may include, but is not limited to, a next generation node base station (gNB) in a 5G system, an evolved NodeB (eNB) in an LTE system, a radio network controller (RNC), a NodeB (NodeB, NB), a base station controller (BSC), a base transceiver station (BTS), a home NodeB (home evolved NodeB B or home NodeB, HNB), a base band unit (BBU), a transmitting and receiving point (TRP), a transmitting point (TP), a miniature base station device (pico), a mobile switching center, or a network device in a future network. Alternatively, the base station may be a device that performs base station functions in D2D, V2X, M2M, etc. In systems with different radio access technologies, the names of devices having access network device functions may be different.

[0078] Optionally, in some deployments of the base station, the base station may include a centralized unit (CU), a distributed unit (DU), etc. In some other deployments of the base station, the CU may be further divided into a CU control plane (CP), a CU user plane (UP), etc. In still some other deployments of the base station, the base station may alternatively be an open radio access network (ORAN) architecture, etc. The specific deployment method of the base station is not limited in this application.

[0079] Based on the aforementioned UE, AMF, and base station, an embodiment of the present application provides a communication system as shown in Fig. 1. Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application. As shown in Fig. 1, the communication system may include at least one base station, at least one terminal device such as UE1 to UE6 in Fig. 1, and an AMF. It should be understood that for specific descriptions of the AMF, UE, and base station, please refer to the above descriptions. Details will not be described here.

[0080] For example, UEs may communicate directly with each other. For example, direct communication between UEs may be implemented by using D2D technology. As shown in FIG. 1, UE4 and UE5 and UE4 and UE6 may communicate directly with each other by using D2D technology. UE4 or UE6 may communicate with UE5 alone or simultaneously. In another example, UE4 to UE6 may communicate with a base station separately. For example, UE4 or UE6 may communicate with a base station directly or indirectly. For example, UE6 may communicate with a base station via UE5. Note that FIG. 1 illustrates an example of communication links between one base station and multiple UEs and between communication devices. Alternatively, a communication system may include multiple base stations, and the coverage of each base station may include a different number of UEs, for example, more or fewer UEs. This is not limited in this embodiment of the present application.

[0081] Optionally, the communication system shown in FIG. 1 may further include a unified data management (UDM) network element, an authentication server function (AUSF) network element, etc. The specific structure of the communication system is not limited in this embodiment of the present application. For example, the unified data management (UDM) is a control plane function provided by an operator and is responsible for storing information such as a subscriber permanent identifier (SUPI), a security context, and subscription data of a subscriber in a PLMN. The AUSF is a control plane function provided by an operator and is typically used for authentication, for example, authentication between a terminal device (subscriber) and a PLMN. Alternatively, the communication system may further include another network element such as a network controller and a session management function (SMF), which is not limited in this embodiment of the present application.

[0082] When an emergency, such as a disaster, occurs in the HPLMN that the UE is currently accessing, in order to reduce service interruption for the UE, the UE needs to roam to another PLMN that can provide service (even if the UE does not activate a roaming agreement). Once the failure is removed, the UE may re-access the original PLMN (e.g., the HPLMN). In other words, in a disaster scenario, the HPLMN to which the UE is connected is usually destroyed. As a result, the UE cannot effectively access the HPLMN, resulting in a service interruption for the UE. To ensure service continuity, the UE may register with a PLMN that provides disaster roaming service.

[0083] In this regard, the present application provides a communication method and apparatus, so that the AMF that receives the registration request message sent by the UE can clearly understand whether the UE is in a disaster scenario, thereby improving the efficiency of information exchange. In addition, the communication method provided in the present application can effectively reduce service interruptions for the UE in a disaster scenario. For communication systems to which the present application is applicable, please refer to the above description (e.g., Figure 1). Details will not be described here.

[0084] 2 is a schematic flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 2, the method includes the following steps:

[0085] 201: The UE sends a registration request message to the AMF, where the registration request message includes indication information, and the indication information indicates whether a disaster scenario exists. In response, the AMF receives the registration request message.

[0086] When a disaster occurs, base stations, core network elements, etc. may be damaged, and UEs may be disconnected from the network. In other words, a disaster causes an interruption of communication services. For example, a natural disaster such as an earthquake may cause fires or power failures in some radio access network devices. As a result, cell coverage between the radio access network and the core network may suddenly disappear, or routes between the radio access network and the core network may no longer exist. Man-made disasters, such as the installation of faulty software or improperly managed certificates, may cause abnormal behavior in the radio access network, causing users in the network to fail to exchange signaling or data. Note that the disaster scenario described in this embodiment of the present application may also be referred to as a disaster roaming scenario, and the specific name of the disaster scenario is not limited in this embodiment of the present application.

[0087] It may be understood that the method by which the UE determines that it is in a disaster scenario is not limited in this embodiment of the present application. For example, when the UE cannot access the previous PLMN, the UE learns that it is in a disaster scenario. Alternatively, when the UE attempts to re-access a network such as a roaming network after disconnecting from the previous network, the UE may learn that it is in a disaster scenario based on a broadcast message of a base station in the roaming network. The above-mentioned method for determining that the UE is in a disaster scenario is merely an example and should not be construed as a limitation on this embodiment of the present application. Therefore, the UE may send a registration request message to the AMF of the roaming network.

[0088] In this embodiment of the present application, the indication information indicating whether a disaster scenario exists may be understood as the indication information indicating whether the UE is in a disaster scenario, or the indication information indicating whether the HPLMN of the UE is in a disaster scenario, or the indication information indicating whether the previous network corresponding to the UE is in a disaster scenario, or the indication information indicating whether a registration request message is initiated in a disaster scenario, or the indication information indicating whether the UE initiates a registration request message in a disaster scenario. This is not limited in this embodiment of the present application. In other words, whether the registration request message is for registration in a disaster scenario may be indicated through the indication information. It may be understood that the above indication information may also be called a disaster condition indication, etc. The specific name of the indication information is not limited in this embodiment of the present application.

[0089] For example, when the indication information is a first value, the indication information indicates that a disaster scenario exists. When the indication information is a second value, the indication information indicates that a disaster scenario does not exist. For example, whether a disaster scenario exists may be indicated by one bit of indication information. For example, the first value may be one, and the second value may be zero. In other words, after the UE determines that the UE is roaming from another network to a roaming network due to a disaster, the UE may send a registration request message carrying indication information to the AMF, where the indication information is the first value. Through the one-bit information, the AMF can learn whether the UE is in a disaster scenario and can more effectively support the UE's registration process regardless of whether the UE is in a disaster scenario. Of course, the specific bits of the indication information are not limited in this embodiment of the present application.

[0090] For example, the contents included in the registration request message may be shown in Table 1. It may be understood that the following contents included in the registration request message are merely examples and should not be construed as limitations on this embodiment of the present application. [Table 1]

[0091] In a possible implementation, the registration request message further includes a registration type, which includes any one of an initial registration, a mobility registration updating, a periodic registration updating, or an emergency registration.

[0092] For example, the registration type may be indicated by using three bits, as shown in Table 2. It may be understood that the relationship between bits and registration types shown in Table 2 is merely an example. [Table 2]

[0093] In this embodiment of the present application, in relation to the indication information and registration type, the AMF can not only learn that the UE is in a disaster scenario, but also learn whether the registration request message is for an initial registration, a mobility registration update, a periodic registration update, or an emergency registration in a disaster scenario.

[0094] For example, in Table 3, disaster roaming initial registration is added, so that the AMF learns that the UE is in a disaster scenario. In Table 4, disaster roaming registration is added, so that the AMF learns that the UE is in a disaster scenario. However, when the UE is in a disaster scenario, the type of registration request message initiated may not be limited to disaster roaming initial registration. Alternatively, disaster roaming registration may have a semantic conflict with initial registration, mobility registration update, periodic registration update, or emergency registration. The methods shown in Tables 3 and 4 cannot effectively determine whether the registration request message includes an initial registration type or a disaster initial registration during the initial registration of the UE. Semantically, initial registration may include disaster initial registration, so there may be a logical scope inconsistency.

[0095] However, in this embodiment of the present application, indication information is added to the registration request message. Compared with the registration types shown in Table 3 or Table 4, more registration types in disaster scenarios can be indicated, so the AMF can use different registration access control methods for different types of registration request messages. For example, for initial registration, the AMF can perform authentication operations, assign tracking areas, etc. As another example, for mobility registration updates, the AMF may not need to perform authentication, etc.

[0096] In addition, the AMF can explicitly learn whether a UE is in a disaster scenario. In other words, the AMF can effectively determine which type of UE sends a registration request message received by the AMF. For example, the AMF can effectively determine whether the registration request message is a local network access UE (also referred to as a local network access user or a local network access device), an international roaming UE (also referred to as an international roaming user, an international roamer, etc.), or a disaster roaming UE (also referred to as a disaster roaming user or a disaster roamer). If the registration request message does not include indication information, it is difficult for the AMF to know whether the registration request message is initiated by a roaming UE in a disaster scenario or a roaming subscribed UE. As a result, the AMF only knows that the UE is actually a non-subscribed UE and a roaming UE in a disaster scenario after authentication by the HPLMN. This further affects the control policy that the AMF needs to take for the UE in a disaster scenario (e.g., the control policy used by the AMF is delayed). [Table 3] [Table 4]

[0097] It can be understood that when the UE sends a registration request message, if the registration request message does not include the aforementioned indication information, it may indicate that the UE is not in a disaster scenario.

[0098] 202: The AMF sends a registration response message to the UE based on the indication information and the load status, and the UE receives the registration response message in response.

[0099] The load situation may include the load situation of the AMF or the load situation of the network corresponding to the AMF. How the AMF learns the load situation of the network corresponding to the AMF is not limited in this embodiment of the present application.

[0100] In this embodiment of the present application, the registration response message includes a registration accept message or a registration reject message. For example, the AMF determines the registration accept message or the registration reject message based on the indication information and a load situation, so as to send the registration accept message or the registration reject message to the UE. For example, the AMF may determine a threshold based on the indication information, and then determine the registration accept message or the registration reject message based on the load situation and the threshold. For example, the indication information indicates that a disaster scenario exists, and the threshold is a first threshold (which may also be referred to as a disaster load threshold, etc.). In another example, if the indication information indicates that a disaster scenario does not exist, the threshold is a second threshold (which may also be referred to as a non-disaster load threshold, etc.).

[0101] In other words, in this embodiment of the present application, different thresholds may be determined based on whether a disaster scenario exists. In this way, the AMF can use different control measures based on corresponding thresholds and load conditions. For example, after a registration request message is received, if the indication information is a first value such as 1, the AMF can determine whether to accept the registration of the UE based on the first threshold. For example, if the load condition exceeds the first threshold, the registration request message can be rejected. Otherwise, the registration request message is accepted. If the indication information is a second value such as 0 or does not carry any indication information, this indicates that the UE is a local network UE or a roaming-affiliated UE, and whether to accept the registration of the UE can be determined based on the second threshold.

[0102] It may be understood that the specific criteria for the first threshold and the second threshold are not limited in this embodiment of the present application. For example, the load situation may be determined based on the number of connected UEs, and the first threshold and the second threshold may be set based on criteria for UE access. In another example, the load situation may be determined based on the load percentage of the network (or the load percentage of the AMF), and the first threshold and the second threshold may be set based on the load percentage of the network. The specific criteria for the load situation, the first threshold, and the second threshold are not limited in this embodiment of the present application.

[0103] Optionally, the first threshold may be greater than the second threshold. In this case, when a disaster scenario occurs, it can be ensured that the UE in the disaster scenario has priority access to the network. For example, since the UE in the disaster scenario has priority access to the network, the UE can communicate with the outside world quickly or in a timely manner. Optionally, the first threshold may be smaller than the second threshold. In this case, since the UE in the disaster scenario is a non-roaming UE, the first threshold may be smaller than the second threshold to ensure the communication quality between the home network UE and the roaming UE. The magnitude relationship between the first threshold and the second threshold is not limited in this embodiment of the present application.

[0104] In this embodiment of the present application, the registration request message includes indication information. On the one hand, the AMF explicitly learns whether the UE is in a disaster scenario, thereby improving the efficiency of information exchange. On the other hand, the AMF can further learn the reason why the UE accesses a roaming network (e.g., a roaming PLMN or a network corresponding to the AMF).

[0105] 3 is a schematic flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 3, the method includes the following steps:

[0106] 301: A base station in a roaming network determines a maximum waiting time based on the load situation.

[0107] The maximum waiting time may also be called the maximum network access waiting time (inbound-waiting-max-time), disaster roaming waiting range, maximum roaming waiting time, etc. The specific name of the maximum waiting time is not limited in this embodiment of the present application.

[0108] In this embodiment of the present application, the load situation may include the load situation of the base station or the load situation of the network corresponding to the base station. The base station determining the maximum waiting time based on the load situation means that the base station can dynamically adjust the maximum waiting time based on the load situation. For example, a higher load (which can also be understood as a heavier load) indicates a longer maximum waiting time. A lower load indicates a shorter maximum waiting time. By associating the load situation with the maximum waiting time, the load situation of the base station or the network can be effectively improved. In other words, it is ensured that UEs are evenly distributed across different time ranges. For example, when the load is light, UEs may perform access intensively for a short time, and when the load is heavy, UEs may perform access sparsely for a long time. In this way, network congestion can be effectively alleviated.

[0109] It can be understood that the specific relationship between load and maximum wait time is not limited in this embodiment of the present application. Similarly, the measurement of the maximum wait time is not limited. For example, the maximum wait time may be measured in seconds, for example, 5 seconds or 255 seconds.

[0110] 302: The base station sends a system message to the UE, where the system message includes a maximum waiting time. In response, the UE receives the system message.

[0111] For example, the system message may include a system information block 1, another SIB (hereinafter referred to as SIB-vX), etc. This is not limited in this embodiment of the present application.

[0112] For example, the signaling format of SIB1 may be shown as follows: [Table 5]

[0113] SIB1-v17XX-IEs indicates the version (v) number of the system message, inbound-waiting-max-time indicates the maximum waiting time, and INTEGER indicates the specific value of the maximum waiting time.

[0114] For example, the signaling format of SIB-vX may be shown as follows: [Table 6]

[0115] It can be understood that SIB-vX-IEs indicates the version number of the system message, inbound-waiting-max-time indicates the maximum waiting time, and INTEGER indicates a specific value of the maximum waiting time.

[0116] If the maximum waiting time is included in the SIB-vX and the system message does not include the SIB-vX, this indicates that the UE can immediately send a registration request message. In other words, when the UE does not need to wait, the system message does not need to include the SIB-vX.

[0117] 303: The UE determines a waiting time for sending a registration request message based on the value of the UE identifier mod the maximum waiting time.

[0118] In this embodiment of the present application, the UE identifier may include a 5th generation system (5GS) mobile identity, such as a UE subscription (subscription concealed identifier (SUCI)), a globally unique temporary UE identity (GUTI), a subscription permanent identifier (SUPI), an international mobile equipment identity (IMEI), an international mobile subscriber identity (IMSI), etc. Using IMSI as an example, the UE may determine a waiting time for sending a registration request message based on the IMSI and the maximum waiting time. For example, the maximum waiting time is 30, and UE1's IMSI is 460011234567891, and UE2's IMSI is 460011234567898. For example, the value of the IMSI mod maximum waiting time (e.g., IMSI mod (inbound-waiting-max-time)) is 460011234567891 mod 30=21, and 460011234567898 mod 30=28. UE1 needs to wait 21 seconds before sending a registration request message, and UE2 needs to wait 28 seconds before sending a registration request message. Because the waiting times of UE1 and UE2 are different, network congestion caused by simultaneous initiation of registration requests by UE1 and UE2 can be effectively avoided.

[0119] It can be understood that the UE may use a timer to adjust the waiting time for the registration request message when camping on a cell. Alternatively, the UE may use a timer to adjust the waiting time for the registration request message when acquiring a broadcast message of a base station in a roaming network. The time at which the UE starts the time adjustment is not limited in this embodiment of the present application.

[0120] In this embodiment of the present application, since the IMSI can be unique within each UE (similar to a phone number), its distribution is statistically random and uniform within the network, which ensures that the result obtained after modulo operation of the random number modulo the maximum waiting time is randomly and uniformly distributed from 0 to the maximum waiting time, ensuring that the UEs are evenly distributed in different time ranges.

[0121] 304: The UE sends a registration request message to the AMF after the waiting time has elapsed. In response, the AMF receives the registration request message.

[0122] The specific content of the registration request message is not limited in this embodiment of the present application. In other words, the method provided in this embodiment of the present application can be applied not only to a non-disaster scenario, such as when the UE is a roaming joining UE, but also to a disaster scenario, such as when the UE is a disaster roaming UE. For a specific description of the non-disaster scenario, please refer to the relevant standard or protocol. Details will not be described here.

[0123] For example, when the UE determines that the UE is in a disaster scenario, the UE sends a registration request message to the AMF. For a specific description of how the UE determines that the UE is in a disaster scenario, please refer to the method shown in Figure 2. Details will not be described here. In this case, the registration request message may not include indication information. For example, the registration request message may include a registration type.

[0124] In another example, the registration request message may include indication information. Thus, the indication information explicitly indicates whether a disaster scenario exists. For a specific description of when a disaster scenario exists, please refer to the method shown in FIG. 2. In other words, the method shown in FIG. 3 may be combined with the method shown in FIG. 2. A specific description of the indication information, etc. is not provided here. In addition, a specific description of sending a registration response message to the UE by the AMF based on the indication information and the load situation is not provided.

[0125] According to the method provided in this embodiment of the present application, when a UE needs to access a roaming network, a base station in the roaming network determines a maximum waiting time based on a load situation, so as to effectively balance the time points at which the UE accesses the roaming network, thereby mitigating the case where a large number of UEs access the roaming network. In addition, the waiting time is determined by using the value of the UE identifier mod the maximum waiting time, so as to mitigate the case where a large number of UEs access the network supporting AMF at the same time, thereby minimizing the amount of calculation and ensuring the randomness of UE access.

[0126] 4 is a schematic flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 4, the method includes the following steps:

[0127] 401: The terminal device sends a registration request message to the AMF, and the AMF receives the registration request message.

[0128] 402: The AMF sends a registration rejection message to the UE, and the UE receives the registration rejection message.

[0129] As can be understood, please refer to relevant standards, protocols, etc. for specific descriptions of step 401 and step 402. The registration request message and the registration rejection message are not limited in this embodiment of the present application.

[0130] 403: The UE determines a list based on the registration rejection message, where the list includes networks that support AMF and are not allowed to access in a disaster scenario.

[0131] In this embodiment of the present application, after receiving a registration rejection message, the UE may add a network that supports AMF and that the UE is not allowed to access to the list to prevent the UE from repeatedly attempting to access the network. For example, the registration request message may be an initial registration initiated by the UE (e.g., the UE first attempts to access an AMF in a roaming network). Therefore, the UE may add a network that supports the AMF that the UE first attempts to access to the list. For example, the registration request message may alternatively be a registration request message initiated by the UE again after the UE has been rejected one or more times, rather than an initial registration initiated by the UE. In this case, because the UE has failed multiple attempts to access the AMF, the UE may add a network that supports AMF to the list. This effectively prevents the UE from wasting resources or time trying to access the network again and being rejected again.

[0132] A network may be understood to include any one or more of a PLMN, a tracking area, or a portion of a tracking area. For example, the list may include a disaster forbidden PLMN list and a disaster forbidden tracking areas list (also referred to as a disaster forbidden tracking areas of roaming list) or disaster forbidden tracking areas for regional provision of list (or may also be referred to as a disaster forbidden tracking areas for regional provision of service list).

[0133] In a possible implementation, the method provided in this embodiment of the present application may be further combined with the method shown in Fig. 2. For example, the registration request message may include indication information, so that the AMF may send a registration rejection message to the UE based on the indication information and the load situation.

[0134] In a possible implementation, the method provided in this embodiment of the present application may be further combined with the method shown in Figure 3. For example, a base station in a roaming network determines a maximum waiting time based on a load situation and transmits the maximum waiting time to a UE. The UE then determines a waiting time for transmitting a registration request message based on the value of the UE identifier mod the maximum waiting time, and transmits the registration request message to an AMF after the waiting time has elapsed.

[0135] In a possible implementation, the method provided in this embodiment of the present application may be further combined with the methods shown in Figures 2 and 3. For a specific description of the combination of the methods in Figures 2, 3 and 4, please refer to Figure 5 shown below, and the details will not be described here.

[0136] Generally, after receiving a registration rejection message, the UE adds the network corresponding to the AMF to another list, for example, a forbidden list in a relevant standard or protocol. However, in a disaster scenario, the UE is allowed to access another network corresponding to the AMF again. When using the above method, even if the UE receives a registration rejection message, the UE still repeatedly attempts to access the rejected network, which not only affects the communication status of the UE but also aggravates network congestion.

[0137] However, according to the method provided in this embodiment of the present application, through the list, the UE can add the network corresponding to the AMF to the list after receiving a registration rejection message from the AMF, thereby reducing the case where the UE repeatedly accesses the AMF, and effectively alleviating the deterioration of network congestion.

[0138] It can be understood that the above-described embodiments may be independent solutions or may be combined based on internal logic. All of these solutions fall within the scope of protection of the present application. For example, the above-described embodiments may be combined with each other. For example, the methods shown in FIGS. 2 and 3 may be combined with each other. As another example, the methods shown in FIGS. 2 and 4 may be combined with each other. As another example, the methods shown in FIGS. 3 and 4 may be combined with each other. As another example, the methods shown in FIGS. 2, 3, and 4 may be combined with each other. For an example of a combination of FIGS. 2 to 4, please refer to the method shown in FIG. 5.

[0139] 5 is a schematic flowchart of a communication method according to an embodiment of the present application. As shown in FIG. 5, the method includes the following steps:

[0140] 501: A base station in a roaming network determines a maximum waiting time based on a load situation.

[0141] 502: The base station sends a system message to the UE, where the system message includes a maximum waiting time. In response, the UE receives the system message.

[0142] 503: The UE determines a waiting time for sending a registration request message based on the value of the maximum waiting time of the IMSI mod of the UE.

[0143] 504: The UE sends a registration request message to the AMF after the waiting time has elapsed. In response, the AMF receives the registration request message. The registration request message includes indication information, which indicates whether a disaster scenario exists.

[0144] 505: The AMF sends a registration rejection message to the UE based on the indication information and the load situation, and the UE receives the registration rejection message in response.

[0145] 506: The UE determines a list based on the registration rejection message, where the list includes networks that support AMF and are not allowed to access in a disaster scenario.

[0146] For ease of understanding, please refer to FIGS. 2 to 4 for a specific description of the method shown in FIG. 5. Details will not be described one by one here. For example, for steps 501 to 504, please refer to the method shown in FIG. 3. For the registration request messages shown in steps 504 and 505, please refer to the method shown in FIG. 2. For step 506, please refer to the method shown in FIG. 4.

[0147] It can be understood that in the above embodiment, authentication may further be performed between the AMF and the AUSF in the HPLMN of the UE. For example, after the AMF receives a registration request message, the AMF may send an authentication request to the AUSF in the HPLMN, and the AUSF sends the authentication request in the HPLMN to the UDM. The UDM sends an authentication response to the AUSF, and the AUSF sends an authentication response to the AMF, and the AMF sends the authentication response to the UE. As can be understood, for the authentication process between the UE and the AMF and the authentication process between the AMF and the AUSF in the HPLMN, please refer to relevant standards, protocols, etc. This is not limited in this embodiment of the present application.

[0148] According to the method provided in this embodiment of the present application, the AMF in the roaming network can not only learn whether the UE is in a disaster scenario, but also determine whether to send a registration rejection message to the UE based on the scenario in which the UE is located. In this way, after receiving the registration rejection message, the UE adds the network corresponding to the AMF to a list to avoid wasting resources caused by multiple access attempts by the UE.

[0149] A communication device provided in an embodiment of the present invention is described below.

[0150] In the present application, the communication device is divided into functional modules based on the above-described method embodiment. For example, each functional module may be divided into corresponding functions, or two or more functions may be integrated into one processing module. The integrated module may be implemented in the form of hardware or in the form of a software functional module. It should be noted that the module division in the present application is an example and is merely a logical function division. During actual implementation, the modules may be divided in other ways. The communication device in the embodiment of the present application will be described in detail below with reference to FIGS. 6 to 8.

[0151] 6 is a schematic structural diagram of a communication device according to an embodiment of the present application. As shown in FIG. 6, the communication device includes: a processing unit 601 and a transceiver unit 602.

[0152] In some embodiments of the present application, the communication device may be the terminal device shown above, a chip in the terminal device, etc. In other words, the communication device may be configured to perform the steps, functions, etc. performed by the terminal device in the above-described method embodiments.

[0153] For example, the transceiver unit 602 is configured to output a registration request message, where the registration request message includes indication information, and the indication information indicates whether a disaster scenario exists. The transceiver unit 602 is further configured to input a registration response message.

[0154] In this embodiment of the present application, configuring the transceiver unit 602 to output a registration request message includes configuring the transceiver unit 602 to send a registration request message to the AMF, and configuring the transceiver unit 602 to input a registration response message includes configuring the transceiver unit 602 to receive a registration response message from the AMF.

[0155] For example, the transceiver unit 602 may be further configured to perform the transmitting step in step 201 shown in Figure 2, and the transceiver unit 602 may be further configured to perform the receiving step in step 202 shown in Figure 2. In another example, the transceiver unit 602 may be further configured to perform the transmitting step in step 502 shown in Figure 5, and the processing unit 601 may be further configured to perform the step 503 shown in Figure 5. The transceiver unit 602 may be further configured to perform the transmitting step in step 504 and the receiving step in step 505 shown in Figure 5, and the processing unit 601 may be further configured to perform the step 506 shown in Figure 5.

[0156] The specific description of the transceiver unit and the processing unit will not be described in detail one by one here. For example, the processing unit 601 may perform the steps of outputting a registration request message, inputting a registration response message, etc. via the transceiver unit 602.

[0157] As can be understood, for descriptions of the registration request message, instruction information, registration type, disaster scenario, etc. in this embodiment of the present application, please refer to the descriptions of the above-mentioned method embodiments (e.g., Figures 2 and 5), and the details will not be described one by one here.

[0158] For example, the transceiver unit 602 is configured to input a system message, where the system message includes a maximum waiting time. The processing unit 601 is configured to determine a waiting time for transmitting a registration request message based on the identifier of the communication device and the maximum waiting time. The transceiver unit 602 is further configured to output the registration request message after the waiting time has elapsed.

[0159] It may be understood that the transceiver unit 602 being configured to input a system message includes the transceiver unit 602 being configured to receive a system message from a base station in a roaming network. The transceiver unit 602 being further configured to output a registration request message after a waiting time has elapsed includes the transceiver unit 602 being further configured to send the registration request message to an AMF after the waiting time has elapsed.

[0160] For example, the transceiver unit 602 may be further configured to perform the receiving step in step 302 shown in FIG. 3, the processing unit 601 may be further configured to perform the step 303 shown in FIG. 3, and the transceiver unit 602 may be further configured to perform the transmitting step in step 304 shown in FIG. 3.

[0161] As can be understood, in this embodiment of the present application, please refer to the description of the above-mentioned method embodiment (shown in FIG. 3 or FIG. 5) for the description of the system message, the maximum waiting time, the identifier of the communication device (including IMSI), the registration request message, the disaster scenario, etc. The details will not be described one by one here.

[0162] For example, the transceiver unit 602 is configured to output a registration request message and input a registration rejection message, and the processing unit 601 is configured to determine a list based on the registration rejection message, where the list includes networks that support AMF and that are not allowed to be accessed in a disaster scenario.

[0163] For example, the transceiver unit 602 may be further configured to perform the transmitting step in step 401 and the receiving step in step 402 shown in FIG. 4, and the processing unit 601 may be further configured to perform step 403 shown in FIG. 4.

[0164] As can be understood, please refer to the description of the above-mentioned embodiment (shown in FIG. 4 or FIG. 5) for the description of the registration request message, the registration rejection message, the list, etc. The details will not be described one by one here.

[0165] Referring again to Figure 6, in some other embodiments of the present application, the communication device may be the AMF shown above, a chip within the AMF, etc. In other words, the communication device may be configured to perform the steps, functions, etc. performed by the AMF in the method embodiments described above.

[0166] For example, the transceiver unit 602 is configured to input a registration request message, where the registration request message includes indication information, and the indication information indicates whether a disaster scenario exists. The processing unit 601 is configured to output a registration response message via the transceiver unit 602 based on the indication information and the load condition. In this embodiment of the present application, the processing unit 601 is configured to determine a registration response message based on the indication information and the load condition, and then output the registration response message via the transceiver unit 602.

[0167] In another example, the processing unit 601 is configured to determine the threshold value based on the indication information, and the transceiver unit 602 outputs a registration allow message or a registration reject message based on the load situation and the threshold value.

[0168] For example, the transceiver unit 602 may be further configured to perform the receiving step in step 201, the transmitting step in step 202, etc. shown in Figure 2. Details will not be described here. In another example, the transceiver unit 602 may be further configured to perform the receiving step in step 504 and the transmitting step in step 505 shown in Figure 5.

[0169] As can be understood, in this embodiment of the present application, for descriptions of the registration request message, instruction information, registration type, disaster scenario, load status, and thresholds (including the first threshold and the second threshold), please refer to the descriptions of the above-mentioned method embodiment (shown in FIG. 2 or FIG. 5), and the details will not be described one by one here.

[0170] Referring again to Figure 6, in some other embodiments of the present application, the communication device may be the base station shown above, a chip in the base station, etc. In other words, the communication device may be configured to perform the steps, functions, etc. performed by the base station in the aforementioned method embodiments.

[0171] For example, the processing unit 601 is configured to determine the maximum waiting time based on the load situation. The transceiver unit is configured to output a system message, where the system message includes the maximum waiting time.

[0172] For example, the processing unit 601 may be further configured to perform step 301 shown in Figure 3, and the transceiver unit 602 may be further configured to perform the transmitting step in step 302, the receiving step in step 304, etc. shown in Figure 3. As another example, the processing unit 601 may be further configured to perform step 501 shown in Figure 5, and the transceiver unit 602 may be further configured to perform the transmitting step in step 502, etc. shown in Figure 5.

[0173] As can be understood, in this embodiment of the present application, please refer to the description of the above-mentioned method embodiment (shown in FIG. 3 or FIG. 5) for the description of the load situation, maximum waiting time, disaster scenario, etc. The details will not be described one by one here.

[0174] It can be understood that the specific descriptions of the transceiver unit and the processing unit in the above-mentioned embodiments are merely examples. For the specific functions, steps, etc. performed by the transceiver unit and the processing unit, please refer to the above-mentioned method embodiments. Details will not be described here.

[0175] The transmitter-side device and the receiver-side device in the embodiments of the present application have been described above, and possible product forms of the transmitter-side device and the receiver-side device are described below. It should be understood that any form of product having the functions of the transmitter-side device in Fig. 6 or any form of product having the functions of the receiver-side device in Fig. 6 is within the protection scope of the embodiments of the present application. It should be further understood that the following description is merely an example, and the product forms of the transmitter terminal device and the receiver terminal device in the embodiments of the present invention are not limited thereto.

[0176] In a possible embodiment, in the communication device shown in Fig. 6, the processing unit 601 may be one or more processors, and the transceiver unit 602 may be a transceiver, or the transceiver unit 602 may include a transmitting unit and a receiving unit. The transmitting unit may be a transmitter, the receiving unit may be a receiver, or the transmitting unit and the receiving unit may be integrated into one device, for example, a transceiver. In this embodiment of the present application, the processor and the transceiver may be combined or similar. The connection method between the processor and the transceiver is not limited in this embodiment of the present application.

[0177] As shown in FIG. 7, the communication device 70 includes a processing unit 701 and a transceiver unit 702 .

[0178] For example, when the communication apparatus is configured to perform a step, method, or function performed by a terminal device, the transceiver 710 is configured to send a registration request message to the AMF, receive a registration response message from the AMF, etc. Alternatively, the transceiver 710 is configured to receive a system message from a base station in a roaming network. The processor 720 is configured to determine a waiting time for sending the registration request message based on an identifier of the terminal device and a maximum waiting time. Alternatively, the processor 720 is configured to determine a list based on a registration rejection message, where the list corresponds to the AMF and includes networks to which access is not permitted in a disaster scenario.

[0179] For example, when the communication device is configured to perform a step, method, or function performed by the AMF, the transceiver 710 is configured to receive a registration request message from the terminal device and send a registration response message (including a registration accept message or a registration reject message) to the terminal device. The processor 720 is configured to determine the registration response message based on the indication information and the load situation.

[0180] For example, when the communication device is configured to perform the steps, methods, or functions performed by the above-mentioned base station, the processor 720 is configured to determine a maximum waiting time based on a load situation, and the transceiver 710 is configured to send a system message to the terminal device, where the system message includes the maximum waiting time.

[0181] As can be understood, for a specific description of the transceiver and the processor, please refer to the communication device shown in FIG. 6 or the method embodiment described above, and details will not be described here.

[0182] In various embodiments of the communication apparatus shown in Figure 7, the transceiver may include a receiver and a transmitter, where the transceiver is configured to perform receiving functions (or operations) and the transmitter is configured to perform transmitting functions (or operations). The transceiver is configured to communicate with another device / apparatus over a transmission medium.

[0183] Optionally, the communication device 70 may further include one or more memories 730 configured to store program instructions and / or data (e.g., when the communication device is configured to execute steps performed by a terminal device, the memory may include a list, and therefore the list shown in FIG. 7 is indicated by dashed lines). The memory 730 is coupled to the processor 720. A coupling in this embodiment of the present application may be an indirect coupling or communication connection between devices, units, or modules in an electrical, mechanical, or other form, used for information exchange between the devices, units, or modules. The processor 720 may cooperate with the memory 730. The processor 720 may execute program instructions stored in the memory 730. Optionally, at least one of the one or more memories may be included in the processor.

[0184] The specific connection medium between the transceiver 710, the processor 720, and the memory 730 is not limited in this embodiment of the present application. In this embodiment of the present application, in FIG. 7, the memory 730, the processor 720, and the transceiver 710 are connected via a bus 740. The bus is shown by a bold line in FIG. 7. The connection method between the other components is only an example for illustration purposes, and the present application is not limited thereto. The bus may be classified into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is shown in FIG. 7, but this does not mean that only one bus or only one type of bus exists.

[0185] In this embodiment of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc. The processor is capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, any conventional processor, etc. The steps of the methods disclosed in connection with the embodiments of the present application may be implemented directly by a hardware processor, or may be implemented by using a combination of hardware and software modules in a processor.

[0186] In this embodiment of the present application, the memory may include, but is not limited to, a non-volatile memory such as a hard disk drive (HDD) or a solid-state drive (SSD), a random access memory (RAM), an erasable programmable read-only memory (EPROM), a read-only memory (ROM) or a portable read-only memory (CD-ROM). The memory is any storage medium that can be used to carry or store program code in the form of instructions or data structures and that can be read and / or written by a computer (e.g., a communication device shown in this application). However, the present application is not limited thereto. Alternatively, the memory in this embodiment of the present application may be a circuit or any other device that can implement a storage function and is configured to store program instructions and / or data.

[0187] For example, when the communication device is configured to execute steps performed by a terminal device, the processor 720 is primarily configured to process communication protocols and communication data, control the entire communication device, execute software programs, and process data from the software programs. The memory 730 is primarily configured to store software programs and data. The transceiver 710 may include a control circuit and an antenna. The control circuit is primarily configured to convert baseband signals and radio frequency signals and process the radio frequency signals. The antenna is primarily configured to transmit and receive radio frequency signals in the form of electromagnetic waves. The input / output devices, such as a touch screen, display screen, and keyboard, are primarily configured to receive data entered by a user and output data to the user. After the communication device is powered on, the processor 720 may read the software program in the memory 730, interpret and execute instructions from the software program, and process data from the software program. When data needs to be transmitted wirelessly, the processor 720 performs baseband processing on the data to be transmitted and then outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal in the form of electromagnetic waves via the antenna. When data is transmitted to a communication device, the radio frequency circuitry receives a radio frequency signal via an antenna, converts the radio frequency signal to a baseband signal, and outputs the baseband signal to the processor 720. The processor 720 converts the baseband signal to data and processes the data. In another implementation, the radio frequency circuitry and antenna may be located independently from the processor that performs the baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna may be located independently, away from the communication device.

[0188] It can be understood that the communication device shown in this embodiment of the present application may alternatively include more components than those shown in FIG. 7, etc. This is not limited to this embodiment of the present application. The above-described methods performed by the processor and transceiver are merely examples. Please refer to the above-described methods for specific steps performed by the processor and transceiver.

[0189] In another possible embodiment, in the communication device shown in FIG. 6 , the processing unit 601 may be one or more logic circuits, and the transceiver unit 602 may be an input / output interface, or may be referred to as a communication interface, interface circuit, interface, etc. Alternatively, the transceiver unit 602 may include a transmitting unit and a receiving unit. The transmitting unit may be an output interface, and the receiving unit may be an input interface. The transmitting unit and the receiving unit may be integrated into one unit, for example, an input / output interface. As shown in FIG. 8 , the communication device shown in FIG. 8 includes a logic circuit 801 and an interface 802. The processing unit 601 may be implemented via the logic circuit 801, and the transceiver unit 602 may be implemented via the interface 802. The logic circuit 801 may be a chip, a processing circuit, an integrated circuit, a system on chip (SoC), etc. The interface 802 may be a communication interface, an input / output interface, a pin, etc. For example, FIG. 8 illustrates an example in which the communication device is a chip. The chip includes the logic circuit 801 and the interface 802.

[0190] In this embodiment of the present application, the logic circuit and the interface may further be coupled to each other, and the specific connection method between the logic circuit and the interface is not limited to this embodiment of the present application.

[0191] For example, when the communication apparatus is configured to perform a method, function, or step performed by a terminal device, the interface 802 is configured to output a registration request message and input a registration response message. In another example, the interface 802 is configured to input a system message, and the logic circuit 801 is configured to determine a waiting time for sending the registration request message based on an identifier of the terminal device and a maximum waiting time. In another example, the logic circuit 801 is configured to determine the list based on a registration rejection message.

[0192] For example, when the communication device is configured to perform a method, function, or step performed by an AMF, the interface 802 is configured to input a registration request message and output a registration response message. In another example, the logic circuit 801 is configured to determine a registration response message based on the indication information and the load situation, and the interface 802 is configured to output the registration response message.

[0193] For example, when a communication device is configured to execute a method, function or step performed by an AMF, the logic circuit 801 is configured to determine a maximum waiting time based on a load situation, and the interface 802 is configured to output a system message.

[0194] As can be understood, please refer to the above-mentioned embodiments for specific descriptions of the interfaces and logic circuits, and the details will not be described one by one here.

[0195] It can be understood that the communication device shown in this embodiment of the present application may implement the methods provided in the embodiments of the present application in the form of hardware, or may implement the methods provided in the embodiments of the present application in the form of software, which is not limited in the embodiments of the present application.

[0196] For specific implementation of the embodiment shown in Figure 8, please refer to the above-mentioned embodiment, and the details will not be described here.

[0197] An embodiment of the present application further provides a wireless communication system. The wireless communication system includes a terminal device and an AMF. The terminal device and the AMF may be configured to perform the method of any one of the above-mentioned embodiments. Optionally, the wireless communication system further includes a base station, and the base station may be configured to perform the method of any one of the above-mentioned embodiments. For specific descriptions of the terminal device, the AMF, and the base station, please refer to the above-mentioned embodiments. Details will not be described here.

[0198] Additionally, the present application further provides a computer program, which is used to implement the actions and / or processes performed by the terminal device in the methods provided in the present application.

[0199] The present application further provides a computer program, which is used to implement the actions and / or processes performed by the AMF in the methods provided in the present application.

[0200] The present application further provides a computer program for use in implementing the actions and / or processes performed by a base station (e.g., a base station in a roaming network of a UE) in the methods provided herein.

[0201] The present application further provides a computer-readable storage medium that stores computer code that, when executed on a computer, enables the computer to perform the actions and / or processes performed by a terminal device in the methods provided herein.

[0202] The present application further provides a computer-readable storage medium that stores computer code that, when executed on a computer, enables the computer to perform the actions and / or processes performed by the AMF in the methods provided herein.

[0203] The present application further provides a computer-readable storage medium that stores computer code that, when executed on a computer, enables the computer to perform the actions and / or processes performed by a base station (e.g., a base station in a roaming network of a UE) in the methods provided herein.

[0204] The present application further provides a computer program product, which includes computer code or a computer program that, when executed on a computer, performs the operations and / or processes performed by the terminal device in the methods provided herein.

[0205] The present application further provides a computer program product, which includes computer code or a computer program that, when executed on a computer, performs the actions and / or processes performed by the AMF in the methods provided herein.

[0206] The present application further provides a computer program product, which includes computer code or a computer program that, when executed on a computer, performs the operations and / or processes performed by a base station (e.g., a base station in a roaming network of a UE) in the methods provided herein.

[0207] In the embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the described device embodiments are merely examples. For example, the division into units is merely a logical functional division, and other divisions may be used in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some functions may be ignored or not performed. In addition, the shown or described mutual couplings or direct couplings or communication connections may be indirect couplings or communication connections via some interfaces, devices, or units, or may be electrical, mechanical, or other forms of connection.

[0208] Units described as separate components may or may not be physically separated, and components 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 for implementing the technical effects of the solutions provided in the embodiments of the present application.

[0209] In addition, the functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0210] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be essentially implemented in the form of a software product, or a portion of the technical solution may be implemented in the form of a software product. The software product is stored in a storage medium and includes a plurality of instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method described in the embodiments of the present application. The readable storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0211] 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 modifications or replacements that are easily understood by those skilled in the art within the technical scope disclosed in the present application shall 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 communication method comprising: sending a registration request message to an access mobility management network element by a terminal device, the registration request message including indication information, the indication information being one-bit information indicating whether a disaster scenario corresponding to the terminal device exists; receiving, by the terminal device, from the access mobility management network element, a registration response message based on the indication information and a load situation, the registration response message including a registration accept message or a registration reject message, the registration accept message or the registration reject message being determined by the access mobility management network element based on a threshold determined based on the indication information and the load situation; A method comprising:

2. When the indication information is a first value, the indication information indicates that the disaster scenario corresponding to the terminal device exists; or When the indication information is a second value, the indication information indicates that the disaster scenario corresponding to the terminal device does not exist. The method of claim 1.

3. the registration request message further includes a registration type, the registration type including any one of an initial registration type, a mobility registration type, a periodic registration type, or an emergency registration type; 3. The method according to claim 1 or 2.

4. 1. A communication method comprising: receiving, by an access mobility management network element, a registration request message from a terminal device, the registration request message including indication information, the indication information being one-bit information indicating whether a disaster scenario corresponding to the terminal device exists; sending, by the access and mobility management network element, a registration response message to the terminal device based on the indication information and a load situation; and wherein the step of sending, by the access mobility management network element, a registration response message to the terminal device based on the indication information and a load situation includes: determining, by the access and mobility management network element, a threshold value based on the indication; sending, by the access and mobility management network element, a registration acceptance message or a registration rejection message to the terminal device based on the load situation and the threshold; A method comprising:

5. When the indication information indicates that the disaster scenario corresponding to the terminal device exists, the threshold value is a first threshold value; or When the indication information indicates that the disaster scenario corresponding to the terminal device does not exist, the threshold value is a second threshold value. The method of claim 4.

6. 1. A communication method comprising: receiving, by the terminal device, a system message from a base station in a roaming network, the system message including a maximum waiting time; determining, by the terminal device, a waiting time for transmitting a registration request message based on an identifier of the terminal device mod the value of the maximum waiting time; sending, by the terminal device, the registration request message to an access mobility management network element after the waiting time has elapsed, the registration request message including indication information, the indication information being one-bit information indicating whether a disaster scenario corresponding to the terminal device exists; A method comprising:

7. When the indication information is a first value, the indication information indicates that the disaster scenario exists; or When the indication information is a second value, the indication information indicates that the disaster scenario does not exist. The method of claim 6.

8. The step of sending, by the terminal device, the registration request message to an access mobility management network element includes: sending, by the terminal device, the registration request message to the access and mobility management network element if the terminal device determines that the terminal device is in a disaster scenario; 8. The method of claim 6 or 7, comprising:

9. If the terminal device determines that the terminal device is in a disaster scenario, the indication information is a first value. The method of claim 8.

10. receiving, by the terminal device, a registration reject message from the access and mobility management network element; determining, by the terminal device, a list based on the registration rejection message, the list including networks that correspond to the access and mobility management network element and that are not allowed to be accessed in a disaster scenario; 10. The method according to any one of claims 6 to 9.

11. The network comprises any one or more of a public land mobile network (PLMN), a tracking area or a part of a tracking area; The method of claim 10.

12. A communication device, a transceiver unit configured to transmit and receive signals; The following operations are performed via said transceiver unit: sending a registration request message to an access mobility management network element, the registration request message including indication information, the indication information being one-bit information indicating whether a disaster scenario corresponding to the communication device exists; receiving a registration response message based on the indication information and a load condition from the access mobility management network element, the registration response message including a registration accept message or a registration reject message, the registration accept message or the registration reject message being determined by the access mobility management network element based on a threshold determined based on the indication information and the load condition; a processing unit configured to perform operations including: A communication device comprising:

13. When the indication information is a first value, the indication information indicates that the disaster scenario corresponding to the communication device exists; or When the indication information is a second value, the indication information indicates that the disaster scenario corresponding to the communication device does not exist. The communication device of claim 12.

14. the registration request message further includes a registration type, the registration type including any one of an initial registration type, a mobility registration type, a periodic registration type, or an emergency registration type; 14. A communication device according to claim 12 or 13.

15. A communication device, a transceiver unit configured to receive a registration request message from a terminal device, the registration request message including indication information, the indication information being one-bit information indicating whether a disaster scenario corresponding to the terminal device exists; and a processing unit configured to send, through the transceiver unit, a registration response message to the terminal device based on the indication information and a load situation; wherein the processing unit is particularly configured to determine a threshold value based on the indication information, and to send, through the transceiver unit, a registration acceptance message or a registration rejection message to the terminal device based on the load situation and the threshold value.

16. When the indication information indicates that the disaster scenario corresponding to the terminal device exists, the threshold value is a first threshold value; or When the indication information indicates that the disaster scenario corresponding to the terminal device does not exist, the threshold value is a second threshold value.

16. The communication device of claim 15.

17. A communication device, a transceiver unit configured to receive a system message from a base station in a roaming network, the system message including a maximum waiting time; a processing unit configured to determine a waiting time for transmitting a registration request message based on an identifier of the communication device mod the value of the maximum waiting time; the transceiver unit is further configured to send the registration request message to an access and mobility management network element after the waiting time has elapsed, the registration request message including indication information, the indication information being one-bit information indicating whether a disaster scenario corresponding to the communication device exists; Communication equipment.

18. When the indication information is a first value, the indication information indicates that the disaster scenario corresponding to the communication device exists; or When the indication information is a second value, the indication information indicates that the disaster scenario corresponding to the communication device does not exist.

18. The communication device of claim 17.

19. the transceiver unit is particularly configured to send the registration request message to the access and mobility management network element when the communication device is in a disaster scenario.

19. A communication device according to claim 17 or 18.

20. If the communication device is in a disaster scenario, the indication information is a first value.

20. The communication device of claim 19.

21. the transceiver unit is further configured to receive a registration reject message from the access and mobility management network element; the processing unit is configured to determine a list based on the registration rejection message, the list including networks corresponding to the access and mobility management network element and to which access is not permitted in a disaster scenario; 21. A communication device according to any one of claims 17 to 20.

22. The network comprises any one or more of a public land mobile network (PLMN), a tracking area or a part of a tracking area; 22. The communication device of claim 21.

23. A communication device comprising a processor and a memory, the processor is configured to store computer-executable instructions; The processor is configured to execute the computer-executable instructions such that the method of any one of claims 1 to 3 is performed. Communication equipment.

24. A communication device comprising a processor and a memory, the processor is configured to store computer-executable instructions; The processor is configured to execute the computer-executable instructions such that the method of claim 4 or 5 is performed. Communication equipment.

25. A communication device comprising a processor and a memory, the processor is configured to store computer-executable instructions; The processor is configured to execute the computer-executable instructions such that the method of any one of claims 6 to 11 is performed. Communication equipment.

26. A communication device comprising a logic circuit and an interface, the logic circuit and the interface being coupled together; A communication device, wherein the interface is configured to input and / or output code instructions, and the logic circuit is configured to execute the code instructions so that the method of any one of claims 1 to 3 is performed.

27. A communication device comprising a logic circuit and an interface, the logic circuit and the interface being coupled together; A communication device, wherein the interface is configured to input and / or output code instructions, and the logic circuit is configured to execute the code instructions so that the method according to claim 4 or 5 is performed.

28. A communication device comprising a logic circuit and an interface, the logic circuit and the interface being coupled together; A communications device, wherein the interface is configured to input and / or output code instructions, and the logic circuit is configured to execute the code instructions such that a method according to any one of claims 6 to 11 is performed.

29. 4. A computer-readable storage medium configured to store a computer program, the computer program being configured to, when executed, perform the method of any one of claims 1 to 3.

30. A computer-readable storage medium configured to store a computer program, the computer program being capable of performing the method of claim 4 or 5 when executed.

31. 12. A computer readable storage medium configured to store a computer program which, when executed, performs the method of any one of claims 6 to 11.

Images