WO2021068207A1

WO2021068207A1 - Apparatus, method and computer program

Info

Publication number: WO2021068207A1
Application number: PCT/CN2019/110643
Authority: WO
Inventors: Olaf Pollakowski; Jing PING; Anatoly ANDRIANOV
Original assignee: Nokia Shanghai Bell Co., Ltd.; Nokia Solutions And Networks Oy
Priority date: 2019-10-11
Filing date: 2019-10-11
Publication date: 2021-04-15
Also published as: CN114514764B; CN114514764A

Abstract

There is provided an apparatus, said apparatus comprising means for receiving, at a first entity, a request from a second entity to allocate a service for the second entity, providing a request resource comprising information representative of the request to allocate a service and in response to providing the request resource, allocating the service for the second entity and providing a service resource comprising information representative of the allocated service, wherein each of the service resource and the request resource comprise an association with the other of the service resource and the request resource.

Description

APPARATUS, METHOD AND COMPUTER PROGRAM

Field

The present application relates to a method, apparatus, system and computer program and in particular but not exclusively to allocation and deallocation of resources.

Background

A communication system can be seen as a facility that enables communication sessions between two or more entities such as user terminals, base stations and/or other nodes by providing carriers between the various entities involved in the communications path. A communication system can be provided for example by means of a communication network and one or more compatible communication devices. The communication sessions may comprise, for example, communication of data for carrying communications such as voice, video, electronic mail (email) , text message, multimedia and/or content data and so on. Non-limiting examples of services provided comprise two-way or multi-way calls, data communication or multimedia services and access to a data network system, such as the Internet.

In a wireless communication system at least a part of a communication session between at least two stations occurs over a wireless link. Examples of wireless systems comprise public land mobile networks (PLMN) , satellite based communication systems and different wireless local networks, for example wireless local area networks (WLAN) . Some wireless systems can be divided into cells, and are therefore often referred to as cellular systems.

A user can access the communication system by means of an appropriate communication device or terminal. A communication device of a user may be referred to as user equipment (UE) or user device. A communication device is provided with an appropriate signal receiving and transmitting apparatus for enabling communications, for example enabling access to a communication network or communications directly with other users. The communication device may access a carrier provided by a station, for example a base station of a cell, and transmit and/or receive communications on the carrier.

The communication system and associated devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and/or parameters which shall be used for the connection are also typically defined. One example of a communications system is UTRAN (3G radio) . Other examples of communication systems are the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology and so-called 5G or New Radio (NR) networks. NR is being standardized by the 3rd Generation Partnership Project (3GPP) .

Summary

In a first aspect there is provided an apparatus comprising means for receiving, at a first entity, a request from a second entity to allocate a service for the second entity, providing a request resource comprising information representative of the request to allocate a service and in response to providing the request resource, allocating the service for the second entity and providing a service resource comprising information representative of the allocated service, wherein each of the service resource and the request resource comprise an association with the other of the service resource and the request resource.

The apparatus may comprise means for providing an indication of the association between the request resource and the service resource to the second entity.

The request resource may be periodically read by the second entity to determine the association between the request resource and the service resource.

The request resource may comprise a first pointer attribute. The service resource may comprise a second pointer attribute. The apparatus may comprise means for providing the association with the service resource in the first pointer attribute and the association with the request resource in the second pointer attribute.

The apparatus may comprise means for deleting the association between the request resource and the service resource such that the allocated service is deallocated.

The apparatus may comprise means for providing an indication of the status of the request to allocate a service to the second entity.

The information representative of the request to allocate the service may comprise at least one of second entity identity information, requested service information, information configuring service allocation request status reports and information configuring notification settings.

Means for allocating the service may comprise means for initiating a service instance or using an existing service instance.

The request to allocate a service may not include an indication of a type of service instance. The apparatus may comprise means for determining the type of service instance at the first entity.

In a second aspect there is provided an apparatus comprising means for providing a request to a first entity from a second entity to allocate a service for the second entity, the request for use in providing a request resource comprising information representative of the request to allocate a service, receiving an indication at the second entity from the first entity that the service has been allocated, determining, from the request resource, an association with a service resource and determining, from the service resource, information representative of the allocated service.

Means for receiving an indication that the service has been allocated may comprise means for receiving an indication of the association between the request resource and the service resource from the first entity at the second entity.

Means for receiving an indication that the service has been allocated may comprise means for periodically reading the request resource to determine the association between the request resource and the service resource.

The apparatus may comprise means for providing an indication to the first entity from the second entity to delete the association between the request resource and the service resource such that the allocated service is deallocated.

Means for receiving an indication that the service has been allocated may comprise means for receiving an indication of the status of the request to allocate the service from the first entity at the second entity.

The request resource may comprise a first pointer attribute. The apparatus may comprise means for determining the association with the service resource from the first pointer attribute.

