Abstract: A network management architecture referred to as the Control/Orchestration/Management/Policy/Analytics (COMPA) architecture (or COMPA for short). The COMPA architecture functions to simplify and automate the operations (both management and business process) of a network. In one aspect, the COMPA architecture addresses four use case categories: (1) Resource/Service Onboarding; (2) Automated Product Offerings; (3) Automated Management; and (4) Service Exposure. COMPA enables rapid service introduction into the network and lifecycle management; dynamic network governance via policy; and controlled access to functionality provided by different responsibility domains.

Abstract: A network management architecture referred to as the Control/Orchestration/Management/Policy/Analytics (COMPA) architecture (or COMPA for short). The COMPA architecture functions to simplify and automate the operations (both management and business process) of a network. In one aspect, the COMPA architecture addresses four use case categories: (1) Resource/Service Onboarding; (2) Automated Product Offerings; (3) Automated Management; and (4) Service Exposure. COMPA enables rapid service introduction into the network and lifecycle management; dynamic network governance via policy; and controlled access to functionality provided by different responsibility domains.

Abstract: A technique is disclosed for synchronizing first and second data sets stored in a data repository. A method includes triggering, by the data repository, in response to a commit order relating to an ongoing transaction requested by a client and instructing the data repository to apply data modification(s) on the first data set, transmission of a notification event message relating to the ongoing transaction to a data consistency controller. The method includes receiving, by the data repository, a notification event response message relating to the ongoing transaction from the data consistency controller, the notification event response message indicating to the data repository whether (i) to commit the data modification(s) instructed by the commit order on the first data set and corresponding data modification(s) on the second data set, or (ii) to roll back the data modification(s) instructed by the commit order on the first data set.

Abstract: A method and apparatus for operating a data back end node in a data layered architecture network. A database of subscriber data is maintained at a database such that the data is organized into at least one data group. The data associated with each subscriber is associated with a data group. A virtual Home Location Register identifier is assigned to the data group. At least a part of the subscriber data and the virtual HLR identifier is sent to an HLR front end node. In the event of a reset by a Core Network node, only subscriber data associated with the identified data group will need to be rebuilt.

Abstract: A network management architecture referred to as the Control/Orchestration/Management/Policy/Analytics (COMPA) architecture (or COMPA for short). The COMPA architecture functions to simplify and automate the operations (both management and business process) of a network. In one aspect, the COMPA architecture addresses four use case categories: (1) Resource/Service Onboarding; (2) Automated Product Offerings; (3) Automated Management; and (4) Service Exposure. COMPA enables rapid service introduction into the network and lifecycle management; dynamic network governance via policy; and controlled access to functionality provided by different responsibility domains.

Abstract: A network management architecture referred to as the Control/Orchestration/Management/Policy/Analytics (COMPA) architecture (or COMPA for short). The COMPA architecture functions to simplify and automate the operations (both management and business process) of a network. In one aspect, the COMPA architecture addresses four use case categories: (1) Resource/Service Onboarding; (2) Automated Product Offerings; (3) Automated Management; and (4) Service Exposure.

Abstract: An apparatus configured to operate as a Backup system in a Data Layered Architecture Public Land Mobile Network. The apparatus comprises an interface for enabling a data exchange between the apparatus and a plurality of Authentication Centre Front Ends, and a memory for storing subscriber authentication data. The apparatus further comprises a processor for detecting a failure of a Data Back End and for receiving a redirected authentication data set request from an Authentication Centre Front End via the interface. The processor is further configured, in the event of a detected failure of Data Back End, to generate one or more authentication data sets in response to the request using the data stored in the memory, and send the generated data set(s) to the Authentication Centre Front End via the interface.

Abstract: A technique is disclosed for synchronizing first and second data sets stored in a data repository. A method includes triggering, by the data repository, in response to a commit order relating to an ongoing transaction requested by a client and instructing the data repository to apply data modification(s) on the first data set, transmission of a notification event message relating to the ongoing transaction to a data consistency controller. The method includes receiving, by the data repository, a notification event response message relating to the ongoing transaction from the data consistency controller, the notification event response message indicating to the data repository whether (i) to commit the data modification(s) instructed by the commit order on the first data set and corresponding data modification(s) on the second data set, or (ii) to roll back the data modification(s) instructed by the commit order on the first data set.

Abstract: A method and apparatus for operating a data back end node in a data layered architecture network. A database of subscriber data is maintained at a database such that the data is organized into at least one data group. The data associated with each subscriber is associated with a data group. A virtual Home Location Register identifier is assigned to the data group. At least a part of the subscriber data and the virtual HLR identifier is sent to an HLR front end node. In the event of a reset by a Core Network node, only subscriber data associated with the identified data group will need to be rebuilt.

Abstract: Various techniques for routing a request message, which requests a service requiring a data operation on data which is stored in a data backend system, are discussed. The request message is received by a first application front end entity of an application layer. Based on the received request message, a data operation message is sent from the first application front end entity to a first data repository of the data backend system. The first data repository returns routing information to the first application front end entity, which enables the first application front end entity to route the request message to a second application front end entity of the application layer. The second application front end entity communicates with a given data repository which stores the data.

Abstract: An apparatus configured to operate as a Backup system in a Data Layered Architecture Public Land Mobile Network. The apparatus comprises an interface for enabling a data exchange between the apparatus and a plurality of Authentication Centre Front Ends, and a memory for storing subscriber authentication data. The apparatus further comprises a processor for detecting a failure of a Data Back End and for receiving a redirected authentication data set request from an Authentication Centre Front End via the interface. The processor is further configured, in the event of a detected failure of Data Back End, to generate one or more authentication data sets in response to the request using the data stored in the memory, and send the generated data set(s) to the Authentication Centre Front End via the interface.

Abstract: A method and apparatus for providing data redundancy in a data layered architecture network. An enhanced redundancy data backend node stores data designated as dynamic data in a first memory. It also stores data designated as static data in a second memory having a higher latency and/or higher volume than the first memory. Data therefore has a lower memory footprint, as only dynamic data need be regularly updated.

Abstract: Various techniques for routing a request message, which requests a service requiring a data operation on data which is stored in a data backend system, are discussed. The request message is received by a first application front end entity of an application layer. Based on the received request message, a data operation message is sent from the first application front end entity to a first data repository of the data backend system. The first data repository returns routing information to the first application front end entity, which enables the first application front end entity to route the request message to a second application front end entity of the application layer. The second application front end entity communicates with a given data repository which stores the data.

Abstract: The present invention relates to arrangements for charging in a packet switched network. Packets are charged differently dependent on which service flow the packets belong to. The charging system comprises a control system and a serving element residing in a packet forwarding system wherein said control system comprises an account function adapted to manage an account of at least one user and a charging policy decision point arranged to calculate a charging policy for allowed services for the at least one user. Moreover, said serving element comprises a token bucket per user adapted to store reservations received from the account function of the user associated with the token bucket and a charging policy enforcement point arranged to perform charging for a plurality of the allowed services by reducing the stored reservation of the token bucket according to the calculated charging policy.

Abstract: The present invention relates to arrangements for charging in a packet switched network. Packets are charged differently dependent on which service flow the packets belong to. The charging system comprises a control system and a serving element residing in a packet forwarding system wherein said control system comprises an account function adapted to manage an account of at least one user and a charging policy decision point arranged to calculate a charging policy for allowed services for the at least one user. Moreover, said serving element comprises a token bucket per user adapted to store reservations received from the account function of the user associated with the token bucket and a charging policy enforcement point arranged to perform charging for a plurality of the allowed services by reducing the stored reservation of the token bucket according to the calculated charging policy.