WO2024017489A1

WO2024017489A1 - Location based multi-quality of service (multi-qos) slicing

Info

Publication number: WO2024017489A1
Application number: PCT/EP2022/077861
Authority: WO
Inventors: Stephen Terrill; Massimiliano Maggiari
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-07-22
Filing date: 2022-10-06
Publication date: 2024-01-25

Abstract

A method, system and apparatus are disclosed. A management node is provided. The management node is configured to determine a composite quality of service, QOS, profile including a plurality of basic QOS profiles associated with corresponding differential service areas, determine a first differential service area associated with a first network node, determine a first basic QOS profile of the plurality of basic QOS profile associated with the first differential service area, determine a first QOS configuration for the network node based on the first basic QOS profile, and transmit the first QOS configuration to the first network node to cause the first network node to perform at least one network node function in accordance with the first QOS configuration.

Description

LOCATION BASED MULTI-QUALITY OF SERVICE (MULTI-QOS)

SLICING

TECHNICAL FIELD

The present disclosure relates to wireless communications, and in particular, to location-based multi-quality-of-service (QOS) slicing.

BACKGROUND

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

Network slicing ("slicing") is a 4G and 5G feature in which the network may be “sliced” to fulfill the different requirements imposed by different services and use cases. The different service requirements may be expressed in several areas, such as access location, needed throughput, isolation level, availability, quality of service (QOS), etc. Existing systems have considered slicing as a way of prioritizing different traffic which is consistent with net neutrality laws. For example, network slicing may refer to creating logically separated partitions of the network, which may also be referred to as slices or network slices, which may be for addressing different business purposes. These network slices may be logically separated to a degree that they can be regarded and managed as networks of their own. For example, network slicing may utilize virtualization technology (e.g., Software Defined Networking (SDN) and Network Functions Virtualization (NFV)) to allow multiple virtual (i.e., logical) networks to be created on top of a common shared physical infrastructure. These virtual networks may be referred to as network slices. The network slices may then be customized to meet needs of different use cases. Network slices may differ for supported features and network functions optimizations. The operator may deploy multiple network slice instances delivering exactly the same features but for different groups of WDs, e.g. as they deliver a different committed service and/or because they may be dedicated to a customer. A single WD can simultaneously be served by one or more network slice instances.

QOS configuration may determine how packets representing specific services inside the slices are prioritized with respect to each other, so that the right service priority differentiation may be implemented (i.e., certain services may be higher priority than other services).

During slices design and configuration, the service requirements may be translated into specific QOS characteristics to be configured in the various network domains implementing the slice, e.g., Radio Access Network, Packet Core, and Transport.

In the Radio Access Network and Packet Core domain, the QOS configuration may be a combination of 5QI tables and packet scheduling priorities (5QI = 5G QOS Identifier). In the Transport domain, the QOS configuration may be a combination of packet scheduling priority and dedicated resource allocation. In the RAN domain, the interpretation of the 5 QI values may be set per slice.

Existing systems may define a number of slice characteristics used as input in the slice creation process, and may define an area of service where the slice should be available if it is not available across the entire network.

In existing systems, QOS configuration may need to be coordinated across the different domains. This is typically achieved through the centralized Operations and Support Systems (OSS). OSS systems are designed to ensure that the QOS is consistently configured in the Radio Access area from where the slice will be consumed, that the QOS is consistently configured across RAN and Packet Core with the same 5QI values, and that the QOS is properly configured in the Transport domain with a mapping between the 5QI priorities and the DCSP transport configuration. Failing to provide a consistent configuration may result in errors in handling the packets carried by the slices not fulfilling the agreed service quality (SLA).

SUMMARY

Some embodiments advantageously provide methods, systems, and apparatuses for location-based multi-QOS slicing. Existing systems may suffer one or more of the following problems:

Existing systems may require complex QOS provisioning mechanism without any QOS profile OSS support

Existing systems may only support a single QOS configuration per slice without location-based priority differentiation, i.e., resulting in equal treatment for all cells in the network irrespective of the location.

Existing systems may define a number of slice attributes which are input to network planning and orchestration.

Further, in existing systems, the area of differential treatment may be the same as the area of service for the slice and is missing a way to describe a slice can be accessed across a broader area (such as the entire network) while only having specialized treatment in certain arears (such as stadium, enterprises, malls, etc.).

As input to orchestration, existing systems define an area of service where the slice should be available. This may be insufficient to cover the case where the slice is available to the entire network, however the differential treatment for the slice should only be available in certain areas.

According to one aspect of the present disclosure, a management node configured to communicate with a first network node is provided. The management node includes processing circuitry configured to determine a composite quality of service, QOS, profile, where the composite QOS profile includes a plurality of basic QOS profiles, and where a basic QOS profile of the plurality of QOS profiles is associated with a corresponding differential service area. The processing circuitry is further configured to determine a first differential service area associated with the first network node. The processing circuitry is further configured to determine a first basic QOS profile of the plurality of basic QOS profile, where the first basic QOS profile is associated with the first differential service area. The processing circuitry is further configured to determine a first QOS configuration for the network node based on the first basic QOS profile, where the QOS configuration is configured to cause the network node to perform at least one network node function in accordance with the first QOS configuration. The processing circuitry is further configured to cause a transmission of the first QOS configuration to the first network node. According to another aspect of the present disclosure, a method implemented in a management node configured to communicate with a first network node is provided. A composite quality of service, QOS, profile is determined, where the composite QOS profile includes a plurality of basic QOS profiles, and where a basic QOS profile of the plurality of QOS profiles is associated with a corresponding differential service area. A first differential service area associated with the first network node is determined. A first basic QOS profile of the plurality of basic QOS profile is determined, where the first basic QOS profile is associated with the first differential service area. A first QOS configuration for the network node is determined based on the first basic QOS profile. The first QOS configuration is transmitted to the first network node, where the first QOS configuration is configured to cause the first network node to perform at least one network node function in accordance with the first QOS configuration

