Enhancements to slice requirement verification and alignment capability

Abstract

A method and network nodes for enhancements to slice requirement verification and alignment capability are disclosed. According to one aspect, a method in a network node operating as a network slice capability enablement, NSCE, server configured to communicate with a vertical application layer, VAL, server includes receiving from the VAL server a request message to request slice requirements verification and alignment subscription, the request message comprising a slice identifier identifying a network slice, slice requirements for the network slice and a mode for automatic alignment to instruct the NSCE server whether to automatically enforce generated optimal slice requirements for the network slice to align with the slice requirements included in the request message; and generate by the NSCE server optimal slice requirements for the network slice and determine whether to enforce them in accordance with the mode for automatic alignment.

Description

[0001] ENHANCEMENTS TO SLICE REQUIREMENT VERIFICATION AND ALIGNMENT

[0002] CAPABILITY

[0003] RELATED APPLICATIONS

[0004] This application claims the benefit of provisional patent application serial number PCT / CN2023 / 123075, filed on 2023-10-03, the disclosure of which is hereby incorporated herein by reference in its entirety.

[0005] TECHNICAL FIELD

[0006] The present disclosure relates to wireless communications, and in particular, to enhancements to slice requirement verification and alignment capability.

[0007] BACKGROUND

[0008] The Third Generation Partnership Project (3GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile wireless devices (WD), as well as communication between network nodes and between WDs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0009] 3GPP Technical Standard (TS) 23.435 is a service enabler layer to expose network slice capabilities for 3rdparty or verticals. 3GPP TS 23.435 clause 9.16 - Slice requirements verification and alignment capability exposure is discussed herein. The Verticals like vehicle-to-anything (V2X), may compare the quality of service (QoS) achieved by the provider with the QoS / slice requirements and its own experience of the QoS to verify if the QoS / Slice requirements are reasonably configured. To order a slice with certain slice requirements parameters and their values, the verticals will put their best effort into slice requirements translation. However, they are not able to guarantee that all the potential factors will be considered to generate the optimal slice requirements parameters on the first try.

[0010] In some cases, there may be some unforeseen exceptions (e.g., unexpected traffic changes) and the current configured slice requirements parameters are not able to fulfil the verticals requirements (e.g., more resources are required to address the exceptions), the vertical application layer (VAL) client may also suffer unsatisfied experience. Or in some other cases, when the service is executed on the required slice, the slice may not fully match the service real-time running conditions. For example, may be only 60% of the slice resource is used to support the service, and rest of the slice resource is always idle, or the slice resource is insufficient due to under-provisioning.

[0011] Hence, network slice capability enablement (NSCE) is able to provide the capability of comparing the QoS achievement status together with the operation, administration and management (0AM) QoS data versus real customer QoS data (e.g., Mean Opinion Score) collected from the VAL client to check whether the existing QoS / Slice related data is able to satisfy the VAL clients. Alignment notifications to VAL server for the slice requirements are periodically sent.

[0012] The current procedure defined in 3GPP TS 23.435 clause 9.16.2.1 may provide exposure to the VAL server for slice requirements verification and alignment capability. It verifies the slice requirements based on configured requirements and network slice performance statistics in order to generate the optimal slice requirements. The optimal slice requirement is notified to the VAL server. This leads to the following issues:

[0013] The WD - network condition is dynamic, and this may result in temporary misalignment in slice requirements leading to an unnecessarily large number of notifications to the VAL server. The large number of notifications will lead to wastage of network resources.

[0014] The slice alignment notification is sent to the VAL server which contains the updated slice requirement, but the updated slice requirement is not enforced into the system. This impacts the QoS of the VAL clients because the slice requirements are misaligned.

[0015] The use cases like ultra reliable and low latency communications (URLLC), which are subject to latency, the misalignment notification without any alignment enforcement action leads to an increase in latency and degrades the QoS of users. It also increases round-trip latency to provision the correct slice requirements in the 5G system.

[0016] SUMMARY

[0017] Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. Some embodiments advantageously provide methods and network nodes for enhancements to slice requirement verification and alignment capability.

[0018] Some embodiments add enhancements to the existing solution described in 3GPP TS 23.435 clause 9.16.2.1 slice requirements verification and alignment capability. The solution allows the VAL server to restrict the sending of slice alignment notifications from NSCE server based on QoS margin and alignment notification information. The solution enables the VAL server to indicate the automatic alignment mode to enforce the updated or optimal slice requirements reducing latency and maintaining the desired QoS.

