Control node, vertical application layer server and methods performed in a wireless communication network

Abstract

Embodiments herein relate to, for example, a method performed by a VAL server (14), or a control node (15) for handling services in a wireless communication network. The VAL server (14) transmits an indication to the control node (15), wherein the indication indicates one or more network slices to use, and / or an alternative slice requirement and / or a requirement adjustment related to a network slice. The VAL then receives a second indication from the control node (15), wherein the second indication indicates a decision related to a slice service provision at the control node (15).

Description

[0001] CONTROL NODE, VERTICAL APPLICATION LAYER SERVER AND METHODS PERFORMED IN A WIRELESS COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a control node, a vertical application layer (VAL) server, and methods performed therein regarding wireless communication. Furthermore, a computer program product and a computer-readable storage medium are also provided herein. Especially, embodiments herein relate to handling or enabling communication, such as managing slice services, in a communication network.

[0004] BACKGROUND

[0005] In a typical communication network, user equipments (UE), also known as wireless communication devices, mobile stations, stations (STA) and / or wireless devices, communicate via a Radio Access Network (RAN) to one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cell areas, with each service area or cell area being served by a network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some radio access technologies (RAT) may also be called, for example, a NodeB, an evolved NodeB (eNodeB) and a gNodeB (gNB). The service area or cell area is a geographical area where radio coverage is provided by a network node. The network node operates on radio frequencies to communicate over an air interface with the UEs within range of the access node. The network node communicates over a downlink (DL) to the UE, and the UE communicates over an uplink (UL) to the access node.

[0006] A Universal Mobile Telecommunications System (UMTS) is a third generation telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and / or High-Speed Packet Access (HSPA) for communication with user equipments. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and UTRAN specifically, and investigate enhanced data rate and radio capacity. In some RANs, e.g., as in UMTS, several network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural network nodes connected thereto. The RNCs are typically connected to one or more CNs.

[0007] Specifications for the Evolved Packet System (EPS) have been completed within the 3rdGeneration Partnership Project (3GPP) and this work continues in the coming 3GPP releases, such as fifth generation (5G) and sixth generation (6G) networks. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E- UTRAN / LTE is a 3GPP radio access technology wherein the network nodes are directly connected to the EPC core network. As such, the RAN of an EPS has an essentially non- hierarchical architecture comprising network nodes connected directly to one or more CNs.

[0008] With the emerging 5G technologies also known as new radio (NR) and / or upcoming 6G RAN the use of very many transmit- and receive-antenna elements may utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions. The benefit is to increase the cell capacity and coverage.

[0009] Furthermore, vehicle to everything (V2X) communication is also supported, which includes any combination of direct communication between vehicles, pedestrians, and infrastructure. V2X communication may take advantage of a network (NW) infrastructure, when available, but at least basic V2X connectivity should be possible even in case of lack of coverage. Providing an LTE-based V2X interface may be economically advantageous because of the LTE economies of scale, and it may enable tighter integration between communications with the NW infrastructure e.g. vehicle to infrastructure (V2I) and vehicle to pedestrians (V2P) and vehicle to vehicle (V2V) communications, as compared to using a dedicated V2X technology.

[0010] There are many research projects and field tests of connected vehicles in various countries or regions, including projects that are based on the use of existing cellular infrastructure.

[0011] V2X communications may carry both non-safety information and safety information, where each of the applications and services may be associated with specific requirements, in terms of, e.g., latency, reliability, capacity, and / or the like. From an application point of view, V2X includes the following types of communication / services shown with reference to Fig. 1.

[0012] Vehicle to vehicle (V2V): This covers communication between vehicles using V2V applications and is predominantly broadcast-based. V2V may be realized by either direct communication between the devices in the respective vehicles, or via infrastructure such as a cellular network. An example of V2V is the transmission of a cooperative awareness message (CAM) with vehicle status information, such as position, direction, and speed, transmitted to other vehicles in the proximity repeatedly e.g. every 100ms-1s. Another example is the transmission of a decentralized environmental notification message (DENM), which is an event-triggered message to alert vehicles. These two examples are taken from the ETSI intelligent transport systems (ITS) specification of V2X applications, which also specifies the conditions under which the messages are generated. Main characteristic of V2V applications is the tight requirements on latency that can vary from 20ms, for pre-crash warning messages, to 100ms for other road safety services.

[0013] Vehicle to infrastructure (V2I): This comprises communication between vehicles and a roadside unit (RSU). The RSU may be a stationary transportation infrastructure entity which communicates with vehicles in its proximity. An example of V2I is transmission of speed notifications from the RSU to vehicles, as well as queue information, collision risk alerts, and / or curve speed warnings. Due to the safety related nature of V2I, delay requirements are similar to V2V requirements.

