WO2022083438A1 - Network registration method - Google Patents

Abstract

The present application provides a network registration method and apparatus. Said method comprises: a terminal device sending a registration request message to a network device, the registration request message comprising a first network identifier, and 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; and the terminal device receiving a registration rejection message sent by the network device, and according to at least one of an access type of the network to be registered and a cause value, performing an operation corresponding to the access type, the access type comprising the public network and the non-public network. Thus, according to the method and apparatus of the present application, when network registration is rejected, it can be determined whether the network type for which access cannot be performed 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 registrations of the public network and the non-public network identified using the same network identifier by user equipment do not impact on each other.

Description

How to register online

This application claims the priority of the Chinese patent application with the application number 202011132345.4 and the invention titled "Method of Network Registration" filed with the State Intellectual Property Office of China on October 21, 2020, the entire contents of which are incorporated into this application by reference.

technical field

The embodiments of the present application relate to the field of communications, and more particularly, to a method for network registration.

Background technique

In the 5G core network (5G Core Network, 5GC), the public network integrated non-public network (Public Network Integrated Non-Public Network, PNI-NPN) relies on the public network (Public Land Mobile Network, PLMN) with the help of, for example, network slices (Network Slicing), dedicated data network (Dedicated Date Network Name, Dedicated DNN) and other technologies realize functions similar to enterprise private networks.

The PLMN can be identified by the PLMN ID. For PNI-NPN, there is currently no dedicated ID to identify, but simply use the PLMN ID corresponding to the PLMN to which it is associated. When a PLMN cannot be accessed, the user equipment (User Equipment, UE) will add the PLMN ID corresponding to the PLMN to a list (Forbidden PLMN list). When the UE performs automatic network selection again, it will not select the cell corresponding to the PLMN ID in the list, so that the UE cannot access the PNI-NPN associated with the PLMN ID. Similarly, when the UE cannot access a certain PNI-NPN, the UE cannot access the PLMN identified by the same PLMN ID.

Therefore, the UE's network registration for the PLMN and PNI-NPN sharing the same PLMN ID will affect each other.

SUMMARY OF THE INVENTION

The embodiment of the present application provides a method for network registration, which can ensure that when a terminal device cannot register with the public network, its registration on the non-public network will not be affected under the condition that the public network and the non-public network share the same network identifier. ,vice versa.

A first aspect provides a method for network registration, the method comprising: sending a registration request message, where the registration request message includes a first network identifier, the registration request message indicates a request to access a to-be-registered network, and the to-be-registered network is A public network or a non-public network identified by the first network identifier; receiving a registration rejection message; Types include public and non-public networks.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the performing an operation corresponding to the access type includes: when the access type of the network to be registered is a public network, performing the operation corresponding to the first The network identifier is added to the first list, and the first list indicates 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 list The 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.

In combination with the first aspect, or in combination with the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the performing an operation corresponding to the access type includes: when the to-be-registered When the access type of the network is the public network, it enters the first state; or when the access type of the network to be registered is non-public network, it enters the second state; the first state and the second state are not the same state.

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.

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 first network identifier cannot be accessed. The identified non-public network.

In combination with the first aspect, or in combination with 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 the public network, the non-access stratum NAS instructs the access stratum AS that the cell of the public network identified by the network identifier in the first list cannot be selected; or when the access type of the network to be registered is the public network; When the access type is non-public network, the NAS layer instructs the AS layer that the non-public network cell identified by the network identifier in the second list cannot be selected.

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

In combination with the first aspect, or in combination with any one of the first to fourth possible implementations of the first aspect, in a fifth possible implementation of the first aspect, the registration rejection message Include the reason value.

In combination with the first aspect, or in combination with any one of the first to fifth possible implementations of the first aspect, in the sixth possible implementation of the first aspect, the registration request message Include the access type of the network to be registered.

In a second aspect, a method for network registration is provided, the method includes: receiving a registration request message, where the registration request message includes a first network identifier and an access type of the network to be registered, the registration request message instructing the terminal device to register with the network The device requests to access the to-be-registered network, the access type includes public network and non-public network, and the to-be-registered network is the public network or the non-public network identified by the first network identifier; it is determined to refuse the terminal device to access the network. The network to be registered; send a registration rejection message to the terminal device.

With reference to the second aspect, 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, and the cause value is used to indicate refusal to access the network to be registered; send to the terminal device The reason value.

With reference to the first possible implementation manner of the second aspect, in the second possible implementation manner of the second aspect, the determining the cause value includes: when the access type of the network to be registered is a public network, determining the cause value , the reason value indicates that access to the public network identified by the first network identifier is refused; or when the access type of the network to be registered is a non-public network, the reason value is determined, and the reason value indicates that access to the first network is refused the non-public network identified by the identifier; or the cause value is determined, the cause value indicating that access to the network identified by the first network identifier is refused.

With reference to 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 includes the reason value.

A third aspect provides an apparatus for network registration, the apparatus comprising: a transceiver module for 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 to-be-registered network, The to-be-registered network is 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; the processing module is configured to receive a registration rejection message according to the access type and cause value of the to-be-registered network At least one of the access types, perform operations corresponding to the access types, where the access types include public networks and non-public networks.

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 to the first network identifier list, the first list indicates 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 the second A list, where the second list indicates that access to the non-public network identified by the network identifier in the second list is prohibited.

In combination with the third aspect, or in combination with the first possible implementation manner of the third aspect, in the 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 When it is a public network, it enters the first state; or when the access type of the network to be registered is a non-public network, it enters the second state; the first state and the second state are not the same state.

With reference to the second possible implementation manner of the third 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.

With reference to the second possible implementation manner of the third 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 first network identifier cannot be accessed. The identified non-public network.

In combination with the first or second possible implementation manner of the third aspect, in the 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 public network, the non-access stratum NAS indicates that the access stratum AS cannot select the public network cell identified by the network identifier in the first list; or when the access type of the network to be registered is non-public network, the NAS layer indicates The AS layer cannot select the non-public network cell identified by the network identifier in the second list.

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

In combination with the third aspect, or in combination with any one of the first to fourth possible implementations of the third aspect, in a fifth possible implementation of the third aspect, the registration rejection message Include the reason value.

