Method for network slice isolation management
By introducing isolation groups and isolation profiles into the 5G network, the problem of isolation of network slicing resources at multiple domains and levels is solved, and the security and reliability of network slicing is improved, ensuring the commercial deployment of 5G networks.
Patent Information
- Application Number
- CN202080096495.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-02-14
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2040-02-14
AI Technical Summary
Existing technologies are difficult to achieve effective isolation of network slicing resources at multiple domains and levels, especially in 5G networks. There is a lack of unified management and orchestration solutions for cross-domain resource isolation, which has led to the threat of the security of network slicing.
Introducing the concept of quarantine groups and quarantine profiles, by defining quarantine groups in each layer and domain, and defining resources at levels and policies based on quarantine profiles, to achieve network slicing resource isolation across multiple domains and levels .
It realizes effective isolation of network slicing resources across multiple domains and levels in a 5G network, improves the security and reliability of network slicing, and ensures the reliability and guarantee of commercial deployment.
Smart Images

Figure CN115152268B_ABST
Abstract
Description
Technical Field
[0001] Example and non-limiting embodiments generally relate to security, privacy and digital rights management, and more specifically, to methods for network slice isolation management. Background Art
[0002] It is known to provide resources in a wireless communication network. Summary of the invention
[0003] The following summary is intended to be exemplary only. This summary is not intended to limit the scope of the claims.
[0004] In one aspect, a method comprises: specifying or creating one or more isolation groups for at least one service, wherein resources of the service specified in the isolation group are shared with or without isolation; wherein an isolation group is defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service; linking an isolation profile for each of the one or more isolation groups, wherein the isolation profile includes at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile includes at least an isolation level for defining an isolation type; and allocating or reallocating the at least one resource to the at least one service based on the isolation profile linked to the one or more isolation groups.
[0005] On the other hand, a device comprises: at least one processor; and at least one non-transitory memory comprising computer program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to at least perform: specifying or creating one or more isolation groups for at least one service, wherein resources of the services specified in the isolation groups are shared with or without isolation; wherein isolation groups are defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service; linking an isolation profile for each of the one or more isolation groups, wherein the isolation profile includes at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile includes at least an isolation level for defining an isolation type; and allocating or reallocating the at least one resource to the at least one service based on the isolation profile linked to the one or more isolation groups.
[0006] On the other hand, a machine-readable exemplary non-transitory program storage device is provided, which tangibly embodies an instruction program executable by the machine to perform operations, the operations including: specifying or creating one or more isolation groups for at least one service, wherein resources of the service specified in the isolation group are shared with or without isolation; wherein isolation groups are defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service; linking an isolation profile for each of the one or more isolation groups, wherein the isolation profile includes at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile includes at least an isolation level for defining an isolation type; and allocating or reallocating the at least one resource to the at least one service based on the isolation profile linked to the one or more isolation groups.
[0007] On the other hand, an apparatus comprises: a component for specifying or creating one or more isolation groups for at least one service, wherein resources of the service specified in the isolation group are shared with or without isolation; wherein an isolation group is defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service; a component for linking an isolation profile for each of the one or more isolation groups, wherein the isolation profile includes at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile includes at least an isolation level for defining an isolation type; and a component for allocating or reallocating the at least one resource to the at least one service based on the isolation profile linked to the one or more isolation groups. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The foregoing aspects and other features are described in the following description in conjunction with the accompanying drawings, in which:
[0009] Figure 1 An example device that can be implemented in hardware and is configured to implement network slice isolation management based on the examples described in this document.
[0010] Figure 2 A class diagram showing support for resource isolation.
[0011] Figure 3 An example of isolated groups of network slice resources for two tenants is shown.
[0012] Figure 4 Another example of isolated groups of network slice resources for two tenants is shown.
[0013] Figure 5 Another example of isolated groups of network slice resources for two tenants is shown.
[0014] Fig. 6A A workflow showing the creation and validation of an isolation group.
[0015] Figure 6B A workflow describing the (re)allocation of resources with isolation groups is shown.
[0016] Figure 7 It is a class diagram of network slices that supports resource allocation.
[0017] Figure 8 An example workflow for network slice isolation in an E2E domain is shown.
[0018] Fig. 9 An example workflow for network slice isolation in the RAN domain is shown.
[0019] Fig.10 An example workflow for network slice isolation in the CN domain is shown.
[0020] Fig.11 This is an example method for implementing network slice isolation management based on the examples described in this article. DETAILED DESCRIPTION
[0021] The following acronyms and abbreviations that may be found in the specification and / or drawings are defined as follows:
[0022] 3GPP Third Generation Partnership Project
[0023] 5G Fifth Generation
[0024] 5GC 5G Core Network
[0025] AC access network
[0026] CN Core Network
[0027] CS Circuit Switching
[0028] DN Distinguish Name
[0029] E2E End to End
[0030] eMBB Enhanced Mobile Broadband
[0031] ETSI European Telecommunications Standards Institute
[0032] F False
[0033] FM Fault Management
[0034] gNB (or gNodeB) is a base station for 5G / NR, i.e., a node that provides NR user plane and control plane protocol termination to the UE and is connected to the 5GC via the NG interface
[0035] GSM Global System for Mobile Communications
[0036] GSMA GSM Association
[0037] GSMA NG GSMA Network Group
[0038] GST Generic Slice Template
[0039] Id Identifier
[0040] I / G Interface
[0041] IG Isolation Group
[0042] IOC Information Object Class
[0043] IoT
[0044] M Mandatory
[0045] MF Managed Function
[0046] MFPRAN Managed Function Provider Radio Access Network
[0047] MFC Managed Function Consumer
[0048] MFI Managed Function Instance
[0049] MFP Managed Function Provider / Manufacturer
[0050] MFPCN MFP Core Network
[0051] mIoT Massive Internet of Things
[0052] MNO Mobile Network Operator
[0053] MnS Management Services
[0054] MOI Managed Object Instance
[0055] NF Network Function
[0056] NFVO Network Function Virtualization Orchestrator
[0057] ng or NG new generation
[0058] NR New Radio
[0059] NS Network Slicing
[0060] NSC Network Service Consumer
[0061] NSI Network Slicing Example
[0062] NSP Network Service Provider
[0063] NSS Network Slicing Subnet
[0064] NSSC Network Slicing Subnet Consumer
[0065] NSSCN Network Slicing Subnet Core Network
[0066] NSSI Network Slicing Subnet Example
[0067] NSSP Network Slicing Subnet Provider / Producer
[0068] NSSPCN Network Slicing Subnet Provider / Producer Core Network
[0069] NSSPRAN Network Slicing Subnet Provider / Manufacturer Radio Access Network
[0070] NSSPTN Network Slicing Subnet Provider / Producer Transport Network
[0071] NSSRAN Network Slicing Subnet Radio Access Network
[0072] NSSTN Network Slicing Subnet Transport Network
[0073] NW Network
[0074] O Optional
[0075] PM Performance Management
[0076] PNF Physical Network Function
[0077] Pol Strategy
[0078] RAN Radio Access Network
[0079] RLS Row Level Security
[0080] SA2 Service Architecture - Working Group 2
[0081] SA5 Service Architecture - Working Group 5
[0082] SD Slice Differentiator
[0083] SLA Service Level Agreement
[0084] S-NSSAI Single Network Slice Selection Auxiliary Information
[0085] SSL Secure Sockets Layer
[0086] SST Slice / Service Type
[0087] T True
[0088] TLS Transport Layer Security
[0089] TN transmission network
[0090] TS Technical Specifications
[0091] UE User Equipment (e.g., wireless device, typically a mobile device)
[0092] UML Unified Modeling Language
[0093] uRLLC Ultra-Reliable Low Latency Communications
[0094] V pair (vesa2rsion)
[0095] VLAN Virtual Local Area Network
[0096] VIM Virtual Infrastructure Manager
[0097] VM Virtual Machine
[0098] VNF Virtual Network Function
[0099] VNFM VNF Manager
[0100] VPN Virtual Private Network
[0101] ZSM Zero Touch Network and Service Management
[0102] This article describes an example architecture involving E2E network slicing and service management.
[0103] Figure 1 The present invention is an example apparatus 100 that can be implemented in hardware and is configured to implement network slice isolation management based on the examples described herein. The apparatus 100 includes a processor 102 and at least one non-transitory memory 104 including computer program code 105, wherein the at least one memory 104 and the computer program code 105 are configured to, together with the at least one processor 102, cause the apparatus to implement network slice isolation management 106 based on the examples described herein. The apparatus 100 optionally includes a display 108, which can be used to display various aspects of the system or provide input and output (I / O). The apparatus 100 optionally includes one or more network (NW) interfaces (I / Fs) 110. The NW I / Fs 110 can be wired and / or wireless and communicate over the Internet / other network using any communication technology. The NW I / Fs 110 can include one or more transmitters and one or more receivers.
[0104] The apparatus 100 may be configured to implement the functions of a network slice management function / provider (NSMF / NSP), or a network slice subnet management function / provider (NSSMF / NSSP), or a network function management function / managed function provider (NFMF / MFP). The management function is typically an independent device, but in some limited cases, the management function may be part of a network element.
[0105] Network slicing has been specified as normative content in 3GPP SA2 and SA5 (see 3GPP TS 23.501, TS 28.530 and TS 28.531). Network slicing in the context of 3GPP SA2 or SA5 is on the E2E slice or service layer / domain, while the network slice subnet is on another specific layer / domain.
[0106] In 3GPP TS 28.530 V16.1.0 (2019-12), Section 4.1.9 describes the tenant information concept, indicating that the purpose of tenant information is to support multi-tenant environments in 5G network management, and further indicates that the 3GPP management system can use tenant information to associate communication services with tenants and control tenants' access to management capabilities.
[0107] As a key technology of 5G networks, network slicing enables mobile network operators (MNOs) to provide network resources to their enterprises or vertical consumers more effectively and efficiently.
[0108] Weak network slice isolation can compromise the security of the entire 5G network. For example, sensitive data managed within a network slice could be exposed to applications running in other network slice services through side channel attacks. This risk is even higher because isolation is distributed across each security domain of the underlying 5G security architecture. Therefore, tenant / slice isolation is very important to ensure reliable and guaranteed service guarantees and is essential for the commercial deployment of 5G networks based on network slicing technology.
[0109] Isolation of slices includes isolation of management resources (e.g., data, functions, or services) and managed resources (e.g., data, network functions, infrastructure resources, etc.) in multiple domains (e.g., RAN, core, transport, etc.).
[0110] The resources of a slice can be dedicated to the slice or shared with other slices. The challenge of slice isolation is the isolation of resources between slices.
[0111] Isolation at multiple layers (E2E slices / services, slice subnets, managed functions, etc.) to ensure the expected security level of network slices is critical for mobile network operators (MNOs) to deploy 5G networks commercially. The GSM Association (GSMA) defines requirements for isolating resources of network slices at different levels in the Generic Slicing Template (GST) (see GSMANG.116 - Generic Network Slicing Template). Some operators have also proposed requirements for resource isolation between network slices in 3GPP.
[0112] However, to date, there is no known central unified management / orchestration solution to isolate or separate resources of network slices with different isolation levels across multiple domains (e.g., E2E service / slice management domain, core network, radio access network (RAN), transport network, virtual infrastructure management domain, infrastructure (including PNF, VNF, virtual infrastructure, etc. domains)).
[0113] Furthermore, even though network slices can be grouped based on common characters and characteristics (e.g., same tenants, same security requirements, etc.), isolation between network slice groups has not been considered during network slice instance deployment and runtime.
[0114] The example described in this article introduces a new approach for isolating the resources of a network slice from other network slices across multiple domains / layers during deployment and runtime, especially when managing the plane.
[0115] Isolation groups (or isolation zones) or similar isolation groups or isolation zones are introduced to aggregate shared resources of network slices (or other services in various layers) with or without isolation.
[0116] An isolation group is defined in each resource layer constituting the E2E network slice. For example, an isolation group exists in the E2E slice layer to group the resources of the network slice service, an isolation group exists in the network slice subnet (NSS) layer to group the resources of the NSS service, and an isolation group exists in the managed function (MF) layer to group the resources of the MF service.
[0117] Isolation groups can be further defined based on the type of resource. For example, in a specific layer, there are isolation groups to group management resources of a service, and in the layer, there are isolation groups to group managed resources of a service.
[0118] Isolation groups can be further defined by characteristics and features (tenant, SST, industry, region, type of IoT device, etc.).
[0119] Each network slice or NSS service or MF service, etc. is assigned one or more isolation groups. In one embodiment, at least one service is a committed service in the network slice layer, a network slice subnet service in the slice subnet layer, a managed function service in the managed function layer, or a virtual network function. Therefore, the service can be a network slice service, a network slice subnet service, or a managed function service.
[0120] Network slices designated in the same isolation group share common resources with or without isolation.
[0121] The resources allocated to a network slice (or NSS service or MF service, etc.) are physically or logically isolated from the resources of other network slices (or NSS service or MF service, etc.) designated in different isolation groups.
[0122] When a network slice consumer (or NSSC or MFC) requests a network slice (or NSS service or MF service) provider / producer (NSP / NSSP / MFP) to allocate / modify one or more resources for a network slice (or NSS service or MF service), the network slice (or NSS service or MF service) consumer (NSC / NSSC / MFC) can explicitly create an isolation group for the network slice (or NSS service or MF service) and set the isolation group.
[0123] Otherwise, the service provider / producer (e.g., NSP, NSSP or MFP) may create or select one or more isolation groups for a network slice (or NSS service or MF service) based on an isolation profile or other isolation or sharing requirements from a service consumer for a requested service, and assign the one or more isolation groups to the network slice (or NSS service or MF service).
[0124] Isolation profiles (similarly Isolation Profiles) are introduced to define the isolation requirements of isolation groups. Each isolation group is associated with an isolation profile. The isolation profile includes an isolation level (or isolation level, as defined in GST). The isolation profile should include isolation policies for isolating and protecting resources assigned to the isolation group. 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.
[0125] Based on the isolation profile, the resources of one isolation group are separated from other isolation groups. Typically, an isolation profile is associated with an isolation group. In some cases, an isolation profile can be associated with a service profile for a supported service, or can be independent, for example, in a service allocation request with an isolation requirement but without explicitly identifying an isolation group. In this case, the NSP / NSSP / MFP can create or select one or more isolation groups for the service, link one or more isolation profiles to the one or more groups, and assign the one or more groups to the service.
[0126] Class diagram that supports resource isolation for supported services. Figure 2 A class diagram 200 is depicted that supports resource isolation for supported services. Figure 2 In the UML, aggregation is graphically represented as a hollow diamond, composition is graphically represented as a solid diamond, the asterisk "*" represents multiple instances, "1" represents one instance, and the arrow represents the direction of the association.
[0127] Several classes of type InformationObjectClass are shown, including SupportedService 202 class, AllocatedResource 204 class, IsolationGroup 206 class, IsolationProfile 208 class, and IsolationPolicy 210 class.
[0128] exist Figure 2 , there is a bidirectional association between SupportedService 202 and AllocatedResource 204. There is a directional association between SupportedService 202 and IsolationGroup 206. There is a directional association between SupportedService 202 and IsolationProfile 208. There is a directional association between IsolationGroup 206 and IsolationProfile 208. There is a directional association between IsolationProfile 208 and IsolationPolicy 210. There is naming containment between IsolationGroup 206 and itself (indicated by the text "Name" and the solid diamond association), and aggregation between IsolationProfile 208 and itself.
[0129] SupportedService 202 may be a committed service in the network slice layer, an NSS service in the slice subnet layer, an MF service in the managed function layer, a network service and VNF in the virtualized case, etc. AllocatedResource 204 may be a network slice instance (NSI) in the network slice layer, an NSS instance (NSSI) in the slice subnet layer, an MF instance (MFI) in the managed function layer, or a network slice instance and a VNF instance (VM or container-based) in the virtualized resource layer, etc. Therefore, in some embodiments, the allocated resource may be a network slice instance in the network slice layer, a network slice subnet instance in the slice subnet layer, a managed function instance in the managed function layer, or a virtual network function instance in the virtualized resource layer.
[0130] A service is associated with one or more isolation groups. Each group is used to aggregate a type of resources requested for a service (e.g., management resources, managed resources, or hybrid resources) based on a group type (e.g., tenant, region, service type (SST), or hybrid, etc.). For example, both management resources (e.g., resources supporting FM, PM data of slices, resources supporting creation, reading, updating, and deletion operations for slices, etc.) and managed resources (e.g., resources supporting RAN, TN, CN, network function / NF services, subscriber data) can be used for network slice management, operation, and service end users. Several isolation groups can be created to support resource isolation of network slices. Some groups are used for management resource isolation, and some groups are used for managed resource isolation.
[0131] An isolation group can be a root isolation group or included by another isolation group (larger scope). For example, an SST isolation group can be included by a tenant isolation group. Each isolation group is associated with an isolation profile to define isolation levels, isolation and protection policies, etc. (e.g., IsolationPolicy 210). If an isolation group contains another isolation group, the isolation level of the containing isolation group can be stricter than the isolation level of the contained isolation group. For example, if an SST isolation group is included by a tenant isolation group, and the isolation level of the SST isolation group is logical isolation, the isolation level of the tenant isolation group can be logical or physical isolation. If the isolation level of the SST isolation group is physical isolation, the isolation level of the tenant isolation group should be physical isolation.
[0132] Isolation for supported services can be based on isolation profiles for each resource type's isolation group. An example approach is outlined below:
[0133] Check the isolation profile of the linked isolation group of resource one
[0134] ο Check the isolation profile of the linked isolation group (leaf isolation group)
[0135] ο Check the isolation profile that contains the isolation group (intermediate IG)
[0136] ο Check the isolation profiles of the containing isolation groups (intermediate IG or root IG) of the intermediate IG until the root isolation group is reached
[0137] Check the isolation profile of the isolation group linked to resource 2
[0138] ο Check the isolation profile of the linked isolation group (leaf isolation group)
[0139] ο Check the isolation profile that contains the isolation group (intermediate IG)
[0140] ο Check the isolation profiles of the containing isolation groups (intermediate IG or root IG) of the intermediate IG until the root isolation group is reached
[0141] Check the isolation profiles of the linked isolation groups until all resource types have been addressed
[0142] Thus, in other words, the method includes determining the following. If the isolation group of the resource linked to the service is a leaf isolation group, it is contained by another group (e.g., a parent group), and that other group may be contained by further groups, until continuing to the root isolation group. In turn, the method considers the isolation profile of the linked isolation group itself, then the isolation profile of its parent group, then the isolation profile of the parent group's parent group, and so on, until the root group is addressed.
[0143] Figure 3 An example 300 of isolated groups of network slice resources for two tenants and network slice resources for two SSTs is depicted. Figure 3The example 300 shown in is the managed resources (e.g., AN, CN, and TN) 302 of a network slice provider. Two tenant isolation groups are IG_Tenant-1-dedicated 310 and IG_Tenant-2-dedicated 350. The two tenant isolation groups are physically isolated from each other and from other IGs. The isolation groups contained within IG_Tenant-1-dedicated 310 are IG_SST-eMBB 320 and IG_SST-uRLLC 330, and IGs 320 and 330 are physically isolated from each other. IG_SD-1 322 and IG_SD-2 324 are contained within IG_SST-eMBB 320 and are logically isolated from each other. The isolation groups included in IG_Tenant-2-dedicated 350 are IG_SST-eMBB 360, IG_SST-uRLLC 370, IG_SST-mIOT-1 380, and IG_SST-mIOT-2 385. IGs 370 and 385 are physically isolated from other IGs, while IGs 360 and 380 are logically isolated from other IGs. IG_SD-1 362 and IG_SD-2 364 are included in IG_SST-eMBB 360 and are logically isolated. IG_SD-1 372 and IG_SD-2 374 are included in IG_SST-uRLLC 370 and are logically isolated. The managed resources (e.g., AN, CN, and TN) 302 of the network slice provider also include isolation groups IG_SST-eMBB-common 390 and IG_SST-mIOT-common 395 to aggregate the managed resources for eMBB and mIOT SST, and IGs 390 and 395 are logically isolated from other IGs. Isolation groups IG_SD-1 396 and IG_SD-2 397 are included in IG_SST-mIOT-common 395 and are logically isolated from each other. Therefore, as Figure 3 As shown in , the one or more isolation groups may include a tenant isolation group and a public isolation group.
[0144] Understandably, Figure 3In and throughout the rest of this disclosure, isolation group objects and other objects are named based on the functionality they are related to or serve. For example, IG_SST-eMBB defines an enhanced mobile broadband (eMBB) slice / service type (SST) isolation group (IG), IG_SD-1 defines a slice differentiator (SD) isolation group (IG), IG_SST-uRLLC defines an ultra-reliable low latency communication slice / service type (SST) isolation group (IG), IG_SST-mIOT-1 defines a massive Internet of Things (mIoT) slice / service type (SST) isolation group (IG), etc.
[0145] The resources of services specified in an isolation group can be shared with or without isolation. Figure 3 In the present invention, there are larger (e.g., containing) isolation groups (such as IG 310), and there are also smaller (e.g., contained) and leaf isolation groups (such as 330). The service provider always assigns a leaf IG to a service for specific resources. Within this leaf IG (e.g., 330), the resources assigned to the services (e.g., service-uRLLC-1 and service-uRLLC-2) are shared without isolation. In another case, there is a third service, namely eMBB service (service-eMBB-SD1-3). The service provider will assign another leaf IG (e.g., 322) to the eMBB service. Therefore, the resources of service-eMBB-SD1-3 and service-uRLLC-1 / service-uRLLC-2 should be isolated from each other because they belong to different isolation groups (IGs). Both 322 and 330 are under the same larger IG 310. The service resources in different sub-IGs of the super IG (IG 310) should be isolated. Therefore, the service resources in the super IG can be with or without isolation. For example, in this scenario, service-uRLLC-1 and service-uRLLC-2 are assigned without isolation. Here, the two services assigned to IG 330 are assigned without isolation from each other because they share a common IG, i.e., IG 330. At the same time, the service assigned to IG 330 and the service assigned to IG 322 have isolation even though they share a common IG, i.e., IG 310.
[0146] Figure 4 Another example 400 of isolated groups of network slice resources for two tenants is depicted. Figure 4The example 400 shown in is the management resources (e.g., FM, PM data) 402 of the network slice provider. The two tenant isolation groups are IG_Tenant-1-dedicated 410 and IG_Tenant-2-dedicated 450. The two tenant isolation groups are physically isolated from each other and from other IGs. The isolation groups contained within IG_Tenant-1-dedicated 410 are IG_SST-eMBB 420 and IG_SST-uRLLC 430. 420 is logically isolated from other IGs, while 430 is physically isolated from other IGs. The isolation groups contained within IG_Tenant-2-dedicated 450 are IG_SST-eMBB 452, IG_SST-uRLLC456, IG_SST-mIOT-1 454, and IG_SST-mIOT-2 458, which are logically isolated from each other.
[0147] Figure 5 Another example 500 of isolated groups of network slice resources for two tenants is depicted. Figure 5 The example 500 shown in is the management resources (e.g., FM, PM Management Service (MnS)) 502 of the network slice provider. The two tenant isolation groups are IG_Tenant-1-dedicated 510 and IG_Tenant-2-dedicated 550. The two tenant isolation groups are physically isolated from each other and from other IGs. The isolation groups contained in IG_Tenant-1-dedicated 510 are IG_SST-eMBB 520 and IG_SST-uRLLC 530. They are logically isolated from each other. The isolation group contained in IG_Tenant-2-dedicated 550 is IG_SST-uRLLC 560. The management resources (e.g., FM, PM MnS) 502 of the network slice provider also include an isolation group IG_Common 590 that is logically isolated from other IGs.
[0148] Information Object Class Definition
[0149] IsolationGroup. The IsolationGroup IOC includes the properties inherited from the Top IOC and the following properties:
[0150] Property Name Support qualifiers isReadable isWritable isInvariant isNotifyable resourceType M T F T F groupType M T F T F Role-related attributes isolationProfile M T T F T
[0151] resourceType defines the type of resources that can be allocated to the supported services. resourceType can be, for example, management resources (data, management services, etc.), managed resources (management data, functions, services, etc.), or mixed types of resources. Management resources can be management resources that generally support supervision (for example, performance management and fault management). Managed resources can be resources that support radio access network, transport network or core network functions or services. Each type of resource for a service can be associated with an IsolationGroup. groupType defines the characteristics of an IsolationGroup, for example, it can be tenant-based, service type-based, region-based, industry-based, or mixed, etc. An IsolationGroup can be contained by another IsolationGroup of the same resourceType. During the implementation of isolation requirements, the service provider can check the service profile linked to the IsolationGroup in the entire distinguished name (DN) path of the id of the linked IsolationGroup (from leaf to root).
[0152] IsolationProfile. The IsolationProfile IOC includes the properties inherited from the Top IOC and the following properties:
[0153] Property Name Support qualifiers isReadable isWritable isInvariant isNotifyable isolationLayer M T F T F IsolationDomain M T F T F resourceType M T F T F isolationLevel M T T F T Role-related attributes isolationPolicy M T T F T isolationProfile O T T F T
[0154] IsolationLayer defines the layer of the network in which related resources are allocated and isolated, which can be, for example, the E2E service / network slice layer, the slice subnet layer, the managed function layer, the network service and VNF layer in the case of virtualization. IsolationDomain defines the domain of the network in which related resources are allocated and isolated, which can be, for example, the E2E service / network slice domain, the core network (CN) domain, the access network (AN) domain, the transport network (TN) domain, the virtualization domain, etc.
[0155] For the definition of isolationLevel, see GSMA NG.116 (Generic Network Slicing Template).
[0156] The isolation level and / or policy can be different for different isolation layers and domains.
[0157] An IsolationProfile (e.g., IsolationProfile 208) may be aggregated by another IsolationProfile of the same resourceType, isolationLayer, and isolationDomain. When a service provider creates one or more IsolationGroups (e.g., one or more of IsolationGroup 206) based on an IsolationProfile identified by a service consumer, it should create one or more IsolationGroups from the root group to the leaf group based on the aggregation relationship of the one or more IsolationProfiles. If an IsolationProfile is not aggregated by another IsolationProfile, a single IsolationGroup may be created for such resources requested by the service that is both a root group and a leaf group.
[0158] Alternatively, IsolationProfile may not be defined in a hierarchy. A single IsolationProfile may exist to include all levels of isolation requirements. In this case, the Service Provider may also create one or more IsolationGroups from the root group to the leaf group, based on the requirements defined in the IsolationProfile.
[0159] The IsolationPolicy (e.g., IsolationPolicy 210) IOC includes the properties inherited from the Top IOC and the following properties:
[0160] Property Name Support qualifiers isReadable isWritable isInvariant isNotifyable Isolation Rules M T T F T
[0161] isolationRules define rules for isolating and protecting specific resources in specific layers and domains. For example, the rules defined in isolationRules for logically isolating common management data (FM, PM data, logs, etc.) of services in the E2E slice layer may be "protect data with access control and static encryption, and protect data with TLS / SSL by using slice-specific credentials in transit". The rules for logically isolating management services may be "dedicated management service instances should be created for slices". The rules for physically isolating the radio access network subnets of network slices may be "dedicated DU / units should be assigned to slices", etc. The rules for logically isolating the core network subnets of network slices may be "leverage a robust implementation of the virtualization layer (e.g., hypervisor, container platform, etc.) to separate the NF / NF services of subnets, and utilize dedicated virtual switches, VLANs to separate the traffic of NF / NF services, etc."
[0162] Resource-isolated workflows in service providers / producers. Fig. 6A An example workflow 600 - 1 (ie, example method) for creation and validation of an isolation group is shown. Figure 6B An example workflow 600 - 2 (eg, example method) describing (real) allocation (eg, assignment or reallocation) of resources with isolation groups is shown. Fig. 6A and Figure 6B can be considered to belong together.
[0163] exist Fig. 6A , processing a request (601). At 602, the method includes: receiving a service assignment / modification request. At 604, the method includes: extracting and interpreting one or more isolation groups from the request. At 606, the method determines whether the one or more isolation groups are empty. If the determination at 606 is affirmative (e.g., "yes"), then at 608, the method includes: extracting and interpreting one or more isolation profiles from the request. If the determination at 606 is negative (e.g., "no"), the method proceeds to reference numeral 624 in the workflow. At 610, the method includes: determining whether the one or more isolation profiles are empty. If the determination at 610 is affirmative (e.g., "yes"), then at 612, the method includes: specifying the one or more isolation profiles to the requested service. If the determination at 610 is negative (e.g., "no"), the method proceeds to reference numeral 614 in the workflow.
[0164] At 614, the method includes: verifying one or more isolation profiles. At 616, the method includes: determining whether the one or more isolation profiles are valid. If the determination at 616 is negative (e.g., "No"), then at 618, an error is reported. If the determination at 616 is affirmative (e.g., "Yes"), then at 620, the method includes: creating one or more isolation groups for the requested service based on the one or more isolation profiles. At 622, the method includes: linking the one or more isolation profiles to the associated one or more isolation groups. At 624, the method includes: verifying one or more isolation groups. At 626, the method includes: determining whether the one or more isolation groups are valid. If the determination at 626 is negative (e.g., "No"), then an error is reported at 628. If the determination at 626 is affirmative (e.g., "Yes"), then the method proceeds to Figure 6B Reference number 630 in the workflow / method 600-2 shown in FIG.
[0165] exist Figure 6B , utilizing the isolated resources to implement the service request (629). At 630, the method includes: allocating or reallocating resources for the service. At 632, the method includes: obtaining an isolation group of the resource type requested for the service. At 634, the method includes: determining whether resources of the same isolation group (the original IG of the resource type) exist. If the determination at 634 is affirmative (e.g., "yes"), the method continues to allocate resources to the service (648). If the determination at 634 is negative (e.g., "no"), the method proceeds to 636. At 636, the method includes: obtaining the parent isolation group of the current IG. At 638, the method includes: determining whether the parent IG exists and whether the resources of the parent IG do not exist. If the determination at 638 is affirmative (e.g., "yes"), the method proceeds to 636. If the determination at 638 is negative (e.g., "no"), the method proceeds to 640.
[0166] At 640, the method includes: obtaining an isolation profile of the current isolation group. At 642, the method includes: creating and protecting the resources of the current isolation group under the resources of its parent isolation group according to the isolation level and policy of the isolation profile of the current isolation group. As shown at 644, the step at 642 includes: if there is no parent IG for the current isolation group, then creating the resource under the common resource. At 646, the method includes: linking the new resource to the current isolation group, and then proceeding to 634 to check again whether the resources of the same isolation group (which is the original IG for the resource type of the service) exist. At 648, the method includes: allocating the resources of the same isolation group to the service without isolation. As shown at 650, if the resources of the same IG cannot meet the service requirements, the step at 648 may include: scaling out or reconfiguring resources. At 652, the method includes: determining whether there are more resource types. If the determination at 652 is affirmative (e.g., "yes"), the method proceeds to 632, otherwise the method 600-2 terminates.
[0167] A class diagram of a network slice that supports resource isolation. At least two class implementation options are provided.
[0168] Option 1: Isolation groups are based on “Served Network Slices” in each layer. In this option, the network slice object is modeled in the E2E service layer. The MOI is uniquely identified by the DN and refers to the E2E Slice Id (S-NSSAI).
[0169] Option 2: Isolation groups are based on "Served Service" in each layer. In this option, service objects are modeled in each layer. MOI is uniquely identified by DN and is independent of E2E Slice Id (S-NSSAI).
[0170] Figure 7 is an example network slice class diagram 700 that supports resource allocation. Figure 7 In the UML, based on the aggregation is graphically represented as a hollow diamond, the asterisk "*" represents multiple instances, "1" represents one instance, "0..1" represents zero or one or one at a time, and the arrow represents the direction of the association.
[0171] exist Figure 7In the example shown, each class is of type InformationObjectClass. There is a directional association between IsolationGroup(CS)704 and IsolationProfileNS702. There is a directional association between CommittedService714 and IsolationGroup(CS)704. There is a directional association between NetworkSlice720 and CommittedService714. There is a directional association between IsolationGroup(NSS)708 and IsolationProfileNSS706. There is a directional association between NSSService716 and IsolationGroup(NSS)708. There is a directional association between NetworkSliceSubnet722 and NSSService716. There is a directional association between NetworkSlice720 and NetworkSliceSubnet722. There is a directional association between NetworkSliceSubnet722 and itself. There is a directional association between IsolationGroup(NS)728 and IsolationProfileNS726. There is a directional association between NetworkService 730 and IsolationGroup (NS) 728 .
[0172] There is a directional association between NetworkSliceSubnet 722 and NetworkService 730. There is a directional association between IsolationGroup(MF) 710 and IsolationProfileMF 712. There is a directional association between MFService 718 and IsolationGroup(MF) 710. There is a directional association between ManagedFunction 724 and MFService 718. There is a directional association between NetworkSliceSubnet 722 and ManagedFunction 724. There is a directional association between ManagedFunction 724 and VNF 732. There is a directional association between NetworkService 730 and VNF732. There is a directional association between VNF 732 and IsolationGroup(VNF) 734. There is a directional association between IsolationGroup(VNF) 734 and IsolationProfileVNF 736.
[0173] Understandably, Figure 7 In and throughout the rest of this disclosure, the name of an object (e.g., a class object) is based on the functionality it relates to or serves. For example, the class object IsolationProfileNS 702 is a network slice isolation profile class object, IsolationGroup(NSS) 708 is a network slice subnet isolation group class object, etc.
[0174] Workflow for resource isolation implementation in multiple layers for network slice allocation. The following assumptions are made:
[0175] 1. In this embodiment, network slicing can be supported by network slice instances (NSIs) that constitute RAN, CN and TN NSSIs.
[0176] 2. gNB is a physical box, and CN is virtualized.
[0177] 3. Three IsolationProfiles are defined for network slicing.
[0178]
[0179] 4. In this embodiment, no resources are allocated to network slices, NSS, MF or NF with the same IsolationGroup. Otherwise, the process may be different.
[0180] Figure 8 An example workflow 800 for network slice isolation in an E2E domain is depicted. Figure 8 Shown are NSC 820, NSP 830, NSSPRAN 840, NSSPCN 850, and NSSPTN 860. Figure 8 In FIG. 8 , reference numerals 801 to 813 correspond to numbers 1 to 13, respectively. Figure 8 In the workflow 800, the directional arrows are examples, and thus in other embodiments, an entity may perform an action on another entity in a different entity than that shown in the workflow 800.
[0181] At 801, NSC 820 requests NSP 830 to allocate resources for a network slice, wherein the input parameters include, for example, ServiceProfile, one or more IsolationProfileNS, etc. As shown at 870, the NSC may include one or more IsolationGroups created before the request instead of using one or more IsolationProfileNS as input parameters. At 802, NSP 830 verifies the one or more isolation profiles and creates one or more isolation groups accordingly. As shown at 880, if the one or more isolation profiles are empty, one or more default profiles of the tenant of the network slice may be used based on the system configuration or the tenant's policy or SLA.
[0182] At 803, the NSP 830 decomposes the network slice request into one or more NSS requests based on the service profile and one or more IsolationGroups. At 804, the NSP 830 converts one or more IsolationProfileNS of one or more IsolationGroups in the network slice request into one or more IsolationProfileNSSRAN, one or more IsolationProfileNSSCN, and one or more IsolationProfileNSSTN. As shown at 890, the IsolationProfile for RAN, CN, and TN NSS can be the same for management resources (see, for example, Figure 4 and Figure 5 ), but may be different for managed resources (see for example Figure 3 ). For example, the IsolationRules for RAN resources can be [“Isolate at and above the RLS layer”], the IsolationRules for core resources can be [“Isolate NF / NF services using a robust virtualization layer”, “Isolate traffic for NF / NF services using dedicated virtual switches”], and the IsolationRules for TN resources can be [“Isolate using VPN”].
[0183] At 805, NSP 830 requests NSSPRAN 840 to allocate resources for RAN NSS services. Input parameters include, for example, SliceProfile, one or more IsolationProfileNSSRAN, etc. At 806, NSSPRAN 840 provides an allocation response to NSP 830, including, for example, RAN NSS service instance, one or more IsolationGroups, etc. At 807, NSP 830 requests NSSPCN 850 to allocate resources for CN NSS services, wherein the input parameters include, for example, SliceProfile, one or more IsolationProfileNSSCN, etc. At 808, NSSPRAN 840 provides an allocation response to NSP 830, including, for example, CNNSS service instance, one or more IsolationGroups, etc. At 809, NSP 830 requests NSSPTN 860 to allocate resources for TN NSS services, wherein the input parameters include, for example, SliceProfile, one or more IsolationProfileNSSTN, etc. At 810, NSSPRAN 840 provides an allocation response to NSP 830, including, for example, a TN NSS service instance, one or more IsolationGroups, etc. At 811, NSP 830 creates a network slice and a committed service instance for the network slice, associates the one or more IsolationGroups with the committed service instance, and associates the committed service instance with the NSI. At 812, NSP 830 allocates resources for management data and services of the network slice based on one or more related IsolationProfiles of management resources of the network slice. At 813, NSP 830 sends a response to NSC 820, including a committed service instance, one or more IsolationGroups, etc.
[0184] Fig. 9 An example workflow 900 for network slice isolation in the RAN domain is depicted. Fig. 9 Shown in the figure are NSP 920, NSSPRAN 930, and MFPRAN 940. Fig. 9 In FIG. 1 , reference numerals 901 to 910 correspond to numbers 1 to 10, respectively. Fig. 9 In the example, the directional arrows are examples, so that in other embodiments, the entity can perform an action on another entity in a different entity than that shown in the workflow 900. This example shows the option of the service consumer specifying one or more IsolationGroups.
[0185] At 901, NSP 920 requests NSSPRAN 930 to allocate one or more IsolationGroups, wherein the input parameters include, for example, one or more IsolationProfileNSSRAN, S-NSSAI, etc. At 902, NSSPRAN 930 verifies the one or more isolation profiles and creates one or more isolation groups accordingly. As shown at 950, if the one or more isolation profiles are empty, one or more default profiles of the SST of S-NSSAI can be used based on the system configuration. At 903, NSSPRAN 930 provides a response to NSP 920 regarding the one or more created IsolationGroups.
[0186] At 904, NSP 1020 requests NSSPRAN 930 to allocate RAN NSS for the network slice, where input parameters include, for example, S-NSSAI, SliceProfileRAN, one or more IsolationGroups, etc.
[0187] At 905, the NSSPRAN 930 maps the NSS request to configuration parameters of the RAN MF according to the slice profile and one or more IsolationProfiles of the one or more IsolationGroups. At 906, the NSSPRAN 930 configures parameters on the RAN MF for the MFPRAN 940, such as the S-NSSAI and function and isolation related parameters. At 907, the MFPRAN 940 provides a configuration response to the NSSPRAN 930. At 908, the NSSPRAN 930 creates a RAN NSSI and an NSS service instance for the S-NSSAI, associates the one or more IsolationGroups with the NSS service instance, and associates the NSS service instance with the NSSI. At 909, the NSSPRAN 930 allocates resources for management data and services for the S-NSSAI based on one or more related IsolationProfiles of the management resources of the NSS. At 910, the NSSPRAN 930 provides an allocation response to the NSP 920, such as the RAN NSSI, the RAN NSS service instance, etc.
[0188] Fig.10 An example workflow 1000 for network slice isolation in a CN domain is depicted. Fig.10 Shown in the figure are NSP 1020, NSSPCN 1030, NFVO 1050, VIM or VNFM 1060, and MFPCN 1070. Fig.10In FIG. 1 , reference numerals 1001 to 1013 correspond to numbers 1 to 13, respectively. Fig.10 In the example 1000, the directional arrows are examples, so that in other embodiments, the entity may perform an action on another entity in a different entity than that shown in the workflow 1000. This example 1000 shows the option of a service consumer specifying one or more IsolationGroups.
[0189] At 1001, NSP 1020 requests NSSPCN 1030 to allocate one or more IsolationGroups, where the input parameters include, for example, one or more IsolationProfileNSSCN, S-NSSAI, etc. At 1002, NSSPCN 1030 verifies the one or more isolation profiles and creates one or more isolation groups accordingly. As shown at 1080, if the one or more isolation profiles are empty, one or more default profiles of the SST of the S-NSSAI can be used based on the system configuration. At 1003, NSSPCN 1030 provides a response with the one or more created IsolationGroups to NSP 1020.
[0190] At 1004, NSP 1020 requests NSSPCN 1030 to allocate CN NSS for network slices, where input parameters include, for example, S-NSSAI, SliceProfileCN, one or more IsolationGroups, etc. At 1005, NSSPCN 1030 maps the NSS request to network services and CN MFs with configuration parameters according to the slice profile and the IsolationProfile of one or more IsolationGroups. At 1006, NSSPCN 1030 requests NFVO 1050 to deploy and configure network services. At 1007, NFVO 1050 requests VIM or VNFM 1060 to deploy VNFs based on the resource and isolation request.
[0191] At 1008, NFVO 1050 provides a deployment response to NSSPCN 1030, including the NS with VNF information. At 1009, NSSPCN 1030 configures parameters on the core MF for MFPCN 1070, including S-NSSAI and function-related parameters. At 1010, MFPCN 1070 provides a configuration response to NSSPCN 1030. At 1011, NSSPCN 1030 creates CNNSSI and NSS service instance for S-NSSAI, associates the one or more IsolationGroups with the NSS service instance, and associates the NSS service instance with the NSSI. At 1012, NSSPCN 1030 allocates resources for management data and services for S-NSSAI, based on one or more related IsolationProfiles of management resources of NSS. At 1013, NSSPCN 1030 provides an allocation response to NSP 1020, including CN NSSI, CN NSS service instance, etc.
[0192] The examples described herein may contribute to 3GPP SA5 or ETSI ZSM specifications.
[0193] Fig.11 An example method 1100 for implementing network slice isolation management based on the examples described herein is provided. At 1102, the method includes: specifying or creating one or more isolation groups for at least one service, wherein resources of the service specified in the isolation group are shared with or without isolation. At 1104, the method includes: wherein an isolation group is defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service. At 1106, the method includes: linking an isolation profile for each isolation group in the one or more isolation groups, wherein the isolation profile includes at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile includes at least an isolation level for defining an isolation type. At 1108, the method includes: allocating or reallocating the at least one resource to the at least one service based on the isolation profile linked to the one or more isolation groups.
[0194] An example method includes: specifying or creating one or more isolation groups for at least one service, wherein resources of the service specified in the isolation group are shared with or without isolation; wherein an isolation group is defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service; linking an isolation profile for each of the one or more isolation groups, wherein the isolation profile includes at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile includes at least an isolation level for defining an isolation type; and allocating or reallocating the at least one resource to the at least one service based on the isolation profile linked to the one or more isolation groups.
[0195] The method may further include: wherein the isolation group is defined based on a type of at least one resource and a service characteristic supported by the at least one resource.
[0196] The method may further include: wherein, based on the isolation profile, resources allocated to the service are physically or logically isolated from resources of other services specified in different isolation groups.
[0197] The method may further include: wherein one or more isolation groups are specified or created by a service consumer or a service producer.
[0198] The method may further include: wherein the isolation level is physical or logical isolation.
[0199] The method may further include: wherein the isolation profile is associated with a service profile of a supported service, or is independent.
[0200] The method may further include: wherein at least one resource is a management resource, and the at least one resource is a managed resource.
[0201] The method may further include: wherein one or more isolation groups are root isolation groups, or one or more isolation groups are contained by another isolation group.
[0202] The method may further include: wherein the isolation level of the containing isolation group is stricter than the isolation level of the contained isolation group.
[0203] The method may further include determining isolation for at least one resource of a service by examining isolation profiles containing isolation groups until all isolation groups in a chain of containing isolation groups including a root isolation group are addressed or considered.
[0204] The method may further include determining isolation for at least one service by examining isolation profiles of linked isolation groups until a plurality of resource types are addressed.
[0205] The method may further include: wherein, when resources of a service are specified in a common isolation group, the resources of the service specified in the isolation group are shared without isolation; and wherein, when resources of a service are further specified in different isolation groups within the common isolation group, the resources of the service specified in the isolation group are shared under isolation.
[0206] An example device comprises: at least one processor; and at least one non-transitory memory comprising computer program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to at least perform: specifying or creating one or more isolation groups for at least one service, wherein resources of the services specified in the isolation groups are shared with or without isolation; wherein isolation groups are defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service; linking an isolation profile for each of the one or more isolation groups, wherein the isolation profile includes at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile includes at least an isolation level for defining an isolation type; and allocating or reallocating the at least one resource to the at least one service based on the isolation profile linked to the one or more isolation groups.
[0207] The apparatus may further include: wherein the isolation group is defined based on a type of at least one resource and a service characteristic supported by the at least one resource.
[0208] The apparatus may further include: wherein, based on the isolation profile, resources allocated to the service are physically or logically isolated from resources of other services specified in different isolation groups.
[0209] The apparatus may further include: wherein the one or more isolation groups are specified or created by a service consumer or a service producer.
[0210] The apparatus may further include: wherein the isolation level is physical or logical isolation.
[0211] The apparatus may further include: wherein the isolation profile is associated with a service profile of a supported service, or is independent.
[0212] The apparatus may further include: wherein at least one resource is a management resource, and the at least one resource is a managed resource.
[0213] The apparatus may further include: wherein one or more isolation groups are root isolation groups, or one or more isolation groups are contained by another isolation group.
[0214] The apparatus may further include: wherein an isolation level of the containing isolation group is stricter than an isolation level of the contained isolation group.
[0215] The apparatus may further include: wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the apparatus to at least perform: determining isolation for at least one resource of a service by: checking isolation profiles containing isolation groups until all isolation groups in the chain of containing isolation groups including the root isolation group are addressed or considered.
[0216] The apparatus may further include: wherein the at least one memory and the computer program code are further configured to, together with the at least one processor, cause the apparatus to at least perform: determining isolation for at least one service by: checking isolation profiles of the linked isolation groups until multiple resource types are addressed.
[0217] The device may further include: wherein, when resources of a service are specified in a common isolation group, the resources of the service specified in the isolation group are shared without isolation; and wherein, when resources of a service are further specified in different isolation groups within the common isolation group, the resources of the service specified in the isolation group are shared under isolation.
[0218] An exemplary non-transitory program storage device readable by a machine is provided, which tangibly embodies an instruction program executable by the machine to perform operations, the operations including: specifying or creating one or more isolation groups for at least one service, wherein resources of the service specified in the isolation group are shared with or without isolation; wherein isolation groups are defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service; linking an isolation profile for each of the one or more isolation groups, wherein the isolation profile includes at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile includes at least an isolation level for defining an isolation type; and allocating or reallocating the at least one resource to the at least one service based on the isolation profile linked to the one or more isolation groups.
[0219] The non-transitory program storage device operations may further include wherein the isolation group is defined based on a type of the at least one resource and a service characteristic supported by the at least one resource.
[0220] The non-transitory program storage device operations may further include wherein, based on the isolation profile, resources allocated to the service are physically or logically isolated from resources of other services designated in a different isolation group.
[0221] The non-transitory program storage device operations may further include where one or more isolation groups are specified or created by a service consumer or a service producer.
[0222] The non-transitory program storage device operations may further include: wherein the isolation level is physical or logical isolation.
[0223] The non-transitory program storage device operations may further include wherein the isolation profile is associated with a service profile of a supported service, or is independent.
[0224] The non-transitory program storage device operations may further include: wherein at least one resource is a management resource, and wherein the at least one resource is a managed resource.
[0225] The non-transitory program storage device operations may further include wherein the one or more isolation groups are root isolation groups, or wherein the one or more isolation groups are contained by another isolation group.
[0226] The non-transitory program storage device operations may further include wherein an isolation level of the containing isolation group is stricter than an isolation level of the contained isolation group.
[0227] The non-transitory program storage device operations may further include determining isolation for at least one resource of a service by examining isolation profiles of containing isolation groups until all isolation groups in a chain of containing isolation groups including a root isolation group are addressed or considered.
[0228] The non-transitory program storage device operations may further include determining isolation for the at least one service by examining isolation profiles of linked isolation groups until a plurality of resource types are addressed.
[0229] These non-transitory program storage device operations may further include: wherein, when resources of a service are specified in a common isolation group, the resources of the service specified in the isolation group are shared without isolation; and wherein, when resources of a service are further specified in different isolation groups within the common isolation group, the resources of the service specified in the isolation group are shared under isolation.
[0230] An example apparatus comprises: a component for specifying or creating one or more isolation groups for at least one service, wherein resources of the service specified in the isolation group are shared with or without isolation; wherein an isolation group is defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service; a component for linking an isolation profile for each of the one or more isolation groups, wherein the isolation profile includes at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile includes at least an isolation level for defining an isolation type; and a component for allocating or reallocating the at least one resource to the at least one service based on the isolation profile linked to the one or more isolation groups.
[0231] The apparatus may further include: wherein the isolation group is defined based on a type of at least one resource and a service characteristic supported by the at least one resource.
[0232] The apparatus may further include: wherein, based on the isolation profile, resources allocated to the service are physically or logically isolated from resources of other services specified in different isolation groups.
[0233] The apparatus may further include: wherein the one or more isolation groups are specified or created by a service consumer or a service producer.
[0234] The apparatus may further include: wherein the isolation level is physical or logical isolation.
[0235] The apparatus may further include: wherein the isolation profile is associated with a service profile of a supported service, or is independent.
[0236] The apparatus may further include: wherein at least one resource is a management resource, and the at least one resource is a managed resource.
[0237] The apparatus may further include: wherein one or more isolation groups are root isolation groups, or one or more isolation groups are contained by another isolation group.
[0238] The apparatus may further include: wherein an isolation level of the containing isolation group is stricter than an isolation level of the contained isolation group.
[0239] The apparatus may further include means for determining isolation for at least one resource of a service by examining isolation profiles containing isolation groups until all isolation groups in a chain of containing isolation groups including a root isolation group are addressed or considered.
[0240] The apparatus may further include means for determining isolation for the at least one service by examining isolation profiles of the linked isolation groups until a plurality of resource types are addressed.
[0241] The device may further include: wherein, when resources of a service are specified in a common isolation group, the resources of the service specified in the isolation group are shared without isolation; and wherein, when resources of a service are further specified in different isolation groups within the common isolation group, the resources of the service specified in the isolation group are shared under isolation.
[0242] It should be understood that the above description is merely illustrative. Various alternatives and modifications may be devised by those skilled in the art. For example, the features described in the various dependent claims may be combined with each other in any suitable combination. In addition, features from the different embodiments described above may be selectively combined into new embodiments. Therefore, this description is intended to cover all such alternatives, modifications and variations that fall within the scope of the appended claims.
Claims
1. A method, include: specifying or creating one or more isolation groups for at least one service, wherein resources of the services specified in the isolation groups are shared with or without isolation; wherein an isolation group is defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service; linking an isolation profile for each of the one or more isolation groups, wherein the isolation profile comprises at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile comprises at least an isolation level for defining an isolation type; and The at least one resource is allocated or reallocated to the at least one service based on the isolation profile linked to the one or more isolation groups.
2. The method according to claim 1, in, The isolation group is defined based on a type of the at least one resource and a service characteristic supported by the at least one resource.
3. The method according to claim 1, in, Based on the isolation profile, resources allocated to a service are physically or logically isolated from resources of other services specified in different isolation groups.
4. The method according to claim 1, in, The one or more isolation groups are specified or created by a service consumer or a service producer.
5. The method according to claim 1, in, The isolation level is physical or logical isolation.
6. The method according to claim 1, in, The isolation profile may be associated with a service profile for a supported service or may be independent.
7. The method according to claim 1, in, The at least one resource is a management resource, and the at least one resource is a managed resource.
8. The method of claim 1, wherein the one or more isolation groups are root isolation groups, or the one or more isolation groups are contained by another isolation group.
9. The method according to claim 8, in, The isolation level of the containing isolation group is stricter than the isolation level of the contained isolation group.
10. The method according to claim 8, further comprising: include: Isolation is determined for the at least one resource of a service by examining isolation profiles containing isolation groups until all isolation groups in a chain of containing isolation groups including the root isolation group are addressed or considered.
11. The method according to claim 1, further comprising: include: Isolation is determined for the at least one service by examining isolation profiles of linked isolation groups until a plurality of resource types are addressed.
12. The method according to claim 1, in, When the resources of the services are specified in a common isolation group, the resources of the services specified in the isolation group are shared without isolation; as well as Wherein, when the resources of the service are further specified in different isolation groups within the common isolation group, the resources of the service specified in the isolation group are shared in isolation.
13. A device, include: at least one processor; as well as at least one non-transitory memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least perform: specifying or creating one or more isolation groups for at least one service, wherein resources of the services specified in the isolation groups are shared with or without isolation; wherein an isolation group is defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service; linking an isolation profile for each of the one or more isolation groups, wherein the isolation profile comprises at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile comprises at least an isolation level for defining an isolation type; and The at least one resource is allocated or reallocated to the at least one service based on the isolation profile linked to the one or more isolation groups.
14. The device according to claim 13, in, The isolation group is defined based on a type of the at least one resource and a service characteristic supported by the at least one resource.
15. The device according to claim 13, in, Based on the isolation profile, resources allocated to a service are physically or logically isolated from resources of other services specified in different isolation groups.
16. The device according to claim 13, in, The one or more isolation groups are specified or created by a service consumer or a service producer.
17. The device according to claim 13, in, The isolation level is physical or logical isolation.
18. The device according to claim 13, in, The isolation profile may be associated with a service profile for a supported service or may be independent.
19. The device according to claim 13, in, The at least one resource is a management resource, and the at least one resource is a managed resource.
20. The device according to claim 13, in, The one or more isolation groups are root isolation groups, or the one or more isolation groups are contained by another isolation group.
21. The device according to claim 20, in, The isolation level of the containing isolation group is stricter than the isolation level of the contained isolation group.
22. The device according to claim 20, in, The at least one memory and the computer program code are also configured to, together with the at least one processor, cause the apparatus to at least perform: determining isolation for the at least one resource of a service by: checking isolation profiles containing isolation groups until all isolation groups in the chain of containing isolation groups including the root isolation group are addressed or considered.
23. The device according to claim 13, in, The at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least perform: determining isolation for the at least one service by checking isolation profiles of the linked isolation group until a plurality of resource types are addressed.
24. The device according to claim 13, in, When the resources of the services are specified in a common isolation group, the resources of the services specified in the isolation group are shared without isolation; as well as Wherein, when the resources of the service are further specified in different isolation groups within the common isolation group, the resources of the service specified in the isolation group are shared in isolation.
25. A non-transitory program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform operations, the operations include: specifying or creating one or more isolation groups for at least one service, wherein resources of the services specified in the isolation groups are shared with or without isolation; wherein an isolation group is defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service; linking an isolation profile for each of the one or more isolation groups, wherein the isolation profile comprises at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile comprises at least an isolation level for defining an isolation type; and The at least one resource is allocated or reallocated to the at least one service based on the isolation profile linked to the one or more isolation groups.
26. The non-transitory program storage device of claim 25, in, The isolation group is defined based on a type of the at least one resource and a service characteristic supported by the at least one resource.
27. The non-transitory program storage device of claim 25, in, Based on the isolation profile, resources allocated to a service are physically or logically isolated from resources of other services specified in different isolation groups.
28. The non-transitory program storage device of claim 25, in, The one or more isolation groups are specified or created by a service consumer or a service producer.
29. The non-transitory program storage device of claim 25, in, The isolation level is physical or logical isolation.
30. The non-transitory program storage device of claim 25, in, The isolation profile may be associated with a service profile for a supported service or may be independent.
31. The non-transitory program storage device of claim 25, in, The at least one resource is a management resource, and the at least one resource is a managed resource.
32. The non-transitory program storage device of claim 25, in, The one or more isolation groups are root isolation groups, or the one or more isolation groups are contained by another isolation group.
33. The non-transitory program storage device of claim 32, in, The isolation level of the containing isolation group is stricter than the isolation level of the contained isolation group.
34. The non-transitory program storage device of claim 32, in, The operations further include determining isolation for the at least one resource of a service by examining isolation profiles containing isolation groups until all isolation groups in a chain of containing isolation groups including the root isolation group are addressed or considered.
35. The non-transitory program storage device of claim 25, in, The operations further include determining isolation for the at least one service by examining isolation profiles of the linked isolation groups until a plurality of resource types are addressed.
36. The non-transitory program storage device of claim 25, in, When the resources of the services are specified in a common isolation group, the resources of the services specified in the isolation group are shared without isolation; as well as Wherein, when the resources of the service are further specified in different isolation groups within the common isolation group, the resources of the service specified in the isolation group are shared in isolation.
37. A device, include: means for specifying or creating one or more isolation groups for at least one service, wherein resources of the services specified in the isolation groups are shared with or without isolation; wherein an isolation group is defined for at least one resource in each layer and each domain to aggregate the at least one resource of the at least one service; means for linking an isolation profile for each of the one or more isolation groups, wherein the isolation profile comprises at least one policy for protecting the at least one resource of the one or more isolation groups, and wherein the isolation profile comprises at least an isolation level for defining an isolation type; and Means for allocating or reallocating the at least one resource to the at least one service based on the isolation profile linked to the one or more isolation groups.
38. The device according to claim 37, in, The isolation group is defined based on a type of the at least one resource and a service characteristic supported by the at least one resource.
39. The device according to claim 37, in, Based on the isolation profile, resources allocated to a service are physically or logically isolated from resources of other services specified in different isolation groups.
40. The device according to claim 37, in, The one or more isolation groups are specified or created by a service consumer or a service producer.
41. The device according to claim 37, in, The isolation level is physical or logical isolation.
42. The device according to claim 37, in, The isolation profile may be associated with a service profile for a supported service or may be independent.
43. The device according to claim 37, in, The at least one resource is a management resource, and the at least one resource is a managed resource.
44. The device according to claim 37, in, The one or more isolation groups are root isolation groups, or the one or more isolation groups are contained by another isolation group.
45. The device according to claim 44, in, The isolation level of the containing isolation group is stricter than the isolation level of the contained isolation group.
46. The device according to claim 44, further comprising: include: Means for determining isolation for the at least one resource of a service by examining isolation profiles containing isolation groups until all isolation groups in a chain of containing isolation groups including the root isolation group are addressed or considered.
47. The device according to claim 37, further comprising: include: Means for determining isolation for the at least one service by examining isolation profiles of the linked isolation groups until a plurality of resource types are addressed.
48. The device according to claim 37, in, When the resources of the services are specified in a common isolation group, the resources of the services specified in the isolation group are shared without isolation; as well as Wherein, when the resources of the service are further specified in different isolation groups within the common isolation group, the resources of the service specified in the isolation group are shared in isolation.
