WO2020040752A1

WO2020040752A1 - Support for enterprise network slicing and flexible sub-slicing controlled by an enterprise

Info

Publication number: WO2020040752A1
Application number: PCT/US2018/047361
Authority: WO
Inventors: Padma Sudarsan; Devaki Chandramouli; Cinzia Sartori
Original assignee: Nokia Technologies Oy; Nokia Usa Inc.
Priority date: 2018-08-21
Filing date: 2018-08-21
Publication date: 2020-02-27

Abstract

In some example embodiment, there may be provided an apparatus including 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 to at least: obtain an enterprise identifier indicating at least one network slice allocated to an enterprise; and send, as part of connection establishment with a radio access network, a message to a radio access network, the message including the enterprise identifier and a request to be assigned to an enterprise bundle including the at least one network slice allocated to the enterprise. Related systems, methods, and articles of manufacture are also described.

Description

SUPPORT FOR ENTERPRISE NETWORK SLICING AND FLEXIBLE SUB-SLICING

CONTROLLED BY AN ENTERPRISE

Field

[0001] The subject matter described herein relates to wireless.

Background

[0002] As the cellular system including the Fifth Generation (5G) system supports an increasing number of devices and services including applications with a wide range of use cases and diverse needs with respect to bandwidth, latency, and reliability requirements, the cellular system may need to prioritize resources across the wireless access network and the core network (and/or for example, prioritizing across the control plane and the user plane) to support differentiation among different services.

Summary

[0003] Methods and apparatus, including computer program products, are provided for enterprise network slices.

[0004] In some example embodiment, there may be provided an apparatus including 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 to at least: obtain an enterprise identifier indicating at least one network slice allocated to an enterprise; and send, as part of connection establishment with a radio access network, a message to a radio access network, the message including the enterprise identifier and/or a request for the at least one network slice allocated to the enterprise.

[0005] In some variations, one or more of the features disclosed herein including the following features can optionally be included in any feasible combination. The enterprise identifier may be an enterprise bundle identifier indicating the at least one network slice allocated to the enterprise by the network. The enterprise identifier may be obtained from a system information block, from a user equipment routing selection policy carried by a user equipment configuration update message, a storage device at the apparatus, an over-the-top-application, a web service, and/or a cloud server. The message may include a radio resource control message, a radio resource control setup complete message, and/or a configuration update message. The message may further include a single network slice selection assistance information including a slice service/type and/or slice differentiator. The enterprise identifier may be obtained, from the radio access network, based on subscription information, enterprise policy agreement, and/or operator policy associated with the apparatus. In response to the message being sent, a rejection of a connection to the radio access network may be received, the rejection based on subscription information and/or other policy indicating the apparatus is not allowed use of the at least one network slice identified by the enterprise identifier. The at least one network slice may include a bundle including at least one sub-slice. The at least one network slice may be allocated by the network to the enterprise based on a request from the enterprise, and wherein the enterprise creates or requests creation of the at least one sub-slice within the bundle.

[0006] In some example embodiment, there may be provided an apparatus including 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 to at least: receive, from a user equipment, an enterprise identifier indicating at least one network slice allocated to an enterprise associated with the user equipment; and select, based on the enterprise identifier, at least one network function in a core network.

[0007] In some variations, one or more of the features disclosed herein including the following features can optionally be included in any feasible combination. The enterprise identifier may be an enterprise bundle identifier indicating at least one network slice allocated to the enterprise by the network. The enterprise identifier may be received in a radio resource control message, a radio resource control setup complete message, and/or a configuration update message. The selection of the at least one network function may include selection of an access management function. The selection of the access management function may include sending, towards the access management function, a registration request including the identifier and/or a single network slice selection assistance information. A registration accept indicating an allowed at least one network slice and/or sub-slice allocated to the enterprise may be received, the allowed at least one network slice and/or sub-slice based on policy at a network slice selection function and/or network repository function.

[0008] In some example embodiment, there may be provided an apparatus including 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 to at least: receive, from a radio access network, a registration request including an enterprise identifier indicating at least one network slice allocated to an enterprise associated with the user equipment and network slice selection assistance information; receive subscription information for the user equipment; and select, based on the subscription information, at least one network function in the core network.

[0009] In some variations, one or more of the features disclosed herein including the following features can optionally be included in any feasible combination. The selection may include a selection, based on the enterprise identifier, of a session management function instance, user plane function instance, and/or an access management function instance. The selected at least one network function may include a selection, based on the enterprise identifier, of a session management function instance, user plane function instance, and/or an access management function instance. A registration accept message indicating whether the at least one network slice identified by the enterprise identifier is allowed for use by the user equipment may be sent towards the radio access network. The at least one network function, for the at least one slice allocated to the enterprise, may be selected based on policy from a network slice selection function and/or network repository function.

[0010] The above-noted aspects and features may be implemented in systems, apparatus, methods, and/or articles depending on the desired configuration. The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. Features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims.

Description of Drawings

[0011] In the drawings,

[0012] FIG. 1 depicts an example of a portion of a 5G wireless network, in accordance with some example embodiments;

[0013] FIG. 2 depicts a block diagram of a system in which an enterprise can create and/or access an enterprise bundle of network sub-slices, in accordance with some example embodiments;

[0014] FIG. 3 depicts an example of a process flow enterprise bundling of network sub- slices, in accordance with some example embodiments;

[0015] FIGs. 4A-4D depict an example of a sequence flow for enterprise bundling of network sub-slices, in accordance with some example embodiments;

[0016] FIG. 5 depicts an example of a network node, in accordance with some example embodiments; and

[0017] FIG. 6 depicts an example of an apparatus, in accordance with some example embodiments.

[0018] Like labels are used to refer to same or similar items in the drawings. Detailed Description

[0019] 5G wireless mobile technology may enable a broad range of use cases including services from enhanced Mobile Broadband (eMBB), to mission critical communication, as well as massive-scale connectivity for Internet of Things (IoT) devices, such as sensors, wearables, smart vehicles. 5G may also usher in new business models with different requirements from different vertical industries. For example, an enterprise customer may need ultra-reliable services, while another enterprise customer may need ultra-high-bandwidth communication, extremely low latency, or a combination of the two. The 5G network may be configured to offer different mixes of service capabilities to meet these different requirements at any given time.

