CN114514764B

CN114514764B - Apparatus, method and computer program

Info

Publication number: CN114514764B
Application number: CN201980101220.4A
Authority: CN
Inventors: O·珀拉科瓦斯基; 平静; A·安德里亚诺维
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Priority date: 2019-10-11
Filing date: 2019-10-11
Publication date: 2024-05-07
Anticipated expiration: 2039-10-11
Also published as: CN114514764A; WO2021068207A1

Abstract

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 including information representing a request to allocate a service; and in response to providing the requested resources, allocating a 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 requested resource comprises an association with the other of the service resource and the requested resource.

Description

Apparatus, method and computer program

Technical Field

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

Background

A communication system may be considered 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 communication path. The communication system may be provided, for example, by means of a communication network and one or more compatible communication devices. The communication session may include, for example, data communications for carrying communications such as voice, video, electronic mail (email), short message messages, multimedia and/or content data, and the like. Non-limiting examples of services provided include bi-or multi-directional calls, data communications or multimedia services, and access to data network systems such as the internet.

In a wireless communication system, at least a portion of a communication session between at least two stations occurs over a wireless link. Examples of wireless systems include Public Land Mobile Networks (PLMNs), satellite-based communication systems, and different wireless local area networks, such as Wireless Local Area Networks (WLANs). Some wireless systems may be divided into cells and are therefore commonly referred to as cellular systems.

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

Communication systems 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 communication 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 air interface (NR) networks. NR is being standardized by the third generation partnership project (3 GPP).

Disclosure of Invention

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 including information representing a request to allocate a service; and in response to providing the requested resources, allocating a 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 requested resource comprises an association with the other of the service resource and the requested resource.

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

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

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

The apparatus may include means for deleting an association between the requested resource and the service resource such that the allocated service is deallocated.

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

The information indicating the request for allocation of the service may include at least one of second entity identity information, requested service information, information configuring a service allocation request status report, and information configuring a notification setting.

The means for allocating the service may comprise means for starting a service instance or using an existing service instance.

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

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

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

The means for receiving an indication that the service has been allocated may include means for periodically reading the requested resource to determine an association between the requested resource and the service resource.

The apparatus may include means for providing an indication from the second entity to the first entity to delete the association between the requested resource and the service resource to cause the allocated service to be deallocated.

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

The information representing the service allocation request may include at least one of second entity identity information, request service information, information configuring a service allocation request status report, and information configuring a notification setting.

The request resource may include a first pointer attribute. The apparatus may include means for determining an 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 including information representing a request to allocate a service; and in response to providing the requested resources, allocating a 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 requested resource comprises an association with the other of the service resource and the requested resource.

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

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

The method may include deleting an association between the requested resource and the service resource such that the allocated service is deallocated.

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

The information indicating the request for allocation of the service may include at least one of second entity identity information, request service information, information configuring a service allocation request status report, and information configuring a notification setting.

Assigning the service may include launching a service instance or using an existing service instance.

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

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

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

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

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

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

The information indicating allocation of the service request may include at least one of second entity identity information, request service information, information configuring a service allocation request status report, and information configuring a notification setting.

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

Receiving, at a first entity, a request from a second entity to allocate a service for the second entity; providing a request resource including information representing a request to allocate a service; and in response to providing the requested resources, allocating a 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 requested resource comprises an association with the other of the service resource and the requested resource.

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

The request resource may include a first pointer attribute. The service resource may include a second pointer attribute. The device may be configured to provide an association with the service resource in the first pointer attribute and an 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 allocation service request to the second entity.

The device may be configured to initiate a service instance or use an existing service instance.

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

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

Providing, from a second entity to a first entity, a request for allocation of a service for said second entity, said request for providing a request resource comprising information representing said request for allocation of a service; receiving, at the second entity, an indication from the first entity that a service has been allocated; determining an association with a service resource from the request resource; and determining information representative of the allocated service from the service resource.

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

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

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

