Method for network registration

Abstract

The application provides a network registration method and device, the method comprising: a terminal device sending a registration request message to a network device, the registration request message comprising a first network identifier, the registration request message indicating a request to access a network to be registered, the network to be registered being a public network or a non-public network identified by the first network identifier; the terminal device receiving a registration rejection message sent by the network device, and performing an operation corresponding to an access type according to at least one of an access type and a cause value of the network to be registered, the access type comprising a public network and a non-public network. Thus, the method and device of the application can determine whether the network type that cannot be accessed when network registration is rejected is a public network or a non-public network corresponding to a network identifier, and perform an operation corresponding to the public network or the non-public network, so that the registration of a user device for a public network and a non-public network identified using the same network identifier does not affect each other.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communications, and more specifically, to a network registration method. BACKGROUND

[0002] In a 5G core network (5GC), a public network integrated non-public network (PNI-NPN) is a function similar to an enterprise private network implemented by a public land mobile network (PLMN) through, for example, network slicing, a dedicated data network name (Dedicated DNN), and the like.

[0003] A PLMN can be identified by a PLMN ID. A PNI-NPN currently has no dedicated ID to identify it, but is simply identified by the PLMN ID corresponding to the PLMN to which it is associated. When a user equipment (UE) cannot access a certain PLMN, the UE adds the PLMN ID corresponding to the PLMN to a list (Forbidden PLMN list). When the UE performs automatic network selection again, the UE will not select a cell corresponding to the PLMN ID in the list, resulting in the UE being unable to access the PNI-NPN associated with the PLMN ID. Similarly, when the UE cannot access a certain PNI-NPN, the UE is also unable to access the PLMN identified by the same PLMN ID.

[0004] Therefore, network registration of a UE for a PLMN and a PNI-NPN sharing the same PLMN ID affects each other. SUMMARY

[0005] Embodiments of the present application provide a network registration method that can ensure that, when a public network and a non-public network share the same network identifier, a terminal device cannot be affected in registering the non-public network when the terminal device cannot register the public network, and vice versa.

[0006] In a first aspect, a network registration method is provided. The method includes sending a registration request message, the registration request message including a first network identifier, the registration request message indicating a request to access a network to be registered, the network to be registered being a public network or a non-public network identified by the first network identifier; receiving a registration rejection message; and performing an operation corresponding to an access type of the network to be registered according to at least one of an access type and a cause value, the access type including a public network and a non-public network.

[0007] With reference to the first aspect, in a first possible implementation manner of the first aspect, the operation corresponding to the access type is performed, including: when the access type of the network to be registered is a public network, adding the first network identifier into a first list, the first list indicating that the public network identified by the network identifier in the first list is prohibited to be accessed; or when the access type of the network to be registered is a non-public network, adding the first network identifier into a second list, the second list indicating that the non-public network identified by the network identifier in the second list is prohibited to be accessed.

[0008] With reference to the first aspect, or with reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the operation corresponding to the access type is performed, including: when the access type of the network to be registered is a public network, entering a first state; or when the access type of the network to be registered is a non-public network, entering a second state; the first state and the second state are not the same state.

[0009] With reference to the second possible implementation manner of the first aspect, optionally, the first state indicates that the public network cannot be accessed, and the second state indicates that the non-public network cannot be accessed.

[0010] With reference to the second possible implementation manner of the first aspect, optionally, the first state indicates that the public network identified by the first network identifier cannot be accessed, and the second state indicates that the non-public network identified by the first network identifier cannot be accessed.

[0011] With reference to the first aspect, or with reference to the first or second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the operation corresponding to the access type is performed, including: when the access type of the network to be registered is a public network, a non-access stratum (NAS) layer indicating that an access stratum (AS) layer cannot select a cell of the public network identified by the network identifier in the first list; or when the access type of the network to be registered is a non-public network, the NAS layer indicating that the AS layer cannot select a cell of the non-public network identified by the network identifier in the second list.

[0012] With reference to the first aspect, in a fourth possible implementation manner of the first aspect, the reason value is used to indicate: the public network identified by the first network identifier cannot be accessed; or the non-public network identified by the first network identifier cannot be accessed; or the network identified by the first network identifier cannot be accessed.

[0013] With reference to the first aspect, or with reference to any one of the first to fourth possible implementation manners of the first aspect, in a fifth possible implementation manner of the first aspect, the registration rejection message includes the reason value.

[0014] In a sixth possible implementation manner of the first aspect, the access type of the network to be registered is included in the registration request message.

[0015] In a second aspect, a method for network registration is provided. The method comprises: receiving a registration request message, the registration request message comprising a first network identifier and an access type of a network to be registered, the registration request message indicating that a terminal device requests a network device to access the network to be registered, the access type comprising a public network and a non-public network, the network to be registered being the public network or the non-public network identified by the first network identifier; determining to reject the terminal device to access the network to be registered; and sending a registration rejection message to the terminal device.

[0016] In a first possible implementation manner of the second aspect, a cause value is determined according to the access type of the network to be registered, the cause value being used to indicate the rejection of accessing the network to be registered; and the cause value is sent to the terminal device.

[0017] In a second possible implementation manner of the first possible implementation manner of the second aspect, when the access type of the network to be registered is the public network, the cause value is determined, the cause value indicating the rejection of accessing the public network identified by the first network identifier; or when the access type of the network to be registered is the non-public network, the cause value is determined, the cause value indicating the rejection of accessing the non-public network identified by the first network identifier; or the cause value is determined, the cause value indicating the rejection of accessing the network identified by the first network identifier.

[0018] In the first or second possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, the registration rejection message comprises the cause value.

[0019] In a third aspect, an apparatus for network registration is provided. The apparatus comprises: a transceiver, configured to send a registration request message, the registration request message comprising a first network identifier, the registration request message indicating a request to access a network to be registered, the network to be registered being a public network or a non-public network identified by the first network identifier; the transceiver is further configured to receive a registration rejection message; and a processing module, configured to perform an operation corresponding to an access type according to at least one of the access type and a cause value, the access type comprising the public network and the non-public network.

[0020] With reference to the third aspect, in a first possible implementation manner of the third aspect, the processing module is specifically configured to: when the access type of the network to be registered is a public network, add the first network identifier into a first list, the first list indicating that access to the public network identified by the network identifier in the first list is prohibited; or when the access type of the network to be registered is a non-public network, add the first network identifier into a second list, the second list indicating that access to the non-public network identified by the network identifier in the second list is prohibited.

[0021] With reference to the third aspect, or with reference to any one of the first to fourth possible implementation manners of the third aspect, in a second possible implementation manner of the third aspect, the processing module is specifically further configured to: when the access type of the network to be registered is a public network, enter a first state; or when the access type of the network to be registered is a non-public network, enter a second state; the first state and the second state are not the same state.

[0022] With reference to the second possible implementation manner of the third aspect, optionally, the first state indicates that access to a public network is not allowed, and the second state indicates that access to a non-public network is not allowed.

[0023] With reference to the second possible implementation manner of the third aspect, optionally, the first state indicates that access to the public network identified by the first network identifier is not allowed, and the second state indicates that access to the non-public network identified by the first network identifier is not allowed.

[0024] With reference to the first or second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the processing module is specifically further configured to: when the access type of the network to be registered is a public network, instruct a non-access stratum (NAS) layer that an access stratum (AS) layer cannot select a cell of the public network identified by the network identifier in the first list; or when the access type of the network to be registered is a non-public network, instruct the NAS layer that the AS layer cannot select a cell of the non-public network identified by the network identifier in the second list.

