EP4736382A1 - Predicting conflicting communication parameters in a wireless communication network - Google Patents

Abstract

Various aspects of the present disclosure relate to provided a method at a node of a wireless communications platform, the method comprising: obtaining a requirement for configuring a communication parameter from at least one external application; detecting a trigger to evaluate a potential conflict condition, the trigger determined based on the obtained requirement; requesting analytics information to support evaluating the potential conflict condition, wherein the analytics information relate to detecting conflict for the obtained requirement; receiving analytics information; detecting a potential conflict condition based on the received analytics; and notifying the potential conflict condition to the at least one external application.

Description

PREDICTING CONFLICTING COMMUNICATION PARAMETERS IN A WIRELESS COMMUNICATION NETWORK

TECHNICAL FIELD

[0001] The subject matter disclosed herein relates generally to the field of predicting conflicting communication parameters in a wireless communication network. This document defines a node of a wireless communications platform, a method performed in a node of a wireless communications platform, an analytics entity, and a method performed by analytics entity.

BACKGROUND

[0002] A wireless communications system may include one or multiple network communication devices, such as base stations, which may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers, or the like). Additionally, the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G)).

SUMMARY

[0003] An article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’ or “one or both of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0004] Accordingly, there is provided a node of a wireless communications platform, the node comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the node to: obtain a requirement for configuring a communication parameter from at least one external application; detect a trigger to evaluate a potential conflict condition, the trigger determined based on the obtained requirement; request analytics information to support evaluating the potential conflict condition, wherein the analytics information relate to detecting conflict for the obtained requirement; receive analytics information; detect a potential conflict condition based on the received analytics; and notify the potential conflict condition to the at least one external application.

[0005] There is further provided a method at a node of a wireless communications platform, the method comprising: obtaining a requirement for configuring a communication parameter from at least one external application; detecting a trigger to evaluate a potential conflict condition, the trigger determined based on the obtained requirement; requesting analytics information to support evaluating the potential conflict condition, wherein the analytics information relate to detecting conflict for the obtained requirement; receiving analytics information; detecting a potential conflict condition based on the received analytics; and notifying the potential conflict condition to the at least one external application.

[0006] There is further provided an analytics entity comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the analytics entity to: receive a request from a wireless communications platform, the request for analytics information to support evaluating a potential conflict condition, wherein the analytics information relate to detecting conflict for a requirement; and send analytics information to the wireless communications platform in response to the request.

[0007] There is further provided a method at an analytics entity, the method comprising: receiving a request from a wireless communications platform, the request for analytics information to support evaluating a potential conflict condition, wherein the analytics information relate to detecting conflict for a requirement; and sending analytics information to the wireless communications platform in response to the request.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 illustrates an example of a wireless communications system in accordance with aspects of the present disclosure.

[0009] Figure 2 illustrates an example of a conflict management function in accordance with aspects of the present disclosure.

[0010] Figure 3 illustrates an example of an SA6 SEAL implementation in accordance with aspects of the present disclosure.

[0011] Figure 4 illustrates an example of SA6 EDGEAPP implementation in accordance with aspects of the present disclosure

[0012] Figure 5 illustrates an example of a user equipment (UE) 500 in accordance with aspects of the present disclosure.

[0013] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure.

[0014] Figure 7 illustrates an example of a network equipment (NE) 700 in accordance with aspects of the present disclosure.

[0015] Figure 8 illustrates a flowchart of a method performed by a NE in accordance with aspects of the present disclosure.

[0016] Figure 9 illustrates a flowchart of another method performed by a NE in accordance with aspects of the present disclosure. DETAILED DESCRIPTION

[0017] The inventors have identified that current network architecture needs to be enhanced to support efficient conflict management to guarantee fulfilling the service agreements assuming multiple stakeholders involved. This may require extensive and sophisticated use case analysis and what-if scenario testing based on customer needs. This will increase the complexity of the system since it will require real time measurements and simulating different environments continuously so as to allow sufficient testing of the expected performance and capturing worst-case scenarios.

[0018] A problem addressed by the present disclosure is that of how to efficiently resolve potential resource conflicts which may be caused by network/service capability exposure requirements from different 3rd party consumers (servers or applications of the UEs). In particular, how to ensure the capability exposure requirements of different consumers with similar requests are fulfilled.

[0019] There is provided herein a new capability for predicting conflicting communication parameters. Such conflicting communication parameters may comprise third-party application service requirements, where the service requirements relate to network services, wherein the network services can be control plane (RAN or Core Network) services, management plane service, application enablement services or device application services. The conflict results to the possible failure of meeting the application service requirements (or the stretching of network resources to accommodate all requests), whereas the requirements can be either policies or communication parameters provisioning/adaptation. One example of communication parameters provisioning/adaptation can be the V2X service provisioning QoS policies for sidelink communications. Such policies can be provided by the application server or the core network, and sidelink resource conflicts in a given area due to high load may result to performance degradation for the end users. Such performance degradation could result in system performance falling short of critical requirements for a particular application, for instance for traffic safety applications.

[0020] Aspects of the present disclosure are described in the context of a wireless communications system. [0021] Figure 1 illustrates an example of a wireless communications system 100 in accordance with aspects of the present disclosure. The wireless communications system 100 may comprise one or more wireless communications platforms. The wireless communications system 100 may include one or more Network Equipment (NE) 102, one or more UE 104, and a core network (CN) 106. The CN 106 may be implemented by way of at least one NE 102. The NE 102 may comprise a base station, for example a gNB. The one or more NE 102 may embody at least one of an application enablement layer, an edge enablement layer a service or a functionality. Such a layer is part of the system and may be implmented with the CN 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE- Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a NR. network, such as a 5G network, a 5 G- Advanced (5G-A) network, or a 5G ultrawideband (5G-UWB) network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20. The wireless communications system 100 may support radio access technologies beyond 5G, for example, 6G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0022] The one or more NE 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the NE 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a network function, a network entity, a radio access network (RAN), a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. An NE 102 and a UE 104 may communicate via a communication link, which may be a wireless or wired connection. For example, an NE 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface. [0023] An NE 102 may provide a geographic coverage area for which the NE 102 may support services for one or more UEs 104 within the geographic coverage area. For example, an NE 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, an NE 102 may be moveable, for example, a satellite associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas may be associated with different NE 102.

[0024] The one or more UE 104 may be dispersed throughout a geographic region of the wireless communications system 100. A UE 104 may include or may be referred to as a remote unit, a mobile device, a wireless device, a remote device, a subscriber device, a transmitter device, a receiver device, or some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, the UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or machine-type communication (MTC) device, among other examples.

[0025] A UE 104 may be able to support wireless communication directly with other UEs 104 over a communication link. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehi cl e-to- vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link 114 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0026] An NE 102 may support communications with the CN 106, or with another NE 102, or both. For example, an NE 102 may interface with other NE 102 or the CN 106 through one or more backhaul links (e.g., SI, N2, N2, or network interface). In some implementations, the NE 102 may communicate with each other directly. In some other implementations, the NE 102 may communicate with each other or indirectly (e.g., via the CN 106. In some implementations, one or more NE 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs).

[0027] The CN 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The CN 106 may be an evolved packet core (EPC), or a 5G core (5GC), which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management functions (AMF)) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.) for the one or more UEs 104 served by the one or more NE 102 associated with the CN 106.

[0028] The CN 106 may communicate with a packet data network over one or more backhaul links (e.g., via an SI, N2, N2, or another network interface). The packet data network may include an application server. In some implementations, one or more UEs 104 may communicate with the application server. A UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the CN 106 via an NE 102. The CN 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server using the established session (e.g., the established PDU session). The PDU session may be an example of a logical connection between the UE 104 and the CN 106 (e.g., one or more network functions of the CN 106).

[0029] In the wireless communications system 100, the NEs 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communications). In some implementations, the NEs 102 and the UEs 104 may support different resource structures. For example, the NEs 102 and the UEs 104 may support different frame structures. In some implementations, such as in 4G, the NEs 102 and the UEs 104 may support a single frame structure. In some other implementations, such as in 5G and among other suitable radio access technologies, the NEs 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures). The NEs 102 and the UEs 104 may support various frame structures based on one or more numerologies.