In a third aspect there is provided a method comprising receiving, at a first entity, a request from a second entity to allocate a service for the second entity, providing a request resource comprising information representative of the request to allocate a service and in response to providing the request resource, allocating the service for the second entity and providing a service resource comprising information representative of the allocated service, wherein each of the service resource and the request resource comprise an association with the other of the service resource and the request resource.

The method may comprise providing an indication of the association between the request resource and the service resource to the second entity.

The request resource may comprise a first pointer attribute. The service resource may comprise a second pointer attribute. The method may comprise providing the association with the service resource in the first pointer attribute and the association with the request resource in the second pointer attribute.

The method may comprise deleting the association between the request resource and the service resource such that the allocated service is deallocated.

The method may comprise providing an indication of the status of the request to allocate a service to the second entity.

Allocating the service may comprise initiating a service instance or using an existing service instance.

The request to allocate a service may not include an indication of a type of service instance. The method may comprise determining the type of service instance at the first entity.

In a fourth aspect there is provided a method comprising providing a request to a first entity from a second entity to allocate a service for the second entity, the request for use in providing a request resource comprising information representative of the request to allocate a service, receiving an indication at the second entity from the first entity that the service has been allocated, determining, from the request resource, an association with a service resource and determining, from the service resource, information representative of the allocated service.

Receiving an indication that the service has been allocated may comprise receiving an indication of the association between the request resource and the service resource from the first entity at the second entity.

Receiving an indication that the service has been allocated may comprise periodically reading the request resource to determine the association between the request resource and the service resource.

The method may comprise providing an indication to the first entity from the second entity to delete the association between the request resource and the service resource such that the allocated service is deallocated.

Receiving an indication that the service has been allocated may comprise receiving an indication of the status of the request to allocate the service from the first entity at the second entity.

In a fifth aspect there is provided an apparatus comprising: at least one processor and at least one memory including a computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to:

receive, at a first entity, a request from a second entity to allocate a service for the second entity, provide a request resource comprising information representative of the request to allocate a service and in response to providing the request resource, allocate the service for the second entity and provide a service resource comprising information representative of the allocated service, wherein each of the service resource and the request resource comprise an association with the other of the service resource and the request resource.

The apparatus may be configured to provide an indication of the association between the request resource and the service resource to the second entity.

The request resource may comprise a first pointer attribute. The service resource may comprise a second pointer attribute. The apparatus may be configured to provide the association with the service resource in the first pointer attribute and the association with the request resource in the second pointer attribute.

The apparatus may be configured to delete the association between the request resource and the service resource such that the allocated service is deallocated.

The apparatus may be configured to provide an indication of the status of the request to allocate a service to the second entity.

The apparatus may be configured to initiate a service instance or using an existing service instance.

The request to allocate a service may not include an indication of a type of service instance. The apparatus may be configured to determine the type of service instance at the first entity.

In a sixth aspect there is provided an apparatus comprising: at least one processor and at least one memory including a computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to:

provide a request to a first entity from a second entity to allocate a service for the second entity, the request for use in providing a request resource comprising information representative of the request to allocate a service, receive an indication at the second entity from the first entity that the service has been allocated, determine, from the request resource, an association with a service resource and determine, from the service resource, information representative of the allocated service.

The apparatus may be configured to receive an indication of the association between the request resource and the service resource from the first entity at the second entity.

The apparatus may be configured to periodically read the request resource to determine the association between the request resource and the service resource.

The apparatus may be configured to providing an indication to the first entity from the second entity to delete the association between the request resource and the service resource such that the allocated service is deallocated.

The apparatus may be configured to receive an indication of the status of the request to allocate the service from the first entity at the second entity.

In a seventh aspect there is provided a computer readable medium comprising program instructions for causing an apparatus to perform at least the following receiving, at a first entity, a request from a second entity to allocate a service for the second entity, providing a request resource comprising information representative of the request to allocate a service and in response to providing the request resource, allocating the service for the second entity and providing a service resource comprising information representative of the allocated service, wherein each of the service resource and the request resource comprise an association with the other of the service resource and the request resource.

The apparatus may be caused to perform providing an indication of the association between the request resource and the service resource to the second entity.

The request resource may comprise a first pointer attribute. The service resource may comprise a second pointer attribute. The apparatus may be caused to perform providing the association with the service resource in the first pointer attribute and the association with the request resource in the second pointer attribute.

The apparatus may be caused to perform deleting the association between the request resource and the service resource such that the allocated service is deallocated.

The apparatus may be caused to perform providing an indication of the status of the request to allocate a service to the second entity.

The request to allocate a service may not include an indication of a type of service instance. The apparatus may be caused to perform determining the type of service instance at the first entity.

In an eighth aspect there is provided a computer readable medium comprising program instructions for causing an apparatus to perform at least the following providing a request to a first entity from a second entity to allocate a service for the second entity, the request for use in providing a request resource comprising information representative of the request to allocate a service, receiving an indication at the second entity from the first entity that the service has been allocated, determining, from the request resource, an association with a service resource and determining, from the service resource, information representative of the allocated service.