[0014] Vehicle to pedestrian (V2P): This covers communication between vehicles and vulnerable road users, such as pedestrians, using V2P applications. V2P typically takes place between distinct vehicles and pedestrians either directly or via infrastructure such as a cellular network.

[0015] Vehicle to network (V2N): This covers communication between a vehicle and a centralized application server, or an ITS Traffic Management Center, both using V2N applications, via infrastructure, such as a cellular network. One example is a bad road condition warning sent to all vehicles in a wide area, or traffic flow optimization in which V2N application suggests speeds to vehicles and coordinates traffic lights. Therefore, V2N messages are supposed to be controlled by a centralized entity, such as a Traffic Management Center, and may be provisioned to vehicles in a large geographical area, rather than in a small area. Additionally, unlike V2V / V2I, latency requirements are more relaxed in V2N because it is not meant to be used for safety purposes, e.g. a latency requirement of 1s is typically considered. Since 3GPP Release 16, Service Enablement Architecture Layer for Verticals (SEAL) has been introduced to support vertical applications such as V2X applications. 3GPP TS 23.434 v.18.5.0 specifies application plane and signalling plane entities for application-enabling services, e.g., group management, configuration management, location management, identity / key management, network resource management, that can be reused across vertical applications. SEAL also specifies the northbound application programming interfaces (API) for its individual services to enable flexible integration with vertical applications.

[0016] In the VAL architecture, a VAL client communicates with a VAL server over VAL- UU reference point. VAL-UU supports both unicast and multicast delivery modes. Fig. 2 depicts a network slice capability enablement (NSCE) architecture in the non-roaming case, using the reference point representation showing how various entities interact with each other.

[0017] The network slice capability enablement client communicates with the network slice capability enablement server over the NSCE-UU reference point. The network slice capability enablement client provides the support for network slice capability enablement functions to the VAL client(s) over NSCE-C reference point. The VAL server(s) communicates with the network slice capability enablement server over the NSCE-S reference point. It is assumed that the network slice capability enablement server is deployed at the 5G system domain. The network slice capability enablement server, acting as application function (AF), may communicate with the 5G Core Network functions via network exposure function NEF (N33) reference point, for interactions with policy control function (PCF), network slice admission control function (NSACF), etc. The network slice capability enablement server may interact with operation, administration and maintenance (GAM) system over NSCE-OAM reference point, as consumer in both network slice as a service (NSaaS) and network operator (NoP) model defined in the clause 4.1.6 and clause 4.1.7 of 3GPP TS 28.530 v.18.0.0, see for Network Slice Provisioning capabilities, Performance Assurance, Fault Supervision etc.

[0018] NOTE: OAM interfaces and / or network slice information can be exposed to an authorized (trusted) third-party , such as a NSCE, only after a contract has been signed between the mobile network operator (MNO) and this third-party. Whether and how CAPIF / EGMF can be used to expose management services (MnS) is up to SA5 decision.

[0019] 3GPP TS 23.435 v.18.0.0 is a service enabler layer to expose network slice capabilities for 3rd party or verticals. In this specification, it is mentioned about - Network Slice Allocation in the NSaaS model, see clause 9.18. A NSCE server allocates network slices on behalf of the VAL server by providing slice allocation as a service to the VAL server since the VAL server cannot access the 5G System directly. In procedure 9.18.2.1, the VAL server provides the slice requirements to the NSCE server and the NSCE server interacts with the 5G System to allocate the slice, server

[0020] SUMMARY

[0021] As part of developing embodiments herein one or more problems was first identified such as:

[0022] - the current procedure defined in clause 9.18.2.1 of TS 23.435 v.18.0.0 can perform slice allocation but cannot report the failed slice allocation to the VAL server as a service exposure. It lacks ways to report the failed instances of a slice allocation;

[0023] - the VAL server can provide more than one slice requirement for various users or UEs and cannot indicate the priority or preference of which slices shall be prioritized for the slice allocation. It is possible that slice allocation can or take relatively more time for the golden subscription of users of the VAL server because of non-prioritized execution of the slice allocation, which negatively impacts quality of service (QoS) for VAL users. The VAL server cannot indicate the NSCE server to allocate slices in the preferred order; during slice allocation, if the NSCE server cannot meet slice requirements then it will result in a failure. This failure could be a false failure because of dynamic network-UE conditions. The VAL server cannot provide alternative slice requirements and slice adjustment measures for slice allocation. It is possible that different users may have different service level agreements (SLA), key performance indicators (KPI), and / or QoS requirements and the VAL server cannot indicate the adjustment in their slice requirements if provided slice requirements lead to failed slice allocation; and

