DEVICES AND METHODS FOR TIME SENSITIVE COMMUNICATION IN A COMMUNICATION NETWORK

Abstract

The disclosure relates to devices and methods for implementing an application-based quality of service notification scheme, in particular for URLLC services in a 5G communication network. According to a first aspect the disclosure relates to a method for providing a communication service in a communication network, wherein the method comprises: a network application entity providing communication service quality information, in particular a communication service quality measure value, to a network management and/or control entity of the communication network, wherein the communication service quality information is determined based on timing information.

Claims

1. A method for providing a communication service in a communication network, comprises: providing, by a network application entity, communication service quality information to a network management and/or control entity of the communication network, wherein the communication service quality information is determined based on timing information.

2. The method of claim 1, further comprises: extracting the timing information from an application layer message received from a user equipment, and determining the communication service quality information on the basis of the extracted timing information.

3. The method of claim 2, further comprises: extracting, by the network application entity, further timing information from a further application layer message received from the user equipment via a further communication path of the communication network; and the determining the communication service quality information comprises: determining the communication service quality information based on the extracted timing information and the extracted further timing information.

4. The method of claim 1, further comprises: receiving, by the network application entity, the communication service quality information from a user equipment of the communication network.

5. The method of claim 1, further comprises: receiving, by the network application entity, the timing information from a user equipment of the communication network; and determining the communication service quality information based on the received timing information.

6. The method of claim 1, wherein the communication service quality information comprises a communication service quality measure value and the providing the communication service quality information to the network management and/or control entity comprises: providing the communication service quality information to the network management and/or control entity based on comparing the communication service quality measure value to a threshold value, and wherein the threshold value is configured in advance by the network application entity.

7. The method of claim 1, comprises: providing, by the network application entity, the communication service quality information to the network management and/or control entity periodically.

8. The method of claim 1, wherein the communication service quality information comprises at least one of an end-to-end delay or a jitter of the communication service.

9. The method of claim 8, further comprises: providing, by the network application entity, at least one of a quality of service (QoS) class identifier, a session identifier or a flow identifier associated with the communications service quality information to the network management and/or control entity.

10. A method for quality of service (QoS) monitoring of a communication service in a communication network, wherein the method comprises: receiving, by a network management and/or control entity, communication service quality information from at least one of a user equipment or a network application entity of the communication network, wherein the communication service quality information is determined based on timing information; and adjusting, by the network management and/or control entity, the communication network to the QoS of the communication service based on the received communication service quality information.

11. The method of claim 10, wherein the adjusting the communication network comprises adjusting the communication network by one or more of: re-selecting at least one of a user plane function or a radio access network for an on-going communication session; selecting at least one of a new user plane function or a new radio access network for a new communication session; re-orchestrating one or more network functions; or re-configuring a semi-persistent scheduling configuration in the radio access network of the communication network.

12. The method of claim 10, further comprises: receiving, by the network management and/or control entity, at least one of a QoS class identifier, a session identifier or a flow identifier associated with the communications service quality information.

13. The method of claim 10, comprises: receiving, by the network management and/or control entity, communication service quality information periodically.

14. A method for using a communication service provided by a network application entity in a communication network, wherein the method comprises: providing, by a user equipment, communication service quality information to at least one of the network application entity or a network management and/or control entity of the communication network, wherein the communication service quality information is determined based on timing information.

15. The method of claim 14, further comprises: extracting, by the user equipment, the timing information from an application layer message received from the network application entity of the communication network; and determining, by the user equipment, the communication service quality information on the basis of the extracted timing information.

16. The method claim 15, further comprises: extracting, by the user equipment, further timing information from a further application layer message received from the network application entity via a further communication path of the communication network, wherein, the determining the communication service quality information comprises: determining the communication service quality information based on the extracted timing information and the extracted further timing information.

17. The method of claim 14, wherein the communication service quality information comprises a communication service quality measure value, wherein the providing the communication service quality information to at least one of the network application entity or the network management and/or control entity comprises: providing the communication service quality information to the at least one of the network application entity or the network management and/or control entity, based on a comparison of the communication service quality measure value to a threshold value, and wherein the threshold value is configured in advance by the network application entity.

