JP7609892B2 - NETWORK ACCESS METHOD, APPARATUS, AND SYSTEM - Google Patents

Description

This application relates to the field of communications technology, and more particularly to network access methods, devices, and systems.

A terminal having the capability or permission to access a non-public network (hereinafter referred to as a private network terminal for short) may access a public network through the non-public network to perform data transmission. However, in different phases of the 3GPP evolution, a private network terminal accesses a non-public network in a different manner. For example, in the R16 phase of 3GPP, a private network terminal may request to register with a non-public network by using subscription information between the private network terminal and the non-public network, and a private network terminal may request to register with a public network by using subscription information between the private network terminal and the public network. However, in the R17 phase of 3GPP, a private network terminal may request to register with a non-public network by using subscription information between the private network terminal and the public network.

However, so far, current technology does not document the solution to be used when a terminal that does not have the capability or authorization to access a non-public network (hereinafter referred to as a non-private network terminal for short) attempts to access a non-public network defined in the R16 phase of 3GPP or the R17 phase of 3GPP.

Embodiments of the present application provide a network access method, apparatus, and system to solve a problem caused when a first terminal attempts to access a non-public network.

To achieve the above objectives, the embodiments of the present application provide the following technical solutions:

According to a first aspect, an embodiment of the present application provides a network access method. The method includes: A first terminal transmits, to an access management network element in a first non-public network, a first message used to request the first terminal to register on the first non-public network. The first terminal receives, from the access management network element, a second message used to indicate that registration of the first terminal on the first non-public network is rejected. The second message includes first indication information, and the first indication information indicates that access of the first terminal to the first non-public network is prohibited. The first terminal updates a prohibited network list of the first terminal based on the first indication information. The updated prohibited network list includes information about the first non-public network.

It should be appreciated that the first terminal may obtain an updated prohibited network list by updating the prohibited network list of the first terminal.

This embodiment of the present application provides a network access method. In this method, the first terminal sends a first message to an access management network element in the first non-public network to request the first terminal to register on the first non-public network. Then, the first terminal receives a second message from the access management network element, the second message indicating that the registration of the first terminal on the first non-public network is rejected, and the first indication information indicates that the access of the first terminal to the first non-public network is prohibited. This helps the first terminal to update the prohibited network list of the first terminal based on the first indication information, so that the updated prohibited network list includes information about the first non-public network. Then, when selecting a network for registration, the first terminal can avoid selecting the first non-public network that the first terminal is prohibited from accessing. This solution can solve the problem caused when the first terminal that does not have permission to access the non-public network attempts to access the first non-public network.

In a possible implementation, the first non-public network in this embodiment of the present application supports interworking with the first public network.

In a possible implementation, the first non-public network in this embodiment of the present application interworks with the first public network by using a roaming architecture.

In a possible implementation, the method provided in this embodiment of the present application further includes: The first terminal selects a network other than the first non-public network for registration based on the updated prohibited network list. This prevents the first terminal that does not have permission to access the non-public network from accessing the first non-public network, and prevents the first terminal from automatically/manually selecting the first non-public network that the first terminal is prohibited from accessing.

In a possible implementation, the method provided in this embodiment of the present application further includes: The first terminal starts a timer based on the first indication information. When the timer expires, the first terminal deletes information about the first non-public network from the updated prohibited network list. This helps the first terminal to subsequently continue to attempt to access the first non-public network.

In a possible implementation, the second message includes a timer time value, and the method provided in this embodiment of the present application further includes : the first terminal sets a timer based on the timer time value, which helps the first terminal obtain the timer time value from the first non-public network.

In a possible implementation, the first terminal is a terminal that does not have the capability or permission to access a non-public network.

According to a second aspect, an embodiment of the present application provides a network access method. The method includes: an access management network element in a first non-public network receives, from a first terminal, a first message used to request the first terminal to register on the first non-public network; the access management network element obtains a third message from an integrated data management network element in the first public network; the access management network element transmits, based on the third message, to the first terminal, a second message used to indicate that the registration of the first terminal to the first non-public network is rejected, the second message including first indication information indicating that the access of the first terminal to the first non-public network is prohibited.

In this solution, an access management network element in a first non-public network receives from a first terminal a first message used to request the first terminal to register in the first non-public network, and then, based on the third message, the access management network element sends to the first terminal a second message used to indicate that the registration of the first terminal in the first non-public network is denied, thus preventing the first terminal having permission to access the non-public network from accessing the first non-public network.

In a possible implementation, the third message includes subscription data of the first terminal, the subscription data including the second indication information. In an aspect, the second indication information is used to indicate that the first terminal can only access a public network. Alternatively, in another aspect, the second indication information is used to indicate that the first terminal cannot access a non-public network.

In a possible implementation, the second indication information includes a supported network list of the first terminal, the network list not including information about the first non-public network. Alternatively, the supported network list of the first terminal does not include information about any non-public network.

In a possible implementation, the third message includes third indication information, which is used to indicate that the subscription data of the first terminal is not successfully acquired.

In a possible implementation, the third message further includes a cause value for the unsuccessful acquisition of the subscription data of the first terminal, the cause value indicating that the first terminal is not allowed to access the first non-public network.

In a possible implementation, the third message does not include subscription data of the first terminal.

In a possible implementation, the method provided in this embodiment of the present application further includes: The access management network element determines to deny registration of the first terminal to the first non-public network based on the third message.

In a possible implementation, the access management network element determining to deny registration of the first terminal to the first non-public network based on the third message includes: The access management network element determining to deny registration of the first terminal to the first non-public network based on the second indication information.

In a possible implementation, the access management network element determining to deny registration of the first terminal to the first non-public network based on the third message includes: The access management network element determining to deny registration of the first terminal to the first non-public network based on the third indication information.

In a possible implementation, the access management network element determining to deny registration of the first terminal to the first non-public network based on the third message includes: the access management network element determining that the third message does not include subscription data of the first terminal and thus deciding to deny registration of the first terminal to the first non-public network.

According to a third aspect, an embodiment of the present application provides a network access method. The method includes: an integrated data management network element in a first public network receives an inquiry message from an access management network element in a first non-public network, the inquiry message being used to inquire about subscription data of a first terminal; the integrated data management network element transmits a third message to the access management network element, the third message including one or more of the subscription data and the cause value of the first terminal, the subscription data including a second indication information, the second indication information being used to indicate that the first terminal can only access the public network, i.e., the second indication information being used to indicate that the first terminal cannot access the first non-public network, and the cause value being used to indicate that the first terminal is not allowed to access the first non-public network.

In a possible implementation, the second indication information includes a supported network list of the first terminal, and the network list does not include information about the first non-public network.

In a possible implementation, the third message includes third indication information, which is used to indicate that the subscription data of the first terminal is not successfully acquired.

In a possible implementation, the third message further includes a cause value for the unsuccessful acquisition of the subscription data of the first terminal, the cause value indicating that the first terminal is not allowed to access the first non-public network.

In a possible implementation, the third message does not include subscription data of the first terminal.

According to a fourth aspect, an embodiment of the present application provides a network access method. The method includes: a second terminal receives broadcast information from an access network device in a first non-public network, the broadcast information including first indication information used to indicate that the first non-public network and the public network are interworked; the second terminal determines to access the first non-public network by using first subscription information based on the broadcast information; the first subscription information is subscription information of the second terminal in the first public network.

In a possible implementation, the first identifier of the second terminal carried in the first subscription information is associated with a first public network. For example, the first identifier of the second terminal carries information about the first public network. For example, the first public network may be a first PLMN and the information about the first public network may be a first PLMN ID.

This embodiment of the present application provides a network access method. In this method, a second terminal receives broadcast information from an access network device in a first non-public network, so that the second terminal can determine that the first non-public network and the public network are interworked. This helps a terminal having the ability or permission to access the non-public network to subsequently access the first non-public network by using subscription information between the terminal and the public network. Furthermore, since a terminal having the ability or permission to access the non-public network cannot receive the broadcast information, waste of network resources caused when a terminal having no ability or permission to access the non-public network attempts to access the first non-public network can be avoided.

In a possible implementation, the method provided in this embodiment of the present application may further include: The second terminal accesses the first non-public network by using the first subscription information.

In a possible implementation, the second terminal accessing the first non-public network by using the first subscription information includes: the second terminal sending a registration request message to an access management network element in the first non-public network, the registration request message carrying a first identifier of the second terminal.

In a possible implementation, the second terminal is a terminal that has the capability or permission to access a non-public network.

In a possible implementation, the broadcast information is further used to indicate that the first non-public network and the public network are interworked by using a roaming architecture.

In a possible implementation, the broadcast information is transmitted for terminals that have the capability or permission to access the non-public network.

In a possible implementation, the broadcast information further includes information about one or more public networks that interwork with the first non-public network, and the information about the public networks may be identifiers of the public networks. For example, the public network may be a PLMN and the identifier of the public network may be a PLMN ID. The first public network belongs to one or more public networks. This helps the second terminal determine the one or more public networks that interwork with the first non-public network.

In a possible implementation, the network selection priority of the first public network is the highest among the network selection priorities of the one or more public networks.

According to a fifth aspect, an embodiment of the present application provides a network access method. The method includes: an access network device in a first non-public network transmits broadcast information, the broadcast information including first indication information, and the first indication information is used to indicate that the first non-public network and the public network are interworked.

In a possible implementation, the broadcast information further includes information about one or more public networks that interwork with the first non-public network.

According to a sixth aspect, an embodiment of the present application provides a network access method. The method includes: A second terminal sends a first message to an access management network element in a first non-public network by using first subscription information, the first message is used to indicate a request to register the second terminal in the first non-public network, the first subscription information is subscription information of the second terminal in the first non-public network, or the first subscription information is subscription information of the second terminal in the first public network. The second terminal receives a second message from the access management network element, the second message is used to indicate that the registration of the second terminal to the first non-public network is rejected. The second message includes fourth indication information, and the fourth indication information is used to indicate a cause for rejecting the registration of the second terminal to the first non-public network.

In a possible implementation, when the first public network interworks with the first non-public network by using a roaming architecture, the first subscription information is subscription information of the second terminal in the first non-public network. In this case, the second identifier of the second terminal carried in the first subscription information is related to the first non-public network. For example, the second identifier of the second terminal includes an identifier of the first non-public network. The identifier of the first non-public network is determined based on the identifier of the target public network and a network identifier (Network Identifier, NID). The target public network identifier may be a reserved value provided by a third party operator for the target public network.

In a possible implementation, when the first public network interworks with the first non-public network through the N3IWF, the first subscription information is subscription information of the second terminal in the first public network. In this case, the third identifier of the second terminal carried in the first subscription information is related to the first public network. For example, the third identifier of the second terminal includes information about the first public network. For example, the information about the first non-public network is an identifier of the first non-public network. For example, the identifier of the first non-public network is a first PLMN ID.

In a possible implementation, the first subscription information is subscription information of a second terminal in the first non-public network, and the method provided in this embodiment of the present application further includes: The second terminal registers with the first non-public network based on the fourth indication information by using the second subscription information of the second terminal, the second subscription information being subscription information of the second terminal in the first public network.

In a possible implementation, the method provided in this embodiment of the present application further includes: The second terminal receives a fourth message from the access management network element, the fourth message including a network candidate list of the second terminal, the network candidate list including information about the first non-public network. This helps the second terminal determine that the second terminal can register with the first non-public network.

In a possible implementation, the method provided in this embodiment of the present application further includes: The second terminal receives a fifth message from the access management network element, the fifth message being used to indicate that the registration of the second terminal to the first non-public network is accepted. The second terminal adds information about the first non-public network to the network candidate list of the second terminal. This helps the second terminal determine that the second terminal can register to the first non-public network, and then selects the second subscription information of the second terminal to register to the first non-public network.

In a possible implementation, the fourth indication information is used to indicate that the second terminal is an unauthorized terminal.

In a possible implementation, when the first subscription information is subscription information of a second terminal in a first public network, and the second terminal further has third subscription information of a second terminal in a first non-public network, the method provided in this embodiment of the present application further includes: The second terminal requests to register with the first non-public network by using the third subscription information. The third subscription information includes a fourth identifier of the second terminal, which is related to the first non-public network. For example, the fourth identifier includes information about the first non-public network. For example, the information about the first non-public network is an identifier of the first non-public network. In this case, the identifier of the first non-public network is determined based on the identifier of the target public network and the NID.

In a possible implementation, the second terminal requesting to register with the first non-public network by using the third subscription information includes: the second terminal sending a registration request message to an access management network element in the first non-public network, the registration request message including a fourth identifier of the second terminal.

According to a seventh aspect, an embodiment of the present application provides a network access method. The method includes: an access management network element in a first non-public network receives a first message from a second terminal, the first message being used to indicate that the second terminal requests to register in the first non-public network by using first subscription information, the first subscription information being subscription information of the second terminal in the first non-public network, or the first subscription information being subscription information of the second terminal in the first public network. The access management network element transmits a second message to the second terminal, the second message being used to reject the registration of the second terminal to the first non-public network, the second message including fourth indication information, the fourth indication information being used to indicate a cause for rejecting the registration of the second terminal to the first non-public network.

In a possible implementation, the method provided in this embodiment of the present application further includes: The access management network element sends a fourth message to the second terminal, the fourth message including a network candidate list of the second terminal. The network candidate list includes information about the first non-public network. For example, the information about the first non-public network is an identifier of the first non-public network. In this case, the identifier of the first non-public network is determined based on the identifier of the target public network and the NID.

In a possible implementation, the method provided in this embodiment of the present application further includes: The access management network element sends a fifth message to the second terminal, the fifth message being used to indicate that the registration of the second terminal to the first non-public network is accepted. This helps the second terminal determine, based on the fifth message, that the second terminal can register to the first non-public network.

In a possible implementation, the fourth indication information is used to indicate that the second terminal is an unauthorized terminal.

In a possible implementation, the method provided in this embodiment of the present application further includes: The access management network element determines to deny registration of the second terminal to the first non-public network.

In a possible implementation, the access management network element's refusal of registration of the second terminal to the first non-public network includes: The access management network element determines to deny registration of the second terminal to the first non-public network based on configuration information or subscription information of the second terminal in the first non-public network.

According to an eighth aspect, an embodiment of the present application provides a communication device. The communication device may implement the method according to the first aspect or any one of the possible implementations of the first aspect, and thus may further implement the beneficial effects according to the first aspect or any one of the possible implementations of the first aspect. The communication device may be a first terminal or a device supporting the first terminal in implementing the method according to the first aspect or any one of the possible implementations of the first aspect, for example a chip used within the first terminal. The communication device may implement the aforementioned method by using software or hardware, or by executing corresponding software by hardware.

In an example, an embodiment of the present application provides a communication device. The communication device includes a communication unit and a processing unit. The processing unit is configured to process information, and the communication unit is configured to receive or transmit information. For example, the communication unit is configured to send, to an access management network element in a first non-public network, a first message used to request the first terminal to register on the first non-public network. The communication unit is further configured to receive, from the access management network element, a second message used to indicate that registration of the first terminal on the first non-public network is denied. The second message includes first indication information, the first indication information indicating that access of the first terminal to the first non-public network is prohibited. The processing unit is configured to update a prohibited network list of the first terminal based on the first indication information, and the updated prohibited network list includes information about the first non-public network.

In a possible implementation, the first non-public network in this embodiment of the present application supports interworking with the first public network.

In a possible implementation, the first non-public network in this embodiment of the present application interworks with the first public network by using a roaming architecture.

In a possible implementation, the processing unit is further configured to select a network other than the first non-public network for registration based on the updated prohibited network list.

In a possible implementation, the processing unit is further configured to start a timer based on the first indication information and, when the timer expires, remove information about the first non-public network from the updated prohibited network list.

In a possible implementation, the second message includes a timer time value, and the first terminal sets the timer based on this timer time value.

In a possible implementation, the first terminal is a terminal that does not have the capability or permission to access a non-public network.

For example, when the communication device is a chip or chip system in the first terminal, the processing unit may be a processor and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin, or a circuit. The processing unit executes instructions stored in the storage unit to enable the first terminal to implement the network access method according to the first aspect or any one of the possible implementations of the first aspect. The storage unit may be a storage unit in the chip (e.g., a register or a cache) or a storage unit in the first terminal and external to the chip (e.g., a read-only memory or a random access memory).

According to a ninth aspect, an embodiment of the present application provides a communication device. The communication device may implement the method according to the second aspect or any one of the possible implementations of the second aspect, and thus may further implement the beneficial effects according to the second aspect or any one of the possible implementations of the second aspect. The communication device may be an access management network element or a device supporting the access management network element in implementing the method according to the second aspect or any one of the possible implementations of the second aspect, for example a chip used within the access management network element. The communication device may implement the aforementioned method by using software or hardware, or by executing corresponding software by hardware.

In an example, an embodiment of the present application provides a communication device. The communication device is an access management network element in a first non-public network, or a chip used in the access management network element. The device includes a communication unit and a processing unit. The processing unit is configured to process information, and the communication unit is configured to receive or transmit information. For example, the communication unit is configured to receive a first message from a first terminal, the first message being used to request the first terminal to register in the first non-public network. The communication unit is configured to obtain a third message from an integrated data management network element in the public network. The communication unit is configured to transmit a second message to the first terminal based on the third message, the second message being used to indicate that the registration of the first terminal in the first non-public network is rejected, the second message including first indication information, and the first indication information indicating that the access of the first terminal to the first non-public network is prohibited.

In a possible implementation, the third message includes subscription data of the first terminal, the subscription data including the second indication information. In an aspect, the second indication information is used to indicate that the first terminal can only access a public network. Alternatively, in another aspect, the second indication information is used to indicate that the first terminal cannot access a non-public network.

In a possible implementation, the second indication information includes a supported network list of the first terminal, and the network list does not include information about the first non-public network.

In a possible implementation, the third message includes third indication information, which is used to indicate that the subscription data of the first terminal is not successfully acquired.

In a possible implementation, the third message does not include subscription data of the first terminal.

In a possible implementation, the third message further includes a cause value for the unsuccessful acquisition of the subscription data of the first terminal, the cause value indicating that the first terminal is not allowed to access the first non-public network.

In a possible implementation, the processing unit is configured to decide to deny registration of the first terminal to the first non-public network based on the third message.