[0024] - the current procedure is modelled as Request-Response. It leads to a non- scalable slice allocation procedure because the NSCE server slice allocation procedure may take time to interact with the 5G system to allocate slices and it may exceed the waiting period of the request session. Because of the delay in the processing and sending Network Slice Allocation response message, the request message session may expire, or timeout and the response cannot be delivered in the same session. The waiting period grows in case of a large number of slices to be allocated. An object of embodiments herein is, thus, to provide a mechanism that improves the performance for handling services in network slices of a wireless communication network.

[0025] According to an aspect the object is achieved by providing a method performed by a VAL server for handling services in a wireless communication network. The VAL server transmits an indication to a control node, wherein the indication indicates one or more network slices to use, and / or an alternative slice requirement and / or adjustment requirement related to a network slice. The VAL server further receives a second indication from the control node, wherein the second indication indicates a decision related to a slice service provision at the control node.

[0026] According to another aspect the object is achieved by providing a method performed by a control node for handling services in a wireless communication network. The control node receives an indication from a VAL server, wherein the indication indicates one or more network slices to use, and / or an alternative slice requirement and / or adjustment requirement related to a network slice. The control node performs a decision related to a slice service provision based on the indication. The control node then sends a second indication to the VAL server, wherein the second indication is related to the performed decision.

[0027] According to yet another aspect the object is achieved by providing a VAL server for handling services in a wireless communication network. The VAL server is configured to transmit an indication to a control node, wherein the indication indicates one or more network slices to use and / or an alternative slice requirement and / or adjustment requirement related to a network slice. The VAL server is further configured to receive a second indication from the control node, wherein the second indication indicates a decision related to a slice service provision at the control node.

[0028] According to another aspect the object is achieved by providing a control node for handling services in a wireless communication network. The control node is configured to receive an indication from a VAL server, wherein the indication indicates one or more network slices to use, and / or an alternative slice requirement and / or adjustment requirement related to a network slice. The control node is further configured to perform a decision related to a slice service provision based on the indication, and to send a second indication to the VAL server, wherein the second indication is related to the performed decision.

[0029] It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the control node, and VAL server, respectively.

[0030] It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the control node, and VAL server, respectively.

[0031] It is herein proposed a solution that adds enhancements to the existing solution described in TS 23.435 v.18.0.0 clause 9.18.2.1 Network Slice Allocation in NSaaS model. The solution allows the VAL server to indicate, for example, a list of network slice identifiers in a prioritized order. Such prioritized order may enable the control node, such as a NSCE server, to allocate slices as per the prioritized list. The VAL server may further in the indication indicate alternative slice requirements to use for slice allocation for failed instances of slice allocation. The indication may further indicate a slice adjustment requirement, such as an adjustment expiration time and / or an adjustment range to adjust the slice requirements during slice allocation. The VAL server may further indicate a notification endpoint to receive the slice allocation notification in a different session, which enables the control node and VAL server to communicate asynchronously for scalable slice allocation procedure. The control node may provide the second indication such as a rejection indication indicating failed network slice allocation information to the VAL server. Thus, this will result in a more flexible solution resulting in an improved performance for handling slice services in the wireless communication network.

[0032] BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Embodiments will now be described in more detail in relation to the enclosed drawings, in which: Fig. 1 shows an overview of V2X services according to prior art;

[0034] Fig. 2 shows a schematic overview depicting a network slice capability enablement (NSCE) architecture according to prior art;

[0035] Fig. 3 shows a schematic overview of a wireless communication network according to embodiments herein:

[0036] Fig. 4 shows a combined flowchart and signalling scheme according to embodiments herein;

[0037] Fig. 5 shows a flowchart depicting a method performed by a VAL server according to embodiments herein; Fig. 6 shows a flowchart depicting a method performed by a control node according to embodiments herein;

[0038] Fig. 7 shows a combined flowchart and signalling scheme according to embodiments herein;

[0039] Fig. 8 is a block diagram depicting a VAL server according to embodiments herein; and Fig. 9 is a block diagram depicting a control node according to embodiments herein.

[0040] DETAILED DESCRIPTION

[0041] Embodiments herein are described within the context of 3GPP NR radio technology. It is understood that the problems and solutions described herein are equally applicable to wireless access networks and UEs implementing other access technologies and standards. NR is used as an example technology where embodiments are suitable, and using NR in the description therefore is particularly useful for understanding the problem and solutions solving the problem. In particular, embodiments are applicable also to 6G, 3GPP LTE, or 3GPP LTE and NR integration, also denoted as non-standalone NR.

