Terminal registration method, terminal and network side device

By allowing terminals to register with networks not included in the prohibited network list and receive DC service information during disaster situations, the problem of high signaling overhead in disaster scenarios is solved, ensuring normal terminal service.

CN115209448BActive Publication Date: 2026-02-06VIVO MOBILE COMM CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110383153.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-04-09
Publication Date
2026-02-06
Estimated Expiration
2041-04-09

AI Technical Summary

Technical Problem

In disaster scenarios, terminals may fail to register correctly with prohibited networks, leading to increased signaling overhead and impacting user experience, especially for emergency service forwarding.

Method used

In a disaster situation, the terminal selects a network that is not in the prohibited network list to register with, and receives the registration acceptance information and DC service information sent by the network, instructing it to provide DC services to the service network.

Benefits of technology

This reduces signaling overhead, ensures that terminals can continue to receive services, and improves the user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115209448B_ABST
    Figure CN115209448B_ABST
Patent Text Reader

Abstract

The application discloses a terminal registration method, a terminal and a network side device, and belongs to the technical field of wireless communication. The terminal registration method comprises the following steps: if a first network for providing services for a terminal occurs a DC (disaster condition), the terminal selects a second network, and sends registration request information to the second network, wherein the second network is not in a forbidden network list of the terminal; and the terminal receives registration acceptance information and DC service information sent by the second network, wherein the registration acceptance information is used for indicating that the registration request of the terminal is accepted, and the DC service information is used for indicating that the second network is a network for providing DC services for the first network.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of wireless communication, and particularly relates to a terminal registration method, a terminal and a network side device. BACKGROUND

[0002] When a disaster (e.g., a fire) occurs in a public land mobile network (PLMN), the PLMN can not be able to continue to provide services for a user equipment (UE, also referred to as a terminal). In order to reduce the impact on the UE, if there is another PLMN ready to provide services (such as voice calls and / or mobile data services, etc.) for the UE, the UE can obtain services from the other PLMN when the disaster occurs, so that service interruption is minimized.

[0003] In a non-disaster scenario (i.e., a scenario in which the service PLMN of the UE does not cause the terminal to be unable to provide services due to a disaster), the UE is not allowed to access a forbidden PLMN. However, in order to avoid the UE being unable to obtain service in a disaster scenario and improve the service experience of users, especially for those UEs with emergency service forwarding, the 3GPP system needs to provide a way for the UE to register to the forbidden PLMN of the UE to minimize service interruption of the UE. However, the premise of accessing the forbidden PLMN is that the service PLMN of the UE has DC, and the UE cannot find an allowed PLMN.

[0004] However, for the following scenario:

[0005] PLMN A is a forbidden PLMN of the UE, but has not been added to the forbidden PLMN list of the UE;

[0006] The PLMN D providing services for the UE has DC;

[0007] PLMN A is able to provide DC services for PLMN D when DC occurs.

[0008] Since PLMN A has not been added to the forbidden PLMN list of the UE, the UE considers PLMN A as an allowed PLMN of the UE, and performs selection and registration. When the UE registers to PLMN A, it does not carry any registration information about the DC scenario.

[0009] For this case, the PLMN A processing manner is to reject the registration request of the UE (because the PLMN A is the forbidden PLMN of the UE), then the UE needs to add the PLMN A into the forbidden PLMN list of the UE, and further perform the selection and registration of the PLMN A in the DC scenario, which obviously increases the signaling overhead of the UE and the PLMN A. SUMMARY

[0010] Embodiments of the present application provide a terminal registration method, a terminal and a network side device, which can solve the problem of large signaling overhead of the terminal registration method in the DC scenario.

[0011] In a first aspect, a terminal registration method is provided, comprising:

[0012] If a first network providing services for the terminal occurs a disaster condition DC, the terminal selects a second network, and sends a registration request information to the second network, wherein the second network is not in a forbidden network list of the terminal.

[0013] The terminal receives registration acceptance information and DC service information sent by the second network, wherein the registration acceptance information is used to indicate acceptance of the registration request of the terminal, and the DC service information is used to indicate that the second network is a network providing DC services for the first network.

[0014] In a second aspect, a terminal registration method is provided, comprising:

[0015] A network side device receives a registration request information sent by a terminal.

[0016] If a first network providing services for the terminal occurs a DC, and a second network where the network side device is located is a forbidden network of the terminal, and the second network is a network providing DC roaming services for the first network occurring the DC, the network side device sends registration acceptance information and DC service information to the terminal, wherein the registration acceptance information is used to indicate acceptance of the registration request of the terminal, and the DC service information is used to indicate that the second network is a network providing DC services for the first network.

[0017] In a third aspect, a terminal registration device is provided, comprising:

[0018] A registration module is configured to, if a first network providing services for the terminal occurs a disaster condition DC, select a second network, and send a registration request information to the second network, wherein the second network is not in a forbidden network list of the terminal.

[0019] The first receiving module is configured to receive registration acceptance information and DC service information sent by the second network, wherein the registration acceptance information is used to indicate that the registration request of the terminal is accepted, and the DC service information is used to indicate that the second network is a network providing DC service for the first network.

[0020] In a fourth aspect, a terminal registration apparatus is provided, comprising:

[0021] The first receiving module is configured to receive registration request information sent by the terminal.

