OLD | NEW |
1 .. include:: replace.txt | 1 .. include:: replace.txt |
2 .. highlight:: cpp | 2 .. highlight:: cpp |
3 | 3 |
4 ++++++++++++++++++++ | 4 ++++++++++++++++++++ |
5 Design Documentation | 5 Design Documentation |
6 ++++++++++++++++++++ | 6 ++++++++++++++++++++ |
7 | 7 |
8 | 8 |
9 -------- | 9 -------- |
10 Overview | 10 Overview |
(...skipping 102 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
113 | 113 |
114 The main objective of the EPC model is to provides means for the | 114 The main objective of the EPC model is to provides means for the |
115 simulation of end-to-end IP connectivity over the LTE model.· | 115 simulation of end-to-end IP connectivity over the LTE model.· |
116 To this aim, it supports for the | 116 To this aim, it supports for the |
117 interconnection of multiple UEs to the Internet, via a radio access | 117 interconnection of multiple UEs to the Internet, via a radio access |
118 network of multiple eNBs connected to a single SGW/PGW node, as shown | 118 network of multiple eNBs connected to a single SGW/PGW node, as shown |
119 in Figure :ref:`fig-epc-topology`. | 119 in Figure :ref:`fig-epc-topology`. |
120 | 120 |
121 The following design choices have been made for the EPC model: | 121 The following design choices have been made for the EPC model: |
122 | 122 |
123 #. The only Packet Data Network (PDN) type supported is IPv4. | 123 #. Support of IPv4 and v6 Packet Data Network (PDN) types. |
124 #. The SGW and PGW functional entities are implemented within a single | 124 #. The SGW and PGW functional entities are implemented within a single |
125 node, which is hence referred to as the SGW/PGW node. | 125 node, which is hence referred to as the SGW/PGW node. |
126 #. The scenarios with inter-SGW mobility are not of interests. Hence, a | 126 #. The scenarios with inter-SGW mobility are not of interests. Hence, a |
127 single SGW/PGW node will be present in all simulations scenarios· | 127 single SGW/PGW node will be present in all simulations scenarios· |
128 #. A requirement for the EPC model is that it can be used to simulate the | 128 #. A requirement for the EPC model is that it can be used to simulate the |
129 end-to-end performance of realistic applications. Hence, it should | 129 end-to-end performance of realistic applications. Hence, it should |
130 be possible to use with the EPC model any regular ns-3 application | 130 be possible to use with the EPC model any regular ns-3 application |
131 working on top of TCP or UDP. | 131 working on top of TCP or UDP. |
132 #. Another requirement is the possibility of simulating network topologies | 132 #. Another requirement is the possibility of simulating network topologies |
133 with the presence of multiple eNBs, some of which might be | 133 with the presence of multiple eNBs, some of which might be |
(...skipping 3995 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
4129 "under the hood" to configure the EPC upon explicit methods called by | 4129 "under the hood" to configure the EPC upon explicit methods called by |
4130 ``LteHelper``. The exact interactions are displayed in the Figure :ref:`fig-help
ers`. | 4130 ``LteHelper``. The exact interactions are displayed in the Figure :ref:`fig-help
ers`. |
4131 | 4131 |
4132 .. _fig-helpers: | 4132 .. _fig-helpers: |
4133 ··· | 4133 ··· |
4134 .. figure:: figures/helpers.* | 4134 .. figure:: figures/helpers.* |
4135 :align: center | 4135 :align: center |
4136 | 4136 |
4137 Sequence diagram of the interaction between LteHelper and EpcHelper | 4137 Sequence diagram of the interaction between LteHelper and EpcHelper |
4138 | 4138 |
OLD | NEW |