[0030] One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix. A first numerology (e.g., /t=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., /t=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., //=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., g=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerology (e.g., /t=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth numerology (e.g., /t=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0031] A time interval of a resource (e.g., a communication resource) may be organized according to frames (also referred to as radio frames). Each frame may have a duration, for example, a 10 millisecond (ms) duration. In some implementations, each frame may include multiple subframes. For example, each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.

[0032] Additionally or alternatively, a time interval of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may include a number (e.g., quantity) of slots. The number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100. For instance, the first, second, third, fourth, and fifth numerologies (i.e., /t=0, jtz=l, =2, jtz=3, =4) associated with respective subcarrier spacings of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and 16 slots per subframe, respectively. Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of slots for a subframe may depend on a numerology. For a normal cyclic prefix, a slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing), a slot may include 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for a normal cyclic prefix and an extended cyclic prefix may depend on a numerology. It should be understood that reference to a first numerology (e.g., /t=0) associated with a first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and slots.

[0033] In the wireless communications system 100, an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc. By way of example, the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, the NEs 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands. In some implementations, FR1 may be used by the NEs 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data). In some implementations, FR2 may be used by the NEs 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.

[0034] FR1 may be associated with one or multiple numerol ogies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology (e.g., /t=0), which includes 15 kHz subcarrier spacing; a second numerology (e.g., //=1), which includes 30 kHz subcarrier spacing; and a third numerology (e.g., //=2), which includes 60 kHz subcarrier spacing. FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies). For example, FR2 may be associated with a third numerology (e.g., /z=2), which includes 60 kHz subcarrier spacing; and a fourth numerology (e.g., /t=3), which includes 120 kHz subcarrier spacing. [0035] Beyond the era of 5G wireless communication networks, the notion of “system” will consist of multiple segments and will see the traditional network as a pipe consisting of commodity hardware/software. This may comprise RAN, TN, CN as well as the edge cloud/cloud / application enablement domains for the e2e User Plane (UP), whereas the control and management plane can be unified and will consist of virtualized services which will be deployed within the access and core network domains and will be able to be exposed to the vertical customer, to allow him optimize end to end the service he offers to his subscribers.

[0036] The parties involved in the operation of such a system will be also increased as compared to today. Further, there will be numerous stakeholders involved at developing/producing the platform capabilities within this extended system and these stakeholders may span the vertical domain, the edge/regional/core cloud provider domain, as well as API/SDK 3rd party providers.

[0037] In such extension of the system, the set of problems faced by such wireless communication networks will be extended too. Such problems may relate to edge/cloud resource management / control, selecting the best DN for the application, application portability/migration aspects, extension of slicing to cover the edge/vertical cloud components, trusted application-to-application interactions, etc.

[0038] One challenge in this direction is the need for testing and verifying new services that span across different domains and for evaluating the impact on the different part of the system. Also, the pro-active monitoring of events related to different parts of the system (device, RAN, Transport Network, CN, edge Data Network (DN), regional or cloud DN, middleware) may help solve some issues. However such operation will present significant complexity to the different stakeholders and will require a level of coordination/orchestration as well as negotiations between the players involved.

Furthermore, a vertical customer will need extensive testing before using 5G access for critical operations and backup access networks to be available for critical services / redundancy may be essential.

[0039] One possible issue in the case of multiple telco services which are provided by different stakeholders (e.g. MNO, ECSP, ASP) and exposed at the finer granularity (e.g. as microservices) is the fact that possible conflicts may occur since one or more telco services may affect the same telco resources.

[0040] Resources are defined herein may comprise any combination of radio resources or network resources or QoS profiles or management resources or slice resources or computational resources at the telco edge or cloud.

[0041] A conflict as defined herein may be expected to happen either directly or indirectly or implicitly when two or more consumers perform network API invocations to request to affect the same telco resources. The consumers can request the same telco service or different service which may share some dependencies with respect to the affected telco resources.

[0042] For the above definition of conflict and resources, the conflict management is a task of significant importance since the producer of a network service needs to accommodate the requests from multiple consumers in a timely manner (according to applicable Service Level Agreements (SLAs)). There are some cases where this is a challenging task.

[0043] For example, multiple application servers (e.g. vertical servers, ASPs servers (e.g gaming servers), edge/cloud providers’ servers) or even application clients (in case of SNA) may request from the 5GS (core network, enablement layer) to consume a service via NEF/OAM/Enablement layer APIs. Multiple requests may target the same network resources, and the uncoordinated authorization and triggering of such requests may lead to conflicts, which need to be solved either via some prioritization of requests (e.g. VIP users,..) or via some conflict management logic at the service/API provider domain. One example of such potential conflict can be a slice modification trigger (different parameters to change) which is provided by more than one VAL server to SEAL NSCE, and SEAL NSCE needs to select which policy to apply. Another example is conflicting URSP rule guidance by different AFs (from different applications of the UE).

[0044] Figure 2 illustrates an example of a conflict management function in accordance with aspects of the present disclosure. An exposure Exposure Gateway 224 may comprise a Netwrok Exposure Function (NEF), an Exposure governance management function (EGMF), a Common API Framework (CAPIF), or an Enabler. The Exposure Gateway 224 includes a conflict management function which is arranged to identify conflicts on requests and check conflict mitigation. The Exposure Gateway 224 communicates with at least one Network Service Provider. Such Network Service Providers may comprise a Network Service Provider #1 (NF) 252; a Network Service Provider #2 (MnS producer) 254; and a Network Service Provider #3 (SEAL/EES) 256. The Exposure Gateway 224 may use a plurality of API invokers to communicate with a plurality of consumers. Such consumers may comprise, for example: Global AF #1, 261; Edge AF #2, 262; Vertical App Server #x, 263; App @UE #1, 264; and App @UE #2, 265.

[0045] Accordingly, the inventors have identified that current network architecture needs to be enhanced to support efficient conflict management to guarantee fulfilling the service agreements assuming multiple stakeholders involved. This may require extensive and sophisticated use case analysis and what-if scenario testing based on customer needs. This will increase the complexity of the system since it will require real time measurements and simulating different environments continuously so as to allow sufficient testing of the expected performance and capturing worst-case scenarios.

[0046] A problem addressed by the present disclosure is that of how to efficiently resolve potential resource conflicts which may be caused by network/service capability exposure requirements from different 3rd party consumers (servers or applications of the UEs). In particular, how to ensure the capability exposure requirements of different consumers with similar requests are fulfilled.

[0047] In 3GPP, the notion of resource conflict is discussed in different levels. For example, in TS 23.503 vl8.1.0 (April 2023) titled “Policy and charging control framework for the 5G System (5GS); Stage 2”, support for Service data flow prioritization and conflict handling is described. In particular, service pre-emption priority enables the PCF to resolve conflicts where the activation of all requested active PCC rules for services would result in a cumulative authorized QoS which exceeds the Subscribed Guaranteed bandwidth QoS.

For example, the PCF may use the pre-emption priority of a service, the activation of which would cause the subscriber's authorized QoS to be exceeded. If this pre-emption priority is greater than that of any one or more active PCC rules, the PCF can determine whether the deactivation of any one or more such rules would allow the higher pre-emption priority PCC rule to be activated whilst ensuring the resulting cumulative QoS does not exceed a subscriber's Subscribed Guaranteed Bandwidth QoS. If such a determination can be made, the PCF may resolve the conflict by deactivating those selected PCC rules with lower preemption priorities and accepting the higher priority service information from the AF. If such a determination cannot be made, the PCF may reject the service information from the AF. In this context, Allocation and Retention Priority indicates the allocation, retention, and priority of the service data flow. The Allocation and Retention Priority resolves conflicts of demands for network resources.

[0048] However, such an approach leaves a gap: conflict resolution in PCF could further benefit from utilizing a predictive conflict management functionality to identify the impact to all service flows, when an ARP value is set or updated.

[0049] 3GPP TS 22.153 v 19.0.0 (September 2022), titled “Multimedia priority service”, specifies the service requirements for Multimedia Priority Service (MPS). MPS allows Service Users priority access to system resources in situations such as during congestion, creating the ability to deliver or complete sessions of a high priority nature. Service Users are government-authorized personnel, emergency management officials and/or other authorized users. MPS supports priority sessions on an "end-to-end" priority basis.

[0050] However, such an approach leaves a gap in that the MPS provides some hard decisions based on emergency events. The use of predictive congestion handling can allow avoiding terminating sessions blindly, but there remains the possibility of performing more intelligently some optimization on minimizing the impact on existing non-prioritized sessions.

[0051] Furthermore, in 3 GPP SA6, there are situations where there may be possible resource or policy conflict. More specifically in Potential Conflicting VAL/AF policies, and in Conflicting VAL requirements towards application enablement services. [0052] Firstly, considering Potential Conflicting VAL/AF policies, it should be noted that 3GPP TS 23.435 v2.0.0 (June 2023) titled “Procedures for Network Slice Capability Exposure for Application Layer Enablement Service”, provides the following definitions:

• VAL server policy: Network slice management Policy which can be seen as application function policy from VAL Provider/ slice customer/ASP, abstracted based on the slice usage pattern of application, consisting of trigger event, and expected action. When provided to NSCE server, the NSCE server will trigger the expected action based on the policy.

• MNO policy: The network slice management policy between the VAL and MNO pertaining to a specific service and slice, including ranges of network slice capabilities which can be adapted, i.e. Network slice Service level agreement.

• NSCE service provider policy (NSPP): The network slice capability enablement service policy between the VAL and NSCE service provider pertaining to a specific service and slice, including ranges of network slice capability enablement service which can be adapted, i.e. NSCE service level agreement.

• Policy harmonization: The NSCE service that harmonizing the VAL server policy parameter, to make sure the VAL server policy is compatible with the policies of the MNO and NSCE service provider policy for the same service or slice

[0053] Examples of policies in the context of NSCALE are the following:

• Based on monitored performance metric from 0AM, when the max number of PDU sessions or max number of UE is reached, trigger the slice modification with expected parameters.

• Based on monitored Network Slice load from NSACF, when the number of PDU sessions or number of UE exceeds the threshold, trigger the slice modification with expected parameters.

• Based on monitored Network Slice load predictions from NWDAF, when Network Slice load predictions (Predicted Number of PDU Session establishments at the Network Slice) exceeds the threshold with high confidence, trigger the slice modification with expected parameters.

• Based on the monitored the time period, when getting to a certain time period (e.g. summer vacation, spring festival etc.), trigger the slice modification with expected parameters.

• Based on the monitored time period, when getting to a certain time period, trigger the slice modification based on the expected QoS per UE. QoS is mapped/calculated by NSCE to specific parameters of the slice such as the dLThptPerUE, uLThptPerUE, dLThptPerSliceSubnet, uLThptPerSliceSubnet, delayTol erance, dLLatency, uLLatency.

[0054] The notion of conflict in policy management in NSCALE is about having policies from VAL server, MNO, NSPP with potential misalignment or potential overlap (e.g., targeting the same resources). Such policies trigger some action towards 0AM for a slice lifecycle change. In that case, when a VAL policy is received at NSCE layer, it checks whether the VAL policy is in conflict with the MNO policies or NSPP. One criterion is to translate the network slice parameters in the service profile to see whether it is in conflict with that in the VAL provided policy. If policy harmonization is not requested and policies conflict, then the request could be rejected.

[0055] One additional aspect is when two or more VAL servers provide a policy which may result in a slice modification which is conflicting. For example, VAL server 1 asks for a certain RRM split for slice #1 in a given area, whereas VAL server #2 asks the extension of slice #2 the same area, and this may have some conflict in terms of the resources which will be stretched to accommodate both requests.

[0056] Secondly, consider Conflicting VAL requirements towards application enablement services. A VAL requirement can be a request for value added platform services (provided by enablement layer) or for a request for 5GC or 0AM services (indirect request via enabler). The VAL requirement may come from the server (e.g. V2X server) or from the device applications. These support services target certain computational or network resources. Some examples include: SEAL NRM, SEAL NSCE, and EDGEAPP.

[0057] According to 3GPP TS 23.434 vl8.4.1 titled “Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows”, the SEAL NRM service has some value-add capabilities which require interactions with the underlying network. More specifically, the NRM layer acts as AF to update the PCC procedures when the vertical requires some application layer adaptation. This includes the re-mapping of a QoS profile for an application session (upgrade or downgrade or selecting an alternative QoS profile). QoS adaptation for an application traffic flow (upgrade) may impact both the QoS profile load and other application sessions which are mapped to the target QoS profile, especially in high load scenarios. Another capability which may trigger some action towards 5GC and may have impact on other UE sessions, is the SEAL NRM acting as AF for UP path change / redundancy.

[0058] It should be noted that based on these capabilities, the network may not be able to accommodate multiple QoS/ UP path changes since this will affect the performance of other sessions in a given area.

[0059] SEAL NSCE is a slice enablement layer which is specified in 3GPP TS 23.435 v2.0.0 (June 2023). One of the capabilities of SEAL NSCE is to allow request of a slice adaptation or modification from a group of applications /UEs and this may have a severe impact on other UEs traffic using the target slice.

[0060] There is thus a need for feasibility checking, and potential conflict management may be needed to ensure that the trigger from NSCALE doesn’t impact the application service. Otherwise, this may lead to many requests towards 0AM which may be rejected (since 0AM also has its own feasibility assurance capability).

[0061] EDGEAPP may be applicable in edge enablement, the UE (EEC, AC) may trigger an EAS re-selection or new EAS instantiation to a target area due to mobility etc. Also, the EAS may trigger the relocation to a different EDN. Such request from multiple UEs (e.g., in case of expected mobility from multiple UEs to a target EDN or EAS e.g., gaming server) may lead to potential resource conflicts which cannot be estimated in advance.

[0062] One particular use case is the EAS discovery procedure (3GPP TS 23.558 v 18.2.0 (March 2023) titled “Architecture for enabling Edge Applications”, clause 8.14.2.3) or the service continuity scenario related to ACR initiated by the EEC and AC (3 GPP TS 23.558 v 18.2.0, clause 8.8.2.2), where the EEC is selecting or re-selecting the required EAS from a list of EASs, based on the information received from the AC at the device and the AC profile.

[0063] Multiple UEs triggering the sei ection/re- sei ection of an EAS in target area may lead to congestion / conflicts for the target EAS / EDN. There would be an advantage in providing a mechanism for predicting possible conflicts when multiple connections are expected to the target EASZEDN and possible recommendations to overcome these (e.g., by selecting other EAS in the list, or setting priorities). A similar advantage applies also for the selection of EES by EEC from a list of EESs in a target service area.

[0064] There is described herein a new capability for predicting conflicting 3rd party application service requirements, where the service requirements relate to network services. The conflict results to the possible failure of meeting the application service requirements (or the stretching of network resources to accommodate all requests), whereas the requirements can be either policies or communication parameters provisioning/adaptation (in other words, the application / vertical wants to be able to perform “write” or “update” operations targeting or affecting certain network or UE resources). There are two main scenarios where conflicts could happen: Configuration of UE/group related parameters, and Configuration / adaptation of network/edge parameters based on AF /application requests.

[0065] Considering firstly, Configuration of UE/group related parameters; use cases include the provisioning of V2X policies/parameters by the V2X server to the V2X UEs and 5GC, for using Uu and PC5 interfaces for the communication of the V2X messages. Some policies/parameters are provided by the MNO (e.g. AS layer configurations like DRX cycles), whereas some parameters may be provided by the V2X servers or the MNO (PC5 QoS policies). [0066] A V2X service may be multi-operator. For example, UEs belonging to a V2X platoon may belong to different PLMNs. In that case, some parameters may be provided to the UEs by either the MNOs or the V2X server. This may result in conflicts if certain provisioning parameters are provided by different sources to different UEs.

[0067] Another use case can be the configuration of VAL UEs in each service area to trigger a slice adaptation via updating the local UE policies (which may trigger the URSP rule precedence change). Such a change of parameters may affect the performance of other UEs, and it is challenging to understand the real impact to other users in the target slice at a given service area.

[0068] A further use case can be when multiple applications at the UE side may provide application layer QoS requirements (for communicating with other UEs via unicast/groupcast/broadcast) to the UE NAS/AS layer. In that case, there needs to be a mechanism to avoid conflicts without affecting the performance.

[0069] Secondly, considering Configuration / adaptation of network/edge parameters based on AF /application requests; in such a scenario, the AF/ application at the device or server side requires the adaptation of a network parameter which can be the network QoS/resource, the UP path change or traffic steering (e.g. changing UPF/DNAI), providing service provision parameters/policies to PCF and others. Such conflicts may be of different types:

• direct conflicts: plurality of applications request the same service in a target service area for the same time (for example an EES service or a NEF service).

• indirect conflicts: two or more applications request different services which are mapped to similar network resources or services with dependencies. Examples include:

• implicit conflicts: two or more applications request different services which are mapped to different resources but a posteriori the impact of the requirements to the network may create a negative impact for some users in the service area. [0070] By way of example, different applications may provide policies to optimize different metrics and (re-)configure different parameters. Nonetheless, optimizing one metric may have implicit, unwanted, and maybe adversary side effects on one of the metrics optimized by another application, e.g., assuring QoS metrics for GBR users may degrade non-GBR metrics or even cell throughput.

[0071] The following nodes or functions have roles in the methods described herein:

• Conflict mitigation logical functionality (CMLf) as part of the existing SEALZEDGEAPP servers or as new entity;

• Analytics enabler functionality (AEf) (AD AES, NWDAF, MDAS) which predicts possible conflicts;

• Device enabler functionality (DEf) (local CMLU/ SEAL client) which provides local conflict resolution or prediction based on resolution policies and other app/network data; and

• End Application (EA) which can be the vertical or edge application server / client or AF consumer of the network service and/or analytics.

[0072] In overview, the mechanism described herein comprises the following high- level steps.

1. An End Application (EA) sends a request to a wireless communications platform (or middleware platform) for configuring or changing a network/UE related communication parameter, wherein the configuration/change can be predictive. The request may also include the service/application for which this applies, the service area and time of validity as well as the configuration parameter/policy.

2. The wireless communications platform determines to use a conflict mitigation logical functionality (CMLf) to evaluate possible conflict resulting for the reques, wherein the conflict can be a policy or resource conflict and can be either direct or in-direct or implicit. 3. CMLf at the platform subscribes to or requests from Analytics Enablement functionality (AEf) a new analytics service/event/ID e.g. “AF policy conflict analytics” which requires the statistics or predictions on the expected conflict when change a network/UE related communication parameter. In case of prediction this may also include the time horizon, area of interest as well as the preferred confidence level.

4. AEf collects the data based on the analytics event, wherein the data can be offline data from a Data Base on the prior conflicts / failures or service degradations when the network/UE communication parameter changed in the past. This may include also data collection from the network and Operations, Administration and Maintenance (OAM) related to network performance and failures in high congestion scenarios, and inputs from UEs which provide QoE / performance / fault related data for the given application or service type.

5. AEf derives analytics on the congestion subject on a given configuration/change of the network/UE related parameter. Such analytics can be stats or predictions on the expected probability of conflict and the conflict type (direct, indirect, implicitly) and the resource for which the conflict will apply. Such analytics in certain implementations can be also in form of prescriptions / recommendations on how to resolve a potential conflict by indicating a set of actions which attempt to avoid rejecting the request from EA.

6. AEf sends the derived analytics output to the CMLf.

7. CMLf determines a conflict resolution action / policy which is to accept or reject or negotiate the request from EA.

8. CMLf sends the determined the conflict resolution action to the EA.

9. EA and CMLf may further negotiate.

[0073] Figure 3 illustrates an example of an SA6 SEAL implementation in accordance with aspects of the present disclosure. The SEAL implementation may be applied where the AEf is AD AES (Application Data Analytics Enablement Server, see 3GPP TS 23.436 v2.0.0 (June 2023) titled “Functional architecture and information flows for Application Data Analytics Enablement Service”), the CMLf is a logical functionality in a SEAL server (which can be the Configuration Management SEAL server or the NSCE server or a new server), and the EA can be either the VAL server or the VAL client (it is possible the consumer of this service to be the device end application or the server application.

[0074] Figure 3 illustrates a UE 310, a SEAL Platform 320, a VAL server 330, and a data producer 340. The UE 310 comprises a VAL client 312, and a SEAL client 314. The SEAL client 314 may comprise an ADAEC. The SEAL platform 320 comprises an AD AES 322 and a Conflict Management SEAL 324. The Conflict Management SEAL 324 may comprise a CAPIF Functionality. The VAL server 330 may comprise an Application Function (AF). The Data Producer 340 may comprise an A-ADRF, a DN, a DCAF, or an A-DCCF.

[0075] The process begins at 371 : The VAL server 330 or VAL client 312 sends a VAL request to the Conflict Management Server (ConMS) 324 to configure or adapt a network/slice resource or VAL policy parameter.

[0076] In certain implementations (if it is about the VAL policy), the VAL server 330 sends this request as part of the VAL server policy provisioning request to SEAL server (ConMS can be part of NSCE server). The request contains the policy, VAL server ID, Default policy indication, and S-NSSAI. The VAL server policy can be in the form of a policy profile which contains list of trigger events associated with the parameters and expected actions. It contains priority and scheduling information with pre-emption capability for the policies. The scheduling information schedules the policy by defining the schedule (start and end time) for the policy.

[0077] The request may contain a requirement of predictive conflict resolution / feasibility checking to be performed. The request may include at least one of the parameters illustrated in Table 1 below.

Table 1: VAL policy/parameter provisioning Request

[0078] At 372: The ConMS server checks whether the policy/resource configuration or update is in conflict with other policies (to indicate a direct conflict). The server then subscribes to AD AES 322 for resource/policy conflict analytics. This can be done via a subscribe request/response between ConMS and AD AES. The subscribe request may include some of the following parameters:

• Consumer ID

• Analytics ID (conflict analytics)

• Analytics filter information

• Analytics type (non-real time, real time, ML-enabled or predictive, statistics or prescriptive/recommendations)

• Resource ID (the resource identifier for which the confict analytics is expected) • Conflict type or profile (the conflict type can be for instance AF request confict, QoS policy conflict, OAM policy conflict, Slice modification conflict, EAS instantiation conflict, EAS migration conflict etc.)

• Conflict definition / criteria are used to configure the AD AES to understand what is a conflict in case of recommendation

• VAL service ID

• Target VAL UE ID(s)

• Target VAL server ID

• Target data producer profile criteria

• Preferred confidence level

• Area of Interest

• Time validity

[0079] The AD AES 322 maps the analytics event ID to a list of data collection event identifiers, and a list of data producer IDs. Such mapping may be preconfigured by OAM or may be determined by AD AES 322 based on the analytics event type / vertical type and/or data producer profile.

[0080] At 373: The AD AES 322 sends a data collection subscription request to the Data Producers (the data producer 340 at the DN side or the SEAL client 314 at the UE side) with the respective Data Collection Event ID and the requirement for data collection. Such data producers may also include the A-ADRF, the A-DCCF, the VAL server, SEALDD server, or the VAL UEs. The data collection subscription request may comprise historical conflict data per resource/policy,..

[0081] The Data Producers 340, 314 send a subscription response as a positive or negative acknowledgement to the AD AES 322.

[0082] At 374: The Data Producers 314, 340 (at UE or DN side) send the data to the AD AES 322, where the data correspond to the data collection ID or the analytics event ID for which the AD AES 322 subscribed. Such data can be historical data from A-ADRF regarding the service degradation or fault reports under a particular configuration of the resource and/or policy conflict type/profile for which the conflict is analyzed. The data notification may comprise historical conflict data per resource/policy,..

[0083] The AD AES 322 may receive also data (periodically or if a threshold is reached based on configuration) from the application of the UE within the ongoing session (via ADAEC). Such data can be about the RTT, average/peak throughput, jitter, QoE measurements (MOS, stalling events, stalling ratios, etc), QoS profile load, VAL server load, etc.

[0084] At 375: The AD AES abstracts or correlates the data based on the analytics event and the data collection configuration. The AD AES derives conflict analytics on the requested resource or conflict type / profile subject to certain configuration, based on the analytics ID and type of request. Such analytics can be stats or prediction for a given area/time and based on the event type for a given resource/policy configuration.

[0085] At 376: The AD AES sends the analytics to the consumer, where these analytics include the policy #1 or resource #x predicted or statistic probability of conflict for a given area and time horizon, including also the confidence level, whether offline/online analytics were used, as well as the type of expected conflict and possible recommendation for resolution (in case of prescriptive analytics). Such analytics can be also in form of predicting whether the conflict probability is below a certain pre-defined threshold. The analytics may comprise stats/predictions for conflict, and type of conflict.

[0086] At 377: The ConMS determines whether a conflict is expected and of which type (direct, indirect or implicit) and may also recommend an action to address any potential conflict. Such action can be a new policy or a different resource configuration to avoid having a conflict while meeting the application requirements.

[0087] At 378: The ConMS sends a response to the VAL policy/resource provisioning request to the VAL server or client (if it is to VAL client this can be done via SEAL client), indicating the result (positive, negative or counter-proposal). [0088] Figure 4 illustrates an example of SA6 EDGEAPP implementation in accordance with aspects of the present disclosure. The process 400 illustrated in figure 4 is applicable to the architecture for edge enablement as specified in 3GPP TS 23.558 v 18.2.0. In such an architecture, the Edge Enabler Layer (EEL) consists of the Edge Enabler Server (EES) which provides some support capabilities at the edge platform such as service continuity support, edge service capability exposure among others, and Edge Enabler Client (EEC) which is an app at the device side as the client counterpart of the EES to support aspects related to configuration and discovery of Edge Application Servers (EAS). In this architecture, the Edge Configuration Server (ECS) is an entity for configuring the parameters related to EDN to the UEs / end devices.

[0089] As shown in Figure 4, the CMLf is a logical functionality at the EEL (mainly at EES, but it can be also possible that this resides at the EEC side), or this can be a new enablement functionality (or service or server) at the edge or another centralized /cloud platform based on implementation. Also, the use of analytics may be optional in this embodiment where the AEf can be an analytics functionality such as AD AES (however in certain embodiments this analytics entity can be also NWDAF e.g. DN performance analytics).

[0090] Figure 4 illustrates process 400 performed by A UE 410, an AD AES 422, an S- EES (or T-EES) 426, a CMLf 440, and an S-EAS (or T-EAS) 450. The UE 410 comprises an Application Client (AC) 412 and an Edge Enabler Client (EEC) 414. The CMLf 440 may be located at an edge server in the cloud.

[0091] At 471, the EAS (source or target based on the scenario) 450 or the EEC 414 sends a trigger which requires the change of the EAS 450 or the configuration of the EAS 450 for a target UE or group of UEs. Such message can be from EAS 450 or EEC 414 at the service continuity / ACR or service continuity planning procedures as specified in TS 23.558 v 18.2.0 clause 8.8. Or this can be part of the EAS discovery request from EEC or EAS discovery subscription request or EAS discovery subscription update request information flows as specified in TS 23.558 v 18.2.0. As an example, plurality of S-EASs may inform S-EES with ACIDs, and predicted/expected UEs location or Expected AC Geographical Service Area in the ACR launching procedure. [0092] The trigger, may include the new aspects of the EAS or EEC requirement for checking potential conflicts / impacts based on the selection of an EAS or the migration/relocation to another EAS or EDN. Also, the EEC / AC or EAS may provide some conflict criteria or alternative KPI requirements in case of a conflict (which can be due to high congestion at a target EASZEDN for the same time and edge service area).

[0093] At 472, the CMLf 440 at the EES or as new logical entity evaluates together with the S-EES or T-EES 426 the need for checking with an analytics entity possible conflicts using also inputs from multiple requests. This can be triggered if multiple requests arrive at EES at the same time and EES needs to perform in parallel many actions/triggers for a resource/policy change resulting by a change of the EASZEES for the affected UEs, or by triggering instantiation of new EAS in a target EDN.

[0094] At 473, the CMLf 440 subscribes for AD AES 422 analytics which can be performance related or edge load analytics as specified in TS 23.436 v2.0.0, or via subscribing for new analytics service (as indicated in connection with figure 3).

[0095] At 474, the CMLf 440 receives from AD AES the request analytics outputs for the given EASZEES or EDN or for a given UE or group of UEs sessions. The analytics notification may comprise stats/predictions for conflict, and/or type of conflict.

[0096] At 475, the CMLf 440 determines whether a conflict is expected and of which type (direct, indirect or implicit) and may also recommend an action to address any potential conflict. Such action can be a new policy or a different resource configuration to avoid having a conflict while meeting the application requirements. Such a determination may take the form of a prediction.

[0097] At 476, the CMLf 440 sends a notification to the EES (source or target) 426 to indicate the predictive conflict which results from the edge service (e.g. EAS re-selection, new EAS instantiation). Such notification includes at least some of the following parameters:

• One or more of EES ID, E AS ID, EEC ID, AC ID, group ID

Conflict indication for T-EASZEES or EECZUE • Conflict type (direct, indirect, implicit)

• Time horizon / validity and service area (cell or edge service area)

• Confidence level and prediction timer

• Recommended alternative / action to avoid conflict (e.g. new target EAS or EDN, delay ACR / edge service)

• Probability of conflict and impact of conflict (loss of service or performance degradation for EAS or for one or more UEs).

[0098] At 477, the EES 426 then sends to the EEC 414 and/or EAS 450 based on the scenario an indication of potential conflict together with some cause (direct, indirect, implicit). This indication may provide subset or any abstraction of the information provided in step 476.

[0099] Accordingly, there is provided a node of a wireless communications platform, the node comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the node to: obtain a requirement for configuring a communication parameter from at least one external application; detect a trigger to evaluate a potential conflict condition, the trigger determined based on the obtained requirement; request analytics information to support evaluating the potential conflict condition, wherein the analytics information relate to detecting conflict for the obtained requirement; receive analytics information; detect a potential conflict condition based on the received analytics; and notify the potential conflict condition to the at least one external application.

[0100] The node may comprise an entity or unit of at least one wireless communications platform. The node may be an edge or cloud or core network platform comprising an application enablement layer, wherein the application enablement layer may comprise one or more application and/or edge enablement servers or services. The node may comprise a NE 102 as describe herein. The wireless communications platform may comprise multiple services, modules, functionalities or capabilities. The wireless communications platform may provide PaaS, SaaS or laaS modules. [0101] The wireless communications platform may be an application enablement layer. The wireless communications platform may be an edge or cloud or core network platform comprising an application enablement layer, wherein the application enablement layer may comprise one or more application and/or edge enablement servers or services. The wireless communications platform may comprise a Conflict Management Logical function. Conflict Management Logical function may be embedded in the one or more application or edge enablement servers or can be a standalone new server or service. The communication parameter may be a network parameter. The analytics information may be requested from an analytics entity. The analytics entity may comprise a function, a service, a capability, a software module, or a server.

[0102] There is thus provided a new capability for predicting conflicting communication parameters. Such conflicting communication parameters may comprise third-party application service requirements, where the service requirements relate to network services, wherein the network services can be control plane (RAN or Core Network) services, management plane service, application enablement services or device application services. The conflict results to the possible failure of meeting the application service requirements (or the stretching of network resources to accommodate all requests), whereas the requirements can be either policies or communication parameters provisioning/adaptation. One example of communication parameters provisioning/adaptation can be the V2X service provisioning QoS policies for sidelink communications. Such policies can be provided by the application server or the core network, and sidelink resource conflicts in a given area due to high load may result to performance degradation for the end users, which may be crucial for traffic safety services.

[0103] The external application may be a vertical application layer server or client, an Application Function in the untrusted MNO domain, an edge application server or client, or a non-3gpp system entity which interacts with 3gpp system via an application or proxy or gateway.

[0104] The processor may be further configured to cause the node to determine a conflict resolution action, wherein the conflict resolution action comprises a recommendation to the external application for resolving the potential conflict condition. [0105] The processor may be further configured to cause the node to negotiate with the at least one external application a resolution to the potential conflict condition. The potential conflict condition may comprise at least one of a potential resource conflict and a policy conflict. The resource may comprise at least one of: radio resources, network resources, QoS profiles, management resources, slice resources, computational resources at the edge of the wireless communication network, or computational resources in the cloud.

[0106] The policy may comprise any combination of a Vertical Application Layer server policy, a Network slice management Policy, a mobile network operator policy, a network slice capability enablement service policy.

[0107] The processor may be further configured to cause the node to determine criteria for detecting a conflict. The processor may be further arranged to detect a potential conflict condition comprises detecting a conflict type. The processor may be further configured to cause the node to determine criteria for detecting a conflict type. The conflict type may comprise at least one of the following: an AF request conflict, a QoS policy conflict, an slice Life Cycle Management (LCM) conflict, a VAL policy conflict, a UE policy conflict. The potential conflict condition may comprise either a direct conflict, an indirect conflict, or an implicit conflict.

[0108] The requirement for configuring a communication parameter may be predictive. The at least one external application may be at least one of an AF, an application service, and a device application. The received analytics information may comprise any combination of offline and online analytics.

[0109] The potential conflict condition may comprise at least one of: a potential failure to meet the obtained requirement; a potential failure or service degradation at the wireless communications platform resulting from the obtained requirement; and a potential failure or service degradation experienced by other applications or users affected by the configuration of the communication parameter.

[0110] There is further provided a method at a node of a wireless communications platform, the method comprising: obtaining a requirement for configuring a communication parameter from at least one external application; detecting a trigger to evaluate a potential conflict condition, the trigger determined based on the obtained requirement; requesting analytics information to support evaluating the potential conflict condition, wherein the analytics information relate to detecting conflict for the obtained requirement; receiving analytics information; detecting a potential conflict condition based on the received analytics; and notifying the potential conflict condition to the at least one external application.

[OHl] The node may comprise an entity or unit of at least one wireless communications platform. The wireless communications platform may comprise multiple services, modules, functionalities or capabilities. The wireless communications platform may provide Platform as a Service (PaaS), Software as a Service (SaaS) or Infrastructure as a Service (laaS) modules.

[0112] The wireless communications platform may be an application enablement layer. The wireless communications platform may be an edge or cloud or core network platform comprising an application enablement layer, wherein the application enablement layer may comprise one or more application and/or edge enablement servers or services. The wireless communications platform may comprise a Conflict Management Logical function. Conflict Management Logical function may be embedded in the one or more application or edge enablement servers or can be a standalone new server or service. The communication parameter may be a network parameter. The analytics information may be requested from an analytics entity.

[0113] There is thus provided a new capability for predicting conflicting communication parameters. Such conflicting communication parameters may comprise third-party application service requirements, where the service requirements relate to network services, wherein the network services can be control plane (RAN or Core Network) services, management plane service, application enablement services or device application services. The conflict results to the possible failure of meeting the application service requirements (or the stretching of network resources to accommodate all requests), whereas the requirements can be either policies or communication parameters provisioning/adaptation. One example of communication parameters provisioning/adaptation can be the V2X service provisioning QoS policies for sidelink communications. Such policies can be provided by the application server or the core network, and sidelink resource conflicts in a given area due to high load may result to performance degradation for the end users, which may be crucial for traffic safety services.

[0114] The external application may be a vertical application layer server or client, an Application Function in the untrusted MNO domain, an edge application server or client, or a non-3gpp system entity which interacts with 3gpp system via an application or proxy or gateway.

[0115] The method may further comprise determining a conflict resolution action, wherein the conflict resolution action comprises a recommendation to the external application for resolving the potential conflict condition. The method may further comprise negotiating with the at least one external application a resolution to the potential conflict condition. The potential conflict condition may comprise at least one of a potential resource conflict and a policy conflict.

[0116] The resource may comprise at least one of: radio resources, network resources, QoS profiles, management resources, slice resources, computational resources at the edge of the wireless communication network, or computational resources in the cloud.

[0117] The policy may comprise any combination of a Vertical Application Layer server policy, a Network slice management Policy, a mobile network operator policy, a network slice capability enablement service policy. The method may further comprise determining criteria for detecting a conflict. The method may further comprise detecting a potential conflict condition comprises detecting a conflict type. The method may further comprise determining criteria for detecting a conflict type.

[0118] The conflict type may comprise at least one of the following: an AF request conflict, a QoS policy conflict, an slice LCM conflict, a VAL policy conflict, a UE policy conflict. The potential conflict condition may comprise either a direct conflict, an indirect conflict, or an implicit conflict. The requirement for configuring a communication parameter may be predictive. The at least one external application may be at least one of an AF, an application service, and a device application. The received analytics information may comprise any combination of offline and online analytics. [0119] The potential conflict condition may comprise at least one of: a potential failure to meet the obtained requirement; a potential failure or service degradation at the wireless communications platform resulting from the obtained requirement; and a potential failure or service degradation experienced by other applications or users affected by the configuration of the communication parameter.

[0120] There is further provided an analytics entity comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the analytics entity to: receive a request from a wireless communications platform, the request for analytics information to support evaluating a potential conflict condition, wherein the analytics information relate to detecting conflict for a requirement; and send analytics information to the wireless communications platform in response to the request.

[0121] The wireless communications platform may be an application enablement layer. The wireless communications platform may comprise a Conflict Management Logical function. The communication parameter may be a network parameter. The analytics information may be requested from an analytics entity. The analytics entity may be implemented by the node of a wireless communications platform. The node may comprise an entity or unit of at least one wireless communications platform. The wireless communications platform may comprise multiple services, modules, functionalities or capabilities. The wireless communications platform may provide PaaS, SaaS or laaS modules.

[0122] There is thus provided a new capability for predicting conflicting communication parameters. Such conflicting communication parameters may comprise third-party application service requirements, where the service requirements relate to network services. The conflict results to the possible failure of meeting the application service requirements (or the stretching of network resources to accommodate all requests), whereas the requirements can be either policies or communication parameters provi si oning/ adaptati on .

[0123] The processor may be further configured to cause the analytics entity to derive analytics information, wherein sending analytics information to the wireless communications platform in response to the request for conflict comprises sending the derived analytics information.

[0124] The analytics entity may thus be arranged to predict conflicts. The potential conflict condition may comprise at least one of a potential resource conflict and a policy conflict. The resource may comprise at least one of: radio resources, network resources, QoS profiles, management resources, slice resources, computational resources at the edge of the wireless communication network, or computational resources in the cloud.

[0125] The policy comprises any combination of a Vertical Application Layer server policy, a Network slice management Policy, a mobile network operator policy, a network slice capability enablement service policy. The potential conflict condition may comprise either a direct conflict, an indirect conflict, or an implicit conflict. The requirement for configuring a communication parameter may be predictive.

[0126] The at least one external application may be at least one of an AF, an application service, and a device application. The received analytics information may comprise any combination of offline and online analytics.

[0127] There is further provided a method at an analytics entity, the method comprising: receiving a request from a wireless communications platform, the request for analytics information to support evaluating a potential conflict condition, wherein the analytics information relate to detecting conflict for a requirement; and sending analytics information to the wireless communications platform in response to the request.

[0128] The wireless communications platform may be an application enablement layer. The wireless communications platform may comprise a Conflict Management Logical function. The communication parameter may be a network parameter. The analytics information may be requested from an analytics entity. The analytics entity may be implemented by the node of a wireless communications platform. The node may comprise an entity or unit of at least one wireless communications platform. The wireless communications platform may comprise multiple services, modules, functionalities or capabilities. The wireless communications platform may provide PaaS, SaaS or laaS modules. [0129] There is thus provided a new capability for predicting conflicting communication parameters. Such conflicting communication parameters may comprise third-party application service requirements, where the service requirements relate to network services. The conflict results to the possible failure of meeting the application service requirements (or the stretching of network resources to accommodate all requests), whereas the requirements can be either policies or communication parameters provi si oning/ adaptati on .

[0130] The method may further comprise deriving analytics information, wherein sending analytics information to the wireless communications platform in response to the request for conflict comprises sending the derived analytics information. The analytics entity may thus be arranged to predict conflicts. The potential conflict condition may comprise at least one of a potential resource conflict and a policy conflict.

[0131] The resource may comprise at least one of: radio resources, network resources, QoS profiles, management resources, slice resources, computational resources at the edge of the wireless communication network, or computational resources in the cloud. The policy comprises any combination of a Vertical Application Layer server policy, a Network slice management Policy, a mobile network operator policy, a network slice capability enablement service policy.

[0132] The potential conflict condition may comprise either a direct conflict, an indirect conflict, or an implicit conflict. The requirement for configuring a communication parameter may be predictive.

[0133] The at least one external application may be at least one of an AF, an application service, and a device application. The received analytics information may comprise any combination of offline and online analytics.

[0134] Application enablement services are providing some abstracted / middleware support capabilities to ease the integration with 3GPP networks. From the variety of services offered by this layer / platform, some services may affect network resources and allow the 3rd party consumers (verticals, ASPs, AFs, apps at the UE) to influence the network/slice behavior. It is possible to have potential conflicts that need to be resolved in order to avoid application service disruptions or service performance degradations. Hence a problem that tends to be solved by the arrangements described herein is that of how to provide mechanisms to avoid conflicts which may affect the network and application service / session performance.

[0135] There is described herein a new capability for predicting conflicting 3rd party application service requirements, where the service requirements relate to network services. The conflict results to the possible failure of meeting the application service requirements (or the stretching of network resources to accommodate all requests), whereas the requirements can be either policies or communication parameters provisioning/adaptation (in other words, the application / vertical wants to be able to perform “write” or “update” operations targeting or affecting certain network or UE resources).

[0136] It should be noted that there is at present no mechanism for conflict resolution in 3 GPP, since feasibility/conflict checking is not so far standardized and is up to implementation (conflicts are handled by rejecting at the phase of admitting new requests). Current conflict mitigation means do not take into account the prediction aspects and also do not cover “implicit” conflict which can be easily understood by the system.

[0137] There is presented herein a new capability in SEAL (for the conflict resolution) and AD AES (for providing conflict analytics) for enhancing vertical enablement services.

[0138] There is further presented herein a new capability in Edge Enablement / EDGAPP for detecting and resolving potential conflicts assuming multiple EEC or EAS requests in a given edge service area.

[0139] There is described herein a method at a wireless communications platform [which may be at application enablement layer] for identifying a potential resource and/or policy conflict. The method comprises: obtaining a requirement for configuring a network and/or communication parameter [optionally, the configuration requirement may be predictive] from at least one external application [optionally: application can be an AF, an application service, a device application] determining to evaluate a potential conflict, based on the obtained requirement by the at least one external applications, wherein the conflict can be a policy or resource conflict [optionally: the conflict may be either direct or in-direct or implicit conflict] requesting analytics information to support evaluating the potential conflict, wherein the analytics information relate to detecting potential conflict for the given external application requirement receiving the requested analytics information [optionally: the analytics can be offline or online analytics] detecting a potential conflict related to a resource or policy, partly based on the received analytics notifying the potential conflict related to the resource or policy to the at least one external application.

[0140] The method may further comprise determining a conflict resolution action. The method may further comprise negotiating with the at least one external application the potential conflict resolution. The method may further comprise determining the criteria for detecting a conflict and/or conflict type. The conflict type may comprise at least one of the following: an AF request conflict, a QoS policy conflict, an slice LCM conflict, a VAL policy conflict, a UE policy conflict.

[0141] There is further provided an analytics entity (AD AES) for providing conflict analytics. There is further provided a UE.

[0142] Figure 5 illustrates an example of a UE 500 in accordance with aspects of the present disclosure. The UE 500 may include a processor 502, a memory 504, a controller 506, and a transceiver 508. The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0143] The processor 502, the memory 504, the controller 506, or the transceiver 508, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.

[0144] The processor 502 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 502 may be configured to operate the memory 504. In some other implementations, the memory 504 may be integrated into the processor 502. The processor 502 may be configured to execute computer-readable instructions stored in the memory 504 to cause the UE 500 to perform various functions of the present disclosure.

[0145] The memory 504 may include volatile or non-volatile memory. The memory 504 may store computer-readable, computer-executable code including instructions when executed by the processor 502 cause the UE 500 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 504 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0146] In some implementations, the processor 502 and the memory 504 coupled with the processor 502 may be configured to cause the UE 500 to perform one or more of the functions described herein (e.g., executing, by the processor 502, instructions stored in the memory 504). For example, the processor 502 may support wireless communication at the UE 500 in accordance with examples as disclosed herein.