In a possible implementation, the processing unit being configured to determine, based on the third message, to deny registration of the first terminal to the first non-public network includes: The processing unit being configured to determine, based on the second indication information, to deny registration of the first terminal to the first non-public network.

In a possible implementation, the processing unit being configured to determine, based on the third message, to deny registration of the first terminal to the first non-public network includes: The processing unit being configured to determine, based on the third indication information, to deny registration of the first terminal to the first non-public network.

For example, when the communication device is a chip or chip system in the access management network element, the processing unit may be a processor and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin, or a circuit. The processing unit executes instructions stored in the storage unit to enable the access management network element to implement the network access method according to the second aspect or any one of the possible implementations of the second aspect. The storage unit may be a storage unit in the chip (e.g., a register or a cache) or a storage unit in the access management network element and external to the chip (e.g., a read-only memory or a random access memory).

According to a tenth aspect, an embodiment of the present application provides a communication device. The communication device may implement the method according to the third aspect or any one of the possible implementations of the third aspect, and thus may further implement the beneficial effects according to the third aspect or any one of the possible implementations of the third aspect. The communication device may be an integrated data management network element, or a device supporting the integrated data management network element in implementing the method according to the third aspect or any one of the possible implementations of the third aspect, such as a chip used within the integrated data management network element. The communication device may implement the aforementioned method by using software or hardware, or by executing corresponding software by hardware.

In an example, an embodiment of the present application provides a communication device. The communication device includes a communication unit and a processing unit. The processing unit is configured to process information, and the communication unit is configured to receive or transmit information. For example, the communication unit is configured to receive an inquiry message used to inquire subscription data of the first terminal from an access management network element in a first non-public network. The communication unit is further configured to send a third message to the access management network element, the third message including one or more of the subscription data and the cause value of the first terminal, the subscription data including a second indication information, the second indication information being used to indicate that the first terminal can only access the public network, i.e., the second indication information being used to indicate that the first terminal cannot access the non-public network, and the cause value being an indication that the first terminal is not allowed to access the first non-public network.

In a possible implementation, the second indication information includes a supported network list of the first terminal, and the network list does not include information about the first non-public network.

In a possible implementation, the third message includes third indication information, which is used to indicate that the subscription data of the first terminal is not successfully acquired.

In a possible implementation, the third message further includes a cause value for the unsuccessful acquisition of the subscription data of the first terminal, the cause value indicating that the first terminal is not allowed to access the first non-public network.

In a possible implementation, the third message does not include subscription data of the first terminal.

In a possible implementation, the communications device is an integrated data management network element for use within the public network, or a chip within an integrated data management network element for use within the public network.

For example, when the communication device is a chip or chip system in the integrated data management network element, the processing unit may be a processor and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin, or a circuit. The processing unit executes instructions stored in the storage unit to enable the integrated data management network element to implement the network access method according to the third aspect or any one of the possible implementations of the third aspect. The storage unit may be a storage unit within the chip (e.g., a register or cache) or a storage unit within the integrated data management network element and external to the chip (e.g., a read-only memory or a random access memory).

According to an eleventh aspect, an embodiment of the present application provides a communication device. The communication device may implement the method according to the fourth aspect or any one of the possible implementations of the fourth aspect, and thus may further implement the beneficial effects according to the fourth aspect or any one of the possible implementations of the fourth aspect. The communication device may be a second terminal or a device supporting the second terminal in implementing the method according to the fourth aspect or any one of the possible implementations of the fourth aspect, for example a chip used within the second terminal. The communication device may implement the aforementioned method by using software or hardware, or by executing corresponding software by hardware.

In an example, an embodiment of the present application provides a communication device. The communication device includes a communication unit and a processing unit. The processing unit is configured to process information, and the communication unit is configured to receive or transmit information. For example, the communication unit is configured to receive broadcast information from an access network device in a first non-public network, and the broadcast information includes first indication information used to indicate that the first non-public network and the public network are interworked. The processing unit is configured to determine, based on the broadcast information, to access the first non-public network by using first subscription information. The first subscription information is subscription information of a second terminal in the first public network.

In a possible implementation, the second terminal is a terminal that has the capability or permission to access a non-public network.

In a possible implementation, the broadcast information is further used to indicate that the first non-public network and the public network are interworked by using a roaming architecture.

In a possible implementation, the broadcast information further includes information about one or more public networks that interwork with the first non-public network, the first public network belonging to the one or more public networks. This helps the second terminal determine the one or more public networks that interwork with the first non-public network.

In a possible implementation, the network selection priority of the first public network is the highest among the network selection priorities of the one or more public networks.

In a possible implementation, the first identifier of the second terminal carried in the first subscription information is associated with the first public network. For example, the first identifier of the second terminal carries information about the first public network. For example, the first public network is a first PLMN and the information about the first public network is an identifier of the first public network. In this case, the identifier of the first public network may be a first PLMN ID.

In a possible implementation, the processing unit is further configured to access the first non-public network by using the first subscription information.

In a possible implementation, the processing unit being further configured to access the first non-public network by using the first subscription information includes: The processing unit is further configured to send a registration request message to an access management network element in the first non-public network through the communication unit, the registration request message carrying a first identifier of the second terminal.

For example, when the communication device is a chip or chip system in the second terminal, the processing unit may be a processor and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin, or a circuit. The processing unit executes instructions stored in the storage unit to enable the second terminal to implement the network access method according to the fourth aspect or any one of the possible implementations of the fourth aspect. The storage unit may be a storage unit in the chip (e.g., a register or a cache) or a storage unit in the second terminal and external to the chip (e.g., a read-only memory or a random access memory).

According to a twelfth aspect, an embodiment of the present application provides a communication device. The communication device may implement the method according to the fifth aspect or any one of the possible implementations of the fifth aspect, and thus may further implement the beneficial effects according to the fifth aspect or any one of the possible implementations of the fifth aspect. The communication device may be an access network device or a device supporting the access network device in implementing the method according to the fifth aspect or any one of the possible implementations of the fifth aspect, for example a chip used within the access network device. The communication device may implement the aforementioned method by using software or hardware, or by executing corresponding software by hardware.

In an example, an embodiment of the present application provides a communication device. The communication device includes a communication unit and a processing unit. The processing unit is configured to process information, and the communication unit is configured to receive or transmit information. For example, the communication unit is configured to transmit broadcast information, the broadcast information including first indication information, and the first indication information is used to indicate that a first non-public network and a public network are interworked.

In a possible implementation, the broadcast information further includes information about one or more public networks that interwork with the first non-public network.

In a possible implementation, the communication device is applicable to non-public networks.

For example, when the communication apparatus is a chip or chip system in an access network device, the processing unit may be a processor and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin, or a circuit. The processing unit executes instructions stored in the storage unit to enable the access network device to implement the network access method according to the fifth aspect or any one of the possible implementations of the fifth aspect. The storage unit may be a storage unit in the chip (e.g., a register or a cache) or a storage unit in the access network device and external to the chip (e.g., a read-only memory or a random access memory).

According to a thirteenth aspect, an embodiment of the present application provides a communication device. The communication device may implement the method according to the sixth aspect or any one of the possible implementations of the sixth aspect, and thus may further implement the beneficial effects according to the sixth aspect or any one of the possible implementations of the sixth aspect. The communication device may be a second terminal or a device supporting the second terminal in implementing the method according to the sixth aspect or any one of the possible implementations of the sixth aspect, for example a chip used within the second terminal. The communication device may implement the aforementioned method by using software or hardware, or by executing corresponding software by hardware.

In an example, an embodiment of the present application provides a communication device. The communication device is a second terminal or a chip used in the second terminal. The communication device includes a communication unit and a processing unit. The processing unit is configured to process information, and the communication unit is configured to receive or transmit information. For example, the communication unit is configured to send a first message to an access management network element in a first non-public network by using first subscription information, the first message is used to indicate a request to register the second terminal in the first non-public network, the first subscription information is subscription information of the second terminal in the first non-public network, or the first subscription information is subscription information of the second terminal in the first public network. The communication unit is configured to receive a second message from the access management network element, the second message is used to indicate that registration of the second terminal in the first non-public network is rejected. The second message includes a fourth indication information, which is used to indicate a cause for rejecting registration of the second terminal to the first non-public network.

In a possible implementation, when the first public network interworks with the first non-public network by using a roaming architecture, the first subscription information is subscription information of the second terminal in the first non-public network. In this case, the second identifier of the second terminal carried in the first subscription information is related to the first non-public network. For example, the second identifier of the second terminal includes information about the first non-public network. For example, the information about the first non-public network is an identifier of the first non-public network. In this case, the identifier of the first non-public network is determined based on the identifier of the target public network and the NID.

In a possible implementation, when the first public network interworks with the first non-public network through the N3IWF, the first subscription information is subscription information of the second terminal in the first public network. In this case, the third identifier of the second terminal carried in the first subscription information is related to the first public network. For example, the third identifier of the second terminal includes information about the first public network. For example, the information about the first public network is an identifier of the first public network.

In a possible implementation, the first subscription information is subscription information of a second terminal in the first non-public network, and the processing unit is further configured to perform registration to the first non-public network based on the fourth indication information by using the second subscription information of the second terminal, the second subscription information being subscription information of the second terminal in the first public network.

In a possible implementation, the communication unit is further configured to receive a fourth message from the access management network element, the fourth message including a network candidate list of the second terminal, the network candidate list including information about the first non-public network. This helps the second terminal to determine that the second terminal can register with the first non-public network.

In a possible implementation, the communication unit is further configured to receive a fifth message from the access management network element, the fifth message being used to indicate that the registration of the second terminal to the first non-public network is accepted. The second terminal adds information about the first non-public network to the network candidate list of the second terminal. This helps the second terminal to determine that the second terminal can register to the first non-public network and subsequently select second subscription information of the second terminal for registering to the first non-public network.

In a possible implementation, the fourth indication information is used to indicate that the second terminal is an unauthorized terminal.

In a possible implementation, when the first subscription information is subscription information of a second terminal in a first public network, and the second terminal further has third subscription information of a second terminal in a first non-public network, the processing unit is further configured to request registration to the first non-public network by using the third subscription information. The third subscription information includes a fourth identifier of the second terminal, which is related to the first non-public network. For example, the fourth identifier includes information about the first non-public network. For example, the information about the first non-public network is an identifier of the first non-public network. In this case, the identifier of the first non-public network is determined based on the identifier of the target public network and the NID.

In a possible implementation, when the first subscription information is subscription information of a second terminal in a first public network, and the second terminal further has third subscription information of a second terminal in a first non-public network, the processing unit is further used by the second terminal to request to register in the first non-public network by using the third subscription information. The third subscription information includes a fourth identifier of the second terminal, which is related to the first non-public network. For example, the fourth identifier includes information about the first non-public network. For example, the information about the first non-public network is an identifier of the first non-public network. In this case, the identifier of the first non-public network is determined based on the identifier of the target public network and the NID.

In a possible implementation, the processing unit is configured to send a registration request message to an access management network element in the first non-public network through the communication unit, the registration request message including a fourth identifier of the second terminal.

For example, when the communication device is a chip or chip system in the second terminal, the processing unit may be a processor and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin, or a circuit. The processing unit executes instructions stored in the storage unit to enable the second terminal to implement the network access method according to the sixth aspect or any one of the possible implementations of the sixth aspect. The storage unit may be a storage unit in the chip (e.g., a register or cache) or a storage unit in the second terminal and external to the chip (e.g., a read-only memory or a random access memory).

According to a fourteenth aspect, an embodiment of the present application provides a communication device. The communication device may implement the method according to the seventh aspect or any one of the possible implementations of the seventh aspect, and thus may further implement the beneficial effects according to the seventh aspect or any one of the possible implementations of the seventh aspect. The communication device may be an access management network element or a device supporting the access management network element in implementing the method according to the seventh aspect or any one of the possible implementations of the seventh aspect, for example a chip used within the access management network element. The communication device may implement the aforementioned method by using software or hardware, or by executing corresponding software by hardware.

In an example, an embodiment of the present application provides a communication device. The communication device is an access management network element or a chip used in the access management network element. The communication device includes a communication unit and a processing unit. The processing unit is configured to process information, and the communication unit is configured to receive or transmit information. For example, the communication unit is configured to receive a first message from a second terminal, the first message being used to indicate that the second terminal requests to register in a first non-public network by using first subscription information, the first subscription information being subscription information of the second terminal in the first non-public network, or the first subscription information being subscription information of the second terminal in the first public network. The communication unit is configured to send a second message to the second terminal, the second message being used to reject the registration of the second terminal to the first non-public network, the second message including a fourth indication information, and the fourth indication information being used to indicate a cause for rejecting the registration of the second terminal to the first non-public network.

In a possible implementation, the communication unit is further configured to send a fourth message to the second terminal, the fourth message including a network candidate list of the second terminal, the network candidate list including information about the first non-public network.

In a possible implementation, the communication unit is further configured to send a fifth message to the second terminal, the fifth message being used to indicate that the registration of the second terminal to the first non-public network is accepted. This helps the second terminal to determine, based on the fifth message, that the second terminal can register to the first non-public network.

In a possible implementation, the fourth indication information is used to indicate that the second terminal is an unauthorized terminal.

In a possible implementation, the processing unit is configured to decide to deny registration of the second terminal to the first non-public network.

In a possible implementation, the processing unit being configured to determine to deny registration of the second terminal to the first non-public network includes: The processing unit being configured to determine to deny registration of the second terminal to the first non-public network based on configuration information or subscription information of the second terminal in the first non-public network.

In a possible implementation, the communication device is an access management network element used in the first non-public network, or a chip within an access management network element used in the first non-public network.

For example, when the communication device is a chip or chip system in the access management network element, the processing unit may be a processor and the communication unit may be a communication interface. For example, the communication interface may be an input/output interface, a pin, or a circuit. The processing unit executes instructions stored in the storage unit to enable the access management network element to implement the network access method according to the seventh aspect or any one of the possible implementations of the seventh aspect. The storage unit may be a storage unit in the chip (e.g., a register or a cache) or a storage unit in the access management network element and external to the chip (e.g., a read-only memory or a random access memory).

According to a fifteenth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are run on a computer, the computer is enabled to perform a network access method according to the first aspect or any one of the possible implementations of the first aspect.

According to a sixteenth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are run on a computer, the computer is enabled to perform a network access method according to the second aspect or any one of the possible implementations of the second aspect.

According to a seventeenth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are run on a computer, the computer is enabled to perform a network access method according to the third aspect or any one of the possible implementations of the third aspect.

According to an eighteenth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are run on a computer, the computer is enabled to perform a network access method according to the fourth aspect or any one of the possible implementations of the fourth aspect.

According to a nineteenth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are run on a computer, the computer is enabled to perform a network access method according to the fifth aspect or any one of the possible implementations of the fifth aspect.

According to a twentieth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are run on a computer, the computer is enabled to perform a network access method according to the sixth aspect or any one of the possible implementations of the sixth aspect.

According to a twenty-first aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores a computer program or instructions. When the computer program or instructions are run on a computer, the computer is enabled to perform a network access method according to the seventh aspect or any one of the possible implementations of the seventh aspect.

According to a twenty-second aspect, an embodiment of the present application provides a computer program product including instructions that, when run on a computer, enable the computer to perform a network access method according to the first aspect or a possible implementation of the first aspect.

According to a twenty-third aspect, an embodiment of the present application provides a computer program product including instructions that, when run on a computer, enable the computer to perform a network access method according to the second aspect or a possible implementation of the second aspect.

According to a twenty-fourth aspect, an embodiment of the present application provides a computer program product including instructions that, when run on a computer, enable the computer to perform a network access method according to the third aspect or a possible implementation of the third aspect.

According to a twenty-fifth aspect, an embodiment of the present application provides a computer program product including instructions that, when run on a computer, enable the computer to perform a network access method according to the fourth aspect or a possible implementation of the fourth aspect.

According to a twenty-sixth aspect, an embodiment of the present application provides a computer program product including instructions that, when run on a computer, enable the computer to perform a network access method according to the fifth aspect or a possible implementation of the fifth aspect.

According to a twenty-seventh aspect, an embodiment of the present application provides a computer program product including instructions that, when run on a computer, enable the computer to perform a network access method according to the sixth aspect or a possible implementation of the sixth aspect.

According to a twenty-eighth aspect, an embodiment of the present application provides a computer program product including instructions that, when run on a computer, enable the computer to perform a network access method according to the seventh aspect or a possible implementation of the seventh aspect.

According to a twenty-ninth aspect, an embodiment of the present application provides a communication device configured to perform a method according to any one of the possible designs of the first to seventh aspects. The communication device may be the first terminal as described above, or may be a device including the first terminal, or may be a component (e.g., a chip) used in the first terminal. Alternatively, the communication device may be the access management network element as described above, or may be a device including the access management network element, or may be a component (e.g., a chip) used in the access management network element. The communication device may be the integrated data management network element as described above, or may be a device including the integrated data management network element, or may be a component (e.g., a chip) used in the integrated data management network element. Alternatively, the communication device may be the access network device as described above, or may be a device including the access network device, or may be a component (e.g., a chip) used in the access network device. Alternatively, the communication device may be the second terminal as described above, or may be a device including the second terminal, or may be a component (e.g., a chip) used in the second terminal. The communication device includes a corresponding module or unit for performing the method as described above. The modules or units may be implemented using hardware or software, or by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the above-mentioned functions.

According to a thirtieth aspect, an embodiment of the present application provides a communication device. The communication device includes at least one processor and a communication interface. When the communication device operates, the processor executes computer-executable instructions or programs stored in the communication device such that the communication device is enabled to perform a method according to any possible design of any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, or the seventh aspect. For example, the communication device may be a first terminal or a component used in the first terminal. For example, the communication device may be an access management network element or a component used in the access management network element. For example, the communication device may be a second terminal or a component used in the second terminal. For example, the communication device may be an integrated data management network element or a component used in the integrated data management network element. For example, the communication device is an access network device or a component used in the access network device.

It should be appreciated that the communication device described in the thirtieth aspect may further include a bus and a memory. The memory is configured to store code and data. Optionally, the at least one processor, the communication interface, and the memory are coupled to each other.

According to a thirty-first aspect, an embodiment of the present application provides a communication device. The communication device includes at least one processor. The at least one processor is coupled to a memory. When the communication device operates, the processor executes computer-executable instructions or programs stored in the memory such that the communication device is enabled to perform a method according to the first aspect or any one of the possible designs of the first aspect. For example, the communication device may be a first terminal or a chip used within the first terminal.

