Difference between revisions of "3gpp-emulator"
(TOC) |
|||
| Line 12: | Line 12: | ||
== Introduction == | == Introduction == | ||
| − | Introduce the context, | + | Introduce the context, citing TridentCom'08. Not too long (a couple of paragraph should be ok) [Miguel] |
| − | == | + | == Reference Architecture == |
| − | + | The reference scenario architecture is composed of several domains. Each domain consists of an core netowrk (CN) and an arbitrary number of access networks (ANs). The IMS lays within the CN, consisting of a set of CSCFs proxies (our model considers one of each type: P-CSCF, S-CSCF and I-CSCF). Each AN is connected to its corresponding CN through an Access Router (AR). | |
| − | + | The different domain CNs are connected through an interconnection point (IX), also known as inter-PLMS (Public Land Mobile Network) backbone. The IX also interconnect a segment of auxiliary network elements (such as a DNS server). | |
| − | == | + | The scenario considers two kinds of attachemnt point for external equipment: access networks (for UEs) and IMS cores (for core entities, such as the SIP Application Server shown as example in the figure below). |
| + | |||
| + | The following script [TODO] allows VNUML multi-domain specifications automatically. Some observations follow: | ||
| + | |||
| + | * The first parameter is the number of domains (D) and the second one the number of access network per domain (N). | ||
| + | * The 'external' attribute is not added in neither acc*_* nor core* <net>s, due to it is depend of the host physical interface (e.g., eth0, eth1, etc.) and the particular VLAN ID being used. Therefore, '''user need to edit the resulting XML properly'''. | ||
| + | * An auxiliary segment with a DNS server is added | ||
| + | * IPv6 addresses are automatically assigned to each element | ||
| + | * The script only generates homogeneous specifications, i.e. the same number of AN for each domain, although the resulting XML can be easily prune to fit user needs. | ||
| + | |||
| + | <div align="center">[Missing Figure]</div> | ||
| + | |||
| + | == Intradomain Scenario == | ||
| + | |||
| + | <div align="center">[Missing Figure]</div> | ||
| + | |||
| + | == Interdomain Scenario == | ||
| + | |||
| + | <div align="center">[Missing Figure]</div> | ||
| + | |||
| + | == Supporting stuff == | ||
Link to filesystems, kernels, etc. | Link to filesystems, kernels, etc. | ||
Revision as of 13:55, 6 March 2008
3GPP System Architecture Evolution Scenarios
Authors: Fermín Galán (fermin at tid.es) Miguel Gómez (miguelg at tid.es) version 1.0, March Xth, 2008
Contents
Introduction
Introduce the context, citing TridentCom'08. Not too long (a couple of paragraph should be ok) [Miguel]
Reference Architecture
The reference scenario architecture is composed of several domains. Each domain consists of an core netowrk (CN) and an arbitrary number of access networks (ANs). The IMS lays within the CN, consisting of a set of CSCFs proxies (our model considers one of each type: P-CSCF, S-CSCF and I-CSCF). Each AN is connected to its corresponding CN through an Access Router (AR).
The different domain CNs are connected through an interconnection point (IX), also known as inter-PLMS (Public Land Mobile Network) backbone. The IX also interconnect a segment of auxiliary network elements (such as a DNS server).
The scenario considers two kinds of attachemnt point for external equipment: access networks (for UEs) and IMS cores (for core entities, such as the SIP Application Server shown as example in the figure below).
The following script [TODO] allows VNUML multi-domain specifications automatically. Some observations follow:
- The first parameter is the number of domains (D) and the second one the number of access network per domain (N).
- The 'external' attribute is not added in neither acc*_* nor core* <net>s, due to it is depend of the host physical interface (e.g., eth0, eth1, etc.) and the particular VLAN ID being used. Therefore, user need to edit the resulting XML properly.
- An auxiliary segment with a DNS server is added
- IPv6 addresses are automatically assigned to each element
- The script only generates homogeneous specifications, i.e. the same number of AN for each domain, although the resulting XML can be easily prune to fit user needs.
Intradomain Scenario
Interdomain Scenario
Supporting stuff
Link to filesystems, kernels, etc.
Roadmap
List of things to do. Open to contributions.
