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

Abstract

Embodiments herein relate to a method for handling services in a wireless communication network, e.g. Performed by a VAL server (14) or a control node (15). The VAL server (14) sends an indication to the control node (15), where the indication indicates one or more network slices to be used, and / or alternative slice requirements and / or requirement adjustments associated with the network slices. The VAL then receives a second indication from the control node (15), where the second indication indicates a decision related to slicing service provision at the control node (15).

Description

Control nodes, vertical application layer servers, and methods executed in wireless communication networks. Technical Field

[0001] The embodiments described herein relate to control nodes, vertical application layer (VAL) servers, and methods for wireless communication executed therein. Furthermore, computer program products and computer-readable storage media are also provided herein. In particular, the embodiments described herein relate to processing or enabling communications in a communication network, such as managing slice services. Background Technology

[0002] In a typical communication network, User Equipment (UE) (also known as wireless communication equipment, mobile station, station (STA), and / or wireless device) communicates with one or more core networks (CN) via a Radio Access Network (RAN). RAN coverage is divided into geographical areas of service or cell areas, each served by a network node, such as an access node (e.g., a Wi-Fi access point) or a Radio Base Station (RBS) (which may also be referred to as NodeB, evolved NodeB (eNodeB), and gNodeB (gNB) in some Radio Access Technologies (RATs)). A service area or cell area is a geographical area where radio coverage is provided by a network node. Network nodes operate on radio frequency to communicate with UEs within range of the access node via an air interface. Network nodes transmit messages to the UE via downlink (DL), and the UE transmits messages to the access node via uplink (UL).

[0003] Universal Mobile Telecommunications System (UMTS) is a third-generation telecommunications network that evolved from the second-generation (2G) Global System for Mobile Communications (GSM). The UMTS Terrestrial Radio Access Network (UTRAN) is essentially a RAN that uses Wideband Code Division Multiple Access (WCDMA) and / or High-Speed ​​Packet Access (HSPA) for communication with user equipment. In a forum known as the 3rd Generation Partnership Project (3GPP), telecommunications vendors propose and agree on standards for current and future generation networks, particularly UTRAN, and study enhanced data rates and radio capacity. In some RANs, such as in UMTS, several network nodes may be connected, for example, via terrestrial lines or microwave to a controller node, such as a Radio Network Controller (RNC) or Base Station Controller (BSC), which monitors and coordinates the various activities of the multiple network nodes connected to it. The RNC is typically connected to one or more CNs.

[0004] Specifications for Evolved Packet Systems (EPS) have been finalized within the 3rd Generation Partnership Project (3GPP), and this work continues in upcoming 3GPP releases, such as 5G and 6G networks. EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) (also known as Long Term Evolution (LTE) Radio Access Network) and the Evolved Packet Core (EPC) (also known as the System Architecture Evolution (SAE) Core Network). E-UTRAN / LTE is a 3GPP radio access technology in which network nodes are directly connected to the EPC core network. Therefore, the RAN of EPS has a substantially non-hierarchical architecture, consisting of network nodes directly connected to one or more CNs.

[0005] With the advent of 5G technology (also known as New Radio (NR)) and / or the upcoming 6G RAN, numerous transmit and receive antenna elements are available that can utilize beamforming, such as transmitter-side beamforming and receiver-side beamforming. Transmitter-side beamforming means that the transmitter can amplify signals transmitted in one or more selected directions while suppressing signals transmitted in other directions. Similarly, at the receiver, the receiver can amplify signals from one or more selected directions while suppressing unwanted signals from other directions. The benefit is increased cell capacity and coverage.

[0006] Furthermore, it supports vehicle-to-everything (V2X) communication, which includes any combination of direct communication between vehicles, pedestrians, and infrastructure. V2X communication can utilize network (NW) infrastructure (where available), however, at least basic V2X connectivity should be possible, even in cases of insufficient coverage. Due to the economies of scale of LTE, providing an LTE-based V2X interface can be economically advantageous, and it enables tighter integration with NW infrastructure communications (e.g., vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), and vehicle-to-vehicle (V2V) communication) compared to using dedicated V2X technologies.

[0007] Numerous research projects and field tests exist in various countries and regions regarding connected vehicles, including projects based on the use of existing cellular infrastructure.

[0008] V2X communication can carry both insecure and secure information, and each application and service can be associated with specific requirements (such as latency, reliability, capacity, etc.). From an application perspective, V2X includes the following types of communication / services, as shown in Figure 1.

[0009] Vehicle-to-vehicle (V2V):This covers communication between vehicles using V2V applications and is primarily broadcast-based. V2V can be achieved through direct communication between devices within the respective vehicles or via infrastructure such as cellular networks. An example of V2V is the repeated transmission of Cooperative Awareness (CAM) messages containing vehicle status information such as position, direction, and speed to other nearby vehicles (e.g., every 100ms–1s). Another example is the transmission of Distributed Environmental Notification (DENM) messages, which are event-triggered messages to alert vehicles. These two examples are taken from the ETS Intelligent Transportation Systems (ITS) specification for V2X applications, which also specifies the conditions for message generation. A key characteristic of V2V applications is the stringent requirements regarding latency, which can vary from 20ms for pre-collision warning messages to 100ms for other road safety services.