According to another aspect of the present disclosure, a network node configured to communicate with a management node, the network node being associated with a first differential service area is provided. The network node includes processing circuitry configured to receive a QOS configuration from the management node, where the QOS configuration is based on a first basic QOS profile that is associated with the first differential service area and a composite quality of service, QOS, profile, and where the composite QOS profile is associated with a plurality of basic QOS profiles. A basic QOS profile of the plurality of basic QOS profiles is associated with a corresponding differential service area. The processing circuitry is further configured to perform at least one network node function in accordance with the QOS configuration.

According to another aspect of the present disclosure, a method implemented in a network node configured to communicate with a management node is provided. The network node is associated with a first differential service area. A QOS configuration is received from the management node, where the QOS configuration is based on a first basic QOS profile that is associated with the first differential service area and a composite quality of service, QOS, profile, and where the composite QOS profile is associated with a plurality of basic QOS profiles. A basic QOS profile of the plurality of basic QOS profiles is associated with a corresponding differential service area. At least one network node function is performed in accordance with the QOS configuration.

BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

FIG. 6 is a flowchart illustrating example methods implemented in a communication system including a host computer, a network node and a wireless device for receiving user data at a host computer according to some embodiments of the present disclosure; FIG. 7 is a flowchart of an example process in a management node for location-based multi-QOS slicing according to some embodiments of the present disclosure;

FIG. 8 is a flowchart of an example process in a wireless device for locationbased multi-QOS slicing according to some embodiments of the present disclosure;

FIG. 9 is a schematic diagram of an example network architecture according to some embodiments of the present disclosure;

FIG. 10 is a schematic view of another example network architecture according to some embodiments of the present disclosure;

FIG. 11 is a schematic view of another example network architecture according to some embodiments of the present disclosure;

FIG. 12 is a class diagram of QOS profiles according to some embodiments of the present disclosure;

FIG. 13 is another class diagram of QOS profiles according to some embodiments of the present disclosure; and

FIG. 14 is a block diagram of an operations support system (OSS) unit according to some embodiments of the present disclosure.

DETAILED DESCRIPTION

Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to location-based multi-QOS slicing. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Like numbers refer to like elements throughout the description.

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

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

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

The term “network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node. The term “management node” used herein can refer to any kind of network entity, such as a node implementing one or more management node functions, a network node implementing one or more management node functions, a cloud-based entity (e.g., a server, host computer, etc.) implementing one or more management node functions, etc. A management node may refer to an operations support systems (OSS) node, a service character node, a slice orchestrator node, such as a Network Slice Management Function (NSMF), Network Slice Subnet Management Function (NSSMF) as described by 3GPP, or Service Management and Orchestration (SMO) as described by ORAN Alliance or Open Network Automation Platform (ONAP), etc.

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

Also, in some embodiments the generic term “radio network node” is used. It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB node, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

In some embodiments, the term “differential service area” is used. It can be any type of area or grouping, such as grouping(s) of cells/network nodes based on physical locations, geographic areas, hardware/software capabilities, associated network providers/customers/users/etc., premises/types of premises (e.g., medical/hospital premises, sports stadiums, corporate campuses, etc.), tracking area codes (“TAC”), etc ), in which a particular network slice and/or quality of service (QOS) configuration may be treated/interpreted differently from differential service area to differential service area. For example, a differential service area may be a group of one or more cells and/or network nodes, the group being associated with, e.g., a geographic area/premises/etc., in which a network slice and/or QOS configuration/profile/etc. may be treated/interpreted differently in the first differential service area as compared to other differential service areas. As an example, a network node/wireless device/etc. may be configured with a first network slice and/or QOS profile/configuration/setting/index/parameter set/etc. in a wireless communication network including a plurality of differential service areas, such as a first differential service area and a second differential service area. The network (i.e. , the network node, core node, management node, etc.) treats/interprets the first network slice and/or QOS profile/configuration/setting/index/parameter set/etc. according to a first interpretation/meaning in the first differential service area, and according to a second interpretation/meaning in the second differential service area. A “first interpretation”/ “first meaning” may cause, for example, a wireless device/network node/etc. in the first differential service area to be configured (e.g., by a core node/management node/network node/etc.) with a first configuration including one or more parameters/settings (e.g., power settings, data throughput/latency settings, traffic priority settings, beamforming settings, etc.), which may differ from the “second interpretation”/“second meaning” according to one or more parameters/settings. Thus, a wireless device configured with a first network slice and/or QOS profile/ configuration may receive a first quality of service treatment in a first cell of the first differential service area, and may receive a second quality of service treatment in a second cell of the second differential service area.

Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure. Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.

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

Some embodiments provide location-based multi-QOS slicing.

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

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

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

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

A network node 16 is configured to include a QOS implementation unit 32 which is configured to perform one or more network node 16 functions as described herein such as, for example, receiving a QOS configuration from the management node 15 and performing at least one network function in accordance with the QOS configuration. A management node 15 is configured to include an Operations Support Systems (OSS) unit 34 which is configured to perform one or more management node 15 functions as described herein such as, for example, determining a composite QOS profile, determining a first differential service area associated with the network node 16, determine a first basic QOS profile of the plurality of basic QOS profile associated with the first differential service area, determining a QOS configuration for the network node 16 based on the first basic QOS profile, and to causing a transmission of the QOS configuration to the network node 16.

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

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

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

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

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

