WO2018130306A1

WO2018130306A1 - Quality of service class indicator structure and corresponding controllers and control methods

Info

Publication number: WO2018130306A1
Application number: PCT/EP2017/050715
Authority: WO
Inventors: Clarissa Marquezan; Xueli AN; Ramin KHALILI; Ishan Vaishnavi; Artur Hecker
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2017-01-13
Filing date: 2017-01-13
Publication date: 2018-07-19

Abstract

The present invention relates to treatment of one or more control messages of a service type or slice in the communication network and introduces entities and messages facilitating the treatment of said control messages. The treatment of the one or more control messages is executed by use of one or more control policy profile units. Any one of the one or more control policy profile units is associated with a service type or a slice and arranged to define a treatment of control messages of the service type or the slice in the communication network, wherein a control message of the service type or slice is a control message generated with regard to the service type or the slice.

Description

QUALITY OF SERVICE CLASS INDICATOR STRUCTURE AND CORRESPONDING CONTROLLERS AND CONTROL METHODS TECHNICAL FIELD

The present invention is directed to treatment of control messages of a service type or slice in the communication network and introduces entities and messages facilitating the treatment of said control messages. The treatment of control messages comprises, for example, generation of the control messages, exchange/communication (i.e., transmission and/or reception) of the control messages, management of the control messages, and/or processing of the control messages.

BACKGROUND

As a further development in the area of communication networks, the 5 Generation mobile technology (5G) will be standardized and deployed by 2020. Compared to the 4G mobile telecommunication system, 5G will support use cases with very high variety in terms of performance attributes, for instance ultra-reliable communications for mission critical services, eHealth, public safety, real-time vehicle control, tactile Internet, connectivity for drones, and so on. Supporting such an assorted set of use cases can be accomplished only by a flexible network, capable to adapt to achieve heterogeneous performance. Herein, the use cases refer to services and/or slices in a communication network. The term "service" is well known in the area of communication technique and refers, for example, to provision of data storage, data manipulation or processing, data presentation, data communication (i.e., transmission and/or reception) and/or other data processing capability in a communication network. The term "slice" is also well known in the area of communication technique. A slice refers, for example, to a composition of adequately configured network functions, network applications, and/or underlying cloud infrastructures that are bundled together to meet one or more requirements of a specific use case in the communication network.

For the next generation mobile system, a wide variety of electronic devices will require connectivity (smartphone, wearable devices, smart cars, electronic household appliances, industrial equipment etc.). Such devices will feature one or multiple access capabilities. Based on the services they will provide, they will be characterized by very different performance requirements and data traffic models. The heterogeneity of the deployed access infrastructure will represent both an opportunity and a challenge for next generation operators. Finally, the need to integrate communication services required by vertical industries completes the list of key requirements for next generation networks. As mentioned, examples of use cases are: a) Broadcast-like Services which are focused on the dissemination of information, but no need "hard" requirements; b) eHealth Extreme Life Critical where low latency and ultra-reliability are essential for this type of use case. The configuration of connectivity for eHealth Extreme Life Critical devices should not have some kind of priority over broadcastlike services. The diversity of requirements of these use cases affects not only their data plane, but also the execution of control plane procedures. For instance, control packets for management of the sessions of eHealth Extreme Life Critical devices need to treat differently than the ones from Broadcast-like Services. The lack of prompt treatment of control messages from the first type of use cases could result in life- threatening situations, while the second would results in users having to reload web pages. Therefore, mechanisms to differentiate also the treatment of control plane messages needs to be enabled so that Mobile Core Networks (MCN) Operators can support different use cases and fulfil the expected data and control plane requirements from such use cases.

Thus, solutions improving the treatment of control plane messages or control messages respectively are of great interest. SUMMARY

The object of the present invention is improving the treatment of control plane messages or control messages respectively in a communications network. In particular, the treatment of control plane messages is to be improved in a communication network with a variety of use cases having different performance attributes, requirements and/or conditions.

The object of the present invention is achieved by the solution provided in the enclosed independent claims. Advantageous implementations of the present invention are further defined in the respective dependent claims, in the description, and/or in the appended figures.

In particular, the invention, described herein, allows to improve the treatment of control plane messages or control messages respectively in that it enables a differentiation of the control plane messages or control messages respectively in a communication network, for example, in the next generation mobile network such as 5G. Moreover, the invention, as described herein, enables a differentiation of control signaling (i.e., processing, transmission and/or reception of control plane messages or control messages respectively) among different service types and/or slices and/or enables a differentiation of control signaling within the same slice or service. Herein, the term "control plane message" and the term "control message" are used synonymously. The term "control plane message" or "control message" respectively are well known and represent messages that are transmitted in communication network to control the operation of the communication devices or entities in the communication network and/or to control processes running in the communication network.

According to the present invention, a control policy profile unit is introduced that allows the distinguishing of the treatment of control messages of different service types or slices. Further, a control plane policy management (referred to also as CPPM in the following) entity as well as the control plane (CP) extension (CP extension) and user to control plane extension (U2CP extension) functions or entities are provided to enable control plane differentiation, i.e. differentiation of control (plane) messages of different service types or slices.

According to a first aspect, control policy profile unit is provided that is associated with a service type or a slice and that is arranged to define a treatment of control messages of the service type or the slice in the communication network, wherein a control message of the service type or slice is a control message generated with regard to the service type or the slice.

In a first possible implementation according to the first aspect, the treatment of a control message of the service type or the slice comprises a generation of the control message, a transmission of the control message, a reception of the control message, and/or a processing of the control message.

In a second possible implementation form according to the first aspect as such or according to the first implementation form of the first aspect, the control policy profile unit comprises a specification of the treatment of control messages of the service type or the slice in the communication network.

In a third possible implementation form according to the second possible implementation form of the first aspect, the treatment of the control messages of the service type or slice is based one of the following mechanisms: a label based mechanism, according to which a label is attached to a control message of the service type or slice, to be transmitted in the communication network, wherein the label identifies the control policy profile unit, which defines the treatment of the control message of the service type or slice; a channel based mechanism, according to which one or more control channels are identified for transmitting the control messages of the service type or slice.

In a fourth possible implementation form according to the third possible implementation form of the first aspect: if the treatment of the control messages of the service type or slice is based on the label based mechanism, the control policy profile unit defines that the label has to comprise at least one of the following entries: a subscriber class indication; a device traffic in the communication network, with which the control policy profile unit is associated; a slice indication indicating a slice, with which the control policy profile unit is associated; a control plane quality of service, QoS, class identifier; if the treatment of the control messages of the service type or slice is based on the channel based mechanism, the control policy profile unit defines one or more parameters specifying one or more control channels for transmitting the control messages of the service type or slice.

According to a second aspect, a control plane policy management entity is provided that is arranged to manage one or more control policy profile units as outlined above and/or as described in more detail in the following, wherein the control plane policy management entity is configured to: generate a new control policy profile unit arranged as outlined above and/or as described in more detail in the following; amend an existing control policy profile unit to be amended and arranged as outlined above and/or as described in more detail in the following; and/or delete an existing control policy profile unit to be deleted and arranged as outlined above and/or as described in more detail in the following.

In a first possible implementation according to the second aspect, the control plane policy management entity is configured to: generate the new control policy profile unit in response to a presence of a profile of the service type or slice, with which the new control policy profile unit is associated; amend the existing control policy profile unit to be amended in response to a presence of an amended profile of the service type or slice, with which the new control policy profile unit is associated; and/or delete the existing control policy profile unit to be deleted in response to a presence of an indication indicating the deletion.

In a second possible implementation form according to the second aspect as such or according to the first implementation form of the second aspect, the control plane policy management entity is configured to: transmit the generated new control policy profile unit to one or more communication network entities, which is or are configured to treat control messages of the service type or slice with which the new control policy profile unit is associated; transmit the amended existing control policy profile unit to the one or more communication network entities for announcing the amended existing control policy profile unit in the communication network; and/or transmit information on the deleted existing control policy profile unit to the one or more communication network entities for announcing the deletion of the existing control policy profile unit in the communication network.