[0019] More specifically, according to some embodiments the method performed by an NSCE server is provided and comprises the step of receiving from the VAL server a request message to request slice requirements verification and alignment subscription, the request message comprises a slice identifier identifying a network slice, the slice requirements for the network slice as determined by the VAL server. The request message also includes a mode for automatic alignment to instruct the NSCE server whether to automatically enforce generated optimal slice requirements for the network slice to align with the slice requirements included in the request message. The method further include the step of generating optimal slice requirements for the network slice and determining whether to enforce them in accordance with the mode for automatic alignment. The generation of the optimal slice requirements by the NSCE server is based on received subscription data and statistics from the network or NSCE clients. The NSCE server may then send to the VAL server a notification to indicate the updated slice requirements information and an indication whether the updated slice requirements has been enforced or not by the NSCE server.

[0020] For example, the request message comprises reporting information to indicate reporting conditions of the alignment between the generated optimal slice requirements and the slice requirements included in the request message and sending an alignment notification to the VAL server based on the reporting information.

[0021] In one example, the reporting information comprises time information for reporting the alignment notification, or spatial information such as location information or presence of minimum number of UEs in the network slice. Based on the reporting information, the NSCE server sends an alignment notification to the VAL server.

[0022] According to another example, the request message comprises reporting margins to request notification when the generated optimal slice requirements fall below the margins. For example the reporting margins are QoS margins for the network slice.

[0023] In one example, when the mode for automatic alignment indicates OFF, the request message is also used to instruct the NSCE server to not automatically enforce the generated optimal slice requirements for the network slice to align with the slice requirements included in the request message, and when the mode for automatic alignment indicates ON, the request message instructs the NSCE server to automatically enforce the generated optimal slice requirements for the network slice to align with the slice requirements included in the request message.

[0024] According to an embodiment, a network comprising one or more processors and memory comprising instructions which when executed by the one or more processors, the network node is configured to perform any of the embodiments described herein.

[0025] According to an embodiment, a second network node operating as a vertical application layer, VAL, server configured to communicate with a network slice capability enablement, NSCE, server, is provided and configured to configure slice requirements for a network slice and transmit to the NSCE server, a request message to request slice requirements verification and alignment subscription, where the request message comprises a slice identifier identifying a network slice, the slice requirements for the network slice and a mode for automatic alignment parameter to instruct the NSCE server whether to automatically enforce generated optimal slice requirements for the network slice to align with the slice requirements included in the request message. The VAL server may further receive a notification from the NSCE server to indicate the updated slice requirements information and an indication whether the updated slice requirements has been enforced or not by the MSCE server.

[0026] For example, when the mode for automatic alignment indicates OFF, the request message instructs the NSCE server to not automatically enforce the NSCE server generated optimal slice requirements for the network slice to align with the slice requirements included in the request message, and when the mode for automatic alignment indicates ON, the request message instructs the NSCE server to automatically enforce the NSCE server generated optimal slice requirements for the network slice to align with the slice requirements included in the request message.

[0027] In one example, the request message comprises reporting information to indicate reporting conditions of the alignment between the generated optimal slice requirements by the NSCE server and the slice requirements included in the request message and to receive an alignment notification based on the reporting information included in the request message.

[0028] In one example, the reporting information comprises time information for reporting the alignment notification or spatial information such as location information or presence of minimum number of UEs in the network slice.

[0029] In one example, the request message transmitted by the VAL server comprises reporting margins to request notification when the generated optimal slice requirements by the NSCE server fall below the margins. The reporting margin may be QoS margin for the network slice.

[0030] BRIEF DESCRIPTION OF THE DRAWINGS

[0031] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0032] FIG. 1 is a schematic diagram of an example network architecture illustrating a communication system connected via an intermediate network to a host computer according to the principles in the present disclosure;

[0033] FIG. 2 is a block diagram of a host computer communicating via a network node with a wireless device over an at least partially wireless connection according to some embodiments of the present disclosure;

[0034] FIG. 3 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for executing a client application at a wireless device according to some embodiments of the present disclosure;

[0035] FIG. 4 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a wireless device according to some embodiments of the present disclosure;

[0036] FIG. 5 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data from the wireless device at a host computer according to some embodiments of the present disclosure;

[0037] FIG. 6 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure;

[0038] FIG. 7 is a sequence diagram of slice requirements verification and alignment capability exposure in accordance with some embodiments;

[0039] FIG. 8 is a flowchart of a method performed in a Network Slice Capability Enablement function for enhancements to slice requirement verification and alignment capability;

[0040] FIG. 9 is a flowchart of a method performed in a Vertical Application Layer (VAL) server for enhancements to slice requirement verification and alignment capability; and

[0041] FIG. 10, 11 and 12 are schematic block diagrams of example embodiments of a network node.

[0042] DETAILED DESCRIPTION

[0043] Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to enhancements to slice requirement verification and alignment capability. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

[0044] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0045] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.

[0046] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0047] The term “network node” used herein may be any kind of network node comprised in a Core network, service network or radio network. The latter may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

[0048] In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein may be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low -cost and / or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device, etc.