The apparatus may be configured to receive, at the second entity, an indication of a status of the request to allocate service from the first 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 including information representing a request to allocate a service; and in response to providing the requested resources, allocating a 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 requested resource comprises an association with the other of the service resource and the requested resource.

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

The request resource may include a first pointer attribute. The service resource may include a second pointer attribute. The apparatus may be caused to perform providing an association with the service resource in the first pointer attribute and providing an 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 a status of an allocation service request to the second entity.

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

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

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

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

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

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

Drawings

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

FIG. 1 shows a schematic diagram of an example communication system including a base station and a plurality of communication devices;

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

FIG. 3 illustrates a schematic diagram of an example control device;

FIG. 4 shows a flow chart of a method according to an example embodiment;

FIG. 5 shows a flow chart of a method according to an example embodiment;

fig. 6 illustrates a network resource model according to an example embodiment.

Detailed Description

Before explaining examples in detail, certain general principles of wireless communication systems and mobile communication devices are briefly explained with reference to fig. 1 to 3 to help understand the underlying technology of the described examples.

In a wireless communication system 100 such as that shown in fig. 1, wireless access is provided to communication devices (e.g., user Equipment (UE)) 102, 104, 105 via at least one base station or similar wireless transmitting and/or receiving node or point. The base station is typically controlled by at least one suitable controller means in order to be able to operate it and manage the mobile communication devices communicating with the base station. The controller device may be located in a Radio Access Network (RAN) (e.g., wireless communication system 100) or a Core Network (CN) (not shown) and may be implemented as one central device or its functions may be distributed over multiple devices. The controller means may be part of the base station and/or provided by a separate entity such as a radio network controller. In fig. 1, control means 108 and 109 are shown as controlling the respective macro level base stations 106 and 107. The control means of the base station may be interconnected with other control entities. The control device typically has a memory capacity and at least one data processor. The control means and functions may be distributed among a plurality of control units. In some systems, the control means may additionally or alternatively be provided in the radio network controller.

In fig. 1, base stations 106 and 107 are shown connected to a broader communication network 113 via gateway 112. Further gateway functions 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 separate gateway functions and/or via controllers of macro-level stations. The base stations 116, 118, and 120 may be pico or femto base stations, or the like. In this example, base stations 116 and 118 are connected via gateway 111, and base station 120 is connected via controller device 108. In some embodiments, smaller base stations may not be provided. The smaller base stations 116, 118, and 120 may be part of a second network, such as a WLAN, and may be WLAN Access Points (APs).

The communication devices 102, 104, 105 may access the communication system based on various access technologies, such as Code Division Multiple Access (CDMA) or Wideband CDMA (WCDMA). Other non-limiting examples include Time Division Multiple Access (TDMA), frequency Division Multiple Access (FDMA), and various schemes thereof, such as 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 the like.

An example of a wireless communication system is an architecture standardized by the third generation partnership project (3 GPP). Recent 3 GPP-based developments are commonly referred to as Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio access technology. The various stages of development of the 3GPP specifications are referred to as releases. The latest development of LTE is commonly referred to as LTE-Advanced (LTE-a). LTE (LTE-a) employs a radio mobile architecture called evolved universal terrestrial radio access network (E-UTRAN) and a core network called evolved packet core (Evolved Packet Core, EPC). The 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 termination to the communication device. Other examples of radio access systems include those provided by base stations of systems based on technologies such as Wireless Local Area Networks (WLANs). The base station may provide coverage for an entire cell or similar radio service area. The core network elements include a Mobility Management Entity (MME), a serving gateway (S-GW), and a packet gateway (P-GW).