[0022] The first sending module is configured to send, to the terminal, registration acceptance information and DC service information if a first network providing service for the terminal has DC, a second network in which a network-side device is located is a forbidden network of the terminal, and the second network is a network providing DC roaming service for the first network having DC, wherein the registration acceptance information is used to indicate that the registration request of the terminal is accepted, and the DC service information is used to indicate that the second network is a network providing DC service for the first network.

[0023] In a fifth aspect, a terminal is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, and the program or instruction, when executed by the processor, implements the steps of the method according to the first aspect.

[0024] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is configured to select a second network if a first network providing service for the terminal has disaster condition (DC), and the communication interface is configured to send, to the second network, registration request information, wherein the second network is not in a forbidden network list of the terminal; and receive registration acceptance information and DC service information sent by the second network, wherein the registration acceptance information is used to indicate that the registration request of the terminal is accepted, and the DC service information is used to indicate that the second network is a network providing DC service for the first network.

[0025] In a seventh aspect, a network-side device is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, and the program or instruction, when executed by the processor, implements the steps of the method according to the second aspect.

[0026] In an eighth aspect, a network-side device is provided, including a processor and a communication interface, wherein the communication interface is configured to receive a registration request message sent by a terminal; if a first network serving the terminal has DC, and a second network where the network-side device is located is a forbidden network of the terminal, and the second network is a network providing DC roaming service for the first network having DC, the network-side device sends a registration acceptance message and DC service information to the terminal.

[0027] In a ninth aspect, a readable storage medium is provided, and the readable storage medium stores a program or instructions, which are executed by a processor to implement the steps of the method according to the first aspect or the steps of the method according to the second aspect.

[0028] In a tenth aspect, a chip is provided, and the chip includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to run a program or instructions to implement the method according to the first aspect or the method according to the second aspect.

[0029] In an eleventh aspect, a computer program / program product is provided, and the computer program / program product is stored in a non-volatile storage medium, and the program / program product is executed by at least one processor to implement the steps of the terminal registration method according to the first aspect or the steps of the terminal registration method according to the second aspect.

[0030] In the embodiments of the present application, after the service network of the terminal has DC, the terminal can be correctly registered in a forbidden network providing DC service for the service network, so that the terminal can continue to obtain services, and the user service experience is improved. BRIEF DESCRIPTION OF DRAWINGS

[0031] Figure 1 A block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0032] Figure 2 A flowchart of a terminal registration method performed by a terminal according to the embodiments of the present application;

[0033] Figure 3 A flowchart of a terminal registration method performed by a network-side device according to the embodiments of the present application;

[0034] Figure 4 A flowchart of a terminal registration method according to the first embodiment of the present application;

[0035] Figure 5 A flowchart of a terminal registration method according to the second embodiment of the present application;

[0036] Figure 6 a flowchart of a terminal registration method of Embodiment Three of the present application;

[0037] Figure 7 a structural diagram of a terminal registration device of Embodiment One of the present application;

[0038] Figure 8 a structural diagram of a terminal registration device of Embodiment Two of the present application;

[0039] Figure 9 a structural diagram of a communication device of the present application;

[0040] Figure 10 a hardware structural diagram of a terminal of the present application. DETAILED DESCRIPTION

[0041] The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of them. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0042] The terms "first", "second", and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second" are generally of a kind, and are not limited to the number of objects, for example, the first object can be one or more. In addition, "and / or" in the specification and claims means at least one of the connected objects, and the character " / " generally represents an "or" relationship between the front and rear associated objects.

[0043] It is worth noting that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied outside the NR system application, such as in a 6th Generation (6G) communication system. th

[0044] Figure 1 ​A block diagram of a wireless communication system to which embodiments of the present application can be applied is shown. The wireless communication system includes a terminal 11 and a network side device 12. The terminal 11 can also be referred to as a terminal device or a user terminal (UE). The terminal 11 can be a terminal side device such as a mobile phone, a tablet personal computer, a laptop computer, a personal digital assistant (PDA), a palm computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), a wearable device, or a vehicle user equipment (VUE). The wearable device includes a smart watch, a bracelet, a headset, glasses, and the like. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network side device 12 can be a base station or a core network. The base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a node B, an evolved node B (eNB), a home node B, a home evolved node B, a WLAN access point, a WiFi node, a transmitting receiving point (TRP), or some other appropriate terminology in the art so long as the same technical effects are achieved. The base station is not limited to a specific technical term.

[0045] The terminal registration method, the terminal, and the network side device provided by the embodiments of the present application are described in detail below in combination with the accompanying drawings and some embodiments and application scenarios.

[0046] The solution idea of the terminal registration method in the embodiments of the present application is as follows: When the terminal's forbidden network has known that the network currently serving the terminal has a DC case, after receiving the registration request sent by the terminal, the terminal's registration process should be performed instead of being directly rejected, and the terminal is instructed that the forbidden network is a network providing DC service for the terminal's serving network.

[0047] That is, the precondition of the terminal registration method in the embodiments of the present application is:

[0048] 1) The network PLMN A that the terminal sends a registration request to is a forbidden network of the UE, but has not been added to the forbidden network list of the terminal; when the serving network PLMN D of the terminal has DC, since the PLMN A has not been added to the forbidden network list of the terminal, the terminal considers the PLMN A as an allowed network of the terminal, preferentially selects the PLMN A, and initiates a registration process to the PLMN A:

[0049] 2) The PLMN D does not have DC, and provides service for the terminal;