[0025] With reference to the third aspect, in a fourth possible implementation manner of the third aspect, the cause value is used to indicate that: access to the public network identified by the first network identifier is not allowed; or access to the non-public network identified by the first network identifier is not allowed; or access to the network identified by the first network identifier is not allowed.

[0026] With reference to the third aspect, or with reference to any one of the first to fourth possible implementation manners of the third aspect, in a fifth possible implementation manner of the third aspect, the registration reject message comprises the cause value.

[0027] With reference to any one of the first to fifth possible implementation manners of the third aspect, in a sixth possible implementation manner of the first aspect, the access type of the network to be registered is comprised in the registration request message.

[0028] In a fourth aspect, a network registration apparatus is provided, which comprises: a transceiver configured to receive a registration request message, the registration request message comprising a first network identifier and an access type of a network to be registered, the registration request message indicating that a terminal device requests a network device to access the network to be registered, the access type comprising a public network and a non-public network, the network to be registered being the public network or the non-public network identified by the first network identifier; a processor configured to determine to reject the terminal device to access the network to be registered; and the transceiver is further configured to send a registration rejection message to the terminal device.

[0029] With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the processor is further configured to determine a cause value according to the access type of the network to be registered, the cause value being used to indicate that the terminal device is rejected to access the network to be registered; and the transceiver is further configured to send the cause value to the terminal device.

[0030] With reference to the first possible implementation manner of the fourth aspect, optionally, the processor is further configured to: when the access type of the network to be registered is the public network, determine the cause value, the cause value indicating that the terminal device is rejected to access the public network identified by the first network identifier; or when the access type of the network to be registered is the non-public network, determine the cause value, the cause value indicating that the terminal device is rejected to access the non-public network identified by the first network identifier; or determine the cause value, the cause value indicating that the terminal device is rejected to access the network identified by the first network identifier.

[0031] With reference to the first possible implementation manner of the fourth aspect, optionally, the registration rejection message comprises the cause value.

[0032] In the embodiments of the present application, when the user equipment is rejected in network registration, the user equipment can determine whether the network type that cannot be accessed is the public network or the non-public network corresponding to the network identifier, and perform operations corresponding to the public network or the non-public network, so that the registration of the user equipment for the public network and the non-public network identified by using the same network identifier will not affect each other.

[0033] In a fifth aspect, a communication apparatus is provided, which comprises a processor configured to execute a computer program stored in a memory, so that the communication apparatus executes the communication method in any one of the first to sixth possible implementation manners of the first aspect, or executes the communication method in any one of the first to third possible implementation manners of the second aspect.

[0034] In a sixth aspect, a computer readable storage medium is provided, which stores a computer program, when the computer program is executed on a computer, the computer program causes the computer to execute the communication method in any one of the first to sixth possible implementation manners of the first aspect, or execute the communication method in any one of the first to third possible implementation manners of the second aspect.

[0035] In a seventh aspect, a chip system is provided, comprising: a processor configured to invoke and run a computer program from a memory, so that a communication device in which the chip system is installed performs the communication method of any one of the first to sixth possible implementation manners of the first aspect, or performs the communication method of any one of the first to third possible implementation manners of the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0036] Figure 1 is an example of the application scenario of the network registration method of the present application.

[0037] Figure 2 is an example of the technical problem solved by the network registration method of the present application.

[0038] Figure 3 is an example of the network registration method of the present application.

[0039] Figure 4 is an example of the terminal device performing the operation corresponding to the access type of the present application.

[0040] Figure 5 is another example of the network registration method of the present application.

[0041] Figure 6 is a schematic block diagram of another network registration method of the present application.

[0042] Figure 7 is an example of the terminal device of the present application.

[0043] Figure 8 is an example of the network device of the present application.

[0044] Figure 9 is an example of the communication device of the present application.

[0045] Figure 10 is another example of the communication device of the present application.

[0046] Figure 11 is a schematic structural diagram of the terminal device of the present application. DETAILED DESCRIPTION

[0047] In the 5G system, the public network can be a PLMN, and in the future communication system, the public network can still be a PLMN, or can also have other names, which are not limited in the present application. In the 5G system, taking the PLMN as an example, it is identified by a PLMN ID, and one PLMN ID corresponds to one public network PLMN. In the future communication system, the PLMN can still be identified by a PLMN ID, or can also be identified by other identifiers; one identifier can also correspond to one public network, or one identifier can also correspond to multiple public networks, which are not limited in the present application. In the 5G system, the non-public network can be a PNI-NPN, can also be a Non-Public Network (NPN), or can also be a Standalone Non-Public Network (SNPN), and in the future communication system, the non-public network can still be a PNI-NPN or an NPN, or can also be an SNPN, or can also be other networks, which are not limited in the present application.

[0048] In the present application, the "public network" and the "non-public network" are respectively two different access types or two different network types; the "public network", "public network", "public network", "public land mobile network" have the same meaning, and the "private network", "non-public network", "non-public network", "non-public network", "non-public land mobile network" have the same meaning.

[0049] In the 5G communication system, the access management network element can be the Access and Mobility Management Function (AMF) network element described in the present application. In the future communication system, the access management network element can still be an AMF network element, or can also have other names, which are not limited in the present application.

[0050] The (Radio) Access Network ((R)AN) network element is used to provide network access functions for authorized terminal devices in a specific area, and can use transmission tunnels of different qualities according to the level of the terminal device, the demand of the service, etc. The (R)AN network element can manage radio resources, provide access services for terminal devices, and then complete the forwarding of control signals and terminal device data between terminal devices and core networks. The (R)AN network element can also be understood as a base station in the traditional network.

[0051] It should be noted that the above "network element" can also be referred to as an entity, device, apparatus or module, etc., and the present application is not particularly limited. In addition, in order to facilitate understanding and description, the description of "network element" is omitted in part of the description, for example, (R)AN network element is referred to as (R)AN, in which case the "(R)AN network element" should be understood as (R)AN network element or (R)AN entity, and the following description of the same or similar cases is omitted.

[0052] The RAN described in the present application is the NG-RAN in the 5G communication system, and in the future communication system, the RAN can still be the NG-RAN, or can also have other names, which are not limited in the present application.

[0053] The terminal device in the present application can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication function, and various forms of terminals, mobile stations (MS), terminals, user equipment (UE), soft terminals, etc. For example, water meters, electricity meters, sensors, etc.

[0054] The PNI-NPN is to provide NPN services through the PLMN network, for example, by allocating one or more network slice entities to the NPN to realize the non-public network function. Under this type of network, the UE also subscribes to the PLMN network. The PNI-NPN adopts the standard 5G network architecture, but limits the access user to subscribe to the NPN, and can provide slice services corresponding to the NPN through slice selection.

[0055] Since the 5G network does not broadcast network slice selection information (Single Network Slice Selection Assistance Information, S-NSSAI) on the air interface, the slice cannot limit the UE to attempt to access the network in its unauthorized network slice coverage area, so the closed access group (Closed Access Group, CAG) technology is used for access control. CAG represents a group of subscription user groups that can access one or more CAG cells.

[0056] The CAG key technology of the PNI-NPN scheme is determined by the PLMN ID and the CAG ID of the 5G network, and the cell enabled with the CAG only allows the subscription UE to access. The CAG ID is unique within the associated PLMN ID, and a CAG cell can broadcast multiple PLMNs and associated CAG IDs. Each PLMN is associated with one or more CAG IDs (up to 12), and the CAG cell can also broadcast the readable network name according to each CAG ID.