Thus, the network node 16 further has software 74 stored internally in, for example, memory 72, or stored in external memory (e g., database, storage array, network storage device, etc.) accessible by the network node 1 via an external connection. The software 74 may be executable by the processing circuitry 68. The processing circuitry 68 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e g., by network node 16. Processor 70 corresponds to one or more processors 70 for performing network node 16 functions described herein. The memory 72 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and/or processing circuitry 68, causes the processor 70 and/or processing circuitry 68 to perform the processes described herein with respect to network node 16. For example, processing circuitry 68 of the network node 16 may include QOS implementation unit 32 configured to perform one or more network node 16 functions as described herein such as, for example, receiving a QOS configuration from the management node 15 and performing at least one network function in accordance with the QOS configuration.

The communication system 10 further includes the management node 15 already referred to. The management node 15 may have hardware 80 that may include a communication interface 82 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10. Communication interface 82 may be configured to facilitate a connection 64 to the network node 16. The connection 64 may be direct or it may pass through a core network 14 of the communication system 10 and/or through one or more intermediate networks 30 outside the communication system 10.

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

Thus, the management node 15 may further comprise software 90, which is stored in, for example, memory 88 at the management node 15, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the management node 15. The software 90 may be executable by the processing circuitry 84. The software 90 may include a client application 92. The client application 92 may be operable to provide a service to a human or non-human user via the management node 15, with the support of the host computer 24. In the host computer 24, an executing host application 50 may communicate with the executing client application 92 via the OTT connection 52 terminating at the management node 15 and the host computer 24. In providing the service to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transfer both the request data and the user data. The client application 92 may interact with the user to generate the user data that it provides. For example, the client application 92 may interact with the user to receive configuration information related to QOS profiles, differential service areas, mappings of services/QOS slices/profiles/etc. to index values, etc.

The processing circuitry 84 may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by management node 15. The processor 86 corresponds to one or more processors 86 for performing management node 15 functions described herein. The management node 15 includes memory 88 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 90 and/or the client application 92 may include instructions that, when executed by the processor 86 and/or processing circuitry 84, causes the processor 86 and/or processing circuitry 84 to perform the processes described herein with respect to management node 15. For example, the processing circuitry 84 of the management node 15 may include a OSS unit 34 configured to perform one or more management node 15 functions as described herein such as, for example, determining a composite QOS profile, determine a first differential service area associated with the network node 16, determining a first basic QOS profile of the plurality of basic QOS profile associated with the first differential service area, determining a QOS configuration for the network node 16 based on the first basic QOS profile, and to causing a transmission of the QOS configuration to the network node 16.

In some embodiments the first differential service area could also be a part of the area covered by a network node (e g., some cells on the same gNodeB). In these embodiments, however, it is a network node that receives the configuration request for both the differentiated area and non-differentiated area.

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

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

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

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

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

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

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

FIG. 3 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIGS. 1 and 2, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16, a management node 15, and a WD 22, which may be those described with reference to FIG. 2. In a first step of the method, the host computer 24 provides user data (Block SI 00). In an optional substep of the first step, the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50 (Block SI 02). In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 04). In an optional third step, the network node 16 transmits to the WD 22 the user data which was carried in the transmission that the host computer 24 initiated, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 06). In an optional fourth step, the WD 22 executes a client application, such as, for example, the client application 92, associated with the host application 50 executed by the host computer 24 (Block SI 08).

FIG. 4 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment. The communication system may include a host computer 24, a network node 16, a management node 15, and a WD 22, which may be those described with reference to FIGS. 1 and 2. In a first step of the method, the host computer 24 provides user data (Block S 110). In an optional substep (not shown) the host computer 24 provides the user data by executing a host application, such as, for example, the host application 50. In a second step, the host computer 24 initiates a transmission carrying the user data to the WD 22 (Block SI 12). The transmission may pass via the network node 16, in accordance with the teachings of the embodiments described throughout this disclosure. In an optional third step, the WD 22 receives the user data carried in the transmission (Block SI 14). FIG. 5 is a flowchart illustrating an exemplary method implemented in a communication system, such as, for example, the communication system of FIG. 1, in accordance with one embodiment. The communication system may include a host computer 24, a management node 15, a network node 16 and a WD 22, which may be those described with reference to FIGS. 1 and 2. In an optional first step of the method, the WD 22 receives input data provided by the host computer 24 (Block SI 16). In an optional substep of the first step, the WD 22 executes the client application 92, which provides the user data in reaction to the received input data provided by the host computer 24 (Block S 118). Additionally or alternatively, in an optional second step, the WD 22 provides user data (Block SI 20). In an optional substep of the second step, the WD provides the user data by executing a client application, such as, for example, client application 92 (Block SI 22). In providing the user data, the executed client application 92 may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the WD 22 may initiate, in an optional third substep, transmission of the user data to the host computer 24 (Block S124). In a fourth step of the method, the host computer 24 receives the user data transmitted from the WD 22, in accordance with the teachings of the embodiments described throughout this disclosure (Block SI 26).

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