Examples of suitable communication systems are the 5G or NR concepts. The network architecture in NR may be similar to LTE-advanced. The base station of the NR system may be referred to as a next generation node B (gNB). The change in network architecture may depend on the need to support various radio technologies and finer QoS support, as well as some on-demand requirements, e.g., quality of service (QoS) levels, to support quality of experience (QoE) of the user. In addition, network aware services and applications and service and application aware networks may bring about changes to the architecture. These are related to Information Centric Networking (ICN) and user centric content delivery networking (UC-CDN) approaches. NR may use multiple-input-multiple-output (MIMO) antennas, more base stations or nodes than LTE (so-called small cell concept), including macro sites operating in cooperation with smaller stations, and perhaps also employ various radio technologies to achieve better coverage and enhanced data rates.

Future networks may utilize Network Function Virtualization (NFV), which is a network architecture concept that proposes to virtualize network node functions as "building blocks" or entities that are operably connected or linked together to provide services. A Virtualized Network Function (VNF) may comprise one or more virtual machines running computer program code using standard or generic servers instead of custom hardware. Cloud computing or data storage may also be used. In radio communications, this may mean performing node operations in a server, host, or node that is at least partially operatively coupled to the remote radio head. Node operations may also be distributed among multiple servers, nodes, or hosts. It should also be appreciated that the allocation of labor between core network operation and base station operation may be different from LTE or even non-existent.

An example 5G Core Network (CN) includes functional entities. The CN is connected to the UE via a 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 a Data Network (DN) and a tunnel (tunnel) established over 5G to a UE exchanging traffic with the DN.

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

One possible mobile communication device will now be described in more detail with reference to fig. 2, fig. 2 showing a schematic, partial cross-sectional view of a communication device 200. Such communication devices are often referred to as User Equipment (UE) or terminals. A suitable mobile communication device may be provided by any device capable of transmitting and receiving radio signals. Non-limiting examples include Mobile Stations (MS) or mobile devices such as mobile phones or so-called "smartphones", computers with wireless interface cards or other wireless interface facilities (e.g., USB dongles), personal Data Assistants (PDAs) or tablet computers with wireless communication capabilities, voice over IP (VoIP) phones, portable computers, desktop computers, image capture terminal devices such as digital cameras, game terminal devices, music storage and playback appliances, car radio terminal devices, wireless endpoints, mobile stations, notebook computer embedded devices (LEEs), notebook computer installation devices (LMEs), smart devices, wireless Customer Premise Equipment (CPE), or any combination of these, etc. The mobile communication device may provide, for example, data communications for carrying communications such as voice, electronic mail (email), short message messages, multimedia, and the like. Thus, users can be offered and provided with a large number of services via their communication devices. Non-limiting examples of such services include bi-or multi-directional calls, data communication or multimedia services or simply accessing data communication network systems such as the internet. Broadcast or multicast data may also be provided to the user. Non-limiting examples of content include downloads, television and radio programming, video, advertising, various alerts, and other information.

The mobile device typically has at least one data processing entity 201, at least one memory 202 and possibly other components 203 for software and hardware assistance in performing tasks it is designed to perform, including control of access and communication to access systems and other communication devices. The data processing, storage and other associated control means may be provided on a suitable circuit board and/or in a chipset. This feature is indicated by reference numeral 204. The user may control the operation of the mobile device by means of a suitable user interface such as a keypad 205, voice commands, touch sensitive screen or pad, combinations thereof, or the like. A display 208, speakers, and microphone may also be provided. In addition, the mobile communication device may include suitable connectors (wired or wireless) to other devices and/or for connecting external accessories (e.g., hands-free devices) to other devices.

The mobile device 200 may receive signals over the air or radio interface 207 via suitable means for receiving and may transmit signals via suitable means for transmitting radio signals. In fig. 2, the transceiver device is schematically designated by block 206. The transceiver means 206 may be provided, for example, by means of a radio part and an associated antenna arrangement. The antenna arrangement may be arranged inside or outside the mobile device.