18. The method of claim 10, comprises: receiving, by the network management and/or control entity, communication service quality information aperiodically

19. The method of claim 1, comprises: providing, by the network application entity, the communication service quality information to the network management and/or control entity aperiodically.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In the following embodiments of the disclosure are described in more detail with reference to the attached figures and drawings, in which:

[0035] FIG. 1a is a diagram illustrating a notification message and/or a notification response flow for downlink traffic implemented by embodiments of the disclosure;

[0036] FIG. 1b is a diagram illustrating a notification message and/or a notification response flow for downlink traffic implemented by further embodiments of the disclosure;

[0037] FIG. 2 is a diagram illustrating notification message and/or a notification response signaling implemented by embodiments of the disclosure for the notification message flow of FIG. 1;

[0038] FIG. 3a is a diagram illustrating a notification message and/or a notification response flow for uplink traffic implemented by embodiments of the disclosure;

[0039] FIG. 3b is a diagram illustrating a notification message and/or a notification response flow for uplink traffic implemented by further embodiments of the disclosure;

[0040] FIG. 4 is a diagram illustrating notification message and/or a notification response signaling implemented by embodiments of the disclosure for the notification message flow of FIG. 3;

[0041] FIG. 5 is a diagram illustrating a notification message flow for downlink traffic implemented by further embodiments of the disclosure;

[0042] FIG. 6 is a diagram illustrating a notification message flow for uplink traffic implemented by further embodiments of the disclosure;

[0043] FIG. 7 is a diagram illustrating a notification message flow for downlink traffic implemented by further embodiments of the disclosure;

[0044] FIG. 8 is a diagram illustrating a notification message flow for downlink traffic implemented by further embodiments of the disclosure;

[0045] FIG. 9 is a diagram illustrating notification message and/or a notification response signaling implemented by embodiments of the disclosure for the notification message flow of FIG. 8;

[0046] FIG. 10 is a diagram illustrating notification message and/or a notification response signaling implemented by further embodiments of the disclosure for the notification message flow of FIG. 8; and

[0047] FIG. 11 is a diagram illustrating a notification reporting type selection procedure implemented by embodiments of the disclosure.

[0048] In the following identical reference signs refer to identical or at least functionally equivalent features.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

[0049] In the following description, reference is made to the accompanying figures, which form part of the disclosure, and which show, by way of illustration, specific aspects of embodiments of the disclosure or specific aspects in which embodiments of the present disclosure may be used. It is understood that embodiments of the disclosure may be used in other aspects and comprise structural or logical changes not depicted in the figures. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims.

[0050] For instance, it is understood that a disclosure in connection with a described method may also hold true for a corresponding device or system configured to perform the method and vice versa. For example, if one or a plurality of specific method steps are described, a corresponding device may include one or a plurality of units, e.g. functional units, to perform the described one or plurality of method steps (e.g. one unit performing the one or plurality of steps, or a plurality of units each performing one or more of the plurality of steps), even if such one or more units are not explicitly described or illustrated in the figures. On the other hand, for example, if a specific apparatus is described based on one or a plurality of units, e.g. functional units, a corresponding method may include one step to perform the functionality of the one or plurality of units (e.g. one step performing the functionality of the one or plurality of units, or a plurality of steps each performing the functionality of one or more of the plurality of units), even if such one or plurality of steps are not explicitly described or illustrated in the figures. Further, it is understood that the features of the various exemplary embodiments and/or aspects described herein may be combined with each other, unless specifically noted otherwise.