[0010] Vehicle to Infrastructure (V2I): This includes communication between vehicles and roadside units (RSUs). An RSU can be a stationary traffic infrastructure entity that communicates with vehicles in its vicinity. Examples of V2I include sending speed notifications from the RSU to vehicles, as well as sending queue information, collision risk warnings, and / or cornering speed warnings. Due to the safety-related nature of V2I, latency requirements are similar to those for V2V.

[0011] Vehicle-to-pedestrian (V2P): This covers communication between vehicles using V2P applications and vulnerable road users, such as pedestrians. V2P typically occurs between different vehicles and pedestrians, either directly or via infrastructure such as cellular networks.

[0012] Vehicle to Network (V2N): This covers communication between vehicles and centralized application servers or ITS traffic management centers via infrastructure such as cellular networks, both of which use V2N applications. An example is a warning of poor road conditions sent to all vehicles over a large area, or traffic flow optimization, where the V2N application suggests speeds to vehicles and coordinates traffic lights. Therefore, V2N messages should be controlled by a centralized entity (such as a traffic management center) and can be delivered to vehicles over a large geographic area rather than a small one. Furthermore, unlike V2V / V2I, latency requirements are more lenient in V2N because it is not designed for safety purposes; for example, a latency requirement of 1 second is typically considered.

[0013] Since 3GPP Release 16, the Service Enablement Architecture Layer (SEAL) for Vertical Industries has been introduced to support vertical applications such as V2X applications. 3GPP TS 23.434 v.18.5.0 specifies application plane and signaling plane entities for application enabling services (e.g., group management, configuration management, location management, identity / key management, network resource management), which can be reused in vertical applications. SEAL also specifies northbound application programming interfaces (APIs) for its separate services to enable flexible integration with vertical applications.

[0014] In the VAL architecture, VAL clients communicate with the VAL server through the VAL-UU reference point. VAL-UU supports both unicast and multicast delivery modes. Figure 2 depicts the Network Slicing Capability Enablement (NSCE) architecture in a non-roaming scenario, using reference points to illustrate how various entities interact.

[0015] Network slicing capability enabling clients communicate with the network slicing capability enabling server via the NSCE-UU reference point. The network slicing capability enabling client provides support for network slicing capability enabling functions to (one or more) VAL clients via the NSCE-C reference point. (One or more) VAL servers communicate with the network slicing capability enabling server via the NSCE-S reference point. Assume the network slicing capability enabling server is deployed in the 5G system domain. The network slicing capability enabling server, acting as an application function (AF), can communicate with 5G core network functions via the Network Open Function (NEF) (N33) reference point for interaction with Policy Control Function (PCF), Network Slice Admission Control Function (NSACF), etc. The network slicing capability enabling server can interact with the Operations Management and Maintenance (OAM) system through the NSCE-OAM reference point, acting as a consumer in both the Network Slice as a Service (NSaaS) and Network Operator (NoP) models as defined in Clauses 4.1.6 and 4.1.7 of 3GPP TS 28.530v.18.0.0. See Network Slicing Capability Provision, Performance Guarantee, Fault Monitoring, etc.

[0016] Note: OAM interface and / or network slicing information may only be made available to a third party after a contract has been entered into between the mobile network operator (MNO) and an authorized (trusted) third party (such as the NSCE). Whether and how CAPIF / EGMF is used for Open Managed Services (MnS) is a matter for SA5 to decide.

[0017] 3GPP TS 23.435 v.18.0.0 is a service enablement layer that provides network slicing capabilities to third parties or vertical industries. This specification mentions network slice allocation in the NSaaS model (see Section 9.18). Since the VAL server cannot directly access the 5G system, the NSCE server allocates network slices on behalf of the VAL server by providing a slice allocation-as-a-service to the VAL server. In procedure 9.18.2.1, the VAL server provides a slice request to the NSCE server, and the NSCE server interacts with the 5G system to allocate slices to the server. Summary of the Invention

[0018] As part of developing the embodiments described herein, one or more problems are first identified, such as:

[0019] The current procedure, as defined in section 9.18.2.1 of TS 23.435 v.18.0.0, can perform slice allocation but cannot report failed slice allocations to the VAL server as a service exposure. It lacks a way to report failed instances of slice allocation.

[0020] - A VAL server can provide more than one slice request for various users or UEs and cannot indicate which slices should be prioritized or preferred for slice allocation. It is possible that due to the non-prioritized execution of slice allocation, slice allocation may take relatively longer for users with gold subscriptions on the VAL server, negatively impacting the Quality of Service (QoS) for VAL users. The VAL server cannot instruct the NSCE server to allocate slices in a preferred order;

