Apparatus, method and computer program

Abstract

The present application relates to an apparatus comprising at least one processor and at least one memory, the memory comprising computer code for one or more programs, the at least one memory and the computer code configured to configure with the at least one processor, the apparatus is caused to perform at least the following: receiving (400), from a service consumer, a request to assign a network slice instance or a network slice subnet instance to the service consumer; assigning (402) a network slice instance or a network slice subnet instance to the service consumer, where the network slice instance or the network slice subnet instance is newly created or existing; and sending (404) a return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated, where the return code depends on whether the network slice instance or the network slice subnet instance is newly created or existing.

Description

Technical Field

[0001] The present application relates to apparatus, methods and computer programs for managing network slice instances and network slice subnet instance allocation in a communication system. Background Art

[0002] A communication system may be viewed as a facility that enables a communication session between two or more entities (such as communication devices, base stations, and / or other nodes) by providing a carrier wave between the various entities involved in the communication path.

[0003] The communication system may be a wireless communication system. Examples of wireless systems include public land mobile networks (PLMNs) operating based on radio standards such as those provided by 3GPP, satellite-based communication systems, and different wireless local area networks, such as wireless local area networks (WLANs). Wireless systems can typically be divided into a number of cells and are therefore often referred to as cellular systems.

[0004] Communication systems and associated equipment typically operate in accordance with a given standard or specification, which specifies what the various entities associated with the system are allowed to do and how it should be achieved. Communication protocols and / or parameters for the connection are also typically defined. An example of a standard is the so-called 5G standard. Summary of the invention

[0005] According to one aspect, a device is provided, comprising a means for: receiving a request from a service consumer to allocate a network slice instance or a network slice subnet instance to the service consumer; allocating the network slice instance or the network slice subnet instance to the service consumer, wherein the network slice instance or the network slice subnet instance is newly created or already exists; and sending a return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

[0006] The device may include a device for: when the network slice instance or the network slice subnet instance is newly created, sending a first return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated; or when the network slice instance or the network slice subnet instance already exists, sending a second return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated.

[0007] The first return code and the second return code may be different.

[0008] The first bit of the first return code and the first bit of the second return code may be the same or different.

[0009] The first bit of the first return code and the first bit of the second return code may be '2'.

[0010] The first return code may be '201'.

[0011] The second return code may be '211'.

[0012] The device may include a device for: determining that the request includes information indicating that the network slice instance or the network slice subnet instance can be shared between another service consumer and the service consumer; determining that the network slice instance or the network slice subnet instance already exists and can be shared between another service consumer and the service consumer; and allocating the network slice instance or the network slice subnet instance that already exists and can be shared between another service consumer and the service consumer to the service consumer.

[0013] The device may include a device for: determining that the request does not include information indicating that the network slice instance or the network slice subnet instance can be shared between another service consumer and the service consumer; newly creating a network slice instance or a network slice subnet instance; and allocating the newly created network slice instance or the network slice subnet instance to the service consumer.

[0014] The device may include a device for: receiving a request to deallocate the network slice instance or the network slice subnet instance from the service consumer; deallocating the network slice instance or the network slice subnet instance from the service consumer, wherein the network slice instance or the network slice subnet instance is terminated or modified; and sending a return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance is terminated or modified.

[0015] The device may include a device for: when the network slice instance or the network slice subnet instance is terminated, sending a third return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated; or when the network slice instance or the network slice subnet instance is modified, sending a fourth return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated.

[0016] The third return code and the fourth return code may be different.

[0017] The first bit of the third return code and the first bit of the fourth return code may be the same as or different from each other.

[0018] The first bit of the third return code and the first bit of the fourth return code may be '2'.

[0019] The third return code may be '204'.

[0020] The fourth return code may be '212'.

[0021] The device may include a device for: determining that the network slice instance or the network slice subnet instance is not shared between another service consumer and the service consumer; and terminating the network slice instance or the network slice subnet instance.

[0022] The device may include a device for: determining that the network slice instance or the network slice subnet instance is shared between another service consumer and the service consumer; and modifying the network slice instance or the network slice subnet instance.

[0023] According to one aspect, a device is provided comprising at least one processor and at least one memory, the memory comprising computer code for one or more programs, the at least one memory and the computer code being configured to, together with the at least one processor, cause the device to at least perform the following: receiving a request from a service consumer to allocate a network slice instance or a network slice subnet instance to the service consumer; allocating a network slice instance or a network slice subnet instance to the service consumer, wherein the network slice instance or the network slice subnet instance is newly created or already exists; and sending a return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

[0024] The at least one memory and the computer code may be configured to, together with the at least one processor, cause the apparatus to at least: when the network slice instance or the network slice subnet instance is newly created, send a first return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated; or when the network slice instance or the network slice subnet instance already exists, send a second return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated.

[0025] The first return code and the second return code may be different.

[0026] The first bit of the first return code and the first bit of the second return code may be the same or different.

[0027] The first bit of the first return code and the first bit of the second return code may be '2'.

[0028] The first return code may be '201'.

[0029] The second return code may be '211'.

[0030] The at least one memory and the computer code may be configured to, together with the at least one processor, cause the apparatus to at least: determine that the request includes information indicating that the network slice instance or the network slice subnet instance can be shared between another service consumer and the service consumer; determine that the network slice instance or the network slice subnet instance already exists and can be shared between another service consumer and the service consumer; and allocate the network slice instance or the network slice subnet instance that already exists and can be shared between another service consumer and the service consumer to the service consumer.

[0031] The at least one memory and the computer code may be configured to, together with the at least one processor, cause the apparatus to at least: determine that the request does not include information indicating that the network slice instance or the network slice subnet instance can be shared between another service consumer and the service consumer; create a new network slice instance or a network slice subnet instance; and allocate the newly created network slice instance or the network slice subnet instance to the service consumer.

[0032] The at least one memory and the computer code may be configured to, together with the at least one processor, cause the apparatus to at least: receive a request to deallocate the network slice instance or the network slice subnet instance from the service consumer; deallocate the network slice instance or the network slice subnet instance from the service consumer, wherein the network slice instance or the network slice subnet instance is terminated or modified; and send a return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance is terminated or modified.

[0033] The at least one memory and the computer code may be configured to, together with the at least one processor, cause the apparatus to at least: when the network slice instance or the network slice subnet instance is terminated, send a third return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated; or when the network slice instance or the network slice subnet instance is modified, send a fourth return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated.

[0034] The third return code and the fourth return code may be different.

[0035] The first bit of the third return code and the first bit of the fourth return code may be the same as or different from each other.

[0036] The first bit of the third return code and the first bit of the fourth return code may be '2'.

[0037] The third return code may be '204'.

[0038] The fourth return code may be '212'.

[0039] The at least one memory and the computer code may be configured to, together with the at least one processor, cause the apparatus to at least: determine that the network slice instance or the network slice subnet instance is not shared between another service consumer and the service consumer; and terminate the network slice instance or the network slice subnet instance.