[0051] FIG. 1a is a diagram illustrating a notification message flow implemented in a communication network 100, in particular 5G communication network 100. As will be described in more detail below, the communication network 100 comprises or is configured to serve one or more user equipment 101. The user equipment 101 is configured to use a communication service, in particular a URLLC service, provided by the communication network 100. In an example, the URLLC service can include, for instance, industrial communication services, time sensitive network (TSN) communication services, automotive (i.e. V2X or eV2X) communication services and the like. As illustrated in FIG. 1a, by using the radio resource control (RRC) layer and/or the non-access stratum (NAS) layer, the user equipment 101 is configured to communicate with the communication network 100 via a radio access network, RAN, 103 of the communication network 100.

[0052] As illustrated in FIG. 1a, an application 101a can be executed on the user equipment 101, which implements this communication service on the user equipment 101. At the application layer the user equipment 101 (more specifically, the application 101a) is configured to communicate with a network application entity configured to provide the communication service to the user equipment 101. In the embodiments shown in FIG. 1a and FIG. 1b, the network application entity is implemented as an application server 107, which executes an application 107a for providing the communication service to the user equipment 101. The application server 107 can be located in a core network 105 of the communication network 100 and/or in a cloud network in communication with the communication network 100. As will be described in more detail further below, in further embodiments of the disclosure the network application entity providing the communication service to the user equipment 101 may be implemented by an application function 105a of a core network 105 of the communication network 100.

[0053] As will be described in more detail below, the network application entity, in particular application server 107 is configured to provide communication service quality information, in particular a communication service quality measure value, to a network management and/or control entity of the communication network 100 for QoS monitoring of the communication service in the communication network 100. The network management and/or control entity is configured to receive the communication service quality information from the network application entity, in particular the application server 107 and/or from the user equipment 101 and to adjust the communication network 100 for improving the QoS of the communication service on the basis of the communication service quality information. Thus, the user equipment 101 is configured to provide the communication service quality information to the network application entity, in particular the application server 107 of the communication network 100 and/or to a network management and/or control entity of the communication network 100.

[0054] The network management and/or control entity can be a management plane entity and/or a control plane entity, e.g. implemented as a distributed entity or function having some functionality in the core network 105 and some functionality in the management plane of the communication network 100. For instance, as illustrated in FIG. 1a, the network management and/or control entity can be in an access and mobility management function (AMF) 105b, a policy and control function (PCF) 105b, a session management function (SMF) 105b or as another type of function implemented in the core network 105 of the communication network. Alternatively or additionally, as illustrated in FIG. 1b, the network management and/or control entity can be in a network function 109a in the management plane 109 of the communication network 105, such as a network slice subnet management function (NSSMF), a network slice management function (NSMF), management and orchestration (MANO), exposure governance management function (EGMF), performance management (PM); fault management (FM), configuration management (CM) and the like.

[0055] The communication service quality information can be provided in form of a notification message, as illustrated in FIG. 1a. In an embodiment, the communication service quality information can comprise, for instance, an end-to-end delay and/or a jitter of the communication service.

[0056] According to a further embodiment, the network application entity, in particular application server 107 is further configured to extract timing information, in particular one or more timestamps, from an application layer uplink message received from the user equipment 101 as part of the communication service and to determine the communication service quality information on the basis of the timing information. The timing information, in particular the timestamp can indicate, for instance, the generation time of the application layer downlink message and/or an offset value showing the execution time of the application layer downlink message, i.e. the corresponding data packet at the receiving node.

[0057] According to a further embodiment, the user equipment 101 is configured to extract this timing information, in particular the one or more timestamps, from an application layer message received from the network application entity, in particular the application server 107 as part of the communication service and to determine the communication service quality information on the basis of the timing information. Furthermore, the user equipment 101 can be configured to extract this timing information, in particular the one or more timestamps, from an application layer message received from the network application entity, in particular the application server 107, and transmit back the extracted timing information to the network application entity, in particular the application server 107, as part of the communication service, wherein the timing information can be used to determine the communication service quality information by the application server 107.

