CN117426123A

CN117426123A - Methods, apparatuses and computer program products for providing cell selection of serving network slices for an area

Info

Publication number: CN117426123A
Application number: CN202280040179.6A
Authority: CN
Inventors: 元盛焕; M·麦格拉斯; O·布拉克奇; M·纳希尔-厄尔-伊斯拉姆; D·钱德拉穆利
Original assignee: Nokia Technologies Oy
Current assignee: Nokia Technologies Oy
Priority date: 2021-04-05
Filing date: 2022-04-05
Publication date: 2024-01-19

Abstract

Methods, apparatuses, and computer program products are described that support non-uniform network slice deployment across a service area of a registration area or tracking area covered by at least a radio access network. The network function transmits a plurality of tracking area codes associated with the network to the user device to indicate the primary tracking area code and the secondary tracking area code to the user device. The selection of the tracking area code may be accomplished by the user device based on the primary tracking area code and the secondary tracking area code and the forbidden tracking area identification list. The user device may be prevented from receiving service from the network slice based on the service area in which the user device attempts to access the network slice. The network function may limit reporting of the tracking area code to the user equipment based on the serving cell identity. Network slicing may be limited to private networks.

Description

Methods, apparatuses and computer program products for providing cell selection of serving network slices for an area

Cross Reference to Related Applications

The present application claims priority from U.S. provisional patent application No.63/200,941, filed on 5, 4, 2021, and U.S. provisional patent application No.63/226,964, filed on 29, 7, 2021, both of which are incorporated herein in their entirety.

Technical Field

Example embodiments relate generally to cell selection associated with network slicing via a communication infrastructure.

Background

The third generation partnership project (3 GPP) is a standard organization for developing protocols for mobile phones, and is known for development and maintenance of various standards including second generation (2G), third generation (3G), fourth generation (4G), long Term Evolution (LTE), and fifth generation (5G) standards. A 5G network is designed as a Service Based Architecture (SBA), or in other words a system architecture, in which system functionality is implemented by a set of network functions that provide services to other authorized network functions to access their services.

The 5G network may include a plurality of base stations (e.g., next generation node bs (gnbs), RAN nodes, etc.) serving one or more cells across a particular area. A cell changes (referred to as a handover in connected mode) when a User Equipment (UE) moves in a specific area to maintain connectivity between the UE and a serving Radio Access Network (RAN). A cell transmits and receives data with a UE via multiple beams. Conditional Handover (CHO) allows the source cell to prepare multiple target cells for the UE for future handover procedures.

The 5G network system allows supporting network slicing, which is an end-to-end logical network supporting some set of network functions. As such, a network slice is a logical network infrastructure that provides specific network capabilities and network characteristics. In a 5G network that includes multiple network slices, a particular network slice may be configured to support particular features (e.g., hardware specifications, network functions, domain access, etc.) that are not common to all network slices. The UE may be configured to access multiple networks and/or network slices through a shared access point. Access to network slices may be limited to UEs associated with certain credentials or meeting certain requirements.

Network slicing (as introduced by 5G systems) contains concepts that allow for differentiated handling of UEs depending on the specific needs of each client. Thus, network slicing in 5G systems makes it possible for a Mobile Network Operator (MNO) to treat customers as belonging to different tenant types, each with corresponding service requirements. The service requirements of a particular tenant group are managed according to the network slice type associated with each tenant type. UEs belonging to a particular tenant type are eligible to use network slices specified according to their respective Service Level Agreements (SLAs) and subscriptions.

The network slices may be configured to be different in terms of their service requirements, such as ultra-reliable low latency communications (URLLC) or enhanced mobile broadband (eMBB), or via tenants providing those specific services. The network slice support is assumed to be uniform in the Tracking Area (TA) so that all cells in the TA have the same network slice support. From the UE perspective, the Registration Area (RA) is a list of TAs that support the same network slice. When the UE registers with the network, the UE may indicate a network slice for access via the requested S-nsai.

The core network analyzes the UE configuration file and subscription data to verify a list of network slices that the UE can access. The core network provides the UE with a list of allowed network slices. The core network knows the current TA of the UE from the registration request and knows the slice support of the adjacent TA. In the RA of the UE, all TAs in the RA of the UE support the allowed network slice selection assistance information (nsaai) of the UE. From the UE perspective, the RA is a list of TAs that support the same network slice. The core network analyzes the UE profile and subscription data to verify which network slices the UE can access.

The 5G system introduces and allows support of non-public networks (NPN), which are networks deployed by the 5G system for non-public use. As such, the NPN is either a separate non-public network (SNPN) independent of network functions provided by a Public Land Mobile Network (PLMN), or a public network integrated NPN (PNI-NPN) operating with support of the PLMN. In order for the UE to access the NPN, a login procedure is performed between the UE and the network to ensure that the UE has or can obtain the appropriate credentials.

Disclosure of Invention

Methods, apparatus, and computer program products are disclosed that facilitate supporting non-uniform network slice deployment(s) within a service area of at least a registration area and/or a tracking area covered by a radio access network.

According to one aspect of the disclosure, a method is provided that includes receiving a plurality of tracking area codes associated with at least one network from a cell. The method may also include selecting a tracking area code from a plurality of tracking area codes associated with at least one network.

In some embodiments, the method may further include identifying a first tracking area code from the plurality of tracking area codes, and one or more second tracking area codes. In some embodiments, the method may further include selecting the first tracking area code or one of the one or more second tracking area codes. In some embodiments, the method may further comprise: one or more identifiers of one or more network slices or one or more network slice groups are received from a cell for at least one respective tracking area code of a plurality of tracking area codes. In some embodiments, the method may further comprise: a tracking area identifier list is received from a cell, the tracking area identifier list including one or more of a forbidden tracking area identifier or an allowed tracking area identifier. In some embodiments, the method may further include determining whether one or more tracking area codes of the plurality of tracking area codes are associated with a tracking area identifier list. In some embodiments, the method may further include determining that one or more of the plurality of tracking area codes allow tracking of the area code. In some embodiments, the method may further include selecting a corresponding allowable tracking area code based on the relative priorities of the one or more allowable tracking area codes. In some embodiments, the method may further include determining that one or more of the plurality of tracking area codes is a forbidden tracking area code. In some embodiments, the method may further include selecting a respective tracking area code based on the relative priorities of the plurality of tracking area codes that are not disabled.

In some embodiments of the method, the prioritization of the one or more second tracking area codes is based on an encoding order associated with the plurality of tracking area codes. In some embodiments of the method, a first tracking area code of the plurality of tracking area codes is associated with a first information element of the system information block. In some embodiments of the method, one or more second tracking area codes of the plurality of tracking area codes are associated with a second information element of the system information block, the second information element being different from the first information element. In some embodiments of the method, the first tracking area code is a primary tracking area code and the one or more second tracking area codes are secondary tracking area codes. In some embodiments of the method, respective ones of the plurality of tracking area codes are mapped to respective single network slice selection assistance information. In some embodiments of the method, the at least one network comprises one or more of a public land mobile network, a standalone non-public network, or a public network integrated non-public network.

According to one aspect of the present disclosure, there is provided an apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, at least cause the apparatus to receive from a cell a plurality of tracking area codes associated with at least one network. The apparatus may also be caused to at least: a tracking area code is selected from a plurality of tracking area codes associated with at least one network.

In some embodiments, the apparatus may be further caused to at least: a first tracking area code, and one or more second tracking area codes, are identified from the plurality of tracking area codes. In some embodiments, the apparatus may be further caused to at least: a first tracking area code, or one of the one or more second tracking area codes, is selected. In some embodiments, the apparatus may be further caused to at least: one or more identifiers of one or more network slices or one or more network slice groups are received from a cell for at least one respective tracking area code of a plurality of tracking area codes. In some embodiments, the apparatus may be further caused to at least: a tracking area identifier list is received from a cell, the tracking area identifier list including one or more of a forbidden tracking area identifier or an allowed tracking area identifier. In some embodiments, the apparatus may be further caused to at least: a determination is made as to whether one or more tracking area codes of the plurality of tracking area codes are associated with the tracking area identifier list. In some embodiments, the apparatus may be further caused to at least: one or more of the plurality of tracking area codes is determined to allow tracking of the area code. In some embodiments, the apparatus may be further caused to at least: based on the relative priorities of the one or more allowed tracking area codes, a corresponding allowed tracking area code is selected. In some embodiments, the apparatus may be further caused to at least: one or more forbidden tracking area codes of the plurality of tracking area codes are determined. In some embodiments, the apparatus may be further caused to at least: based on the relative priorities of the plurality of tracking area codes that are not disabled, a corresponding tracking area code is selected.

In some embodiments of the apparatus, the prioritization of the one or more second tracking area codes is based on an encoding order associated with the plurality of tracking area codes. In some embodiments of the apparatus, a first tracking area code of the plurality of tracking area codes is associated with a first information element of the system information block. In some embodiments of the apparatus, one or more second tracking area codes of the plurality of tracking area codes are associated with a second information element of the system information block, the second information element being different from the first information element. In some embodiments of the apparatus, the first tracking area code is a primary tracking area code and the one or more second tracking area codes are secondary tracking area codes. In some embodiments of the apparatus, respective ones of the plurality of tracking area codes are mapped to respective single network slice selection assistance information. In some embodiments of the apparatus, the at least one network comprises one or more of a public land mobile network, a standalone non-public network, or a public network integrated non-public network.

According to one aspect of the present disclosure, a computer program product is provided, the computer program product comprising at least a non-transitory computer readable storage medium having program code portions stored thereon, wherein the program code portions are configured to receive a plurality of tracking area codes associated with at least one network from a cell when executed by at least a processor. The computer program product may be further configured to select a tracking area code from at least a plurality of tracking area codes associated with at least one network, when executed by at least the processor.

In some embodiments, the computer program product may be further configured to identify at least a first tracking area code, and one or more second tracking area codes, from among the plurality of tracking area codes when executed at least by the processor. In some embodiments, the computer program product may be further configured to select at least the first tracking area code, or one of the one or more second tracking area codes, when executed at least by the processor. In some embodiments, the computer program product may be further configured to, when executed by at least the processor, at least: one or more identifiers of one or more network slices or one or more network slice groups are received from a cell for at least one respective tracking area code of a plurality of tracking area codes. In some embodiments, the computer program product may be further configured to receive, at least when executed by the processor, a tracking area identifier list from at least the cell, the tracking area identifier list including one or more of a forbidden tracking area identifier or an allowed tracking area identifier. In some embodiments, the computer program product may be further configured to determine, at least when executed by the processor, whether one or more tracking area codes of the plurality of tracking area codes are associated with the tracking area identifier list. In some embodiments, the computer program product may be further configured to determine at least one or more allowable tracking area codes of the plurality of tracking area codes when executed at least by the processor. In some embodiments, the computer program product may be further configured to select a respective allowed tracking area code based at least on a relative priority of one or more allowed tracking area codes when executed by at least the processor. In some embodiments, the computer program product may be further configured to determine at least one or more forbidden tracking area codes of the plurality of tracking area codes when executed at least by the processor. In some embodiments, the computer program product may be further configured to select a respective tracking area code based at least on a relative priority of the plurality of tracking area codes that are not disabled when executed at least by the processor.

In some embodiments of the computer program product, the prioritization of the one or more second tracking area codes is based on an encoding order associated with the plurality of tracking area codes. In some embodiments of the computer program product, a first tracking area code of the plurality of tracking area codes is associated with a first information element of the system information block. In some embodiments of the computer program product, one or more second tracking area codes of the plurality of tracking area codes are associated with a second information element of the system information block, the second information element being different from the first information element. In some embodiments of the computer program product, the first tracking area code is a primary tracking area code and the one or more second tracking area codes are secondary tracking area codes. In some embodiments of the computer program product, respective ones of the plurality of tracking area codes are mapped to respective single network slice selection assistance information. In some embodiments of the computer program product, the at least one network comprises one or more of a public land mobile network, a standalone non-public network, or a public network integrated non-public network.

According to one aspect of the disclosure, an apparatus is provided that includes means for receiving a plurality of tracking area codes associated with at least one network from a cell. The apparatus may also include means for selecting a tracking area code from a plurality of tracking area codes associated with at least one network.

In some embodiments, the apparatus may further include means for identifying a first tracking area code from the plurality of tracking area codes, and one or more second tracking area codes. In some embodiments, the apparatus may further comprise means for selecting the first tracking area code, or one of the one or more second tracking area codes. In some embodiments, the apparatus may further include means for receiving one or more identifiers of one or more network slices or one or more network slice groups from the cell for at least one respective tracking area code of the plurality of tracking area codes. In some embodiments, the apparatus may further include means for receiving a tracking area identifier list from the cell, the tracking area identifier list including one or more of a forbidden tracking area identifier or an allowed tracking area identifier. In some embodiments, the apparatus may further include means for determining whether one or more tracking area codes of the plurality of tracking area codes are associated with a tracking area identifier list. In some embodiments, the apparatus may further comprise means for determining one or more of the plurality of tracking area codes to allow tracking of the area code. In some embodiments, the apparatus may further comprise means for selecting a respective allowed tracking area code based on the relative priorities of the one or more allowed tracking area codes. In some embodiments, the apparatus may further include means for determining one or more forbidden tracking area codes of the plurality of tracking area codes. In some embodiments, the apparatus may further include means for selecting a respective tracking area code based on the relative priorities of the plurality of tracking area codes that are not disabled.

According to one aspect of the present disclosure, there is provided a method comprising: the paging area is determined based on one or more first single network slice selection assistance information associated with one or more protocol data unit sessions and one or more second single network slice selection assistance information, wherein the one or more second single network slice selection assistance information is supported by at least one radio access network node associated with the registration area, wherein the one or more protocol data unit sessions cause paging.

In some embodiments, the method may further include retrieving, via at least an application protocol process, a plurality of tracking area codes including a first tracking area code and one or more second tracking area codes. In some embodiments, the method may further include causing transmission of a plurality of tracking area codes associated with the at least one network to the user equipment at least via the cell. In some embodiments, the method may further include receiving a registration request from the user equipment via at least the cell, the registration request including a primary tracking area code and one or more secondary tracking area codes. In some embodiments, the method may further comprise causing transmission of at least an additional secondary tracking area code to the user equipment at least via the cell. In some embodiments, the method may further include assigning a registration area to the user device based at least on the primary tracking area code and the one or more secondary tracking area codes. In some embodiments, the method may further include determining a tracking area identifier list including one or more of a forbidden tracking area identifier or an allowed tracking area identifier. In some embodiments, the method may further comprise causing transmission of the tracking area identifier list to the user equipment at least via the cell.

In some embodiments of the method, the at least one network comprises one or more of a public land mobile network, a standalone non-public network, or a public network integrated non-public network. In some embodiments of the method, the prioritization of the one or more second tracking area codes is based on an encoding order associated with the plurality of tracking area codes. In some embodiments of the method, a first tracking area code of the plurality of tracking area codes is associated with a first information element of the system information block. In some embodiments of the method, one or more second tracking area codes of the plurality of tracking area codes are associated with a second information element of the system information block, the second information element being different from the first information element. In some embodiments of the method, the first tracking area code is a primary tracking area code and the one or more second tracking area codes are secondary tracking area codes. In some embodiments of the method, respective ones of the plurality of tracking area codes are mapped to respective single network slice selection assistance information.

According to one aspect of the present disclosure, there is provided an apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to: the paging area is determined based on one or more first single network slice selection assistance information associated with one or more protocol data unit sessions and one or more second single network slice selection assistance information, wherein the one or more second single network slice selection assistance information is supported by at least one radio access network node associated with the registration area, wherein the one or more protocol data unit sessions cause paging.