[0050] 3) There is a DC service roaming agreement between the PLMN A and the PLMN D, that is, when the PLMN D has DC, the PLMN A can provide DC service for the terminal served by the PLMN D.

[0051] Please refer to Figure 2 The embodiment of the present application provides a terminal registration method, comprising:

[0052] Step 21: If the first network that provides service for the terminal has DC, the terminal selects a second network, and sends registration request information to the second network, wherein the second network is not in the forbidden network list of the terminal.

[0053] The first network and the second network in the embodiment of the present application can be PLMNs.

[0054] Step 22: The terminal receives registration acceptance information and DC service information sent by the second network, wherein the registration acceptance information is used for indicating that the registration request of the terminal is accepted, and the DC service information is used for indicating that the second network is a network that provides DC service for the first network.

[0055] In the embodiment of the present application, when the first network that provides service for the terminal has DC, the terminal can select a second network and register; if the second network is a forbidden network of the terminal and is not in the forbidden network list of the terminal, the second network does not reject the registration of the terminal, but accepts the registration of the terminal and indicates that the terminal provides DC service, so that the terminal can continue to obtain service, and signaling overhead is saved, and user service experience is improved.

[0056] In the embodiment of the present application, optionally, the first network having DC comprises at least one of the following:

[0057] The terminal cannot receive broadcast information of the first network;

[0058] The first network cannot provide service for the terminal;

[0059] The terminal receives the indication information of the DC of the first network.

[0060] The indication information of the DC of the first network can be sent by the first network or the second network.

[0061] In the embodiments of the present application, the registration request information does not carry DC related information, and the DC related information includes at least one of the following: an identifier (such as a PLMN ID) of the first network in which the DC occurs, DC registration indication information, and a registration type being a DC registration type. That is, since the second network is not in the forbidden network list of the terminal, the terminal considers the second network as a network that allows registration, and therefore does not carry DC related information when sending the registration acceptance information to the second network.

[0062] In the embodiments of the present application, the registration request information carries the identifier information of the terminal, and the identifier information is used to indicate that the network providing services for the terminal is the first network.

[0063] In the embodiments of the present application, the DC service information is used to indicate at least one of the following:

[0064] Registration of the terminal in the DC case;

[0065] The second network is a forbidden network of the terminal;

[0066] The second network is a network that provides DC roaming services for the first network in which the DC occurs.

[0067] In an implementation, the DC service information is carried by the registration acceptance message. That is, the registration acceptance message can carry the registration acceptance information and the DC service information. The configuration update command message is a non-access stratum (NAS) message.

[0068] In an implementation, the DC service information is carried by the configuration update command message.

[0069] In the embodiments of the present application, after the terminal receives the DC service information sent by the second network, the terminal further adds the second network to the forbidden network list according to the DC service information.

[0070] Optionally, before the terminal adds the second network into the forbidden network list, the terminal further receives DC release information, wherein the DC release information is used to indicate that the first network has released DC. The DC release message can be sent by the second network, that is, after receiving the DC release information sent by the second network, the terminal adds the second network into the forbidden network list.

[0071] Optionally, the DC release information is carried by at least one of the following information: a deregistration request message and a configuration update command message.

[0072] Optionally, the storage location of the forbidden network list comprises at least one of the following: a mobile equipment (ME) and a universal integrated circuit card (UICC).

[0073] Please refer to Figure 3 The embodiment of the application further provides a terminal registration method, comprising:

[0074] Step 31: The network side device receives the registration request information sent by the terminal.

[0075] Step 32: If DC occurs in the first network providing services for the terminal, and the second network where the network side device is located is the forbidden network of the terminal, and the second network is the network providing DC roaming services for the first network where DC occurs, the network side device sends registration acceptance information and DC service information to the terminal, wherein the registration acceptance information is used to indicate acceptance of the registration request of the terminal, and the DC service information is used to indicate that the second network is the network providing DC services for the first network.

[0076] In the embodiment of the application, when the forbidden network of the terminal receives the registration request sent by the terminal, the terminal is not rejected, but is accepted, and it is indicated that the terminal provides DC services, so that the terminal can continue to obtain services and improve user service experience.

[0077] Optionally, the registration request information does not carry DC related information, and the DC related information comprises at least one of the following: an identifier of the first network where DC occurs, DC registration indication information and a registration type being a DC registration type.

[0078] Optionally, the registration request information carries identifier information of the terminal, and the identifier information is used to indicate that the network providing services for the terminal is the first network, so that the network side device can know that the service network of the terminal is the first network.

[0079] In an embodiment of the present application, the DC service information is used to indicate at least one of the following:

[0080] The registration of the terminal is a registration in a DC condition;

[0081] The second network is a forbidden network of the terminal;

[0082] The second network is a network that provides DC roaming service for the first network in which the DC occurs.

[0083] In an embodiment of the present application, the DC service information is carried by at least one of the following information: a registration acceptance message and a configuration update command message.

[0084] In an embodiment of the present application, the method further comprises: if the first network has released the DC, sending DC release information to the terminal, the DC release information being used to indicate that the first network has released the DC.

[0085] In an embodiment of the present application, the DC release information is carried by at least one of the following information: a deregistration request message and a configuration update command message.

[0086] The terminal registration method of the present application is described below in combination with specific embodiments.

[0087] Embodiment one of the present application:

[0088] When a first network (i.e. PLMN D) that provides service for a terminal (UE) occurs DC, the terminal selects and registers to a forbidden network PLMN A (i.e. a second network) that has not been added to a forbidden PLMN list of the terminal, and the second network accepts the registration request of the terminal.

