Methods, apparatuses, and computer program products supporting onboarding and authentication of user equipment for networks and network slices

Abstract

Methods, apparatuses, and computer program products are described to support sending and receiving onboarding support and / or authentication requirement information to a UE via a RAN, etc., for registration with a network and / or network slice, such as a PLMN and / or SNPN. The onboarding support and / or authentication requirement information can be specifically configured for one or more networks and / or network slices thereof that utilize a shared RAN for communication with the UE. The UE selects a cell and network and / or network slice based on the onboarding support and / or authentication requirement information. The UE can camp on the shared RAN. The one or more networks include at least a RAN and a corresponding AMF that provide the onboarding support and / or authentication requirement information to the UE prior to or at the time the UE contacts the AMF associated with the network and / or network slice.

Description

Technical Field

[0001] The example implementation generally involves transmitting onboarding support information and authentication requirement information to the user equipment for registration with the network and / or network slice. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) is a standards organization that develops mobile phone protocols and is known for developing and maintaining various standards, including second-generation (2G), third-generation (3G), fourth-generation (4G), Long Term Evolution (LTE), and fifth-generation (5G) standards. 5G networks have been designed as a service-based architecture (SBA), or in other words, a system architecture where system functionality is achieved through a set of network functions that provide services to other authorized network functions in order to access their services.

[0003] 5G network systems allow support for network slices, which are end-to-end logical networks supporting a specific set of network functions. Thus, a network slice is a logical network infrastructure that provides specific network capabilities and characteristics. In a 5G network comprising multiple network slices, a particular network slice can be configured to support specific characteristics (e.g., hardware specifications, network functions, domain access, etc.) that are not common to all network slices. User equipment (UEs) can be configured to access multiple networks and / or network slices through a shared access point. Access to a network slice can be restricted to UEs associated with specific credentials or meeting specific requirements.

[0004] Network slicing, introduced by 5G systems, incorporates the concept of differentiated treatment of user equipment (UEs) based on the specific requirements of each customer. Therefore, network slicing in 5G systems allows mobile network operators (MNOs) to treat customers as belonging to different tenant types, each with corresponding service requirements. The service demands of a specific tenant group are managed according to the network slice type associated with each tenant type. UEs belonging to a specific tenant type are eligible to use the network slice specified according to their respective Service Level Agreement (SLA) and subscription.

[0005] 5G systems introduce and allow support for non-public networks (NPNs), which are networks deployed by 5G systems for non-public use. Thus, an NPN is either an independent non-public network (SNPN) that does not rely on the network functions provided by a Public Land Mobile Network (PLMN), or a Public Network Integrated NPN (PNI-NPN) that operates with the support of a PLMN. For a user equipment (UE) to access an NPN, a loading procedure is performed between the UE and the network to ensure that the UE has or can obtain the appropriate credentials. Summary of the Invention

[0006] Methods, apparatus, and computer program products are disclosed that facilitate the transmission of load support information and authentication requirement information between one or more networks and / or their network slices and one or more user equipments. This disclosure provides processes related to communication of load support information and authentication requirement information for user equipment via a shared radio access network and / or access and mobility management functions associated with one or more networks, such as SNPN, PNI-NPN, PLMN, etc., or combinations thereof. Example embodiments include network infrastructure that sends and receives information (e.g., load support information, authentication requirement information, registration information, etc.) about the availability of load and authentication functions for supported networks and / or network slices to user equipment via a radio access network (RAN) and / or access and mobility management function (AMF) before the user equipment establishes contact with a network function (e.g., AMF, etc.) and / or during the initial contact between the user equipment and the network function.

[0007] According to one aspect of this disclosure, a method is provided that includes inducing the broadcast of loading support information associated with at least one network slice to a user equipment via a network. Additionally, the method includes receiving a connection request from the user equipment via the network, the connection request including information identifying a selected network slice that supports loading for an unsubscribed user equipment. According to some embodiments, the method further includes registering the user equipment with the selected network slice. Furthermore, registering the user equipment with the selected network slice includes sending network slice-specific credentials to the user equipment. According to some embodiments, and in response to the completion of the registration process, the method may further include establishing a connection between the user equipment and the selected network slice via the network.

[0008] In some embodiments of the method, loading support information includes one or more of network slice-specific authentication requirements or network slice-specific loading availability for at least one network slice. In some embodiments of the method, the network slice-specific authentication requirements include an indication of whether the user equipment registering with the network and the selected network slice needs to authenticate the user equipment using the network slice, and wherein the network slice-specific loading availability includes an indication of whether the network slice supports loading. In some embodiments of the method, broadcasting loading support information to the user equipment is performed via a radio access network node. In some embodiments of the method, the network includes one or more of a public terrestrial mobile network, a standalone non-public network, or a public network integrated with a non-public network.

[0009] According to another aspect of this disclosure, an apparatus is provided comprising at least one processor and at least one memory, wherein the at least one memory includes computer program code configured, together with the at least one processor, to cause the apparatus to at least: cause the broadcast of loading support information associated with at least one network slice to a user equipment via a network. The computer program code configured, together with the at least one processor, further causes the apparatus to receive a connection request from the user equipment via the network, the connection request including information identifying a selected network slice that supports loading for an unsubscribed user equipment. According to some embodiments, the apparatus may also be caused to register the user equipment with the selected network slice. In such embodiments, registering the user equipment with the selected network slice may include sending additional network slice-specific credentials to the user equipment. According to some embodiments, and in response to the completion of the registration process, the computer program code may also cause the apparatus to establish a connection between the user equipment and the selected network slice via network infrastructure.

[0010] In some embodiments of the device, loading support information includes one or more of network slice-specific authentication requirements or network slice-specific loading availability for at least one network slice. In some embodiments of the device, the network slice-specific authentication requirements include an indication of whether user equipment (UE) needs to be authenticated using the network slice to register with the network and the selected network slice, and the network slice-specific loading availability includes an indication of whether the network slice supports loading. In some embodiments of the device, broadcasting loading support information to UE is performed via a radio access network node. In some embodiments of the device, the network includes one or more of a public terrestrial mobile network, a standalone non-public network, or a public network integrated with a non-public network.

[0011] According to another aspect of this disclosure, a computer program product is provided, comprising at least a non-transitory computer-readable storage medium on which a portion of program code is stored, wherein the program code portion, when executed, is configured to cause the broadcast of loading support information associated with at least one network slice to a user equipment via a communication network and associated infrastructure. Furthermore, the program code portion is configured to receive a connection request from the user equipment via the communication network, the connection request including information identifying a selected network slice that supports loading for an unsubscribed user equipment. In some embodiments, the program code portion, when executed, is also configured to register the user equipment with the selected network slice. According to such an embodiment, registering the user equipment with the selected network slice includes transmitting network slice-specific credentials to the user equipment. After the registration process is satisfactorily completed, the computer program product may also be configured to establish a connection between the user equipment and the selected network slice via the network and associated hardware and software infrastructure.

[0012] In some embodiments of the computer program product, loading support information includes one or more of network slice-specific authentication requirements or network slice-specific loading availability for at least one network slice. In some embodiments of the computer program product, the network slice-specific authentication requirements include an indication of whether the user equipment (UE) registering with the network and the selected network slice needs to be authenticated using the network slice, and wherein the network slice-specific loading availability includes an indication of whether the network slice supports loading. In some embodiments of the computer program product, broadcasting loading support information to the UE is performed via a radio access network node. In some embodiments of the computer program product, the network includes one or more of a public terrestrial mobile network, an independent non-public network, or a public network integrated with a non-public network.

[0013] According to another aspect of this disclosure, an apparatus is provided that includes components for inducing the broadcast of loading support information associated with at least a network slice to a user equipment via a network. Furthermore, the apparatus includes components for receiving a connection request from the user equipment via the network, the connection request including information identifying a selected network slice that supports loading for an unsubscribed user equipment. According to some embodiments, the apparatus further includes components for registering the user equipment with the selected network slice. Therefore, registering the user equipment with the selected network slice includes sending network slice-specific credentials to the user equipment. The network slice-specific credentials may be primary or secondary credentials that may have been previously transmitted or may not have been transmitted to the user equipment. According to some embodiments, and in response to the completion of the registration process, the apparatus may further include components for establishing a connection between the user equipment and the selected network slice via the network.

[0014] In some embodiments of the device, loading support information includes one or more of network slice-specific authentication requirements or network slice-specific loading availability for at least one network slice. In some embodiments of the device, the network slice-specific authentication requirements include an indication of whether authentication of the user equipment using the network slice is required to register the user equipment with the network and the selected network slice, and the network slice-specific loading availability includes an indication of whether the network slice supports loading. In some embodiments of the device, broadcasting loading support information to the user equipment is performed via a radio access network node. In some embodiments of the computer program product, the network includes one or more of a public terrestrial mobile network, a standalone non-public network, or a public network integrated with a non-public network.

[0015] According to another aspect of this disclosure, a method is provided that includes receiving, at least via a network, loading support information associated with each of a plurality of network slices. The method also includes selecting, from the plurality of network slices, a network slice that supports loading for unsubscribed user equipment. Accordingly, the network slice is selected by a communication device based on the loading support information. Furthermore, the method includes selecting a cell of a network associated with the selected network slice. According to some embodiments, the method may further include inducing the transmission of a connection request via the network to an access and mobility management function associated with the selected network slice for connection initiation with the selected network slice. In such embodiments, the method may include receiving registration information from the access and mobility management function via the network and in response to the transmission of the connection request. Additionally, the registration information may include additional loading support information required to connect to the selected network slice, such as primary and / or secondary credential requirements not previously transmitted. Furthermore, the method may include connecting to the selected network slice via the network.

[0016] In some embodiments of the method, loading support information includes one or more of network slice-specific authentication requirements or network slice-specific loading availability for each of a plurality of network slices. In some embodiments of the method, the network slice-specific authentication requirements include an indication of whether a user equipment registering with a selected network slice needs to authenticate with each of the plurality of network slices. According to some embodiments of the method, network slice-specific loading availability includes an indication of whether loading is supported by each of the plurality of network slices.

[0017] According to another aspect of this disclosure, an apparatus is provided comprising at least one processor and at least one memory, wherein the at least one memory includes computer program code configured, together with the at least one processor, to cause the apparatus to receive, at least via a network, loading support information associated with each of a plurality of network slices. In response to the received information, the apparatus is also caused to select, from the plurality of network slices, a network slice that supports loading of unsubscribed user devices. The network slice is selected based on the loading support information. Furthermore, the apparatus is configured to additionally select a cell of a network associated with the selected network slice. Some embodiments of the apparatus may be configured to transmit a connection request via the network to an access and mobility management function associated with the selected network slice for connection initiation with the selected network slice. Additionally or alternatively, the apparatus may be configured to receive registration information via the network from the access and mobility management function in response to the transmitted request. Such registration information may include additional loading support information required to connect to the selected network slice. The additional information may include additional credential requirements. Furthermore, the apparatus of the example embodiments may be configured to connect to the selected network slice via a network and its associated components.