[0147] The controller 506 may manage input and output signals for the UE 500. The controller 506 may also manage peripherals not integrated into the UE 500. In some implementations, the controller 506 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 506 may be implemented as part of the processor 502.

[0148] In some implementations, the UE 500 may include at least one transceiver 508. In some other implementations, the UE 500 may have more than one transceiver 508. The transceiver 508 may represent a wireless transceiver. The transceiver 508 may include one or more receiver chains 510, one or more transmitter chains 512, or a combination thereof.

[0149] A receiver chain 510 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 510 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 510 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 510 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 510 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0150] A transmitter chain 512 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 512 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 512 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 512 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0151] Figure 6 illustrates an example of a processor 600 in accordance with aspects of the present disclosure. The processor 600 may be an example of a processor configured to perform various operations in accordance with examples as described herein. The processor 600 may include a controller 602 configured to perform various operations in accordance with examples as described herein. The processor 600 may optionally include at least one memory 604, which may be, for example, an L1/L2/L3 cache. Additionally, or alternatively, the processor 600 may optionally include one or more arithmetic-logic units (ALUs) 606. One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0152] The processor 600 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 600) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), and others).

[0153] The controller 602 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. For example, the controller 602 may operate as a control unit of the processor 600, generating control signals that manage the operation of various components of the processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.