The apparatus may be caused to perform providing an indication to the first entity from the second entity to delete the association between the request resource and the service resource such that the allocated service is deallocated.

In a ninth aspect there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to the third or fourth aspect.

In the above, many different embodiments have been described. It should be appreciated that further embodiments may be provided by the combination of any two or more of the embodiments described above.

Description of Figures

Embodiments will now be described, by way of example only, with reference to the accompanying Figures in which:

Figure 1 shows a schematic diagram of an example communication system comprising a base station and a plurality of communication devices;

Figure 2 shows a schematic diagram of an example mobile communication device;

Figure 3 shows a schematic diagram of an example control apparatus;

Figure 4 shows a flowchart of a method according to an example embodiment;

Figure 5 shows a flowchart of a method according to an example embodiment;

Figure 6 shows a Network Resource Model according to an example embodiment.

Detailed description

Before explaining in detail the examples, certain general principles of a wireless communication system and mobile communication devices are briefly explained with reference to Figures 1 to 3 to assist in understanding the technology underlying the described examples.

In a wireless communication system 100, such as that shown in figure 1, communication devices (e.g., user equipment (UE) ) 102, 104, 105 are provided wireless access via at least one base station or similar wireless transmitting and/or receiving node or point. Base stations are typically controlled by at least one appropriate controller apparatus, so as to enable operation thereof and management of mobile communication devices in communication with the base stations. The controller apparatus may be located in a Radio Access Network (RAN) (e.g. wireless communication system 100) or in a core network (CN) (not shown) and may be implemented as one central apparatus or its functionality may be distributed over several apparatuses. The controller apparatus may be part of the base station and/or provided by a separate entity such as a radio network controller. In Figure 1

control apparatus

108 and 109 are shown to control the respective macro

level base stations

106 and 107. The control apparatus of a base station can be interconnected with other control entities. The control apparatus is typically provided with memory capacity and at least one data processor. The control apparatus and functions may be distributed between a plurality of control units. In some systems, the control apparatus may additionally or alternatively be provided in a radio network controller.

In Figure 1

base stations

106 and 107 are shown as connected to a wider communications network 113 via gateway 112. A further gateway function may be provided to connect to another network.

The

smaller base stations

116, 118 and 120 may also be connected to the network 113, for example by a separate gateway function and/or via the controllers of the macro level stations. The

base stations

116, 118 and 120 may be pico or femto level base stations or the like. In the example,

base stations

116 and 118 are connected via a gateway 111 whilst base station 120 connects via the controller apparatus 108. In some embodiments, the smaller base stations may not be provided.

Smaller base stations

116, 118 and 120 may be part of a second network, for example WLAN and may be WLAN Access Points (APs) .

The

communication devices

102, 104, 105 may access the communication system based on various access techniques, such as code division multiple access (CDMA) , or wideband CDMA (WCDMA) . Other non-limiting examples comprise time division multiple access (TDMA) , frequency division multiple access (FDMA) and various schemes thereof such as the interleaved frequency division multiple access (IFDMA) , single carrier frequency division multiple access (SC-FDMA) and orthogonal frequency division multiple access (OFDMA) , space division multiple access (SDMA) and so on.

An example of wireless communication systems are architectures standardized by the 3rd Generation Partnership Project (3GPP) . A latest 3GPP based development is often referred to as the long term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology. The various development stages of the 3GPP specifications are referred to as releases. More recent developments of the LTE are often referred to as LTE Advanced (LTE-A) . The LTE (LTE-A) employs a radio mobile architecture known as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and a core network known as the Evolved Packet Core (EPC) . Base stations of such systems are known as evolved or enhanced Node Bs (eNBs) and provide E-UTRAN features such as user plane Packet Data Convergence/Radio Link Control/Medium Access Control/Physical layer protocol (PDCP/RLC/MAC/PHY) and control plane Radio Resource Control (RRC) protocol terminations towards the communication devices. Other examples of radio access system comprise those provided by base stations of systems that are based on technologies such as wireless local area network (WLAN) . A base station can provide coverage for an entire cell or similar radio service area. Core network elements include Mobility Management Entity (MME) , Serving Gateway (S-GW) and Packet Gateway (P-GW) .

An example of a suitable communications system is the 5G or NR concept. Network architecture in NR may be similar to that of LTE-advanced. Base stations of NR systems may be known as next generation Node Bs (gNBs) . Changes to the network architecture may depend on the need to support various radio technologies and finer QoS support, and some on-demand requirements for e.g. Quality of Service (QoS) levels to support Quality of Experience (QoE) for a user. Also network aware services and applications, and service and application aware networks may bring changes to the architecture. Those are related to Information Centric Network (ICN) and User-Centric Content Delivery Network (UC-CDN) approaches. NR may use multiple input –multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept) , including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.

Future networks may utilise network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into “building blocks” or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications this may mean node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent.