[0089] Please refer to Figure 4 The terminal registration method of the embodiment of the present application comprises:

[0090] Step 0a. The service network of the terminal, i.e. the first network (PLMN D), occurs DC (disaster condition), and the disaster condition comprises at least one of the following:

[0091] The terminal cannot receive broadcast information of the first network;

[0092] The first network cannot provide service for the terminal;

[0093] The terminal receives indication information that the first network occurs DC.

[0094] Step 0b. The terminal performs PLMN selection, selects to the second network (PLMN A), and the second network (PLMN A) is:

[0095] The forbidden PLMN of the terminal, but has not been added to the forbidden PLMN list of the terminal;

[0096] The second network (PLMN A) is one of the PLMNs in which the first network (PLMN D) provides DC services in a DC scenario;

[0097] The second network (PLMN A) has obtained the indication information that the first network (PLMN D) has occurred DC.

[0098] Step 1: The terminal sends a registration request message to the AMF of the second network (PLMN A), and the registration request message does not carry DC related information. The registration request message carries the identification information of the terminal, which is used to indicate that the network providing services for the terminal is the first network.

[0099] Step 2: The AMF of the second network (PLMN A) performs the registration process of the terminal based on the indication information that the first network (PLMN D) has occurred DC and the identification information of the terminal, and sends a registration acceptance message to the terminal, wherein the registration acceptance message carries DC service information, and the DC service information is used to indicate the following information:

[0100] The registration of the terminal is the registration in the DC case;

[0101] The second network (PLMN A) is the forbidden network of the terminal;

[0102] The second network (PLMN A) is the network that provides DC roaming services for the first network (PLMN D) that has occurred DC.

[0103] Step 3: The terminal receives the registration acceptance message, adds the second network (PLMN A) to the forbidden PLMN list of the terminal based on the DC service information carried in the registration acceptance message, and the storage location of the forbidden PLMN list includes at least one of the following: ME and UICC.

[0104] Embodiment two of the application:

[0105] The difference between the embodiment of the application and embodiment one is that the DC service information is carried in the configuration update command message.

[0106] Please refer to Figure 5 The terminal registration method of the embodiment of the application comprises:

[0107] Step 0a. A service network of the terminal, "first network (PLMN D)", experiences a DC (disaster condition), which includes at least one of the following:

[0108] The terminal is unable to receive broadcast information of the first network;

[0109] The first network is unable to provide services for the terminal;

[0110] The terminal receives indication information that the first network experiences a DC.

[0111] Step 0b. The terminal performs PLMN selection and selects to a second network (PLMN A), which is:

[0112] A forbidden PLMN of the terminal, but has not yet been added to the forbidden PLMN list of the terminal;

[0113] The second network (PLMN A) is one of the PLMNs that the first network (PLMN D) provides DC services in the DC scenario;

[0114] The second network (PLMN A) has obtained the indication information that the first network (PLMN D) experiences a DC.

[0115] Step 1: The terminal sends a registration request message to the AMF of the second network (PLMN A), which does not carry DC-related information. The registration request message carries the identification information of the terminal, which indicates that the network providing services for the terminal is the first network.

[0116] Step 2: The AMF of the second network (PLMN A) performs the registration process of the terminal based on the indication information that the first network (PLMN D) experiences a DC and the identification information of the terminal, and sends a registration acceptance message to the terminal.

[0117] Step 3: The terminal receives the registration acceptance message.

[0118] Step 4: The AMF of the second network (PLMN A) sends a configuration update command message to the terminal, which carries DC service information indicating the following information:

[0119] The registration of the terminal is a registration under a DC condition;

[0120] The second network (PLMN A) is a forbidden network of the terminal;

[0121] The second network (PLMN A) is a network that provides DC roaming services for the first network (PLMN D) experiencing a DC.

[0122] Step 5: The terminal adds the second network (PLMN A) to the forbidden PLMN list of the terminal based on the DC service information carried in the configuration update command message, and the storage location of the forbidden PLMN list includes at least one of the following: ME and UICC.

[0123] Embodiment three of the present application:

[0124] In the embodiment of the present application, the terminal adds the second network (PLMN A) to the forbidden PLMN list of the terminal based on the DC release information of the first network (PLMN D) sent by the second network (PLMN A).

[0125] Please refer to Figure 6 The terminal registration method of the embodiment of the present application includes:

[0126] Step 0a. The service network of the terminal, i.e. the first network (PLMN D), has a DC (disaster condition), and the disaster condition includes at least one of the following:

[0127] The terminal cannot receive the broadcast information of the first network;

[0128] The first network cannot provide services for the terminal;

[0129] The terminal receives the indication information that the first network has a DC.

[0130] Step 0b. The terminal performs PLMN selection and selects the second network (PLMN A), and the second network (PLMN A) is:

[0131] The forbidden PLMN of the terminal, but has not been added to the forbidden PLMN list of the terminal;

[0132] The second network (PLMN A) is one of the PLMNs that the first network (PLMN D) provides DC services in the DC scenario;

[0133] The second network (PLMN A) has obtained the indication information that the first network (PLMN D) has a DC.

[0134] Step 1: The terminal sends a registration request message to the AMF of the second network (PLMN A), and the registration request message does not carry DC related information. The registration request message carries the identification information of the terminal, and the identification information indicates that the network providing services for the terminal is the first network.

