Method, device, terminal equipment and network equipment for accessing network

Abstract

The present application discloses a method, apparatus, terminal device and network device for accessing a network, the method comprising: when the first network device initially accessed by the user device cannot provide network services due to a target reason, accessing a second network device; when the target reason is eliminated, accessing a target network device; the target network device comprises at least one of the following: the first network device; a third network device, the third network device being a currently available network device with the highest priority; the second network device, when the user device has no available and permitted network, the target network device is the second network device, which can avoid the first network device resources being idle and the second network device network resources being in short supply when the reason causing the first network device to be unable to provide network services is eliminated.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of communications, and in particular to a method, an apparatus, a terminal device and a network device for accessing a network. Background Art

[0002] In the New Radio (NR), a terminal, which may also be referred to as a terminal device or a user equipment (UE), initially accesses a first network device. However, when the first network device cannot provide network services due to some reasons, such as a transmission disaster, the UE may access a second network device and receive network services at the second network device.

[0003] At this time, if the reason why the first network device cannot provide network services is eliminated, the UE may still access the second network device, and the second network device may continue to provide network services to the terminal, resulting in the first network device resources being idle and the second network device's network resources being in short supply. Summary of the invention

[0004] The embodiments of the present application provide a method, apparatus, terminal device and network device for accessing a network, which can solve the problem that the resources of a first network device are idle while the network resources of a second network device are in short supply.

[0005] In a first aspect, a method for accessing a network is provided, which is performed by a user device, comprising: when a first network device initially accessed by the user device cannot provide network services due to a target reason, accessing a second network device; when the target reason is eliminated, accessing a target network device; the target network device comprises at least one of the following: the first network device; a third network device, the third network device being a currently available network device with the highest priority; the second network device, and when the user device has no available and allowed network, the target network device is the second network device.

[0006] According to a second aspect, a method for accessing a network is provided, which is executed by a target network device, and includes: receiving an access request sent by a user device, wherein the access request is sent by the user device when a target reason is excluded, and the target reason is that a first network device initially accessed by the user device cannot provide network services; executing an access process of the user device; the target network device includes at least one of the following: the first network device; a third network device, the third network device is a currently available network device with the highest priority; and a second network device, when the user device has no available and allowed network, the target network device is the second network device, and the second network device is a network device accessed by the user device when the first network device cannot provide network services due to the target reason.

[0007] According to a third aspect, a device for accessing a network is provided, comprising: a first access module, for accessing a second network device when the first network device initially accessed by the user device cannot provide network services due to a target reason; a second processing module, for accessing a target network device when the target reason is eliminated; the target network device comprises at least one of the following: the first network device; a third network device, the third network device being the currently available network device with the highest priority; the second network device, the target network device being the second network device when the user device has no available and allowed network.

[0008] In a fourth aspect, a device for accessing a network is provided, comprising: a second access module, for receiving an access request sent by a user device, wherein the access request is sent by the user device when a target cause is excluded, and the target cause is the reason why a first network device initially accessed by the user device cannot provide network services; a second processing module, for executing an access process of the user device; the target network device comprises at least one of the following: the first network device; a third network device, the third network device being a currently available network device with the highest priority; a second network device, when the user device has no available and allowed network, the target network device is the second network device, and the second network device is a network device accessed by the user device when the first network device cannot provide network services due to the target cause.

[0009] In a fifth aspect, a terminal device is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

[0010] In a sixth aspect, a network device is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the second aspect.

[0011] In a seventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0012] In an eighth aspect, a computer program product is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect or the second aspect.

[0013] In a ninth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect or the second aspect.

[0014] The embodiments of the present invention provide a method, apparatus, terminal device and network device for accessing a network. When the first network device initially accessed by the user device cannot provide network services due to a target reason, the user device accesses a second network device; when the target reason is eliminated, the user device accesses a target network device; the target network device includes at least one of the following: the first network device; a third network device, the third network device is a currently available network device with the highest priority; the second network device, when the user device has no available and permitted network, the target network device is the second network device, and when the reason causing the first network device to be unable to provide network services is eliminated, the user device can access the first network device initially accessed to avoid the first network device resources being idle while the second network device network resources are in short supply, or access the third network device currently available with the highest priority to avoid the first network device resources being idle while the second network device network resources are in short supply while enjoying better network services, or access the second device when the user device has no available and permitted network, at this time, the first network device is unavailable, thereby avoiding waste of its resources, and ensuring that the user device can obtain normal network services. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0016] Figure 1 A schematic diagram of a wireless communication system to which an embodiment of the present application can be applied is shown.

[0017] Figure 2 is a schematic flow chart of a method for accessing a network according to an embodiment of the present invention;

[0018] Figure 3 is a schematic flow chart of a method for accessing a network according to another embodiment of the present invention;

[0019] Figure 4 is a schematic flow chart of a method for accessing a network according to another embodiment of the present invention;

[0020] Figure 5 is a schematic flow chart of a method for accessing a network according to another embodiment of the present invention;

[0021] Figure 6 is a schematic flow chart of a method for accessing a network according to another embodiment of the present invention;

[0022] Figure 7 is a schematic diagram of the structure of a device for accessing a network according to an embodiment of the present invention;

[0023] Figure 8 is a schematic diagram of the structure of a device for accessing a network according to an embodiment of the present invention;

[0024] Fig. 9 is a schematic diagram of the structure of a network device according to another embodiment of the present invention;

[0025] Fig.10 is a schematic structural diagram of a terminal device according to another embodiment of the present invention. DETAILED DESCRIPTION

[0026] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0027] The terms "first", "second", etc. 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 interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.

[0028] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, 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 for the systems and radio technologies mentioned above as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for illustrative purposes, and the NR terminology is used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.

[0029] Figure 1A schematic diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11, a first network side device 12, and a second network side device 13. Among them, the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal side devices, and the wearable device includes: a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The first network side device 12 and the second network side device 13 can be a base station or a core network, wherein the base station can be called a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0030] The following describes in detail the method for accessing a network provided by the embodiment of the present application through specific embodiments and application scenarios in conjunction with the accompanying drawings.

[0031] like Figure 2 As shown, an embodiment of the present invention provides a method 200 for accessing a network, which can be performed by a terminal device and / or a network device. In other words, the method can be performed by software or hardware installed in the terminal device and / or the network device. The method includes the following steps:

[0032] S202: When the first network device initially accessed by the user equipment cannot provide network services due to target reasons, access a second network device.

[0033] When the first network device cannot provide network services due to target reasons, the UE can access the second network device and receive network services at the second network device.

[0034] The first network may be the UE's Home PLMN (Home PLMN, HPLMN), Equivalent HPLMN list (EHPLMN), or Visited PLMN (VPLMN); the second network may be the UE's forbidden Public Land Mobile Network (Public Land Mobile Network, PLMN) or a non-forbidden PLMN.

[0035] The UE receives network services and performs services on the second network. In a possible implementation, the UE accesses the second network device, but disables the equivalent network information of the second network device. For example, all equivalent network information of the second network device is disabled; or part of the equivalent network information of the second network device is disabled; or part of the equivalent network information of the second network device is used, that is, part of the equivalent network information of the second network device is disabled but another part of the equivalent network information of the second network device is used.

[0036] In a possible implementation manner, the second network device does not send the equivalent network information of the second network device to the UE.

[0037] In another possible implementation manner, the second network device may send equivalent network information of the second network device to the UE, but the UE may perform at least one of the following steps:

[0038] Do not save and / or disable the information.

[0039] The second network device shall not be added to the equivalent network information (the UE shall not add to the stored list the PLMN code of the registered PLMN that sent the list).

[0040] Save and / or select available networks, where the available networks are networks available in disaster situations; if there are some networks in the equivalent networks, and these networks are also in the "List of PLMNs to be used while in Disaster condition", then the UE can save these networks and / or select these networks.

[0041] The equivalent network information is retained in the forbidden network information list. For the equivalent network information, the network information shall not be deleted from the list of any PLMN code that is already in the forbidden PLMN list as specified in subclause 5.3.13A.

[0042] The above steps prevent the UE from thinking that the equivalent network of the second network (eg, EPLMN) can also provide services to the UE when a disaster occurs in the first network.

[0043] S204: When the target cause is eliminated, access the target network device.