[0018] In some embodiments of the apparatus, loading support information includes one or more of network slice-specific authentication requirements or network slice-specific loading availability for each of a plurality of network slices. In some embodiments of the apparatus, network slice-specific authentication requirements include an indication of whether a user equipment registering with a selected network slice needs to authenticate with each of the plurality of network slices. According to some embodiments of the apparatus, network slice-specific loading availability includes an indication of whether loading is supported by each of the plurality of network slices.

[0019] According to another aspect of this disclosure, a computer program product is provided, comprising at least a non-transitory computer-readable storage medium having a portion of program code stored thereon, wherein the program code portion, when executed, is configured to receive loading support information associated with each of a plurality of network slices via a network. In response to the received information, the program code portion is further configured to select, from the plurality of network slices, a network slice that supports loading of an unsubscribed user device. The program code portion is configured to select the network slice according to predefined criteria and at least the loading support information. Furthermore, the program code portion, when executed, is configured to additionally select a cell of a network associated with the selected network slice. Some embodiments of the computer program product may include a portion of program code configured to send a connection request via the network to an access and mobility management function associated with the selected network slice for connection initiation with the selected network slice. In some embodiments, the computer program product may include a portion of program code configured to receive registration information from the access and mobility management function via the network and in response to a previously sent request. Therefore, the registration information may include additional loading support information required to connect to the selected network slice, and in practice, such additional information may include additional credential requirements. In addition, embodiments of the computer program product may include a program code portion configured to induce a communicable connection from the device to a selected network chip via a network and its associated components.

[0020] In some embodiments of the computer program product, loading support information includes one or more of network slice-specific authentication requirements or network slice-specific loading availability for each of a plurality of network slices. In some embodiments of the computer program product, network slice-specific authentication requirements include an indication of whether a user equipment registering with a selected network slice needs to authenticate with each of the plurality of network slices. According to some embodiments of the computer program product, network slice-specific loading availability includes an indication of whether loading is supported for each of the plurality of network slices.

[0021] According to another aspect of this disclosure, an apparatus is provided that includes components for receiving loading support information associated with each of a plurality of network slices via a network. The apparatus also includes components for selecting, from the plurality of network slices, a network slice that supports loading for unsubscribed user devices. Thus, the network slice is selected by the communication device based on the loading support information. Furthermore, the apparatus includes components for selecting a cell of a network associated with the selected network slice. According to some embodiments, the apparatus may further include components for sending a connection request via the network to an access and mobility management function associated with the selected network slice for connection initiation with the selected network slice. In such embodiments, the apparatus may further include components for receiving registration information from the access and mobility management function via the network and in response to the transmission of the connection request. Furthermore, the registration information may include additional loading support information required to connect to the selected network slice, such as primary and / or secondary credential requirements not previously transmitted via the network to the associated communication device. Additionally, the apparatus may provide components for connecting to one or more selected network slices via one or more communication networks.

[0022] In some embodiments of the device, loading support information includes one or more of network slice-specific authentication requirements or network slice-specific loading availability for each of a plurality of network slices. In some embodiments of the device, network slice-specific authentication requirements include an indication of whether a user equipment registering with a selected network slice needs to authenticate with each of the plurality of network slices. According to some embodiments of the device, network slice-specific loading availability includes an indication of whether loading is supported for each of the plurality of network slices.

[0023] According to another aspect of this disclosure, a method is provided, comprising receiving loading support information and authentication requirement information associated with one or more networks from at least an access and mobility management function. In some embodiments, the one or more networks include a public terrestrial mobile network or an independent non-public network. The method may further include causing one or more broadcasts of the loading support information and authentication requirement information, such that the broadcasts are received by at least a user equipment. Some embodiments of the method may further include receiving from the user equipment a connection request including information identifying a selected network among the one or more networks, the connection request supporting loading for an unsubscribed user equipment. Furthermore, the method may include sending a registration request to at least the access and mobility management function based on the network selection and connection request, and / or sending a registration request to at least the access and mobility management function based on the network selection and connection request. In some embodiments, the method further includes receiving a registration response from at least the access and mobility management function. Additionally, the method may include establishing a connection between the user equipment and the selected network.

[0024] In some embodiments of the method, one or more networks further include one or more public network integrations of non-public networks or network slices. In some embodiments of the method, the access and mobility management functions include multiple access and mobility management functions. Therefore, each access and mobility function may be further associated with at least a corresponding network in one or more networks, such that each access and mobility function can cause a broadcast of corresponding load support and / or authentication requirement information. In some embodiments of the method, load support information is received and transmitted via system information block transmission. According to some embodiments of the method, system information block transmission is sent in response to a request from a user equipment and / or as a continuous broadcast to multiple user equipments residing on a cell shared by one or more networks.

[0025] According to another aspect of this disclosure, an apparatus is provided comprising at least one processor and at least one memory, wherein the at least one memory includes computer program code configured, together with the at least one processor, to cause the apparatus to at least: receive loading support information and authentication requirement information associated with one or more networks from at least an access and mobility management function. The one or more networks include public land mobile networks or independent non-public networks. Furthermore, the apparatus may also be configured to broadcast the loading support information and authentication requirement information to at least a user equipment. According to an example embodiment, the apparatus may also be caused to receive from the user equipment a connection request including information identifying a selected network among the one or more networks, the connection request supporting loading for an unsubscribed user equipment. Additional embodiments of the apparatus may be configured to send a registration request to at least an access and mobility management function based on network selection and connection requests, and receive a registration response from at least an access and mobility management function. Therefore, in response to the registration response, the apparatus may be able to establish a connection between the user equipment and the selected network.

[0026] In some embodiments of the device, one or more networks further include one or more public network integrations of non-public networks or network slices. In some embodiments of the device, the access and mobility management functions include multiple access and mobility management functions. Therefore, each access and mobility function may be further associated with at least a corresponding network in one or more networks, such that each access and mobility function can cause a broadcast of corresponding load support and / or authentication requirement information. In some embodiments of the device, load support information is received and transmitted via system information block transmission. According to some embodiments of the device, system information block transmission is sent in response to a request from a user equipment and / or as a continuous broadcast to multiple user equipments residing on a cell shared by one or more networks.

[0027] According to another aspect of the invention, a computer program product is provided, comprising at least a non-transitory computer-readable storage medium having a portion of program code stored thereon, wherein the program code portion, when executed, is configured to receive loading support information and authentication requirement information associated with one or more networks from at least an access and mobility management function. In some embodiments, the one or more networks include public terrestrial mobile networks or independent non-public networks. Furthermore, the program code portion may be configured to cause the broadcast of the loading support information and authentication requirement information to at least a user equipment. Some embodiments of the computer program product include a portion of program code further configured to receive from the user equipment a connection request including information identifying a selected network among the one or more networks, the connection request supporting loading for an unsubscribed user equipment. In response, such embodiments may include a portion of program code further configured to transmit a registration request to at least the access and mobility management function based on the network selection and connection request. In some embodiments, the program code portion, when executed, is also configured to receive a registration response from at least the access and mobility management function and establish a connection between the user equipment and the selected network.

[0028] In some embodiments of the computer program product, one or more networks further include one or more public network integrations of non-public networks or network slices. In some embodiments of the computer program product, the access and mobility management functions include multiple access and mobility management functions. Therefore, each access and mobility function may be further associated with at least a corresponding network in one or more networks, such that each access and mobility function can cause a broadcast of corresponding load support and / or authentication requirement information. In some embodiments of the computer program product, load support information is received and transmitted via system information block transmission. According to some embodiments of the computer program product, system information block transmission is sent in response to a request from a user equipment and / or as a continuous broadcast to multiple user equipment residing on a cell shared by one or more networks.

[0029] According to another aspect of this disclosure, an apparatus is provided comprising components for receiving loading support information and authentication requirement information associated with one or more networks from at least an access and mobility management function. In some embodiments, the one or more networks include a public land mobile network or an independent non-public network. The apparatus may further include components for inducing one or more broadcasts of the loading support information and authentication requirement information such that the broadcasts are received by at least one user equipment. Some embodiments of the apparatus may further include components for receiving from the user equipment a connection request including information identifying a selected network among the one or more networks, the connection request supporting loading for an unsubscribed user equipment. Furthermore, the apparatus may include additional components for sending a registration request to at least the access and mobility management function based on the network selection and connection request, and / or additional components for sending the registration request to at least the access and mobility management function based on the network selection and connection request. In some embodiments, the apparatus further includes components for receiving a registration response from at least the access and mobility management function. Additionally, the apparatus may include components for establishing a connection between the user equipment and the selected network.

[0030] In some embodiments of the device, one or more networks further include one or more public network integrations of non-public networks or network slices. In some embodiments of the device, the access and mobility management functions include multiple access and mobility management functions. Therefore, each access and mobility function may be further associated with at least a corresponding network in one or more networks, such that each access and mobility function can cause a broadcast of corresponding load support and / or authentication request information. In some embodiments of the device, load support information is received and transmitted via system information block transmission. According to some embodiments of the device, system information block transmission is sent in response to a request from a user equipment and / or as a continuous broadcast to multiple user equipments residing on a cell shared by one or more networks.

[0031] According to another aspect of this disclosure, a method is provided that includes receiving, via a network, loading support information and authentication requirement information associated with each of a plurality of networks, including one or more of public terrestrial mobile networks or independent non-public networks. The method may further include selecting, from the plurality of networks, a network that supports loading for unsubscribed user equipment. The network is selected based on the loading support information and authentication requirement information. Additionally, the method of this example embodiment includes selecting a cell of the selected network. According to some embodiments, the method may further include sending a connection request via the network to an access and mobility management function associated with the selected network for connection initiation with the selected network. Furthermore, the method of the example embodiment may include receiving registration information via the network from the access and mobility management function. The registration information includes additional loading support information required to connect to the selected network. Furthermore, the method of this example embodiment includes connecting to the selected network.

[0032] In some embodiments of the method, the multiple networks further include one or more public network integrations of non-public networks or network slices. In some embodiments of the method, the access and mobility management functions include multiple access and mobility management functions, each associated with a corresponding network among the multiple networks. Therefore, in such embodiments of the method, each access and mobility function can be configured to trigger a broadcast of corresponding load support information and authentication requirement information. In some embodiments of the method, load support information and authentication requirement information are received and transmitted via system information block transmission; therefore, system information block transmission is sent in response to a request from a user equipment or as a continuous broadcast to multiple user equipments residing in a cell shared by multiple networks.

