[go: up one dir, main page]

WO1993016539A1 - Procede et appareil de communication - Google Patents

Procede et appareil de communication Download PDF

Info

Publication number
WO1993016539A1
WO1993016539A1 PCT/NZ1993/000004 NZ9300004W WO9316539A1 WO 1993016539 A1 WO1993016539 A1 WO 1993016539A1 NZ 9300004 W NZ9300004 W NZ 9300004W WO 9316539 A1 WO9316539 A1 WO 9316539A1
Authority
WO
WIPO (PCT)
Prior art keywords
devices
routing list
message
routing
path length
Prior art date
Application number
PCT/NZ1993/000004
Other languages
English (en)
Inventor
Russell William Gibbard
John Stewart Cameron Yaldwyn
Roger Neil Ballantine
Robert William Platts
Alan Christopher Sutherlan
Original Assignee
HER MAJESTY THE QUEEN IN RIGHT OF THE GOVERNMENT OF NEW ZEALAND, acting by and through THE CHIEF OF DEFENCE FORCE
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by HER MAJESTY THE QUEEN IN RIGHT OF THE GOVERNMENT OF NEW ZEALAND, acting by and through THE CHIEF OF DEFENCE FORCE filed Critical HER MAJESTY THE QUEEN IN RIGHT OF THE GOVERNMENT OF NEW ZEALAND, acting by and through THE CHIEF OF DEFENCE FORCE
Publication of WO1993016539A1 publication Critical patent/WO1993016539A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/02—Topology update or discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/30—Routing of multiclass traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection

Definitions

  • the present invention relates to a method and apparatus for communicating between a number of devices. More particularly, but not exclusively, the present invention relates to a method of and an apparatus for communicating between units of an artillery fire control system.
  • GB 2170079 discloses a communications network in which computers communicate via local area networks (LANs) and bridging devices connected to the LANs which are interconnected by a satellite backbone.
  • the bridging devices generate routing lists indicating which LAN each listed computer is connected to.
  • the bridging devices however only learn of the LAN to which a computer is connected once data is relayed from that computer.
  • the bridging devices are not configured at start-up to know the location of each device on the network.
  • only bridging devices have routing lists, thus all devices do not know what other devices are connected to the network at any time.
  • the routing lists do not include a path length parameter to enable bridging devices to store the shortest path between devices. Also, as routing lists are not communicated between devices, they can not be scrutinised for errors.
  • SUBSTITUTE SHEET EP 404337 discloses a mesh connected network of host computers linked through switches.
  • the switches contain completely configured routing lists.
  • This invention relates to a statically configured configured systems rather than to a method of establishing and maintaining routing lists in a dynamic system.
  • EP 365337 discloses a routing engine for routing communications between a number of LANs.
  • the routing engine records which LAN each source computer is on as it monitors communications. If a destination address is one of the computers listed in the routing engine the data packet will be directed to the appropriate LAN, otherwise it will be sent to all LANs.
  • This specification does not disclose a method for generating complete routing lists for all devices of a network at start-up. Nor does it disclose the use of a path length parameter in the routing list or a method of reconfiguring the system should a link fail.
  • a method of communicating between a plurality of devices wherein each device maintains a routing list containing the devices to which it can communicate and the directly connected device to which communications should be directed to communicate with each device, said method comprising the steps of:
  • each of the directly connected devices updating its routing list to include an entry for the newly connected device
  • each of the directly connected devices transmitting a message to the newly connected device informing the newly connected device of its presence and, in the case of a bridging device, the other devices which can be accessed through it;
  • said newly connected device updating its routing list in response to the transmitted messages to include listings for each of the directly connected devices, and for every other device known to these directly connected devices;
  • a method of voice/data communication between a plurality of devices over a communications link comprising the steps of:
  • i/ a device requesting voice communication sending a digital start message to every other device, either directly or through other devices, requesting that data transmission cease to allow voice communication; ii/ each device acknowledging receipt of the request for voice communication, either directly to the device requesting voice communication or through other devices; iii/ the device requesting voice communication transmitting voice communications; iv/ each device, apart from the device requesting voice communication, receiving the voice communication and monitoring the transmission for a message indicating the return of data communication; and v/ at the end of voice communication, the device requesting voice communication sending a digital stop message to every other device informing the device that digital communication may resume.
  • Figure 1 shows a block diagram of the smart modem.
  • SUBSTITUTE SHEET Figure 2 shows a possible configuration of devices.
  • Figure 3 shows a further possible configuration.
  • the "smart modem" referred to in the specification is shown in Figure 1.
  • Central processing unit 1 can store to and retrieve data from memory 2.
  • the central processing unit may consist of Motorola 68302 microprocessor using proprietary extended CCITT X.25 protocol.
  • Central processing unit 1 may communicate with other devices via twisted pair line modem 3, radio modem 4, serial port 5 or telephone network modem 6.
  • Twisted pair line modem 3 may transmit data modulated on a 32 kilohertz carrier at 2 or 4 kbps. in this way voice transmissions can be made on the lower part of the spectrum without interfering with data transmission.
  • the smart modem may be connected to other devices via twisted pair line modem 3 by inexpensive twisted pair lines.
  • CPU 1 may communicate with other devices via a radio link.
  • Radio modem 4 may be connected to an appropriate radio unit to enable communication to another device by radio link. Data may be transmitted using fast frequency shift keying at 150 or 1200 bps. To avoid the need to digitise voice communication and use high frequency radio equipment the smart modem may send data only when voice communications are not in progress.
  • Serial port 5 allows direct communication to other digital devices. Serial communication may be according to RS232, RS422 or Mil-188 standards.
  • central processing unit 1 may communicate with a telephone exchange via telephone network modem 6. This may enable an artillery battery to communicate with a regimental computer or commander via a line or cellular telephone link.
  • Display 7 may display status information and programme options of the smart modem. When a smart modem is used as a gun display unit, display 7 may display firing instructions. When a smart modem is used as a command post display 7 may display acknowledgements from gun display units. Keypad 8 allows selection of configuration options.
  • Speaker 9 enables voice communications from other devices to be heard and microphone 10 allows voice communications to be transmitted from the smart modem to other devices.
  • Switch 11 may be depressed to initiate voice communications and- released to terminate voice communications.
  • Units COl and C02 are smart modems as shown in Figure 1 used as command posts.
  • Devices G01 to G04 are smart modems used as gun display units.
  • separate smart modems are used as radio link bridging devices, although all other devices have radio ports. This is for strategic reasons to move radio transmission away from the battery positions.
  • B01 and B02 are field computers. These will typically be portable laptop type computers.
  • BOl may be the main command computer and B02 a back up computer.
  • Computer BOl may be linked to a regimental command post via a telephone port in modem COl o by radio link, etc.
  • Units GOl to G04 are gun display units. These devices display the firing instructions supplied from command post COl in conjunction with computer calculations from computer BOl.
  • SUBSTITUTE SHEET Computer BOl may be supplied with information regarding the characteristics of each gun and the ammunition available for eac gun. Upon the computer being supplied with information as to th location of each gun and the position of a desired target the computer may calculate the trajectory, charge, bearing, fuse setting and elevation required for a particular gun and lot of ammunition. Firing parameters for a number of targets may be stored in the computer awaiting a command to proceed with a mission. As a firing mission is selected the firing data for each gur may be sent to command post COl. The firing data for each gu may be transmitted to each gun display unit via lines L01 and L02 and radio link R.
  • the firing data for each gun display unit is transmitted with th unique address (callsign) of the gun display unit. In this way only the firing data pertaining to that gun display unit is received and displayed by the gun display unit.
  • Other units may however enter a "spy mode" in which they can request information directed to another gun display unit.
  • the gun display unit doe this merely by sending a "spy" request to the unit COl, which responds with the data that it had previously sent to the other gun display unit. This may be useful when a gun display unit fails so that instructions may be relayed between adjacent guns.
  • Firing command signals are sent as part of the firing data to th gun display units. For example a command to fire "at my command may be transmitted to the gun display units and displayed on the displays of the gun display units. Before the command is acknowledged the word "ACK" flashes on the display. Gunners may acknowledge receipt of the command on keypads on the gun display unit with the acknowledgment being transmitted back to the command post COl. The word "ACK” then stops flashing. A statu table displayed on the display of command post COl may indicate the acknowledgment of commands. Fire commands may be sent by voice. These commands may also be acknowledged at the gun display units.
  • serial link SI SUBSTITUTE SHEET
  • gun display units G01 and G02 and smart modem SOI are connected by a twisted pair line L01.
  • Smart modem SOI communicates with smart modem S02 via a radio link R, each smart modem communicating via a suitable radio unit.
  • Smart modem S02, gun display unit G03 and command post smart modem C02 are connected by twisted pair line L02.
  • Auxiliary computer B02 is connected to command post smart modem C02 via a serial link.
  • Serial links SI and S2 may be RS232, RS422 or Mil-188 interfaces.
  • the present invention enables each device of the network to know at any time which devices are connected to the network and the port to which a device should communicate to relay communications to a desired device.
  • the invention enables the devices of a network to configure themselves as the network is set up or a device removed.
  • the network is configured so that the optimum connection paths between devices are established.
  • the invention enables "self healing" so that should a device fail an alternative route can be established to route messages, where available.
  • the design of the present invention allows any form of configuration of devices, such as daisy chain, star or random as the network is self configuring. This allows great flexibility in operation.
  • Data may be transmitted over twisted pair lines L01 and L02 modulated on a 32 kHz carrier at 2 or 4 kbps. Voice transmissions may be sent simultaneously on the lower frequency part of the spectrum.
  • radio links are either data or voice communication, but not both simultaneously.
  • Each device has a unique identification code (callsign) . This may be set manually or may be attributed to the device as it connects to the network.
  • An enhanced X.25-based protocol is used in which a data frame includes fields for the sender's identification code and the identification code of the destination device. This enables a frame of data to be transmitted to one of several receivers.
  • each communicating device COl, G01, G02, SOI, S02, G03 and C02 stores a routing list.
  • This routing list includes a listing for each device connected to the network (including devices such as computers BOl and B02) .
  • the port through which the bridging device communicates is recorded. This may be via a serial port as between BOl and COl; a line port as between COl and SOI; a radio port as between SOI and S02, or a telephone port.
  • the routing list also records whether the connection between the device and another device is a direct link (as between COl and SOI) or whether an intermediate bridging device is required (as between COl and S02, where SOI is the bridging device) .
  • a number is also recorded against each device in the routing list indicating the path length to that device.
  • Each line or serial link carries a path length value of 2 whereas a radio link carries the value of 3.
  • the radio link carries a value of 3 so that faster and more reliable links such as a line or serial link will be preferred if that option is available. It will be appreciated that in more complex configurations there may be multiple paths between one device and another device. In these situations the shortest path is selected.
  • the left hand column lists the devices which COl knows are on the network.
  • the next column indicates whether the device is connected via COl's serial, line or radio link.
  • the third column indicates whether the connection to the device is direct or through a bridging device. If the connection is through a bridging device then the directly connected bridging device to which communications should be sent is listed.
  • the fourth column gives a value representing the path length.
  • the first line indicates that device COl can communicate with device BOl via COl's serial port, the link is direct and the path length is 2.
  • the link to auxiliary computer B02 is via the line port of device COl and the device to which a message to B02 should be sent in the first instance is smart modem SOI.
  • the path length is 9 representing two line links (2 each), one serial link (2) and one radio link (3) .
  • the other devices have corresponding routing lists.
  • the path length column is used to determine which route a signal should be sent by, if there is more than one path.
  • a high value (ie. maximum value) in the path length field indicates a device can no longer be accessed by that route.
  • beacon message may be transmitted by a device to all directly connected devices.
  • a beacon message is not addressed to any specific device, and so requires no specific acknowledgment according to the X.25 protocol.
  • a beacon message contains the sender's callsign, but the destination field is null, indicating that all devices can receive the message.
  • the signal thus informs directly connected devices of the senders existence on the network.
  • Beacon messages may be transmitted at a fast rate when the devic is initially configured to ensure that all devices are alerted o its presence and a stable configuration can be rapidly achieved. Once a stable configuration has been reached beacons can be sent out at longer intervals so that other devices in the network are continually updated that the transmitting device remains on the network.
  • the data section of a beacon message contains the callsigns of the directly connected devices known to the transmitting device. Thus, if a device receiving the transmission finds itself absent from this list, then it will be apparent that the routing list o the transmitting device requires updating.
  • An identification message may also be used. This has a similar format to a routing list update message, except that it is used to identify the sender. It is addressed to a particular device and so must be acknowledged. As beacon messages are not acknowledged they must be transmitted at regular intervals. An identification message is sent to a new device to inform it of the presence of the sender on the network. It will not be repeated if it is acknowledged.
  • An identify yourself message may be used to determine whether a device is still on the network.
  • a short message may be transmitted to a device and, if not acknowledged, the sender can assume the device is no longer connected. This will result in a high value being assigned to the path length for that device.
  • a routing list update message (which must be acknowledged) is used for this purpose.
  • a routing list update message may be sent from a bridging device to a directly connected device to notify it of the devices that are connected directly or indirectly to other ports of the bridging device. This indicates to the device which other devices can be accessed by that bridging device. This message is sent from a directly connected bridging device to a new device in response to a beacon from the new device. This enables a newly connected device to create an up-to-date routing list.
  • routing list acknowledgment message is returned to the transmitting device to confirm that a receiver has the most up to date version of the routing list.
  • SUBSTITUTE SHEET connected device receive the beacon messages and update their routing lists to include the newly connected device, if it is not already in their routing list. Bridging devices then send routing list update messages back to the newly connected device to let it know of their connection and the devices accessible through them. Other devices send identification messages to inform the newly connected device of their direct connection.
  • the identification message or routing list update message is repeated until acknowledgement is received. If no acknowledgement is received this indicates there is a fault on the line and the device is marked as "not connected" in the routing list (i.e: a high value in the path length).
  • the newly connected device forms an initial routing list from these communications consisting of the information provided by directly connected devices.
  • the newly connected device Upon receiving a routing list update message from a bridging device the newly connected device will be informed of all devices that can be accessed through that bridge. When the locally connected non-bridging devices send identification messages the newly connected device will know that these devices are directly connected to it, rather than through a bridging device.
  • the routing list set up by the newly connected device contains the callsigns of all locally connected devices as well as those accessible via bridging devices.
  • beacon messages sent by the newly connected device will include the callsigns of all devices that sent routing list update or identification messages to it. Any device that receives such a beacon will not respond with a routing list update (or identification) if it finds its own callsign included in the beacon.
  • Beacons continue to be sent at a fast rate (every 5 seconds) until no further identification or routing list update responses are received to a predetermined number of consecutive beacons.
  • SUBSTITUTE SHEET Beacon messages are then transmitted at a slower rate (for example every 25 seconds).
  • the routing list update message consists of the callsigns of devices connected to the bridging device and their updated path lengths. Bridging devices further downstream likewise transmit updated routing lists to devices now connected further downstream. Other devices merely update their own routing lists. In this way the update is propagated throughout the network.
  • the routing lists of all other devices must be updated to show that the device is no longer in the network.
  • a device will assume that a directly connected device has been removed when a beacon message has not been received for a predetermined period. This period may be one minute where a slow beacon rate of one beacon per 25 seconds is used.
  • a device will assume that a directly connected device has been removed if no response is received to a message sent to it, even after retrying. In either case, the bridging device will transmit an "identify yourself" message to the device. If no acknowledgment is received after a specified number of retries, the device will be flagged as disconnected in the routing list. This disconnection is reflected by a high value in the path length field.
  • any previously connected bridging device Upon disconnection of a device, any previously connected bridging device updates its routing list and transmits this updated routing list to all devices connected to its other ports.
  • Directly connected bridging devices will likewise update their routing lists (by giving a high path length value to the device) and pass the updated routing list on to all directly connected devices downstream.
  • each device to store in its routing list all possible paths between it and a given device.
  • the path having the shortest path length parameter will be utilised. Should one path fail then the path having the next lowest path length parameter is used. This method would however lengthen the routing list and thus the time required to configure the system.
  • the path having the shortest path length will be entered in the routing list.
  • a routing list update message is received by a device it compares the path length of each device in the message with the path length it has stored for that device in its routing list (taking into account the path length between communicating devices). If it has an entry for a device having an alternate path of shorter path length it sends a routing list update message back to the sender including the shorter path for that device. It should be noted that the path must not only be shorter but alternate (ie: not via the bridging device it is communicating with) . The sender updates its routing list, replacing the old entry for the shorter new entry, and sends a routing list update message including the new entry to other directly connected devices.
  • routing list update messages back indicating that the devices on either side of the failed device have high path lengths.
  • a bridging device having an alternative path with a lower path length receives this message it sends back a routing list update message indicating the alternate path. This routing list update message propagates back to the device just prior to the failed device until all devices have updated routing lists including the alternate path.
  • the routing lists of converted devices will be updated to restore the entry to the new shorter path.
  • a routing list update message is transmitted from smart modem S02 to smart modem SOI to update SOl's routing list.
  • This routing list update message consists of a list of the devices which can now be accessed through smart modem S02 along with the path length to each device (i.e.: B02:4, C02:2, G03:2, G04:2) .
  • Smart modem S02 also transmits a routing list update message to G04 consisting of a list of devices which can be accessed downstream of S02 along with the- path length to each device (i.e.: B01:7, C01:5, G01:5, G02:5,. S01:3) .
  • G04 Upon receipt of the routing list update message from S02, G04 forms the following entries in its routing list: (S02 L dir 2), (BOl L S02 9), (COl L S02 7), (GOl L S02 7), (G02 L S02 7), (SOI L S02 5). G04 then sends a routing list update acknowledgement message to S02.
  • G03 upon receiving G04's beacon adds the entry (G04 L dir 2) to its routing list. G03 then sends an identification message to G04. G04 receives the identification message from G03 and adds the entry (G03 L dir 2) to its routing list. It then sends a routing list update acknowledgement message to G03.
  • C02 Upon receiving the beacon from G04, C02 adds the entry (G04 L dir 2) to its routing list. It then sends a routing list update message to G04 of the form (B02:2). Upon receiving the routing list update message from C02 G04 adds the entries (C02 L dir 2) and (B02 L C02 4) to its routing list. G04 then sends a routing list update acknowledgement message to C02.
  • S02 sends a routing list update message to SOI of the form (B02:4, C02:2, G03:2, G04:2).
  • SOI adds the entry (G04 R S02 5) to its routing list. Only this entry is added because the rest are already present.
  • SOI then sends a routing list update message to COl, GOl and G02 of the form (B02:7, C02:5, G03:5, G04:5, S02:3).
  • COl receives the routing list update message from SOI and adds the entry (G04 L SOI 7) as the other devices are already present.
  • GOl likewise receives the routing list update message and adds the entry (G04 L SOI 7).
  • G02 likewise receives the routing list update message and adds the entry (G04 L SOI 7).
  • the routing lists for the devices are as shown in Table 2.
  • the routing list tells the device if it is directly connected to another device or not. If it is directly connected the device may simply directly communicate with another device. Where however a device is connected to another device through a bridging device, the routing list tells the device to which bridging device the message should be sent in the first instance. Where more than one possible route is available the device will select the bridging device having the shortest path length to the selected device. Accordingly, if GOl wished to communicate with G03, it would refer to its routing list to determine where the message should be sent in the first instance. The routing list for GOl indicates that communications to G03 should be sent through SOI. Accordingly, the message would be addressed to SOI in the first instance.
  • SOI Upon receiving the message from GOl, SOI would look to its routing list, which indicates that transmissions to G03 should be sent via S02. Accordingly SOI would transmit the message to S02. S02 would then look to its routing list to find that it was directly connected to G03. The message would thus be transferred to G03.
  • CO2 would update its routing list to include a high path length value for COl and send a routing list update message with a high path length for COl to C02 (ie: C01:H) .
  • S02 would update its routing list to include a high path length value for COl and send a routing list update message with a high path length for COl to C02 (ie: C01:H) .
  • S02 would update its routing list to include a high path length value for COl and send a routing list update message with a high path length for COl to C02 (ie: C01:H) .
  • S02 would update its
  • SUBSTITUTESHEET routing list to enter a high path length value for device COl and send a routing list update message having a high path length value for COl to SOI (ie: C01:H).
  • SOI would check its path length for device COl and find that its length in its routing list is 2.
  • SOI would send a routing list update message to S02 including the entry (C01:2).
  • S02 would update its entry for COl to (COl R SOI 5) and send a routing list update message to C02 of the form (C01:5).
  • C02 would update its routing list to include an,entry (COl L S02 7).
  • communications would be rerouted to the radio link between SOI and S02.
  • the network can rapidly reconfigure itself when changes occur to the network to provide the optimum communication path.
  • each device wishing to transmit must wait a different length of time before transmitting. Accordingly, each device must have a different delay to ensure that no two devices commence transmission simultaneously.
  • the position of a device's own call sign ip, its own routing list is different for each device. Accordingly, the position of a device in its own routing list may be use to assign a delay to each device.
  • SUBSTITUTE SHEET access priorities This value may be the position of the call sign of the last device to transmit on the network.
  • bridging devices One further problem faced is the acknowledgement of messages passing through bridging devices. Where a number of bridging devices are used the bridging device will acknowledge receipt of the message from the previous device and then try to on-transmit the message.
  • a higher level acknowledge message may be used. This higher level acknowledgement is different from a normal acknowledgement and indicates that a message has reached the device it was destined for. This message may be relayed between bridging devices in the normal way.
  • FIG. 3 a possible operational field configuration is shown.
  • this network employs two frequencies, one for local gun communications, and another for battlefield communications.
  • a regimental command post computer 20 is connected to an artillery battery computer 21 via smart modems 22 and 23.
  • Smart modem 19 supplies meteorological information to smart modems' 22 and 23 via a radio link.
  • Smart modem 24 provides data from a mortar locating radar via a line connection.
  • a forward observer 28 is connected to smart modem 23 by a radio link. Forward observers can send voice communications or data providing information as to the accuracy of fire.
  • a second battery computer 33 is connected on the same battlefield network via a radio link between smart modems 23 and 34.
  • the local gun network for the first battery consists of gun display units 25 connected through a radio link to smart modem 18, and gun display units 26, 27, 29, 30 and 31 connected via
  • gun units 34, 35 and 36 are connected by line to SM 37.
  • the present invention allows for flexible interconnection of devices without requiring configuration by field staff.
  • the network also determines the best route for messages to be transmitted and is self healing in case a link in the network becomes inoperative (provided an alternative link is available) .
  • the invention also allows for the transmission of voice or data communications over all links of the network without requiring Digitalization of the voice communication or sophisticated radio equipment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Procédé de communication entre dispositifs, permettant une reconfiguration dynamique à mesure que l'on ajoute des dispositifs au réseau, ou qu'on les retire. Chaque dispositif conserve une liste d'acheminement indiquant la voie préférée de communication vers chacun des autres dispositifs. Chaque dispositif émet à des intervalles réguliers des messages balise afin d'informer les autres dispositifs de sa présence sur le réseau. Les nouveaux messages balise indiquent le raccordement d'un nouveau dispositif, et la non réception des messages balise indique la déconnexion d'un dispositif. De préférence, les listes d'acheminement comprennent un paramètre de longueur de voie et la voie la plus courte est enregistrée pour chaque dispositif. On a également prévu un procédé d'émission de données numériques ou vocales sur une liaison radioélectrique.