In some embodiments, the apparatus may be further caused to at least: a plurality of tracking area codes including a first tracking area code and one or more second tracking area codes are retrieved via at least an application protocol process. In some embodiments, the apparatus may be further caused to at least: causing transmission of a plurality of tracking area codes associated with at least one network to a user equipment via at least a cell. In some embodiments, the apparatus may be further caused to at least: a registration request is received from a user equipment via at least a cell, the registration request including a primary tracking area code and one or more secondary tracking area codes. In some embodiments, the apparatus may be further caused to at least: causing transmission of at least an additional secondary tracking area code to the user equipment via at least the cell. In some embodiments, the apparatus may be further caused to at least: a registration area is assigned to the user device based at least on the primary tracking area code and one or more secondary tracking area codes. In some embodiments, the apparatus may be further caused to at least: a tracking area identifier list is determined that includes one or more of a forbidden tracking area identifier or an allowed tracking area identifier. In some embodiments, the apparatus may be further caused to at least: causing a transmission of a tracking area identifier list to the user equipment at least via the cell.

In some embodiments of the apparatus, the at least one network comprises one or more of a public land mobile network, a standalone non-public network, or a public network integrated non-public network. In some embodiments of the apparatus, the prioritization of the one or more second tracking area codes is based on an encoding order associated with the plurality of tracking area codes. In some embodiments of the apparatus, a first tracking area code of the plurality of tracking area codes is associated with a first information element of the system information block. In some embodiments of the apparatus, one or more second tracking area codes of the plurality of tracking area codes are associated with a second information element of the system information block, the second information element being different from the first information element. In some embodiments of the apparatus, the first tracking area code is a primary tracking area code and the one or more second tracking area codes are secondary tracking area codes. In some embodiments of the apparatus, respective ones of the plurality of tracking area codes are mapped to respective single network slice selection assistance information.

According to one aspect of the present disclosure, there is provided a computer program product comprising at least a non-transitory computer readable storage medium having program code portions stored thereon, wherein the program code portions are configured to, when executed by at least a processor, determine a paging area based on one or more first single network slice selection assistance information associated with one or more protocol data unit sessions, and one or more second single network slice selection assistance information, wherein the one or more second single network slice selection assistance information is supported by at least one radio access network node associated with a registration area, wherein the one or more protocol data unit sessions cause paging.

In some embodiments, the computer program product may be further configured to, when executed by at least the processor, at least: a plurality of tracking area codes including a first tracking area code and one or more second tracking area codes are retrieved via at least an application protocol process. In some embodiments, the computer program product may be further configured to, when executed by at least the processor, at least: causing transmission of a plurality of tracking area codes associated with at least one network to a user equipment via at least a cell. In some embodiments, the computer program product may be further configured to, when executed by at least the processor, at least: a registration request is received from a user equipment via at least a cell, the registration request including a primary tracking area code and one or more secondary tracking area codes. In some embodiments, the computer program product may be further configured to, when executed by at least the processor, at least: causing transmission of at least an additional secondary tracking area code to the user equipment via at least the cell. In some embodiments, the computer program product may be further configured to, when executed by at least the processor, at least: a registration area is assigned to the user device based at least on the primary tracking area code and one or more secondary tracking area codes. In some embodiments, the computer program product may be further configured to, when executed by at least the processor, at least: a tracking area identifier list is determined that includes one or more of a forbidden tracking area identifier or an allowed tracking area identifier. In some embodiments, the computer program product may be further configured to, when executed by at least the processor, at least: causing a transmission of a tracking area identifier list to the user equipment at least via the cell.

In some embodiments of the computer program product, the at least one network comprises one or more of a public land mobile network, a standalone non-public network, or a public network integrated non-public network. In some embodiments of the computer program product, the prioritization of the one or more second tracking area codes is based on an encoding order associated with the plurality of tracking area codes. In some embodiments of the computer program product, a first tracking area code of the plurality of tracking area codes is associated with a first information element of the system information block. In some embodiments of the computer program product, one or more second tracking area codes of the plurality of tracking area codes are associated with a second information element of the system information block, the second information element being different from the first information element. In some embodiments of the computer program product, the first tracking area code is a primary tracking area code and the one or more second tracking area codes are secondary tracking area codes. In some embodiments of the computer program product, respective ones of the plurality of tracking area codes are mapped to respective single network slice selection assistance information.

According to one aspect of the disclosure, an apparatus is provided that includes means for determining a paging area based on one or more first single network slice selection assistance information associated with one or more protocol data unit sessions, and one or more second single network slice selection assistance information, wherein the one or more second single network slice selection assistance information is supported by at least one radio access network node associated with a registration area, wherein the one or more protocol data unit sessions cause paging.

In some embodiments, the apparatus may further include means for retrieving, via at least an application protocol process, a plurality of tracking area codes including a first tracking area code and one or more second tracking area codes. In some embodiments, the apparatus may further include means for causing transmission of a plurality of tracking area codes associated with the at least one network to the user equipment at least via the cell. In some embodiments, the apparatus may further include means for receiving a registration request from a user equipment via at least a cell, the registration request including a primary tracking area code and one or more secondary tracking area codes. In some embodiments, the apparatus may further comprise means for causing transmission of at least an additional secondary tracking area code to the user equipment at least via the cell. In some embodiments, the apparatus may further include means for assigning a registration area to the user device based at least on the primary tracking area code and the one or more secondary tracking area codes. In some embodiments, the apparatus may further include means for determining a tracking area identifier list that includes one or more of a forbidden tracking area identifier or an allowed tracking area identifier. In some embodiments, the apparatus may further comprise means for causing transmission of the tracking area identifier list to the user equipment at least via the cell.

According to one aspect of the disclosure, a method is provided that includes causing transmission of a plurality of tracking area codes associated with at least one network to at least one user device, wherein respective ones of the plurality of tracking area codes are associated with one or more network slices, or one or more groups of network slices.

In some embodiments, the method may further include causing transmission of one or more identifiers of one or more network slices or one or more network slice groups to at least one user device for at least one respective tracking area code of the plurality of tracking area codes. In some embodiments, the method may further include receiving a plurality of tracking area codes associated with the at least one network from the network, wherein the plurality of tracking area codes includes a first tracking area code and one or more second tracking area codes.

According to one aspect of the present disclosure, there is provided an apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to: causing transmission of a plurality of tracking area codes associated with at least one network to at least one user device, wherein respective ones of the plurality of tracking area codes are associated with one or more network slices or one or more groups of network slices.

In some embodiments, the apparatus may be further caused to at least: the method further includes causing transmission of one or more identifiers of one or more network slices or one or more network slice groups to at least one user device for at least one respective tracking area code of the plurality of tracking area codes. In some embodiments, the apparatus may be further caused to at least: a plurality of tracking area codes associated with at least one network are received from the network, wherein the plurality of tracking area codes includes a first tracking area code and one or more second tracking area codes.

According to one aspect of the present disclosure, there is provided a computer program product comprising at least a non-transitory computer readable storage medium having program code portions stored thereon, wherein the program code portions are configured, when executed by at least a processor, to cause transmission of a plurality of tracking area codes associated with at least one network to at least one user device, wherein respective ones of the plurality of tracking area codes are associated with one or more network slices, or one or more groups of network slices.

In some embodiments, the computer program product may be further configured to, when executed by at least the processor, at least: the method further includes causing transmission of one or more identifiers of one or more network slices or one or more network slice groups to at least one user device for at least one respective tracking area code of the plurality of tracking area codes. In some embodiments, the computer program product may be further configured to, when executed by at least the processor, at least: a plurality of tracking area codes associated with at least one network are received from the network, wherein the plurality of tracking area codes includes a first tracking area code and one or more second tracking area codes.

According to one aspect of the disclosure, an apparatus is provided that includes means for causing transmission of a plurality of tracking area codes associated with at least one network to at least one user device, wherein respective ones of the plurality of tracking area codes are associated with one or more network slices, or one or more groups of network slices.

In some embodiments, the apparatus may further include means for causing transmission of one or more identifiers of one or more network slices or one or more network slice groups to at least one user device for at least one respective tracking area code of the plurality of tracking area codes. In some embodiments, the apparatus may further include means for receiving a plurality of tracking area codes associated with at least one network from the network, wherein the plurality of tracking area codes includes a first tracking area code and one or more second tracking area codes.

In an example embodiment, a method is provided that includes causing transmission of a message including a tracking area identity list from a first node to a second node. The tracking area identity list includes a plurality of tracking area identities. The respective tracking area identity of the plurality of tracking area identities is indicated as a primary tracking area identity or a secondary tracking area identity. The method further includes receiving a response from the second node based at least on the message including the tracking area identification list.

In another example embodiment, an apparatus is provided, the apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to: causing a message to be transmitted from the first node to the second node that includes the tracking area identification list. The tracking area identity list includes a plurality of tracking area identities. The respective tracking area identity of the plurality of tracking area identities is indicated as a primary tracking area identity or a secondary tracking area identity. The at least one memory and the computer program code are also configured to, with the at least one processor, cause the apparatus at least to: a response is received from the second node based on the message including the tracking area identification list.

In another example embodiment, a computer program product is provided that includes a non-transitory computer-readable storage medium having program code portions stored thereon that are configured, upon execution, to cause transmission of a message including a tracking area identification list from a first node to a second node. The tracking area identity list includes a plurality of tracking area identities. The respective tracking area identity of the plurality of tracking area identities is indicated as a primary tracking area identity or a secondary tracking area identity. The program code portion is further configured to receive a response from the second node based at least on the message including the tracking area identification list when executed.

In yet another example embodiment, an apparatus is provided that includes means for causing transmission of a message including a tracking area identity list from a first node to a second node. The tracking area identity list includes a plurality of tracking area identities. The respective tracking area identity of the plurality of tracking area identities is indicated as a primary tracking area identity or a secondary tracking area identity. The apparatus also includes means for receiving a response from the second node based at least on the message including the tracking area identification list.

With respect to a method, apparatus and/or computer program product, in one embodiment, a first node comprises a first next generation radio access network (NG-RAN) node and a second node comprises a second NG-RAN node. In this example embodiment, the message may include an Xn setup request and the response may include an Xn setup response. Alternatively, the message may include an NG-RAN node configuration update, and the response may include an NG-RAN node configuration update acknowledgement. In one embodiment, the first node comprises a next generation node B distributed unit (gNB-DU) and the second node comprises a next generation node B central unit (gNB-CU). In this example embodiment, the message may include an F1 setup request, and the response may include an F1 setup response. Alternatively, the message may include a gNB-DU configuration update, and the response may include a gNB-DU configuration update acknowledgement. In an example embodiment, the first node comprises a first next generation radio access node (NG-RAN) node and the second node comprises an access and mobility management function (AMF). In this example embodiment, the message may include a Next Generation (NG) setup request, and the response may include a NG setup response. Alternatively, the message may include a Radio Access Node (RAN) configuration update, and the response may include a RAN configuration update acknowledgement. The message may include an initial User Equipment (UE) message. In an example embodiment, the message may include a semantic description indicating a wide area slice classification or a limited area slice classification.

Various other aspects are also described in the following detailed description and the appended claims.

Drawings

Having thus described embodiments of the present disclosure in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 illustrates an example architecture of a communication network, according to some embodiments;

FIG. 2 illustrates an example architecture of a communication network, according to some embodiments;

FIG. 3 illustrates an example architecture of a communication network, according to some embodiments;

FIG. 4 illustrates an example computing device for communicating with other network entities over a communication network, in accordance with some embodiments;

FIG. 5 illustrates an example architecture of a communication network including network slices, according to some embodiments;

fig. 6 is a block diagram illustrating an example single network slice selection assistance information format in accordance with some embodiments;

FIG. 7 is a block diagram illustrating an example area associated with a communication network, according to some example embodiments;

FIG. 8 is a block diagram illustrating example areas associated with a communication network according to some example embodiments;

fig. 9A is a block diagram illustrating an example area associated with a communication network, according to some example embodiments;

fig. 9B is a block diagram illustrating an example area associated with a communication network, according to some example embodiments;

Fig. 10 is a signaling diagram illustrating communications, such as between a communication device and a network entity, according to some example embodiments;

FIG. 11 is a flowchart illustrating operations performed, such as by a communication device or other client device, according to some example embodiments;

FIG. 12 is a flowchart illustrating operations performed, such as by a communication device or other client device, according to some example embodiments;

FIG. 13 is a flowchart illustrating operations performed, such as by a communication device or other client device, according to some example embodiments;

fig. 14A is a signaling diagram illustrating communications, such as between network entities, according to some example embodiments;

fig. 14B is a signaling diagram illustrating communications, such as between network entities, according to some example embodiments;

fig. 15A is a signaling diagram illustrating communications, such as between network entities, according to some example embodiments;

fig. 15B is a signaling diagram illustrating communications, such as between network entities, according to some example embodiments;

fig. 16A is a signaling diagram illustrating communications, such as between network entities, according to some example embodiments;

fig. 16B is a signaling diagram illustrating communications, such as between network entities, according to some example embodiments;

Fig. 17A is a signaling diagram illustrating communications, such as between network entities, according to some example embodiments;

fig. 17B is a signaling diagram illustrating communications, such as between network entities, according to some example embodiments; and

fig. 18 is a flowchart illustrating operations performed, such as by a network entity, according to some example embodiments.

Detailed Description

Some embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. Indeed, 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 satisfy applicable legal requirements. The term "or" is used herein in both the alternative sense and the connective sense unless otherwise indicated. The terms "illustrative" and "exemplary" are used as examples without an indication of quality level. Like numbers refer to like elements throughout. As used herein, the terms "data," "content," "information," and similar terms may be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present invention. Thus, the use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.

Furthermore, as used herein, the term "circuitry" refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) A combination of circuitry and computer program product(s), comprising software and/or firmware instructions stored on one or more computer-readable memories, which work together to cause an apparatus to perform one or more functions described herein; and (c) circuitry, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that requires software or firmware to operate, even if the software or firmware is not physically present. This definition of "circuitry" applies to all uses of this term herein, including all uses in any claims. As another example, as used herein, the term "circuitry" also includes an implementation that includes one or more processors and/or portions thereof, as well as accompanying software and/or firmware. As another example, the term "circuitry" as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit or a similar integrated circuit in a server, a cellular network device, other network device, and/or other computing device for a mobile phone.

Furthermore, as used herein, the terms "node," "entity," "intermediate entity," "intermediate," and similar terms may be used interchangeably to refer to a computer connected via one or more networks, or a program running on one or more networks capable of data creation, modification, deletion, transmission, reception, and/or storage, in accordance with embodiments of the present invention. Thus, the use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.

Furthermore, as used herein, the terms "user device," "user apparatus," "device," "mobile device," "personal computer," "laptop," "notebook," "desktop computer," "desktop," "mobile phone," "tablet," "smart phone," "smart device," "cell phone," "computing device," "communication device," "user communication device," "terminal," and similar terms may be used interchangeably to refer to an apparatus (such as may be embodied by a computing device) configured to access one or more networks for at least the purpose of wired and/or wireless transmission of communication signals in accordance with embodiments of the present disclosure. Thus, the use of any such terms should not be taken to limit the spirit and scope of embodiments of the present disclosure.

Further, as used herein, the terms "network slice," "particular slice," "network portion," and similar terms may be used interchangeably to refer to an end-to-end logical communication network or portion thereof within a PLMN, SNPN, PNI-NPN, or another network.

As defined herein, a "computer-readable storage medium" that refers to a non-transitory physical storage medium (e.g., a volatile or non-volatile memory device) may be distinguished from a "computer-readable transmission medium" that refers to an electromagnetic signal. Such a medium may take many forms, including, but not limited to, non-transitory computer-readable storage media (e.g., non-volatile media, volatile media), and transmission media. For example, transmission media includes coaxial cables, copper wire, fiber optic cables, and carrier waves (such as acoustic waves and electromagnetic waves) that propagate through space without wires or cables, including radio, optical and infrared waves. Signals include man-made transient changes in amplitude, frequency, phase, polarization, or other physical properties that are transmitted over a transmission medium. Examples of non-transitory 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 disk read-only memory (CD-ROM), digital Versatile Disks (DVD), blu-ray discs (BD), etc., or a combination thereof), random Access Memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), FLASH-EPROM, or any other non-transitory media from which a computer can read. The term "computer-readable storage medium" is used herein to refer to any computer-readable medium except transmission media. However, it should be appreciated that where an embodiment is described as using a computer-readable storage medium, in alternative embodiments, other types of computer-readable storage media may be used in place of, or in addition to, computer-readable storage media.