[0049] Also, in some embodiments the generic term “radio network node” is used. It may be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH). Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0050] Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, may be distributed among several physical devices.

[0051] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0052] Some embodiments provide to enhancements to slice requirement verification and alignment capability.

[0053] Referring now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG. 1 a schematic diagram of a communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as UTE and / or NR (5G), which comprises an access network 12, such as a radio access network, and a core network 14. The access network 12 comprises a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include many more WDs 22 and network nodes 16.

[0054] Also, it is contemplated that a WD 22 may be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 may have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 may be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN and to 6G access network.

[0055] The communication system 10 may itself be connected to a host computer 24, which may be embodied in the hardware and / or software of a standalone server, a cloud- implemented server, a distributed server or as processing resources in a server farm. The host computer 24 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. The connections 26, 28 between the communication system 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24 or may extend via an optional intermediate network 30. The intermediate network 30 may be one of, or a combination of more than one of, a public, private or hosted network. The intermediate network 30, if any, may be a backbone network or the Internet. In some embodiments, the intermediate network 30 may comprise two or more sub-networks (not shown).

[0056] The communication system of FIG. 1 as a whole enables connectivity between one of the connected WDs 22a, 22b and the host computer 24. The connectivity may be described as an over-the-top (OTT) connection. The host computer 24 and the connected WDs 22a, 22b are configured to communicate data and / or signaling via the OTT connection, using the access network 12, the core network 14, any intermediate network 30 and possible further infrastructure (not shown) as intermediaries. The OTT connection may be transparent in the sense that at least some of the participating communication devices through which the OTT connection passes are unaware of routing of uplink and downlink communications. For example, a network node 16 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 24 to be forwarded (e.g., handed over) to a connected WD 22a. Similarly, the network node 16 need not be aware of the future routing of an outgoing uplink communication originating from the WD 22a towards the host computer 24.

[0057] In some embodiments, one network node 16a may be configured as an NSCE server and another network node 16b may be configured as a VAL server in a vertical application layer. The NSCE server may be part of an intermediary service platform accessible to various Public Land Mobile networks deploying core networks or may be part of a PLMN network. The PLMN Core network may be 5G, 6G or any subsequent generation of core networks. The network node 16a may be configured with an alignment unit 32 which may be configured to enforce slice requirements based on the alignment notification. A network node 16b may be configured with a configuration unit 34 which may be configured to configure the slice alignment and enforcement configuration. Note that in some embodiments, the NSCE server and / or the VAL server may be located in the core network 14 and / or the host computer 24.

[0058] Example implementations, in accordance with an embodiment, of the WD 22, network node 16 and host computer 24 discussed in the preceding paragraphs will now be described with reference to FIG. 2. In a communication system 10, a host computer 24 comprises hardware (HW) 38 including a communication interface 40 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 10. The host computer 24 further comprises processing circuitry 42, which may have storage and / or processing capabilities. The processing circuitry 42 may include a processor 44 and memory 46. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 42 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 44 may be configured to access (e.g., write to and / or read from) memory 46, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0059] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by host computer 24. Processor 44 corresponds to one or more processors 44 for performing host computer 24 functions described herein. The host computer 24 includes memory 46 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 48 and / or the host application 50 may include instructions that, when executed by the processor 44 and / or processing circuitry 42, causes the processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host computer 24. The instructions may be software associated with the host computer 24.

[0060] The software 48 may be executable by the processing circuitry 42. The software 48 includes a host application 50. The host application 50 may be operable to provide a service to a remote user, such as a WD 22 connecting via an OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the remote user, the host application 50 may provide user data which is transmitted using the OTT connection 52. The “user data” may be data and information described herein as implementing the described functionality. In one embodiment, the host computer 24 may be configured for providing control and functionality to a service provider and may be operated by the service provider or on behalf of the service provider. The processing circuitry 42 of the host computer 24 may enable the host computer 24 to observe, monitor, control, transmit to and / or receive from the network node 16 and or the wireless device 22.

[0061] The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 58 enabling it to communicate with the host computer 24 and with the WD 22. The hardware 58 may include a communication interface 60 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 62 for setting up and maintaining at least a wireless connection 64 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 to the host computer 24. The connection 66 may be direct or it may pass through a core network 14 of the communication system 10 and / or through one or more intermediate networks 30 outside the communication system 10.

[0062] In the embodiment shown, the hardware 58 of the network node 16 further includes processing circuitry 68. The processing circuitry 68 may include a processor 70 and a memory 72. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 68 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to and / or read from) the memory 72, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0063] Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or processing circuitry 68, causes the processor 70 and / or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of network node 16a may be configured with an alignment unit 32 which may be configured to enforce slice requirements based on the alignment notification. Processing circuitry 68 of network node 16b may be configured with a configuration unit 34 which may be configured to configure the slice alignment and enforcement configuration.