According to a thirty-second aspect, an embodiment of the present application provides a communication device. The communication device includes at least one processor. The at least one processor is coupled to a memory. When the communication device operates, the processor executes computer-executable instructions or programs stored in the memory such that the communication device is enabled to perform a method according to the second aspect or any one of the possible designs of the second aspect. For example, the communication device may be an access management network element or a chip used within the access management network element.

According to a thirty-third aspect, an embodiment of the present application provides a communication device. The communication device includes at least one processor. The at least one processor is coupled to a memory. When the communication device operates, the processor executes computer-executable instructions or programs stored in the memory such that the communication device is enabled to perform a method according to the third aspect or any one of the possible designs of the third aspect. For example, the communication device may be an integrated data management network element or a chip used within the integrated data management network element.

According to a thirty-fourth aspect, an embodiment of the present application provides a communication device. The communication device includes at least one processor. The at least one processor is coupled to a memory. When the communication device operates, the processor executes computer-executable instructions or programs stored in the memory such that the communication device is enabled to perform a method according to the fourth aspect or any one of the possible designs of the fourth aspect. For example, the communication device may be a second terminal or a chip used within the second terminal.

According to a thirty-fifth aspect, an embodiment of the present application provides a communication device. The communication device includes at least one processor. The at least one processor is coupled to a memory. When the communication device operates, the processor executes computer-executable instructions or programs stored in the memory such that the communication device is enabled to perform a method according to the fifth aspect or any one of the possible designs of the fifth aspect. For example, the communication device may be an access network device or a chip used within the access network device.

According to a thirty-sixth aspect, an embodiment of the present application provides a communication device. The communication device includes at least one processor. The at least one processor is coupled to a memory. When the communication device operates, the processor executes computer-executable instructions or programs stored in the memory such that the communication device is enabled to perform a method according to the sixth aspect or any one of the possible designs of the sixth aspect. For example, the communication device may be a second terminal or a chip used within the second terminal.

According to a thirty-seventh aspect, an embodiment of the present application provides a communication device. The communication device includes at least one processor. The at least one processor is coupled to a memory. When the communication device operates, the processor executes computer-executable instructions or programs stored in the memory such that the communication device is enabled to perform a method according to the seventh aspect or any one of the possible designs of the seventh aspect. For example, the communication device may be an access management network element or a chip used within the access management network element.

It should be understood that the memory described in any one of the thirty-first to thirty-seventh aspects may alternatively be replaced with a storage medium. This is not limited in the embodiments of the present application. In a possible implementation, the memory described in any one of the thirty-first to thirty-seventh aspects may be a memory within the communication device. Of course, the memory may alternatively be located outside the communication device, but at least one processor may still execute computer-executable instructions or programs stored in the memory.

According to a thirty-eighth aspect, an embodiment of the present application provides a communication device. The communication device includes one or more modules configured to perform a method according to any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, or the seventh aspect. The one or more modules may correspond to a step in a method according to any one of the first aspect, the second aspect, the third aspect, the fourth aspect, the fifth aspect, the sixth aspect, or the seventh aspect.

According to a thirty-ninth aspect, an embodiment of the present application provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to operate a computer program or instructions to perform a network access method according to the first aspect or a possible implementation of the first aspect. The communication interface is configured to communicate with another module external to the chip.

According to a fortieth aspect, an embodiment of the present application provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to operate a computer program or instructions to perform a network access method according to the second aspect or a possible implementation of the second aspect. The communication interface is configured to communicate with another module external to the chip.

According to a forty-first aspect, an embodiment of the present application provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to operate a computer program or instructions to perform a network access method according to the third aspect or a possible implementation of the third aspect. The communication interface is configured to communicate with another module external to the chip.

According to a forty-second aspect, an embodiment of the present application provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to operate a computer program or instructions to perform a network access method according to the fourth aspect or a possible implementation of the fourth aspect. The communication interface is configured to communicate with another module external to the chip.

According to a forty-third aspect, an embodiment of the present application provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run a computer program or instructions to perform a network access method according to the fifth aspect or a possible implementation of the fifth aspect. The communication interface is configured to communicate with another module external to the chip.

According to a forty-fourth aspect, an embodiment of the present application provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run a computer program or instructions to perform a network access method according to the sixth aspect or a possible implementation of the sixth aspect. The communication interface is configured to communicate with another module external to the chip.

According to a forty-fifth aspect, an embodiment of the present application provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run a computer program or instructions to perform a network access method according to the seventh aspect or a possible implementation of the seventh aspect. The communication interface is configured to communicate with another module external to the chip.

Specifically, the chip provided in the embodiments of the present application further includes a memory configured to store computer programs or instructions.

According to a forty-sixth aspect, an embodiment of the present application provides a communication system. The communication system includes a communication device according to the ninth aspect or any one of the possible implementations of the ninth aspect, and a communication device according to the tenth aspect or any one of the possible implementations of the tenth aspect.

In a possible implementation, the communication system may further include a communication device according to the eighth aspect or any one of the possible implementations of the eighth aspect.

According to a forty-seventh aspect, an embodiment of the present application provides a communication system. The communication system includes a communication device according to the eleventh aspect or any one of the possible implementations of the eleventh aspect, and a communication device according to the twelfth aspect or any one of the possible implementations of the twelfth aspect.

According to a forty-eighth aspect, an embodiment of the present application provides a communication system. The communication system includes a communication device according to the thirteenth aspect or any one of the possible implementations of the thirteenth aspect, and a communication device according to the fourteenth aspect or any one of the possible implementations of the fourteenth aspect.

Any of the devices, computer storage media, computer program products, chips, or communication systems provided above are configured to perform the corresponding methods provided above. Therefore, for the beneficial effects that can be achieved by the devices, computer storage media, computer program products, chips, or communication systems provided above, please refer to the beneficial effects of the corresponding solutions in the corresponding methods provided above. Details will not be repeated in this specification.

2 is a schematic diagram of the architecture of a public network integrated NPN and a standalone NPN according to an embodiment of the present application; FIG. 1 is a schematic diagram of an architecture of a public or non-public network according to an embodiment of the present application. 1 is a diagram of the architecture of a communication system to which a network access method according to an embodiment of the present application can be applied; FIG. 1 is a diagram of a 5G network architecture according to an embodiment of the present application. A schematic diagram of an architecture in which a non-public network and a public network are interworked based on N3IWF according to an embodiment of the present application. 1 is a schematic diagram of an architecture in which a non-public network and a public network are interworked based on a roaming architecture according to an embodiment of the present application; 1 is a first schematic flow chart of a network access method according to an embodiment of the present application; 4 is a second schematic flow chart of a network access method according to an embodiment of the present application; 4 is a third schematic flow chart of a network access method according to an embodiment of the present application; 4 is a fourth schematic flow chart of a network access method according to an embodiment of the present application; 5 is a fifth schematic flow chart of a network access method according to an embodiment of the present application. 1 is a first schematic flow chart of a specific embodiment of a network access method according to an embodiment of the present application; 4 is a second schematic flow chart of a specific embodiment of a network access method according to an embodiment of the present application; 4 is a third schematic flow chart of a specific embodiment of a network access method according to an embodiment of the present application; 4 is a fourth schematic flow chart of a specific embodiment of a network access method according to an embodiment of the present application; 5 is a fifth schematic flow chart of a specific embodiment of a network access method according to an embodiment of the present application. 6 is a sixth schematic flow chart of a specific embodiment of a network access method according to an embodiment of the present application. 1 is a schematic diagram of the structure of a communication device according to an embodiment of the present application; 1 is a schematic diagram of the structure of another communication device according to an embodiment of the present application; 1 is a schematic diagram of a structure of a chip according to an embodiment of the present application.

In order to clearly describe the technical solutions in the embodiments of the present application, the embodiments of the present application use terms such as "first" and "second" to distinguish between the same items or between similar items having essentially the same function or purpose. For example, a first terminal and a second terminal are merely intended to distinguish between different terminals, and are not intended to limit their order. Those skilled in the art can understand that terms such as "first" and "second" do not limit the quantity and execution order, and terms such as "first" and "second" do not indicate clear differences.

It should be noted that in this application, terms such as "example" or "for example" are used to denote providing an example, illustration, or explanation. Any embodiment or design style described in this application as an "example" or "for example" is not being described as being preferred or having more advantages over another embodiment or design style. Strictly speaking, the use of terms such as "example" or "for example" is intended to concretely present the relevant concept.

The network architecture and service scenarios described in the embodiments of the present application are intended to more clearly explain the technical solutions in the embodiments of the present application, and are not limitations on the technical solutions provided in the embodiments of the present application. Those skilled in the art may understand that with the evolution of network architectures and the emergence of new service scenarios, the technical solutions provided in the embodiments of the present application can also be applied to similar technical problems.

In this application, "at least one" means one or more, and "multiple" means more than one. "And/or" describes an association relationship between related objects and indicates that three relationships may exist. For example, A and/or B may represent the following cases: only A is present, both A and B are present, and only B is present, where A and B may be singular or plural. The character "/" generally indicates an "or" relationship between related objects. "At least one of the following items" or similar expressions means any combination of the items, such as any combination of one item or multiple items. For example, at least one of a, b, or c may refer to a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural.

The steps of the network access method provided in the embodiments of the present application are merely examples. Not all of the steps are required, and not all of the information or content of each message is required. Steps or content may be added or removed as needed in the usage process.

The same step or steps or messages having the same function in the embodiments of this application may be cross-referenced in different embodiments.

The system architecture and service scenarios described in the embodiments of the present application are intended to more clearly explain the technical solutions in the embodiments of the present application, and are not limitations on the technical solutions provided in the embodiments of the present application. Those skilled in the art may find that the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems with the evolution of network architectures and the emergence of new service scenarios. In the embodiments of the present application, an example in which the provided method is applied to an NR system or a fifth generation mobile communication technology (5th generation mobile networks or 5th generation wireless systems, 5th-Generation, 5G) network is used for explanation.

Before describing the embodiments of this application, we will first explain the relevant terms used in the embodiments of this application as follows.

(1) A public network refers to a network established and operated to provide land mobile communications services to the public, i.e., a traditional carrier network. Land mobile communications services include, but are not limited to, cellular communications services. For example, a public network may be a public land mobile network (PLMN).

(2) A non-public network (NPN) is a non-public 5G network that is a communication network that can be used by several individual users. For example, a non-public network may include an industrial communication network, an enterprise private network, and the like. The typical service area of an industrial communication network is usually one or more industrial parks, and the service area of an enterprise private network is usually all users within an enterprise. In other words, a non-public network serves only devices managed or owned by the industrial communication network or the enterprise private network, and provides network communication services such as data connections for those devices.

For example, if a non-public network provides communications services to an industrial park, the non-public network may provide communications services to terminals located within the industrial park that have the capability and authorization to access the non-public network.

The non-public networks of the embodiments of this application are sometimes referred to as private or dedicated networks. This is generally referred to herein and will not be discussed in detail below.

Non-public networks may include public network integrated NPNs (PNI-NPNs) and standalone NPNs (SNPNs). Public network integrated NPNs may be implemented with the support of the PLMN, whereas SNPNs may be implemented independently of the network functions of the PLMN.

The public network integrated NPN may be implemented using network slices in the PLMN. In order to prevent unauthorized terminals from accessing and attempting to select the PNI-NPN, a closed access group (CAG) function is further used. The CAG is used to identify a group of terminals. A group of terminals that can be identified using the CAG is allowed to access a cell associated with the CAG. In order to prevent a terminal that is not allowed to access a CAG cell from automatically selecting and accessing the CAG cell, the CAG cell broadcasts one or more CAG identifiers, and the terminal is configured with an available CAG list and an indication (the indication is used to indicate whether the terminal is allowed to access the 5G system (5GS) only through the CAG cell). The integrated data management network element has subscription data for the terminal, which includes the terminal's available CAG list and indication.

As shown in FIG. 1(a), a public network integrated NPN is used as an example in FIG. 1(a). Base station 1 transmits system information block (SIB) 1, where SIB 1 includes PLMN ID=A and CAG identifier=X. Base station 2 transmits SIB 2, where SIB 2 includes PLMN ID=A. Terminal 1 has PLMN ID=A and CAG identifier=X. Terminal 2 includes PLMN ID=A, CAG identifier=X, and an indication indicating that terminal 2 can access the 5G system only through the CAG cell. Terminal 3 has PLMN ID=A. In this case, terminal 1 can access both base station 1 and base station 2, terminal 2 can access base station 1 but cannot access base station 2, and terminal 3 can access base station 2 but cannot access base station 1.

As shown in FIG. 1B, a standalone NPN is used as an example in FIG. 1B. The SNPN (5G network) is deployed independently and does not depend on the PLMN. The SNPN is identified using a PLMN ID and an NID. The PLMN ID may be a unique value reserved by a third-party operator or may be a specific value of the PLMN operator deploying the SNPN. In the SNPN, the base station 3 in the SNPN transmits an SIB3, which includes the identifier N of the SNPN (e.g., PLMN ID and NID1). The terminal 4 selects the NPN network to be accessed based on the broadcast information and the configured network selection information. If the terminal 4 finds that the configured network selection information (PLMN ID and NID2) is different from the PLMN ID broadcast by the base station 3 or different from the PLMN ID and NID1 broadcast by the base station 3, the terminal 4 does not choose to access the SNPN. If the terminal 4 finds that the configured network selection information (PLMN ID and NID1) is the same as the PLMN ID broadcast by the base station 3 or is the same as the PLMN ID and NID1 broadcast by the base station 3, the terminal 4 chooses to access the SNPN.

The architectures described in (a) of FIG. 1 and (b) of FIG. 1 do not support handover. Base station 1, base station 2, and base station 3 may be base stations of a 5G network. For example, base station 1, base station 2, and base station 3 may be next generation NodeBs (gNBs), respectively. In (a) of FIG. 1, it is used as an example that base station 1 and base station 2 access the same 5G core network (5G Core, 5GC). Base station 2 accesses 5GC, which corresponds to a non-public network.

Figure 2 shows the configuration of a public or non-public network. The public or non-public network includes a terminal, an access network (AN), a core network (Core), and a data network (DN). The terminal, AN, and Core are the main components of the architecture. Logically, the terminal, AN, and Core may each be divided into two parts: a user plane and a control plane. The control plane is responsible for mobile network management, and the user plane is responsible for service data transmission. In Figure 2, the NG2 reference point is between the control plane of the AN and the control plane of the Core, the NG3 reference point is between the user plane of the AN and the user plane of the Core, and the NG6 reference point is between the user plane of the Core and the data network.

The terminal is the ingress of interaction between the mobile user and the network, providing basic computing and storage capabilities, displaying service windows to the user, and receiving user operation input. Terminals in 5G networks may use new radio technologies to establish signaling and data connections to the AN to transmit control signals and service data to the mobile network.

The AN is similar to a base station in a conventional network, and is deployed near terminals to provide network access functions to authorized terminals within a certain area. The AN can determine transmission tunnels of various qualities based on the terminal's level and service requirements, etc. to transmit the terminal's data. The AN can manage its resources, use those resources appropriately, and provide access services to terminals as needed, and is responsible for forwarding control signals and terminal data between the terminal and the core network.

The Core is responsible for maintaining subscription data of the mobile network, managing network elements in the mobile network, and providing functions such as session management, mobility management, policy management, and security authentication to the terminal. In the terminal attachment procedure, the Core provides network access authentication for the terminal. When the terminal has a service request, the Core allocates network resources to the terminal. When the terminal moves, the Core updates the network resources of the terminal. When the terminal is idle, the Core provides a fast recovery mechanism for the terminal. In the terminal detachment procedure, the Core releases the network resources of the terminal. When the terminal has service data, the Core provides data routing function for the terminal, for example, forwarding uplink data to the data network or receiving downlink data of the terminal from the data network. The Core sends the received downlink data of the terminal to the AN so that the AN sends the downlink data of the terminal to the terminal.

A data network is a data network that provides services to users. Typically, clients are located in terminals and servers are located in data networks. A data network can be a private network, e.g. a local area network, an external network not managed and controlled by an operator, e.g. the Internet, or a dedicated network deployed collaboratively by multiple operators, e.g. a network providing IP multimedia core network subsystem (IMS) services.

In conclusion, FIG. 2 describes the main components of a non-public or public network. FIG. 3 shows a communication system to which the network access method of the present application is applicable. The communication system includes a terminal 10 and an access management network element 20. The access management network element 20 is a network element in the non-public network 100.

A terminal 10 may access the non-public network 100 via an access network device 30 and an access management network element 20 located within the non-public network 100 .

In an embodiment of the present application, the terminals 10 may be distributed within a wireless network, and each terminal may be fixed or mobile.

In a possible implementation, the communication system may further include an integrated data management network element 40. The integrated data management network element 40 is a network element in the public network 200. The public network 200 and the non-public network 100 are interworked. After the terminal 10 successfully accesses the non-public network 100, the terminal 10 may access the public network 200 through the non-public network 100.

In an embodiment of the present application, the communication system shown in FIG. 3 may be applied to a current 5G network architecture or another future network architecture. This is not limited in the embodiment of the present application.

In the following, an example is used in which the communication system shown in FIG. 3 is applicable to a 5G network, in other words, both the non-public network 100 and the public network 200 are 5G networks. A network element or entity corresponding to the access management network element 20 may be an access and mobility management function (AMF) network element shown in FIG. 3. A network element or entity corresponding to the unified data management network element 40 may be a unified data management (UDM) network element. A network element or entity corresponding to the access network device 30 may be a (radio) access network ((R)AN) device.

As shown in FIG. 4, the non-public network 100 or the public network 200 includes a session management function (SMF) network element, a policy control function (PCF) network element, a network slice selection function (NSSF) network element, an authentication server function (AUSF) network element, a network exposure function (NEF) network element, a network repository function (NRF) network element, and an application function (APF) network element. function, AF) network elements, etc. This is not particularly limited in the embodiments of the present application.

As shown in FIG. 5a, the non-public network 100 or the public network 200 may further communicate with a data network (DN), which may be managed by an AF network element.