[0042] Embodiments herein relate to wireless communication networks in general. Fig. 3 is a schematic overview depicting a wireless communication network 1 . The wireless communication network 1 comprises one or more RANs and one or more CNs. The wireless communication network 1 may use one or a number of different technologies. Embodiments herein relate to recent technology trends that are of particular interest in a NR context, however, embodiments are also applicable in further developments of existing wireless communications systems such as e.g. 6G, LTE or WCDMA.

[0043] In the wireless communication network 1, a user equipment (UE) 10, such as a mobile station, a wireless device, a non-access point (non-AP) STA, a STA, and / or a wireless terminal, is communicating via, e.g., one or more Access Networks (AN), e.g., RAN, to one or more CNs. It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communications terminal or device, user equipment, narrowband (NB)- internet of things (loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node, e.g., smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a network node within an area served by the network node.

[0044] The wireless communication network 10 comprises a radio network node 12, e.g., an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a stand-alone access point, or any other network unit or node capable of communicating with a UE within a service area 11 , such as a cell, served by the network node 12 depending e.g., on a radio access technology and terminology used. The service area 11 may also be referred to as a cell, a beam or a beam group of a first radio access technology (RAT), such as 6G, 5G, LTE, Wi-Fi, or similar. The radio network node 12 may be associated with a first Public Land Mobile Network (PLMN) and / or a first Non-Public Network (NPN).

[0045] The wireless communication network 10 further comprises a VAL server 14., and a control node 15 handling network slice services such as a NSCE server or a network entity that handles a network slice functionality.

[0046] According to embodiments herein the VAL server 14 transmits an indication to the control node 15, wherein the indication indicates one or more network slices to use and / or an alternative slice requirement (along with an existing requirement), and / or a requirement adjustment to alternative requirement or existing requirement, related to a network slice. For example, the VAL server 14 may provide a request with the indication, wherein the indication indicates one or more of: a prioritized list of one or more network slices, one or more alternative slice requirements, one or more slice adjustment requirements, and / or a notification endpoint for a scalable slice allocation procedure. The control node 15 performs a decision related to a slice service provision based on the indication. For example, the control node 15 may determine whether to provide a network slice service to the VAL server 14, and / or apply alternative slice requirements and / or one or more slice adjustment requirements. The control node 15 further sends a second indication to the VAL server 14, wherein the second indication is indicating determination, and / or applied alternative slice requirement and / or slice adjustment requirement.

[0047] Embodiments herein allow one or more of the following:

[0048] - Allowing the VAL server 14 to indicate the prioritized lists of network slices

[0049] - Allowing the VAL server 14 to provide Alternative slice requirements

[0050] - Allowing the VAL server 14 to provide Slice adjustment requirements like an adjustment range, or adjustment expiration time.

[0051] The adjustment range provides the range to the control node 15, such as a NSCE server, to adjust the values of slice requirements for the slice allocation. The control node 15 may apply the adjustment range as a limit on the slice requirements for the slice allocation. The adjustment expiration time provides a time window to adjust the value of slice requirement for slice allocation. This enables the control node 15 to adjust the slice in a certain time window.

[0052] Providing information regarding failed allocation of network slice to the VAL server 14.

[0053] - Allowing the VAL server 14 to provide a notification endpoint for scalable slice allocation procedure.

[0054] Fig. 4 is a combined flowchart and signalling scheme according to some embodiments herein.

[0055] Action 401. The VAL server 14 transmits the indication to the control node 15, wherein the indication indicates one or more network slices to use and / or an alternative slice requirement, and / or an adjustment requirement, related to a network slice. For example, the VAL server 14 may send a request to the control node 15 to order a Network Slice. The VAL server 14 may specify the Network Slice requirements for the VAL service. The Network Slice requirement at the VAL server may be specified with the attributes of Generic network Slice Template (GST), which results in network slice types (NEST), as specified in GSMA NG.116. The request may include a VAL Service ID, VAL UE's ID List, and Single-Network Slice Selection Assistance Information (S-NSSAI). The indication may comprise a list of prioritized slice identifiers for allocation. The VAL server 14 may also provide an endpoint to receive the notification. Embodiments herein may include a prioritized list of network slices enabling the control node 15 to allocate network slices on a priority basis to provide QoS to the VAL users. The alternative slice requirements and / or slice requirements adjustment may enable the control node 15 to adjust the slice requirements during slice allocation, and the slice requirements adjustment may provide allocation of network slices in case of failure of another network slice leading to improved QoS of the VAL users.

[0056] Action 402. The control node 15 may determine whether to provide a network slice service to the VAL server 14, and / or apply alternative slice requirement and / or one or more slice adjustment requirements as indicated by the received indication.

[0057] Action 403. The control node 15 may further apply the indication and / or allow access to the requested network slice. For example, the control node 15 may perform a Network Slice Allocation. If the control node 15 acts as NSaaS provider, and the existing allocated network slice can satisfy the Network Slice requirements, the control node 15 may allocate the existing network slice to the VAL server 14. Otherwise, the control node 15 as network slice provisioning MnS consumer requests of 'AllocacatedNsi' operation as specified in 3GPP TS 28.531 v.18.0.0. If the VAL server 14 provides the slice adjustment requirement then the control node 15 may use the slice adjustment requirement for slice allocation. The alternative slice requirement and / or slice requirement adjustment in the request may comprise a range to adjust the values of slice requirement for the slice allocation, and / or an adjustment expiration time providing a time window to adjust the value of slice requirement for slice allocation.

[0058] Action 404. The control node 15 further sends the second indication to the VAL server 14, wherein the second indication is indicating determination, and / or applied alternative slice requirement and / or slice adjustment requirement. The control node 15 may thus send the result of network slice allocation to the VAL server 14 as a notification message if the endpoint is provided by the VAL server 14, otherwise a response message may be used. The response message may include a failed slice requirement indication, indicating that the adjustment / requirement / network slice cannot be allocated by the control node 15. The second indication indicating, for example, rejection that provides failed network slice allocation information to the VAL server 14 may aid the VAL server 14 to understand which network slice(s) are allocated and failed. This helps the VAL server

[0059] 14 to maintain the telemetry, analytics, understand the experience of the VAL users, and / or evaluate the Network Slice service provider SLA or KPI values. The delivery of a slice allocation response as a notification in a separate session enables the control node

[0060] 15 to create a scalable slice allocation.

[0061] Fig. 5 illustrates an example of a method performed by the VAL server 14 for handling services in the wireless communication network 1 in accordance with embodiments herein.

[0062] Action 501. The VAL server 14 transmits the indication to the control node 15, wherein the indication indicates the one or more network slices to use, and / or the alternative slice requirement and / or requirement adjustment related to a network slice. For example, the VAL server 14 may provide a request with the indication, wherein the indication indicates one or more of: a prioritized list of one or more network slices, one or more alternative slice requirements, one or more slice adjustment requirements, and / or a notification endpoint for a scalable slice allocation procedure. The alternative slice requirement and / or adjustment requirement in the request may comprise a range to adjust one or more values of a requirement for slice allocation, and / or an adjustment expiration time providing a time window to adjust a value of the requirement for slice allocation.

[0063] Action 502. The VAL server 14 receives the second indication from the control node 15, wherein the second indication indicates the decision related to the slice service provision at the control node 15. The second indication may be an indication of determination, and / or applied alternative slice requirement and / or slice adjustment requirement. The second indication may comprise a failure indication and / or information related to the allocation of a network slice.

[0064] Fig. 6 illustrates an example of a method performed by the control node 15, such as a NSCE server, for handling services in the wireless communication network 1 in accordance with embodiments herein.

[0065] Action 601. The control node 15 receives the indication from the VAL server 14, wherein the indication indicates the one or more network slices to use and / or, the alternative slice requirement and / or adjustment requirement related to a network slice. The indication may indicate one or more of: a prioritized list of one or more network slices, one or more alternative slice requirements, one or more slice adjustment requirements, and / or a notification endpoint for a scalable slice allocation procedure The alternative slice requirement and / or adjustment requirement in the request may comprise a range to adjust one or more values of a requirement for slice allocation, and / or an adjustment expiration time providing a time window to adjust a value of the requirement for slice allocation.

[0066] Action 602. The control node 15 performs the decision related to the slice service provision based on the indication. For example, the control node 15 may determine whether to provide the network slice service to the VAL server 14, and / or apply the alternative slice requirement and / or one or more slice adjustment requirements.

[0067] Action 603. The control node 15 sends the second indication to the VAL server 14, wherein the second indication is related to the performed decision. The second indication may be indicating determination, and / or applied alternative slice requirement and / or slice adjustment requirement. The second indication may comprise a failure indication and / or information related to the allocation of a network slice.

[0068] It should be noted that the current procedure described in TS 23.435 v.18.0.0 clause 9.18.2.1 allocates a slice to the VAL server 14 but does not provide a failed network slice information list. It is possible that the control node 15 will not meet all the slice requirements described by the VAL server 14. Hence it may be necessary to update the VAL server 14 for the failed network slice information. The VAL server 14 may provide more than one slice for allocation and some slices could have a preference to be allocated first for KPI or SLA reasons. For example, the slice allocation may be for golden subscribers of the VAL server 14 but currently there is no way to indicate the preference which slice shall be created first. During allocation, it may happen that slice requirements are not exactly met, and this may lead to the failure of a slice allocation. The slice adjustment requirements and alternative slice requirements provide an opportunity for the VAL server 14 to indicate the slice requirements adjustment to the control node 15 during slice allocation. The current request-response model is not sufficient for configuring more than one network slice or a large number of network slices. The VAL server 14 in case of requesting multiple slice allocation, the existing procedure request message session can timeout due to waiting for the response because slice allocation involves configuring and interacting with other network entities. Embodiments herein may ask the VAL server 14 to provide a notification endpoint to send the notification of network slice information for a scalable slice allocation procedure. Priority may be added in the indication to allocate the slice in case of more than one slice, and / or slice adjustments to allow a network slice within a certain accepted adjustment window. Embodiments herein may add a separate notification message, such as the second indication, to notify the slice allocation response, which may also notify the VAL server 14 for failed network slice allocation.

[0069] Embodiments herein may enable the VAL server 14 to indicate the priority for slice allocation for its users, an alternative slice requirement, and / or a slice adjustment requirement. Furthermore, the VAL server 14 may be aware of failed slice information and may provide alternative requirements for slice allocation.

[0070] Some exemplified changes, according to some embodiments herein, in TS 23.435 v.18.0.0 are underlined below:

[0071] 9.18.2 Procedure

[0072] 9.18.2.1 Network Slice Allocation in NSaaS model This subclause depicts the procedure of the Network Slice Allocation in NSaaS model, when the VAL server needs to allocate the Network Slice, interaction with 5GS via the NSCE server.

[0073] Figure 7: Network Slice Allocation in NSaaS model 71. The VAL server makes a request to order the Network Slice. The VAL server specifies the Network Slice requirements for the VAL service. The Network Slice requirement at the VAL server may be specified with the attributes of GST (which results in NEST) as specified in GSMA NG.116.

[0074] 72. The VAL server requests the Network Slice allocation with the Network Slice requirements. The Network Slice allocation request includes the VAL Service ID, VAL UE's ID List, and S -NS SAL The VAL server prioritizes the slice identifier list for allocation. The VAL server also provides an endpoint to receive the notification.

[0075] 73. The NSCE server performs the Network Slice Allocation. If the NSCE server act as NSaaS provider, and the existing allocated network slice could satisfied the Network Slice requirements, the NSCE server allocates the existing network slice to the VAL. Otherwise, the NSCE server as network slice provisioning MnS consumer requests of 'AllocacatedNsi' operation as specified in 3GPP TS 28.531 [8], If the VAL server provides the Slice adjustment requirements then the NSCE server uses the Slice adjustment requirements for slice allocation.

[0076] When the 'AllocatedNsi' operation is received, the network slice provisioning MnS Producer performs charging mechanism as specified in 3GPP TS 28.202

[0028] ,

[0077] The NSCE server performs AF-driven guidance for URSP determination to 5GS per VAL UE.

[0078] NOTE 1 : According to the network operator policy, the NSCE server acting as AF may send the created network slice information to the PCF via NEF as part of the AF-driven guidance for URSP determination to 5G system (as specified in TS 23.501

[0016] ). This guidance may create the new route selection parameters to indicate sets of PDU Session information (DNN, S-NSSAI) that can be associated with applications matching the application traffic.

[0079] The NSCE server sends the result of Network Slice Allocation to the VAL server as a notification message if the endpoint is provided by the VAL server (see action 76) otherwise the response message is used (see action 74). The response includes the failed slice requirements which cannot be allocated by the NSCE server.

[0080] Optionally, the VAL server can include alternative slice requirements and slice requirements adjustment in the request. The adjustment range provides the range to the NSCE server to adjust the values of slice requirements for the slice allocation. The adjustment expiration time provides the time window to adjust the value of slice requirement for slice allocation.

[0081] 75. The NSCE server delivers the Network Slice Allocation Information to the NSCE Clients of VAL UEs based on the VAL UE's ID list from step 2, using the procedure defined in 9. 17.2.2 step 2 - step 4, in case the Network Slice Allocation is successful, if the NSCE server does not perform AF-driven guidance for URSP determination to 5GS in step 3. The Network Slice Allocation Information contains the VAL service ID, S-NSSAI, and DNN.

[0082] NOTE 2: If the UE is provisioned with URSP rules by the network operator, the UE handles the precedence between the delivered network slice info via NSCE layer info and URSP rules as defined in clause 6.1.2.2. 1 of 3GPP TS 23.503

[0017] , How the UE uses the Network Slice info delivered via NSCE layer in relation to the URSP is implementation dependent.

[0083] 9.18.3 Information flows

[0084] 9.18.3.1 General

[0085] The following information flows are specified for Network Slice Allocation:

[0086] - Network Slice Allocation request and response.

[0087] 9.18.3.2 Network Slice Allocation

[0088] Table 9.18.3.2-1 and Table 9.18.3.2-2 describe information elements for Network Slice

[0089] Allocation request and response between the VAL server and the NSCE server. Table 9.18.3.2-1 : Network Slice Allocation request

[0090] Table 9.18.3.2-2: Network Slice Allocation response

[0091] Table 9.18.3.2-3: Network Slice Allocation notification

[0092] Fig. 8 depicts embodiment of the VAL server 14 for handling services in the wireless communication network according to embodiments herein.

[0093] The VAL server 14 may comprise processing circuitry 801 , e.g. one or more processors, configured to perform the methods herein. The VAL server 14 and / or the processing circuitry 801 is configured to transmit the indication to the control node 15, wherein the indication indicates the one or more network slices to use, and / or the alternative slice requirement and / or requirement adjustment related to a network slice. For example, the VAL server 14 and / or the processing circuitry 801 may be configured to provide the request with the indication, wherein the indication indicates the one or more of: a prioritized list of one or more network slices, one or more alternative slice requirements, one or more slice adjustment requirements, and / or a notification endpoint for a scalable slice allocation procedure.

[0094] The VAL server 14 and / or the processing circuitry 801 is configured to receive the second indication from the control node 15, wherein the second indication indicates the decision related to a slice service provision at the control node 15. The second indication may be the indication of determination, and / or applied alternative slice requirement and / or slice adjustment requirement. The second indication may comprise a failure indication and / or information related to the allocation of a network slice. Thus, the VAL server 14 may be aware of failed slice information and may provide alternative requirements for slice allocation.

[0095] The methods according to the embodiments described herein for the VAL server 14 are respectively implemented using e.g., a computer program product 807 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the VAL server 14. The computer program product 807 may be stored on a computer-readable storage medium 808, e g. a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 808, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the VAL server 14. In some embodiments, the computer-readable storage medium may be a transitory or a non- transitory computer-readable storage medium. Thus, embodiments herein may disclose a VAL server 14 for handling communication in a wireless communication network, wherein the VAL server 14 comprises processing circuitry and a memory, the memory comprising instructions executable by the processing circuitry whereby the VAL server 14 is operative to perform any of the methods herein. Fig. 9 depicts embodiment of the control node 15, such as a NSCE server, for handling services in the wireless communication network according to embodiments herein.

[0096] The control node 15 may comprise processing circuitry 901 , e.g. one or more processors, configured to perform the methods herein.

[0097] The control node 15 and / or the processing circuitry 901 is configured to receive the indication from the VAL server 14, wherein the indication indicates the one or more network slices to use and / or, the alternative slice requirement and / or adjustment requirement related to a network slice.

[0098] The control node 15 and / or the processing circuitry 901 is configured to perform the decision related to the slice service provision based on the indication. For example, the control node 15 and / or the processing circuitry 901 may be configured to determine whether to provide the network slice service to the VAL server 14, and / or apply the alternative slice requirement and / or one or more slice adjustment requirements.

[0099] The control node 15 and / or the processing circuitry 901 is configured to send the second indication to the VAL server 14, wherein the second indication is related to the performed decision. The second indication may be indicating determination, and / or applied alternative slice requirement and / or slice adjustment requirement.

[0100] The control node 15 further comprises a memory 905. The memory 905 comprises one or more units to be used to store data on, such as indications, mapping, second indication, network slice information, thresholds, data related to nodes, and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the control node 15 may comprise a communication interface 906 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas, such as antenna arrays.

[0101] The methods according to the embodiments described herein for the control node 15 are respectively implemented using e.g., a computer program product 907 or a computer program, comprising instructions, i.e. , software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the control node 15. The computer program product 907 may be stored on a computer-readable storage medium 908, e.g. a disc, a USB stick or similar. The computer-readable storage medium 908, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the control node 15. In some embodiments, the computer- readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose a control node 15 for handling communication in a wireless communication network, wherein the control node 15 comprises processing circuitry and a memory, the memory comprising instructions executable by the processing circuitry whereby the control node 15 is operative to perform any of the methods herein.

[0102] In some embodiments, a more general term “network node” is used and it can correspond to any type of radio network node or any network node, which communicates with a UE and / or with another network node. Examples of network nodes are NodeB, Master eNB, Secondary eNB, a network node belonging to Master cell group (MCG) or Secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, network controller, radio-network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), etc.

