Method of isolating group selection during slice provision

Abstract

There is provided an apparatus (202, 302) comprising: means for receiving a request to create or update a network slice, where the request comprises a selection list; means for determining an isolation group using the selection list; and means for providing a network slice instance for the network slice request wherein the determined isolation group is associated with the network slice instance.

Description

Technical Field

[0001] The present application relates to a method, apparatus, system and computer program, and in particular, but not exclusively, to an apparatus, method and computer program for isolation group selection during slice provisioning. Background Art

[0002] A communication system can be viewed as a facility that enables communication sessions between two or more entities (such as user terminals, base stations, and / or other nodes) by providing carrier waves between the various entities involved in the communication path. For example, a communication system can be provided by means of a communication network and one or more compatible communication devices. A communication session can include, for example, data communications for carrying communications such as voice, video, electronic mail (email), text messages, multimedia, and / or content data. Non-limiting examples of the services provided include two-way or multi-way calls, data communications or multimedia services, and access to data network systems (such as the Internet). In a wireless communication system, at least a portion of a communication session between at least two stations is conducted over a wireless link. Examples of wireless systems include public land mobile networks (PLMNs), satellite-based communication systems, and various wireless local area networks, such as wireless local area networks (WLANs). Some wireless systems can be divided into cells and are therefore often referred to as cellular systems.

[0003] A user may access the communication system through an appropriate communication device or terminal. The user's communication device may be referred to as user equipment (UE) or user device.

[0004] Communication systems and associated equipment typically operate in accordance with a given standard or specification that specifies what the various entities associated with the system are allowed to do and how this is achieved. Communication protocols and / or parameters for connections are also typically defined. One example of a communication system is UTRAN (3G radio). Other examples of communication systems include the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio access technology and so-called 5G or New Radio (NR) networks. NR is being standardized by the 3rd Generation Partnership Project (3GPP).

[0005] A feature of modern communication systems is called network slicing. Network slicing is a feature that enables multiplexing virtualized and / or independent logical networks on a physical network infrastructure. Summary of the Invention

[0006] According to a first aspect, a device is disclosed, comprising: a device for receiving a request to create or update a network slice, wherein the request includes a selection list; a device for determining an isolation group using the selection list; and a device for providing a network slice instance for the network slice request, wherein the determined isolation group is associated with the network slice instance.

[0007] According to some examples, the selection list includes ranges that the slice consumer can specify to determine the isolation group.

[0008] According to some examples, the slice consumer may specify a range including at least one isolation selection type and at least one isolation selection value. For example, the type indicated by the isolation selection type may include at least one of the following: group type; group name; group type identifier; identifier; isolation level. For example, the isolation selection value may indicate a value corresponding to the type specified in the isolation selection type.

[0009] According to some examples, the apparatus comprises means for checking an isolated selection type and an isolated selection value of at least one of the first item and the second item in the selection list.

[0010] According to some examples, the device includes means for preconfiguring isolation groups in the device.

[0011] According to some examples, means for pre-configuring the isolation group in the device includes means for creating the isolation group in the device based on information from a network operator.

[0012] According to some examples, the apparatus includes means for allocating resources to the network slice instance based on the isolation profile of the determined isolation group. For example, resources may be allocated to one or more of: management data; resources.

[0013] According to some examples, the means for determining the isolation group includes means for selecting a preconfigured isolation group or means for creating an isolation group.

[0014] According to some examples, the device for providing the network slice instance includes a device for creating a network slice instance or a device for updating a network slice instance.

[0015] According to some examples, the isolation group includes a set of network slices that have the same isolation requirements for management and managed resources.

[0016] According to some examples, the device also includes: a device for converting the received selection list into a slice profile selection list for at least one of a radio access network (RAN), a core network (CN), and a transport network (TN); a device for transmitting the slice profile selection list to at least one of a RAN network slice subnet provider, a CN network slice subnet provider, and a TN network slice subnet provider, wherein at least one of the RAN network slice subnet provider, the CN network slice subnet provider, and the TN network slice subnet provider uses the received slice profile selection list to determine an isolation group; and a device for receiving information of a network slice subnet instance from at least one of the RAN network slice subnet provider, the CN network slice subnet provider, and the TN network slice subnet provider, wherein the network subnet slice instance is associated with the determined isolation group.

[0017] According to some examples, the device may include a network service provider (NSP); a network slice management service provider (NSMS_P); a network slice subnet provider (NSSP); and a network slice subnet management service provider (NSSMS_P).

[0018] According to some examples, the network slice includes a complete network slice or a network slice subnet.

[0019] According to some examples, the network slice instance includes a network slice instance or a network slice subnet instance.

[0020] According to some examples, the apparatus includes at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code being configured to, together with the at least one processor, cause the device to operate.

[0021] According to a second aspect, a device is provided, comprising at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to at least perform: receiving a request to create or update a network slice, wherein the request comprises a selection list; determining an isolation group using the selection list; and providing a network slice instance for the network slice request, wherein the determined isolation group is associated with the network slice instance.

[0022] According to a third aspect, a device is provided, comprising: a device for transmitting a request to create or update a network slice, wherein the request includes a selection list, and wherein the selection list includes ranges that the device can specify to determine an isolation group, the ranges including at least one isolation selection type and at least one isolation selection value; and a device for receiving information of a network slice instance, wherein the network slice instance is associated with a determined isolation group.

[0023] According to some examples, the type indicated by the isolation selection type may include at least one of the following: group type; group name; group type identifier; identifier; isolation level. According to some examples, the isolation selection value may indicate a value corresponding to the type specified in the isolation selection type.

[0024] According to some examples, the isolation group includes a set of network slices that have the same isolation requirements for management and managed resources.

[0025] According to some examples, the device may include a network slice consumer (NSC); a network slice management service consumer (NSMS_C); a network slice subnet consumer (NSSC); and a network slice subnet management service consumer (NSSMS_C).

[0026] According to some examples, the network slice includes a complete network slice or a network slice subnet.

[0027] According to some examples, the network slice instance includes a network slice instance or a network slice subnet instance.

[0028] According to some examples, the apparatus includes at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, enable the apparatus to perform operations.