[0033] According to another aspect of this disclosure, an apparatus is provided comprising at least one processor and at least one memory, wherein the at least one memory includes computer program code configured, together with the at least one processor, to cause the apparatus to receive, at least via a network, loading support information and authentication requirement information associated with each of a plurality of networks, including one or more of public land mobile networks or independent non-public networks. Additionally, the apparatus is configured to select, at least from the plurality of networks, a network that supports loading of unsubscribed user equipment. The network selection is based on the loading support information and authentication requirement information. The apparatus of this example embodiment is also configured to select a cell of the selected network. In some embodiments, the apparatus is further configured to transmit a connection request via the network to an access and mobility management function associated with the selected network for connection initiation with the selected network. Furthermore, the apparatus may also be configured to receive registration information via the network from the access and mobility management function. The registration information includes additional loading support information required to connect to the selected network. Some embodiments of the apparatus may be configured to connect to the selected network based at least on the registration information or other received information.

[0034] In some embodiments of the device, the multiple networks also include one or more public network integrations of non-public networks or network slices. In some embodiments of the device, the access and mobility management functions include multiple access and mobility management functions, each associated with a corresponding network among the multiple networks. Therefore, in such embodiments of the device, each access and mobility function can be configured to trigger a broadcast of corresponding load support information and authentication request information. In some embodiments of the device, load support information and authentication request information are received and transmitted via system information block transmission; therefore, system information block transmission is sent in response to a request from a user equipment or as a continuous broadcast to multiple user equipments residing in a cell shared by multiple networks.

[0035] According to another aspect of the invention, a computer program product is provided, comprising at least a non-transient computer-readable storage medium having a portion of program code stored thereon, wherein the program code portion, when executed, is configured to receive, via a network, loading support information and authentication requirement information associated with each of a plurality of networks, including one or more of public terrestrial mobile networks or independent non-public networks. Furthermore, the program code portion, when executed, is configured to select, from the plurality of networks, a network that supports loading of an unsubscribed user equipment. In some embodiments, the network is selected based on the loading support information and authentication requirement information. The program code portion of this example embodiment may be further configured to select a cell of the selected network. In some embodiments, the program code portion is also configured to transmit a connection request via the network to an access and mobility management function associated with the selected network for connection initiation with the selected network. Furthermore, the program code portion may be configured to receive registration information via the network from the access and mobility management function. The registration information includes additional loading support information required to connect to the selected network. Some embodiments may include a program code portion that, when executed, is configured to connect to the selected network based at least on the registration information or other received information.

[0036] In some embodiments of the computer program product, the multiple networks also include one or more public network integrations of non-public networks or network slices. In some embodiments of the computer program product, the access and mobility management functions include multiple access and mobility management functions, each associated with a corresponding network among the multiple networks. Therefore, in such embodiments of the computer program product, each access and mobility function can be configured to trigger a broadcast of corresponding load support information and authentication requirement information. In some embodiments of the computer program product, load support information and authentication requirement information are received and transmitted via system information block transmission; therefore, system information block transmission is sent in response to a request from a user equipment or as a continuous broadcast to multiple user equipment residing in a cell shared by multiple networks.

[0037] According to another aspect of this disclosure, an apparatus is provided comprising components for receiving, via a network, loading support information and authentication requirement information associated with each of a plurality of networks, including one or more of public terrestrial mobile networks or independent non-public networks. The apparatus may further include components for selecting from the plurality of networks a network that supports loading for unsubscribed user equipment. In some embodiments, the network is selected based on the loading support information and authentication requirement information; furthermore, the apparatus may include components for selecting a cell of the selected network. According to some embodiments, the apparatus may further include components for sending a connection request via the network to an access and mobility management function associated with the selected network for connection initiation with the selected network. Further embodiments may include components for receiving registration information via the network from the access and mobility management function. According to such embodiments, the registration information may include additional loading support information required to connect to the selected network. Additionally, the apparatus may include components for connecting to the selected network.

[0038] In some embodiments of the device, the multiple networks also include one or more public network integrations of non-public networks or network slices. In some embodiments of the device, the access and mobility management functions include multiple access and mobility management functions, each associated with a corresponding network among the multiple networks. Therefore, in such embodiments of the device, each access and mobility function can be configured to trigger a broadcast of corresponding load support information and authentication request information. In some embodiments of the device, load support information and authentication request information are received and transmitted via system information block transmission; therefore, system information block transmission is transmitted in response to a request from a user equipment or as a continuous broadcast to multiple user equipments residing in a cell shared by multiple networks.

[0039] Various other aspects are also described in the following detailed description and the appended claims. Attached Figure Description

[0040] The embodiments of this disclosure have been described in general terms. Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and in which:

[0041] Figure 1 The illustration shows an example architecture of a communication network according to some embodiments;

[0042] Figure 2 The illustration shows an example architecture of a communication network according to some embodiments;

[0043] Figure 3 The illustration shows an example architecture of a communication network according to some embodiments;

[0044] Figure 4The illustration shows an example computing device for communicating with other network entities via a communication network, according to some embodiments;

[0045] Figure 5 The illustration shows an example architecture of a communication network including network slicing according to some embodiments;

[0046] Figure 6 This is a flowchart illustrating signaling between communication devices via network infrastructure according to some embodiments;

[0047] Figure 7 This is a flowchart illustrating communication transmission between communication devices via network infrastructure according to some embodiments;

[0048] Figure 8 It is a flowchart illustrating operations performed by a communication device or other client device according to some example embodiments;

[0049] Figure 9 It is a flowchart illustrating operations performed by a communication device or other client device according to some example embodiments;

[0050] Figure 10 It is a flowchart illustrating operations performed by a communication device or other client device according to some example embodiments; and

[0051] Figure 11 It is a flowchart illustrating operations performed by a communication device or other client device according to some example embodiments. Detailed Implementation

[0052] Some embodiments of the invention will now be described more fully below with reference to the accompanying drawings, which illustrate some, but not all, of the embodiments of the invention. In fact, various embodiments of the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will meet applicable legal requirements. Unless otherwise stated, the term “or” is used herein in a substitute and combined sense. The terms “illustrative” and “exemplary” are used as examples and do not indicate a level of quality. Similar reference numerals refer to similar elements throughout. As used herein, the terms “data,” “content,” “information,” and similar terms may be used interchangeably to refer to data that can be transmitted, received, and / or stored according to embodiments of the invention. Therefore, the use of any such terms should not be construed as limiting the spirit and scope of the embodiments of the invention.

[0053] Furthermore, as used herein, the term "circuit system" refers to (a) a purely hardware circuit implementation (e.g., an implementation in analog and / or digital circuitry); (b) a combination of circuitry and (multiple) computer program products, including software and / or firmware instructions stored on one or more computer-readable storage media, which work together to enable a device to perform one or more functions described herein; and (c) circuitry that requires software or firmware to operate, such as, for example, (multiple) microprocessors or portions thereof, even if the software or firmware is not actually present. This definition of "circuit system" applies to all uses of the term herein, including all uses in any claim. As another example, as used herein, the term "circuit system" also includes an implementation comprising one or more processors and / or portions thereof, along with accompanying software and / or firmware. As yet another example, as used herein, the term "circuit system" also includes, for example, baseband integrated circuits or application processor integrated circuits for mobile phones, or similar integrated circuits in servers, cellular network devices, other network devices, and / or other computing devices.

[0054] Furthermore, as used herein, the terms "node," "entity," "intermediary," "intermediary entity," "middleman," and similar terms may be used interchangeably to refer to a computer or a program running on one or more networks via one or more network connections capable of creating, modifying, deleting, transmitting, receiving, and / or storing data according to embodiments of the invention. Therefore, the use of any such terms should not be construed as limiting the spirit and scope of the embodiments of the invention.

[0055] Furthermore, as used herein, the terms “user equipment,” “user device,” “device,” “apparatus,” “mobile device,” “personal computer,” “laptop,” “laptop,” “desktop computer,” “desktop computer,” “mobile phone,” “tablet computer,” “smartphone,” “smart device,” “cellular phone,” “computing device,” “communication device,” “user communication device,” “terminal,” and similar terms may be used interchangeably to refer to an apparatus configured to access one or more networks for at least the purpose of wired and / or wireless transmission of communication signals according to a particular embodiment of this disclosure, such as an apparatus that may be embodied by a computing device. Therefore, the use of any such terms should not be construed as limiting the spirit and scope of the embodiments of this disclosure.

[0056] Furthermore, as used herein, the terms “network slice,” “specific slice,” “slice,” “network portion,” and similar terms may be used interchangeably to refer to an end-to-end logical communication network or a portion thereof in a PLMN, SNPN, PNI-NPN, or other network.

[0057] As defined herein, a “computer-readable storage medium” referring to a non-transient physical storage medium (e.g., a volatile or non-volatile memory device) may differ from a “computer-readable transmission medium” referring to an electromagnetic signal. Such a medium can take many forms, including, but not limited to, non-transient computer-readable storage media (e.g., non-volatile media, volatile media) and transmission media. Transmission media include, for example, coaxial cables, copper wires, fiber optic cables, and carrier waves that can propagate through space without wires or cables, such as sound waves and electromagnetic waves, including radio waves, light waves, and infrared waves. Signals include artificial transient changes in amplitude, frequency, phase, polarization, or other physical properties transmitted through the transmission medium. Examples of non-transient computer-readable media include magnetic computer-readable media (e.g., floppy disks, hard disks, magnetic tapes, any other magnetic media), optical computer-readable media (e.g., compact disc read-only memory (CD-ROM), digital universal disc (DVD), Blu-ray disc (BD), etc., or combinations thereof), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), FLASH-EPROM, or any other non-transient medium from which a computer can read. The term computer-readable storage medium is used herein to refer to any computer-readable medium other than a transmission medium. However, it should be understood that while embodiments are described as using computer-readable storage media, other types of computer-readable media may replace the computer-readable storage media in the embodiments or may be used in addition to the computer-readable storage media in alternative embodiments.

[0058] In the following explanation, certain embodiments are described with reference to communication devices capable of communicating via wired and / or wireless networks and communication systems serving such communication devices. Before explaining these exemplary embodiments in detail, refer to... Figures 1-3 A brief explanation of some general principles of wired and / or wireless communication systems, their access systems, and communication equipment is provided to aid in understanding the technologies upon which the described examples are based.

[0059] According to some embodiments, communication devices or terminals may be provided for use via cells, base stations, access points, etc. (e.g., wireless transmitters and / or receiver nodes providing access points for radio access communication systems and / or other forms of wired and / or wireless networks) or combinations thereof. Such wired and / or wireless networks include, but are not limited to, networks configured to comply with 2G, 3G, 4G, LTE, 5G and / or any other similar or yet-to-be-developed future communication network standards. This disclosure contemplates that any methods, apparatus, computer program code, and any part or combination thereof may also be implemented using yet-to-be-developed communication networks and associated standards, which will be developed in the future and understood by those skilled in the art based on this disclosure.

