hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 5.3.7 Supplementary Services | In case the CTM user (calling or called party) invokes supplementary services, the same record used to charge the connection, or a different one, has to store the relevant charging information for the services. |
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 5.3.8 Usage metering records during the handover phase | The CTM standardization defines different handover capabilities for the CTM terminal. These capabilities are limited during the first phase of the implementation of the service (according to [1]) or by the operator's decision. If the CTM handset will be given the possibility to perform a switch to switch handover or an... |
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 5.3.9 Structure of the CTM usage metering record for Hot Billing purpose | The "hot billing" (HB) function, which allows the CTM subscriber to receive the bill in a short time (to be defined) could be realized through the creation (in the switch) of a short record (extracted from the CTM complete one). This could be sent in real time to a dedicated charging/billing centre. This one shall coll... |
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 5.4 Mobile telecommunication systems | The issue of charging in this subclause will only be related to mobile systems specified by ETSI. In this context mobile systems are those, intended to cover large geographical areas by radio access for portable telecommunication terminals. Other systems like cordless telephones are considered in separate clauses. Char... |
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 5.4.1 Different home and away charging for outgoing mobile calls | Due to occasionally considerable differences between charging in fixed and in mobile networks, a feature is available intending to equalize charging of mobile calls from the customer's home location to charging of calls from the fixed network. The feature makes it possible for people to be customer on the mobile servic... |
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 5.4.2 Split charging aspects in mobile telecommunication | Due to the differences between charging of calls in fixed networks and in mobile networks split charging is interesting for charging of calls from other networks to mobile customers. Cost of calls from fixed network customers to mobile could be higher than cost for calls to other fixed network customers. Split charging... |
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 5.4.3 Charging aspects for mobile telecommunication signalling | Generally the signalling traffic is not charged. The tools are not yet available but might be needed. Mobile telecommunication creates considerable signalling traffic due to its nature. The following events requires signalling resources: • During visits much of the signalling traffic utilize signalling resources from f... |
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 5.5 Universal Personal Telecommunication (UPT) | ETSI/NA7 has produced an ETR 055-3 [5]. ETR 055-3 is Part 3 of a multi-part ETR 055. The ETR details the service requirements on the charging and billing mechanisms involved with the Universal Personal Telecommunication (UPT) service, and the necessary information transfer required between UPT service providers and net... |
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 5.6 Universal Mobile Telecommunication Systems (UMTS) | NOTE: Studies should be performed on charging in UMTS. |
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 5.7 Packet oriented traffic | Packet oriented traffic can be provided by virtual circuit (VC) or by permanent virtual circuit (PVC). The access from the user to the packet network is called a logical channel. ETSI TR 101 619 V1.1.1 (1998-11) 27 Packet oriented traffic may be provided to the users in multi-operator/multi-provider environments on con... |
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 5.7.1 Usage related elements for charging | The usage related elements for charging are basically the same as for circuit oriented traffic, see Table 1. Certain considerations for call set up and volume related charging should be mentioned. The call set up signalling may include available space for transfer of information between the users. The charging of call ... |
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 5.7.2 Reference configurations | The network mechanisms for charging and revenue accounting in packet oriented networks could be based on the same principles as for circuit oriented networks. It means the call related data for packet oriented calls should be monitored and registered by the network as for the circuit oriented traffic. If charging is ma... |
ce0cf9aedacd99b318dbb55a851242b7 | 101 619 | 6.1 ETSI Technical Bodies involvement | The situation for deliverables is seen below. Other items may later be identified for studies. TC-TMN document I-ETS 300 819 [2] specifies the usage information on the NE/OS Interface. ETSI SPS1 has extended the ISUP protocol for transfer of charging related data [9]. ETSI SPS3 has extended the INAP protocol for transf... |
8f9c2c4efc247937f72f2cf968ff40d6 | 101 639 | 1 Scope | The present document gives examples for the Radio sub-system link control to be implemented in the Base Station System (BSS) and Mobile Switching Centre (MSC) of the GSM and DCS 1 800 systems in case hierarchical cell structures are employed. Unless otherwise specified, references to GSM also include DCS 1 800, and mul... |
8f9c2c4efc247937f72f2cf968ff40d6 | 101 639 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
8f9c2c4efc247937f72f2cf968ff40d6 | 101 639 | 3 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04 [4]. |
8f9c2c4efc247937f72f2cf968ff40d6 | 101 639 | 4 General | ETS 300 911 (GSM 05.08 [3]) specifies the radio sub system link control implemented in the Mobile Station (MS), Base Station System (BSS) and Mobile Switching Centre (MSC) of the GSM and DCS 1 800 systems of the European digital cellular telecommunications system (Phase 2). The present document gives several examples o... |
8f9c2c4efc247937f72f2cf968ff40d6 | 101 639 | 5 Hierarchical networks | |
8f9c2c4efc247937f72f2cf968ff40d6 | 101 639 | 5.1 General | In a hierarchical, or microcellular network, traffic is supported on multiple layers of cells. Typically, a network operator could implement a layer consisting of microcells as a second layer in his existing network consisting of large or small cells. The addition of this second layer would improve the capacity and cov... |
8f9c2c4efc247937f72f2cf968ff40d6 | 101 639 | 5.2 Cell types | GSM 03.30 [2] distinguishes between three kinds of cells: large cells, small cells and micro cells. The main difference between these kinds lies in the cell range, the antenna installation site, and the propagation model applying: |
8f9c2c4efc247937f72f2cf968ff40d6 | 101 639 | 5.2.1 Large cells | In large cells the base station antenna is installed above the maximum height of the surrounding roof tops; the path loss is determined mainly by diffraction and scattering at roof tops in the vicinity of the mobile i.e. the main rays propagate above the roof tops; the cell radius is minimally 1 km and normally exceeds... |
8f9c2c4efc247937f72f2cf968ff40d6 | 101 639 | 5.2.2 Small cells | For small cell coverage the antenna is sited above the median but below the maximum height of the surrounding roof tops and so therefore the path loss is determined by the same mechanisms as stated in subclause 5.1.1. However large and small cells differ in terms of maximum range and for small cells the maximum range i... |
8f9c2c4efc247937f72f2cf968ff40d6 | 101 639 | 5.2.3 Microcells | COST 231 defines a microcell as being a cell in which the base station antenna is mounted generally below roof top level. Wave propagation is determined by diffraction and scattering around buildings i.e. the main rays propagate in street canyons. COST 231 proposes an experimental model for microcell propagation when a... |
8f9c2c4efc247937f72f2cf968ff40d6 | 101 639 | 6 Idle mode procedures | GSM 03.22 [1] outlines how idle mode operation shall be implemented. Further details are given in Technical Specifications GSM 04.08 and GSM 05.08 [3]. A useful feature for hierarchical networks is that cell prioritization, for Phase 2 MS, can be achieved during cell reselection by the use of the reselection parameters... |
8f9c2c4efc247937f72f2cf968ff40d6 | 101 639 | 7.1 General | In the following annexes four examples of handover and power control algorithms are presented. All of these are considered sufficient to allow successful implementation in hierarchical or microcellular networks. None of these solutions is mandatory. The "Description of algorithm" of each annex, contains a text as provi... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 1 Scope | The present document examines the relationship between the telecommunication services platform, the end user applications support platforms and the other platforms (as defined in the EII Enterprise Model [2]), and the GMM Architectural Framework [5]. The requirements of these are specified in architectural terms. The f... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 1.1 Who will use the present document? | The present document will be useful for the following users: - network operators to determine the interfaces required in future networks; - regulators to determine the connection and interconnection points required in a future network; - equipment manufacturers to determine the requirements of the interfaces between eq... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 1.2 Benefits of a Network Architecture | There are several benefits expected from having an agreed architecture: - It reduces costs of development and implementation. - It helps guarantee that new equipment can be introduced. - It ensures that services can be evolved and added to the system. - It gives customers confidence that smooth upgrades are possible. I... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 3 Definitions and abbreviations | This work starts from [9], extended by work on the EII Enterprise Model [2] and the GMM Architectural Framework [5]. |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: application: a collection of user tasks which require processing, storage and communications functions to carry them out. service: something offered by a service provider to an end user (customer) or application. platform: a set of cap... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: API Applications Programming Interface ASP Applications Support Platform CNIS Platforms supporting provision of Communication and Networking of Information Services DASH Description of Architecture and Services Harmonization DAVIC Digital Audi... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 4 Guiding Principles on Architecture | In a world of global service provisioning with multiple service and network providers working under multiple regulatory environments, it is not possible to guarantee the type of network infrastructure that will be available to provide GMM services to customers. The EII and GII are envisaged to be a seamless federation ... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 5 Use of Enterprise Models | The definition of the GII architecture starts from the enterprise model. The primary purpose of an enterprise model is to identify interfaces which are likely to be of general commercial importance. In order to do this, a number of roles are identified which describe a reasonably well-defined business activity and whic... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 6 Structural Model & Interfaces | The structural model shown in figure 6 was developed from figure 3 during work on the EII Enterprise Model [2]. This extends the concept of structural and infrastructural roles from the GII and identifies the interfaces between roles. In the present document the distinction between high priority and low priority interf... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 6.1 Interfaces to the Telecommunications Platform | Centring on the telecommunications platform, figure 6 can be reduced to the interfaces shown in figure 7. GCS e4 including IN access e6 (e4 phys) e8 (e4 phys) e4 phys A CNIS DIPSS B e3 e7 e5 e2 e5 e3 Figure 7: Essential interfaces for the telecommunications platform All interfaces except those to GCS are logical, and r... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 6.2 Segment, Domain and Platform Interfaces | It can be seen from figure 6 that each interface, for example, e6, e4, e5, e8 can have up to 3 parts. The significance of these is described below: • Segment - Segment This is the technical interface between different segments which may or may not cross domain boundaries. For example, e13 is the technical interface bet... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 7 Relationship to the GMM Framework Architecture | The GMM (Global Multimedia Mobility) framework architecture developed by ETSI PAC is shown in figure 8. Application Services Domain Application Services Domain UIM UIM Mobile TE Fixed TE Mobile TE Fixed TE Access Networks Core Transport Networks (including intelligence) Examples: ° GSM NSS+ IN ° ISDN/IN based ° B-ISDN ... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 7.1 Open issues related to the GMM model | These include: - Can switching be carried out in the Access Network? Where is the local exchange function in the GMM model? The GMM model is not regarded as satisfactory due to the presence of the V5 interface - this is the interface between a high speed access network and the core switching or leased line network. The... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 7.2 Evolution of GMM Model | Further domains are required to be added to the GMM Conceptual Model to answer some of the above questions. In particular, the question of the location of the Internet on the GMM Conceptual Model is best answered by showing a separate user domain and service provider domain. For these reasons it is clearer to re-draw t... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 8 Relationship to UMTS | In figure 8, where "UMTS" is shown as an example of an Access Network segment, this should be replaced by "UMTS Radio Access Network (URAN)". Mobility management shall also be included in the core transport network functions. The URAN then allows access to core transport services to complete the UMTS functionality. |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 9 Relationship to IMT-2000 | RAN (Radio Access Network) is the IMT-2000 radio access network component as shown in figure 10. This is the generic equivalent of the URAN as the radio access component of the GMM Model. User Identity Module Mobile Terminal Radio Access Network UIM - MT Interface Radio Interface (UNI) RAN - CN Interface NNI (UIM) (MT)... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 10 Scenarios | The following scenarios show how GCS will be used by the other roles and platforms, and thus identify where standardization work is needed within ETSI. High value scenarios from the SRC6 report [1] include: - Interactive Video Services including VoD; - Distributed Processing; - Radio Distribution; - Computer Supported ... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 10.1 Video-on-Demand Scenario | With reference to figure 6, the following options are possible for Video-on-Demand: 1) Role Instance A is the end-user (customer). Role Instance B is the Content Provider. 2) The Content Provider creates, assembles and encodes the content (video films with soundtrack) wholly within Role Instance B. 3a)The Content Provi... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 10.2 Distributed Processing Scenario | Table 2.2 from the SRC6 report [1] provides the following examples of Distributed Processing: - distributed manufacturing; - real time inventory control; - electronic funds transfer at point-of-sale (EFTPOS); - network and service management. For the first three items there is end-to-end user communication. Such servic... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 10.3 Radio Distribution Scenario | Radio can be distributed to users in a number of ways: a) Broadcasting via air waves as for traditional am and fm distribution. Programmes to be broadcast are transmitted from a programme production platform to a broadcasting platform that is part of the GCS. The programs are directly broadcast without being stored in ... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 12 Reference Models for GCS | Figure 11 is used in some form in both the EII and GII work. This shows the critical interfaces between the information processing and storage functions and a network operations domain as well as between two network operations domains. The transport, control, and management aspects of these interfaces are shown. The co... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 12.1 Open architectural issues on the functional reference model | Open questions include: a) The layering of functions in a future Information Network "stack". b) The service functionality provided by IN for a future telecommunications service platform serving the Information Network. How much does IN need to do now - does it need to go beyond pure call control and handle mobility/po... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 13 Options for the Distribution of Functions | It can be seen from the above that IN functionality as currently implemented is included in the E-SCF box in figure 11. Certainly all connection-related IN functions could fit into this box. However, there are plans in ETSI and ITU to enhance IN to include a much wider range of functionality, which could either be prov... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 13.1 Interoperability | There is fairly strong agreement that one of the useful call terminating functions which IN can perform within the EII is to detect incompatibilities and invoke interworking functions to provide interoperability. This requires enhancements to the basic call models planned for IN CS-3. It will include the ability to rec... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 13.2 Mobility | There is fairly common agreement that Mobility Management will include the option to use IN operations in future, especially if the roaming is greater than the local exchange area, i.e. Location Updating, Location Registration and User Registration. Otherwise, if the mobility is "localized" Mobility Management could be... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 13.3 UPT server-based implementation. | UPT provides mobility functionality in fixed networks. A user can register a unique number (UPT number) on any fixed network number and is reachable via this UPT number at the registered fixed network number. In a server-based UPT-implementation for the data administration (follow me destination, short dial number etc.... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 13.4 IN and B-ISDN CS-3 | Multi-connection and Multi-Party services are being implemented in the ITU using distributed IN (in every local switch), but is this market lead or technology lead? It is not really clear what the high penetration services are. This is also being standardized in Servers by IETF and under consideration for future Networ... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 14 Interfaces | The interfaces between GCS and other roles are listed in table 1 [2]. Table 1: Interfaces between GCS and other roles Interface Connected Functions Explanation e6 CNIS GCS Corresponds to the communications protocols used to access and control telecommunications services. This could be considered to be the e4 interface ... |
8d509819e1aa40caaede13a52e1e5386 | 101 615 | 15 Functions/Protocols/APIs to be developed | The scenarios provided in clause 6 can be used to identify the characteristics of the required interfaces and the ETSI work areas should be tasked with standardization activities. It is necessary to identify which new standards (if any) are required. In addition it could be recognized that future services will be devel... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 1 Scope | The present document covers the overall validation of the cross layer DCC functionality of the ETSI ITS architecture. It considers the cross layer DCC specification developed in ETSI TS 103 175 [i.1] and the cross layer concept described in ETSI TR 101 612 [i.2] and all other relevant DCC components in the communicatio... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 2 References | |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 3 Definitions, symbols and abbreviations | |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 103 175 [i.1], ETSI TR 101 612 [i.2] and the following apply: NAV: busy flag defined in [i.3] ns-3: discrete-event network simulator for Internet systems, targeted primarily for research and educational use. NOTE: ns-3 is free software... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: α Adaption parameter that control the DCC algorithm β Adaption parameter that control the DCC algorithm δ Default packet length for the simulations CBPTarget Target channel load CBRn CBR measured at the nth monitoring interval CLn Channel load calcu... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: A-DCC Adaptive DCC AIFS Arbitration Inter Frame Space BSM Basic Safety Message BTP Basic Transport Protocol CAM Cooperative Awareness Message CBP Channel Busy Percentage CBR Channel Busy Ratio CCA Clear Channel Assessment CCH Control Channel C... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 4 DCC theory | The aim of DCC is to avoid overloading the ITS-G5 radio channel. This can be done by different means as specified in ETSI TS 102 687 [i.5]. It has been shown recently that a pure message rate control can effectively limit the channel load [i.24], therefore most of the simulation results presented in the present documen... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5 Simulation results | |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1 Characteristics of common algorithms | |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1.1 Reactive table based algorithm | |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1.1.1 Simulator 1: Conclusions | Using Simulator 1, the following issues targeting reactive dynamic DCC algorithm are studied. • DCC synchronization • Channel load characterization • Non-identical receiver parameters The following conclusions are drawn: • It is very important to provide a solution to avoid the synchronization of DCC behaviour among IT... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1.1.2 Simulator 1: Introduction | The results of simulator 1 are detailed in paper [i.7], using a simulation tool combining ns-3 (network simulator) and SUMO (Simulation of urban mobility). Simulator 1 implemented the reactive DCC algorithm, controlling the message rate following a parameter look-up table (shown in table 2). Following simulations are p... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1.1.3 Simulator 1: Tools and setup | Simulator 1 uses the open discrete event simulation environment ns-3 (version 3.21) [i.9], combined with the traffic simulator SUMO (version 0.22) [i.10]. The key simulation modules, which are relevant to simulator 1, are illustrated in figure 1, where the modules highlighted in red are newly developed extensions to ns... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1.1.4 Simulation 1.1: Study on the synchronization issue of the DCC | In the present clause the results of the four different versions of Reactive DCC are shown for a homogeneous static highway scenario: DccReactive-1, DccReactive-2, DccReactive-3, and DccReactive-4. The performances of these mechanisms are compared with DccOff, which is the ITS-G5 MAC without distributed congestion cont... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1.1.5 Simulation 1.2: Study on channel load characterization | In the present clause the impact of the weight factor α of the channel load defined in equation 1 is studied based on the performance investigations of DccReactive-1 and DccReactive-3 for a homogeneous static highway scenario. The Cancel-and-Go mechanisms (DccReactive-2 and DccReactive -4) were omitted, because Cancel-... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1.1.6 Simulation 1.3: Study on non-identical sensing capabilities | In the present clause the impact of non-identical sensing capabilities is studied. Based on simulation 1.1 and simulation 1.2, simulation 1.3 targets DccReactive-3 (Wait-and-Go & Unsynchronized) and DccOff mechanisms. Figure 10 and figure 11 compare PDR and PIR of DccReactive and DccOff mechanisms for the cases where t... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1.2 Adaptive linear control algorithms | A common adaptive linear control algorithm is called LIMERIC which is described in clause 5.2.2.4. |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1.3 Comparison of different common algorithms | |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1.3.1 Simulator 2: Introduction | The results of simulator 2 are obtained from the iTETRIS ITS simulation platform. Three DCC methods are comparatively evaluated: • T-DCC - represent the congestion control obtained solely by the CAM triggering conditions • R-DCC - a lookup table-based reactive DCC mechanism following ETSI TS 102 687 [i.5] • A-DCC - an ... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1.3.2 Simulator 2: Tools and Setup | The iTETRIS ITS simulation platform has been used to conduct the performance evaluation of the DCC algorithms T-DCC, R-DCC, and A-DCC respectively. The architecture of iTETRIS depicted in figure 13 federates the traffic simulator SUMO [i.10], an ETSI ITS compliant extension of the network simulator ns-3 [i.9] and an IT... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.1.3.3 Simulator 2: Simulation results | The present clause provides the results of basic simulation-based experiments on the performance of three DCC algorithms. Figure 14 shows that the scenario is sufficiently dense to generate up to 100 % channel load if DCC is not used. The channel load reduction is pictured in red in figure 14 and is reached only by rel... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2 Mixed use of different algorithms | |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.1 Simulator 3: Conclusions | With simulator 3, coexistence of a reactive table-based DCC algorithm called CAM-DCC and LIMERIC [i.16], [i.17] has been studied. Firstly, it is observed that introducing LIMERIC vehicle ITS-S in a CAM-DCC network leads to only modest performance degradations of CAM-DCC in one of the test scenarios (Simulation Y.2), an... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.2 Simulator 3: Introduction | |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.2.1 Overview | The Medium Access Control (MAC) and Physical Layer (PHY) protocols for vehicular communications are specified in the IEEE 802.11-2012 [i.3] standard and well accepted. Differences exist, however, in other components. In particular, several congestion control algorithms are under investigation to improve packet error ra... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.2.2 DCC background | Most vehicular network applications require frequent exchange of status messages among vehicle ITS-S, which inform neighbours about vehicle positions and movements. These messages are referred to as Cooperative Awareness Messages (CAMs) in Europe (specified in ETSI EN 302 637-2 [i.6]) and Basic Safety Messages (BSM) in... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.2.3 CAM-DCC algorithm | When using DCC for controlling the radio channel congestion, it does not only shape the traffic into the MAC layer, but also limits CAM generation in the facilities layer. Therefore, the DCC algorithm with CAM generation is referred to as CAM-DCC in the present clause 5.2. The CAM generation rules and DCC mechanisms ar... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.2.4 LIMERIC algorithm | LIMERIC is a distributed and adaptive linear rate-control algorithm where each ITS-S adapts its message rate in a way such that the total channel load converges to a specified target [i.17]. The message rate of ITS-S (denoted as ()) is adapted every δ time using the linear equation 4: = 1 − × −1 + × ( ... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.3 Simulator 3: Tools and setup | |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.3.1 Simulation tools | The simulations are conducted with ns-2.34, a widely-used open source packet level network simulator [i.8]. The vehicle mobility scenarios were created with SUMO [i.10] (see also clause 5.1.1.3). SUMO allows modelling of intermodal traffic systems including road vehicles, public transport and pedestrians [i.13]. While ... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.3.2 Simulator configuration | The SUMO mobility simulator has been configured for a highway of length 4 km, with three lanes in each direction. As shown in figure 17, the middle part of the road is a winding section of linear length 375 m (with a radius of the winding part set to be 40 m). The winding section allows for testing the performance of t... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.3.3 CAM-DCC implementation | The CAM-DCC implementation is based on the following assumption and parameters. It is recalled that CAM-DCC relies on a table look-up and state machine to map channel load measures to transmit rates (see ETSI TS 102 687 [i.5]). Table 12 shows the specific values used in the simulations. While they may not be identical ... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.3.4 LIMERIC implementation | In the LIMERIC implementation, vehicle ITS-S generate CAMs when LIMERIC allows. The CAM generation rules based on vehicle dynamics are not applied. The parameters used in the LIMERIC simulations are summarized in table 14. The packet length d was set to the default length δ. Table 14: Parameters settings for LIMERIC in... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.3.5 Simulation scenarios | To be specific, this work is mainly trying to answer the following questions in the mixed work: 1) How does the performance of the day 1 deployed DCC change when an adaptive algorithm such as LIMERIC is introduced afterwards? 2) Can the performance of both algorithms be controlled by adjusting algorithm parameters? 3) ... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.3.6 Alternate CAM-DCC lookup table parameters | Compared to the default lookup table shown in table 12, the modified lookup table (table 15) increases the covered channel load range from [30 %, 60 %] to [40 %, 70 %]. Hence, a given channel load maps to slightly higher TX rates in the modified lookup table compared to the default lookup table outlined in table 12. Fo... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.3.7 Alternate LIMERIC target CBP | LIMERIC adapts the transmit rate in a way such that the channel load is driven toward the indicated target CBP ( ) and it converges to a CBP that is a smaller fraction of . Therefore, different target CBP values can lead to different convergence behaviours for LIMERIC. For studying the impact of the LI... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.3.8 Simulations with the different parameter settings for the algorithms | Simulator 3 was used with four different algorithm parameter settings. The description of these settings is listed in table 16. Table 16: List of algorithm parameter settings Simulation Simulation Name Description 3.1 Default parameter setting CAM-DCC look-up table set as in table 12 (default); LIMERIC target CBP set t... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.4 Simulator 3: Simulation results | |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.4.1 Introduction to the results | Packet Error Ratio (PER) and 95th percentile Inter-Packet Gap (IPG) are used as performance evaluation metrics. PER is defined as the ratio of the number of missed packets at a receiver from a particular transmitter to the total number of packets sent by that transmitter. IPG is defined as the elapsed time between succ... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.4.2 Simulation 3.1: Default parameter setting | As shown in figure 18, the 95th percentile IPGs for CAM-DCC vehicle ITS-S with LIMERIC vehicle ITS-S in the network (percentages 80 %, 50 % and 20 %) are lower than CAM-DCC operating alone and do not significantly change with the different percentages of LIMERIC vehicle ITS-S in the network. Further, CAM-DCC vehicle IT... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.4.4 Simulation 3.2: Modified lookup table | In the present clause results of simulations with the modified lookup table illustrated in table 15 together with a CBP target of 79 % are outlined. Figure 21: 95th percentile IPG of the mixed network with modified look-up table and LIMERIC target CBP as 79 %: (left) CAM-DCC; (right) LIMERIC Figure 22: PER of the mixed... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.4.5 Simulation 3.3: Modified LIMERIC target value | In the present clause, results of simulations with the default lookup table, illustrated in table 12, together with a reduced CBP target of 68 % are outlined. Figure 24 and figure 25 demonstrate similar trends as in figure 18 and figure 19. However, the absolute IPG values for LIMERIC vehicle ITS-S are increased since ... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.2.4.6 Simulation 3.4: Modified look-up table and LIMERIC target value | In the present clause, results of simulations with the modified lookup table, illustrated in table 15, together with the lower CBP target of 68 % are outlined. Figure 27: 95th percentile IPG of the mixed network with modified look-up table and LIMERIC target CBP as 68 %: (left) CAM-DCC; (right) LIMERIC Figure 28: PER o... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.