[0064] The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 80 that may include a radio interface 82 configured to set up and maintain a wireless connection 64 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0065] The hardware 80 of the WD 22 further includes processing circuitry 84. The processing circuitry 84 may include a processor 86 and memory 88. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 84 may comprise integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 86 may be configured to access (e.g., write to and / or read from) memory 88, which may comprise any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0066] Thus, the WD 22 may further comprise software 90, which is stored in, for example, memory 88 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the WD 22, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the WD 22 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides.

[0067] The processing circuitry 84 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by WD 22. The processor 86 corresponds to one or more processors 86 for performing WD 22 functions described herein. The WD 22 includes memory 88 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or processing circuitry 84, causes the processor 86 and / or processing circuitry 84 to perform the processes described herein with respect to WD 22.

[0068] In some embodiments, the inner workings of the network node 16, WD 22, and host computer 24 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 1.

[0069] In FIG. 2, the OTT connection 52 has been drawn abstractly to illustrate the communication between the host computer 24 and the wireless device 22 via the network node 16, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from the WD 22 or from the service provider operating the host computer 24, or both. While the OTT connection 52 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

[0070] The wireless connection 64 between the WD 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the last segment. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc.

[0071] In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 52 between the host computer 24 and WD 22, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 52 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or supplying values of other physical quantities from which software 48, 90 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 52 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the network node 16, and it may be unknown or imperceptible to the network node 16. Some such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary WD signaling facilitating the host computer’s 24 measurements of throughput, propagation times, latency and the like. In some embodiments, the measurements may be implemented in that the software 48, 90 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 52 while it monitors propagation times, errors, etc.

[0072] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data and a communication interface 40 that is configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes the network node 16 with a radio interface 62. In some embodiments, the network node 16 is configured to, and / or the network node’s 16 processing circuitry 68 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the WD 22, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the WD 22.

[0073] In some embodiments, the host computer 24 includes processing circuitry 42 and a communication interface 40 that is configured to a communication interface 40 configured to receive user data originating from a transmission from a WD 22 to a network node 16. In some embodiments, the WD 22 is configured to, and / or comprises a radio interface 82 and / or processing circuitry 84 configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending a transmission to the network node 16, and / or preparing / terminating / maintaining / supporting / ending in receipt of a transmission from the network node 16.

[0074] Although FIGS. 1 and 2 show various “units” such as alignment unit 32, and configuration unit 34 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0075] FIG. 3 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIGS. 1 and 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIG. 2. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block S 102). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block S106). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block S108). FIG. 4 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 1 and 2. In a first step of the method, the host computer 24 provides user data (Block SI 10). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block S 114).

[0076] FIG. 5 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 1 and 2. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block S 116). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block SI 18). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block S 120). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block S122). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block SI 24). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block S126).