[0060] Access points and the communications therethrough are typically controlled by at least one suitable control device to enable their operation and the management of mobile communication devices communicating with them. In some embodiments, the control device for a node may be integrated with, coupled to, and / or otherwise provided for controlling the access point. In some embodiments, the control device may be arranged to allow communication between a user device and a core network or a network entity of the core network. For this purpose, the control device may include at least one memory, at least one data processing unit such as a processor, and an input / output interface (e.g., a GPS receiver / transmitter, keyboard, mouse, touchpad, display, Universal Serial Bus (USB), Bluetooth, Ethernet, wired / wireless connectivity, etc., or combinations thereof). The control device may be coupled to other relevant components of the access point via the interface. The control device may be configured to execute appropriate software code to provide control functions. It should be understood that similar components may be provided in control devices provided elsewhere in the network system, such as in core network entities. The control device may interconnect with other control entities. Control devices and functions may be distributed among several control units. In some embodiments, each base station may include a control device. In alternative embodiments, two or more base stations may share a single control device.

[0061] Access points and associated controllers can communicate with each other via fixed-line connections and / or via radio interfaces. Logical connections between base station nodes can be provided, for example, by X2, S1, similar interfaces, or combinations thereof. This interface can be used, for example, for the operation of a coordinating station and for performing reselection or handover operations. The logical communication connection between the initial and final communication nodes of the network can include multiple intermediate nodes. Furthermore, any node can be added to or removed from the logical communication connection as needed to establish and maintain network functional communication.

[0062] Communication equipment or user equipment may include any suitable device capable of receiving at least communication signals including data. Communication signals may be transmitted via a wired connection, a wireless connection, or a combination thereof. For example, the device may be a handheld data processing device equipped with a radio receiver, data processing, and a user interface device. Non-limiting examples include mobile stations (MS) such as mobile phones or so-called "smartphones," portable computers such as laptops or tablets that provide wireless interface cards or other wireless interface facilities, personal digital assistants (PDAs) that provide wireless communication capabilities, or any combination thereof, etc. Other examples include wearable wireless devices, such as devices integrated with: watches or smartwatches, glasses, helmets, hats, clothing, wirelessly connected headphones, jewelry, etc., universal serial bus (USB) sticks with wireless functionality, modem data cards, machine-type devices, or any combination thereof, etc.

[0063] In some embodiments, a communication device, such as one configured to communicate with a wireless network or core network entity, may be a handheld or other type of mobile communication device or user equipment. Wireless communication capabilities and suitable electronic control devices for implementing its operation may be provided to the mobile communication device. Thus, the communication device may provide at least one data processing entity, such as a central processing unit and / or core processor, at least one memory, and other possible components, such as additional processors and memory for use in software and hardware-assisted performance of tasks designed to be performed. Data processing, storage, and other related control devices may be provided on a suitable circuit board and / or in a chipset. The data processing and memory functions provided by the control devices of the communication device are configured to induce control and signaling operations according to certain embodiments, as described later in this specification. A user may control the operation of the communication device by means of a suitable user interface such as a touch-sensitive display or keyboard and / or keypad, one of a plurality of actuator buttons, voice commands, combinations thereof, etc. A speaker and microphone are typically also provided. Furthermore, the mobile communication device may include suitable connectors (wired or wireless) to other devices and / or for connecting external accessories (e.g., hands-free devices) to it.

[0064] In some embodiments, the communication device can wirelessly communicate via one or more suitable means for receiving and transmitting signals (e.g., a GPS receiver / transmitter, a remote touchpad interface with a remote display, a Wi-Fi interface, etc.). In some embodiments, a radio unit can be connected to the device's control unit. The radio unit may include a radio section and an associated antenna arrangement. The antenna arrangement may be located inside or outside the communication device.

[0065] Figures 1-3The illustrations depict various example architectures of a communication network 100 in which various methods, apparatuses, and computer program products can be executed and / or used. In some embodiments, the communication network 100 may include components and dedicated equipment of any suitable configuration, quantity, orientation, location, and / or dimension, configured to provide an air interface (e.g., New Radio (NR)) for communication or connection between a user equipment 102 (UE 102) and a data network 116 (DN 116) via a core network 101 (CN 101) of the communication network 100. The UE 102 may be associated with one or more devices that are associated with one or more Network Function (NF) service consumers. Figure 1 As illustrated, a communication network 100 may be provided, in which a UE 102 can operatively communicate with a radio access network 104 (RAN 104) via means such as a tower, base station, access point, network node, etc. In some embodiments, RAN 104 may communicate with CN 101 or a component or entity thereof. In some embodiments, CN 101 may facilitate communication between UE 102 and DN 116, such as for sending data, messages, requests, etc., or combinations thereof. In some embodiments, DN 116 or CN 101 may communicate with an application server or application function 112 (AS / AF 112). RAN 104, CN 101, DN 116 and / or AS / AF 112 may be associated with a network repository function (NRF), NF service producer, service communication agent (SCP), secure edge protection agent (SEPP), policy charging associated function (PCF), etc., or combinations thereof.

[0066] In the context of 5G networks, such as Figure 2 and Figure 3As illustrated, the communication network 100 may include a series of connected network devices and dedicated hardware distributed throughout a service area, state, province, city, or country, and one or more network entities that may be stored at one or more connected network devices or dedicated hardware and / or hosted by one or more connected network devices or dedicated hardware. In some embodiments, UE 102 may be connected to RAN 104, which may then relay communication between UE 102 and CN 101, CN 101 being connected to DN 116, which may communicate with one or more AS / AF 112. In some embodiments, UE 102 may communicate with RAN 104, which may act as a relay between UE 102 and other components or services of CN 101. For example, in some embodiments, UE 102 may communicate with RAN 104, which may in turn communicate with Access and Mobility Management Function 108 (AMF 108). In other instances or embodiments, UE 102 may communicate directly with AMF 108. In some embodiments, AMF 108 may communicate with one or more network functions (NFs), such as Authentication Server Function 120 (AUSF 120), Network Slice Selection Function 122 (NSSF 122), Network Repository Function 124 (NRF 124), Policy Accounting Function 114 (PCF 114), Network Data Analysis Function 126 (NWDAF 126), Unified Data Management Function 118 (UDM 118), AS / AF 112, Session Management Function 110 (SMF 110), and so on.

[0067] In some embodiments, SMF 110 may communicate with one or more user plane functions 106 (UPF 106, UPF 106a, UPF 106b, collectively referred to as "UPF 106"). By way of example only, in some embodiments, UPF 106 may communicate with RAN 104 and DN 116. In other embodiments, DN 116 may communicate with a first UPF 106a and RAN 104 may communicate with a second UPF 106b, while SMF 110 communicates with both the first UPF 106a and the second UPF 106b, and the first UPF 106a and the second UPF 106b communicate with each other.

[0068] In some embodiments, UE 102 may include a single-mode or dual-mode device, enabling UE 102 to connect to one or more RANs 104. In some embodiments, RAN 104 may be configured to implement one or more radio access technologies (RATs), such as Bluetooth, Wi-Fi, and Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), LTE, or 5G NR, which can be used to connect UE 102 to CN 101. In some embodiments, RAN 104 may include or utilize chips (such as silicon chips) in UE 102 that can be paired with or otherwise identified by similar chips in CN 101, allowing RAN 104 to establish a communication connection or line between UE 102 and CN 101 by identifying and pairing chips within UE 102 with chips within CN 101. In some embodiments, RAN 104 may implement one or more base stations, towers, etc., to facilitate communication between UE 102 and CN 101's AMF 108.

[0069] In some embodiments, the communication network 100 or its components (e.g., base stations, towers, etc.) may be configured to communicate with a communication device (e.g., UE 102) such as a cellular phone via multiple different frequency bands, such as FR1 (below 6 GHz), FR2 (millimeter wave), other suitable frequency bands, their sub-bands, etc. In some embodiments, the communication network 100 may include or employ a large number of multiple-input multiple-output (MIMO) antennas. In some embodiments, the communication network 100 may include multi-user MIMO (MU-MIMO) antennas. In some embodiments, the communication network 100 may employ edge computing, whereby the computing server is communicatively, physically, computationally, and / or temporally closer to the communication device (e.g., UE 102) to reduce latency and data traffic congestion. In some embodiments, the communication network 100 may employ other technologies, devices, or techniques, such as small cells, low-power RAN, beamforming of radio waves, Wi-Fi cellular convergence, non-orthogonal multiple access (NOMA), channel coding, etc., or combinations thereof.

[0070] like Figure 3As illustrated, UE 102 can be configured to communicate with RAN 104 in the N1 interface, for example, according to a Non-Access Stratum (NAS) protocol. In some embodiments, RAN 104 can be configured to communicate with CN 101 or its components (e.g., AMF 108) in the N2 interface, for example, in the control plane between the base station of RAN 104 and AMF 108. In some embodiments, RAN 104 can be configured to communicate with UPF 106 in the N3 interface, for example, in the user plane. In some embodiments, AMF 108 and / or SMF 110 can be configured to communicate with other services or network entities within CN 101 in various different interfaces and / or according to various different protocols. For example, in some embodiments, AMF 108 and / or SMF 110 can be configured to communicate with AUSF 120 in the Nausf interface or the N12 interface. In some embodiments, AMF 108 and / or SMF 110 may be configured to communicate with NSSF 122 in the Nnssf interface. In some embodiments, AMF 108 and / or SMF 110 may be configured to communicate with NRF 124 in the Nnrf interface. In some embodiments, AMF 108 and / or SMF 110 may be configured to communicate with PCF 114 in the Npcf or N7 interface. In some embodiments, AMF 108 and / or SMF 110 may be configured to communicate with NWDAF 126 in the Nnwdaf interface. In some embodiments, AMF 108 and / or SMF 110 may be configured to communicate with UDM 118 in the Nudm, N8, or N10 interface. In some embodiments, AMF 108 and / or SMF 110 may be configured to communicate with AS / AF 112 in the Naf interface. In some embodiments, SMF 110 may be configured to communicate with UPF 106 in an N4 interface, which may act as a bridge between the control plane and the user plane, such as acting as a conduit for Protocol Data Unit (PDU) sessions during the transmission of information between UE 102 and CN 101 or their components / services.

[0071] It should be understood that some of the example embodiments described herein occur in the context of telecommunications networks, including but not limited to telecommunications networks that conform to and / or otherwise incorporate aspects of the fifth-generation (5G) architecture. Although Figures 1-3 Various configurations and / or components of an example architecture of a communication network 100 are illustrated, but many other systems, system configurations, networks, network entities and paths / protocols communicating within it are conceived and considered within the scope of this disclosure.

[0072] Although the methods, devices / apparatus, and computer program products / code described herein are described in the context of fifth-generation core networks (5GC) and systems, such as Figures 1-3 As illustrated in the figures and described above, the methods, apparatus, and computer program products described can still be applied in a broader context within any suitable telecommunications system, network, standard, and / or protocol. It should be understood that the described methods, apparatus, and computer program products can also be applied to future networks and systems that are clearly undeveloped by those skilled in the art according to this disclosure.