According to a third aspect, a control plane policy management method is provided that is arranged to manage one or more control policy profile units arranged as outlined above and/or as described in more detail in the following, wherein the control plane policy management method comprises steps of: generating a new control policy profile unit arranged as outlined above and/or as described in more detail in the following; amending an existing control policy profile unit to be amended and arranged as outlined above and/or as described in more detail in the following; and/or deleting an existing control policy profile unit to be deleted and arranged as outlined above and/or as described in more detail in the following. The control plane policy management method is executed, for example, by the control plane policy management entity as outlined above and/or as described in more detail in the following. Thus, the control plane policy management method may comprise any one of the steps executed by the control plane policy management entity.

According to a fourth aspect, a communication network entity is provided that is arranged to communicate and/or to support communication with further communication network entities in a communication network, wherein the communication network entity is configured to treat one or more control messages of a service type or slice according to a control policy profile unit, wherein the control policy profile unit is arranged as outlined above and/or as described in more detail in the following.

In a first possible implementation according to the fourth aspect, the communication network entity is configured to receive a new control policy profile unit, an amended control policy profile unit and/or information on a deleted control policy profile unit, and wherein the communication network entity is configured to: treat one or more control messages, with which the new control policy profile unit is associated, by use of the new control policy profile unit; treat one or more control messages, with which the amended control policy profile unit is associated, by use of the amended control policy profile unit; and/or treat one or more control messages, with which the deleted control policy profile unit is associated, by disregarding the deleted existing control policy profile unit.

In a second possible implementation form according to first implementation form of the fourth aspect, the communication network entity is configured to receive the new control policy profile unit, the amended control policy profile unit and/or information on a deleted control policy profile unit from a control plane policy management entity.

In a third possible implementation form according to second implementation form of the fourth aspect, the control plane policy management entity is a control plane policy management entity as outlined above and/or as described in more detail in the following.

In a fourth possible implementation form according to the fourth aspect as such or according to the any of the preceding implementation forms of the fourth aspect, the treatment of the one or more control messages comprises generation of one or more control messages, transmission of one or more control messages to one or more of the further communication network entities in the communication network, reception of one or more control messages from one or more of the further communication network entities in the communication network, management of one or more control messages, and/or processing of one or more control messages.

According to a fifth aspect, a method of communication is provided that comprises: sending, to a OpenFlow switch, a configuration message comprising a header of the configuration message, a flag for message fragmentation, a size of a packet to be sent to a OpenFlow controller, and a flag of a communication channel indicating a type of the communication channel, a operation parameter that qualifies the communication channel, being used for defining the communication channel that should be used for transmissions of control plane messages between the OpenFlow controller and the OpenFlow switch.

According to a sixth aspect, a method of communication is provided that comprises: sending to a communication entity a configuration message comprising a parameter with a subscriber identifier, a subscriber class of service, an identification of a specific network the subscriber belongs to, and an identification of a control plane quality of service label, indicating quality of service for control messages associated with the subscriber identifier, class, and a network ID being used to label all control messages generated and transmitted by the communication entity. According to a seventh aspect, a communication method is provided that is arranged for supporting communication of a communication network entity with further communication network entities in a communication network, wherein the method comprises a treating of one or more control messages of a service type or slice according to a control policy profile unit, wherein the control policy profile unit is arranged as outlined above and/or as described in more detail in the following or wherein the method further comprises steps of the method of the fifth or sixth aspect. The communication method is executed, for example, by the communication network entity as outlined above and/or as described in more detail in the following. Thus, the control plane policy management method may comprise any one of the steps executed by the communication network entity.

BRIEF DESCRIPTION OF DRAWINGS The above-described aspects and implementation forms of the present invention will be explained in the following description of specific embodiments in relation to the enclosed drawings, in which

Fig. 1 shows an arrangement of a control policy profile unit according to an embodiment of the present invention.

Fig. 2 shows an exemplary arrangement of a control plane policy management entity according to an embodiment of the present invention.

Fig. 3 shows steps executed by the control plane policy management entity according to an embodiment of the present invention.

Fig. 4 shows an exemplary arrangement of a communication network entity according to an embodiment of the present invention.

Fig. 5 shows steps executed by the communication network entity according to an embodiment of the present invention. Fig. 6a shows an exemplary embodiment of a system, in which one or more control policy profile units, the control plane policy management entity and one or more communication network entities are implemented, according to an embodiment of the present invention. Fig. 6b shows a further exemplary embodiment of the system, in which one or more control policy profile units, the control plane policy management entity and one or more communication network entities are implemented, according to an embodiment of the present invention.

Fig. 7 visualizes a message exchange executed in the system with regard to a control policy profile unit according to an embodiment of the present invention.

Fig. 8 shows an implementation of the present invention in an evolved packet core (EPC) architecture according to an embodiment of the present invention. Fig. 9 shows a further implementation of the present invention in an evolved packet core (EPC) architecture according to an embodiment of the present invention. shows an implementation of the present invention in software- defined networking (SDN) architecture according to an embodiment of the present invention. shows an arrangement of a configuration message transmitted according to an embodiment of the present invention. shows an arrangement of a configuration message transmitted according to an embodiment of the present invention.

DETAILED DESCRIPION OF EMBODIMENTS

Generally, it has to be noted that all arrangements, devices, modules, components, models, elements, units, entities, and means and so forth described in the present application could be implemented by software or hardware elements or any kind of combination thereof. All steps which are performed by the various entities described in the present application as well as the functionality described to be performed by the various entities are intended to mean that the respective entity is adapted to or configured to perform the respective steps and functionalities. Even if in the following description of the specific embodiments, a specific functionality or step to be performed by a general entity is not reflected in the description of a specific detailed element of the entity which performs the specific step or functionality, it should be clear for a skilled person that these methods and functionalities can be implemented in respective hardware or software elements, or any kind of combination thereof. Further, the method of the present invention and its various steps are embodied in the functionalities of the various described apparatus elements.

Moreover, any of the embodiments and features of any of the embodiments, described herein, may be combined with each other, unless a combination is explicitly excluded. Fig. 1 shows an arrangement of a control policy profile unit 100 according to an embodiment of the present invention. As shown exemplary in Fig. 1, a plurality of service types and/or slices 102 1, 102_k, 102_n is provided in a communication network, wherein n > l , i.e. n is a positive integer and wherein n > k > 1 and k is a positive integer. A control policy profile unit 100 is provided with regard to one of the plurality of service types and/or slices 102 1, 102_k,

102_n. According to Fig. 1 , the control policy profile unit 100 is associated exemplary with a service type or slice 102_k. I.e. the control policy profile unit 100 defines a treatment of control messages of the service type or slice 102_k. For this purpose, according to the present embodiment, the control policy profile unit 100 comprises a specification 101 of the treatment of control messages of the service type or slice 102_k. The treatment of a control message comprises, for example, generation of one or more control messages, exchange/communication (i.e. transmission and/or reception) of one or more control messages, and/or processing of one or more control messages. Because the control policy profile unit 100 is associated with (i.e. is provided for) one service type or slice 102_k of a plurality of service types and/or slices 102 1, 102_k, 102_n, also the specification 101 of the control message treatment refers to the one service type or slice 102_k of a plurality of service types and/or slices 102 1, 102_k, 102_n. The specification 101 defines how any one of control messages relating to (i.e. being generated with regard to) the service type or slice 102_k is to be treated in the communication network.

According to an embodiment, the treatment, specified in the specification 101, is based on a particular treatment mechanism. According to a further embodiment, the treatment, specified in the specification 101 is based on one of the following two mechanisms: a label based mechanism, a channel based mechanism.

The label based mechanism means that a label is attached to a control message of the service type or slice 102_k to be transmitted in the communication network. The label identifies the control policy profile unit 100, which defines the treatment of the control message of the service type or slice 102_k. Thus, any one of control messages of the service type or slice 102_k in the communication network carries a respective control plane differentiation mark, can be recognized as belonging to the service type or slice 102_k via said mark, and can be treated as specified in the specification 101 of the control policy profile unit 100 associated with the service type or slice 102_k.