A terminal accesses a network (non-public network or public network) through an (R)AN device, and the terminal communicates with an AMF network element through an N1 interface (abbreviated as N1). The SMF network element communicates with one or more UPF network elements through an N4 interface (abbreviated as N4). The UPF network element communicates with a DN through an N6 interface (abbreviated as N6). The (R)AN device communicates with an AMF network element through an N2 interface (abbreviated as N2). The (R)AN device communicates with a UPF network element through an N3 interface (abbreviated as N3). The control plane network elements may also interact with each other through service-oriented interfaces. For example, as shown in FIG. 4, the AMF network element, the SMF network element, the UDM network element, and the PCF network element interact with each other through service-oriented interfaces. For example, the external service-oriented interface provided by the AMF network element may be Namf. The external service-oriented interface provided by the SMF network element may be Nsmf. The external service-oriented interface provided by the UDM network element may be Nudm. The external service-oriented interface provided by the PCF network element may be Npcf. The external service-oriented interface provided by the NSSF network element may be Nnssf. The external service-oriented interface provided by the NEF network element may be Nnef. The external service-oriented interface provided by the AF network element may be Naf. It should be understood that for a relevant description of the names of various service-oriented interfaces, please refer to the figure of the 5G system architecture of the current technology. Details will not be described in this specification.

In the network architecture shown in FIG. 4, an example is used in which the control plane network elements interact with each other through a service-oriented interface. Of course, alternatively, the control plane network elements may communicate with each other as follows: the AMF entity communicates with the SMF network element through an N11 interface (abbreviated as N11); any two of the one or more UPF network elements communicate with each other through an N9 interface (abbreviated as N9); the SMF network element communicates with the PCF network element through an N7 interface (abbreviated as N7), which in turn communicates with the AF network element through an N5 interface; any two AMF network elements communicate with each other through an N14 interface (abbreviated as N14); the SMF network element communicates with the UDM through an N10 interface (abbreviated as N10); the AMF network element communicates with the AUSF through an N12 interface (abbreviated as N12). The AUSF network element communicates with the UDM network element through an N13 interface (abbreviated as N13). The AMF network element communicates with the UDM network element through an N8 interface (abbreviated as N8).

Please note that FIG. 4 merely illustrates an example of one UPF network element and one SMF network element. Of course, FIG. 4 may include multiple UPF network elements and multiple SMF network elements, for example, SMF network element 1 and SMF network element 2. This is not particularly limited in the embodiments of the present application.

It should be noted that the (R)AN device, AMF network element, SMF network element, UDM network element, UPF network element, and PCF network element in FIG. 4 are merely names, and these names do not constitute any restrictions on the devices. In 5G networks and other future networks, the network elements or entities corresponding to the (R)AN device, AMF network element, SMF network element, UDM network element, UPF network element, and PCF network element may alternatively have other names. This is not particularly limited in the embodiments of the present application. For example, the UDM network element may alternatively be replaced by a home subscriber server (HSS), a user subscription database (USD), or a database entity, etc. This is uniformly described in this specification and will not be described in detail later.

Different releases of the 3rd generation partnership project (3GPP) provide different modalities for interworking between non-public and public networks. Therefore, these modalities are described separately below with reference to Figures 5a and 5b.

In the first release of 3GPP, as shown in FIG. 5a, the non-public network 100 interworks with the public network 200 using an architecture based on a non-3GPP interworking function (N3IWF). In this case, the terminal 10 has two subscription information, specifically, the terminal 10 has both private network subscription information between the terminal 10 and the non-public network 100 and first public network subscription information between the terminal 10 and the public network 200. The private network subscription information is used by the terminal 10 to access the non-public network 100. The first public network subscription information is used by the terminal 10 to access the public network 200. It should be understood that the private network subscription information between the terminal 10 and the non-public network 100 includes an identifier 1 of the terminal 10, and the identifier 1 of the terminal 10 includes an identifier of the non-public network 100. The first public network subscription information between the terminal 10 and the public network 200 includes an identifier 2 of the terminal 10, and the identifier 2 of the terminal 10 includes an identifier of the public network 200.

For example, the first release might be Release (R) 16.

As shown in FIG. 5a, the terminal 10 determines an identifier of the non-public network 100 using private network subscription information between the terminal 10 and the non-public network 100. Then, the terminal 10 accesses an access network device deployed in the non-public network 100, and the terminal 10 performs 3GPP registration to the non-public network 100 through the access network device. The terminal 10 determines an identifier of the public network 200 using the first public network subscription information between the terminal 10 and the public network 200. Then, the terminal 10 selects an N3IWF in the public network 200, establishes a PDU session in the non-public network 100 to access the N3IWF of the public network 200, and performs N3GPP registration to the public network 200.

Specifically, as shown in FIG. 5a, the non-public network 100 includes an AMF network element 1, an SMF network element 1, and a UPF network element 1, and the public network 200 includes an AMF network element 2, an SMF network element 2, a UPF network element 2, and an N3IWF. The N3IWF is configured to implement interworking between the non-public network 100 and the public network 200.

The terminal 10 accesses the non-public network 100 using a 3GPP access technology of NPN, and then establishes a PDU session between the terminal 10 and the UPF network element 1 in the non-public network 100. Thereafter, when the terminal 10 needs to perform non-3GPP (N3GPP) registration to the public network 200 through the non-public network 100, the terminal 10 may send a public network registration request message to the UPF network element 1 using the PDU session established between the terminal 10 and the UPF network element 1. The public network registration request message is used to request the terminal 10 to register with the public network 200. The UPF network element 1 then sends a public network registration request message to the N3IWF through the DN1 shown in FIG. 5a. After receiving the public network registration request message, the N3IWF may forward the public network registration request message to the AMF network element 2 in the public network 200, and the AMF network element 2 determines whether the terminal 10 is allowed to register in the public network 200 based on the public network registration request message. If the AMF network element 2 allows the terminal 10 to register in the public network 200, the AMF network element 2 sends a registration accept message to the N3IWF, so that the N3IWF sends a registration accept message to the UPF network element 1 in the non-public network 100 through the DN1. After receiving the registration accept message, the UPF network element 1 may also send the registration accept message to the terminal 10 using a PDU session between the UPF network element 1 and the terminal 10. It can be understood that the DN1 is configured to provide a service to the non-public network 100, and the DN2 is configured to provide a service to the public network 200. Specifically, the terminal 10 may access services deployed on DN1 through the non-public network 100. Specifically, the terminal 10 may access services deployed on DN2 through the public network 200.

Please note that for the communication interfaces between the network elements of the non-public network 100 and the public network 200 shown in FIG. 5a, please refer to the description of FIG. 4. Details will not be repeated here. As shown in FIG. 5a, the N3IWF communicates with the DN through the N6 interface. The N3IWF communicates with the AMF network element 2 through the N2 interface in the public network.

In the second release of 3GPP (the second release is an upgrade release of the first release), the non-public network 100 interworks with the public network 200 using a roaming architecture, as shown in FIG. 5. In this case, the terminal 10 has a second public network subscription information between the terminal 10 and the public network 200. As shown in FIG. 5b, the terminal 10 determines an identifier of the non-public network 100 using the second public network subscription information between the terminal 10 and the public network 200. After determining the identifier of the non-public network 100, the terminal 10 may choose to perform registration to the non-public network 100 using an (R)AN device deployed in the non-public network. The terminal 10 may then establish a session (e.g., a PDU session) in the non-public network 100, which determines, based on the second public network subscription information, that the mode of the session is home routed (HR) mode or local breakout mode. For example, the second release may be R17.

It should be understood that the second public network subscription information includes information about one or more non-public networks that the terminal 10 is allowed to access. When the terminal 10 is located within the coverage area of the non-public network a, the terminal 10 may receive broadcast information of the non-public network a (including an identifier of the non-public network a). If the identifier of the non-public network a included in the broadcast information is the same as the identifier of the non-public network among the identifiers of the one or more non-public networks, the terminal 10 may determine that the non-public network a can be selected for access.

5b uses an example in which the roaming architecture supporting interworking between the non-public network 100 and the public network 200 is in home routed mode. In FIG. 5b, the non-public network 100 of the terminal 10 (sometimes referred to as the terminal's visited network) includes an AMF network element 1, a visited SMF (V-SMF) network element, a visited PCF (V-PCF) network element, an (R)AN device, a visited UPF (V-UPF) network element, and a visited NSSF (V-NSSF) network element. The public network 200 of the terminal 10 (sometimes referred to as the terminal's home network) includes a home SMF (H-SMF) network element, a home PCF (H-PCF) network element, a home UPF (H-UPF) network element, a UDM network element, an AUSF network element, and a home NSSF (H-NSSF) network element.

The H-SMF network element communicates with the V-SMF network element through an N16 interface, and the AUSF network element communicates with the AMF network element through an N12 interface. The H-PCF network element communicates with the V-PCF network element through an N24 interface. The AMF network element 1 communicates with the V-NSSF network element through an N22 interface. The V-NSSF network element communicates with the H-NSSF network element through an N31 interface. The H-UPF network element communicates with the V-UPF network element through an N9 interface.

The public network 200 may further include a home security edge protection proxy (H-SEPP). The non-public network 100 may further include a visited security edge protection proxy (V-SEPP). The public network 200 communicates with the non-public network 100 through the visited SEPP and the home SEPP. An N32 interface exists between the home SEPP and the visited SEPP.

In an embodiment of the present application, the public network may be a PLMN and the non-public network may be a SNPN. This is generally stated in this specification and will not be described in detail later.

The functions of the functional entities in the core network are as follows:

The UPF network element is configured to forward user data packets according to the routing rules of the SMF network element, e.g., to send uplink data to a DN or another UPF and to forward downlink data to another UPF or a RAN.

The AUSF network element is configured to perform security authentication on the terminal.

The AMF is configured to perform access management and mobility management of the terminal. The AMF is responsible for terminal status maintenance, terminal reachability management, non-mobility management (MM), non-access stratum (NAS) message forwarding, and session management (SM) N2 message forwarding.

The SMF network element is responsible for managing the terminal's sessions and allocating or releasing resources for the terminal's sessions, where the resources include session quality of service (QoS) parameters, session paths, and forwarding rules, etc.

The NSSF is configured to select a network slice for the terminal.

NEF exposes network functions to third parties through a northbound application programming interface (API).

The NRF stores and selects network function entity information for different network elements.

The UDM network element is configured to store subscription information of the terminal or manage the context of the terminal.

The PCF network element is configured to manage the policies.

The AF network element is configured to manage the application.

