International Business Machines Corporation

Lenovo (singapore) Pte. Ltd.

Ng4t Gmbh

Canio Cillis

Ronald Leroy Billau

Ekkart Leschke

Vincenzo V Di Luoffo

Bruce Oliver Anthony, Jr

Richard Ott

Robert Bruce Nicholson

Jochen Kappel

Martin McDonald

William Frederick Berg

Christian Van Maastricht

Victor S Moore

Dinesh C Verma

Erich Miles Nahum

Chatschik Bisdikian

Laurence J Plant

George Willard Van Leeuwen

Ravinder Kumar Sabhikhi

Philip E Grady

Raj Kumar Singh

Josef Reisinger

Colin James Thorne

Yan Fei Cai

Wissam A Elriachy

Heike Leuschner

Ting Ding

Biao Long

Vivek Kashyap

Daniel Joseph Martin

An approach is provided for optimizing a deployment pattern. Precedent system(s) that have components that match components in an initial deployment pattern of a new system are identified. A historical performance of the precedent system(s) is determined to not satisfy target non-functional requirements (NFRs) and target service levels of the new system. Responsive to determining that the historical performance did not satisfy the NFRs and the target service levels, the components in the initial deployment pattern are modified and a new deployment pattern for the new system is generated so that (i) the new deployment pattern includes the modified components and (ii) a performance of the new system using the new deployment pattern is likely to satisfy the target NFRs and the target service levels. A recommendation for deploying the new system using the new deployment pattern is generated.

Constructing and enhancing a deployment pattern

An approach is provided for optimizing a deployment pattern. Event and configuration data of precedent systems is aggregated. Based on the aggregated data, a metadata model of the precedent systems is generated. Components of an initial deployment pattern of a new system are identified. Target non-functional requirements (NFRs) and target service levels of the new system are determined. Based on the metadata model, precedent system(s) that have components that match or are similar to the components in the initial deployment pattern are identified. A performance of the precedent system(s) is compared to the NFRs and target service levels. A new deployment pattern for the new system is generated. The new deployment pattern includes a modification of the components identified in the initial deployment pattern. A recommendation for deploying the new system using the new deployment pattern is generated.

A method and associated computer system. A processor queries a service catalog and a virtual service inventory to obtain network service instances including a virtual network function. The processor seamlessly replaces the virtual network function by a new version of the virtual network function without interruption of the network service in the production environment. The processor deploys the new version of the virtual network function unattached to the production environment, including: replacing a network address of the virtual network function in the load balancer with a network address of the new version of the virtual network function. In response to a determination by the processor that the virtual network function has a floating network address, the processor detaches the floating network address from the virtual network function and attaches the detached floating network address to the new version of the virtual network function.

Replacing a virtual network function in a network service

A method and associated computer system. A processor queries a service catalog and a virtual service inventory to obtain network service instances including a virtual network function. The processor deploys a new version of the virtual network function by performing at least one step of the following steps: replacing the network address of the virtual network function with the network address of the new version of the virtual network function; detaching a floating network address from the virtual network function and attaching the detached floating network address to the new version of the virtual network function (if one of the obtained network service instances is connected to a load balancer and/or the virtual network function is configured with an inherent load balancing); replacing the instance identifier of the virtual network function in a forwarding policy rule with the instance identifier of the new version of the virtual network function.

A method and associated system for testing a virtual network function by a virtual network tester, wherein a predefined certification context specification specifies services based on the virtual network function in form of different usage patterns, and wherein a predefined test case selection matrix specifies applicable test cases for each usage pattern. In response to selecting a usage pattern from the different sage patterns, the applicable test cases are determined from the test case selection matrix and control parameters of the test case selection matrix based on the selected usage pattern.

Testing a virtual network function by a virtual network tester

A method and system for testing a Virtualized Network Function (VNF) in a network. Metadata including test parameters pertaining to a network environment specific to the VNF is retrieved. At least one Virtualized Network Tester (VNT) for testing the VNF is created and stored in the network. The metadata is mapped to a test list to define a test suite of test cases based on the test parameters in the metadata. The VNF is tested by the at least one VNT according to the test suite to enable the at least one VNT to emulate the network environment specific to the VNF. The VNF is disconnected from the network and from virtual networks during the testing. If the testing is successful, the VNF is attached to the network and to virtual networks to enable the VNF to be deployed in the network. If the testing is unsuccessful, the method ends.

