The FLYWAY® Information Exchange

1. General

his page just consists of tables, listing the commands and responses that need to be exchanged between FLYWAY® system units. They are not complete, but will be filled in as work on specifications progress. Some details will be left out, for patent reasons. Symbols used: Beamcar cabin/mobile unit Central computers Local LAN server Local LAN terminal (for traveler interface) Node computer Propulsion car/mobile unit Stationary Bluetooth unit at station cubicle Stationary Bluetooth unit in beam (node connected) Stationary Bluetooth unit at station (traveler interface) Travelerīs mobile Bluetooth unit

As shown on other pages, the data communication in an automatic transport system is rather complex. Each of the tables below deals with a separate type of network, where the communicating units at each end are indicated. It will be noted, however, that the source and destination units are not always on those networks. Rather, they are the real source and destination units for the communication indicated. In other words, much communication takes place in a kind of relay, from one network to another. Contents of this page: General. The Bluetooth RF-network between stationary units and beamcar units. The Bluetooth RF-network between travelers and station terminals. The Bluetooth RF-network between travelers and beamcar cabins. Between station terminals and servers. Between station servers and central computers. Between nodes and stationary Bluetooth units. Between nodes and central computers. Between beamcars and cubicles. The referens numbers in the tables indicate where comments to a message are to be found. The same messages will often appear in several tables, and itīs wasteful to write the same comments more than once.

2. The Bluetooth RF-network between nodes and beamcar units

Nr.	Subject	Source	Destination	Parameters & Comments
2:1	Order to pick up someone/something			Parameters: Travelerīs identity, time, place & berth of pickup-destination
2:2	Cancellation of pickup-order			Parameters: Travelerīs identity, time, place & berth of pickup-destination
2:3	Speed directives from node			Parameters: Codes that provide speed adjustments information to fit the car into the assigned timeslot. Note: Issued when the beamcar approaches a weaving point or for other reasons.
2:4	Malfunction announcement			Parameters: Codes that signify degree of seriousness: Can the car continue for a while, should be taken ot now, or can it move. Notes: Central computers will have to be informed, but the node computer has to take the first decision what to do, considering the general traffic situation. A car on duty would also inform passengers.
2:5	Travel info to passengers			Parameters: Delays, reroutings, etc. Notes: This info could also be generated by the local node. And it would be generated by the car itself, in response to 2:6.
2:6	Information about altered travel routes			Parameters: Delays, reroutings, etc. Notes: Generated by the node or the central computers.
2:7	Travel log			Parameters: Where, when, undue waiting times, how far it has traveled, etc. Notes: The system makes statistics to successively improve service. It also needs to know when a car is due for a checkup.

3. The Bluetooth RF-network between travelers and station terminals

Nr.	Subject	Source	Destination	Parameters & Comments
3:1	Traveler orders a beamcar			Parameters: Travelerīs identity, Beamcarīs category or identity, time & place of pickup spot. Note: A traveler could teoretically order as many cars he can afford.
3:2	Traveler cancels an order for beamcar			Parameters: Travelerīs identity.
3:3	Acknowledgement of order			Parameters: Travelerīs identity, Beamcarīs category or identity, time & place of pickup spot. In response to 1.
3:4	Acknowledgement of cancellation			Parameters: Travelerīs identity, Beamcarīs category or identity, time & place of pickup spot, amount that will drawn from account. In response to 2.
3:5	Information regarding ordered car			Parameters: Travelerīs identity, Beamcarīs category or identity, time & place of pickup spot, when a car will be available, what identity or category, OR if the order cannot be effectuated, OR a reject if the traveler is not credit-worthy. In response to 1.

4. The Bluetooth RF-network between travelers and beamcar cabins

Note: The cabin will also have a manual terminal for those travelers that do not have Bluetooth units available.
Those are included here, for convenience.

Nr.	Subject	Source	Destination	Parameters & Comments
4:1	Passenger requests access to car			Parameters: Travelerīs identity. Note: In response to this, the cabin will be lowered (if needed), the doors opened.
4:2	Passengerīs destination			Parameters: destination.
4:3	Passenger requests the journey to begin			Parameters: Travelerīs identity. Note: In response to this, the doors will close and the cabin will be lifted to commence journey.

5. Between station terminals and servers

Nr.	Subject	Source	Destination	Parameters & Comments

6. Between station servers and central computers

Nr.	Subject	Source	Destination	Parameters & Comments

7. Between nodes and stationary Bluetooth units

Nr.	Subject	Source	Destination	Parameters & Comments

8. Between nodes and central computers

Nr.	Subject	Source	Destination	Parameters & Comments
8:1	Regular traffic reports			Parameters: Carsī identities, positions, destinations, etc. Note:
8:2	Accident & malfunction reports			Parameters: Carsī identities, positions, destinations, etc. Note:
8:3	Reports from individual cars			Parameters: Carīs identity, position, destination, nature of report. Note: Could well be reports or requests from passengers
8:4	Reports to individual cars			Parameters: Carīs identity, nature of report. Note: Could well be passenger information, or request that a particular passenger get in touch
8:5	Reports to many or all cars			Parameters: Carsī identities, nature of report. Note: Could well be passenger information

9. Between Beamcars and Cubicles

Nr.	Subject	Source	Destination	Parameters & Comments
9:1	Command to open cubicle doors			Parameters: Carīs identity & position, cubicleīs identity. Note: If carīs position checks out, the cubicle doors are opened.
9:2	Command to close cubicle doors			Parameters: Carīs identity & position, cubicleīs identity. Note: If carīs position checks out, the cubicle doors are closed.
9:3	Cubicle doors are closed			Parameters: Carīs identity & position, cubicleīs identity. Note: If cubicleīs identity checks out an d all is OK with the cabin, the beamcar takes off.
9:4	Iīm coming in to land			Parameters: Carīs identity, type & position, cubicleīs identity. Note: If carīs type checks out, the cubicle answers in the affirmative. The car needs to have the right size and door arrangements. Thus; the right "type".
9:5	Youīre OK to land			Parameters: Carīs identity, cubicleīs identity. Note: In response to 9:4.
9:6	Youīre NOT OK to land!			Parameters: Carīs identity, cubicleīs identity, time when available. Note: In response to 9:4. Reasons given could be: Cubicle occupied, car has wrong type, car comes from wrong directions, cubicle not available for traffic for some reason or another.