[0044] For example, the target cause may include a disaster (Disaster Condition, DC) occurring to the first network device. When the user device has left the disaster area (the region where Disaster Condition applies, or Disaster Condition roaming service allowed area), the target cause is considered to be eliminated and the target network device can be accessed.

[0045] The target network device includes at least one of the following:

[0046] The first network device is the network device that the user equipment initially accesses before accessing the second network device. The UE searches for and registers with the first network, or its equivalent network, such as EPLMN, or returns to the network selection mode and the network at that time before the disaster. Therefore, when the target cause is eliminated, the UE re-accesses the first network device, receives the network service of the first network device, releases the resources of the second network device, and avoids the idleness of the resources of the first network device and the tight use of the network resources of the second network device.

[0047] The third network device is a currently available network device with the highest priority. The UE enters the automatic network selection mode to select the currently available network device with the highest priority. The third network device may be the first network device or the second network device, or may be other network devices except the first network device and the second network device.

[0048] The second network device, when the user equipment has no available and allowed network, the target network device is the second network device. If the UE has no available and allowed PLMN in the area, and cannot use any other method to determine whether there is a PLMN with a higher priority than the currently selected PLMN, and there is no other network that can provide services when a disaster occurs in the first network, then the UE remains on the second network device. At this time, there is no waste of resources because the first network device is unavailable, and there is no other available network. In order to ensure the network service of the UE, the UE continues to reside in the second network to ensure that the user equipment can obtain normal network services.

[0049] A method for accessing a network provided by an embodiment of the present invention includes: when a first network device initially accessed by a user device cannot provide network services due to a target reason, accessing a second network device; when the target reason is eliminated, accessing a target network device; the target network device includes at least one of the following: the first network device; a third network device, the third network device is a currently available network device with the highest priority; the second network device, when the user device has no available and permitted network, the target network device is the second network device, and when the reason causing the first network device to be unable to provide network services is eliminated, the user device can access the first network device initially accessed to avoid the first network device resources being idle while the second network device's network resources are in short supply, or access the third network device currently available with the highest priority to avoid the first network device resources being idle while the second network device's network resources are in short supply while enjoying better network services, or access the second device when the user device has no available and permitted network, at this time, since the first network device is unavailable, its resources are avoided from being wasted, and it is ensured that the user device can obtain normal network services.

[0050] In a possible implementation, when the target network device is the first network device, the accessing the target network device includes: accessing the first network device according to a stored network duplication value. Specifically, if the UE stores a duplicate value of the RPLMN and a duplicate value of the PLMN selection mode, and these duplicate values ​​are used before PLMN selection is triggered due to a process of minimizing service interruption (Minimization of Service Interruption, MINT) or a process in which the UE registers with the second network due to a disaster in the first network, then return to the stored duplicate PLMN selection mode and use the stored duplicate value of RPLMN if the UE stores a duplicate value of the RPLMN and a duplicate of the PLMN selection mode that were in use beforePLMN selection due to MINT (Minimization of Service Interruption)

[0051] In a possible implementation, when the target network device is the second network device, if the second network device cannot provide the target network service, a limited network service state is maintained on the second network device, for example, a registration rejection message, a deregistration message, a service rejection message (service reject), etc., from the second network device is received.

[0052] like Figure 3 As shown, an embodiment of the present invention provides a method 300 for accessing a network, which can be performed by a terminal device and / or a network device. In other words, the method can be performed by software or hardware installed in the terminal device and / or the network device. The method includes the following steps:

[0053] S302: When the first network device initially accessed by the user equipment cannot provide network services due to target reasons, access a second network device.

[0054] This step can be done using Figure 2 The description of step S202 of the embodiment will not be repeated here.

[0055] S303: Obtain the first message.

[0056] The first message is used to indicate that the user equipment has left the disaster area (Out of the Disaster Region or Out of the Disaster Region Area, or MINT not available), the current network no longer provides normal services due to the MINT, or the current network no longer provides normal services due to a disaster in the first network. Optionally, the first message can use a reserved bit field or a newly added bit field.

[0057] The first message may be sent by any one of the first network device, the second network device, and the third network device.

[0058] The first message includes at least one of the following: satellite positioning information; wireless fidelity (WIFI) positioning information; and Bluetooth positioning information. The UE uses the positioning information to determine that the user equipment has left the disaster area.

[0059] The first message includes at least one of the following: a non-access stratum (NAS) message, an access stratum AS message, and an air interface message.

[0060] The NAS message carries a first cause value, and the first cause value indicates that the second network device no longer provides services due to a disaster of the first network device. In one implementation, the NAS message includes at least one of the following: a registration message, a message of a service request process, a NAS direct transfer message, and a deregistration message.

[0061] Specifically, in one implementation, the UE sends an uplink NAS message, such as a mobility registration request; the network rejects the UE's registration request, carrying a rejection reason or a certain information element, and the rejection reason or the certain information element indicates that the UE has left the disaster area.

[0062] In another implementation, the second network device finds that the UE has left the disaster area, and sends a downlink NAS message to the UE, such as a deregistration request message, carrying a reason or a certain information element, where the reason or the certain information element indicates that the UE has left the disaster area.

[0063] An access layer AS message, the AS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device. In one implementation, the AS message includes at least one of the following: a connection establishment rejection message, a release message, and a system message.

[0064] Specifically, in one implementation, the UE sends an uplink AS message, such as a connection request; the second network device rejects the UE's connection request and carries a rejection reason or a certain information element, which indicates that the UE has left the disaster area.

[0065] In another implementation, the second network device finds that the UE has left the disaster area, and sends a downlink AS message to the UE, such as a connection release message, carrying a reason or a certain information element, where the reason or the certain information element indicates that the UE has left the disaster area.

[0066] An air interface message, where the air interface message is used to indicate a second cause value, where the second cause value includes at least one of the following:

[0067] Disable PLMN (PLMN not allowed);

[0068] Disable tracking area (Tracking area not allowed);

[0069] Disable roaming in the target tracking area (Roaming not allowed in this tracking area);

[0070] There are no suitable cells in the tracking area.

[0071] Serving network not authorized.

[0072] The content of the first reason value and / or the second reason value may be, for example:

[0073]

[0074] and / or

[0075]

[0076] S304: When the target cause is eliminated, access the target network device.

[0077] This step can be done using Figure 2 The description of step S204 of the embodiment will not be repeated here.

[0078] A method for accessing a network provided by an embodiment of the present invention includes: when a first network device initially accessed by a user device cannot provide network services due to a target reason, accessing a second network device; when the target reason is eliminated, accessing a target network device; the target network device includes at least one of the following: the first network device; a third network device, the third network device is a currently available network device with the highest priority; the second network device, when the user device has no available and permitted network, the target network device is the second network device, and when the reason causing the first network device to be unable to provide network services is eliminated, the user device can access the first network device initially accessed to avoid the first network device resources being idle while the second network device's network resources are in short supply, or access the third network device currently available with the highest priority to avoid the first network device resources being idle while the second network device's network resources are in short supply while enjoying better network services, or access the second device when the user device has no available and permitted network, at this time, since the first network device is unavailable, its resources are avoided from being wasted, and it is ensured that the user device can obtain normal network services.

[0079] like Figure 4 As shown, an embodiment of the present invention provides a method 400 for accessing a network, which can be performed by a terminal device and / or a network device. In other words, the method can be performed by software or hardware installed in the terminal device and / or the network device. The method includes the following steps:

[0080] S402: When the first network device initially accessed by the user equipment cannot provide network services due to target reasons, access a second network device.

[0081] This step can be done using Figure 2 The description of step S202 of the embodiment will not be repeated here.

[0082] S403: Obtain the scope of the disaster area.

[0083] The disaster area range may be obtained from one of the first network device, the second network device and the fourth network device. The fourth device may be a device other than the first network device and the second network device. The fourth device may include the third network device. The fourth device may include a Bluetooth device, a satellite, a television, or other terminal devices.

[0084] The disaster area is an area where one or more network devices are affected by the disaster and cannot provide services. The disaster area includes an area where the first network is affected by the disaster and cannot provide services, and may also include an area where multiple other network devices are affected by the disaster and cannot provide services.