[0077] FIG. 6 is a flowchart illustrating an example method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16 and a WD 22, which may be those described with reference to FIGS. 1 and 2. In an optional first step of the method, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 16 receives user data from the WD 22 (Block S128). In an optional second step, the network node 16 initiates transmission of the received user data to the host computer 24 (Block S 130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (Block S132).

[0078] FIG. 7 illustrates a flow diagram in accordance with embodiments herein. The flow diagram is illustrated as an enhancement to the slice requirement verification and alignment capability specified in 3GPP TS 23.435 of the 3GPP.

[0079] The reason for enhancing the standard procedure as proposed herein is due to that the procedure in the standard as specified in clause 9.16 of TS 23.435 mentions periodic alignment but there is no periodicity information present in the IE table. Moreover, the current procedure only verifies and sends notifications for alignment to the VAL server. This increases the latency in the system in for example time-critical use cases, URLLC, autonomous vehicles, UAVs, etc. because the slice alignment notification is sent to the VAL server and then the VAL server has to interact with the NSCE server to optimize the slice as per the requirement notification. This also impacts the QoS of the VAL clients because the slice requirements are misaligned. Hence the enhancements presented herein introduce three aspects: 1. Margin (e.g., QoS margin) - if the generated requirements such as QoS of the slice is within the margin then no need to send notification and alignment. Because the UE conditions are dynamic and this may lead to unnecessary notifications. Therefore, it is necessary to save resources and report notification only when required. 2. Automatic align mode - If the Automatic align mode is ON then the NSCE server will align the slice to meet the requirements on behalf of the VAL server, saving the round trip time and thereby reducing latency. 3. alignment reporting conditions - based on location, time and number of UEs, alignment reporting can be allowed.

[0080] The proposed enhancements to the procedure are suitable for URLLC, and time- critical use cases because the existing procedure increases latency in end-to-end system to maintain the QoS or slice requirements and could lead to a wastage of resources in reporting unnecessary alignment notifications. Slice requirements verification and alignment capability exposure

[0081] Verticals can compare the QoS achieved by the provider with the QoS / slice requirements and its own experience of the QoS to verify if the QoS / Slice requirements are reasonably configured. To order a slice with certain slice requirements parameters and their values, the verticals will put their best effort into slice requirements translation. However, they are not able to guarantee that all the potential factors will be considered to generate the optimal slice requirements parameters on the first try.

[0082] In some cases, there may be some unforeseen exceptions (e.g., unexpected traffic changes) and the current configured slice requirements parameters are not able to fulfil the verticals requirements (e.g., more resources are required to address the exceptions), the VAL client may also suffer unsatisfied experience. Or in some other cases, when the service is executed on the required slice, the slice may not fully match the service real-time running conditions, for example, maybe only 60% of the slice resource is used to support the service, and rest of the slice resource is always idle, or the slice resource is insufficient due to under-provisioning.

[0083] Hence, NSCE is able to provide the capability of comparing the QoS achievement status together with the 0AM QoS data versus real customer QoS data (e.g., Mean Opinion Score) collected from VAL client to check whether the existing QoS / Slice related data is able to satisfy the VAL clients and send periodically alignment notifications to VAL server for the slice requirements. The VAL server can indicate the preference for enforcement of slice requirements alignment to meet the slice requirements for time- critical use cases like URLLC. The time-critical use case is subject to latency and without the automatic alignment, it will lead to an increase in delay for slice requirement alignment which impacts the QoS of the VAL clients.

[0084] F IG. 9 provides a possible procedure of slice requirements verification and alignment capability exposure illustrating the enhancements.

[0085] Pre-conditions:

[0086] 1. The NSCE Server has subscribed to the service of network slice performance management provided by the Exposure Governance Management FunctionEGMF. Referring again to the steps in FIG. 9:

[0087] 1. The VAL server sends slice requirements verification and alignment subscription NSCE server to require the NSCE server to check whether the slice requirements (by configuring the attributes of serviceProfile) matches the real network slice usage status, the request may include the network slice (S-NSSAI), the ID of the VAL server, the slice requirements parameters (attributes of serviceProfile) which is requested to be aligned. The subscription may include Automatic alignment mode indicates the NSCE server should automatically align the slice requirements in order to meet the requested slice requirements on behalf of the VAL server. Optionally, the request may include the slice margin (e.g„ QoS margin) in terms of for example percentage to indicate the threshold-based reporting of alignment notification shall be done only when QoS or slice requirements are below the QoS margin or any provided slice margin. The alignment notification reporting allows the VAL server to optionally configure alignment reporting information so that the reporting (or notification) can be based on location, number of UEs, and time. The NSCE server monitors the UE location using SEAL LM services in order to send / block the reporting of alignment notification. See Table 1 for details of the subscription request.

[0088] 2. The NSCE server checks if the VAL server is authorized to trigger the service of slice requirements alignment.

[0089] 3. The NSCE server response to VAL server with the result of slice requirements verification and alignment request, e.g., the slice requirements alignment request is accepted.

[0090] 4. The NSCE server may optionally subscribe the QoE data from the NSCE client. The QoE data can refer to the data defined in clause 16 of TS 26.114. Note: The QoE data collection from NSCE client follows the mechanism defined in EVEX work in 3GPP SA4.

[0091] 5. The NSCE server subscribes the network slice related performance data and KPIs (e.g., the average PRB usage, the distribution of the PRB usage) defined in 3GPP TS 28.552. The NSCE server can also subscribe the analytics data (both statistics and predictions) from MDAS and ADAEs. 6. The NSCE server periodically receives the subscribed data (from steps 4 and 5) and compares the slice requirement parameters of network slice (the values of attributes of serviceProfile, e.g., radioSpectrum, the maxNumberofUEs) with network slice performance statistics (e.g., active number of users, the average PRB usage, the distribution of the PRB usage of the S-NSSAI) to generate the optimal slice requirements for the required service (represented by S-NSSAI) of the vertical. This step depends on implementation (e.g., if in implementation specific time window the VAL client experience is satisfied while the network slice resources are with low utilization, the resources required in the slice requirements could be reduced based on predictions and statistics). The NSCE server uses the Automatic alignment mode to perform the slice alignment with the generated optimal slice requirement using the procedure defined in clause 4, 10 of TS 23,435 if the mode is set to ON. If mode is set to OFF, then the NSCE will not attempt to align the slice requirements with the generated slice requirements. Based on the response received from procedure in clause 4,10, the NSCE server may send the notification to the VAL server if alignment reporting information is received at step 1. If slice margin such as QoS margin are received at step 1, the NSCE server uses the QoS margin to verify whether the slice requirements are within the margin or not. If the slice requirements are within the margin, then the NSCE server does not send the notification, otherwise it notifies the VAL server.

[0092] 7. Based on the analysis in step 6, the NSCE server periodically sends notifications to VAL server to inform the recommended changes of the slice requirements parameters. The notification may include a slice enforcement indication to indicate whether the updated slice requirements has been enforced by the NSCEE server or not as illustrated in Table 2.

[0093] Information flows for Slice verification and

[0094] The following information flows are specified for slice requirements verification and alignment capability exposure.

[0095] The Table below describes information elements for slice requirements verification and alignment subscription. Table 1 Slice requirements verification and alignment subscription Slice requirements verification and alignment notification

[0096] Table 2 describes information elements for slice requirements verification and alignment notification.

[0097] Table 2 Slice requirements verification and alignment notification

[0098] FIG. 8 is a flowchart of an example process or method in a network node 16a operating and / or containing functionality to operate as a network slice capability enablement, NSCE, server (also referred to herein as NSCE server 16a) configured to communicate with a network node 16b operating and / or containing functionality to operate as a vertical application layer, VAL, server (also referred to herein as VAL server 16b) based on embodiments herein and Figure 7. One or more blocks described herein may be performed by one or more elements of network node 16a such as by one or more of processing circuitry 68 (including the alignment unit 32), processor 70, radio interface 62 and / or communication interface 60. Network node 16a such as via processing circuitry 68 and / or processor 70 and / or radio interface 62 and / or communication interface 60.

[0099] The method comprises the step of performing the step S134a of receiving from the VAL server a request message to request slice requirements verification and alignment subscription, the message would comprise a slice identifier identifying a network slice, the slice requirements for the network slice as requested by the VAL server and a mode for automatic alignment parameter that is used to instruct the NSCE server whether to automatically enforce generated optimal slice requirements for the network slice to align with the slice requirements included in the request message. The method comprises the step S 134b of generating by the NSCE server the optimal slice requirements based on for example obtained statistic data and subscription data related to the network slice from the network or more specifically from an analytics function as described in Figure 7 steps 4 and 5 and determining whether to enforce them in accordance with the mode for automatic alignment. If the mode for automatic alignment indicates OFF, it is an instruction to the NSCE server to not automatically enforce the generated optimal slice requirements for the network slice to align with the slice requirements that were included in the request message. If the mode for automatic alignment indicates ON, it is an instruction to the NSCE server to automatically enforce the generated optimal slice requirements for the network slice to align with the slice requirements included in the request message. The NSCE server may send notifications to VAL server to inform the updated / recommended changes of the slice requirements parameters which are generated by the NSCE server. The notification may include a slice enforcement indication to indicate whether the updated slice requirements has been enforced by the NSCEE server or not as illustrated in Table 2 (above).

[0100] In one example, the request message comprises reporting information to indicate to the NSCE server the reporting conditions regarding the alignment between the generated optimal slice requirements and the slice requirements included in the request message. If the reporting conditions are met, the NSCE server performs the step of sending an alignment notification based on the reporting information.

[0101] In one example, the reporting information comprises time information for reporting the alignment notification. In another example, the reporting information comprises location information for reporting the alignment notification. In yet another example the reporting information indicates reporting of the alignment notification based on presence of minimum number of UEs in the network slice.

[0102] In another example, the message comprises reporting margins to request that the NSCE server sends notification to the VAL server when the generated optimal slice requirements fall below the margins where for example the reporting margins correspond to Quality of Service (QoS) margins.

[0103] In one example, the method further comprises the step at the NSCE server of sending an alignment notification based on (temporal information (Block S134) and enforce slice requirements based on the alignment notification (Block SI 36). More specifically, the alignment notification may be sent from the NSCE server to the VAL server if the generated slice requirements by the NSCE server fall below the provided margins or the alignment notification is sent based on the reporting information (e.g., location, time. Number of UEs in the network slice).

[0104] FIG. 9 is a flowchart of an example process or method performed by a network node 16b operating as a vertical application layer, VAL, server configured to communicate with a network slice capability enablement, NSCE, server 16a. One or more blocks described herein may be performed by one or more elements of network node 16b such as by one or more of processing circuitry 68 (including the configuration unit 34), processor 70, and communication interface 60. The method comprises the step s 138 of configuring slice requirements for a network slice and the step si 40 of transmitting to the NSCE server 16a, a request message comprising an identity of the network slice, the slice requirements configured by the VAL server and an automatic alignment mode parameter that can be set to ON or OFF. If the VAL server provides Automatic alignment mode as ON, then the NSCE server 16a may apply or enforce the generated slice requirements in the 5G system using procedure defined in clause 4.10 of 3GPP TS 23.435. If the VAL server provides Automatic alignment mode as OFF, then the NSCE server 16a is not required to align and enforce the generated optimal slice requirement based on the requested slice requirements. The automatic alignment mode reduces the latency in enforcing the slice requirements and maintains the QoS for the VAL users using the network slice. The VAL server may receive notifications from the NSCE server so the VAL server is informed about the updated / recommended changes of the slice requirements parameters which are generated by the NSCE server. The notification may include a slice enforcement indication to indicate whether the updated slice requirements has been enforced by the NSCEE server or not as illustrated in Table 2.

[0105] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for enhancements to slice requirement verification and alignment capability.

[0106] Some embodiments are configured to allow the VAL server 16b to provide the slice margin (e.g., QoS margin). The QoS margin enables the NSCE server 16a to monitor whether the generated slice requirements are in the requested margin or not. If the slice requirements are within the margin then the NSCE server 16a may not send the alignment notifications to the VAL server 16b.

[0107] Some embodiments are configured to allow the VAL server 16b to provide the alignment reporting information. This enables the NSCE server 16a to send or block the alignment notification based on the temporal information, spatial information and number of WDs 22. The temporal information may define the time, spatial information provides the location information, and the number of WDs 22 may define the presence of a minimum number of WDs 22 in the slice.

[0108] The QoS margin and alignment reporting information based on spatial, temporal and count of WDs 22 allows the NSCE server to save resources by sending alignment notifications as per the configuration.

[0109] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that may be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0110] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the fimctions / acts specified in the flowchart and / or block diagram block or blocks.

[0111] These computer program instructions may also be stored in a computer readable memory or storage medium that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0112] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0113] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0114] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0115] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments may be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and sub combinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or sub combination.