[0020] To optimize the network to meet these different needs, network slicing may be used. A network slice refers to a logical network that provides specific network capabilities and network characteristics. The network slice may be considered a logical end-to-end network that can be dynamically created, so that a given user equipment may access different network slices over the same radio access network (e.g., over the same radio interface). The network slices can provide different services and/or have different QoS needs/requirements. 3GPP TS 23.501, System Architecture for the 5G System, describes examples of network slices. Network slicing may allow the running of multiple logical networks as virtually independent operations on a common physical infrastructure in an efficient and economical way. As such, the enterprises can meet, using network slicing, and the service level requirements for the type of specific service being offered.

[0021] In network slicing, the slice may be identified using a Single Network Slice Selection Assistance Information (S-NSSAI). The S-NSSAI may include the Slice Service/Type (SST) and/or Slice Differentiator (SD) fields. The Slice Differentiator (SD) field may be defined only by a network operator. Moreover, the Slice Differentiator (SD) is an optional information field that complements the Slice/Service type (SSTs) to differentiate among multiple network slices of the same Slice/Service type. The identification of the network slice may thus be from the perspective of the user equipment and/or the network operator. However, the prior network slice identification supports a process that assumes network slicing is always performed at the use case level first, such as at the level of the enhanced mobile broadband, Internet of Things, ultralow latency, and/or the like. Only as a next step is there provided further refinement to support network slicing which may be able support enterprises within the realms of different use or service cases. In practice, this implies that the user equipment may provide an S-NSSAI pointing (with the SST pointing) towards a given network slice, such as a vehicle-to-everything (V2X) network slice, for example. As a next step, if the Slice Differentiator (SD) is optionally provided by the user equipment, the SD may be used to direct the user equipment towards, for example, an appropriate vehicle-to-everything (V2X) network slice (e.g., a given network slice for a certain type or brand of vehicle). However, this process does not enable a model in which the network operator can assign a dedicated network slice for a specific enterprise and then allow the specific enterprise to further slice (e.g., into slices, such as sub-slices) the network slice. There is thus a need for network slicing that allows a network operator to provide or contract a network slice of the operator’s network to an enterprise, and then the enterprise can be allowed to further slice (e.g., sub-slice) the network slice to cater to the differing and varied needs of the enterprise’ s end- user, customers, for example.

[0022] In some example embodiments, a user equipment may indicate, to the network, network slice assistance information to enable the network to direct the user equipment towards a network slice allocated (e.g., assigned, owned, provided to, associated with, contracted) to an enterprise. This assistance information may include an identifier, such as an enterprise identifier identifying a network slice, or bundle of slices, allocated to the enterprise. The enterprise identifier may be implemented as an enterprise bundle identifier (EBID). [0023] In some example embodiments, an enterprise (e.g., an entity or other collection of users) may request an enterprise bundle of one or more slices with certain service level agreement (SLA) requirements. The network may respond with an enterprise bundle of one or more slices allocated to the enterprise. The enterprise may be allowed to create sub-slices within the enterprise bundle, although the network may create sub-slices within the allocated network bundle as well. In this way, the network may allocate the enterprise bundle of one or more network slices, while the enterprise itself may be able to control the slices/sub-slices within the allocated enterprise bundle.

[0024] In some example embodiments, the routing of user equipment may be based on an identifier, such as an enterprise identifier (also referred to herein as an enterprise bundle ID (EBID)), identifying the enterprise bundle slice. After an initial routing to the enterprise bundle slice, the user equipment may be further routed based on the SST and/or SD. For example, the identifier, such as the enterprise bundle ID (EBID), may be used to identify a network slice and, in particular, the enterprise resource bundle of network slice(s) assigned by the operator to the enterprise. Thus, the initial routing of UE towards the network slice may be based on the EBID. In some example embodiments, the enterprise may, in addition to the EBID, be allowed to further specify routing associated with a slice/sub-slice using the SST and/or the SD, so that the user equipment can be routed based on the SST/SD combination.

[0025] In some example embodiments, the user equipment may perform network/cell selection based on enterprise bundle ID.

[0026] In some example embodiments, selection of certain network functions (e.g., network nodes including certain network functions, such as the access and mobility management function (AMF) and/or the like) may be performed based on enterprise bundle ID. [0027] In some example embodiments, user equipment that are not configured with the enterprise bundle ID may be prohibited from accessing the enterprise bundle associated with the enterprise bundle ID.

[0028] Before providing additional description regarding the UE configuration in accordance with some example embodiments, an example of a portion of a 5G wireless network 100 is described with respect to FIG. 1.

[0029] The 5G wireless network 100 may include a user equipment (UE) 150A-C configured to wirelessly couple to a radio access network (RAN) 152 being served by a wireless access point, such as a base station, wireless local area network access point, home base station, and/or other type of wireless access point. When visiting a network, the UE may access the network’s radio access network.

[0030] The network 100 may include a core network, which may include an access and mobility management function (AMF) 154, a visiting session management function (V-SMF) 156, a visiting policy control function (v-PCF) 160, a visiting network slice selection function (v- NSSF) 164, and/or a visiting user plane function (V-UPF) 158. In the example of FIG. 1, devices 152-164 may be associated with a visiting public land mobile network (VPLMN) 166.

[0031] The network 100 and/or the core network may include devices having functions supporting a home public land mobile network (HPLMN) 170 as well. For example, these devices in the HPLMN 170 may include devices and corresponding functions for“home” wireless local area network (WLAN) access, offloading, and/or non-3GPP access. These devices may include a home SMF 172, a home PCF 174, a home NSSF 176, unified data management 178, an authentication server function (AUSF) 180, an application function (AF) 182, a home user plane function (H-UPF) 184, and a data network (DN) 186.