[0040] The at least one memory and the computer code may be configured to, together with the at least one processor, cause the apparatus to at least: determine that the network slice instance or the network slice subnet instance is shared between another service consumer and the service consumer; and modify the network slice instance or the network slice subnet instance.

[0041] According to one aspect, a device is provided, comprising a circuit configured to: receive a request from a service consumer to allocate a network slice instance or a network slice subnet instance to the service consumer; allocate the network slice instance or the network slice subnet instance to the service consumer, wherein the network slice instance or the network slice subnet instance is newly created or already exists; and send a return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

[0042] The circuit can be configured to: when the network slice instance or the network slice subnet instance is newly created, send a first return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated; or when the network slice instance or the network slice subnet instance already exists, send a second return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated.

[0043] The first return code and the second return code may be different.

[0044] The first bit of the first return code and the first bit of the second return code may be the same or different.

[0045] The first bit of the first return code and the first bit of the second return code may be '2'.

[0046] The first return code may be '201'.

[0047] The second return code may be '211'.

[0048] The circuit can be configured to: determine that the request includes information indicating that the network slice instance or the network slice subnet instance can be shared between another service consumer and the service consumer; determine that the network slice instance or the network slice subnet instance already exists and can be shared between another service consumer and the service consumer; and allocate the network slice instance or the network slice subnet instance that already exists and can be shared between another service consumer and the service consumer to the service consumer.

[0049] The circuit can be configured to: determine that the request does not include information indicating that the network slice instance or the network slice subnet instance can be shared between another service consumer and the service consumer; newly create a network slice instance or a network slice subnet instance; and allocate the newly created network slice instance or the network slice subnet instance to the service consumer.

[0050] The circuit can be configured to: receive a request to deallocate the network slice instance or the network slice subnet instance from the service consumer; deallocate the network slice instance or the network slice subnet instance from the service consumer, wherein the network slice instance or the network slice subnet instance is terminated or modified; and send a return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance is terminated or modified.

[0051] The circuit can be configured to: when the network slice instance or the network slice subnet instance is terminated, send a third return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated; or when the network slice instance or the network slice subnet instance is modified, send a fourth return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated.

[0052] The third return code and the fourth return code may be different.

[0053] The first bit of the third return code and the first bit of the fourth return code may be the same as or different from each other.

[0054] The first bit of the third return code and the first bit of the fourth return code may be '2'.

[0055] The third return code may be '204'.

[0056] The fourth return code may be '212'.

[0057] The circuit can be configured to: determine that the network slice instance or the network slice subnet instance is not shared between another service consumer and the service consumer; and terminate the network slice instance or the network slice subnet instance.

[0058] The circuit can be configured to: determine that the network slice instance or the network slice subnet instance is shared between another service consumer and the service consumer; and modify the network slice instance or the network slice subnet instance.

[0059] According to one aspect, a method is provided, comprising: receiving a request for allocating the network slice instance or the network slice subnet instance from a service consumer; allocating the network slice instance or the network slice subnet instance to the service consumer, wherein the network slice instance or the network slice subnet instance is newly created or already exists; and sending a return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

[0060] The method may include: when the network slice instance or the network slice subnet instance is newly created, sending a first return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated; or, when the network slice instance or the network slice subnet instance already exists, sending a second return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated.

[0061] The first return code and the second return code may be different.

[0062] The first bit of the first return code and the first bit of the second return code may be the same or different.

[0063] The first bit of the first return code and the first bit of the second return code may be '2'.

[0064] The first return code may be '201'.

[0065] The second return code may be '211'.

[0066] The method may include: determining that the request includes information indicating that the network slice instance or the network slice subnet instance can be shared between another service consumer and the service consumer; determining that the network slice instance or the network slice subnet instance already exists and can be shared between another service consumer and the service consumer; and allocating the network slice instance or the network slice subnet instance that already exists and can be shared between another service consumer and the service consumer to the service consumer.

[0067] The method may include: determining that the request does not include information indicating that the network slice instance or the network slice subnet instance can be shared with the service consumer in another service consumer; newly creating a network slice instance or a network slice subnet instance; and allocating the newly created network slice instance or the network slice subnet instance to the service consumer.

[0068] The method may include: receiving a request to deallocate the network slice instance or the network slice subnet instance from the service consumer; deallocating the network slice instance or the network slice subnet instance from the service consumer, wherein the network slice instance or the network slice subnet instance is terminated or modified; and sending a return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance is terminated or modified.

[0069] The method may include: when the network slice instance or the network slice subnet instance is terminated, sending a third return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated; or, when the network slice instance or the network slice subnet instance is modified, sending a fourth return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated.

[0070] The third return code and the fourth return code may be different.

[0071] The first bit of the third return code and the first bit of the fourth return code may be the same as or different from each other.

[0072] The first bit of the third return code and the first bit of the fourth return code may be '2'.

[0073] The third return code may be '204'.

[0074] The fourth return code may be '212'.

[0075] The method may include: determining that the network slice instance or the network slice subnet instance is not shared between another service consumer and the service consumer; and terminating the network slice instance or the network slice subnet instance.

[0076] The method may include: determining that the network slice instance or the network slice subnet instance is shared between another service consumer and the service consumer; and modifying the network slice instance or the network slice subnet instance.

[0077] According to one aspect, a computer program comprising computer executable code is provided, which, when running on at least one processor, is configured to: receive a request from a service consumer to allocate a network slice instance or a network slice subnet instance to the service consumer; allocate the network slice instance or the network slice subnet instance to the service consumer, wherein the network slice instance or the network slice subnet instance is newly created or already exists; and send a return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

[0078] The computer program may include computer executable code, which, when running on at least one processor, is configured to: when the network slice instance or the network slice subnet instance is newly created, send a first return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated; or when the network slice instance or the network slice subnet instance already exists, send a second return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated.

[0079] The first return code and the second return code may be different.

[0080] The first bit of the first return code and the first bit of the second return code may be the same or different.

[0081] The first bit of the first return code and the first bit of the second return code may be '2'.

[0082] The first return code may be '201'.

[0083] The second return code may be '211'.

[0084] The computer program may include computer executable code, which, when running on at least one processor, is configured to: determine that the request includes information indicating that the network slice instance or the network slice subnet instance can be shared between another service consumer and the service consumer; determine that the network slice instance or the network slice subnet instance already exists and can be shared between another service consumer and the service consumer; and allocate the network slice instance or the network slice subnet instance that already exists and can be shared between another service consumer and the service consumer to the service consumer.

[0085] The computer program may include computer executable code, which, when running on the at least one processor, is configured to: determine that the request does not include information indicating that the network slice instance or the network slice subnet instance can be shared between another service consumer and the service consumer; create a new network slice instance or a network slice subnet instance; and allocate the newly created network slice instance or the network slice subnet instance to the service consumer.

[0086] The computer program may include computer executable code, which, when running on at least one processor, is configured to: receive a request to deallocate the network slice instance or the network slice subnet instance from the service consumer; deallocate the network slice instance or the network slice subnet instance from the service consumer, wherein the network slice instance or the network slice subnet instance is terminated or modified; and send a return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance is terminated or modified.