An example 5G core network (CN) comprises functional entities. The CN is connected to a UE via the radio access network (RAN) . A User Plane Function (UPF) whose role is called PDU Session Anchor (PSA) may be responsible for forwarding frames back and forth between the data network (DN) and the tunnels established over the 5G towards the UE (s) exchanging traffic with the DN.

The UPF is controlled by an Session Management Function (SMF) that receives policies from a Policy Control Function (PCF) . The CN may also include an Access &Mobility Function (AMF) .

A possible mobile communication device will now be described in more detail with reference to Figure 2 showing a schematic, partially sectioned view of a communication device 200. Such a communication device is often referred to as user equipment (UE) or terminal. An appropriate mobile communication device may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a mobile station (MS) or mobile device such as a mobile phone or what is known as a ’smart phone’ , a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle) , personal data assistant (PDA) or a tablet provided with wireless communication capabilities, voice over IP (VoIP) phones, portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , smart devices, wireless customer-premises equipment (CPE) , or any combinations of these or the like. A mobile communication device may provide, for example, communication of data for carrying communications such as voice, electronic mail (email) , text message, multimedia and so on. Users may thus be offered and provided numerous services via their communication devices. Non-limiting examples of these services comprise two-way or multi-way calls, data communication or multimedia services or simply an access to a data communications network system, such as the Internet. Users may also be provided broadcast or multicast data. Non-limiting examples of the content comprise downloads, television and radio programs, videos, advertisements, various alerts and other information.

A mobile device is typically provided with at least one data processing entity 201, at least one memory 202 and other possible components 203 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The data processing, storage and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 204. The user may control the operation of the mobile device by means of a suitable user interface such as key pad 205, voice commands, touch sensitive screen or pad, combinations thereof or the like. A display 208, a speaker and a microphone can be also provided. Furthermore, a mobile communication device may comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto.

The mobile device 200 may receive signals over an air or radio interface 207 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In Figure 2 transceiver apparatus is designated schematically by block 206. The transceiver apparatus 206 may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

Figure 3 shows an example of a control apparatus 300 for a communication system, for example to be coupled to and/or for controlling a station of an access system, such as a RAN node, e.g. a base station, eNB or gNB, a relay node or a core network node such as an MME or S-GW or P-GW, or a core network function such as AMF/SMF, or a server or host. The method may be implemented in a single control apparatus or across more than one control apparatus. The control apparatus may be integrated with or external to a node or module of a core network or RAN. In some embodiments, base stations comprise a separate control apparatus unit or module. In other embodiments, the control apparatus can be another network element such as a radio network controller or a spectrum controller. In some embodiments, each base station may have such a control apparatus as well as a control apparatus being provided in a radio network controller. The control apparatus 300 can be arranged to provide control on communications in the service area of the system. The control apparatus 300 comprises at least one memory 301, at least one

data processing unit

302, 303 and an input/output interface 304. Via the interface the control apparatus can be coupled to a receiver and a transmitter of the base station. The receiver and/or the transmitter may be implemented as a radio front end or a remote radio head.

For 5G management 3GPP SA5 moved to a Service Based Management Architecture (SBMA) where Management Services (MnS) are exposed by MnS Producers and consumed by MnS Consumers. Note that the term Management Service (MnS) is used by 3GPP SA5. MnS may also be referred to as Application Programming Interface (API) .

The MnS design follows a strict model driven approach, where only CRUD (create, read update, delete) operations are used by the MnS Consumer to manipulate the information model on the MnS Producer. Task specific operations should be avoided. This design approach is identical to the one advocated by the REST (REpresentational State Transfer) design principles.

Because of this approach many "legacy style" task specific operations need to be re-specified using only specific information model elements and CRUD operations. Operations must be specified right from the beginning using this model driven approach.

For example, the "allocate" and "deallocate" operations must be specified using this model driven approach.

With the "allocate" operation a MnS Consumer can request to use a certain telecommunication service. The term “telecommunication service” refers to any type of function providing a telecommunication service. The telecommunication service may be a slice, a slice subnet or a subnetwork, or any other resource.

Upon reception of the request the MnS Provider checks if the requested telecommunication service is already available in the network and can be used (if required after reconfiguration of the existing service) as well by the requesting MnS Consumer. If this is the case, the telecommunication service is allocated to the MnS Consumer and can be used by that MnS Consumer. The MnS Consumer is provided with information required to be able to use the telecommunications service such as the service ID and the characteristics of the allocated service (since the characteristics of the allocated service may not match exactly the requested service characteristics) . For example, when the requested service availability is 97%then a service with 99%service availability is deemed to be acceptable for the MnS Consumer by the MnS Producer.

If no existing telecommunication services matches the requested service characteristics or an existing service whose service characteristics match the requested service characteristics cannot be used by the requesting MnS Consumer for some reason, a new telecommunications service instance is created in the network and a resource representing the new instance is created in the MnS Producer. Information about the created service, such as the service ID, is returned to the MnS Consumer.