[0073] Turn now Figure 4 This disclosure describes examples of apparatuses that may be embodied by user equipment or network entities, such as servers or other computing devices, according to exemplary embodiments. As described below in conjunction with the flowcharts and block diagrams presented herein, apparatus 200 of the exemplary embodiments may be configured to perform the functions described herein. In any instance, apparatus 200 may more generally be embodied by computing devices such as servers, personal computers, computer workstations, or other types of computing devices, including those used as components of user equipment and / or wireless networks or wireless local area networks. Regardless of how apparatus 200 is embodied, the apparatuses of the exemplary embodiments can be configured as follows: Figure 4 The configuration shown is intended to include a processor 202 and a memory device 204 and, in some embodiments, to communicate with and / or a communication interface 206.

[0074] Although not illustrated, the device of the example embodiment may optionally include a user interface, such as a touchscreen, display, keypad, etc., or combinations thereof. Furthermore, the device according to the example embodiment may be configured with a global positioning circuit, which includes a global positioning receiver and / or a global positioning transmitter configured to communicate with one or more global navigation satellite systems (e.g., GPS, GLONASS, Galileo, etc., or combinations thereof). The global positioning circuit may be configured to transmit and / or receive direct / indirect satellite and / or cell signals for the device and / or communication with the device or Figure 1 Another communication device associated with one or more global navigation satellite systems determines geolocation data (e.g., latitude, longitude, altitude, height, geographic coordinates, etc., or combinations thereof).

[0075] Processor 202 (and / or coprocessor or auxiliary processor or any other circuitry otherwise associated with the processor) may communicate with memory device 204 via a bus for transferring information between components of device 200. The memory device may, for example, include one or more volatile and / or non-volatile memories, such as non-transient memory devices. In other words, for example, the memory device may be an electronic storage device (e.g., a computer-readable storage medium) that includes gates configured to store data (e.g., bits) that can be retrieved by a machine (e.g., a computing device such as a processor). According to example embodiments, the memory device may be configured to store information, data, content, applications, instructions, etc., or combinations thereof, enabling the device to perform various functions. For example, the memory device may be configured to buffer input data for processor processing. Additionally or alternatively, the memory device may be configured to store instructions for processor execution.

[0076] In some embodiments, device 200 may be embodied in various computing devices as described above. However, in some embodiments, the device may be embodied as a chip or chipset. In other words, the device may include one or more physical packages (e.g., chips) that include materials, components, and / or wires on a structural assembly (e.g., a substrate). The structural assembly may provide physical strength, dimensional retention, and / or electrical interaction constraints for the component circuitry included thereon. Thus, in some cases, the device may be configured to implement embodiments of the invention on a single chip or as a single “system-on-a-chip.” Thus, in some cases, a chip or chipset may constitute a component for performing one or more operations to provide the functionality described herein.

[0077] Processor 202 can be embodied in a variety of different ways. For example, a processor can be embodied as one or more of various hardware processing units, such as a coprocessor, microprocessor, controller, digital signal processor (DSP), processing element with or without an accompanying DSP, or various other circuits including integrated circuits, such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), microcontroller units (MCUs), hardware accelerators, dedicated computer chips, and so on. Thus, in some embodiments, a processor may include one or more processing cores configured to execute independently. Multi-core processors can implement multiprocessing within a single physical package. Additionally or alternatively, a processor may include one or more processors configured in series via a bus to enable independent execution of instructions, pipelining, and / or multithreading.

[0078] In one example embodiment, processor 202 may be configured to execute instructions stored in memory device 204 or accessible to the processor. Alternatively or additionally, the processor may be configured to perform hard-coded functionality. Thus, whether configured by hardware or software methods or by a combination thereof, the processor may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to embodiments of this disclosure when appropriately configured. Therefore, for example, when the processor is embodied as an ASIC, FPGA, etc., or a combination thereof, the processor may be hardware specifically configured to perform the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of instructions, the instructions may specifically configure the processor to perform the algorithms and / or operations described herein when the instructions are executed. However, in some cases, the processor may be a processor of a particular device (e.g., an encoder and / or decoder) configured to further configure the processor to employ embodiments of the invention via instructions for performing the algorithms and / or operations described herein. The processor may include clocks, arithmetic logic units (ALUs), and logic gates, etc., configured to support the operation of the processor.

[0079] In embodiments including communication interface 206, the communication interface can be any component, such as a device or circuitry embodied in hardware or a combination of hardware and software, configured to receive and / or transmit data from / to a network and / or any other device or module communicating with device 200, such as NF, NRF, base station, access point, SCP, UE 102, RAN 104, core network services, AS / AF 112, database or other storage devices, etc., or combinations thereof. In this regard, the communication interface may include, for example, one or more antennas and supporting hardware and / or software for enabling communication with a wireless communication network. Additionally or alternatively, the communication interface may include circuitry for interacting with one or more antennas to induce the transmission of signals via one or more antennas or the processing of signals received via one or more antennas. In some embodiments, the one or more antennas may include one or more of the following: dipole antenna, monopole antenna, helical antenna, loop antenna, waveguide, horn antenna, parabolic reflector, corner reflector, dish antenna, microstrip patch array, convex plane, concave plane, convex-convex, concave-concave lens, etc., or combinations thereof. In some environments, the communication interface may alternatively or also support wired communication. Thus, for example, the communication interface may include a communication modem and / or other hardware / software for supporting communication via cable, Digital Subscriber Line (DSL), USB, etc., or combinations thereof. In some embodiments, session management functions (e.g., SMF 110) may include 5GC session management functions for any suitable Control and User Plane Separation (CUPS) architecture, such as those for General Packet Radio Service (GPRS), Gateway GPRS Support Node Control Plane Function (GGSN-C), Trusted Radio Access Gateway Control Plane Function (TWAG-C), Broadband Network Gateway Control and User Plane Separation (BNG-CUPS), N4 interface, Sxa interface, Sxb interface, Sxc interface, Evolved Packet Core (EPC) Service Gateway Control Plane Function (SGW-C), EPC Packet Data Network Gateway Control Plane Function (PGW-C), EPC Traffic Detection Control Plane Function (TDF-C), etc., or combinations thereof.

[0080] As illustrated, device 200 may include a processor 202 that communicates with memory 204 and is configured to provide signals to and receive signals from communication interface 206. In some embodiments, communication interface 206 may include a transmitter and a receiver. In some embodiments, processor 202 may be configured to at least partially control the operation of device 200. In some embodiments, processor 202 may be configured to control the operation of a transmitter and receiver by implementing control signaling to the transmitter and receiver via electrical leads. Similarly, processor 202 may be configured to control other elements of device 200 by implementing control signaling via electrical leads connecting processor 202 to other elements such as a display or memory 204.

[0081] Device 200 is capable of operating using one or more air interface standards, communication protocols, modulation types, access types, etc. Signals transmitted and received by processor 202 may include signaling information according to applicable cellular system air interface standards and / or any number of different wired or wireless networking technologies, including but not limited to Wi-Fi, Wireless Local Access Network (WLAN) technologies such as IEEE 802.11, 802.16, 802.3, Asymmetric Digital Subscriber Line (ADSL), Cable Data Service Interface Specification (DOCSIS), etc., or combinations thereof. Furthermore, these signals may include voice data, user-generated data, user-requested data, etc., or combinations thereof.

[0082] For example, the cellular modem in device 200 and / or therein may be able to operate according to various first-generation (1G) communication protocols, second-generation (2G or 2.5G) communication protocols, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, fifth-generation (5G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (e.g., Session Initiation Protocol (SIP)), etc., or combinations thereof. For example, device 200 may be able to operate according to 2G wireless communication protocol provisional standard (IS) 136 (IS-136), Time Division Multiple Access (TDMA), GSM, IS-95, Code Division Multiple Access, Code Division Multiple Access (CDMA), etc., or combinations thereof. Furthermore, for example, device 200 may be able to operate according to 2.5G wireless communication protocol GPRS, Enhanced Data GSM Environment (EDGE), etc., or combinations thereof. Furthermore, for example, device 200 may be able to operate according to 3G wireless communication protocols such as UMTS, Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), etc., or combinations thereof. NA 200 may also be able to operate according to 3.9G wireless communication protocols such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), etc., or combinations thereof. Additionally, for example, device 200 may be able to operate according to 4G wireless communication protocols such as Advanced LTE, 5G, etc., and similar wireless communication protocols that may be developed subsequently. In some embodiments, device 200 may be able to operate according to or within the framework of any suitable CUPS architecture, such as Gateway GGSN-C, TWAG-C, Broadband Network Gateway (BNG), N4 interface, Sxa interface, Sxb interface, Sxc interface, EPC SGW-C, EPCPGW-C, EPC TDF-C, etc., or combinations thereof. In fact, although this article describes the operation in conjunction with 5G systems, the apparatus and methods can be configured to operate in conjunction with many other types of systems (including those developed and implemented below).

[0083] Some embodiments disclosed herein can be implemented as software, hardware, application logic, or a combination of software, hardware, and application logic. For example, the software, application logic, and / or hardware may reside on memory 204, processor 202, or electronic components. In some example embodiments, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media. In the context of this document, "computer-readable medium" can be any non-transitory medium that can contain, store, communicate, propagate, or transmit instructions for use by or in connection with an instruction execution system, apparatus, or device (such as a computer or data processor circuit system), for example, [examples would be inserted here]. Figure 4As depicted. Computer-readable media can include non-transitory computer-readable storage media, which can be any medium that can contain or store instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

[0084] Figure 5 An example communication network 600 including two example network slices is illustrated. UE 102 utilizes at least a communication interface 206 to establish one or more network connections by transmitting and receiving communication signals between UE 102 via at least the communication interface 206 and public network function 603, first network slice 601, and / or second network slice 602. It should be understood that in some embodiments, the communication interface 206 can directly connect UE 102 to the first network slice 601 and / or second network slice 602, thereby bypassing public network function 603. Furthermore, it should be understood that the communication interface 206 can indirectly connect UE 102 to the first network slice 601 and / or second network slice 602 by first establishing a connection via public network function 603. In some embodiments, UE 102 can connect to multiple public and / or private networks and / or multiple public and / or private network slices via the communication interface 206. In some embodiments, the communication interface 206 may be communicatively connected to one or more of a RAN, cell, gNB, ng-eNB, NodeB, etc., or combinations thereof, so that communication signals can be transmitted and received therethrough.

[0085] In the illustrated embodiment, the first network slice 601 includes multiple network functions, including at least Network Storage Function 1 (NRF1) 124a, Policy Charging Function 1 (PCF1) 114a, User Plane Function 1 (UPF1) 106a, and Session Management Function 1 (SMF1) 110a. Each network function of the first network slice 601 is independent of the network functions of the common network function 603 and the second network slice 602. Furthermore, the first network slice 601 is configured to connect the UE 102 to the data network 1 (DN1) 116a. The second network slice 602 includes multiple network functions, including at least Network Storage Function 2 (NRF2) 124b, Policy Charging Function 2 (PCF2) 114b, User Plane Function 2 (UPF2) 106b, and Session Management Function 2 (SMF2) 110b. Each network function of the second network slice 602 is independent of the common network function 603 and the network functions associated with the first network slice 601. In addition, the second network slice 602 is configured to connect UE 102 to data network 2 (DN2) 116b.