[0029] According to a fourth aspect, a device is provided, comprising at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the device to at least perform the following: transmit a request to create or update a network slice, wherein the request includes a selection list, and wherein the selection list includes a range that the device can specify to determine an isolation group, the range including at least one isolation selection type and at least one isolation selection value; and receive information of a network slice instance, wherein the network slice instance is associated with a determined isolation group.

[0030] According to a fifth aspect, a method is provided, comprising: receiving a request to create or update a network slice, wherein the request comprises a selection list; determining an isolation group using the selection list; and providing a network slice instance for the network slice request, wherein the determined isolation group is associated with the network slice instance.

[0031] According to some examples, the selection list includes ranges that the slice consumer can specify to determine the isolation group.

[0032] According to some examples, the slice consumer may specify a range including at least one isolation selection type and at least one isolation selection value. For example, the type indicated by the isolation selection type may include at least one of the following: group type; group name; group type identifier; identifier; isolation level. For example, the isolation selection value may indicate a value corresponding to the type specified in the isolation selection type.

[0033] According to some examples, the method includes checking an isolate selection type and an isolate selection value of at least one of a first item and a second item in the selection list.

[0034] According to some examples, the method includes preconfiguring the isolation group.

[0035] According to some examples, pre-configuring the isolation group includes creating the isolation group based on information from a network operator.

[0036] According to some examples, the method includes allocating resources to the network slice instance based on the isolation profile of the determined isolation group. For example, resources can be allocated for one or more of the following: management data; resources.

[0037] According to some examples, determining the isolation group includes selecting a preconfigured isolation group or creating an isolation group.

[0038] According to some examples, providing a network slice instance includes creating a network slice instance or updating a network slice instance.

[0039] According to some examples, the isolation group includes a set of network slices that have the same isolation requirements for management and managed resources.

[0040] According to some examples, the method also includes: converting the received selection list into a slice profile selection list for at least one of a radio access network (RAN), a core network (CN), and a transport network (TN); transmitting the slice profile selection list to at least one of a RAN network slice subnet provider, a CN network slice subnet provider, and a TN network slice subnet provider, wherein at least one of the RAN network slice subnet provider, the CN network slice subnet provider, and the TN network slice subnet provider uses the received slice profile selection list to determine an isolation group; and receiving information of a network slice subnet instance from at least one of the RAN network slice subnet provider, the CN network slice subnet provider, and the TN network slice subnet provider, wherein the network subnet slice instance is associated with the determined isolation group.

[0041] According to some examples, the network slice includes a complete network slice or a network slice subnet.

[0042] According to some examples, the network slice instance includes a network slice instance or a network slice subnet instance.

[0043] According to a sixth aspect, a method is provided, comprising: transmitting a request to create or update a network slice, wherein the request comprises a selection list, and wherein the selection list comprises a range that can be specified for determining an isolation group, the range comprising at least one isolation selection type and at least one isolation selection value; and receiving information of a network slice instance, wherein the network slice instance is associated with the determined isolation group.

[0044] According to some examples, the type indicated by the isolation selection type may include at least one of the following: group type; group name; group type identifier; identifier; isolation level. According to some examples, the isolation selection value may indicate a value corresponding to the type specified in the isolation selection type.

[0045] According to some examples, the isolation group includes a set of network slices that have the same isolation requirements for management and managed resources.

[0046] According to some examples, the network slice includes a complete network slice or a network slice subnet.

[0047] According to some examples, the network slice instance includes a network slice instance or a network slice subnet instance.

[0048] According to a seventh aspect, a computer program is provided, comprising instructions for causing an apparatus to perform at least the following: receiving a request to create or update a network slice, wherein the request comprises a selection list; determining an isolation group using the selection list; and providing a network slice instance for the network slice request, wherein the determined isolation group is associated with the network slice instance.

[0049] According to an eighth aspect, a computer program is provided, comprising instructions for causing an apparatus to perform at least the following: transmitting a request to create or update a network slice, wherein the request comprises a selection list, and wherein the selection list comprises a range that the apparatus can specify to determine an isolation group, the range comprising at least one isolation selection type and at least one isolation selection value; and receiving information of a network slice instance, wherein the network slice instance is associated with a determined isolation group.

[0050] According to a ninth aspect, a computer program is provided, comprising instructions stored thereon for performing at least the following: receiving a request to create or update a network slice, wherein the request comprises a selection list; determining an isolation group using the selection list; and providing a network slice instance for the network slice request, wherein the determined isolation group is associated with the network slice instance.

[0051] According to a tenth aspect, a computer program is provided, comprising instructions stored thereon for performing at least the following: transmitting a request to create or update a network slice, wherein the request comprises a selection list, and wherein the selection list comprises ranges that the device can specify for determining an isolation group, the ranges comprising at least one isolation selection type and at least one isolation selection value; and receiving information of a network slice instance, wherein the network slice instance is associated with a determined isolation group.

[0052] According to the eleventh aspect, a non-transitory computer-readable medium comprising program instructions is provided, wherein when the program instructions are executed by an apparatus, the apparatus is caused to perform at least the following: receive a request to create or update a network slice, wherein the request comprises a selection list; determine an isolation group using the selection list; and provide a network slice instance for the network slice request, wherein the determined isolation group is associated with the network slice instance.

[0053] According to the twelfth aspect, a non-transitory computer-readable medium comprising program instructions is provided, wherein the program instructions, when executed by an apparatus, cause the apparatus to perform at least the following: transmit a request to create or update a network slice, wherein the request comprises a selection list, and wherein the selection list comprises a range that the apparatus can specify for determining an isolation group, the range comprising at least one isolation selection type and at least one isolation selection value; and receive information of a network slice instance, wherein the network slice instance is associated with a determined isolation group.

[0054] According to a thirteenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions stored thereon for performing at least the following: receiving a request to create or update a network slice, wherein the request comprises a selection list; determining an isolation group using the selection list; and providing a network slice instance for the network slice request, wherein the determined isolation group is associated with the network slice instance.