The channel based mechanism means that one or more control channels are identified for transmitting control messages of the service type or slice 102_k. Thus, control messages of the service type or slice 102_k are differentiated from other control messages via control channels, identified for transmitting control messages of the service type or slice 102_k. In this case, the differentiation is not enclosed in the control message itself as in the above mentioned label based mechanism, but it is configured in the control channel used to transmit control messages of the service type or slice 102_k. In this case, all communication network entities operating with such type of control message differentiation mechanism, i.e. transmitting and/or receiving control messages of the service type or slice 102_k, need to create the specific control channels according to the requirements in the control policy profile unit 100, specified, e.g., in the specification 101. For instance, a control channel can be identified by the transport protocol. In this case, the control channel is associated with the control policy profile unit 100, and the control messages belonging to 102_k have to be placed in the correct channel (i.e. transmitted and received via the correct channel). In addition, according to an embodiment, the communication network entities treating the control messages of the service type or slice 102_k are able to configure the channels to operate according to parameters specified in the control policy profile unit 100 (e.g., in the specification 101), said parameters being specified for and/or characterizing the channel establishment, determining and/or identification. According to the present invention, provision of different control policy profile units 100 is enabled, wherein each of the control policy profile units 100 is associated with a respective service types and/or slices 102 1, 102_k, 102_n. Furthermore, a service type and/or slice 102 1, ..., 102_k, ..., 102_n will be associated with one control policy unit 100 only.

In the further embodiments, the entities dealing with the control policy profile unit 100 will be explained in the following in more detail.

Fig. 2 shows an exemplary arrangement of a control plane policy management entity (CPPM) 200 according to an embodiment of the present invention. In general, the CPPM entity 200 is arranged to manage one or more control policy profile units 100. In particular, the CPPM entity 200 is configured to generate one or more new control policy profile units 100, to amend one or more existing control policy profile units 100, and/or to delete one or more existing control policy profile units 100 to be deleted.

Fig. 2 shows an exemplary structure of the CPPM 200 according to an embodiment of the present invention. According to the present embodiment, the CPPM entity 200 comprises a transmitting entity 202, configured to execute transmission of data in the communication network, and a receiving entity 203, configured to execute reception of data in the communication network. According to an embodiment, the transmitting entity 202 and the receiving entity 203 are provided as one entity (e.g., transceiver), as indicated in Fig. 2 by the box with dashed lines. Thus, any one of the transmission steps, which is described herein as being executed by the CPPM entity 200, is executed by the transmitting entity 202. Any one of the reception steps, which is described herein as being executed by the CPPM entity 200, is executed by the receiving entity 203.

Further, the CPPM entity 200 comprises one or more processing entities 201 configured to execute different processing steps, except for the transmission and reception of data, which are executed accordingly by the transmitting entity 202 and the receiving entity 203. Thus, any one of the steps, which is described herein as being executed by the CPPM entity 200 and which does not refer to data transmission or reception, is executed by at least one of the one or more processing entities 201.

The CPPM entity 200 is configured to generate a new control policy profile unit 100 in response to a presence of a profile of the service type or slice 102 1, ..., 102_k, ..., 102_n with which the new control policy profile unit is associated; to amend an existing control policy profile unit 100 to be amended in response to a presence of an amended profile of the service type or slice, with which the new control policy profile unit is associated; and/or to delete an existing control policy profile unit 100 to be deleted in response to a presence of an indication indicating the deletion.

Further, the CPPM entity 200 is configured to: transmit the generated new control policy profile unit 100 to one or more communication network entities, which is or are configured to treat control messages of the service type or slice 102 1, ..., 102_k, ..., 102_n with which the new control policy profile unit 100 is associated; transmit the amended existing control policy profile unit 100 to the one or more communication network entities for announcing the amended existing control policy profile unit 100 in the communication network; and/or transmit information on the deleted existing control policy profile unit 100 to the one or more communication network entities for announcing the deletion of the existing control policy profile unit in the

communication network. By transmitting the generated new control policy profile unit 100 to one or more communication network entities, which is or are configured to treat control messages of the service type or slice 102 1, ..., 102_k, ..., 102_n with which the new control policy profile unit 100 is associated, the generated new control policy profile unit 100 is announced in the communication network.

Fig. 3 shows steps executed by the CCPM entity 200 according to an embodiment of the present invention to manage one or more control policy profile units 100. The steps, shown in Fig. 3, correspond to the steps described above with regard to Fig. 2 and comprise: generating 301 a new control policy profile unit 100, amending an existing control policy profile unit 100, deleting an existing control policy profile unit 100. Said steps 301, 302, 303 do not have a fixed order. Their execution time depends on the time at which an information with regard to a new control policy profile unit and/or with regard to an existing control policy profile unit 100 to be deleted or amended is present. The respective step 301, 302, 303 will be executed in response to the presence of the corresponding information. For example, this information may be received (by the CCPM entity 200) from a further communication network entity dealing with and/or working based on control policy profile units 100.

Fig. 4 shows an exemplary arrangement of a communication network entity 400 according to an embodiment of the present invention. The communication network entity 400 is configured for communication (comprising, e.g., data/message transmission and/or reception) with further communication network entities 400 in the communication network. The communication network entity 400 is configured to treat control messages of a service type or slice 102 1, ..., 102_k, ..., 102_n according to respective control policy profile units 100.

Fig. 4 shows an exemplary structure of the communication network entity 400 according to an embodiment of the present invention. According to the present embodiment, the communication network entity 400 comprises a transmitting entity 402, configured to execute transmission of data in the communication network, and a receiving entity 403, configured to execute reception of data in the communication network. According to an embodiment, the transmitting entity 402 and the receiving entity 403 are provided as one entity (e.g., transceiver), as indicated in Fig. 4 by the box with dashed lines. Thus, any one of the transmission steps, which is described herein as being executed by the communication network entity 400, is executed by the transmitting entity 402. Any one of the reception steps, which is described herein as being executed by the communication network entity 400, is executed by the receiving entity 403.

Further, the communication network entity 400 comprises one or more processing entities 401 configured to execute different processing steps, except for the transmission and reception of data, which are executed accordingly by the transmitting entity 402 and the receiving entity 403. Thus, any one of the steps, which is described herein as being executed by the communication network entity 400 and which does not refer to data transmission or reception, is executed by at least one of the one or more processing entities 401.

The communication network entity 400 is configured to receive a new control policy profile unit 100, an amended control policy profile unit 100 and/or information on a deleted control policy profile unit 100. In response to any of the received information, the communication network entity 400 executes corresponding steps. Thus, the communication network entity 400 is configured to: treat control messages, with which the new control policy profile unit 100 is associated (i.e. the new control policy profile unit 100 is associated with the service type or slice 102 1, ..., 102_k, ..., 202_n of the control message(s)), by use of the new control policy profile unit 100; treat control messages, with which the amended control policy profile unit 100 is associated, by use of the amended control policy profile unit 100; and/or treat control messages, with which the deleted control policy profile unit 100 is associated, by disregarding the deleted existing control policy profile unit 100. In the latter case, the control policy profile unit 100 is deleted and is, therefore, not taken into consideration.

Fig. 5 shows steps executed by the communication network entity 400 according to an embodiment of the present invention to support communication of the communication network entity 400 with further communication network entities 400, in particular the transmission and/or reception of communication messages. The steps, shown in Fig. 5, correspond to the steps described above with regard to Fig. 4 and comprise in general the treating 500 of control messages of a service type or slice 102 1, ..., 102_k, ..., 102_n according to a control policy profile unit 100, wherein the control policy profile unit 100 is arranged according to any one of claims 1 to 5. The treating 500 of control messages comprises at least one of the following steps: transmitting 501 a control message according to a control policy profile unit 100 associated with the service type or slice 102 1, ..., 102_k, ..., 102_n of the control message; receiving 502 a control message according to a control policy profile unit 100 associated with the service type or slice 102 1, ..., 102_k, ..., 102_n of the control message; processing 503 a control message according to a control policy profile unit 100 associated with the service type or slice 102 1, ..., 102_k, ..., 102_n of the control message. The execution of the sub steps 501, 502, 503 of the general control message treatment step 500 is arbitrary. It depends on the flow (e.g., schedule) of steps executed by the communication network entity 400.

Fig. 6a shows an exemplary embodiment of a system, in which one or more control policy profile units 100, the CPPM entity 200 and one or more communication network entities 400_1, 400_2 are implemented, according to an embodiment of the present invention. The communication network entities 400_1, 400_2, the one or more control policy profile units 100 and/or the CPPM entity 200 are arranged, for example, as described above.

According to the present embodiment, the implementation of the system is shown with regard to two planes of the communication network architecture, which commonly comprises different planes, e.g., basic planes comprising data plane and control plane. The system of the present embodiment is implemented with regard to the control plane 610, where signal traffic and, thus, control messages are carried, and data or user plane 620, where network user traffic is carried. Thus, the communication network entities 400_1, 400_2 (see also the above-described communication network entity 400) comprise one or more communication network entities 400_1 of the control plane 610 and one or more communication network entities 400_2 of the user plane 620.