[0085] In one implementation, this step may be: when the user equipment is not in the disaster area, obtaining the range of the disaster area.

[0086] In one implementation, this step may specifically include: when the target reason includes not being in the service area of ​​the first network device, obtaining the disaster area range from the second network device and / or the fourth network device. In other words, if the UE cannot obtain network services from the first network because it is not in the service area of ​​the first network device, the UE may obtain the disaster area range from the second network device and / or the fourth network device.

[0087] In one implementation, this step may specifically include: obtaining the disaster area range through a second message; wherein the second message is sent by one or more of the first network device, the second network device, and the fourth network device. Optionally, the second message may use a reserved bit field or a newly added bit field.

[0088] The second message includes at least one of the following:

[0089] Register to receive messages;

[0090] Registration rejection message;

[0091] Scheduling request acceptance message;

[0092] Scheduling request rejection message;

[0093] Configuration update message;

[0094] Go to register message;

[0095] Session management messages;

[0096] Session rejection message;

[0097] Session release message;

[0098] Short messages;

[0099] User plane data, such as International Mobile Subscriber (IMS) signaling, Hyper Text Transfer Protocol (HTTP) signaling, application data of applications (APP), etc.

[0100] Bluetooth signaling, such as Bluetooth link control instructions; Bluetooth link strategy instructions; Bluetooth test instructions.

[0101] In one implementation, the second message includes at least one of the following:

[0102] The correspondence between the disaster network identification (ID) and the disaster type assignment code (TAC), wherein the disaster network identification is the identification of the network where the disaster occurred. For example:

[0103]

[0104] The correspondence between the disaster network identifier, the disaster type allocation code and the cell, wherein the disaster network identifier is the identifier of the network where the disaster occurs. For example:

[0105]

[0106] The correspondence between the disaster network identifier and the network slice information, wherein the network slice information is such as the Network Slice Selection Assistance Information (NSSAI), and the disaster network identifier is the identifier of the network where the disaster occurred. For example:

[0107]

[0108] Among them, network slice information is as follows:

[0109]

[0110] Single network slice information (Single NSSAI, S-NSSAI) such as:

[0111]

[0112] The correspondence between the disaster network identifier and the data network name (Data Network Name) information, wherein the disaster network identifier is the identifier of the network where the disaster occurred. For example:

[0113]

[0114] DNN data structures such as:

[0115]

[0116] In one implementation, the second message may include at least one of the following:

[0117] The correspondence between the identifier of the network where no disaster has occurred and the tracking area identifier, wherein the tracking area corresponding to the tracking area identifier covers the overlapping area of ​​the network where no disaster has occurred and the disaster area of ​​the network where the disaster has occurred; for example:

[0118]

[0119] a correspondence between an identifier of a network where no disaster has occurred, a tracking area identifier, and a cell identifier, wherein the tracking area corresponding to the tracking area identifier covers an overlapping area between a network where no disaster has occurred and a disaster area of ​​a network where a disaster has occurred, and wherein the cell corresponding to the cell identifier covers an overlapping area between a network where no disaster has occurred and a disaster area of ​​a network where a disaster has occurred;

[0120] a correspondence between an identifier of a network where no disaster has occurred and data network name information, wherein the data network name information indicates a data network that cannot provide services in the network where the disaster has occurred due to the disaster but can provide services in the network where no disaster has occurred;

[0121]

[0122] The correspondence between the identifier of a network where no disaster has occurred and the network slice information, wherein the network slice information indicates a network slice that cannot provide services in a network where a disaster has occurred but can provide services in a network where no disaster has occurred.

[0123] This makes it possible to receive network services through a network where no disaster has occurred and identify a network where a disaster has occurred.

[0124] In one implementation, the second message includes at least one of the following:

[0125] Network identification;

[0126] Tracking area information;

[0127] Geolocation information;

[0128] Community information;

[0129] Network Slice Selection Assistance Information (NSSAI);

[0130] Data Network Name (DNN) information.

[0131] S404: Based on the range of the disaster area, determine whether the user equipment leaves the disaster area.

[0132] Specifically, in one implementation, when a portion of the network where the disaster occurs belongs to the disaster area, it is determined that the user equipment has not left the disaster area.

[0133] In one implementation, when a portion of the network where the disaster occurs does not fall within the scope of the disaster area, it is determined that the user equipment has left the disaster area. For example, if the UE receives the current geographic location information and finds that the current geographic location information does not fall within the "disaster area scope" information, it is considered that the UE has left the disaster area, and the UE can attempt to select and / or access the first network and / or the third network.

[0134] In one implementation, after obtaining the disaster area range through the second message, the method further includes at least one of the following:

[0135] In the case where the second message includes network slice information, the parameter indicated by the network slice is not used to obtain the service; in the case where the second message includes data network name information, the parameter indicated by the data network name information is not used to obtain the protocol data unit session service. In this way, the UE is prevented from attempting to obtain the service in a network where a disaster occurs, which may result in a service acquisition failure.

[0136] S405: When the target cause is eliminated, access the target network device.

[0137] This step can be done using Figure 2 The description of step S204 of the embodiment will not be repeated here.

[0138] A method for accessing a network provided by an embodiment of the present invention includes: when a first network device initially accessed by a user device cannot provide network services due to a target reason, accessing a second network device; when the target reason is eliminated, accessing a target network device; the target network device includes at least one of the following: the first network device; a third network device, the third network device is a currently available network device with the highest priority; the second network device, when the user device has no available and permitted network, the target network device is the second network device, and when the reason causing the first network device to be unable to provide network services is eliminated, the user device can access the first network device initially accessed to avoid the first network device resources being idle while the second network device's network resources are in short supply, or access the third network device currently available with the highest priority to avoid the first network device resources being idle while the second network device's network resources are in short supply while enjoying better network services, or access the second device when the user device has no available and permitted network, at this time, since the first network device is unavailable, its resources are avoided from being wasted, and it is ensured that the user device can obtain normal network services.

[0139] Several examples are given below to exemplarily illustrate a method for accessing a network provided by an embodiment of the present invention.

[0140] Example 1

[0141] In step S402, a disaster occurs in a first network device to which the user equipment initially accesses.

[0142] In step S403, the UE obtains the disaster area range from the first network, such as a tracking area (TA), a TA list, or longitude and latitude, for example, through a registration acceptance / rejection, a scheduling request (SR) acceptance / rejection, a configuration update message, or a deregistration message of the first network.

[0143] In one implementation, when the UE obtains the disaster area range from the first network, it may not be in the disaster area. For example, in an area of ​​the first network where no disaster has occurred, the UE receives a notification from the first network that a disaster has occurred in a certain area. The UE can access the second network when entering the disaster area.

[0144] In another implementation, when the UE obtains the range of the disaster area from the first network, the UE may be notified in the disaster area, for example, when a disaster occurs in the first network, that the UE is in the disaster area and the range of the disaster area.

[0145] In step S402, the UE leaves the disaster network, ie, the first network, and accesses the second network.

[0146] The UE can obtain the coverage of the first network where the disaster occurs, such as the TA area, or the longitude and latitude, from the second network; for example, it can be obtained through the registration acceptance / rejection, SR acceptance / rejection, configuration update message, and deregistration message of the second network.

[0147] In step S404, the UE determines that it has left the disaster area by comparing the current geographical location or TA area, and executes step S405 based on the determination result.

[0148] Example 2:

[0149] In step S402, a disaster occurs in a first network device to which the user equipment initially accesses. The UE leaves the disaster network, ie, the first network, and accesses a second network.

[0150] In step S403, the UE obtains the disaster area range from the second network, such as the TA area, TA list, or longitude and latitude, for example, through registration acceptance / rejection, SR acceptance / rejection, configuration update message, and deregistration message of the second network.

[0151] In one implementation, when the UE obtains the scope of the disaster area from the second network, it may not be in the disaster area. For example, in an area of ​​the first network where no disaster has occurred, the UE receives a notification from the second network that a disaster has occurred in a certain area of ​​the first network. The UE may not access the first network when entering the disaster area.

[0152] In another implementation, when the UE obtains the scope of the disaster area from the first network, the second network may be in the disaster area. For example, when a disaster occurs in the first network, the UE is notified that it is in the disaster area of ​​the first network and the scope of the disaster area.