[0055] According to a fourteenth aspect, a non-transitory computer-readable medium is provided, comprising program instructions stored thereon for performing at least the following: transmitting a request to create or update a network slice, wherein the request comprises a selection list, and wherein the selection list comprises a range that the device can specify for determining an isolation group, the range comprising at least one isolation selection type and at least one isolation selection value; and receiving information of a network slice instance, wherein the network slice instance is associated with a determined isolation group. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Embodiments will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0057] Figure 1 shows a schematic diagram of a 5G system;

[0058] Figure 2 is a signaling diagram according to an example embodiment;

[0059] Figure 3 is a signaling diagram according to an example embodiment;

[0060] FIG4 is a flow chart according to an example embodiment;

[0061] Figure 5 An example isolation group is shown;

[0062] Figure 6 is a signaling diagram according to an example embodiment;

[0063] Figure 7 is a signaling diagram according to an example embodiment;

[0064] Figure 8 is a signaling diagram according to an example embodiment;

[0065] Figure 9 shows a schematic diagram of a control device according to an example embodiment;

[0066] Figure 10 shows a schematic diagram of an apparatus according to an example embodiment;

[0067] Figure 11 is a flowchart of a method according to an example embodiment;

[0068] Figure 12 is a flowchart of a method according to an example embodiment;

[0069] Figure 13 A schematic diagram of a non-volatile storage medium storing instructions that, when executed by a processor, allow the processor to perform one or more steps of the method of some embodiments is shown. DETAILED DESCRIPTION

[0070] In the following, certain embodiments are explained with reference to a mobile communication device capable of communicating via a wireless cellular system and a mobile communication system providing services for such mobile communication devices. Figure 1 Certain general principles of wireless communication systems, their access systems and mobile communication devices are briefly explained to help understanding the technology on which the examples are based.

[0071] Figure 1A schematic diagram of a 5G system (5GS) is shown, which is provided as an example of a communication system. The 5GS may include a terminal or user equipment (UE), a 5G radio access network (5GRAN) or next generation radio access network (NG-RAN), a 5G core network (5GC), one or more application functions (AFs), and one or more data networks.

[0072] The 5G-RAN may include one or more gNodeBs (gNBs) or one or more gNodeB (gNB) distributed unit functions connected to one or more gNodeB (gNB) centralized unit functions.

[0073] The 5GC may include the following entities: network slice selection function (NSSF); network exposure function; network repository function (NRF); policy control function (PCF); unified data management (UDM); application function (AF); authentication server function (AUSF); access and mobility management function (AMF); and session management function (SMF). Figure 1 It also shows various interfaces (N1, N2, etc.) that may be implemented between the various elements of the system.

[0074] Although for the purpose of explanation Figure 1 A 5G system is shown in the figure, but it should be understood that the present application can also be applied to other systems, such as a 4G system.

[0075] As mentioned above, a feature of modern communication systems is called network slicing. A sliced network can include a set of logical networks on top of a shared infrastructure. Each logical network can be designed to serve a specific purpose and can include the required network resources for end-to-end configuration and connection. In some examples, each network slice can be understood as an independent end-to-end network to meet the diverse needs required by specific applications. Each network slice can be managed by a network operator (NOP). The network operator can be a mobile network operator or a virtual mobile network operator. Mobile networks can support network slicing, thereby effectively accommodating a large number of services with very different service level requirements. For example, network slices can be customized based on the requirements in the service level agreement (SLA) agreed between related services, customers, enterprises or vertical industries.

[0076] 3GPP TS28.541 defines the NetworkSlice and NetworkSliceSubnet information object classes (IOCs). The NetworkSlice IOC includes the ServiceProfile data type. This data type represents the attributes of the network slicing related requirements that a network slice instance in a 5G network should support. Network slicing related requirements can be applicable to a one-to-one relationship between a network slice customer (NSC) and a network slice provider (NSP). The ServiceProfile data type can define multiple attributes. Existing attributes include the networkSliceSharingIndicator attribute, which specifies whether an instance of a NetworkSliceInstance object can be shared with other instances. The NetworkSliceSubnet IOC includes the SliceProfile data type, which represents the attributes of the network slicing subnet related requirements that a NetworkSliceSubnet instance in a 5G network should support. NetworkSliceSubnet can be divided into RANSliceSubnet, CNSliceSubnet, and TopSliceSubnet. RANSliceSubnet represents the RAN network slice subnet in the 5G network and is associated with one or more "RANSliceSubnetProfile". CNSliceSubnet represents the CN network slice subnet in the 5G network and is associated with one or more "CNSliceSubnetProfile". TopSliceSubnet represents the top network slice subnet in the 5G network and is associated with one or more "TopSliceSubnetProfile". The SliceProfile data type defines various attributes. The existing resourceSharingLevel attribute defined in CNSliceSubnetProfile, RANSliceSubnetProfile and TopSliceSubnetProfile is described in 3GPPTS28.541, which specifies whether the resources allocated to the network slice can be shared with other network slices.

[0077] In some examples, network slices can be isolated. GSMANG.127 describes isolation as a feature that can be used for network slicing. A network slice instance (NSI) can be completely or partially, logically and / or physically isolated from another network slice instance. Network slicing allows multiple NSIs to be executed simultaneously on top of a common infrastructure, meeting their independent business key performance indicators while ensuring their independence. The use of a single shared infrastructure makes isolation a feature that supports network slicing. In some examples, isolation can be viewed as the ability of a network service provider (NSP) to ensure that congestion, attacks, and lifecycle related events (e.g., scale-up / down) on one NSI do not negatively impact other existing NSIs.

