Abstract: A concept for balancing a load in a mobile communication network, comprising receiving 130 receive data from a radio transceiver using a first interface and determining 140 a first receive data packet and a second receive data packet from the receive data, the first receive data packet and the second receive data packet being associated to different services. The concept comprises forwarding 150 the first receive data packet to a first processing unit using a second interface, and forwarding the second receive data packet to a second processing unit using the second interface.

Abstract: According to one general aspect, a method for managing a plurality of different tenants on a shared computing infrastructure including at least one application server apparatus may include associating a tenant with a plurality of services, wherein each service provides a set of actions that the service is configured to perform. In some embodiments, the method may include associating at least one tenant runlevel for each associated service with the tenant. In various embodiments, the method may include, when the application server apparatus executes a service for the tenant, determining the tenant runlevel associated with the tenant, and managing the set of actions configured to be performed by the service based at least in part upon the tenant runlevel associated with the tenant and the service.

Abstract: A kernel provides a mechanism allowing various applications (e.g. CRM, logistics, procurement, etc.) hosted on a plurality of different application servers, to share access to a common underlying system (e.g. database). An automated process for implementing a kernel change (e.g. for upgrade or replacement) may employ a “Stop-the-World” approach involving suspension of application server instances, coordinated by the start service of the last application server whose kernel is to be changed. As used herein, suspending refers to halting any processing prior to calling a central service (CS) as long as a CS instance is unavailable, and then to resuming processing once the CS instance becomes available. This suspension of relevant clients avoids errors from arising during the downtime of the CS instance. Once the application server instances are in a stopped state, the CS instance is restarted. Then, the application server instances are resumed, and their kernels are changed.

Abstract: A concept for balancing a load in a mobile communication network, comprising receiving 130 receive data from a radio transceiver using a first interface and determining 140 a first receive data packet and a second receive data packet from the receive data, the first receive data packet and the second receive data packet being associated to different services. The concept comprises forwarding 150 the first receive data packet to a first processing unit using a second interface, and forwarding the second receive data packet to a second processing unit using the second interface.

Abstract: Coordinating persisted data in a distributed system, in which persisted data is stored with identifiers that indicate a hierarchical relationship of the persisted data with a business scenario. When operation data is stored as a record of a transaction within the distributed system, a root identifier (ID) and a connection ID can be added to the operational data record. The root ID indicates a source endpoint of the transaction, and the connection ID indicates a communication message from the source endpoint to the destination endpoint related to the transaction. A persisted data coordination engine can access persisted data in the distributed system and generate a business scenario transaction tree based on the root ID and the connection ID. A map of the business scenario transaction tree can then be created and reported.

Abstract: Dynamically isolating application servers, wherein only active application servers are indicated to client applications to prevent access to inactive application servers by the client applications. A central server of a distributed system determines a state of application servers in a system, and generates a list of application servers that includes all application servers of the system including an indication of the state of the application servers. The central server also generates a filtered list of application servers that excludes inactive application servers or application servers in an inactive mode. The filtered list is passed to client applications, which enables the client applications to only access the active application servers, but not access the inactive application servers.

Abstract: According to one general aspect, a method for managing a plurality of different tenants on a shared computing infrastructure including at least one application server apparatus may include associating a tenant with a plurality of services, wherein each service provides a set of actions that the service is configured to perform. In some embodiments, the method may include associating at least one tenant runlevel for each associated service with the tenant. In various embodiments, the method may include, when the application server apparatus executes a service for the tenant, determining the tenant runlevel associated with the tenant, and managing the set of actions configured to be performed by the service based at least in part upon the tenant runlevel associated with the tenant and the service.

Abstract: A system, computer program product and method of processing function calls in a distributed application environment are provided. A number of function calls for communication from a sending application to a receiving application are queued in a database. Dependencies among at least a portion of the function calls that are being queued are determined while the function calls are stored in the queues. A schedule of execution of the function calls is then generated based on the determined dependencies.

Abstract: Coordinating persisted data in a distributed system, in which persisted data is stored with identifiers that indicate a hierarchical relationship of the persisted data with a business scenario. When operation data is stored as a record of a transaction within the distributed system, a root identifier (ID) and a connection ID can be added to the operational data record. The root ID indicates a source endpoint of the transaction, and the connection ID indicates a communication message from the source endpoint to the destination endpoint related to the transaction. A persisted data coordination engine can access persisted data in the distributed system and generate a business scenario transaction tree based on the root ID and the connection ID. A map of the business scenario transaction tree can then be created and reported.

Abstract: Dynamically isolating application servers, wherein only active application servers are indicated to client applications to prevent access to inactive application servers by the client applications. A central server of a distributed system determines a state of application servers in a system, and generates a list of application servers that includes all application servers of the system including an indication of the state of the application servers. The central server also generates a filtered list of application servers that excludes inactive application servers or application servers in an inactive mode. The filtered list is passed to client applications, which enables the client applications to only access the active application servers, but not access the inactive application servers.

Abstract: A system and method for connection failover. A plurality of virtual machines connect to a proxy using a protocol library. The proxy establishes a connection to a gateway. A user context including a conversation identifier is stored. The proxy continues a conversation with a second virtual machine based on the conversation identifier and user context if a first virtual machine fails when the conversation is in a ready for failover state.

Abstract: A system and method for connection failover. A plurality of virtual machines connect to a proxy using a protocol library. The proxy establishes a connection to a gateway. A user context including a conversation identifier is stored. The proxy continues a conversation with a second virtual machine based on the conversation identifier and user context if a first virtual machine fails when the conversation is in a ready for failover state.

Abstract: A system, computer program product and method of processing function calls in a distributed application environment are provided. A number of function calls for communication from a sending application to a receiving application are queued in a database. Dependencies among at least a portion of the function calls that are being queued are determined while the function calls are stored in the queues. A schedule of execution of the function calls is then generated based on the determined dependencies.

Abstract: An optical duplexer, configured as a directional coupler, is integrated into an optical coupling arrangement with a fiber optic pigtail, constructed in planar-optical hybrid technology on a substrate (1). To reduce the required surface area and decrease optical cross talk, the branch of the directional coupler (waveguide 6, branch 7) is sharply bent. The bend is equipped with a reflecting mirror (11) integrated opposite the inner edge (10) of the bend. Furthermore, the waveguiding end of the bent branch (7) is equipped with a cylindrical lens. A laser diode (8) is located before this, and a photodiode (5) is located before the angled end of the straight-line integrated waveguide (2).

Abstract: An optical switch has a substrate and a transparent material in which a three-dimensional diffraction pattern is recorded which is capable of diffracting light, the material having non-linear optical properties and extending in the form of a first layer above the substrate. At least one first electrode and at least one second electrode are provided for varying the diffraction pattern in accordance with applied voltages.