FIG. 7 is a flowchart of an exemplary process in a management node 15 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of management node such as by one or more of processing circuitry 84 (including the OSS unit 34), processor 86, communication interface 82, and/or memory 88. The management node 15 is configured to determine (Block SI 34) a composite quality of service, QOS, profile, where the composite QOS profile includes a plurality of basic QOS profiles, and where a basic QOS profile of the plurality of QOS profiles is associated with a corresponding differential service area. The management node 15 is configured to determine (Block S136) a first differential service area associated with a first network node 16. The management node 15 is configured to determine (Block S138) a first basic QOS profile of the plurality of basic QOS profile, where the first basic QOS profile is associated with the first differential service area. The management node 15 is configured to determine (Block SI 40) a first QOS configuration for the first network node based on the first basic QOS profile, where the first QOS configuration is configured to cause the first network node to perform at least one network node function in accordance with the first QOS configuration. The management node 15 is configured to transmit (Block SI 42) the first QOS configuration to the first network node.

In one or more embodiments, the first QOS configuration includes and/or indicates: at least one index value; and a mapping of the at least one index value to a corresponding QOS parameter set. In one or more embodiments, at least one of the at least one index value is a 5G QOS Identifier, 5QI, value. In one or more embodiments, a corresponding QOS parameter set includes at least one of: a resource type, the resource type being one of: a guaranteed bit rate, GBR, resource type, and a non-GBR resource type; a priority level; a packet delay budget; a packet error rate; a default averaging window; a domain priority level; a relative priority; and a radio link control, RLC, mode. In one or more embodiments, the first differential service area is determined based on at least one of: a cell associated with the first network node 16, a tracking area code, TAC, associated with the first network node 16, and a geographic area associated with the first network node 16. Note that in some embodiments one node may only cover part of the cells in an area. In these embodiments it is possible to input into the management system data defining a geographic area and the management system then converts this information into data format that the network nodes understand and can process as explained in embodiments disclosed here. In one or more embodiments, the composite QOS configuration profile is associated with a network slice. In one or more embodiments, the management node is at least one of: an Operations Support Systems, OSS, node; a service orchestrator node; and a slice orchestrator node. In one or more embodiments, the management node is pre-configured with at least one of: a meaning of an index value for the network node (16) for a plurality of different services, a meaning of an index value for a plurality of differential service areas, a service having a first meaning in one of the plurality of differential service areas and having a second meaning in another of the plurality of differential service areas, and a plurality of index values for a plurality of services for the first network node (16) in the first differential service area associated with the first network node (16).

In one or more embodiments, the management node 15 processing circuitry 84 is further configured to determine a second differential service area associated with a second network node 16, determine a second basic QOS profile of the plurality of basic QOS profiles, where the second basic QOS profile is associated with the second differential service area, determine a second QOS configuration for the second network node 16 based on the second basic QOS profile, where the second QOS configuration is configured to cause the second network node 16 to perform at least one network node 16 function in accordance with the second QOS configuration, and cause transmission of the second QOS configuration to the second network node 16. In one or more embodiments, the second QOS configuration differs from the first QOS configuration by at least one of: a resource type, the resource type being one of: a guaranteed bit rate, GBR, resource type, and a non-GBR resource type; a priority level; a packet delay budget; a packet error rate; a default averaging window; a domain priority level; a relative priority; and a radio link control, RLC, mode. In one or more embodiments, the first basic QOS profile is associated with at least one of: a profile name; and a location, the location being derived by a location aware topology manager. In one or more embodiments, the determining (Block SI 38) of the first basic QOS profile associated with the first differential service area includes: determining a location associated with the first differential service area; and identifying, among the plurality of basic QOS profiles of the composite QOS profile, the first QOS profile having the same location as the location associated with the first differential service area. In one or more embodiments, the determining (Block SI 40) of the first QOS configuration for the first network node 16 based on the first basic QOS profile includes modifying at least one parameter, the at least one parameter including at least one of: a resource type, the resource type being one of: a guaranteed bit rate, GBR, resource type, and a non-GBR resource type; a priority level; a packet delay budget; a packet error rate; a default averaging window; a domain priority level; a relative priority; and a radio link control, RLC, mode.

FIG. 8 is a flowchart of an exemplary process in a network node 16 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 68 (including the QOS implementation unit 32), processor 70, radio interface 62 and/or communication interface 60. The network node 16 is configured to receive (Block S144) a QOS configuration from the management node, where the QOS configuration is based on a first basic QOS profile that is associated with the first differential service area and a composite quality of service, QOS, profile, where the composite QOS profile is associated with a plurality of basic QOS profiles, and where a basic QOS profile of the plurality of basic QOS profiles is associated with a corresponding differential service area. The network node 16 is configured to perform (Block SI 46) at least one network node function in accordance with the QOS configuration.

In one or more embodiments, the QOS configuration includes and/or indicates: at least one index value; and a mapping of the at least one index value to a corresponding QOS parameter set. In one or more embodiments, at least one of the at least one index value is a 5G QOS Identifier, 5QI, value. In one or more embodiments, a corresponding QOS parameter set includes at least one of: a resource type, the resource type being one of: a guaranteed bit rate, GBR, resource type, and a non-GBR resource type; a priority level; a packet delay budget; a packet error rate; a default averaging window; a domain priority level; a relative priority; and a radio link control, RLC, mode. In one or more embodiments, the first differential service area is determined based on at least one of: a cell associated with the network node, a tracking area code, TAC, associated with the network node, and a geographic area associated with the network node In one or more embodiments, In one or more embodiments, the composite QOS configuration profile is associated with a network slice. In one or more embodiments, the network node is at least one of: an Operations Support Systems, OSS, node; a service orchestrator node; and a slice orchestrator node.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for location based QOS slicing.