According to the present embodiment, the CPPM entity 200 is located in the control plane 610.

In the following, for a better distinguishing between the communication network entities 400_1 of the control plane 610 and the communication network entities 400_2 of the user plane 620, the communication network entities 400_1 of the control plane 610 will be referred to as control plane entities (CPEs) and the communication network entities 400_2 of the user plane 620 will be referred to as user plane entities (UPEs). Both the CPEs 400_1 and the UPEs 400_2 are configured to treat each one of the control messages of a service type or slice 102 1, ..., 102_k, ..., 102_n according to a corresponding control policy unit 100 associated with the respective service type or slice 102 1, ..., 102_k, ..., 102_n, as described above with regard to Fig. 4.

Thus, according to the present embodiment, a system architecture is provided that has a decoupled control plane 610 and user plane 620, upon which a CPPM entity 200 as well as communication network entities 400, 400_1, 400_2 (i.e. one or more CPEs 400_1 and one or more EPEs 400_2) are provided to enable the control plane 610 differentiation according to specific service type or slice requirements of how the control plane 610 traffic of such service type or slice should be handled.

In the control plane, the CPEs 400 1 communicate with each other by transmitting and receiving control messages. Further, one or more CPEs 400_1 of the control plane 610 are configured to transmit control messages to the UPEs 400_2 of the user plane 620. This is indicated in Fig. 6a by the connection line between the CPE 400 1 and the UPE 400_2. Thus, a communication network entity of the user plane 620 can be considered as a UPE 400_2, if it is arranged to treat (e.g., generate, transmit, receive, manage, and/or process) control messages. According to an embodiment, the user plane 620 will comprise one or more communication network entities that are not arranged as UPEs 400_2 of the present invention because not every communication network entity of the user plane 620 is arranged to treat control messages.

The CPPM entity 200 generates one or more new control policy profile units 100, amends one or more existing control policy profile units 100, and/or deletes one or more existing control policy profile units 100, as described above. In the following, the term "control policy profile unit" will be abbreviated by "CrtPP" for sake of conciseness. Additionally, according to the present embodiment the CPPM entity 200 is configured to store the one or more CrtPPs 100. In particular, the CPPM entity 200 is configured to coordinates how the one or more CrtPPs 100 are installed and enforced by the communication network entities 400, 400_1, 400_2 (i.e. one or more CPEs 400_1 and one or more EPEs 400_2) that treat/handle (i.e., generate, transmit, receive, manage, and/or process) control plane traffic. For this purpose, the CPPM entity 200 is configured to communicate with the one or more CPEs 400_1 and with the one or more UPEs 400_2, as indicated by the connection lines between the CPPM entity 200 and any one of the CPEs 400_1 and UPEs 400_2.

According to the present embodiment, a communication interface 640 is provided between the CPPM entity 200 and any one of the CPEs 400_1. For sake of conciseness, the communication interface 640 will be referred to in the following as "CP-If '. The CP-If 640 is provided for transmission of one or more CrtPPs 100 from the CPPM entity 200 to the one or more CPEs 400_1.

Further, according to the present embodiment, a communication interface 630 is provided between the CPPM entity 200 and any one of the UPEs 400_2. For sake of conciseness, the communication interface 630 will be referred to in the following as "user to control plane interface" of "U2CP-If ' respectively. The U2CP-If 630 is provided for transmission of one or more CrtPPs 100 from the CPPM entity 200 to the one or more EPEs 400_2.

Both the CP-If 640 and the U2CP-If 630 are used by the CPPM entity 200 in order to: distribute and update one or more CrtPPs 100 at the one or more CPEs 400 1 and at the one or more UPEs 400_2; check the status if a CrtPP 100 is installed in the one or more CPEs 400_1 and in the one or more UPEs 400_2; change the definition of one or more already deployed or existing CrtPP 100.

The arrangement of the one or more CPEs 400 1 such that they treat communication messages according to one or more CrtPPs 100 enables the one or more CPEs 400_1 to: generate differentiated control messages to other CPEs 400_1 or UPEs 400_2, and differentiate the treatment of control messages received either from one or more other CPEs 400_1 or UPEs 400_2. The treatment of the control messages will follow the criteria defined in the CrtPPs 100 (e.g., in the specifications 101 of the CrtPPs 100). An example of criteria for a CrtPP 100 can be the prioritization in the queues of the CPEs 400_1 or UPEs 400_2 of control messages from a particular use case, e.g. of a particular service type or slice 102 1, ..., 102_k, ..., 102_n. In this case, both the CPEs 400_1 and the UPEs 400_2 must support the type of treatment defined in the criteria, i.e. in the CrtPP 100. In this example, a support of a queuing system with prioritization will be required. Fig. 6b shows a further exemplary embodiment of the system, in which one or more CrtPPs 100, the CPPM entity 200 and one or more communication network entities 400, 400_1, 400_2 are implemented, according to an embodiment of the present invention. The embodiment of Fig. 6b is based on the embodiment of Fig. 6a. Therefore, the description presented above with regard to Fig. 6a concerns also the embodiment of Fig. 6b.

In Fig. 6b a use case plane is provided as a further plane 650. The use case plane comprises use case entities 651_1, ..., 65 l_i, ...,. 65 l_m, wherein i and m are positive integers and 1 < i < m. Each one of the use case entities 651 1, 651_i, 651_m is associated with (e.g., provided for) a service type or slice 102 1, ..., 102_k, 102_n and is configured to manage and/or communicate profiles of the respective service type or slice 102 1, ..., 102_k, 102_n associated with the use case entities 651 1, ..., 651_i, 651_m.

The CPPM entity 200 is arranged to communicate with the use case entities 651 1, ..., 65 l_i, ...,. 65 l_m, as shown in Fig. 6b by the connection line connecting the CPPM entity 200 with the use case plane 650. In particular, the CPPM entity 200 receives from any one of the use case entities 651 1, 65 l_i, 651_m the profile of the service type or slice 102 1, ..., 102_k, 102_n, with which the use case entity 651 1, 65 l_i, 651_m is associated.

According to the present embodiment, a corresponding communication interface 660 is provided that allows the communication between the CPPM entity 200 and the use case entities 651 1, 65 l_i, 651_m. Particularly, the one or more profiles of the one or more service types or slices 102 1, ..., 102_k, 102_n are transmitted via the interface 660. In the following, the interface 660 will be referred to as "profile interface" or "Pr-If ' respectively.

In response to the presence of a profile of a service type or slice 102 1, ..., 102_k, 102_n, the CPPM entity 200 will generate a new CrtPP 100 for the service type or slice 102 1, ..., 102_k, 102_n or amend an existing CrtPP 100 for the service type or slice 102 1, 102_k, 102_n.

The CPPM entity 200 will generate a new CrtPP 100 for the service type or slice 102 1, 102_k, 102_n if no CrtPP 100 for the service type or slice 102 1, 102_k, 102_n exists. For example, the CPPM entity 200 will generate a new CrtPP 100 for the service type or slice 102 1, ..., 102_k, 102_n in response to a reception of a new profile of a service type or slice 102 1, ..., 102_k, 102_n from a use case entity 651 1, 651_i, 651 _m. The new CrtPP 100 will be generated for the service type or slice 102 1, ..., 102_k, 102_n, new profile of which has been received or is present.

In case a CrtPP 100 for the service type or slice 102 1, ..., 102_k, 102_n exists and in case the profile of the respective service type or slice 102 1, ..., 102_k, 102_n, with which the CrtPP 100 is associated, has changed or has been amended respectively, the CPPM entity 200 will amend the respective existing CrtPP 100 in view of the amendments or changes in the profile of the service type or slice 102 1, ..., 102_k, 102_n. According to a further embodiment, the CPPM entity 200 is configured to examine, whether the profile of a service type or slice 102 1, ..., 102_k, 102_n has changed, i.e. has been amended. Thus, the CPPM entity 200 is configured to adapt the CrtPPs 100, managed by the CPPM entity 200, in response to amended profiles of service types or slices 102 1, 102_k, 102_n.