[0032] FIG. 1 also depicts service interfaces, such as Nl, N2, N3, N4, N6, N7, Nl l, N15, N18, N24, and/or the like. The architecture, nodes (including AMF, V-PCF, H-PCF, H- SMF, and V-SMF as well as other devices depicted at FIG. 1), and the service interfaces may be defined in accordance with a standard, such as 3 GPP TS 23.501, although other standards as well as proprietary interfaces may be used. Although FIG. 1 depicts a single visiting network and a single home network, other quantities of visiting and/or home network may be included as well.

[0033] A network slice, as noted above, refers to a logical network that provides specific network capabilities and network characteristics. The network slice may be considered a logical end-to-end network that can be dynamically created, so that a given UE may access different network slices over the same radio access network (e.g., over the same radio interface). The network slices can provide different services and/or have different QoS needs/requirements. 3GPP TS 23.501, System Architecture for the 5G System, describes examples of network slices.

[0034] The UE’s subscription information may dictate the configuration information related to the quantity, QoS type, and/or identity of the network slices. In some example embodiments, the UE’s subscription information may include the enterprise network bundle of network slices the UE is allowed to access. For example, the subscription information may list the EBIDs that the UE is allowed to access. Alternatively, or additionally, the subscription information may list the EBIDs that the UE is not allowed to access. The UE’s configuration information (provided by the network when registering in a PLMN, such as a VPLMN and/or HPLMN) may include one or more network slice identifiers, such as one or more single network slice selection assistance information (S-NSSAI). The S-NSSAI may be comprised of: a) a slice/service type (SST), which refers to the expected network slice behavior in terms of features and services; and/or b) a slice differentiator (SD), which is optional information that complements the slice/service type(s) to differentiate amongst multiple network slices of the same slice/service type. The S-NSSAI may be augmented with an EBID or some other identifier of the one or more network slices allocated to an enterprise. [0035] FIG. 2 depicts an example of a system 200, in accordance with some example embodiments. The system 200 may include a network operator portal 205, such as a cloud server, computer, web service, over-the-top service, and/or the like, that can be accessed by an enterprise portal 210, such as a cloud server, computer, over-the-top-application, and/or the like. In the example of FIG. 2, an enterprise may request at least one network slice (e.g., in the form of an enterprise bundle), and the bundle may have certain QoS requirements. For example, the enterprise portal 210 may allow the enterprise to request and be allocated (e.g., contract, purchase, be assigned, and/or the like) from the network operator portal 205 at least one network slice at a given service level or QoS in accordance with, for example, a service level agreement. The network operator’s network 212 may then fulfill the requested network slice(s) by allocating or creating, at 216, the network slice(s) for the enterprise. The network slice(s) form the enterprise resource bundle for the enterprise. The enterprise 210 may then create, 220, one or more slices, such as sub-slices, from the allocated enterprise resource bundle. The enterprise 210 may create the sub-slices via an interface 217, such as an API, service interface, and/or other interface to the network 212. Alternatively, or additionally, the enterprise 210 may send a request to the network operator portal (or API therein) to create the sub-slices 220 within the enterprise resource bundle.

[0036] FIG. 3 depicts an example system 300, in accordance with some example embodiments.

[0037] The assistance information for a user equipment may include the S-NSSAI and, in accordance with some example embodiments, an identifier, such as an enterprise bundle ID (EBID) identifying an enterprises bundle of one or more network slices allocated to an enterprise. In the example of FIG. 3, the user equipment (UE) 150A may have assistance information including S-NSSAI #1 312A and EBID 1 314A. User equipment 150B may have assistance information including S-NSSAI #1 312B and EBID 2 314B, while user equipment 150C may have assistance information including S-NSSAI #2 312C and EBID 2 314B. [0038] The user equipment 150A may indicate, to the network (e.g., a node associated with a network operator such as a base station or access point) slice assistance information (e.g., S-NSSAI #1 312A). The slice assistance information may further include an identifier, such as the enterprise bundle ID (EBID 1 314A), which can enable the network to direct the user equipment towards a network slice bundle allocated to an enterprise. For example, the enterprise bundle ID (EBID) may be used to identify the network slice(s) allocated by the network operator to the enterprise. In the example of FIG. 3, UE 150A indicates to S-NSSAI#l 312A and EBID

1 314A. The S-NSSAI#l 312A and EBID 1 314A enable the network, such as the RAN 152A, to direct the UE 150A to enterprise A’s network bundle slice 350A. FIG. 3 also shows UE 150B and UE 150C indicating assistance information and, in particular, the enterprise bundle ID (EBID

2 314B), so UE 150A-B are directed to enterprise B’s bundle of network slices 350B. As noted, the enterprise bundle ID identifies the enterprises bundle of slices. To differentiate further, the network may use the SST and/or SD to further route to the network slices/sub-slices within the allocated enterprise resource bundle of slices. Thus, the EBID may identify the enterprise and the corresponding at least one slice, which may have one or more sub-slices.

[0039] In the example of FIG. 3, the EBID is used by the network as a filter to route the traffic to the appropriate allocated network bundle for the enterprise, and then further routing may be based on Slice/Service Type (SST) and/or the Slice Differentiator (SD) in accordance with the enterprise’s application and service level agreement needs. The initial routing of the user equipment may, as noted, be based on the enterprise bundle ID (e.g., EBID 1 314A for UE 150A and EBID 2 314B for UEs 150A and B). After the initial routing of UE 150A to the network slice allocated to enterprise A 350A, the RAN 152A may further route based on the SST and/or SD. Likewise, UE 150B is initially routed, at the RAN, based on the EBID 2 314B to the enterprise bundle slice allocated to enterprise B 350B, and then any further routing may be based on the SST and/or SD. In the case of the enterprise B bundle 350B, it has two sub-slices 269A and 269B. The RAN can route towards each slice based on the S-NSSAI. Specifically, the RAN 150B may route UE 2 to the first sub-slice 269A based on the S-NSSAI #1, while routing UE 3 to the second sub-slice based on the S-NSSAI #2. In the example of FIG. 3, the sub-slice 269A is of a certain type to support eMBB, while the sub-slice 269 is of a certain type for supporting EIRECC; these types are merely examples as other types of sub-slices may be implemented as well.