In the following, certain embodiments are explained with reference to communication devices capable of communicating via a wired and/or wireless network, as well as communication systems serving such communication devices. Before explaining these example embodiments in detail, some general principles of a wired and/or wireless communication system, its access system, and a communication device are briefly explained with reference to fig. 1-3 to help understand the techniques behind the described examples.

According to some embodiments, a communication device or terminal may be provided for wireless access via a cell, base station, access point, or the like (e.g., a wireless transmitter and/or receiver node providing an access point for a radio access communication system and/or other forms of wired and/or wireless networks), or a combination thereof. Such wired and/or wireless networks include, but are not limited to, networks configured to conform to 2G, 3G, 4G, LTE, 5G, and/or any other similar or yet to be developed future communication network standards. The present disclosure contemplates that any method, apparatus, computer program code, and any portion or combination thereof, may also be implemented using a communication network and associated (as will be developed in the future and understood by those skilled in the art in light of the present disclosure) standards that have not yet been developed.

The access point and the communication therethrough are typically controlled by at least one suitable control means in order to effect the operation thereof and the management of the mobile communication devices with which it communicates. In some embodiments, the control means of the node may be integrated with, coupled to, and/or otherwise provided for controlling the access point. In some embodiments, the control means may be arranged to allow communication between the user equipment and the core network or a network entity of the core network. To this end, the control means may comprise at least one memory, at least one data processing unit (such as a processor, etc.), and an input/output interface (e.g. global positioning system receiver/transmitter, keyboard, mouse, touch pad, display, universal Serial Bus (USB), bluetooth, ethernet, wired/wireless connection, etc., or a combination thereof). Via the interface, the control means may be coupled to the relevant other components of the access point. The control means may be configured to execute appropriate software code to provide the control functions. It should be appreciated that similar components may be provided in a control device provided elsewhere in the network system, e.g. in a core network entity. The control means may be interconnected with other control entities. The control means and functions may be distributed among a plurality of control units. In some embodiments, each base station may comprise control means. In alternative embodiments, two or more base stations may share a control device.

The access point and associated controller may communicate with each other via a fixed line connection and/or via a radio interface. The logical connection between the base station nodes may be provided by, for example, X2, S1, a similar interface, or a combination thereof. The interface may be used, for example, to coordinate the operation of the stations and to perform reselection or handoff operations. The logical communication connection between the initial communication node and the final communication node of the network may comprise a plurality of intermediate nodes. Further, any node may be added to or removed from the logical communication connection as needed to establish and maintain network function communications.

The communication device or user equipment may comprise any suitable device capable of at least receiving a communication signal comprising data. The 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 user interface means. Non-limiting examples include a Mobile Station (MS), such as a mobile phone, or so-called "smart phone", a portable computer, such as a laptop or tablet computer equipped with a wireless interface card or other wireless interface facility, a Personal Data Assistant (PDA) provided with wireless communication capabilities, or any combination of these, or the like. Other examples include wearable wireless devices (such as devices integrated with watches or smart watches, glasses, helmets, hats, clothing, headsets with wireless connection capabilities, jewelry, etc.), universal Serial Bus (USB) sticks with wireless capabilities, modem data cards, machine type devices, or any combination of these, etc.

In some embodiments, a communication device (e.g., configured for communication with a wireless network or core network entity) may be exemplified by a handheld or other mobile communication device or user equipment. The mobile communication device may be provided with wireless communication capabilities and appropriate electronic control means for enabling its operation. Thus, the communication device may be provided with at least one data processing entity (e.g. a central processing unit and/or a core processor), at least one memory and possibly other components such as additional processors and memory for use in software and hardware assisted execution of tasks it is intended to perform. The data processing, storage and other associated control means may be provided on a suitable circuit board and/or in a chipset. The data processing and memory functions provided by the control means of the communication device are configured to cause control and signalling operations according to certain embodiments described later in this specification. The user may control the operation of the communication device by means of a suitable user interface, such as a touch sensitive display or touch pad and/or keypad, one or more actuator buttons, voice commands, combinations of these, etc. Speakers and microphones are also typically provided. In addition, the mobile communication device may include suitable connectors (wired or wireless) to other devices and/or for connecting external accessories thereto (e.g., hands-free devices).

In some embodiments, the communication device may communicate wirelessly via one or more suitable means for receiving and transmitting signals (e.g., a global positioning system receiver/transmitter, a remote touchpad interface with a remote display, a Wi-Fi interface, etc.). In some embodiments, the radio unit may be connected to the control means of the device. The radio unit may comprise a radio part and associated antenna means. The antenna arrangement may be arranged inside or outside the communication device.

Fig. 1-3 illustrate various example architectures of a communication network 100 in which various methods, apparatuses, and computer program products may be executed and/or used. In some embodiments, the communication network 100 may include any suitable configuration, number, orientation, positioning, and/or size of components and dedicated devices configured to provide an air interface (e.g., a New Radio (NR)) for communication or connection between the user equipment 102 (UE 102) and the data network 116 (DN 116) via the core network 101 (CN 101) of the communication network 100. The UE 102 may be associated with one or more devices associated with one or more Network Function (NF) service consumers. As illustrated in fig. 1, a communication network 100 may be provided in which a UE 102 is in operative communication with a radio access network 104 (RAN 104), such as through a transmission tower, a base station, an access point, a network node, or the like. In some embodiments, RAN 104 may communicate with CN 101 or components or entities thereof. In some embodiments, CN 101 may facilitate communications between UE 102 and DN 116, such as for sending data, messages, requests, etc., or a combination thereof. In some embodiments, DN 116 or CN 101 can 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 Proxy (SCP), secure Edge Protection Proxy (SEPP), policy Charging Function (PCF), etc., or a combination thereof.

In the context of a 5G network, such as illustrated in fig. 2 and 3, 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 and/or hosted by one or more connected network devices or dedicated hardware. In some embodiments, UE 102 may connect to RAN 104, then RAN 104 may relay communications between UE 102 and CN 101, CN 101 connects to DN 116, and DN 116 may communicate with one or more AS/AFs 112. In some embodiments, UE 102 may communicate with RAN 104, and RAN 104 may act as a relay between UE 102 and other components or services of CN 101. For example, in some embodiments, the UE 102 may communicate with the RAN 104, which in turn may communicate with the access and mobility management function 108 (AMF 108). In other examples or embodiments, the UE 102 may communicate directly with the 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 charging 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 the like.

In some embodiments, the SMF 110 may communicate with one or more user plane functions 106 (UPFs 106, 106a, 106b, collectively "UPFs 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.

In some embodiments, the UE 102 may include a single mode device or a dual mode device such that the UE 102 may connect to one or more RANs (e.g., RAN 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, etc., that may be used to connect UE 102 to CN 101. In some embodiments, RAN 104 may include, or be implemented using, a chip in UE 102 (such as a silicon chip that may be paired with, or otherwise identified by, a similar chip in CN 101), so that RAN 104 may establish a connection or communication line between UE 102 and CN 101 by identifying and pairing a chip within UE 102 with a chip within CN 101. In some embodiments, RAN 104 may implement one or more base stations, towers, etc. to communicate between UE 102 and AMF 108 of CN 101.

In some embodiments, communication network 100 or components thereof (e.g., base stations, towers, etc.) may be configured to communicate with communication devices (e.g., UE 102) such as cellular telephones, etc., over a plurality of different frequency bands (e.g., FR1 (below 6 GHz), FR2 (millimeter waves), other suitable frequency bands, sub-bands thereof, etc.). In some embodiments, communication network 100 may include or employ massive multiple-input multiple-output (MIMO) antennas. In some embodiments, communication network 100 may include multi-user MIMO (MU-MIMO) antennas. In some embodiments, the communication network 100 may employ edge computation whereby the computation server is communicatively, physically, computationally, and/or temporally closer to the communication device (e.g., UE 102) in order to reduce latency and data traffic congestion. In some embodiments, communication network 100 may employ other technologies, devices, or technologies, such as small cells, low power RANs, beamforming of radio waves, wi-Fi cellular convergence, non-orthogonal multiple access (NOMA), channel coding, and the like, or combinations thereof.

As illustrated in fig. 3, the UE 102 may be configured to communicate with the CN 101 in an N1 interface, e.g., according to a non-access stratum (NAS) protocol. In some embodiments, RAN 104 may be configured to communicate with CN 101 or its components (e.g., AMF 108) in an N2 interface (e.g., in a control plane between a base station of RAN 104 and AMF 108). In some embodiments, RAN 104 may be configured to communicate with UPF 106 in an N3 interface (e.g., in a user plane). In some embodiments, AMF 108 and/or SMF 110 may be configured to communicate with other services or network entities within CN 101 in a variety of different interfaces and/or according to a variety of different protocols. For example, in some embodiments, the AMF 108 and/or the SMF 110 may be configured to communicate with the AUSF 120 in a Nausf interface or an N12 interface. In some embodiments, AMF 108 and/or SMF 110 may be configured to communicate with NSSF 122 in an Nnssf interface. In some embodiments, AMF 108 and/or SMF 110 may be configured to communicate with NRF 124 in an Nnrf interface. In some embodiments, AMF 108 and/or SMF 110 may be configured to communicate with PCF 114 in an Npcf interface or an N7 interface. In some embodiments, AMF 108 and/or SMF 110 may be configured to communicate with NWDAF 126 in an Nnwdaf interface. In some embodiments, the AMF 108 and/or SMF 110 may be configured to communicate with the UDM 118 in a Nudm interface, an N8 interface, or an N10 interface. In some embodiments, AMF 108 and/or SMF 110 may be configured to communicate with AS/AF 112 in a Naf interface. In some embodiments, the SMF 110 may be configured to communicate with the UPF 106 in an N4 interface, which may serve as a bridge between the control plane and the user plane, such as serving as a channel for Protocol Data Unit (PDU) sessions during which information is sent between, for example, the UE 102 and the CN 101 or components/services thereof.

It should be appreciated that certain example embodiments described herein occur in the context of a telecommunications network, including but not limited to a telecommunications network that conforms to and/or otherwise contains aspects of a fifth generation (5G) architecture. Although fig. 1-3 illustrate various configurations and/or components of an example architecture of a communication network 100, many other systems, system configurations, networks, network entities, and paths/protocols for communication therein are contemplated and considered within the scope of this disclosure.

Although the methods, apparatus/means, and computer program products/codes described herein are described in the context of fifth generation core networks (5 GC) and systems, such as illustrated in fig. 1-3 and described above, the described methods, apparatus, and computer program products may be applied in a broader context within any suitable telecommunication systems, networks, standards, and/or protocols. It should be appreciated that the described methods, apparatus and computer program products may also be applied to future networks and systems not yet developed, as will be apparent to those skilled in the art in light of the present disclosure.

Turning now to fig. 4, an example of an apparatus that may be embodied by a user device or by a network entity (such as a server or other computing device) is depicted in accordance with an example embodiment of the present disclosure. The apparatus 200 of example embodiments may be configured to perform the functions described herein as described below in connection with the flowcharts and block diagrams presented herein. In any instance, the apparatus 200 may be more generally embodied by a computing device, such as a server, personal computer, computer workstation, or other type of computing device (including those that function as components of a user device and/or a wireless network or wireless local area network). Regardless of the manner in which the apparatus 200 is embodied, the apparatus of the example embodiments may be configured as shown in fig. 4 to include a processor 202 and a memory device 204, and in some embodiments and/or a communication interface 206, associated therewith, or otherwise in communication therewith.

Although not illustrated, the apparatus of example embodiments may also optionally include a user interface, such as a touch screen, display, keyboard, or the like, or a combination thereof. Further, an apparatus according to an example embodiment may be configured with global positioning circuitry including a global positioning receiver and/or a global positioning transmitter configured to communicate with one or more global navigation satellite systems (e.g., global Positioning System (GPS), GLONASS, galileo, etc., or a combination thereof). The global positioning circuitry may be configured to transmit and/or receive direct/indirect satellite and/or cellular signals to determine geographic location data (e.g., latitude, longitude, altitude, geographic coordinates, etc., or a combination thereof) of the apparatus and/or another communication device associated with the apparatus or one or more global navigation satellite systems.

The processor 202 (and/or a coprocessor, or any other circuitry that assists or is otherwise associated with the processor) may communicate with the memory device 204 via a bus for communicating information among the components of the apparatus 200. For example, the memory device may include one or more volatile and/or non-volatile memories, such as a non-transitory memory device. 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 may be retrieved by a machine (e.g., a computing device, such as a processor). The memory device may be configured to store information, data, content, applications, instructions or the like, or a combination thereof, for enabling the apparatus to carry out various functions in accordance with example embodiments. For example, the memory device may be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device may be configured to store instructions for execution by the processor.

In some embodiments, the apparatus 200 may be embodied in various computing devices as described above. However, in some embodiments, the apparatus may be embodied as a chip or chip set. 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 protection, and/or electrical interaction constraints for the component circuitry included thereon. Thus, in some cases, the apparatus may be configured to implement embodiments of the invention on a single chip or as a single "system on a chip". As such, in some cases, a chip or chipset may constitute a component for performing one or more operations to provide the functionality described herein.

The processor 202 may be embodied in a number of different ways. For example, a processor may be embodied as one or more of various hardware processing components, such as a coprocessor, a microprocessor, a controller, a Digital Signal Processor (DSP), a processing element with or without an accompanying DSP, or various other circuitry including integrated circuits such as, by way of example, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. Thus, in some embodiments, a processor may include one or more processing cores configured to execute independently. Multi-core processors may implement multiprocessing within a single physical package. Additionally or alternatively, the processors may include one or more processors configured in series via a bus to enable independent execution of instructions, pipelines, and/or multiple threads.

In an example embodiment, the processor 202 may be configured to execute instructions stored in the memory device 204 or otherwise accessible to the processor. Alternatively or additionally, the processor may be configured to perform hard-coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, a processor may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to embodiments of the present disclosure when configured accordingly. Thus, for example, when the processor is embodied as an ASIC, FPGA, or the like, or a combination thereof, the processor may be specially configured hardware for carrying out the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of instructions, the instructions may have a specific configuration to 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., encoder and/or decoder) configured to further configure the processor by instructions for performing the algorithms and/or operations described herein, thereby employing embodiments of the invention. A processor may include, among other things, a clock configured to support operation of the processor, an Arithmetic Logic Unit (ALU), and logic gates.

In embodiments including communication interface 206, the communication interface may be any component, such AS a device or circuitry embodied in hardware, or a combination of hardware and software, that is configured to receive and/or transmit data from/to a network and/or any other device or module in communication with apparatus 200 (such AS NF, NRF, base station, access point, SCP, UE 102, RAN 104, core network services, AS/AF 112, database or other storage device, etc., or a combination thereof). In this regard, the communication interface may include, for example, one or more antennas and supporting hardware and/or software for enabling communications with a wireless communication network. Additionally or alternatively, the communication interface may include circuitry to interact with one or more antennas to cause transmission of signals via the one or more antennas or to process reception of signals received via the one or more antennas. In some embodiments, the one or more antennas may include dipole antennas, monopole antennas, helical antennas, loop antennas, waveguides, feedhorns, parabolic reflectors, corner reflectors, dish antennas, microstrip patch arrays, convex planes, concave planes, convex, concave lenses, etc., or combinations thereof.

In some environments, the communication interface may alternatively or additionally support wired communication. As such, 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 a combination thereof. In some embodiments, the 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 for General Packet Radio Service (GPRS), gateway GPRS support node control plane functions (GGSN-C), trusted wireless access gateway control plane functions (TWAG-C), broadband network gateway control and user plane separation (BNG-CUPS), N4 interfaces, sxa interfaces, sxb interfaces, sxc interfaces, evolved Packet Core (EPC) serving gateway control plane functions (SGW-C), EPC packet data network gateway control plane functions (PGW-C), EPC traffic detection control plane functions (TDF-C), and the like, or combinations thereof.

As illustrated, the apparatus 200 may include a processor 202, the processor 202 being in communication with a memory 204 and configured to provide signals to a communication interface 206 and to receive signals from the communication interface 206. In some embodiments, communication interface 206 may include a transmitter and a receiver. In some embodiments, the processor 202 may be configured to control, at least in part, the functions of the apparatus 200. In some embodiments, the processor 202 may be configured to control the functions of the transmitter and receiver by affecting control signaling to the transmitter and receiver via the electrical leads. Likewise, the processor 202 may be configured to control other elements of the apparatus 200 by effecting control signaling via electrical leads connecting the processor 202 to the other elements such as the display or memory 204.

The apparatus 200 may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like. The signals transmitted and received by processor 202 may include signaling information in accordance with the air interface standard of the applicable cellular system, 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 Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, asymmetric Digital Subscriber Line (ADSL), data Over Cable Service Interface Specification (DOCSIS), and the like, or a combination thereof. Further, these signals may include voice data, user generated data, user requested data, and the like, or combinations thereof.

For example, the apparatus 200 and/or a cellular modem therein may be capable of operating in accordance with 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)), and the like, or combinations thereof. For example, the apparatus 200 may be capable of operating in accordance with 2G wireless communication protocol temporary standard (IS) 136 (IS-136), time Division Multiple Access (TDMA), GSM, IS-95, code Division Multiple Access (CDMA), the like, or a combination thereof. Further, for example, the apparatus 200 may be capable of operating in accordance with 2.5G wireless communication protocols GPRS, enhanced Data GSM Environment (EDGE), or the like, or a combination thereof. Further, for example, the apparatus 200 may be capable of operating in accordance with a 3G wireless communication protocol, such as UMTS, code division multiple access 2000 (CDMA 2000), wideband Code Division Multiple Access (WCDMA), time division synchronous code division multiple access (TD-SCDMA), and the like, or a combination thereof. The NA 200 may also be capable of operating in accordance with a 3.9G wireless communication protocol, such as Long Term Evolution (LTE), evolved universal terrestrial radio access network (E-UTRAN), or the like, or a combination thereof.