[0087] The computer program may include computer executable code, which, when running on at least one processor, is configured to: when the network slice instance or the network slice subnet instance is terminated, send a third return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated; or when the network slice instance or the network slice subnet instance is modified, send a fourth return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated.

[0088] The third return code and the fourth return code may be different.

[0089] The first bit of the third return code and the first bit of the fourth return code may be the same as or different from each other.

[0090] The first bit of the third return code and the first bit of the fourth return code may be '2'.

[0091] The third return code may be '204'.

[0092] The fourth return code may be '212'.

[0093] The computer program may include computer executable code, which, when running on at least one processor, is configured to: determine that the network slice instance or the network slice subnet instance is not shared between another service consumer and the service consumer; and terminate the network slice instance or the network slice subnet instance.

[0094] The computer program may include computer executable code, which, when running on at least one processor, is configured to: determine that the network slice instance or the network slice subnet instance is shared between another service consumer and the service consumer; and modify the network slice instance or the network slice subnet instance.

[0095] According to one aspect, a device is provided, comprising a means for: sending a request to a service provider (service producer) to allocate a network slice instance or a network slice subnet instance to a service consumer; and receiving a return code from the service provider indicating that the network slice instance or the network slice subnet instance has been allocated to the service consumer, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

[0096] The device may include a device for: when the network slice instance or the network slice subnet instance is newly created, receiving a first return code from the service provider indicating that the network slice instance or the network slice subnet instance has been allocated; or when the network slice instance or the network slice subnet instance already exists, receiving a second return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated.

[0097] The first return code and the second return code may be different.

[0098] The first bit of the first return code and the first bit of the second return code may be the same or different.

[0099] The first bit of the first return code and the first bit of the second return code may be '2'.

[0100] The first return code may be '201'.

[0101] The second return code may be '211'.

[0102] The device may include a device for: sending a request to the service provider to deallocate the network slice instance or the network slice subnet instance from the service consumer; and receiving a return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated from the service consumer, wherein the return code depends on whether the network slice instance or the network slice subnet instance is terminated or modified.

[0103] The device may include a device for: when the network slice instance or the network slice subnet instance is terminated, receiving a third return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated; or when the network slice instance or the network slice subnet instance is modified, receiving a fourth return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated.

[0104] The third return code and the fourth return code may be different.

[0105] The first bit of the third return code and the first bit of the fourth return code may be the same.

[0106] The first bit of the third return code and the first bit of the fourth return code may be '2'.

[0107] The third return code may be '204'.

[0108] The fourth return code may be '212'.

[0109] According to one aspect, a device is provided, comprising at least one processor and at least one memory for computer code of one or more programs, wherein the at least one memory and the computer code are configured to, together with the at least one processor, cause the device to perform at least the following: send a request to a service provider to allocate a network slice instance or a network slice subnet instance to a service consumer; and receive a return code from the service provider indicating that the network slice instance or the network slice subnet instance has been allocated to the service consumer, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

[0110] The at least one memory and the computer code may be configured to, together with the at least one processor, cause the apparatus to at least: when the network slice instance or the network slice subnet instance is newly created, receive a first return code from the service provider indicating that the network slice instance or the network slice subnet instance has been allocated; or when the network slice instance or the network slice subnet instance already exists, receive a second return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated.

[0111] The first return code and the second return code may be different.

[0112] The first bit of the first return code and the first bit of the second return code may be the same or different.

[0113] The first bit of the first return code and the first bit of the second return code may be '2'.

[0114] The first return code may be '201'.

[0115] The second return code may be '211'.

[0116] The at least one memory and the computer code may be configured to, together with the at least one processor, cause the apparatus to at least: send a request to the service provider to deallocate the network slice instance or the network slice subnet instance from the service consumer; and receive a return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated from the service consumer, wherein the return code depends on whether the network slice instance or the network slice subnet instance has been terminated or modified.

[0117] The at least one memory and the computer code may be configured to, together with the at least one processor, cause the apparatus to at least: receive a third return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated when the network slice instance or the network slice subnet instance is terminated; or receive a fourth return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated when the network slice instance or the network slice subnet instance is modified.

[0118] The third return code and the fourth return code may be different.

[0119] The first bit of the third return code and the first bit of the fourth return code may be the same.

[0120] The first bit of the third return code and the first bit of the fourth return code may be '2'.

[0121] The third return code may be '204'.

[0122] The fourth return code may be '212'.

[0123] According to one aspect, a device is provided, comprising a configuration configured to: send a request to a service provider to allocate a network slice instance or a network slice subnet instance to a service consumer; and receive a return code from the service provider indicating that the network slice instance or the network slice subnet instance has been allocated to the service consumer, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

[0124] The device may include a circuit configured to: when the network slice instance or the network slice subnet instance is newly created, receive a first return code from the service provider indicating that the network slice instance or the network slice subnet instance has been allocated; or when the network slice instance or the network slice subnet instance already exists, receive a second return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated.

[0125] The first return code and the second return code may be different.

[0126] The first bit of the first return code and the first bit of the second return code may be the same or different.

[0127] The first bit of the first return code and the first bit of the second return code may be '2'.

[0128] The first return code may be '201'.

[0129] The second return code may be '211'.

[0130] The device may include a circuit configured to: send a request to the service provider to deallocate the network slice instance or the network slice subnet instance from the service consumer; and receive a return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated from the service consumer, wherein the return code depends on whether the network slice instance or the network slice subnet instance is terminated or modified.

[0131] The device may include a circuit configured to: when the network slice instance or the network slice subnet instance is terminated, receive a third return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated; or when the network slice instance or the network slice subnet instance is modified, receive a fourth return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated.

[0132] The third return code and the fourth return code may be different.

[0133] The first bit of the third return code and the first bit of the fourth return code may be the same.

[0134] The first bit of the third return code and the first bit of the fourth return code may be '2'.

[0135] The third return code may be '204'.

[0136] The fourth return code may be '212'.

[0137] According to one aspect, a method is provided, comprising: sending a request to a service provider to allocate a network slice instance or a network slice subnet instance to a service consumer; and receiving a return code from the service provider indicating that the network slice instance or the network slice subnet instance has been allocated to the service consumer, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

[0138] The method may include: when the network slice instance or the network slice subnet instance is newly created, receiving a first return code from the service provider indicating that the network slice instance or the network slice subnet instance has been allocated; or when the network slice instance or the network slice subnet instance already exists, receiving a second return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated.

[0139] The first return code and the second return code may be different.

[0140] The first bit of the first return code and the first bit of the second return code may be the same or different.

[0141] The first bit of the first return code and the first bit of the second return code may be '2'.

[0142] The first return code may be '201'.

[0143] The second return code may be '211'.

[0144] The method may include: sending a request to the service provider to deallocate the network slice instance or the network slice subnet instance from the service consumer; and receiving a return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated from the service consumer, wherein the return code depends on whether the network slice instance or the network slice subnet instance has been terminated or modified.