Testing a virtualized network function in a network

A processor-implemented method, apparatus, and/or computer program product move Open Systems Interconnection (OSI) layer 4 connections between wirelessly-connected user equipment to a series of cell-towers, wherein an OSI layer 4 connection is extracted out of the underlying cellular protocols at the series of cell-towers. A detection is made that user equipment, which has a broken-out layer 4 connection, has moved from a first cell-tower to a second cell-tower. Traffic for an existing layer 4 connection from the user equipment is tunnelled between the first cell-tower and the second cell-tower. In response to a predetermined trigger event occurring, an ongoing bidirectional flow of data packets is migrated from the user equipment over to layer 4 connections maintained at the second cell-tower. Furthermore, OSI layer 4 connections for all server ports other than the proxied active layer 4 connections that are proxied in the web cache are byte cached.

Mobility management of OSI connections between cell towers

A processor-implemented method, apparatus, and/or computer program product move Open Systems Interconnection (OSI) layer 4 connections between wirelessly-connected user equipment to a series of cell-towers, wherein an OSI layer 4 connection is extracted out of the underlying cellular protocols at the series of cell-towers. A detection is made that user equipment, which has a broken-out layer 4 connection, has moved from a first cell-tower to a second cell-tower. Traffic for an existing layer 4 connection from the user equipment is tunnelled between the first cell-tower and the second cell-tower. A predetermined trigger event is identified. In response to the predetermined trigger event occurring, an ongoing bidirectional flow of data packets is migrated from the user equipment over to layer 4 connections maintained at the second cell-tower.

In a mobile data network with a breakout system, when data is broken out, the RLC function is split into two different flows, between the UE and the breakout system and between the breakout system and the RNC. These two flows are processed by different RLC functions that may drift apart and become out of synchronization resulting in errors that diminish the user's quality of experience. Other errors may also occur in communication on these two different flows. The breakout system attempts to correct these errors using data stored locally in communication data structures for the two data flows. If the errors cannot be corrected, the breakout system can initiate an RLC reset into both of these flows to resynchronize the data communication.

Utilizing stored data to reduce packet data loss in a mobile data network with data breakout at the edge

A network management system utilizes an element manager at the RNC level to reduce the workload and efficiently manage multiple wireless appliances in a mobile data network. Management communications from the network management system flow through the element manager to all devices under the RNC level appliance hosting the element manager. The element manager provides for fault management, performance monitoring and configuration of the many breakout appliances and reports necessary information back to the network management system.

Network management for wireless appliances in a mobile data network

A system and method provides seamless switchover of a user device (UE) between a mobile data network and a wireless network while providing policy and charging control (PCC) of the data session in the mobile data network. A mobile core network component is made ASF aware to process user data traffic related to an auto switching function (ASF) server from a UE client located on the UE using a special access point name (APN). The mobile core network component then uses a dedicated deep packet inspection (ASF DPI) for all data transfers to the special APN. The core network component is then able to process the UE data traffic seamlessly as the traffic is toggled between the ASF tunnel the WiFi tunnel. By monitoring the data traffic on the ASF tunnel, the core component (GGSN/PGW) is able to provide PCC for the data session.

Service awareness and seamless switchover between client based WiFi access and mobile data network access

Mobile network services are performed at the edge of a mobile data network in a way that is transparent to most of the existing equipment in the mobile data network. The mobile data network includes a radio access network and a core network. A first service mechanism in the radio access network breaks out data coming from a basestation, and performs one or more mobile network services at the edge of the mobile data network based on the broken out data. A second service mechanism in the core network receives data monitored during attach and Packet Data Protocol (PDP) context activation, and establishes sessions with components in the mobile data network that support charging and policy control for sessions broken out by the first service mechanism.

Charging and policy for services at the edge of a mobile data network

A flow setup table in a basestation breakout component allows for servicing non-cacheable IP data flows at the breakout component without the need for network address translation. For each broken out IP flow at the breakout component, the flow setup table holds a mapping between tunnel IDs and the IP related information. The flow setup table data is sent to the breakout component at the gateway. The gateway breakout component uses the flow setup table to forward non-cacheable data requests to the internet and return data received from the internet back to the basestation breakout component. The basestation component then sends the non-cacheable data in the correct tunnel to the user equipment requesting the data.

Growing community of inventors

Berlin, Germany

Canio Cillis