[0040] In some example embodiments, the radio access network (RAN), such as a base station or access point, may provide the enterprise bundle ID (EBID) in system information block (SIB) to the UEs. For example, RAN 152A and/or 152B may provide, as part of the SIB, the available EBIDs, such as EBID 1 314A and/or 314B, to the UEs 150A-C. Although the EBID may be provided in a SIB to the UE, the EBID (or other like identifier) may be provided to the UE in other messages as well. For example, the UE Routing Selection policy (URSP, which provides policy for outgoing UE traffic) may be used to provide the EBID to the UE. For example, during a configuration update, the network (e.g., PCF, AMF, and/or RAN) may provide to the UE a configuration update including the URSP having the EBID. Alternatively or additionally, the EBID may be pre-configured in the UE. Alternatively or additionally, the EBID may be provided to the UE by an over-the-top-application, web service, cloud server, and/or the like. Alternatively or additionally, the EBID may be configured in the UE as part of registration acceptance procedure or service acceptance procedure.

[0041] At 362A, the UE 150A may provide, to the network, the enterprise bundle ID (EBID) in a message, such as a radio resource control (RRC) message, in accordance with some example embodiments. For example, the UE 150A may, at 362A, send a RRC message including the EBID 1 314A (as well as other network slice assistance information) to the RAN 152A.

[0042] In some example embodiments, selection of network functions (NFs) may be performed based at least in part on an identifier, such as the EBID, that indicates the network slice bundle allocated to an enterprise. For example, the network may perform selection of the AMF and/or other network functions including 5G core (5GC) network functions, such as the SMF, UPF, and/or the like. For example, the EBID 1 314A may enable the RAN 152A to select the AMF 154A while EBID 2 314B may enable the RAN 152B to select AMF 154B, other appropriate network slice specific NFs, such as an SMF, UPF, and/or the like may be selected as well based at least in part on the EBID. The network function selection may be based at least in part on EBID, as noted, and may be performed initially during connection setup and/or before routing, using the S-NSSAI, is performed within the slice/sub-slices of the enterprise’s bundle.

[0043] FIG. 4A depicts an example of a signaling diagram 400, in accordance with some example embodiments. The signaling diagram includes the UE 150A, the RAN 152A, the AMF 154A, the UDM 178, the NSSF 164 (or, e.g., 176), and the network repository function (NRF) 492.

[0044] The UE 150A may be configured with network slice assistance information including an identifier (e.g., an EBID) as well as the S-NSSAI, in accordance with some example embodiments.

[0045] In some example embodiments, the UE, such as UE 150A, may receive, at 410, one or more identifiers, such as the EBID indicating the network slices allocated to an enterprise, from the network, in accordance with some example embodiments. For example, the RAN 152A may provide to the UE 150A at least one identifier, such as an EBID, in accordance with some example embodiments. The identifier may be included in a system information block (SIB), although as noted above the UE may obtain an identifier, such as the EBID in other ways as well.

[0046] In some example, embodiments, the SIB may include the EBIDs to which the UE is subscribed to (as noted in the UE’s subscriber information in the network). Alternatively or additionally, the SIB may include the EBIDs to which the UE is forbidden (or prohibited access) may also be included in the SIB. [0047] During connection setup 412, the UE 150A may send, at 414, a connection request, such as an RRC connection request to the RAN 152A. The RAN 152A may respond, at 416, with, for example, an RRC connection setup response. At 416, the UE 150A may send, to the RAN 152A in a message such as a connection setup message, an identifier, such as the EBID, along with other information such as the S-NSAAI information (e.g., SST and SD), in accordance with some example embodiments. Although the previous example refers to the use of RRC messages to provide the EBID, the EBID may be provided at other times and/or in other types of signaling (e.g., NAS signaling messages).

[0048] The RAN 152A may use the enterprise bundle ID provided by the UE to select the appropriate NF, such as an AMF based on enterprise bundle ID. At 420, the RAN 152A may perform network function (NF) selection based at least in part on the at least one identifier (e.g., EBID) that identifies the at least one network slice, or sub-slice, associated with the enterprise’s bundle. For example, the RAN 152A may perform AMF selection, so that an appropriate AMF can be selected for the slice/sub-slice of enterprise resource bundle 350A. In the FIG. 3 example, the EBID1, SST#l, and SD#2 may cause the selection of AM 154A, for example, while EBID 2 may cause selection of AMF 154B.

[0049] The AMF 154A may then check the subscription data from the UDM for the UE and with the help of NSSF and NRF, and the AMF 154A may select the appropriate 5GC NF instances based on the enterprise bundle ID (as well as other information including network slice assistance information). To that end, the RAN 152 may, at 425 A, send to the AMF 154A a registration request including the slice assistance information, such as the requested EBID, and NSSAI (e.g., SST and SD information) for a given slice/sub-slice in the bundle 350A. This may enable the AMF to check, at 425B, the subscription data by sending a request for subscription information to the UDM 178 for the UE 150A. At 425C, the AMF may receive from the UDM 178 the requested subscription information, such as a list of the subscribed EBIDs the UE is allowed (or not allowed) to access as well as other information including other assistance information such as the subscribed S-NSSAI. As used herein, the requested EBID(s) may refer to the EBID(s) provided by the UE during the registration request, while the subscribed EBID(s) refers to what the subscription information includes (or indicates) for the UE in the current PLMN and enterprise.

