We claim:
1. A simulation controller comprising:
a global process manager;
a model manager created by the global process manager, generating models when requested by the global process manager;
a vector manager created by the global process manager, generating vectors when requested by the global process manager; and
wherein the global process manager manages the models and vectors received by a simulator.
2. A simulation environment, as defined in claim 1, further comprising a simulator, connected to the global process, model, and vector managers, that receives the models and vectors in accordance to instructions provided by the global process manager.
3. A simulation controller, as defined in claim 2, wherein:
the model manager instantiates and configures models upon request of the global process manager; and
these models can direct the creation of new models.
4. A simulation controller, as defined in claim 3, wherein:
the model manager manages the models such that all models are generated and configured sequentially; and
all of the models enter simulation time in parallel.
5. A simulation controller, as defined in claim 1, wherein:
the model manager instantiates and configures models upon request of the global process manager; and
these models may direct the creation of new models.
6. A simulation controller, as defined in claim 5, wherein:
the model manager manages the models such that all models are generated and configured sequentially; and
all of the models enter simulation time in parallel.
7. A simulation control method comprising the steps of:
generating a model manager operative to list the models to be used by a simulator;
generating a vector manager operative to manage the vectors to be used by a simulator;
instantiating a global testbench;
instantiating vectors to be used by the global testbench and simulator;
instantiating the interface models to be simulated with the global testbench; and
configuring the global testbench and interface models to be used by the simulator.
8. A simulation control method, as defined in claim 4, further comprising the step of managing the vectors, the global testbench, and interface models such that the simulator simulates.
9. A simulation control method, as defined in claim 5, further comprising the steps of:
receiving simulation results; and
analyzing the simulation results.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A system for processing packets of information, the system comprising:
an ingress module comprising an L2TP Access Concentrator (LAC), the ingress module receiving a plurality of packets of information from a first network, the ingress module determining the type of each of the plurality of packets; and
a route server module comprising an L2TP Network server (LNS), the route server module being coupled to the ingress module, the route server module sending a distributed processing request to the ingress module;
wherein the ingress module receives the distributed processing request and, responsively, performs Multi-Protocol Label Switching (MPLS) processing on data packets of the plurality of packets having an MPLS label and routes the MPLS processed packets in accordance with the MPLS label;
wherein the ingress module forwards non-data packets of the plurality of packets of information to the route server module via an L2TP tunnel established between the LAC and the LNS; and
wherein the route server module receives the non-data packets of the plurality of packets of information and performs centralized processing operations on the non-data packets.
2. The system of claim 1, wherein the MPLS processing comprises swapping a first MPLS label with a second MPLS label.
3. The system of claim 1, wherein the centralized processing comprises establishing a connection with an entity on the Internet.
4. A method comprising:
receiving a plurality of packets of information from a first network at an ingress module, the ingress module comprising an L2TP Access Concentrator (LAC);
determining the type of each of the plurality of packets;
sending a distributed processing request from a route server module to the ingress module, the route server module comprising an L2TP Network server (LNS);
receiving the distributed processing request at the ingress module and, responsively, performing Multi-Protocol Label Switching (MPLS) processing on data packets of the plurality of packets having an MPLS label and routes the MPLS processed packets in accordance with the MPLS label;
forwarding non-data packets of the plurality of packets of information from the ingress module to the route server module via an L2TP tunnel established between the LAC and the LNS; and
receiving the non-data packets of the plurality of packets of information at the route server module and performing centralized processing on the non-data packets at the route server module.
5. The system of claim 4, wherein the MPLS processing comprises forwarding the data packets of the plurality of packets of information to an egress module.
6. The system of claim 4, wherein the centralized processing comprises establishing a connection with an entity on the Internet.
7. A routing device comprising:
an ingress portion comprising an L2TP Access Concentrator (LAC), the ingress portion receiving negotiation packets; and
a route server portion coupled to the ingress portion, the route server portion comprising an L2TP Network server (LNS), the route server portion receiving the negotiation packets from the ingress portion via an L2TP tunnel established between the LAC and the LNS and completing a negotiation, the route server portion sending a distributed switching request message to the ingress portion upon the completion of a negotiation;
wherein the ingress portion receives the distributed switching request message and, responsively, sends a reply message to the route server portion; and
wherein the ingress portion, upon the receipt of the distributed switching request message, performs Multi-Protocol Label Switching (MPLS) processing on subsequently received data packets having an MPLS label and routes the MPLS processed packets in accordance with MPLS label.
8. The routing device of claim 7 wherein the ingress portion determines a forwarding equivalence class.
9. The routing device of claim 7, wherein the data packets include labeling information and the ingress portion uses the label information from the data packets to determine an outgoing link.
10. The routing device of claim 7, wherein the ingress portion forwards all control packets to the route server portion via the tunnel established between the LAC and the LNS.
11. The routing device of claim 7, wherein all MPLS LDP, CRLDP, or RSVP packets are routed to the route server portion via the tunnel established between the LAC and the LNS.
12. A system comprising:
means for receiving a plurality of packets of information from a first network at an ingress module comprising an L2TP Access Concentrator (LAC);
means for determining the type of each of the plurality of packets;
means for sending a distributed processing request from a route server module comprising an L2TP Network Server (LNS) to the ingress module;
means for receiving the distributed processing request at the ingress module and, responsively, performing Multi-Protocol Label Switching (MPLS) processing on data packets of the plurality of packets having an MPLS packets of the plurality of packets having an MPLS label and routes the MPLS processed packets in accordance with the MPLS label;
means for forwarding non-data packets of the plurality of packets of information from the ingress module to the route server module via an L2TP tunnel established between the LAC and the LNS; and
means for receiving the non-data packets of the plurality of packets of information at the route server module and performing centralized processing on the non-data packets of the plurality of packets of information at the route server module.
13. A computer program on a computer readable medium, the program comprising:
first code for receiving a plurality of packets of information from a first network at an ingress module comprising an L2TP Access Concentrator (LAC);
second code for determining the type of each of the plurality of packets;
third code for sending a distributed processing request from a route server module comprising an L2TP Network Server (LNS) to the ingress module;
fourth code for receiving the distributed processing request at the ingress module and, responsively, performing Multi-Protocol Label Switching (MPLS) processing on data packets of the plurality of packets packets of the plurality of packets having an MPLS label and routes the MPLS processed packets in accordance with the MPLS label;
fifth code for forwarding non-data packets of the plurality of packets of information from the ingress module to the route server module via an L2TP tunnel established between the LAC and the LNS; and
sixth code for receiving the non-data packets of the plurality of packets of information at the route server module and performing centralized processing on the non-data packets of the plurality of packets of information at the route server module.
14. The system of claim 1, wherein the MPLS processing comprises assigning an MPLS label to each of the data packets.
15. The system of claim 1, wherein the non-data packets comprise packets selected from the group consisting of (i) control packets, (ii) routing protocol packets, (iii) MPLS label distribution protocol (LDP) packets, (iv) Constraint Based LDP (CRLDP) packets, and (v) Resource Reservation Protocol-Traffic Engineering (RSVP-TE) packets.
16. The method of claim 4, further comprising:
removing a Point-to-Point Protocol (PPP) header from each of the data packets of the plurality of packets at the ingress module.
17. The method of claim 16, further comprising:
performing decompression on the data packets of the plurality of packets at the ingress module.
18. The method of claim 4, further comprising:
encapsulating each of the data packets with a Point-to-Point Protocol (PPP) header; and
forwarding the encapsulated packet to a destination on a second network that carries packets according to the PPP.
19. The method of claim 18, further comprising:
performing compression on the data packets of the plurality of packets at the ingress module.
20. The method of claim 4, wherein prior to receiving the distributed processing request at the ingress module, the ingress module tunnels all received packets of the plurality of packets of information to the route server module via the tunnel established between the LAC and the LNS.
21. The method of claim 4, further comprising:
receiving, at the ingress module, routing table entries sent from the route server module.
22. The method of claim 4, wherein sending the distributed processing request from the route server module to the ingress module occurs in response to the route server module completing a given centralized processing operation selected from the group consisting of (i) a Point-to-Point Protocol negotiation process, and (ii) an MPLS negotiation process.