[0145] The method may include: when the network slice instance or the network slice subnet instance is terminated, receiving a third return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated; or, when the network slice instance or the network slice subnet instance is modified, receiving a fourth return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated.

[0146] The third return code and the fourth return code may be different.

[0147] The first bit of the third return code and the first bit of the fourth return code may be the same.

[0148] The first bit of the third return code and the first bit of the fourth return code may be '2'.

[0149] The third return code may be '204'.

[0150] The fourth return code may be '212'.

[0151] According to one aspect, a computer program comprising computer executable code is provided, which, when running on at least one processor, is configured to: send a request to a service provider to allocate a network slice instance or a network slice subnet instance to a service consumer; and receive a return code from the service provider indicating that the network slice instance or the network slice subnet instance has been allocated to the service consumer, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

[0152] The computer program may include computer executable code, which, when running on at least one processor, is configured to: when the network slice instance or the network slice subnet instance is newly created, receive a first return code from the service provider indicating that the network slice instance or the network slice subnet instance has been allocated; or when the network slice instance or the network slice subnet instance already exists, receive a second return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated.

[0153] The first return code and the second return code may be different.

[0154] The first bit of the first return code and the first bit of the second return code may be the same or different.

[0155] The first bit of the first return code and the first bit of the second return code may be '2'.

[0156] The first return code may be '201'.

[0157] The second return code may be '211'.

[0158] The computer program may include computer executable code, which, when running on at least one processor, is configured to: send a request to the service provider to deallocate the network slice instance or the network slice subnet instance from the service consumer; and receive a return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated from the service consumer, wherein the return code depends on whether the network slice instance or the network slice subnet instance is terminated or modified.

[0159] The computer program may include computer executable code, which, when running on at least one processor, is configured to: when the network slice instance or the network slice subnet instance is terminated, receive a third return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated; or when the network slice instance or the network slice subnet instance is modified, receive a fourth return code from the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated.

[0160] The third return code and the fourth return code may be different.

[0161] The first bit of the third return code and the first bit of the fourth return code may be the same.

[0162] The first bit of the third return code and the first bit of the fourth return code may be '2'.

[0163] The third return code may be '204'.

[0164] The fourth return code may be '212'.

[0165] According to one aspect, a computer-readable medium is provided, comprising program instructions stored thereon for executing at least one of the above methods.

[0166] According to one aspect, a non-transitory computer-readable medium is provided, comprising program instructions stored thereon for executing at least one of the above methods.

[0167] According to one aspect, a non-volatile tangible storage medium is provided, comprising program instructions stored thereon for executing at least one of the above methods.

[0168] In the above, many different aspects have been described. It should be understood that further aspects can be provided by combining any two or more of the above aspects.

[0169] Various other aspects are also described in the following detailed description and appended claims.

[0170] List of abbreviations

[0171] AF: Application Function

[0172] AMF: Access and Mobility Management Function

[0173] API: Application Programming Interface

[0174] BS: Base Station

[0175] CU: Centralized Unit

[0176] CRUD: Create Read Update Delete

[0177] DL: Downlink

[0178] DU: Distributed Unit

[0179] eMBB: Enhanced Mobile Broadband

[0180] gNB:gNodeB

[0181] GSM: Global System for Mobile Communications

[0182] GSMA: Global System for Mobile Communications Association

[0183] GST: Generic Network Slicing Template

[0184] HSS: Home Subscriber Server

[0185] HTTP: Hypertext Transfer Protocol

[0186] IOC: Information Object Class

[0187] IoT: Internet of Things

[0188] LTE: Long Term Evolution

[0189] MAC: Media Access Control

[0190] MIoT: Massive Internet of Things

[0191] MS: Mobile Station

[0192] MTC: Machine Type Communication

[0193] NEF: Network Exposure Function

[0194] NF: Network Function

[0195] NR: New Radio

[0196] NRF: Network Repository Function

[0197] NSD: Network Service Descriptor

[0198] NSI: Network Slicing Example

[0199] NSSI: Network Slicing Subnet Instance

[0200] PDU: Packet Data Unit

[0201] RAM: Random Access Memory

[0202] (R)AN: (Radio) Access Network

[0203] REST: Representational State Transfer

[0204] ROM: Read Only Memory

[0205] SLA: Service Level Agreement

[0206] SMF: Session Management Function

[0207] TN: Transmission Network

[0208] TR: Technical Report

[0209] TS: Technical Specifications

[0210] UE: User Equipment

[0211] UMTS: Universal Mobile Telecommunications System

[0212] URLLC: Ultra-Reliable Low Latency Communication

[0213] 3GPP: Third Generation Partnership Project

[0214] 5G: 5th Generation

[0215] 5GC: 5G Core Network

[0216] 5GS: 5G System BRIEF DESCRIPTION OF THE DRAWINGS

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

[0218] Figure 1 A schematic diagram of a 5G system is shown;

[0219] Figure 2 shows a schematic diagram of the control device;

[0220] Figure 3 A schematic diagram of a user equipment is shown;

[0221] Figure 4 A block diagram of a method for managing network slice instances and network slice subnet instance allocation in a communication system performed by a service provider is shown;

[0222] Figure 5 A block diagram illustrating a method for managing network slice instances and network slice subnet instance allocation in a communication system performed by a service consumer; and

[0223] Figure 6 A schematic diagram of a non-volatile storage medium storing instructions that, when executed by a processor, allow the processor to perform Figure 4 and 5 One or more steps in a method. DETAILED DESCRIPTION

[0224] In some of the following embodiments, reference is made to mobile communication devices capable of communicating via a wireless cellular system and to mobile communication systems providing services for such mobile communication devices. Figure 1 , 2 and 3 briefly explain some general principles of wireless communication systems, their access systems and mobile communication devices to help understand the technology on which the examples are based.

[0225] Figure 1 A schematic representation of a 5G system (5GS) is shown. The 5GS may include a user equipment (UE), a (radio) access network ((R)AN), a 5G core network (5GC), one or more application functions (AFs), and one or more data networks (DNs).

[0226] The 5G(R)AN may include one or more gNodeB(gNB) distributed unit functions, connected to one or more gNodeB(gNB) centralized unit functions.

[0227] 5GC may include access and mobility management function (AMF), session management function (SMF), authentication server function (AUSF), user data management (UDM), user plane function (UPF) and / or network exposure function (NEF).

[0228] Figure 2 The diagram shows the Figure 1 An example of a control device 200 for the functions of a (R)AN or 5GC shown. The control device may include at least one random access memory (RAM) 211a, at least one read-only memory (ROM) 211b, at least one processor 212, 213, and an input / output interface 214. At least one processor 212, 213 may be coupled to the RAM 211a and the ROM 211b. At least one processor 212, 213 may be configured to execute appropriate software code 215. The software code 215 may, for example, allow one or more steps to be performed to perform one or more aspects of the present invention. The software code 215 may be stored in the ROM 211b. The control device 200 may be interconnected with another control device 200 that controls other functions of a 5G (R)AN or 5GC. In some embodiments, each function of the (R)AN or 5GC includes a control device 200. In an alternative embodiment, two or more functions of the (R)AN or 5GC may share a control device.