Terminals may include a variety of handheld devices, vehicle-mounted devices, wearable devices, and computing devices with wireless communication capabilities or other processing devices connected to a wireless modem. A terminal may be a subscriber unit, a cellular phone, a smartphone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a wireless modem, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a machine type communication (MTC) terminal, a user equipment (UE), a mobile station (MS), a terminal device (terminal The relay user equipment may further include a 5G UE (5G LTE) or a 5G LTE-LTE (5G LTE-LTE) or a 5G LTE-LTE (5G LTE-LTE) or a 5G LTE-LTE (5G LTE-LTE). The relay user equipment may be, for example, a 5G residential gateway (RG). For ease of explanation, in this application, the above-mentioned devices are collectively referred to as terminals.

It should be understood that the terminals in the embodiments of the present application may be terminal devices in the Internet of Things, or terminals in multiple vertical industrial application fields such as ports, intelligent factories, rail transportation, logistics, unmanned aerial vehicles, and autonomous vehicles, for example, mobile robots, automated guided vehicles (AGVs), autonomous vehicles, control devices and sensors on trains, or control devices and sensors deployed in factories.

For example, in the embodiment of the present application, the terminal may alternatively be a wearable device. A wearable device, sometimes called a wearable intelligent device, is a collective term for wearable devices, such as glasses, gloves, watches, clothes, and shoes, developed by applying wearable technology to the high-performance design of daily accessories. A wearable device is a portable device that can be directly worn on the body or integrated into a user's clothes or accessories. A wearable device implements powerful functions not only through hardware devices, but also through software support, data exchange, and cloud interaction. Generalized wearable intelligent devices include full-featured and large-sized devices such as smart watches or smart glasses that can implement all or some functions without relying on a smartphone, and devices such as various smart bands or smart jewelry that monitor physical signs, which are specialized in only one type of application function and need to cooperate with other devices such as smartphones. The terminal may alternatively be a sensor device used in a factory.

The access network device is configured to provide network access functions to authorized terminals in a certain area, and can use transmission tunnels of various qualities based on the level and service requirements of the terminals, etc. The access network device can manage radio resources, provide access services to the terminals, and further complete the transfer of control signals and terminal data between the terminals and the core network. The access network device may also be understood as a base station in a conventional network. For example, the access network device may be responsible for functions such as radio resource management, quality of service (QoS) management, and data compression and encryption on the air interface side.

In the embodiment of the present application, the specific structure of the execution body of the network access method is not particularly limited in the embodiment of the present application, as long as communication can be performed according to the network access method of the embodiment of the present application by operating a program that records the code of the network access method of the embodiment of the present application. For example, the network access method provided in the embodiment of the present application may be performed by a function module in the first terminal that can call and execute a program, or may be performed by a communication device, such as a chip, used in the first terminal. The network access method provided in the embodiment of the present application may be performed by a function module in the access management network element that can call and execute a program, or may be performed by a communication device, such as a chip, used in the access management network element. This is not limited in the present application. The network access method provided in the embodiment of the present application may be performed by a function module in the integrated data management network element that can call and execute a program, or may be performed by a communication device, such as a chip, used in the integrated data management network element. This is not limited in the present application. The following embodiment will be described using an example in which the network access method is performed by a first terminal, an access management network element, and an integrated data management network element.

Figure 6 illustrates an embodiment of a network access method interaction according to an embodiment of the present application. The method includes the following steps:

Step 601: A first terminal sends a first message to an access management network element in a first non-public network. In response, the access management network element in the first non-public network receives a first message from the first terminal. The first message is used to request registration of the first terminal in the first non-public network.

It should be understood that the first terminal is located within the coverage area of the first non-public network. It should be understood that the first terminal may detect one or more candidate non-public networks, and the first non-public network may be any of the one or more candidate non-public networks. Of course, the first non-public network may be the candidate non-public network with the strongest signal quality among the one or more candidate non-public networks.

For example, the access management network element may be the access management network element 20 shown in FIG. 2. The first non-public network may be the non-public network 100 in FIG. 2.

The first terminal in this embodiment of the present application does not have permission or ability to access a non-public network. Of course, the first terminal may have permission or ability to access a public network. This is not limited in this embodiment of the present application.

Note that in one aspect, the "non-public network" in "the first terminal does not have permission to access the non-public network" may refer to non-public networks in general. In other words, the first terminal does not have permission to access any non-public network. For example, the first terminal cannot access the non-public network, regardless of whether the non-public network is non-public network 1 or non-public network 2. In another aspect, the "non-public network" in "the first terminal does not have permission to access the non-public network" may refer to a specific non-public network. In other words, the first terminal cannot access only that specific non-public network (e.g., the specific non-public network is the first non-public network), but the first terminal may access non-public networks other than the first non-public network. For example, the first non-public network is non-public network 1. The first terminal does not have the ability to access non-public network 1, but the first terminal has the ability to access non-public network 2.

For example, a first terminal may be specifically configured to access a non-public network 2 serving a factory 1, and when the first terminal is located within the coverage area of the non-public network 1 serving the factory 2, the first terminal does not have permission to access the non-public network 1.

In a possible implementation, the first message may further carry an identifier of the first terminal. The identifier of the first terminal is used to identify the first terminal. For example, the identifier of the first terminal may be one or more of a subscription permanent identifier (SUPI) and a concealed subscriber identifier (SUCI). For the identifier of the terminal in the following embodiment, please refer to the description in this specification. Details will not be described again later.

In a particular implementation, step 601 of this embodiment of the present application may be implemented as follows: the first terminal sends a first message to an access management network element in the first non-public network through an access network device in the first non-public network. Correspondingly, the access management network element in the first non-public network receives a first message from the first terminal through an access network device in the first non-public network. It may be understood that the access management network element may further obtain information about the first non-public network from the access network device in the first non-public network. For example, the information about the first non-public network may be used to identify the non-public network. For example, the information about the first non-public network may be an identifier of the first non-public network. For example, the information about the first non-public network is an identifier of the first non-public network. In this case, the identifier of the first non-public network is determined based on the identifier of the target public network and the NID.

The target public network in this embodiment of the present application is a public network corresponding to the first non-public network. For example, the target public network is a public network of operator A. If the target public network identifier assigned to the target public network by operator A is "00000" and the NID is "0001", the first non-public network identifier includes "00000001". In other words, the target public network identifier is a specific value assigned to the target public network by the operator deploying the first non-public network. Alternatively, the target public network identifier is a unique value reserved for the target public network by a third-party operator. This is not limited in the embodiment of the present application.

For example, the first message may be a registration request message.

Step 602: The access management network element sends a query message to the integrated data management network element in the first public network. In response, the integrated data management network element in the first public network receives a query message from the access management network element in the non-public network. The query message is used to query subscription data of the first terminal.

The first public network interworks with the first non-public network. In other words, the first non-public network described in steps 601 to 605 is a non-public network that interworks with the first public network.

For example, the inquiry message may carry an identifier of the first terminal and information about the first non-public network.

For example, the first public network may be public network 200 shown in FIG. 2. The integrated data management network element may be integrated data management network element 40 in FIG. 2.

Step 603: The integrated data management network element sends a third message to the access management network element. In response, the access management network element obtains a third message from the integrated data management network element in the first public network. The third message includes one or more of the subscription data and the cause value of the first terminal.

The subscription data includes second indication information. In one aspect, the second indication information is used to indicate that the first terminal can access only the public network. Alternatively, in another aspect, the second indication information is used to indicate that the first terminal cannot access a non-public network. The cause value indicates that the first terminal is not allowed to access the first non-public network.

Note that step 602 may be omitted if the integrated data management network element may actively send a third message to the access management network element.

It should be understood that the "public network" in "the first terminal can access only the public network" refers to a public network in general. In other words, the first terminal is configured to access any public network other than the non-public network, and is not limited to accessing only the first public network. The "non-public network" in "the first terminal cannot access the non-public network" may refer to a non-public network in general. In other words, the first terminal cannot access any non-public network. The "non-public network" in "the first terminal cannot access the non-public network" refers to a specific non-public network. In other words, the first terminal cannot access the first non-public network. This is not limited in the embodiment of the present application.

Step 604: The access management network element sends a second message to the first terminal based on the third message. In response, the first terminal receives a second message from the access management network element. The second message is used to indicate that registration of the first terminal to the first non-public network is rejected. The second message includes first indication information, and the first indication information indicates that access of the first terminal to the first non-public network is prohibited.

Step 605: The first terminal updates the first terminal's prohibited network list based on the first indication information. The updated prohibited network list includes information about the first non-public network.

Of course, the updated prohibited network list may also be considered the first prohibited network list.

In an alternative manner, step 605 of this embodiment of the present application may be implemented as follows: the first terminal adds information about the first non-public network to the first terminal's prohibited network list based on the first indication information.

In one aspect, it can be understood that the prohibited network list of the first terminal may have information about one or more networks, and the one or more networks may include the first non-public network. In other words, the prohibited network list of the first terminal may include the first non-public network. Each of the one or more networks has a record item, and the record item is used to indicate whether access to the network is prohibited or allowed. In this case, the updated prohibited network list including information about the first non-public network may be understood as the first terminal setting the record item corresponding to the first non-public network to an access prohibited state.

When a first terminal updates its prohibited network list, it may mean that the first terminal updates a record item corresponding to the first non-public network in the prohibited network list.

For example, if the record item of the first non-public network is indicator a, it indicates that access to the first non-public network is prohibited. If the record item of the first non-public network is indicator b, it indicates that access to the first non-public network is allowed. The record item corresponding to the first non-public network in the prohibited network list is indicator b, in this case, the first terminal performs steps 601 to 603 to request access to the first non-public network. However, the first terminal receives a second message in the process of requesting access to the first non-public network. Based on the second message, the first terminal determines that access to the first non-public network is denied. Then, the first terminal may set the record item corresponding to the first non-public network to indicator a.

Of course, indicator a may alternatively be represented in an inactive state and indicator b may alternatively be represented in an active state. This is not limited to this embodiment of the present application.

Of course, in another aspect, the prohibited network list of the first terminal may have information about one or more networks, which do not include the first non-public network. In this case, the updated prohibited network list including information about the first non-public network may be understood as the first terminal adding information about the first non-public network to the prohibited network list and setting the record item corresponding to the first non-public network to indicator a.

For example, the first non-public network is non-public network 1, and the first terminal does not have permission to access non-public network 1. When the first terminal is located within the coverage area of non-public network 1, the first terminal may send a first message to an access management network element in non-public network 1 through an access network device in non-public network 1 to request to register with non-public network 1. If the first terminal then receives a second message from the access management network element, and the second message indicates that the registration of the first terminal with non-public network 1 is denied, the first terminal may determine that non-public network 1 is a non-public network that the first terminal is prohibited from accessing.

In this embodiment of the present application, the information about the first non-public network is used to identify the first non-public network. For example, the information about the first non-public network may be an identifier of the first non-public network. Of course, the information about the first non-public network may alternatively be another parameter that can identify the first non-public network. This is not limited in the embodiment of the present application.

This embodiment of the present application provides a network access method, in which a first terminal sends a first message to an access management network element in a first non-public network to request the first terminal to register with the first non-public network. Then, the first terminal receives a second message from the access management network element, where the second message indicates that the registration of the first terminal with the first non-public network is rejected, and the first indication information indicates that the first terminal is prohibited from accessing the first non-public network. This helps the first terminal to update a prohibited network list of the first terminal based on the first indication information, so that the updated prohibited network list includes information about the first non-public network. Then, when selecting a network for registration, the first terminal can avoid selecting the first non-public network that the first terminal is prohibited from accessing. This solution can solve the problem that occurs when a first terminal that does not have permission to access the first non-public network attempts to access the first non-public network.

In a possible embodiment, after step 605, the method provided in this embodiment of the present application may further include the first terminal selecting a network other than the first non-public network for registration based on the updated prohibited network list.

In a particular implementation, the first terminal selecting a network other than the first non-public network for registration based on the updated prohibited network list may be implemented as follows: That is, the first terminal selects a network for registration that is not recorded in the updated prohibited network list based on the updated prohibited network list.

For example, the first non-public network is non-public network 1. If the updated prohibited network list includes information about non-public network 1, the first terminal may select non-public network 2 other than non-public network 1 for registration. If the updated prohibited network list includes information about non-public network 1 and information about non-public network 2, the first terminal may also select non-public network 3 other than non-public network 1 and non-public network 2 for registration, in which case the updated prohibited network list does not include information about non-public network 3.

In a possible embodiment, after step 605, the method provided in this embodiment of the present application may further include the first terminal starting a timer based on the first indication information. When the timer expires, the first terminal deletes information about the first non-public network from the updated prohibited network list. In this way, when the timer expires, the first non-public network may continue to be used as a non-public network that the first terminal may choose to access.

It should be understood that expiration of a timer can mean that the timer reaches its corresponding timer time value.

In an alternative implementation, the first terminal deleting information about the first non-public network from the updated prohibited network list may alternatively be rephrased as follows: the first terminal updates the first prohibited network list to obtain a second prohibited network list. The second prohibited network list does not include information about the first non-public network, or the record item corresponding to the first public network in the second prohibited network list indicates that the first non-public network is an accessible network. This is not limited to this embodiment of the present application.

Referring to the above example, when the timer expires, the first terminal updates the record item corresponding to the first non-public network from indicator a to indicator b.

It may be understood that when the first terminal removes information about the first non-public network from the updated prohibited network list, the first terminal may continue to request to register with the first non-public network thereafter. For example, for a first terminal that does not have permission to access the non-public network, if the first terminal has permission to access the non-public network after the setting, the first terminal may thereafter register with the first non-public network since the first terminal removes information about the first non-public network from the prohibited network list when the timer time value corresponding to the timer is reached.

Note that in this embodiment of the present application, deleting information about a non-public network from the prohibited network list may also be expressed as setting, by the second terminal, a record item corresponding to the non-public network to indicator a.

In this embodiment of the present application, a timer time value corresponding to the timer may be predefined in the protocol, a timer time value corresponding to the timer may be set by the first terminal, or a timer time value corresponding to the timer may be set for the first terminal by the access management network element.

When the access management network element sets a timer time value corresponding to the timer for the first terminal, the second message includes the timer time value. In response, the first terminal sets the timer based on the timer time value. Of course, the access management network element may alternatively transmit the timer time value corresponding to the timer to the first terminal using a message other than the second message. This is not limited in this embodiment of the present application.

The embodiment described in FIG. 6 is applicable to the following scenarios:

Scenario 1: Both the first non-public network and the first public network are networks defined in the first release. For example, the first non-public network is an R16 non-public network and the first public network is an R16 public network.

Scenario 2: Both the first non-public network and the first public network are networks defined in the second release. For example, the first non-public network is an R17 non-public network and the first public network is an R17 public network. In this case, the access management network element may be the AMF network element of FIG. 5b.

In scenarios 1 and 2, when interworking is not supported between the first non-public network and the first public network, step 605 may be omitted. In this case, the first indication information in the second message may be replaced with indication information x, where the indication information x is used to indicate that the cause of prohibiting the first terminal from accessing the first non-public network is that the first terminal is an unauthorized terminal. The first terminal being an unauthorized terminal indicates that the first non-public network cannot identify the identity of the first terminal.

In scenario 2, when interworking is supported between the first non-public network and the first public network, step 605 is a required step.

Note that if the first non-public network is an R17 non-public network and the first public network is an R17 public network, the first non-public network interworks with the first public network using a roaming architecture.

Figure 7 illustrates an embodiment of a network access method interaction according to an embodiment of the present application. The method includes the following steps:

Step 701: An access network device in a first non-public network transmits broadcast information. In response, a second terminal receives broadcast information from the access network device in the first non-public network. The broadcast information includes first indication information, and the first indication information is used to indicate that the first non-public network and the public network are interworked.

The second terminal in this embodiment of the present application has permission to access a non-public network. Of course, the second terminal may have permission to access a public network, or the second terminal may not have permission to access a public network. This is not limited in this embodiment of the present application.

In one aspect, the "non-public network" in "the second terminal has permission to access the non-public network" may refer to non-public networks in general. In other words, the second terminal has permission to access any non-public network. For example, the second terminal can access a non-public network regardless of whether the non-public network is non-public network 1 or non-public network 2. In another aspect, the "non-public network" in "the second terminal has permission to access the non-public network" may refer to a specific non-public network. In other words, the second terminal can access only that specific non-public network (e.g., the specific non-public network is the first non-public network).

It can be understood that the "public network" in "the first non-public network and the public network are interworked" can be any public network in general.

It should be understood that the second terminal is located within the coverage area of the first non-public network, and the second terminal is capable of receiving broadcast information transmitted by an access network device in the first non-public network.

For example, the first indication information may be a first indicator, and the first indicator is used to indicate that the first non-public network and the public network are interworked. For example, the first indication information may be "1".

In a particular implementation, the first indication information is used to indicate that the first non-public network and the public network are interworked using a roaming architecture. This helps the second terminal to access the first non-public network using the roaming architecture. The second terminal accessing the first non-public network using the roaming architecture may mean that the second terminal accesses the first non-public network using subscription information (e.g., the first subscription information below) of the second terminal in the public network.

In a possible implementation, before step 701, the method of this embodiment of the present application may further include an access network device in the first non-public network determining that the first non-public network and the public network are interworked. For example, the access network device in the first non-public network determining that the first non-public network and the public network are interworked may be implemented as follows: That is, the access network device determines that the non-public network and the public network are interworked based on the operator's configuration information.

Step 702: The second terminal determines, based on the broadcast information, to access the first non-public network using the first subscription information. The first subscription information is subscription information of the second terminal in the first public network.

In a possible implementation, the first identifier of the second terminal carried in the first subscription information relates to the first public network. For example, the first identifier of the second terminal carries information about the first public network, such as, for example, a network identifier PLMN ID.

It may be understood that the first public network is one of one or more public networks that interwork with the first non-public network.

For example, the first public network may be public network 200 of FIG. 5b. The first non-public network may be non-public network 100 of FIG. 5b. The access management network element may be AMF network element 1 of FIG. 5b.

This embodiment of the present application provides a network access method. In this method, a second terminal receives broadcast information broadcasted by an access network device, which helps the second terminal determine based on the first indication information carried in the broadcast information that the first non-public network supports interworking with the public network. The second terminal may then determine that the second terminal can access the first non-public network using the first subscription information. When the second terminal subsequently needs to access the first non-public network, the second terminal may request to register with the first non-public network using the first subscription information. This avoids registration failures that occur when the second terminal blindly initiates a registration request to the first non-public network without knowing that the public network and the first non-public network are interworked.

In a possible embodiment, after step 702, the method provided in this embodiment of the present application may further include the second terminal accessing the first non-public network using the first subscription information.

In a possible implementation, the second terminal accessing the first non-public network using the first subscription information may be implemented as follows: the second terminal sends a first message to an access management network element in the first non-public network using the first subscription information, where the first message is used to indicate that the second terminal registers with the first non-public network. The first message carries a first identifier of the second terminal.

In an example, the first message may carry a registration indication, which is used to indicate that the second terminal is registering with the first non-public network.

In a possible embodiment, the broadcast information further includes information about one or more public networks that interwork with the first non-public network, to which the first public network belongs. The access network device broadcasts information about the one or more public networks, which helps the second terminal determine the one or more public networks that can be accessed by the second terminal.

In a possible implementation, the broadcast information may further include a manual selection access indication, and the second terminal may prompt the user to access the first non-public network in a manual selection manner based on the manual selection access indication. This prevents the second terminal from automatically selecting the first non-public network.

For example, if the first non-public network belongs to country A, then the one or more public networks also belong to country A.

In a possible implementation, the first public network may be any one of the one or more public networks described above. In other words, the second terminal may select any public network from the one or more public networks described above as the first public network. In another possible implementation, the network selection priority of the first public network is the highest among the network selection priorities of the one or more public networks described above. Alternatively, the first public network is a public network supported by the second terminal.

It should be understood that the second terminal has a network selection preference for each of the one or more public networks described above.

In a possible implementation, the second terminal has subscription information between the second terminal and the public network.

The first non-public network of the embodiment described in FIG. 7 may be an R17 non-public network. The public network may be an R17 public network. In other words, the first non-public network and the public network of the embodiment described in FIG. 7 are interworked using a roaming architecture.

Figure 8 illustrates an embodiment of a network access method interaction according to an embodiment of the present application. The method includes the following steps:

Step 801: The second terminal sends a first message to an access management network element in the first non-public network using the first subscription information. In response, the access management network element in the first non-public network receives a first message from the second terminal, where the first message is used to indicate that the second terminal requests to register with the first non-public network using the first subscription information.

In the example, the second terminal in this embodiment of the present application is a second terminal supporting a network of a first release. A second terminal supporting a network of a first release means that the second terminal has non-public network subscription information between the second terminal and a first non-public network of a first release, and has public network subscription information between the second terminal and a first public network of a first release. In this case, in step 801, the "first non-public network" in "the second terminal sends a first message to an access management network element in the first non-public network using the first subscription information" refers to the first non-public network of a second release.

When the second terminal is a second terminal supporting a network of a first release, the access management network element in the first non-public network may be an access management network element in the first non-public network of a second release. In this case, the first subscription information is subscription information of the second terminal in the first non-public network. In other words, the first subscription information is non-public network subscription information of the second terminal in the first non-public network of a first release.

In another example, the second terminal in this embodiment of the present application is a second terminal supporting a network of a second release. A second terminal supporting a network of a second release means that the second terminal has public network subscription information between the second terminal and a first public network of a second release. In this case, in step 801, the "first non-public network" in "the second terminal sends a first message to an access management network element in the first non-public network using the first subscription information" refers to the first non-public network of the first release.

When the second terminal is a second terminal supporting a network of a second release, the access management network element in the first non-public network may be an access management network element in the first non-public network of the first release. In this case, the first subscription information is subscription information of the second terminal in the first public network. In other words, the first subscription information is public network subscription information between the second terminal and the first public network of the second release.

The first release may be an R16 release and the second release may be an R17 release.

In a possible implementation, when a first public network of a second release interworks with a first non-public network of a second release using a roaming architecture, the first subscription information is subscription information of a second terminal in the first non-public network of a first release. In this case, a second identifier of the second terminal carried in the first subscription information relates to the first non-public network. For example, the second identifier of the second terminal includes an identifier of the first non-public network.

In a possible implementation, when the first public network of the first release interworks with the first non-public network of the first release through the N3IWF, the first subscription information is subscription information of the second terminal in the first public network of the second release. In this case, the third identifier of the second terminal carried in the first subscription information relates to the first public network. For example, the third identifier of the second terminal includes information about the first public network. For example, the information about the first public network is used to identify the first public network.

In this embodiment of the present application, the second terminal sending a first message to an access management network element in a first non-public network using the first subscription information may also be understood as the second terminal sending a first message to an access management network element in a first non-public network, where it is understood that an identifier of the second terminal included in the first message may be obtained from the first subscription information.

For example, if the first non-public network is a first non-public network of a second release, the first message sent by the second terminal to the access management network element in the first non-public network using the first subscription information carries a second identifier of the second terminal. For example, if the first non-public network is a first non-public network of a first release, the first message sent by the second terminal to the access management network element in the first non-public network using the first subscription information carries a third identifier of the second terminal.

Step 802: The access management network element transmits a second message to the second terminal. In response, the second terminal receives the second message from the access management network element.

The second message is used to reject registration of the second terminal to the non-public network, and the second message includes fourth indication information, and the fourth indication information is used to indicate a cause for rejecting registration of the second terminal to the non-public network.

In conclusion, the embodiment described in FIG. 8 is applicable to scenarios where the release of the non-public network or public network to which the second terminal subscribes is different from the release of the non-public network to which the second terminal registers. The details are as follows: Case 1: When the second terminal requests to register with the first non-public network of the second release using the private network subscription information of the second terminal in the first non-public network of the first release, the access management network element in the first non-public network of the second release rejects the registration of the second terminal to the first non-public network of the second release. Case 2: When the second terminal requests to register with the first non-public network of the first release using the public network subscription information of the second terminal in the first public network of the second release, the access management network element in the first non-public network of the first release rejects the registration of the second terminal to the first non-public network of the first release.

The first subscription information may be subscription information of a second terminal in the first non-public network or may be subscription information of a second terminal in the first public network. However, in the different cases, different processing actions are taken by the second terminal after receiving the second message. These actions are described separately below.

Example 1: The first subscription information is subscription information of a second terminal in a first non-public network. In other words, the first subscription information is subscription information of a second terminal in a first non-public network of a first release, where the first non-public network to which the second terminal is attempting to register is a first non-public network of a second release, and the first public network is a first public network of a second release.

This embodiment of the present application provides a network access method. In this method, the second terminal sends a first message to an access management network element in a first non-public network using first subscription information, where the first subscription information is subscription information of the second terminal in the first non-public network, or the first subscription information is subscription information of the second terminal in the first public network. The second terminal then receives a second message from the access management network element, which helps the second terminal subsequently determine based on the second message that the access management network element in the first non-public network has rejected the registration of the second terminal to the non-public network, and based on the fourth indication information, determine the cause of the rejection of the registration of the second terminal to the non-public network by the access management network element. This solution can solve a problem that arises when a second terminal registers to a first non-public network using subscription information of the second terminal in the first non-public network, or can solve a problem that arises when a second terminal registers to a first non-public network using subscription information of the second terminal in the first public network.

Figure 9 illustrates another network access method according to an embodiment of the present application. The method includes the following steps:

Step 901 is the same as step 801. Details will not be repeated here.

Step 902: The access management network element determines to deny registration of the second terminal to the first non-public network.

Specifically, step 902 may be implemented as follows: the access management network element determines to deny registration of the second terminal to the first non-public network based on configuration information or subscription information of the second terminal in the first non-public network.

For example, if the configuration information indicates that the first non-public network does not support interworking with the first public network in N3IWF mode, the access management network element decides to deny registration of the second terminal to the first non-public network.

For example, if the subscription information of the second terminal in the first non-public network indicates that the second terminal can no longer access the first non-public network using the subscription information, the access management network element determines to deny registration of the second terminal to the first non-public network.

Step 903 is the same as step 802. Details will not be repeated here.

In a possible embodiment, as shown in FIG. 9, the method provided in this embodiment of the present application may further include step 904 after step 903, or the method provided in this embodiment of the present application may further include step 905 and step 906 after step 904.

Step 904: The access management network element transmits a fourth message to the second terminal. In response, the second terminal receives a fourth message from the access management network element. The fourth message includes a candidate network list for the second terminal. The candidate network list includes information about the first non-public network.

In this embodiment of the present application, when the candidate network list includes information about the first non-public network, it indicates that the second terminal may register with the first public network. The fact that the candidate network list includes information about the first non-public network may also be rephrased as the record item corresponding to the first public network included in the candidate network list being active.

It should be understood that the candidate network list of the second terminal includes one or more candidate non-public networks that the second terminal can choose to access. The first non-public network belongs to the one or more candidate non-public networks.

It may be appreciated that in step 904, the second terminal may determine that registration of the second terminal to the first non-public network using the subscription information of the second terminal in the first non-public network of the first release is denied, but the second terminal may register to the first non-public network.

Step 905: The access management network element sends a fifth message to the second terminal. In response, the second terminal receives a fifth message from the access management network element. The fifth message is used to indicate that the registration of the second terminal to the first non-public network is accepted.

For example, the fifth message includes an acceptance indication, which is used to indicate that registration of the second terminal to the first non-public network is accepted.

Step 906: The second terminal adds information about the first non-public network to the candidate network list of the second terminal based on the fifth message.

In an alternative implementation, step 906 of this embodiment of the present application may also be stated as follows: the second terminal updates its prohibited network list based on the fifth message. The updated prohibited network list includes information about the first non-public network.

For details on how the second terminal updates its prohibited network list, please refer to the above-mentioned process in which the first terminal updates its prohibited network list. Details will not be repeated here.

It can be seen that in steps 905 and 906, the second terminal can determine that registration of the second terminal to the first non-public network using the subscription information of the second terminal in the first non-public network of the first release is denied, but the second terminal can register to the first non-public network.

In a possible embodiment, as shown in FIG. 9, when the second terminal determines that the second terminal can register with the first non-public network, the method provided in this embodiment of the present application may further include the following steps:

Step 907: The second terminal registers with the first non-public network based on the fourth indication information using second subscription information of the second terminal, where the second subscription information is subscription information of the second terminal in the first public network.

The second subscription information includes an identifier of the first public network, and the second subscription information includes a fifth identifier of the second terminal, the fifth identifier related to the identifier of the first public network.

It may be understood that when the first subscription information is subscription information of a second terminal in a first non-public network, the fourth indication information may be further used to instruct the second terminal to register in the first non-public network using a roaming architecture. In other words, the fourth indication information may be further used to instruct the second terminal to register in the first non-public network using the second subscription information of the second terminal. This is not limited in this embodiment of the present application.

This embodiment of the present application provides a network access method. In this method, the second terminal sends a first message to an access management network element in a first non-public network using first subscription information, where the first subscription information is subscription information of the second terminal in the first non-public network. The second terminal then receives a second message from the access management network element, which helps the second terminal subsequently determine based on the second message that the access management network element in the first non-public network rejects the registration of the second terminal to the non-public network, and based on the fourth indication information, determine the cause of the rejection of the registration of the second terminal to the non-public network by the access management network element. Then, if the second terminal still needs to register to the first non-public network, the second terminal may register to the first non-public network using the second subscription information of the second terminal based on the cause. In this solution, after a registration to the first non-public network using subscription information of a second terminal in the first non-public network is rejected, the second terminal can register to the first non-public network using second subscription information.

Example 2: The first subscription information is subscription information of a second terminal in a first public network. In other words, the first subscription information is subscription information of a second terminal in a first public network of a second release. However, the first non-public network to which the second terminal attempts to register is the first non-public network of the first release. The first public network that interworks with the first non-public network of the first release is the first public network of the first release.

In this case, the fourth indication information is used to indicate that the second terminal is an unauthorized terminal. In other words, the fourth indication information is used to indicate that the non-public network cannot identify the identity of the second terminal.

Figure 10 illustrates another network access method according to an embodiment of the present application. The method includes the following steps:

Step 1001 is the same as step 801. Details will not be repeated here.

Step 1002: The access management network element decides to deny registration of the second terminal to the first non-public network.

Specifically, step 1002 may be implemented as follows: if the access management network element is unable to obtain subscription information of the second terminal or is unable to identify the identity of the second terminal, i.e., authentication of the second terminal fails, the access management network element decides to reject registration of the second terminal to the first non-public network.

Step 1003 is the same as step 802. Details will not be repeated here.

It should be appreciated that the second message is further used to instruct the second terminal to request registration with the first non-public network using the third subscription information.

In a possible embodiment, when the second terminal further has third subscription information of the second terminal in the first non-public network, as shown in FIG. 10, after step 1003, the method provided in this embodiment of the present application may further include the following steps:

Step 1004: The second terminal requests to register with the first non-public network using the third subscription information.

It should be understood that the third subscription information is subscription information between the second terminal and the first non-public network of the first release. The third subscription information includes a fourth identifier of the second terminal, and the fourth identifier relates to the first non-public network. For example, the fourth identifier includes information about the first non-public network. For example, the information about the first non-public network is an identifier of the first non-public network. For the contents of the identifier of the first non-public network, please refer to the description in other parts of the embodiment of this application. Details will not be repeated in this specification.

In a possible implementation, step 1004 of this embodiment of the present application may be implemented as follows: the second terminal sends a registration request message to an access management network element in a first release non-public network, where the registration request message is used to request the second terminal to register in the first release non-public network. The registration request message includes a fourth identifier of the second terminal. The fourth identifier of the second terminal is determined based on the third subscription information. In other words, the fourth identifier of the second terminal includes information about the first non-public network.

In a possible implementation, after the second terminal successfully registers with the first non-public network of the first release, the method provided in this embodiment of the present application may further include requesting that the second terminal register with the first public network of the first release using subscription information of the second terminal in the first public network.

It may be appreciated that the second message of step 1003 of example 2 may further include indication information used to instruct the second terminal to request registration with the first non-public network using the third subscription information.

This embodiment of the present application provides a network access method. In this method, the second terminal sends a first message to an access management network element in a first non-public network using first subscription information, where the first subscription information is subscription information of the second terminal in the first public network. The second terminal then receives a second message from the access management network element, which helps the second terminal subsequently determine based on the second message that the access management network element in the first non-public network rejects the registration of the second terminal to the non-public network, and based on the fourth indication information, determine that the cause of the rejection of the registration of the second terminal to the non-public network by the access management network element is that the second terminal is an unauthorized terminal. Then, if the second terminal still needs to register to the first non-public network, the second terminal may register to the first non-public network using the third subscription information of the second terminal based on this cause. In this solution, after a registration to the first non-public network using subscription information of a second terminal in the first non-public network is rejected, the second terminal can register to the first non-public network using third subscription information.

With reference to the architecture shown in FIG. 5b, as shown in FIG. 11, an example is used in which the first terminal is a non-SNPN device, the first non-public network is an SNPN of R17 release (hereinafter abbreviated as R17 SNPN, corresponding to the non-public network 100 of FIG. 5b), the access management network element is an SNPN AMF network element in the R17 SNPN (corresponding to the AMF network element 1 of FIG. 5b), the access network device is an SNPN RAN, the public network is a PLMN of R17 release (hereinafter abbreviated as R17 PLMN, corresponding to the public network 200 of FIG. 5b), and the integrated data management network element is the UDM network element of FIG. 5b, and the method includes the following steps.

Step 1101: The non-SNPN device sends a registration request message to the SNPN AMF network element. In response, the SNPN AMF network element receives a registration request message from the non-SNPN device. The registration request message is used to request the non-SNPN device to register with the R17 SNPN.

For example, the registration request message carries an identifier of the non-SNPN device. For example, the identifier of the non-SNPN device may be a SUPI or a SUCI.

In a particular implementation, step 1101 may be implemented as follows: the non-SNPN device sends a registration request message to the SNPN AMF network element through the SNPN RAN in the R17 SNPN. In addition, the SNPN AMF network element may further receive an identifier of the R17 SNPN from the SNPN RAN, and the identifier of the R17 SNPN is used to identify the R17 SNPN. The SUPI or SUCI of the non-SNPN device includes the HPLMN ID of the non-SNPN device. The HPLMN ID is used to determine the home public network corresponding to the non-SNPN device.

Step 1102: If roaming interworking is not supported between the R17 SNPN and the R17 PLMN, the SNPN AMF network element sends a registration reject message 1 to the non-SNPN device. In response, the non-SNPN device receives a registration reject message 1 from the SNPN AMF network element.

The Registration Rejection Message 1 is used to indicate that registration of a non-SNPN device to the R17 SNPN is rejected, and the Registration Rejection Message 1 may further carry the cause of rejecting registration of the non-SNPN device to the R17 SNPN, where the cause is that the non-SNPN device is an illegal UE.

Step 1103: If roaming interworking is supported between the R17 SNPN and the R17 PLMN, the SNPN AMF network element sends a subscription acquisition request message to the UDM network element in the R17 PLMN. In response, the UDM network element receives a subscription acquisition request message from the SNPN AMF network element. The subscription acquisition request message is used to request subscription data for a non-SNPN device.

For example, the subscription acquisition request message carries an identifier of the R17 SNPN and an identifier of the non-SNPN device. The identifier of the R17 SNPN is carried in the subscription acquisition request message, which helps the UDM network element determine the non-public network accessed by the non-SNPN device.

As shown in FIG. 11, step 1103 may be implemented as follows: the SNPN AMF network element sends a subscription acquisition request message to a V-SEPP in an R17 SNPN. The V-SEPP then sends the acquired subscription acquisition request message to an H-SEPP in an R17 PLMN, so that the H-SEPP forwards the subscription acquisition request message to a UDM network element.

Step 1104: The UDM network element sends a subscription acquisition response message to the SNPN AMF network element. In response, the SNPN AMF network element receives a subscription acquisition response message from the UDM network element. The subscription acquisition response message is used by the SNPN AMF network element to decide to reject the registration of the non-SNPN device to the R17 SNPN.

As shown in FIG. 11, step 1104 may be implemented as follows: the UDM network element sends a subscription acquisition response message to the H-SEPP in the R17 PLMN. The H-SEPP then sends the acquired subscription acquisition response message to the V-SEPP in the R17 SNPN, so that the V-SEPP sends the subscription acquisition response message to the SNPN AMF network element in the R17 SNPN.

For example, in one aspect, the subscription acquisition response message carries subscription data of the non-SNPN device, the subscription data including second indication information, the second indication information being used to indicate that the non-SNPN device can only access the public network. Alternatively, the second indication information is used to indicate that the non-SNPN device cannot access the non-public network. For example, the second indication information includes a supported network list of the non-SNPN device. The supported network list of the non-SNPN device does not include information about the R17 SNPN. Alternatively, a record item corresponding to the R17 SNPN in the supported network list of the non-SNPN device is used to indicate that access to the R17 SNPN is prohibited.

In another aspect, the subscription acquisition response message includes third indication information, which is used to indicate that subscription data for the non-SNPN device is not successfully acquired.

In yet another aspect, the join acquisition response message includes a cause value, which is used to indicate that non-SNPN devices are not allowed to access the R17 SNPN.

In yet another aspect, the subscription acquisition response message does not include subscription data for non-SNPN devices.

Step 1105: The SNPN AMF network element determines, based on the subscription acquisition response message, to reject registration of the non-SNPN device to the R17 SNPN.

Step 1106: The SNPN AMF network element sends a registration rejection message 2 to the non-SNPN device. In response, the non-SNPN device receives a registration rejection message 2 from the SNPN AMF network element. The registration rejection message 2 is used to indicate that the registration of the non-SNPN device to the R17 SNPN is rejected. The registration rejection message 2 may further carry the cause of rejecting the registration of the non-SNPN device to the R17 SNPN. For example, the cause of rejecting the registration of the non-SNPN device to the R17 SNPN is that the non-SNPN device is not allowed to access the R17 SNPN.

Step 1107: The non-SNPN device adds information about the R17 SNPN to the non-SNPN device's prohibited network list.

It should be appreciated that step 1107 may alternatively be implemented as follows: the non-SNPN device updates the non-SNPN device's prohibited network list. The updated prohibited network list of the non-SNPN device includes information about the R17 SNPN. The information about the R17 SNPN is used to identify the R17 SNPN. For example, the information about the R17 SNPN may be an identifier of the R17 SNPN.

It should be understood that the prohibited network list includes one or more networks that non-SNPN devices are prohibited from accessing, including the R17 SNPN.

In a possible embodiment, after step 1107, the method provided in this embodiment of the present application may further include the following steps:

Step 1108: The non-SNPN device performs network selection based on the prohibited network list and selects a network other than the networks in the prohibited network list for registration.

In the embodiment shown in FIG. 11, it should be noted that steps 1101 and 1102 may constitute separate embodiments to resolve issues that arise when a non-SNPN device accesses an R17 SNPN when roaming architecture interworking is not supported between the R17 SNPN and the R17 PLMN. Steps 1101 and steps 1103 to 1108 may constitute separate embodiments to resolve issues that arise when a non-SNPN device accesses an R17 SNPN when roaming architecture interworking is supported between the R17 SNPN and the R17 PLMN.

Please note that the registration request message in the embodiment shown in FIG. 11 may correspond to the first message in the embodiment shown in FIG. 6. The join acquisition response message may correspond to the third message in the embodiment shown in FIG. 6. The registration rejection message 2 may correspond to the second message in the embodiment shown in FIG. 6. The join acquisition request message may correspond to the inquiry message in the embodiment shown in FIG. 6. The cause for rejecting the registration of a non-SNPN device to the R17 SNPN may correspond to the first indication information in the embodiment shown in FIG. 6.

Referring to FIG. 5b, FIG. 12 shows a specific embodiment of another network access method according to the present application. In this embodiment, an example is used in which the first non-public network is an R17 SNPN, the access network device is an SNPN RAN, and the second terminal is an SNPN device, and the method includes the following steps:

Step 1201: The SNPN RAN in the R17 SNPN transmits broadcast information. In response, the SNPN device receives broadcast information from the SNPN RAN. The broadcast information includes an interworking indication, which is used to indicate that interworking is supported between the R17 SNPN and the R17 PLMN.

It can be understood that the SNPN device is located within the coverage area of the R17 SNPN and the SNPN device can receive broadcast information from the SNPN RAN.

Step 1202: The SNPN device determines, based on the interworking indication in the broadcast information, to access the R17 SNPN and the R17 PLMN using subscription information between the SNPN device and the R17 PLMN.

In a possible implementation, if the broadcast information further includes identifiers of one or more R17 PLMNs that interwork with the R17 SNPN, step 1202 may be implemented as follows: the SNPN device determines, based on the interworking indication in the broadcast information, to access the R17 SNPN and the target R17 PLMN using target subscription information between the SNPN device and the R17 PLMN. The target R17 PLMN belongs to one or more of the R17 PLMNs.

In a possible implementation, after step 1202, the embodiment shown in FIG. 12 may further include the SNPN device sending a registration request message to the SNPN AMF network element in the R17 SNPN through the SNPN RAN in the R17 SNPN to request to register with the R17 SNPN. The registration request message carries an identifier of the SNPN device described in the target subscription information, and the identifier of the SNPN device described in the target subscription information includes an identifier of the R17 PLMN. When the SNPN AMF network element allows the SNPN device to register with the R17 SNPN, the SNPN AMF network element sends a registration accept message to the SNPN device.

With reference to FIG. 5b, FIG. 13 describes a specific embodiment of a network access method according to an embodiment of the present application using an example in which the second terminal is an SNPN device, the first non-public network is an SNPN of R17 release (hereinafter abbreviated as R17 SNPN), the access management network element is an SNPN AMF network element in the R17 SNPN, the access network device is an SNPN RAN, the first public network is a PLMN of R17 release (hereinafter abbreviated as R17 PLMN), and the unified data management network element is a UDM network element. The method includes the following steps:

Step 1301: The SNPN device sends a registration request message to the SNPN AMF network element using subscription information 1. In response, the SNPN AMF network element receives a registration request message from the SNPN device. The registration request message includes the identifier 1 of the SNPN device.

It should be understood that the SNPN device shown in FIG. 13 and FIG. 14 may be an R16 SNPN device. An R16 SNPN device means that the SNPN device has private network subscription information between the SNPN device and an SNPN with an R16 release, and also has public network subscription information between the SNPN device and an SNPN with an R16 release. Subscription information 1 may be private network subscription information between the SNPN device and an SNPN with an R16 release in the SNPN device. The private network subscription information between the SNPN device and an SNPN with an R16 release includes an identifier 1 of the SNPN device. The identifier 1 of the SNPN device includes an identifier of the SNPN with an R16 release.

The reasons for the SNPN AMF network element's refusal to register an SNPN device to an R17 SNPN are different when the SNPN AMF network element is obtained by upgrading an AMF network element in an SNPN with an R16 release and when the SNPN AMF network element is directly deployed. Therefore, the following provides an explanation of Cases 1 to 3.

Case 1: SNPN AMF network elements are directly deployed.

Step 1302: The SNPN AMF network element determines that the SNPN device has failed security authentication.

Specifically, if the SNPN AMF network element is directly deployed in the R17 SNPN, rather than being obtained by upgrading an AMF network element in the R16 SNPN, the SNPN AMF network element cannot parse the SNPN device identifier 1. Thus, the SNPN AMF network element determines that the SNPN device has failed security authentication.

Step 1303: The SNPN AMF network element sends a registration rejection message 11 to the SNPN device. In response, the SNPN device receives a registration rejection message 11 from the SNPN AMF network element. The registration rejection message 11 is used to indicate that the registration of the SNPN device to the R17 SNPN is rejected. The registration rejection message 11 may further carry the cause of rejecting the registration of the SNPN device to the R17 SNPN, where the cause is that the SNPN device is an unauthorized terminal, in other words, the SNPN cannot identify the identity of the SNPN device.

Case 2: The SNPN AMF network element is acquired by upgrading the AMF network element in the R16 SNPN, and the operator's policy does not support the N3IWF mode. In other words, the R17 SNPN and the R17 PLMN do not support N3IWF mode interworking, but the R17 SNPN and the R17 PLMN support roaming mode interworking.

Step 1304: The SNPN AMF network element determines, based on the subscription information 1 of the SNPN device and the operator's policy, that the SNPN device registers in roaming mode to the R17 SNPN.

Step 1305: The SNPN AMF network element sends a registration rejection message 12 to the SNPN device. In response, the SNPN device receives a registration rejection message 12 from the SNPN AMF network element. The registration rejection message 12 is used to indicate that the registration of the SNPN device to the R17 SNPN is rejected. The registration rejection message 12 may further carry a cause for rejecting the registration of the SNPN device to the R17 SNPN, where the cause is that private network subscription information between the SNPN device and the R16 release SNPN is unavailable.

In a possible implementation, the registration rejection message 12 may further carry indication information y used to instruct the SNPN device to register with the R17 SNPN using the roaming architecture, and the indication information y is used to help the SNPN device decide to register with the R17 SNPN using the public network subscription information.

Step 1306: The SNPN device registers with the R17 SNPN using public network subscription information based on the cause for rejecting registration of the SNPN device with the R17 SNPN.

After step 1306, the method may further include the SNPN AMF network element sending a candidate network list to the SNPN device, where it can be understood that the candidate network list includes information about the R17 SNPN. Alternatively, after step 1306, the method may further include the SNPN AMF network element sending a fourth message to the SNPN device, where the fourth message is used to instruct the SNPN device to add the R17 SNPN to the candidate network list. The SNPN device adds information about the R17 SNPN to the candidate network list based on the fourth message.

Case 3: The SNPN AMF network element is acquired by upgrading the AMF network element in the R16 SNPN, and the operator's policy still supports the N3IWF mode. In other words, the R17 SNPN and the R17 PLMN support interworking in the N3IWF mode.

Step 1307: The SNPN AMF network element determines, based on the subscription information 1 of the SNPN device and the operator's policy, that the SNPN device can register with the R17 SNPN in N3IWF mode.

Step 1308: The SNPN AMF network element sends a registration accept message to the SNPN device. In response, the SNPN device receives a registration accept message from the SNPN AMF network element. The registration accept message indicates that the SNPN device is allowed to register with the R17 SNPN.

With reference to FIG. 5b, FIG. 14 describes a specific embodiment of a network access method according to an embodiment of the present application using an example in which the second terminal is an SNPN device, the first non-public network is an SNPN of R17 release (hereinafter abbreviated as R17 SNPN), the access management network element is an SNPN AMF network element in the R17 SNPN, the access network device is an SNPN RAN, the first public network is a PLMN of R17 release (hereinafter abbreviated as R17 PLMN), and the unified data management network element is a UDM network element. The method includes the following steps:

Step 1401: The SNPN device sends a registration request message to the SNPN AMF network element using subscription information 2. In response, the SNPN AMF network element receives a registration request message from the SNPN device. The registration request message includes the identifier 2 of the SNPN device.

Furthermore, the SNPN AMF network element may further obtain an identifier of the R17 SNPN from the SNPN RAN. The identifier 2 of the SNPN device includes an identifier of the HPLMN corresponding to the SNPN device.

Subscription information 2 is the public network subscription information between the SNPN device and the PLMN of the R16 release.

Step 1402: If the R17 SNPN does not support interworking with the HPLMN corresponding to the SNPN device, the SNPN AMF network element determines that the SNPN device has failed security authentication.

Step 1403: The SNPN AMF network element sends a registration rejection message 21 to the SNPN device. In response, the SNPN device receives a registration rejection message 21 from the SNPN AMF network element. The registration rejection message 21 is used to indicate that the registration of the SNPN device to the R17 SNPN is rejected. The registration rejection message 21 may further carry the cause of rejecting the registration of the SNPN device to the R17 SNPN, where the cause is that the SNPN device is an unauthorized terminal.

Step 1404: If the R17 SNPN supports interworking with the HPLMN corresponding to the SNPN device, the SNPN AMF network element sends a registration accept message to the SNPN device. In response, the SNPN device receives a registration accept message from the SNPN AMF network element. The registration accept message indicates that the SNPN device is allowed to register with the R17 SNPN.

In a possible implementation, if the R17 SNPN supports interworking with the HPLMN corresponding to the SNPN device, the SNPN AMF network element may further send configuration information to the SNPN device, where the configuration information is used by the SNPN device to determine a candidate network list for the SNPN device. The candidate network list includes information about the R17 SNPN.

The subscription information 2 in the embodiment described in FIG. 14 corresponds to the first subscription information in the aforementioned embodiment, where the first subscription information is subscription information of a second terminal in a first non-public network. The registration request message corresponds to the aforementioned first message. The registration rejection message corresponds to the second message in the embodiment described in FIG. 9.

With reference to FIG. 5a, as shown in FIG. 15, an example is used in which the first terminal is a non-SNPN device, the first non-public network is an SNPN of R16 release (hereinafter abbreviated as R16 SNPN, corresponding to the non-public network 100 of FIG. 5a), the access management network element is an SNPN AMF network element in the R16 SNPN (corresponding to the AMF network element of FIG. 5a), the access network device is an SNPN RAN, the first public network is a PLMN of R16 release (hereinafter abbreviated as R16 PLMN, corresponding to the public network 200 of FIG. 5a), and the integrated data management network element is a UDM network element of FIG. 5b, and the method includes the following steps.

Step 1501: The non-SNPN device sends a registration request message to the SNPN AMF network element. In response, the SNPN AMF network element receives a registration request message from the non-SNPN device. The registration request message is used to request the non-SNPN device to register with the R16 SNPN.

For example, the registration request message carries an identifier of the non-SNPN device. For example, the identifier of the non-SNPN device may be a SUPI or a SUCI.

In a particular implementation, step 1501 may be implemented as follows: the non-SNPN device sends a registration request message to the SNPN AMF network element through the SNPN RAN in the R16 SNPN. In addition, the SNPN AMF network element may further receive an identifier of the R16 SNPN from the SNPN RAN, and the identifier of the R16 SNPN is used to identify the R16 SNPN. The SUPI or SUCI of the non-SNPN device includes the HPLMN ID of the non-SNPN device. The HPLMN ID is used to determine the home public network corresponding to the non-SNPN device.

Step 1502: If roaming interworking is not supported between the R16 SNPN and the R16 PLMN, the SNPN AMF network element determines that the non-SNPN device has failed security authentication.

Step 1503: The SNPN AMF network element sends a registration rejection message 1 to the non-SNPN device. In response, the non-SNPN device receives a registration rejection message 1 from the SNPN AMF network element. The registration rejection message 1 indicates that registration of the non-SNPN device to the R16 SNPN is rejected.

The registration rejection message 1 may further carry the reason for rejecting the registration of the non-SNPN device to the R16 SNPN, where the reason is that the non-SNPN device is an unauthorized terminal.

Referring to FIG. 5a, as shown in FIG. 16, an example is used in which the second terminal is an SNPN device, the non-public network of the SNPN device is an SNPN of R16 release (hereinafter abbreviated as R16 SNPN), the access management network element is an SNPN AMF network element in the R16 SNPN, the access network device is an SNPN RAN, the public network of the SNPN device is a PLMN of R16 release (hereinafter abbreviated as R16 PLMN), and the integrated data management network element is a UDM network element, and the method includes the following steps:

Step 1601: The SNPN device sends a registration request message to the SNPN AMF network element using subscription information 3. In response, the SNPN AMF network element receives a registration request message from the SNPN device. The registration request message includes the identifier 3 of the SNPN device.

It should be understood that the SNPN device shown in Figures 16 and 17 may be an R17 SNPN device. By R17 SNPN device, it is meant that the SNPN device has subscription information between the SNPN device and a PLMN with an R17 release, i.e. subscription information 3.

The SNPN device identifier 3 in step 1601 includes the HPLMN ID corresponding to the SNPN device.

Step 1602: If roaming interworking is not supported between the R16 SNPN and the R16 PLMN, the SNPN AMF network element cannot parse the SNPN device identifier 3 and determines that the SNPN device has failed security authentication.

Step 1603: The SNPN AMF network element sends a registration rejection message 11 to the SNPN device. In response, the SNPN device receives a registration rejection message 11 from the SNPN AMF network element. The registration rejection message 11 is used to indicate that the registration of the SNPN device to the R17 SNPN is rejected. The registration rejection message 11 may further carry a cause for rejecting the registration of the SNPN device to the R17 SNPN, where the cause is that the SNPN device is an unauthorized terminal.

Step 1604: If the SNPN device further has subscription information 4, upon detecting an available SNPN, the SNPN device may further initiate a registration request message to the SNPN AMF network element using subscription information 4.

In one example, subscription information 4 is subscription information between an SNPN device and an R16 SNPN. In another example, subscription information 4 is subscription information between an SNPN device and an R17 SNPN.

The subscription information 4 includes the SNPN device identifier 4, which is related to the identifier of the SNPN device. For example, the SNPN device identifier 4 includes the identifier of the SNPN. Specifically, the registration request message of step 1604 carries the SNPN device identifier 4.

Step 1605: The SNPN device accesses the R16 SNPN and R16 PLMN in N3IWF mode.

For the specific implementation of step 1605, please refer to the description in the current technology. Details will not be described in this specification.

In this embodiment of the present application, if the SNPN device has both private network affiliation information between the SNPN device and the R16 SNPN and public network affiliation information between the SNPN device and the R16 PLMN, the SNPN device may access the R16 SNPN and the R16 PLMN in N3IWF mode.

The SNPN device may access the R16 SNPN and the R16 PLMN in N3IWF mode, which means that the SNPN device may request to register with the R16 SNPN using private network subscription information. Once the SNPN device successfully registers with the R16 SNPN, the SNPN device may request to register with the R16 PLMN using public network subscription information between the SNPN device and the R16 PLMN.

For example, the subscription information 4 in the embodiment described in FIG. 16 may be the third subscription information of the second terminal in the first non-public network. The subscription information 3 may be the first subscription information in the aforementioned embodiment, where the first subscription information is the subscription information of the second terminal in the first public network. The registration request message may be the aforementioned first message. The registration rejection message 11 corresponds to the second message in the embodiment described in FIG. 10.

The above mainly describes the solutions in the embodiments of the present application from the viewpoint of the interaction between network elements. It can be understood that, to implement the aforementioned functions, each network element, such as the first terminal, the second terminal, the access management network element, the integrated data management network element, or the access network device, includes a corresponding structure and/or software module for performing each function. Those skilled in the art will easily realize that the present application can be implemented by hardware or a combination of hardware and computer software in combination with the units and algorithm steps in the examples described in the embodiments disclosed herein. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use various methods to implement the described functions for each specific application, and such implementation shall not be considered outside the scope of the present application.

In the embodiment of the present application, the first terminal, the second terminal, the access management network element, the integrated data management network element, and the access network device may be divided into functional units based on the above-mentioned method examples. For example, each functional unit may be obtained by division based on the corresponding function, or two or more functions may be integrated into one processing unit. The integrated unit may be implemented in the form of hardware or in the form of a software functional unit. Please note that in the embodiment of the present application, the division into units is an example, and is merely a logical division of functions, and may be other divisions during actual implementation.

Above, the method in the embodiment of the present application has been described with reference to Figures 6 to 16. In the following, a communication device for performing the aforementioned method provided in the embodiment of the present application will be described. Those skilled in the art may understand that the method and the device may be combined and referenced with each other. The communication device provided in the embodiment of the present application may perform the steps performed by the first terminal, the second terminal, the access management network element, the integrated data management network element, and the access network device in the aforementioned method.

When an integrated unit is used, FIG. 17 shows a communication device in the above embodiment. The communication device may include a communication module 113 and a processing module 112.

In an optional implementation, the communication device may further include a storage module 111 configured to store program code and data of the communication device.

In one example, the communication device is a first terminal or a chip used within the first terminal. In this case, the communication module 113 is configured to support the communication device to communicate with an external network element (e.g., an access management network element). For example, the communication module 113 is configured to perform signal reception and transmission operations of the first terminal in the aforementioned method embodiment. The processing module 112 is configured to perform signal processing operations of the first terminal in the aforementioned method embodiment.

For example, the communication module 113 is configured to perform the sending action performed by the first terminal in step 601 of FIG. 6 in the embodiment described above. The communication module 113 is configured to perform the receiving action performed by the first terminal in step 604 of FIG. 6 in the embodiment described above. The processing module 112 is configured to support the communication device in performing the action performed by the first terminal in step 605 of FIG. 6.

In another example, the communication device is an access management network element or a chip used within the access management network element. In this case, the communication module 113 is configured to support the communication device to communicate with an external network element (e.g., a first terminal or an integrated data management network element). For example, the communication module 113 is configured to perform the signal receiving and transmitting operations of the access management network element in the aforementioned method embodiment. The processing module 112 is configured to perform the signal processing operations of the access management network element in the aforementioned method embodiment.

For example, the communication module 113 is configured to perform the receive actions performed by the access management network element in steps 601 and 603 of FIG. 6 in the above embodiment. The communication module 113 is configured to perform the transmit actions performed by the access management network element in steps 602 and 604 of FIG. 6 in the above embodiment.

In yet another example, the communication device is an integrated data management network element or a chip used within the integrated data management network element. In this case, the communication module 113 is configured to support the communication device to communicate with an external network element (e.g., an access management network element). For example, the communication module 113 is configured to perform the signal receiving and transmitting operations of the integrated data management network element in the above-mentioned method embodiment. The processing module 112 is configured to perform the signal processing operations of the integrated data management network element in the above-mentioned method embodiment.

For example, the communication module 113 is configured to perform the receive action performed by the integrated data management network element in step 602 of FIG. 6 in the embodiment described above. The communication module 113 is configured to perform the transmit action performed by the integrated data management network element in step 603 of FIG. 6 in the embodiment described above.

In one example, the communication device is a second terminal or a chip used within the second terminal. In this case, the communication module 113 is configured to support the communication device to communicate with an external network element (e.g., an access network device). For example, the communication module 113 is configured to perform signal reception and transmission operations of the second terminal in the above-mentioned method embodiment. The processing module 112 is configured to perform signal processing operations of the second terminal in the above-mentioned method embodiment.

For example, the communication module 113 is configured to perform the receiving action performed by the second terminal in step 701 of FIG. 7 in the above embodiment. The processing module 112 is configured to support the communication device in performing the action performed by the second terminal in step 702 of FIG. 7 in the above embodiment.

In one example, the communication device is a second terminal or a chip used within the second terminal. In this case, the communication module 113 is configured to support the communication device to communicate with an external network element (e.g., an access management network element). For example, the communication module 113 is configured to perform signal reception and transmission operations of the second terminal in the aforementioned method embodiments. The processing module 112 is configured to perform signal processing operations of the second terminal in the aforementioned method embodiments.

For example, the communication module 113 is configured to perform the sending action performed by the second terminal in step 801 of FIG. 8 in the embodiment described above. The communication module 113 is configured to perform the receiving action performed by the second terminal in step 802 of FIG. 8 in the embodiment described above.

In a possible embodiment, the communication module 113 is configured to perform the receiving actions performed by the second terminal in steps 904 and 905 of FIG. 9 in the previous embodiment. The processing module 112 is configured to support the communication device in performing the actions performed by the second terminal in steps 906 and 907 of FIG. 9.

In another possible embodiment, the processing module 112 is configured to support the communication device in performing the actions performed by the second terminal in step 1004 of FIG. 10.

In one example, the communication device is an access management network element or a chip used within the access management network element. In this case, the communication module 113 is configured to support the communication device to communicate with an external network element (e.g., a second terminal). For example, the communication module 113 is configured to perform the signal receiving and transmitting operations of the access management network element in the aforementioned method embodiment. The processing module 112 is configured to perform the signal processing operations of the access management network element in the aforementioned method embodiment.

For example, the communication module 113 is configured to perform the receive action performed by the access management network element in step 801 of FIG. 8 in the embodiment described above. The communication module 113 is configured to perform the transmit action performed by the access management network element in step 802 of FIG. 8 in the embodiment described above.

In a possible embodiment, the processing module 112 is configured to support the communication device in performing the action performed by the access management network element in step 902 of FIG. 9. The communication module 113 is configured to perform the transmission action performed by the access management network element in step 904 or step 905 of FIG. 9 in the above embodiment.

In another possible embodiment, the processing module 112 is configured to support the communication device in performing the actions performed by the access management network element in step 1002 of FIG. 10.

It should be noted that the communication module 113 shown in FIG. 17 may alternatively be replaced by a communication unit, and the processing module 112 may alternatively be replaced by a processing unit. Alternatively, the storage module 111 may alternatively be replaced by a storage unit. The processing unit is configured to control and manage the actions of the communication device. For example, the processing unit is configured to perform information/data processing steps performed by the communication device. The communication unit is configured to support the communication device in performing information/data transmission or reception steps.

In a possible implementation, the communication unit may include a receiving unit and a transmitting unit. The receiving unit is configured to receive a signal, and the transmitting unit is configured to transmit a signal.

The processing module 112 may be a processor or controller, such as a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processing module 112 may implement or perform various exemplary logic blocks, modules, and circuits described with reference to the disclosed subject matter of this application. Alternatively, the processor may be a combination of processors that perform computational functions, such as a combination of one or more microprocessors, or a combination of a digital signal processor and a microprocessor. The communication module may be a transceiver, a transceiver circuit, or a communication interface, etc. The storage module may be a memory.

When the processing module 112 is a processor 1801 or a processor 1805, the communication module 113 is a communication interface 1803, and the storage module 111 is a memory 1802, the communication apparatus of the present application may be the communication device shown in FIG. 18.

Figure 18 is a schematic diagram of the hardware structure of a communication device according to an embodiment of the present application. For the structures of the first terminal, the second terminal, the access management network element, the integrated data management network element, and the access network device of the embodiment of the present application, please refer to the schematic diagram of the structure of the communication device shown in Figure 18. The communication device includes a processor 1801, a communication line 1804, and at least one communication interface (communication interface 1803 is used as an example for explanation in Figure 18).

The processor 1801 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to control program execution of the solutions of this application.

Communication lines 1804 may include paths for transmitting information between the aforementioned components.

The communication interface 1803 is configured to exchange information with another device. For example, the communication interface 1803 is any device, such as a transceiver, configured to communicate with another device or communication network, such as, for example, an Ethernet, a radio access network (RAN), or a wireless local area network (WLAN).

Optionally, the communication device may further include memory 1802.

Memory 1802 may be a read-only memory (ROM) or another type of static storage device capable of storing static information and instructions, or a random access memory (RAM) or another type of dynamic storage device capable of storing information and instructions, or may be an electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CDROM), or a programmable logic device (PLC) capable of storing information and instructions. The memory 1802 may be a hard disk drive (HDD), a memory, a CD-ROM (CD-ROM) or other compact disk storage, an optical disk storage (such as a compact disk, a laser disk, an optical disk, a digital versatile disk, and a Blu-ray (registered trademark) disk), a magnetic disk storage medium or another magnetic storage device, or any other medium that can be used to carry or store the expected program code in the form of instructions or data structures that can be accessed by a computer. However, the memory 1802 is not limited to these. The memory may exist independently and be connected to the processor through a communication line 1804. Alternatively, the memory may be integrated into the processor.

