CN116762399A

CN116762399A - Method, device and system for registering to multiple networks

Info

Publication number: CN116762399A
Application number: CN202080107986.6A
Authority: CN
Inventors: 孙海洋; 朱方园; 李岩
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-12-18
Filing date: 2020-12-18
Publication date: 2023-09-15
Also published as: WO2022126631A1

Abstract

The embodiment of the application provides a method, a device and a system for registering a plurality of networks. The method comprises the following steps: the network device or the terminal device determines a plurality of networks supporting a plurality of network slices to be accessed by the terminal device according to the plurality of network slice information to be accessed by the terminal device, and then the terminal device can register to the plurality of networks. The multiple networks may be multiple public land mobile networks PLMNs, or multiple subnets in a PLMN, such as a non-public network NPN. By the method, the terminal equipment can access a plurality of network slices through registering to the plurality of networks, so that the requirement of the network slices expected to be used by the terminal equipment is met, services are better provided for users, and user experience is improved.

Description

Method, device and system for registering to multiple networks

Technical Field

The present application relates to the field of communications, and in particular, to a method, apparatus, and system for registering with multiple networks.

Background

In the fifth generation (the 5th generation,5G) mobile communication system, the demands of different types of application scenarios on the network are differentiated, and some even conflict with each other. Providing services for different types of application scenes through a single network at the same time can lead to complex network architecture, low network management efficiency and low resource utilization efficiency. The network slicing (network slicing) technology can provide mutually isolated network environments for different application scenes by establishing a virtual independent logic network on the same network infrastructure, so that the different application scenes can customize network functions and characteristics according to respective requirements so as to ensure the requirements of service quality (quality of service, qoS) of different services. That is, one physical network is divided into a plurality of virtual networks by the network slicing technique. A virtual network is regarded as a 'network slice', each network slice is mutually independent, and each network slice is used for customizing and managing network functions according to the requirements of application scenes. Thus, a network slice corresponds to one or more particular services.

Public land mobile networks (public land mobile network, PLMNs) are networks that an operator establishes and operates to provide land mobile services to the public. The network slices supported by different PLMNs may be the same or different. In a roaming scenario, a User Equipment (UE) moves from a home public land mobile network (home public land mobile network, HPLMN) to a visited public land mobile network (visited public land mobile network, VPLMN). Since the HPLMN supported network slice may not be exactly the same as the VPLMN supported network slice, and the UE expects to access multiple different network slices to obtain services for multiple types of traffic, then a certain network slice of the multiple network slices that the UE can use in the HPLMN may not continue to be used in the VPLMN. Thus, the UE cannot use all expected types of services, and the user experience is reduced.

Disclosure of Invention

A method, apparatus and system for registering with multiple networks are described.

In a first aspect, embodiments of the present application provide a method of registering with a plurality of networks, the method being performed by a network device. The method comprises the following steps: the network equipment acquires information of a plurality of network slices which are requested to be accessed by the terminal equipment; the network device determines a plurality of networks associated with the plurality of network slices, wherein each network slice of the plurality of network slices is supported by at least one network of the plurality of networks; the network device transmits information associated with a plurality of networks to the terminal device, the information associated with the plurality of networks being used for the terminal device to register with the plurality of networks. According to the scheme, the network equipment determines a plurality of networks capable of supporting a plurality of network slices requesting access, and sends information associated with the networks to the terminal equipment, so that the terminal equipment can register to the networks, the networks to which the terminal equipment is registered are used for requesting the access, the network slices to which the terminal equipment is required to access are met, the requirement of the network slices expected to be used by the terminal equipment is met, service is better provided for users, and user experience is improved.

For example, the plurality of networks may refer to a plurality of PLMNs. For example, the above method may be applied to a scenario in which the terminal device moves out of the HPLMN, and may be understood as a roaming scenario or a cross-PLMN scenario. Different PLMNs of the roaming site support different network slices. By the above method, the terminal device can register to a plurality of PLMNs, and a plurality of network slices to which the terminal device requests access are used by the plurality of PLMNs. Alternatively, the plurality of networks may refer to a plurality of subnets under one PLMN, for example, the subnets may refer to non-public networks NPN. The plurality of subnets may be a plurality of subnets under the HPLMN or may be a plurality of subnets under the VPLMN. Different subnets under the HPLMN or one VPLMN support different network slices. By the method, the terminal device can register a plurality of subnets, and a plurality of network slices which are accessed by the terminal device are requested by the plurality of subnets. The above description is also applicable to the methods provided in other aspects of the present application, and will not be repeated.

"registering with multiple networks" may be understood as "registering with multiple networks simultaneously". The "simultaneous" does not limit the terminal device to perform the action of registering to the plurality of networks at the same time, the terminal device may register to a first network of the plurality of networks and then to other networks of the plurality of networks, and the terminal device maintains a registered state in the first network when the terminal device registers to the other networks of the plurality of networks. The above description is also applicable to the methods provided in other aspects of the present application, and will not be repeated.

For example, the network device may be a unified data management, UDM, appliance. The UDM device may receive the information of the plurality of network slices from the terminal device through the mobility management AMF device, and transmit information associated with the plurality of networks to the terminal device through the AMF device.

In a possible embodiment, the method further comprises: the network device receives capability information of the terminal device from the terminal device, the capability information indicating that the terminal device has a capability of registering with a plurality of networks.

In a possible implementation, a network device determines a plurality of networks associated with a plurality of network slices, comprising: the network equipment acquires corresponding information, wherein the corresponding information is used for indicating the network to which the terminal equipment is allowed to register and the network slice supported by each network in the network to which the terminal equipment is allowed to register; the network device determines a plurality of networks associated with the plurality of network slices according to the corresponding information and the information of the plurality of network slices to which the terminal device requests access. That is, the network device acquires information of the network to which the terminal device is allowed to register and the network slices supported by each of the networks to which the terminal device is allowed to register, and then determines a plurality of networks from the information of the plurality of network slices to which the terminal device requests access, each of the plurality of network slices being supported by at least one of the plurality of networks.

Alternatively, in another possible implementation, a network device determines a plurality of networks associated with a plurality of network slices, comprising: the network equipment sends information of a plurality of network slices which the terminal equipment requests to access to the roaming preferred application function SOR-AF device; the network apparatus receives roaming preference SOR information from the SOR-AF device, and the network apparatus determines a plurality of networks based on the SOR information. That is, the SOR-AF apparatus determines a plurality of networks from information of a plurality of network slices to which the terminal device requests access, and feeds back to the network device by means of the SOR information. For example, this embodiment may be applicable to the roaming scenario described above.

In a possible embodiment, the method further includes: the network device determines information associated with the plurality of networks, wherein the information associated with the plurality of networks indicates the plurality of networks, or when the plurality of networks includes a first network in which the terminal device is currently registered, the information associated with the plurality of networks may also indicate information of at least one network other than the first network among the plurality of networks. That is, after the network device determines a plurality of networks associated with the plurality of network slices, the network currently registered by the terminal device may be removed to determine information associated with the plurality of networks. With this embodiment, the information of the plurality of networks is reduced.

In one possible implementation, a network device determines a plurality of networks associated with a plurality of network slices, comprising: the network device determines a network set including the plurality of networks. Then, the network device transmits information of a network set including a plurality of networks to the terminal device, and the terminal device can satisfy a plurality of network slices to which the terminal device requests access through a plurality of networks registered in the network set.

In another possible implementation, a network device determines a plurality of networks associated with a plurality of network slices, comprising: the network device determines a plurality of network sets, wherein each of the plurality of network slices for which the terminal device requests access is supported by at least one of the plurality of networks in each of the plurality of network sets, in other words, each of the plurality of network sets includes a plurality of networks respectively supporting the plurality of network slices for which the terminal device requests access. The network device may select one network set from the plurality of network sets as the determined plurality of networks and transmit the determined plurality of networks to the terminal device. Alternatively, the network device may send a plurality of eligible network sets to the terminal device, where the plurality of network sets includes a network set in which a plurality of networks to which the terminal device is ultimately registered are located. For example, the network set where the plurality of networks to which the terminal device is finally registered is the network set with the highest priority among the plurality of network sets. Or when the network device sends information containing a plurality of network sets meeting the conditions to the terminal device, the terminal device selects one network set meeting the conditions and registers the network set to the network.

In a possible implementation manner, the network device sends information associated with a plurality of networks to the terminal device, including: the network device transmits SOR information to the terminal device, the SOR information including information associated with the plurality of networks. That is, after the network device determines the plurality of networks associated with the plurality of network slices, the plurality of networks associated with the plurality of network slices are included in the SOR information, and the network device transmits information associated with the plurality of networks to the terminal device through the SOR information. For example, this embodiment is applicable to roaming scenarios.

In a possible embodiment, the method further comprises: the network device transmits to the terminal device indication information for registering the plurality of networks, the indication information being used for indicating the terminal device to register the plurality of networks.

In a second aspect, embodiments of the present application provide a method of registering with a plurality of networks, the method being performed by a terminal device. The method comprises the following steps: the terminal equipment sends information of a plurality of network slices which are requested to be accessed by the terminal equipment to the network equipment; the terminal device receives information of a plurality of networks associated with a plurality of network slices from the network device, wherein each network slice of the plurality of network slices is supported by at least one network of the plurality of networks; the terminal device registers at least one network of the plurality of networks according to the information of the plurality of networks. For example, if the terminal device is registered with a first network of the plurality of networks, the terminal device is registered with at least one network of the plurality of networks other than the first network; alternatively, the terminal device registers with multiple networks. In either way, the terminal device eventually registers with the plurality of networks. According to the scheme, the terminal equipment registers to the networks according to the received information of the networks, and the network slices which the terminal equipment requests to access are used by the registered networks, so that the requirements of the network slices which the terminal equipment expects to use are met, services are better provided for users, and user experience is improved.

The plurality of networks may refer to the description of the plurality of networks in the first aspect, and will not be described here again.

For example, the network device may be a unified data management, UDM, appliance. The terminal device may transmit information of a plurality of network slices requesting access to the UDM device through the AMF device, or may receive information of the plurality of networks from the UDM device through the mobility management AMF device.

In a possible embodiment, the method further comprises: the terminal device sends capability information of the terminal device to the network device, the capability information indicating that the terminal device has a capability of registering with a plurality of networks.

In a possible implementation manner, the terminal device receives information of a plurality of networks associated with a plurality of network slices from the network device, including: the terminal device receives roaming preference SOR information from the network device, the SOR information including information of a plurality of networks. That is, the terminal device is capable of receiving information of a plurality of networks associated with a plurality of network slices from the network device in the form of receiving SOR information. For example, this embodiment is applicable to roaming scenarios. Further, the terminal device registers at least one network of the plurality of networks according to the information of the plurality of networks, including: the terminal equipment updates the selector controlled by the operator or the selector controlled by the auxiliary updating user according to the SOR information; the terminal device registers to at least one of the plurality of networks according to the updated operator-controlled selector or the user-controlled selector.

In a possible embodiment, the method further comprises: the terminal device receives, from the network device, indication information registered with the plurality of networks, the indication information being for indicating that the terminal device is registered with the plurality of networks.

In a possible implementation, the terminal device receives, from a network device, information of a plurality of networks associated with a plurality of network slices, including: the terminal device receives a plurality of network sets from the network device, the plurality of network sets including a first network set, the first network set including a plurality of networks. Further, the terminal device registers at least one network of the plurality of networks according to the information of the plurality of networks, including: the terminal device selects a first network set from the plurality of network sets, and registers at least one network from the plurality of networks according to information of the plurality of networks in the first network set. For example, the first network set is a highest priority network set of the plurality of network sets.

In a third aspect, embodiments of the present application provide a method of registering with a plurality of networks, the method being performed by a terminal device. The method comprises the following steps: the terminal device receives first information from the network device, where the first information is used to indicate the network set and the network slices supported by each network in the network set, or the first information includes the association relationship between the network set and the network slices supported by each network in the network set. The terminal equipment selects a plurality of networks associated with a plurality of network slices to be accessed by the terminal equipment from the network set, wherein each network slice in the plurality of network slices is supported by at least one network in the plurality of networks; the terminal device registers with at least one of the plurality of networks. For example, if the terminal device is registered with a first network of the plurality of networks, the terminal device is registered with at least one network of the plurality of networks other than the first network; alternatively, the terminal device registers with multiple networks. In either way, the terminal device eventually registers with the plurality of networks. According to the scheme, the terminal equipment selects a plurality of networks and registers the networks, and the networks to be accessed by the terminal equipment are used through the registered networks, so that the requirement of network slicing expected to be used by the terminal equipment is met, services are better provided for users, and user experience is improved.

For example, the network device may be a unified data management, UDM, appliance. The terminal device may receive the above-mentioned first information from the UDM device through the mobility management AMF device.

In a possible embodiment, optionally, the method further comprises: the terminal device sends capability information of the terminal device to the network device, the capability information indicating that the terminal device has a capability of registering with a plurality of networks.

In a possible embodiment, optionally, the method further comprises: the terminal device sends information of a plurality of network slices which the terminal device requests to access to the network device.

In a possible implementation manner, the terminal device receives first information from the network device, including: the terminal equipment receives roaming preference SOR information from the network equipment, wherein the SOR information comprises the first information, namely the SOR information comprises the network set and the association relation of network slices supported by each network in the network set. That is, the terminal device may not only directly receive the network set and the association of the network slices supported by each network in the network set from the network device, but in another implementation, the network set and the association of the network slices supported by each network in the network set may be presented in the form of SOR information. For example, this embodiment is applicable to roaming scenarios. Further, the terminal device selects a plurality of networks associated with a plurality of network slices to be accessed by the terminal device from the network set, including: the terminal equipment updates an operator-controlled selector or an auxiliary update user-controlled selector according to the first information in the SOR information; the terminal device selects a plurality of networks according to the updated operator-controlled selector or the user-controlled selector.

In a possible implementation, each network in the set of networks is a network to which the terminal device is allowed to register.

Alternatively, in another possible implementation manner, if the terminal device sends the information of the plurality of network slices requested to be accessed by the terminal device to the network device, in the received first information, the network that does not support any network slice of the plurality of network slices requested to be accessed by the terminal device may be removed. That is, each network in the set of networks supports at least one network slice of the plurality of network slices for which the terminal device requests access.

In a possible embodiment, the method further comprises: the terminal device receives, from the network device, indication information indicating that the terminal device registers with the plurality of networks.

In a fourth aspect, embodiments of the present application provide a method of registering with a plurality of networks, the method being performed by a network device. The method comprises the following steps: the network equipment acquires information of a plurality of network slices which are requested to be accessed by the terminal equipment; the network device determines first information according to information of a plurality of network slices which are requested to be accessed by the terminal device, wherein the first information is used for indicating a network set and network slices supported by each network in the network set, and each network in the network set supports at least one network slice in the plurality of network slices which the terminal device requests to be accessed. The network device sends the first information to the terminal device, the first information being for the terminal device to register with a plurality of networks in the network set. According to the scheme, the network equipment determines a network set capable of supporting at least one network slice in a plurality of network slices which the terminal equipment requests to access, and sends the network set and the network slices supported by each network in the network set to the terminal equipment. After the terminal equipment receives the first information, registering the first information to the network in the network set, and using a plurality of network slices to be accessed by the terminal equipment through the registered networks so as to meet the requirement of the network slices expected to be used by the terminal equipment, thereby better providing services for users and improving user experience.

For example, the network device may be a unified data management, UDM, appliance. The UDM device may receive information of a plurality of network slices to which the terminal device requests access from the terminal device through the mobility management AMF device, and transmit the first information to the terminal device through the AMF device.

In a possible implementation manner, the network device determines first information, including: the network equipment acquires corresponding information, wherein the corresponding information is used for indicating the network to which the terminal equipment is allowed to register and the network slice supported by each network in the network to which the terminal equipment is allowed to register; the network equipment determines first information according to the corresponding information and the information of the plurality of network slices which the terminal equipment requests to access. That is, the network device knows the network to which the terminal device is allowed to register and the information of the network slices supported by each network in the network to which the terminal device is allowed to register, then selects a network set supporting at least one network slice in the plurality of network slices to which the terminal device requests to access according to the information of the plurality of network slices to which the terminal device requests to access, acquires the information of the network slices supported by the network set, and presents the information in the form of first information.

In another possible implementation, the network device determines the first information, including: the network equipment sends information of a plurality of network slices which the terminal equipment requests to access to the roaming preferred application function SOR-AF device; the network device receives roaming preference SOR information from the SOR-AF device, and the network device determines first information according to the SOR information. That is, the SOR-AF apparatus generates SOR information from information of a plurality of network slices to which the terminal device requests access and feeds back the SOR information to the network device, and the network device determines the first information from the SOR information. For example, this embodiment is applicable to roaming scenarios.