[0078] Network slice isolation can be managed. Network slice isolation can include the isolation of management resources (e.g., data, functions, or services) and managed resources (e.g., data, network functions, infrastructure resources, etc.) across multiple domains (e.g., RAN, core, transport, etc.). In some examples, mobile network operators (MNOs) commercially deploying 5G networks may require isolation at multiple layers (e.g., E2E slices / services, slice subnets, managed functions, etc.) to ensure the expected security level of network slices. Isolation groups can be introduced to aggregate network slices (or other services at various layers) that share the same resources, with or without isolation. Isolation groups can be defined at each resource layer that forms an E2E network slice. For example, isolation groups can be present at the E2E slice layer (grouping resources for network slice services), the network slice subnet (NSS) layer (grouping resources for NSS services), or the managed function (MF) layer (grouping resources for MF services). In some examples, isolation groups can be further defined by characters and characteristics (e.g., tenant, slice / service type (SST), industry, region, IoT device type, etc.). Isolation profiles can be introduced to define the isolation requirements of isolation groups. Each isolation group can be associated with an isolation profile, and the isolation profile includes isolation levels or isolation rules, which will be described in more detail below. The isolation profile may include isolation policies to isolate and protect resources assigned to the isolation group. The isolation profiles and isolation policies in different domains (e.g., E2E, RAN, core, transport, virtualization, etc.) or different layers (e.g., network slices, slice subnets, managed functions, network services, VNFs, etc.) can be different. A service provider / manufacturer, such as a network slice provider (NSP), a network slice subnet provider (NSSP), or a managed function provider (MFP), can create or select isolation groups for network slices (or NSS services, or MF services) and assign the isolation groups to network slices (or NSS services, or MF services).

[0079] GSMA NG.116 (v5.07) defines isolation levels with the following attributes: isolation, physical isolation, and logical isolation. Therefore, these attributes can define the isolation requirements of network slices / network slice instances.

[0080] Table 1 below defines the isolation level attributes and associated allowed values in further detail.

[0081]

[0082] Table 1: Isolation level attributes and associated allowed values

[0083] However, the present application recognizes that the above proposals do not describe a mechanism for a network slice consumer (NSC) to select or indicate isolation requirements when requesting a network slice, such as a network service provider (NSP) selecting an isolation group.

[0084] Some example embodiments described herein introduce a mechanism for extending data types, such as ServiceProfile and SliceProfile data types, with additional attributes that can be used by slice consumers (e.g., NSCs) and service producers (e.g., NSPs) to select isolation groups with appropriate isolation requirements when requesting the creation of network slices. Slice consumers can also use the same attributes to request the association or modification of isolation groups, and therefore request isolation requirements for the created slices. Additional attributes include an IsolationSelectionList, which can be used by slice consumers and service producers to select the desired isolation group. In the example, the IsolationSelectionList is a list with IsolationSelectionType and IsolationSelectionValue attributes, which can be used by slice consumers to specify the combined conditions for selecting an isolation group for the requested network slice. The IsolationSelectionType attribute can indicate a "type". For example, allowed "types" can include groupType, groupName, groupTypeIdentifier, identifier, and IsolationLevel. In the example, the IsolationSelectionValue attribute indicates a "value" corresponding to the "type" specified in the IsolationSelectionType attribute.

[0085] During the network slice lifecycle management process, a slice consumer can transmit a request to create or update a network slice to a service producer. The slice consumer can also provide an IsolationSelectionList attribute in the network slice request, which the service provider can use to identify and / or select an appropriate isolation group. The service provider can create a network slice instance for the requested network slice and associate the network slice instance with the selected isolation group. For example, the service provider can associate the selected isolation group and corresponding isolation requirements with the network slice instance and implement the isolation requirements during network slice creation. The service producer can then transmit the information about the network slice instance to the slice consumer.

[0086] According to some examples, a slice consumer may be a network slice consumer (NSC), a network slice management service consumer (NSMS_C), a network slice subnet consumer (NSSC), or a network slice subnet management service consumer (NSSMS_C). According to some further examples, a service producer may be a network service provider (NSP), a network slice management service provider (NSMS_P), a network slice subnet provider (NSSP), or a network slice subnet management service provider (NSSMS_P). According to some further examples, the term "network slice" may include a complete network slice or a network slice subnet. In some examples, a network slice subnet represents a set of network functions (including their corresponding resources) that form part or all of a network slice. According to some further examples, a network slice instance may include a network slice instance or a network slice subnet instance. In some examples, a network slice subnet instance forms part of the entire network slice instance.

[0087] In some examples, such as Figure 2 As shown, the service consumer is NSC 200 and the service producer is NSP 202 .

[0088] In this example, at S201, NSP 202 receives a request to create or update a network slice from NSC 200. The request may include an IsolationSelectionList.

[0089] At S202, the NSP 202 identifies and / or determines, based on the IsolationSelectionList, an appropriate isolation group for the network slice requested by the NSC 200. For example, determining the isolation group may include selecting and / or creating the isolation group.

[0090] At S203, NSP 202 associates the network slice instance with the selected isolation group. For example, NSP 202 may associate the determined isolation group and the corresponding isolation requirements with the network slice instance and implement the isolation requirements during network slice creation.

[0091] At S204, NSP 202 transmits information of the network slice instance to NSC 200.

[0092] In other examples, such as Figure 3 As shown, the slice consumer can be NSSC 300, and the service producer can be NSSP 302.

[0093] In this example, at S301, NSSP 302 receives a request to create or update a network slice subnet from NSSC 300. The request may include an IsolationSelectionList.

[0094] At S302, NSSP 302 uses IsolationSelectionList to identify and / or determine an appropriate isolation group for the network slice subnet requested by NSSC 300. For example, determining the isolation group may include selecting and / or creating the isolation group.

[0095] At S303, the NSSP 302 associates the network slice subnet instance with the determined isolation group. For example, the NSSP 302 may associate the selected isolation group (and thus the isolation requirement) with the network slice subnet instance and implement the isolation requirement during network slice subnet creation.

[0096] At S304 , NSSP 302 transmits information of the network slice subnet instance to NSSC 300 .

[0097] FIG. 4 illustrates a process by which an NSP identifies and / or determines an isolation group for an NSC based on an IsolationSelectionList.

[0098] At S401 of the process, the NSP receives a request from the NSC to create or update a network slice. In an example, the request includes a service ServiceProfile with attributes. The attributes of the ServiceProfile may include an IsolationSelectionList attribute.

[0099] At S402 , the NSP checks the IsolationSelectionType and IsolationSelectionValue of the first item in the IsolationSelectionList.

[0100] At S403, when IsolationSelectionType is an identifier, IsolationSelectionValue includes the distinguished name (DN) of the isolation group MOI. Then, the NSP searches for the isolation group management object instance (MOI) from the existing isolation group list based on the DN of the MOI.