[0057] The UE configures two pieces of information in the configuration data when configuring the CAG, one is the CAG list (Allowed CAG list) that the UE can access, which stores the IDs of all CAG cells that the UE can access and the associated PLMN ID; the other is an indication of whether the UE can only access the network through the CAG cell (CAG-only indication). The UE configured with the indication can only access the network through the CAG cell, and the UE not configured with the indication can access the network through the CAG or not. The network side of the 5G core network can initiate a UE configuration update process to update the configuration on the UE.

[0058] Figure 1 is a schematic diagram of an application scenario of an embodiment of the present application. As shown in Figure 1 In the initial access and cell reselection process, the NG-RAN needs to broadcast the CAG ID and the associated PLMN ID it supports; the UE obtains the CAG information supported by the cell by listening to the cell broadcast, and compares the CAG information listened to with the locally preconfigured CAG information, if there is an intersection, it indicates that the UE can access the hit CAG through the cell. Among them, the UE not configured with the CAG-only indication identifier can select the accessible CAG cell according to its allowed access CAG list, or can select the subscribed public PLMN cell. The UE configured with the CAG-only indication identifier can only select the accessible CAG cell according to the Allowed CAG list configured by itself. The AMF on the core network side can authenticate the identity of the UE according to the subscription information of the user, and synchronize the allowed access CAG list of the UE to the NG-RAN after the authentication is passed. Among them, the network side comprehensively judges whether the access attempt of the UE is legal according to the NG-RAN capability requested by the UE to access (whether it supports CAG and which CAG it supports) and the subscription information of the UE (whether it is configured with the CAG-only indication and which CAGs are in the Allowed CAG list) (whether there is an intersection between the Allowed CAG list of the UE and the CAG supported by the NG-RAN).

[0059] Since PNI-NPN adopts the standard 5G network architecture, the handover between PNI-NPN and public network is supported for the UE which is not configured with the CAG-only indication identifier. The handover from the CAG cell to the PLMN cell needs the base station or the core network side to confirm whether the UE is configured with the CAG-only indication identifier. The handover from the PLMN cell to the CAG cell needs the base station or the AMF to determine whether the CAG ID of the target base station is in the Allowed CAG list of the UE.

[0060] The problem to be solved by the technical solution will be further described below in combination with a specific scenario. It should be understood that the applicable scenarios of the technical solution should not be limited to the specific scenarios mentioned in the present application, and any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application.

[0061] Figure 2 is an example of the technical problem solved by the embodiments of the present application.

[0062] Specifically, in such a scenario, the UE is a 5G network access-capable mobile phone of an employee of company A, the PLMN is the network of China Mobile, and the PNI-NPN is a private network of company A built by China Mobile. The employee of company A has not purchased the 5G service of China Mobile, i.e., cannot access the PLMN; but he needs his mobile phone to be able to access the private network of company A for free, i.e., has the ability to access the PNI-NPN. As shown in Figure 2 When the UE tries to access the public network PLMN of China Mobile, the access attempt of the UE will be rejected because no corresponding package is purchased. When the received rejection message carries the cause value #31 (indicating Redirection to EPC, i.e., falling back to the 4G core network EPC), or #27 (indicating N1 mode not allowed, i.e., the N1 access mode of 5G is not allowed), or the access attempt times (Registration Attempt Counter, RAT) for the PLMN have reached the maximum limit of 5 times, the UE will add the identifier PLMN ID corresponding to the PLMN to a "blacklist" (i.e. Figure 2Forbidden PLMN list). Since PNI-NPN currently has no exclusive ID to identify, but simply uses the PLMN ID corresponding to the public network PLMN associated with it to identify. When the UE does automatic network selection again, it will exclude the network identifiers in the "blacklist", which will cause the UE to also be unable to access the associated PNI-NPN. In this specific scenario, the PLMN and the PNI-NPN share a PLMN ID for identification, resulting in the problem that users cannot access the A company's enterprise private network without purchasing the operator's 5G service, that is, the problem that when the public network cannot be accessed, the private network also cannot be accessed. Similarly, the opposite is also true, that is, when the UE accesses the private network, its access attempt is rejected, and after receiving the rejection message, the UE will also add the PLMN ID corresponding to the PNI-NPN to the same "blacklist", and when the UE does automatic network selection again, it will also exclude the PLMN ID, thereby causing the associated public network to also be unable to access.

[0063] The technical solutions in the embodiments of the present application will be described below with reference to the drawings.

[0064] Figure 3 is a schematic interaction diagram of the network registration method 100 of the embodiments of the present application, which is executed by a terminal device and a network device.

[0065] As shown in Figure 3 , the method 300 includes:

[0066] S310, the terminal device sends a registration request message to the network device, including a first network identifier and an access type of a to-be-registered network;

[0067] For the terminal device side, before sending the registration request message, it has determined that the network identifier of the to-be-registered network that needs to be accessed is the first network identifier, and has also determined that the access type of the to-be-registered network that needs to be accessed is a public network or a non-public network.

[0068] It should be understood that in a 5G communication network, one network identifier can identify one public network and at least one non-public network. Although for non-public networks identified using the same network identifier, they can be distinguished according to the CAG ID, the CAG ID is not transmitted in the interaction information, so the terminal device cannot explicitly request the network device to access a certain non-public network.

[0069] S320, the network device determines to reject the terminal device to access the to-be-registered network;

[0070] The network device judges the access request of the terminal device according to the received registration request message. Mainly according to the first network identifier and the access type of the network to be registered, it is determined that the terminal device requests to access the public network or the non-public network corresponding to the first network identifier, and then it is judged whether the terminal device can access the cell of the network it requests.

[0071] If the judgment result is that the terminal device is allowed to access the request, the network registration is performed according to the existing process, and if the judgment result is that the terminal device is refused to access the network to be registered, the next step is performed.

[0072] Optionally, after the judgment result is that the terminal device is refused to access the network to be registered, the network device can also determine a cause value before performing the next step, which is used to indicate the access request of the terminal device. It can be consistent with the existing one, and the cause value is determined according to the judgment result of refusing access; or the cause value can be determined according to the judgment result of refusing access and the access type of the network to be registered sent by the terminal device.

[0073] Specifically, when the access type of the network to be registered is a public network, the cause value is determined to indicate the refusal to access the public network identified by the first network identifier; or when the access type of the network to be registered is a non-public network, the cause value is determined to indicate the refusal to access the non-public network identified by the first network identifier; or the cause value is determined to indicate the refusal to access the network identified by the first network identifier.

[0074] It should be understood that in the existing 5G communication system, the registration request message sent by the terminal device to the network device only carries the above-mentioned first network identifier, and does not carry the access type of the network to be registered, so the network side cannot determine the corresponding cause value according to the access type of the network to be registered requested by the terminal device to access.

[0075] S330, the network device sends a registration rejection message to the terminal device;

[0076] In S320, after the network device determines to refuse the terminal device to access the network to be registered, the network device sends a registration rejection message to the terminal device in S330.

[0077] Optionally, the "registration rejection message" can carry a cause value, which can be an existing indication that the network device cannot access the network identified by the first network identifier; or it can indicate the type of network that the terminal device cannot access on the basis of refusing the terminal device to access the network to be registered.

[0078] Specifically, the cause value can be used to indicate:

[0079] a public network identified by the first network identifier; or a non-public network identified by the first network identifier; or a network identified by the first network identifier.