The memory 1802 is configured to store computer-executable instructions for carrying out the solution of the present application, and the processor 1801 controls the execution. The processor 1801 is configured to execute the computer-executable instructions stored in the memory 1802 to implement the network access method provided in the above embodiment of the present application.

Optionally, the computer executable instructions of the embodiments of the present application may be referred to as application program code, although this is not a limitation of the embodiments of the present application.

During a particular implementation, in an embodiment, the processor 1801 may include one or more CPUs, such as, for example, CPU0 and CPU1 of FIG. 18.

During a particular implementation, in an embodiment, a communications device may include multiple processors, such as, for example, processor 1801 and processor 1805 of FIG. 18. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may be one or more devices, circuits, and/or processing cores configured to process data (e.g., computer program instructions).

In one example, the communication device is a first terminal or a chip used within the first terminal. In this case, the communication module 113 is configured to support the communication device to communicate with an external network element (e.g., an access management network element). For example, the communication module 113 is configured to perform signal reception and transmission operations of the first terminal in the aforementioned method embodiment. The processing module 112 is configured to perform signal processing operations of the first terminal in the aforementioned method embodiment.

For example, the communication module 113 is configured to perform the sending action performed by the first terminal in step 601 of FIG. 6 in the embodiment described above. The communication module 113 is configured to perform the receiving action performed by the first terminal in step 604 of FIG. 6 in the embodiment described above. The processing module 112 is configured to support the communication device in performing the action performed by the first terminal in step 605 of FIG. 6.