[0103] In some embodiments, the non-limiting term wireless device or UE is used and it refers to any type of wireless device communicating with a network node and / or with another wireless device in a cellular or mobile communication system. Examples of UE are loT capable device, target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, etc.

[0104] Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and / or transmit signals (e.g. data) e.g. New Radio (NR), Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0105] As will be readily understood by those familiar with communications design, that functions means or circuits may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.

[0106] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and / or program or application data. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0107] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0108] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non- transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0109] It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

Claims

CLAIMS1. A method performed by a vertical application layer, VAL, server (14) for handling services in a wireless communication network (1), the method comprising transmitting (501) an indication to a control node (15), wherein the indication indicates one or more network slices to use, and / or an alternative slice requirement and / or a requirement adjustment related to a network slice; and receiving (502) a second indication from the control node (15), wherein the second indication indicates a decision related to a slice service provision at the control node (15).

2. The method according to claim 1, wherein transmitting the indication comprises providing a request with the indication, wherein the indication indicates one or more of: a prioritized list of one or more network slices, one or more alternative slice requirements, one or more slice adjustment requirements, and / or a notification endpoint for a scalable slice allocation procedure.

3. The method according to any of the claims 1-2, wherein the alternative slice requirement and / or adjustment requirement comprises a range to adjust one or more values of a requirement for slice allocation, and / or an adjustment expiration time providing a time window to adjust a value of the requirement for slice allocation.