[0021] - During slice allocation, if the NSCE server cannot meet the slice requirements, it will result in a failure. Due to dynamic network-UE conditions, this failure may be a false failure. The VAL server cannot provide alternative slice requirements or slice adjustment measures for slice allocation. It is possible that different users may have different Service Level Agreements (SLAs), Key Performance Indicators (KPIs), and / or QoS requirements, and if the provided slice requirements result in a failed slice allocation, the VAL server cannot indicate adjustments to the slice requirements; and

[0022] The current process is modeled as a request-response. This results in a non-scalable slice allocation process because the NSCE server slice allocation process can take time to interact with the 5G system to allocate slices, and it may exceed the waiting period of the request session. Due to the latency in processing and sending network slice allocation response messages, request message sessions may expire or time out, and responses cannot be delivered within the same session. With a large number of slices to allocate, the waiting period increases.

[0023] Therefore, the purpose of the embodiments described herein is to provide a mechanism for improving the performance of services in network slices of wireless communication networks.

[0024] According to one aspect, this objective is achieved by providing a method for processing services in a wireless communication network, executed by a VAL server. The VAL server sends an instruction to a control node, wherein the instruction specifies one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements associated with the network slices. The VAL server further receives a second instruction from the control node, wherein the second instruction specifies a decision related to slice service provision at the control node.

[0025] According to another aspect, this objective is achieved by providing a method for processing services in a wireless communication network, executed by a control node. The control node receives an instruction from a VAL server, wherein the instruction specifies one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements related to the network slices. Based on the instruction, the control node performs a decision related to the provision of slice services. The control node then sends a second instruction to the VAL server, wherein the second instruction is related to the decision performed.

[0026] According to another aspect, this objective is achieved by providing a VAL server for processing services in a wireless communication network. The VAL server is configured to send an instruction to a control node, wherein the instruction specifies one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements associated with the network slices. The VAL server is also configured to receive a second instruction from the control node, wherein the second instruction specifies a decision related to slice service provision at the control node.

[0027] According to another aspect, this objective is achieved by providing a control node for processing services in a wireless communication network. The control node is configured to receive an instruction from a VAL server, wherein the instruction specifies one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements related to the network slices. The control node is further configured to: based on the instruction, perform a decision related to the provision of slice services, and send a second instruction to the VAL server, wherein the second instruction is related to the decision performed.

[0028] Furthermore, this document provides a computer program product including instructions that, when executed on at least one processor, cause at least one processor to perform the methods of this document, as performed by a control node and a VAL server, respectively.

[0029] Furthermore, this document provides a computer-readable storage medium on which a computer program product including instructions, when executed on at least one processor, causes the at least one processor to perform the methods of this document, as performed by a control node and a VAL server, respectively.

[0030] This paper presents an enhanced solution to the existing solution described in Section 9.18.2.1, “Network Slice Allocation in the NSaaS Model,” of TS 23.435 v.18.0.0. This solution allows the VAL server to indicate, for example, a list of network slice identifiers in a priority order. This priority order enables control nodes (such as NSCE servers) to allocate slices according to the priority list. The VAL service can further indicate, in the indication, alternative slice requirements to be used for slice allocation in cases of failed allocation. This indication can also indicate slice adjustment requirements for adjusting slice requirements during allocation, such as adjustment expiration time and / or adjustment range. The VAL server can further instruct notification endpoints to receive slice allocation notifications in different sessions, enabling asynchronous communication between the control node and the VAL server for a scalable slice allocation process. The control node can provide the VAL server with a second indication of failed network slice allocation information, such as a rejection indication. Therefore, this results in a more flexible solution, leading to improved performance for handling slice services in wireless communication networks. Attached Figure Description

[0031] The embodiments will now be described in more detail with reference to the accompanying drawings, wherein:

[0032] Figure 1 shows an overview of V2X services based on existing technology;

[0033] Figure 2 shows a schematic overview of the Network Slicing Capability Enablement (NSCE) architecture according to the prior art;

[0034] Figure 3 illustrates a schematic overview of a wireless communication network according to embodiments herein.

[0035] Figure 4 illustrates a combined flowchart and signaling scheme according to embodiments herein;

[0036] Figure 5 shows a flowchart depicting a method performed by a VAL server according to an embodiment of this document;

[0037] Figure 6 shows a flowchart depicting a method performed by a control node according to an embodiment herein;

[0038] Figure 7 illustrates a flowchart and signaling scheme for a combination according to embodiments herein;

[0039] Figure 8 is a block diagram depicting a VAL server according to an embodiment herein; and

[0040] Figure 9 is a block diagram depicting a control node according to an embodiment herein. Detailed Implementation

[0041] The embodiments described herein are set in the context of 3GPP NR radio technology. It should be understood that the problems and solutions described herein are equally applicable to radio access networks and UEs implementing other access technologies and standards. NR is used as an example technology in which the embodiments are suitable; therefore, the use of NR in the description is particularly useful for understanding the problems and solutions. In particular, the embodiments are also applicable to 6G, 3GPP LTE, or 3GPP LTE and NR integration (also referred to as non-standalone NR).