[0050] At 425D, the AMF 154 A may send to the NSSF 164 the EBIDs, requested NSSAI, subscribed NSSAI, PLMN ID of the UE, and/or the like. At 425E, the NSSF may, at this point, check the request based on policy such as the enterprise policy (e.g., policy indicating what the enterprise is allowed to create or use in the enterprise bundle), business policy, and/or operator policy. And then the NSSF 164 may respond, at 425E, with a NS-ID (network slice-identifier), allowed NSSAI for this enterprise (EBID) (e.g., which EBIDs are allowed or selected to be used), and the candidate AMFs which may be selected for this EBID. The NS-ID may be provided, as noted by the NSSF, and may map to the slice assistance information, such as the S-NSSAI and EBID. The NSSF may reject the request received at 425D if policy associated with the enterprise bundle slice does not comply with the request from the UE. At 425F, the AMF may then use the NS-ID to send a request to the NRF 492 to retrieve any other candidate network functions (NFs) for the EBID, which may be used with the selected/allowed network slice(s) bundle. Based on the bundle of slices available to the enterprise and the S-NSSAI requested, a NRF may provide, at 425G, to the AMF candidate NFs, such as the SMF and/or UPF, for the EBID indicated in 425F. The NRF may thus respond back to the AMF with the optimum NFs for this EBID. At 425H, the AMF may send a message accepting the registration request received at 425A (or a rejection may be sent as well as noted the NSSF rejects the request). At 4251, the RAN responds to the UE with a registration success message (or a registration rejected as well if for example the NSSF rejects the request). Thus, with the help of NSSF 164 and NRF 492, the AMF may select appropriate 5GC NF instances, such as SMF, UPF, and/or the like, for the network slice(s) associated with the EBID as well as other information including the SST and/or SD. In this way, the RAN and AMF can select the NF instances for the network slice associated with the EBID, and then routing can proceed to any sub-slices in the network slice.

[0051] In addition, RAN and AMF can use S-NSSAI for routing the UE to the appropriate slice within the enterprise slice based on the SST/SD information. A given network slice or sub-slice may have a certain set of NF instances. These NF instances may be selected using the S-NSSAI and, for example, the EBID (or other like identifier). Moreover, the selection of the NFs such as the AMF and other 5GC NFs may be performed to select the appropriate slice specific NFs based on enterprise bundle ID (EBID) before routing the UE to the sub-slice within the enterprise slice. Moreover, the UE may, as noted, perform network or cell selection based on enterprise bundle ID. For example, the UE may send information including the EBID to the RAN based on provisioned URSP rules and a sequence of information exchange with the AMF so that the AMF can assign the UE to a network slice. And, the access to a network slice or sub- slice associated with a given enterprise may be blocked for certain UE that are not configured with the appropriate identifier (e.g., the EBID) to access the enterprise slice/sub-slice.

[0052] FIG. 4B depicts an example of a process flow, in accordance with some example embodiments. At 430, a user equipment may obtain an enterprise identifier, such as the EBID, indicating at least one network slice allocated to an enterprise, in accordance with some example embodiments. The enterprise identifier may be obtained from a system information block, from a user equipment routing selection policy (which may be carried by a user equipment configuration update message), a storage device at the apparatus, an over-the-top-application, a web service, and/or a cloud server.

[0053] At 432, the user equipment may send, as part of connection establishment with a radio access network, a message to a radio access network, in accordance with some example embodiments. This message may include the enterprise identifier, such as the EBID, and/or a request for the at least one network slice (or sub-slice) allocated to the enterprise. For example, the request may include a request to be assigned (e.g., mapped to) the slices and/or sub-slices allocated to the enterprise as part of the enterprise bundle identified by the EBID. The request may be an explicit request in the message or implicit in the message. In some example embodiments, the message may comprise a radio resource control message, a radio resource control setup complete message, and/or a UE configuration update message. The message may also carry a network slice selection assistance information, such as a slice service/type and/or slice differentiator.

[0054] In some example embodiments, the user equipment obtains, at 430, the enterprise identifier based on subscription information and/or other policy information in the network that indicates whether the user equipment is allowed to access the slice allocated to the enterprise. If the user equipment is not allowed access to the slice allocate to the enterprise, the user equipment may receive a rejection of a connection to the radio access network. This rejection may be based on subscription information, operator policy, enterprise negotiated agreement, and/or the like indicating the apparatus is not allowed use of the network slice identified by the enterprise identifier.

[0055] FIG. 4C depicts an example of a process flow, in accordance with some example embodiments. At 440, a radio access network may receive, from a user equipment, an enterprise identifier, such as an EBID and/or the like, indicating at least one network slice allocated to an enterprise associated with the user equipment, in accordance with some example embodiments. This radio access network may receive, along with the bundle, additional network slice assistance information. The radio access network may receive the enterprise identifier and/or network slice assistance information in a radio resource control message, a radio resource control setup complete message, and/or a configuration update message (e.g., a UE configuration update message). [0056] At 442, the radio access network may select, based on the received enterprise identifier, at least one network function in a core network, in accordance with some example embodiments. The selection of the at least one network function may include selection of an access management function. The selection of the access management function may trigger the radio access network to send, towards the access management function, a registration request including the enterprise identifier and/or a single network slice selection assistance information.

[0057] FIG. 4D depicts an example of a process flow, in accordance with some example embodiments. At 460, the AMF may receive, from a radio access network, a registration request including an enterprise identifier indicating at least one network slice allocated to an enterprise associated with the user equipment and network slice selection assistance information, in accordance with some example embodiments. At 462, the AMF may receive, based on the enterprise identifier, subscription information for the user equipment. The received subscription information may be received in response to request sent to the UDM, which responds with at least the EBID(s) and other network slice assistance information for the user equipment. At 464, the AMF may select, based on the subscription information, at least one network function in the core network, in accordance with some example embodiments. For example, a network slice bundle (including the slices or sub-slices therein) may have a set of network function instances, such as an AMF, USMF, UPF, and/or the like in order to provide that slice (or sub-slice). The AMF may, based on the EBID and other network assistance information, select those network function instances to enable the subsequent routing of the EIE’s traffic via the slice.

[0058] FIG. 5 depicts a block diagram of a network node 500, in accordance with some example embodiments. The network node 500 may be configured to provide one or more network side operations as described with respect to FIGs. 1-4, for example. Moreover, a mobile wireless network may have a plurality of the network nodes 500 as well. For example, the network node may be incorporated into one or more of the devices 152-180. [0059] The network node 500 may include a network interface 502, a processor 520, and a memory 504, in accordance with some example embodiments. The network interface 502 may include wired and/or wireless transceivers to enable access other nodes including base stations, devices 152-180, the Internet, and/or other nodes. The memory 504 may comprise volatile and/or non-volatile memory including program code, which when executed by at least one processor 520 provides, among other things, the processes disclosed herein including processes discloses with respect to FIGs. 1-4A-4D.

[0060] FIG. 6 illustrates a block diagram of an apparatus 10, in accordance with some example embodiments.