Further, for example, the apparatus 200 may be capable of operating in accordance with 4G wireless communication protocols (such as LTE-advanced), 5G, etc., and similar wireless communication protocols that may be subsequently developed. In some embodiments, apparatus 200 may be capable of operating in accordance with or within the framework of any suitable CUPS architecture, such as for gateway GGSN-C, TWAG-C, broadband Network Gateway (BNG), N4 interface, sxa interface, sxb interface, sxc interface, EPC SGW-C, EPC PGW-C, EPC TDF-C, and the like, or a combination thereof. Indeed, although described herein in connection with the operation of a 5G system, the apparatus and methods may be configured to operate in connection with many other types of systems, including those developed and implemented below.

Some embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware and application logic. For example, software, application logic, and/or hardware may reside on the memory 204, the processor 202, or electronic components. In some example embodiments, the application logic, software, or instruction sets are maintained on any one of a variety of conventional computer-readable media. In the context of this document, a "computer-readable medium" can be any non-transitory medium that can contain, store, communicate, propagate, or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuit, an example of which is depicted in fig. 4. A computer-readable medium may include a non-transitory computer-readable storage medium, which may 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.

Fig. 5 illustrates an example communication network 500 that includes two example network slices. The UE 102 utilizes at least the communication interface 206 to establish one or more network connections by causing transmission and reception of communication signals between the UE 102 and the public network function 503, the first network slice 501, and/or the second network slice 502 via at least the communication interface 206. It should be appreciated that in some embodiments, the communication interface 206 may connect the UE 102 directly to the first network slice 501 and/or the second network slice 502, bypassing the public network function 503. Further, it should be appreciated that the communication interface 206 may indirectly connect the UE 102 to the first network slice 501 and/or the second network slice 502 by first establishing a connection through the public network function 503.

In some embodiments, the UE 102 may connect to multiple public and/or private networks, and/or multiple public and/or private network slices, through the communication interface 206. In some embodiments, the communication interface 206 may be communicatively coupled to one or more of a RAN (e.g., RAN 104), a cell, a gNB, a ng-eNB, a NodeB, etc., or a combination thereof, such that communication signals may be transmitted and received through the communication interface 206. The RAN node (e.g., the gNB, NG-eNB, nodeB) may be configured to exchange network slice support information (e.g., S-nsai, etc.) for one or more TAs over at least one Xn interface during an Xn setup procedure and/or a next generation radio access network (NG-RAN) node configuration procedure (e.g., an update procedure).

In the illustrated embodiment, the first network slice 501 includes a plurality of network functions including at least a network repository function 1 (NRF 1) 124a, a policy charging function 1 (PCF 1) 114a, a user plane function 1 (UPF 1) 106a, and a session management function 1 (SMF 1) 110a. Each network function of the first network slice 501 is independent of the network functions of the public network function 503 and the second network slice 502. Further, the first network slice 501 is configured to connect the UE 102 to the data network 1 (DN 1) 116a. The second network slice 502 includes a plurality of network functions including at least a network repository function 2 (NRF 2) 124b, a policy and charging function 2 (PCF 2) 114b, a user plane function 2 (UPF 2) 106b, and a session management function 2 (SMF 2) 110b. Each network function of the second network slice 502 is independent of the common network function 503 and the network function associated with the first network slice 501. Further, the second network slice 502 is configured to connect the UE 102 to the data network 2 (DN 2) 116b.

The first network slice 501 and the second network slice 502 may be configured at least in part according to one or more configurations of network slice X and/or network slice Y as described herein at least with respect to fig. 7-10. For example, the first network slice 501 may be configured according to network slices X, S-NSSAI X (e.g., S-NSSAI X810 described below with respect to at least FIG. 8), and any associated regions (e.g., XSA 706 described below with respect to at least FIG. 7). The second network slice 502 may be configured according to network slice Y, S-NSSAI Y (e.g., S-NSSAI Y808 described below with respect to at least FIG. 8) and any associated regions (e.g., YSA 704 described below with respect to at least FIG. 7).

In some embodiments, a particular network slice may be served via one or more frequency bands, one or more cells, and/or one or more base stations dedicated to the particular network slice in a respective region (e.g., RA, TA, SA, etc.). When additional network slices are added to the respective areas, one or more additional frequency bands, cells, base stations, and/or TACs/TAIs may be assigned to the respective areas covered by the additionally added network slices. One or more TAC configurations of the first region, and/or one or more associated TA configurations, may be mapped to a second region in which additional services (e.g., eMBB services) not provided in the first region are provided. The first region may be a subset of the second region. The second region may be a subset of the first region.

In some embodiments, the example communication network 500 of fig. 5 includes one or more of a Public Land Mobile Network (PLMN), an independent non-public network (SNPN), a public network integrated NPN (PNI-NPN), and the like. For example, the first network slice 501 may be configured with the public network function 502 as part of a PLMN such that the UE 102 may access the first network slice 501 without undergoing a (at least some) login (onboard) procedure or authentication of credentials. Further, the second network slice 502 may be configured as a PNI-NPN operating under support of the PLMN, which includes the first network slice 501 and the public network function 502, but also requires that the UE 102 be of a specific tenant type in order to be eligible for use of the second network slice 502. Furthermore, to access the second network slice 502, the UE 102 will have to undergo a login procedure and/or authentication of credentials that incorporates the authentication of credentials associated with the UE 102 and one or more Service Level Agreement (SLA) and/or subscribed credentials.

In instances where the UE 102 has been subscribed to the second network slice 502, a subsequent credential authentication process may be initiated by the UE 102 or the second network slice 502 without requiring additional login or registration processes. It should also be appreciated that according to some embodiments, the first network slice 501 and/or the second network slice 502 may be configured as separate networks from the example communication network 500, rather than as network slices, such as an SNPN that supports authentication and/or login procedures. Further, in some embodiments, a plurality of additional network slices (e.g., third network slice, fourth network slice, etc.) may be included into the example communication network 500, wherein each network slice is configured with or without authentication feature requirements, with or without login features for unregistered user devices, and/or a plurality of network functions (e.g., NRF, UPF, PCF, SMF, AS/AF, AUSF, DN, etc.).

The respective network slices may be configured to provide one or more respective services to the UE 102 or the like that are not provided by one or more other network slices, as described herein. Corresponding network slices may be served by one or more cells, base stations, etc. of RAN 104, as shown in fig. 1-3 and described above. One or more corresponding network slices, cells, base stations, and/or other network entities and/or infrastructure components as described above may be associated with one or more corresponding RA, cellular coverage area, TA, service Area (SA), etc., as described herein. One or more respective network slices (or functions thereof), cells, base stations, and/or other network entities and/or infrastructure components may be disabled, locked, restricted, or otherwise made unavailable to one or more UEs within a respective RA, cellular coverage area, TA, SA, etc., as described herein. One or more respective network slices (or functions thereof), cells, base stations, and/or other network entities and/or infrastructure components may be allowed, unlocked, accessible, or otherwise made available to one or more UEs within a respective RA, cellular coverage area, TA, SA, etc., as described herein.

Fig. 6 is a block diagram illustrating an example single network slice selection assistance information (S-NSSAI) format 600 in accordance with some embodiments. As illustrated in fig. 6, the S-nsai 602 is configured according to the S-nsai format 600. A network slice (e.g., the first network slice 501 or the second network slice 502 as described above with respect to fig. 5) may be uniquely identified via a corresponding S-nsai, such as S-nsai 602. The UE may connect to and be served by multiple S-nsais simultaneously. A cell may support multiple S-nsais and a TA may support multiple network slices via one or more serving cells. The S-NSSAI 602 may include one or more of a Slice Service Type (SST) 604 portion or a Slice Discriminator (SD) 606 portion.

SST 604 may include approximately 8 bits of data configured to indicate at least a type of service associated with a respective network slice. The SST 606 portion may have normalized and/or non-normalized values, such as values ranging between 0 and 127 may belong to a normalized SST range. For example, a value of 1 in the SST 606 section may indicate that the associated network slice of S-NSSAI 602 is suitable for processing 5G eMBBs. Further, for example, a value of 2 in the SST 606 portion may indicate that the associated network slice of S-NSSAI 602 is suitable for processing URLLC. The respective values in the SST 606 portion may indicate that the associated network slice of the S-NSSAI 602 is or is not suitable for handling particular services, functions, etc. associated with, for example, the respective network, RA, TA, etc.

SD 606 may include approximately 24 bits of data configured to indicate a respective network slice from among a plurality of network slices that is associated with a particular region (e.g., TA, RA, etc.). The SD 606 portion may be defined in terms of one or more of MNOs, PLMNs (e.g., home PLMN (HPLM), etc.), or other administrative entities (e.g., standards organization, government, etc.) within a particular interval or region. The S-nsai 602 may include one or more additional portions (not shown) including one or more additional bits (not shown) to facilitate identifying RA, TA, network slice, service, cell, beam, RAN, and/or any other network entity described herein to the UE and/or another network entity associated therewith. One or more S-nsais (e.g., S-nsai Y808, S-nsai X810, etc.) as described below may be configured at least in part as described above with respect to S-nsai format 600 and/or S-nsai 602.

Fig. 7 is a block diagram illustrating an example deployment area 700 associated with a communication network (e.g., communication networks 100 and/or 500 as described above) according to some example embodiments. Deployment area 700 includes RA 702, S-NSSAI Y 'S service area (YSA) 704, and S-NSSAI X' S service area (XSA) 704. The RA 702 may be configured to support multiple TAs of one or more network slices (e.g., the first network slice 501 or the second network slice 502 as described above with respect to fig. 5). Corresponding ones of the one or more network slices may be identified by a corresponding S-nsai (e.g., S-nsai 602 as described above with respect to fig. 6). For example, network slice Y (not shown) may be identified by S-nsai Y (not shown) and a UE (e.g., UE 102) may access services of network slice Y while located within YSA 704. Another network slice, network slice X (not shown) may be identified by S-nsai X (not shown), and a UE (e.g., UE 102) may access the services of network slice X while located within XSA 706. The RA 702 may include one or more additional service areas, tracking areas, etc., associated with one or more additional network slices and additional S-NSSAIs, as described herein.

The SA (e.g., YSA 704, XSA 706, etc.) may be a proper subset of RA 702. An SA (e.g., YSA 704, XSA 706, etc.) may be separate from or overlap with another SA. For example, YSA 704 may at least partially overlap XSA 706. The SA (e.g., YSA 704, XSA 706, etc.) may be a proper subset of another SA. For example, XSA 706 may be configured within YSA 704. The RA 702 may be identified by a tracking area identity (or Tracking Area Identifier) (TAI) list that indicates one or more TAIs and/or Tracking Area Codes (TACs). When a UE is detected within the RA 702, at least the UE and/or a core network associated with the RA 702 (e.g., CN 101) may cause one or more network entities to perform RA update procedures and/or TA update procedures. When detecting that the UE has moved outside the RA 702, at least the UE may cause one or more network entities to perform RA update procedures and/or TA update procedures for another RA. Based on the S-nsai sent to the UE, the UE may determine that it may access one or more network slices associated with the SA within the RA. For example, the UE may determine that it may access a first network slice associated with a first SA, and the UE may determine that it may not access a second network slice associated with a second SA.

According to example embodiments of the present disclosure, when a UE is not located in a service area of a respective S-nsai, the UE may be prevented from accessing or otherwise using the respective S-nsai of the respective network slice. For example, when the UE is not located within YSA 704, the UE may be prevented from using network slice Y. The UE may be prevented from using network slice Y by using a barring factor associated with the operator specific access class. The inhibit factor may be associated with S-nsai and may be set to 0 within RA outside the corresponding SA. For example, in the portion of RA 702 not covered by YSA 704, the disable factor for S-nsai Y may be set to 0, thereby preventing the UE from receiving S-nsai Y at least when the UE is outside of YSA 704, and also preventing the UE from connecting to network slice Y within RA 702.

When the UE is outside the supported SA, the UE may be prevented from receiving the corresponding S-nsai. The AMF (e.g., AMF 108) may be configured to block the S-nsai from being transmitted to or received by the UE based at least on a location or cell associated with the UE. When the UE moves out of YSA 704, the AMF may send updated allowed nsais to the UE, excluding S-nsais Y. When the UE moves into YSA 704, the AMF may send updated allowed nsais, including S-nsai Y. The SA may be associated with a respective cell or base station (e.g., gNB) of a RAN (e.g., RAN 104), and the AMF may determine which S-nsai to include in the nsai based on the respective cell or base station.

Nsai mapping on Next Generation Application Protocols (NGAPs) associated with base stations (e.g., gnbs) and/or cell identifiers may be used as a trigger condition for the AMF to send updated allowed nsais (e.g., including or excluding specific S-nsais). If the SA cannot be described as a set of RAN nodes (e.g., the gnbs), the NGAP may be adjusted during the NG setup procedure and the NG configuration update procedure so that the RAN nodes may cause the respective S-nsais supported for each respective cell transmission. For example, a first cell of the gNB may belong to YSA 704 and a second cell of the gNB may belong to XSA 706, which may cause transmission of a message reporting the association of the first cell with the second cell to the AMF or another network entity. The AMF may configure and/or send the updated allowed nsai based on the cell associated with the UE. The RAN may be configured to cause a network slice area notification (such as a RAN notification for rrc_inactive+ngap) to be transmitted from a node of the RAN to the AMF. For example, the UE may be communicatively connected to the gNB via a first cell supporting YSA 704, and the UE may move to a second cell of the gNB supporting XSA 706. Based on this change from the first cell to the second cell of the gNB, the gNB may cause a notification message (e.g., one or more RRC messages) to be transmitted to at least the AMF, thereby indicating to the at least the AMF that the network slice support changes.

In response to the AMF determining that the network slice support has changed for the UE (e.g., based on nsai mapping on NGAP or RAN notification messages as described above), the mobile traffic communication procedure may be adjusted for the UE. For example, when the UE is located in a particular SA (e.g., YSA 704, XSA 706), the UE may be allowed (e.g., by a gNB, AMF, etc.) to complete Mobile Originated (MO) traffic associated with a particular network slice (e.g., network slice Y, X) or associated S-nsai. However, when the UE is outside a particular SA, it will not be able to initiate traffic for a particular network slice and/or associated S-nsai because when the UE transitions to connected mode and attempts to re-activate any PDU session associated with a particular S-nsai, the re-activation will fail outside the particular SA. For example, while inside YSA 704, the UE may be configured to complete MO traffic associated with network slice Y and/or S-nsai Y; outside of YSA 704, the UE will not be able to complete MO traffic or re-activate PDU sessions for S-nsai Y.