One or more network node 16 functions described below may be performed by one or more of processing circuitry 68, processor 70, QOS implementation unit 32, communication interface 60, etc. One or more management node 15 functions described below may be performed by one or more of processing circuitry 84, processor 86, OSS unit 34, communication interface 82, etc.

In one or more embodiments of the present disclosure, a management node 15, such as an Operations and Support Systems (OSS) node, coordinates the QOS configuration through Basic QOS Profiles and Composite QOS Profiles to provide both a coherent QOS coordination across the different domains and the possibility to associate different QOS configuration for different location where the slices are accessed by wireless devices 22. The QOS configuration may include the 5QI values and their interpretation in the RAN, which may translate to Resource type (GBR/non- GBR), priority levels, Packet delay budget, Packet Error Rate, Default Averaging Window, Domain priority level, relative priority, RLC mode, etc. The QOS configuration(s) may be stored (e.g., in memory 88), may be accessible from another network entity (e.g., via communication interface 82), and/or may be configured/input by a user (e.g., via client application 92).

In some embodiments of the present disclosure, the management node 15 may add an attribute such as the differential service area which covers the area for differentiated QOS treatment (e.g., list of cells, TAC, geographic area, etc.), and the QOS treatment in the area, such that there may be multiple differential service areas, which may be translated to the configuration of the cells 18/network nodes 16 in those areas with the differential treatment, which is separate to the area of service where a user of a wireless device 22 may get access to the slice. Embodiments of the present disclosure include techniques for management node 15 (e.g., OSS/orchestration) to handle the differential service areas.

One or more embodiments described herein may significantly improve the speed of QOS upgrade operations, where the slices associated to specific QOS profiles may need to be updated to meet new requirements needs.

In some embodiments, QOS configurations may be modeled in the Management Information Base of the network managed function through 5 QI tables, 5QI flows, and scheduling priority values. These models may be instantiated in each network managed function’s instances and may need to be configured in a homogenous way when part of the same slice/service.

In embodiments of the present disclosure, the concept of a Slice QOS Profile is used, which is known at the OSS level. “OSS level” may refer to the perspective from the management node 15/OSS unit 34 The Slice QOS Profile may describe the QOS characteristics, and it may be used to drive the managed network functions configurations. There may be multiple QOS profiles for the slice and these QOS profiles may be associated to the differentiated service areas.

For example, as shown in FIG. 9, which depicts an example network architecture according to some embodiments of the present disclosure, there may be, for example, two QOS profiles used across the network. In the example of FIG. 9, the network nodes 16 are gNBs 16. The two QOS profiles may each have its own 5QI flow profiles. This example shows the view of the architecture from the perspective of the management node 15 (“OSS View”) and from the perspective of the network node 16 (“Network / gNB View”). In some embodiments, the QOS profiles’ scope may not be the network node 16’s functions, but rather the management node 15 ’ s functions. In this way, the replication of the same QOS profile for each network node 1 ’s function it is configured on may be avoided.

In some embodiments of the present disclosure, instead of storing and/or modeling every 5QI table, 5QIs, and scheduling priority values for each managed network function, the management node 15/OSS system may model and/or store one QOS profile representing a specific set of slice/service requirements and characteristics. These QOS Profiles are referred to herein as “Basic QOS Profile” and may be used to configure a set of managed network functions where a homogenous QOS configuration may be needed. When creating the slice, the management node 15 may use a reference to the ’’Basic QOS Profile” to ensure the same configuration is applied to the slice configuration for all the involved managed network functions where the slice/service needs to be configured. This may result in a common QOS configuration across all the managed network functions of the slice/service

While some aspects of the QOS may always be the same across all the involved managed network functions (e.g. 5QIs), in embodiments of the present disclosure, some aspects may be configured/interpreted in a different way depending from the location from where the service/slice is accessed (which may be represented by the differential slice area and related attributes to the network slice type (NEST) template).

Referring to FIG. 10, which is an example network implementation according to embodiments of the present disclosure in which a first Basic QOS Profile 1 is associated with a public mobile broadband network (MBB), and a second Basic QOS Profile 2 is associate with a hospital premises network. When configuring slices for healthcare services in a hospital, it may be beneficial that the relative priority scheduling for a particular service may be higher for a user accessing the service from the hospital premises and that the relative priority scheduling for the service may be lower for a user accessing it from the public mobile broadband network when not inside the hospital premises.

In some embodiments of the present disclosure, a “Composite QOS Profile” profile type may be utilized. The Composite QOS Profile may aggregate different Basic QOS Profiles, described herein, which may be used to serve different locations of the deployed slice/service and which may help to ensure the right consistency level in the QOS configuration.

An example of configuration consistency and configuration differentiation would be the consistency of the 5QI table I flows across the aggregated Basic QOS Profile(s) and the different Relative Priority Scheduling for specific flows for the aggregated Basic QOS Profile(s).

In FIG. 10, the Composite QOS Profile X is a composite QOS profile at slice/service level aggregating multiple (Basic) QOS profiles to differentiate priority level by location. In this example, the Public MBB has almost the same QOS profile but lower priority scheduling (RPS). The hospital premises has almost the same QOS profile but higher priority scheduling (RPS).

FIG. 11 depicts an example system according to some embodiments of the present disclosure. The management node 15 includes an operation support system (OSS) unit 34, which may include functionalities such as a QOS profile manager 94, slice manager 96, configuration manager 98, and location aware topology manager 100. The management node 15/OSS unit 34 communicates with the macro network and a dedicated network (each of which includes one or more network nodes 16), including sending/receiving configuration commands, and sending/receiving telemetry.

