A technique for distributing transmission resources in a media data streaming system is disclosed. A user terminal of the media data streaming system comprises an interface configured to receive a stream of variable bitrate encoded media data via a communications network. The user terminal further comprises a memory storing program code and at least one processing device configured to execute the program code. The program code causes the processing device to determine bitrate variation information for the media data stream and to trigger transmission of the bitrate variation information towards a network component. The network component is configured to trigger dynamic distribution of the transmission resources of the communications network among multiple user terminals dependent on the bitrate variation information.

The present disclosure generally discloses a testing capability related to service testing in a communication network. The testing capability may be configured to support debugging of failures identified during service validation testing of a service in a communication network. The testing capability may be configured to support debugging of failures (e.g., transmission failures or the like) associated with a failed service validation test (e.g., a transmission verification test or the like). The testing capability may be configured to support debugging of failures identified during service validation testing of an Ethernet service. The testing capability may be configured to support debugging of failures (e.g., frame loss or the like) identified during service validation testing of an Ethernet service where the service validation testing of the Ethernet service is performed based on International Telecommunication Union (ITU)-Standardization (ITU-T) Y.1564, which is an Ethernet-based service activation test methodology.

Mechanisms are provided for migrating a computing environment entitlement contract (CEEC) from one computing resource to another. These mechanisms generate one or more CEEC data structures, each CEEC data structure defining terms of a business level agreement between a contracting party and a provider of the data processing system. A CEEC cohort is generated comprising a collection of CEECs having similar terms. The one or more CEEC data structures are associated with a computing resource cohort and a seller of a CEEC data structure, in the one or more CEEC data structures and a buyer of the CEEC data structure, in the one or more CEEC data structures, is identified. The CEEC data structure is migrated from the seller to the buyer and workloads are executed in accordance with terms specified in the CEEC data structure at the buyer after migrating the CEEC data structure.

A service request processing method, a related apparatus, and a system are provided. In the service request processing method provided in embodiments of the present invention, after receiving a service request reported by a network element, a load balancer first determines whether status information of a data node that corresponds to the service request indicates that the data node is available; and rejects, if the status information indicates that the data node is unavailable, to deliver the service request to an application node.

A method includes polling, via a service specific manager operating on a software container in a cloud infrastructure, usage of different application resources and parameters for each service of a plurality of services provided in the cloud infrastructure to yield respective polled data for each service, collating, at the service specific manager, the respective polled data for each service to yield a collation, and based on the collation, deriving a respective weight for each service which a container manager can use to create multiple instances of a new service. The method further includes communicating the respective weight for each service to the container manager and determining, via the container manager, whether to scale up or scale down container services based on the respective weight for each service.

Implementation of an application rule for an application to be accessed by a User Equipment, UE, in a user session in a Service Based Architecture, SBA, domain in a core network of a telecommunications system is disclosed. The SBA, among others, comprises a Policy Control Function, PCF (6), an Application Function, AF (5), and a Session Management Function, SMF (9). The method comprising the steps of receiving, by the PCF (6), an application rule comprising an AF Identifier, AF-ID, identifying the application rule, an Application Identifier, App-ID, identifying the application, and at least one service requirement for processing the application in the SBA domain. The PCF (6) instructing the SMF (9) to execute the at least one service requirement to all present and future user sessions pertaining to the respective application. Complementary methods of supporting the execution of the application rule and devices are also presented.

The present invention relates to a method, computer system, and computer program product for data processing based on a response strategy. According to the method, a performance value of a server is determined in response to receiving at least one request to the server. A response strategy for the at least one request is determined based on the determined performance value. At least one response is provided to the at least one request according to the determined response strategy.

Techniques for generating and monitoring service level objectives (SLOs) are disclosed. The techniques include an SLO platform performing: storing a first SLO definition of a first SLO including a first error budget for a first metric associated with a first service; storing a second SLO definition of a second SLO including a second error budget for a second metric associated with a second service; obtaining first telemetry data from a first data source associated with the first service; obtaining second telemetry data from a second data source associated with the second service; monitoring the first SLO at least by computing the first metric based on the first telemetry data and evaluating the first metric against the first error budget; and monitoring the second SLO at least by computing the second metric based on the second telemetry data and evaluating the second metric against the second error budget.

Techniques for generating and monitoring service level objectives (SLOs) are disclosed. The techniques include an SLO platform performing: storing a first SLO definition of a first SLO including a first error budget for a first metric associated with a first service; storing a second SLO definition of a second SLO including a second error budget for a second metric associated with a second service; obtaining first telemetry data from a first data source associated with the first service; obtaining second telemetry data from a second data source associated with the second service; monitoring the first SLO at least by computing the first metric based on the first telemetry data and evaluating the first metric against the first error budget; and monitoring the second SLO at least by computing the second metric based on the second telemetry data and evaluating the second metric against the second error budget.

A method for providing updated network slice information to a network slice selection function (NSSF includes registering, by a network slice management function (NSMF) with a network function (NF) repository function (NRF), an NF profile corresponding to the NSMF and subscribing, by the NSMF with the NRF, for status updates corresponding to NF instances belonging to network slice instances created by the NSMF. The method further includes receiving, by the NSMF from the NRF, a notification message including one or more network traffic load level updates related to at least one of the NF instances, processing the one or more network traffic load level updates to generate network slice instance configuration information for at least one of the network slice instances, and providing, by the NSMF, the network slice instance configuration information to a NSSF managing the at least one of the network slice instances.