[0080] It should be understood that the representation of the cause value can be represented by "#" and numbers, such as #27 and #76 in the existing communication system, and can also be other identifiers, which are not limited in the present application.

[0081] S340, the terminal device performs an operation corresponding to the access type according to at least one of the access type of the network to be registered and the cause value.

[0082] Optionally, after receiving the rejection message, the terminal device can perform an operation corresponding to the access type according to the access type of the network to be registered.

[0083] Optionally, if the received rejection message carries a cause value, the terminal device can perform an operation corresponding to the access type according to the cause value, or according to the access type of the network to be registered and the cause value.

[0084] Specifically, when the cause value indicates that the terminal device cannot access the network identified by the first network identifier, the terminal device performs an operation corresponding to the access type according to the access type of the network to be registered and the cause value; or when the cause value indicates that the terminal device cannot access the public network identified by the first network identifier, or cannot access the non-public network identified by the first network identifier, the terminal device can perform an operation corresponding to the access type according to the cause value.

[0085] It should be understood that in the embodiments of the present application, the cause value is carried in the registration rejection message sent by the network device to the terminal device, and the cause value can also be carried in other messages sent by the network device to the terminal device, which is not limited in the present application.

[0086] Wherein, "performing an operation corresponding to the access type" can be as shown in the following table: Figure 4

[0087] Figure 4 is a schematic interaction diagram of the method 400 of the terminal device performing an operation corresponding to the access type according to the present application.

[0088] Optionally, mode 1: when the access type of the network to be registered is a public network, the first network identifier is added to a first list, the first list indicating that the public network identified by the network identifier in the first list is prohibited to be accessed; or when the access type of the network to be registered is a non-public network, the first network identifier is added to a second list, the second list indicating that the non-public network identified by the network identifier in the second list is prohibited to be accessed.

[0089] ​The first list can also be referred to as a Forbidden list associated with a public network, and the second list can also be referred to as a Forbidden list associated with a non-public network.

[0090] It should be understood that in the existing 5G communication system, the registration request message sent by the terminal device to the network device only carries the first network identifier, and does not carry the access type of the network to be registered, so that the network device cannot give an indication corresponding to the access type of the network to be registered when rejecting the access request of the terminal device. The terminal device will add the first network identifier to a list without distinguishing the access type after receiving the rejection message.

[0091] Optionally, mode 2: when the access type of the network to be registered is a public network, the non-access layer NAS instructs the access layer AS not to select the cells of the public network identified by the network identifiers in the first list; or when the access type of the network to be registered is a non-public network, the NAS layer instructs the AS layer not to select the cells of the non-public network identified by the network identifiers in the second list.

[0092] It should be understood that in the existing 5G communication system, the AS layer can also not exclude the public network or the non-public network corresponding to the network identifiers in the first list and the second list when performing network search, but only exclude the network corresponding to the network identifiers in the existing list without distinguishing the access type. After the AS layer feeds back the search result to the NAS layer, the NAS layer will screen the public network and the non-public network corresponding to the network identifiers in the first list and the second list, respectively.

[0093] Optionally, mode 3: when the access type of the network to be registered is a public network, enter a first state; or when the access type of the network to be registered is a non-public network, enter a second state; the first state and the second state are not the same state.

[0094] Optionally, the first state indicates that the public network cannot be accessed, i.e., the N1 mode associated with the public network is disabled or deactivated; the second state indicates that the non-public network cannot be accessed, i.e., the N1 mode associated with the non-public network is disabled or deactivated. Optionally, the first state indicates that the public network identified by the first network identifier cannot be accessed, i.e., the N1 mode associated with the public network identified by the first network identifier is disabled; the second state indicates that the non-public network identified by the first network identifier cannot be accessed, i.e., the N1 mode associated with the non-public network identified by the first network identifier is disabled.

[0095] It should be understood that the first state and the second state are not the same state, but it cannot be said that the first state and the second state are different, specifically, the "cannot access" in the first state is for the access type of the public network, and the "cannot access" in the second state is for the access type of the non-public network; and when the terminal device cannot access the public network and the non-public network, the first state and the second state are both "cannot access" states for the terminal device. For example, in a communication system, the parameters used to represent the first state and the second state are not the same, and when the terminal device cannot access the public network corresponding to the first network identifier and the non-public network corresponding to the first network identifier, the values of the parameters used to represent the above two states can be the same.

[0096] In addition, taking the 5G communication system as an example, no matter whether the access type of the network to be registered is a public network or a non-public network, the terminal device can also enter a third state, which is that the UE cannot access all networks in the N1 mode, but can access the network in the S1 mode.

[0097] In the present scheme, the implementation of mode 2 is premised on mode 1, and mode 3 does not affect mode 1 and mode 3 does not affect mode 2. When step S340 is performed, only mode 1 can be executed, or only mode 3 can be executed; mode 1 and mode 2 can be executed, or mode 1 and mode 3 can be executed; mode 1, mode 2 and mode 3 can be executed, and the present application does not limit this. When the terminal device performs network operation in one, two or three modes, there is no sequence between different modes, and they can be flexibly combined, and there is no difference in effect when solving the foregoing technical problems.

[0098] According to the network registration method of the present application, when the network registration of the user equipment is rejected, the type of the network that cannot be accessed is determined as the public network or the non-public network corresponding to the network identifier, and the operation corresponding to the public network or the non-public network is performed, so that the registration of the public network and the non-public network using the same network identifier will not affect each other.

[0099] Figure 5 Fig. 500 is a schematic interaction diagram of the network registration method of the embodiment of the present application. In order to facilitate understanding, in the method 500, as an example but not limitation, the AMF is taken as the network device, the UE is taken as the terminal device, and the PLMN ID is taken as the "first network identifier".

[0100] Figure 5is the interaction between the UE and the AMF. It should be understood that in the 5G system, the connection between the UE and the AMF is represented by the N1 interface, and the N1 interface is mainly used for NAS layer signaling transmission. The UE can be directly connected with the AMF through the N1 interface without going through the NG-RAN. The N1 interface can also represent a combined path, i.e., the connection of the UE and the NG-RAN and the connection of the NG-RAN and the AMF.

[0101] In S510, the UE sends a registration request message to the AMF, and the registration request message carries a PLMN ID and an access type;

[0102] The AMF can determine, according to the registration request message, that the UE requests to access the public network or the non-public network identified by the PLMN ID.

[0103] In S520, the AMF determines whether to allow the access of the UE;

[0104] If the determination result is to reject the access, optionally, the AMF determines a cause value according to the received “access type”. When the access type of the network requested by the UE is a public network, the cause value can be determined as #X, indicating that the UE cannot access the public network identified by the PLMN ID; when the access type of the network requested by the UE is a non-public network, the cause value can be determined as #Y, indicating that the UE cannot access the non-public network identified by the PLMN ID. Alternatively, no matter the access type of the network requested by the UE is a public network or a private network, the AMF can determine the cause value #Z, indicating that the UE cannot access the network identified by the PLMN ID. Wherein, X, Y, Z are positive integers. The representation of the cause value is not limited in the present application.

[0105] In S530, the AMF sends a registration feedback message to the UE;

[0106] When the access of the UE is allowed in S520, the network registration is performed, and the subsequent steps are not performed. The AMF sends a registration permission message to the UE, indicating that the request of the UE for network registration is allowed.

[0107] When the access of the UE is rejected in S520, the AMF sends a registration rejection message to the UE, indicating that the access request of the UE is rejected. Optionally, the registration rejection message carries a cause value.