[0042] The embodiments described herein generally relate to wireless communication networks. Figure 3 is a schematic overview depicting a wireless communication network 1. Wireless communication network 1 includes one or more RANs and one or more CNs. Wireless communication network 1 may use one or more different technologies. The embodiments described herein relate to recent technology trends of particular interest in the NR context; however, the embodiments are also applicable to further developments of existing wireless communication systems, such as, for example, 6G, LTE, or WCDMA.

[0043] In wireless communication network 1, user equipment (UE) 10 (such as mobile stations, wireless devices, non-access point (non-AP) STAs, STAs, and / or wireless terminals) communicates with one or more CNs via, for example, one or more access networks (ANs) (e.g., RANs). Those skilled in the art will understand that "UE" is a non-limiting term and refers to any terminal, wireless communication terminal or device, user equipment, narrowband (NB)-Internet of Things (IoT) device, machine-type communication (MTC) device, device-to-device (D2D) terminal, or node, such as a smartphone, laptop, mobile phone, sensor, relay, mobile tablet computer, or even a small base station capable of communicating with network nodes within an area served by network nodes using radio communication.

[0044] Wireless communication network 10 includes radio network nodes 12, such as access nodes, access controllers, base stations, such as radio base stations, including gNodeB (gNB), evolved NodeB (eNB, eNode B), NodeB, base transceiver station, radio remote unit, access point base station, base station router, wireless local area network (WLAN) access point or access point station (AP STA), or any other network element or node capable of communicating with a UE within a service area 11 (such as a cell) served by network node 12, depending on, for example, the radio access technology and terminology used. Service area 11 may also be referred to as a cell, beam, or beam group of a first radio access technology (RAT), such as 6G, 5G, LTE, Wi-Fi, etc. Radio network node 12 may be associated with a first public terrestrial mobile network (PLMN) and / or a first non-public network (NPN).

[0045] The wireless communication network 10 also includes a VAL server 14 and a control node 15 that processes network slicing services, such as an NSCE server or a network entity that processes network slicing functions.

[0046] According to embodiments herein, VAL server 14 sends an instruction to control node 15, wherein the instruction specifies one or more network slices to be used, and / or alternative slice requirements (together with existing requirements) and / or adjustments to the alternative or existing requirements. For example, VAL server 14 may provide a request with an instruction specifying one or more of the following: a priority 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 the scalable slice allocation process. Control node 15 performs decisions related to slice service provision based on the instruction. For example, control node 15 may determine whether to provide network slice services to VAL server 14 and / or apply alternative slice requirements and / or one or more slice adjustment requirements. Control node 15 also sends a second instruction to VAL server 14, wherein the second instruction specifies the determined and / or applied alternative slice requirements and / or slice adjustment requirements.

[0047] The embodiments described herein allow one or more of the following:

[0048] - Allows VAL server 14 to indicate a preferred list of network slices;

[0049] - Allows VAL server 14 to provide alternative slicing requirements;

[0050] - Allows VAL server 14 to provide slice adjustment requirements, such as adjustment range or adjustment expiration time.

[0051] The adjustment range provides the control node 15 (such as the NSCE server) with a range of values ​​for adjusting the slice requirements used for slice allocation. The control node 15 can apply the adjustment range as a restriction on the slice requirements used for slice allocation.

[0052] The adjustment expiration time provides a time window for adjusting the slice requirements used for slice allocation. This allows control node 15 to adjust slices within a specific time window.

[0053] - Provide VAL server 14 with information about failed network slice allocations.

[0054] - Allows VAL server 14 to provide a notification endpoint for the scalable slice allocation process.

[0055] Figure 4 is a flowchart and signaling scheme of combinations according to some embodiments described herein.

[0056] Action 401. VAL server 14 sends an indication to control node 15, wherein the indication specifies one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements related to the network slices. For example, VAL server 14 may send a request to control node 15 to order network slices. VAL server 14 may specify network slice requirements for VAL services. Network slice requirements at the VAL server may be specified using attributes of a generic network slice template (GST) as defined in GSMA NG.116, resulting in a network slice type (NEST). The request may include the VAL service ID, a list of VAL UE IDs, and Single Network Slice Selection Assistance Information (S-NSSAI). The indication may include a list of priority slice identifiers for allocation. VAL server 14 may also provide an endpoint to receive notifications. Embodiments herein may include a priority list of network slices that enables control node 15 to allocate network slices according to priority to provide QoS to VAL users. Alternative slice requirements and / or slice requirement adjustments enable control node 15 to adjust slice requirements during slice allocation, and slice requirement adjustments can provide network slice allocation in the event of another network slice failure, resulting in improved QoS for VAL users.

[0057] Action 402. Control node 15 may determine whether to provide network slicing services to VAL server 14, and / or apply alternative slice requests and / or one or more slice adjustment requests as indicated by the received instructions.