[0153] In step S404, the UE determines that it has left the disaster area by comparing the current geographical location or TA area, and executes step S405 based on the determination result.

[0154] Example 3:

[0155] In step S402, a disaster occurs in a first network device to which the user equipment initially accesses.

[0156] In step S403, the UE obtains the scope of the disaster area from the third network. The third device learns about the disaster that occurred in the first network device. The third device is not the first network device where the disaster occurred, nor is it the second network device registered by the UE. The third device can be, for example, a Bluetooth device, a satellite, or a radio and television, and can tell the UE the area where the disaster occurred in the first network device, such as the longitude and latitude, the TA LIST, and the CELL LIST of the first network device, through broadcast, multicast, public alarm message, SMS, Bluetooth message, etc.

[0157] Alternatively, the third device may inform the UE of the information that the UE has entered the disaster area. For example, when the UE moves to an area and finds that the cell of the first network device can be searched and / or the cell is not in the disaster cell list, it determines in step S404 that it has left the scope of the disaster area, and in step S405, it may select the first network device and try to initiate registration in the cell when the service requires it.

[0158] like Figure 5 As shown, an embodiment of the present invention provides a method 500 for accessing a network, which can be performed by a terminal device and / or a network device. In other words, the method can be performed by software or hardware installed in the terminal device and / or the network device. The method includes the following steps:

[0159] S502: When the first network device initially accessed by the user equipment cannot provide network services due to target reasons, access a second network device.

[0160] The first network device to which the user equipment initially accesses sends a disaster, and the first network device includes, for example, four networks: ND1, 2, 3, and 4. Normal networks NA1, NA2, and ND1-2.

[0161] In this step, when the first network device ND1 to which the user equipment initially accesses cannot provide network services due to target reasons, the user equipment may access the second network device NA1.

[0162] At this time, NA1 may only be able to identify a portion of the disaster area, i.e., the overlapping area 54 of NA1 and ND1, because NA1 has a MINT service cooperation contract with ND1 but not with ND2. That is, ND2 does not notify NA1 of ND2's disaster area 55, nor does it notify UE.

[0163] S504: When the second network cannot provide services, access a fifth network device.

[0164] At this time, the UE continues to look for a network that can provide services when a disaster occurs in the first network. Since the second network NA1 has indicated that the UE can no longer be served by the second network NA1, the UE can now search for other networks that can provide services when a disaster occurs in the first network, that is, a fifth network device, such as other disabled PLMNs; wherein the fifth network device has the ability to provide network services when the first network device is unable to provide network services due to target reasons.

[0165] When the UE leaves area 54, NA1 believes that the UE has left the disaster area that NA1 can identify, but in fact the UE may still be in the disaster area, that is, disaster area 55. For example, position X is in area 54, and positions Y and Z are not in area 54. The UE moves from position X to position Y. At position X, the UE is normally served on NA1, but at position Y, the UE cannot obtain the service of NA1, that is, the second network cannot provide services. At this time, the UE cannot obtain the services of ND1 and ND2, but can search for NA2, that is, NA2 can serve as the fifth network device and has the ability to provide network services when the first network device cannot provide network services due to target reasons. Therefore, the service on NA2 is selected instead.

[0166] In one implementation, the method may further include: accessing the target network device when the target cause is eliminated. Figure 2 The description of step S204 of the embodiment is not repeated here. For example, when the UE reaches position Z, the UE cannot obtain the service of NA1, but obtains the service of position Z of ND1, that is, the service of the ND1-2 network. Therefore, the service on NA1 is selected instead.

[0167] A method for accessing a network provided by an embodiment of the present invention can ensure that a user device can obtain normal network services by accessing a fifth network device when the second network cannot provide services.

[0168] Combination of the above Figure 2-Figure 5 A method for accessing a network according to an embodiment of the present invention is described in detail. A method for accessing a network according to another embodiment of the present invention will be described in detail with reference to the accompanying drawings. It can be understood that the interaction between the network device and the terminal device described from the network device side is similar to Figure 2-Figure 5 The description on the terminal device side in the method shown is the same, and to avoid repetition, the relevant description is appropriately omitted.

[0169] like Figure 6 As shown, an embodiment of the present invention provides a method 600 for accessing a network, which can be executed by a network device. In other words, the method can be executed by software or hardware installed in a terminal device and / or a network device, and the network device can be a target network device described below. The method includes the following steps:

[0170] S602: Receive an access request sent by a user equipment.

[0171] The access request is sent by the user equipment when a target reason is eliminated, and the target reason is that the first network equipment initially accessed by the user equipment cannot provide network services;

[0172] S604: Execute the access process of the user equipment.

[0173] Executing this step enables the UE to receive normal network services on the target network device.

[0174] The target network device includes at least one of the following:

[0175] The first network device is a device that the user device initially accesses but cannot provide normal network services due to target reasons.

[0176] A third network device, wherein the third network device is a currently available network device with the highest priority;

[0177] The second network device, when the user device has no available and allowed network, the target network device is the second network device, and the second network device is the network device that the user device accesses when the first network device cannot provide network services due to the target reason.

[0178] In one implementation, when the target network device is the first network device, the access request is sent according to a stored network repetition value.

[0179] In an implementation manner, when the target network device is the second network device, if the second network device cannot provide the target network service, a limited network service is provided for the user equipment.

[0180] In one implementation, the target cause includes a disaster occurring to the first network device, and when the user device has left the disaster area, the target cause is eliminated.

[0181] In one implementation, before receiving the access request sent by the user equipment, the method further includes: sending a first message, where the first message is used to indicate that the user equipment has left the disaster area.

[0182] In one implementation, the first message includes at least one of the following: a non-access layer NAS message, the NAS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster in the first network device; an access layer AS message, the AS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster in the first network device; an air interface message, the air interface message is used to indicate a second cause value, the second cause value includes at least one of the following: disabling a public land mobile network PLMN; disabling a tracking area; disabling roaming in a target tracking area; no suitable cell in the tracking area; the serving network is unauthorized.

[0183] In one implementation, the NAS message includes at least one of the following: a registration message, a message of a service request process, a NAS direct transfer message, a deregistration message; or the AS message includes at least one of the following: a connection establishment rejection message, a release message, a system message.

[0184] In one implementation, before receiving the access request sent by the user equipment, the method further includes: sending a disaster area range, wherein the disaster area range is an area where one or more network devices are affected by the disaster and cannot provide services.

[0185] In one implementation, the sending of the disaster area range includes: sending the disaster area range when the user equipment is not in the disaster area.

[0186] In an implementation manner, when the target reason includes being not in the service area of ​​the first network device, the target network device is the second network device and / or the fourth network device.

[0187] In one implementation, the sending of the disaster area range includes:

[0188] Sending the disaster area range through a second message;

[0189] The second message includes at least one of the following:

[0190] Register to receive messages;

[0191] Registration rejection message;

[0192] Scheduling request acceptance message;

[0193] Scheduling request rejection message;

[0194] Configuration update message;

[0195] Go to register message;

[0196] Session management messages;

[0197] Session rejection message;

[0198] Session release message;

[0199] Short messages;

[0200] User plane data;

[0201] Bluetooth signaling.

[0202] In one implementation, the second message includes at least one of the following:

[0203] A correspondence between a disaster network identifier and a disaster type allocation code, wherein the disaster network identifier is an identifier of a network where a disaster occurs;

[0204] The correspondence between the disaster network identifier, the disaster type allocation code and the cell, wherein the disaster network identifier is the identifier of the network where the disaster occurs;

[0205] The correspondence between the disaster network identifier and the network slice information, wherein the disaster network identifier is the identifier of the network where the disaster occurs;

[0206] The corresponding relationship between the disaster network identifier and the data network name information, wherein the disaster network identifier is the identifier of the network where the disaster occurs.

[0207] In one implementation, the second message includes at least one of the following:

[0208] a correspondence between an identifier of a network where no disaster has occurred and an identifier of a tracking area, wherein the tracking area corresponding to the identifier of the tracking area covers an overlapping area between the network where no disaster has occurred and the disaster area of ​​the network where the disaster has occurred;