[0101] At S404, when IsolationSelectionType is groupName, IsolationSelectionValue includes the specific group name of IsolationGroup. Then, NSP searches for the isolation group MOI from the existing isolation group list based on the group name.

[0102] At S405, when IsolationSelectionType is groupType, IsolationSelectionValue includes the specific group type of IsolationGroup.Then, the NSP checks the second item in IsolationSelectionList.

[0103] At S406, when the second item is available and the IsolationSelectionType of the second item in the list is groupTypeIdentifer (group type identifier), the IsolationSelectionValue of the second item includes a specific group type identifier of the isolation group. The NSP then selects the isolation group based on the IsolationSelectionValue of the first and second items in the IsolationSelectionList. The IsolationSelectionValue of the first item may include a tenant, a slice / service type (SST), an NSC, etc. In some examples, the tenant may be a communication service customer (CSC).

[0104] At S407, when the second item is not available and the IsolationSelectionValue of the first item is a tenant, the NSP determines the identity of the NSC from the network slicing request received from the NSC. In some examples, the identity of the NSC can be determined as part of the authentication and authorization process. The NSP determines tenant information, such as a tenant ID, based on the determined NSC identity. The NSP then searches for the isolation group MOI from the existing isolation group list based on the IsolationSelectionValue of the first item (i.e., the tenant) and the tenant information.

[0105] At S408, when the second item is not available and the IsolationSelectionValue of the first item is NSC, the NSP determines the identity of the NSC from the network slicing request received from the NSC, and searches for the isolation group MOI from the existing isolation group list based on the IsolationSelectionValue and NSCid of the first item (i.e., NSC).

[0106] At S409, when the second item is not available and the IsolationSelectionValue of the first item is a single network slice selection (SST), the NSP determines the SST value directly from the ServiceProfile or single network slice selection auxiliary information (S-NSSAI) in the network slice request received from the NSC. The NSP searches for the isolation group operation object (MOI) from the existing isolation group list based on the IsolationSelectionValue of the first item (i.e., SST) and the SST value.

[0107] In some examples, isolation groups can be pre-configured in the NSP. The NSC requesting a network slice from the NSP can specify compound conditions for selecting an isolation group. For example, the NSC can use an IsolationSelectionList to do this. The NSP can then identify and / or select a pre-configured isolation group associated with the requested network slice. In some examples, if the network slice request sent by the NSC to the NSP includes an IsolationSelectionList that specifies a specific IsolationSelectionType and IsolationSelectionValue, the NSP can identify and / or select a pre-configured isolation group with the same characteristics as the received IsolationSelectionType and IsolationSelectionValue.

[0108] Figure 5 Example pre-configured isolation groups 1, 2, 3, and 4 are shown. Figure 5When the NSC sends a network slice request including an IsolationSelectionList to the NSP, and the IsolationSelectionList specifies IsolationSelectionType as "groupName" and IsolationSelectionValue as "Isolation forFactoryAclass1 (A factory isolation category 1)", the NSP can identify IsolationGroup-1 as associated with the requested network slice. In some examples, "FactoryA" can be a communication service customer (CSC) requesting a network slice. For example, the CSC can be a company, etc. Similarly, if the NSP receives an IsolationSelectionList, where the first item in the list specifies IsolationSelectionType as "groupType", IsolationSelectionValue as "Tenant", and the second item in the IsolationSelectionList specifies IsolationSelectionType as "groupTypeIdenitifer" and IsolationSelectionValue as "FactoryA", the NSP can also identify IsolationGroup-1 as associated with the requested network slice.

[0109] However, if, for example, the NSC sends a network slice request to the NSP including an IsolationSelectionList, where the first item in the list specifies IsolationSelectionType as "groupType" and IsolationSelectionValue as "NSC", and the second item in the list specifies IsolationSelectionType as "groupTypeIdentifier" and IsolationSelectionValue as "FactoryA", then the NSP may identify and / or select to associate IsolationGroup-4 with the requested network slice.

[0110] An entity such as a Network Operator (NOP) or an administrator user can create isolation groups in the NSP. Figure 6 A sequence diagram between the NOP 600 and the NSP 602 is shown.

[0111] At S601, NOP 600 creates an isolation group request and transmits the request to NSP 602. For example, the isolation group request may include isolation group attributes and / or may be an MOI isolation group request. In an example, the isolation group request includes one or more attributes. For example, the one or more attributes may include one or more of the following: an IsolationProfile attribute; a groupType attribute; a groupTypeIdentifier attribute; a groupName attribute; or an identifier attribute.

[0112] At S602, the NSP 602 verifies the isolation profile and then creates an isolation group accordingly.

[0113] At S603, NSP 602 creates an isolation group response. NSP 602 then transmits the response to NOP 600. For example, the isolation group response may be a distinguished name (DN) of the isolation group and / or an MOI isolation group response. This process loops until all isolation groups are created in NSP 602.

[0114] NOP can also create isolation groups in NSSP. Figure 7 A sequence diagram between NOP 700 and NSSP 702 is shown.

[0115] At S701, the NOP creates an isolation group request and sends the request to the NSSP 702. For example, the isolation group request may include isolation group attributes and / or may be an MOI isolation group request. In an example, the isolation group request includes one or more attributes. For example, the one or more attributes may include one or more of the following: an IsolationProfile attribute; a groupType attribute; a groupTypeIdentifier attribute; a groupName attribute; or an identifier attribute.

[0116] At S702, NSSP 702 verifies the isolation profile and then creates an isolation group accordingly.

[0117] At S703, NSSP 702 creates an isolation group response. NSSP 702 then transmits the response to NOP 700. For example, the isolation group response may be an MOI isolation group response and / or an isolation group DN. This process repeats until all isolation groups are created in NSSP 702.

[0118] Figure 8A sequence diagram is shown between NSC 800, NSP 802, NSSPRAN 804, NSSPCN 806 and NSSPTN 808. The sequence diagram shows the mechanism for determining the isolation group for the requested network slice, with appropriate isolation requirements.