[0135] Step 2: The AMF of the second network (PLMN A) performs a registration process of the terminal based on the indication information that the first network (PLMN D) occurs DC and the identification information of the terminal, and sends a registration acceptance message to the terminal, wherein the DC service information is carried in the registration acceptance message, and the DC service information is used to indicate the following information:

[0136] The registration of the terminal is the registration in the case of DC.

[0137] The second network (PLMN A) is a forbidden network of the terminal.

[0138] The second network (PLMN A) is a network that provides DC roaming service for the first network (PLMN D) that occurs DC.

[0139] Step 3: The second network (PLMN A) obtains the indication information that the first network (PLMN D) is DC released.

[0140] Step 4: The second network (PLMN A) sends DC release information to the terminal.

[0141] Step 5: After receiving the DC release information, the terminal adds the second network (PLMN A) to the forbidden PLMN list of the terminal, and the storage location of the forbidden PLMN list includes at least one of the following: ME and UICC.

[0142] It should be noted that the terminal registration method provided by the embodiment of the application can be executed by a terminal registration device, or a control module in the terminal registration device for executing the terminal registration method. In the embodiment of the application, the terminal registration device executes the terminal registration method as an example to illustrate the terminal registration device provided by the embodiment of the application.

[0143] Please refer to Figure 7 The embodiment of the application further provides a terminal registration device 70, which comprises:

[0144] The registration module 71 is configured to select a second network and send registration request information to the second network if a first network that provides services for the terminal occurs a disaster condition DC, wherein the second network is not in a forbidden network list of the terminal.

[0145] The first receiving module 72 is configured to receive registration acceptance information and DC service information sent by the second network, wherein the registration acceptance information is used to indicate that the registration request of the terminal is accepted, and the DC service information is used to indicate that the second network is a network that provides DC service for the first network.

[0146] In the embodiments of the present application, when the first network providing services for the terminal has DC, the second network can be selected and registered. If the second network is a forbidden network of the terminal and is not in the forbidden network list of the terminal, the second network does not reject the registration of the terminal, but accepts the registration of the terminal and indicates that the terminal provides DC services, so that the terminal can continue to obtain services, signaling overhead is saved, and user service experience is improved.

[0147] In the embodiments of the present application, optionally, the registration request information does not carry DC related information, and the DC related information includes at least one of the following: an identifier of the first network having DC, DC registration indication information, and a registration type being a DC registration type.

[0148] In the embodiments of the present application, optionally, the registration request information carries identifier information of the terminal, and the identifier information is used to indicate that the network providing services for the terminal is the first network.

[0149] In the embodiments of the present application, optionally, the DC service information is used to indicate at least one of the following:

[0150] Registration of the terminal under the DC condition;

[0151] The second network is a forbidden network of the terminal;

[0152] The second network is a network providing DC roaming services for the first network having DC.

[0153] In the embodiments of the present application, optionally, the DC service information is carried through at least one of the following information: a registration acceptance message and a configuration update command message.

[0154] In the embodiments of the present application, optionally, the terminal registration device 70 further includes:

[0155] The adding module is configured to add the second network to the forbidden network list according to the DC service information.

[0156] In the embodiments of the present application, optionally, the terminal registration device 70 further includes:

[0157] The second receiving module is configured to receive DC release information, and the DC release information is used to indicate that the first network has released DC.

[0158] The adding module is configured to add the second network to the forbidden network list according to the DC service information after the second receiving module receives the DC contact information.

[0159] Optionally, the DC release information is carried by at least one of the following information: a de-registration request message and a configuration update command message.

[0160] The terminal registration apparatus in the embodiments of the present application can be an apparatus, an apparatus with an operating system, or an electronic device, and can also be a component in a terminal, an integrated circuit, or a chip. The apparatus or the electronic device can be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal can include, but is not limited to, the types of the terminal 11 listed above, and the non-mobile terminal can be a server, a Network Attached Storage (NAS), a personal computer (PC), a television (TV), a cashier machine, a self-service machine, or the like, and the embodiments of the present application are not limited thereto.

[0161] The terminal registration apparatus provided in the embodiments of the present application can implement the various processes of the method embodiments and achieve the same technical effects, and thus, details are not repeated here. Figure 2 The terminal registration apparatus provided in the embodiments of the present application can implement the various processes of the method embodiments and achieve the same technical effects, and thus, details are not repeated here.

[0162] Please refer to Figure 8 The embodiments of the present application further provide a terminal registration apparatus 80, which comprises:

[0163] A first receiving module 81 is configured to receive registration request information sent by a terminal.

[0164] A first sending module 82 is configured to send, to the terminal, registration acceptance information and DC service information if a first network serving the terminal has DC, a second network in which a network-side device is located is a forbidden network of the terminal, and the second network is a network providing DC roaming service for the first network having DC, wherein the registration acceptance information is used to indicate acceptance of the registration request of the terminal, and the DC service information is used to indicate that the second network is a network providing DC service for the first network.

[0165] In the embodiments of the present application, when a forbidden network of a terminal receives registration request information sent by the terminal, the terminal is not rejected, but is accepted, and it is indicated that the terminal provides DC service, so that the terminal can continue to obtain service and improve user service experience.

[0166] Optionally, in the embodiments of the present application, the registration request information carries identification information of the terminal, and the identification information is used to indicate that the network serving the terminal is the first network.

[0167] Optionally, in the embodiments of the present application, the DC service information is used to indicate at least one of the following:

[0168] The registration of the terminal is a registration in a DC case;

[0169] The second network is a forbidden network of the terminal;

[0170] The second network is a network providing a DC roaming service for the first network in which the DC occurs.

[0171] In the embodiments of the present application, optionally, the DC service information is carried by at least one of the following information: a registration accept message and a configuration update command message.

[0172] In the embodiments of the present application, optionally, the terminal registration device 80 further comprises:

[0173] The second sending module is configured to send DC release information to the terminal if the first network has released the DC, wherein the DC release information is used to indicate that the first network has released the DC.

[0174] In the embodiments of the present application, optionally, the DC release information is carried by at least one of the following information: a deregistration request message and a configuration update command message.

[0175] The terminal registration device provided by the embodiments of the present application can realize each process of the method embodiments and achieve the same technical effects. To avoid repetition, details are not described herein. Figure 3

[0176] As shown in Figure 9 The embodiments of the present application also provide a communication device 90, which comprises a processor 91, a memory 92, a program or instruction stored in the memory 92 and executable on the processor 91. For example, when the communication device 90 is a terminal, the program or instruction is executed by the processor 91 to realize each process of the terminal registration method embodiments executed by the terminal and achieve the same technical effects. When the communication device 90 is a network side device, the program or instruction is executed by the processor 91 to realize each process of the terminal registration method embodiments executed by the network side device and achieve the same technical effects. To avoid repetition, details are not described herein.

[0177] ​The terminal provided in the embodiments of the present application also includes a processor and a communication interface, wherein the processor is configured to select a second network if a first network providing service for the terminal occurs a disaster condition (DC), and the communication interface is configured to send registration request information to the second network, wherein the second network is not in a forbidden network list of the terminal; receive registration acceptance information and DC service information sent by the second network, wherein the registration acceptance information is used to indicate acceptance of the registration request of the terminal, and the DC service information is used to indicate that the second network is a network providing DC service for the first network. The terminal embodiment corresponds to the terminal side method embodiment described above, and each implementation process and implementation manner of the method embodiment can be applied to the terminal embodiment and achieve the same technical effects. Specifically, Figure 10 A hardware structure diagram of a terminal according to an embodiment of the present application.

[0178] The terminal 100 includes, but is not limited to, at least part of components such as a radio frequency unit 101, a network module 102, an audio output unit 103, an input unit 104, a sensor 105, a display unit 106, a user input unit 107, an interface unit 108, a memory 109, and a processor 1010.

[0179] Those skilled in the art can understand that the terminal 100 can also include a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected to the processor 1010 through a power management system, so as to realize functions such as management of charging, discharging, and power consumption management through the power management system. Figure 10 The terminal structure shown in the above figure does not constitute a limitation on the terminal, and the terminal can include more or fewer components than the figure, or combine certain components, or different component arrangements, which are not described here.

[0180] It should be understood that in the embodiments of the present application, the input unit 104 can include a graphics processing unit (GPU) 1041 and a microphone 1042. The graphics processing unit 1041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 106 can include a display panel 1061, which can be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also called a touch screen. The touch panel 1071 can include two parts of a touch detection device and a touch controller. The other input devices 1072 can include, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), a trackball, a mouse, a joystick, etc., which are not described here.

[0181] In the embodiments of the present application, the radio frequency unit 101 receives the downlink data from the network side device, and sends the data to the processor 1010 for processing. In addition, the radio frequency unit 101 sends the uplink data to the network side device. Generally, the radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0182] The memory 109 can be used to store software programs or instructions and various data. The memory 109 can mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, application programs or instructions required by at least one function (such as a sound playing function, an image playing function, etc.), etc. In addition, the memory 109 can include a high-speed random access memory, and can also include a non-volatile memory, which can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. For example, at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state memory device.

[0183] The processor 1010 can include one or more processing units; optionally, the processor 1010 can integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communication, such as a baseband processor. It can be understood that the above-mentioned modem processor can also not be integrated into the processor 1010.

[0184] The processor 1010 is configured to provide a disaster condition DC of a first network of the service, and select a second network by the terminal.

[0185] The radio frequency unit 101 is configured to send registration request information to the second network, wherein the second network is not in a forbidden network list of the terminal; and receive registration acceptance information and DC service information sent by the second network, wherein the registration acceptance information is used to indicate that the registration request of the terminal is accepted, and the DC service information is used to indicate that the second network is a network providing DC service for the first network.

[0186] In the embodiments of the present application, when the first network providing services for the terminal occurs DC, the terminal can select the second network and register, if the second network is the forbidden network of the terminal and is not in the forbidden network list of the terminal, the second network does not reject the registration of the terminal, but accepts the registration of the terminal and indicates that the terminal provides DC services, so that the terminal can continue to obtain services, and signaling overhead is saved, and user service experience is improved.

[0187] Optionally, the DC of the first network comprises at least one of the following:

[0188] The terminal cannot receive broadcast information of the first network;

[0189] The first network cannot provide services for the terminal;

[0190] The terminal receives the indication information of the DC of the first network.

[0191] Optionally, the registration request information does not carry DC related information, and the DC related information comprises at least one of the following: an identifier of the first network which occurs DC, DC registration indication information and a registration type which is a DC registration type.

[0192] Optionally, the registration request information carries identifier information of the terminal, and the identifier information is used to indicate that the network providing services for the terminal is the first network.