Fig. 3 shows an example of a control apparatus 300 for a communication system, e.g. for coupling to and/or for controlling stations of an access system, such as a RAN node (e.g. base station, eNB or gNB), or a relay node or 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 device or across multiple control devices. The control means may be integrated with or external to a node or module of the core network or RAN. In some embodiments, the base station includes a separate control device unit or module. In other embodiments, the control device may be another network element such as a radio network controller or a spectrum controller. In some embodiments, each base station may have such control means as well as control means provided in a radio network controller. The control means 300 may be arranged to provide control of the communication in the service area of the system. The control device 300 comprises at least one memory 301, at least one data processing unit 302, 303 and an input/output interface 304. The control means may be coupled via an interface to a receiver and a transmitter of the base station. The receiver and/or transmitter may be implemented as a radio front-end or a remote radio head.

For 5G management, 3gpp SA5 moves to a service-based management architecture (SBMA) in which management services (MnS) are published 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 an Application Programming Interface (API).

MnS designs follow a strict model driven approach in which MnS consumers use only CRUD (create, read update, delete) operations to manipulate information models on MnS producers. Task-specific operations should be avoided. This design method is the same as that advocated by REST (Representational STATE TRANSFER) design principle.

Because of this approach, many "traditional style" task-specific operations require reassignment using only specific information model elements and CRUD operations. Operations must be specified from the beginning using this model driven approach.

For example, such model driven methods must be used to specify "allocate" and "deallocate" operations.

Through the "distribution" operation, mnS consumers may request the use of certain telecommunication services. The term "telecommunications service" refers to any type of functionality that provides telecommunications services. The telecommunication service may be a slice, a slice subnet or subnetwork, or any other resource.

Upon receipt of the request, the MnS provider checks whether the requested telecommunication service is already available in the network and (after reconfiguration of the existing service if necessary) can be used by the requesting MnS consumer. If this is the case, then the telecommunications service is allocated to and available to the MnS consumer. MnS consumers have the information needed to be able to use telecommunication services, such as service ID and the characteristics of the assigned service (as the characteristics of the assigned service may not exactly match the requested service characteristics). For example, when the requested service availability is 97%, mnS producers consider a service with 99% service availability acceptable to MnS consumers.

If no existing telecommunication service matches the requested service characteristic or the existing service whose service characteristic matches the requested service characteristic is not for some reason available to the MnS consumer requesting it, then a new telecommunication service instance is created in the network and the resources representing the new instance are created in the MnS producer. Information about the created service, such as the service ID, will be returned to the MnS consumer.

Through the "deallocation" operation, the MnS consumer signals to the MnS producer that the allocated telecommunications service is no longer to be used. MnS producers may thus trigger actions such as deleting previously allocated telecommunication services or reconfiguration.

3GPP TS 32.531 describes "allocate" and "deallocate" operations for Network Slice Instance (NSI), network Slice Subnet Instance (NSSI), and subnets. The specification uses a classical approach in which a specific operation with specific input parameters and output parameters is specified. Dedicated operations are assigned for slice allocation and slice deallocation, dedicated operations are assigned for slice subnet allocation and slice subnet deallocation, and dedicated operations are assigned for subnet allocation.

The definition of allocation NSI and de-allocation NSI from 3gpp TS 28.531 is repeated here.

6.5.1 AllocateNsi operation

6.5.1.1 Describes

This operation is invoked by AllocateNsi operation service consumers to request that the provider allocate network slice instances to meet network slice related requirements. The provider may create a new NSI or use an existing NSI to fulfill the request.

6.5.1.2 Input parameters

6.5.1.3 Output parameters

6.5.3 DeallocateNsi operation

6.5.3.1 Describes

This operation is invoked by DeallocateNsi operations service consumer to request the provider to deallocate the network slice instance because the consumer no longer needs NSI. The provider may terminate the requested NSI or modify the requested NSI without terminating to satisfy the request.

6.5.3.2 Input parameters

6.5.3.3 Output parameters

It can be seen that the definition in 3gpp TS 28.531 follows the traditional way of dedicated operation based, where dedicated tuples for "allocate" and "deallocate" operations are specified for slices, slice subnets and subnets. Thus, there is a need for generic "allocation" and "deallocation" functions implemented using only information model elements and CRUD operations.