[0061] The apparatus 10 may represent a user equipment, such as the user equipment 150A. The apparatus 10, or portions therein, may be implemented in other network nodes including base stations/WLAN access points as well as the other network nodes (e.g., devices 152-184).

[0062] The apparatus 10 may include at least one antenna 12 in communication with a transmitter 14 and a receiver 16. Alternatively transmit and receive antennas may be separate. The apparatus 10 may also include a processor 20 configured to provide signals to and receive signals from the transmitter and receiver, respectively, and to control the functioning of the apparatus. Processor 20 may be configured to control the functioning of the transmitter and receiver by effecting control signaling via electrical leads to the transmitter and receiver. Likewise, processor 20 may be configured to control other elements of apparatus 10 by effecting control signaling via electrical leads connecting processor 20 to the other elements, such as a display or a memory. The processor 20 may, for example, be embodied in a variety of ways including circuitry, at least one processing core, one or more microprocessors with accompanying digital signal processor(s), one or more processor(s) without an accompanying digital signal processor, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuitry, one or more computers, various other processing elements including integrated circuits (for example, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and/or the like), or some combination thereof. Accordingly, although illustrated in FIG. 6 as a single processor, in some example embodiments the processor 20 may comprise a plurality of processors or processing cores.

[0063] The apparatus 10 may be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like. Signals sent and received by the processor 20 may include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireline or wireless networking techniques, comprising but not limited to Wi-Fi, wireless local access network (WLAN) techniques, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, ADSL, DOCSIS, and/or the like. In addition, these signals may include speech data, user generated data, user requested data, and/or the like.

[0064] For example, the apparatus 10 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 (for example, session initiation protocol (SIP) and/or the like. For example, the apparatus 10 may be capable of operating in accordance with 2G wireless communication protocols IS-136, Time Division Multiple Access TDMA, Global System for Mobile communications, GSM, IS-95, Code Division Multiple Access, CDMA, and/or the like. In addition, for example, the apparatus 10 may be capable of operating in accordance with 2.5G wireless communication protocols General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), and/or the like. Further, for example, the apparatus 10 may be capable of operating in accordance with 3G wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), and/or the like. The apparatus 10 may be additionally capable of operating in accordance with 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and/or the like. Additionally, for example, the apparatus 10 may be capable of operating in accordance with 4G wireless communication protocols, such as LTE Advanced, 5G, and/or the like as well as similar wireless communication protocols that may be subsequently developed.

[0065] It is understood that the processor 20 may include circuitry for implementing audio/video and logic functions of apparatus 10. For example, the processor 20 may comprise a digital signal processor device, a microprocessor device, an analog-to-digital converter, a digital- to-analog converter, and/or the like. Control and signal processing functions of the apparatus 10 may be allocated between these devices according to their respective capabilities. The processor 20 may additionally comprise an internal voice coder (VC) 20a, an internal data modem (DM) 20b, and/or the like. Further, the processor 20 may include functionality to operate one or more software programs, which may be stored in memory. In general, processor 20 and stored software instructions may be configured to cause apparatus 10 to perform actions. For example, processor 20 may be capable of operating a connectivity program, such as a web browser. The connectivity program may allow the apparatus 10 to transmit and receive web content, such as location-based content, according to a protocol, such as wireless application protocol, WAP, hypertext transfer protocol, HTTP, and/or the like.

[0066] Apparatus 10 may also comprise a user interface including, for example, an earphone or speaker 24, a ringer 22, a microphone 26, a display 28, a user input interface, and/or the like, which may be operationally coupled to the processor 20. The display 28 may, as noted above, include a touch sensitive display, where a user may touch and/or gesture to make selections, enter values, and/or the like. The processor 20 may also include user interface circuitry configured to control at least some functions of one or more elements of the user interface, such as the speaker 24, the ringer 22, the microphone 26, the display 28, and/or the like. The processor 20 and/or user interface circuitry comprising the processor 20 may be configured to control one or more functions of one or more elements of the user interface through computer program instructions, for example, software and/or firmware, stored on a memory accessible to the processor 20, for example, volatile memory 40, non-volatile memory 42, and/or the like. The apparatus 10 may include a battery for powering various circuits related to the mobile terminal, for example, a circuit to provide mechanical vibration as a detectable output. The user input interface may comprise devices allowing the apparatus 20 to receive data, such as a keypad 30 (which can be a virtual keyboard presented on display 28 or an externally coupled keyboard) and/or other input devices.

[0067] As shown in FIG. 6, apparatus 10 may also include one or more mechanisms for sharing and/or obtaining data. For example, the apparatus 10 may include a short-range radio frequency (RF) transceiver and/or interrogator 64, so data may be shared with and/or obtained from electronic devices in accordance with RF techniques. The apparatus 10 may include other short-range transceivers, such as an infrared (IR) transceiver 66, a BluetoothTM (BT) transceiver 68 operating using Bluetooth™ wireless technology, a wireless universal serial bus (USB) transceiver 70, a Bluetooth™ Low Energy transceiver, a ZigBee transceiver, an ANT transceiver, a cellular device-to-device transceiver, a wireless local area link transceiver, and/or any other short-range radio technology. Apparatus 10 and, in particular, the short-range transceiver may be capable of transmitting data to and/or receiving data from electronic devices within the proximity of the apparatus, such as within 10 meters, for example. The apparatus 10 including the Wi-Fi or wireless local area networking modem may also be capable of transmitting and/or receiving data from electronic devices according to various wireless networking techniques, including 6LoWpan, Wi-Fi, Wi-Fi low power, WLAN techniques such as IEEE 802.11 techniques, IEEE 802.15 techniques, IEEE 802.16 techniques, and/or the like.