In a possible implementation manner, the network set in the first information indicates the plurality of networks, or when the network set includes a first network in which the terminal device is currently registered, the network set in the first information indicates at least one network other than the first network. I.e. the network device determines the first information comprising: the network device determines first information according to a first network currently registered by the terminal device. That is, after the network device determines a plurality of networks associated with a plurality of network slices, the network currently registered by the terminal device may be removed to determine the first information. With this embodiment, the information of the plurality of networks is reduced.

In a possible implementation manner, the network device sends first information to the terminal device, including: the network device transmits SOR information to the terminal device, the SOR information including the first information. That is, the network device transmits the first information to the terminal device through the SOR information. For example, this embodiment is applicable to roaming scenarios.

In a fifth aspect, embodiments of the present application provide a method of registering with a plurality of networks, the method performed by a network device. The method comprises the following steps: the network device receives capability information of the terminal device from the terminal device, the capability information indicating that the terminal device has a capability of registering with a plurality of networks; the network equipment determines first information, wherein the first information is used for indicating a network set and network slices supported by each network in the network set; the network device sends the first information to the terminal device, the first information being for the terminal device to register with a plurality of networks in the network set. According to the above scheme, in the case that the terminal device has the capability of registering to a plurality of networks, the network device determines a network set and transmits the network set and the network slices supported by each network in the network set to the terminal device. After the terminal equipment receives the first information, registering the network slices to be accessed by the terminal equipment and the first information to the networks in the network set, and using the network slices to be accessed by the terminal equipment through the registered networks so as to meet the requirement of the network slices expected to be used by the terminal equipment, provide services for users better and improve user experience.

For example, the network device may be a unified data management, UDM, appliance. The UDM device may receive capability information of the terminal device from the terminal device through the mobility management AMF device, and transmit the first information to the terminal device through the AMF device.

In a possible implementation manner, the network device determines first information, including: the network equipment acquires corresponding information, wherein the corresponding information is used for indicating the network to which the terminal equipment is allowed to register and the network slice supported by each network in the network to which the terminal equipment is allowed to register; the network device determines the first information according to the corresponding information and the capability information of the terminal device. That is, the network device knows the information of the network to which the terminal device is permitted to register and the network slice supported by each of the networks to which the terminal device is permitted to register, and in the case where the terminal device has the capability of registering to a plurality of networks, the information of the network to which the terminal device is permitted to register and the network slice supported by each of the networks to which the terminal device is permitted to register is presented in the form of the first information.

In another possible implementation, the network device determining the first information includes: the network equipment sends the capability information of the terminal equipment to the SOR-AF device of the roaming preferable application function; the network device receives roaming preference SOR information from the SOR-AF device, and the network device determines first information according to the SOR information. That is, the SOR-AF apparatus generates first information according to capability information of the terminal device and feeds back to the network device by way of the SOR information, and the network device determines the first information according to the SOR information. For example, this embodiment is applicable to roaming scenarios.

In a possible implementation, the network set in the first information indicates the plurality of networks, or when the network set includes a first network in which the terminal device is currently registered, the first information indicates at least one network other than the first network. I.e. the network device determines the first information comprising: the network device determines first information according to a first network currently registered by the terminal device. That is, after determining the plurality of networks associated with the plurality of network slices, the network device may remove the network currently registered by the terminal device to determine the first information to obtain a final plurality of networks. With this embodiment, the information of the plurality of networks is reduced.

In a sixth aspect, embodiments of the present application provide a method of registering with a plurality of networks, the method performed by a unified data management, UDM, device. The method comprises the following steps: the UDM device obtains the identification of the AMF of the service, and stores the context information of a plurality of networks to which the terminal equipment is registered separately, wherein the context information corresponding to each network in the plurality of networks comprises the identification of the AMF of the service. That is, the network device stores association information of the plurality of networks and AMFs of services corresponding to each of the plurality of networks. When the terminal device registers to the network, the AMF of the service provides access management service for the terminal device. When the terminal equipment registers to the first network and then registers to the second network, the UDM device stores the identifiers of the AMFs of the services corresponding to the first network and the first network, and the identifiers of the AMFs of the services corresponding to the second network and the second network, and does not trigger the terminal equipment to register to the first network.

In a seventh aspect, embodiments of the present application provide a method of registering with a plurality of networks, the method being performed by an SOR-AF device. The method comprises the following steps: the SOR-AF device receives information of a plurality of network slices which are requested to be accessed by the terminal equipment from the network equipment; the SOR-AF device generates roaming preference SOR information according to information of a plurality of network slices which are requested to be accessed by the terminal equipment, wherein the SOR information is used for indicating a plurality of networks connected with the plurality of network slices, and each network slice in the plurality of network slices is supported by at least one network in the plurality of networks; the SOR-AF means sends SOR information to the network device.

In an eighth aspect, embodiments of the present application provide a method of registering with a plurality of networks, the method being performed by a roaming preferred application function, SOR-AF, device. The method comprises the following steps: the SOR-AF device receives information of a plurality of network slices which are requested to be accessed by the terminal equipment from the network equipment; the SOR-AF device generates roaming preference SOR information according to the information of a plurality of network slices which are requested to be accessed by the terminal equipment, wherein the SOR information is used for indicating a network set and network slices supported by each network in the network set, and each network slice in the plurality of network slices is supported by at least one network in the network set; the SOR-AF means sends SOR information to the network device.

In a ninth aspect, embodiments of the present application provide a communication apparatus comprising a processor for reading and running a program from a memory, to implement a method as in the first aspect or any of the possible embodiments (e.g. when the communication apparatus is a universal data management, UDM, apparatus), or to implement a method as in the second aspect or any of the possible embodiments (e.g. when the communication apparatus is a terminal device), or to implement a method as in the third aspect or any of the possible embodiments (e.g. when the communication apparatus is a terminal device), or to implement a method as in the fourth aspect or any of the possible embodiments (e.g. when the communication apparatus is a UDM apparatus), or to implement a method as in the fifth aspect or any of the possible embodiments (e.g. when the communication apparatus is a UDM apparatus), or to implement a method as in the sixth aspect or any of the possible embodiments (e.g. when the communication apparatus is a UDM apparatus), or to implement a method as in the seventh aspect or any of the possible embodiments (e.g. when the communication apparatus is a UDM apparatus), or to implement a method as in the fourth aspect or any of the possible embodiments (e.g. when the communication apparatus is a soaf apparatus), or a preferred apparatus, e.g. when the soaf apparatus is implemented.

In a tenth aspect, an embodiment of the present application provides a communication system, including a network device and a terminal device, where the network device may perform the method of the first aspect or any possible implementation manner, and where the terminal device may perform the method of the second aspect or any possible implementation manner.

In an eleventh aspect, an embodiment of the present application provides a communication system, including a network device and a terminal device, where the terminal device may perform the method of the third aspect or any possible implementation manner, and where the network device may perform the method of the fourth aspect or any possible implementation manner, or where the network device may perform the method of the fifth aspect or any possible implementation manner.

In a twelfth aspect, an embodiment of the present application provides a communication system, including an access and mobility management function AMF device and a unified data management UDM device, where the UDM device may perform the method of the first aspect or any possible implementation, or the UDM device may perform the method of the fourth aspect or any possible implementation, or the UDM device may perform the method of the fifth aspect or any possible implementation, or the UDM device may perform the method of the sixth aspect or any possible implementation.

In a thirteenth aspect, an embodiment of the present application provides a communication system, including a unified data management, UDM, device, which may perform the method of the first aspect or any of the possible embodiments, and a roaming preference application, SOR-AF, device, which may perform the method of the embodiment of the seventh aspect; alternatively, the UDM device may perform the method of the fourth or any possible embodiment or the fifth or any possible embodiment, and the SOR-AF device may perform the method of the eighth or any possible embodiment.

In a fourteenth aspect, embodiments of the present application provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform a method as in the first aspect or any of the possible embodiments, or a method as in the second aspect or any of the possible embodiments, or a method as in the third aspect or any of the possible embodiments, or a method as in the fourth aspect or any of the possible embodiments, or a method as in the fifth aspect or any of the possible embodiments, or a method as in the sixth aspect or any of the possible embodiments, or a method as in the seventh aspect or any of the possible embodiments, or a method as in the eighth aspect or any of the possible embodiments.

In a fifteenth aspect, embodiments of the present application provide a computer readable storage medium having instructions stored therein that, when run on a computer, cause a processor to perform a method as in the first aspect or any of the possible embodiments, or the second aspect or any of the possible embodiments, or the third aspect or any of the possible embodiments, or the fourth aspect or any of the possible embodiments, or the fifth aspect or any of the possible embodiments, or the sixth aspect or any of the possible embodiments, or the seventh aspect or any of the possible embodiments, or the eighth aspect or any of the possible embodiments.

Drawings

Fig. 1 is a schematic diagram of a scenario registered to multiple networks according to an embodiment of the present application;

FIG. 2 is a schematic diagram of registering multiple networks in another scenario in which embodiments of the present application are applicable;

fig. 3 and fig. 4 are schematic diagrams of network architecture in roaming scenarios, to which embodiments of the present application are applicable;

fig. 5 and fig. 6 are schematic diagrams of network architecture in a scenario in which a plurality of subnets are laid out in a PLMN according to an embodiment of the present application;

fig. 7 is a schematic diagram of a communication device according to an embodiment of the present application;

Fig. 8 is a schematic diagram of another communication device according to an embodiment of the present application;

fig. 9 is a schematic flow interaction diagram of a method for registering with multiple networks according to an embodiment of the present application;

FIG. 10 is a schematic flow interaction diagram of SOR information generation by SOR-AF according to an embodiment of the present application;

FIG. 11 is another flow interaction diagram of a method for registering with multiple networks according to an embodiment of the present application;

FIG. 12 is a flow chart illustrating another method of registering with multiple networks according to an embodiment of the present application;

FIG. 13 is a schematic flow interaction diagram of SOR information generation by another SOR-AF according to an embodiment of the present application;

fig. 14 is another flow interaction diagram of another method for registering with multiple networks according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.

Some concepts related to the present application will be described below:

1. network slice:

the 5G starts an era of everything interconnection, and the 5G supports three scenes of eMBB, mMTC and URLLC, wherein the three scenes comprise diversified and differentiated applications.

ebb: based on breakthroughs in wireless-side spectrum utilization and spectrum bandwidth technology, 5G may provide transmission rates that are more than 10 times faster than 4G. For current popular AR/VR, high-definition video live broadcast, only 5G ultra-high rate can meet the requirement, and 4G transmission rate cannot be supported. When the VR is used for watching high-definition or large-scale interactive games, a network cable is used for acquiring data, wireless connection is performed in the future through a 5G network, and the VR/AR can obtain quick experience.

mctc: through techniques such as multi-user shared access, ultra-dense heterogeneous network and the like, 5G can support 100 thousands of devices accessed per square kilometer, and the number of the devices is 10 times that of 4G. Recently, the rapid development of smart cities, and public facilities such as street lamps, well covers, water meters and the like have network connection capability, so that remote management can be performed, but 5G has more innovation. Based on the strong connection capability of the 5G network, public equipment in various industries in the city can be accessed to the intelligent management platform. The public facilities work cooperatively through the 5G network, and can be managed uniformly by a small amount of maintenance personnel, so that the operation efficiency of the city is greatly improved.

URLLC: the most typical application in 5G is automatic driving, and the most common scenes for automatic driving are sudden braking, vehicle-to-vehicle, vehicle-to-person, vehicle-to-infrastructure and the like, wherein multiple communication is performed simultaneously, and a large amount of data processing and decision making are needed instantaneously. There is therefore a need for networks with large bandwidth, low latency and high reliability, 5G networks with the ability to cope with such scenarios.

The 4G era is to meet all application scenarios and customer groups through one network, for example, if the network is to provide narrowband internet of things (narrowband internet of things, NB-IoT) capability, the NB-related characteristics on the network element are opened, and if the network reliability is to be built, the redundant backup of the network element device level is increased, and the requirements of the mass market are continuously met through the continuous superposition of the characteristics.

However, the requirements of various services in the vertical industry in terms of time delay, connection number, reliability, safety and the like are far away and have unpredictability, for example, AR service needs to use network ultra-high bandwidth of >1600Mbps, energy meter reading service needs network to provide mass connection, automatic driving needs network to ensure end-to-end low time delay of several milliseconds and high reliability of more than 99.999 percent, and if all the requirements at present and the requirements possibly proposed in the future are still to be met through one network, the realization is not possible at all.

The network slicing technology can enable an operator to divide a plurality of virtual networks in one hardware infrastructure, allocate resources according to needs and flexibly combine the capabilities, thereby meeting different requirements of various services. When new demands are put forward and the current network cannot meet the demands, an operator only needs to virtually draw out a new slicing network for the demands, and the existing slicing network is not influenced, so that the service is on line at the fastest speed.

Network slicing is to virtualize a plurality of end-to-end networks on the basis of one general hardware through slicing technology, and each network has different network functions and adapts to different types of service requirements. That is, a network slice is a network that is used to support the logical separation of particular network capabilities from network characteristics. For example, after purchasing physical resources, an operator uses the physical resources to virtually form an eMBB slice network for mass internet surfing services, and then uses the physical resources to virtually form an mMTC slice network for intelligent meter reading requirements of certain manufacturers in the vertical industry, wherein the two slice networks respectively provide services for different service scenes.

Although the demands for network functions are varied from industry to industry in the vertical industry, these demands can be resolved into demands for network functions such as network bandwidth, connection count, latency, reliability, etc. The 5G standard also summarizes the characteristics of the requirements of different services on network functions into three typical scenes, and the types of network slices corresponding to the three typical scenes are respectively an eMBB slice, an mMTC slice and a URLLC slice.

2. Single network selection slice assistance information (single network slice selection assistance information, S-NSSAI):

S-NSSAI is used to identify a network slice. Depending on the operator' S operational or deployment needs, one S-nsai may be associated with one or more network slice instances, and one network slice instance may be associated with one or more S-nsais. For example, eMBB slice 1, eMBB slice 2, and eMBB slice 3 are all eMBB type slices, and their S-NSSAI values are all 0x01000000; the eMBB+mMTC slice 4 can provide services for eMBB type services and mMTC services, so that the eMBB type slice and the mMTC type slice are provided, and corresponding S-NSSAI values are 0x01000000 and 0x02000000 respectively.

The S-NSSAI includes two parts, slice/service type (SST) and slice difference (slice differentiator, SD):

SST refers to the network slicing behavior expected in terms of characteristics and services. For example, SST standard ranges of values 1, 2, and 3, value 1 representing emmbb, value 2 representing URLLC, and value 3 representing large-scale internet of things (massive internet of things, MIoT).

SD is an optional information used to supplement SST to distinguish multiple network slices of the same slice/traffic type.

The SST and SD parts combine to represent a slice type and multiple slices of the same slice type. For example, S-NSSAI values of 0x01000000, 0x02000000, and 0x03000000 represent an eMBB type slice, a URLLC type slice, and a MIoT type slice, respectively. And S-NSSAI values of 0x01000001 and 0x01000002 represent eMBB type slices, which can serve user group 1 and user group 2 respectively.

3. Network slice selection assistance information (network slice selection assistance information, nsai):

NSSAI is a collection of S-NSSNI. NSSAI used in 5G networks has a request NSSAI (requested NSSAI), an allowed NSSAI (allowed NSSAI), a rejected NSSAI (rejected NSSAI), and a contracted NSSAI (subscribed NSSAI), whose specific definitions are shown in table 1:

TABLE 1

Plmn selection:

a PLMN is a network established and operated by an operator for providing land mobile services to the public. In the prior art, the UE selects PLMN according to the following priority:

first, currently registered PLMN (registered PLMN), or PLMN (equivalent RPLMN) equivalent to the currently registered PLMN;

a second, HPLMN, or PLMN equivalent to HPLMN (EPLMN);

a third, user-controlled PLMN selector (user-controlled PLMN selector);

fourth, operator-controlled PLMN selector (operator-controlled PLMN selector).

Wherein the third and fourth PLMN selectors each include a set of prioritized PLMN lists for UE selection, as shown in table 2. Each PLMN selector includes a PLMN list arranged in descending order according to priority. If the UE cannot select PLMNs arranged in the first and second positions, the UE selects a PLMN according to the PLMN selector controlled by the user arranged in the third position, and preferentially selects a PLMN with a higher priority, for example, PLMN1 in table 2, according to the ranking of PLMNs in the PLMN selector. If the UE cannot select PLMNs arranged in the first, second and third digits, the UE selects a PLMN according to a PLMN selector controlled by an operator arranged in the fourth digit, and similarly, the UE may preferentially select a PLMN with a higher priority according to the ranking of PLMNs in the PLMN selector.

TABLE 2

User controlled PLMN selector/operator controlled PLMN selector
PLMN1
PLMN2
PLMN3
PLMN4
PLMN5

5. Roaming preference (Steering of Roaming, SOR)