In case the CPPM entity 200 receives an indication that a profile of a service type or slice 102 1, ..., 102_k, 102_n has been deleted (e.g., from a use case entity 651 1, ..., 651_i, 65 l_m), the CPPM entity 200 will delete the respective CrtPP 100 associated with (e.g., generated for) the service type or slice 102 1, ..., 102_k, 102_n, profile of which has been deleted.

The one or more new CrtPPs 100, the one or more amended CrtPPs 100 and/or the indication that a profile of a service type or slice 102 1, ..., 102_k, ..., 102_n has been deleted are transmitted, according to the present embodiment, via the Pr-If 660 to the CPPM entity 200.

Any of the CrtPP 100 changes are announced by the CPPM entity 200 to the one or more CPEs 400_1 and the one or more UPEs 400_2. In this way, the one or more CPEs 400_1 and the one or more UPEs 400_2 always treat the control messages according to current specification of the CrtPPs 100, i.e. according to the current specification of the service type or slice 102 1, ..., 102_k, 102_n or its profile respectively. Fig. 7 visualizes a message exchange executed in the above discussed system as presented in Fig. 6a or 6b with regard to a control policy profile unit according to an embodiment of the present invention. With regard to the message exchange, at least one of the following two stages is executable: the configuration stage and the operational stage.

The configuration stage includes steps where the use case plane 650 and particularly the use case entities 651 1, 65 l_i, 65 l_m of the use case plane 650 indicate the configuration information for the CPPM entity 200, e.g., via the Pr-If 660 to define and/or update the one or more CrtPPs 100. This configuration information (e.g., new profiles of one or more service types or slices 102 1, ..., 102_k, 102_n, amended profiles of one or more service types or slices 102 1, 102_k, 102_n, and/or indication on deleted profiles of one or more service types or slices 102 1, ..., 102_k, 102_n) is processed at first by the CPPM entity 200. The processing comprises generation of one or more new CrtPPs 100, amending of one or more new CrtPPs 100 and/or deletion of one or more new CrtPPs 100. The one or more new CrtPPs 100 and the one or more amended CrtPPs 100 are stored by the CPPM entity 200. In a second step of the configuration stage the updated information on the CrtPPs 100 is transmitted to the one or more CPEs 400_1 and to the one or more UPEs 400_2. Thus, the one or more CPEs 400_1 and the one or more UPEs 400_2 will treat the control messages according to current specification of the CrtPPs 100, i.e. according to the current specification of the service type or slice 102 1, ..., 102_k, 102_n or its profile respectively. In the operational stage, if there are control messages that are related to a use case, i.e. that are associated with a service type or slice 102 1, ..., 102_k, 102_n with a corresponding CrtPP 100, such control messages are exchanged/communicated among CPEs 400_1 and/or between CPEs 400_1 and UPEs 400_2 following the specification or criteria established in the corresponding CrtPP 100.

Fig. 7 visualizes the execution of both the configuration stage and the operational stage.

By the arrow, leading from the use case plane 650 to the CPPM entity 200, the defining and the configuration ofthe CrtPPs 100 for the use cases 651 1, 651_i, 651_m is illustrated. For example, a profile of a use case, i.e. service type or slice 102_k may specify that any control message of the a use case, i.e. service type or slice 102_k will have the highest priority, while control messages of other use cases, i.e. service type or slice 102 1, 102_k-l , 102_k+l, 102_n will be served with lower priority. Thus, the corresponding use case entity 651_1, ..., 65 l_i, ...,. 65 l_m, which handles the profile of the use case, i.e. service type or slice 102_k, will transmit the respective information to the CPPM entity 200 via the PR-If interface 660. The CPPM entity 200 will adapt then the respective CrtPP 100 respectively. By the arrows, leading from the CPPM entity 200 to the communication network entities 400_1, 400_2, the configuration of the communication network entities 400_1, 400_2 is visualized. Any one of the communication network entities 400_1, 400_2 will receive the current one or more CrtPPs 100 from the CPPM entity 200. The current one or more CrtPPs 100 will be transmitted to the one or more CPEs 400_1 via the interface CP-If 640 and to the one or more UPEs 400_2 via the interface U2CP-If 630.

According to an embodiment, the CPPM entity 200 transmits to the communication network entities 400_1, 400_2 also a default CrtPP, which specifies the treatment of control messages that are not associated to any specific CrtPP, e.g. that refer to a use case (i.e. service type or slice) that does not have a CrtPP.

Fig. 7 shows further devices (e.g., UE - User Equipments) 700_1, ..., 700_i, ..., 700_m that belong respectively to one of use cases (i.e. service types or slices) handled by the corresponding use case entity 651_1, ..., 65 l_i, ..., 65 l_m. Each one of the devices 700_1, ..., 700_i, ..., 700_m can for instance requests new flows at one of the UPEs 400_2, as shown by the dashed arrows leading from the devices 700_1, ..., 700_i, ..., 700_m to the left UPE 400_2 in Fig. 7. Before sending the control messages associated with such requests, the UPE 400_2 that received the requests will check if the requests are associated with use cases having a specific CrtPP 100 configured at said UPE 400_2. Then, in a next step the UPE 400_2 will send control messages, associated with the requests, to the CPE 400_1, with which the UPE 400_2 is connected (see in Fig. 7 the arrow leading from the left UPE 400_2 to the left CPE 400_1). Each one of the control messages is then transmitted from the UPE 400_2 to the CPE 400_1 according to the respective CrtPP 100, associated with the use case (i.e. service type or slice) of the respective device 700_1, ..., 700_i, ..., 700_m, request of which is handled in the control message.

As soon as the requests arrive at the CPE 400_1, the requests will be treated also according with the same CrtPP 100 used by both CPE 400_1 and UPE 400_2.

Further, the CPE 400_1 that received the control messages associated with the requests interacts with further CPEs 400_1 by transmitting the information on the requests to the further CPEs 400_1 (see in Fig. 7 the arrow leading from the left CPE 400_1 to the right CPE 400_1). All communication of the control messages between the CPEs 400_1 is executed according to the respective CrtPPs 100.

Once all control messages are exchanged among the CPEs 400_1, the data plane for the data traffic requested in the requests will be established by executing a