[0119] At S801, NSC 800 transmits a request to create or update a network slice to NSP 802. The request may include a ServiceProfile data type having an IsolationSelectionList attribute, which enables NSC 800 to specify a complex condition for selecting an isolation group to NSP 802.

[0120] At S802, NSP 802 identifies and / or determines an isolation group having the desired isolation requirements specified in IsolationSelectionList. For example, determining the isolation group may include selecting and / or creating the isolation group.

[0121] At S803, NSP 802 separates the received network slice request into multiple network slice subnet requests according to ServiceProfile. For example, NSP can decompose ServiceProfile into one or more SliceProfiles.

[0122] At S804, NSP 802 converts the IsolationSelectionList included in the network slicing request into SliceProfileIsolationSelectionList. SliceProfileIsolationSelectionList can be used for at least one of the radio access network (RAN), the core network (CN), and the transport network (TN).

[0123] At S805, NSP 802 transmits a request to create or update a network slice subnet (NSS). The network slice subnet request may be transmitted to one or more of RAN network slice subnet provider 804, CN network slice subnet provider 806, and TN network slice subnet provider 808. The request may include one or more of RANSliceProfile, CNSliceProfile, and TNSliceProfile. RANSliceProfile may include an IsolationSelectionList attribute for the RAN network slice subnet (NSS), CNSliceProfile may include an IsolationSelectionList attribute for the CN network slice subnet, and TNSliceProfile may include an IsolationSelectionList attribute for the TN network slice subnet.

[0124] At S806, at least one of RAN NSSP 804, CN NSSP 806, and TN NSSP 808 identifies and / or selects an isolation group. The isolation group may be determined based on the isolation requirements specified in the received IsolationSelectionList. For example, the RAN NSSP may determine the isolation group based on the IsolationSelectionList specified in the RANSliceProfile, and / or the CN NSSP may determine the isolation group based on the IsolationSelectionList specified in the CNSliceProfile, and / or the TN NSSP may determine the isolation group based on the IsolationSelectionList specified in the TNSliceProfile.

[0125] At S807, at least one of the RAN NSSP 804, the CN NSSP 806, and the TN NSSP 808 provides a network slice subnet instance for the network slice subnet request. Providing the network slice subnet instance may include creating and / or updating the network slice subnet instance. For example, the RAN NSSP may provide a network subnet slice instance for the network slice subnet request received at the RAN NSSP, and / or the CN NSSP may provide a network subnet slice instance for the network slice subnet request received at the CN NSSP, and / or the TN NSSP may provide a network subnet slice instance for the network slice subnet request received at the TN NSSP. The selected isolation group may be associated with the network slice subnet instance. For example, the isolation group determined by the RAN NSSP may be associated with the network slice subnet instance provided by the RAN NSSP, and / or the isolation group determined by the CN NSSP may be associated with the network slice subnet instance provided by the CN NSSP, and / or the isolation group determined by the TN NSSP may be associated with the network slice subnet instance provided by the TN NSSP.

[0126] At S808, at least one of the RAN NSSP, the CN NSSP, and the TN NSSP allocates resources for the associated network slice subnet instance. For example, the RAN NSSP may allocate resources for the network slice subnet instance provided by the RAN NSSP, and / or the CN NSSP may allocate resources for the network slice subnet instance provided by the CN NSSP, and / or the TN NSSP may allocate resources for the network slice subnet instance provided by the TN NSSP. According to some examples, resources of the network slice subnet instance are allocated or reused based on the isolation profile of the determined isolation group. Management data of the network slice subnet instance is isolated based on the isolation profile of the determined isolation group.

[0127] At S809, at least one of the RAN NSSP 804, the CN NSSP 806, and the TN NSSP 808 transmits information of the network slice subnet instance to the NSP 802. For example, the RAN NSSP may transmit information of the network slice subnet instance provided by the RAN NSSP, the CN NSSP may transmit information of the network slice subnet instance provided by the CN NSSP, and the TN NSSP may transmit information of the network slice subnet instance provided by the TN NSSP.

[0128] At S810, the NSP 802 provides a network slice instance for the network slice request received from the NSC 800. For example, providing the network slice instance may include creating and / or updating the network slice instance. The NSP 802 then associates the determined isolation group with the network slice instance.

[0129] At S811, NSP 802 allocates resources to the network slice instance. According to some examples, the resources of the network slice instance are allocated or reused based on the isolation profile of the determined isolation group. Management data of the network slice instance is isolated based on the isolation profile of the determined isolation group.

[0130] At S812, NSP 802 transmits information of the network slice instance to NSC 800.

[0131] Figure 9 Shows the control Figure 1 An example of a control device 900 for a 5GRAN or 5GC function is shown. The control device may include at least one random access memory (RAM) 911a, at least one read-only memory (ROM) 911b, at least one processor 912, 913, and an input / output interface 914. The at least one processor 912, 913 may be coupled to the RAM 911a and ROM 911b. The at least one processor 912, 913 may be configured to execute appropriate software code 915. The software code 915 may, for example, enable execution of one or more steps to implement one or more aspects of the present solution. The software code 915 may be stored in ROM 911b. The control device 900 may be interconnected with another control device 900 that controls other 5GRAN or 5GC functions. In some embodiments, each 5GRAN or 5GC function includes a control device 900. In alternative embodiments, two or more 5GRAN or 5GC functions may share a control device.

[0132] Figure 10 An example of a terminal 1000 is shown, such as Figure 1 The terminal 1000 can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include user equipment, a mobile station (MS) or a mobile device (such as a mobile phone or so-called "smartphone"), a computer equipped with a wireless interface card or other wireless interface facilities (e.g., a USB dongle), a personal data assistant (PDA) or tablet equipped with wireless communication capabilities, a machine type communication (MTC) device, an Internet of Things (IoT) type communication device, or any combination thereof. Terminal 1000 can provide, for example, data communication for bearer communication. The communication can be one or more of voice, electronic mail (email), text message, multimedia, data, machine data, etc.