[0058] Thus, embodiments of the disclosure can relate to notification message (e.g., including the form of a request/response messaging and/or subscribe/notify messaging) inside core network CN 105, and/or management plane 109, and/or RAN 103 including, e.g., interactions with application layer as a first option, and/or RRC layer, and/or NAS layer as a second option. Embodiments of the disclosure can be based on the assumption that only application layers at the UE and at the application server are synchronized. Thus, embodiments of the disclosure may not require any additional synchronization between the UE 101 and RAN 103 or the UE 101 and CN 105 or RAN 103 and CN 105. According to embodiments of the disclosure application layer information may include timing information in the form of a timestamp showing the generation time of a corresponding packet and/or an offset value showing the execution time of the packet at the receiving node, or a timestamp showing the execution time of the packet at the receiving node. As will be appreciated, on the basis of one or more of such timestamps communication service quality measure values, such as packet jitter or end-to-end delay, can be determined. If such application layer information is used in the 5G network 100, then there may not be a need for user plane QoS monitoring mechanism at the network layer. As will be described in more detail below, embodiments of the disclosure can also relate to communication between the network application entity, in particular the application server 107, and the core network 105 of the communication network 100 and/or between the network application entity, in particular the application server 107, and the management plane 109 of the communication network 100. Such communication can be performed via currently being specified interfaces for the 5G system or possibly new interfaces that may be specified later.

[0059] As already described, FIG. 1a shows the notification message flow for the first option mentioned above, i.e., core network CN 105 and RAN 103 notification via application layer interaction, for the downlink traffic case. In this case, the UE application 101a can perform end-to-end delay and jitter measurement when it receives the packet. If the packet passes the end-to-end delay and jitter evaluation (i.e., the packet is received within the required delay and jitter threshold), it can be delivered for further processing. Meanwhile, the UE application 101a generates a notification message which informs the application server (AS) 107 about the measurement results, i.e. the communication service quality information. If the measurement result exceeds a certain threshold, this may even create a violation report with a cause. This cause could be a delay or jitter violation. Once the AS 107 receives the notification message, it passes this information to the 5G core network (5GC) 105 and radio access network (RAN) 103 over the interface provided in embodiments of the disclosure.

[0060] The threshold values (e.g., end-to-end delay per packet, jitter per packet, average end-to-end delay, average jitter, etc.) can be delivered to the UE(s) 101 beforehand by the application server 107 for each service type. The notification message can also be sent without considering any kind of threshold value and the UE 101 reports depending on the configuration by the application server 107. For example, the application server 107 may request the UE 101 to start reporting at a certain time and for certain duration.

[0061] FIG. 1b shows a further embodiment, where the application server 107 receives the notification message including the communication service quality information from the user equipment 101 and forwards this information to the network management and/or control entity implemented in form of a network function 109a in the management plane 109 of the communication network 105.

[0062] FIG. 2 shows possible notification signaling for the embodiment shown in FIG. 1a for the downlink traffic case (a similar notification signaling can be implemented for the embodiment shown in FIG. 1b). The notification message can include not only delay and jitter measurement(s), i.e. the communication service quality information, but also a QoS indication information (e.g., QoS indication can be QCI as in LTE, which may be used also in case of LTE-5G tight interworking, and/or 5QI as described in 5G system), Session ID and/or Flow ID information. When the AS 107 sends the notification message to 5GC 105 via the interface provided in embodiments of the disclosure (e.g., user plane interface or control plane interface or management plane interface), 5GC 105 may perform different operations such as User Plane Function (UPF) and/or RAN re-selection (e.g., distributed unit (DU) change, cell re-selection, handover to another cell, and beam re-selection). Furthermore, 5GC 105 may communicate this information to currently used UPF function(s) 204 and the UPF(s) 204 may check their internal schedules for this specific session/flow and may also change the internally assigned QoS indication information (e.g., QoS indication can be QCI as in LTE, which may be used also in case of LTE-5G tight interworking, and/or 5QI as described in 5G system) for the flow. Furthermore, RAN 103 and 5GC 105 can additionally generate a response message and report back to the AS 107 about what kind of actions are to be taken for the session/flow. The final response message can also be sent to the UE 101 by the application server (AS) 107 or the application function (AF) 105a.