Further, for Mobile Termination (MT) traffic, when the UE is outside of a particular SA (e.g., YSA 704, XSA 706), the AMF may be configured to page the UE for downlink data associated with a PDU session associated with the S-nsai of the particular SA. For RAN nodes (e.g., gnbs) with uniform cell support, the AMF may identify a particular SA via the NGAP procedure. For RAN nodes (e.g., gnbs) with non-uniform cell support (e.g., different cells of the same gNB support different SAs), the AMF may identify support for a particular SA via network slice support information received/retrieved from the RAN node for the associated cell. For example, a gNB having a first cell supporting YSA 704 and a second cell supporting XSA 706 will cause transmission of a network slice support information message to at least the AMF, and based at least on the network slice support information message, the AMF will not page the UE for downlink data associated with a PDU session associated with one or more of YSA 704 or XSA 706.

Based on, for example, a location of the UE determined from at least communications between the UE and the particular cell, the AMF may not page the UE for downlink data. UE mobility may be controlled by the network (e.g., PLMN, etc.) or its entity (e.g., AMF, SMF, etc.). The admission NSSAI (including admission S-NSSAI for a particular region (e.g., RA, SA, TA, etc.) may be modified, updated, or otherwise altered (e.g., by the network or its entity) to prevent and/or admit access to a particular network slice after path switching associated with the UE and determining the location of the UE (e.g., based on GPS, gNB/cell communications or identification, or other methods for location determination described herein). In some embodiments, access by a UE to a particular network slice may be allowed and/or restricted by deploying a SNPN, PNI-NPN, and/or similar private networks within a particular SA. For example, YSA 704 may be served by PNI-NPN configured to allow only services to UEs: a predefined UE (e.g., predefined through a list of allowed UEs that have access to the PNI-NPN), and/or a preconfigured UE (e.g., preconfigured with required credential(s) prior to entering YSA 704), or a UE that is allowed/configured to perform the necessary logins and/or configurations to receive services from the PNI-NPN while in YSA 704.

Fig. 8 is a block diagram illustrating an example deployment area 800 associated with a communication network (e.g., communication networks 100 and/or 500 as described above) according to some example embodiments. Deployment area 800 includes AMF 108, base station 802a, base station 802b, base station 802c, base station 802d, cell 804a, cell 804b, cell 804c, cell 804d, TA/RA 804, and TA/RA 806. The plurality of base stations (e.g., base stations 802a, 802b, 802c, 802 d) may be associated with one or more RANs (e.g., RAN 104) and may include one or more RAN nodes (e.g., gnbs, etc.). One or more base stations may be configured to send and/or receive messages with one or more other base stations via one or more interfaces (e.g., an Xn interface, etc.). For example, base station 802a may be communicatively connected with base station 802b via at least an Xn interface, and base station 802a may cause, for example, transmission of network slice support information to base station 802 b.

AMF 108 may cause transmission of an nsai to a respective base station, the nsai including one or more S-nsais associated with a particular network slice (e.g., network slice X, network slice Y, or other network slice), such as described above with respect to fig. 7. One or more base stations (e.g., base station 802a, etc.) may provide cell or UE location/connection information to AMF 108, such as described above with respect to fig. 7. The deployment area 800 may support one or more network slices (e.g., network slice X) uniformly throughout/across a particular TA/RA (e.g., TA/RA 806). Deployment area 800 may support one or more network slices (e.g., network slice Y) non-uniformly throughout a particular TA/RA (e.g., TA/RA 804). The respective cells (e.g., cell 804b, etc.) may provide services to respective SAs (not shown) associated with the respective TAs/RAs (e.g., TA/RA 804, etc.). For example, base station 802a may provide services to XSA 706 via at least cell 804a, as shown in fig. 7 and described above.

As shown, cell 804a and cell 804b cover respective SA (not shown) portions of TA/RA 804, and cell 806a and cell 806b cover respective SA (not shown) portions of TA/RA 806. Network slice X (not shown)) is served by base stations 802a, 802b, 802c, and 802d of their respective cells. The S-nsai X810 may be transmitted by the base stations 802a, 802b, 802c, and 802d to UEs within their respective cells. Network slice Y (not shown) is served by base station 802b within cell 804 b. S-nsai Y808 may be transmitted to UEs within cell 804b via at least base station 802b, and S-nsai Y808 is prevented from being transmitted via base stations 802a, 802c, and 802 d. The AMF 108 may determine (such as through an NGAP procedure) which S-nsai may be transmitted to one or more UEs (e.g., authorized to use the S-nsai) at least via a respective base station (e.g., a gNB, etc.) and/or a respective cell.

With respect to fig. 8, when one or more UEs authorized to access and use services such as network slice Y are located outside of the SA of network slice Y (e.g., YSA 704 as shown in fig. 7), or in other words outside of the SA covered by cell 804b of base station 802b, the UEs may be prevented from receiving and/or requesting services from network slice Y. The UE may be prevented from receiving and/or requesting service from, for example, network slice Y via one or more base stations (e.g., gnbs) configured to cause transmission of a Unified Access Control (UAC) Operator Defined Access Class (ODAC). One or more definitions associated with the at least one ODAC may be sent to the UE during a registration procedure (e.g., RRC registration, etc.). The UE may be prevented from receiving and/or requesting services from the network slice at least by the AMF. The AMF provides (e.g., causes transmission of) a permitted nsai and/or a permitted S-nsai to the UE via the base station, which indicates to the UE the non-uniform network slice support permitted in the respective TA/RA. The allowed NSSAI and/or the allowed S-NSSAI may be sent to the UE, but the UE may require additional authorization credentials associated with the subscription before the UE can receive service from the network slice.

Service enabler methods such as those described above (e.g., UAC ODAC, allowed nsai, subscription authorization, and/or other methods for providing non-uniform network slice services within TA/RA) may be used to indicate to the authorizing UE that it is allowed nsai associated with network slice X and network slice Y, e.g., in TA/RA 804. Furthermore, when the UE requests access and/or service from network slice X anywhere in TA/RA 804, the UE will be authorized for access, whether at least via base station 802a or 802b. However, when the UE is in a SA associated with base station 802b and/or cell 804b, the UE may only be authorized for access and/or service from network slice Y, while when the UE is within a SA associated with base station 802a and/or cell 804a, access and/or service from network slice Y will be barred.

Disabling access and/or services of network slice Y may be caused by configuring at least base station 802a (e.g., a gNB) to cause transmission (e.g., via beam and/or cell broadcast, transmission, etc.) of a unique ODAC to a UE within an associated SA. Furthermore, disabling access and/or services for network slice Y may provide the ODAC definition to the UE (e.g., during a registration process, etc.) at least by configuring AMF 108, which maps network slice Y to a particular Access Class (AC). When the UE causes a service request to be initiated for network slice Y via base station 802a (e.g., via one or more procedures for PDU session establishment and/or modification), the UE may perform at least a check for access control/barring in the event that network slice Y is mapped to a particular AC. The UE may at least determine that network slice Y associated with a particular AC (e.g., an AC that base station 802a may broadcast/transmit) is barred and, thus, access to network slice Y (e.g., at least via base station 802 a) is barred (e.g., locked, blocked, restricted, protected, etc.).

If the UE moves into the SA of base station 802b, access to network slice Y may be granted based on determining that base station 802b does not broadcast/transmit access control/barring information associated with network slice Y. 802b may broadcast/transmit information (e.g., nsai, etc.) reflecting that the base station 802b or its cell (e.g., cell 804 b) does support communication between at least the UE and the network slice Y. If the UE moves into TA/RA 806, AMF 108 may cause transmission of an allowed value of nsai=x during the registration procedure (e.g., based at least on determining that network slice Y is not supported in TA/RA 806). In response, the UE may not request establishment of one or more PDU sessions for network slice Y based on determining that network slice Y is not indicated/reflected via the allowed nsais received by the UE. The UE may request (e.g., cause transmission of a request message to AMF 108 via RAN 104) to establish one or more PDU sessions for network slice X based on determining that network slice X is indicated/reflected via the allowed nsai received from AMF 108.

The UE may have an established PDU session associated with a network slice Y within the SA, the network slice Y being associated with the base station 802b or its cell, the UE may move to the SA associated with the base station 802a, and the movement may be detected as a trigger condition for one or more handover events based on the associated mobility pattern. For example, based on the connected mode mobility state, the base station 802a may reject one or more PDU session requests associated with network slice Y received from the UE. Further, one or more PDU sessions associated with network slice Y may be rejected via base station 802a based on determining that network slice Y is not supported, and based on the idle mode mobility state, the UE may be barred from gaining access based on ODAC, such as described above. One or more services or features associated with network slice Y may be mapped to network slice X in a limited area (e.g., XSA 706, overlapping SA between XSA 706 and YSA 704, and/or a portion of one or more TA/RA).

The UE may have an established PDU session within the SA for network slice Y associated with base station 802b or its cell, the UE may exit TA/RA 804 and move into TA/RA 806, depending on the mobility mode, as will occur. In the connected mode mobility state, since network slice Y is not supported by either base station 802c or base station 802d in TA/RA 806, base station 802c and base station 802d of TA/RA 806 will cause rejection of the PDU session associated with network slice Y. The UE may obtain additional allowed nsais including S-nsais for network slice X because network slice X is supported within TA/RA 806. In the idle mode mobility state, the UE may not request to establish or re-establish a PDU session for network slice Y, as network slice Y is not included as part of the additional admission nsais of TA/RA 806.

The ODAC definition (S), which may be configured at least by AMF 108, are configured to facilitate enablement and/or association of one or more of S-nsai, data Network Name (DNN), or application identifier (S) with corresponding AC values, which may be configured to be broadcast from a particular base station (e.g., RAN node, gNB, etc.). The ODAC definition message may include a plurality of definitions, and at least one associated priority (e.g., prioritization, ranking, proportion, etc.) value for the respective definition, which informs (e.g., indicates, identifies, etc.) in what order the UE may evaluate the definition.

For example, a UE within an SA associated with base station 802a may attempt to send a service request message (e.g., to base station 802a and/or the network) to establish a PDU session for both network slice X and network slice Y, the prioritization order may indicate that network slice X definition(s) are evaluated prior to network slice Y definition(s). The prioritization order may be configured to prevent prohibition of service requests associated with at least one prohibited network slice and at least one permitted network slice. For example, to prevent access attempts associated with network slice X and network slice Y from being barred based on one or more network configurations for disabling network slice Y in the SA associated with base station 802a, the prioritization/prioritization order indicates: since network slice Y is disabled at least in one or more SAs of TA/RA 804, network slice X definition(s) are evaluated prior to network slice Y definition. Network slice X may be evaluated first and then access attempts may be allowed because the access attempts may be mapped to AC for network slice X, but not AC for network slice Y.

The prioritization order may be configured by the AMF 108 based on predefined SA limits for one or more network slices (e.g., network slice Y). AMF 108 may support ODAC defined configuration. The AMF 108 may cause transmission of an allowed nsai, which may be configured with a plurality of S-nsais for a plurality of network slices associated with a TA/RA (e.g., TA/RA 804) associated with non-uniform network slice support. One or more ODAC definitions may be sent to the UE (e.g., from the AMF via the RAN node/base station) as part of a registration procedure and/or a UE configuration update procedure.

A base station (e.g., a gNB, or other RAN node described herein) may be configured to support transmission and reception of ODAC and ODAC definitions relative to one or more other network entities (e.g., UE 102, AMF 108, CN 101, etc.). Each respective base station of the plurality of base stations covering one or more SAs of the TA/RA may not need to be configured with the same network slice configuration. Two or more base stations may cover at least a portion of the same SA. A base station may be configured to cover multiple SAs via one or more cells, and/or one or more beams.

The AMF may configure and/or cause a list of transmission allowed nsais (e.g., updated nsai list) based on one or more trigger criteria, e.g., allow the nsais to include S-nsai Y (or another corresponding S-nsai). For example, the AMF may detect/determine that the UE is handed over from the gNB in XSA 706 to the gNB in YSA 704, and the trigger criteria may cause the AMF to cause transmission of a list of allowed nsais (e.g., including S-nsais Y) to the UE in YSA 704. The AMF may detect/determine that a UE having an allowed nsai that does not include S-nsai Y has performed a service request procedure in, for example, YSA 704 (or another corresponding SA), and the trigger criteria may cause the AMF to cause a list of allowed nsais (e.g., including S-nsai Y) to be transmitted to the UE of YSA 704.

The AMF may configure and/or cause a list of transmission-allowed nsais (e.g., an updated list of nsais) based on one or more trigger criteria, e.g., the list does not include (e.g., prevents) S-nsais Y (or another corresponding S-nsais). For example, the AMF may detect/determine that the UE is handed off from the gNB in YSA 704 to the gNB in XSA 706, and the trigger criteria may cause the AMF to cause transmission of a list of allowed nsais (e.g., block S-nsais Y) to the UE in XSA 706. The AMF may detect/determine that a UE with an allowed nsai (which includes S-nsai Y) has performed a service request procedure for network slice Y in XSA 706, for example, and the trigger criteria may cause the AMF to cause a list of allowed nsais to be transmitted to the UE of XSA 706 (e.g., block/remove S-nsai Y). The AMF may block the S-nsais in the list of nsais based on determining that the location of the UE (e.g., cell identifier, RAN node identifier, GPS location, etc.) is outside of the corresponding SA of the corresponding S-nsais.

A private network associated with the SA may be deployed. For example, one or more RAN nodes, cells, and/or AMFs serving YSA 704, network slices Y deployed as SNPNs may be shared between PLMNs and SNPNs within YSA 704. The AMF may be shared between the PLMN and the SNPN, and one or more other Network Functions (NFs) may not be shared between the PLMN and the SNPN. One or more other NFs associated with the SNPN may not be shared with the PLMN. For example, referring to fig. 5 for purposes of illustration, a public network function 503 may include AMF 108 and represent shared resources between PLMNs and SNPNs, and a first network slice 501 may represent a PLMN, while a second network slice 502 may represent a SNPN, each with their respective non-shared resources (e.g., NF, etc.). The UE starts and stops operating in the SNPN access mode when the UE enters and exits the SA (e.g., YSA 704) associated with the SNPN (e.g., configured with the services associated with network slice Y described above). While in the SA (e.g., YSA 704), the UE may still be registered with the PLMN and receive PLMN services through the non-3 GPP interworking function (N3 IWF) of the PLMN (e.g., facilitate access to PLMN services via the SNPN) using Internet Protocol (IP) connectivity available via the SNPN.

The private network described above may be deployed as a PNI-NPN associated with the SA. One or more cells in the SA (e.g., YSA 704) may be shared between the PLMN and PNI-NPN. For example, the PNI-NPN may be accessed by one or more of a non-CAG UE or a CAG UE. The UE may be configured with an allowed CAG list that includes CAG-IDs (e.g., CAG-ID nn) that are broadcast/transmitted via one or more cells in the SA. A UE accessing a cell (as a CAG cell) may be provided with a particular S-nsai (e.g., S-nsai X810, etc.) that is allowed for SA (e.g., XSA 706, etc.). The UE may use the PDU session associated with the particular S-nsai via the CAG cell based on the allowed nsai for the SA. UEs not configured with CAG cells will not be allowed to use PNI-NPN services.

In some embodiments, the RAN node (e.g., see base station 802a described above with respect to fig. 8, etc.) or a cell thereof may be configured to associate one or more TACs with a respective network (e.g., PLMN, SNPN, etc.). The RAN node or cell may be shared by multiple networks. A cell may broadcast (e.g., cause transmission via a beam to a UE or another network entity) one or more TACs associated with the respective network. The RAN node or cell supporting the respective network(s) may be configured to provide one or more TACs to one or more UEs via Information Elements (IEs) of a System Information Block (SIB) during SIB broadcast. The first TAC may be configured into a first IE of the SIB, which may be regarded as the master TAC. Further, one or more second TACs may be configured into one or more second IEs of the SIB, which may be considered as secondary TACs. The one or more second TACs may be prioritized within the SIB (e.g., by a network entity generating the SIB, such as an AMF, SMF, or other network function described above), which may be reflected in their coding order associated with the SIB and/or the one or more second IEs. For example, the UE may determine that a second TAC of the one or more second TACs is preferred/prioritized over a third TAC based on determining that the second TAC is read before the third TAC (e.g., by a network operator). The secondary TAC(s) may be a proper subset of the primary TAC region.