Fig. 4 shows a flow chart 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 representing a request to allocate a service.

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

Fig. 5 shows a flow chart of a method according to an example embodiment.

In a first step T1, the method comprises providing a request from the second entity to the first entity for allocation of a service for the second entity, the request being for providing a request resource comprising information representing the request for allocation of the service.

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

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

In a fourth step T4, the method comprises determining information representing the allocated service from the service resources.

The first and second entities may be function blocks in an Operation Support System (OSS)/service support system (BSS) or a vertical system. The first entity may be a MnS producer. MnS producers may be management functions or servers. The second entity may be a MnS consumer. MnS consumers may be management functions or clients (clients).

The method may implement the generic "allocate" "deallocate" function using only specific information model fragments (resources) and CRUD operations. Without using any special operations.

The method uses requested resources created by MnS consumers in MnS producers. The request resource represents a request for service allocation.

For example, mnS consumers provide a request to distribute services to MnS producers. In response, the MnS producer creates (i.e., provides) a resource on the MnS producer that includes information representing the MnS consumer's request to allocate a service. This resource is referred to as the request resource. Normal create resource operations (REST solutions: HTTP POST or HTTP PUT) may be used to request resource creation.

The request resource may include a first pointer attribute and the service resource may include a second pointer attribute. The method may include providing an association with a service resource in a first pointer attribute and providing an association with a request resource in a second pointer attribute. The first pointer attribute and the second pointer attribute may include an identification name (DN), a URI, or any other identifier. The first pointer attribute may carry null semantics when creating the request resource.

The information indicating that the service is requested to be distributed may include second entity identity information (e.g., information about the requesting MnS consumer, such as an identifier and URI), or information about the entity for which the MnS consumer makes the request.

The information indicating that the service is requested to be allocated may include requested service information, i.e., information describing the requested service (e.g., service characteristics, service configuration (profile), or service descriptor), such as service availability.

The information describing the requested service may be a specific value of the service characteristic, e.g. the service availability should be 97% or a range of values of the service characteristic, e.g. the service availability should be between 97% and 100%. For example, mnS consumers may not specify specific characteristics of the requested service, but include a range of values in the service allocation request. The MnS producer then decides what the MnS consumer can accept based on this range of values. This value range may be specified by, for example, the filters applied by the MnS producer to all existing service instances.

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

As a result of this approach, mnS production can allocate any type of resource to MnS consumers to meet the requirements of the services that the consumers desire. The consumer does not need to identify the resource type in the service allocation request itself. For example, a consumer may request "distribute services to support uRLLC" with reliability 99.999%, no delay tolerance, and so on. The consumer does not need to specify "distribution network slices" or "slice subnets". The producer may decide the type of resource for the consumer based on the service level requirements in the request.

The information indicating that the service allocation request is requested may include information configuring a service allocation request status report. For example, such information may configure how MnS producers should make the results of the dispensing process available, or whether and how MnS producers make the progress of the dispensing process available.

The information indicating that the allocation of the service is requested may include information configuring notification settings. For example, the information may include information about where notifications that MnS producers may provide during processing of allocation requests should be sent, such as callback (callback) URIs or information about allocation process result notifications that MnS producers may provide, should be sent, such as callback URIs.

Creation or provision of the requested resource causes the MnS producer to begin processing allocation requests based on the representation of the requested resource. Distributing the service may include launching the service instance or using an existing service instance. In an example embodiment, the MnS producer scans existing and available service instances and checks whether any of these can be allocated to MnS consumers.

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

Setting pointer attributes in the request resource to values pointing to the service resource

Set a pointer attribute in the service resource to the request resource.

When an existing service cannot be allocated, the MnS producer instantiates a new service instance in the network. The new service instance may be created using prior art methods. The new service instance is represented by a new service resource created by the MnS producer and published to MnS consumers. After this, the relationship between the new service resource and the request resource can be established by MnS producer by setting the pointer attribute described previously.