PCT/NZ1993/000004 1992-02-07 1993-02-05 Procede et appareil de communication WO1993016539A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
NZ24155192 1992-02-07
NZ241551 1992-02-07

Publications (1)

Publication Number Publication Date
WO1993016539A1 true WO1993016539A1 (fr) 1993-08-19

Family

ID=19923875

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/NZ1993/000004 WO1993016539A1 (fr) 1992-02-07 1993-02-05 Procede et appareil de communication

Country Status (2)

Country Link
AU (1) AU3464693A (fr)
WO (1) WO1993016539A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2295751A (en) * 1994-11-30 1996-06-05 Ibm Data communication system using directory service providing routing information
WO1999025101A3 (fr) * 1997-11-07 1999-07-29 Ericsson Telefon Ab L M Reseau de transmission de donnees et procedes y relatifs
US6523070B1 (en) * 1996-07-23 2003-02-18 3Com Corporation Communication device with circuitry to promote cascade series connection including identification of device position in the series and sensing the end device in the series
EP0812086A3 (fr) * 1996-06-07 2005-07-20 Nippon Telegraph And Telephone Corporation Système et procédé de contrôle d'un VLAN
KR100553867B1 (ko) * 1998-07-04 2006-05-25 삼성전자주식회사 Ieee 1394 버스로 연결된 네트워크에서의 버스 리셋 처리방법
WO2011050753A1 (fr) * 2009-11-02 2011-05-05 华为技术有限公司 Procédé et appareil de traitement de coordination d'opération à organisation automatique, et système de communication

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0179629A2 (fr) * 1984-10-25 1986-04-30 International Standard Electric Corporation Réseau de commutation de paquets
AU7401991A (en) * 1990-03-29 1991-10-03 Nec Corporation Communications system reconfigurable with reduced network configuration data

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0179629A2 (fr) * 1984-10-25 1986-04-30 International Standard Electric Corporation Réseau de commutation de paquets
AU7401991A (en) * 1990-03-29 1991-10-03 Nec Corporation Communications system reconfigurable with reduced network configuration data

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2295751A (en) * 1994-11-30 1996-06-05 Ibm Data communication system using directory service providing routing information
WO1996017457A1 (fr) * 1994-11-30 1996-06-06 International Business Machines Corporation Acheminement dans un reseau de transmission de donnees
EP0812086A3 (fr) * 1996-06-07 2005-07-20 Nippon Telegraph And Telephone Corporation Système et procédé de contrôle d'un VLAN
US6523070B1 (en) * 1996-07-23 2003-02-18 3Com Corporation Communication device with circuitry to promote cascade series connection including identification of device position in the series and sensing the end device in the series
WO1999025101A3 (fr) * 1997-11-07 1999-07-29 Ericsson Telefon Ab L M Reseau de transmission de donnees et procedes y relatifs
US6401129B1 (en) 1997-11-07 2002-06-04 Telefonaktiebolaget Lm Ericsson (Publ) Routing functionality application in a data communications network with a number of hierarchical nodes
KR100553867B1 (ko) * 1998-07-04 2006-05-25 삼성전자주식회사 Ieee 1394 버스로 연결된 네트워크에서의 버스 리셋 처리방법
WO2011050753A1 (fr) * 2009-11-02 2011-05-05 华为技术有限公司 Procédé et appareil de traitement de coordination d'opération à organisation automatique, et système de communication

