Intelligent Transport Systems - Telenor

More documents

Recommendations

Info

62 Initiator Edit group list Peer group Figure 7 Use case diagram for group list viewing and editing Figure 8 Use case diagram for adding a group Figure 9 Use case diagram for viewing the contact list Figure 10 Use case diagram for editing the contact list Delete group Add group Search for groups Initiator Add group Search Peer group Initiator Add existing group Create new group Search for groups Initiator View contact status Edit contact status Edit contact list View contact list Delete contact Add new contact Peer group Search for contacts F-10 is illustrated in Figure 8. When the user wants to add a group a search among the existing groups is initiated. If no group is found a new group is created. • F-11 View contact list: The user shall be able to see a list of personal contacts. This list will only contain the contacts that are online and participating in the same group as the user. Figure 9 illustrates this and shows that the user may edit the list. This is explained in the next requirement. • F-12 Edit contact list: The user shall be able to edit the contact list, either by deleting contacts or adding new ones by searching for contacts in the group. F-12 is illustrated in Figure 10 and is identical to the use case for requirement F-9. 3.2 Non-Functional Requirements The non-functional requirements for the ITS include both general requirements for the development and some performance attributes. Performance attributes are included to be able to validate the technology but are not of vital importance for this prototype. Later versions should seek to fulfill these requirements. Each nonfunctional requirement is assigned an identity in the format NF – , where is a sequential number. • NF-1 Network technology independence: The network technology shall be hidden from the user and be independent of the application so that any network technology can be used. Network technologies can be client-server protocols and peer-to-peer technology. One should easily be able to change a JXTA for J2ME implementation with for instance an HTTP and central server implementation. • NF-2 Run in SDK and JWT: The prototype should run both in the Software Development Kit (SDK) and the Java Wireless Toolkit from Sun. • NF-3 Run on a J2ME compatible device: The prototype should be able to run on a cellular phone or PDA supporting J2ME, for instance the Motorola Accompli 008 [3]. • NF-4 Usability: The user should be able to use the service application without training and should get to know it within 10 minutes. • NF-5 Security: Information that is exchanged in private room should be encrypted and not be available for others than the two parties of the conversation. Telektronikk 1.2003
• NF-6 Availability: The user should be able to connect to the network and register with the service in 90 % of the cases. • NF-7 Reliability: The service should run without problems for 12 hours without the user needing to restart the application. If disconnected, the user should be able to continue the session when logging on within 5 minutes. • NF-8 Cost: The user should be able to control the cost of the service usage, for instance by choosing how often to poll for incoming messages. • NF-9 Response time: The user should receive response from the relay within the poll interval (which can be set by the user). 4 Service Design This section will go through the design phase, and the class-, state-, sequence-, and collaboration diagrams of UML will illustrate this. A class diagram shows how the classes of a system relate to one another, while the state diagram focuses on the state changes in just one object. State diagram for the client will be presented here. While the sequence diagram shows how objects communicate with each other over time, collaboration diagrams show how objects interact according to space. 4.1 The Architecture The architecture is dependent on the network technology used. This prototype will use the JXTA network technology [4], and the JXTA for J2ME package that is designed for J2ME enabled devices. Mobile devices, represented as cell phones in Figure 11, are dependent upon a relay/proxy server on the Internet to connect to the JXTA network. The proxy servers are responsible for forwarding messages to the appropriate ITS client by sending it to the relay server where that particular client is registered. Network technologies used for transport will influence the way a mobile terminal will connect ITSSystem Client Telektronikk 1.2003 Mobile handset Wireless data communications Wireless communication infrastructure fixed network ITSSystem Client Mobile handset Internet to the relay. Figure 12 shows a scenario for a cell phone using GSM or GPRS. The client will then have to connect via a wireless link to a terminal access server before connecting to a proxy server. This is the most likely scenario for drivers, but a goal for the future is that the phone itself could decide the most appropriate transport technology to use at any given time and place and change this when appropriate. 4.2 Class Diagrams The service consists of three main classes; the NetworkClient, the DatabaseClient, and the ITSClient. NetworkClient is responsible for the network connection, while the DatabaseClient is responsible for interacting with the database on the mobile device. ITSClient is the main class and takes care of the interaction with the user through a graphical user interface (GUI), and uses NetworkClient and DatabaseClient to obtain necessary information. The overview class diagram for the system, hiding attributes and operations (methods), is illustrated in Figure 13. The responsibility for implementing the different parts is also shown in this diagram. Internet access server Internet Mobile handset ITSSystem Client Figure 11 The architecture of the ITS Figure 12 A cell phone connecting to the relay 63
Page 2 and 3:
Telektronikk Volume 99 No. 1 - 2003
Page 4 and 5:
Jan A Audestad (61) is Senior Advis
Page 6 and 7:
Figure 1 Example of MEMS 4 Therefor
Page 8 and 9:
6 Sensor Figure 3 Road with electro
Page 10 and 11:
8 Token to be trusted TTP operator
Page 12 and 13:
10 Road telematics also represents
Page 14 and 15: Figure 1 Mainstream taxonomy of ITS
Page 16 and 17: 14 may be fields where absolute con
Page 18 and 19: Figure 2 Development of passengers
Page 20 and 21: 18 presently being ported. (The way
Page 22 and 23: 20 tion, including intermodal and m
Page 24 and 25: Table 1 European Architecture Proje
Page 26 and 27: CALM system Management Entity (CME)
Page 28 and 29: Figure 5 ITS vehicle - Infrastructu
Page 30 and 31: Tore Arthur Worren (53) graduated f
Page 32 and 33: Tore Urnes (34) is Senior Research
Page 34 and 35: 32 traffic (e.g. due to an accident
Page 36 and 37: 34 prior to designing and deploying
Page 38 and 39: Haruo Ozaki (44) is an associate pr
Page 40 and 41: Number of subscriber 38 80 70 60 50
Page 42 and 43: 40 References 1 VICS Center. Februa
Page 44 and 45: 42 yourself!” were commonplace un
Page 46 and 47: 44 and dedicated terminals for MOBI
Page 48 and 49: 46 Map info registration Road datab
Page 50 and 51: Figure 4 Yellow pages with travel p
Page 52 and 53: 50 streamline the entry, maintenanc
Page 54 and 55: 52 form ensures the 3rd party servi
Page 56 and 57: Figure 7 Travel information site wi
Page 58 and 59: 56 ticular regard to movement and v
Page 60 and 61: 58 wide TETRA closed mobile radio n
Page 62 and 63: Figure 1 A user informing other use
Page 66 and 67: Figure 13 Overview of class diagram
Page 68 and 69: Figure 18 State diagram for ITSClie
Page 70 and 71: Figure 23 Sequence diagram for addi
Page 72 and 73: 70 :ITSClient :NetworkClient :Datab
Page 74 and 75: 72 Scenario 1: Jane travels through
Page 76 and 77: Nina Myren (37) is studying Media S
Page 78 and 79: Figure 3 Example of architecture 76
Page 80 and 81: Hilde Lovett (38) is Senior Researc
Page 82 and 83: Figure 2 Toys illustrating a stress
Page 84 and 85: 82 2 “Safety and efficiency in th
Page 86 and 87: Nina Myren (37) is studying Media S
Page 88 and 89: 86 of interest, stores and places a
Page 90 and 91: 88 oping the service with regard to
Page 92 and 93: Einar Flydal (53) is Senior Adviser
Page 94 and 95: Table 1 European cities with census
Page 96 and 97: 94 tion at peak periods have shown
Page 98 and 99: Table 2 Financial and economic comp
Page 100 and 101: Figure 5 Vehicle on Cardiff test tr
Page 102 and 103: 100 gest that 25 - 30 % of current
Page 104 and 105: Erik Fenstad (34) is Strategy Advis
Page 106 and 107: Dag Sanne obtained his BCom from th
Page 108 and 109: Figure 6 Some examples from the dev
Page 110 and 111: J. Edward Anderson is Chairman, Pre
Page 112 and 113: 110 emergency braking deceleration,
Page 114 and 115:
112 not yet available, it is comman
Page 116 and 117:
114 nals to the central computer vi
Page 118 and 119:
116 11 Irving, J H et al. Fundament
Page 120 and 121:
118 on IP technology and implemente
Page 122 and 123:
120 Conclusion The “circuit switc
Page 124 and 125:
122 Telektronikk 1.2003
Page 126 and 127:
Figure 1 Network configuration Figu
Page 128 and 129:
Figure 5 Interconnection of network
Page 130 and 131:
128 • Smart dust about one cubic
Page 132 and 133:
3) The invariant part of the virus
Page 134 and 135:
Figure 6 Access control 132 Initiat
Page 136 and 137:
134 In order to obtain a high level
Page 138 and 139:
Page 140 and 141:
Einar Utvik (62) worked in Televerk
Page 142 and 143:
140 Norwegian delegation to PP-02 M
Page 144 and 145:
Elected Council members Elected Cou
Page 146 and 147:
144 four-year period in the context
Page 148 and 149:
146 an active role to play in coord
Page 150 and 151:
148 of candidatures for the elected
Page 152 and 153:
Ingunn Yssen, Senior Gender Adviser
Page 154 and 155:
152 5.19.2 Agenda for Connectivity
Page 156 and 157:
Page 158 and 159:
156 MEMS Micro-Electromechanical Sy
Page 160 and 161:
158 LRT Light Rail Transit Light Ra
show all

Intelligent Transport Systems - Telenor

Create successful ePaper yourself

Delete template?

Save as template?