The UE may select a TAC from a plurality of TACs including a first TAC/primary TAC and one or more second TAC/secondary TACs based on one or more selection criteria. The UE may select the TAC associated with the first IE of the SIB based on the UE's ability to read one or more second IEs of the SIB. For example, the UE may not be able to read one or more second IEs of the SIB, and the UE may select TACs of the first IEs of the SIB. The addition of the secondary TAC(s) in the SIB may not require locking and/or unlocking of the respective cell, so that UEs that cannot read one or more secondary TACs or the second IE may remain in the respective cell. The UE may select the TAC based on a TAI list, which may include one or more of a forbidden TAI or an allowed TAI. The TAI list may be a white list, a black list, or a combination thereof, indicating to the UE which TACs and/or network slices the UE may or may not use within a particular area. For example, the UE may receive a plurality of TACs and a list of forbidden TAIs from the cell, then the UE may determine that only one TAC of the plurality of TACs is not associated with the list of forbidden TAIs, and then the UE may select the one TAC.

The UE may select TAC from among the plurality of TACs based on priority reflected in the coding order of TACs within the associated SIB. For example, the primary TAC may be selected from one or more secondary TACs based on a determination by the UE that the primary TAC was read from the SIB before the one or more secondary TACs. One or more secondary TACs may be listed according to descending priority. For example, the first secondary TAC may be selected as compared to the fourth secondary TAC, since the first secondary TAC is read by the UE before the fourth secondary TAC. The UE may select a first TAC (e.g., a primary TAC or a secondary TAC) read from the SIB, which is not indicated to the UE as being disabled by the TAI list (e.g., a forbidden TAI list). For example, the fourth secondary TAC read from the SIB by the UE may be selected by the UE because the primary TAC and the first, second, and third secondary TACs are all determined to be disabled. The non-forbidden auxiliary TAC with the highest priority may be selected by the UE. The UE may determine which TAC is the primary TAC and which TAC is the secondary TAC based on the coding position (e.g., first IE, second IE, etc.) and/or order (e.g., first TAC of the first IE, fifth TAC of the second IE, etc.) within the SIB. If the UE receives all TACs of the plurality of TACs from the cell as forbidden TACs, the UE may consider the current serving cell as an unsuitable cell and the UE may initiate a procedure of communicating with a different cell.

Each respective TAC of the plurality of TACs may be configured (e.g., by a network, AMF, etc.) to be associated with (e.g., mapped with) one or more respective S-nsais, or one or more respective sets of network slices. For example, a UE within YSA 704 may receive a TAC from a serving cell (e.g., cell 804b as described above with respect to fig. 8) that is mapped to S-nsai Y (e.g., S-nsai 808 as described above with respect to fig. 7, and/or as described above with respect to fig. 8). The UE may select TACs mapped to S-nsai Y (if the UE wants to utilize S-nsai Y) and cause an indication of the selected TACs to be transmitted to the corresponding RAN node to establish a connection to the network slice Y and/or receive services from the network slice Y. The plurality of TACs may be configured with TACs mapped to S-nsai Y, and/or TACs mapped to S-nsai X (e.g., as described above with respect to fig. 7, and/or S-nsai 810 as described above with reference to fig. 8). The plurality of TACs may be configured with one or more TACs mapped to one or more corresponding S-NSSAIs. For PLMNs, the S-nsai or network slice group (S) supported by each TAC may be configured in the UE or broadcast by the cell.

Fig. 9A is a block diagram illustrating an example deployment area 900 associated with a communication network (e.g., communication networks 100 and/or 500 as described above) according to some example embodiments. Deployment area 900 includes cell 901, cell 902, cell 903, cell 904, cell 905, cell 911, and cell 912. Each respective cell is configured to serve one or more network slices (e.g., cell 904 serves network slice a and network slice D). Each respective cell is configured to serve one or more TAs (e.g., cell 904 serves TA 4). The RAN node of RAN 104 may be configured with one or more cells (e.g., a first gNB may be configured with cell 911 and cell 912, and a second gNB may be configured with cell 903 and cell 905). Located within deployment area 900 are UE1 102a, UE2 102b, and UE3 102c. UE1 102a, UE2 102b, and UE3 102c may be configured according to one or more of the configurations described above with respect to UE 102, and at least with respect to fig. 1-4. UE1 102a is shown moving from location 914 to location 916 along an example path within at least the SA associated with cell 902. UE2 102b is located at a location 918 within at least the SA associated with cell 904. UE3 102c is located at a location 920 within the SA associated with at least one or more of cell 903 and cell 904.

A RAN node (e.g., a gNB) within the deployment area 900 that serves a plurality of cells (e.g., cells 901, 902, 903, 904, 905, 911, 912) may be configured to: one or more additional TACs are broadcast upon determining that one or more additional network slices need to be supported by one or more of the plurality of cells. As described above, one or more additional TACs may be configured as secondary TACs within the second IE of the SIB. Each of the respective one or more additional TACs may be associated with one or more S-nsais supported within the tracking area and/or registration area. The UE that cannot read the secondary TAC may observe the area from the perspective of the primary TAC.

In some embodiments, a RAN node (which serves a cell supporting multiple TACs of a network) may indicate the multiple TACs to different RAN nodes and additionally indicate whether the respective TACs of the multiple TACs are primary or secondary TACs. In this regard, as shown in method 1800 of fig. 18, at operation 1802, the apparatus (e.g., when embodied by a RAN node) includes means, such as processor 202, memory 204, communication interface 206, etc., for causing transmission of a message including a Tracking Area Identifier (TAI) list from a first node to a second node, wherein the TAI list includes a plurality of TAIs, and wherein a respective TAI of the plurality of TAIs is indicated as a primary TAI or a secondary TAI. In some embodiments, at operation 1804, the apparatus further comprises means, such as the processor 202, the memory 204, the communication interface 206, etc., for receiving a response from the second node based at least on the message comprising the TAI list.

For example, in some embodiments, as shown in fig. 14A and 14B, the first RAN node 1401 may indicate a plurality of TACs, as well as indications of primary and secondary TACs, via an Xn interface as part of an Xn setup request or configuration update to the second RAN node 1402. As shown, the Xn setup request or configuration update may cause a response to be generated by the second RAN node, such as an Xn setup response or configuration update acknowledgement. As another example, in some embodiments, as shown in fig. 15A and 15B, the first RAN node 1501 may indicate the plurality of TACs, and indications of the primary TAC and the secondary TAC, via the F1 interface as part of an F1 setup request or configuration update to the second RAN node 1502. As shown, the F1 setup request or configuration update may cause a response to be generated by the next generation node B central unit (gNB-CU), such as an F1 setup response or configuration update acknowledgement.

In some embodiments, the information about the TA may be in the form of a TAI. In some embodiments, the information about the TA may include semantics such that the primary TAC, or one or more secondary TACs, may represent a wide area slice or a limited area slice, such as a limited or limited service area slice. The limited area slice may be a dynamic slice, which may be deployed over a period of time. That is, the dynamic slice may be a temporary slice. In some embodiments, the RAN node may include a Centralized Unit (CU) (such as a gNB-CU), or a Distributed Unit (DU) (such as a gNB-DU), e.g., as shown in fig. 15A; or NG-RAN node (e.g., as shown in fig. 14A), such as a base station or a portion of a base station (e.g., a Network Function (NF) of a base station). In some embodiments, as shown in fig. 16A-16B, and 17A-17B, in the absence of an Xn interface or the like, information about multiple TACs provided by RAN nodes 1601, 1701 may be relayed via core network nodes (such as via AMFs 1602, 1702). The relaying of information may take the form of a configuration transfer procedure. In some embodiments, the information transfer may take the form of: an NG setup message and corresponding NG setup response via the NG interface (e.g., as shown in fig. 16A), a RAN configuration update and corresponding RAN configuration update acknowledgement (e.g., as shown in fig. 16B), an initial UE message (e.g., as shown in fig. 17A), or an NG setup request and corresponding NG setup response (e.g., as shown in fig. 17B).

Fig. 9B is a block diagram illustrating a deployment area 900 observed by one or more UEs that cannot read the secondary TAC. An inactive UE (i.e., a UE that cannot read the secondary TAC) may only view the deployment area 900 from the perspective of the primary TAC (e.g., all cells may appear to belong to a single TA). For example, an inactive UE may determine that multiple cells (e.g., cells 901, 902, 903, 904, 905, 911, 912) are all associated with a single TA, such as TA5 as shown in fig. 9B. A UE that cannot read the secondary TAC may not distinguish between TAs, e.g., TA1 of cell 911 and cell 912 and TA2 of cells 901 and 902 may be determined by the UE as all parts of TA5. Although a UE that cannot read the secondary TAC may not be able to distinguish between TAs, the network (e.g., AMF 108, RAN 104, etc.) and/or any UE that is capable of reading the secondary TAC may observe (e.g., detect, determine, etc.) that one or more of TA1, TA2, TA3, and TA4 are associated with their respective ones of the plurality of cells.

The enabled UE (i.e., the UE capable of reading the secondary TAC) may be configured to report all observed TAIs. For example, the enabled UE1 102a may report TA1 and TA5, and the enabled UE may also report the respective TAs as a primary TA (e.g., TA 5) and a secondary TA (e.g., TA 1). Since TA1 and TA5 belong to the same cell (e.g., cell 911 and/or cell 912) from the RAN perspective, UE1 102a may obtain an allowed nsai associated with network slices A, B and C, where RA is configured to be equal to TA1. For example, UE1 102a may cause a message to be transmitted to AMF 108 via cell 912 (e.g., when at location 914) indicating TA1 is the primary TA and TA5 is the secondary TA, and in response, UE1 102a may receive an allowed nsai associated with network slices A, B and C from AMF 108 via cell 912. The UE may report only one of the observed TAs (e.g., primary TA 5). The AMF 108 may be preconfigured with information about the primary and secondary TAs (e.g., for the deployment area 900), and based on the preconfigured information about the primary and secondary TAs, the AMF 108 may assign one or more secondary TAs as part of the RA of the UE (e.g., UE1 102 a). For example, if UE1 102a registers via TA5 and UE1 102a is determined to be an enabled UE, the network may assign/provide ra=ta1 to UE1 102a without rejecting the initial registration request.

Upon determining that an additional TAC other than the TAC reported by the UE is assigned by the network, the enabled UE (e.g., UE1102 a) may initiate a registration area update procedure. For example, UE1102a may receive a secondary TAC associated with cell 904 and TA4, after reporting TA5 to the network, the network may determine that UE1102a is an enabled UE, and that UE1102a is located in the SA of cell 904 (e.g., via a cell identifier). Such as when there is a subscription change, the network (e.g., AMF 108) may page one or more UEs within the SA of cell 904 and the one or more UEs may access updated/changed network slices associated with the subscription change configured in cell 904. The UE may perform cell selection and/or cell reselection based on all S-nsais or network slice groups supported by all TACs of the corresponding cells in the selected network.

The RAN node (e.g., next Generation (NG) -RAN node, gNB, etc.) may broadcast/transmit one or more additional TAIs (e.g., secondary TAIs) via a second IE that is different from the first IE that includes the primary TAIs configured in the SIB. The AMF may be configured to obtain/retrieve information associated with network slices supported by the primary TAI and the secondary TAI via the NGAP process (e.g., from a repository configured via memory). The AMF may be configured to assign a registration area based on the primary TAC and the secondary TAC. The AMF may be configured to determine (e.g., based on transmissions from the UE, or information stored in a network repository associated with the UE ID) whether the UE is an enabled UE (i.e., a UE that is enabled/configured to read the second IE and determine the secondary TAC/TAI), or an non-enabled UE (i.e., a UE that is not enabled/configured to read the second IE and determine the secondary TAC/TAI). The AMF may cause transmission, via the RAN node, of a paging message to one or more UEs indicating one or more of the primary TAC/TAI, the secondary TAC/TAI, the NGAP procedure, or the corresponding registration area.

When detecting/determining that multiple TACs are available for the selected network (e.g., PLMN, etc.), the UE may select a TAC during cell selection and reselection according to one or more TAC priority criteria described above. For example, UE1 102a, when located at location 916, may be capable of selecting a service from network slice a via one or more of cell 901, cell 902, and cell 903. At location 916, UE1 102a is at least partially covered by cell 901 and cell 902 associated with TA2, and cell 903 associated with TA 3. UE1 102a may select between TA2 and TA3 based on the prioritization of network operator configurations reflected via the SIBs. In the case of registration and registration area update procedures, the UE may report the observed TAC (e.g., to a network, AMF, etc.). The UE may perform a registration procedure when detecting/determining additional secondary TACs (e.g., read in the SIB). It should be appreciated that in some embodiments, by providing at least the secondary TAC to the enabled UEs, instead of assigning additional TACs to one or more cells in the area to support additional network slices, all UEs in the area that have no relation to the additional network slices need not perform additional registration updates.

One or more private networks may be deployed in association with a SA (e.g., YSA 704, XSA 706, or any other SA described herein). For example, access to a network slice and/or services provided by the network slice may be restricted within the SA by deploying the network slice as a private network within the SA. For example, network slice Y (e.g., associated with S-NSSAI Y) may be configured as a private network (e.g., PNI-NPN, SNPN, etc.) within YSA 704. The RAN node and/or its cells associated with YSA 704 may be configured to broadcast (e.g., cause transmission to UEs within YSA 704) a Closed Access Group (CAG) Identifier (ID). The CAG-ID may be received by the UE and may be used to determine an identity of a private network (e.g., PNI-NPN, SNPN, etc.) within YSA 704. For example, a UE within YSA 704 may receive a CAG-ID associated with network slice Y, which is deployed as a PNI-NPN, and the UE determines to use resources of the cell and/or services of network slice Y via the CAG identified by the CAG-ID. The UE may determine whether the PDU session associated with S-nsai Y may be used based on the CAG-ID associated with the PDU session.

The network slice may be deployed as a PNI-NPN in a portion of deployment region 900 (e.g., within cell 905 and cell 903). Cells in the portion of deployment area 900 covered by the PNI-NPN may be configured to broadcast a CAG-ID (e.g., CAG-ID nn) associated with the PNI-NPN. One or more UEs using (e.g., accessing, requesting, etc.) services provided by the PNI-NPN may be configured with a DNN allowed CAG list including the CAG-ID. The UE routing policy (urs) sent by the PCF (e.g., PCF 114) may include a list of allowed CAG IDs associated with one or more DNNs and/or S-nsais. The UE may consider the allowed CAG ID list before initiating a PDU session request. The SMF (e.g., SMF 110) may accept or reject one or more PDU sessions for the respective DNN and/or S-nsai based on the DNN allowed CAG ID list. The allowed CAG list associated with the respective DNN and/or S-nsai may be a subset of the allowed configuration list that the UE is given for mobility management procedures.

Fig. 10 is a signaling diagram illustrating an example signal sequence 1000 for supporting non-uniform network slice deployment across deployment areas (e.g., deployment areas 700, 900, 800 as described above) between communication devices (e.g., UEs 102, gnbs, devices 200, etc.) at least by way of a network infrastructure (e.g., communication networks 100, 500, etc.). As shown, the example network infrastructure for signal sequence 1000 includes at least UE 102, RAN 104, AMF 108, and SMF 110. The network infrastructure for the signal sequence 1000 may include one or more other network entities described above with respect to fig. 1-9, such as the UPF 106, UDM 118, UE1 102a, base station 802b, first network slice 501, etc., described herein.