4. The method according to any of the claims 1-3, wherein the second indication is an indication of determination, and / or applied alternative slice requirement and / or slice adjustment requirement.

5. The method according to any of the claims 1-4, wherein the second indication comprise a failure indication.

6. A method performed by a control node (15) for handling services in a wireless communication network 1 , the method comprising receiving (601) an indication from a vertical application layer, VAL, server (14), wherein the indication indicates one or more network slices to use and / or, an alternative slice requirement and / or adjustment requirement related to a network slice;- performing (602) a decision related to a slice service provision based on the indication; and sending (603) a second indication to the VAL server (14), wherein the second indication is related to the performed decision.

7. The method according to claim 6, wherein performing the decision comprises determining whether to provide the network slice service to the VAL server (14), and / or apply the alternative slice requirement and / or one or more slice adjustment requirements.

8. The method according to any of the claims 6-7, wherein receiving the indication comprises obtaining a request with the indication, wherein the indication indicates one or more of: a prioritized list of one or more network slices, one or more alternative slice requirements, one or more slice adjustment requirements, and / or a notification endpoint for a scalable slice allocation procedure.

9. The method according to any of the claims 6-8, wherein the alternative slice requirement and / or adjustment requirement comprises a range to adjust one or more values of a requirement for slice allocation, and / or an adjustment expiration time providing a time window to adjust a value of the requirement for slice allocation.