[0108] In S540, the UE adds the PLMN ID to the first list or the second list.

[0109] Optionally, after receiving the registration reject message, the UE can determine that the public network or the non-public network identified by the PLMN ID cannot be accessed, in combination with the network type requested to be accessed. When it is determined that the public network identified by the PLMN ID cannot be accessed, the UE adds the PLMN ID to the first list, which is similar to adding the PLMN ID to the "black list" of the public network. Similarly, when it is determined that the non-public network identified by the PLMN ID cannot be accessed, the UE adds the PLMN ID to the second list, which is similar to adding the PLMN ID to the "black list" of the non-public network.

[0110] Optionally, the registration reject message received by the UE carries a cause value, which is #Z described above. The UE adds the PLMN ID to the first list or the second list according to #Z and the access type of the network requested to be accessed. The specific case is similar to the foregoing case.

[0111] Optionally, when the cause value received by the UE is #X described above, the UE adds the PLMN ID to the first list. When the cause value is #Y described above, the UE adds the PLMN ID to the second list.

[0112] In S550, the UE enters the first state or the second state.

[0113] After receiving the registration reject message, the UE can determine whether the public network or the non-public network corresponding to the PLMN ID cannot be accessed according to the access type of the network requested to be accessed, or according to the received cause value #X or #Y, or according to the access type of the network requested to be accessed and the cause value #Z, and enters the first state and the second state respectively.

[0114] Optionally, after the UE enters the first state, i.e., enters the N1 mode associated with the public network, the UE cannot access the public network corresponding to the PLMN ID in the N1 mode. After the UE enters the second state, i.e., enters the N1 mode associated with the non-public network, the UE cannot access the non-public network corresponding to the PLMN ID in the N1 mode.

[0115] Optionally, after the UE enters the first state, the UE cannot access the public network identified by the first network identifier, i.e., the N1 mode associated with the public network identified by the first network identifier is disabled. After the UE enters the second state, the UE cannot access the non-public network identified by the first network identifier, i.e., the N1 mode associated with the non-public network identified by the first network identifier is disabled. Alternatively, the UE enters the third state only according to the received cause value #Z, and in the third state, the UE cannot access all networks in the 5G communication system.

[0116] It should be understood that the UE entering different states can be implemented by a finite state machine.

[0117] In S560, the NAS layer instructs the AS layer not to search for a cell of a public network corresponding to the PLMN ID in the first list or not to search for a cell of a non-public network corresponding to the PLMN ID in the second list.

[0118] Similarly, the performance of this step is also based on the fact that the UE has determined whether the public network or the non-public network corresponding to the PLMN ID cannot be accessed, and the specific determination method is as described in the steps of S540 and S550, which will not be described here.

[0119] The UE can issue a first instruction to instruct the AS layer not to search for a cell of a public network corresponding to the PLMN ID in the first list, or a second instruction to instruct the AS layer not to search for a cell of a non-public network corresponding to the PLMN ID in the second list, or a third instruction to instruct the AS layer to search only for an Evolved Universal Terrestrial Radio Access (Network) (E-UTRA) cell, an Evolved Universal Radio Access Network (E-URAN) cell, or other 4G cells or other non-NR (New Radio) cells, or non-NG-RAN cells, or other non-5G cells.

[0120] Specifically, when the UE requests to access a public network corresponding to a PLMN ID, if the UE is configured with a CAG-only Indication identifier at this time, the AMF will directly reject the access of the UE. If the UE is not configured with a CAG-only Indication identifier, the AMF directly judges whether the cell requested by the UE allows the UE to access, and when the cell requested by the UE does not allow the UE to access, the AMF sends a registration rejection message to the UE, indicating that the UE cannot access the network.

[0121] Optionally, the registration rejection message includes a cause value #X indicating that the UE cannot access the public network corresponding to the PLMN ID. Alternatively, the registration rejection message includes a cause value #Z indicating that the UE cannot access the network corresponding to the PLMN ID. The UE adds the PLMN ID to the first list in the N1 mode according to #X or according to the requested access type for the public network and #Z, and / or the UE enters the first state, and / or the NAS layer of the UE instructs the AS layer not to search for a public network corresponding to the PLMN ID. Alternatively, the UE only adds the PLMN ID to the existing "blacklist" according to the received cause value #Z, enters the third state, and the NAS layer sends the third instruction to the AS layer.

[0122] Specifically, when the UE requests to access the PNI-NPN corresponding to the PLMN ID, the AMF determines whether the access attempt of the UE is legal according to the capability of the cell requested to be accessed by the UE and the subscription information of the UE. When the requested cell does not allow the UE to access, the AMF sends a registration rejection message to the UE, indicating that the UE cannot access the network. Optionally, the registration rejection message includes #Y, indicating that the UE cannot access the non-public network corresponding to the PLMN ID. Or, the registration feedback message includes #Z, indicating that the UE cannot access the network corresponding to the PLMN ID. The UE adds the PLMN ID to the second list in the N1 mode according to #Y or according to the requested access type for the non-public network and #Z, and / or the UE enters the second state, and / or the NAS layer of the UE indicates the AS layer not to search for the non-public network corresponding to the PLMN ID. Alternatively, the UE only adds the PLMN ID to the existing "blacklist" according to the received reason value #Z, enters the third state, and the NAS layer sends the third indication to the AS layer.

[0123] It should be understood that S540, S550 and S560 can be only one of the operations, such as only S540 or only S550, or two or three of the operations, such as S540 and S550, or S540 and S560, and are not limited to the three operations shown in Figure 5 the figure, nor are they limited to the order of operations, and can be freely combined.

[0124] In the embodiments of the present application, when the user equipment is rejected in network registration, the type of the network that cannot be accessed can be determined as the public network or the non-public network corresponding to the network identifier, and the operation corresponding to the public network or the non-public network is performed, so that the registration of the public network and the non-public network using the same network identifier will not affect each other.

[0125] Figure 6 is another schematic block diagram of a network registration method 600 of the embodiments of the present application, in which the UE performs separate registration for the public network and the non-public network, and the two protocol stacks of the public network and the non-public network do not interfere with each other. The public network can be a 5G network or a 4G or other network. The UE simultaneously maintains two sets of registration contexts. For the public network and the non-public network sharing the same network identifier, when the UE cannot register one type of network, the other type of network will not be affected.

[0126] In the embodiments of the present application, the public network and the non-public network of 5G are directly set as two separate protocol stacks, which do not interfere with each other, and are simple and clear. Even when the public network and the non-public network share the same network identifier, the registration of the public network and the non-public network will not affect each other.

[0127] The above, in combination with Figure 3 to Figure 6The method provided by the embodiments of the present application is described in detail. Hereinafter, the method is described in combination with Figure 7 to Figure 11 The communication apparatus provided by the embodiments of the present application is described in detail.

[0128] Figure 7 FIG. 1 is a schematic block diagram of the communication apparatus provided by the embodiments of the present application. As shown in the figure, the communication apparatus 10 can include a transceiver module 11 and a processing module 12.

[0129] In a possible design, the communication apparatus 10 can correspond to the terminal device in the above method embodiments. For example, the communication apparatus 10 can be a user equipment, or a chip configured in a user equipment.

[0130] Specifically, the communication apparatus 10 can correspond to the terminal device in the method 300, the method 400 and the method 500 according to the embodiments of the present application, and the communication apparatus 10 can include a module for performing the method performed by the terminal device in the method 300, the method 400 and the method 500. Figure 3 Figure 4 Figure 5 Figure 3 Figure 4 Figure 5