[0209] a correspondence between an identifier of a network where no disaster has occurred, a tracking area identifier, and a cell identifier, wherein the tracking area corresponding to the tracking area identifier covers an overlapping area between a network where no disaster has occurred and a disaster area of ​​a network where a disaster has occurred, and wherein the cell corresponding to the cell identifier covers an overlapping area between a network where no disaster has occurred and a disaster area of ​​a network where a disaster has occurred;

[0210] a correspondence between an identifier of a network where no disaster has occurred and data network name information, wherein the data network name information indicates a data network that cannot provide services in the network where the disaster has occurred due to the disaster but can provide services in the network where no disaster has occurred;

[0211] The correspondence between the identifier of a network where no disaster has occurred and the network slice information, wherein the network slice information indicates a network slice that cannot provide services in a network where a disaster has occurred but can provide services in a network where no disaster has occurred.

[0212] In one implementation, the second message includes at least one of the following:

[0213] Network identification;

[0214] Tracking area information;

[0215] Geolocation information;

[0216] Community information;

[0217] Network slicing information;

[0218] Data network name information.

[0219] This step can be done using Figure 2 Embodiment step S204, Figure 3 Example steps S303-304, Figure 4 Example steps S403-405, Figure 5 The corresponding descriptions of steps S503 - 504 of the embodiment are not repeated here to avoid repetition.

[0220] It should be noted that the method for accessing a network provided in the embodiment of the present application can be executed by a device for accessing a network, or a control module in the device for executing and loading the above method. In the embodiment of the present application, the method for accessing a network provided in the embodiment of the present application is described by taking the method for accessing a network performed by a device for accessing a network as an example.

[0221] Figure 7 is a schematic diagram of the structure of a device for accessing a network according to an embodiment of the present invention. Figure 7 As shown, the device 700 for accessing a network includes: a first access module 710 and a first processing module 720 .

[0222] The first access module 710 is used to access the second network device when the first network device initially accessed by the user device cannot provide network services due to a target reason. The first processing module 720 is used to access the target network device when the target reason is eliminated; the target network device includes at least one of the following: the first network device; the third network device, the third network device is the currently available network device with the highest priority; the second network device, when the user device has no available and allowed network, the target network device is the second network device.

[0223] In one implementation, the first access module 710 is configured to access the first network device according to a stored network repetition value when the target network device is the first network device.

[0224] In one implementation, the first access module 710 is configured to maintain a limited network service state on the second network device when the target network device is the second network device and the second network device cannot provide the target network service.

[0225] In one implementation, the target cause includes a disaster occurring to the first network device, and when the user device has left the disaster area, the target cause is eliminated.

[0226] In one implementation, the first access module 710 is further used to obtain a first message before accessing the target network device, where the first message is used to indicate that the user equipment has left the disaster area.

[0227] In one implementation, the first message includes at least one of the following:

[0228] A non-access stratum NAS message, the NAS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device;

[0229] An access layer AS message, the AS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device;

[0230] An air interface message, where the air interface message is used to indicate a second cause value, where the second cause value includes at least one of the following:

[0231] Disabling the Public Land Mobile Network (PLMN);

[0232] Disable tracking areas;

[0233] Disable roaming in target tracking areas;

[0234] There is no suitable cell in the tracking area;

[0235] The service network is not authorized.

[0236] In one implementation, the NAS message includes at least one of the following: a registration message, a message of a service request process, a NAS direct transfer message, a deregistration message; or

[0237] In one implementation, the AS message includes at least one of the following: a connection establishment rejection message, a release message, and a system message.

[0238] In one implementation, the first access module 710 is also used to obtain a disaster area range before accessing the target network device, wherein the disaster area range is obtained from one or more of the first network device, the second network device, and the fourth network device, and the disaster area range is an area where one or more network devices are affected by a disaster and cannot provide services.

[0239] In one implementation, the first access module 710 is used to obtain the scope of the disaster area when the user equipment is not in the disaster area.

[0240] In one implementation, the first access module 710 is used to obtain the disaster area range from the second network device and / or the fourth network device when the target reason includes being not in the service area of ​​the first network device.

[0241] In one implementation, the first access module 710 is used to obtain the disaster area range through a second message; wherein the second message is sent by one or more of the first network device, the second network device, and the fourth network device, and the second message includes at least one of the following:

[0242] Register to receive messages;

[0243] Registration rejection message;

[0244] Scheduling request acceptance message;

[0245] Scheduling request rejection message;

[0246] Configuration update message;

[0247] Go to register message;

[0248] Session management messages;

[0249] Session rejection message;

[0250] Session release message;

[0251] Short messages;

[0252] User plane data;

[0253] Bluetooth signaling.

[0254] In one implementation, the second message includes at least one of the following:

[0255] A correspondence between a disaster network identifier and a disaster type allocation code, wherein the disaster network identifier is an identifier of a network where a disaster occurs;

[0256] The correspondence between the disaster network identifier, the disaster type allocation code and the cell, wherein the disaster network identifier is the identifier of the network where the disaster occurs;

[0257] The correspondence between the disaster network identifier and the network slice information, wherein the disaster network identifier is the identifier of the network where the disaster occurs;

[0258] The corresponding relationship between the disaster network identifier and the data network name information, wherein the disaster network identifier is the identifier of the network where the disaster occurs.

[0259] In one implementation, the second message includes at least one of the following:

[0260] a correspondence between an identifier of a network where no disaster has occurred and an identifier of a tracking area, wherein the tracking area corresponding to the identifier of the tracking area covers an overlapping area between the network where no disaster has occurred and the disaster area of ​​the network where the disaster has occurred;

[0261] a correspondence between an identifier of a network where no disaster has occurred, a tracking area identifier, and a cell identifier, wherein the tracking area corresponding to the tracking area identifier covers an overlapping area between a network where no disaster has occurred and a disaster area of ​​a network where a disaster has occurred, and wherein the cell corresponding to the cell identifier covers an overlapping area between a network where no disaster has occurred and a disaster area of ​​a network where a disaster has occurred;

[0262] a correspondence between an identifier of a network where no disaster has occurred and data network name information, wherein the data network name information indicates a data network that cannot provide services in the network where the disaster has occurred due to the disaster but can provide services in the network where no disaster has occurred;

[0263] The correspondence between the identifier of a network where no disaster has occurred and the network slice information, wherein the network slice information indicates a network slice that cannot provide services in a network where a disaster has occurred but can provide services in a network where no disaster has occurred.

[0264] In one implementation, the second message includes at least one of the following:

[0265] Network identification;

[0266] Tracking area information;

[0267] Geolocation information;

[0268] Community information;

[0269] Network slicing information;

[0270] Data network name information.

[0271] In one implementation, the first access module 710 is used to determine whether the user equipment has left the disaster area based on the range of the disaster area.

[0272] In one implementation, the first access module 710 is configured to determine that the user equipment has not left the disaster area when a portion of the network where the disaster occurs belongs to the disaster area; or

[0273] In the case that the partial area of ​​the network where the disaster occurs does not belong to the disaster area, it is determined that the user equipment has left the disaster area.

[0274] In one implementation, the first access module 710 is configured to, after acquiring the disaster area range through the second message, further perform at least one of the following:

[0275] In the case where the second message includes network slice information, the service is not obtained using the parameters indicated by the network slice;

[0276] In the case where the second message includes the data network name information, the protocol data unit session service is acquired without using the parameters indicated by the data network name information.

[0277] In one implementation, the first access module 710 is also used to access a fifth network device after accessing the second network device when the second network cannot provide services, wherein the fifth network device has the ability to provide network services when the first network device cannot provide network services due to target reasons.

[0278] In an implementation manner, the first access module 710 is configured to disable the equivalent network information of the second network device after accessing the second network device.

[0279] The device for accessing the network in the embodiments of the present application may be a device, or a component, an integrated circuit, or a chip in a terminal. The device may be a mobile electronic device or a non-mobile electronic device. For example, the mobile electronic device may be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc. The non-mobile electronic device may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine, or a self-service machine, etc., which is not specifically limited in the embodiments of the present application.

[0280] The device 700 according to the embodiment of the present invention can refer to the process of the method 200-500 corresponding to the embodiment of the present invention, and the various units / modules in the device 700 and the above-mentioned other operations and / or functions are respectively for implementing the corresponding processes in the method 200-500, and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be repeated here.