[0154] The controller 602 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 604 and determine subsequent instruction(s) to be executed to cause the processor 600 to support various operations in accordance with examples as described herein. The controller 602 may be configured to track memory address of instructions associated with the memory 604. The controller 602 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, the controller 602 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 600 to cause the processor 600 to support various operations in accordance with examples as described herein. Additionally, or alternatively, the controller 602 may be configured to manage flow of data within the processor 600. The controller 602 may be configured to control transfer of data between registers, arithmetic logic units (ALUs), and other functional units of the processor 600.

[0155] The memory 604 may include one or more caches (e.g., memory local to or included in the processor 600 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 604 may reside within or on a processor chipset (e.g., local to the processor 600). In some other implementations, the memory 604 may reside external to the processor chipset (e.g., remote to the processor 600).

[0156] The memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 600, cause the processor 600 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. The controller 602 and/or the processor 600 may be configured to execute computer-readable instructions stored in the memory 604 to cause the processor 600 to perform various functions. For example, the processor 600 and/or the controller 602 may be coupled with or to the memory 604, the processor 600, the controller 602, and the memory 604 may be configured to perform various functions described herein. In some examples, the processor 600 may include multiple processors and the memory 604 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.

[0157] The one or more ALUs 606 may be configured to support various operations in accordance with examples as described herein. In some implementations, the one or more ALUs 606 may reside within or on a processor chipset (e.g., the processor 600). In some other implementations, the one or more ALUs 606 may reside external to the processor chipset (e.g., the processor 600). One or more ALUs 606 may perform one or more computations such as addition, subtraction, multiplication, and division on data. For example, one or more ALUs 606 may receive input operands and an operation code, which determines an operation to be executed. One or more ALUs 606 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 606 may support logical operations such as AND, OR, exclusive-OR (XOR), not-OR (NOR), and not- AND (NAND), enabling the one or more ALUs 606 to handle conditional operations, comparisons, and bitwise operations. [0158] The processor 600 may support wireless communication in accordance with examples as disclosed herein. The processor 600 may be configured to or operable to support a means for providing a method at a node of a wireless communications platform, the method comprising: obtaining a requirement for configuring a communication parameter from at least one external application; detecting a trigger to evaluate a potential conflict condition, the trigger determined based on the obtained requirement; requesting analytics information to support evaluating the potential conflict condition, wherein the analytics information relate to detecting conflict for the obtained requirement; receiving analytics information; detecting a potential conflict condition based on the received analytics; and notifying the potential conflict condition to the at least one external application.

[0159] The processor 600 may be configured to or operable to support a means for providing a method at an analytics entity, the method comprising: receiving a request from a wireless communications platform, the request for analytics information to support evaluating a potential conflict condition, wherein the analytics information relate to detecting conflict for a requirement; and sending analytics information to the wireless communications platform in response to the request.

[0160] Figure 7 illustrates an example of a NE 700 in accordance with aspects of the present disclosure. The NE 700 may include a processor 702, a memory 704, a controller 706, and a transceiver 708. The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. These components may be coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces.

[0161] The processor 702, the memory 704, the controller 706, or the transceiver 708, or various combinations or components thereof may be implemented in hardware (e.g., circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. [0162] The processor 702 may include an intelligent hardware device (e.g., a general- purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof). In some implementations, the processor 702 may be configured to operate the memory 704. In some other implementations, the memory 704 may be integrated into the processor 702. The processor 702 may be configured to execute computer-readable instructions stored in the memory 704 to cause the NE 700 to perform various functions of the present disclosure.

[0163] The memory 704 may include volatile or non-volatile memory. The memory 704 may store computer-readable, computer-executable code including instructions when executed by the processor 702 cause the NE 700 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium such the memory 704 or another type of memory. Computer-readable media includes both non- transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.

[0164] In some implementations, the processor 702 and the memory 704 coupled with the processor 702 may be configured to cause the NE 700 to perform one or more of the functions described herein (e.g., executing, by the processor 702, instructions stored in the memory 704). For example, the processor 702 may support wireless communication at the NE 700 in accordance with examples as disclosed herein. The NE 700 may be configured to support a means for providing a method at a node of a wireless communications platform, the method comprising: obtaining a requirement for configuring a communication parameter from at least one external application; detecting a trigger to evaluate a potential conflict condition, the trigger determined based on the obtained requirement; requesting analytics information to support evaluating the potential conflict condition, wherein the analytics information relate to detecting conflict for the obtained requirement; receiving analytics information; detecting a potential conflict condition based on the received analytics; and notifying the potential conflict condition to the at least one external application. [0165] The NE 700 may be configured to or operable to support a means for providing a method at an analytics entity, the method comprising: receiving a request from a wireless communications platform, the request for analytics information to support evaluating a potential conflict condition, wherein the analytics information relate to detecting conflict for a requirement; and sending analytics information to the wireless communications platform in response to the request.

[0166] The controller 706 may manage input and output signals for the NE 700. The controller 706 may also manage peripherals not integrated into the NE 700. In some implementations, the controller 706 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some implementations, the controller 706 may be implemented as part of the processor 702.

[0167] In some implementations, the NE 700 may include at least one transceiver 708. In some other implementations, the NE 700 may have more than one transceiver 708. The transceiver 708 may represent a wireless transceiver. The transceiver 708 may include one or more receiver chains 710, one or more transmitter chains 712, or a combination thereof.

[0168] A receiver chain 710 may be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain 710 may include one or more antennas for receive the signal over the air or wireless medium. The receiver chain 710 may include at least one amplifier (e.g., a low-noise amplifier (LN A)) configured to amplify the received signal. The receiver chain 710 may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal. The receiver chain 710 may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.

[0169] A transmitter chain 712 may be configured to generate and transmit signals (e.g., control information, data, packets). The transmitter chain 712 may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM). The transmitter chain 712 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium. The transmitter chain 712 may also include one or more antennas for transmitting the amplified signal into the air or wireless medium.

[0170] Figure 8 illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0171] At 802, the method may include obtaining a requirement for configuring a communication parameter from at least one external application. The operations of 802 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 802 may be performed by a NE as described with reference to Figure 7.