[0131] When the communication apparatus 10 is used to perform the method 300 in the method 300, the transceiver module 11 can be configured to perform the step 310 and the step 330 in the method 300, and the processing module 12 can be configured to perform the step 340 in the method 300. Figure 3

[0132] When the communication apparatus 10 is used to perform the method 500 in the method 500, the transceiver module 11 can be configured to perform the step 510 and the step 530 in the method 500, and the processing module 12 can be configured to perform the step 540, the step 550 and the step 560 in the method 300. Figure 5 When the communication apparatus 100 is used to perform the method 400 in the method 400, the processing module 120 can be configured to perform the manner 1, the manner 2 and the manner 3.

[0133] Figure 4

[0134] ​​​​​​​​​In particular, the transceiver 11 is configured to send a registration request message, the registration request message comprising the first network identifier, the registration request message indicating a request to access a network to be registered, the network to be registered being a public network or a non-public network identified by the first network identifier; the transceiver 11 is configured to receive a registration reject message; the processing module 12 is configured to perform an operation corresponding to an access type of the network to be registered according to at least one of the access type and a cause value, the access type comprising a public network and a non-public network.

[0135] Optionally, the processing module 12 can be specifically configured to: when the access type of the network to be registered is a public network, add the first network identifier to a first list, the first list indicating that the communication apparatus 10 is prohibited from accessing a public network identified by a network identifier in the first list; or when the access type of the network to be registered is a non-public network, add the first network identifier to a second list, the second list indicating that the communication apparatus 10 is prohibited from accessing a non-public network identified by a network identifier in the second list.

[0136] Optionally, the processing module 12 can be specifically configured to: when the access type of the network to be registered is a public network, enter a first state; or when the access type of the network to be registered is a non-public network, enter a second state; the first state and the second state are not the same state.

[0137] Optionally, the processing module 12 can be specifically configured to: when the access type of the network to be registered is a public network, enter a first state; or when the access type of the network to be registered is a non-public network, enter a second state; the first state and the second state are not the same state.

[0138] Optionally, the processing module 12 can be specifically configured to: when the access type of the network to be registered is a public network, enter a first state; or when the access type of the network to be registered is a non-public network, enter a second state; the first state and the second state are not the same state.

[0139] Optionally, the processing module 12 can be specifically configured to: when the access type of the network to be registered is a public network, enter a first state; or when the access type of the network to be registered is a non-public network, enter a second state; the first state and the second state are not the same state.

[0140] In particular, the transceiver 11 is specifically configured to receive a cause value, the cause value being included in the registration reject message received by the transceiver 11. The cause value can be used to indicate that the communication apparatus 10 cannot access a public network identified by the first network identifier; or cannot access a non-public network identified by the first network identifier; or cannot access a network identified by the first network identifier.

[0141] Optionally, the registration request message sent by the transceiver 11 can further comprise an access type of the network to be registered.

[0142] Figure 8 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application. As shown in the figure, the communication apparatus 20 can include a transceiver module 21 and a processing module 22.

[0143] In a possible design, the communication apparatus 20 can correspond to the network device in the method embodiments above. For example, the communication apparatus 20 can be an AMF, or a chip configured in an AMF.

[0144] Specifically, the communication apparatus 20 can correspond to the network device in the method 300 and the method 500 according to the embodiments of the present application, and the communication apparatus 20 can include a module for performing the method performed by the network device in the method 300 in the method 300 or the method 500 in the method 500. In addition, each unit in the communication apparatus 20 and the other operations and / or functions described above are respectively configured to implement the corresponding procedures of the method 300 in the method 300 or the method 500 in the method 500. Figure 3 Figure 5 In addition, each unit in the communication apparatus 20 and the other operations and / or functions described above are respectively configured to implement the corresponding procedures of the method 300 in the method 300 or the method 500 in the method 500. Figure 3 Figure 5 In addition, each unit in the communication apparatus 20 and the other operations and / or functions described above are respectively configured to implement the corresponding procedures of the method 300 in the method 300 or the method 500 in the method 500.

[0145] Specifically, when the communication apparatus 20 is configured to perform the method 300 in the method 300, the transceiver module 21 can be configured to perform the step 310 and the step 330 in the method 300, and the processing module 22 can be configured to perform the step 320 in the method 300. Figure 3 When the communication apparatus 20 is configured to perform the method 500 in the method 500, the transceiver module 21 can be configured to perform the step 510 and the step 530 in the method 500, and the processing module 22 can be configured to perform the step 520 in the method 300.

[0146] Figure 5 Specifically, the transceiver module 21 is configured to receive a registration request message, the registration request message including a first network identifier and an access type of a network to be registered, the registration request message indicating that a terminal device requests a network device to access the network to be registered, the access type including a public network and a non-public network, the network to be registered being the public network or the non-public network identified by the first network identifier; the processing module 22 is configured to determine to reject the terminal device to access the network to be registered; and the transceiver module 210 is configured to send a registration rejection message to the terminal device.

[0147] Optionally, the processing module 22 is further configured to determine a cause value according to the access type of the network to be registered, the cause value being used to indicate that the terminal device is rejected to access the network to be registered; and the transceiver module 21 is further configured to send the cause value to the terminal device.

[0148] Optionally, the processing module 22 is further configured to determine a cause value according to the access type of the network to be registered, the cause value being used to indicate that the terminal device is rejected to access the network to be registered; and the transceiver module 21 is further configured to send the cause value to the terminal device.

[0149] ​​​The processing module 22 is specifically configured to: when the access type of the network to be registered is a public network, determine the cause value to indicate rejection of access to the public network identified by the first network identifier; or when the access type of the network to be registered is a non-public network, determine the cause value to indicate rejection of access to the non-public network identified by the first network identifier; or determine the cause value to indicate rejection of access to the network identified by the first network identifier.

[0150] According to the foregoing method, Figure 9 A schematic diagram of a communication device 30 provided by an embodiment of the present application is shown in Figure 9 The device 30 can be a device that needs to perform network registration, including various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems, and various forms of terminals, mobile stations (MS), terminals, user equipment (UE), soft terminals, and the like, which have wireless communication functions.

[0151] The device 30 can include a processor 31 (i.e., an example of a processing module) and a memory 32. The memory 32 is configured to store instructions, and the processor 31 is configured to execute the instructions stored in the memory 32, so that the device 30 implements the steps performed by the device that performs network registration in the corresponding method in Figure 3 、 Figure 4 or Figure 5 .

[0152] Further, the device 30 can further include an input port 33 (i.e., an example of a transceiver module) and an output port 34 (i.e., another example of a transceiver module). Further, the processor 31, the memory 32, the input port 33 and the output port 34 can communicate with each other through internal connection paths to transmit control and / or data signals. The memory 32 is configured to store a computer program, and the processor 31 can be configured to call and run the computer program from the memory 32 to control the input port 33 to receive signals and control the output port 34 to transmit signals, thereby completing the steps of the terminal device in the above method. The memory 32 can be integrated in the processor 31 or can be separately arranged from the processor 31.

[0153] Optionally, if the communication device 30 is a communication device, the input port 33 is a receiver, and the output port 34 is a transmitter. The receiver and the transmitter can be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as a transceiver.

[0154] Optionally, if the communication device 30 is a chip or a circuit, the input port 33 is an input interface, and the output port 34 is an output interface.