RAN 104 may be configured with one or more base stations (e.g., base station 802b, etc.) and one or more cells (e.g., cell 804b, cell 902, etc.) for performing the operations described below with respect to fig. 10. One or more base stations may be configured to communicate (e.g., via an Xn interface, etc.) with one or more other base stations. The network infrastructure may be configured according to 5G system standards or the like (e.g., 4G, LTE, etc.), and the serving RAN (e.g., RAN 104, etc.) may include one or more 5G radio nodes, such as one or more gnbs or equivalents. The signal sequence 1000 may be implemented with one or more network infrastructures associated with one or more networks (e.g., PLMN, PNI-NPN, SNPN, etc.), and each respective one of the one or more networks may include one or more network slices (e.g., network slice Y as described above). The one or more network slices may be associated with one or more SAs of an RA of a deployment area (e.g., deployment area 700, 900, 800 as described above).

The signal sequence 1000 begins at block 1002, where the AMF 108 and RAN 104 are configured via a Next Generation (NG) setup to support mapping of S-nsais to respective TAIs. For example, the AMF 108 may be configured to obtain/retrieve information via at least a repository configured via a network-accessible memory (e.g., memory 204) to associate respective network slices with one or more of the primary TAI and/or the secondary TAI via an NGAP process. The RAN node of RAN 104 may be configured, such as by AMF 108, to receive and/or transmit a plurality of TAIs at least between AMF 108 and UE 102. The respective S-nsais mapped to the respective network slices and TAI/TACs may be configured according to the S-nsai format 600 described above. Upon detecting the UE 102 (e.g., requesting service), the RAN 104 causes transmission of a plurality of TACs associated with the primary TAI and one or more secondary TAIs configured during NG establishment, see block 1004.RAN 104 may broadcast a plurality of TACs via one or more RAN nodes and one or more cells. The broadcast information including the plurality of TACs may be formatted according to SIBs configured with at least a first IE and a second IE, as described above.

At block 1006, the UE 102 determines to camp on a cell of a RAN node (e.g., a RAN node that broadcasts/transmits multiple TACs to the UE 102). UE 102 may determine to camp on the cell based at least on the broadcast information received by UE 102 at block 1004. The UE 102 may identify and/or select one or more TACs based on the received plurality of TACs for performing the registration process, see block 1008. For example, based on its current location within the registration area and/or available cells, the UE 102 may identify and then select the primary TAC and the secondary TAC to send back to the network (e.g., AMF 108, SMF 110) to establish, for example, a PDU session.

At block 1010, one or more of UE 102, RAN 104, AMF 108, and SMF 110 perform a registration procedure to register UE 102 with a network and/or network slice associated with at least one of the selected TACs. At block 1012, one or more of the UE 102, RAN 104, AMF 108, and SMF 110 perform a transition procedure of the UE 102 to idle mode. While in idle mode (e.g., idle mode mobility state), the UE may request to establish, and/or reestablish, a PDU session for the network slice associated with the selected TAC and/or S-nsai mapped to the selected TAC.

At block 1014, the SMF 110 is configured to cause transmission of a Downlink (DL) PDU associated with a PDU session associated with S-NSSAI identified to the network by the UE 102 via at least one of the selected TACs. The SMF 110 causes initiation of a namf_communication_n1n2message transfer service with at least the AMF 108, see block 1016. At block 1018, AMF 108 selects one or more RAN nodes to send one or more paging messages. The selection of the one or more RAN nodes may be based on S-nsais and additional S-nsais supported (or not supported) by the one or more RAN nodes associated with RAN 104 and/or RA, and one or more additional RAN nodes. The AMF 108 may also cause transmission of a paging message to the selected RAN node and may identify a target UE (e.g., UE 102) for receiving the paging message. Upon receiving the paging message, RAN 104 may cause transmission of the paging message to one or more target UEs (e.g., UE 102) via the selected RAN node.

The operations/processes described above with respect to fig. 10 may be performed in response to one or more previous operations/processes, e.g., UE 102 may automatically perform the identification and/or selection of block 1008 based on the determination completed at block 1006. One or more additional operations/procedures (not shown) may be performed during the signal sequence 1000, e.g., after the operations/procedures of block 1008, the UE 102 may cause transmission of the selected TAC to the AMF 108 via the RAN 104 to initiate the operations/procedures of block 1010. In some embodiments, the transmission of the selected TAC may be performed, for example, as part of a registration process. In some embodiments, in instances where RAN 104 forwards the selected TAC to AMF 108, RAN 104 may additionally indicate a primary tracking area code and a secondary tracking area code(s). As described above, the information about the TA may be in the form of TAI. In some embodiments, the information about the TA may include the following semantics: the primary TAC and/or one or more secondary TACs may represent a wide area slice or a limited area slice (e.g., a limited, or restricted service area slice). The limited area slice may be a dynamic slice, which may be deployed over a period of time. That is, the dynamic slice may be a temporary slice. Signal sequence 1000 may include one or more additional operations/processes (not shown) as described above with respect to fig. 1-9, as described below with respect to fig. 11-13, and/or any other configuration, operation, and/or process described herein.

In some embodiments, such as in instances where the UE includes the capability to read multiple TACs, the NGAP user location information (e.g., as shown in fig. 17A) contained in the NGAP initial UE message includes multiple TAIs broadcast by the NG-RAN cell in which the UE has established a connection. In this regard, in some embodiments, the IE may indicate the primary TAI and the at least one secondary TAI (e.g., by marking or tagging the primary TAI and/or the at least one secondary TAI). In some embodiments, the IE may indicate (e.g., by a marker or label) at least one secondary TAI for the limited service area slice(s).

In some embodiments, such as in instances where the UE does not include the capability to read multiple TACs, the NGAP user location information contained in the NGAP initial UE message contains a single TAI broadcast by the NG-RAN cell in which the UE has established a connection. It should be appreciated that throughout this disclosure, the term TAC may also refer to TAI, for example, if there is a selected network. In this regard, the combination of TAC and network identifier may form a TAI.

Although the user location information may be provided in various ways, one example of an initial UE message including the user location information is provided below:

/>

Where M indicates a mandatory IE and O indicates an optional IE in this example embodiment. Further, the initial UE message may include more or different fields and IEs than those in the above table, which is provided by way of example and not limitation.

Regarding the TAI list, the IE indicates a TAI list, such as that broadcast by the NGRAN node, that can be accessed by the UE. Although the TAI list may be structured in various ways, an example TAI list (e.g., as part of NR user location information) is structured as follows:

in this example embodiment, the TAI type IE may be included in messages exchanged according to fig. 14A to 16B. Further, the TAI list may include more, or different, fields and IEs than those in the above table, which is provided by way of example and not limitation.

In another embodiment, the NGAP setup (e.g., NG setup request, as shown in fig. 16A and 17B) may include a TAI slice support list, which may be marked and/or annotated to indicate a primary TAI and one or more secondary TAIs. In some embodiments, the associated IE indicates at least one secondary TAI for the limited service area slice (e.g., by marking and/or labeling). In some embodiments, the response message (e.g., an NG setup response as shown in fig. 16A) may include a slice support list, which may be marked and/or annotated to indicate the primary slice and one or more secondary slices. In some embodiments, the associated IE indicates at least one secondary slice (e.g., by marking and/or labeling) for the limited service area slice. In some embodiments, a configuration message (e.g., an AMF configuration update message) from the core network entity to the RAN entity may include a slice support list, which may be marked and/or annotated to indicate the primary slice and one or more secondary slices. In some embodiments, the associated IE indicates at least one secondary slice (e.g., by marking and/or labeling) of the limited service area slice.

In another embodiment, as shown in fig. 14A, an Xn-AP setup (e.g., an Xn setup request) may include a TAI slice support list, which may be marked and/or annotated to indicate a primary TAI and one or more secondary TAIs. In some embodiments, the associated IE indicates at least one secondary TAI for the limited service area slice (e.g., by marking and/or labeling). In some embodiments, the response message (e.g., an Xn setup response as shown in fig. 14A) may also include a TAI slice support list, which may be marked and/or annotated to indicate the primary TAI and one or more secondary TAIs. In some embodiments, the associated IE indicates at least one secondary TAI for the limited service area slice (e.g., by marking and/or labeling).

In another embodiment, as shown in fig. 15A, the F1-AP setup (e.g., F1 setup request) may include a TAI slice support list, which may be marked and/or annotated to indicate a primary TAI and one or more secondary TAIs. In some embodiments, the associated IE indicates at least one secondary TAI for the limited service area slice (e.g., by marking and/or labeling). It should be appreciated that throughout this disclosure, information regarding the primary TAI and one or more secondary TAIs may be tabulated in different formats, e.g., where F1 setup requests (as shown in fig. 15A) and the gNB-DU configuration updates (as shown in fig. 15B), the information may be embedded in the serving cell information IE. Combinations of different formats are also possible.