In combination with any one of the first to fifth possible implementations of the third aspect, in a sixth possible implementation of the first aspect, the registration request message includes the network to be registered access type.

In a fourth aspect, a network registration device is provided, the device comprising: a transceiver module for receiving a registration request message, where the registration request message includes a first network identifier and an access type of the network to be registered, the registration request message Instruct the terminal device to request from the network device to access the network to be registered, the access type includes a public network and a non-public network, and the network to be registered is the public network or the non-public network identified by the first network identifier; processing module , which is used for determining to refuse the terminal equipment to access the network to be registered; the transceiver module is also used for sending a registration rejection message to the terminal equipment.

With reference to the fourth aspect, in a possible first implementation manner of the fourth aspect, the processing module is further configured to determine a cause value according to the access type of the network to be registered, where the cause value is used to indicate that the terminal device refuses to access the The network to be registered; the transceiver module is further configured to send the cause value to the terminal device.

With reference to the first possible implementation manner of the fourth aspect, optionally, the processing module is further configured to: when the access type of the network to be registered is a public network, determine the cause value, and the cause value indicates that access to the first network is refused. A public network identified by a network identifier; or when the access type of the network to be registered is a non-public network, determine the cause value, which indicates that access to the non-public network identified by the first network identifier is refused; or determine The reason value, the reason value indicating that access to the network identified by the first network identifier is denied.

With reference to the first possible implementation manner of the fourth aspect, optionally, the registration rejection message includes the reason value.

In the embodiment of the present application, when the network registration is rejected, the user equipment may determine whether the inaccessible network type is the public network corresponding to the network identifier or the non-public network, and perform operations corresponding to the public network or the non-public network, so that the user equipment Registrations on public and non-public networks identified by the same network identifier will not affect each other.

A fifth aspect provides a communication device, the device comprising: a processor for executing a computer program stored in a memory, so that the communication device executes any one of the first to sixth possibilities of the first aspect The communication method in the implementation manner of the second aspect, or the communication method in any one of the first to third possible implementation manners of the second aspect.

In a sixth aspect, a computer-readable storage medium is provided, and a computer program is stored on the computer-readable storage medium, and when the computer program runs on a computer, the computer is made to execute the first to sixth aspects of the first aspect The communication method in any of the possible implementations, or the communication method in any of the first to third possible implementations of the second aspect is performed.

In a seventh aspect, a chip system is provided, the chip system includes: a processor for calling and running a computer program from a memory, so that a communication device installed with the chip system executes the first to sixth aspects of the first aspect The communication method in any one of the six possible implementations, or the communication method in any one of the first to third possible implementations of the second aspect.

Description of drawings

FIG. 1 is a schematic structural diagram of an example of an application scenario of the method for network registration of the present application.

FIG. 2 is a schematic structural diagram of an example of the technical problem solved by the method for network registration of the present application.

FIG. 3 is a schematic interaction diagram of an example of the network registration method of the present application.

FIG. 4 is a schematic interaction diagram of an operation corresponding to an access type performed by a terminal device of the present application.

FIG. 5 is a schematic interaction diagram of still another example of the network registration method of the present application.

FIG. 6 is a schematic block diagram of still another method for network registration of the present application.

FIG. 7 is a schematic block diagram of an example of a terminal device of the present application.

FIG. 8 is a schematic block diagram of an example of a network device of the present application.

FIG. 9 is a schematic block diagram of an example of a communication device of the present application.

FIG. 10 is a schematic block diagram of still another example of the communication device of the present application.

FIG. 11 is a schematic structural diagram of a terminal device of the present application.

Detailed ways

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

The "public network" and "non-public network" mentioned in this application are two different access types, or two different network types; "public network", "public network", "public network" The meanings of "private network", "non-public network", "non-public network", "non-public network" and "non-public land mobile network" are the same.

In a 5G communication system, the access management network element may be the access management function (Access and Mobility Management Function, AMF) network element described in this application. In the future communication system, the access management network element may still be an AMF network element, or may have other names, which are not limited in this application.

The (Radio Access Network, (R)AN) network element is used to provide network access functions for authorized terminal equipment in a specific area, and can use different quality transmission tunnels according to the level of terminal equipment and service requirements. The (R)AN network element can manage wireless resources, provide access services for terminal equipment, and then complete the forwarding of control signals and terminal equipment data between the terminal equipment and the core network. The (R)AN network element can also be understood as a traditional network. in the base station.

It should be noted that the above-mentioned "network element" may also be referred to as an entity, a device, an apparatus, or a module, etc., which is not particularly limited in this application. In addition, in this application, in order to facilitate understanding and description, the description of "network element" is omitted in some descriptions. For example, the (R)AN network element is abbreviated as (R)AN, in this case, the "(R)AN ")AN network element" should be understood as (R)AN network element or (R)AN entity, and below, the description of the same or similar situations is omitted.

The RAN described in this application is the NG-RAN in the 5G communication system. In the future communication system, the RAN may still be the NG-RAN, or may have other names, which are not limited in this application.

Terminal devices in this application may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems with wireless communication functions, as well as various forms of terminals, mobile stations (Mobile Station, MS), terminal (Terminal), user equipment UE, soft terminal and so on. For example, water meters, electricity meters, sensors, etc.

PNI-NPN provides NPN services through the PLMN network, for example, by allocating one or more network slice entities for the NPN to realize non-public network functions. Under this type of network, the UE also subscribes to the PLMN network. PNI-NPN adopts the standard 5G network architecture, but restricts access users to sign up for NPN, and can provide slice services corresponding to NPN through slice selection.

Since the 5G network does not broadcast Network Slice Selection Assistance Information (S-NSSAI) on the air interface, slicing cannot restrict the UE from attempting to access the network in its unauthorized network slice coverage area, so it is necessary to use The Closed Access Group (CAG) technology is used for access control. A CAG represents a group of subscribers that can access one or more CAG cells.

The key technology of the PNI-NPN solution, CAG, is jointly determined by the PLMNID and CAGID of the 5G network. A cell with CAG enabled is only allowed to access UEs. The CAG ID is unique within the associated PLMNID, 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 a readable network name according to each CAGID.