[0155] As an implementation manner, the functions of the input port 33 and the output port 34 can be implemented by a transceiver circuit or a transceiver dedicated chip. The processor 31 can be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.

[0156] As another implementation manner, the communication device provided by the embodiment of the present application can be implemented by using a general-purpose computer. That is, program codes for implementing the functions of the processor 31, the input port 33 and the output port 34 are stored in the memory 32, and the general-purpose processor implements the functions of the processor 31, the input port 33 and the output port 34 by executing the codes in the memory 32.

[0157] The modules or units in the communication device 30 can be used to perform the actions or processes performed by the device (e.g., a terminal device) performing network registration in the above method. Here, the detailed description is omitted to avoid redundancy.

[0158] The concepts, explanations, detailed descriptions and other steps related to the technical solutions provided by the embodiments of the present application involved in the device 10 are described in the foregoing method or other embodiments, and are not repeated here.

[0159] According to the foregoing method, Figure 10 The schematic diagram of the communication device 40 provided by the embodiments of the present application is shown in Figure 10 The device 40 can be a device performing network registration, and includes a network element with access management function, such as AMF.

[0160] The device 40 can include a processor 41 (i.e., an example of a processing module) and a memory 42. The memory 42 is configured to store instructions, and the processor 41 is configured to execute the instructions stored in the memory 42, so that the device 40 implements the steps performed by the device performing network registration in the corresponding method in Figure 3 or Figure 5 .

[0161] Further, the device 40 can further include an input port 43 (i.e., an example of a transceiver module) and an output port 44 (i.e., another example of a transceiver module). Further, the processor 41, the memory 42, the input port 43 and the output port 44 can communicate with each other through internal connection paths to transmit control and / or data signals. The memory 42 is configured to store a computer program, and the processor 41 can be configured to call and run the computer program from the memory 42 to control the input port 43 to receive signals and control the output port 44 to send signals, thereby completing the steps of the terminal device in the above method. The memory 42 can be integrated in the processor 41 or can be separately arranged from the processor 41.

[0162] Alternatively, if the communication device 40 is a communication device, the input port 43 is a receiver and the output port 44 is a transmitter. The receiver and transmitter may be the same or different physical entities. When they are the same physical entity, they may be collectively referred to as a transceiver.

[0163] Optionally, if the communication device 40 is a chip or a circuit, the input port 43 is an input interface, and the output port 44 is an output interface.

[0164] As an implementation method, the functions of the input port 43 and the output port 44 can be implemented by a transceiver circuit or a dedicated transceiver chip. The processor 41 can be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.

[0165] As another implementation, it is possible to use a general-purpose computer to implement the communication device provided in the embodiments of the present application. Specifically, the program code that implements the functions of the processor 41, input port 43, and output port 44 is stored in the memory 42, and the general-purpose processor executes the code in the memory 42 to implement the functions of the processor 41, input port 43, and output port 44.

[0166] Among them, each module or unit in the communication device 40 can be used to execute each action or processing process performed by the network side device (ie, network device) during network registration in the above method. Here, in order to avoid redundancy, its detailed description is omitted.

[0167] For the concepts, explanations, detailed descriptions and other steps involved in the device 40 and related to the technical solutions provided in the embodiments of the present application, please refer to the descriptions of these contents in the aforementioned methods or other embodiments, and will not be repeated here.

[0168] Figure 11 This is a schematic diagram of the structure of a terminal device 500 provided in this application. For ease of explanation, Figure 11 Only the main components of the terminal device are shown. Figure 11 As shown, the terminal device 500 includes a processor, a memory, a control circuit, an antenna, and an input and output device.

[0169] The processor is mainly used for processing communication protocols and communication data, and controlling the whole terminal device, executing software programs, and processing data of the software programs, for example, for supporting the terminal device to perform the actions described in the embodiments of the method for indicating a transmission precoding matrix. The memory is mainly used for storing software programs and data, for example, storing the codebook described in the embodiments. The control circuit is mainly used for converting baseband signals and radio frequency signals, and processing radio frequency signals. The control circuit and the antenna can also be called a transceiver, which is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. The input and output devices, such as touch screens, display screens, keyboards, etc., are mainly used for receiving user input data and outputting data to users.

[0170] When the terminal device is powered on, the processor can read the software programs in the storage unit, interpret and execute the instructions of the software programs, and process the data of the software programs. When data needs to be transmitted wirelessly, the processor performs baseband processing on the data to be transmitted, and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal, and transmits the radio frequency signal in the form of electromagnetic waves through the antenna. When data is transmitted to the terminal device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data.

[0171] Those skilled in the art can understand that, for the convenience of description, Figure 11 Only one memory and one processor are shown. In actual terminal devices, there can be multiple processors and memories. The memory can also be referred to as a storage medium or a storage device, and the embodiments of the present application do not limit this.

[0172] As an optional implementation, the processor can include a baseband processor and a central processor. The baseband processor is mainly used for processing communication protocols and communication data, and the central processor is mainly used for controlling the whole terminal device, executing software programs, and processing data of the software programs. Figure 11The processor in the embodiment integrates the functions of the baseband processor and the central processing unit. Those skilled in the art will appreciate that the baseband processor and the central processing unit may also be independent processors interconnected through technologies such as buses. Those skilled in the art will appreciate that a terminal device may include multiple baseband processors to adapt to different network standards, and a terminal device may include multiple central processing units to enhance its processing capabilities, and the various components of the terminal device may be connected through various buses. The baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit may also be expressed as a central processing circuit or a central processing chip. The function of processing the communication protocol and communication data may be built into the processor, or may be stored in a storage unit in the form of a software program, and the processor executes the software program to implement the baseband processing function.

[0173] like Figure 11 As shown, terminal device 500 includes a transceiver unit 510 and a processing unit 520. The transceiver unit may also be referred to as a transceiver, transceiver, transceiver device, etc. Optionally, the device in transceiver unit 510 that implements the receiving function may be considered a receiving unit, and the device in transceiver unit 510 that implements the transmitting function may be considered a transmitting unit, that is, transceiver unit 510 includes a receiving unit and a transmitting unit. For example, the receiving unit may also be referred to as a receiver, receiver, receiving circuit, etc., and the transmitting unit may be referred to as a transmitter, transmitter, or transmitting circuit, etc.

[0174] Figure 11 The terminal device shown can execute each action executed by the terminal device in the above-mentioned method 300, 400 or 500. Here, in order to avoid redundancy, its detailed description is omitted.

[0175] It should be understood that in the embodiments of the present application, the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0176] It should also be understood that the memory in the embodiments of the present application can be a volatile memory or a nonvolatile memory, or can include both volatile and nonvolatile memory. Among them, the nonvolatile memory can be a read-only memory (Read-only memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. The volatile memory can be a random access memory (Random access memory, RAM) used as an external cache. By way of example, but not by way of limitation, many forms of random access memory (Random access memory, RAM) are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Souble data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) and direct memory bus random access memory (Direct rambus RAM, DR RAM).

[0177] The above-described embodiments can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented by software, the above-described embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions described in the embodiments of the present application are wholly or partially generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another, for example, the computer instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (for example, infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. containing one or more available medium collections. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state disk.

[0178] It should be understood that the term "and / or" herein merely describes the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent three cases of A alone, A and B together, and B alone. In addition, the character " / " herein generally represents that the front and rear associated objects are in an "or" relationship.

[0179] It should be understood that in various embodiments of the present application, the size of the sequence number of the above-described processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0180] Those skilled in the art can appreciate that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized in electronic hardware or in a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application. Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be described here. In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0181] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, i.e. can be located in one place or can be distributed on multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment. In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present alone, or two or more units can be integrated in one unit. If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that make contributions to the prior art or parts of the technical solutions can be embodied in the form of software products, which are stored in a storage medium and include a number of instructions for making a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in each embodiment of the present application. The foregoing storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and various program code storage media.