[0229] Figure 3 An example of a UE 300 is shown, such as Figure 1 UE 300 is a UE shown in . UE 300 can be provided by any device capable of sending and receiving radio signals. Non-limiting examples include user equipment, a mobile station (MS) or a mobile device (such as a mobile phone or a so-called "smartphone"), a computer equipped with a wireless interface card or other wireless interface facilities (e.g., a USB dongle), a personal data assistant (PDA) or tablet computer equipped with wireless communication capabilities, a machine type communication (MTC) device, a cellular Internet of Things (CIoT) device, or any combination of these or the like. For example, UE 300 can provide data transmission for carrying communications. The communication can be one or more of voice, electronic mail (email), text messaging, multimedia, data, machine data, etc.

[0230] The UE 300 may receive signals over the air or radio interface 307 via appropriate means for reception, and may transmit signals via appropriate means for transmitting radio signals. Figure 3 In the mobile device, the transceiver arrangement is schematically designated by block 306. The transceiver arrangement 306 may be provided, for example, by means of a radio component and an associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

[0231] The UE 300 may be equipped with at least one processor 301, at least one memory ROM 302a, at least one RAM 302b and other possible components 303 for software and hardware assistance to perform the tasks it is designed to perform, including controlling access to access systems and other communication devices and communication with access systems and other communication devices. At least one processor 301 is coupled to RAM 302b and ROM 302a. At least one processor 301 may be configured to execute appropriate software code 308. The software code 308 may, for example, allow one or more of the present aspects to be performed. The software code 308 may be stored in ROM 302a.

[0232] The processor, memory and other related control devices may be provided on an appropriate circuit board and / or in a chipset. This feature is indicated by reference numeral 304. The device may optionally have a user interface, such as a keyboard 305, a touch screen or touch pad, a combination thereof, etc. Optionally, one or more of a display, a speaker and a microphone may be provided, depending on the type of device.

[0233] 3GPP TS28.531 defines the Network Slice Instance (NSI) and Network Slice Subnet Instance (NSSI) allocation and deallocation use cases. 3GPP TS28.531 defines allocateNsi, allocateNssi, deallocateNsi and deallocateNssi operations, procedures and RESTful HTTP based solution set implementation.

[0234] The allocateNsi and allocateNssi operations require that in a successful response the NSI or NSSI is either newly created or already exists and is shared (ie, reused).

[0235] The deallocateNsi and deallocateNssi operations require that the NSI or NSSI be terminated (ie, deleted) or modified in a successful response.

[0236] The content of 3GPP TS28.531 Section 5.1.1 Network Slice Instance Allocation is as follows.

[0237]

[0238]

[0239]

[0240] 3GPP TS28.531 Section 5.1.2 Network Slice Subnet Instance Allocation reads as follows.

[0241]

[0242]

[0243]

[0244] The content of 3GPP TS28.531 Section 5.1.3 Network Slice Instance Deallocation is as follows.

[0245]

[0246]

[0247] The content of 3GPP TS28.531 Section 5.1.4 Network Slice Subnet Instance Deallocation is as follows.

[0248]

[0249]

[0250] The allocateNsi and allocateNssi operations may not be implemented with normal create-read-update-delete (CRUD) operations because they may not be clean create operations (i.e., may create a new NSI or NSSI, or may share an existing NSI or NSSI).

[0251] In the above, the term "clean" may mean that for a CRUD operation, an operation only provides a successful result. For example, for a C (i.e., create) operation, a successful result may be to create a new resource.

[0252] 3GPP TS28.541 defines the NetworkSlice and NetworkSliceSubnet information object classes (IOCs). The NetworkSlice IOC includes the attribute ServiceProfile. The attribute Service Profile captures a set of requirements for a NSI, such as enhanced mobile broadband (eMBB), massive Internet of Things (MIoT), or ultra-reliable low latency communications (URLLC). The NetworkSliceSubnet IOC includes the attribute SliceProfile. The attribute SliceProfile captures resource model information that describes the static parameters and functional components of the NSSI. It may include a slice profile, a network slice subnet type (e.g., RANeMBB, CN eMBB), additional system features (e.g., multicast, edge computing), priority, QoS attributes (e.g., bandwidth, latency, number of subscribers, etc.), or a network service descriptor (NSD) identifier (ID).

[0253] 3GPP TS28.531 Section 9 (Version 17.3.0) defines an OpenAPI with a Representational State Transfer (REST) ​​implementation of allocateNsi and allocateNssi operations. Such OpenAPI creates a new ServiceProfile IOC and SliceProfile resource IOC for each successful request, respectively. This is not semantically correct because the attributes of the IOC should not be created as IOCs.

[0254] RFC2616 Section 6 deals with Hypertext Transfer Protocol (HTTP) return codes.

[0255] RFC2616 Section 6.1.1 Status Codes and Reason Phrases are as follows.

[0256] The status-code element is a 3-bit integer result code of the attempt to understand and satisfy the request. These codes are fully defined in Section 10. The reason-phrase is intended to give a brief textual description of the status-code. The status-code is intended for use by automated machines, while the reason-phrase is intended for use by human users. Clients are not required to examine or display the reason-phrase.

[0257] The first digit of the status-code defines the category of the response. The last two digits do not have any classification role. The first digit has 5 values:

[0258] -1xx: Informational - Request received, continue processing

[0259] -2xx: Success - The operation was successfully received, understood, and accepted

[0260] - 3xx: Redirect - Further action must be taken to complete the request

[0261] - 4xx: Client Error - The request included incorrect syntax or could not be satisfied

[0262] - 5xx: Server Error - The server failed to fulfill an apparently valid request

[0263] Given below are the individual values ​​of the numeric status codes defined for HTTP / 1.1, along with an example set of corresponding reason-phrases. The reason-phrases listed here are suggestions only - they may be replaced by locally equivalent phrases without affecting the protocol.

[0264] Status-Code=(Status-Code=)

[0265] "100"; Section 10.1.1: Continue

[0266] "101"; Section 10.1.2: Switching Protocols

[0267] "200"; Section 10.2.1: OK

[0268] "201"; Section 10.2.2: Created

[0269] "202"; Section 10.2.3: Accepted

[0270] "203"; Section 10.2.4: Non-Authoritative Information

[0271] "204"; Section 10.2.5: No Content

[0272] "205"; Section 10.2.6: Reset Content

[0273] "206"; Section 10.2.7: Partial Content

[0274] "300"; Section 10.3.1: Multiple Choices

[0275] "301"; Section 10.3.2: Moved Permanently

[0276] "302"; Section 10.3.3: Found

[0277] "303"; Section 10.3.4: See Other

[0278] "304"; Section 10.3.5: Not Modified

[0279] "305"; Section 10.3.6: Use Proxy

[0280] "307"; Section 10.3.8: Temporary Redirect

[0281] "400"; Section 10.4.1: Bad Request

[0282] "401"; Section 10.4.2: Unauthorized

[0283] "402"; Section 10.4.3: Payment Required (payment required)

[0284] "403"; Section 10.4.4:Forbidden