[0193] Optionally, the DC service information is used to indicate at least one of the following:

[0194] Registration of the terminal in the case of DC;

[0195] The second network is the forbidden network of the terminal;

[0196] The second network is a network providing DC roaming services for the first network which occurs DC.

[0197] Optionally, the DC service information is carried by at least one of the following information: a registration acceptance message and a configuration update command message.

[0198] Optionally, the processor 1010 is further used to add the second network to the forbidden network list according to the DC service information after receiving the DC service information sent by the second network.

[0199] Optionally, the processor 1010 is further used to receive DC release information before adding the second network to the forbidden network list, and the DC release information is used to indicate that the first network has released DC.

[0200] Optionally, the DC release information is carried by at least one of the following information: a de-registration request message and a configuration update command message.

[0201] Optionally, the storage location of the forbidden network list comprises at least one of the following: a mobile equipment (ME) and a universal integrated circuit card (UICC).

[0202] The embodiment of the present application further provides a network side device, comprising a processor and a communication interface, the communication interface is used for receiving registration request information sent by a terminal; if a first network serving the terminal occurs DC, and a second network where the network side device is located is a forbidden network of the terminal, and the second network is a network providing DC roaming service for the first network where DC occurs, the network side device sends registration acceptance information and DC service information to the terminal, wherein the registration acceptance information is used for indicating acceptance of the registration request of the terminal, and the DC service information is used for indicating that the second network is a network providing DC service for the first network. The network side device embodiment is corresponding to the network side device method embodiment described above, each implementation process and implementation manner of the method embodiment described above can be applied to the network side device embodiment, and the same technical effects can be achieved.

[0203] The embodiment of the present application further provides a readable storage medium, the readable storage medium stores a program or instructions, the program or instructions are executed by a processor to realize each process of the terminal registration method embodiment described above, and the same technical effects can be achieved, to avoid repetition, which will not be repeated here.

[0204] The processor is the processor in the terminal in the embodiment described above. The readable storage medium comprises a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0205] The embodiment of the present application further provides a chip, the chip comprises a processor and a communication interface, the communication interface and the processor are coupled, the processor is used for running a program or instructions to realize each process of the terminal registration method embodiment described above, and the same technical effects can be achieved, to avoid repetition, which will not be repeated here.

[0206] It should be understood that the chip mentioned in the embodiment of the present application can also be referred to as a system level chip, a system chip, a chip system or a system on chip, etc.

[0207] It should be noted that, in the present document, the terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises... a" does not, without more constraints, exclude the presence of additional identical elements in the process, method, article, or apparatus that comprises the element. Furthermore, it is to be understood that the method and apparatus of the present application can be carried out by more than one process, method, article, or apparatus either simultaneously, concurrently, or with intervening action that are carried out at the same time, in any order, or in an overlapping manner. For example, the described method can be performed in a different order or simultaneously, and the various steps can be combined or omitted, or additional steps can be added, without departing from the scope of the described method. Also, features described with respect to certain examples can be combined in other examples.

[0208] From the above description of the embodiments, it is apparent that the above-described method can be implemented by software and necessary universal hardware platform, of course, it can also be implemented by hardware, but in many cases, the former is a better implementation. Based on such understanding, the technical solutions of the present application can be embodied in the form of computer software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a plurality of instructions for making a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) execute the method described in various embodiments of the present application.

[0209] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-described specific embodiments, which are merely illustrative rather than restrictive, and those of ordinary skill in the art can make many forms under the inspiration of the present application without departing from the scope of the present application and the scope protected by the claims.

Claims

1. A terminal registration method characterized by comprising: Comprising: If a first network providing service for a terminal occurs a disaster condition (DC), the terminal selects a second network and sends a registration request information to the second network, wherein the second network is a forbidden network of the terminal but has not been added into a forbidden network list of the terminal; The terminal receives registration acceptance information and DC service information sent by the second network, wherein the registration acceptance information is used for indicating acceptance of the registration request of the terminal, and the DC service information is used for indicating that the second network is a network providing DC service for the first network; After the terminal receives the DC service information sent by the second network, the terminal further comprises: The terminal adds the second network into the forbidden network list according to the DC service information.

2. The method of claim 1, wherein, The first network occurs DC comprises at least one of the following: The terminal cannot receive broadcast information of the first network; The first network cannot provide service for the terminal; The terminal receives indication information that the first network occurs DC.

3. The method of claim 1, wherein, The registration request information does not carry DC related information, and the DC related information comprises at least one of the following: an identifier of the first network occurring DC, DC registration indication information and a registration type being a DC registration type.

4. The method of claim 1, wherein, The registration request information carries identifier information of the terminal, and the identifier information is used for indicating that a network providing service for the terminal is the first network.

5. The method of claim 1, wherein, The DC service information is used for indicating at least one of the following: Registration of the terminal in a DC case; The second network is a forbidden network of the terminal; The second network is a network providing DC roaming service for the first network occurring DC.

6. The method of claim 1, wherein, The DC service information is carried by at least one of the following information: registration acceptance message and configuration update command message.

7. The method of claim 1, wherein, Before the terminal adds the second network into the forbidden network list, the terminal further comprises: Receiving DC release information, wherein the DC release information is used for indicating that the first network has released DC.

8. The method of claim 7, wherein, The DC release information is carried by at least one of the following information: deregistration request message and configuration update command message.

9. The method of claim 1, wherein, The storage location of the forbidden network list comprises at least one of the following: mobile equipment (ME) and universal integrated circuit card (UICC).