In another example, the communication device is an access management network element or a chip used within the access management network element. In this case, the communication module 113 is configured to support the communication device to communicate with an external network element (e.g., a first terminal or an integrated data management network element). For example, the communication module 113 is configured to perform the signal receiving and transmitting operations of the access management network element in the aforementioned method embodiment. The processing module 112 is configured to perform the signal processing operations of the access management network element in the aforementioned method embodiment.

For example, the communication module 113 is configured to perform the receive actions performed by the access management network element in steps 601 and 603 of FIG. 6 in the above embodiment. The communication module 113 is configured to perform the transmit actions performed by the access management network element in steps 602 and 604 of FIG. 6 in the above embodiment.

In yet another example, the communication device is an integrated data management network element or a chip used within the integrated data management network element. In this case, the communication module 113 is configured to support the communication device to communicate with an external network element (e.g., an access management network element). For example, the communication module 113 is configured to perform the signal receiving and transmitting operations of the integrated data management network element in the above-mentioned method embodiment. The processing module 112 is configured to perform the signal processing operations of the integrated data management network element in the above-mentioned method embodiment.

For example, the communication module 113 is configured to perform the receive action performed by the integrated data management network element in step 602 of FIG. 6 in the embodiment described above. The communication module 113 is configured to perform the transmit action performed by the integrated data management network element in step 603 of FIG. 6 in the embodiment described above.