corresponding communication among the UPEs 400_2 (see in Fig. 7 the arrow leading from the left UPE 400_2 to the right UPE 4002), which is generally known. The communication among the UPEs 400_2, however, is executed independently of the corresponding CrtPPs 100, i.e. by disregarding the CrtPPs because CrtPPs 100 are relevant for the transmission of control messages only (i.e. messages transmitted in the control plane 610 (i.e. among the entities 400_1 of the control plane 610) and messages transmitted between the control plane 610 and the user plane 620 (i.e.

between the entities 400_1 of the control plane 610 and the entities 400_2 of the user plane 620). Fig. 8 shows an implementation of the present invention in an evolved packet core

(EPC) architecture according to an embodiment of the present invention. In Fig. 8, the CPPM entity (see above described CPPM entity 200) is logically centralized inside the 3 GPP Policy Control and Charging (PCC) Framework, which is generally known and therefore not explained in further detail. In the following, only the changes implemented according to the present invention according to the present embodiment will be explained in more detail. In Fig. 8, the conventional connections, which are not amended by implementing the present invention according to the present embodiment, are represented by dashed lines. The conventional interfaces, which are not amended by implementing the present invention according to the present embodiment, are indicated by their usual names that are well known.

According to the present embodiment, the CPPM entity is included as a new entity in the PCC logical framework.

The SPR (subscription policy repository) entity of PPC framework is enhanced so that it will also store the information about which kind of control plane differentiation requirements are associated with types of subscriptions. For instance, the SPR in addition to storing pure subscriber information will store also the class of the subscriber's services, e.g., uRLLC (ultra-reliable and low latency communications), eMBB (enhanced mobile broadband), mMTC (massive machine type communications), etc. To these classes of subscribers there is the specification of which control plane differentiation should be applied per class of subscriber. Thus, the SPR is implemented as a use case entity 651_1, ..., 651_i, 65 l_m of the use case level 650 that provides profiles of different service types and/or slices.

The Pr-If interface 660 is added between the CPPM and SPR, so that the information about the requirements for handing the control plane traffic of the classes of subscribers is propagated from the SPR to the CPPM entity.

The following entities are arranged such that they represent the EPCs 400_1 of the control plane 610 of the present invention and thus execute the functions of the EPCs 400_1 described herein: MME (mobility management entity), SGW (serving gateway), and PGW (packed data network gateway). Thus, the exchange of control messages among these entities, i.e. among MME, SGW and PGW will be done according to the CrtPP policies 100 distributed by the CPPM entity 200 to all CPEs 400_1 (i.e. MME, SGW and PGW) via the CP-If interface 640 specified herein. The eNB entity is arranged as the UPE 400_2 described herein and thus executes the functions of the UPE 400_2 described herein. Hence, also the eNB can differentiate, when necessary, the control traffic, e.g. the control messages that it sends to the MME to trigger the control plane procedures for keeping the connectivity of the UE (user equipment), such as attachment, service request, mobility, etc. Because, according to the present embodiment, the CPPM entity 200 is centralized at the PCC framework, interfaces CP-If 640 and U2CP-If 630 are added as shown in Fig. 8. Particularly, the following new interfaces are added:

• New interfaces to implement the functionalities of the CP-If interface 640:

o MME-CP-If: Interface that implements the CP-If 640 between the

MME and the CPPM entity 200.

o SGW-CP-If: Interface that implements the CP-If 640 between the SGW and the CPPM entity 200.

o PGW-CP-If: Interface that implements the CP-If 640 between the PGW and the CPPM entity 200.

New interface to implement the functionalities of the U2CP-If interface 630:

o eNB-U2CP-If: Interface that implements the U2 CP-If 630 between the eNB and the CPPM entity 200.

According to the present embodiment a label-based CrtPP policy 100 is used for the differentiation of control plane traffic. Thus, the treatment of control messages is based on the label based mechanism. For this purpose, a new identifier for control plane differentiation named Control Plane QoS Class Identifier (CP-QCI) can be used. The one or more CrtPPs 100 of the present embodiment will specify (e.g. via the specification 100) that the CP-QCI is to be used for the treatment of the control messages, and the control messages will be transmitted such that they comprise the

CP-QCI. According to the present embodiment, the CP-QCI also specifies at least one of the following: (a) priority; (b) packet delay budget; and (c) packet error loss rate. All communication network entities 400, 400_1, 400_2, i.e. MME, SGW and PGW as CPEs 400_1 and eNB as UPE 400_2 will have a mapping table containing the CrtPP 100, which in the label-based type of CrtPP policy 100 contains the following fields:

IDs used to analyze the type of control traffic label to be used CP-QCI

treatment to be applied

Subscriber class ID identifying Optionally, it can CP-QCI class user/device (or group also be considered of users/devices) the slice ID to which

traffic; the user/device

belongs to

This table with CrtPP policies is used in the following ways:

When a CPE 400_1 or a UPE 400_2 needs to generate a control message, the CPE 400_1 or the UPE 400_2 firstly checks the identifiers to match into a CP-QCI class (as exposed in the table above), secondly defines the CP-QCI for the given control message to be generated, and thirdly marks the control message with the transport information that corresponds to the treatment of the CP-QCI class.

When a CPE 400_1 or a UPE 400_2 receives a control message, the CPE 400_1 or the UPE 400_2 will process such messages according to the priority queues defined by the CP-QCI associated with the control plane packet.

Fig. 9 shows a further implementation of the present invention in an evolved packet core (EPC) architecture according to an embodiment of the present invention. In the present embodiment, the CPPM entity functionalities are split between the MME and PCC. In Fig. 9, the conventional connections, which are not amended by implementing the present invention according to the present embodiment, are represented by dashed lines. The conventional interfaces, which are not amended by implementing the present invention according to the present embodiment, are indicated by their usual names that are well known.

The goal of the present embodiment is to reduce the amount of interfaces. This means that, instead of creating new interfaces, as in the embodiment of Fig. 8, existing interfaces are extended.

Similarly to the embodiment of Fig. 8, also in the present embodiment, MME, SGW and PGW are implemented as EPCs 401 1 and the eNB is implemented as UPC 401_2. Further, also according to the present embodiment, the CPPM entity 200 is placed as a new entity inside the PCC framework, and the implementation of the Pr-If 660, between CPPM entity 200 and SPR remains the same as explained in the embodiment of Fig. 8. The main difference among the embodiments of Fig. 8 and Fig. 9 resigns in how the CP-If 640 and U2 CP-If 630 are implemented and in the effect on

functionalities of the CPPM entity 200.

According to the present embodiment, the CPPM entity 200 receives the CrtPP policies 100 from the SPR and is responsible for: (a) interacting with PGW, via PGW- CP-If 640 (exactly as described in the embodiment of Fig. 8); and (b) delegating to the MME via the new interface MME-CP-If 640 the tasks of distributing and managing the CrtPP policies to the SGW as well as to the eNB. This means that the MME is used as a proxy by the CPPM to reach out both SGW and eNB because the MME has already defined, i.e. well established and known control interfaces towards these entities. Therefore, in this embodiment the following interfaces are extended to enable the management of control plane differentiation:

• MME-CP-If 640 between MME and CPPM 200: This interface, as defined in the embodiment of Fig. 8, performs the same functionalities of enabling the CPPM entity 200 to configure and manage the CrtPP policies 100 in the MME as a CPE 400_1. In addition, this interface is extended to support the

CPPM 200 to delegate the MME to act as a proxy for the CPPM, enabling the MME to configure and manage the CrtPP policies 100 in the SGW and in the eNB. Another functionality of the MME-CP-If 640, is to allow the MME to report the status of the CrtPP policies 100 (from itself, and from eNB and SGW) back to the CPPM entity 200.

• eS 11 representing an enhanced S 1 1 : In addition to support the current control functionalities of current Sl l interface as generally known (e.g., control procedures between MME and SGW), the conventional Sl l interface is extended according to the present embodiment to support also the functionalities defined in the interface 640. This way, via eS 1 1 the

MME can interact with the SGW to configure and manage the CrtPP policies 100.

• eS 1 -MME representing an enhanced S 1 -MME: The S 1 -MME interface is extended in order to support also the functionalities defined in the interface U2CP-If 630. Therefore, via eSl-MME interface the MME can interact with the eNB to configure and manage the CrtPP policies 100.

Similarly to the embodiment of Fig. 8, also in the present embodiment label-based CrtPP policies 100 are used for differentiating control messages, and the same mechanism of CP-QCI as defined above with regard to the embodiment of Fig. 8 is used also here.

Fig. 10 shows an implementation of the present invention in software-defined networking (SDN) architecture according to an embodiment of the present invention. Particularly, Fig. 10 illustrates an embodiment for CP differentiation for SDN, considering OpenFlow (OF) as the SDN technology. As generally known, OpenFlow (OF) is a communications protocol that gives access to the forwarding plane of a network switch or router over the network. The following changes and extensions of conventional components are introduced in the conventional SDN architecture according to the present embodiment:

• The CPPM entity 200 is a new entity belonging to the Control Plane (CP) Logical Architecture.

· SDN Apps will interact with the CPPM entity 200 via Pr-If 660 in order to indicate which kind of CrtPP policies 100 should be applied for the treatment of the control plane traffic, i.e. control messages associated with such SDN Apps.

• The Controller Core Architecture is extended with a CPE 410 1. This CPE 410 1 will interact with:

o CPPM entity 200 via the CP-If 640 in order to retrieve, configure, and manage the CrtPP policies 100 at the controller core level; o Flowpath Request Processing function or entity inside the Controller Core Architecture, so that whenever an OF control message related to flowpath setup needs to be sent to the OF Switch, it is sent according to the CrtPP 100 of the SDN Apps related to the need to setup a flowpath; o Controller-Switch (C-S) Channel Manager function or entity inside the Controller Core Architecture, so to enable the enforcement of the CrtPP 100 in messages arriving from the switches and leaving the controller. The CrtPP policy in this embodiment is channel-based and it will be detailed in the sequence.

From the point of view of the data plane, extensions are introduced in order to support the proper operation of OF switches according to the control plane differentiation of the present invention. There is no standardized architecture for an OF switch, however, it is expected that such architecture needs to process control messages that arrive or are transmitted to the SDN Controller (Control Message Processing function illustrated in Fig. 10), as well as, there must be a function responsible for managing the OF channels open between a OF switch and a SDN Controller (or multiple controllers), as depicted in Fig. 10 by the Switch-Controller (S-C) Channel Manager function. The following extension is included inside a OF switch architecture according to the present embodiment:

• An UPE 401_2 is added inside the OF switch architecture. The UPE 401_2 will interact indirectly with the CPPM entity 200 via U2CP-If 630. The interaction is indirect because the U2CP-If 630 is actually connected to the Control Message Processing function or entity inside the OF Switch. As it will be explained later, we extended OF protocol in order to include new control messages sent from the CPPM entity 200 to the OF switch in order to indicate which kind of channel-based CrtPP 100 should be established between the OF switch and the control plane to enable the treatment of OF packets generated (or traversing a chain of OF switches) with the appropriated control plane (i.e. control message) differentiation. Therefore, the first function or entity inside the OF switch to handle an OF message is the Control Message Processing function or entity, that will verify the type of the OF message, and only the new types of OF messages introduced in this invention will be processed by the UPE 401_2.

According to the present embodiment considers the channel-based mechanism is implemented for treating the CrtPPs 100. This means that the differentiation is enforced via the channel connecting the CPE entities (e.g., distributed controllers that need to coordinate their operations) or UPE entities communicating with CPE entities. In OpenFlow standard, controller and OF switch establish TCP channels for their control plane communication. Here, the possibility of opening auxiliary channels between controller and OF switch is used. These auxiliary channels will be open according with the channel-based CrtPP policies 100 defined, and exemplified in the following. The CrtPP 100 defines the types of channel parameters to be configured for the auxiliary connections established between controller and OF switch. Examples of these parameters for auxiliary TCP connections are:

• Size of receiving and sending buffers

• Number of packets in the global input queue

• Prioritization of low latency in operation of channel

• Prioritization of throughput in operation of channel

· Compact or not small messages in the same packet (TCP CORK)

• Defined TCP congestion algorithm

• Allowed node delay for sending any kind of message (TCP_NODELAY)

In the following, an example of a channel based CrtPP 100 is provided, i.e. the following can be specified in the CrtPP 100:

{ "SDNAppID": "MBB",

"Channel" {

{

"ChanelProtocol": "TCP",

"Options": {

"GlobalQueueSize": 1000,

"LowLatency": True,

"NoDelay": True,

... } ,

}

"SDNAppID": "BestEffort",

"Channel" {

{

"ChannelProtocol": "TCP",

"Options": {

"LowLatency": False,

"NoDelay": False, }

} }

The CP -If 640 is implemented to configure the CPE 400 1 inside the controller core architecture essentially to manage how messages sent from the controller are mapped into the differentiated channels and transmitted to the OF switches. The type of OF messages that have a relationship with SDN Apps, are the ones associated with flowpath setup. Therefore, when the flowpath request processing function or entity receives a message, it first checks via the CPE 400_1, which has a table mapping between the SDN App type and the type of control plane channel to be used by such SDN App according to the CrtPP 100, what is the channel to be used; only then the message will be transmitted in the appropriated channel.

The U2CP-If 630 is implemented as the mechanism used by the controller to indicate to the OF switch which kind of auxiliary channels should be opened with specific requirements, to assure the control traffic (i.e. control message) differentiation required by a certain SDN App. According with the OF specification, OF switches initiate the establishment of auxiliary channels. According to the present embodiment, the CPPM entity 200 is supported to send to the UPC 400_2 inside the OF Switch, which kind of CrtPP 100, i.e., which kind of auxiliary channels should be opened. Two exemplary alternatives of extending OpenFlow in order to implement the U2CP-If 630 are provided in the following and are as follows:

The first alternative for U2CP-If 630 implementation maintains the number and types of OF messages, however, the fields of the OFPT_SET_CONFIG message are extended in order to include the new data type OFP_CHANNEL_FLAGS, which encloses the parameters that define a CrtPP policy related to an auxiliary channel to be established. An exemplary extension of the data structure OFP SWITCH CONFIG that is used when the OFPT_SET_CONFIG type of message is sent from the controller to the Switch is as follows: /* Switch configuration */

struct ofp_switch_config {

struct ofp header header;

struct ofp channel flags channel flags

uintl6_t flags; /* Bitmap of OFPC_" flags. */

uintl6 1 miss_send_len; /* Max bytes of packet that datapath should send to the controller. See ofp controller max len for valid values. */

} ;

The new data structures needed to the defined in order to allow the extension of the

OFPT_SET_CONFIG message are, for example, as follows:

First example of a data structure specifying channel configuration capabilities:

/*Channel Configuration capabilities. */

struct ofp_channel_flags {

uintl6_t channeljype; /* Bitmap of ofp_channel_types. */

struct ofp channel options /* Bitmap of OFP CHOPT *.*/

}

Second example of a data structure specifying configurable channel types enum ofp_channel_types {

OFPC_TCP = 0,

OFPC UDP = 1 « 0,

OFPC_TLS = 1 « 1,

OFPC DTLS = 3,

Third example of a data structure specifying channel configuration capabilities struct ofp_channel_options {

uint8_t tcp_nodelay,

uint32_t recv_buffer_size,

uint32 t send buffer size, uint8_t tcp_cork,

} ; The second alternative for U2CP-If 630 implementation defines the new type of OF messages. This new type of OF message is called OFPT_SET_CHANNEL_CONFIG and it is illustrated in the following. The OF standard defines the types of OF headers (i.e., messages) in the OFP_TYPE data structure. A new type called OFPT_SET_CHANNEL_CONFIG is defined. After this, the new message itself is defined that is represented by the data structure OFP_CHANNEL_CONFIG. The CPPM entity 200, thus, uses this message to send the CrtPP 100 which is enclosed in the OFP_CHANNEL_FLAGS data structure which was defined above.

In the following, an exemplary illustration of the new type of OF message called OFPT_SET_CHANNEL_CONFIG is provided: enum ofp_header {

/* Switch configuration messages. */

/* Controller/switch message */

OFPT GET CONFIG REQUEST = 7,

OFPT GET CONFIG REPLY = 8,

OFPT SET CONFIG = 9,

OFPT_SET_CHANNEL_CONFIG = 36,

}

/* Switch configuration. */

struct ofp_channel_config {

struct ofp header header;

struct ofp channel flags channel flags

} The present invention described herein allows enforcement of heterogeneous use cases (i.e. service types and/or slices) running in communication networks such as mobile core networks to be enforced not only on forwarding user plane traffic, but also on the forwarding of control plane traffic. In particular, the present invention enables a differentiation of control plane messages or control messages respectively for connectivity management of devices associated with specific requirements. Further, the present invention provides a potential to reduce the variations on the latency of connectivity management for the use cases that require control plane differentiation, such as uRLLC.

Furthermore, the present invention described herein allows an isolation of the traffic of different procedures related with connectivity management, such as attach, new flows, mobility, etc. in different channels. The present invention enables EPC to support dynamic programming of how control messages will be used by the control entities of the architecture removing the static and pre-configured values.

Additionally, the present invention enables and supports programmability of the features and options of transport level of OF channels. Particularly, the present invention enables opening sockets between controller and switch that operate according to the performance needed by the SDN Apps, and not only based on what the SDN platform demands. Further, the proposed solution can also be used for the differentiated transmission of other OF messages in both directions, i.e., controller to OF switch, and OF switch to controller. OpenFlow (OF) switches that are implemented by use of the present invention can work perfectly with the switches that are not implemented according to the present invention, e.g. conventional switches. Thus, the present invention can be utilized in a modular and flexible way.

In view of the aforesaid, an embodiment of the present invention, combinable with the further embodiments described herein, concerns a method of communication, comprising sending, to a OpenFlow (OF) switch, a configuration message comprising a header of the configuration message, a flag for message fragmentation, a size of a packet to be sent to a OpenFlow (OF) controller, and a flag of a communication channel indicating a type of the communication channel, a operation parameter that qualifies the communication channel, being used for defining the communication channel that should be used for transmissions of control plane messages between the OpenFlow controller and the OpenFlow switch. Fig. 1 1 shows an exemplary arrangement of said configuration message 1 1 according to an embodiment of the present invention. The configuration message 1 1 comprises at least the following: the header 1 11 of the configuration message 1 1, the flag 1 12 for message fragmentation, i.e. fragmentation of the configuration message 1 1, the size 113 of the packet to be sent to the OpenFlow (OF) controller, and the flag 114 of the communication channel, wherein the flag 1 14 indicates the type of said communication channel, the operation parameter 115 that qualifies said communication channel, being used for defining the communication channel that should be used for the transmissions of control plane messages between the OpenFlow controller and the OpenFlow switch.

Additionally, in view of the aforesaid, a further embodiment of the present invention, combinable with the further embodiments described herein, concerns a method of communication, comprising sending to a communication entity a configuration message comprising a parameter with a subscriber identifier, a subscriber class of service, an identification of a specific network the subscriber belongs to, and an identification of a control plane quality of service label, indicating quality of service for control messages associated with the subscriber identifier, class, and a network ID being used to label all control messages generated and transmitted by the communication entity. The communication entity is, according to an embodiment of the present invention, a session and mobility management entity, a control gateways, or an access point. Fig. 12 shows an exemplary arrangement of said configuration message 12 according to an embodiment of the present invention. The configuration message 12 comprises at least the following: the parameter 121 with the subscriber identifier, the subscriber class of service 122, the identification 123 of the specific network the subscriber belongs to, and the identification 124 of the control plane quality of service label, indicating the quality of service for control messages associated with the subscriber identifier, the class 125, and the network ID (identification) 126 being used to label all control messages generated and transmitted by the communication entity. As shown above, exemplary implementations of the present invention include a control plane slice implementation and a control plane function sharing with guaranteed control plane differentiation. The control plane slice implementation, as described herein, can be used to implement the slicing of control plane. The use case is thus the slice type and control traffic from the different slices is differentiated and isolated based on our solution. As to control plane function sharing with guaranteed control plane differentiation, it has been agreed in TR23.799 that control information about device location in different slices could be supported by a shared entity that manages the device location information between infrastructure and the different devices. This shared control plane function, will have to handle control traffic (about device location update) from different slices, i.e., use cases. The present invention can be applicable also to support such shared control plane function to be able to differentiate the control traffic treatment among the different slices sharing this function. For the communication purposes, different known communication standards and/or protocols can be used according to the present invention.

Further, the present invention is implementable in a modular way. Thus, the embodiments described above may be combined with each other in several ways.

Thus, as shown above, the present invention relates to treatment of one or more control messages of a service type or slice in the communication network and introduces entities and messages facilitating the treatment of said control messages. The treatment of the one or more control messages is executed by use of one or more control policy profile units. Any one of the one or more control policy profile units is associated with a service type or a slice and arranged to define a treatment of control messages of the service type or the slice in the communication network, wherein a control message of the service type or slice is a control message generated with regard to the service type or the slice.

The invention has been described in conjunction with various embodiments herein. However, other variations to the enclosed embodiments can be understood and effected by those skilled in the art and practicing the claimed invention, from a study of the drawings, the disclosure and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the indefinite article "a" or "an" does not exclude a plurality. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.

Claims

1. A control policy profile unit associated with a service type or a slice and arranged to define a treatment of control messages of the service type or the slice in the communication network, wherein a control message of the service type or slice is a control message generated with regard to the service type or the slice.

2. The control policy profile unit according to claim 1, wherein the treatment of a control message of the service type or the slice comprises a generation of the control message, a transmission of the control message, a reception of the control message, and/or a processing of the control message.

3. The control policy profile unit according to any one of the preceding claims, wherein the control policy profile unit comprises a specification of the treatment of control messages of the service type or the slice in the communication network.

4. The control policy profile unit according to claim 3, wherein the treatment of the control messages of the service type or slice is based one of the following mechanisms:

a label based mechanism, according to which a label is attached to a control message of the service type or slice to be transmitted in the communication network, wherein the label identifies the control policy profile unit, which defines the treatment of the control message of the service type or slice;

a channel based mechanism, according to which one or more control channels are identified for transmitting the control messages of the service type or slice.

5. The control policy profile unit according to claim 4, wherein:

if the treatment of the control messages of the service type or slice is based on the label based mechanism, the control policy profile unit defines that the label has to comprise at least one of the following entries: a subscriber class indication; a device traffic in the communication network, with which the control policy profile unit is associated; a slice indication indicating a slice, with which the control policy profile unit is associated; a control plane quality of service, QoS, class identifier;

if the treatment of the control messages of the service type or slice is based on the channel based mechanism, the control policy profile unit defines one or more parameters specifying one or more control channels for transmitting the control messages of the service type or slice.

6. A control plane policy management entity arranged to manage one or more control policy profile units arranged according to any one of claims 1 to 5, wherein the control plane policy management entity is configured to:

generate a new control policy profile unit arranged according to any one of claims 1 to 5;

amend an existing control policy profile unit to be amended and arranged according to any one of claims 1 to 5; and/or

delete an existing control policy profile unit to be deleted and arranged according to any one of claims 1 to 5.

7. The control plane policy management entity according to claim 6, wherein the control plane policy management entity is configured to:

generate the new control policy profile unit in response to a presence of a profile of the service type or slice, with which the new control policy profile unit is associated;

amend the existing control policy profile unit to be amended in response to a presence of an amended profile of the service type or slice, with which the new control policy profile unit is associated; and/or

delete the existing control policy profile unit to be deleted in response to a presence of an indication indicating the deletion.

8. The control plane policy management entity according to claim 6 or 7, wherein the control plane policy management entity is configured to:

transmit the generated new control policy profile unit to one or more communication network entities, which is or are configured to treat control messages of the service type or slice with which the new control policy profile unit is associated; transmit the amended existing control policy profile unit to the one or more communication network entities for announcing the amended existing control policy profile unit in the communication network; and/or transmit information on the deleted existing control policy profile unit to the one or more communication network entities for announcing the deletion of the existing control policy profile unit in the communication network.

9. A control plane policy management method arranged to manage one or more control policy profile units arranged according to any one of claims 1 to 5, wherein the control plane policy management method comprises steps of:

generating a new control policy profile unit arranged according to any one of claims 1 to 5;

amending an existing control policy profile unit to be amended and arranged according to any one of claims 1 to 5; and/or

deleting an existing control policy profile unit to be deleted and arranged according to any one of claims 1 to 5.

10. A communication network entity arranged to communicate and/or to support communication with further communication network entities in a communication network, wherein the communication network entity is configured to treat one or more control messages of a service type or slice according to a control policy profile unit, wherein the control policy profile unit is arranged according to any one of claims 1 to 5.

11. The communication network entity according to claim 10, wherein the communication network entity is configured to receive a new control policy profile unit, an amended control policy profile unit and/or information on a deleted control policy profile unit, and wherein the communication network entity is configured to:

treat one or more control messages, with which the new control policy profile unit is associated, by use of the new control policy profile unit;

treat one or more control messages, with which the amended control policy profile unit is associated, by use of the amended control policy profile unit; and/or

treat one or more control messages, with which the deleted control policy profile unit is associated, by disregarding the deleted existing control policy profile unit.

12. The communication network entity according to claim 11 , wherein the communication network entity is configured to receive the new control policy profile unit, the amended control policy profile unit and/or information on a deleted control policy profile unit from a control plane policy management entity.

13. The communication network entity according to claim 12, wherein the control plane policy management entity is a control plane policy management entity according to any one of claims 6 to 9.

14. The communication network entity according to any one of claims 10 to 13, wherein the treatment of the one or more control messages comprises generation of one or more control messages, transmission of one or more control messages to one or more of the further communication network entities in the communication network, reception of one or more control messages from one or more of the further communication network entities in the communication network, and/or processing of one or more control messages.

15. A method of communication, comprising sending, to a OpenFlow switch, a configuration message comprising a header of the configuration message, a flag for message fragmentation, a size of a packet to be sent to a OpenFlow controller, and a flag of a communication channel indicating a type of the communication channel, a operation parameter that qualifies the communication channel, being used for defining the communication channel that should be used for transmissions of control plane messages between the OpenFlow controller and the OpenFlow switch.

16. A method of communication, comprising sending to a communication entity a configuration message comprising a parameter with a subscriber identifier, a subscriber class of service, an identification of a specific network the subscriber belongs to, and an identification of a control plane quality of service label, indicating quality of service for control messages associated with the subscriber identifier, class, and a network ID being used to label all control messages generated and transmitted by the communication entity.

17. A communication method arranged for supporting communication of a communication network entity with further communication network entities in a communication network, wherein the method comprises a treating of one or more control messages of a service type or slice according to a control policy profile unit, wherein the control policy profile unit is arranged according to any one of claims 1 to 5 or wherein the method further comprises steps of the method according to claim 15 or 16.