[0068] The apparatus 10 may comprise memory, such as a subscriber identity module (SIM) 38, a removable user identity module (R-UIM), an eUICC, an UICC, and/or the like, which may store information elements related to a mobile subscriber. In addition to the SIM, the apparatus 10 may include other removable and/or fixed memory. The apparatus 10 may include volatile memory 40 and/or non-volatile memory 42. For example, volatile memory 40 may include Random Access Memory (RAM) including dynamic and/or static RAM, on-chip or off- chip cache memory, and/or the like. Non-volatile memory 42, which may be embedded and/or removable, may include, for example, read-only memory, flash memory, magnetic storage devices, for example, hard disks, floppy disk drives, magnetic tape, optical disc drives and/or media, non-volatile random access memory (NVRAM), and/or the like. Like volatile memory 40, non-volatile memory 42 may include a cache area for temporary storage of data. At least part of the volatile and/or non-volatile memory may be embedded in processor 20. The memories may store one or more software programs, instructions, pieces of information, data, and/or the like which may be used by the apparatus for performing operations disclosed herein. Alternatively or additionally, the apparatus may be configured to cause the operations disclosed herein with respect to the base stations/WLAN access points and network nodes including the UEs.

[0069] The memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying apparatus 10. The memories may comprise an identifier, such as an international mobile equipment identification (IMEI) code, capable of uniquely identifying apparatus 10. In the example embodiment, the processor 20 may be configured using computer code stored at memory 40 and/or 42 to the provide operations disclosed herein with respect to the base stations/WLAN access points and network nodes including the UEs.

[0070] Some of the embodiments disclosed herein may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and/or hardware may reside on memory 40, the control apparatus 20, or electronic components, for example. In some example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a“computer-readable medium” may be any non- transitory media 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 circuitry, with examples depicted at FIG. 6, computer-readable medium may comprise a non-transitory computer-readable storage medium that may be any media that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

[0071] Without in any way limiting the scope, interpretation, or application of the claims appearing below, a technical effect of one or more of the example embodiments disclosed herein may be improved network slicing.

[0072] The subject matter described herein may be embodied in systems, apparatus, methods, and/or articles depending on the desired configuration. For example, the base stations and user equipment (or one or more components therein) and/or the processes described herein can be implemented using one or more of the following: a processor executing program code, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), an embedded processor, a field programmable gate array (FPGA), and/or combinations thereof. These various implementations may include implementation in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device. These computer programs (also known as programs, software, software applications, applications, components, program code, or code) include machine instructions for a programmable processor, and may be implemented in a high-level procedural and/or object- oriented programming language, and/or in assembly/machine language. As used herein, the term “computer-readable medium” refers to any computer program product, machine-readable medium, computer-readable storage medium, apparatus and/or device (for example, magnetic discs, optical disks, memory, Programmable Logic Devices (PLDs)) used to provide machine instructions and/or data to a programmable processor, including a machine-readable medium that receives machine instructions. Similarly, systems are also described herein that may include a processor and a memory coupled to the processor. The memory may include one or more programs that cause the processor to perform one or more of the operations described herein.

[0073] Although a few variations have been described in detail above, other modifications or additions are possible. In particular, further features and/or variations may be provided in addition to those set forth herein. Moreover, the implementations described above may be directed to various combinations and subcombinations of the disclosed features and/or combinations and subcombinations of several further features disclosed above. Other embodiments may be within the scope of the following claims.

[0074] If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined. Although various aspects of some of the embodiments are set out in the independent claims, other aspects of some of the embodiments comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims. It is also noted herein that while the above describes example embodiments, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications that may be made without departing from the scope of some of the embodiments as defined in the appended claims. Other embodiments may be within the scope of the following claims. The term“based on” includes“based on at least.” The use of the phase“such as” means“such as for example” unless otherwise indicated.

Claims

WHAT IS CLAIMED

1. 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 to at least:

obtain an enterprise identifier indicating at least one network slice allocated to an enterprise; and

send, as part of connection establishment with a radio access network, a message to a radio access network, the message including the enterprise identifier and/or a request for the at least one network slice allocated to the enterprise.

2. The apparatus of claim 1, wherein the enterprise identifier is an enterprise bundle identifier indicating the at least one network slice allocated to the enterprise by the network.

3. The apparatus of any of claims 1-2, wherein the enterprise identifier is obtained from a system information block, from a user equipment routing selection policy carried by a user equipment configuration update message, a storage device at the apparatus, an over-the- top-application, a web service, and/or a cloud server.

4. The apparatus of any of claims 1-3, wherein the message comprises a radio resource control message, a radio resource control setup complete message, and/or a configuration update message.

5. The apparatus of any of claims 1-4, wherein the message further includes a single network slice selection assistance information including a slice service/type and/or slice differentiator.

6. The apparatus of any of claims 1-5, wherein the apparatus is further caused to at least obtain, from the radio access network, the enterprise identifier based on subscription information, enterprise policy agreement, and/or operator policy associated with the apparatus.

7. The apparatus of any of claims 1-6, wherein in response to the message being sent, the apparatus is further caused to at least receive a rejection of a connection to the radio access network, the rejection based on subscription information and/or other policy indicating the apparatus is not allowed use of the at least one network slice identified by the enterprise identifier.

8. The apparatus of any of claims 1-7, wherein the at least one network slice comprises a bundle including at least one sub-slice.

9. The apparatus of claim 8, wherein the at least one network slice is allocated by the network to the enterprise based on a request from the enterprise, and wherein the enterprise creates or requests creation of the at least one sub-slice within the bundle.

10. An apparatus comprising:

at least one processor; and

receive, from a user equipment, an enterprise identifier indicating at least one network slice allocated to an enterprise associated with the user equipment; and

select, based on the enterprise identifier, at least one network function in a core network.

11. The apparatus of claim 10, wherein the enterprise identifier is an enterprise bundle identifier indicating at least one network slice allocated to the enterprise by the network.

12. The apparatus of any of claims 10-11, wherein the enterprise identifier is received in a radio resource control message, a radio resource control setup complete message, and/or a configuration update message.

13. The apparatus of any of claims 10-12, wherein the selection of the at least one network function comprises selection of an access management function.

14. The apparatus of claim 13, wherein the selection of the access management function further comprises:

sending, towards the access management function, a registration request including the identifier and/or a single network slice selection assistance information.

15. The apparatus of any of claims 10-14, wherein the apparatus is further configured to at least receive a registration accept indicating an allowed at least one network slice and/or sub-slice allocated to the enterprise, the allowed at least one network slice and/or sub-slice based on policy at a network slice selection function and/or network repository function.