When configuring the CAG, the UE will configure two pieces of information in the configuration data. One is the CAG list that the UE can access (Allowed CAG list), which stores the IDs of all CAG cells that the UE can access and the associated CAG cells. PLMN ID; the other is the identification of whether the UE can only access the network through the CAG cell (CAG-only indication). The UE configured with this identification can only access the network through the CAG cell, and the UE without the identification It is also possible to access the network by not using the CAG method. The network side of the 5G core network can initiate a UE configuration update process to update the configuration on the UE.

FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application. As shown in Figure 1, in the process of initial access and cell reselection, the NG-RAN needs to broadcast the CAGID and the associated PLMN ID it supports; the UE obtains the CAG information supported by the cell by listening to the cell broadcast, and monitors the CAG information it monitors. The CAG information is compared with the locally pre-configured CAG information, and if there is an intersection between the two, it indicates that the UE can access the hit CAG through the cell. Among them, the UE that is not configured with the CAG-only indication can select an accessible CAG cell according to its own access-allowed CAG list, or can select a subscribed public PLMN cell. The UE configured with the CAG-only indication can only select accessible CAG cells 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 user's subscription information, and after the authentication is passed, synchronize the CAG list of the UE that is allowed to access to the NG-RAN. Among them, the network side comprehensively judges the access of the UE according to the NG-RAN capability requested by the UE to access (whether CAG is supported, which CAGs are supported) and the subscription information of the UE (whether CAG-only indication is configured, and which CAGs are in the Allowed CAG list). Whether the incoming attempt is legal (whether there is an intersection between the UE's Allowed CAG list and the CAG supported by the NG-RAN).

Since PNI-NPN adopts a standard 5G network architecture, handover between PNI-NPN and the public network is supported for UEs that are not configured with CAG-only indication. The handover from the CAG cell to the PLMN cell requires the base station or the core network side to confirm whether the UE is configured with the CAG-only indication. The handover from the PLMN cell to the CAG cell requires the base station or the AMF to determine whether the CAGID of the target base station is in the UE's Allowed CAG list.

The problem to be solved by the technical solution will be further elaborated below in conjunction with a specific scenario. It should be understood that the applicable scenario of the technical solution should not be limited to the specific scenario mentioned in this application. Within the technical scope disclosed in the application, changes or substitutions can be easily conceived, which should all be covered by the protection scope of this application.

FIG. 2 is a schematic diagram of an example of a technical problem solved by an embodiment of the present application.

Specifically, in such a scenario, UE is a mobile phone of Company A's employees capable of accessing the 5G network, PLMN is China Mobile's network, and PNI-NPN is an enterprise private network commissioned by Company A to build by China Mobile. Company A's employees have not purchased China Mobile's 5G services, that is, they cannot access PLMN; but they need their mobile phones to be able to access Company A's private network for free, that is, they have the ability to access PNI-NPN. As shown in FIG. 2 , when the UE attempts to access the public network PLMN of China Mobile, the access attempt of the UE will be rejected because the corresponding package has not been purchased. When the received rejection message carries the reason value #31 (indicates Redirection to EPC, that is, falls back to 4G core network EPC), or #27 (indicates N1 mode not allowed, that is, 5G N1 access mode is not allowed), or When the number of access attempts (Registration Attempt Counter, RAT) corresponding to the PLMN has reached the maximum limit of 5 times, the UE will add the identifier PLMN ID corresponding to the PLMN to a "blacklist" (that is, Forbidden in Figure 2). PLMN list). Since PNI-NPN does not currently have a dedicated ID to identify it, it is simply identified by the PLMN ID corresponding to its associated public network PLMN. When the UE performs automatic network selection again, the network identifiers in the "blacklist" will be excluded, which will cause the UE to be unable to access the associated PNI-NPN. In this specific scenario, PLMN and PNI-NPN share a PLMN ID for identification, which leads to the problem that users cannot access company A's private network without purchasing the operator's 5G service. When the network cannot be accessed, the private network cannot be accessed. The same is true, and vice versa, that is, when the UE accesses the private network, its access attempt is rejected. After receiving the rejection message, the UE will also add the PLMN ID corresponding to the PNI-NPN to the same "blacklist". When the UE performs automatic network selection again, the PLMN ID will be excluded, so that the associated public network cannot be accessed.

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

FIG. 3 is a schematic interaction diagram of a method 100 for network registration according to an embodiment of the present application, where the method 100 is executed by a terminal device and a network device.

As shown in Figure 3, the method 300 includes:

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

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

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

S320, the network device determines to refuse the terminal device to access the to-be-registered network;

The network device judges the access request of the terminal device according to the received registration request message. Mainly based on the first network identifier and the access type of the network to be registered, determine whether the terminal device requests access to the public network or non-public network corresponding to the first network identifier, and then determine whether the terminal device can access the network. The cell of the requested network.

If the judging result is a request for allowing the terminal device to access, network registration is performed according to the existing process, and if the judging result is that the terminal device is denied access to the to-be-registered network, the next step is performed.

Optionally, after the judgment result is that the terminal device is refused access to the network to be registered, before proceeding to the next step, the network device may further determine a cause value, and use the cause value to indicate the rejection of the terminal device's access request. The reason value may be determined according to the judgment result of access refusal, which is consistent with the existing ones; or the cause value may be determined according to the judgment result of access refusal and the access type of the network to be registered sent by the terminal device.

Specifically, when the access type of the network to be registered is a public network, the determination reason value is used to indicate that access to the public network identified by the first network identifier is refused; or when the access type of the network to be registered is a non-public network, The determination cause value is used to indicate refusal to access the non-public network identified by the first network identifier; or the determination cause value is used to indicate the refusal to access the network identified by the first network identifier.

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. The access type of the to-be-registered network that the terminal device requests to access determines the corresponding cause value.

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

In S320, after the network device determines that the terminal device is to be denied access to the network to be registered after judging, in step S330, a registration rejection message is sent to the terminal device.

Optionally, the "registration rejection message" may carry a reason value, which may be an existing network device indicating that the network device cannot access the network identified by the first network identifier; On the basis of , it indicates the type of network that the terminal device cannot access.