[0116] FURTHER DESCRIPTION

[0117] Figure 10 is a schematic block diagram of a network node 1100 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 1100 may be, for example, a core network node that implements a NF (e.g., NSCE, VAL server, or the like). As illustrated, the network node 1100 includes a one or more processors 1104 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and / or the like), memory 1106, and a network interface 1108. The one or more processors 1104 are also referred to herein as processing circuitry. The one or more processors 1104 operate to provide one or more functions of the network node 1100 as described herein (e.g., one or more functions of the NSCE, VAL server, or the like, as described herein. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 1106 and executed by the one or more processors 1104.

[0118] Figure 11 is a schematic block diagram that illustrates a virtualized embodiment of the network node 1100 according to some embodiments of the present disclosure. Again, optional features are represented by dashed boxes. As used herein, a “virtualized” network node is an implementation of the network node 1100 in which at least a portion of the functionality of the network node 1100 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the network node 1100 includes one or more processing nodes 1200 coupled to or included as part of a network(s) 1202. Each processing node 1200 includes one or more processors 1204 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory 1206, and a network interface 1208. In this example, functions 1210 of the network node 1100 described herein (e.g., one or more functions of the NSCE, VAL server, or the like, as described herein) are implemented at the one or more processing nodes 1200 or distributed across the two or more processing nodes 1200 in any desired manner. In some particular embodiments, some or all of the functions 1210 of the network node 1100 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 1200.

[0119] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the network node 1100 or a node (e.g., a processing node 1200) implementing one or more of the functions 1210 of the network node 1100 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0120] Figure 12 is a schematic block diagram of the network node 1100 according to some other embodiments of the present disclosure. The network node 1100 includes one or more modules 1300, each of which is implemented in software. The module(s) 1300 provide the functionality of the network node 1100 described herein. This discussion is equally applicable to the processing node 1200 of Figure 11 where the modules 1300 may be implemented at one of the processing nodes 1200 or distributed across multiple processing nodes 1200.