[0281] Figure 8 is a schematic diagram of the structure of a device for accessing a network according to an embodiment of the present invention. Figure 8 As shown, the device 800 for accessing a network includes: a second access module 810 and a second processing module 820 .

[0282] The second access module 810 is used to receive an access request sent by a user device, wherein the access request is sent by the user device when a target reason is eliminated, and the target reason is that the first network device initially accessed by the user device cannot provide network services. The second processing module 820 is used to execute the access process of the user device; the target network device includes at least one of the following:

[0283] the first network device;

[0284] A third network device, wherein the third network device is a currently available network device with the highest priority;

[0285] The second network device, when the user device has no available and allowed network, the target network device is the second network device, and the second network device is the network device that the user device accesses when the first network device cannot provide network services due to the target reason.

[0286] In one implementation, when the target network device is the first network device, the access request is sent according to a stored network repetition value.

[0287] In one implementation, the second processing module 820 is configured to provide limited network service for the user equipment when the target network device is the second network device and the second network device cannot provide the target network service.

[0288] In one implementation, the target cause includes a disaster occurring to the first network device, and when the user device has left the disaster area, the target cause is eliminated.

[0289] In one implementation, the second processing module 820 is used to send a first message before receiving the access request sent by the user equipment, where the first message is used to indicate that the user equipment has left the disaster area.

[0290] In one implementation, the first message includes at least one of the following:

[0291] A non-access stratum NAS message, the NAS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device;

[0292] An access layer AS message, the AS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device;

[0293] An air interface message, where the air interface message is used to indicate a second cause value, where the second cause value includes at least one of the following:

[0294] Disabling the Public Land Mobile Network (PLMN);

[0295] Disable tracking areas;

[0296] Disable roaming in target tracking areas;

[0297] There is no suitable cell in the tracking area;

[0298] The service network is not authorized.

[0299] In one implementation, the NAS message includes at least one of the following: a registration message, a message of a service request process, a NAS direct transfer message, and a deregistration message.

[0300] In one implementation, the AS message includes at least one of the following: a connection establishment rejection message, a release message, and a system message.

[0301] In one implementation, the second processing module 820 is used to send a disaster area range before receiving an access request sent by the user equipment, wherein the disaster area range is an area where one or more network devices are affected by a disaster and cannot provide services.

[0302] In one implementation, the second processing module 820 is configured to send the disaster area range when the user equipment is not in the disaster area.

[0303] In an implementation manner, when the target reason includes being not in the service area of ​​the first network device, the target network device is the second network device and / or the fourth network device.

[0304] In one implementation, the second processing module 820 is used to send the disaster area range through a second message; wherein the second message includes at least one of the following:

[0305] Register to receive messages;

[0306] Registration rejection message;

[0307] Scheduling request acceptance message;

[0308] Scheduling request rejection message;

[0309] Configuration update message;

[0310] Go to register message;

[0311] Session management messages;

[0312] Session rejection message;

[0313] Session release message;

[0314] Short messages;

[0315] User plane data;

[0316] Bluetooth signaling.

[0317] In one implementation, the second message includes at least one of the following:

[0318] A correspondence between a disaster network identifier and a disaster type allocation code, wherein the disaster network identifier is an identifier of a network where a disaster occurs;

[0319] The correspondence between the disaster network identifier, the disaster type allocation code and the cell, wherein the disaster network identifier is the identifier of the network where the disaster occurs;

[0320] The correspondence between the disaster network identifier and the network slice information, wherein the disaster network identifier is the identifier of the network where the disaster occurs;

[0321] The corresponding relationship between the disaster network identifier and the data network name information, wherein the disaster network identifier is the identifier of the network where the disaster occurs.

[0322] In one implementation, the second message includes at least one of the following:

[0323] a correspondence between an identifier of a network where no disaster has occurred and an identifier of a tracking area, wherein the tracking area corresponding to the identifier of the tracking area covers an overlapping area between the network where no disaster has occurred and the disaster area of ​​the network where the disaster has occurred;

[0324] a correspondence between an identifier of a network where no disaster has occurred, a tracking area identifier, and a cell identifier, wherein the tracking area corresponding to the tracking area identifier covers an overlapping area between a network where no disaster has occurred and a disaster area of ​​a network where a disaster has occurred, and wherein the cell corresponding to the cell identifier covers an overlapping area between a network where no disaster has occurred and a disaster area of ​​a network where a disaster has occurred;

[0325] a correspondence between an identifier of a network where no disaster has occurred and data network name information, wherein the data network name information indicates a data network that cannot provide services in the network where the disaster has occurred due to the disaster but can provide services in the network where no disaster has occurred;

[0326] The correspondence between the identifier of a network where no disaster has occurred and the network slice information, wherein the network slice information indicates a network slice that cannot provide services in a network where a disaster has occurred but can provide services in a network where no disaster has occurred.

[0327] In one implementation, the second message includes at least one of the following:

[0328] Network identification;

[0329] Tracking area information;

[0330] Geolocation information;

[0331] Community information;

[0332] Network slicing information;

[0333] Data network name information.

[0334] The device for accessing the network in the embodiments of the present application may be a device, or a component, an integrated circuit, or a chip in a terminal. The device may be a mobile electronic device or a non-mobile electronic device. For example, the mobile electronic device may be a mobile phone, a tablet computer, a laptop computer, a PDA, an in-vehicle electronic device, a wearable device, an ultra-mobile personal computer (UMPC), a netbook, or a personal digital assistant (PDA), etc. The non-mobile electronic device may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a teller machine, or a self-service machine, etc., which is not specifically limited in the embodiments of the present application.

[0335] The device for accessing the network in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0336] The device 800 according to an embodiment of the present invention can refer to the process of the method 600 corresponding to the embodiment of the present invention, and the various units / modules in the device 800 and the above-mentioned other operations and / or functions are respectively for implementing the corresponding processes in the method 600, and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be repeated here.

[0337] Specifically, the embodiment of the present application also provides a network side device. Fig. 9 As shown, the network device 900 includes: an antenna 901, a radio frequency device 902, and a baseband device 903. The antenna 901 is connected to the radio frequency device 902. In the uplink direction, the radio frequency device 902 receives information through the antenna 901 and sends the received information to the baseband device 903 for processing. In the downlink direction, the baseband device 903 processes the information to be sent and sends it to the radio frequency device 902. The radio frequency device 902 processes the received information and sends it out through the antenna 901.

[0338] The frequency band processing device may be located in the baseband device 903 . The method performed by the network-side device in the above embodiment may be implemented in the baseband device 903 . The baseband device 903 includes a processor 904 and a memory 905 .

[0339] The baseband device 903 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in the figure, one of the chips is, for example, a processor 904, which is connected to the memory 905 to call the program in the memory 905 and execute the network device operations shown in the above method embodiment.

[0340] The baseband device 903 may further include a network interface 906 for exchanging information with the radio frequency device 902 . The interface may be, for example, a common public radio interface (CPRI for short).

[0341] Specifically, the network side device of the embodiment of the present invention also includes: instructions or programs stored in the memory 905 and executable on the processor 904, and the processor 904 calls the instructions or programs in the memory 905 to execute: receiving an access request sent by a user device, wherein the access request is sent by the user device when the target cause is eliminated, and the target cause is the reason why the first network device initially accessed by the user device cannot provide network services; executing the access process of the user device; the target network device includes at least one of the following: the first network device; a third network device, the third network device is a currently available network device with the highest priority; a second network device, when the user device has no available and allowed network, the target network device is the second network device, and the second network device is the network device to which the user device accesses when the first network device cannot provide network services due to the target cause.

[0342] In one implementation, when the target network device is the first network device, the access request is sent according to a stored network repetition value.

[0343] In an implementation manner, when the target network device is the second network device, if the second network device cannot provide the target network service, a limited network service is provided for the user equipment.

[0344] In one implementation, the target cause includes a disaster occurring to the first network device, and when the user device has left the disaster area, the target cause is eliminated.

[0345] In an implementation manner, before receiving the access request sent by the user equipment, the following is further performed: sending a first message, where the first message is used to indicate that the user equipment has left the disaster area.

[0346] In one implementation, the first message includes at least one of the following:

[0347] A non-access stratum NAS message, the NAS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device;