With the "deallocate" operation the MnS Consumer signals to the MnS Producer that the allocated telecommunication service will not be used any more. The MnS producer may, as a result, trigger actions such as deletion of the previously allocated telecommunication service or reconfiguration

3GPP TS 32.531 describes "allocate" and "deallocate" operations for a Network Slice Instance (NSI) , a Network Slice Subnet Instance (NSSI) and a Subnetwork. The specification uses the classical approach where dedicated operations with dedicated input parameters and output parameters are specified. A dedicated operation is specified for slice allocation and slice deallocation, a dedicated operation for slice subnet allocation and slice subnet deallocation and a dedicated operation for subnetwork allocation.

The definition of allocate NSI and deallocate NSI from 3GPP TS28.531 is repeated here.

6.5.1 AllocateNsi operation

6.5.1.1 Description

This operation is invoked by allocateNsi operation service consumer to request the provider to allocate a network slice instance to satisfy network slice related requirements.

The provider may create a new NSI or using existing NSI to satisfy the request.

6.5.1.2 Input parameters

6.5.1.3 Output parameters

6.5.3 DeallocateNsi operation

6.5.3.1 Description

This operation is invoked by deallocateNsi operation service consumer to request the provider to deallocate a network slice instance since the NSI is no longer needed for the consumer. The provider may terminate the requested NSI or modify the requested NSI without termination to satisfy the request.

6.5.3.2 Input parameters

6.5.3.3 Output parameters

As can be seen the definition in 3GPP TS 28.531 follows the traditional style based on dedicated operations where dedicated tuples of "allocate" and "deallocate" operations are specified for a slice, a slice subnet and a subnetwork. There is hence a need for a generic "allocate" and "deallocate" functionality implemented with information model elements and CRUD operations only.

Figure 4 shows a flowchart of a method according to an example embodiment.

In a first step, S1, the method comprises receiving, at a first entity, a request from a second entity to allocate a service for the second entity.

In a second step, S2, the method comprises providing a request resource comprising information representative of the request to allocate the service.

In a third step, S3, the method comprises, in response to providing the request resource, allocating the service for the second entity and providing a service resource comprising information representative of the allocated service, wherein each of the service resource and the request resource comprise an association with the other of the service resource and the request resource.

Figure 5 shows a flowchart of a method according to an example embodiment.

In a first step, T1, the method comprises providing a request to a first entity from a second entity to allocate a service for the second entity, the request for use in providing a request resource comprising information representative of the request to allocate a service.

In a second step, T2, the method comprises receiving an indication at the second entity from the first entity that the service has been allocated.

In a third step, T3, the method comprises determining, from the request resource, an association with a service resource.

In a fourth step, T4, the method comprises determining, from the service resource, information representative of the allocated service

The first and second entity may be a function block in an operation support system (OSS) /business support system (BSS) or a vertical system. The first entity may be a MnS Producer. The MnS Producer may be a Management Function or a server. The second entity may be a MnS Consumer. The MnS Consumer may be a Management Function or a client.

The method may realise generic "allocate" and "deallocate" functions with specific information model fragments (resources) and CRUD operations only. No dedicated operations are used.

The method makes use of a request resource that is created by the MnS Consumer in the MnS Producer. The request resource represents the request for allocation of a service

For example, the MnS Consumer provides a request to allocate a service to the MnS producer. In response, the MnS producer creates (i.e. provides) on the MnS Producer a resource comprising information representative of the request of the MnS Consumer to allocate a service. This resource is called the request resource. A normal create resource operation (REST solution: HTTP POST or HTTP PUT) may be used for the request resource creation.

The request resource may comprise a first pointer attribute and the service resource may comprise a second pointer attribute. The method may comprise providing the association with the service resource in the first pointer attribute and the association with the request resource in the second pointer attribute. The first pointer attribute and the second pointer attribute may comprise Distinguished Names (DNs) , URIs or any other identifier. When the request resource is created, the first pointer attribute may carry null semantics.

Information representative of the request to allocate a service may comprise second entity identity information, e.g., information on the requesting MnS Consumer, e.g. identifier and URI, or information about the entity on which behalf the MnS Consumer is issuing the request

Information representative of the request to allocate a service may comprise requested service information, that is, information describing the requested service (e.g. service characteristics, service profile or service descriptor) such as service availability.

The information describing the request service may be concrete values for service characteristics, e.g. service availability shall be 97%or value ranges for service characteristics, e.g. service availability shall be between 97%and 100%. For example, the MnS Consumer may not specify the concrete characteristics of the requested service but include a value range in the service allocation request. The MnS Producer then decides what could be acceptable to the MnS Consumer based on the value range. This value range may be specified, for example, by a filter that the MnS Producer shall apply to all existing service instances.

As a result of this method, the MnS produce may allocate an arbitrary type of resources to a MnS Consumer to satisfy the requirements of the service required by the consumer. The consumer itself doesn’t, need to identify the resource type in the service allocation request. For example, a consumer can request “allocate a service to support uRLLC with reliability 99.999%, non-delay tolerance” , etc. The consumer does not need to specify “allocate a network slice” or “slice subnet” . The producer can decide the resource type for the consumer according to service level requirements in the request.