[0172] At 804, the method may include detecting a trigger to evaluate a potential conflict condition, the trigger determined based on the obtained requirement. The operations of 804 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 804 may be performed by a NE as described with reference to Figure 7.

[0173] At 806, the method may include requesting analytics information to support evaluating the potential conflict condition, wherein the analytics information relate to detecting conflict for the obtained requirement. The operations of 806 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 806 may be performed by a NE as described with reference to Figure 7.

[0174] At 808, the method may include receiving analytics information. The operations of 808 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 808 may be performed by a NE as described with reference to Figure 7.

[0175] At 810, the method may include detecting a potential conflict condition based on the received analytics. The operations of 810 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 810 may be performed by a NE as described with reference to Figure 7.

[0176] At 812, the method may include notifying the potential conflict condition to the at least one external application. The operations of 812 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 812 may be performed by a NE as described with reference to Figure 7.

[0177] It should be noted that the method described herein describes a possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible.

[0178] Figure illustrates a flowchart of a method in accordance with aspects of the present disclosure. The operations of the method may be implemented by a NE as described herein. In some implementations, the NE may execute a set of instructions to control the function elements of the NE to perform the described functions.

[0179] At 902, the method may include receiving a request from a wireless communications platform, the request for analytics information to support evaluating a potential conflict condition, wherein the analytics information relate to detecting conflict for a requirement. The operations of 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 902 may be performed by a NE as described with reference to Figure 7.