SOR is a technique by which the HPLMN directs roaming UEs to register into a preferred roaming network. For example, when a roaming agreement change occurs, the UDM of the HPLMN sends roaming preference (steering of roaming, SOR) information to the UE. For example, the SOR information includes at least one of: (a) A list (list of preferred PLMN/access technology combinations) of combinations of preferred PLMNs or access technologies, (b) a security packet (a secured packet) containing a list of combinations of the above preferred PLMNs or access technologies encapsulated by a security mechanism; neither of (c) is provided. Wherein (a) to (c) are generated based on data analysis by the operator.

The SOR information may be used to update the PLMN list in the above-mentioned user-controlled PLMN selector or operator-controlled PLMN selector, and the UE performs PLMN selection and registration according to the priority of the PLMN selector and the priority of the PLMNs in the PLMN selector, for example, default SOR information is used to update the operator-controlled PLMN selector.

In the present application, registering with a network is also understood to mean accessing the network, which is hereinafter referred to as "registering" with the network.

6. Non-Public Network (Non-Public Network, NPN)

An NPN is a network that is oriented to users of a non-public network and may be dedicated for use by private entities, such as businesses. The NPN may be deployed in different forms, in particular, may be deployed as a completely independent network, may be hosted by a PLMN, may be a network slice of the PLMN. NPN is divided into two types:

(1) Independent networking NPN (Stand-alone non-public networks, SNPN)

The SNPN is operated by an NPN operator, and the UE signs up for one or more NPN, and identifies one SNPN by a PLMN ID and network identification (NID, network identifier) combination, independent of the network functions provided by the PLMN.

(2) Public network integrated NPN, or NPN called non-independent networking (Public network integrated NPN, PNI-NPN)

PNI-NPN services may be provided by a PLMN network, such as by assigning one or more network slices to the NPN to implement NPN functions. The concept of having a closed access group (Closed Access Group, CAG) in the PNI-NPN can achieve the effect of preventing other UEs from registering the NPN. The PNI-NPN determines a CAG from the PLMN ID and the CAG ID, the UE subscription information comprises the CAG ID, and a user without indication information of the configured CAG-only can support switching between the PNI-NPN and the PLMN network.

The network slices supported by different PLMNs may be the same or different. As shown in fig. 1, in the roaming scenario shown in fig. 1, when the UE moves out of the HPLMN to roam to the VPLMN, there is a case in which the HPLMN supported network slice is different from the VPLMN supported network slice, i.e., the S-nsai of the HPLMN can only be used in an individual VPLMN. Thus, the UE can only use one VPLMN, which is not preferred, in some areas of the roaming place, and the VPLMN cannot support all network slices that the UE expects to use, and thus the UE cannot use all network slices that it wants to use in one PLMN.

For example, the UE wants to use traffic 1 and traffic 2, where traffic 1 is served by network slice 1 and traffic 2 is served by network slice 2. For example, the plurality of network slices that the UE requests access are network slice 1 and network slice 2. When the UE is in the HPLMN, the HPLMN is able to support network slice 1 and network slice 2, and the UE may use network slice 1 and network slice 2 when registering with the HPLMN. When the UE roams, the slicing supported by the different PLMNs located at the roaming place is as follows in table 3:

TABLE 3 Table 3

PLMN ID	Supported network slice
PLMN1	S-NSSAI 1、S-NSSAI 3
PLMN2	S-NSSAI 2、S-NSSAI 4
PLMN3	S-NSSAI 1、S-NSSAI 4
PLMN4	S-NSSAI 3、S-NSSAI 5
PLMN5	S-NSSAI 2、S-NSSAI 5

Wherein S-NSSAI 1, S-NSSAI 2, S-NSSAI 3, S-NSSAI 4, S-NSSAI 5 are used to identify network slice 1, network slice 2, network slice 3, network slice 4, network slice 5, respectively.

According to the current method for selecting PLMN by UE, the UE can select the PLMN with the highest priority in the PLMN selector controlled by the operator according to the priority as the VPLMN. As shown in table 2, assuming that the priority of PLMN1 is highest, the UE registers with PLMN1 as a VPLMN. However, the UE registers with only one PLMN regardless of the prioritization among the PLMNs, and thus cannot use network slice 1 and network slice 2 within one PLMN.

The network slices supported by different subnets (e.g., NPN) under the same PLMN may be the same or may be different, as shown in fig. 2. In the example of fig. 2, this PLMN may be an HPLMN or, alternatively, a VPLMN. The PLMN includes a subnet 1 and a subnet 2 with overlapping coverage areas. Similar to fig. 1, the UE may use network slice 1 and network slice 2 before moving, but subnet 1 only supports network slice 1 after moving and subnet 2 only supports network slice 2. Neither the UE registers with subnet 1 nor subnet 2, nor the UE can use network slice 1 and network slice 2 within one subnet.

The problem to be solved by the present application is how to meet the requirements of the network slice that the UE expects to use. Taking the example in fig. 1 and 2 above as an example, the present application aims to provide a solution that enables a UE to use network slice 1 and network slice 2 in the above scenario.

The technical solution of the embodiment of the present application may be applied to various communication systems, such as a long term evolution (long term evolution, LTE) system, an LTE frequency division duplex (frequency division duplex, FDD) system, an LTE time division duplex (time division duplex, TDD), a fifth generation (5th generation,5G) mobile communication system, or a New Radio (NR) system, or to future communication systems or other similar communication systems. Taking the fifth generation (5th generation,5G) mobile communication system as an example, the system comprises a server network architecture and a reference point-based network architecture. In addition, the embodiment of the application can be applied to other communication technologies facing the future. The network architecture and the service scenario described in the present application are for more clearly describing the technical solution of the present application, and do not constitute a limitation to the technical solution provided by the present application, and those skilled in the art can know that the technical solution provided by the present application is equally applicable to similar technical problems with evolution of the network architecture and occurrence of new service scenarios. The above various systems include non-roaming scenarios and roaming scenarios.

As described above, the present application may be applied to a roaming scenario (or referred to as a cross-PLMN scenario), or may be applied to a scenario in which a plurality of subnets (for example, NPN) are laid out within the same PLMN (HPLMN or VPLMN). When the present application is used in roaming scenarios, it can be applied to the network architecture of the communication system as shown in fig. 3 or fig. 4. When the present application is used in a scenario in which a plurality of subnets are laid out in the same PLMN, it is applicable to a network architecture of a communication system as shown in fig. 5 or fig. 6.

For the roaming scenario, when the UE roams from the HPLMN to the VPLMN, the roaming scenario may be classified into a roaming scenario of local breakout (local break) and a roaming scenario of home routing (home route) according to whether the user plane of the UE is VPLMN terminated or HPLMN terminated. In roaming scenarios, interworking of the servitized interfaces between the VPLMN and the HPLMN may be performed by respective secure edge protection agents (security edge protection proxy, SEPP) to implement message filtering and topology hiding functions across PLMN control plane interfaces. FIG. 3 is a schematic diagram of a network architecture of a service-based interface. Fig. 4 is a schematic diagram of a network architecture based on a point-to-point interface.

For a scenario in which multiple subnets are laid out in the same PLMN, when the UE moves from the HPLMN to the VPLMN, multiple subnets, for example, multiple NPN are laid out in the VPLMN, the network architecture for which the scenario is applicable is shown in fig. 5. When the UE is located in the HPLMN, a plurality of subnets, for example, a plurality of NPN are laid out in the HPLMN, and a network architecture suitable for this scenario is shown in fig. 6. Fig. 5 and fig. 6 are schematic diagrams of network architecture based on point-to-point interfaces, and the principle of the schematic diagrams of network architecture of service-based interfaces is similar and is not shown.

"service-based interface" refers to the use of a service-based interface within a control plane under a serviced architecture. For example, namf is a service-based interface provided by AMF network elements, which may communicate with other network functions through Namf. Nsmf is a service-based interface provided by the SMF, which may communicate with other network functions through Nsmf. The Nnssf is a service-based interface provided by NSSF network elements, which may communicate with other network functions through the Nnssf. A functional network element may open its capabilities to other functional network elements being authorized via a service-based interface to provide Network Function (NF) services. In other words, NF services refer to various capabilities that can be provided.

The network architecture may comprise three parts, namely a terminal device, a radio access network (radio access network, RAN) and a core network.

The functions of some of the network elements involved in the network architecture are described in detail below.

The terminal equipment is equipment with a wireless receiving and transmitting function. The terminal equipment is connected with the access network equipment in a wireless mode, so that the terminal equipment is accessed into the communication system. The terminal device may also be referred to as a terminal, user Equipment (UE), mobile station, mobile terminal, etc. The terminal device may be a mobile phone, a tablet computer, a computer with a wireless transceiving function, a virtual reality terminal device, an augmented reality terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned operation, a wireless terminal in teleoperation, a wireless terminal in smart grid, a wireless terminal in transportation security, a wireless terminal in smart city, a wireless terminal in smart home, or the like. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the terminal equipment. By way of example and not limitation, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device or an intelligent wearable device, and is a generic name for intelligently designing daily wear and developing wearable devices, such as glasses, gloves, watches, clothes, shoes, and the like, by applying wearable technology. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart helmets, smart jewelry, etc. for physical sign monitoring. The terminal device may also be an in-vehicle module, an in-vehicle component, an in-vehicle chip or an in-vehicle unit built in the vehicle as one or more components or units, through which the vehicle may implement the method of the present application.

The RAN is used to implement radio related functions. The nodes in the RAN may also be referred to as access network devices or base stations for accessing terminal devices to the wireless network. The access network device may be a base station (base station), an evolved NodeB (eNodeB) in an LTE system or an evolved LTE system (LTE-Advanced), a next generation NodeB (gNB) in a 5G communication system, a transmission reception point (transmission reception point, TRP), a baseband unit (BBU), a WiFi Access Point (AP), a base station in a future mobile communication system or an access node in a WiFi system, etc. The radio access network device may also be a module or unit that performs the functions of the base station part, for example, a Centralized Unit (CU), or a Distributed Unit (DU). The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the wireless access network equipment. For example, in one network architecture, the radio access network device may be a CU node, or a DU node, or an access network device comprising a CU node and a DU node. Specifically, the CU node is configured to support protocols such as radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP), service data adaptation protocol (service data adaptation protocol, SDAP), etc.; the DU node is used to support radio link control (radio link control, RLC) layer protocols, medium access control (medium access control, MAC) layer protocols, and physical layer protocols.

The core network may include one or more of the following network elements: unified data management (unified data management, UDM) network elements, application function (application function, AF) network elements, access and mobility management function (access and mobility management function, AMF) network elements, session management function (session management function, SMF) network elements, user plane function (user plane function, UPF) network elements, and network slice selection function (network slice selection function, NSSF) network elements, and the like. The network elements described above may also be referred to as devices, apparatuses or entities, and the application is not limited thereto, e.g. a UDM network element may also be referred to as a UDM device, UDM apparatus or UDM entity. In the following description, it will be referred to simply, for example, "UDM network element" is referred to simply as "UDM" and "AMF network element" is referred to simply as "AMF".

The AMF is used to take charge of mobility management of the user. Mobility management includes, for example, mobility state management, assigning a user temporary identity, authenticating and authorizing a user, and the like.

SMF is used to take care of UPF selection, reselection, network protocol (internet protocol, IP) address assignment, establishment, modification or release of protocol data unit (protocol data unit, PDU) session, quality of service (quality of service, qoS) control, etc.

The UDM is responsible for managing subscription data and for informing the corresponding network element when the subscription data is modified.

The AF is used to provide application layer services to the UE. The AF represents an application interacting with other controlling network elements of the 5G network, including providing quality of service QoS requirements, charging (Policy) requirements, routing Policy requirements, etc. Wherein, as shown in fig. 1 to 6, the SOR-AF is an AF used for the above-mentioned SOR technique, and the SOR-AF is connected to the UDM.

The UPF is interconnected with a Data Network (DN) for detection, routing and forwarding of packet data packets. For example, the UPF may act as an upstream classifier (uplink classifier, ULCL) to support offloading traffic before forwarding to the data network, or the UPF may act as a offload point (BP) to support multi-homed PDU sessions.

NSSF is used to account for the selection of network slices. In the examples of fig. 3-5, H-NSSF is deployed within the HPLMN and V-NSSF is deployed within the VPLMN. According to the method of the embodiment of the application, a point-to-point interface or a service operation between the UDM and the H-NSSF can be increased.

The network elements described above may be implemented by specified hardware, or may be implemented by software instances on specified hardware, or may be implemented by virtual functions instantiated on a suitable platform, and the application is not limited in this regard.

When the present application is applied to a roaming scenario across PLMNs, as shown in fig. 3 and 4, a UE roams to a VPLMN and registers to the network through a RAN located in the VPLMN, AMF, SMF, NSSF in the following description refers to AMF, SMF, NSSF located in the VPLMN, and UDM and SOR-AF refer to UDM and SOR-AF located in the HPLMN, respectively. When the present application is applied to a scenario in which a plurality of subnets are laid out in the same VPLMN, as shown in fig. 5, the UE roams to the VPLMN and registers to the network through the RAN located in the VPLMN, AMF, SMF, NSSF in the following description refers to AMF, SMF, NSSF located in the NPN range in the VPLMN, and UDM and SOR-AF refer to UDM and SOR-AF located in the HPLMN, respectively. When the present application is applied to a scenario in which multiple subnets are laid out in the same HPLMN, as shown in fig. 6, AMF, SMF, NSSF, UDM and SOR-AF are AMF, SMF, NSSF, UDM and SOR-AF located in the current PLMN. For NPN, the functional network elements such as AMF, SMF, NSSF, UDM and SOR-AF may be combined or separated, and do not affect the implementation of the method in the present application.

It should be noted that "a plurality of" means two or more, and "a plurality of" may be understood as "at least two" in this embodiment of the present application. "at least one" may be understood as one or more, for example as one, two or more. For example, including at least one means including one, two or more, and not limiting what is included. For example, at least one of A, B and C is included, then A, B, C, A and B, A and C, B and C, or A and B and C may be included. Likewise, the understanding of the description of "at least one" and the like is similar.

Fig. 7 and 8 are schematic structural diagrams of a communication device according to an embodiment of the present application, which may be used to perform a method of registering with multiple networks. For ease of understanding, a method for registering with multiple networks provided in accordance with an embodiment of the present application will be described.

Fig. 9 is a schematic flow interaction diagram of a method for registering with multiple networks according to an embodiment of the present application. The registration to the plurality of networks may be to the plurality of PLMNs or to a plurality of subnets under one PLMN. Registration to a plurality of PLMNs will be described below as an example.

The method involves interactions between the UE, AMF and UDM. When the method is used for registering to multiple PLMNs across roaming scenarios of the PLMNs, the UE may be the UE in fig. 3 or fig. 4, the AMF may be the AMF in the VPLMN in fig. 3 or fig. 4, and the UDM may be the UDM in the HPLMN in fig. 3 or fig. 4. For example, the VPLMN may be any PLMN in table 3 above.

For example, the method comprises the steps of:

in step 901, the ue sends a registration request (registration request) message to the AMF.

For example, the UE sends a registration request message to the RAN (not shown in fig. 9), which, upon receiving the registration request message, sends the registration request message to the AMF, e.g., the RAN may be the RAN located in the VPLMN in fig. 3 or fig. 4.

Accordingly, the AMF receives the registration request message from the UE through the RAN.

In the example of fig. 9, the registration request message includes information of a plurality of network slices to which the UE requests access. The information of the plurality of network slices the UE requests access to may be UE requested NSSAI. For example, the plurality of network slices that the UE requests access to are network slice 1 and network slice 2,UE requested NSSAI include S-nsai 1 identifying network slice 1 and S-nsai 2 identifying network slice 2.

In addition, the registration request message may include a PLMN ID of a PLMN currently registered by the UE.

In addition, the registration request message may further include registration type information, which may be used to indicate that the type of this registration is initial registration, for example.

Optionally, the registration request message may further include UE capability information, where the capability information indicates that the UE has a capability of registering with multiple networks. For example, the capability information is specifically used to indicate that a subscriber identity module (subscriber identity module, SIM) in the UE has the capability to register with multiple PLMNs. For example, the UE transmits UE capability information to the network through a registration request message, the UE capability information may be implemented by one bit (bit), when the capability information has a first value (e.g., 1), indicating that the UE has a capability of registering to a plurality of PLMNs; when the capability information has a second value (e.g., 0), it indicates that the UE does not have the capability to register with multiple PLMNs. Or when the UE has the capability of registering to a plurality of PLMNs, the UE sends UE capability information to the network through a registration request message; when the UE does not have the capability to register with multiple PLMNs, the UE does not transmit the UE capability information.

After the AMF receives the registration request message, corresponding steps in the registration flow are executed. For example, if the AMF does not have the subscription information of the UE, the AMF invokes a service operation to the UDM to obtain the subscription information of the UE.

