# US 2003/0200295 A1 · Network system having a virtual-service-module

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2003/0200295 A1
- Document ID: US20030200295A1
- Status: Published application
- Kind: A1
- Application number: 10/126,300
- Filed: 2002-04-19
- Published: 2003-10-23
- Earliest claimed: 2002-04-19
- Assignees: Nortel Networks Limited
- Inventors: David Gary Roberts; Sanjay Dhawan; Mahesh Kumar; Glen William Gibson; Bala Sankaranarayanan; Sam Rajarathinam
- Web page: https://patentgrep.com/patent/US20030200295A1

## CPC

- H04L 41/122: of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
- H04L 69/40: for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A method, apparatus, and system in which a network system includes a virtual graph composed of a plurality individual networks. A first individual network is associated with a first user. The first individual network includes a plurality of service modules modeled to be representing a first set of network elements. The second individual network is associated with a second user. The second individual network includes a plurality of service modules modeled to be representing a second set of network elements. The second set of network element differs in the type of network elements included in the second individual network and the topological order of the network elements in the second individual network than the first set of network elements.

## Claims

### Claim 1

An apparatus, comprising:
a service module modeled to represent a network element that performs one or more functions to process a packet in a network system, the service module embedded in a container program, the service module being a self-contained module of data and its associated processing software that has an archive file containing both executable code as well as metadata that integrates the service module with the network system.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the service module comprises a high-level abstraction composed of multiple sub-components, the sub-components include:
a management component to interface with components internal to a virtual network graph;
a packet-processing component to determine a path of a packet through the virtual network graph; and
a flow set-up component to process packets beyond what instructions in the packet-processing component can accomplish.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the service module belongs to an object class and one or more instances of the service module exist, a first instance of the service module having different versioning information than a second instance of the service module.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the network element is one of a group consisting of a router, an Ethernet switch, a virtual private network, a firewall, a load balancer, a bridge, and a network address translator.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the meta data includes information that describes the various configuration parameters supported by the service module and any specific commands required to configure the service module through a command-line interface.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the container program to provide a common environment for a first service module to interact with a second service module.

### Claim 7 (depends on 1)

The apparatus of claim 1, wherein the container program comprises an operating system.

### Claim 8 (depends on 1)

The apparatus of claim 1, further comprising:
a first service module embeds in the container program;
a second service module embeds in the container program, the second service module to communicate information with the first service module via the container program without a direct object reference to the first service module.

### Claim 9 (depends on 1)

The apparatus of claim 1, wherein the executable code to include instructions to install and remove the service module, as well as instructions to configure the service module with configuration information.

### Claim 10 (depends on 1)

The apparatus of claim 1, wherein the service module is mapped to physical processing power and memory capacity dedicated to that service module.

### Claim 11 (depends on 1)

The apparatus of claim 1, wherein the service module is contained in a computer readable medium.

### Claim 12

A network system, comprising:
a virtual graph composed of a plurality individual networks;
a first individual network associated with a first user, the first individual network having processing and memory resources dedicated to the first individual network; and
a second individual network associated with a second user, the second individual network having processing and memory resources dedicated to the second individual network, wherein the processing and memory resources dedicated for the first individual network being independent from the processing and memory resources dedicated to the second individual network.

### Claim 13 (depends on 12)

The network system of claim 12, further comprising:
two or more service modules included in a topology of the first individual network, a first service module modeled to represent a network element, the two or more service modules arrangeable in the first individual network in an arbitrary topology.

### Claim 14 (depends on 12)

The network system of claim 12, wherein the first individual network includes a first service module modeled to represent a network element, the second individual network includes a second service module modeled to represent a network element, the topology of the first individual network being composed of different network elements than included in the topology of the second individual network.

### Claim 15 (depends on 12)

The network system of claim 12, wherein the first individual network maps to a first virtual address space within a global domain housing all of the virtual address spaces and the second individual network maps to a second virtual address space within the global domain housing all of the virtual address spaces.

### Claim 16 (depends on 12)

The network system of claim 12, wherein the first individual network includes a first service module modeled to represent a network element, a new instance of the first service module having different functionality than the existing instance of the first service module to dynamically load during program execution.

### Claim 17 (depends on 16)

The network system of claim 16, wherein the new instance to mirror the network routing path of the existing instance during the installation of the new instance so that the addition of functionality does not cause downtime for any other components.

### Claim 18 (depends on 12)

The network system of claim 12, wherein the first individual network includes a first service module modeled to represent a network element, a first instance of the first service module being embedded in a container program, a second instance of the service module being embedded in the container program to allow multiple instances of the same service module modeled to represent a particular type of network element to be upgraded independently.

### Claim 19 (depends on 12)

The network system of claim 12, further comprising:
a resource management circuit employing a token bucket algorithm to ensure that each individual network receives processing and memory dedicated to that individual network.

### Claim 20 (depends on 12)

The network system of claim 12, wherein the topology of the first individual network includes a first service module modeled to represent a network element and a physical network element external to the virtual graph.

### Claim 21

A network system, comprising:
a virtual graph composed of a plurality individual networks;
a first individual network associated with a first user, the first individual network including a first plurality of service modules modeled to be representing a first set of network elements;
a second individual network associated with a second user, the second individual network including a second plurality of service modules modeled to be representing a second set of network elements, wherein the second set of network element differs in type of network elements included in the second individual network and topological order of the network elements in the second individual network than the first set of network elements.

### Claim 22 (depends on 21)

The network system of claim 21, wherein the first plurality of service modules includes a first service module embedded in a container program, the first service module being a self-contained module of data and its associated processing software that has an archive file containing both executable code as well as metadata that integrates the service module with the network system.

### Claim 23 (depends on 21)

The network system of claim 21, wherein the first individual network has a unique virtual address space, dedicated processing power and dedicated memory to make the first individual network logically and physically distinct from the second individual network.

### Claim 24 (depends on 23)

The network system of claim 23, wherein the dedicated processing power employs a token bucket algorithm.

### Claim 25 (depends on 21)

The network system of claim 21, wherein the first plurality of service modules includes a first service module, the network system to load, remove, configure or modify the first service module during program execution without a packet flow disruption.

### Claim 26 (depends on 21)

The network system of claim 21, wherein the virtual graph composed of a plurality individual networks is hosted on a single computing machine.

### Claim 27 (depends on 26)

The network system of claim 26, wherein the first individual network associated with the first user also includes a physical network element external to the single computing machine.

### Claim 28 (depends on 1)

The apparatus of claim 1, further comprising:
a physical layer in the network system, the physical layer having processing power and memory space dedicated to the service module.

### Claim 29 (depends on 21)

The network system of claim 21, wherein the virtual graph composed of a plurality individual networks is hosted on a multiple computing machines connected by a network.

### Claim 30 (depends on 29)

The network system of claim 29, wherein the first individual network associated with the first user also includes a physical network element external to the network connecting the multiple computing machines.

### Claim 31

An apparatus, comprising:
a computer readable medium storing a software module modeled to represent a network element that performs one or more functions to process a packet in a network system, the software module consisting of a high-level abstraction composed of multiple sub-components, wherein the sub-components include
a management component to interface with components internal to a virtual network graph;
a packet-processing component to determine a path of a packet through the virtual network graph; and
a flow set-up component to process packets beyond what instructions in the packet-processing component can accomplish.

### Claim 32 (depends on 31)

The apparatus of claim 31, wherein the software module being a self-contained module of data and its associated processing software that has an archive file containing both executable code as well as metadata that integrates the software module with the network system.