Specifically, the reason value can be 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 cannot access the network identified by the first network identifier.

It should be understood that the representation of the cause value may be represented by "#" and numbers, and may be #27 and #76 in the existing communication system, or may be other identifiers, which are not limited in this application.

S340: The terminal device performs an operation corresponding to the access type according to at least one of the access type and the cause value of the network to be registered.

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

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

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 and the cause value of the network to be registered; 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 and access the network according to the cause value. type of operation.

It should be understood that, in the embodiment of the present application, the reason value is carried in the registration rejection message sent by the network device to the terminal device, and the reason value may also be carried in other messages that the network device sends to the terminal device. This is not limited.

Wherein, "execute the operation corresponding to the access type" may be as shown in Figure 4:

FIG. 4 is a schematic interaction diagram of a method 400 for a terminal device of the present application to perform an operation corresponding to an access type.

Optionally, method 1: when the access type of the network to be registered is a public network, a first network identifier is added to a first list, where the first list indicates that access to the network identifiers 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 the second list, and the second list indicates that access to the network identifiers in the second list is prohibited The identified non-public network.

Among them, the "first list" can also be expressed as the Forbidden list associated with the public network; the "second list" can also be expressed as the Forbidden list associated with the non-public network.

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. Therefore, the network device is rejecting the terminal. The device's access request also cannot give an indication corresponding to the access type of the network to be registered. After receiving the rejection message, the terminal device will add the first network identifier to a list that does not distinguish between access types.

Optionally, Manner 2: when the access type of the network to be registered is a public network, the non-access stratum NAS instructs the access stratum AS that the cell of the public network identified by the network identifier in the above-mentioned first list cannot be selected; Or, when the access type of the network to be registered is a non-public network, the NAS layer instructs the AS layer that the non-public network cell identified by the network identifier in the second list cannot be selected.

It should be understood that, taking the existing 5G communication system as an example, when the AS layer performs a network search, it may not exclude the public or non-public networks corresponding to the network identifiers in the first list and the second list, and only exclude the existing network. For some networks corresponding to the network identifiers in the "list that do not distinguish between access types", when the AS layer feeds back the search results to the NAS layer, the NAS layer will respectively analyze the above-mentioned "first list" and "second list". The public network and non-public network corresponding to the network identifier in the filter are filtered.

Optionally, way 3: when the access type of the network to be registered is public network, enter the first state; or when the access type of the network to be registered is non-public network, enter the second state; the first state is not the same state as the second state.

Wherein, optionally, the first state indicates that the public network cannot be accessed, that is, the N1 mode associated with the public network is disabled, or the N1 mode associated with the public network is deactivated; the second state indicates that the private network cannot be accessed. network, that is, the N1 mode associated with the non-public network is disabled, or the N1 mode associated with the non-public network is deactivated. Optionally, the first state indicates that the public network identified by the first network identifier cannot be accessed, that is, the N1 mode associated with the public network identified by the first network identifier is disabled; the second state indicates that the public network cannot be accessed. Access to the non-public network identified by the first network identifier, that is, the N1 mode associated with the non-public network identified by the first network identifier is disabled.

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. As far as the network is concerned, "cannot access" in the second state is for the access type of non-public network; and when the terminal device can neither access the public network nor the non-public network, the first state and the third state The two states are both "inaccessible" states for the terminal device. For example, in a communication system, the parameters used to represent the first state and the second state are different, and when the terminal device can neither access the public network corresponding to the first network identifier nor access the corresponding network identifier of the first network When the non-public network is used, the values of the parameters used to represent the above two states can be the same.

In addition, taking the 5G communication system as an example, regardless of 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. The third state is that the UE cannot access all networks in the N1 mode. But it can access the network in S1 mode.

In this solution, the realization of mode 2 is based on the premise of mode 1, and mode 3 and mode 1, and mode 3 and mode 2 do not affect each other. When performing step S340, only mode 1, or only mode 3 may be executed; mode 1 and mode 2, or modes 1 and 3 may also be executed; mode 1, mode 2, and mode 3 may also be executed, and this application Not limited. When the terminal device performs one, two or three of the network operations, there is no sequence between the different methods, and they can be combined flexibly, and the effects that can be achieved when solving the aforementioned technical problems are not good or bad. points.

According to the network registration method of the present application, when the network registration is rejected, the user equipment can determine whether the inaccessible network type is the public network corresponding to the network identifier or the non-public network, and perform operations corresponding to the public network or non-public network , so that the registration of the user equipment on the public network and the non-public network identified by the same network identifier will not affect each other.

FIG. 5 is a schematic interaction diagram of a method 500 for network registration according to an embodiment of the present application. In addition, for ease of understanding, in the method 500, as an example and not a limitation, the AMF is used as the network device, the UE is used as the terminal device, and the PLMNID is used as the "first network identifier" as an example for description.

Figure 5 is the interaction between UE and 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 directly connect to the AMF through the N1 interface without going through the NG-RAN. The N1 interface can also represent a combined path, ie the connection of the UE to the NG-RAN and the connection of the NG-RAN to the AMF.

In S510, the UE sends a registration request message to the AMF, where the registration request message carries the PLMN ID and the access type;

The AMF may determine, according to the registration request message, whether the UE requests to access the public network or non-public network identified by the PLMN ID.

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

If the judgment result is access rejection, optionally, the AMF determines the cause value according to the received "access type". When the access type of the network requested by the UE is the public network, the cause value may 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, it can be determined that the cause value is #Y, indicating that the UE cannot access the non-public network identified by the PLMN ID. Alternatively, regardless of whether 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. Among them, X, Y, Z are positive integers. The present application does not limit the representation of the cause value.

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

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

When the AMF determines in step S520 that the access of the UE is rejected, 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 reason value.

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

Optionally, after receiving the registration rejection message, the UE may determine that it cannot access the public network or non-public network identified by the PLMN ID in combination with the network type requested to access. When it is determined that the public network identified by the PLMN ID cannot be accessed, the PLMN ID is added to the first list, which is similar to adding the PLMN ID to the "blacklist" of the public network. Similarly, when it is determined that the non-public network identified by the PLMN ID cannot be accessed, the PLMN ID is added to the second list, which is similar to adding the PLMN ID to the "blacklist" of the non-public network.