[0063] FIG. 3a shows the uplink traffic scenario in which the AS 107 performs end-to-end delay and jitter measurement when it receives the uplink packet, i.e., the application layer message in the uplink direction. If the packet passes the end-to-end delay and jitter evaluation (i.e., the packet is received within the required delay and jitter threshold), it is delivered for further processing. Meanwhile, the AS 107 generates a notification message which informs the 5GC 105 and RAN 103 about the measurement result, i.e. the communication service quality information, over the interface. Similarly, if the measurement result exceeds a certain threshold, this may even create a violation report with a cause which could be a delay or jitter violation. Furthermore, a notification message can also be sent to the UE 101 by the AS 107 or the AF 105a as a feedback information of its uplink transmission.

[0064] Thus, according to an embodiment, the AS 107 or the AF 105a is configured to transmit a notification message including the communication service quality information to the network management and/or control entity 105b, 109a implemented in the core network 105 and/or management plane 109 of the communication network 100. Moreover, according to an embodiment, the AS 107 or the AF 105a is configured to extract timing information, in particular one or more timestamps, from an application layer uplink message received from the user equipment 101 as part of the communication service and to determine the communication service quality information on the basis of the timing information.

[0065] According to a further embodiment, the AS 107 or the AF 105a is configured to receive the timing information, e.g. the one or more timestamps from the UE 101 and to determine the communication service quality information on the basis of the timing information. In this case the timing information has been extracted by the UE 101 from an application layer message received from the AS 107 or the AF 105a as part of the communication service. In a further embodiment, the AS 107 or the AF 105a is configured to receive the communication service quality information directly from the UE 101. In this case, the UE 101 has extracted the timing information, e.g. the one or more timestamps from an application layer message received from the AS 107 or the AF 105a as part of the communication service and determines the communication service quality information on the basis of the extracted timing information.

[0066] An embodiment similar to the embodiment shown in FIG. 3a is illustrated in FIG. 3b, where the network management and/or control entity 109a is implemented as a network function 109a in the management plane 109 of the communication network 100.

[0067] FIG. 4 shows possible notification signaling for the embodiment shown in FIG. 3a for uplink traffic (a similar notification signaling can be implemented for the embodiment shown in FIG. 3b). The notification message can include not only delay and jitter measurement(s), i.e. the communication service quality information, but also a QoS indication information (e.g., QoS indication can be QCI as in LTE, which may be used also in case of LTE-5G tight interworking, and/or 5QI as described in 5G system), Session ID and/or Flow ID information. When the AS 107 sends the notification message to 5GC 105 via the interface provided in embodiments of the disclosure (e.g., user plane interface or control plane interface or management plane interface), 5GC 105 may perform different operations such as User Plane Function (UPF) and/or RAN re-selection (e.g., distributed unit (DU) change, cell re-selection, handover to another cell, and beam re-selection). Furthermore, 5GC 105 may communicate this information to the currently used UPF function(s) 204 and the UPF(s) 204 may check their internal schedules for this specific session/flow and may also change the internally assigned QoS indication information for the flow. Furthermore, RAN 103 and 5GC 105 can additionally generate a response message and report back to the AS 107 about what kind of actions are to be taken for the session/flow. The final response message can also be sent to the UE 101 by the application server (AS) 107 or the application function (AF) 105a.

[0068] FIG. 5 shows the notification message flow for the embodiment shown in FIG. 3a for downlink traffic (a similar notification signaling can be implemented for the embodiment shown in FIG. 3b). In this case, the UE application 101a can perform end-to-end delay and jitter measurement(s) when it receives the packet (either directly received from AS 107 or via the application function (AF) 105a located in 5GC 105). Similar to the previously described embodiments, the UE application 101a can perform end-to-end delay and jitter measurement(s), when it receives the packet. If the packet passes the end-to-end delay and jitter evaluation (i.e., the packet is received within the required delay and jitter threshold), it is delivered for further processing. Meanwhile, the UE application 101a generates a notification message which informs the application server (AS) 107a via the application function (AF) 105a about the measurement result, i.e. the communication service quality information, which may include a violation report with a cause. This cause could be a delay or jitter violation. Once the AF 105a receives the notification message, it directly passes this information to other 5G core network (5GC) 105 entities 105b and the radio access network (RAN) 103 over the interface provided in embodiments of the disclosure.