10. The method according to any of the claims 6-9, wherein the second indication is an indication of determination, and / or applied alternative slice requirement and / or slice adjustment requirement.

11. The method according to any of the claims 6-10, wherein the second indication comprise a failure indication.

12. A vertical application layer, VAL, server (14) for handling services in a wireless communication network (1), wherein the VAL server (14) is configured to transmit an indication to a control node (15), wherein the indication indicates one or more network slices to use, and / or an alternative slice requirement and / or a requirement adjustment related to a network slice; andreceive a second indication from the control node (15), wherein the second indication indicates a decision related to a slice service provision at the control node (15).

13. The VAL (14) server according to claim 12, wherein the VAL server (14) is configured to perform the method according to any of the claims 2-5.

14. A control node (15) for handling services in a wireless communication network (1), wherein the control node is configured to receive an indication from a vertical application layer, VAL, server (14), wherein the indication indicates one or more network slices to use and / or, an alternative slice requirement and / or adjustment requirement related to a network slice; perform a decision related to a slice service provision based on the indication; and send a second indication to the VAL server (14), wherein the second indication is related to the performed decision.

15. The control node (15) according to claim 14, wherein the control node (15) is configured to perform the method according to any of the claims 7-11.

16. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-11 herein, as performed by the control node, and VAL server, respectively.

17. A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-11 herein, as performed by the control node, and VAL server, respectively.

Images