Optionally, the registration rejection message received by the UE carries a cause value, and the cause value is the above #Z, and the UE adds the PLMN ID to the first list or the first list according to #Z and the access type of the network requesting access, respectively. The second list, the specific situation is similar to the previous one.

Optionally, when the cause value received by the UE is the above #X, the UE adds the PLMN ID to the first list, and when the cause value is the above #Y, the UE adds the PLMN ID to the second list.

In S550, the UE enters the first state or the second state.

After the UE receives the registration rejection message, it can be based on the access type of the network requested to be accessed as public network or non-public network, or according to the received reason value is #X or #Y, or according to the access type of the network requested to access Enter type and reason value #Z, determine whether the public network or non-public network corresponding to the PLMN ID cannot be accessed, and enter the first state and the second state respectively.

Optionally, after the UE enters the first state, that is, after entering the N1 mode associated with deactivating the public network, it cannot access the public network corresponding to the PLMN ID in the N1 mode; after the UE enters the second state, that is, entering the After deactivating the N1 mode associated with the non-public network, the private network corresponding to the PLMN ID cannot be accessed in the N1 mode.

Optionally, after the UE enters the first state, it cannot access the public network identified by the first network identifier, that is, the N1 mode associated with the public network identified by the first network identifier is disabled; the UE enters After the second state, the non-public network identified by the first network identifier cannot be accessed, that is, 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, in which the UE cannot access all networks in the 5G communication system.

It should be understood that the entry of the UE into different states may be implemented by a finite state machine.

In S560, the NAS layer instructs the AS layer not to search for the cells of the public network corresponding to the PLMN IDs in the first list or not to search for the cells of the non-public network with the PLMN IDs in the second list.

Similarly, this step is also performed on the basis that the UE has determined that it cannot access the public network or non-public network corresponding to the PLMN ID. The specific determination method is as described in the previous steps of S540 and S550, and will not be repeated here. .

The UE may issue a first instruction to instruct the AS layer not to search for the cells of the public network corresponding to the PLMN IDs in the first list; it may also issue a second instruction to instruct the AS layer not to search for the cells corresponding to the PLMN IDs in the second list. It can also issue a third instruction, instructing the AS layer to only search for the evolved Universal Terrestrial Radio Access (Network) (Evolved Universal Terrestrial Radio Access (Network), E-UTRA) cell, the evolved universal Evolved Universal Radio Access Network (E-URAN) cells, or other 4G cells or other non-NR (New Radio) cells, or non-NG-RAN cells, or other non-5G cells.

Specifically, when the UE requests to access the public network corresponding to the PLMN ID, if the UE is configured with the CAG-only Indication identifier at this time, the AMF will directly reject the UE's access. If the UE is not configured with the CAG-only Indication flag, the AMF directly determines whether the cell requested by the UE allows the UE to access. 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. .

Optionally, the registration rejection message includes a reason 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 as public network and #Z, and/or the UE enters the first state, and/or the NAS layer of the UE indicates The AS layer does not search the public network corresponding to the PLMN ID. Or, the UE only adds the PLMN ID to the existing "blacklist" according to the received cause value #Z, and enters the above-mentioned third state, and the NAS layer sends the above-mentioned third indication to the AS layer.

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 the UE requests to access 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. Alternatively, 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 of non-public network and #Z, and/or the UE enters the second state, and/or the NAS layer of the UE Instructs the AS layer not to search 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 cause value #Z, and enters the above-mentioned third state, and the NAS layer sends the above-mentioned third indication to the AS layer.

It should be understood that, for S540, S550 and S560, only one of the operations can be performed independently, such as only S540 or only S550, or two or three of them, such as S540 and S550, or S540 and S560. , is not limited to the operations performed together by the three items as shown in FIG. 5 , nor is it limited to such an operation sequence, and can be freely combined.

In the embodiment of the present application, when the network registration is rejected, the user equipment may determine whether the inaccessible network type is the public network corresponding to the network identifier or the non-public network, and perform operations corresponding to the public network or the non-public network, so that the user equipment Registrations on public and non-public networks identified by the same network identifier will not affect each other.

6 is a schematic block diagram of another method 600 for network registration according to an embodiment of the present application. In this method, the UE performs separate registration for the public network and the non-public network, and the two sets of protocol stacks of the public network and the non-public network do not interfere with each other. The public network may be a 5G network or a 4G or other network. The UE maintains two sets of registered contexts at the same time. For public networks and non-public networks that share the same network identifier, when the UE cannot register with one type of network, the other type of network will not be affected.

In the embodiment of this 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 can be prevented from affecting each other.

In the above, the methods provided by the embodiments of the present application are described in detail with reference to FIG. 3 to FIG. 6 . Hereinafter, the communication apparatus provided by the embodiments of the present application will be described in detail with reference to FIG. 7 to FIG. 11 .

FIG. 7 is a schematic block diagram of a communication apparatus provided by an embodiment of the present application. As shown in the figure, the communication device 10 may include a transceiver module 11 and a processing module 12 .

In a possible design, the communication apparatus 10 may correspond to the terminal device in the above method embodiment. For example, it may be user equipment, or a chip configured in the user equipment.

Specifically, the communication apparatus 10 may 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 may include a method for executing the method 300 in FIG. 3 or the method in FIG. 4 400 or the modules of the method performed by the terminal device in the method 500 in FIG. 5 . In addition, each unit in the communication device 10 and the above-mentioned other operations and/or functions are respectively to implement the corresponding flow of the method 300 in FIG. 3 or the method 400 in FIG. 4 or the method 500 in FIG. 5 .

Wherein, when the communication device 10 is used to execute the method 300 in FIG. 3 , the transceiver module 11 can be used to execute the steps 310 and 330 of the method 300 , and the processing module 12 can be used to execute the step 340 of the method 300 .

When the communication device 10 is used to execute the method 500 in FIG. 5 , the transceiver module 11 can be used to execute the steps 510 and 530 of the method 500 , and the processing module 12 can be used to execute the steps 540 , 550 and 560 of the method 300 . .