[0182] The above merely provides the specific implementation of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of the changes or replacements within the technical range disclosed by the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A network registration method, characterized in that: include: Sending a registration request message, where the registration request message includes a first network identifier, and the registration request message indicates a request to access a network to be registered, where the network to be registered is a public network or a non-public network identified by the first network identifier; receiving a registration reject message, the registration reject message including a cause value, the cause value being used to indicate a network type for which access is rejected; According to at least one of the access type of the network to be registered and the cause value, an operation corresponding to the access type is performed, where the access type includes a public network and a non-public network.

2. The method according to claim 1, characterized in that The performing of an operation corresponding to the access type includes: When the access type of the network to be registered is a public network, adding the first network identifier to a first list, the first list indicating that access to the public network identified by the network identifier in the first list is prohibited; or When the access type of the network to be registered is a non-public network, the first network identifier is added to a second list, and the second list indicates that access to the non-public network identified by the network identifier in the second list is prohibited.

3. The method according to claim 1 or 2, characterized in that The performing of an operation corresponding to the access type includes: When the access type of the network to be registered is a public network, entering the first state; or When the access type of the network to be registered is a non-public network, entering the second state; The first state and the second state are not the same state.

4. The method according to claim 3, characterized in that The first state indicates that a public network cannot be accessed, and the second state indicates that a non-public network cannot be accessed.

5. The method according to claim 3, characterized in that The first state indicates that the public network identified by the first network identifier cannot be accessed, and the second state indicates that the non-public network identified by the first network identifier cannot be accessed.

6. The method according to claim 2, characterized in that The performing of an operation corresponding to the access type includes: When the access type of the network to be registered is a public network, the non-access stratum NAS instructs the access stratum AS not to select a cell of the public network identified by the network identifier in the first list; or When the access type of the network to be registered is a non-public network, the NAS layer instructs the AS layer not to select a non-public network cell identified by a network identifier in the second list.

7. The method according to claim 1, characterized in that The cause value is used to indicate: cannot access the public network identified by the first network identifier; or cannot access the non-public network identified by the first network identifier; or The network identified by the first network identifier cannot be accessed.

8. The method according to any one of claims 4 to 7, characterized in that The registration request message includes the access type of the network to be registered.

9. A network registration method, characterized in that: include: receiving a registration request message, the registration request message including a first network identifier and an access type of a network to be registered, the registration request message instructing a terminal device to request access to the network to be registered from a network device, the access type including a public network and a non-public network, and the network to be registered being the public network or the non-public network identified by the first network identifier; Determine to deny the terminal device access to the network to be registered; A registration rejection message is sent to the terminal device, where the registration rejection message includes a reason value, where the reason value is used to indicate the type of network to which access is rejected.

10. The method according to claim 9, characterized in that The method further comprises: Determine a cause value according to the access type of the network to be registered, where the cause value is used to indicate that access to the network to be registered is denied; Send the cause value to the terminal device.

11. The method according to claim 10, characterized in that The determination reason value includes: When the access type of the network to be registered is a public network, determining the cause value, where the cause value indicates that access to the public network identified by the first network identifier is denied; or When the access type of the network to be registered is a non-public network, determining the cause value, where the cause value indicates that access to the non-public network identified by the first network identifier is denied; or The cause value is determined, the cause value indicating that access to the network identified by the first network identifier is denied.

12. A network registration device, characterized in that: include: a transceiver module, configured to send a registration request message, the registration request message including a first network identifier, the registration request message indicating a request to access a network to be registered, the network to be registered being a public network or a non-public network identified by the first network identifier; The transceiver module is further configured to receive a registration rejection message, where the registration rejection message includes a cause value, where the cause value is used to indicate a network type for which access is rejected; The processing module is configured to execute an operation corresponding to the access type of the network to be registered and at least one of the cause value, where the access type includes a public network and a non-public network.

13. The device according to claim 12, characterized in that The processing module is specifically used for: When the access type of the network to be registered is a public network, adding the first network identifier to a first list, the first list indicating that access to the public network identified by the network identifier in the first list is prohibited; or When the access type of the network to be registered is a non-public network, the first network identifier is added to a second list, and the second list indicates that access to the non-public network identified by the network identifier in the second list is prohibited.

14. The device according to claim 12 or 13, characterized in that The processing module is further configured to: When the access type of the network to be registered is a public network, entering the first state; or When the access type of the network to be registered is a non-public network, entering the second state; The first state and the second state are not the same state.

15. The device according to claim 14, characterized in that The first state indicates that a public network cannot be accessed, and the second state indicates that a non-public network cannot be accessed.

16. The device according to claim 14, characterized in that The first state indicates that the public network identified by the first network identifier cannot be accessed, and the second state indicates that the non-public network identified by the first network identifier cannot be accessed.

17. The device according to claim 13, characterized in that The processing module is further configured to: When the access type of the network to be registered is a public network, the non-access stratum NAS instructs the access stratum AS not to select a cell of the public network identified by the network identifier in the first list; or When the access type of the network to be registered is a non-public network, the NAS layer instructs the AS layer not to select a non-public network cell identified by a network identifier in the second list.

18. The device according to claim 12, characterized in that The cause value is used to indicate: cannot access the public network identified by the first network identifier; or cannot access the non-public network identified by the first network identifier; or The network identified by the first network identifier cannot be accessed.

19. The device according to any one of claims 15 to 18, characterized in that The registration request message includes the access type of the network to be registered.

20. A network registration device, characterized in that: include: a transceiver module, configured to receive a registration request message, the registration request message including a first network identifier and an access type of a network to be registered, the registration request message instructing a terminal device to request access to the network to be registered from a network device, the access type including a public network and a non-public network, and the network to be registered being the public network or the non-public network identified by the first network identifier; A processing module, configured to determine whether to deny the terminal device access to the network to be registered; The transceiver module is further configured to send a registration rejection message to the terminal device, where the registration rejection message includes a reason value, and the reason value is configured to indicate a network type for which access is rejected.

21. The device according to claim 20, characterized in that The processing module is further configured to determine a cause value according to the access type of the network to be registered, wherein the cause value is used to indicate that the terminal device refuses to access the network to be registered; The transceiver module is further configured to send the cause value to the terminal device.

22. The device according to claim 21, characterized in that The processing module is specifically used for: When the access type of the network to be registered is a public network, determining the cause value, where the cause value indicates that access to the public network identified by the first network identifier is denied; or When the access type of the network to be registered is a non-public network, determining the cause value, where the cause value indicates that access to the non-public network identified by the first network identifier is denied; or The cause value is determined, the cause value indicating that access to the network identified by the first network identifier is denied.

23. A communication device, characterized in that: include: A processor, configured to execute a computer program stored in a memory, so that the communication device executes the method according to any one of claims 1 to 8, or executes the method according to any one of claims 9 to 11.

24. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed on a computer, enables the computer to execute the method according to any one of claims 1 to 8 or the method according to any one of claims 9 to 11.

25. A chip system, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a communication device equipped with the chip system executes the method according to any one of claims 1 to 8, or executes the method according to any one of claims 9 to 11.

Images