Also Published As

Publication number Publication date
AU3464693A (en) 1993-09-03

Similar Documents

Publication Publication Date Title
JP4446664B2 (ja) 無線マスタ・スレーブ分散通信ネットワーク
US5455569A (en) Link layered communications network and method
EP0940022B1 (fr) Acheminement de messages par reseau radio
EP1885039B1 (fr) Système d'éclairage d'urgence
US6028857A (en) Self-organizing network
EP0605957A1 (fr) Système de réseau local radiophonique avec transfert des stations mobiles
JP2002033752A (ja) 分散コンピューティング環境におけるトポロジ伝達方法およびシステム
US7110367B2 (en) Dynamic routing control system and method for radio access network
US5910179A (en) Method and system for transmitting data within a tree structure and receiving a confirmation or status therefor
US5995494A (en) Data communication using network DCE and modified channel associated signaling
US6266513B1 (en) Apparatus and method for missing message reconciliation
WO1993016539A1 (fr) Procede et appareil de communication
US5736933A (en) Method and apparatus for providing redundancy in a communication network
CA2290967A1 (fr) Procede et systeme pour commander l'utilisation de la capacite de transmission de satellites dans des reseaux terrestres
JP6779409B2 (ja) ネットワークアドレス指定方法、管制局及び地球局
JP4098504B2 (ja) ネットワーク装置
KR100321664B1 (ko) 냉동컨테이너용통신유닛을자동선택하는시스템
CA2416443C (fr) Procede de transmission de donnees en zone d'acces
AU730943B2 (en) Method for data transmission to slave exchanges
JPH0831863B2 (ja) 伝送制御方法
JP3441957B2 (ja) 位置登録制御方式
JPH10303979A (ja) 分散化無線通信システムおよびそのシステムで使用する無線局
EP0674449A2 (fr) Méthode pour le transfert de données entre stations de base et contrôleur régional dans un réseau d'appel de personnes
JP2001211470A (ja) 改良されたプロトコルを使用する移動無線遠隔通信システム
JP3102370B2 (ja) 無線局管理システム

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AT AU BB BG BR CA CH CZ DE DK ES FI GB HU JP KP KR LK LU MG MN MW NL NO NZ PL PT RO RU SD SE SK UA US

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): AT BE CH DE DK ES FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
EX32 Extension under rule 32 effected after completion of technical preparation for international publication

Ref country code: KZ

LE32 Later election for international application filed prior to expiration of 19th month from priority date or according to rule 32.2 (b)

Ref country code: KZ

LE32 Later election for international application filed prior to expiration of 19th month from priority date or according to rule 32.2 (b)

Ref country code: KZ

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: CA

DPE2 Request for preliminary examination filed before expiration of 19th month from priority date (pct application filed from 20040101)