In one example, the communication device is a second terminal or a chip used within the second terminal. In this case, the communication module 113 is configured to support the communication device to communicate with an external network element (e.g., an access network device). For example, the communication module 113 is configured to perform signal reception and transmission operations of the second terminal in the aforementioned method embodiment. The processing module 112 is configured to perform signal processing operations of the second terminal in the aforementioned method embodiment.

For example, the communication module 113 is configured to perform the receiving action performed by the second terminal in step 701 of FIG. 7 in the above embodiment. The processing module 112 is configured to support the communication device in performing the action performed by the second terminal in step 702 of FIG. 7.

In one example, the communication device is a second terminal or a chip used within the second terminal. In this case, the communication module 113 is configured to support the communication device to communicate with an external network element (e.g., an access management network element). For example, the communication module 113 is configured to perform signal reception and transmission operations of the second terminal in the aforementioned method embodiment. The processing module 112 is configured to perform signal processing operations of the second terminal in the aforementioned method embodiment.

For example, the communication module 113 is configured to perform the sending action performed by the second terminal in step 801 of FIG. 8 in the embodiment described above. The communication module 113 is configured to perform the receiving action performed by the second terminal in step 802 of FIG. 8 in the embodiment described above.

In a possible embodiment, the communication module 113 is configured to perform the receiving actions performed by the second terminal in steps 904 and 905 of FIG. 9 in the previous embodiment. The processing module 112 is configured to support the communication device in performing the actions performed by the second terminal in steps 906 and 907 of FIG. 9.

In another possible embodiment, the processing module 112 is configured to support the communication device in performing the actions performed by the second terminal in step 1004 of FIG. 10.

In one example, the communication device is an access management network element or a chip used within the access management network element. In this case, the communication module 113 is configured to support the communication device to communicate with an external network element (e.g., a second terminal). For example, the communication module 113 is configured to perform the signal receiving and transmitting operations of the access management network element in the aforementioned method embodiment. The processing module 112 is configured to perform the signal processing operations of the access management network element in the aforementioned method embodiment.

For example, the communication module 113 is configured to perform the receive action performed by the access management network element in step 801 of FIG. 8 in the embodiment described above. The communication module 113 is configured to perform the transmit action performed by the access management network element in step 802 of FIG. 8 in the embodiment described above.

In a possible embodiment, the processing module 112 is configured to support the communication device in performing the action performed by the access management network element in step 902 of FIG. 9. The communication module 113 is configured to perform the transmission action performed by the access management network element in step 904 or step 905 of FIG. 9 in the above embodiment.

In another possible embodiment, the processing module 112 is configured to support the communication device in performing the actions performed by the access management network element in step 1002 of FIG. 10.

Figure 19 is a schematic diagram of a structure of a chip 190 according to an embodiment of the present application. Chip 190 includes one or more (including two) processors 1910 and a communication interface 1930.

Optionally, chip 190 further includes memory 1940. Memory 1940 may include read-only memory and random access memory and may provide operating instructions and data to processor 1910. A portion of memory 1940 may further include non-volatile random access memory (NVRAM).

In some implementations, memory 1940 stores the following elements: executable modules or data structures, a subset thereof, or an extended set thereof:

In this embodiment of the present application, the corresponding operations are performed by invoking operation instructions stored in memory 1940 (which may also be stored in the operating system).

In a possible implementation, the structures of the chips used within the first terminal, the second terminal, the access management network element, the integrated data management network element, and the access network device may be similar, and different devices may use different chips to implement their respective functions.

The processor 1910 controls the processing operations of any one of the first terminal, the second terminal, the access management network element, the integrated data management network element, and the access network device, and the processor 1910 may also be referred to as a central processing unit (CPU).

The memory 1940 may include read-only memory and random access memory and may provide instructions and data to the processor 1910. The above-mentioned portions of the memory 1940 may further include NVRAM. For example, during application, the processor 1910 , the communication interface 1930, and the memory 1940 are coupled to each other by means of a bus system 1920. In addition to a data bus, the bus system 1920 may further include a power bus, a control bus, a status signal bus, and the like. However, for ease of explanation, various buses are illustrated as the bus system 1920 in FIG. 19.

The methods disclosed in the embodiments of the present application may be applied to or performed by the processor 1910. The processor 1910 may be an integrated circuit chip and has signal processing capabilities. In one implementation process, the steps of these methods may be implemented using hardware integrated logic circuits in the processor 1910 or may be implemented using instructions in the form of software. The processor 1910 may be a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA) or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor 1910 may implement or perform the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor, etc. The steps of the method disclosed with reference to the embodiments of the present application may be performed and completed directly by the hardware decoding processor, or may be performed and completed by using a combination of hardware and software modules in the decoding processor. The software modules may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in the memory 1940, and the processor 1910 reads the information in the memory 1940 and completes the steps of the aforementioned method in combination with the processor's hardware.

In a possible implementation, the communication interface 1930 is configured to perform the receiving and transmitting steps of the first terminal, the second terminal, the access management network element, the integrated data management network element, and the access network device in the embodiments shown in Figures 6 to 16. The processor 1910 is configured to perform the processing steps of the first terminal, the second terminal, the access management network element, the integrated data management network element, and the access network device in the embodiments shown in Figures 6 to 16.

The communications module may also be a communications interface of a device and is configured to receive signals from another device. For example, when the device is implemented as a chip, the communications module is a communications interface used by the chip to receive signals from or send signals to another chip or device.

According to one aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when actuated, perform the functions performed by the first terminal in FIG. 6.

According to one aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when actuated, perform the functions performed by the access management network element in FIG. 6.

According to one aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when actuated, perform functions performed by the integrated data management network element in FIG. 6.

According to one aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when actuated, perform the functions performed by the second terminal in FIG. 7.

According to one aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when actuated, perform the functions performed by the access network device in FIG. 7.

According to one aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions. When the instructions are actuated, the computer-readable storage medium may perform the functions of the second terminal in FIGS. 8-10.

According to one aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions that, when actuated, may cause the computer-readable storage medium to perform the functions of the access management network elements in FIGS. 8-10.

According to one aspect, a computer program product is provided that includes instructions. The computer program product includes instructions that, when actuated, perform the functions performed by the first terminal in FIG. 6.

According to another aspect, a computer program product is provided that includes instructions. The computer program product includes instructions that, when actuated, perform the functions performed by the access management network element in FIG. 6.

According to one aspect, a computer program product is provided that includes instructions. The computer program product includes instructions that, when activated, perform functions performed by the integrated data management network element in FIG. 6.

According to yet another aspect, a computer program product is provided that includes instructions. The computer program product includes instructions that, when actuated, perform the functions performed by the second terminal in FIG. 7.

According to yet another aspect, a computer program product is provided that includes instructions. The computer program product includes instructions that, when activated, perform the functions performed by the access network device in FIG. 7.

According to yet another aspect, a computer program product is provided that includes instructions. The computer program product includes instructions that, when activated, perform the functions of the second terminal in FIGS. 8 to 10.

According to yet another aspect, a computer program product is provided that includes instructions. The computer program product includes instructions that, when activated, perform the functions of the access management network elements in Figures 8 to 10.

According to one aspect, a chip is provided for use in a first terminal. The chip includes at least one processor and a communication interface coupled to the at least one processor, the processor configured to operate instructions to perform the functions performed by the first terminal in FIG. 6.

According to another aspect, an embodiment of the present application provides a chip for use in an access management network element. The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor, the processor being configured to operate instructions to perform the functions performed by the access management network element in FIG. 6.

According to one aspect, an embodiment of the present application provides a chip for use in an integrated data management network element. The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor, the processor being configured to operate instructions to perform the functions performed by the integrated data management network element in FIG. 6.

According to one aspect, an embodiment of the present application provides a chip for use in a second terminal. The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor, and the processor is configured to execute instructions to implement the functions of the second terminal in FIG. 7.

According to one aspect, an embodiment of the present application provides a chip for use in an access network device. The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor, and the processor is configured to operate instructions to perform the functions of the access network device in FIG. 7.

According to one aspect, an embodiment of the present application provides a chip for use in a second terminal. The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor, and the processor is configured to execute instructions to implement the functions of the second terminal in FIG. 8 to FIG. 10.

According to one aspect, an embodiment of the present application provides a chip for use in an access management network element. The chip includes at least one processor and a communication interface, the communication interface being coupled to the at least one processor, and the processor is configured to execute instructions to perform the functions of the access management network element in FIG. 8 to FIG. 10.

An embodiment of the present application provides a communication system. The communication system includes an access management network element and an integrated data management network element. The access management network element is configured to perform the functions performed by the access management network element in FIG. 6, and the integrated data management network element is configured to perform the functions performed by the integrated data management network element in FIG. 6.

In a possible embodiment, the communication system may further include a terminal, which is configured to perform the functions performed by the first terminal in FIG. 6.

An embodiment of the present application provides a communication system. The communication system includes an access network device and a terminal. The terminal is configured to perform the functions performed by the second terminal in FIG. 7, and the access network device is configured to perform the functions performed by the access network device in FIG. 7.

An embodiment of the present application provides a communication system. The communication system includes an access management network element and a terminal. The access management network element is configured to perform any function performed by the access management network element in Figures 8 to 10, and the terminal is configured to perform any function performed by the second terminal in Figures 8 to 10.

All or part of the above-mentioned embodiments may be implemented using software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, all or part of these embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded into a computer and executed, the procedures or functions according to the embodiments of the present application are performed completely or partially. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or another programmable device. The computer program or instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer program or instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired or wireless manner. The computer-readable storage medium may be any available medium accessible from a computer, or a data storage device, such as a server or data center, that incorporates one or more available media. The available media may be magnetic media, such as a floppy disk, hard disk, or magnetic tape; optical media, such as a digital video disc (DVD); or semiconductor media, such as a solid-state drive (SSD).

Although the present application has been described with reference to embodiments, in the process of implementing the present application for which protection is claimed, a person skilled in the art may understand and implement other variations of the disclosed embodiments by studying the accompanying drawings, the disclosed content, and the appended claims. In the claims, "comprising" does not exclude other components or steps, and "a" or "one" does not exclude a plurality. A single processor or other unit may perform several functions recited in the claims. Although some means are recited in mutually different dependent claims, this does not mean that these means cannot be combined to produce a better effect.

Although the present application has been described with reference to certain features and embodiments thereof, it is clear that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Correspondingly, the present specification and the accompanying drawings are merely exemplary descriptions of the present application as defined by the appended claims, and any or all of the modifications, variations, combinations, or equivalents covering the scope of the present application are deemed to be within the scope of the present application. It is clear that a person skilled in the art can make various modifications and variations to the present application without departing from the spirit and scope of the present application. The present application is intended to cover these modifications and variations of the present application as long as they fall within the scope of protection defined by the following claims and their equivalent technologies.

Claims (17)

receiving, by an access management network element in a first non-public network, a first message from a first terminal, the first message being used to request registration of the first terminal in the first non-public network, the first message including an identifier of a first public network corresponding to the first terminal;
and if the first non-public network supports interworking with the first public network, obtaining, by the access management network element, a third message from an integrated data management network element in the first public network, and sending, by the access management network element, a second message to the first terminal based on the third message, wherein the second message is used to indicate that registration of the first terminal to the first non-public network is rejected, the second message including first indication information, the first indication information indicating that access of the first terminal to the first non-public network is prohibited; or, if the first non-public network does not support interworking with the first public network, sending, by the access management network element, the second message to the first terminal without obtaining the third message. 2. The method of claim 1, wherein the third message includes subscription data of the first terminal, the subscription data including second indication information, the second indication information being used to indicate that the first terminal can only access a public network, i.e., the second indication information being used to indicate that the first terminal cannot access a non-public network. The method of claim 2 , wherein the second indication information includes a supported network list of the first terminal, and the supported network list does not include information about the first non-public network. The method of claim 1 , wherein the third message includes third indication information, and the third indication information is used to indicate that subscription data of the first terminal is not successfully acquired. 5. The method of claim 4, wherein the third message further includes a cause value of the unsuccessful acquisition of the subscription data of the first terminal, the cause value indicating that the first terminal is not allowed to access the first non-public network. The method comprises:
The method according to any one of claims 1 to 5 , further comprising a step of deciding, by the access management network element, to reject the registration of the first terminal to the first non-public network based on the third message. A communication device, the communication device being an access management network element or a chip used in the access management network element, the communication device comprising:
a communication unit configured to receive a first message from a first terminal, the first message being used to request registration of the first terminal in a first non-public network, the first message including an identifier of a first public network corresponding to the first terminal;
The communication unit includes:
and further configured to: obtain a third message from an integrated data management network element in the first public network and send a second message to the first terminal based on the third message if the first non-public network supports interworking with the first public network; or send the second message to the first terminal without obtaining the third message if the first non-public network does not support interworking with the first public network;
the second message is used to indicate that registration of the first terminal to the first non-public network is rejected, the second message includes first indication information, the first indication information indicating that access of the first terminal to the first non-public network is prohibited;
Communications equipment. 8. The communication device of claim 7, wherein the third message includes subscription data of the first terminal, the subscription data including second indication information, the second indication information being used to indicate that the first terminal can only access a public network, i.e., the second indication information being used to indicate that the first terminal cannot access the first non-public network. The communication device of claim 8 , wherein the second indication information includes a supported network list of the first terminal, and the supported network list does not include information about the first non-public network. The communication device according to claim 7 , wherein the third message includes third indication information, and the third indication information is used to indicate that subscription data of the first terminal is not successfully acquired. 11. The communication device of claim 10, wherein the third message further includes a cause value of the unsuccessful acquisition of the subscription data of the first terminal, the cause value indicating that the first terminal is not allowed to access the first non-public network. The communication device according to any one of claims 7 to 11, further comprising a processing unit configured to decide to reject the registration of the first terminal to the first non-public network based on the third message. A communication system comprising an access management network element in a first non-public network and an integrated data management network element in a first public network, the network element being adapted to perform a method according to any one of claims 1 to 6 ,
The integrated data management network element includes:
a communication unit configured to receive an inquiry message from the access management network element, the inquiry message being used to inquire about subscription data of a first terminal;
The communication unit is further configured to send a third message to the access management network element, the third message including one or more of the subscription data and a cause value of the first terminal, the subscription data including second indication information, the second indication information being used to indicate that the first terminal can access only a public network, or the second indication information being used to indicate that the first terminal cannot access a non-public network, and the cause value being an indication that the first terminal is not allowed to access the first non-public network.
Communication systems. The communication system further comprises the first terminal.
14. The communication system of claim 13 . A computer readable storage medium having stored thereon instructions which, when executed , perform the method of any one of claims 1 to 6 . A chip comprising a processor and a communication interface, the communication interface coupled to the processor, the processor configured to run a computer program or instructions to perform a method according to any one of claims 1 to 6 , and the communication interface configured to communicate with another module external to the chip. A communications device comprising at least one processor, the at least one processor coupled to a memory , the at least one processor configured to operate instructions stored in the memory to perform a method according to any one of claims 1 to 6 .

Images