Intelligent Transport Systems - Telenor

More documents

Recommendations

Info

Figure 13 Overview of class diagram for ITS Figure 14 Detailed view of NetworkClient Figure 15 The datatype ITSMessage 64 Bjørg Lyngstad Datatypes ADVANCEDSEARCH : int = 2 SIMPLESEARCH : int = 1 Runnable (from java.lang) NetworkClient exception NetworkClient Every interaction with the network is done through the NetworkClient. This class will be implemented using JXTA for J2ME and will then be able to interact with any device on the JXTA network. NetworkClient takes care of the basic tasks associated with peer group membership, like group- and user discovery, and the joining and creation of groups. Since the only supported protocol in MIDP for communication over the network is HTTP, the NetworkClient uses a JXTA relay. At specified intervals it asks the relay if messages have arrived for the user. NetworkClient imple- 1 MIDlet (from javax.microedition.midlet) ITSClient 1 1 1 DatabaseClient Bjørg Lyngstad & Jorunn Kaasin closeNetworkConnection() joinGroup(groupName : String, groupId : String) : boolean leaveGroup() : boolean run() searchContact(contact : String) : boolean searchContacts(contactList : String[]) : boolean searchForGroup(groupName : String, searchType : int) : void sendMessage(msg : ITSMessage) : boolean setPollInterval(seconds : int) NetworkClient(client : ITSClient, relayAddress : String, relayPort : int, clientName : String) getInstance(client : ITSClient, relayAddress : String, relayPort : int, clientName : String) : NetworkClient ITSMessage CONTACTINFO : int = 2 GROUPINFO : int = 1 MESSAGE : int = 3 ITSMessage(content : String, receiver : String, sender : String) ITSMessage(content : String, receiver : String, sender : String, type : int) getContent() : String getReceiver() : String getSender() : String getType() : int Jorunn Kaasin CommandListener (from javax.microedition.lcdui) ments java.lang.Runnable and creates a thread for the task of polling the relay. The public attributes and methods of NetworkClient are shown in Figure 14. The non-functional requirement NF-1 states that the system should be independent of the network. The realization of the NetworkClient fulfills this requirement, since it hides the interaction with the network for the user, and the exchange of data inside the system is systemspecific, not network specific. Communication and exchange of information and data is done using an ITS specific datatype called ITSMessage, included in the Datatypes packages. The class diagram for ITSMessage is shown in Figure 15. The ITSClient extends the MIDlet class of J2ME, and since MIDlet is the basic unit of execution in MIDP, ITSClient is responsible for the application entry and leaving of states during the midlet’s whole life cycle. The different states are pause, active and destroyed. To react to the different command actions received from the user, ITSClient implements the CommandListener interface. Telektronikk 1.2003
The ITSClient will implement the graphical user interface and includes all the methods used to create the screens with the appropriate text, buttons, lists and textboxes. ITSClient will use the DatabaseClient to retrieve and store information to the database, and use the NetworkClient to communicate with the JXTA network. The only public method, beside the constructor and inherited methods, is receiveMessage(ITSMessage). The NetworkClient calls this method when an incoming message has arrived for the user. The class diagram for the ITSClient and the DatabaseClient is illustrated in Figure 16. The DatabaseClient uses the Record Management System (javax.microedition. rms) of MIDP to achieve a mechanism for MIDlets to persistently store data and later retrieve it. RecordStore is the class representing the collection of records that contributes to the database. The database will consist of contacts, contact ids, groups, and group ids. To make the ITSClient more independent of the network and storage retrieval of data, some ITS specific exception classes are introduced. The hierarchy is shown in Figure 17. 4.3 State Diagram for the ITSClient Figure 18 shows the state diagram for the ITSClient. Regular UML syntax is used, so Telektronikk 1.2003 MIDlet(from javax.microedition.midlet) ITSClient ITSClient() receiveMessage(msg : ITSMessage) : void commandAction(c : Command, d : Displayable) : void DatabaseClient addContact(contact : String) : Boolean addGroup(groupName : String, groupId : String) : Boolean deleteContact(contact : String) : Boolean deleteGroup(groupName : String) : Boolean getContacts() : String[][] getGroups() : String[][] getUserName() : String storeGroups(groups : String[][]) : boolean getInstance() : DatabaseClient 1 1 CommandListener (from javax.microedition.lcd... square brackets represent conditions and the oval ones represent states. The state diagram can to a certain degree be translated directly to the screen flow illustrated later in this section, but the states concerning communication in private mode is then left out. From the diagram it seems that it is only possible to receive messages (that is, messages from Exception (from java.lang) ITSException msg : String ITSException() getMessage() Figure 16 Detailed view of the ITSClient and the DatabaseClient DatabaseException NetworkException Figure 17 The exceptions in the ITS 65
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 64 and 65: 62 Initiator Edit group list Peer g
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?