[0058] Action 403. Control Node 15 may further apply instructions and / or allow access to the requested network slice. For example, Control Node 15 may perform network slice allocation. If Control Node 15 is acting as an NSaaS provider and the existing allocated network slice meets the network slice requirements, Control Node 15 may allocate the existing network slice to VAL Server 14. Otherwise, Control Node 15, acting as a network slice provider Mns consumer, requests the “AllocacatedNsi” operation as specified in 3GPP TS 28.531 v.18.0.0. If VAL Server 14 provides a slice adjustment request, Control Node 15 may use that slice adjustment request for slice allocation. Alternative slice requirements and / or slice requirement adjustments in the request may include adjusting the range of values ​​for the slice requirements used for slice allocation and / or providing an adjustment expiration time for a time window of the adjustment window for the values ​​of the slice requirements used for slice allocation.

[0059] Action 404. Control node 15 further sends a second instruction to VAL server 14, wherein the second instruction specifies the identified and / or applied alternative slice request and / or slice adjustment request. Therefore, if the endpoint is provided by VAL server 14, control node 15 can send the result of the network slice allocation as a notification message to VAL server 14; otherwise, a response message can be used. The response message may include a failed slice request indication, indicating that the adjustment / request / network slice cannot be allocated by control node 15. This second instruction, indicating, for example, a rejection of providing failed network slice allocation information to VAL server 14, helps VAL server 14 understand which / which network slices were allocated and failed. This helps VAL server 14 maintain telemetry, analyze and understand the experience of VAL users, and / or evaluate network slice service provider SLA or KPI values. Delivering the slice allocation response (as a notification) in a separate session enables control node 15 to create scalable slice allocations.

[0060] Figure 5 illustrates an example of a method performed by VAL server 14 for processing services in wireless communication network 1 according to embodiments herein.

[0061] Action 501. VAL server 14 sends an instruction to control node 15, wherein the instruction specifies one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements associated with the network slices. For example, VAL server 14 may provide a request with an instruction specifying one or more of the following: a priority 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 the scalable slice allocation process. The alternative slice requirements and / or adjustment requirements in the request may include a range of one or more values ​​for adjusting the requirements used for slice allocation, and / or an adjustment expiration time for a time window for adjusting the values ​​used for slice allocation.

[0062] Action 502. VAL server 14 receives a second instruction from control node 15, wherein the second instruction indicates a decision related to slice service provision at control node 15. The second instruction may be an instruction to determine and / or apply alternative slice requirements and / or slice adjustment requirements. The second instruction may include failure indications and / or information related to the allocation of network slices.

[0063] Figure 6 illustrates an example of a method for processing services in a wireless communication network 1, performed by a control node 15 (such as an NSCE server) according to embodiments herein.

[0064] Action 601. Control node 15 receives an instruction from VAL server 14, wherein the instruction specifies one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements associated with the network slices. The instruction may indicate one or more of the following: a priority 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 the scalable slice allocation process. The alternative slice requirements and / or adjustment requirements in the request may include a range of one or more values ​​for adjusting the requirements used for slice allocation, and / or an adjustment expiration time for providing a time window for adjusting the values ​​used for slice allocation.

[0065] Action 602. Control node 15 performs decisions related to the provision of slice services based on instructions. For example, control node 15 may determine whether to provide network slice services to VAL server 14 and / or apply alternative slice requests and / or one or more slice adjustment requests.

[0066] Action 603. Control node 15 sends a second instruction to VAL server 14, wherein the second instruction is related to the decision performed. The second instruction may indicate the determination and / or application of alternative slice requirements and / or slice adjustment requirements. The second instruction may include failure indications and / or information related to the allocation of network slices.

[0067] It should be noted that the current process described in Clause 9.18.2.1 of TS 23.435 v.18.0.0 allocates slices to VAL server 14 but does not provide a list of failed network slice information. Control node 15 may not meet all slice requirements described by VAL server 14. Therefore, it may be necessary to update VAL server 14 for failed network slice information. VAL server 14 can provide more than one slice for allocation, and some slices may be allocated first due to KPI or SLA reasons. For example, slice allocation may be for a gold user of VAL server 14, but there is currently no preferred way to indicate which slice should be created first. During allocation, it is possible that slice requirements are not exactly met, and this may lead to slice allocation failure. Slice adjustment requirements and alternative slice requirements provide VAL server 14 with the opportunity to indicate slice requirement adjustments to control node 15 during slice allocation. The current request-response model is insufficient for configuring more than one network slice or a large number of network slices. When VAL server 14 requests multiple slice allocations, existing process request message sessions may time out due to waiting for responses, as slice allocation involves configuring and interacting with other network entities. Embodiments herein may request VAL server 14 to provide a notification endpoint to send notifications of network slice information for an scalable slice allocation process. Priorities may be added to the indication for allocating slices in the case of more than one slice, and / or to slice adjustments to allow network slices to be allocated within an acceptable adjustment window. Embodiments herein may add separate notification messages (such as a second indication) to notify of slice allocation responses, and these notification messages may also notify VAL server 14 of failed network slice allocations.