Information representative of the request to allocate a service may comprise information configuring service allocation request status reports. For example, such information may configure how the MnS Producer shall make the outcome of the allocation process available or if and how the MnS Producer shall make the progress of the allocation process available

Information representative of the request to allocate a service may comprise information configuring notification settings. For example the information may comprise information on where notifications that may be provided by the MnS Producer during processing the allocation request, shall be sent to, e.g. a callback URI or information on where notifications with the outcome of the allocation process that may be provided by the MnS Producer, shall be sent to, e.g. a callback URI.

The creation, or provision, of the request resource causes the MnS Producer to start processing the allocation request based on the representation of the request resource. Allocating a service may comprise initiating a service instance or using an existing service instance. In an example embodiment, the MnS Producer scans the existing and available service instances and checks if any of these can be allocated to the MnS Consumer.

In an example embodiment, when an existing service instance is identified as allocation target, the MnS Producer may create a relationship between the request resource and the service resource by

· setting a pointer attribute in the request resource to a value pointing to the service resource

· setting a pointer attribute in the service resource pointing to the request resource.

When no existing service can be allocated, the MnS Producer instantiates a new service instance in the network. The new service instance may be created using state of the art methods. The new service instance is represented by a new service resource that the MnS Producer creates and exposes to the MnS Consumer. After this a relationship between the new service resource and the request resource may be established by the MnS Producer by setting the previously described pointer attributes.

The result of the allocation is reflected in the information model exposed by the MnS Producer by the establishment of a bidirectional relationship between the request resource and the service resource representing the allocated telecommunication service. This relationship may be realized by a pointer attribute in the request resource holding a pointer (address, name) to the service resource and, vice versa, by a pointer attribute in the service resource holding a pointer to the request resource. The pointer attributes are populated by the MnS Producer. The relationship may be realised by another method, such as containment.

The request resource may be read by the second entity to determine the association between the request resource and the service resource. The request resource may be read by the second entity periodically. The request resource may comprise a first pointer attribute. The apparatus may comprise means for determining the association with the service resource from the first pointer attribute. Determining, from the request resource, an association with the service resource may comprise the MnS Consumer reading the pointer (address) to the service resource from the request resource when the allocation process is ready to determine the address of the service resource.

In one example embodiment, the MnS Consumer polls the pointer attribute in the request resource regularly using a normal resource read operation (REST solution: HTTP GET) . When a valid pointer value is returned (no null semantics) the MnS Consumer knows that the MnS Producer has allocated a service. The MnS Consumer uses the pointer value and reads the representation of the allocated service on the MnS Producer using a normal read resource operation (REST solution: HTTP GET) .

Alternatively, or in addition, receiving an indication that the service has been allocated may comprise receiving an indication of the association between the request resource and the service resource from the first entity at the second entity. The second entity then determines the association from the indication.

In an example embodiment, the MnS Producer sends a notification (e.g. an attribute value change notification) with the pointer value to the MnS Consumer. To receive notifications, the MnS Consumer may have to subscribe to receiving notifications. No polling is required in this case.

Whether polling or notifications are to be used may be hard coded and known to the MnS Consumer and MnS Producer. Alternatively, or in addition, the MnS Consumer may configure the MnS Producer to use polling or notifications (for example in the request resource as described above) . The MnS Consumer may indicate to the MnS Producer that it can receive notifications by populating the value of a specific attribute in the request resource with a valid address value and not with null semantics.

The MnS Consumer may use the retrieved address to read the service resource representation and thereby information representative of the allocated service, such as service ID or service characteristics.

Receiving an indication from the first entity at the second entity that the service has been allocated may comprise receiving an indication of the status of the request to allocate a service from the first entity at the second entity. The indication may be provided in a temporary resource, such as a monitor resource or an outcome resource. An outcome resource may include an indication of the association, e.g., the first pointer attribute. The method may comprise determining from the request resource an association with the service resource once the indication of the status indicates that the service has been allocated.

The MnS Producer may create one or more monitor resources indicating information regarding the processing of the allocation request, such as the status of the allocation request. The monitor resource allows the MnS Consumer to follow the progress of processing the resource allocation request on the MnS Producer. This may be useful when the allocation process takes some time. The MnS Consumer may read this information (e.g. by polling) and/or be notified about changes using notifications. Subscriptions to notifications may be required. The MnS Consumer may configure the MnS Producer to create such a monitor resource (for example, in the request resource as described above) .

In another example embodiment, the MnS Producer creates a temporary resource that will be populated with the outcome of the allocation request once available. The outcome resource may include a pointer attribute indicating the service resource and may mirror the complete representation of the allocated service. Polling or notifications may be used to convey the outcome resource representation to the MnS Consumer. Subscriptions to notifications may be required. The MnS Consumer may configure the MnS Producer to create such an outcome resource (for example, in the request resource as described above) .