When the communication device 100 is used to execute the method 400 in FIG. 4 , the processing module 120 can be used to execute the mode 1, the mode 2 and the mode 3.

Specifically, the transceiver module 11 is configured to send a registration request message, where the registration request message includes a first network identifier, the registration request message indicates a request to access a network to be registered, and the network to be registered is a public network identified by the first network identifier network or non-public network; the transceiver module 11 is configured to receive a registration rejection message; the processing module 12 is configured to perform an operation corresponding to the access type according to at least one of the access type and the cause value of the network to be registered, and the access Access types include public and non-public networks.

Optionally, the processing module 12 may 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, where the first list indicates that the communication device 10 is prohibited from accessing the network. 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 first network identifier is added to the second list, and the second list indicates that the communication device 10 is prohibited Access the non-public network identified by the network identifier in the second list.

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 the first state; or when the access type of the network to be registered is a non-public network, enter the first state Two states; the first state and the second state are not the same state.

The first state indicates that the communication device 10 cannot access the public network identified by the first network identifier, and the second state indicates that the communication device 10 cannot access the non-public network identified by the first network identifier. or

The first state indicates that the communication device 10 cannot access the public network, and the second state indicates that the communication device 10 cannot access the non-public network.

Optionally, the processing module 12 may be specifically configured to: when the access type of the network to be registered is a public network, the NAS layer of the communication device 10 instructs the AS layer that the public network identifier identified by the network identifier in the first list cannot be selected. or when the access type of the network to be registered is a non-public network, the NAS layer of the communication device 10 instructs the AS layer that the non-public network cell identified by the network identifier in the second list cannot be selected.

Specifically, the transceiver module 11 is further configured to receive a cause value, and by receiving a registration rejection message, the registration rejection message includes the cause value. The reason value may be used to indicate that: the communication device 10 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 cannot access the first network identifier network identified by the symbol.

Optionally, the registration request message sent by the transceiver module 11 may further include the access type of the network to be registered.

FIG. 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 device 20 may include a transceiver module 21 and a processing module 22 .

In a possible design, the communication apparatus 20 may correspond to the network device in the above method embodiment. For example, it may be an AMF, or a chip configured in an AMF.

Specifically, the communication apparatus 20 may correspond to the network equipment in the method 300 and the method 500 according to the embodiments of the present application, and the communication apparatus 20 may include a method for performing the method 300 in FIG. 3 or the method 500 in FIG. 5 . A module of a method performed by a network device. In addition, each unit in the communication device 20 and the above-mentioned other operations and/or functions are respectively to implement the corresponding flow of the method 300 in FIG. 3 or the method 500 in FIG. 5 .

Wherein, when the communication device 20 is used to execute the method 300 in FIG. 3 , the transceiver module 21 can be used to execute steps 310 and 330 of the method 300 , and the processing module 22 can be used to execute the step 320 of the method 300 .

When the communication device 20 is used to perform the method 500 in FIG. 5 , the transceiver module 21 can be used to perform steps 510 and 530 of the method 500 , and the processing module 22 can be used to perform the step 520 of the method 300 .

Specifically, the transceiver module 21 is configured to receive a registration request message, where the registration request message includes the first network identifier and the access type of the network to be registered, and the registration request message instructs the terminal device to request the network device to access the network to be registered, The access type includes a public network and a non-public network, and the network to be registered is the public network or the non-public network identified by the first network identifier; the processing module 22 is configured to determine to refuse the terminal device to access the to-be-registered network; The transceiver module 210 is configured to send a registration rejection message to the terminal device.

Optionally, the processing module 22 is further configured to determine a cause value according to the access type of the network to be registered, to instruct the terminal device to refuse to access the network to be registered; the transceiver module 21 is further configured to send the cause to the terminal device. value.

Wherein, the processing module 22 is specifically configured to: when the access type of the network to be registered is a public network, determine a cause value, indicating that access to the public network identified by the first network identifier is refused; or the access type of the network to be registered When it is a non-public network, the cause value is determined to indicate refusal to access the non-public network identified by the first network identifier; or the cause value is determined to indicate refusal to access the network identified by the first network identifier.

According to the aforementioned method, FIG. 9 is a schematic diagram of a communication apparatus 30 provided by an embodiment of the present application. As shown in FIG. 9 , the apparatus 30 may be a device that needs to perform network registration, including various handheld devices and vehicle-mounted devices with wireless communication functions. , wearable devices, computing devices or other processing devices connected to wireless modems, as well as various forms of terminals, mobile stations (Mobile Station, MS), terminals (Terminal), user equipment UE, soft terminals and so on.

The apparatus 30 may include a processor 31 (ie, an example of a processing module) and a memory 32 . The memory 32 is used for storing instructions, and the processor 31 is used for executing the instructions stored in the memory 32, so that the apparatus 30 implements the steps performed by the device for network registration in the method corresponding to FIG. 3, FIG. 4 or FIG. 5 .