[0068] The embodiments described herein enable VAL server 14 to indicate the priority of slice allocation for its users, alternative slice requests, and / or slice adjustment requests. Furthermore, VAL server 14 can be aware of failed slice information and can provide alternative requests for slice allocation.

[0069] Based on some embodiments described herein, some exemplary changes in TS 23.435 v.18.0.0 are underlined below:

[0070] 9.18.2 Process

[0071] 9.18.2.1 Network Slice Allocation in the NSaaS Model

[0072] This sub-clause describes the process of network slice allocation in the NSaaS model, where the VAL server interacts with the 5GS via the NSCE server when a network slice needs to be allocated.

[0073] Figure 7: Network slice allocation in the NSaaS model

[0074] 71. The VAL server makes a request to order network slices. The VAL server specifies the network slice requirements for the VAL service. The network slice requirements at the VAL server can be specified using the GST attribute (which results in NEST) as specified in GSMA NG.116.

[0075] 72. The VAL server requests network slice allocation with network slicing requirements. The network slice allocation request includes the VAL service ID, a list of VAL UE IDs, and S-NSSAI. The VAL server prioritizes the list of slice identifiers for allocation. The VAL server also provides an endpoint for receiving notifications.

[0076] 73. The NSCE server performs network slice allocation. If the NSCE server acts as an NSaaS provider and the existing allocated network slices meet the network slice requirements, the NSCE server allocates the existing network slices to VAL. Otherwise, the NSCE server acts as a network slice provider Mns consumer to request the “AllocacatedNsi” operation as specified in 3GPP TS 28.531 [8]. If the VAL server provides a slice resizing request, the NSCE server uses the slice resizing request. This is used for slice allocation.

[0077] When the “AllocatedNsi” operation is received, the network slice provides the MnS producer with the ability to perform the billing mechanism as specified in 3GPP TS28.202

[28] .

[0078] The NSCE server executes instructions to the 5GS for URSP determination of the AF driver according to VAL UE.

[0079] Note 1: Depending on the network operator's policy, the NSCE server acting as the AF can send the created network slice information to the PCF via the NEF as part of the guidance for the AF drive used for URSP determination in the 5G system (as specified in TS 23.501

[16] ). This guidance can create new routing parameters to indicate the PDU session information set (DNN, S-NSSAI) that can be associated with the application matching the application service.

[0080] If the endpoint is provided by a VAL server The NSCE server will then assign the network slices as follows. As a notification message Send to the VAL server (see Action 76); Otherwise, use a response message. (See Action 74). The response includes that it cannot be made by NSCE Failed slice allocation request from the server.

[0081] Optionally, the VAL server may include alternative slice requirements and slice requirement adjustments in the request. The adjustment scope extends to... The NSCE server provides a range of values ​​for adjusting slice requirements used for slice allocation. The adjustment expiration time provides the adjustment period for slice allocation. The time window for the slice allocation's required values.

[0082] 75. If the NSCE server does not perform the instruction to the AF driver for URSP determination to the 5GS in step 3, then, in the event of successful network slice allocation, the NSCE server, based on the VAL UE ID list from step 2, uses the procedures defined in steps 2-4 of 9.17.2.2 to pass the network slice allocation information to the VAL UE's NSCE client. The network slice allocation information includes the VAL service ID, S-NSSAI, and DNN.

[0083] Note 2: If the UE is provided with URSP rules by the network operator, the UE processes the network slice information transmitted via the NSCE layer with priority between the network slice information and the URSP rules as defined in Clause 6.1.2.2.1 of 3GPP TS 23.503

[17] . How the UE uses the network slice information transmitted via the NSCE layer relative to the URSP depends on the implementation.

[0084] 9.18.3 Information Flow

[0085] 9.18.3.1 Overview

[0086] The following information flow is specified for network slice allocation:

[0087] - Network slice allocation requests and responses.

[0088] 9.18.3.2 Network Slice Allocation

[0089] Tables 9.18.3.2-1 and 9.18.3.2-2 describe the information elements used for network slice allocation requests and responses between the VAL server and the NSCE server.

[0090] Table 9.18.3.2-1: Network Slice Allocation Request

[0091]

[0092] Table 9.18.3.2-2: Network Slice Allocation Response

[0093]

[0094] Table 9.18.3.2-3: Network Slice Allocation Notification

[0095]

[0096] Figure 8 illustrates an embodiment of a VAL server 14 for processing services in a wireless communication network according to embodiments herein.

[0097] VAL server 14 may include processing circuitry 801, such as one or more processors, configured to perform the methods described herein.

[0098] VAL server 14 and / or processing circuitry 801 are configured to send an instruction to control node 15, wherein the instruction specifies one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements associated with the network slices. For example, VAL server 14 and / or processing circuitry 801 may be configured to provide a request with an instruction specifying one or more of the following: a preferred 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 the scalable slice allocation process.