[0180] At 904, the method may include sending analytics information to the wireless communications platform in response to the request. The operations of 904 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 904 may be performed by a NE as described with reference to Figure 7.

[0181] It should be noted that the method described herein describes A possible implementation, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. [0182] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0183] The following abbreviations are relevant in the field addressed by this document: 3GPP, 3rd Generation Partnership Project; UP, User plane; NRM , Network Resource Management; NSCE , Network Slice Capability Enablement; EEC, Edge Enabler Client; AC, EA, Application Client, End Application ; AS , Access Stratum; DRX , Discontinuous Reception ; MNO , Mobile Network Operator; URSP , UE route selection policy; NSSAI, Network Slice Selection Assistance Information; DNN , Data network name; PLMN , Public Land Mobile Network; NPN, Non-public network; A-ADRF, Application - Analytics Data Repository Function, ; A-DCCF, Application - Data Collection Coordination Function; SEALDD , SEAL Data Delivery; SEAL, Service Enabler Architecture Layer; ADAEC , Application Data Analytics Enabler Client; AD AES, Application Data Analytics Enabler Server; QoE , Quality of Experience; MOS, Mean Opinion Score; ConMS , Conflict Management Server; VAL , Vertical Application Layer; ECS, Edge Configuration Server; AEf , Analytics Enablement functionality; ACID, Application Client Identifier; CMLf , Conflict Management Logical function; EESZEEL, Edge Enabler Server / Edge Enabler Layer; EDN, Edge Data Network; ACR , Application Context Relocation; EAS , Edge Application Server; and ECSP, Edge Computing Service Provider