16. An apparatus comprising:

at least one processor; and

receive, from a radio access network, a registration request including an enterprise identifier indicating at least one network slice allocated to an enterprise associated with the user equipment and network slice selection assistance information; receive subscription information for the user equipment; and

select, based on the subscription information, at least one network function in the core network.

17. The apparatus of claim 16, wherein the selection includes a selection, based on the enterprise identifier, of a session management function instance, user plane function instance, and/or an access management function instance.

18. The apparatus of any of claims 16-17, wherein the selected at least one network function includes a selection, based on the enterprise identifier, of a session management function instance, user plane function instance, and/or an access management function instance.

19. The apparatus of claim 18, wherein the apparatus is further caused to at least send,

towards the radio access network, a registration accept message indicating whether the at least one network slice identified by the enterprise identifier is allowed for use by the user equipment.

20. The apparatus of any of claims 16-19, wherein the apparatus is further configured to at least select the at least one network function, for the at least one slice allocated to the enterprise, based on policy from a network slice selection function and/or network repository function.

21. A method comprising:

obtaining an enterprise identifier indicating at least one network slice allocated to an enterprise; and

sending, as part of connection establishment with a radio access network, a message to a radio access network, the message including the enterprise identifier and/or a request for the at least one network slice allocated to the enterprise.

22. The method of claim 21, wherein the enterprise identifier is an enterprise bundle identifier indicating the at least one network slice allocated to the enterprise by the network.

23. The method of any of claims 21-22, wherein the enterprise identifier is obtained from a system information block, from a user equipment routing selection policy carried by a user equipment configuration update message, a storage device at the apparatus, an over-the- top-application, a web service, and/or a cloud server.

24. The method of any of claims 21-23, wherein the message comprises a radio resource control message, a radio resource control setup complete message, and/or a configuration update message.

25. The method of any of claims 21-24, wherein the message further includes a single network slice selection assistance information including a slice service/type and/or slice differentiator.

26. The method of any of claims 21-25, further comprising:

obtaining, from the radio access network, the enterprise identifier based on subscription information, enterprise policy agreement, and/or operator policy associated with the apparatus.

27. The method of any of claims 21-26, further comprising:

in response to the message being sent, receiving a rejection of a connection to the radio access network, the rejection based on subscription information and/or other policy indicating the apparatus is not allowed use of the at least one network slice identified by the enterprise identifier.

28. The method of any of claims 21-27, wherein the at least one network slice comprises a bundle including at least one sub-slice.

29. The method of claim 28, wherein the at least one network slice is allocated by the network to the enterprise based on a request from the enterprise, and wherein the enterprise creates or requests creation of the at least one sub-slice within the bundle.

30. A method comprising:

receiving, from a user equipment, an enterprise identifier indicating at least one network slice allocated to an enterprise associated with the user equipment; and selecting, based on the enterprise identifier, at least one network function in a core network.

31. The method of claim 30, wherein the enterprise identifier is an enterprise bundle identifier indicating at least one network slice allocated to the enterprise by the network.

32. The method of any of claims 30-31, wherein the enterprise identifier is received in a radio resource control message, a radio resource control setup complete message, and/or a configuration update message.

33. The method of any of claims 30-32, wherein the selection of the at least one network function comprises selection of an access management function.

34. The method of claim 33, wherein the selecting further comprises sending, towards the access management function, a registration request including the identifier and/or a single network slice selection assistance information.

35. The method of any of claims 30-34, further comprising:

receiving a registration accept indicating an allowed at least one network slice and/or sub-slice allocated to the enterprise, the allowed at least one network slice and/or sub-slice based on policy at a network slice selection function and/or network repository function.

36. A method comprising:

receiving, from a radio access network, a registration request including an enterprise identifier indicating at least one network slice allocated to an enterprise associated with the user equipment and network slice selection assistance information; receiving subscription information for the user equipment; and

selecting, based on the subscription information, at least one network function in the core network.

37. The method of claim 36, wherein the selection includes a selection, based on the enterprise identifier, of a session management function instance, user plane function instance, and/or an access management function instance.

38. The method of any of claims 36-37, wherein the selected at least one network function includes a selection, based on the enterprise identifier, of a session management function instance, user plane function instance, and/or an access management function instance.

39. The method of claim 38, further comprising:

sending, towards the radio access network, a registration accept message indicating whether the at least one network slice identified by the enterprise identifier is allowed for use by the user equipment.

40. The method of any of claims 36-39, further comprising:

selecting the at least one network function, for the at least one slice allocated to the enterprise, based on policy from a network slice selection function and/or network repository function.

41. An apparatus comprising:

means for obtaining an enterprise identifier indicating at least one network slice allocated to an enterprise; and

means for sending, as part of connection establishment with a radio access network, a message to a radio access network, the message including the enterprise identifier and/or a request for the at least one network slice allocated to the enterprise.

42. The apparatus of claim 41 further comprising means for performing any of claims 22-29.

43. An apparatus comprising:

means for receiving, from a user equipment, an enterprise identifier indicating at least one network slice allocated to an enterprise associated with the user equipment; and means for selecting, based on the enterprise identifier, at least one network function in a core network.

44. The apparatus of claim 43 further comprising means for performing any of claims 31-35.

45. An apparatus comprising:

means for receiving, from a radio access network, a registration request including an enterprise identifier indicating at least one network slice allocated to an enterprise associated with the user equipment and network slice selection assistance information; means for receiving subscription information for the user equipment; and means for selecting, based on the subscription information, at least one network function in the core network.

46. The apparatus of claim 45 further comprising means for performing any of claims 37-40.

47. A non-transitory computer-readable storage medium including program code which when executed by at least one processor causes operations comprising:

48. A non-transitory computer-readable storage medium including program code which when executed by at least one processor causes operations comprising:

receiving, from a user equipment, an enterprise identifier indicating at least one network slice allocated to an enterprise associated with the user equipment; and

selecting, based on the enterprise identifier, at least one network function in a core network.

49. A non-transitory computer-readable storage medium including program code which when executed by at least one processor causes operations comprising: