Patent Description:
The concept of network slice or network slicing is introduced in fifth generation, <NUM>, communication systems in order to address the various requirements from multiple vertical industries assuming a shared network infrastructure. Correspondingly, network services can be customized based on the requirements of different use cases, thereby increasing the network operation efficiency.

The Network slicing concept is expected to be one of the key features in the 5th Generation mobile technology (<NUM>) which will be deployed by <NUM>. Network slicing enables <NUM> mobile telecommunications system to integrate vertical industries by providing a service-tailored network function provisioning scheme.

The network slicing concept is not limited to one single operator network. Network services offered by a service provider can be composed of multiple network slices, which again can be allocated across multiple or different operator networks. Each operator network is based on a proprietary identification management. Therefore, the service provider does not have a simple end-to-end management process in case of a failure or a modification of a network resource in anyone of the multiple operator networks. Based on the complex slicing architecture across multiple operators it is difficult for the service provider to easily detect a failure of a network resource or a modification of a network resource.

D1 (<CIT> & <CIT>) discloses a method and an apparatus for on-boarding network service descriptor. The method includes: receiving, by a primary orchestrator, a cross-domain network service descriptor NSD on-boarding command from a sender; determining, by the primary orchestrator according to the cross-domain NSD on-boarding command, that a secondary orchestrator needs to on-board an NSD corresponding to a management domain of the secondary orchestrator; and sending, by the primary orchestrator, an NSD on-boarding command to the secondary orchestrator, where the NSD on-boarding command is used to instruct the secondary orchestrator to on-board the NSD corresponding to the management domain of the secondary orchestrator, and a management domain of the primary orchestrator is different from the management domain of the secondary orchestrator.

D2 (<CIT> & <CIT>) discloses a life cycle management method and device for a network service. The method includes: determining, by a second device according to a target NS, an existing VNF instance required for life cycle management on the target NS; sending, by the second device, a life cycle management request of the target NS to a first device, where the life cycle management request includes a mapping relationship between an identifier of the existing VNF instance and a characteristic parameter corresponding to the identifier; and receiving, by the first device, the life cycle management request sent by the second device for the target NS, and performing life cycle management on the target NS according to the existing VNF instance and the mapping relationship.

D3 (<CIT>) discloses a slice management system and a slice management method that can dynamically adjust the amount of resources when the amount of resources is insufficient to create a slice. A storing unit of a NFVO stores slice utilization status information. In a BSS/OSS, an allocation determination unit determines to create a new slice or extend an existing slice, and when resources for creation of a new slice or extension of an existing slice are insufficient, a resource change determination unit determines a slice for reduction based on the slice utilization status information. A resource request unit of the NFVO reduces resources of the determined slice.

D4 (<CIT>) discloses a service processing method, device, and system, where service expansion can be performed without changing an original device of an operator. A service processing method includes acquiring business service information corresponding to a to-be-processed service flow, where the business service information includes a service flow identifier of the to-be-processed service flow and a service label corresponding to the service flow identifier. The method includes sending the business service information corresponding to the to-be-processed service flow to a service router, so that the service router processes, according to the business service information, the to-be-processed service flow.

D5 (<NPL>) technical report about study on architecture for Next Generation System and discloses details on network slicing, network services and identifiers.

D6 (<CIT>) cited under Art. <NUM>(<NUM>) EPC and discloses a network management method, a network slice selection function, a network slice management and orchestration, and a network system, to enable an NSSF to have a function of selecting a network slice instance and/or network slice subnet instance for S-NSSAI of UE.

D7 (<NPL>) as well as D8 (<NPL>, XP051348998) both disclose a use case, where a network slice management function should be able to satisfy a request to create a network slice instance.

Having recognized the above-mentioned disadvantages and problems, the present invention aims to improve the state of the art. In particular, an object of the present invention is to provide a network entity and a method for improving identifier allocation and/or identifier mapping of network services.

The above-mentioned object is achieved by the features of the independent claims. Further embodiments of the invention are apparent from the dependent claims, the description and the figures.

According to a first aspect, the invention relates to a network entity on a service layer for identifier allocating and/or identifier mapping of network services, the network entity is configured to receive at least one identifier of a network service, generate at least one further identifier of a further network service, and map the further identifier to at least one received identifier.

Thereby, the network entity advantageously enables a dynamic identification scheme for slices. The advantage of generating a further identifier, in particular a local identifier, is to support an efficient scalability of the slicing concept. It also advantageously supports resilience features, in particular enhancing fault tolerance in case of a local failure or local change of network services. Further, this network entity advantageously improves abstraction features, in particular of the slice or network slice during its life cycle. Further, this network entity has the advantage to hide the further, in particular local, identifiers from the identifiers from other network services.

A network service is defined as a managed entity offered by an operator or service provider including a service level agreement. A network service could include a <NUM> communication service, a slice, part of a slice, a network function, or an infrastructure.

In particular, a further network service comprises a further managed network service.

A service layer can be a service layer, a network slice instance layer, a network subnet slice instance layer or an infrastructure layer in a management function architecture.

According to a first implementation of the network entity according to the first aspect, the network entity is further configured to send the at least one further identifier to at least one second network entity for identifier allocating and/or identifier mapping.

Thereby, the resilience and abstraction features of the end to end identification management is advantageously improved and simplified.

According to a second implementation of the network entity according to the first aspect, the network entity is located on a first service layer and the second network entity is located on a second service layer.

According to a third implementation of the network entity according to the first aspect, the first service layer is an upper service layer compared to the second service layer.

Thereby, the allocating and/or identifier mapping procedure is advantageously enabled from an upper layer to a lower layer in a top-down mapping process. Further, the slicing management across different layers is more dynamic than a central slice management. Top-down mapping is defined as mapping identifiers starting from an upper service layer to a lower service layer.

According to a fourth implementation of the network entity according to the first aspect, the first service layer is a lower service layer compared to the second service layer.

Thereby, the slicing management across different layers is more dynamic than a central slice management. Further, the allocating and/or identifier mapping procedure is advantageously enabled from a lower layer to an upper layer in a bottom-up mapping process. Bottom-up mapping is defined as mapping identifiers starting from a lower service layer to an upper service layer.

According to a fifth implementation of the network entity according to the first aspect, the network entity is located on a first service layer and the second network entity is located on a second service layer, wherein the first service layer is the same service layer as the second service layer.

Thereby, an identifier allocating and/or mapping on the same service layer or a horizontal mapping of identifiers is advantageously enabled. Further, it is also possible, that each service layer is managed or controlled by a different network management function. Furthermore, the first network entity can be located in a different operator network then the second network entity.

According to a sixth implementation of the network entity according to the first aspect, the received identifier is a service instance ID (S-ID) and the at least one further identifier is a network service instance ID (NS-ID) or the received identifier is a network service instance ID (NS-ID) and the at least one further identifier is a network slice instance ID (NSI-ID) or the received identifier is a network slice instance ID (NSI-ID) and the at least one further identifier is a network subnet slice instance ID (NSSI-ID) or the received identifier is a network subnet slice instance ID (NSSI-ID) and the at least one further identifier is at least one infrastructure resource instance ID.

Thereby, the allocating and/or identifier mapping procedure is advantageously enabled end-to end across the layers in a top-down mapping process.

According to a seventh implementation the network entity according to the first aspect, the received identifier is the at least one infrastructure resource instance ID and the at least one further identifier is the network subnet slice instance ID (NSSI-ID) or the received identifier is the at least one network subnet slice instance ID (NSSI-ID) and the at least one further identifier is the network slice instance ID (NSI-ID) the received identifier is the at least one network slice instance ID (NSI-ID) and the at least one further identifier is the network service instance ID (NS-ID) or the received identifier is the at least one network service instance ID (NS-ID) and the at least one further identifier is the service instance ID (S-ID).

Thereby, the allocating and/or identifier mapping procedure is advantageously enabled end-to end across the layers in a bottom up mapping process.

According to an eighth implementation of the network entity according to the first aspect, the mapping of the at least one further identifier to the at least one received identifier is based on a hashing mechanism.

Thereby, advantageously using identifier mapping in the network entity, in particular the local mapping component. Hashing has the advantage of retrieving the mapped identifiers in an efficient and fast way.

According to a ninth implementation of the network entity according to the first aspect, the network entity is further configured to store the mapping of the at least one further identifier to the received identifier.

Thereby, decentralized storage of the generated further identifier is advantageously improving the scalability and speed of the end-to-end identifier allocating and/or identifier mapping process.

According to a tenth implementation of the network entity according to the first aspect, the network entity comprises at least one data base for storing mapped identifiers, wherein at least one database comprises an interface for controlling identifiers.

Thereby, the local storage of allocated and/or mapped identifiers, in particular keys as received identifiers and associated values as further or local identifiers advantageously enable a fast and direct access.

According to a eleventh implementation of the network entity according to the first aspect, the network entity comprises an interface for sending the at least one further identifier of the further network service according to the first implementation of the network entity according to a first aspect or for receiving the at least one identifier of the network service according to the network entity according to the first aspect.

Thereby, this interface advantageously enables a bidirectional communication between the network entities for identifier mapping, in particular local mapping components. The interface supports a standardized communication between the local mapping components within technological domains owned by a single administrative domain or across technological domains owned by multiple administrative domains.

An administrative domain refers to a collection of systems and networks each operated by a single organization or administrative authority, such as an operator according to ETSI GS NFV-MAN <NUM> V1.

Considering an operator network, technological domains can be defined as systems or networks which have technically similar management attributes which could be the same vendor and the same technology such as a core network or access network or transport network or data centre networks.

According to a twelfth implementation of the network entity according to the first aspect, the network entity is attached to a network management function, wherein the network management function is responsible to manage to the same service layer as the network entity.

Thereby, the controlling of the local mapping of different network services is advantageously managed on the respective level improving the scalability and resilience of the managed slice or managed entity.

According to a thirteenth implementation of the network entity according to the first aspect, the network entity is further configured to allocate a generated further identifier to a new further network service or use the at least one further identifier of the further network service, and in case of using the at least one further identifier, send the allocated further identifier to the at least one second network entity for identifier allocating and/or identifier mapping.

The resilience of the end to end identification management is advantageously enhanced.

According to a fourteenth implementation of the network entity according to the first aspect, the network entity is further configured to replace the first received identifier by the new received identifier.

Thereby, the fault tolerance is advantageously reduced.

According to a fifteenth implementation of the network entity according to the first aspect, wherein in case a mapping is required for the single network slice selection assistance information (NSSAI) of a user equipment, the entity is further configured to generate the further identifier of the further network service, wherein the further network service is a service instance (NS) or a network slice instance (NSI) or network slice subnet instance (NSSI).

Thereby, the identification management for user equipment (UE) requesting to a service is advantageously enabled. Particularly, the mapping between the user equipment request (i.e., S-NSSAI) and an exposed service is advantageously enabled and also improves the identification management on different layers of slice management functions and their assigned network entities for identifier mapping, in particular their local mapping components.

According to a second aspect, the invention relates to a method, at a network entity on a service layer for identifier allocating and/or identifier mapping of network services, the method comprises the following steps of receiving at least one identifier of a network service, generating at least one further identifier of a further network service, and mapping the further identifier to at least one received identifier.

Thereby, the method advantageously enables a dynamic identification scheme for slices. The advantage of generating a further identifier, in particular a local identifier, is to support an efficient scalability of the slicing concept. It also advantageously supports resilience features, in particular enhancing fault tolerance in case of a local failure or local change of network services. Further, this method advantageously improves abstraction features, in particular of the slice or network slice during its life cycle. Further, this method has the advantage to hide the further, in particular local, identifiers from the identifiers from other network services.

According to a first implementation of the method according to the second aspect, the method comprises the further following step of sending the at least one further identifier to at least one second network entity for identifier allocating and/or identifier mapping.

Thereby, the resilience of the method is advantageously improved. Further, the fault risk of missing or wrong identifiers is advantageously reduced.

According to a second implementation of the method according to the second aspect, the network entity is located on a first service layer and the second network entity is located on a second service layer.

According to a third implementation of the method according to the second aspect, the first service layer is an upper service layer compared to the second service layer.

According to a fourth implementation of the method according to the second aspect, the first service layer is a lower service layer compared to the second service layer.

According to a further implementation of the network entity according to the first aspect, the network entity is located on a first service layer and the second network entity is located on a second service layer, wherein the first service layer is the same service layer as the second service layer.

According to a fifth implementation of the method according to the second aspect, the received identifier is a service instance ID (S-ID) and the at least one further identifier is a network service instance ID (NS-ID) or the received identifier is a network service ID (NS-ID) and the at least one further identifier is a network slice instance ID (NSI-ID) or the received identifier is a network slice instance ID (NSI-ID) and the at least one further identifier is a network subnet slice instance ID (NSSI-ID) or the received identifier is a network subnet slice instance ID (NSSI-ID) and the at least one further identifier is at least one infrastructure resource instance ID.

According to a sixth implementation of the method according to the second aspect, the received identifier is the at least one infrastructure resource instance ID and the at least one further identifier is the network subnet slice instance ID (NSSI-ID) or the received identifier is the network subnet slice instance ID (NSSI-ID) and the at least one further identifier is the network slice instance ID (NSI-ID) the received identifier is the network slice instance ID (NSI-ID) and the at least one further identifier is the network service instance ID (NS-ID) or the received identifier is the network service instance ID (NS-ID) and the at least one further identifier is the service instance ID (S-ID).

According to a seventh implementation of the method according to the second aspect, the mapping of the at least one further identifier to the at least one received identifier is based on a hashing mechanism.

According to an eighth implementation of the method according to the second aspect, the method comprises the following step of storing the mapping of the at least one further identifier to the received identifier.

According to a ninth implementation of the method according to the second aspect, the network entity comprises at least one data base for storing mapped identifiers, wherein at least one database comprises an interface for controlling identifiers.

According to a tenth implementation of the method according to the second aspect, the network entity comprises an interface for sending the at least one further identifier of the further network service according to the first implementation of the network entity according to a first aspect or for receiving the at least one identifier of the network service according to the network entity according to the first aspect.

Thereby, this interface advantageously enables a bidirectional communication between the network entities for identifier mapping, in particular local mapping components. The interface supports a standardized communication between the local mapping components within a technological domain or across technological or administrative domains.

According to an eleventh implementation of the method according to the second aspect, the network entity is attached to a network management function, wherein the network management function is assigned to the same service layer as the network entity.

According to a twelfth implementation of the method according to the second aspect, the method comprises the following further steps of allocating a generated further identifier to a new further network service or use the at least one further identifier of the further network service, and in case of using the at least one further identifier, sending the allocated identifier to the at least one second network entity for identifier allocating and/or identifier mapping.

According to a thirteenth implementation of the method according to the second aspect, the network entity is further configured to replace the first received identifier by the new received identifier.

According to a fourteenth implementation of the method according to the second aspect for end to end identification management for a slice, the slice is configured across multiple technological domains.

According to a fifteenth implementation of the method according to the second aspect the multiple technological domains are located in a single operator or across multiple operators.

More specifically, it should be noted that the above apparatuses may be implemented based on a discrete hardware circuitry with discrete hardware components, integrated chips or arrangements of chip modules, or based on a signal processing device or chip controlled by a software routine or program stored in a memory, written on a computer-readable medium or downloaded from a network such as the internet.

It shall further be understood that a preferred embodiment of the invention can also be any combination of the dependent claims or above embodiments with the respective independent claim.

These and other aspects of the invention will be apparent and elucidated with reference to the embodiments described hereinafter.

The above aspects and implementation forms of the present invention will be explained in the following description of specific embodiments in relation to the enclosed drawings, in which.

<FIG> shows two network entities <NUM>, <NUM> for identifier allocating and/or identifier mapping of network services. Each network entity <NUM>, <NUM> is located on a service layer in the communication system.

The network entity <NUM>, in particular a local mapping component <NUM>, comprises a mapping function <NUM>, in particular a local mapper <NUM>, two databases 107a, 107b for storing identifiers and at least one interface <NUM> for accessing the databases 107a, 107b. Optionally, the network entity <NUM> comprises only one interface <NUM> for accessing multiple databases 107a, 107b. Further, the network entity <NUM> comprises an external interface <NUM>, in particular ID management interface <NUM>, for sending at least one further identifier of the network service or for receiving at least one identifier of the network service.

The external interface <NUM>, in particular an ID management interface <NUM> is a bidirectional interface and configured to exchange local identifier related information. This external interface <NUM> enables communication between the network entities <NUM>, <NUM>. Further, the external interface <NUM> is adapted to support a cross- domain operation at any service layer. A local identifier is an identifier indicating a corresponding managed entity, for example a network slice instance and is generated by the network entity <NUM>, <NUM>.

The second network entity <NUM> comprises a mapping function <NUM>, a database <NUM> for storing identifiers and one interface <NUM> for accessing the database <NUM>.

The network entity <NUM>, <NUM> on the service layer for identifier allocating and/or identifier mapping of network services is configured to receive the at least one identifier of the network service, generate at least one further identifier of a further network service, and map the further identifier to at least one received identifier.

<FIG> shows a schematic diagram of a mapping according to an embodiment of the present invention.

In this embodiment, multiple network entities <NUM>, <NUM>, <NUM>, <NUM>, <NUM> for identifier allocating and/or identifier mapping of network services are shown.

The first network entity <NUM> comprises a service mapper <NUM> and is located on the customer service layer (CS). The second network entity <NUM> comprises a network service mapper <NUM> and is assigned to the network service layer (NS), the third network entity <NUM> comprises a network slice instance mapper <NUM> and is assigned to the network slice instance layer, the fourth network entity <NUM> comprises a network subnet slice instance mapper <NUM> and is assigned to the network subnet slice instance layer and the fifth network entity <NUM> comprises an infrastructure mapper <NUM> and is assigned to the infrastructure resources layer.

Triggered by a service request from a customer the end to end interaction of these network entities, in particular local mapping components, runs as follows:
In step <NUM>, the service mapper <NUM> of the first network entity <NUM> creates a service with an associated service identifier. The service identifier (S-ID) is generated by the first network entity <NUM>, in particular by the service mapper <NUM>. The network entity <NUM> stores the service identifier in a database <NUM>. Assuming that the service is composed of a single network service and a top-down mapping is considered between the network entity <NUM> and <NUM>, the service mapper <NUM> will connect to the responsible network service mapper <NUM> (NS mapper). The identifier (S-ID) is sent via an interface <NUM>, in particular identifier management interface, to the network service mapper <NUM>. The network service mapper <NUM> receives the actual service identifier and generates a local identifier, in particular a local network service identifier (NS-ID), maps the received identifier (S-ID) with the local identifier (NS-ID) and stores the mapping in a database 217a. In the case of a bottom-up mapping between the network entity <NUM> and <NUM>, a request will be initiated from the management function of the network entity <NUM> to the management function of the network entity <NUM>. Then the NS mapper <NUM> generates local identifier(s) (NS-IDs) and the local identifier(s) is sent to the service mapper <NUM> via the interface <NUM>. After a successfully receiving of the identifier(s) (NS-IDs) the service mapper <NUM> maps the identifier(s) (NS-IDs) with its local ID (S-ID) and stores in the corresponding database <NUM>.

In step <NUM>, the network service mapper <NUM> will create a database entry at a database 217b for mapping the network service identifier and the corresponding network slice instance identifier if a bottom-up mapping is considered between the NS mapper <NUM> and the NSI mapper <NUM>. The network service mapper <NUM> will request the network slice instance identifier(s) from the corresponding network slice instance mapper <NUM>. The network slice instance mapper <NUM> of the network entity <NUM> will generate and send the local identifier (NSI-ID) to the network service mapper <NUM> via an interface <NUM>. After a successful sending of the identifier(s) (NSI IDs) the network service mapper <NUM> maps the identifier(s) in the database 217b of the network entity <NUM>.

In step <NUM> the same procedures take place between the network slice instance mapper (NSI mapper) <NUM> and the network subnet slice instance mapper (NSSI mapper) <NUM>. The NSSI mapper <NUM> generates the local network subnet slice instance identifier or in case of multiple network subnet slice instances multiple identifiers for the received network slice instance identifier and stores the mapping in the database 227b (NSMF DB) of the network entity <NUM> if a top-down mapping is considered. Otherwise, the requested NSSI-ID(s) will be sent to the network slice instance mapper via an interface <NUM>. Then the network slice instance mapper (NSI mapper) maps the NSSI-ID to its local NSI-ID and stores in the database 227a.

In step <NUM>, which is similar to steps <NUM> to <NUM>, an infrastructure mapper generates local identifiers for the constituents of the network subnet slice instance, such as one or multiple network functions (NF) which can be either virtual or physical NF, one or multiple virtual network function links (VNL) or one or multiple virtual subnet links (VSL). If the infrastructure mapper <NUM> receives the NSSI-ID from the network slice subnet instance mapper <NUM>, the infrastructure mapper <NUM> maps and stores the mapping of the identifiers in the local databases 247a, 247b, 247c for the corresponding values. If the infrastructure mapper <NUM> receives a request for the resources ID from the network slice subnet instance mapper <NUM>, the infrastructure mapper <NUM> sends the local identifiers of the constituents of the network subnet slice instance to the NSSI mapper <NUM>. The mapping of the network subnet slice instance identifier to its constituents will be stored in the database 237b of the network entity <NUM>.

Each network entity <NUM>, <NUM>, <NUM>, <NUM>, <NUM> is attached to a management function <NUM>, <NUM>, <NUM>, <NUM>, <NUM> of the corresponding service layer. The management function <NUM>, <NUM>, <NUM>, <NUM>, <NUM> controls the interactions of the network entities <NUM>, <NUM>, <NUM>, <NUM>, <NUM> on the different service layers. The network entities <NUM>, <NUM>, <NUM> comprises two databases for mapping the managed entities of the upper and lower service layer in case of top-down-mapping or bottom up-mapping.

In a further case a hybrid mapping is considered, in which a combination of top-down and bottom-up mapping occurs at any service layer.

In a first step the NSI mapper <NUM> receives a network service identifier (NS-ID) from the NS mapper <NUM>. The NSI mapper <NUM> generates a local identifier, in particular a local network service identifier (NS-ID), maps the received identifier (S-ID) with the local identifier (NS-ID) and stores the mapping in the database 227a in case of a top-down mapping.

In case of a bottom-up mapping between the network entity <NUM> and <NUM>, a request will be initiated from the management function of the network entity <NUM> to the management function of the network entity <NUM>. Then the NSI mapper <NUM> receives at least one local identifier from the NSSI mapper <NUM> and the NSI mapper <NUM> maps the identifier(s) (NSI-IDs) with its local ID (NSI-ID) and stores in the corresponding database <NUM>.

<FIG> shows a user equipment <NUM>, an entity <NUM> and three network entities <NUM>, <NUM>, <NUM>.

The entity <NUM> comprises a mapping function <NUM>. The mapping function <NUM> is a S-NSSAI mapper. Further, the entity comprises three databases 307a, 307b, 307c. Each database is accessible via an internal interface 305a, 305b 305c. The entity <NUM> further comprises an identifier management interface <NUM>.

In this embodiment, in case mapping is required for the single network slice selection assistance information (NSSAI) of a user equipment <NUM>, the entity <NUM> is configured to generate a further identifier of a further network service, wherein the further network service is the service instance (NS) or a network slice instance (NSI) or a network slice subnet instance (NSSI).

In case, where a service is exposed on a network service layer the local mapping of identifiers takes place between the mapping function <NUM>, in particular the S-NSSAI mapper <NUM> and a network service mapper <NUM> of the network entity <NUM>.

In case, where the service is exposed on a network slice instance layer the local mapping of identifiers takes place between the mapping function <NUM> and a network slice instance mapper <NUM> of the network entity <NUM>.

In case whether service is exposed on a network subnet slice instance layer the local mapping of identifiers takes place between the mapping function <NUM> and a network subnet slice instance mapper <NUM> of the network entity <NUM>.

<FIG> shows a schematic overview regarding end-to end-service identification management according to an embodiment of the present invention.

<FIG> shows a network service management function architecture <NUM> and the network service managed entity architecture <NUM>. Each architecture comprises a layered structure. The first layer is the network service layer <NUM>, the second layer is the network slice instance layer <NUM>, the third layer is the network slice subnet layer <NUM> and the fourth layer is the infrastructure layer <NUM>.

In the service management function architecture <NUM> each layer <NUM>, <NUM>, <NUM>, <NUM> comprises at least one management function <NUM>, 412a, 412b, 413a, 413b, 424a, 414b, 415a, 415b. For example, a network slice management function 413a is located on the network slice instance layer <NUM>.

In the network service managed entity architecture <NUM> each layer <NUM>, <NUM>, <NUM>, <NUM> comprises a managed entity <NUM>, 423a, 423b, 424a, 424b, 425a, 425b. The managed entity is a network service <NUM>, a network slice instance 423a, 423b, a network slice subnet instance 424a, 424b and a network function (NF), 425a, 425b or a virtual subnet link VSL, 425a, 425b or a virtual network function link VNL, 425a, 425b.

The layered structure of each architecture <NUM>, <NUM> can be divided across multiple operators (administrative domains) or across multiple technical domains.

An administrative domain refers to a collection of systems and networks each operated by a single organisation or administrative authority, such as an operator according to ETSI GS NFV-MAN <NUM> V1.

Further, a cross-domain operation may occur at any layer of the network service management function architecture or at any layer of the network service managed entity architecture.

Furthermore, in case of a service mapping across administrative domains, this takes place between a management function in a first operator network and a management function in a second operator network. Each management function is assigned to the same layer <NUM>, <NUM>, <NUM>, <NUM>.

<FIG> shows a schematic diagram regarding business roles according to an embodiment of the present invention.

In this embodiment, <FIG> shows the different business roles, management functions and managed entities in a layered structure.

On the first service layer <NUM> the different business roles like end user <NUM>, customer <NUM>, service provider <NUM>, slice provider <NUM>, partial slice provider <NUM> and infrastructure provider <NUM> are shown.

On the second service layer <NUM> the different management functions <NUM>, <NUM>, <NUM>, <NUM>, <NUM> are shown. A management function can be the service management function (SMF) <NUM>, a customer service management function <NUM>, and network slice management function <NUM>, network slice subnet management function <NUM>, and an infrastructure management function <NUM>. The second service layer is assigned to the management plane in a communication system.

On the third service layer <NUM> the different managed entities (NS, NSI, NSSI, NF, VSL, VNL) managed by the respective management functions of the second service layer are shown. The third service layer is assigned to the data plane in a communication system.

A customer <NUM> has to be understood as a business or company offering services to other third party customers or end-users and subscribing services to other third party customers or end-users. Further, this customer purchases the services to at least one service provider. For example, a service provider is an operator.

The at least one service provider <NUM> purchases a slice to at least one slice provider <NUM>.

The at least one slice provider <NUM> purchases parts of the slice or partial slices to at least one partial slice providers <NUM>.

The partial slice provider <NUM> purchases resources, in particular compute resources, storage resources and networking resources from at least one infrastructure provider <NUM>.

For example, the infrastructure provider <NUM> can be the operator owning the physical components of his network or the infrastructure provider <NUM> can be a business offering special components for storing, for example a data warehouse infrastructure provider.

<FIG> also shows a scenario in which a customer <NUM>, for example an automotive company or automotive industry, purchases a service from a service provider <NUM>, for example an operator. The service is composed of one or more network services, where in each network service is composed of one or more network slices.

After receiving a service request from the automotive industry or company the operator creates a service associated with a service identifier. In this embodiment, the service is composed of a single network service. Therefore, the operator creates and identifies the network service (NS). Further, assuming that the network service is also composed of one network slice, the operator creates the network slice instance and generates a network slice instance identifier. The operator will generate a different identifier if the same customer or another customer purchases the same service, network service or network slice request. It is also possible to have a service, which is composed of multiple network services and these services are composed of multiple network slice instances. Furthermore, these different scenarios are possible in a single operator network or across multiple network operators.

In a further embodiment of <FIG> an example scenario is a Platooning service according to 3GPP TS <NUM> v15. <NUM>, Enhancement of 3GPP support for V2X (Vehicle-to-Vehicle or Vehicle-to-Infrastructure) scenarios. One scenario requires multiple network services such as cooperative driving for vehicle platooning and information sharing for platooning between user equipment <NUM> (UE) supporting a V2X application and a road side unit (RSU). This network service is offered by a service provider <NUM> or a customer <NUM>. The first part of the network service for cooperative driving for vehicle platooning may require one or multiple network slice(s) (NSI) for cooperative driving. The second part of the network service for information sharing for platooning between user equipment <NUM> (UE) supporting the V2X application and the RSU may require at least a network slice instance (NSI) for URLCC (Ultra-Reliable and Low Latency Communication) , which is defined by 3GPP TS <NUM> v0. <NUM>, "System Architecture for the <NUM> System".

<FIG> shows a schematic flow diagram of a method according to an embodiment of the present invention.

In this embodiment, a hash table based identifier mapping is shown. The hashing mechanism is usable in each database of a network entity according to the present invention.

Hashing is used to index and retrieve items in a database by using hash keys to find the corresponding value. For example, in the database of the third network entity of <FIG> in which the network slice instance identifier (NSI-ID) is used as a key, the values of the composed network subnet slice instances can be retrieved as shown in <FIG>. In the database 237b of the fourth network entity <NUM> of <FIG> (NSSMF-DB) using the network subnet slice identifier as a key the corresponding infrastructure identifier (NF-ID, VNL-ID) can be retrieved.

Hash-based identifier mapping can be used to support the identifier allocation and identifier mapping method in the network entity, in particular in the local mapper.

While the invention has been illustrated and described in detail in the drawings and the foregoing description, such illustration and description are to be considered illustrative or exemplary and not restrictive. From reading the present disclosure, other modifications will be apparent to a person skilled in the art. Such modifications may involve other features, which are already known in the art and may be used instead of or in addition to features already described herein.

Claim 1:
Network entity (<NUM>) on a service layer for identifier allocating and/or identifier mapping of network services,
wherein the network entity (<NUM>) is configured to:
- receive a first identifier of a first network service,
- generate a second identifier of a second network service, and
- map the second identifier to the first identifier;
wherein one of the first identifier and the second identifier is a network slice instance ID, NSI-ID,
wherein the network entity (<NUM>) is further configured to:
- send the second identifier to a second network entity for identifier allocating and/or identifier mapping.