[0121] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0122] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0123] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

[0124] Abbreviations that may be used in the preceding description include:

[0125] EGMF Exposure Governance Management Function

[0126] NSCE Network Slice Capability Enablement

[0127] VAL Vertical Application Layer

Claims

CLAIMS:

1. A network node operating as a network slice capability enablement, NSCE, server configured to communicate with a vertical application layer, VAL, server, the network node configured to: receive from the VAL server a request message to request slice requirements verification and alignment subscription, the request message comprising a slice identifier identifying a network slice, slice requirements for the network slice and a mode for automatic alignment to instruct the NSCE server whether to automatically enforce generated optimal slice requirements for the network slice to align with the slice requirements included in the request message; and- generate optimal slice requirements for the network slice and determine whether to enforce them in accordance with the mode for automatic alignment.

2. The network node of claim 1 wherein the request message comprises reporting information to indicate reporting conditions of the alignment between the generated optimal slice requirements and the slice requirements included in the request message.

3. The network node of claim 2 wherein the network node is further configured to send an alignment notification based on the reporting information.

4. The network node of Claim 1, wherein the reporting information comprises time information for reporting the alignment notification.

5. The network node of claim 1, wherein the reporting information comprises location information for reporting the alignment notification.

6. The network node of claim 1, wherein the reporting information indicates reporting of the alignment notification based on presence of minimum number of UEs in the network slice.