In step 902, the amf sends a request message a to the UDM. The request message a may include information in the above-described registration request message, for example, the request message a may include information of a plurality of network slices to which the UE requests access, such as S-nsai 1 identifying network slice 1 and S-nsai 2 identifying network slice 2.

Accordingly, the UDM receives the request message a from the AMF.

For example, the AMF may send a request message a to the UDM by calling a service operation of the UDM.

Optionally, after receiving the request message a, the UDM determines that the current PLMN cannot support all the plurality of network slices requested to be accessed by the UE. For example, the current PLMN is PLMN 1, and as shown in Table 3 above, PLMN 1 supports network slice 1 identified by S-NSSAI 1 and network slice 3 identified by S-NSSAI 3, and cannot support network slice 2 identified by S-NSSAI 1, thus triggering the UDM to perform the following step 903.

In step 903, the udm determines the network set.

The network set may be one network set, or may be a plurality of network sets. Wherein each network set includes a plurality of PLMNs, and each network slice that the UE requests access to is supported by at least one PLMN of the plurality of PLMNs.

As described above, the UE requests access to two network slices: network slice 1 and network slice 2. At least two PLMNs are included in each network set, one PLMN supporting network slice 1 and the other PLMN supporting network slice 2. For example, in connection with the example of table 3 above, the network set may include: one or more of { PLMN1 and PLMN2}, { PLMN1 and PLMN5}, { PLMN2 and PLMN3}, { PLMN3 and PLMN5 }. Wherein PLMNs in { are indicative of multiple PLMNs in a network set. Alternatively, the network set may include PLMNs in { PLMN1 and (PLMN 2, PLMN 5) }, () as PLMNs supporting the same network slice.

Optionally, there is no order of priority among the plurality of network sets. Alternatively, there is a priority order among the plurality of network sets. For example, the first network set is the highest priority network set. For example, { PLMN1 and PLMN2} is the highest priority network set, next { PLMN1 and PLMN5}, and so on.

In one possible implementation, the UDM may obtain the SOR information through the SOR-AF, where the SOR information includes information of the above-described network set, which will be described in detail with reference to fig. 10 later.

In another implementation, the UDM may determine the network set from a plurality of network slice information that the UE requests access to.

For example, the UDM configures S-nsai supported by a PLMN with roaming agreements or the UDM obtains S-nsai supported by a PLMN with roaming agreements from NSSF (e.g., NSSF located in HPLMN) and then determines S-nsai supported by a PLMN that allows the UE to access based on S-nsai supported by a PLMN with roaming agreements and subscription information of the UE. The S-NSSAI supported by the PLMN that the UE is allowed to access may be as described in the foregoing table 3. It will be appreciated that when the UDM obtains the S-NSSAI supported by the PLMN with roaming agreement from the NSSF located within the HPLMN, this means that the interface or service operation between the UDM and the NSSF is to be added to the existing network architecture.

The UDM then determines a network set based on the information of the plurality of network slices the UE requests access to and the S-nsais supported by each PLMN.

Optionally, the UDM may determine the network set based on information of a plurality of network slices requested to be accessed by the UE, S-nsais supported by each PLMN, and PLMN IDs of PLMNs currently registered by the UE. For example, the request message a in step 902 also carries the PLMN ID of the PLMN currently registered by the UE, from which the UDM learns the PLMN currently registered by the UE, thereby selecting the network set including the PLMN currently registered by the UE. For example, if the PLMN currently registered by the UE is PLMN1, the network set may include: one or more of { PLMN1 and PLMN2} and { PLMN1 and PLMN5 }.

For example, when UE capability information is included in the request message a, the UDM has the capability of registering to a plurality of PLMNs according to the UE capability information, and then determines a network set. Alternatively, the above-mentioned registration request message and request message a may not contain UE capability information, and the UDM may default that the UE has a capability of registering to a plurality of PLMNs, thereby performing the following operations.

Alternatively, the UDM may also generate SOR information containing the above-described network set according to the above-described manner. The form of the SOR information may also be referred to later in the detailed description of fig. 10.

The S-nsai considered in the above step is the S-nsai included in the UE subscribed S-nsai. That is, regardless of whether the S-nsai that the UE requests access to is determined to be an access-allowed S-nsai in the current PLMN, at least the subscribed S-nsai of the UE includes the S-nsai, or the network slice corresponding to the S-nsai may be registered in other PLMNs. Otherwise, the network side does not have to consider PLMNs that can be registered to for this S-nsai. In other words, for S-nsais for which a UE not included in the subscribed S-nsais requests access, the network device does not need to determine a PLMN for it.

In step 904, the udm sends a response message b to the AMF, the response message b comprising information associated with the network set. Accordingly, the AMF receives a response message b from the UDM, the response message b comprising information associated with the above-mentioned network set.

For example, when the UDM determines a network set through step 903, the UDM may send information associated with the network set through response message b of step 904. When the UDM determines a plurality of network sets through step 903, the UDM may send information of the plurality of network sets through the response message b of step 904, or the UDM may send information of a part of the plurality of network sets according to at least one of priorities of the respective network sets and PLMNs currently registered by the UE. For example, the UDM may send information of one of the network sets with highest priority, or send information of one or more network sets containing the PLMN to which the UE is currently registered.

Further optionally, the UDM may also determine information associated with the network set based on the PLMN currently registered by the UE. The information associated with the network set may include only PLMNs to which the UE is to be additionally registered, and not the PLMNs to which the UE is currently registered. For example, the PLMN currently registered by the UE is PLMN1, and the network set may include: { PLMN1 and PLMN2}, then the information associated with the network set may include only information of PLMN 2.

Optionally, the UDM further sends indication information to the AMF, the indication information being used to indicate that the UE is registered to the plurality of PLMNs. For example, the UDM may send the information associated with the network set and the indication information described above to the AMF through the response message b of step 904.

For example, the UDM may send the above information to the AMF by calling the servicer operation of the AMF.

In step 905, the amf sends a registration accept message to the UE, where the registration accept message includes the information related to the network set.

Optionally, the registration acceptance message further includes the above indication information.

Optionally, the registration accept message further includes at least one of an allowed nsai and a rejected nsai. Alternatively, the message sent by the AMF to the UE in step 905 may be a registration rejection message (not shown in the figure), where the registration rejection message includes the information associated with the network set as described above. For example, when the current PLMN is any of the PLMNs described above, the allowed nsai and the rejected nsai may be as described in table 4, in conjunction with the examples of table 3 above.

TABLE 4 Table 4

PLMN ID	Allowed NSSAI	Rejected NSSAI
PLMN1	S-NSSAI 1	S-NSSAI 2
PLMN2	S-NSSAI 2	S-NSSAI 1
PLMN3	S-NSSAI 1	S-NSSAI 2
PLMN4	null	S-NSSAI 1、S-NSSAI 2
PLMN5	S-NSSAI 2	S-NSSAI 1

For example, the AMF sends a registration accept message/registration reject message to the RAN (not shown in fig. 9), which, upon receipt of the registration accept message, sends the registration accept message/registration reject message to the UE.

Accordingly, the UE receives a registration accept message/registration reject message from the AMF through the RAN.

At step 906, the ue registers with at least one of the plurality of networks.

It should be noted that "registering to a plurality of PLMNs" in the present application may be understood as "registering to a plurality of PLMNs simultaneously", for example, registering to a plurality of PLMNs in a network set simultaneously. "simultaneously" does not necessarily mean that the UE performs an action of registering to a plurality of PLMNs at the same time, the UE may register to a first PLMN of the plurality of PLMNs and then to a second PLMN of the plurality of PLMNs, and the UE maintains a registered state in the first PLMN when the UE registers to the second PLMN. That is, the UE maintains a registered state within a plurality of PLMNs.

In one possible implementation, when the UE receives one network set, the UE may register with PLMNs in the one network set accordingly, via step 905. It should be noted that, if the UE has already registered to the first PLMN in the PLMNs through the registration procedure of steps 901 to 905, the UE only needs to additionally register to other PLMNs except the first PLMN in the PLMNs; otherwise, the UE may additionally register with the multiple PLMNs.

For example, the information associated with the network set received by the UE is { PLMN1 and PLMN2}, and the UE has already been registered to PLMN1 through the registration procedure of steps 901 to 905, so long as the UE is additionally registered to PLMN2. Similarly, if the UE has already registered to PLMN2 through the above registration procedure, the UE only needs to register to PLMN1 additionally. If the UE is currently registered to PLMN3, PLMN4 or PLMN5, the UE registers to PLMN1 and PLMN2. In this case, the UE may be unregistered from the current PLMN.

In another possible implementation, when the UE receives multiple network sets, the UE may first determine one network set (referred to as a first network set) from the multiple network sets, via step 905. For example, the UE may randomly determine one network set from the plurality of network sets as the first network set, or the UE may determine a network set having a highest priority from the plurality of network sets as the first network set, or the UE may determine one network set including registered PLMNs as the first network set, or the UE may determine the first network set in combination with the priorities of the respective network sets and the network set of the registered PLMNs.

For example, the information associated with the network set received by the UE includes { PLMN1 and PLMN2}, { PLMN1 and PLMN5}, { PLMN2 and PLMN3}, { PLMN3 and PLMN5}. The UE may select the first set of networks according to any of the above approaches, e.g., { PLMN1 and PLMN2}.

After the UE determines the first set of networks, the UE may register with PLMNs in the first set of networks accordingly. How the UE operates may refer to the description in the former implementation, and is not described here again.

In another possible implementation, when the UE receives the information associated with the plurality of network sets through step 905 and includes only the information to be registered with the PLMN by the UE, that is, the information associated with the plurality of network sets received through step 905 does not already include the network to which the UE has been registered, the UE may additionally register with the PLMN in the information.

In either of the above ways, the UE eventually registers with multiple PLMNs that can support multiple network slices requested by the UE. After the UE registers to the PLMNs, the requested network slices may be used by the registered PLMNs. For example, when the UE wants to use the service provided by the network slice 2, a session corresponding to the network slice 2 is established, and then the network slice 2 is accessed through the session.

According to the method, the UE can register to the PLMNs according to the network slices which are requested to be accessed, so that the network slices which are requested to be accessed by the UE can be used under the combination of the PLMNs, the requirement of the network slices which the UE expects to use is met, the service is better provided for the user, and the user experience is improved.

As mentioned above, the method may also be applicable to scenarios with multiple subnets within the same PLMN (HPLMN or VPLMN). The method in this scenario also involves interactions between the UE, AMF and UDM. The UE may be the UE in fig. 5 or fig. 6, the AMF may be the AMF in fig. 5 or fig. 6, and the UDM may be the UDM in fig. 5 or fig. 6. Similarly, the UDM may determine one or more network sets, wherein each network set includes a plurality of subnets, and a plurality of network slices to which the UE requests access are supported by at least one of the plurality of subnets, and then, when the UE receives information associated with the network set, may register to the plurality of subnets, and use the plurality of network slices to which access is requested through the registered plurality of subnets. Therefore, a plurality of network slices which the UE requests to access can be used under the combination of a plurality of subnets, so that the requirement of the network slices which the UE expects to use is met, the service is better provided for the user, and the user experience is improved.

As described above, when the method is applied to a roaming scenario across PLMNs, the information associated with the network set may be implemented by means of SOR information, where the SOR information may be generated by the UDM or may be generated by the UDM requesting SOR-AF. Fig. 10 will be described taking UDM request SOR-AF generation SOR information as an example. Fig. 10 will be described in conjunction with fig. 9. For example, the method may comprise the steps of:

in step 1001, the udm sends to the SOR-AF information of a plurality of network slices to which the UE requests access. For example, the information of the plurality of network slices to which the UE requests access may be the information of the plurality of network slices to which the UE requests access included in the request message a of step 902 in fig. 9.

For example, if the subscription information of the UE indicates: the UE is provided with SOR information in case of an initial registration of a VPLMN, and the UDM determines that the SOR information is to be acquired, and then performs step 1001 described above.

Optionally, the UDM may also send UE capability information to the SOR-AF. For example, the UE capability information may be UE capability information included in the request message a of step 902 in fig. 9.

Optionally, the UDM may also send to the SOR-AF the PLMN ID of the PLMN currently registered by the UE. For example, the PLMN ID of the PLMN currently registered by the UE may be the PLMN ID of the PLMN currently registered by the UE included in the request message a of step 902 in fig. 9.

In step 1002, the SOR-AF generates SOR information according to information of a plurality of network slices requested to be accessed by the UE. The SOR information may indicate a set of networks. The network set may be described with reference to step 903 in fig. 9.

For example, SOR-AF is configured with S-NSSAI supported by PLMN of roaming agreement; alternatively, the SOR-AF obtains from the NSSF the S-nsai supported by the PLMN with roaming agreement. Then, the SOR-AF determines the S-NSSAI supported by the PLMN allowing the UE to access according to the S-NSSAI supported by the PLMN with roaming agreement and the subscription information of the UE, and further generates SOR information according to the information of a plurality of network slices requested to be accessed by the UE and the S-NSSAI supported by each PLMN.

The SOR information may include one or more network sets, wherein each network set includes a plurality of PLMNs, each network slice that the UE requests access to is supported by at least one PLMN of the plurality of PLMNs.

As described above, the UE requests access to two network slices: network slice 1 and network slice 2. At least two PLMNs are included in each network set, one PLMN supporting network slice 1 and the other PLMN supporting network slice 2. For example, in connection with the example of table 3 above, the SOR information may include: one or more of { PLMN1 and PLMN2}, { PLMN1 and PLMN5}, { PLMN2 and PLMN3}, { PLMN3 and PLMN5 }. Wherein PLMNs in { are indicative of multiple PLMNs in a network set. Alternatively, the network set may include PLMNs in { PLMN1 and (PLMN 2, PLMN 5) }, () as PLMNs supporting the same network slice.

Optionally, there is no order of priority among the multiple network sets in the SOR information. Alternatively, the SOR information may have a priority order among a plurality of network sets. For example, the network set ranked first in the SOR information is the highest priority network set. For example, { PLMN1 and PLMN2} is the highest priority network set, next { PLMN1 and PLMN5}, and so on.

Alternatively, the SOR-AF may determine SOR information according to information of a plurality of network slices requested to be accessed by the UE, S-nsais supported by each PLMN, and PLMN IDs of PLMNs currently registered by the UE. For example, the SOR-AF may select a network set including the PLMN the UE is currently registered to as the network set in the SOR information. For example, if the PLMN currently registered by the UE is PLMN1, the SOR information may include: one or more of { PLMN1 and PLMN2} and { PLMN1 and PLMN5 }.

Optionally, if the SOR-AF receives the UE capability information, the SOR-AF may determine that the UE has capability to access to multiple PLMNs according to the capability information carrying the UE, thereby determining the SOR information. Alternatively, the SOR-AF may default to the UE having the capability to register with multiple PLMNs, thereby generating SOR information.

Regardless of which of the above forms the network set is, several of the above SOR information may be presented as a list of preferred PLMNs or combinations of access technologies, or as a security package resulting from security packaging of such information.

In step 1003, the SOR-AF sends the SOR information described above to the UDM.

Optionally, the SOR-AF also sends indication information to the UDM, the indication information being used to indicate that the UE is registered to a plurality of PLMNs.

Accordingly, the UDM receives the SOR information from the SOR-AF, determines a network set according to the SOR information, and then performs step 904 as in fig. 9, i.e. delivers information associated with the network set to the UE through steps 904 and 905 in fig. 9. That is, the SOR information is included in the registration accept message in step 905. After receiving the SOR information, the UE registers with at least one of the plurality of networks, via step 906.

For example, the UE registering with at least one network of the plurality of networks according to the SOR information may be implemented as follows:

and the UE is used for assisting in updating the PLMN selector controlled by the user or updating the PLMN selector controlled by the operator according to the received SOR information containing the network set information. Then, the UE performs PLMN selection and registration to a plurality of PLMNs according to the selector.

Specifically, when the UE updates the operator-controlled PLMN selector according to the received SOR information, the UE may perform PLMN selection and registration according to the updated operator-controlled PLMN selector. Alternatively, the UE may assist in updating the user-controlled PLMN selector based on the SOR information. When the SOR information is used to update the user-controlled PLMN selector, the UE provides the SOR information to the user in a user-readable form (e.g., displays to the user) and the user then selects the registered PLMN. In one implementation, the UE may display the correspondence between each PLMN and each supported network slice in a user interface, and the user may select according to his own preference. After receiving the instruction of registering which PLMNs selected by the user, the UE updates the PLMN selector controlled by the user. For example, if the user selects PLMN1 and PLMN2 according to the information provided by the UE, the UE updates the PLMN selector controlled by the user to PLMN1 and PLMN2. When the UE uses a user controlled PLMN selector, it may register with PLMN1 and PLMN2. Furthermore, if the current UE has already registered to PLMN1, it is only required to register additionally to PLMN2. The principle of how the UE updates the operator controlled PLMN selector and the user controlled PLMN selector according to the SOR information is similar will be described below by taking the example of the UE updating the operator controlled PLMN selector according to the SOR information.

When the SOR information includes a network set, the UE updates the operator-controlled PLMN selector according to the SOR information, and the UE registers to PLMNs in the network set according to the updated operator-controlled PLMN selector. For example, SOR information includes information for a collection of networks. For example, when the network set includes PLMN1 and PLMN2, the updated operator controlled PLMN selector is shown in table 5. The UE may register with PLMN1 and PLMN2 according to the methods described above.

TABLE 5

Operator controlled PLMN selector
{PLMN1，PLMN2}

When the SOR information includes information of at least two network sets, the UE updates the operator-controlled PLMN selector according to the SOR information, and the UE selects and registers one network set according to the updated operator-controlled PLMN selector. For example, at least two network sets in the SOR information include: { PLMN1 and PLMN2}, { PLMN1 and PLMN5}, { PLMN2 and PLMN3}, and { PLMN3 and PLMN5}. The updated operator controlled PLMN selector is shown in table 6.

TABLE 6

Operator controlled PLMN selector
{PLMN1，PLMN2}
{PLMN1，PLMN5}
{PLMN2，PLMN3}
{PLMN3，PLMN5}

In one possible implementation, when there is no order of priority for each of the at least two network sets, the UE randomly selects one network set, e.g., the UE selects a PLMN in the first network set and registers. That is, the UE may select PLMN1 and PLMN2 and register.

Alternatively, the UE may select one network set in consideration of PLMNs that have been currently registered, i.e., one network set including PLMNs that have been currently registered. For example, if the UE has already registered to PLMN1 through the above registration procedure, the UE may select { PLMN1 and PLMN2} or { PLMN1 and PLMN5}, that is, the UE may additionally register to PLMN2 or PLMN5.

In another possible implementation, the network sets in the operator controlled PLMN selector are arranged in descending order of priority. The UE registers with the highest priority network set. As described above, { PLMN1 and PLMN2} is the highest priority network set. Thus, the UE registers with PLMN1 and PLMN2. If the UE is currently registered to PLMN1, the UE only needs to register to PLMN2 additionally. Similarly, if the UE has already registered to PLMN2 through the above registration procedure, the UE only needs to register to PLMN1 additionally. If the UE is currently registered to PLMN3, PLMN4 or PLMN5, the UE re-registers to PLMN1 and PLMN2. In this case, the UE may be unregistered from the current PLMN.

Further alternatively, the UE may select a network set with the highest priority in the PLMN selector controlled by the operator, where the network set includes PLMNs that have been currently registered, e.g., if the UE has been currently registered in PLMN1, { PLMN1 and PLMN2} is the network set with the highest priority in the PLMN selector controlled by the operator, the UE only needs to additionally register in PLMN2.

It may be appreciated that when the SOR information is in the form of a security packet, the UE first decapsulates the security packet and then selects and registers with the PLMN according to any of the above manners, which is not described herein.

After the UE registers to the PLMNs, the requested network slices may be used by the registered PLMNs.

By the method, the UE can update the PLMN selector controlled by the user or update the PLMN selector controlled by the operator in an auxiliary manner according to the received SOR information, when the UE selects the PLMN to be accessed according to the updated selector, the UE has the opportunity to register to a plurality of PLMNs, so that a plurality of network slices which the UE requests to access can be used under the combination of the plurality of PLMNs, the requirement of the network slices expected to be used by the UE is met, the service is better provided for the user, and the user experience is improved.

In addition, in the above embodiments, after the UE receives the SOR information, the UDM may update the SOR information again and issue the updated SOR information to the UE again, which is not limited herein.

Fig. 11 is a schematic diagram of another process interaction of a method for registering with multiple networks according to the present application. This schematic will be described in connection with fig. 9 and 10. Fig. 11 relates to interactions between a network device and a terminal device. For example, the network device may be the UDM in fig. 9 or fig. 10, and the terminal device may be the UE in fig. 9. Alternatively, the interaction may also involve an AMF, which may be the AMF in fig. 9. For example, the method comprises the steps of:

In step 1101, the terminal device sends information of a plurality of network slices requesting access to the network device. Accordingly, the network device receives information of a plurality of network slices requesting access from the terminal device.

For example, the network device may be a UDM. The UDM may receive the above information of the plurality of network slices requesting access from the terminal device through the AMF.

For example, the information of the plurality of network slices requesting access may be a requested NSSAI of the terminal device. For example, the plurality of network slices to which the terminal device requests access are network slice 1 and network slice 2, and the terminal device requested NSSAI includes S-NSSAI 1 of network slice 1 and S-NSSAI 2 of network slice 2. The information of the plurality of network slices requesting access may be described with reference to step 901 in fig. 9.

Optionally, the terminal device sends terminal device capability information to the network device. The capability information indicates that the terminal device has the capability of registering with a plurality of networks. For example, the capability information is specifically used to indicate that a SIM card in the terminal device has the capability to register with multiple networks. The terminal device capability information may be described with reference to step 901 in fig. 9.

For further details of step 1101, reference may be made to the descriptions in step 901 and step 902 in fig. 9.

In step 1102, the network device determines a plurality of networks associated with the plurality of network slices according to the information of the plurality of network slices requesting access, wherein each network slice in the plurality of network slices is supported by at least one network in the plurality of networks.

For example, the plurality of networks may refer to a plurality of PLMNs. Alternatively, the plurality of networks may refer to a plurality of subnets under one PLMN, for example, the subnets may refer to non-public networks NPN. The plurality of subnets may be a plurality of subnets under the HPLMN or may be a plurality of subnets under the VPLMN.

The network device determining a plurality of networks associated with a plurality of network slices may include the following:

in an alternative case, the network device determines a network set including the above-mentioned plurality of networks, each of the plurality of network slices to which the terminal device requests access being supported by at least one of the plurality of networks in the network set, in other words, the network set includes a plurality of networks respectively supporting the plurality of network slices to which the terminal device requests access. For example, the one set of networks includes a first network supporting network slice 1 and a second network supporting network slice 2.

In an alternative case, the network device determines a plurality of network sets, wherein each of the plurality of network slices for which the terminal device requests access is supported by at least one of the plurality of networks in each of the plurality of network sets, in other words, each of the plurality of network sets includes a plurality of networks respectively supporting the plurality of network slices for which the terminal device requests access. For example, a network device determines a plurality of network sets, wherein a first network set of the plurality of network sets includes a first network and a second network. Optionally, the first network set has the highest priority among the plurality of network sets.

Alternatively, the network set in the above cases may indicate other networks than the network to which the terminal device is registered, that is, may not include the network to which the current terminal device is registered. For example, when the terminal device has registered with the first network, the network set indicates information excluding other networks than the first network.

In a possible implementation, a network device determines a plurality of networks associated with a plurality of network slices, comprising: the network equipment sends information of a plurality of network slices which the terminal equipment requests to access to the roaming preferred application function SOR-AF device; the network apparatus receives roaming preference SOR information from the SOR-AF device, and the network apparatus determines a plurality of networks based on the SOR information. That is, the SOR-AF apparatus determines a plurality of networks from information of a plurality of network slices to which the terminal device requests access, and feeds back to the network device by means of the SOR information. For example, this embodiment may be adapted to the roaming scenario described above. Details of this embodiment can be found in the description of fig. 10.

Alternatively, in another possible implementation, a network device determines a plurality of networks associated with a plurality of network slices, comprising: the network equipment acquires corresponding information, wherein the corresponding information is used for indicating the network to which the terminal equipment is allowed to register and the network slice supported by each network in the network to which the terminal equipment is allowed to register; the network device determines a plurality of networks associated with the plurality of network slices according to the corresponding information and the information of the plurality of network slices to which the terminal device requests access. For example, the network device may first obtain the S-nsai supported by the PLMN with roaming agreement from the NSSF or the locally configured information, and determine the corresponding relationship according to the S-nsai supported by the PLMN with roaming agreement and the subscription information of the terminal device. That is, the network device acquires information of the network to which the terminal device is allowed to register and the network slices supported by each of the networks to which the terminal device is allowed to register, and then determines a plurality of networks from the information of the plurality of network slices to which the terminal device requests access, each of the plurality of network slices being supported by at least one of the plurality of networks. This embodiment may be described with reference to step 903 in fig. 9.

For further details of step 1102, reference may be made to the description in step 903 in fig. 9.

In step 1103, the network device sends information associated with a plurality of networks to the terminal device. Accordingly, the terminal device receives the plurality of network-associated information from the network device.

The information associated with the plurality of networks may be as described with reference to step 904 in fig. 9.

For example, in a roaming scenario, the UDM network device may send SOR information to the terminal device, the SOR information comprising the information associated with the plurality of networks.

For example, the UDM transmits the plurality of network-associated information to the terminal device through the AMF, and the terminal device receives the plurality of network-associated information from the UDM through the AMF.

Optionally, after the network device determines the plurality of networks, the network device determines information associated with the plurality of networks, and then sends the information associated with the plurality of networks to the terminal device.

For example, the information associated with the plurality of networks indicates the plurality of networks. Or when a first network to which the terminal device is currently registered is included in the plurality of networks, the information associated with the plurality of networks includes information of at least one network other than the first network in the plurality of networks. That is, the information associated with the plurality of networks may not include a network to which the terminal device is currently registered.

As previously described, the network device may determine one or more network sets, and thus, in step 1103, the network device may send information associated with the one or more network sets to the terminal device, wherein each network set indicates a plurality of networks or at least one network of the plurality of networks other than the first network with which the terminal device is currently registered.

Additional details of the information associated with the plurality of networks may be found in the description of step 904 of fig. 9.

Further optionally, the network device further sends indication information to the terminal device indicating that the terminal device registers to the plurality of networks. The plurality of networks in the indication information may be a plurality of networks that are broadly referred to.

For further details of step 1103, reference may be made to the descriptions in steps 904 to 905 in fig. 9.

In step 1104, the terminal device registers at least one network of the plurality of networks according to the information associated with the plurality of networks.

Registering at least one of the plurality of networks refers to: if the terminal equipment is registered to a first network in the networks, the terminal equipment is registered to at least one network except the first network in the networks; or the terminal device registers with the plurality of networks.

For example, the information associated with the plurality of networks indicates the first network and the second network. When the terminal device has been registered with the first network through the above steps, the terminal device re-registers with the second network according to the received information associated with the plurality of networks. Otherwise, the terminal equipment registers to the first network and the second network according to the information of the networks.

For example, this step includes the following cases:

in an optional case, when the plurality of network information includes information of one network set including the first network and the second network, the terminal device registers to a network in the one network set. In another optional case, when the plurality of network information includes information of a plurality of network sets, the terminal device selects one of the plurality of network sets according to the plurality of network information and registers to a network of the network set, for example, the terminal device selects a first network set of the plurality of network sets and registers to a network of the first network set, the first network set including the first network and the second network. Optionally, the first network set is a network set with the highest priority among the plurality of network sets, that is, the terminal device registers to a network in the network set with the highest priority.

For example, the above description may be applied to a case where the terminal device registers to the plurality of networks directly according to the received information of the plurality of networks. In addition, the above description may also be applied to the case where the terminal device updates the operator controlled PLMN selector or assists in updating the user controlled PLMN selector according to the SOR information. Optionally, the terminal device updates the operator controlled PLMN selector or the auxiliary update user controlled PLMN selector according to the SOR information, and then registers to at least one network of the plurality of networks according to the updated operator controlled selector or the user controlled selector. For example, when the above description may also be applied to the terminal device for assisting in updating the network selector controlled by the user according to the SOR information, the terminal device prompts the user with third information according to the plurality of network information, where the third information is used to instruct the user to select a plurality of networks; and the terminal equipment receives the instruction of the user and registers to the networks according to the instruction.

For further details of step 1104, reference may be made to the description of step 906 in FIG. 9.

According to the scheme, the network equipment determines a plurality of networks capable of supporting a plurality of network slices requiring access, and sends information associated with the networks to the terminal equipment, so that the terminal equipment can register to the networks, and the terminal equipment uses the networks requiring access by the terminal equipment through the registered networks, thereby meeting the requirement of the network slices expected to be used by the terminal equipment, providing service for users better, and improving user experience.

Fig. 12 is a schematic flow interaction diagram of another method for registering with multiple networks according to the present application. The registration to the plurality of networks may be to the plurality of PLMNs or to a plurality of subnets under one PLMN. Registration to a plurality of PLMNs will be described below as an example.

The method involves interactions between the UE, AMF and UDM. When the method is used in a roaming scenario across PLMNs, the UE may be the UE in fig. 3 or fig. 4, the AMF may be the AMF in the VPLMN in fig. 3 or fig. 4, and the UDM may be the UDM in the HPLMN in fig. 3 or fig. 4. For example, the VPLMN may be any PLMN in table 3 above.

For example, the method comprises the steps of:

in step 1201, the ue sends a registration request (registration request) message to the AMF.

For example, the UE sends a registration request message to the RAN (not shown in fig. 12), which, upon receiving the registration request message, sends the registration request message to the AMF, e.g., the RAN may be the RAN located in the VPLMN in fig. 3 or fig. 4.

In the example of fig. 12, the registration request message may include UE capability information indicating that the UE has a capability to register with a plurality of networks. For example, the capability information is specifically used to indicate that a SIM in the UE has the capability to register to multiple PLMNs. The capability information may refer to the description of step 901 in fig. 9, and will not be described herein.

In the example of fig. 12, the registration request message may include information of a plurality of network slices to which the UE requests access. The information of the plurality of network slices the UE requests access to may be UE requested NSSAI. For example, the plurality of network slices to which the UE requests access are network slice 1 and network slice 2,UE requested NSSAI include S-nsai 1 identifying network slice 1 and S-nsai 2 identifying network slice 2. The information of the plurality of network slices to which the UE requests access may refer to the description of step 901 in fig. 9, which is not repeated herein.

In addition, the registration request message may further include registration type information for indicating that the type of the registration at this time is initial registration.

In step 1202, the amf sends a request message c to the UDM.

Alternatively, the request message c may include information in the above-mentioned registration request message, for example, the request message c may include at least one of UE capability information, information of a plurality of network slices to which the UE requests access, or PLMN IDs of PLMNs currently registered by the UE. For example, the information of the plurality of network slices that the UE requests access is S-nsai 1 identifying network slice 1 and S-nsai 2 identifying network slice 2.

Accordingly, the UDM receives the request message c from the AMF.

For example, the AMF may send a request message c to the UDM by calling the servicing operation of the UDM.

Optionally, after receiving the request message c, the UDM determines that the current PLMN cannot support all the plurality of network slices requested to be accessed by the UE. For example, the current PLMN is PLMN1, and as shown in Table 3 above, PLMN1 supports network slice 1 identified by S-NSSAI 1 and network slice 3 identified by S-NSSAI 3, and cannot support network slice 2 identified by S-NSSAI 1, thus triggering the UDM to perform step 1203 as follows.

In step 1203, the udm obtains information of network slices supported by each network in the network set.

Similar to fig. 9, the UDM may determine the network set and information of the network slices supported by each network in the network set, or the UDM may acquire the network set and the information of the network slices supported by each network in the network set from the SOR-AF. The method by which the UDM obtains the information of the network set and the network slices supported by each network in the network set from the SOR-AF will be described in detail with reference to fig. 13 later, and this implementation is applicable to roaming scenarios across PLMNs.

The information of the network set and the network slice supported by each network in the network set may be association information of PLMNs in the network set and the network slices supported by each PLMN. In one possible implementation, the PLMNs in the network set are PLMNs to which the UE is allowed to register. For example, a PLMN to which the UE is allowed to register refers to a PLMN to which the UE is allowed to register at the same time. That is, the network set and the information of the network slices supported by each network in the network set may have the form of a table, as shown in table 3 above. Alternatively, the network set and the information of the network slices supported by each network in the network set may include: PLMN1 (S-NSSAI 1, S-NSSAI 3), PLMN2 (S-NSSAI 2, S-NSSAI 4), PLMN3 (S-NSSAI 1, S-NSSAI 4), PLMN4 (S-NSSAI 3, S-NSSAI 5), PLMN5 (S-NSSAI 2, S-NSSAI 5). For example, PLMN1 (S-NSSAI 1, S-NSSAI 3) indicates that PLMN1 supports network slice 1 corresponding to S-NSSAI 1 and network slice 3 corresponding to S-NSSAI 3.

In another possible implementation manner, when the registration request message includes information of a plurality of network slices that the UE requests to access, a PLMN in the network set is a PLMN supporting at least one network slice of the plurality of network slices that the UE requests to access. That is, PLMNs that do not support at least one of the plurality of network slices for which the UE requests access are not included in the network set. For the above example, PLMN 4 of table 3 cannot support neither network slice 1 nor network slice 2 for which the UE requests access. Similarly, the network set and the information of the network slices supported by each network in the network set may have the form of a table, as shown in table 7. Alternatively, the network set and the information of the network slices supported by each network in the network set may include: PLMN1 (S-NSSAI 1, S-NSSAI 3), PLMN2 (S-NSSAI 2, S-NSSAI 4), PLMN3 (S-NSSAI 1, S-NSSAI 4), PLMN5 (S-NSSAI 2, S-NSSAI 5).

TABLE 7

PLMN ID	Supported network slice
PLMN1	S-NSSAI 1、S-NSSAI 3
PLMN2	S-NSSAI 2、S-NSSAI 4
PLMN3	S-NSSAI 1、S-NSSAI 4
PLMN5	S-NSSAI 2、S-NSSAI 5

For example, the UDM configures the S-nsai supported by the PLMN with roaming agreements or the UDM obtains the S-nsai supported by the PLMN with roaming agreements from the NSSF (e.g., NSSF located within HPLMN) and then determines the S-nsai supported by the PLMN that the UE is allowed to access based on the S-nsai supported by the PLMN with roaming agreements and the subscription information of the UE. The S-NSSAI supported by the PLMN that the UE is allowed to access may be as described in the foregoing table 3. It will be appreciated that when the UDM obtains the S-NSSAI supported by the PLMN with roaming agreement from the NSSF located within the HPLMN, this means that the interface or service operation between the UDM and the NSSF is to be added to the existing network architecture.

The UDM may then determine the set of networks and the network slices supported by each network in the set of networks based on the request message c.

For example, when UE capability information is included in the request message c, the UDM has the capability of registering to a plurality of PLMNs according to the UE capability information, and then determines a network set and a network slice supported by each network in the network set. Alternatively, the above-mentioned registration request message and request message c may not contain UE capability information, and the UDM may default that the UE has the capability of registering to a plurality of PLMNs, thereby performing the following operations.

Or when the request message c contains the information of the network slice which the UE requests to access, the UDM associates a plurality of networks in the network set determined by the UDM with the information of the network slice which the UE requests to access according to the information of the network slice which the UE requests to access. This is referred to in the foregoing description and will not be described in detail here.

Or when the request message c includes the PLMN ID of the PLMN currently registered by the UE, the UDM may learn the PLMN currently registered by the UE according to the PLMN ID, so as to select a network set including the PLMN currently registered by the UE and network slices supported by each PLMN in the network set. For example, if the PLMN currently registered by the UE is PLMN1, the information of the network set and the network slices supported by each network in the network set includes information of PLMN2, PLMN3, PLMN4, PLMN5 and the respective supported network slices.

Optionally, when the implementation is applicable to roaming scenarios across PLMNs, the UDM may also generate SOR information containing the above-described network set according to the above-described manner. The form of the SOR information may also be described in detail with reference to fig. 13 later.

In step 1204, the udm sends a response message d to the AMF, the response message d including the information of the network set in step 1203 and the network slices supported by each network in the network set. Accordingly, the AMF receives the response message d from the UDM.

In connection with the previous description of step 1203, in one possible implementation, the UDM may send information of the set of networks to which the UE is allowed to register and the network slices supported by each network in the set of networks via the response message d of step 1204. That is, the networks in the network set are networks to which the UE is allowed to register.

Alternatively, in another possible implementation, the UDM may send the network set supporting at least one network slice of the plurality of network slices that the UE requests access and the information of the network slices supported by each network in the network set through the response message d of step 1204. That is, each network in the network set is capable of supporting at least one of a plurality of network slices for which access is requested by the UE, and the UDM transmits individual network slices supported by such networks (including, but not limited to, network slices for which access is requested by the UE supported by the network) via a response message. Further optionally, the set of networks sent by the UDM does not include information of the network to which the UE is currently registered.

Optionally, the UDM further sends indication information to the AMF, the indication information being used to indicate that the UE is registered to the plurality of PLMNs. For example, the UDM may send the information and the indication information of the network slices supported by the network set and each network in the network set to the AMF through the response message d of step 1204.

In step 1205, the amf sends a registration accept message to the UE, where the registration accept message includes the network set and the information of the network slices supported by each network in the network set.

Optionally, the registration accept message further includes at least one of an allowed nsai and a rejected nsai. Alternatively, the message sent by the AMF to the UE in step 905 may be a registration rejection message (not shown in the figure), where the registration rejection message includes the information of the network set and the network slice supported by each network in the network set. In addition to the content contained in the message being a collection of networks and the network slices supported by each network in the collection of networks, further details of this step may be found in the description of step 905 of fig. 9.

For example, the AMF sends a registration accept message/registration reject message to the RAN (not shown in fig. 12), which, upon receipt of the registration accept message, sends the registration accept message/registration reject message to the UE.

In step 1206, the UE selects a plurality of networks associated with a plurality of network slices to which the UE is to access.

In a first possible implementation, when the UE receives the information of the network set that allows the UE to register and the network slices supported by each network in the network set through step 1205, the UE may select a plurality of PLMNs supporting each of the plurality of network slices to be accessed by the UE according to the information of the plurality of network slices to be accessed by the UE and the information of the network slices supported by each network in the network set.

For example, the UE receives the information of the network set and the network slices supported by each network in the network set, as shown in table 3 above. The plurality of network slices to be accessed by the UE are network slice 1 and network slice 2, and the UE may select PLMN1 and PLMN2, or may select PLMN1 and PLMN5, or may select PLMN2 and PLMN3, or may select PLMN3 and PLMN5.

In a second possible implementation, when the UE receives the network set of at least one network slice supporting the plurality of network slices requested to be accessed by the UE and the information of the network slices supported by each network in the network set through step 1205, the UE may select a plurality of PLMNs supporting each of the plurality of network slices to be accessed by the UE according to the information of the plurality of network slices to be accessed by the UE.

For example, the UE may select PLMN1 and PLMN2, or may select PLMN1 and PLMN5, or may select PLMN2 and PLMN3, or may select PLMN3 and PLMN5, or may select PLMN3, or may select PLMN5, and PLMN2, or may select PLMN2, or PLMN2, which may select PLMN2, or may select PLMN2, which is a network slice.

That is, the operation of the UE is similar whether or not the networks in the network set are capable of supporting at least one of the plurality of network slices for which the UE requests access. In other words, the UE may not be aware of whether a network in the received set of networks is capable of supporting at least one network slice of the plurality of network slices that the UE requested access.

In step 1207, the ue registers with at least one network of the plurality of networks.

For example, the UE registers with at least one network of the plurality of networks according to the plurality of networks associated with the plurality of network slices to be accessed by the UE selected in step 1206.

It should be noted that, if the UE has already registered to the first PLMN in the PLMNs through the registration procedures of steps 1201 to 1205, the UE only needs to additionally register to other PLMNs except the first PLMN in the PLMNs; otherwise, the UE may additionally register with the multiple PLMNs.

For example, assuming that the UE selects to register with PLMN1 and PLMN2, if the UE has already been registered with PLMN1, the UE will only register with PLMN2 additionally, and similarly, if the UE has already registered with PLMN2 through the above-mentioned registration procedure, the UE will only register with PLMN1 additionally. If the UE is currently registered to PLMN3, PLMN4 or PLMN5, the UE re-registers to PLMN1 and PLMN2. In this case, the UE may be unregistered from the current PLMN.

In either of the above ways, the UE eventually registers with multiple PLMNs that can support multiple network slices to be accessed by the UE. After the UE registers to the PLMNs, the requested network slices may be used by the registered PLMNs. For example, when the UE wants to use the service provided by the network slice 2, a session corresponding to the network slice 2 is established, and then the network slice 2 is accessed through the session.

According to the method, the UE can register to the PLMNs according to the network slices to be accessed, so that the network slices to be accessed by the UE can be used under the combination of the PLMNs, the requirement of the network slices expected to be used by the UE is met, services are better provided for users, and user experience is improved.

As mentioned above, the method may also be applicable to scenarios with multiple subnets within the same PLMN (HPLMN or VPLMN). The method in this scenario also involves interactions between the UE, AMF and UDM. The UE may be the UE in fig. 5 or fig. 6, the AMF may be the AMF in the NPN in fig. 5, or the AMF in the NPN1 in fig. 6, and the UDM may be the UDM in fig. 5 or fig. 6. Similarly, the UDM may obtain a network set and information of network slices supported by each network in the network set, where the network set includes a plurality of subnets, and the information of network slices supported by each network in the network set is information of network slices supported by the plurality of subnets. The network set herein may include an identification of a plurality of subnets (e.g., NPNs). Optionally, the network set may further include an identifier of the PLMN corresponding to each subnet. For example, the UDM may obtain a correspondence between each subnet identifier and S-nsai supported by the subnet, or a correspondence between each subnet identifier and the identifier of the PLMN where the subnet is located and S-nsai supported by the subnet. And when the UE receives the information of the network set and the network slices supported by each network in the network set, selecting a plurality of subnets supporting a plurality of network slices to be accessed by the UE, registering the plurality of subnets, and using the plurality of network slices to be accessed through the registered plurality of subnets. Therefore, a plurality of network slices to be accessed by the UE can be used under the combination of a plurality of subnets, so that the requirement of the network slices expected to be used by the UE is met, the service is better provided for the user, and the user experience is improved.

As described above, when the method is applied to a scenario across PLMNs, the network set and the information of the network slices supported by each network in the network set may be implemented by means of SOR information, where the SOR information may be generated by the UDM or may request SOR-AF generation by the UDM. Fig. 13 will be described taking UDM request SOR-AF generation SOR information as an example. Fig. 13 will be described in connection with fig. 12. For example, the method may comprise the steps of:

in step 1301, the UDM sends a request message e to the SOR-AF. For example, the request message e may be information included in the request message c of step 1202 in fig. 12.

For example, if the subscription information of the UE indicates: the SOR information is provided to the UE in case of an initial registration of a VPLMN, and the UDM determines that the SOR information is to be acquired, and then performs step 1301 described above.

For example, the UDM may send information of a plurality of network slices to which the UE requests access to the SOR-AF through a request message e. For example, the information of the plurality of network slices to which the UE requests access may be the information of the plurality of network slices to which the UE requests access included in the request message c of step 1202 in fig. 12.

For example, the UDM may send UE capability information to the SOR-AF through a request message e. For example, the UE capability information may be UE capability information included in the request message c of step 1202 in fig. 12.

In addition, the UDM may also send the PLMN ID of the PLMN currently registered by the UE to the SOR-AF via the request message e. For example, the PLMN ID of the PLMN currently registered by the UE may be the PLMN ID of the PLMN currently registered by the UE included in the request message c of step 1202 in fig. 12.

In step 1302, the SOR-AF generates SOR information from the information in the request message e, which may indicate the set of networks and the network slices supported by each network in the set of networks. The collection of networks and the network slices supported by each network in the collection of networks may be described with reference to step 1203 in fig. 12.

For example, SOR-AF is configured with S-NSSAI supported by PLMN of roaming agreement; alternatively, the SOR-AF obtains from the NSSF the S-nsai supported by the PLMN with roaming agreement. Then, the SOR-AF determines the S-NSSAI supported by the PLMN allowing the UE to access according to the S-NSSAI supported by the PLMN with roaming agreement and the subscription information of the UE, and further generates SOR information according to the S-NSSAI supported by each PLMN.

The SOR information may have any of the following forms:

first form: the SOR information includes the set of networks that the UE is allowed to register with and the network slices supported by each network in the set of networks, as shown in table 3 above. PLMN1, PLMN2, PLMN3, PLMN4 and PLMN5 in table 3 are PLMNs that the UE can register, and the UE is allowed to register with any two or more of these five PLMNs. For example, when the UE registers with PLMN1 and PLMN2, the UE may use network slices S-nsai 1 and S-nsai 3 supported by PLMN1, and network slices S-nsai 2 and S-nsai 4 supported by PLMN 2.

That is, the SOR information may be generated without regard to a plurality of network slices that the UE requests access to. In this case, the request message e in the aforementioned step 1301 may not carry the plurality of network slice information that the UE requests access to.

Second form: the SOR information includes a set of networks that the UE is allowed to register with and a network slice supported by each network in the set of networks, and each network in the set of networks supports at least one network slice that the UE requests access to.

For example, when the request message e carries a plurality of network slice information that the UE requests to access, the generation of the SOR information further considers a plurality of network slices that the UE requests to access, relative to the first form described above. That is, the SOR-AF may screen PLMNs capable of supporting at least one of a plurality of network slices to which the UE requests access according to the plurality of network slices to which the UE requests access, and provide only association information of such PLMNs and the network slices supported by the PLMNs. For the above example, PLMN 4 of table 3 cannot support neither network slice 1 nor network slice 2 for which the UE requests access. Thus, SOR information may be as shown in table 7 above.

Optionally, the UE capability information is carried in the request message e, and the SOR-AF may determine that the UE has a capability of accessing to multiple PLMNs according to the carrying UE capability information, so as to determine the SOR information. Alternatively, the UE capability information may not be carried in the request message e, and the SOR-AF defaults to the UE having the capability of registering with multiple PLMNs, thereby generating SOR information.

Regardless of which form the association information of the network with the respective supporting network slice is in, several of the above SOR information may be presented as a list of preferred PLMNs or combinations of access technologies, or as a security packet resulting from security encapsulation of such information.

In step 1303, the SOR-AF sends the SOR information to the UDM.

Accordingly, the UDM receives the SOR information from the SOR-AF, determines a network set and a network slice supported by each network in the network set according to the SOR information, and then performs step 1204 as shown in fig. 12, i.e., transmits the information of the network set and the network slice supported by each network in the network set to the UE through steps 1204 and 1205 in fig. 12. After receiving the SOR information, the UE selects a plurality of networks associated with a plurality of network slices to be accessed by the UE, via step 1206, and registers with at least one of the plurality of networks, via step 1207.

For example, the UE selecting, according to the SOR information, a plurality of networks associated with a plurality of network slices to be accessed by the UE may be implemented as follows:

the UE is used for assisting in updating a PLMN selector controlled by a user or updating a PLMN selector controlled by an operator according to the received SOR information. The UE then performs PLMN selection according to the selector. The principle of how the UE updates the operator controlled PLMN selector and the user controlled PLMN selector according to the SOR information is similar will be described below by taking the example of the UE updating the operator controlled PLMN selector according to the SOR information.

For example, when the SOR information has the first form described in step 1302, that is, the SOR information includes information of a network set that allows the UE to register and network slices supported by each network in the network set, as shown in the above table 3, the UE updates the operator controlled PLMN selector according to the SOR information, and the UE selects a plurality of PLMNs according to the updated operator controlled PLMN selector and the plurality of network slice information to be accessed. For example, updated operator controlled PLMN selectors are shown in table 8. For example, PLMN1 (S-NSSAI 1, S-NSSAI 3) indicates that PLMN1 supports network slice 1 corresponding to S-NSSAI 1 and network slice 3 corresponding to S-NSSAI 3.

TABLE 8

Operator controlled PLMN selector
PLMN1(S-NSSAI 1、S-NSSAI 3)

PLMN2(S-NSSAI 2、S-NSSAI 4)
PLMN3(S-NSSAI 1、S-NSSAI 4)
PLMN4(S-NSSAI 3、S-NSSAI 5)
PLMN5(S-NSSAI 2、S-NSSAI 5)

For example, the plurality of network slices to be accessed by the UE are network slice 1 and network slice 2, and the UE may select PLMN1 and PLMN2, or may select PLMN1 and PLMN5, or may select PLMN2 and PLMN3, or may select PLMN3 and PLMN5. Assuming that the UE selects PLMN1 and PLMN2, if the UE is currently registered with PLMN1, the UE is additionally registered with PLMN2, and similarly, if the UE is registered with PLMN2 through the above-mentioned registration procedure, the UE is additionally registered with PLMN1. If the UE is currently registered to PLMN3, PLMN4 or PLMN5, the UE re-registers to PLMN1 and PLMN2. In this case, the UE may be unregistered from the current PLMN.

Optionally, PLMNs in the operator controlled PLMN selector are ranked according to a descending priority. The UE may select a plurality of PLMNs with relatively highest priority, i.e. PLMN1 and PLMN2, according to a plurality of network slices to be accessed.

Optionally, the UE may also select a plurality of PLMNs taking into account PLMNs to which the UE has currently registered, i.e. select a plurality of PLMNs including PLMNs to which the UE has currently registered. For example, if the slices to be accessed by the UE are network slice 1 and network slice 2, and the UE has been registered to PLMN1 through the above registration procedure, the UE may select PLMN1 and PLMN2 or select PLMN1 and PLMN5, that is, the UE may additionally register to PLMN2 or PLMN5. Further optionally, the UE may also select a PLMN taking into account the priorities in the PLMN selector controlled by the operator, the PLMN, and the current PLMN to which the UE is to be connected, and a plurality of network slices, for example, the UE may select PLMN1 and PLMN2.

When the SOR information has the second form described in step 1302, as shown in table 7 above, the UE updates the operator controlled PLMN selector according to the SOR information, and the UE selects a plurality of PLMNs according to the updated operator controlled PLMN selector. For example, updated operator controlled PLMN selectors are shown in table 9. For example, PLMN1 (S-NSSAI 1, S-NSSAI 3) indicates that PLMN1 supports network slice 1 corresponding to S-NSSAI 1 and network slice 3 corresponding to S-NSSAI 3.

TABLE 9

Operator controlled PLMN selector
PLMN1(S-NSSAI 1、S-NSSAI 3)
PLMN2(S-NSSAI 2、S-NSSAI 4)
PLMN3(S-NSSAI 1、S-NSSAI 4)
PLMN5(S-NSSAI 2、S-NSSAI 5)

For example, the UE may select a PLMN in combination with tables 4 and 9 above. For example, when the above registration procedure is performed in PLMN1, the S-nsai 1 corresponding to the network slice 1 to which the UE is to access is already included in the allowed nsai, which indicates that the UE may use network slice 1 in PLMN1, but the S-nsai 2 corresponding to the network slice 2 to which the UE is to access is included in the rejected nsai, which indicates that the UE may not use network slice 2 in PLMN 1. Then the UE further selects a PLMN for network slice 2, i.e. a PLMN supporting network slice 2. As can be seen from table 9, PLMN2 and PLMN5 support network slice 2, then the UE may select PLMN2 or PLMN5 registration. Alternatively, PLMNs in the operator controlled PLMN selector are ranked according to a descending priority order. The UE may select a PLMN with a high priority, i.e. select registration to PLMN2.

When the above registration procedure is performed in PLMN2, PLMN3 or PLMN5, the operation of the UE is similar, and will not be described here again. When the above registration procedure is performed in PLMN4, the S-nsai 1 corresponding to the network slice 1 and the S-nsai 2 corresponding to the network slice 2, which the UE requests to access, are both included in the rejected nsai, which indicates that the UE may not use the network slice 1 and the network slice 2 in PLMN 4. Then the UE selects one PLMN for network slice 1 and one PLMN for network slice 2. As can be seen from table 9, PLMN1 and PLMN3 support network slice 1, PLMN2 and PLMN5 support network slice 2, then the UE may select one PLMN from PLMN1 and PLMN3, and one PLMN from PLMN2 and PLMN 5. Alternatively, PLMNs in the operator controlled PLMN selector are ranked according to a descending priority order. The UE may select a PLMN with a high priority, i.e. select registration to PLMN1 and PLMN2.

Alternatively, the UE may select the PLMN directly from table 9. For example, when the above registration procedure is performed in PLMN1, since PLMN1 supports network slice 1, network slice 2 is not supported. Then the UE further selects a PLMN for network slice 2, i.e. a PLMN supporting network slice 2. As can be seen from table 9, PLMN2 and PLMN5 support network slice 2, then the UE may select PLMN2 or PLMN5 registration. Alternatively, PLMNs in the operator controlled PLMN selector are ranked according to a descending priority order. The UE may select a PLMN with a high priority, i.e. to re-register to PLMN2. When the above registration procedure is performed in other PLMNs, the operation of the UE is similar and will not be described here again.

When the UE registers to the plurality of PLMNs, a desired plurality of network slices may be used by the registered PLMNs.

By the method, the UE can update the PLMN selector controlled by the user or update the PLMN selector controlled by the operator in an auxiliary manner according to the received SOR information, when the UE selects the PLMN according to the updated selector, the UE has the opportunity to register to a plurality of PLMNs, so that a plurality of network slices to be accessed by the UE can be used by combining the PLMNs, the requirement of the network slices expected to be used by the UE is met, the service is better provided for the user, and the user experience is improved.

Fig. 14 is another flow interaction diagram of another method for registering with multiple networks according to the present application. The schematic will be described in connection with the steps in fig. 12 and 13. Fig. 14 relates to interactions between a network device and a terminal device. For example, the terminal device may be the UE in fig. 12, and the network device may be the UDM in fig. 12 or fig. 13. Alternatively, the interaction may also involve an AMF, which may be the AMF in fig. 12. For example, the method comprises the steps of:

in step 1401, the terminal device sends a registration request message to the network device. Accordingly, the network device receives the registration request message from the terminal device.

For example, the network device may be a UDM. The UDM may receive the above-described registration request message from the terminal device through the AMF.

For example, the registration request message may include information of a plurality of network slices requested to be accessed by the terminal device, and the information of the plurality of network slices requested to be accessed may be requested NSSAI of the terminal device. For example, the plurality of network slices to which the terminal device requests access are network slice 1 and network slice 2, and the terminal device requested NSSAI includes S-NSSAI 1 of network slice 1 and S-NSSAI 2 of network slice 2. The information of the plurality of network slices requesting access may be described with reference to step 1201 in fig. 12.

For example, the registration request message may include terminal device capability information. The capability information indicates that the terminal device has the capability of registering with a plurality of networks. For example, the capability information is specifically used to indicate that a SIM card in the terminal device has the capability to register with multiple networks. The terminal device capability information may be described with reference to step 1201 in fig. 12.

For further details of step 1401, reference may be made to the descriptions in step 1201 and step 1202 in fig. 12.

Step 1402, the network device determines first information, where the first information is used to indicate a set of networks and network slices supported by each network in the set of networks.

For example, the first information includes association information between the respective network and the network slice supported by each network. For example, the first information may be in the form of a list, as shown in fig. 3 or fig. 7. For example, the network set may refer to a PLMN set. Alternatively, the network set may refer to a set of subnets under one PLMN, e.g., the subnets may refer to non-public network NPN. The plurality of subnets may be a plurality of subnets under the HPLMN or may be a plurality of subnets under the VPLMN.

In an alternative case, the first information may include a set of networks to which the terminal device is allowed to register and a network slice supported by each network in the set of networks. That is, the networks in the network set in the first information are networks to which the terminal device is permitted to register. In this case, the registration request message may not carry information of a plurality of network slices to which the terminal device requests access. That is, the network device may determine the first information without considering information of a plurality of network slices to which the terminal device requests access. This step may be described with reference to step 1203 in fig. 12.

Alternatively, the first information may include a set of networks to which the terminal device is allowed to register and network slices supported by each network in the set of networks, and each network in the set of networks supports at least one network slice of a plurality of network slices to which the terminal device requests access. That is, the network in the network set in the first information is a network to which the terminal device is allowed to register, and the network is capable of supporting at least one network slice of a plurality of network slices to which the terminal device requests access. The case is a subset of the last case in which each network in the set of networks supports at least one network slice of the plurality of network slices for which the terminal device requests access. For example, the network set includes a first network supporting a network slice 1 to which the terminal device requests access and a second network supporting a network slice 2 to which the terminal device requests access, the network set not including networks that cannot support neither the network slice 1 nor the network slice 2. In this case, the registration request message carries information of a plurality of network slices to which the terminal device requests access.

Alternatively, the set of networks in the first information in the above several cases may indicate other networks than the network to which the terminal device has registered, that is, may not include the network to which the terminal device has registered. For example, when the terminal device has registered with the first network, the first information includes information excluding other networks than the first network.

In a possible implementation manner, the network device determines first information, including: the network equipment acquires corresponding information, wherein the corresponding information is used for indicating the network to which the terminal equipment is allowed to register and the network slice supported by each network in the network to which the terminal equipment is allowed to register; the network device determines the first information according to the corresponding information, optionally further according to the information carried in the registration request message. For example, the network device may first obtain the S-nsai supported by the PLMN with the roaming agreement from the NSSF or the locally configured information, and determine the corresponding relationship according to the S-nsai supported by the PLMN with the roaming agreement and the subscription information of the terminal device. That is, the network device knows the information of the network to which the terminal device is permitted to register and the network slice supported by each of the networks to which the terminal device is permitted to register, and then presents the information of the network to which the terminal device is permitted to register and the network slice supported by each of the networks to which the terminal device is permitted to register in the form of the first information. For details of this embodiment reference is made to the description of step 1203 in fig. 12.

In another possible implementation, the network device determining the first information includes: the network equipment sends a request message to the SOR-AF device of the roaming preferred application function, and the request message carries information carried in a registration request message optionally; the network device receives roaming preference SOR information from the SOR-AF device, and the network device determines first information according to the SOR information. That is, the SOR-AF apparatus generates first information and feeds back to the network device by way of the SOR information, and the network device determines the first information according to the SOR information. For example, this embodiment is applicable to a cross PLMN scenario. Details of this embodiment can be found in the description of fig. 13.

In a possible implementation manner, the network device determines the first information, and further includes: the network device determines first information according to a first network currently registered by the terminal device, wherein the network set in the first information comprises at least one network except the first network. That is, after the network device determines a plurality of networks associated with a plurality of network slices, the network currently registered by the terminal device may be removed to determine the first information.

For further details of step 1402, reference may be made to the description in step 1203 of FIG. 12.

Step 1403, the network device sends the first information to the terminal device. Correspondingly, the terminal device receives the first information from the network device.

The first information indicates a set of networks and information of network slices supported by each network in the set of networks. The information of the network set and the network slice supported by each network in the network set can refer to the description of step 1203 in fig. 12.

For example, the UDM transmits SOR information to the terminal device, the SOR information including the first information.

For example, the UDM transmits the first information to the terminal device through the AMF, and the terminal device receives the first information from the UDM through the AMF.

Further optionally, the network device sends to the terminal device indication information further comprising an indication that the terminal device registers with a plurality of networks.

For further details of this step, reference may be made to the descriptions in steps 1204-1205 in fig. 12.

In step 1404, the terminal device selects a plurality of networks associated with a plurality of network slices to be accessed from a set of networks in the first information, wherein each network slice of the plurality of network slices is supported by at least one network of the plurality of networks.

For example, the plurality of network slices to be accessed by the terminal device includes a first network slice and a second network slice, the terminal device selects the first network supporting the first network slice, and selects the second network supporting the second network slice.

For example, the above description may be applied to a case where the terminal device performs selection of a plurality of networks directly from the received first information. In addition to this, the above description can also be applied to the case where the terminal device updates the operator-controlled network selector or assists in updating the user-controlled network selector according to the SOR information. Optionally, the terminal device updates the operator-controlled PLMN selector or the auxiliary update user-controlled PLMN selector according to the SOR information, and then selects the plurality of networks according to the updated operator-controlled selector or the user-controlled selector. When the above description may also be applied to the terminal device for assisting in updating the network selector controlled by the user according to the SOR information, optionally, the terminal device prompts the user with third information according to the received SOR information, where the third information is used to instruct the user to select multiple networks; and the terminal equipment receives the instruction of the user and selects the networks according to the instruction.

For further details regarding this step, reference may be made to the description of step 1206 in FIG. 12.

In step 1405, the terminal device registers with at least one of the plurality of networks.

For example, taking the above example as an example, when the terminal device has registered with the first network through the above steps, the terminal device re-registers with the second network according to the selected plurality of networks. Otherwise, the terminal equipment registers to the first network and the second network according to the selected multiple networks.

For further details of this step, reference is made to the description of step 1207 in FIG. 12.

According to the method, the terminal equipment can register to the networks according to the network slices to be accessed, so that the network slices to be accessed by the terminal equipment can be used under the combination of the networks, the requirement of the network slices expected to be used by the terminal equipment is met, services are better provided for users, and user experience is improved.

It should be noted that, each message in the above figures may have other names. In addition, the information transfer between the network elements may also be implemented by calling the network functions of the network elements under the service architecture, which is not limited in this invention.

In addition, in the embodiments shown in fig. 9 to 14, the UDM may store context information of different networks separately, and the context information corresponding to each network includes an Identifier (ID) of a service AMF (serving AMF). In the following, a network is described as an example of a PLMN, and a subnet under the same PLMN is similar to the PLMN. When a UE registers with a PLMN, the AMF of the service provides access management services for the UE. That is, the UDM stores association information of AMFs of different PLMNs and their corresponding services, as shown in table 10:

Table 10

PLMN ID	AMF ID
PLMN1	AMF6
PLMN2	AMF7
PLMN3	AMF8

When the UE registers to the first PLMN and subsequently registers to the second PLMN, if the two PLMNs belong to PLMNs that the UDM allows the UE to register, the UDM will not perform a deregistration operation on the AMF of the service associated with the first PLMN, that is, the UDM will keep the AMF of the service associated with the first PLMN in a registered state. If the PLMN currently registered by the UE is PLMN1 and subsequently registered to PLMN2, the UDM stores the service AMF IDs corresponding to PLMN1 and PLMN2, and does not register AMF6 corresponding to PLMN 1.

The scheme provided by the embodiment of the application is mainly introduced from the interaction angle among the network elements. Correspondingly, the embodiment of the application also provides a communication device, which can be the terminal equipment in the embodiment of the method, or a device containing the terminal equipment, or a component applicable to the terminal equipment; alternatively, the communication apparatus may be a network device in the above method embodiment, or an apparatus including the above network device, or a component that may be used in the network device. It will be appreciated that the communication device, in order to achieve the above-described functions, comprises corresponding hardware structures and/or software modules performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

Turning to fig. 7, fig. 7 is a schematic diagram of a communication device according to an embodiment of the present application.

The communication device comprises a processing module 701, a receiving module 702 and a transmitting module 703. The processing module 701 is configured to implement processing of data by the communication device. The receiving module 702 is configured to receive contents of a communication device and other units or network elements, and the sending module 703 is configured to receive contents of a communication device and other units or network elements. It is to be appreciated that the processing module 701 in embodiments of the present application may be implemented by a processor or processor-related circuit component (alternatively referred to as a processing circuit), and the receiving module 702 may be implemented by a receiver or receiver-related circuit component. The transmit module 703 may be implemented by a transmitter or transmitter related circuit components.

The communication device may be a communication device apparatus, a chip applied in the communication device apparatus, or other combination devices, components, etc. having the functions of the communication device apparatus.

The communication device may be a network device or UDM of any of fig. 9 to 14, or may be an AMF of fig. 9, 11, 12 or 14, or may be an SOR-AF of fig. 10 or 13, or may be a UE of fig. 9, 11, 12 or 14.

When the communication apparatus is a network device or UDM, the receiving module 702 is configured to obtain information of a plurality of network slices that the terminal device requests to access (e.g. steps 902 and 902 in fig. 9, and step 1101 in fig. 11). The processing module 701 is configured to determine a plurality of networks (e.g., step 903 in fig. 9, steps 1001-1003 in fig. 10, step 1102 in fig. 11) associated with a plurality of network slices, wherein each network slice of the plurality of network slices is supported by at least one network of the plurality of networks. The transmitting module 703 is configured to transmit information associated with a plurality of networks to which the terminal device is registered (for example, steps 904 and 905 in fig. 9, step 1103 in fig. 11) to the terminal device.

Alternatively, the receiving module 702 is configured to obtain information of a plurality of network slices that the terminal device requests to access (for example, steps 1201 and 1202 in fig. 12, step 1401 in fig. 14). The processing module 701 is configured to determine first information (for example, step 1203 in fig. 12, steps 1301 to 1303 in fig. 13, and step 1402 in fig. 14) according to information of a plurality of network slices requested to be accessed by the terminal device, where the first information is used to indicate a network set and network slices supported by each network in the network set, and each network in the network set supports at least one network slice of the plurality of network slices requested to be accessed by the terminal device. The sending module 703 is configured to send the first information to a terminal device (e.g. steps 1204 and 1205 in fig. 12, step 1403 in fig. 14).

Alternatively, the receiving module 702 is configured to obtain capability information of the terminal device, where the capability information indicates that the terminal device has a capability of registering with a plurality of networks (e.g., steps 1201 and 1202 in fig. 12, step 1401 in fig. 14). The processing module 701 is configured to determine, in a case where the terminal device has a capability of registering with a plurality of networks, first information (for example, step 1203 in fig. 12, steps 1301 to 1303 in fig. 13, step 1402 in fig. 14), the first information indicating a network set and a network slice supported by each network in the network set. The sending module 703 is configured to send the first information (e.g. steps 1204 and 1205 in fig. 12, step 1403 in fig. 14) to the terminal device, where the first information is used for registering the terminal device with a plurality of networks in the network set.

Furthermore, the various modules described above may also be used in other processes that support the techniques described herein. The advantages are described above and will not be repeated here.

When the communication apparatus is a UE, the sending module 703 is configured to send information of a plurality of network slices that the terminal device requests to access to the network device (for example, steps 901 and 902 in fig. 9 and step 1101 in fig. 11). The receiving module 702 is configured to receive information of a plurality of networks associated with a plurality of network slices from a network device (e.g., steps 904 and 905 in fig. 9, step 1103 in fig. 11). The processing module 701 is configured to register at least one network of the plurality of networks according to the information of the plurality of networks (e.g., step 906 in fig. 9, step 1104 in fig. 11).

Alternatively, the receiving module 702 is configured to receive first information from a network device, where the first information is used to indicate a network set and a network slice supported by each network in the network set (e.g., steps 1204 and 1205 in fig. 12, and step 1403 in fig. 14). The processing module 701 is configured to select a plurality of networks associated with a plurality of network slices to be accessed by the terminal device from the network set (e.g. step 1206 in fig. 12 and step 1404 in fig. 14), and register with at least one network of the plurality of networks (e.g. step 1207 in fig. 12 and step 1405 in fig. 14).

When the communication device is an AMF, the receiving module 702 is configured to perform steps 901 and 904 in fig. 9, and steps 1201 and 1204 in fig. 12; the sending module 703 is configured to perform steps 902 and 905 in fig. 9, and steps 1204 and 1205 in fig. 12. Furthermore, the various modules described above may also be used in other processes that support the techniques described herein. The advantages are described above and will not be repeated here.

When the communication apparatus is an SOR-AF, the receiving module 702 is configured to receive, from a network device, information of a plurality of network slices to which the terminal device requests access (e.g., step 1001 in fig. 10, step 1301 in fig. 13); the processing module 701 is configured to generate roaming preference SOR information according to information of a plurality of network slices that the terminal device requests to access (e.g. step 1002 in fig. 10, step 1302 in fig. 13); the sending module 703 is configured to send SOR information to a network device (e.g. step 1003 in fig. 10, step 1303 in fig. 13). The SOR information may indicate a plurality of networks, wherein each network slice of the plurality of network slices is supported by at least one network of the plurality of networks. Alternatively, the SOR information may indicate a set of networks and network slices supported by each network in the set of networks, wherein each network in the set of networks supports at least one of a plurality of network slices for which the terminal device requests access. Furthermore, the various modules described above may also be used in other processes that support the techniques described herein. The advantages are described above and will not be repeated here.

Fig. 8 is a schematic diagram of another communication device according to an embodiment of the present application, where the communication device includes: a processor 801, a communication interface 802, and a memory 803. Wherein the processor 801, the communication interface 802, and the memory 803 may be interconnected by a bus 804; bus 804 may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The bus 804 may be classified into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one line is shown in fig. 8, but not only one bus or one type of bus. The processor 801 may be a central processing unit (central processing unit, CPU), a network processor (network processor, NP) or a combination of CPU and NP. The processor may further comprise a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (programmable logic device, PLD), or a combination thereof. The PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), general-purpose array logic (Generic Array Logic, GAL), or any combination thereof. The memory 803 may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache.

The communication means may be, for example, a network device UDM in any of fig. 9 to 14, an AMF in fig. 9, 11, 12 or 14, an SOR-AF in fig. 10 or 13, or a UE in fig. 9, 11, 12 or 14.

The processor 801 is configured to implement a data processing operation of the communication apparatus, and the communication interface 802 is configured to implement a receiving operation and a transmitting operation of the communication apparatus.

When the communication device is a UDM, the communication interface 802 is used to obtain information of a plurality of network slices to which the terminal device requests access (e.g., steps 902 and 902 in fig. 9, step 1101 in fig. 11). The processor 801 is configured to determine a plurality of networks (e.g., step 903 in fig. 9, steps 1001-1003 in fig. 10, step 1102 in fig. 11) associated with a plurality of network slices, wherein each network slice of the plurality of network slices is supported by at least one network of the plurality of networks. The communication interface 802 is configured to send information associated with a plurality of networks to which the terminal device is registered (e.g., steps 904 and 905 in fig. 9, step 1103 in fig. 11) to the terminal device.

Alternatively, the communication interface 802 is used to obtain information of a plurality of network slices (e.g. steps 1201 and 1202 in fig. 12, step 1401 in fig. 14) that the terminal device requests access. The processor 801 is configured to determine first information (e.g. step 1203 in fig. 12, steps 1301 to 1303 in fig. 13, step 1402 in fig. 14) according to information of a plurality of network slices requested to be accessed by the terminal device, where the first information is used to indicate a network set and network slices supported by each network in the network set, and each network in the network set supports at least one network slice of the plurality of network slices requested to be accessed by the terminal device. The communication interface 802 is used to send the first information to the terminal device (e.g. steps 1204 and 1205 in fig. 12, step 1403 in fig. 14).

Alternatively, the communication interface 802 is used to acquire capability information of the terminal device, which indicates that the terminal device has the capability of registering with a plurality of networks (e.g., steps 1201 and 1202 in fig. 12, step 1401 in fig. 14). The processor 801 is configured to determine, in a case where the terminal device has the capability of registering with a plurality of networks, first information (for example, step 1203 in fig. 12, steps 1301 to 1303 in fig. 13, step 1402 in fig. 14) indicating a network set and a network slice supported by each network in the network set. The communication interface 802 is configured to send the first information (e.g., steps 1204 and 1205 in fig. 12, step 1403 in fig. 14) to the terminal device, where the first information is used for registration of the terminal device with a plurality of networks in the network set.

When the communication apparatus is a UE, the communication interface 802 is configured to send information of a plurality of network slices to which the terminal device requests access to the network device (e.g., steps 901 and 902 in fig. 9, and step 1101 in fig. 11). The communication interface 802 is used to receive information of a plurality of networks associated with a plurality of network slices from a network device (e.g., steps 904 and 905 in fig. 9, step 1103 in fig. 11). The processor 801 is configured to register with at least one network of the plurality of networks based on the information of the plurality of networks (e.g., step 906 in fig. 9, step 1104 in fig. 11).

Alternatively, the communication interface 802 is configured to receive first information from the network device, the first information being configured to indicate the set of networks and the network slices supported by each network in the set of networks (e.g., steps 1204 and 1205 in fig. 12, step 1403 in fig. 14). The processor 801 is configured to select a plurality of networks (e.g., step 1206 in fig. 12 or step 1404 in fig. 14) associated with a plurality of network slices to be accessed by the terminal device from the set of networks, and register with at least one of the plurality of networks (e.g., step 1207 in fig. 12 or step 1405 in fig. 14).

When the communication device is an AMF, the communication interface 802 is used to perform steps 901 and 904 in fig. 9, and steps 1201 and 1204 in fig. 12; the communication interface 802 is used to perform steps 902 and 905 in fig. 9, and steps 1204 and 1205 in fig. 12. Furthermore, the various modules described above may also be used in other processes that support the techniques described herein. The advantages are described above and will not be repeated here.

When the communication apparatus is an SOR-AF, the communication interface 802 is configured to receive, from the network device, information of a plurality of network slices to which the terminal device requests access (e.g., step 1001 in fig. 10, step 1301 in fig. 13); the processor 801 is configured to generate roaming preference SOR information according to information of a plurality of network slices to which the terminal device requests access (e.g., step 1002 in fig. 10, step 1302 in fig. 13); the communication interface 802 is used to send SOR information to a network device (e.g., step 1003 in fig. 10, step 1303 in fig. 13). The SOR information may indicate a plurality of networks, wherein each network slice of the plurality of network slices is supported by at least one network of the plurality of networks. Alternatively, the SOR information may indicate a set of networks and network slices supported by each network in the set of networks, wherein each network in the set of networks supports at least one of a plurality of network slices for which the terminal device requests access. Furthermore, the various modules described above may also be used in other processes that support the techniques described herein. The advantages are described above and will not be repeated here.

An embodiment of the present application provides a communication system, which includes the foregoing network device (e.g., UDM) and a terminal device (e.g., UE), where the network device performs a method performed by the UDM in any one of the embodiments shown in fig. 9 to 11, and the terminal device performs a method performed by the UE in the embodiment shown in fig. 9 or 11.

The embodiment of the application also provides a communication system, which comprises the network device (for example, UDM) and the terminal device (for example, UE), wherein the network device performs the method performed by the UDM in any of the embodiments shown in fig. 12 to 14, and the terminal device performs the method performed by the UE in the embodiment shown in fig. 12 or 14.

The embodiment of the application also provides a communication system, which comprises the network device (for example, UDM) and the network device (for example, SOR-AF), wherein the UDM performs the method performed by the UDM in the embodiment shown in fig. 10 or fig. 13, and the SOR-AF performs the method performed by the SOR-AF in the embodiment shown in fig. 10 or fig. 13.

The embodiment of the present application further provides a communication system, which includes the foregoing network device (for example, UDM) and a network device (for example, AMF), where the UDM performs a method performed by the UDM in the embodiment shown in fig. 9, fig. 11, fig. 12, or fig. 14, and the AMF performs a method performed by the AMF in the embodiment shown in fig. 9, fig. 11, fig. 12, or fig. 14.

Embodiments of the present application further provide a computer readable storage medium storing a computer program, where the computer program may implement a procedure related to UDM in any of the embodiments shown in fig. 9 to 14 provided by the above method embodiments, or the computer may implement a procedure related to AMF in the embodiments shown in fig. 9, 11, 12 or 14 provided by the above method embodiments, or the computer may implement a procedure related to SOR-AF in the embodiments shown in fig. 10 or 13 provided by the above method embodiments, or the computer may implement a procedure related to UE in the embodiments shown in fig. 9, 11, 12 or 14 provided by the above method embodiments.

Embodiments of the present application further provide a computer program product, where the computer program product is configured to store a computer program, where the computer program is configured to implement a procedure related to UDM in any of the embodiments shown in fig. 9 to 14 provided by the foregoing method embodiments, or where the computer program is configured to implement a procedure related to AMF in the embodiment shown in fig. 9, 11, 12 or 14 provided by the foregoing method embodiments, or where the computer program is configured to implement a procedure related to SOR-AF in the embodiment shown in fig. 10 or 13 provided by the foregoing method embodiments, or where the computer program is configured to implement a procedure related to UE in the embodiment shown in fig. 9, 11, 12 or 14 provided by the foregoing method embodiments.

The application also provides a chip comprising a processor. The processor is configured to read and execute a computer program stored in the memory to perform the corresponding operations and/or procedures by the UDM, AMF, SOR-AF or UE in the method for registering to multiple networks provided by the present application. Optionally, the chip further comprises a memory, the memory is connected with the processor through a circuit or a wire, and the processor is used for reading and executing the computer program in the memory. Further optionally, the chip further comprises a communication interface, and the processor is connected to the communication interface. The communication interface is used for receiving the processed data and/or information, and the processor acquires the data and/or information from the communication interface and processes the data and/or information. The communication interface may be an input/output interface, interface circuitry, output circuitry, input circuitry, pins, or related circuitry, etc. on the chip. The processor may also be embodied as processing circuitry or logic circuitry.

The chip may be replaced by a chip system, and will not be described herein.

The terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. The object of the present embodiment can be achieved by actually selecting some or all of the units therein.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Furthermore, the terms first and second and the like in the description and in the claims, and in the figures, are used for distinguishing between different objects and not necessarily for describing a particular sequential or chronological order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.

Although the application has been described in connection with specific features and embodiments thereof, it will be apparent that various modifications and combinations can be made without departing from the spirit and scope of the application. Accordingly, the specification and drawings are merely exemplary illustrations of the present application as defined in the appended claims and are considered to cover any and all modifications, variations, combinations, or equivalents that fall within the scope of the application. It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

A method of registering with a plurality of networks, the method comprising:

the network equipment acquires information of a plurality of network slices which are requested to be accessed by the terminal equipment;

the network device determines a plurality of networks associated with the plurality of network slices, wherein each network slice of the plurality of network slices is supported by at least one network of the plurality of networks;

the network device sends information associated with the plurality of networks to the terminal device, the information associated with the plurality of networks being used for the terminal device to register with the plurality of networks.
The method of claim 1, the network device determining a plurality of networks associated with the plurality of network slices, comprising:

the network equipment acquires corresponding information, wherein the corresponding information is used for indicating a network to which the terminal equipment is allowed to register and a network slice supported by each network in the network to which the terminal equipment is allowed to register;

and the network equipment determines a plurality of networks associated with the plurality of network slices according to the corresponding information and the information of the plurality of network slices which the terminal equipment requests to access.
The method of claim 1, the network device determining a plurality of networks associated with the plurality of network slices, comprising:

the network equipment sends information of a plurality of network slices which the terminal equipment requests to access to a roaming preferred application function device;

the network device receives roaming preference information from the roaming preference application function device and determines the plurality of networks based on the SOR information.
A method according to any of claims 1 to 3, the network device sending information associated with the plurality of networks to the terminal device, comprising:

the network device sends roaming preference information to the terminal device, the roaming preference information including the information associated with the plurality of networks.
The method of any one of claims 1 to 4, further comprising:

the network device receives capability information of the terminal device from the terminal device, the capability information indicating that the terminal device has a capability of registering with a plurality of networks.
The method according to claim 1 to 5,

the plurality of networks includes a first network with which the terminal device is currently registered, and the information associated with the plurality of networks indicates at least one network other than the first network among the plurality of networks;

alternatively, the information associated with the plurality of networks indicates the plurality of networks.
A method of registering with a plurality of networks, the method comprising:

the terminal equipment sends information of a plurality of network slices which the terminal equipment requests to be accessed to the network equipment;

the terminal device receives information of a plurality of networks associated with the plurality of network slices from the network device, wherein each network slice of the plurality of network slices is supported by at least one network of the plurality of networks;

the terminal device registers to at least one network of the networks according to the information of the networks.
The method of claim 7, the terminal device registering with at least one of the plurality of networks according to information of the plurality of networks, comprising:

if the terminal equipment is registered to a first network in the networks, the terminal equipment is registered to at least one network except the first network in the networks; or alternatively, the process may be performed,

the terminal equipment registers to the networks according to the information of the networks.
The method of claim 7 or 8, the terminal device receiving information of a plurality of networks associated with the plurality of network slices from the network device, comprising:

the terminal device receives roaming preference information from the network device, the roaming preference information including information of the plurality of networks.
The method of claim 9, the terminal device registering with at least one of the plurality of networks according to information of the plurality of networks, comprising:

the terminal equipment updates an operator-controlled selector or an auxiliary updating user-controlled selector according to the roaming preference information;

the terminal device registers to at least one of the plurality of networks according to the updated operator-controlled selector or the user-controlled selector.
The method of any of claims 7 to 10, further comprising:

the terminal device sends capability information of the terminal device to the network device, the capability information indicating that the terminal device has a capability of registering with a plurality of networks.
A method of registering with a plurality of networks, the method comprising:

the terminal equipment receives first information from network equipment, wherein the first information is used for indicating a network set and network slices supported by each network in the network set;

the terminal equipment selects a plurality of networks associated with a plurality of network slices to be accessed by the terminal equipment from the network set, wherein each network slice in the plurality of network slices is supported by at least one network in the plurality of networks;

the terminal device registers with at least one of the plurality of networks.
The method of claim 12, the terminal device registering with at least one of the plurality of networks, comprising:

if the terminal equipment is registered to a first network in the networks, the terminal equipment is registered to at least one network except the first network in the networks; or alternatively, the process may be performed,

The terminal device registers with the plurality of networks.
The method of claim 12 or 13, further comprising:

the terminal device sends capability information of the terminal device to the network device, the capability information indicating that the terminal device has a capability of registering with a plurality of networks.
The method of any of claims 12 to 14, further comprising:

the terminal device receives, from the network device, indication information indicating that the terminal device registers to a plurality of networks.
The method of any of claims 12 to 15, the terminal device receiving first information from the network device, comprising:

the terminal device receives roaming preference information from the network device, the roaming preference information including the first information.
The method of claim 16, the terminal device selecting, from the set of networks, a plurality of networks associated with a plurality of network slices to be accessed by the terminal device, comprising:

the terminal equipment updates an operator-controlled selector or an auxiliary update user-controlled selector according to the first information in the roaming preference information;

the terminal device selects the plurality of networks according to the updated operator-controlled selector or the user-controlled selector.
The method of any of claims 12 to 17, each network of the set of networks being a network to which the terminal device is allowed to register.
The method of any of claims 12 to 17, further comprising:

and the terminal equipment sends the information of the plurality of network slices which the terminal equipment requests to access to the network equipment.
The method of claim 19, each network in the set of networks supporting at least one network slice of a plurality of network slices for which the terminal device requests access.
The method of any one of claims 1 to 20, the network device being a unified data management apparatus.
The method of any one of claims 1 to 21, the plurality of networks being a plurality of public land mobile networks; alternatively, the plurality of networks are a plurality of subnets under the first public land mobile network.
The method of claim 22, the plurality of subnets being a plurality of non-public networks.
A communication device comprising a processor;

the processor is configured to read and run a program from a memory to implement the method of any one of claims 1 to 6.
A communication device comprising a processor;

the processor is configured to read and run a program from a memory to implement the method of any of claims 7 to 11.
A communication device comprising a processor;

the processor is configured to read and run a program from a memory to implement the method of any of claims 12 to 20.
A computer program product containing instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 23.
A computer readable storage medium having instructions stored therein which, when run on a computer, cause a processor to perform the method of any one of claims 1 to 23.