By establishing a bi-directional relationship between the requested resources and the service resources representing the allocation of telecommunication services, the results of the allocation are reflected in the information model published by the MnS producer. The relationship may be implemented by a pointer attribute in the requesting 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 requesting resource. Pointer attributes are filled by MnS producers. This relationship may be implemented by another method, such as containment.

The requested resource may be read by the second entity to determine an association between the requested resource and the service resource. The second entity may periodically read the request resource. The request resource may include a first pointer attribute. The apparatus may include means for determining an association with a service resource from a first pointer attribute. Determining an association with a service resource from a request resource may include the MnS consumer reading a 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, mnS consumers periodically poll for pointer attributes in the request resource 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. MnS consumers read the representation of the assigned service on MnS producers using pointer values and using normal read resource operations (REST solution: HTTP GET).

Alternatively or additionally, receiving an indication that the service has been allocated may include receiving, at the second entity, an indication from the first entity of an association between the requested resource and the service resource. The second entity then determines an association from the indication.

In an example embodiment, the MnS producer transmits a notification (e.g., an attribute value change notification) with a pointer value to the MnS consumer. In order to receive notifications, mnS consumers may have to subscribe to receive notifications. In this case, no polling is required.

Whether to use polling or notification may be hard coded and known to MnS consumers and MnS producers. Alternatively or additionally, mnS consumers may configure MnS producers to use polling or notification (e.g., in the request resources described above). MnS consumer may indicate to MnS producer that it may receive notification by filling the value of a particular attribute in the request resource with an effective address value instead of null semantics.

MnS consumers may use the extracted address to read the service resource representation and thereby read an information representation of the assigned service, such as a service ID or service feature.

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

MnS producers may create one or more monitoring resources that indicate information about the processing of allocation requests, such as the status of allocation requests. Monitoring resources allows MnS consumers to follow the progress of MnS producers in processing resource allocation requests. This may be useful when the allocation process requires some time. MnS consumers may read this information (e.g., by polling) and/or be notified of changes in usage notification. Subscription to these notifications may be required. MnS consumers may configure MnS producers to create such monitoring resources (e.g., in the request resources described above).

In another example embodiment, mnS producers create temporary resources that, once available, will be filled with the results of the allocation request. The resulting resource may include a pointer attribute indicating the service resource and may mirror a complete representation of the assigned service. Polling or notification may be used to convey the resulting resource representation to MnS consumers. Subscription to these notifications may be required. MnS consumers may configure MnS producers to create such result resources (e.g., in the request resources described above).

The monitoring resource and the result resource may be combined into a single resource.

The request resource may be divided into a plurality of resources, e.g., one resource for the requested service characteristic and one resource for the rest.

A proposed method of implementing the "deallocation" operation is to delete the relationship between the requested resource and the service resource. The method may include providing an indication from the second entity to the first entity to delete the association between the request resource and the service resource such that the allocated service is deallocated.

At least one of 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 a normal resource update operation (REST solution: HTTP PUT or HTTP PATCH). The syntax of null semantics depends on the data exchange format, e.g., JSON has explicit "null" values.

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

In another embodiment, mnS consumers delete the requested resource using a 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, mnS consumers delete pointer values instead of setting them to null semantics.

The behavior of MnS producers in response to service deallocation is implementation specific and may depend on deployment scenarios and traffic conditions. Service instances may be reconfigured or deleted. The corresponding service resource may also be deleted.

The (telecommunications) service may be a network slice, a network slice subnet or subnetwork, or any other resource.

A resource may be a Management Object Instance (MOI), which is an instantiation of a Management Object Class (MOC).

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

Fig. 6 shows a slice NRM specified in TS 28.541, in which a request resource "consumer request (ConsumerRequest)" is updated. 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 include means for: receiving, at the first entity, a request from the second entity to allocate a service for the second entity; providing a request resource including information representing a request to allocate a service; and in response to providing the requested resource, allocating a 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 requested resource comprises an association with the other of the service resource and the requested resource.