Further, the device 30 may further include an input port 33 (ie, an example of a transceiver module) and an output port 34 (ie, 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 an internal connection path to transmit control and/or data signals. The memory 32 is used to store a computer program, and the processor 31 can be used to call and run the computer program from the memory 32 to control the input port 33 to receive signals, control the output port 34 to send signals, and complete the process of the terminal device in the above method. step. The memory 32 may be integrated in the processor 31 or may be provided separately from the processor 31 .

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 may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.

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.

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

As another implementation manner, a general-purpose computer may be used to implement the communication device provided by the embodiments of the present application. The program codes that will implement 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 .

Wherein, each module or unit in the communication apparatus 30 may be used to perform various actions or processing procedures performed by the device (eg, terminal device) performing network registration in the above method.

For the concepts related to the technical solutions provided by the embodiments of the present application involved in the apparatus 10, for explanations and detailed descriptions, and other steps, please refer to the descriptions of the foregoing methods or other embodiments, which will not be repeated here.

According to the foregoing method, FIG. 10 is a schematic diagram of a communication apparatus 40 provided by an embodiment of the present application. As shown in FIG. 10 , the apparatus 40 may be a device that accepts network registration, including a network element with an access management function, such as AMF.

The apparatus 40 may include a processor 41 (ie, an example of a processing module) and a memory 42 . The memory 42 is used for storing instructions, and the processor 41 is used for executing the instructions stored in the memory 42, so that the apparatus 40 implements the steps performed by the device performing network registration in the method corresponding to FIG. 3 or FIG. 5 .

Further, the device 40 may further include an input port 43 (ie, an example of a transceiver module) and an output port 44 (ie, 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 an internal connection path to transmit control and/or data signals. The memory 42 is used to store a computer program, and the processor 41 can be used to call and run the computer program from the memory 42 to control the input port 43 to receive signals, control the output port 44 to send signals, and complete the process of the terminal device in the above method. step. The memory 42 may be integrated in the processor 41 or may be provided separately from the processor 41 .

Optionally, 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 the transmitter may be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers.

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.

As an implementation manner, the functions of the input port 43 and the output port 44 can be considered to be realized by a transceiver circuit or a dedicated chip for transceiver. The processor 41 can be considered to be implemented by a dedicated processing chip, a processing circuit, a processor or a general-purpose chip.

As another implementation manner, a general-purpose computer may be used to implement the communication device provided by the embodiments of the present application. The program codes that will implement the functions of the processor 41 , the input port 43 and the output port 44 are stored in the memory 42 , and the general-purpose processor implements the functions of the processor 41 , the input port 43 and the output port 44 by executing the codes in the memory 42 .

Wherein, each module or unit in the communication apparatus 40 can be used to perform each action or processing process performed by the device on the network side (ie, the network device) during network registration in the above method.

For the concepts related to the technical solutions provided by the embodiments of the present application involved in the apparatus 40, for explanations and detailed descriptions and other steps, please refer to the descriptions of the foregoing methods or other embodiments, which will not be repeated here.

FIG. 11 is a schematic structural diagram of a terminal device 500 provided by this application. For convenience of explanation, FIG. 11 only shows the main components of the terminal device. As shown in FIG. 11 , the terminal device 500 includes a processor, a memory, a control circuit, an antenna, and an input and output device.

The processor is mainly used to process communication protocols and communication data, and to control the entire terminal device, execute software programs, and process data of the software programs, for example, for supporting the terminal device to execute the above-mentioned transmission precoding matrix instruction method embodiment. the described action. The memory is mainly used to store software programs and data, such as the codebook described in the above embodiments. The control circuit is mainly used for the conversion of the baseband signal and the radio frequency signal and the processing of the radio frequency signal. The control circuit together with the antenna can also be called a transceiver, which is mainly used to send and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as touch screens, display screens, and keyboards, are mainly used to receive data input by users and output data to users.

When the terminal device is powered on, the processor can read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor performs baseband processing on the data to be sent, and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal through the antenna in the form of electromagnetic waves. When data is sent 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, which converts the baseband signal into data and processes the data.

Those skilled in the art can understand that, for the convenience of description, FIG. 11 only shows one memory and a processor. In an actual terminal device, there may be multiple processors and memories. The memory may also be referred to as a storage medium or a storage device, etc., which is not limited in this embodiment of the present application.

As an optional implementation manner, the processor may include a baseband processor and a central processing unit. The baseband processor is mainly used to process communication protocols and communication data, and the central processing unit is mainly used to control the entire terminal device, execute A software program that processes data from the software program. The processor in FIG. 11 integrates the functions of the baseband processor and the central processing unit. Those skilled in the art can understand that the baseband processor and the central processing unit may also be independent processors, interconnected by technologies such as a bus. Those skilled in the art can understand that a terminal device may include multiple baseband processors to adapt to different network standards, a terminal device may include multiple central processors to enhance its processing capability, and 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 can 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 in the processor, or may be stored in the storage unit in the form of a software program, and the processor executes the software program to realize the baseband processing function.

As shown in FIG. 11 , the terminal device 500 includes a transceiver unit 510 and a processing unit 520 . The transceiving unit may also be referred to as a transceiver, a transceiver, a transceiving device, or the like. Optionally, the device for implementing the receiving function in the transceiver unit 510 may be regarded as a receiving unit, and the device for implementing the transmitting function in the transceiver unit 510 may be regarded as a transmitting unit, that is, the transceiver unit 510 includes a receiving unit and a transmitting unit. Exemplarily, the receiving unit may also be referred to as a receiver, a receiver, a receiving circuit, and the like, and the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit, or the like.

The terminal device shown in FIG. 11 may perform each action performed by the terminal device in the foregoing method 300 , 400 or 500 . Here, in order to avoid redundant description, the detailed description thereof is omitted.

It should be understood that, in this embodiment of the present application, the processor may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processors, DSP), dedicated integrated Circuit (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-only memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically programmable Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM), which acts as an external cache. By way of example and not limitation, many forms of random access memory (RAM) are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (DRAM) 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 connection dynamic random access memory Access memory (Synchlink DRAM, SLDRAM) and direct memory bus random access memory (Direct rambus RAM, DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented in software, the above-described embodiments may 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, all or part of the processes or functions described in the embodiments of the present application are generated. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server or data center by wire (eg, infrared, wireless, microwave, etc.). 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, a data center, or the like that contains one or more sets of available media. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media. The semiconductor medium may be a solid state drive.

It should be understood that the term "and/or" in this document is only an association relationship to describe associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, and A and B exist at the same time , there are three cases of B alone. In addition, the character "/" in this document generally indicates that the related objects are an "or" relationship.

It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation.

Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application. Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment. In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The functions, if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program codes .

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (29)

1. A method for network registration, comprising:

   Send a registration request message, where the registration request message includes a first network identifier, the registration request message indicates a request to access a network to be registered, and the network to be registered is a public network or a non-public network identified by the first network identifier network;

   receive a registration rejection message;

   According to at least one of an access type and a cause value of the network to be registered, an operation corresponding to the access type is performed, and the access type includes a public network and a non-public network.
2. The method according to claim 1, wherein the performing an operation corresponding to the access type comprises:

   When the access type of the network to be registered is a public network, the first network identifier is added to a first list, where the first list indicates that access to the public network identified by the network identifier in the first list is prohibited. net; 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 network identifier identified by the network identifier in the second list is prohibited. non-public network.
3. The method according to claim 1 or 2, wherein the performing an operation corresponding to the access type comprises:

   When the access type of the network to be registered is the public network, enter the first state; or

   When the access type of the network to be registered is a non-public network, enter the second state;

   The first state and the second state are not the same state.
4. The method according to claim 3, wherein the first state indicates that the public network cannot be accessed, and the second state indicates that the non-public network cannot be accessed.
5. The method according to claim 3, wherein the first state indicates that the public network identified by the first network identifier cannot be accessed, and the second state indicates that the first network identifier cannot be accessed. The identified non-public network.
6. The method according to claim 2 or 3, wherein the performing an operation corresponding to the access type comprises:

   When the access type of the network to be registered is the public network, the non-access stratum NAS instructs the access stratum AS that the cell of the public network identified by the network identifier in the first list cannot be selected; or

   When the access type of the network to be registered is a non-public network, the NAS layer instructs the AS layer that the non-public network cell identified by the network identifier in the second list cannot be selected.
7. The method of claim 1, wherein 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 1 to 7, wherein the registration rejection message includes the cause value.
9. The method according to any one of claims 1 to 8, wherein the registration request message includes an access type of the network to be registered.
10. A method for network registration, comprising:

    Receive a registration request message, where the registration request message includes the first network identifier and the access type of the network to be registered, the registration request message instructs the terminal device to request the network device to access the to-be-registered network, the access type Including a public network and a non-public network, the network to be registered is the public network or the non-public network identified by the first network identifier;

    Determine to deny the terminal device to access the to-be-registered network;

    A registration rejection message is sent to the terminal device.
11. The method of claim 10, wherein the method further comprises:

    Determine a cause value according to the access type of the to-be-registered network, where the cause value is used to indicate refusal to access the to-be-registered network;

    The reason value is sent to the terminal device.
12. The method according to claim 11, wherein the determining the cause value comprises:

    When the access type of the network to be registered is a public network, determine the cause value, where the cause value indicates that access to the public network identified by the first network identifier is refused; or

    When the access type of the network to be registered is a non-public network, the cause value is determined, and the cause value indicates that access to the non-public network identified by the first network identifier is refused; or

    The cause value is determined, the cause value indicating a denial of access to the network identified by the first network identifier.
13. The method of claim 11 or 12, wherein the registration rejection message includes the cause value.
14. A device for network registration, comprising:

    a transceiver module, configured to send a registration request message, where the registration request message includes a first network identifier, the registration request message indicates a request to access a to-be-registered network, and the to-be-registered network is identified by the first network identifier public network or non-public network;

    The transceiver module is further configured to receive a registration rejection message;

    A processing module, configured to perform an operation corresponding to the access type according to at least one of an access type and a cause value of the network to be registered, where the access type includes a public network and a non-public network.
15. The device according to claim 14, wherein the processing module is specifically configured to:

    When the access type of the network to be registered is a public network, the first network identifier is added to a first list, where the first list indicates that access to the public network identified by the network identifier in the first list is prohibited. net; 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 network identifier identified by the network identifier in the second list is prohibited. non-public network.
16. The device according to claim 14 or 15, wherein the processing module is further used for:

    When the access type of the network to be registered is the public network, enter the first state; or

    When the access type of the network to be registered is a non-public network, enter the second state;

    The first state and the second state are not the same state.
17. The apparatus according to claim 16, wherein the first state indicates that the public network cannot be accessed, and the second state indicates that the non-public network cannot be accessed.
18. The apparatus according to claim 16, wherein the first state indicates that the public network identified by the first network identifier cannot be accessed, and the second state indicates that the first network identifier cannot be accessed. The identified non-public network.
19. The device according to claim 15 or 16, wherein the processing module is further configured to:

    When the access type of the network to be registered is the public network, the non-access stratum NAS instructs the access stratum AS that the cell of the public network identified by the network identifier in the first list cannot be selected; or

    When the access type of the network to be registered is a non-public network, the NAS layer instructs the AS layer that the non-public network cell identified by the network identifier in the second list cannot be selected.
20. The apparatus of claim 14, wherein 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.
21. The apparatus according to any one of claims 14 to 20, wherein the registration rejection message includes the reason value.
22. The apparatus according to any one of claims 14 to 21, wherein the registration request message includes an access type of the network to be registered.
23. A device for network registration, comprising:

    a transceiver module, configured to receive a registration request message, where the registration request message includes a first network identifier and an access type of the network to be registered, the registration request message instructs the terminal device to request the network device to access the network to be registered, The access type includes a public network and a non-public network, and the network to be registered is the public network or the non-public network identified by the first network identifier;

    a processing module, configured to determine to refuse the terminal device to access the to-be-registered network;

    The transceiver module is further configured to send a registration rejection message to the terminal device.
24. The apparatus of claim 23, wherein:

    The processing module is further configured to determine a cause value according to the access type of the to-be-registered network, where the cause value is used to instruct the terminal device to refuse to access the to-be-registered network;

    The transceiver module is further configured to send the cause value to the terminal device.
25. The apparatus according to claim 24, wherein the processing module is specifically configured to:

    When the access type of the network to be registered is a public network, determine the cause value, where the cause value indicates that access to the public network identified by the first network identifier is refused; or

    When the access type of the network to be registered is a non-public network, determine the cause value, and the cause value indicates that access to the non-public network identified by the first network identifier is refused; or

    The cause value is determined, the cause value indicating a denial of access to the network identified by the first network identifier.
26. The apparatus of claim 24 or 25, wherein the registration rejection message includes the cause value.
27. A communication device, characterized in that it includes:

    A processor for executing a computer program stored in a memory, so that the communication device performs the communication method according to any one of claims 1 to 9, or performs the communication according to any one of claims 10 to 13 method.
28. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, and when the computer program runs on a computer, the computer is made to execute any one of claims 1 to 9. The communication method described in item 1, or the communication method according to any one of claims 10 to 13 is performed.
29. A chip system, characterized by comprising: a processor for calling and running a computer program from a memory, so that a communication device installed with the chip system executes the communication according to any one of claims 1 to 9 method, or perform a communication method as claimed in any one of claims 10 to 13.

Images