[0348] An access layer AS message, the AS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device;

[0349] An air interface message, where the air interface message is used to indicate a second cause value, where the second cause value includes at least one of the following:

[0350] Disabling the Public Land Mobile Network (PLMN);

[0351] Disable tracking areas;

[0352] Disable roaming in target tracking areas;

[0353] There is no suitable cell in the tracking area;

[0354] The service network is not authorized.

[0355] In one implementation, the NAS message includes at least one of the following: a registration message, a message of a service request process, a NAS direct transfer message, a deregistration message; or

[0356] The AS message includes at least one of the following: a connection establishment rejection message, a release message, and a system message;

[0357] In one implementation, before receiving the access request sent by the user equipment, the following is further performed: sending a disaster area range, wherein the disaster area range is an area where one or more network devices are affected by the disaster and cannot provide services.

[0358] In one implementation, when the user equipment is not in the disaster area, the disaster area range is sent.

[0359] In an implementation manner, when the target reason includes being not in the service area of ​​the first network device, the target network device is the second network device and / or the fourth network device.

[0360] In one implementation, the disaster area range is sent via a second message;

[0361] The second message includes at least one of the following:

[0362] Register to receive messages;

[0363] Registration rejection message;

[0364] Scheduling request acceptance message;

[0365] Scheduling request rejection message;

[0366] Configuration update message;

[0367] Go to register message;

[0368] Session management messages;

[0369] Session rejection message;

[0370] Session release message;

[0371] Short messages;

[0372] User plane data;

[0373] Bluetooth signaling.

[0374] In one implementation, the second message includes at least one of the following:

[0375] A correspondence between a disaster network identifier and a disaster type allocation code, wherein the disaster network identifier is an identifier of a network where a disaster occurs;

[0376] The correspondence between the disaster network identifier, the disaster type allocation code and the cell, wherein the disaster network identifier is the identifier of the network where the disaster occurs;

[0377] The correspondence between the disaster network identifier and the network slice information, wherein the disaster network identifier is the identifier of the network where the disaster occurs;

[0378] The corresponding relationship between the disaster network identifier and the data network name information, wherein the disaster network identifier is the identifier of the network where the disaster occurs.

[0379] In one implementation, the second message includes at least one of the following:

[0380] a correspondence between an identifier of a network where no disaster has occurred and an identifier of a tracking area, wherein the tracking area corresponding to the identifier of the tracking area covers an overlapping area between the network where no disaster has occurred and the disaster area of ​​the network where the disaster has occurred;

[0381] a correspondence between an identifier of a network where no disaster has occurred, a tracking area identifier, and a cell identifier, wherein the tracking area corresponding to the tracking area identifier covers an overlapping area between a network where no disaster has occurred and a disaster area of ​​a network where a disaster has occurred, and wherein the cell corresponding to the cell identifier covers an overlapping area between a network where no disaster has occurred and a disaster area of ​​a network where a disaster has occurred;

[0382] a correspondence between an identifier of a network where no disaster has occurred and data network name information, wherein the data network name information indicates a data network that cannot provide services in the network where the disaster has occurred due to the disaster but can provide services in the network where no disaster has occurred;

[0383] The correspondence between the identifier of a network where no disaster has occurred and the network slice information, wherein the network slice information indicates a network slice that cannot provide services in a network where a disaster has occurred but can provide services in a network where no disaster has occurred.

[0384] In one implementation, the second message includes at least one of the following:

[0385] Network identification;

[0386] Tracking area information;

[0387] Geolocation information;

[0388] Community information;

[0389] Network slicing information;

[0390] Data network name information.

[0391] The specific steps performed by the processor 904 are as follows: Figure 6 The methods for executing the steps shown in the figure achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0392] Fig.10 A schematic diagram of the hardware structure of a terminal device for implementing an embodiment of the present application.

[0393] The terminal device 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009, and a processor 1010 and other components.

[0394] Those skilled in the art can understand that the terminal device 1000 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 implement functions such as charging, discharging, and power consumption management through the power management system. The terminal device structure shown in the figure does not constitute a limitation on the terminal device, and the terminal device may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently, which will not be repeated here.

[0395] It should be understood that in the embodiment of the present application, the input unit 1004 may include a graphics processor (Graphics Processing Unit, GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1007 includes a touch panel 10071 and other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

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

[0397] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 1009 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device.

[0398] The processor 1010 may include one or more processing units; optionally, the processor 1010 may 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 communications, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1010.

[0399] The processor 1010 is configured to access a second network device when the first network device initially accessed by the user equipment cannot provide network services due to a target reason; and access a target network device when the target reason is eliminated; the target network device includes at least one of the following:

[0400] the first network device;

[0401] A third network device, wherein the third network device is a currently available network device with the highest priority;

[0402] The second network device, when the user equipment has no available and allowed network, the target network device is the second network device.

[0403] In an implementation manner, when the target network device is the first network device, accessing the target network device includes: accessing the first network device according to a stored network repetition value.

[0404] In an implementation manner, when the target network device is the second network device, if the second network device cannot provide the target network service, a limited network service state is maintained on the second network device.

[0405] In one implementation, the target cause includes a disaster occurring to the first network device, and when the user device has left the disaster area, the target cause is eliminated.

[0406] In an implementation manner, before accessing the target network device, the following is further performed: obtaining a first message, where the first message is used to indicate that the user equipment has left the disaster area.

[0407] In one implementation, the first message includes at least one of the following:

[0408] A non-access stratum NAS message, the NAS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device;

[0409] An access layer AS message, the AS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device;

[0410] An air interface message, where the air interface message is used to indicate a second cause value, where the second cause value includes at least one of the following:

[0411] Disabling the Public Land Mobile Network (PLMN);

[0412] Disable tracking areas;

[0413] Disable roaming in target tracking areas;

[0414] There is no suitable cell in the tracking area;

[0415] The service network is not authorized.

[0416] In one implementation, the NAS message includes at least one of the following: a registration message, a message of a service request process, a NAS direct transfer message, a deregistration message; or

[0417] In one implementation, the AS message includes at least one of the following: a connection establishment rejection message, a release message, and a system message.

[0418] In one implementation, before accessing the target network device, the following is also performed: obtaining a disaster area range, wherein the disaster area range is obtained from one or more of the first network device, the second network device, and the fourth network device, and the disaster area range is an area where one or more network devices are affected by a disaster and cannot provide services.

[0419] In one implementation, when the user equipment is not in the disaster area, the range of the disaster area is obtained.

[0420] In one implementation, when the target reason includes being not in the service area of ​​the first network device, the disaster area range is obtained from the second network device and / or the fourth network device.

[0421] In one implementation, the disaster area range is obtained through a second message;

[0422] The second message is sent by one or more of the first network device, the second network device, and the fourth network device, and the second message includes at least one of the following:

[0423] Register to receive messages;

[0424] Registration rejection message;

[0425] Scheduling request acceptance message;

[0426] Scheduling request rejection message;

[0427] Configuration update message;

[0428] Go to register message;

[0429] Session management messages;

[0430] Session rejection message;

[0431] Session release message;

[0432] Short messages;

[0433] User plane data;

[0434] Bluetooth signaling.

[0435] In one implementation, the second message includes at least one of the following:

[0436] A correspondence between a disaster network identifier and a disaster type allocation code, wherein the disaster network identifier is an identifier of a network where a disaster occurs;

[0437] The correspondence between the disaster network identifier, the disaster type allocation code and the cell, wherein the disaster network identifier is the identifier of the network where the disaster occurs;

[0438] The correspondence between the disaster network identifier and the network slice information, wherein the disaster network identifier is the identifier of the network where the disaster occurs;

[0439] The corresponding relationship between the disaster network identifier and the data network name information, wherein the disaster network identifier is the identifier of the network where the disaster occurs.

[0440] In one implementation, the second message includes at least one of the following:

[0441] a correspondence between an identifier of a network where no disaster has occurred and an identifier of a tracking area, wherein the tracking area corresponding to the identifier of the tracking area covers an overlapping area between the network where no disaster has occurred and the disaster area of ​​the network where the disaster has occurred;

[0442] a correspondence between an identifier of a network where no disaster has occurred, a tracking area identifier, and a cell identifier, wherein the tracking area corresponding to the tracking area identifier covers an overlapping area between a network where no disaster has occurred and a disaster area of ​​a network where a disaster has occurred, and wherein the cell corresponding to the cell identifier covers an overlapping area between a network where no disaster has occurred and a disaster area of ​​a network where a disaster has occurred;

[0443] a correspondence between an identifier of a network where no disaster has occurred and data network name information, wherein the data network name information indicates a data network that cannot provide services in the network where the disaster has occurred due to the disaster but can provide services in the network where no disaster has occurred;

[0444] The correspondence between the identifier of a network where no disaster has occurred and the network slice information, wherein the network slice information indicates a network slice that cannot provide services in a network where a disaster has occurred but can provide services in a network where no disaster has occurred.

[0445] In one implementation, the second message includes at least one of the following:

[0446] Network identification;

[0447] Tracking area information;

[0448] Geolocation information;

[0449] Community information;

[0450] Network slicing information;

[0451] Data network name information.

[0452] In one implementation, based on the range of the disaster area, it is determined whether the user equipment has left the disaster area.

[0453] In one implementation, when a portion of the network where the disaster occurs belongs to the disaster area, it is determined that the user equipment has not left the disaster area; or

[0454] In the case that the partial area of ​​the network where the disaster occurs does not belong to the disaster area, it is determined that the user equipment has left the disaster area.

[0455] In one implementation, after obtaining the disaster area range through the second message, at least one of the following is further performed:

[0456] In the case where the second message includes network slice information, the service is not obtained using the parameters indicated by the network slice;

[0457] In the case where the second message includes the data network name information, the protocol data unit session service is acquired without using the parameters indicated by the data network name information.

[0458] In one implementation, after accessing the second network device, when the second network fails to provide services, a fifth network device is accessed, wherein the fifth network device has the ability to provide network services when the first network device fails to provide network services due to target reasons.

[0459] In an implementation manner, after accessing the second network device, the equivalent network information of the second network device is disabled.

[0460] The terminal device 1000 according to the embodiment of the present invention can refer to the process of the method 200-500 corresponding to the embodiment of the present invention, and the various units / modules in the terminal device 1000 and the above-mentioned other operations and / or functions are respectively for implementing the corresponding processes in the method 200-500, and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be repeated here.

[0461] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned method embodiment for accessing the network is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0463] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned network access method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0464] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0465] An embodiment of the present application further provides a computer program product, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method for accessing a network as described above.