[0133] Terminal 1000 may be equipped with at least one processor 1001, at least one memory (ROM) 1002a, at least one RAM 1002b, and other possible components 1003 for software and hardware assistance in performing the tasks for which it is designed, including controlling access to and communications with access systems and other communication devices. The at least one processor 1001 is coupled to the RAM 1002b and the ROM 1002a. The at least one processor 1001 may be configured to execute appropriate software code 1008. The software code 1008 may, for example, enable the implementation of one or more aspects of the present solution. The software code 1008 may be stored in the ROM 1002a.

[0134] The processor, memory, and other related control devices may be provided on an appropriate circuit board and / or in a chipset. This feature is indicated by reference numeral 1004. The device may optionally have a user interface, such as a keyboard 1005, a touch screen or touchpad, a combination thereof, or the like. Depending on the type of device, one or more displays, speakers, and microphones may optionally be provided.

[0135] The terminal 1000 may receive signals via the air or radio interface 1007 by appropriate receiving means and may transmit signals by appropriate transmitting means. Figure 10 In FIG, the transceiver arrangement is schematically represented by block 1006. The transceiver arrangement 1006 may be provided, for example, by means of a radio component and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

[0136] Figure 11 is a flowchart of a method according to an example. Figure 11 The flowchart is from the perspective of the device. For example, the device may include a network service provider (NSP), a network slice management service provider (NSMS_P), a network slice subnet provider (NSSP), or a network slice subnet management service provider (NSSMS_P).

[0137] As shown in S1101, the method includes receiving a request to create or update a network slice, wherein the request includes a selection list. According to some examples, the term "network slice" can include a complete network slice or a network slice subnet.

[0138] As shown in S1102 , the method includes determining an isolation group using a selection list.

[0139] As shown in S1103, the method includes providing a network slice instance for the network slice request, wherein the determined isolation group is associated with the network slice instance. According to some examples, the network slice instance may include a network slice instance or a network slice subnet instance.

[0140] Figure 12is a flowchart of a method according to an example. Figure 12 The flowchart is from the perspective of the device. For example, the device may include a network slice consumer (NSC), a network slice management service consumer (NSMS_C), a network slice subnet consumer (NSSC), or a network slice subnet management service consumer (NSSMS_C).

[0141] As shown in S1201, the method includes transmitting a request to create or update a network slice, wherein the request includes a selection list, and wherein the selection list includes a range that the device can specify for determining an isolation group, the range including at least one isolation selection type and at least one isolation selection value. According to some examples, the term "network slice" can include a complete network slice or a network slice subnet.

[0142] As shown in S1202, the method includes receiving information of a network slice instance, wherein the network slice instance is associated with a determined isolation group. According to some examples, the network slice instance may include a network slice instance or a network slice subnet instance.

[0143] Figure 13 A schematic diagram of non-volatile storage media 1300a (e.g., a computer compact disc (CD) or digital versatile disc (DVD)) and 1300b (e.g., a universal serial bus (USB) flash drive) storing instructions and / or parameters 1302 that, when executed by a processor, allow the processor to perform Figure 11 and 12 One or more steps of a method.

[0144] It should be understood that the apparatus may include or be coupled to other units or modules for transmitting and / or receiving, such as a radio component or a radio head. Although the apparatus has been described as one entity, the different modules and memories may be implemented in one or more physical or logical entities.

[0145] It is worth noting that although some embodiments have been described with respect to 5G networks, similar principles may be applied with respect to other networks and communication systems. Thus, although certain embodiments have been described above by way of example with reference to certain example architectures of wireless networks, technologies, and standards, the embodiments may be applied to any other suitable form of communication system in addition to the communication system shown and described herein.

[0146] It is also noted herein that while the above describes example embodiments, there are several changes and modifications which may be made to the claimed solution without departing from the scope of the present invention.

[0147] As used herein, “at least one of: ” and “at least one of ” and similar expressions, where a list of two or more elements is linked by “and” or “or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0148] In general, various embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects of the present application may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device, but the present application is not limited thereto. Although various aspects of the present application may be shown and described in block diagrams, flow charts, or using some other graphical representation, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof, as non-limiting examples.

[0149] As used in this application, the term "circuitry" may refer to one or more or all of the following:

[0150] (a) hardware-only circuit implementations (such as implementations in analog and / or digital circuits only); and

[0151] (b) a combination of hardware circuitry and software, such as (where applicable):

[0152] (i) a combination of analog and / or digital hardware circuitry and software / firmware; and

[0153] (ii) any portion of a hardware processor and software (including a digital signal processor), software, and memory that work together to enable a device such as a mobile phone or server to perform its functions); and

[0154] (c) A hardware circuit and / or processor, such as a microprocessor or portion of a microprocessor, that requires software (e.g., firmware) to operate, but the software may not be present when not required to operate.

[0155] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term "circuitry" also covers an implementation of merely a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example, and where applicable to a particular claim element, the term circuitry also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or networking equipment.

[0156] The embodiments of the present application may be implemented by computer software executable by a data processor of a mobile device (such as, in a processor entity), or by hardware, or by a combination of software and hardware. Computer software or programs, also referred to as program products, include software routines, applets and / or macros that can be stored in a data storage medium readable by any device, and they include program instructions for performing specific tasks. A computer program product may include one or more computer executable components that are configured to perform an embodiment when the program is run. The one or more computer executable components may be at least one software code or a portion thereof.

[0157] Also, in this regard, it should be noted that any blocks of the logic flow in the Figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on physical media such as memory chips or memory blocks implemented within a processor, magnetic media such as hard disks or floppy disks, and optical media such as DVDs and their data variants, CDs. Physical media are non-transitory media.

[0158] The term "non-transitory" as used herein is a restriction on the medium itself (ie, tangible, as opposed to a signal), not on the persistence of the data storage (eg, RAM versus ROM).

[0159] The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. The data processor may be of any type suitable for the local technical environment and may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an FPGA, a gate-level circuit, and a processor based on a multi-core processor architecture, as non-limiting examples.

[0160] Embodiments of the present application can be practiced in various components such as integrated circuit modules. The design of integrated circuits is a fundamentally highly automated process. Complex and powerful software tools are available for converting a logic-level design into a semiconductor circuit design that can be etched and formed on a semiconductor substrate.