[0069] FIG. 6 shows the corresponding uplink traffic scenario, where the AF 105a performs the end-to-end delay and jitter measurement when it receives the uplink packet and relays the traffic to the AS 107. For further details reference is made to the description of FIG. 5 above.

[0070] FIG. 7 shows the notification message flow according to further embodiments of the disclosure. In this case, a firmware 101b can be implemented in the UE 101 which provides the notification messages to the AF 105a. Once the AF 105a receives the notification message from the UE firmware 101b, it directly passes this information to other 5G core network (5GC) 105 entities 105b and the radio access network (RAN) 103 over the interface as provided by embodiments of the disclosure.

[0071] FIG. 8 shows the notification message flow for the second option mentioned above, i.e., CN 105 and RAN 103 notification including, e.g., RRC layer and/or NAS layer interaction. In this case, when the UE application 101a generates the notification message, the message is transmitted to RRC and/or NAS layers in the UE 101 (i.e., the UE modem, as illustrated by the protocol stack shown in FIG. 8), the UE modem passes the message to the RAN 103 (e.g., via RRC layer) or to the CN 105 (e.g., via Non-Access Stratum (NAS) layer). The RAN 103 may also pass the notification message to the CN 105 over a standardized interface. Such a mechanism can be also used for uplink traffic in a way that the network 100 (i.e. RAN 103 or 5GC 105) can generate notification messages and deliver them to the UE 101 via RRC and NAS signaling.

[0072] FIG. 9 shows a possible notification message signaling for the embodiment shown in FIG. 8 considering interactions of UE with RAN and CN to provide notification information. In this case, the UE 101 can communicate with the RAN 103, e.g., over RRC messages, and the CN 105, e.g., over NAS messages, separately while providing notification information.

[0073] FIG. 10 illustrates another possible notification message signaling for the embodiment shown in FIG. 8, wherein, when the RAN 103 receives the notification message from the UE 101, it performs a local check of the session (e.g., SPS schedule checking) and also relays the notification message directly to the CN 105.

[0074] Further embodiments of the disclosure make use of multipath transmission scenarios in the communication network 100. In these multipath transmission scenarios URLLC data can be transmitted over two different communication paths (this could be also two different mobile network operator (PLMN)). Thus, according to an embodiment relating to such a multipath transmission scenario, the UE 101 can send different notification messages for each transmission path to the AS 107 or AF 105a or RAN 103. In case, both paths belong to the same session (i.e., multi-home session), then an extra identifier can be provided in addition to the session ID (e.g. path ID, UPF ID, PLMN ID).

[0075] Thus, in an embodiment, the user equipment 101 is configured to transmit at least two notification messages including the communication service quality measure information to the network application entity 107, 105a of the communication network 100 via different communication paths.

[0076] According to a further embodiment, the user equipment 101 is configured to extract further timing information, in particular a further timestamp, from a further application layer downlink message received from the network application entity 107, 105a via a further communication path and to determine the communication service quality information on the basis of the timing information and the further timing information.

[0077] Likewise, according to a further embodiment, the network application entity 107, 105a is configured to extract further timing information, in particular a further timestamp, from a further application layer uplink message received from the user equipment 101 via a further communication path and to determine the communication service quality information on the basis of the timing information and the further timing information.

[0078] According to embodiments of the disclosure, the application server 107 or application function 105a may configure the UE 101 about a certain notification type as illustrated in FIG. 11. This notification type configuration may consider an event/threshold based reporting (e.g., delay/jitter above a certain threshold) and/or a periodic or aperiodic reporting. According to embodiments the reporting may comprise: an average measured delay/jitter within a certain time period (e.g., 1 sec); a maximum measured delay/jitter within a certain time period (e.g., 1 sec); and/or a delay/jitter measurement time series per time period (e.g., 1 sec).