[0285] "404"; Section 10.4.5: Not Found

[0286] "405"; Section 10.4.6: Method Not Allowed

[0287] "406"; Section 10.4.7: Not Acceptable

[0288] "407"; Section 10.4.8: Proxy Authentication Required (Proxy authentication required)

[0289] "408"; Section 10.4.9: Request Time-out

[0290] "409"; Section 10.4.10: Conflict

[0291] "410"; Section 10.4.11: Gone

[0292] "411"; Section 10.4.12: Length Required (length required)

[0293] "412"; Section 10.4.13: Precondition Failed

[0294] "413"; Section 10.4.14: Request Entity Too Large

[0295] "414"; Section 10.4.15: Request-URI Too Large

[0296] "415"; Section 10.4.16: Unsupported Media Type

[0297] "416"; Section 10.4.17: Requested range not satisfiable "417"; Section 10.4.18: Expectation Failed

[0298] "500"; Section 10.5.1: Internal Server Error

[0299] "501"; Section 10.5.2: Not Implemented

[0300] "502"; Section 10.5.3: Bad Gateway

[0301] "503"; Section 10.5.4: Service Unavailable

[0302] "504"; Section 10.5.5: Gateway Time-out

[0303] "505"; Section 10.5.6: HTTP Version not supported extension-code

[0304] extension-code = 3DIGIT

[0305] Reason-Phrase = *<TEXT, excluding(排除)CR,LF>

[0306] HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes, although such understanding is obviously desirable. However, applications MUST understand the category of any status code (indicated by the first digit) and treat any unrecognized response as equivalent to an x00 status code of that category, with the exception that unrecognized responses MUST NOT be cached. For example, if a client receives an unrecognized status code 431, it can safely assume that something went wrong with its request and treat the response as if it had received a 400 status code. In this case, the user agent SHOULD present the entity returned with the response to the user, as that entity might include human-readable information that could explain the unusual status.

[0307] RFC2616 clause 10.2 Success 2xx content is as follows.

[0308] This type of status code indicates that the client's request was successfully received, understood, and accepted.

[0309] One or more aspects of the present application propose enhancements to the allocateNsi, allocateNssi, deallocateNsi, and deallocateNssi operations implemented by OpenAPI REST.

[0310] One or more aspects of the present application propose enhancements to response flows and response messages.

[0311] One or more aspects of the present application separate the successful response stream into different types of responses through different return codes.

[0312] For allocateNsi and allocateNssi operations, a first type of response may be used for a newly created NSI or NSSI, while a second type of response may be used for an existing NSI or NSSI (ie, no newly created NSI or NSSI).

[0313] Different HTTP success return codes can be used to distinguish between the two types of responses. Since both types of responses are successful responses, the '2xx' return code can be used. The first return code '201' can be used for the first type of response to comply with RFC2616 Section 6 and POST semantics. The second return code "211" can be used in the second response type to comply with RFC2616 Section 6. The first return code and / or the second return code can include an extension (for example, the second return code can be '211.1').

[0314] It should be understood that other first return codes and second return codes, with or without extensions, may be used as long as the first code and the second code do not conflict.

[0315] ServiceProfile IOC or SliceProfile ICO cannot be created.

[0316] For deallocateNsi and deallocateNssi operations, a third type of response may be used for a terminated NSI or NSSI, and a fourth type of response may be used for a modified NSI or NSSI (ie, not terminated) or a non-terminated or modified NSI or NSSI (ie, do nothing).

[0317] Different HTTP success return codes can be used to distinguish between the two types of responses. Since both types of responses are successful responses, a '2xx' return code can be used. A third return code "204" can be used in the third type of response to comply with RFC2616 Section 6 and DELETE semantics. A fourth return code "212" can be used in the fourth type of response type to comply with RFC2616 Section 6. The third return code and / or the fourth return code may include an extension (e.g., the second return code may be "212.1")

[0318] It should be understood that other third return codes and fourth return codes may be used, whether extended or not, as long as the third return code and the fourth return code do not conflict.

[0319] The return codes and semantics may be updated for use with clauses 9.1.2, 9.1.3, 9.2.1.2, 9.2.1.3 in 3GPP TS 28.531 as follows.

[0320] 9.1.1.2 Operation allocateNsi

[0321] The operation is to allocate a network slice instance provided by the service provider, which can be new or existing.

[0322] Table 9.1.2-1: Mapping of IS operation input parameters to SS equivalents (HTTP POST)

[0323]

[0324] Table 9.1.2-2: Mapping of IS operation output parameters to SS equivalents (HTTP POST)

[0325]

[0326] The message flow of the allocation is as follows:

[0327] 1. The MnS consumer sends an HTTP POST request to the MnS provider.

[0328] - The message body SHOULD carry a complete representation of the resource to be created. The resource identifier SHOULD be absent or carry the null semantics.

[0329] 2. The MnS provider sends an HTTP POST response to the MnS consumer.

[0330] - In the case of success, when a new NetworkSlice instance resource is created, "201 Created" should be returned. The message body should contain a complete representation of the ServiceProfile and networkSliceDN that identifies the created NetworkSlice MOI.

[0331] When using an existing NetworkSlice instance, "211 Shared" should be returned and the message body should include the complete representation of the ServiceProfile and networkSliceDN that identifies the shared NetworkSlice MOI.

[0332] - In case of failure, an appropriate error code should be returned. The response message body can provide additional error information.

[0333] 9.1.1.3 DeallocateNsi Operation

[0334] This action deallocates the service profile in the NSI. The provider may terminate the requested NSI or modify the requested NSI without termination to satisfy the request.

[0335] Table 9.1.1.3-1: Mapping of IS operation input parameters to SS equivalents (HTTP DELETE)

[0336] IS operation parameter name SS parameter location SS parameter name SS parameter type Qualifiers networkSliceDN Request Body n / a resource M serviceProfileId Request Body n / a resource M

[0337] Table 9.1.1.3-2: Mapping of IS operation output parameters to SS equivalents (HTTP DELETE)

[0338]

[0339] The message flow for deallocation is as follows:

[0340] 1. The MnS consumer sends an HTTP delete request to the MnS provider.

[0341] -The message body shall include the networkSliceDN identifying the NetworkSlice MOI.

[0342] 2. The MnS provider sends an HTTP delete response to the MnS consumer.

[0343] - Upon successful termination of a NetworkSlice instance, a 204 No Content should be returned.

[0344] - "212 ResourceNotDeleted" should be returned when a network slice instance is successfully modified or when no changes are made to the network slice instance.

[0345] - If failed, an appropriate error code should be returned. The response message body may provide additional error information.

[0346] 9.2.1.2 Operation allocateNssi

[0347] The operation is to allocate a network slice instance provided by the service provider, which can be new or existing.

[0348] Table 9.2.1.2-1: Mapping of IS operation input parameters to SS equivalents (HTTP POST)

[0349] IS operation parameter name SS parameter location SS parameter name SS parameter type Qualifiers attributeListIn Request Body n / a resource M

[0350] Table 9.2.1.2-2: Mapping of IS operation output parameters to SS equivalents (HTTP POST)