[0466] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0467] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0468] 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-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A method for accessing a network, characterized in that: Executed by the user device, including: When the first network device accessed by the user equipment cannot provide network services due to a target reason, accessing a second network device; wherein the target reason includes a disaster occurring in the first network device; the second network device is a disabled public land mobile network PLMN of the UE; Obtaining a first message, and accessing a target network device when it is determined according to the first message that the target cause is eliminated; The first message includes at least one of the following cause values: Disabling the Public Land Mobile Network (PLMN); Disable roaming in target tracking areas; The target network device includes a third network device, and the third network device is a currently available network device with the highest priority.

2. The method according to claim 1, characterized in that In the case where the target network device is the first network device, the access target network device includes: Access the first network device according to the stored network repetition value.

3. The method according to claim 1, characterized in that In the case that the target network device is the second network device, if the second network device cannot provide the target network service, a limited network service state is maintained on the second network device.

4. The method according to claim 1, characterized in that: The first message also includes at least one of the following: A non-access stratum NAS message, the NAS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device; An access layer AS message, the AS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device; An air interface message, where the air interface message is used to indicate a second cause value, where the second cause value includes at least one of the following: Disable tracking areas; There is no suitable cell in the tracking area; The service network is not authorized.

5. The method according to claim 4, characterized in that The NAS message includes at least one of the following: a registration message, a message of a service request process, a NAS direct transfer message, and a deregistration message; or The AS message includes at least one of the following: a connection establishment rejection message, a release message, and a system message.

6. The method according to claim 1, characterized in that After accessing the second network device, the method further includes: In the case where the second network fails to provide services, a fifth network device is accessed, wherein the fifth network device has the ability to provide network services in the case where the first network device fails to provide network services due to target reasons.

7. The method according to claim 1, characterized in that After accessing the second network device, the method further includes at least one of the following: disabling all equivalent network information of the second network device; disabling part of equivalent network information of the second network device; using part of the equivalent network information of the second network device; not saving the equivalent network information; not adding the second network device into the equivalent network information; saving and / or selecting an available network, wherein the available network is a network available in a disaster situation; Keep equivalent network information in the banned network information list.

8. A method for accessing a network, characterized in that: Performed by the target network device, including: Sending a first message, where the first message is used to indicate that the user equipment has left the disaster area; receiving an access request sent by a user equipment, wherein the access request is sent by the user equipment when a target cause is determined to be excluded according to the first message, and the target cause is a cause why a first network device accessed by the user equipment cannot provide network services; wherein the target cause includes a disaster occurring to the first network device; when the first network device cannot provide network services due to the target cause, the network device accessed by the user equipment is a second network device; and the second network device is a disabled public land mobile network PLMN of the UE; Execute an access process of the user equipment; The target network device includes a third network device, and the third network device is a currently available network device with the highest priority; The first message includes at least one of the following cause values: Disabling the Public Land Mobile Network (PLMN); Disable roaming in the target tracking area.

9. The method according to claim 8, characterized in that In the case where the target network device is the first network device, the access request is sent according to the stored network repetition value.

10. The method according to claim 8, characterized in that In the case that the target network device is the second network device, if the second network device cannot provide the target network service, a limited network service is provided for the user equipment.

11. The method according to claim 8, characterized in that The first message also includes at least one of the following: A non-access stratum NAS message, the NAS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device; An access layer AS message, the AS message carrying a first cause value, the first cause value indicating that the second network device no longer provides services due to a disaster of the first network device; An air interface message, where the air interface message is used to indicate a second cause value, where the second cause value includes at least one of the following: Disable tracking areas; There is no suitable cell in the tracking area; The service network is not authorized.

12. The method according to claim 11, characterized in that The NAS message includes at least one of the following: a registration message, a message of a service request process, a NAS direct transfer message, and a deregistration message; or The AS message includes at least one of the following: a connection establishment rejection message, a release message, and a system message.

13. A device for accessing a network, characterized in that: The device is applied to user equipment and includes: A first access module is configured to access a second network device when the first network device accessed by the user equipment cannot provide network services due to a target reason; wherein the target reason includes a disaster occurring in the first network device; and the second network device is a disabled public land mobile network PLMN of the UE; The first access module is further configured to obtain a first message; wherein the first message includes at least one of the following cause values: Disabling the Public Land Mobile Network (PLMN); Disable roaming in target tracking areas; A first processing module, configured to access a target network device when it is determined according to the first message that the target cause is eliminated; The target network device includes a third network device, and the third network device is a currently available network device with the highest priority.

14. A device for accessing a network, characterized in that: The device is applied to a target network device, comprising: a second access module, configured to receive an access request sent by a user equipment, wherein the access request is sent by the user equipment when a target cause is determined to be excluded according to the first message, and the target cause is a cause why a first network device accessed by the user equipment cannot provide network services; wherein the target cause includes a disaster occurring to the first network device; when the first network device cannot provide network services due to the target cause, the network device accessed by the user equipment is a second network device; and the second network device is a disabled public land mobile network PLMN of the UE; A second processing module, configured to execute an access process of the user equipment; The target network device includes a third network device, and the third network device is a currently available network device with the highest priority; The second processing module is further configured to send a first message before receiving an access request sent by the user equipment, wherein the first message is used to indicate that the user equipment has left the disaster area; wherein the first message includes at least one of the following cause values: Disabling the Public Land Mobile Network (PLMN); Disable roaming in the target tracking area.

15. A terminal device, characterized in that: The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method for accessing a network as described in any one of claims 1 to 7.

16. A network device, characterized in that: The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method for accessing a network as described in any one of claims 8 to 12.

17. A readable storage medium, characterized in that: The readable storage medium stores a program or an instruction, and when the program or the instruction is executed by the processor, the steps of the method for accessing a network according to any one of claims 1 to 7 are implemented; or Implement the steps of the method for accessing a network as described in any one of claims 8 to 12.

Images