[0079] According to further embodiments of the disclosure, as already described above, a management and orchestration layer (M&O) can be considered. The Core Network (CN) 105 controls the short-term actions, such as UE-associated session management, while the M&O handles long-term actions. Accordingly, the notification message content can also be utilized to collect long-term statistics. That is, the notification message content can be used, e.g., for short-term actions by the network layer (i.e., CN, transport network (TN), or RAN) or can be used for long-term actions by the M&O layer 109. For example, if the delay requirements cannot be met for a time period, the M&O layer 109 may initiate a re-orchestration of the network functions (NFs) 109a. The re-orchestration may imply, e.g., instantiating a user plane function (UPF) closer to the RAN 103 such as at the edge cloud or radio cloud, instead of at the central cloud. An M&O layer decision can be providing different requirements to the transport network (TN), e.g., in terms of delay budget. Another M&O decision could be slice re-configuration such that different delay budgets are distributed to the domains of the network layer (such as CN, TN, RAN). The access network (AN) can comprise 3GPP-based RAN or non-3GPP based AN, such as Wi-Fi network or private LAN.

[0080] As already described above in the context of FIG. 1b, the M&O layer 109 can contain 3GPP-defined functions, e.g., communication service management function (CSMF), network slice management function (NSMF), network slice subnet management function (NSSMF), management data analytics function (MDAF), as well as the ETSI Network Function Virtualization (NFV) defined functions needed for network function (NF) orchestration. Open-source functions can also be part of the M&O layer, such as open network automation platform (ONAP). The notification message content can thus be utilized by the data analytics functions (e.g., Network Data Analytics Function (NWDAF) in the CN and MDAF in the M&O) from which the analytics could be used by control functions in the network layer (e.g., SMF) and management functions in the M&O layer 109 (e.g., performance management, PM). Also, the analytics can be shared among such functions. For example, the notification message content can be utilized to generate analytics by the NWDAF which may be shared with the MDAF in the M&O layer 109. Accordingly, the decision on the control or management can be taken jointly by CN 105 and M&O 109. The analytics generated by such analytics functions can also be used in the new slice set-up. The analytics may be generated by, e.g., machine learning (ML) or artificial intelligence (AI) designs.

[0081] The notification message content may be also directly shared with the M&O 109 via, e.g., Application APIs through network exposure function or monitoring in the application (e.g., tenant, customer, or enterprise) or in the life-cycle management (LCM) function in the application. The level of actions considering the analytics or notification message content can be also mid-term, such as re-configuration of the semi-persistent scheduling (SPS) configuration.

[0082] While a particular feature or aspect of the disclosure may have been disclosed with respect to only one of several implementations, such feature or aspect may be combined with one or more other features or aspects of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms “include”, “have”, “with”, or other variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprise”. Also, the terms “exemplary”, “for example” and “e.g.” are merely meant as an example, rather than the best or optimal. The terms “coupled” and “connected”, along with derivatives may have been used. It should be understood that these terms may have been used to indicate that two elements cooperate or interact with each other regardless whether they are in direct physical or electrical contact, or they are not in direct contact with each other.

[0083] Although specific aspects have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a variety of alternate and/or equivalent implementations may be substituted for the specific aspects shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the specific aspects discussed herein.

[0084] Although the elements in the following claims are recited in a particular sequence with corresponding labeling, unless the claim recitations otherwise imply a particular sequence for implementing some or all of those elements, those elements are not necessarily intended to be limited to being implemented in that particular sequence.

[0085] Many alternatives, modifications, and variations will be apparent to those skilled in the art in light of the above teachings. Of course, those skilled in the art readily recognize that there are numerous applications of the disclosure beyond those described herein. While the present disclosure has been described with reference to one or more particular embodiments, those skilled in the art recognize that many changes may be made thereto without departing from the scope of the present disclosure. It is therefore to be understood that within the scope of the appended claims and their equivalents, the disclosure may be practiced otherwise than as specifically described herein.