Alternatively or additionally, an apparatus may comprise means for: a request for allocating a service for a second entity is provided from the second entity to the first entity, the request for providing a request resource comprising information representing the request for allocating the service, an indication that the service has been allocated is received from the first entity at the second entity, an association with the service resource is determined from the request resource, and information representing the allocated service is determined from the service resource.

It should be understood that the device may include or be coupled to other units or modules or the like used in or for transmitting and/or receiving, such as a radio or a radio head. Although these devices are described as one entity, the different modules and memories may be implemented in one or more physical or logical entities.

It is noted that while some embodiments have been described with respect to 5G networks, similar principles may be applied to other networks and communication systems. Thus, although certain embodiments are described above by way of example with reference to certain example architectures for wireless networks, technologies, and standards, the embodiments may be applied to any other suitable form of communication system than those shown and described herein.

It should also be noted herein that while the above describes exemplifying 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 circuits, software, logic or any combination thereof. Some aspects of the application may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto. While various aspects of the application may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well known 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 disclosure, the term "circuit" may refer to one or more or all of the following:

(a) Hardware-only circuit implementations (such as implementations in analog and/or digital circuits only); and

(B) A combination of hardware circuitry and software, e.g., as applicable;

(i) A combination of analog and/or digital hardware circuitry and software/firmware; and

(Ii) The hardware processor works with any portion of software (including digital signal processors), software, and memory, which together cause a device, such as a mobile phone or server, to perform various functions); and

(C) Hardware circuitry and/or a processor, such as a microprocessor or a portion of a microprocessor, that requires software (e.g., firmware) to perform the operation, but the software may not exist when the operation is not required.

This definition of circuit applies to all uses of this term in this disclosure (including in any claims). As a further example, as used in this disclosure, the term "circuitry" also encompasses an implementation of only a hardware circuit or processor (or processors) or a hardware circuit or processor and portions thereof (or their) accompanying software and/or firmware. For example and where applicable to the elements of the specific claims, the term circuitry also encompasses a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

Embodiments of the present disclosure may be implemented by computer software, such as executed by a data processor of a mobile device in a processor entity, or by hardware, or by a combination of software and hardware. Computer software or programs (also referred to as program products), including software routines, applets, and/or macros, may be stored in any apparatus-readable data storage medium and they include program instructions that perform particular tasks. The computer program product may include one or more computer-executable components configured to perform embodiments when the program is run. The one or more computer-executable components may be at least one software code or a portion thereof.

Furthermore, it should be noted in this regard that any block of logic flows as in the figures may represent a program step, 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 a physical medium such as a memory chip or memory block implemented within a processor, a magnetic medium such as a hard or floppy disk, and an optical medium such as a DVD and its data variants, CD. Physical media is 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 processor may be of any type suitable to the local technical environment and may include, as non-limiting examples, one or more of a general purpose computer, a special purpose computer, a microprocessor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an FPGA, a gate level circuit, and a processor based on a multi-core processor architecture.

Embodiments of the present disclosure may be practiced in various components such as integrated circuit modules. The design of integrated circuits is generally 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 the various embodiments of the present disclosure is set forth in the independent claims. The embodiments and features (if any) described in this specification that do not fall within the scope of the independent claims should be construed as examples that facilitate an understanding of the various embodiments of the disclosure.

The foregoing description provides a complete and informative description of the exemplary embodiments of the present disclosure by way of non-limiting example. 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 another embodiment that includes a combination of one or more embodiments with any other embodiment previously discussed.

Claims

1. A communication device, 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 representing a request to allocate a service, wherein said information representing said request to allocate said service comprises at least one of second entity identity information, requested service information, information configuring a service allocation request status report and information configuring a notification setting;

means for allocating a service to the second entity and providing a service resource comprising information representative of the allocated service in response to providing the request resource, wherein the information representative of the allocated service comprises at least one of an identity of the service or a characteristic of the service, and each of the service resource and the request resource comprises an association with the other of the service resource and the request resource; and