[0099] VAL server 14 and / or processing circuitry 801 are configured to receive a second instruction from control node 15, wherein the second instruction indicates a decision related to slice service provision at control node 15. The second instruction may be an instruction to determine and / or apply alternative slice requirements and / or slice adjustment requirements. The second instruction may include failure indications and / or information related to network slice allocation. Therefore, VAL server 14 can be aware of failed slice information and can provide alternative requirements for slice allocation.

[0100] The methods for a VAL server 14 according to the embodiments described herein are implemented using, for example, a computer program product 807 or a computer program including instructions (i.e., software code portions) that, when executed on at least one processor, cause at least one processor to perform 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, such as a disk, a Universal Serial Bus (USB) stick, or the like. The computer-readable storage medium 808 on which the computer program product is stored may include instructions that, when executed on at least one processor, cause at least one processor to perform the actions described herein as performed by the VAL server 14. In some embodiments, the computer-readable storage medium may be a transient or non-transitory computer-readable storage medium. Therefore, the embodiments herein may disclose a VAL server 14 for processing communications in a wireless communication network, wherein the VAL server 14 includes processing circuitry and a memory including instructions executable by the processing circuitry, thereby enabling the VAL server 14 to operate to perform any of the methods described herein.

[0101] Figure 9 illustrates an embodiment of a control node 15 (such as an NSCE server) for processing services in a wireless communication network according to embodiments herein.

[0102] Control node 15 may include processing circuitry 901, such as one or more processors, configured to execute the methods described herein.

[0103] Control node 15 and / or processing circuitry 901 are configured to receive instructions from VAL server 14, wherein the instructions specify one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements associated with the network slices.

[0104] Control node 15 and / or processing circuitry 901 are configured to perform decisions related to the provision of slicing services based on indications. For example, control node 15 and / or processing circuitry 901 may be configured to determine whether to provide network slicing services to VAL server 14 and / or apply alternative slicing requests and / or one or more slicing adjustment requests.

[0105] Control node 15 and / or processing circuitry 901 are configured to send a second instruction to VAL server 14, wherein the second instruction is related to the decision being performed. The second instruction may indicate the determination and / or application of alternative slice requirements and / or slice adjustment requirements.

[0106] Control node 15 also includes memory 905. Memory 905 includes one or more units for storing data such as indications, mappings, second indications, network slice information, thresholds, node-related data, and applications that, when executed, perform the methods disclosed herein. Furthermore, control node 15 may include a communication interface 906, such as including a transmitter, receiver, transceiver, and / or one or more antennas (such as an antenna array).

[0107] The methods for controlling node 15 according to the embodiments described herein are implemented using, for example, a computer program product 907 or a computer program including instructions (i.e., software code portions) that, when executed on at least one processor, cause at least one processor to perform the actions described herein as performed by control node 15. The computer program product 907 may be stored on a computer-readable storage medium 908, such as a disk, USB stick, or the like. The computer-readable storage medium 908 on which the computer program product is stored may include instructions that, when executed on at least one processor, cause at least one processor to perform the actions described herein as performed by control node 15. In some embodiments, the computer-readable storage medium may be a transient or non-transitory computer-readable storage medium. Therefore, the embodiments herein may disclose a control node 15 for processing communications in a wireless communication network, wherein the control node 15 includes processing circuitry and a memory including instructions executable by the processing circuitry, thereby enabling the control node 15 to operate to perform any of the methods herein.

[0108] In some embodiments, the more general term "network node" is used, and it can correspond to any type of radio network node or any network node that communicates with the UE and / or with another network node. Examples of network nodes are NodeB, primary eNB, secondary eNB, network nodes belonging to the primary cell group (MCG) or secondary cell group (SCG), base station (BS), multi-standard radio (MSR) radio nodes (such as MSR BS), eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node of control relay, base transceiver station (BTS), access point (AP), transmission point, transmission node, remote radio unit (RRU), remote radio head (RRH), nodes in distributed antenna system (DAS), etc.

[0109] In some embodiments, the non-limiting term wireless device or UE is used, and it refers to any type of wireless device that communicates with network nodes and / or with another wireless device in a cellular or mobile communication system. Examples of UEs are devices with IoT capabilities, target devices, device-to-device (D2D) UEs, proximity-aware UEs (also known as ProSe UEs), machine-type UEs or UEs capable of machine-to-machine (M2M) communication, tablets, mobile terminals, smartphones, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), USB dongles, etc.

[0110] The embodiments are applicable to any RAT system or multi-RAT system, in which wireless devices receive and / or transmit signals (e.g., data), such as 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 GSM Evolution (GSM / EDGE), Global Microwave Access Interoperability (WiMax), or Ultra Mobile Broadband (UMB), to name just a few possible implementations.

[0111] As will be readily understood by those skilled in communication design, functional devices or circuits can 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 can be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices having appropriate hardware and / or software interfaces between them. For example, several functions can be implemented on a processor shared with other functional components of a wireless device or network node.