[0086] In some embodiments, Figure 5Example communication networks 600 include one or more of Public Land Mobile Networks (PLMNs), Standalone Non-Public Networks (SNPNs), Public Network Integration Networks (PNI-NPNs), etc. For example, a first network slice 601 can be configured as part of a PLMN along with a public network function 602, allowing UE 102 to access the first network slice 601 without undergoing an inbound process or credential authentication. Furthermore, a second network slice 602 can be configured as a PNI-NPN operating with the support of a PLMN, comprising the first network slice 601 and the public network function 602, but further requiring UE 102 to belong to a specific tenant type to be eligible to use the second network slice 602. Additionally, to access the second network slice 602, UE 102 will have to undergo an inbound process and / or credential authentication, which incorporates credentials associated with UE 102 and one or more Service Level Agreements (SLAs) and / or subscriptions. If UE 102 has been subscribed to the second network slice 602, the credential authentication process can be initiated by either UE 102 or the second network slice 602 without the need for an additional loading or registration process. It should also be understood that, according to some embodiments, the first network slice 601 and / or the second network slice 602 can be configured as a network separate from the example communication network 600, rather than as a network slice, such as an SNPN supporting authentication and / or loading procedures. Furthermore, in some embodiments, multiple additional network slices (e.g., a third network slice, a fourth network slice, etc.) can be incorporated into the example communication network 600, wherein each network slice is configured with or without authentication feature requirements, with or without loading features for unregistered user equipment, and / or multiple network functions (e.g., NRF, UPF, PCF, SMF, AS / AF, AUSF, DN, etc.).

[0087] Figure 6 A flowchart depicting an example signal sequence 700 is illustrated, providing a network slice-specific loading instruction between communication devices (e.g., apparatus 200, etc.) via at least network infrastructure (e.g., communication networks 100, 600, etc.). As shown, the example network infrastructure utilized for the signal sequence 700 includes at least AMF 108, RAN 104, and UE 102. In some embodiments, the network infrastructure may be configured according to 5G system standards, etc. (e.g., 4G, LTE, etc.), and RAN 104 may include one or more 5G radio nodes, such as one or more gNBs or equivalents. In some embodiments, the example signal sequence 700 may be implemented using one or more network infrastructures (e.g., PLMN, SNPN, etc.) associated with one or more networks, and each of the one or more networks includes one or more network slices.

[0088] During signal sequence 700, the communication network sends information about the availability of the supported network slices to UE 102 prior to initial contact with AMF 108 via AMF 108 and RAN 104. As used herein, the initial contact with AMF 108 refers to the initial contact with AMF regarding the establishment of the corresponding connection and does indeed take into account any previous contact with AMF 108, such as in conjunction with the establishment of a previous connection or for other purposes besides the establishment of the corresponding connection. In some embodiments, information about the supported network slices may be sent alternatively or additionally during the initial contact or communication to establish a connection between UE 102 and AMF 108 via RAN 104, whether initiated by UE 102 or AMF 108. Furthermore, AMF 108 may be configured to continuously or repeatedly broadcast the supported network slices to one or more UEs residing in cells of the associated network. In instances where the UE maintains an idle mode within a cell associated with the network, it can be determined that the UE is camped on the network, enabling the UE to be ready to initiate a potential dedicated service or to receive an ongoing broadcast service from the network via at least one network function. By camping on a cell in an idle mode or state, for example via AMF and RAN, the UE is able to receive information related to the camped network and / or initiate a connection to the camped network. In some embodiments, the UE may be camped on multiple networks via multiple cells. In some embodiments, the UE 102 may request network and / or specific network slice information on demand and / or in real time after receiving input signals from a user and / or an application associated with the UE 102.

[0089] As shown in box 702, AMF 108 sends supporting network slice information to RAN 104 for distribution to the UE(s) associated with RAN 104. For example, UE 102 may be one of multiple UEs camped on the network via RAN 104. As shown in box 702, the slice information includes details of authentication requirements and load availability information for one or more network slices supported by the RAN. In this example, the slice information relates to three supported network slices (e.g., slices 1, 2, and 3). For example, slice 1 is shown as not requiring authentication for the access UE, while slices 2 and 3 each require certain authentication credentials from the UE. Furthermore, slice 2 does not support load for unregistered UEs, while slice 3 supports the load process for registered UEs.

[0090] Block 704 depicts the slice information received by RAN 104 from AMF 108 being further transmitted from RAN 104 to UE 102. As depicted in block 704, upon receiving the slice information, UE 102 initiates registration with the communication network based on the slice information. As shown in block 706, the UE 102 of the example embodiment can be configured to initiate registration with a specific network slice only when certain conditions are available. For example, UE 102 can initiate registration with a network slice in instances where the network slice does not have slice-specific authentication requirements (e.g., the network slice is publicly accessible), see block 706(a). Furthermore, in instances where the network slice has slice-specific authentication requirements and UE 102 meets those specific authentication requirements, UE 102 can initiate registration with the network slice (e.g., UE 102 is associated with a paid subscription according to an SLA), see block 706(b). Additionally, in instances where a network slice has slice-specific authentication requirements and the network slice supports loading for UEs lacking the required credentials, UE 102 may initiate registration with the network slice (e.g., UE 102 is not associated with a required paid subscription, but the network slice is configured to register UE 102 with the required subscription according to the SLA), see block 706(c). In some embodiments, UE 102 initiates registration with a selected network slice based on received network slice information and / or through communication with the host network via RAN 104.

[0091] As shown in box 708, RAN 104 facilitates the registration of UE 102 to AMF 108. The registration process includes: in response to a registration request received from UE 102, AMF 108 sending an indication of network slice-specific loading availability to UE 102 in instances where further information is required or UE 102 has not previously received further information. Additionally or alternatively, the registration process includes: in response to a registration request received from UE 102, AMF 108 performing network slice-specific loading and network slice-specific authentication procedures. It should be understood that AMF 108 may also perform registration from other network functions (e.g., public network function 603 and / or those described herein). Figure 5 Such a process is performed with the support of the network functions associated with the first network slice 601 described. After the registration process is completed, the UE 102 is registered to access the services provided by the selected network slice. In some embodiments, the UE 102 can select and register with multiple network slices, which may be associated with one or more networks.

[0092] According to some embodiments of signal sequence 700, AMF 108 can send information to the gNB of the 5G system regarding the availability of supported network slices associated with the communication network. Such transmission can be performed as part of a 3GPP-defined NG-Setup, and can further transmit information regarding auxiliary authentication requirements for each supported network slice after receiving a registration request from UE 102. According to such an embodiment, the gNB can be further configured to transmit the supported network slice information to UE 102 before receiving communication from UE 102.

[0093] Figure 7 A flowchart depicting example signal sequence 800 is illustrated for communication with a load support indicator associated with a PLMN and SNPN utilizing a shared RAN (e.g., a shared gNB, etc.). The communication signal transmissions described with respect to signal sequence 800 occur between communication devices (e.g., apparatus 200, etc.) via network infrastructure (e.g., communication networks 100, 600, etc.). Figure 7 As shown, the example network infrastructure used for signal sequence 800 includes at least AMF 108, RAN 104, and UE 102. In some embodiments, the network infrastructure can be configured according to 5G system standards, etc., and RAN 104 may include one or more 5G radio nodes, such as one or more gNBs or equivalents. Furthermore, regarding... Figure 7 The described process can further facilitate communication with load support indicators associated with PNI-NPN and SNPN utilizing a shared RAN (e.g., a shared gNB, etc.). In practice, it should be understood that such processes can be applied to access networks (e.g., RAN, etc.) shared among PLMNs, PNI-NPNs, SNPNs, networks, network slices, etc., or combinations thereof.

[0094] like Figure 7As shown, according to signal sequence 800, the communication network transmits information about the availability of load support indicators specific to multiple PLMNs and SNPNs to UE 102 via AMF 108 and RAN 104. AMF 108 initiates the transmission of load support indicators as part of NG setup with RAN 104. During the NG setup process between AMF 108 and RAN 104, AMF 108 initiates the transmission of load support indicators for PLMN-1, PLMN-2, SNPN-1, and SNPN-2, see block 802. As shown, PLMN-1 and SNPN-2 do not provide a load process, while PLMN-2 and SNPN-1 are identified as providing a load process by the NG setup transmission. In some embodiments, one or more networks (e.g., PLMN-1, PLMN-2, SNPN-1, SNPN-2, etc.) and / or one or more network slices (e.g., PNI-NPN associated with PLMN-1, network slices 601, 602, etc.) may be transmitted via one or more bundled communications, which include load support indicators for utilizing one or more networks and / or one or more network slices of the shared RAN 104. According to other embodiments, load support indicators for one or more networks and / or one or more network slices may be transmitted via multiple separate communications, each of which includes a load support indicator for the corresponding network or the corresponding network slice. According to some embodiments, the load support indicator may be configured to include primary and / or secondary authentication information for UE access to PLMN, SNPN, PNI-NPN, network, network slice, etc., or combinations thereof. Furthermore, some embodiments of the load support indicator may be configured such that the load support indicator is added to a System Information Block (SIB). According to such an embodiment, the SIB including the loading of support indicators and / or primary and / or secondary authentication information can be a traditional SIB (e.g., SIB1, etc.), a new SIB, an on-demand SIB, etc., or a combination thereof. Additionally, the SIB can be configured to include loading support indicators and / or primary and / or secondary authentication information for one or more networks and / or network slices.

[0095] After the transmission of NG setup information and before UE 102 initiates a connection with RAN 104, RAN 104 causes the transmission of network-supported PLMN and SNPN information to UE 102, see block 804. As depicted in block 804, the PLMN and SNPN information includes load support indicators for at least PLMN-1, PLMN-2, SNPN-1, and SNPN-2 received by RAN 104 from AMF 108, see block 802. In some embodiments, RAN 104 may be configured to continuously, periodically, or repeatedly broadcast load support indicators associated with one or more networks or network slices to one or more UEs residing in cells of the network. In some embodiments, the broadcast may occur at predetermined time intervals (e.g., in response to a timer configured with AMF) and / or in response to changes in one or more networks or network slices, load, and / or authentication policies. Additionally, such broadcasting of load support indicators for one or more networks or network slices may be in response to communication signals received by one or more networks or network slices from one or more UEs. Furthermore, broadcasts can be transmitted by one or more networks or network slices without receiving prior communication or connection to one or more UEs. In some embodiments, RAN 104 can be configured to transmit a load support indicator associated with one or more networks or network slices in response to UE 102 initiating a connection with RAN 104. According to such an embodiment, during the establishment of an initial connection with UE 102 (such as initiated by UE 102), RAN 104 can transmit a load support indicator for sharing one or more networks or network slices of RAN 104.