[0351]

[0352] The message flow of the allocation is as follows:

[0353] 1. The MnS consumer sends an HTTP POST request to the MnS provider.

[0354] - The message body SHOULD carry a complete representation of the resource to be created. The resource identifier SHOULD be absent or carry the null semantics.

[0355] 2. The MnS provider sends an HTTP POST response to the MnS consumer.

[0356] - If successful, a "201 Created" message should be returned when creating a new NetworkSliceSubnet instance resource. The message body should include a complete representation of the SliceProfile and networkSliceSubnetDN identifying the created NetworkSliceSubnet MOI.

[0357] When an existing NetworkSliceSubnet instance is used, "211 Shared" should be returned and the message body should include a complete representation of the SliceProfile and networkSliceSubnetDN identifying the shared NetworkSliceSubnet MOI.

[0358] - If failed, an appropriate error code should be returned. The response message body may provide additional error information.

[0359] 9.2.1.3 Operation deallocateNssi

[0360] This action deallocates the slice profile in the NSSI. The provider can either terminate the requested NSSI or modify the requested NSSI without terminating it to satisfy the request.

[0361] Table 9.2.1.3-1: Mapping of IS operation input parameters to SS equivalents (HTTP DELETE)

[0362] IS operation parameter name SS parameter location SS parameter name SS parameter type Qualifiers networkSliceSubnetDN Request Body n / a Resource M sliceProfileId Request Body n / a Resource M

[0363] Table 9.2.1.3-2: Mapping of IS operation output parameters to SS equivalents (HTTP DELETE)

[0364]

[0365] The message flow for deallocation is as follows:

[0366] 1. The MnS consumer sends an HTTP DELETE request to the MnS provider.

[0367] -The message body shall include the networkSliceSubnetDN identifying the NetworkSliceSubnet MOI.

[0368] 2. The MnS provider sends an HTTP DELETE response to the MnS consumer.

[0369] - If the NetworkSliceSubnet instance is successfully terminated, "204 No Content" should be returned.

[0370] -If the modification of the NetworkSliceSubnet instance is successful, "212 Resource not deleted" should be returned.

[0371] - If failed, an appropriate error code should be returned. The response message body may provide additional error information.

[0372] Figure 4 A block diagram of a method performed by a service provider for managing NSIs and NSSI allocations in a communication system is shown.

[0373] In step 400, a service provider may receive a request from a service consumer to allocate an NSI or NSSI to the service consumer.

[0374] In step 402, the service provider may allocate an NSI or NSSI to the service consumer, wherein the NSI or NSSI is newly created or already exists.

[0375] In step 404, the service provider may send a return code to the service consumer indicating that the NSI or NSSI has been allocated, wherein the return code depends on whether the NSI or NSSI is newly created or already exists.

[0376] When a NSI or NSSI is newly created, the service provider may send a first return code to the service consumer indicating that the NSI or NSSI has been allocated.

[0377] When the NSI or NSSI already exists, the service provider may send a second return code to the service consumer indicating that the NSI or NSSI has been allocated.

[0378] The first return code and the second return code may be different.

[0379] The first bit of the first return code and the first bit of the second return code may be the same or different.

[0380] The first bit of the first return code and the first bit of the second return code may be '2'.

[0381] The first return code may be '201'.

[0382] The second return code may be '211'.

[0383] The service provider may determine that the request includes information indicating that the NSI or NSSI may be shared between another service consumer and the service consumer. The service provider may determine that a certain NSI or NSSI already exists and may be shared between another service consumer and the service consumer. The service provider may assign the NSI or NSSI that already exists and may be shared between another service consumer and the service consumer to the service consumer.

[0384] The service provider may determine that the request does not include information indicating that the NSI or NSSI can be shared between another service consumer and the service consumer. The service provider may create a new NSI or network slice subnet instance. The service provider may assign the newly created NSI or NSSI to the service consumer.

[0385] The service provider may receive a request from the service consumer to deallocate the NSI or NSSI from the service consumer. The service provider may deallocate the NSI or NSSI from the service consumer, wherein the NSI or NSSI is terminated or modified. The service provider may send a return code to the service consumer indicating that the NSI or NSSI has been deallocated, wherein the return code depends on whether the NSI or NSSI is terminated or modified.

[0386] When the NSI or NSSI is terminated, the service provider may send a third return code to the service consumer indicating that the NSI or NSSI has been deallocated.

[0387] When the NSI or NSSI is modified, the service provider may send a fourth return code to the service consumer indicating that the NSI or NSSI has been deallocated.

[0388] The third return code and the fourth return code may be different.

[0389] The first bit of the third return code and the first bit of the fourth return code may be the same as or different from each other.

[0390] The first bit of the third return code and the first bit of the fourth return code may be '2'.

[0391] The third return code may be '204'.

[0392] The fourth return code may be '212'.

[0393] The service provider can determine that the NSI or NSSI is not shared between another service consumer and the service consumer. The service provider can terminate the NSI or network slice subnet instance.

[0394] The service provider can determine that the NSI or NSSI is shared with another service consumer and between service consumers. The service provider can modify the NSI or network slice subnet instance.

[0395] Figure 5 A block diagram of a method for managing NSI and NSSI allocation in a communication system performed by a service consumer is shown.

[0396] In step 500, the service consumer may send a request to the service provider to allocate an NSI or NSSI to the service consumer.

[0397] In step 502, the service consumer may receive a return code from the service provider, the return code indicating that the NSI or NSSI has been allocated to the service consumer, wherein the return code depends on whether the NSI or NSSI is newly created or already exists.

[0398] When a NSI or NSSI is newly created, the service consumer may receive a first return code from the service provider indicating that the NSI or NSSI has been allocated. When the NSI or NSSI already exists, the service consumer may receive a second return code from the service consumer indicating that the NSI or NSSI has been allocated.

[0399] The first return code and the second return code may be different.

[0400] The first bit of the first return code and the first bit of the second return code may be the same or different.

[0401] The first bit of the first return code and the first bit of the second return code may be '2'.

[0402] The first return code may be '201'.

[0403] The second return code may be '211'.

[0404] The service consumer may send a request to the service provider to deallocate the NSI or NSSI from the service consumer. The service consumer may send or receive a return code from the service consumer indicating that the NSI or NSSI has been deallocated from the service consumer, wherein the return code depends on whether the NSI or NSSI is terminated or modified.

[0405] When the NSI or NSSI is terminated, the service consumer may receive a third return code from the service consumer indicating that the NSI or NSSI has been deallocated. When the NSI or NSSI is modified, the service consumer may receive a fourth return code from the service consumer indicating that the NSI or NSSI has been deallocated.

[0406] The third return code and the fourth return code may be different.

[0407] The first bit of the third return code and the first bit of the fourth return code may be the same.

[0408] The first bit of the third return code and the first bit of the fourth return code may be '2'.

[0409] The third return code may be '204'.

[0410] The fourth return code may be '212'.