Claims

CLAIMS What is claimed is:

1. A node of a wireless communications platform, the node comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the node to: obtain a requirement for configuring a communication parameter from at least one external application; detect a trigger to evaluate a potential conflict condition, the trigger determined based on the obtained requirement; request analytics information to support evaluating the potential conflict condition, wherein the analytics information relate to detecting conflict for the obtained requirement; receive analytics information; detect a potential conflict condition based on the received analytics; and notify the potential conflict condition to the at least one external application.

2. The node of claim 1, wherein the node is further arranged to determine a conflict resolution action, wherein the conflict resolution action comprises a recommendation to the external application for resolving the potential conflict condition.

3. The node of claim 1, wherein the node is further arranged to negotiate with the at least one external application a resolution to the potential conflict condition.

4. The node of claim 1, wherein the potential conflict condition comprises at least one of a potential resource conflict and a policy conflict.

5. The node of claim 4, wherein the resource comprises at least one of: radio resources, network resources, QoS profiles, management resources, slice resources, computational resources at the edge of the wireless communication network, or computational resources in the cloud.

6. The node of claim 4 or 5, wherein the policy comprises any combination of a Vertical Application Layer server policy, a Network slice management Policy, a mobile network operator policy, a network slice capability enablement service policy.

7. The node of any preceding claim, wherein detecting a potential conflict condition comprises detecting a conflict type.