[0112] Alternatively, some functional elements in the processing apparatus discussed may be provided using dedicated hardware, while other functional elements may be provided using hardware for executing software, in association with appropriate software or firmware. Therefore, the terms "processor" or "controller" as used herein do not specifically refer to hardware capable of executing software and may implicitly include, but are not limited to, digital signal processor (DSP) hardware and / or program or application data. Other conventional or custom hardware may also be included. Designers of communication equipment will understand the inherent cost, performance, and maintenance trade-offs in these design choices.

[0113] While the computing devices described herein (e.g., UE, network node, host) may include combinations of the hardware components shown, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, and other operations described herein may be performed by processing circuitry that processes information by, for example, converting acquired information into other information, comparing the acquired or converted information with information stored in a network node, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing. Furthermore, although components are depicted as single boxes within a larger box or nested within multiple boxes, in practice, a computing device may include multiple different physical components constituting a single illustrated component, and functionality may be partitioned between individual components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of a component may be partitioned between the processing circuitry and the communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0114] In some embodiments, some or all of the functions described herein may be provided by processing circuitry that executes instructions stored in memory, which in some 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 functions may be provided by processing circuitry that does not execute instructions stored on a separate or discrete device-readable medium, such as in a hard-wired manner. In any of these particular embodiments, the processing circuitry may be configured to perform the described functions regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited solely to other components of the processing circuitry, but are enjoyed in general by the computing device and / or typically by the end user and wireless network.

[0115] It should be understood that the foregoing description and figures represent non-limiting examples of the methods and apparatus taught herein. Therefore, the apparatuses and techniques taught herein are not limited to the foregoing description and figures. Rather, the embodiments herein are limited only by the following claims and their legal equivalents.

Claims

1. A method for processing services in a wireless communication network (1) executed by a vertical application layer VAL server (14), the method comprising: - Send (501) an instruction to the control node (15), wherein the instruction indicates one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements related to the network slices; and - Receive (502) a second instruction from the control node (15), wherein the second instruction indicates a decision related to the provision of slice services at the control node (15).

2. The method according to claim 1, wherein, Sending the instruction includes: providing a request with the instruction, wherein the instruction specifies one or more of the following: a priority list of one or more network slices, one or more alternative slice requests, one or more slice adjustment requests, and / or a notification endpoint for the scalable slice allocation process.

3. The method according to any one of claims 1 to 2, wherein, The alternative slice requirements and / or adjustment requirements include: adjusting the range of one or more values ​​of the requirements for slice allocation, and / or providing an adjustment expiration time for a time window of the time window for adjusting the values ​​of the requirements for slice allocation.

4. The method according to any one of claims 1 to 3, wherein, The second instruction is an instruction to determine and / or apply alternative slice requirements and / or slice adjustment requirements.

5. The method according to any one of claims 1 to 4, wherein, The second indication includes a failure indication.

6. A method for processing services in a wireless communication network 1, performed by a control node (15), the method comprising: - Receive (601) an instruction from the vertical application layer VAL server (14), wherein the instruction specifies one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements related to the network slices; - Based on the instruction, perform (602) a decision related to the provision of slice services; and - Send (603) a second instruction to the VAL server (14), wherein the second instruction is related to the decision performed.

7. The method according to claim 6, wherein, Performing the decision includes determining whether to provide the network slicing service to the VAL server (14) and / or apply the alternative slice request and / or one or more slice adjustment requests.

8. The method according to any one of claims 6 to 7, wherein, Receiving the instruction includes: obtaining a request having the instruction, wherein the instruction specifies one or more of the following: a priority list of one or more network slices, one or more alternative slice requests, one or more slice adjustment requests, and / or a notification endpoint for a scalable slice allocation process.

9. The method according to any one of claims 6 to 8, wherein, The alternative slice requirements and / or adjustment requirements include: adjusting the range of one or more values ​​of the requirements for slice allocation, and / or providing an adjustment expiration time for a time window of the time window for adjusting the values ​​of the requirements for slice allocation.

10. The method according to any one of claims 6 to 9, wherein, The second instruction is an instruction to determine and / or apply alternative slice requirements and / or slice adjustment requirements.

11. The method according to any one of claims 6 to 10, wherein, The second indication includes a failure indication.

12. A vertical application service VAL server (14) for processing services in a wireless communication network (1), wherein, The VAL server (14) is configured to: send an instruction to the control node (15), wherein the instruction indicates one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements related to the network slices; and receive a second instruction from the control node (15), wherein the second instruction indicates a decision related to slice service provision at the control node (15).

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

14. A control node (15) for processing services in a wireless communication network (1), wherein, The control node is configured to: receive an instruction from a vertical application layer VAL server (14), wherein the instruction specifies one or more network slices to be used, and / or alternative slice requirements and / or adjustment requirements related to the network slices; perform a decision related to slice service provision based on the instruction; and send a second instruction to the VAL server (14), wherein the second instruction is related to the decision performed.

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

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

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

Images