[0161] The scope of protection sought by various embodiments of the present application is set forth in the independent claims. Embodiments and features described in this specification that do not fall within the scope of the independent claims (if any) should be interpreted as examples that help understand the various embodiments of the present application.

[0162] The foregoing description has provided by way of non-limiting examples a complete and informative description of the exemplary embodiments of the present application. However, various modifications and adaptations will become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. Nevertheless, all such and similar modifications of the teachings of this application will still fall within the scope of the present invention as defined by the appended claims. Indeed, further embodiments are also possible, comprising combinations of one or more embodiments with any other embodiments previously discussed.

Claims

1. A device comprising: means for receiving a request to create or update a network slice, wherein the request includes a selection list; means for determining an isolation group using the selection list; and An apparatus for providing a network slice instance for the network slice request, wherein the determined isolation group is associated with the network slice instance.

2. The device according to claim 1, wherein The selection list includes ranges that a slice consumer can specify to determine the isolation group.

3. The apparatus of claim 2, wherein: The range that the slice consumer can specify includes at least one isolation selection type and at least one isolation selection value.

4. The apparatus according to any one of claims 1 to 3, further comprising: means for checking an isolated selection type and an isolated selection value of at least one of a first item and a second item in said selection list.

5. The apparatus according to any one of claims 1 to 4, further comprising: Means for preconfiguring isolation groups in said device.

6. The apparatus of claim 5, wherein: The means for pre-configuring the isolation group in the device includes means for creating the isolation group in the device based on information from a network operator.

7. The apparatus according to any one of claims 1 to 6, further comprising: Means for allocating resources to a network slice instance based on an isolation profile of the determined isolation group.

8. The apparatus according to any one of claims 1 to 7, wherein The means for determining the isolation group may include means for selecting a preconfigured isolation group or means for creating an isolation group.

9. The apparatus according to any one of claims 1 to 8, wherein The device for providing the network slice instance includes a device for creating a network slice instance or a device for updating a network slice instance.

10. The apparatus according to any one of claims 1 to 9, wherein The isolation group includes a set of network slices that have the same isolation requirements for management and managed resources.

11. The apparatus of claim 1 , further comprising: means for converting the received selection list into a slice profile selection list for at least one of a radio access network (RAN), a core network (CN), and a transport network (TN); means for transmitting the slice profile selection list to at least one of a RAN network slice subnet provider, a CN network slice subnet provider, and a TN network slice subnet provider, wherein at least one of the RAN network slice subnet provider, the CN network slice subnet provider, and the TN network slice subnet provider uses the received slice profile selection list to determine an isolation group; and A device for receiving information of a network slice subnet instance from at least one of the RAN network slice subnet provider, the CN network slice subnet provider and the TN network slice subnet provider, wherein the network subnet slice instance is associated with the determined isolation group.

12. A device comprising: means for transmitting a request to create or update a network slice, wherein the request comprises a selection list, and wherein the selection list comprises ranges that the device may specify for determining an isolation group, the ranges comprising at least one isolation selection type and at least one isolation selection value; and An apparatus for receiving information about a network slice instance, wherein the network slice instance is associated with a determined isolation group.

13. The apparatus of claim 12, wherein: An isolation group consists of a set of network slices that have the same isolation requirements for management and managed resources.

14. A method comprising: Receiving a request to create or update a network slice, wherein the request includes a selection list; Use the selection list to identify the isolation group; and A network slice instance is provided for the network slice request, wherein the determined isolation group is associated with the network slice instance.

15. The method of claim 14, wherein: The selection list includes ranges that the slice consumer can specify for determining isolation groups.

16. The method of claim 15, wherein: The range that the slice consumer can specify includes at least one isolation selection type and at least one isolation selection value.

17. The method of any one of claims 14 to 16, further comprising: An isolate selection type and an isolate selection value of at least one of a first item and a second item in the selection list are checked.

18. The method of any one of claims 14 to 17, further comprising: Preconfigure isolation groups.

19. The method of claim 18, wherein: Preconfiguring isolation groups includes creating isolation groups based on information from a network operator.

20. The method of any one of claims 14 to 19, further comprising: Resources are allocated to the network slice instance based on the isolation profile of the determined isolation group.

21. The method according to any one of claims 14 to 20, wherein Determining the isolation group includes selecting a preconfigured isolation group or creating an isolation group.

22. The method of any one of claims 14 to 21, wherein Providing a network slice instance includes creating a network slice instance or updating a network slice instance.

23. The method of any one of claims 14 to 22, wherein The isolation group includes a set of network slices that have the same isolation requirements for management and managed resources.

24. The method of claim 14, further comprising: converting the received selection list into a slice profile selection list for at least one of a radio access network (RAN), a core network (CN), and a transport network (TN); transmitting the slice profile selection list to at least one of a RAN network slice subnet provider, a CN network slice subnet provider, and a TN network slice subnet provider, wherein at least one of the RAN network slice subnet provider, the CN network slice subnet provider, and the TN network slice subnet provider determines the isolation group using the received slice profile selection list; and Receive information of a network slice subnet instance from at least one of the RAN network slice subnet provider, the CN network slice subnet provider and the TN network slice subnet provider, wherein the network subnet slice instance is associated with the determined isolation group.

25. A method comprising: transmitting a request to create or update a network slice, wherein the request includes a selection list, and wherein the selection list includes a range that can be specified for determining an isolation group, the range including at least one isolation selection type and at least one isolation selection value; and Receive information about a network slice instance, wherein the network slice instance is associated with a determined isolation group.

26. The method of claim 25, wherein: The isolation group includes a set of network slices that have the same isolation requirements for management and managed resources.

27. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to at least: Receive a request to create or update a network slice, where: The request includes a selection list; determining an isolation group using the selection list; and A network slice instance is provided for the network slice request, wherein the determined isolation group is associated with the network slice instance.

28. A computer program comprising instructions which, when executed by an apparatus, cause the apparatus to at least: Emitting a request to create or update a network slice, where The request includes a selection list, and wherein the selection list includes ranges that the apparatus may specify for determining an isolation group, the ranges including at least one isolation selection type and at least one isolation selection value; and Receive information about a network slice instance, wherein the network slice instance is associated with a determined isolation group.

Images