8. The node of claim 7, wherein the conflict type comprises at least one of the following: an AF request conflict, a QoS policy conflict, an slice Life Cycle Management conflict, a VAL policy conflict, a UE policy conflict.

9. The node of any preceding claim, wherein the potential conflict condition comprises either a direct conflict, an indirect conflict, or an implicit conflict.

10. The node of any preceding claim, wherein the requirement for configuring a communication parameter is predictive.

11. The node of any preceding claim, wherein the potential conflict condition comprises at least one of: a potential failure to meet the obtained requirement; a potential failure or service degradation at the wireless communications platform resulting from the obtained requirement; and a potential failure or service degradation experienced by other applications or users affected by the configuration of the communication parameter.

12. An analytics entity comprising: at least one memory; and at least one processor coupled with the at least one memory and configured to cause the analytics entity to: receive a request from a wireless communications platform, the request for analytics information to support evaluating a potential conflict condition, wherein the analytics information relate to detecting conflict for a requirement; and send analytics information to the wireless communications platform in response to the request.

13. The analytics entity of claim 12, further comprising deriving analytics information, wherein sending analytics information to the wireless communications platform in response to the request for conflict comprises sending the derived analytics information.

14. The analytics entity of claim 12 or 13, wherein the potential conflict condition comprises at least one of a potential resource conflict and a policy conflict.

15. The analytics entity of claim 14, wherein the resource comprises at least one of: radio resources, network resources, QoS profiles, management resources, slice resources, computational resources at the edge of the wireless communication network, or computational resources in the cloud.

16. The analytics entity of claim 14 or 15, wherein the policy comprises any combination of a Vertical Application Layer server policy, a Network slice management Policy, a mobile network operator policy, a network slice capability enablement service policy.

17. The analytics entity of any of claims 12 to 16, wherein the potential conflict condition comprises either a direct conflict, an indirect conflict, or an implicit conflict.

18. The analytics entity of any of claims 12 to 17, wherein the requirement for configuring a communication parameter is predictive.

19. The analytics entity of any of claims 12 to 18, wherein the at least one external application is at least one of an AF, an application service, and a device application.

20. The analytics entity of any of claims 12 to 19, wherein the received analytics information comprises any combination of offline and online analytics.