The monitor resource and outcome resource may be combined into a single resource.

The request resources may be split into multiple resources, e.g., one resource for the requested service characteristics and one for the rest.

The proposed method for realizing the "deallocate" operation is to delete the relationship between the request resource and the service resource. The method may comprise providing an indication to the first entity from the second entity to delete the association between the request resource and the service resource such that the allocated service is deallocated

At least one the first pointer attribute and the second pointer attribute may be set to a null value.

The association between the request resource and the service resource may be deleted by updating the two pointer attributes to null semantics using normal resource update operations (REST solution: HTTP PUT or HTTP PATCH) . The syntax of null semantics depends on the data interchange format, for example JSON has an explicit "null" value.

Alternatively, only the pointer in the request resource or the service resource may be set to null semantics by the MnS consumer.

In another embodiment the MnS Consumer deletes the request resource using the normal delete operation (REST solution: HTTP DELETE) and may set the pointer in the service resource to null semantics.

At least one of the first pointer attribute and the second pointer attribute may be deleted. In an example embodiment the MnS Consumer deletes the pointer values instead of setting them to null semantics.

The behaviour of the MnS Producer in response to the service deallocation is implementation specific and may depend on the deployment scenario and traffic conditions. The service instance may be reconfigured or deleted. The corresponding service resources may be deleted as well.

The (telecommunication) service may be a Network Slice, a Network Slice Subnet or a subnetwork, or any other resource.

The resource may be a Managed Object Instance (MOI) which is the instantiation of a Managed Object Class (MOC) .

The information model may be a Network Resource Model (NRM) .

Figure 6 shows the slice NRM as specified in TS 28.541 updated with the request resource "ConsumerRequest" . As can be seen in this Figure, the proposed mechanism uses only information model elements (resources, relationships between resources) and CRUD operations.

An apparatus may comprise means for receiving, at a first entity, a request from a second entity to allocate a service for the second entity, providing a request resource comprising information representative of the request to allocate a service and in response to providing the request resource, allocating the service for the second entity and providing a service resource comprising information representative of the allocated service, wherein each of the service resource and the request resource comprise an association with the other of the service resource and the request resource.

Alternatively, or in addition, an apparatus may comprise means for providing a request to a first entity from a second entity to allocate a service for the second entity, the request for use in providing a request resource comprising information representative of the request to allocate a service, receiving an indication at the second entity from the first entity that the service has been allocated, determining, from the request resource, an association with a service resource and determining, from the service resource, information representative of the allocated service.

It should be understood that the apparatuses may comprise or be coupled to other units or modules etc., such as radio parts or radio heads, used in or for transmission and/or reception. Although the apparatuses have been described as one entity, different modules and memory may be implemented in one or more physical or logical entities.

It is noted that whilst some embodiments have been described in relation to 5G networks, similar principles can be applied in relation to other networks and communication systems. Therefore, although certain embodiments were described above by way of example with reference to certain example architectures for wireless networks, technologies and standards, embodiments may be applied to any other suitable forms of communication systems than those illustrated and described herein.

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

In general, the various embodiments may be implemented in hardware or special purpose circuitry, software, logic or any combination thereof. Some aspects of the disclosure may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the disclosure is not limited thereto. While various aspects of the disclosure may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

As used in this application, the term “circuitry” may refer to one or more or all of the following:

(a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

(b) combinations of hardware circuits and software, such as (as applicable) :

(i) a combination of analog and/or digital hardware circuit (s) with software/firmware and

(ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

(c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. ”

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

The embodiments of this disclosure may be implemented by computer software executable by a data processor of the mobile device, such as in the processor entity, or by hardware, or by a combination of software and hardware. Computer software or program, also called program product, including software routines, applets and/or macros, may be stored in any apparatus-readable data storage medium and they comprise program instructions to perform particular tasks. A computer program product may comprise one or more computer-executable components which, when the program is run, are configured to carry out embodiments. The one or more computer-executable components may be at least one software code or portions of it.

Further in this regard it should be noted that any blocks of the logic flow as in the Figures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD. The physical media is a non-transitory media.

The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processors may be of any type suitable to the local technical environment, and may comprise one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) , application specific integrated circuits (ASIC) , FPGA, gate level circuits and processors based on multi core processor architecture, as non-limiting examples.

Embodiments of the disclosure may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

The scope of protection sought for various embodiments of the disclosure is set out by the independent claims. The embodiments and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the disclosure.

The foregoing description has provided by way of non-limiting examples a full and informative description of the exemplary embodiment of this disclosure. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of this disclosure will still fall within the scope of this invention as defined in the appended claims. Indeed, there is a further embodiment comprising a combination of one or more embodiments with any of the other embodiments previously discussed.

Claims

An apparatus comprising means for:

receiving, at a first entity, a request from a second entity to allocate a service for the second entity;

providing a request resource comprising information representative of the request to allocate a service; and

in response to providing the request resource, allocating the service for the second entity and providing a service resource comprising information representative of the allocated service, wherein each of the service resource and the request resource comprise an association with the other of the service resource and the request resource.
An apparatus according to claim 1 or claim 2, comprising means for providing an indication of the association between the request resource and the service resource to the second entity.
An apparatus according to claim 1 or claim 2, wherein the request resource is periodically read by the second entity to determine the association between the request resource and the service resource.
An apparatus according to any of claims 1 to 3, comprising means for deleting the association between the request resource and the service resource such that the allocated service is deallocated.
An apparatus according to any of claims 1 to 4, comprising means for providing an indication of the status of the request to allocate a service to the second entity.
An apparatus according to any of claims 1 to 5, wherein the information representative of the request to allocate the service comprises at least one of second entity identity information, requested service information, information configuring service allocation request status reports and information configuring notification settings.
An apparatus according to any of claims 1 to 6, wherein means for allocating the service comprises means for initiating a service instance or using an existing service instance.
An apparatus according to any of claim 7, wherein the request to allocate a service does not include an indication of a type of service instance and comprising means for determining the type of service instance at the first entity.
An apparatus according to any of claims 1 to 8, wherein the request resource comprises a first pointer attribute and the service resource comprises a second pointer attribute and comprising means for providing the association with the service resource in the first pointer attribute and the association with the request resource in the second pointer attribute.
An apparatus comprising means for:

providing a request to a first entity from a second entity to allocate a service for the second entity, the request for use in providing a request resource comprising information representative of the request to allocate a service;

receiving an indication at the second entity from the first entity that the service has been allocated;

determining, from the request resource, an association with a service resource; and

determining, from the service resource, information representative of the allocated service.
An apparatus according to claim 10, wherein means for receiving an indication that the service has been allocated comprises means for receiving an indication of the association between the request resource and the service resource from the first entity at the second entity.
An apparatus according to claim 10, wherein means for receiving an indication that the service has been allocated comprising means for periodically reading the request resource to determine the association between the request resource and the service resource.
An apparatus according to any of claims 10 to 12, comprising means for providing an indication to the first entity from the second entity to delete the association between the request resource and the service resource such that the allocated service is deallocated.
An apparatus according to any of claims 10 to 13, wherein means for receiving an indication that the service has been allocated comprises means for receiving an indication of the status of the request to allocate the service from the first entity at the second entity.
An apparatus according to any of claims 10 to 14, wherein the information representative of the request to allocate a service comprises at least one of second entity identity information, requested service information, information configuring service allocation request status reports and information configuring notification settings.
An apparatus according to any of claims 10 to 15, wherein the request resource comprises a first pointer attribute and comprising means for determining the association with the service resource from the first pointer attribute.
A method comprising:

receiving, at a first entity, a request from a second entity to allocate a service for the second entity;

providing a request resource comprising information representative of the request to allocate a service; and

in response to providing the request resource, allocating the service for the second entity and providing a service resource comprising information representative of the allocated service, wherein each of the service resource and the request resource comprise an association with the other of the service resource and the request resource.
A method comprising

providing a request to a first entity from a second entity to allocate a service for the second entity, the request for use in providing a request resource comprising information representative of the request to allocate a service;

receiving an indication at the second entity from the first entity that the service has been allocated;

determining, from the request resource, an association with a service resource; and

determining, from the service resource, information representative of the allocated service.
An apparatus comprising: at least one processor and at least one memory including a computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to:

receive, at a first entity, a request from a second entity to allocate a service for the second entity;

provide a request resource comprising information representative of the request to allocate a service; and

in response to providing the request resource, allocate the service for the second entity and provide a service resource comprising information representative of the allocated service, wherein each of the service resource and the request resource comprise an association with the other of the service resource and the request resource.
An apparatus comprising: at least one processor and at least one memory including a computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the apparatus at least to:

provide a request to a first entity from a second entity to allocate a service for the second entity, the request for use in providing a request resource comprising information representative of the request to allocate a service;

receive an indication at the second entity from the first entity that the service has been allocated;

determine, from the request resource, an association with a service resource; and

determine, from the service resource, information representative of the allocated service.
A computer readable medium comprising program instructions for causing an apparatus to perform at least the following:

receiving, at a first entity, a request from a second entity to allocate a service for the second entity;

providing a request resource comprising information representative of the request to allocate a service; and

in response to providing the request resource, allocating the service for the second entity and providing a service resource comprising information representative of the allocated service, wherein each of the service resource and the request resource comprise an association with the other of the service resource and the request resource.
A computer readable medium comprising program instructions for causing an apparatus to perform at least the following:

providing a request to a first entity from a second entity to allocate a service for the second entity, the request for use in providing a request resource comprising information representative of the request to allocate a service;

receiving an indication at the second entity from the first entity that the service has been allocated;

determining, from the request resource, an association with a service resource; and

determining, from the service resource, information representative of the allocated service.