In some embodiments, the 5GC may provide the UE with slices of overlapping TAIs as allowed nsais, since the NG-RAN node supports slices from a radio and protocol perspective. In some embodiments, the UE may include the primary TAI and at least one secondary TAI in the registration request message. Such messages may include fields such as [ attached TAI: primary and secondary (if supported) to indicate the information needed.

In some embodiments, there may be one or more primary TAIs, and/or one or more secondary TAIs.

Fig. 11 is a flowchart of operations of an example method 1100 performed by the example apparatus 200, which in turn may comprise a computer program product comprising a non-transitory computer-readable storage medium storing computer program code to be executed by the at least one computer processor 202, in some embodiments, the example apparatus 200 may be implemented by one or more computing devices (e.g., as described above with respect to fig. 4), such as a user equipment (e.g., UE 102, a smart phone, a laptop computer, etc.). The user equipment may communicate with at least the network and/or network slice via one or more of a cell, beam, base station, processor, or the like, such as described above with respect to communication networks 100 and/or 500.

As shown in block 1102, the apparatus 200 of this example embodiment includes means, such as the processor 202, the memory 204, the communication interface 206, etc., for receiving a plurality of tracking area codes associated with at least one network from a cell. As shown in block 1104, the apparatus 200 (e.g., UE 102, smart phone, laptop or tablet computer, etc.) is further configured with means, such as processor 202, communication interface 206, etc., for selecting a tracking area code from a plurality of tracking area codes associated with at least one network. In an example embodiment, the different TAC(s) may be broadcast per network (such as per PLMN or SNPN) and then the TAC is selected from the TAC(s) for the corresponding network. In another embodiment where both PLMN X and PLMN Y may broadcast TACs, the apparatus may be configured to: in the case of PLMN X and PLMN Y being equivalent, a selection is made between TAC a of PLMN X and TAC B of PLMN Y. The apparatus 200 (e.g., UE 102, smart phone, laptop or tablet computer, etc.) may also be configured to identify a first tracking area code, and one or more second tracking area codes, from among a plurality of tracking area codes, see block 1106. At block 1108, based on the identified first tracking area code and the identified one or more second tracking area codes, the apparatus 200 may also be configured with means for selecting the first tracking area code (e.g., as a primary tracking area code) and/or means for selecting one of the one or more second tracking area codes (e.g., as a secondary tracking area code) for reporting to an AMF of the network or a network slice associated with the tracking area code.

Fig. 12 is a flowchart of operations of an example method 1200 performed by the example apparatus 200, in some embodiments, the example apparatus 200 may be implemented by one or more computing devices (e.g., as described above with respect to fig. 4), such as a network server that at least partially hosts one or more network functions (e.g., AMF 108, etc.). One or more computing devices in turn can include a computer program product comprising a non-transitory computer-readable storage medium storing computer program code to be executed at least by processor 202. One or more computing devices may communicate with at least one radio access network (e.g., RAN 104) via one or more interfaces (e.g., N2 interface, etc.), such as described above with respect to communication networks 100 and/or 500. One or more computing devices may communicate with at least one user device (such as UE 102, etc.) via one or more interfaces (e.g., an N1 interface, an N2 interface, etc.).

The method 1200 may begin at block 1202 when the apparatus 200 of this example embodiment (e.g., an AMF server associated with AMF 108) includes means, such as a processor 202, a memory 204, a communication interface 206, etc., for determining a paging area based on one or more first single network slice selection assistance information associated with one or more protocol data unit sessions, and one or more second single network slice selection assistance information. The one or more second single network slice selection assistance information is supported by the at least one radio access network node associated with the registration area, and the one or more protocol data unit sessions are configured to cause paging between the AMF 108 and the UE 102 via at least the RAN 104.

As shown in block 1204, the apparatus 200 may also be configured with means, such as the processor 202, the communication interface 206, etc., for retrieving, via at least an application protocol process, a plurality of tracking area codes including a first tracking area code, and one or more second tracking area codes. The apparatus 200 (e.g., a server, etc.) may also be configured to cause transmission of a plurality of tracking area codes associated with at least one network to a user equipment via at least a cell, see block 1206. At block 1208, based on the identified first tracking area code and the identified one or more second tracking area codes, the apparatus 200 may be further configured with means for selecting the first tracking area code (e.g., as a primary tracking area code), and/or means for receiving a registration request from the user device via at least the cell, the registration request including the primary tracking area code and the one or more secondary tracking area codes.

Fig. 13 is a flowchart of operations of an example method 1300 performed by the example apparatus 200, which in some embodiments, the example apparatus 200 may be implemented by one or more computing devices (e.g., as described above with respect to fig. 4), such as a radio access network (e.g., RAN 104, etc.) or a portion thereof (e.g., RAN node, gNB, base station 802b, cell 902, etc.). One or more computing devices in turn can include a computer program product comprising a non-transitory computer-readable storage medium storing computer program code to be executed at least by processor 202. One or more computing devices may communicate with at least one network and/or network slice via one or more interfaces (e.g., an N2 interface, etc.), such as described above with respect to communication networks 100 and/or 500. One or more computing devices may communicate with at least one user device (such as UE 102, etc.) via one or more interfaces (e.g., N2 interface).

As shown in block 1302, the apparatus 200 of this example embodiment includes means, such as the processor 202, the memory 204, the communication interface 206, etc., for causing transmission of a plurality of tracking area codes associated with at least one network to at least one user device, wherein respective ones of the plurality of tracking area codes are associated with one or more network slices, or one or more groups of network slices. As shown in block 1304, the apparatus 200 (e.g., base station 502 of serving cell 508A and at least beams 512 and/or 513, etc.) may also be configured with means, such as processor 202, communication interface 206, etc., for causing transmission of one or more network slices or one or more identifiers of one or more network slice groups to at least one user device for at least one respective tracking area code of a plurality of tracking area codes. As shown in block 1306, the apparatus 200 (e.g., base station 502 of serving cell 508A and at least beams 512 and/or 513, etc.) may also be configured with means for receiving a plurality of tracking area codes associated with at least one network from the network, wherein the plurality of tracking area codes includes a first tracking area code and one or more second tracking area codes.

As mentioned above, the flow charts of the referenced methods may be performed by an apparatus according to a related computer program product comprising computer program code. It will be understood that each block of the flowchart, and combinations of blocks in the flowchart, can be implemented by various means, such as hardware, firmware, processor, circuitry, and/or other devices associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory device (e.g., memory 204) of an apparatus (e.g., apparatus 200) employing an embodiment of the invention and executed by a processor (e.g., processor 202) of the apparatus.

As will be appreciated, any such computer program instructions may 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 implements the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture, the execution of which implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart block or blocks.

Thus, a computer program product is defined in the context of computer program instructions, such as computer-readable program code portions, being 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 above-described functions when executed. In other embodiments, computer program instructions (such as computer readable program code portions) need not be stored or otherwise embodied by a non-transitory computer readable storage medium, but may be embodied by a transitory medium, wherein the computer program instructions (such as computer readable program code portions) are still configured to perform the above-described functions when executed.

Accordingly, blocks of the flowchart support combinations of means for performing the specified functions and combinations of operations for performing the specified functions. It will also be understood that one or more blocks of the flowchart, and combinations of blocks in the flowchart, can be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.

In some embodiments, some of the operations, methods, steps, processes, etc., described above may be modified or further amplified. Further, in some embodiments, additional optional operations, methods, steps, procedures, etc. may be included. Modifications, additions, subtractions, inverse transforms, correlations, proportional relationships, non-proportional relationships, attenuations and/or amplifications of the above-described operations may be performed in any order and in any combination. It should also be appreciated that where specific operations, methods, procedures, etc. require specific hardware, such hardware may be considered part of the apparatus 200 of any such embodiment.

Many modifications and other embodiments of the inventions set forth herein will come to mind to one skilled in the art to which these inventions pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the inventions are not to be 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, while the foregoing description and related drawings describe example embodiments in the context of certain example combinations of elements and/or functions, it should be appreciated that different combinations of elements and/or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and/or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

1. A method, comprising:

receiving a plurality of tracking area codes associated with at least one network from a cell; and

a tracking area code is selected from the plurality of tracking area codes associated with the at least one network.

2. The method of claim 1, further comprising:

identifying a first tracking area code, and one or more second tracking area codes, from the plurality of tracking area codes; and

the first tracking area code or one of the one or more second tracking area codes is selected.

3. The method of any of claims 1-2, further comprising:

receiving one or more identifiers of one or more network slices or groups of network slices from the cell for at least one respective tracking area code of the plurality of tracking area codes;

receiving a tracking area identifier list from the cell, the tracking area identifier list comprising one or more of a forbidden tracking area identifier or a allowed tracking area identifier; and

a determination is made as to whether one or more tracking area codes of the plurality of tracking area codes are associated with the tracking area identifier list.

4. A method according to any one of claims 1 to 3, further comprising:

determining one or more allowable tracking area codes of the plurality of tracking area codes; and

Based on the relative priorities of the one or more allowed tracking area codes, a corresponding allowed tracking area code is selected.

5. The method of any one of claims 1 to 4, further comprising:

determining one or more forbidden tracking area codes of the plurality of tracking area codes; and

based on the relative priorities of the plurality of tracking area codes that are not disabled, a corresponding tracking area code is selected.

6. The method of any of claims 1-5, wherein the prioritization of the one or more second tracking area codes is based on an encoding order associated with the plurality of tracking area codes.

7. The method of any of claims 1-6, wherein the first tracking area code of the plurality of tracking area codes is associated with a first information element of a system information block.

8. The method of claim 7, wherein the one or more second tracking area codes of the plurality of tracking area codes are associated with a second information element of the system information block, the second information element being different from the first information element.

9. The method of any of claims 1 to 8, wherein the first tracking area code is a primary tracking area code and the one or more second tracking area codes are secondary tracking area codes.

10. The method of any of claims 1 to 9, wherein respective ones of the plurality of tracking area codes are mapped to respective single network slice selection assistance information.

11. The method of any of claims 1 to 10, wherein the at least one network comprises one or more of a public land mobile network, a standalone non-public network, or a public network integrated non-public network.

12. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code,

the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform the method of any one of claims 1 to 11.

13. A computer program product comprising a non-transitory computer readable storage medium having program code portions stored thereon, the program code portions being configured, when executed, to perform the method of any of claims 1 to 11.

14. An apparatus, comprising:

means for receiving a plurality of tracking area codes associated with at least one network from a cell; and

Means for selecting a tracking area code from the plurality of tracking area codes.

15. The apparatus of claim 14, further comprising:

means for identifying a first tracking area code, and one or more second tracking area codes, from the plurality of tracking area codes; and

means for selecting the first tracking area code or one of the one or more second tracking area codes associated with the at least one network.

16. The apparatus of any of claims 14 to 15, further comprising:

means for receiving one or more identifiers of one or more network slices or one or more network slice groups from the cell for at least one respective tracking area code of the plurality of tracking area codes;

means for receiving a tracking area identifier list from the cell, the tracking area identifier list comprising one or more of a forbidden tracking area identifier or a allowed tracking area identifier; and

means for determining whether one or more tracking area codes of the plurality of tracking area codes are associated with the tracking area identifier list.

17. The apparatus of any of claims 14 to 16, further comprising:

means for determining that one or more of the plurality of tracking area codes allow tracking area codes; and

means for selecting a respective allowable tracking area code based on the relative priorities of the one or more allowable tracking area codes.

18. The apparatus of any of claims 14 to 17, further comprising:

means for determining one or more forbidden tracking area codes of the plurality of tracking area codes; and

means for selecting a respective tracking area code based on the relative priorities of the plurality of tracking area codes that are not disabled.

19. The apparatus of any of claims 14 to 18, wherein the prioritization of the one or more second tracking area codes is based on an encoding order associated with the plurality of tracking area codes.

20. The apparatus of any of claims 14 to 19, wherein the first tracking area code of the plurality of tracking area codes is associated with a first information element of a system information block.

21. The apparatus of claim 20, wherein the one or more second tracking area codes of the plurality of tracking area codes are associated with a second information element of the system information block, the second information element being different from the first information element.

22. The apparatus of any of claims 14 to 21, wherein the first tracking area code is a primary tracking area code and the one or more second tracking area codes are secondary tracking area codes.

23. The apparatus of any of claims 14 to 22, wherein respective ones of the plurality of tracking area codes are mapped to respective single network slice selection assistance information.

24. The apparatus of any of claims 14 to 23, wherein the at least one network comprises one or more of a public land mobile network, a standalone non-public network, or a public network integrated non-public network.

25. A method, comprising:

the paging area is determined based on one or more first single network slice selection assistance information associated with one or more protocol data unit sessions that cause paging, and one or more second single network slice selection assistance information supported by at least one radio access network node associated with a registration area.

26. The method of claim 25, further comprising:

retrieving a plurality of tracking area codes via at least an application protocol process, the plurality of tracking area codes including a first tracking area code and one or more second tracking area codes;

causing transmission of the plurality of tracking area codes associated with at least one network to a user equipment via at least a cell; and

a registration request is received from the user equipment via at least the cell, the registration request including a primary tracking area code and one or more secondary tracking area codes.

27. The method of claim 26, wherein the at least one network comprises one or more of a public land mobile network, a standalone non-public network, or a public network integrated non-public network.

28. The method of any of claims 25 to 27, further comprising:

causing transmission of at least an additional secondary tracking area code to the user equipment via at least the cell.

29. The method of any of claims 25 to 28, further comprising:

the registration area is assigned to the user device based at least on the primary tracking area code and the one or more secondary tracking area codes.

30. The method of claim 29, further comprising:

determining a tracking area identifier list, the tracking area identifier list comprising one or more of a forbidden tracking area identifier or an allowed tracking area identifier; and

causing transmission of the tracking area identifier list to the user equipment at least via the cell.

31. The method of any of claims 25 to 30, wherein the prioritization of the one or more second tracking area codes is based on an encoding order associated with the plurality of tracking area codes.

32. The method of any of claims 25-31, wherein the first tracking area code of the plurality of tracking area codes is associated with a first information element of a system information block.

33. The method of claim 32, wherein the one or more second tracking area codes of the plurality of tracking area codes are associated with a second information element of the system information block, the second information element being different from the first information element.

34. The method of any of claims 25 to 33, wherein the first tracking area code is the primary tracking area code and the one or more second tracking area codes are secondary tracking area codes.

35. The method of any of claims 25 to 34, wherein respective ones of the plurality of tracking area codes are mapped to respective single network slice selection assistance information.

36. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code,

the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform the method of any one of claims 25 to 35.

37. A computer program product comprising a non-transitory computer readable storage medium having program code portions stored thereon, the program code portions being configured, when executed, to perform the method of any of claims 25 to 35.

38. An apparatus, comprising:

means for determining a paging area based on one or more first single network slice selection assistance information associated with one or more protocol data unit sessions, and one or more second single network slice selection assistance information, wherein the one or more second single network slice selection assistance information is supported by at least one radio access network node associated with a registration area, wherein the one or more protocol data unit sessions cause paging.

39. The apparatus of claim 38, further comprising:

means for retrieving a plurality of tracking area codes via at least an application protocol process, the plurality of tracking area codes including a first tracking area code and one or more second tracking area codes;

means for causing transmission of a plurality of tracking area codes associated with at least one network to a user equipment via at least a cell; and

means for receiving a registration request from the user equipment via at least the cell, the registration request comprising a primary tracking area code and one or more secondary tracking area codes.

40. The apparatus of claim 39, wherein the at least one network comprises one or more of a public land mobile network, a standalone non-public network, or a public network integrated non-public network.

41. The apparatus of any one of claims 38 to 40, further comprising:

means for causing transmission of at least an additional secondary tracking area code to the user equipment via at least the cell.

42. The apparatus of any one of claims 38 to 41, further comprising:

means for assigning a registration area to the user device based at least on the primary tracking area code and the one or more secondary tracking area codes.

43. The apparatus of claim 42, further comprising:

means for determining a tracking area identifier list, the tracking area identifier list comprising one or more of a forbidden tracking area identifier or an allowed tracking area identifier; and

means for causing transmission of the tracking area identifier list to the user equipment at least via the cell.

44. The apparatus of any of claims 38 to 43, wherein the prioritization of the one or more second tracking area codes is based on an encoding order associated with the plurality of tracking area codes.

45. The apparatus of any of claims 38 to 44, wherein the first tracking area code of the plurality of tracking area codes is associated with a first information element of a system information block.

46. The apparatus of claim 45, wherein the one or more second tracking area codes of the plurality of tracking area codes are associated with a second information element of the system information block, the second information element being different from the first information element.

47. The apparatus of any of claims 38 to 46, wherein the first tracking area code is the primary tracking area code and the one or more second tracking area codes are secondary tracking area codes.

48. The apparatus of any of claims 38 to 47, wherein respective ones of the plurality of tracking area codes are mapped to respective single network slice selection assistance information.

49. A method, comprising:

causing transmission of a plurality of tracking area codes associated with at least one network to at least one user device, wherein respective ones of the plurality of tracking area codes are associated with one or more network slices, or one or more groups of network slices.

50. The method of claim 49, further comprising:

for at least one respective tracking area code of the plurality of tracking area codes, causing transmission of one or more identifiers of the one or more network slices or the one or more network slice groups to the at least one user device.

51. The method of any one of claims 49 to 50, further comprising:

the method includes receiving, from a network, the plurality of tracking area codes associated with the at least one network, wherein the plurality of tracking area codes includes a first tracking area code and one or more second tracking area codes.

52. The method of claim 51, wherein the prioritization of the one or more second tracking area codes is based on an encoding order associated with the plurality of tracking area codes.

53. The method of any of claims 49-52, wherein the first tracking area code of the plurality of tracking area codes is associated with a first information element of a system information block.

54. The method of claim 53, wherein the one or more second tracking area codes of the plurality of tracking area codes are associated with a second information element of the system information block, the second information element being different from the first information element.

55. The method of any of claims 49 to 54, wherein the first tracking area code is a primary tracking area code and the one or more second tracking area codes are secondary tracking area codes.

56. The method of any of claims 49-55, wherein respective ones of the plurality of tracking area codes are mapped to respective single network slice selection assistance information.

57. The method of any one of claims 49 to 56, wherein the at least one network comprises one or more of a public land mobile network, a stand alone non-public network, or a public network integrated non-public network.

58. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code,

the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform the method of any one of claims 49 to 57.

59. A computer program product comprising a non-transitory computer readable storage medium having program code portions stored thereon, the program code portions being configured, when executed, to perform the method of any of claims 49 to 57.

60. An apparatus, comprising:

means for causing transmission of a plurality of tracking area codes associated with at least one network to at least one user device, wherein respective ones of the plurality of tracking area codes are associated with one or more network slices, or one or more groups of network slices.

61. The apparatus of claim 60, further comprising:

means for causing transmission of one or more identifiers of the one or more network slices or the one or more network slice groups to the at least one user device for at least one respective tracking area code of the plurality of tracking area codes.

62. The apparatus of any one of claims 60 to 61, further comprising:

means for receiving the plurality of tracking area codes associated with the at least one network from the network, wherein the plurality of tracking area codes includes a first tracking area code and one or more second tracking area codes.

63. The apparatus of claim 62, wherein the prioritization of the one or more second tracking area codes is based on an encoding order associated with the plurality of tracking area codes.

64. The apparatus of any of claims 60-63, wherein the first tracking area code of the plurality of tracking area codes is associated with a first information element of a system information block.

65. The apparatus of claim 64, wherein the one or more second tracking area codes of the plurality of tracking area codes are associated with a second information element of the system information block, the second information element being different from the first information element.

66. The apparatus of any of claims 60 to 65, wherein the first tracking area code is a primary tracking area code and the one or more second tracking area codes are secondary tracking area codes.

67. The apparatus of any of claims 60 to 66, wherein respective ones of the plurality of tracking area codes are mapped to respective single network slice selection assistance information.

68. The apparatus of any one of claims 60 to 67, wherein the at least one network comprises one or more of a public land mobile network, a standalone non-public network, or a public network integrated non-public network.

69. A method, comprising:

causing transmission of a message from a first node to a second node comprising a list of tracking area identifiers, wherein the list of tracking area identifiers comprises a plurality of tracking area identifiers, and wherein a respective tracking area identifier of the plurality of tracking area identifiers is indicated as a primary tracking area identifier or a secondary tracking area identifier; and

a response is received from the second node based at least on the message including the tracking area identification list.

70. The method of claim 69, wherein the first node comprises a first next generation radio access network (NG-RAN) node and the second node comprises a second NG-RAN node.

71. The method of claim 70, wherein the message comprises an Xn setup request and the response comprises an Xn setup response.

72. The method of claim 70 wherein the message comprises an NG-RAN node configuration update and the response comprises an NG-RAN node configuration update acknowledgement.

73. The method of claim 69, wherein the first node comprises a next generation node B distributed unit (gNB-DU) and the second node comprises a next generation node B central unit (gNB-CU).

74. The method of claim 73, wherein the message comprises an F1 setup request and the response comprises an F1 setup response.

75. The method of claim 73, wherein the message includes a gNB-DU configuration update and the response includes a gNB-DU configuration update acknowledgement.

76. The method of claim 69, wherein the first node comprises a first next generation radio access node (NG-RAN) node and the second node comprises an access and mobility management function (AMF).

77. The method of claim 76 wherein the message comprises a Next Generation (NG) setup request and the response comprises a NG setup response.

78. The method of claim 76, wherein the message includes a Radio Access Node (RAN) configuration update and the response includes a RAN configuration update acknowledgement.

79. The method of claim 76, wherein the message comprises an initial User Equipment (UE) message.

80. The method of any of claims 69-79, wherein the message further includes a semantic description indicating a wide area slice classification or a limited area slice classification.

81. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform the method of any one of claims 69-80.

82. A computer program product comprising a non-transitory computer readable storage medium having program code portions stored thereon, the program code portions being configured, when executed, to perform the method of any of claims 69 to 80.

83. An apparatus, comprising:

means for causing transmission of a message from a first node to a second node comprising a list of tracking area identities, wherein the list of tracking area identities comprises a plurality of tracking area identities, and wherein a respective tracking area identity of the plurality of tracking area identities is indicated as a primary tracking area identity or a secondary tracking area identity; and

Means for receiving a response from the second node based at least on the message comprising the tracking area identification list.

84. The apparatus of claim 83, wherein the first node comprises a first next generation radio access network (NG-RAN) node and the second node comprises a second NG-RAN node.

85. The apparatus of claim 84, wherein the message comprises an Xn setup request and the response comprises an Xn setup response.

86. The apparatus of claim 84, wherein the message comprises an NG-RAN node configuration update and the response comprises an NG-RAN node configuration update acknowledgement.

87. The apparatus of claim 83, wherein the first node comprises a next generation node B distributed unit (gNB-DU) and the second node comprises a next generation node B central unit (gNB-CU).

88. The apparatus of claim 87, wherein the message comprises an F1 setup request and the response comprises an F1 setup response.

89. The apparatus of claim 87, wherein the message comprises a gNB-DU configuration update and the response comprises a gNB-DU configuration update acknowledgement.

90. The apparatus of claim 83, wherein the first node comprises a first next generation radio access network (NG-RAN) node and the second node comprises an access and mobility management function (AMF).

91. The apparatus of claim 90, wherein the message comprises a Next Generation (NG) setup request and the response comprises a NG setup response.

92. The apparatus of claim 90, wherein the message comprises a Radio Access Network (RAN) configuration update and the response comprises a RAN configuration update acknowledgement.

93. The apparatus of claim 90, wherein the message comprises an initial User Equipment (UE) message.

94. The apparatus of any of claims 83-93, wherein the message further comprises a semantic description indicating a wide area slice classification or a limited area slice classification.