7. The network node of claim 1 wherein the request message comprises reporting margins to request notification when the generated optimal slice requirements fall below the margins.

8. The network node of claim 7 wherein the reporting margins correspond to Quality of Service (QoS) margins.

9. The network node of claim 1 wherein when the mode for automatic alignment indicates OFF, the request message instructs the NSCE server to not automatically enforce the generated optimal slice requirements for the network slice to align with the slice requirements included in the request message.

10. The network node of claim 1 wherein when the mode for automatic alignment indicates ON, the request message instructs the NSCE server to automatically enforce the generated optimal slice requirements for the network slice to align with the slice requirements included in the request message.

11. The network node of claim 1 further configured to send to the VAL server a notification to indicate updated slice requirements information and an indication whether the updated slice requirements has been enforced or not.

12. A method performed by a network slice capability enablement, NSCE, server configured to communicate with a vertical application layer, VAL, server, the method comprising:- receiving from the VAL server a request message to request slice requirements verification and alignment subscription, the request message comprising a slice identifier identifying a network slice, slice requirements for the network slice and a mode for automatic alignment to instruct the NSCE server whether to automatically enforce generated optimal slice requirements for the network slice to align with the slice requirements included in the request message;- generating optimal slice requirements for the network slice and determining whether to enforce them in accordance with the mode for automatic alignment.

13. The method of claim 12 wherein the request message comprises reporting information to indicate reporting conditions of the alignment between the generated optimal slice requirements and the slice requirements included in the request message.

14. The method of claim 13 wherein the method further comprises sending an alignment notification based on the reporting information.

15. The method of claim 13, wherein the reporting information comprises time information for reporting the alignment notification.

16. The method of claim 13, wherein the reporting information comprises location information for reporting the alignment notification.

17. The method of claim 13, wherein the reporting information indicates reporting of the alignment notification based on presence of minimum number of UEs in the network slice.

18. The method of claim 12 wherein the request message comprises reporting margins to request notification when the generated optimal slice requirements fall below the margins.

19. The method of claim 12 wherein the reporting margins correspond to Quality of Service (QoS) margins.

20. The method of claim 12 wherein when the mode for automatic alignment indicates OFF, the request message instructs the NSCE server to not automatically enforce the generated optimal slice requirements for the network slice to align with the slice requirements included in the request message.

21. The method of claim 12 wherein when the mode for automatic alignment indicates ON, the request message instructs the NSCE server to automatically enforce the generated optimal slice requirements for the network slice to align with the slice requirements included in the request message.

22. The method of claim 12 further comprising sending to the VAL server a notification to indicate updated slice requirements information and an indication whether the updated slice requirements has been enforced or not.

23. A network node comprising one or more processors and memory comprising instructions which when executed by the one or more processors, the network node is configured to perform any of the method steps 12 to 22.

24. A second network node operating as a vertical application layer, VAL, server configured to communicate with a network slice capability enablement, NSCE, server, the network node configured to: configure slice requirements for a network slice and;- transmit to the NSCE server, a request message to request slice requirements verification and alignment subscription, the request message comprising a slice identifier identifying a network slice, slice requirements for the network slice and a mode for automatic alignment to instruct the NSCE server whether to automatically enforce generated optimal slice requirements for the network slice to align with the slice requirements included in the request message.

25. The second network node of claim 24 wherein the request message comprises reporting information to indicate reporting conditions of the alignment between the generated optimal slice requirements by the NSCE server and the slice requirements included in the request message.

26. The second network node of claim 25 wherein the second network node is further configured to receive an alignment notification based on the reporting information included in the request message.

27. The second network node of Claim 24, wherein the reporting information comprises time information for reporting the alignment notification.

28. The second network node of claim 24, wherein the reporting information comprises location information for reporting the alignment notification.

29. The second network node of claim 24, wherein the reporting information indicates a request for reporting of the alignment notification based on presence of minimum number of UEs in the network slice.

30. The second network node of claim 24 wherein the request message comprises reporting margins to request notification when the generated optimal slice requirements by the NSCE server fall below the margins.

31. The second network node of claim 30 wherein the reporting margins correspond to Quality of Service (QoS) margins.

32. The second network node of claim 24 wherein when the mode for automatic alignment indicates OFF, the request message instructs the NSCE server to not automatically enforce the NSCE server generated optimal slice requirements for the network slice to align with the slice requirements included in the request message.

33. The second network node of claim 24 wherein when the mode for automatic alignment indicates ON, the request message instructs the NSCE server to automatically enforce the NSCE server generated optimal slicerequirements for the network slice to align with the slice requirements included in the request message.

34. The second network node of claim 24 wherein the second network node is further configured to receive from the NSCE server, a notification to indicate updated slice requirements information and an indication whether the updated slice requirements has been enforced or not.

Images