10. A terminal registration method characterized by comprising: Comprising: A network side device receives registration request information sent by a terminal; If a first network providing service for the terminal occurs a disaster condition (DC), and a second network where the network side device is located is a forbidden network of the terminal but has not been added into a forbidden network list of the terminal, and the second network is a network providing DC roaming service for the first network occurring DC, the network side device sends registration acceptance information and DC service information to the terminal, wherein the registration acceptance information is used for indicating acceptance of the registration request of the terminal, and the DC service information is used for indicating that the second network is a network providing DC service for the first network, so that the terminal adds the second network into the forbidden network list according to the DC service information.

11. The method of claim 10, wherein, The registration request information does not carry DC related information, and the DC related information includes at least one of the following: an identifier of the first network in which the DC occurs, DC registration indication information, and a registration type being a DC registration type.

12. The method of claim 10, wherein, The registration request information carries identifier information of the terminal, and the identifier information is used to indicate that the network providing services for the terminal is the first network.

13. The method of claim 10, wherein, The DC service information is used to indicate at least one of the following: The registration of the terminal is a registration in a DC case; The second network is a forbidden network of the terminal; The second network is a network providing DC roaming services for the first network in which the DC occurs.

14. The method of claim 10, wherein, The DC service information is carried by at least one of the following information: a registration acceptance message and a configuration update command message.

15. The method of claim 10, wherein, Further comprising: If the first network has released the DC, DC release information is sent to the terminal, and the DC release information is used to indicate that the first network has released the DC.

16. The method of claim 15, wherein, The DC release information is carried by at least one of the following information: a deregistration request message and a configuration update command message.

17. A terminal registration apparatus characterized by comprising: Comprising: A registration module, configured to select a second network and send registration request information to the second network if a first network providing services for a terminal has a disaster condition DC, wherein the second network is a forbidden network of the terminal but has not been added to a forbidden network list of the terminal; A first receiving module, configured to receive registration acceptance information and DC service information sent by the second network, wherein the registration acceptance information is used to indicate acceptance of the registration request of the terminal, and the DC service information is used to indicate that the second network is a network providing DC services for the first network; The terminal registration apparatus further comprises: An adding module, configured to add the second network to the forbidden network list according to the DC service information.

18. The apparatus of claim 17, wherein, The registration request information does not carry DC related information, and the DC related information includes at least one of the following: an identifier of the first network in which the DC occurs, DC registration indication information, and a registration type being a DC registration type.

19. The apparatus of claim 17, wherein, The registration request information carries identifier information of the terminal, and the identifier information is used to indicate that the network providing services for the terminal is the first network.

20. The apparatus of claim 17, wherein, The DC service information is used to indicate at least one of the following: The registration of the terminal is a registration in a DC case; The second network is a forbidden network of the terminal; The second network is a network providing DC roaming services for the first network in which the DC occurs.

21. The apparatus of claim 17, wherein, The DC service information is carried by at least one of the following information: a registration acceptance message and a configuration update command message.

22. The apparatus of claim 17, wherein, Further comprising: A second receiving module, configured to receive DC release information, and the DC release information is used to indicate that the first network has released the DC; The adding module is configured to add the second network to the forbidden network list according to the DC service information after the second receiving module receives the DC release information.

23. The apparatus of claim 22, wherein, The DC release information is carried by at least one of the following information: a deregistration request message and a configuration update command message.

24. A terminal registration apparatus characterized by comprising: Comprising: The first receiving module is configured to receive registration request information sent by a terminal. The first sending module is configured to send, to the terminal, registration acceptance information and DC service information, if DC occurs in a first network providing services for the terminal, a second network in which a network-side device is located is a forbidden network of the terminal but has not been added to a forbidden network list of the terminal, and the second network is a network providing DC roaming services for the first network in which DC occurs, wherein the registration acceptance information is used to indicate acceptance of the registration request of the terminal, and the DC service information is used to indicate that the second network is a network providing DC services for the first network, so that the terminal adds the second network to the forbidden network list according to the DC service information.

25. The apparatus of claim 24, wherein, The registration request information carries identification information of the terminal, and the identification information is used to indicate that the network providing services for the terminal is the first network.

26. The apparatus of claim 24, wherein, The DC service information is used to indicate at least one of the following: Registration of the terminal in a DC case; The second network is a forbidden network of the terminal; The second network is a network providing DC roaming services for the first network in which DC occurs.

27. The apparatus of claim 24, wherein, The DC service information is carried by at least one of the following information: registration acceptance information and configuration update command information.

28. The apparatus of claim 24, wherein, Further comprising: The second sending module is configured to send, to the terminal, DC release information indicating that the first network has released DC, if the first network has released DC.

29. The apparatus of claim 28, wherein, The DC release information is carried by at least one of the following information: deregistration request information and configuration update command information.

30. A terminal, characterized by The terminal comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, and the program or instruction is executed by the processor to implement the steps of the terminal registration method according to any one of claims 1 to 8.

31. A network-side device, comprising: The terminal comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, and the program or instruction is executed by the processor to implement the steps of the terminal registration method according to any one of claims 9 to 16.

32. A readable storage medium, characterized by, The readable storage medium stores a program or instruction, and the program or instruction is executed by the processor to implement the steps of the terminal registration method according to any one of claims 1 to 8, or implement the steps of the terminal registration method according to any one of claims 9 to 16.