[0096] Upon receiving PLMN and SNPN information, including at least a load support indicator, UE 102 is configured to select a network and / or network slice associated with RAN 104 in response. In an instance where UE 102 is to select a network and / or network slice that UE 102 has not subscribed to, UE 102 is further configured to select the network and / or network slice based on the received load support indicator, such that the selected network and / or selected network slice provides a loading procedure for unregistered and / or unsubscribed UEs, see block 806. In this instance, UE 102 transmits a selection 104 of a network and / or network slice with loading capability to AMF 108 via RAN to initiate a connection and registration procedure. In response to receiving UE 102's selection of a network and / or network slice, AMF 108 completes the registration and loading procedure according to the SLA to allow UE 102 to access the selected network and / or selected network slice. In addition, AMF 108 may cause the transmission of auxiliary or additional loading and / or authentication requirements to UE 102, as such additional requirements involve the registration process for the selected network and / or the selected network slice, see block 808.

[0097] According to some embodiments, in instances where a cell, RAN, gNB, etc., or combinations thereof, cannot provide one or more load indications and / or authentication requirements to the UE before or during network connection, the AMF and / or other network functions can be configured to support providing one or more load indications and / or authentication requirements as part of the registration process. For example, in instances where a shared RAN cannot transmit auxiliary authentication requirements to the UE before establishing a connection with the corresponding network slice, the AMF associated with that network slice can be configured to cause the transmission of auxiliary authentication requirements to the UE during UE registration with the network slice.

[0098] Figure 8A flowchart illustrating the operation of example method 900 performed by example device 200 is shown. In some embodiments, example device 200 may be embodied by a network-based computing device such as AMF or other network functions, which in turn may include a computer program product comprising a non-transient computer-readable medium storing computer program code to be executed by processor 202. As shown in block 902, the device 200 of this example embodiment includes components such as processor 202, memory 204, communication interface 206, etc., for causing the broadcast of loading support information associated with at least one network slice to a user equipment via a network through one or more shared RANs (e.g., gNB, ng-eNB, NodeB, etc.). In some embodiments, the loading support information includes authentication information for utilizing one or more networks (e.g., PLMN, SNPN, etc.) and / or one or more network slices (e.g., PNI-NPN, etc.) of the shared RAN. As shown in block 904, apparatus 200 is further configured with components such as processor 202, communication interface 206, etc., for receiving connection requests from a user equipment via a network, including information identifying a selected network slice that supports loading for unsubscribed user equipment. In response to at least the received connection request, in some embodiments, apparatus 200 may further include components such as processor 202, communication interface 206, etc., for registering the user equipment with the selected network slice. Registration of the user equipment with the selected network slice may include sending network slice-specific credentials to the user equipment. After the registration process is complete, apparatus 200 of the example embodiment may include components such as processor 202, communication interface 206, etc., for establishing a connection between the user equipment and the selected network slice via network infrastructure.

[0099] like Figure 8As outlined, the network is configured to broadcast load support information associated with one or more network slices connected to the network. The broadcast of the load information is generated at least in part by the network's AMF and transmitted at least in part by the RAN associated with the network to one or more UEs within the RAN's communication range. Upon receiving the broadcast of the load information, one or more UEs may reside on the network and / or its network slices. In some embodiments, one or more UEs may receive the broadcast of the load information even if they are not residing on the network or its network slices. UEs receiving the broadcast of the load information may be configured to utilize the load support information and authentication requirement information from the broadcast to select a network slice. Since the UE selects a network slice based on the load support information and authentication requirement information, the UE can select a network slice to which it has already subscribed and thus gain access. Additionally or alternatively, the UE can select a network slice to which it has not subscribed but which supports loading, and thus the UE can gain access to the network slice through a registration process. The UE then sends this selection back to the network's AMF via the RAN based on the broadcast of the load information to initiate a connection with the selected network slice. Upon receiving a connection request, the AMF can further communicate with the UE via the RAN to connect the UE to the appropriate network slice. Furthermore, if the UE requires a new subscription to access the selected network slice, the AMF can process the registration request and / or send additional information to the UE to authorize its access to the network slice.

[0100] Figure 9A flowchart illustrating the operation of example method 1000 performed by example device 200 is shown. In one embodiment, example device 200 may be embodied by a computing device such as a user device, which may further include a computer program product comprising a non-transitory computer-readable medium storing computer program code to be executed by processor 202. As shown in block 1002, device 200 of this example embodiment includes components such as processor 202, memory 204, communication interface 206, etc., for receiving loading support information associated with each of a plurality of network slices via a network. Device 200 includes components such as processor 202, etc., for selecting from the plurality of network slices a network slice that supports loading for unsubscribed user devices. The network slice is selected based on the received loading support information, see block 1004. Device 200 may also include components such as processor 202, etc., configured to select a cell of a network associated with the selected network slice, see block 1006. In some embodiments, device 200 may further include components such as processor 202, communication interface 206, etc., configured to reside on a cell of a network associated with (e.g., including or otherwise supporting) the selected network slice. In some embodiments, device 200 may also include components such as processor 202, communication interface 206, etc., for transmitting connection requests via network infrastructure to access and mobility management functions associated with the selected network slice for initiating a connection with the selected network slice. Furthermore, according to some embodiments, a registration process may be performed between device 200 and another communication device, such that additional registration information can be received and transmitted by device 200, such as by processor 202, communication interface 206, etc., for connecting to the selected network slice.

[0101] like Figure 9As outlined, the UE is configured, for example, to receive a broadcast of load support information from the network via at least the RAN. This broadcast contains load support information and authentication requirement information related to one or more network slices associated with the network. The broadcast informs the UE which network slices are currently accessible to the UE, accessible through an additional load process, or inaccessible. The UE can use the load support information and authentication requirement information to select a network slice that it can access, either because the UE has subscribed to the network slice and can obtain a subscription by registering with the network slice, or because the network slice does not implement any authentication requirements. The UE can then reside on the selected network slice and / or initiate a connection to the AMF associated with that network slice. If the network slice requires a new subscription, the UE can maintain communicative contact with the AMF via the RAN to complete the registration process and / or register for the required subscription in the selected network slice. In instances where the UE is already connected to or resides in a first network slice associated with the network, the UE can reselect a second network slice associated with the network based on the broadcast information and / or additional broadcast information, and / or reconnect to or reside on the network via the second network slice.

[0102] Figure 10 A flowchart illustrating the operation of example method 1100 performed by example device 200 is shown. In some embodiments, example device 200 may be embodied by a computing device of a RAN, which may in turn include a computer program product comprising a non-transient computer-readable medium storing computer program code to be executed by processor 202. As shown in block 1102, device 200 of this example embodiment includes components such as processor 202, memory 204, communication interface 206, etc., for receiving loading support information and authentication request information related to one or more networks from at least access and mobility management functions. In some embodiments, the one or more networks include one or more of public terrestrial mobile networks, independent non-public networks, etc., or combinations thereof. As shown in block 1104, device 200 includes components such as processor 202, communication interface 206, etc., for causing the received loading support information and authentication request information to be broadcast to at least user equipment. In some embodiments, the apparatus 200 further includes components such as a processor 202, a communication interface 206, etc., configured to receive from at least a user equipment and transmit a connection request to at least a network's access and mobility management functions. The connection request includes information identifying a selected network from one or more networks identified by load support information and authentication requirement information that supports loading for unsubscribed user equipment. In some embodiments, the apparatus 200 may further include components such as a processor 202, a communication interface 206, etc., configured to facilitate the establishment of a connection between the user equipment and the selected network.

[0103] like Figure 10 As outlined, for example, the RAN can be shared by multiple networks, such as PLMNs and / or SNPNs. In some embodiments, a PLMN may be publicly accessible to UEs within the RAN's communication range; however, at least a portion of one or more PLMNs may be restricted to UEs that meet certain predefined requirements. For example, a PLMN may include one or more PNI-NPNs, which may be accessible only to UEs with specific service provider subscriptions, even if other portions of the PLMN or network slices may be publicly accessible. To mitigate network traffic between UEs inquiring about accessibility and the specific network that provides them with a separate accessibility response, the RAN can be configured to receive load support information and authentication requirement information from multiple networks sharing the RAN and cause this information to be broadcast to one or more UEs within the RAN's communication range. In some embodiments, a UE may already be camped on a network or connected to a network via the RAN. The UE can then use this broadcast information to select one or more PLMNs and / or SNPNs for camping and / or connecting via the RAN. For example, in an instance where an unsubscribed UE selects a supported SNPN, the RAN can facilitate communication between the unsubscribed UE and the SNPN to complete the registration process and / or register the UE in a subscription associated with the SNPN. The UE and the selected network can then establish a connection via at least the RAN, allowing the UE to access features or services provided by the selected network. In some embodiments, the UE can continue to receive broadcasts from the RAN regarding loading support information and authentication requirements. According to such embodiments, the UE can be configured to reselect and / or reconnect to and / or re-register to one or more other networks sharing the RAN to access services or features not supported by the network to which the UE is currently connected.

[0104] Figure 11A flowchart illustrating the operation of example method 1200 performed by example device 200 is shown. In one embodiment, example device 200 may be embodied by a user equipment, which may further include a computer program product comprising a non-transient computer-readable medium storing computer program code to be executed by processor 202. As shown in block 1202, the device 200 of this example embodiment includes components such as processor 202, memory 204, communication interface 206, etc., for receiving loading support information and authentication requirement information associated with each of a plurality of networks, including one or more of public terrestrial mobile networks or independent non-public networks. Furthermore, device 200 includes components such as processor 202, etc., for additionally selecting from the plurality of networks a network that supports loading for unsubscribed user equipment. Thus, a network is selected based on loading support information and authentication requirement information, see block 1204. As shown in block 1206, the device 200 of the example embodiment also includes components such as processor 202, communication interface 206, etc., for selecting a cell of the selected network. In some embodiments, the apparatus 200 may additionally include components such as a processor 202, a communication interface 206, etc., for residing on a selected cell associated with a selected network. Furthermore, according to some embodiments, the apparatus 200 may also include components such as a processor 202, a communication interface 206, etc., configured to facilitate at least a portion of the registration process for registering with the selected network and establishing a connection with the selected network after completing the registration process and verifying the registration credentials obtained by the apparatus 200.