[0411] Figure 6 A non-volatile memory medium 6000 (storing instructions and / or parameters that, when executed by a processor, allow the processor to perform Figure 4 and Figure 5 A schematic diagram of one or more steps of a method.

[0412] It is noted that while the above describes exemplifying embodiments, there are numerous variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

[0413] It should be understood that although the above concepts are discussed in the context of 5GS, one or more of these concepts may be applicable to other cellular systems.

[0414] Therefore, the embodiments may vary within the scope of the appended claims. In general, some embodiments may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may implement firmware or software that may be executed by a controller, microprocessor, or other computing device, but the embodiments are not limited thereto. Although various embodiments may be illustrated and described by block diagrams, flow charts, or using some other graphical representations, it is fully understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0415] These embodiments may be implemented by computer software stored in a memory and executable by at least one data processor of the entity involved, or by hardware, or by a combination of software and hardware. Furthermore, it should also be noted in this regard that any process (e.g. Figure 4 and Figure 5 The software may be stored on such physical media as memory chips or memory blocks implemented within a processor, magnetic media such as hard disk or floppy disks, and optical media such as DVDs and their data variants, CDs.

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

[0417] Alternatively or additionally, some embodiments may be implemented using a circuit. The circuit may be configured to perform one or more of the previously described functions and / or method steps. The circuit may be provided in a base station and / or a communication device.

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

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

[0420] (b) A combination of hardware circuits and software, such as:

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

[0422] (ii) any portion of hardware processors and software (including digital signal processors), software and memory that work together to enable a device such as a communication device or base station to perform the various functions described above; and

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

[0424] This definition of circuitry applies to one or all uses of the term in this application, including in any claims. As a further example, as used in this application, the term "circuit" also covers an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term "circuit" also covers, for example, an integrated device.

[0425] The foregoing description has provided a complete and informative description of some embodiments by way of exemplary and non-limiting examples, however, various modifications and adaptations may become apparent to those skilled in the relevant art when the foregoing description is read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the present teachings will still fall within the scope defined by the appended claims.

Claims

1. An apparatus comprising at least one processor and at least one memory, the memory comprising computer code for one or more programs, the at least one memory and the computer code being configured, together with the at least one processor, to cause the apparatus to at least perform the following: receiving a request from a service consumer to allocate a network slice instance or a network slice subnet instance to the service consumer; Allocating a network slice instance or a network slice subnet instance to the service consumer, wherein the network slice instance or the network slice subnet instance is newly created or already exists; and A return code is sent to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

2. The device according to claim 1, wherein: The at least one memory and the computer code are configured to, with the at least one processor, cause the apparatus to at least: When the network slice instance or the network slice subnet instance is newly created, sending a first return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated; or When the network slice instance or the network slice subnet instance already exists, a second return code is sent to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated.

3. The device as claimed in claim 2, wherein: The first return code and the second return code are different.

4. The device according to claim 3, wherein: The first bit of the first return code and the first bit of the second return code are the same as or different from each other.

5. The device according to any one of claims 1 to 4, wherein: The at least one memory and the computer code are configured to, with the at least one processor, cause the apparatus to at least: determining that the request includes information indicating that the network slice instance or the network slice subnet instance can be shared between another service consumer and the service consumer; Determining that the network slice instance or the network slice subnet instance already exists and can be shared between another service consumer and the service consumer; as well as The network slice instance or the network slice subnet instance that already exists and can be shared between another service consumer and the service consumer is allocated to the service consumer.

6. The device according to any one of claims 1 to 4, wherein: The at least one memory and the computer code are configured to, with the at least one processor, cause the apparatus to at least: determining that the request does not include information indicating that the network slice instance or the network slice subnet instance can be shared between another service consumer and the service consumer; Create a new network slice instance or network slice subnet instance; Allocate the newly created network slice instance or network slice subnet instance to the service consumer.

7. The device according to any one of claims 1 to 6, wherein: The at least one memory and the computer code are configured to, with the at least one processor, cause the apparatus to at least: Receiving a request from the service consumer to deallocate the network slice instance or the network slice subnet instance; deallocating the network slice instance or the network slice subnet instance from the service consumer, wherein the network slice instance or the network slice subnet instance is terminated or modified; and Sending a return code to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance has been terminated or modified.

8. The device according to claim 7, wherein: The at least one memory and the computer code are configured to, with the at least one processor, cause the apparatus to at least: When the network slice instance or the network slice subnet instance is terminated, a third return code is sent to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated; or When the network slice instance or the network slice subnet instance is modified, a fourth return code is sent to the service consumer indicating that the network slice instance or the network slice subnet instance has been deallocated.

9. The device of claim 8, wherein: The third return code and the fourth return code are different.

10. The device of claim 9, wherein: The first bit of the third return code is the same as or different from the first bit of the fourth return code.

11. The device according to any one of claims 7 to 10, wherein: The at least one memory and the computer code are configured to, with the at least one processor, cause the apparatus to at least: Determining that the network slice instance or the network slice subnet instance is not shared between another service consumer and the service consumer; as well as Terminate the network slice instance or the network slice subnet instance.

12. The device according to any one of claims 7 to 10, wherein: The at least one memory and the computer code are configured to, with the at least one processor, cause the apparatus to at least: Determining that the network slice instance or the network slice subnet instance is shared between another service consumer and the service consumer; as well as Modify the network slice instance or the network slice subnet instance.

13. An apparatus comprising at least one processor and at least one memory, the memory comprising computer code for one or more programs, the at least one memory and the computer code being configured, together with the at least one processor, to cause the apparatus to at least perform the following: Sending a request to the service provider to allocate a network slice instance or a network slice subnet instance to the service consumer; and receiving a return code from the service provider indicating that the network slice instance or the network slice subnet instance has been allocated to the service consumer, wherein: The return code depends on whether the network slice instance or network slice subnet instance is newly created or already exists.

14. The device of claim 13, wherein: The at least one memory and the computer code are configured to, with the at least one processor, cause the apparatus to at least: When the network slice instance or the network slice subnet instance is newly created, receiving a first return code from the service provider indicating that the network slice instance or the network slice subnet instance has been allocated; or When the network slice instance or the network slice subnet instance already exists, a second return code is received from the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated.

15. The device of claim 14, wherein: The first return code and the second return code are different.

16. The device of claim 15, wherein: The first bit of the first return code and the first bit of the second return code are the same as or different from each other.

17. A method comprising: receiving a request from a service consumer to allocate a network slice instance or a network slice subnet instance to the service consumer; Allocating a network slice instance or a network slice subnet instance to the service consumer, wherein the network slice instance or the network slice subnet instance is newly created or already exists; and A return code is sent to the service consumer indicating that the network slice instance or the network slice subnet instance has been allocated, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

18. A method comprising: Sending a request to the service provider to allocate a network slice instance or a network slice subnet instance to the service consumer; Receiving a return code from the service provider indicating that the network slice instance or the network slice subnet instance has been assigned to the service consumer, wherein the return code depends on whether the network slice instance or the network slice subnet instance is newly created or already exists.

19. A computer program comprising computer executable instructions which, when executed on one or more processors, perform the steps of the method of claim 17 or claim 18.

Images