The present disclosure relates to systems and methods for matching electronic activities with record objects based on entity relationships. The method can include accessing a plurality of electronic activities, identifying an electronic activity, identifying a first participant associated with a first entity and a second participant associated with a second entity, determining whether a record object identifier is included in the electronic activity, identifying a first record object of the system of record that includes an instance of the record object identifier, and storing an association between the electronic activity and the first record object. The method can include determining a second record object corresponding to the second entity, identifying, using a matching policy, a third record object linked to the second record object and identifying a third entity, and storing, by the one or more processors, an association between the electronic activity and the third record object.

The present disclosure relates to systems and methods for matching electronic activities with record objects based on entity relationships. The method can include accessing a plurality of electronic activities, identifying an electronic activity, identifying a first participant associated with a first entity and a second participant associated with a second entity, determining whether a record object identifier is included in the electronic activity, identifying a first record object of the system of record that includes an instance of the record object identifier, and storing an association between the electronic activity and the first record object. The method can include determining a second record object corresponding to the second entity, identifying, using a matching policy, a third record object linked to the second record object and identifying a third entity, and storing, by the one or more processors, an association between the electronic activity and the third record object.

A method for processing NF discovery requests using prioritized lists of preferred locations includes maintaining an NF profiles database including NF profiles of producer NFs registered to provide service to other NFs and a preferred locality attribute mappings database including mappings between preferred locality attributes and prioritized lists of preferred locations. The method includes receiving, from an NF, an NF discovery request including query parameters and a preferred locality attribute. The method further includes accessing the preferred locality attribute mappings database using the preferred locality attribute and obtaining a prioritized list of preferred locations corresponding to the preferred locality attribute, accessing the NF profiles database using the query parameters and identifying NF profiles of producer NFs capable of providing a service indicated by the query parameters, and prioritizing the NF profiles according to the prioritized list of preferred locations. An NF discovery response is generated and transmitted to the NF.

An application, executed by a User Equipment (“UE”), may receive an identifier, which may be used to monitor Key Performance Indicators (“KPIs”) associated with the UE. Such KPIs may be monitored in conjunction with execution of the application, such as at times that the application sends and/or receives traffic. The KPIs may be associated with sensor data, resources, and/or other features or functionality of the UE. The UE may obtain an identifier associated with the application and/or the UE from a KPI monitoring system of some embodiments, may obtain user consent to monitor and/or report KPIs associated with the application, and may provide such KPIs to the KPI monitoring system in conjunction with the identifier. The KPI monitoring system may generate aggregated KPI information, associated with the application, based on the KPIs received from the UE and/or KPIs received from one or more other sources.

An application, executed by a User Equipment (“UE”), may receive an identifier, which may be used to monitor Key Performance Indicators (“KPIs”) associated with the UE. Such KPIs may be monitored in conjunction with execution of the application, such as at times that the application sends and/or receives traffic. The KPIs may be associated with sensor data, resources, and/or other features or functionality of the UE. The UE may obtain an identifier associated with the application and/or the UE from a KPI monitoring system of some embodiments, may obtain user consent to monitor and/or report KPIs associated with the application, and may provide such KPIs to the KPI monitoring system in conjunction with the identifier. The KPI monitoring system may generate aggregated KPI information, associated with the application, based on the KPIs received from the UE and/or KPIs received from one or more other sources.

Examples of techniques for validation of approver identifiers in a cloud computing environment are described herein. An aspect includes receiving, by a processor, a template that defines a plurality of actions to be performed by the processor. Another aspect includes determining for a first action of the plurality of actions whether the template specifies a first user identifier under which to run the first action. Another aspect includes, based on determining that the template specifies the first user identifier, determining whether the template specifies a second user identifier to approve running of the first action under the first user identifier. Another aspect includes, based on determining that the template specifies the second user identifier to approve running of the first action under the first user identifier, validating whether the second user identifier has permission to approve the running of the first action under the first user identifier.

Examples of techniques for validation of approver identifiers in a cloud computing environment are described herein. An aspect includes receiving, by a processor, a template that defines a plurality of actions to be performed by the processor. Another aspect includes determining for a first action of the plurality of actions whether the template specifies a first user identifier under which to run the first action. Another aspect includes, based on determining that the template specifies the first user identifier, determining whether the template specifies a second user identifier to approve running of the first action under the first user identifier. Another aspect includes, based on determining that the template specifies the second user identifier to approve running of the first action under the first user identifier, validating whether the second user identifier has permission to approve the running of the first action under the first user identifier.

Disclosed are systems, computer-readable media and methods for monitoring performance data across microservices. One example method includes establishing a service policy configured on a centralized switch controller, applying the service profile to a virtual interface associated with a microservice, mapping a microservice name for the microservice to an IP address and a port number, tracking a protocol flow for the microservice, wherein the protocol flow is associated with a virtual switch, to yield data, aggregating the data to yield aggregated data and presenting the aggregated data on a user interface.

Disclosed are systems, computer-readable media and methods for monitoring performance data across microservices. One example method includes establishing a service policy configured on a centralized switch controller, applying the service profile to a virtual interface associated with a microservice, mapping a microservice name for the microservice to an IP address and a port number, tracking a protocol flow for the microservice, wherein the protocol flow is associated with a virtual switch, to yield data, aggregating the data to yield aggregated data and presenting the aggregated data on a user interface.

Methods, systems, devices, and software are disclosed for generating a network usage profile. Certain embodiments of the network usage profile include a devices-by-node profile, indicating the set of customer devices available for use in communicating with a customer-side network node located at a customer side of an access network over a period of time, where some of the customer devices are not in operative communication with the customer-side network node during a portion of that time. Other embodiments associate the network usage profile with customer information to generate device-by-customer profiles. Still other embodiments associate the network usage profile with network traffic information to generate traffic-by-device profiles. Even other embodiments associate the multiple sources and types of information to generate traffic-by-customer profiles and/or traffic-by-device-by-customer profiles. Any of the profiles may then be accessed by one or more parties for use in affecting various network services, including targeting content delivery.