In some embodiments, one or more of QOS profile manager 94, slice manager 96, configuration manager 98, and location aware topology manager 100 may be part of OSS unit 34, and/or may be one or more separate units/entities/nodes/etc. For example, QOS profile manager 94 may be implemented on a first management node 15, while location aware topology manager 100 may be implemented on a second management node 15, which may be separate or co-located management nodes 15.

The following functions may be performed, e g., by the management node 15, to enable location-based QOS slicing.

QOS Profile Manager 94: this function may enable the creation of QOS profiles in the form of Basic profile and Composite Profiles. A Composite profile may aggregate multiple basic profiles and/or multiple composite profiles. Profiles may be identified with a profile name (which may be mandatory) and/or location (which may be optional). When location is not specified explicitly, it may be derived as part of the QOS profile provisioning to radio functions as the profile will be attached to such functions in the Location Aware Topology Manager 100.

Location Aware Topology Manager 100 may provide a digital twin representation of the network and location information of the radio access functions and the associated QOS profiles. Location information may be modeled in different ways to meet the security needs of the target operator environment (e.g., full location modeling through GIS spatial coordinates, or through administrative defined geographical areas aggregating the relevant network functions). Slice Manager 96 may be responsible for slice design, creation, monitoring, optimization, healing, and termination. At slice design time, the relevant QOS profile(s) may be added to the slice associated topology to represent the QOS configuration in the location areas covered by the slice. The association between QOS profiles, slice, and network functions in the location areas may be modeled and stored in the Location Aware Topology Manager 100.

The Configuration Manager 98 may be responsible for actuating QOS and slice configuration in the network functions.

FIG. 12 illustrates an example QOS profile model consists of three classes: an abstract QOSProfle class representing modeling the name and description of the profile, a BasicQOSProfile modeling the location and the specific QPS characteristics, and a CompositeQOSProfile modeling the aggregation of multiple Basic or Composite QOS profiles.

FIG. 13 illustrates another example QOS profile model similar to the model of FIG. 12, where slice(s) are associated with the QOS profile(s). The slice may be associated to a QOSProfile which can be implemented through a BasicQOSProfile and/or a CompositeQOSProfle. The association may bidirectional.

FIG. 14 illustrates an example OSS unit 34 of a management node 15 including a QOS profile manager 94, slice manager 96, configuration manager 98, and location aware topology manager 100. The following functions/interfaces and related interactions are described with respect to FIG. 13:

QOS I: the interface may be used to create, read, update, delete, and/or query BasicQOSProfile objects and CompositeQOSProfile objects. The interface may be used by a client to manage the profiles, and by Slice Manager 96 to read the specific QOS characteristics given a QOS profile to create the proper association in the slice model and to properly configure the network functions (e.g., functions of one or more network nodes 16), such as when it is not possible to pre-provision the QOS profiles in the network functions in advance of slice creation on them.

Slice Interface (Slice l): the interface may be used to create, read, update, delete, and/or query network slices. The interface may be used by clients for slice operations. Topology Interface (Topology I): the interface may be used to create, read, update, delete, and/or query the location aware topology digital twin information both in terms of network services (e.g., slices), network resources (e.g., gNodeBs 16) and the way network services and network resources are associated together. This interface may be used by the Slice Manager 96 to manage the topology of the managed slices.

CM Interface (CM_I): the interface may be used to provision the network through configuration management network exposed agents. The interface may be accessed by the QOS Profile Manager 94 in case the pre-provisioning of QOS profiles is supported by the network functions. The interface may also be accessed by the Slice Manager 96 to provision the slices in the network. In case the pre-provisioning of QOS profiles is not supported by the network functions, the Slice Manager 96 may also configure the QOS at the slice provisioning time, e.g., by retrieving the relevant information from the QOS Profile Manager 94 (in such a case, the Slice Manager 96 may also need to make sure the inherent limits of the network functions in terms of QOS Profile are not breached).

Therefore, one or more embodiments of the present disclosure provides one or more of the advantages described below.

One or more embodiments of the present disclosure enable easier (compared to existing systems) techniques for managing QOS associated to specific service definitions through QOS profiles well known to the Operations Support System users with no need to know the detailed QOS configuration of the network.

One or more embodiments of the present disclosure may enable bulk QOS updating as the update of the defined profile may trigger the impact analysis and bulk modification of all slices associated to the defined profiles.

One or more embodiments of the present disclosure may enable easier (compared to existing systems) differentiation of different QOS configuration for different geographical locations, avoiding scattered uncoordinated configuration on the network devices and allowing rapid adaptation of QOS needs to specific locations, which may be implemented using automated location-based optimization algorithms.

One or more embodiments of the present disclosure may enable avoiding complex matching algorithm implementations to match the requested QOS configuration with the actual network configuration to avoid QOS configuration proliferation, which may also be limited by the inherent configuration limits of the network (e.g., maximum number of QOS configurations permitted).

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

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

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

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

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

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

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

It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

WHAT IS CLAIMED IS:

1. A management node (15) configured to communicate with a network node (16), the management node (15) comprising processing circuitry (84) configured to: determine a composite quality of service, QOS, profile, the composite QOS profile including a plurality of basic QOS profiles, a basic QOS profile of the plurality of QOS profiles being associated with a corresponding differential service area; determine a first differential service area associated with the first network node (16); determine a first basic QOS profile of the plurality of basic QOS profiles, the first basic QOS profile being associated with the first differential service area; determine a first QOS configuration for the first network node (16) based on the first basic QOS profile, the first QOS configuration being configured to cause the first network node (16) to perform at least one network node (16) function in accordance with the first QOS configuration; and cause a transmission of the first QOS configuration to the first network node (16).

2. The management node (15) of Claim 1, wherein the first QOS configuration includes and/or indicates: at least one index value; and a mapping of the at least one index value to a corresponding QOS parameter set.

3. The management node (15) of Claim 2, wherein at least one of the at least one index value is a 5G QOS Identifier, 5QI, value.

4. The management node (15) of any one of Claims 2 and 3, wherein a corresponding QOS parameter set includes at least one of: a resource type, the resource type being one of: a guaranteed bit rate, GBR, resource type, and a non-GBR resource type; a priority level; a packet delay budget; a packet error rate; a default averaging window; a domain priority level; a relative priority; and a radio link control, RLC, mode.

5. The management node (15) of any one of Claims 1-4, wherein the first differential service area is determined based on at least one of: a cell associated with the first network node (16), a tracking area code, TAC, associated with the first network node (16), and a geographic area associated with the first network node (16).

6. The management node (15) of any one of Claims 1-5, wherein the composite QOS configuration profile is associated with a network slice.

7. The management node (15) of any one of Claims 1-6, wherein the management node (15) is at least one of: an Operations Support Systems, OSS, node; a service orchestrator node; and a slice orchestrator node.

8. The management node (15) of any one of Claims 1-7, wherein the management node (15) is pre-configured with at least one of: a meaning of an index value for the first network node (16) for a plurality of different services; a meaning of an index value for a plurality of differential service areas, a service having a first meaning in one of the plurality of differential service areas and having a second meaning in another of the plurality of differential service areas; and a plurality of index values for a plurality of services for the first network node (16) in the first differential service area associated with the first network node (16).

9. The management node (15) of any one of Claims 1-8, wherein the processing circuitry (84) is further configured to: determine a second differential service area associated with a second network node (16); determine a second basic QOS profile of the plurality of basic QOS profiles, the second basic QOS profile being associated with the second differential service area; determine a second QOS configuration for the second network node (16) based on the second basic QOS profile, the second QOS configuration being configured to cause the second network node (16) to perform at least one network node (16) function in accordance with the second QOS configuration; and cause a transmission of the second QOS configuration to the second network node (16).

10. The management node (15) of Claim 9, wherein the second QOS configuration differs from the first QOS configuration by at least one of: a resource type, the resource type being one of: a guaranteed bit rate, GBR, resource type, and a non-GBR resource type; a priority level; a packet delay budget; a packet error rate; a default averaging window; a domain priority level; a relative priority; and a radio link control, RLC, mode.

11. The management node (15) of any one of Claims 1-10, wherein the first basic QOS profile is associated with at least one of: a profile name; and a location, the location being derived by a location aware topology manager (100).

12. The management node (15) of any one of Claims 1-11, wherein the determining (S138) of the first basic QOS profile associated with the first differential service area includes: determining a location associated with the first differential service area; and identifying, among the plurality of basic QOS profiles of the composite QOS profile, the first QOS profile having the same location as the location associated with the first differential service area.

13. The management node (15) of any one of Claims 1-12, wherein the determining of the first QOS configuration for the first network node (16) based on the first basic QOS profile includes modifying at least one parameter, the at least one parameter including at least one of: a resource type, the resource type being one of: a guaranteed bit rate, GBR, resource type, and a non-GBR resource type; a priority level; a packet delay budget; a packet error rate; a default averaging window; a domain priority level; a relative priority; and a radio link control, RLC, mode.

14. A method implemented in a management node (15) configured to communicate with a network node (16), the method comprising: determining (SI 34) a composite quality of service, QOS, profile, the composite QOS profile including a plurality of basic QOS profiles, a basic QOS profile of the plurality of QOS profiles being associated with a corresponding differential service area; determining (SI 36) a first differential service area associated with the first network node (16); determining (SI 38) a first basic QOS profile of the plurality of basic QOS profile, the first basic QOS profile being associated with the first differential service area; determining (S140) a first QOS configuration for the first network node (16) based on the first basic QOS profile, the first QOS configuration being configured to cause the first network node (16) to perform at least one network node (16) function in accordance with the first QOS configuration; and causing a transmission (S142) of the first QOS configuration to the first network node (16).

15. The method of Claim 14, wherein the first QOS configuration includes and/or indicates: at least one index value; and a mapping of the at least one index value to a corresponding QOS parameter set.

16. The method of Claim 15, wherein at least one of the at least one index value is a 5G QOS Identifier, 5QI, value.

17. The method of any one of Claims 15 and 16, wherein a corresponding QOS parameter set includes at least one of: a resource type, the resource type being one of: a guaranteed bit rate, GBR, resource type, and a non-GBR resource type; a priority level; a packet delay budget; a packet error rate; a default averaging window; a domain priority level; a relative priority; and a radio link control, RLC, mode.

18. The method of any one of Claims 14-17, wherein the first differential service area is determined based on at least one of: a cell associated with the first network node (16), a tracking area code, TAC, associated with the first network node (16), and a geographic area associated with the first network node (16).

19. The method of any one of Claims 14-18, wherein the composite QOS configuration profile is associated with a network slice.