[0105] like Figure 11As outlined, the UE is configured, for example, to receive a broadcast of load support information from the network via at least the RAN. This broadcast includes load support and / or authentication requirement information related to one or more PLMNs and / or SNPNs utilizing the shared RAN. Thus, the broadcast informs the UE which PLMNs and / or SNPNs are currently accessible to the UE. The broadcast may also inform the UE of which PLMNs and / or SNPNs are accessible through additional load procedures such as registering with a specific service provider and / or enrolling in a subscription. Furthermore, the broadcast may also inform the UE of which PLMNs and / or SNPNs are inaccessible because the UE lacks the predefined credentials specified for the particular PLMN / SNPN and the particular PLMN / SNPN does not support loads from an unsubscribed UE. Therefore, the UE can use the load support and authentication requirement information to select which PLMNs or SNPNs the UE can access. The UE can access the selected network because the UE has a subscription to the selected network or can obtain a subscription through the access procedures provided by the selected network. Furthermore, the UE can access the selected network because the network has no authentication requirements and is therefore publicly accessible. The UE can then choose whether to reside on the selected network and / or initiate a connection with the AMF associated with that network. If the selected PLMN / SNPN requires a new subscription, the UE can maintain communicative contact with the AMF via the RAN to complete the registration process and / or register for the required subscription of the selected PLMN / SNPN. In instances where the UE is already connected to or resides on a first network associated with a shared RAN, the UE can reselect and / or reconnect to a second network based on broadcast information or additional broadcast information.

[0106] It should be understood that, according to this disclosure, the contents of this document regarding... Figures 6-11The described process offers an improvement over traditional systems. Traditional systems for loading and registration of unsubscribed UEs may require trial-and-error communication attempts between the accessing UE and the network-associated AMF to establish a connection with a network slice accessible to the UE. Such traditional systems may require the UE to establish a connection with the AMF before network information regarding authentication and / or loading can be sent to the UE. As will be appreciated by those skilled in the art according to this disclosure, traditional methods involving trial-and-error communication attempts between the UE and the network-associated AMF can lead to increased resource demands on the communication network and the UE. For example, because the UE must connect to a network that it may not be able to access, traditional methods relying on a connection already established between the UE and the network before the UE receives authentication and loading information thus increase the communication signaling traffic through the network's RAN. When the RAN is shared by multiple network slices, SNPNs, PLMNSs, and / or PNI-NPNs, each network slice has its own authentication and loading requirements, which may or may not match the subscription or SLA associated with the UE, thus further exacerbating such problems associated with traditional systems. In such an instance, for a traditional system, the UE would have to connect to each of multiple network slices, SNPN, PLMNS, and / or PNI-NPN and request information from them.

[0107] As described above, the referenced method flowchart can be executed by an apparatus according to a related computer program product including computer program code. It should be understood that each block of the flowchart, and combinations of blocks in the flowchart, can be implemented in various ways, such as hardware, firmware, processors, circuit systems, and / or other devices associated with the execution of software including one or more computer program instructions. For example, one or more of the processes described above can be embodied by computer program instructions. In this regard, the computer program instructions embodying the processes described above can be stored in a memory device (e.g., 204) of an apparatus employing embodiments of the present invention (e.g., 200) and executed by a processor (e.g., 202) of that apparatus. It should be understood that any such computer program instructions can be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus performs the functions specified in the flowchart blocks. These computer program instructions can also be stored in a computer-readable storage medium that can direct a computer or other programmable apparatus to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture, the execution of which implements the functions specified in the flowchart blocks. Computer program instructions may also be loaded onto a computer or other programmable device to cause a series of operations to be performed on the computer or other programmable device, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable device, provide operations for implementing the functions specified in the flowchart blocks.

[0108] Therefore, a computer program product is defined as an instance in which computer program instructions, such as computer-readable program code portions, are stored by at least one non-transitory computer-readable storage medium, wherein the computer program instructions, such as computer-readable program code portions, are configured to perform the aforementioned functions upon execution. In other embodiments, the computer program instructions, such as computer-readable program code portions, do not need to be stored by a non-transitory computer-readable storage medium or otherwise embodied, but may be embodied by a transient medium, wherein the computer program instructions, such as computer-readable program code portions, are still configured to perform the aforementioned functions upon execution.

[0109] Therefore, flowchart blocks support combinations of components used to perform specified functions and combinations of operations used to perform specified functions. It should also be understood that one or more blocks of a flowchart, as well as combinations of blocks in a flowchart, can be implemented by a dedicated hardware-based computer system or a combination of dedicated hardware and computer instructions to perform the specified functions.

[0110] In some embodiments, certain of the operations, methods, steps, processes, etc. described above may be modified or further amplified. Furthermore, in some embodiments, additional optional operations, methods, steps, processes, etc., may be included. Modifications, additions, subtractions, reversals, correlations, proportional relationships, disproportionate relationships, attenuations, and / or amplifications of the above operations can be performed in any order and in any combination. It should also be understood that in instances where a particular operation, method, process, etc., requires specific hardware, such hardware can be considered part of the apparatus 200 used in any such embodiment.

[0111] Benefiting from the teachings presented in the foregoing description and associated drawings, those skilled in the art will conceive of numerous modifications and other embodiments of the invention set forth herein. Therefore, it should be understood that the invention is not limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the appended claims. Furthermore, although the foregoing description and associated drawings describe exemplary embodiments in the context of certain example combinations of elements and / or functions, it should be understood that alternative embodiments may provide different combinations of elements and / or functions without departing from the scope of the appended claims. In this regard, for example, combinations of elements and / or functions different from those explicitly described above are also contemplated as being set forth in some of the appended claims. Although specific terminology is used herein, it is used only in a general and descriptive sense and not for limiting purposes.

Claims

1. A method performed by a user equipment, the method comprising: During the initial communication between the user equipment and the access and mobility management functions, load support information associated with each of the multiple network slices is received via the network (1002). The loading support information includes one or more of network slice-specific authentication requirements and network slice-specific loading availability for each of the plurality of network slices, wherein the network slice-specific authentication requirements include an indication of whether the user equipment needs to be authenticated using each of the plurality of network slices for registration with the selected network slice, and wherein the network slice-specific loading availability includes an indication of whether loading is supported by each of the plurality of network slices. (1004) Select a network slice from the plurality of network slices that supports loading for unsubscribed user devices, wherein the network slice is selected based on the loading support information; Initiate registration with the selected network slice. The user equipment is configured to initiate registration with the network slice when one of the following conditions is met: The network slice does not have slice-specific authentication requirements; The network slice has slice-specific authentication requirements and the user equipment meets the specific authentication requirements; or The network slice has slice-specific authentication requirements and the network slice supports loading for user devices that lack the required credentials. Select (1006) the cell of the network associated with the selected network slice; A connection request is sent via the network to the access and mobility management function associated with the selected network slice for initiating a connection with the selected network slice; Registration information is received from the access and mobility management function via the network, wherein the registration information includes additional loading support information required to connect to the selected network slice; and Connect to the selected network slice via the network.

2. A communication apparatus, comprising: At least one processor; as well as At least one memory including computer program code, The at least one memory and the computer program code are configured, together with the at least one processor, to make the device at least: During the initial communication between the user equipment and the access and mobility management functions, load support information associated with each of the multiple network slices is received via the network (1002). The loading support information includes one or more of network slice-specific authentication requirements and network slice-specific loading availability for each of the plurality of network slices, wherein the network slice-specific authentication requirements include an indication of whether the user equipment needs to be authenticated using each of the plurality of network slices for registering with the selected network slice, and wherein the network slice-specific loading availability includes an indication of whether loading is supported by each of the plurality of network slices. (1004) Select a network slice from the plurality of network slices that supports loading for unsubscribed user devices, wherein the network slice is selected based on the loading support information; Initiate registration with the selected network slice. The user equipment is configured to initiate registration with the network slice when one of the following conditions is met: The network slice does not have slice-specific authentication requirements; The network slice has slice-specific authentication requirements and the user equipment meets the specific authentication requirements; or The network slice has slice-specific authentication requirements and the network slice supports loading for user devices that lack the required credentials. Select (1006) the cell of the network associated with the selected network slice; A connection request is sent via the network to the access and mobility management function associated with the selected network slice for initiating a connection with the selected network slice; Registration information is received from the access and mobility management function via the network, wherein the registration information includes additional loading support information required to connect to the selected network slice; and Connect to the selected network slice via the network.

3. A communication method, comprising: During the initial communication between the user equipment and the access and mobility management functions, load support information and authentication requirement information associated with each of a plurality of networks are received (1202) via the network, said plurality of networks including one or more of public land mobile networks, standalone non-public networks, or public network integrated non-public networks. One or more of the plurality of networks are transmitted via one or more bundled communications, the bundled communications including loading support information for utilizing the one or more networks of the shared radio access network. The loading support information includes one or more of network slice-specific authentication requirements and network slice-specific loading availability for each of the plurality of network slices, wherein the network slice-specific authentication requirements include an indication of whether the user equipment needs to be authenticated using each of the plurality of network slices for registration with the selected network slice, and wherein the network slice-specific loading availability includes an indication of whether loading is supported by each of the plurality of network slices. (1204) Select a network from the plurality of networks that supports loading of unsubscribed user devices, wherein the network is selected based on the loading support information and the authentication requirement information; Select the cell of the network selected by (1206); Send a connection request for connection to the selected network to the access and mobility management function associated with the selected network via the network; Registration information is received from the access and mobility management function via the network, wherein the registration information includes additional loading support information required to connect to the selected network; and Connect to the selected network.

4. The method of claim 3, wherein the loading support information and the authentication requirement information are received via a system information block transmission, and wherein the system information block transmission is sent in response to a request from a user equipment or as a continuous broadcast to multiple user equipments residing in a cell shared by the multiple networks.

5. A communication apparatus, comprising: At least one processor; as well as At least one memory including computer program code, The at least one memory and the computer program code are configured, together with the at least one processor, to make the device at least: During the initial communication between the user equipment and the access and mobility management functions, load support information and authentication requirement information associated with each of a plurality of networks are received via network (1202), said plurality of networks including one or more of public land mobile networks, standalone non-public networks, or public network integrated non-public networks. One or more of the plurality of networks are transmitted via one or more bundled communications, the bundled communications including loading support information for utilizing the one or more networks of the shared radio access network. The loading support information includes one or more of network slice-specific authentication requirements and network slice-specific loading availability for each of the plurality of network slices, wherein the network slice-specific authentication requirements include an indication of whether the user equipment needs to be authenticated using each of the plurality of network slices for registration with the selected network slice, and wherein the network slice-specific loading availability includes an indication of whether loading is supported by each of the plurality of network slices. (1204) Select a network from the plurality of networks that supports loading of unsubscribed user devices, wherein the network is selected based on the loading support information and the authentication requirement information; Select the cell of the network selected by (1206); Send a connection request for connection to the selected network to the access and mobility management function associated with the selected network via the network; Registration information is received from the access and mobility management function via the network, wherein the registration information includes additional loading support information required to connect to the selected network; and Connect to the selected network.

6. The apparatus of claim 5, wherein the loading support information and the authentication requirement information are received and broadcast via a system information block transmission, and wherein the system information block transmission is sent in response to a request from a user equipment or as a continuous broadcast to multiple user equipments residing in a cell shared by the multiple networks.

Images