Means for providing an association with the service resource in a first pointer attribute and an association with the request resource in a second pointer attribute, the request resource including the first pointer attribute and the service resource including the second pointer attribute.

2. The communication device of claim 1, comprising: means for providing an indication of an association between the requested resource and the service resource to the second entity.

3. The communication device of claim 1 or claim 2, wherein the requested resource is periodically read by the second entity to determine an association between the requested resource and the service resource.

4. The communication device according to claim 1 or 2, comprising: means for deleting the association between the requested resource and the service resource such that the assigned service is deallocated.

5. The communication device according to claim 1 or 2, comprising: means for providing an indication of the status of the request to allocate service to the second entity.

6. A communication device according to claim 1 or 2, wherein the means for allocating the service comprises means for initiating a service instance or using an existing service instance.

7. The communication device of claim 6, wherein the request to allocate service does not include an indication of a service instance type and comprises means for determining the service instance type at the first entity.

8. A communication device, comprising:

Means for providing a request from a second entity to a first entity for allocation of a service for use by the first entity in providing a request resource comprising information indicative of the request to allocate a service, wherein the information indicative of the request to allocate the service comprises at least one of second entity identity information, requested service information, information configuring a service allocation request status report and information configuring a notification setting;

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

Means for determining an association with a service resource from the request resource, wherein the service resource includes information representative of the service being allocated and the information representative of the service being allocated includes at least one of an identification of the service or a characteristic of the service;

Means for determining from the service resources the information representative of the service being allocated; and

Means for determining an association with the service resource from a first pointer attribute, the request resource including the first pointer attribute.

9. The communications device of claim 8, wherein means for receiving an indication that the service has been allocated comprises means for receiving an indication of an association between the requested resource and the service resource from the first entity at the second entity.

10. The communications device of claim 8, wherein means for receiving an indication that the service has been allocated includes means for periodically reading the requested resources to determine an association between the requested resources and the service resources.

11. The communication device according to any one of claims 8 to 10, comprising: means for providing an indication from the second entity to the first entity to delete the association between the requested resource and the service resource such that the allocated service is deallocated.

12. The communication device of any of claims 8 to 10, wherein the means for receiving an indication that the service has been allocated comprises means for receiving an indication of a status of the service allocation request from the first entity at the second entity.

13. A method for communication, 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 representing said request to allocate a service, wherein said information representing said request to allocate said service comprises at least one of second entity identity information, requested service information, information configuring a service allocation request status report and information configuring a notification setting;

In response to providing the request resource, allocating a service to the second entity and providing a service resource comprising information representative of the allocated service, wherein the information representative of the allocated service comprises at least one of an identification of the service or a characteristic of the service, and each of the service resource and the request resource comprises an association with the other of the service resource and the request resource; and

An association with the service resource is provided in a first pointer attribute and an association with the request resource is provided in a second pointer attribute, the request resource including the first pointer attribute and the service resource including the second pointer attribute.

14. A method for communication, comprising:

Providing a request from a second entity to a first entity to allocate a service for said second entity, said request for use by said first entity in providing a request resource comprising information representing said request to allocate a service, wherein said information representing said request to allocate said service comprises at least one of second entity identity information, requested service information, information configuring a service allocation request status report and information configuring a notification setting;

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

determining an association with a service resource from the request resource, wherein the service resource includes information representative of the service being allocated and the information representative of the service being allocated includes at least one of an identification of the service or a characteristic of the service;

determining from the service resources the information representative of the assigned service; and

An association with the service resource is determined from a first pointer attribute, the request resource including the first pointer attribute.

15. A communication apparatus, comprising: at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to:

16. A communication apparatus, comprising: at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to:

determining information representing the allocated service from the service resource; and

17. A computer readable medium comprising program instructions for causing an apparatus to perform at least the following:

18. A computer readable medium comprising program instructions for causing an apparatus to perform at least the following:

Receiving, at the second entity, an indication from the first entity that a service has been allocated;