20. The method of any one of Claims 14-19, wherein the management node (15) is at least one of: an Operations Support Systems, OSS, node; a service orchestrator node; and a slice orchestrator node.

21. The method of any one of Claims 14-20, wherein the management node (15) is pre-configured with at least one of: a meaning of an index value for the first network node (16) for a plurality of different services; a meaning of an index value for a plurality of differential service areas, a service having a first meaning in one of the plurality of differential service areas and having a second meaning in another of the plurality of differential service areas; and a plurality of index values for a plurality of services for the first network node (16) in the first differential service area associated with the first network node (16).

22. The method of any one of Claims 14-21, further comprising: determining a second differential service area associated with a second network node (16); determining a second basic QOS profile of the plurality of basic QOS profiles, the second basic QOS profile being associated with the second differential service area; determining a second QOS configuration for the second network node (16) based on the second basic QOS profile, the second QOS configuration being configured to cause the second network node (16) to perform at least one network node (16) function in accordance with the second QOS configuration; and causing a transmission of the second QOS configuration to the second network node (16).

23. The method of Claim 22, wherein the second QOS configuration differs from the first QOS configuration by at least one of: a resource type, the resource type being one of: a guaranteed bit rate, GBR, resource type, and a non-GBR resource type; a priority level; a packet delay budget; a packet error rate; a default averaging window; a domain priority level; a relative priority; and a radio link control, RLC, mode.

24. The method of any one of Claims 14-23, wherein the first basic QOS profile is associated with at least one of: a profile name; and a location, the location being derived by a location aware topology manager (100).

25. The method of any one of Claims 14-24, wherein the determining (S138) of the first basic QOS profile associated with the first differential service area includes: determining a location associated with the first differential service area; and identifying, among the plurality of basic QOS profiles of the composite QOS profile, the first QOS profile having the same location as the location associated with the first differential service area.

26. The method of any one of Claims 14-25, wherein the determining (S140) of the first QOS configuration for the first network node (16) based on the first basic QOS profile includes modifying at least one parameter, the at least one parameter including at least one of: a resource type, the resource type being one of: a guaranteed bit rate, GBR, resource type, and a non-GBR resource type; a priority level; a packet delay budget; a packet error rate; a default averaging window; a domain priority level; a relative priority; and a radio link control, RLC, mode.

27. A network node (16) configured to communicate with a management node (15), the network node (16) being associated with a first differential service area, the network node (16) comprising processing circuitry (68) configured to: receive a QOS configuration from the management node (15), the QOS configuration being based on a first basic QOS profile that is associated with the first differential service area and a composite quality of service, QOS, profile, the composite QOS profile being associated with a plurality of basic QOS profiles, a basic QOS profile of the plurality of basic QOS profiles being associated with a corresponding differential service area; and perform at least one network node (16) function in accordance with the QOS configuration.

28. The network node (16) of Claim 27, wherein the QOS configuration includes and/or indicates: at least one index value; and a mapping of the at least one index value to a corresponding QOS parameter set.

29. The network node (16) of Claim 28, wherein at least one of the at least one index value is a 5G QOS Identifier, 5QI, value.

30. The network node (16) of any of Claims 28 and 29, wherein a corresponding QOS parameter set includes at least one of: a resource type, the resource type being one of: a guaranteed bit rate, GBR, resource type, and a non-GBR resource type; a priority level; a packet delay budget; a packet error rate; a default averaging window; a domain priority level; a relative priority; and a radio link control, RLC, mode.

31. The network node (16) of any of Claims 27-30, wherein the first differential service area is determined based on at least one of: a cell associated with the network node (16), a tracking area code, TAC, associated with the network node (16), and a geographic area associated with the network node (16).

32. The network node (16) of any one of Claims 27-31, wherein the composite QOS configuration profile is associated with a network slice.

33. The network node (16) of any one of Claims 27-32, wherein the network node (16) is at least one of: an Operations Support Systems, OSS, node; a service orchestrator node; and a slice orchestrator node.

34. A method implemented in a network node (16) configured to communicate with a management node (15), the network node (16) being associated with a first differential service area, the method comprising: receiving (S144) a QOS configuration from the management node (15), the QOS configuration being based on a first basic QOS profile that is associated with the first differential service area and a composite quality of service, QOS, profile, the composite QOS profile being associated with a plurality of basic QOS profiles, a basic QOS profile of the plurality of basic QOS profiles being associated with a corresponding differential service area; and performing (SI 46) at least one network node (16) function in accordance with the QOS configuration.

35. The method of Claim 34, wherein the QOS configuration includes and/or indicates: at least one index value, and a mapping of the at least one index value to a corresponding QOS parameter set.

36. The method of Claim 35, wherein at least one of the at least one index value is a 5G QOS Identifier, 5QI, value.

37. The method of any one of Claims 35 and 36, wherein a corresponding QOS parameter set includes at least one of: a resource type, the resource type being one of: a guaranteed bit rate, GBR, resource type, and a non-GBR resource type; a priority level; a packet delay budget; a packet error rate; a default averaging window; a domain priority level; a relative priority; and a radio link control, RLC, mode.

38. The method of any one of Claims 34-37, wherein the first differential service area is determined based on at least one of: a cell associated with the network node (16), a tracking area code, TAC, associated with the network node (16), and a geographic area associated with the network node (16).

39. The method of any one of Claims 34-38, wherein the composite QOS configuration profile is associated with a network slice.

40. The method of any one of Claims 34-39, wherein the network node (16) is at least one of: an Operations Support Systems, OSS, node; a service orchestrator node; and a slice orchestrator node.