EP2837163A1 - Procédé d'initialisation d'adresses dans un système de communication - Google Patents

Procédé d'initialisation d'adresses dans un système de communication

Info

Publication number
EP2837163A1
EP2837163A1 EP13704603.3A EP13704603A EP2837163A1 EP 2837163 A1 EP2837163 A1 EP 2837163A1 EP 13704603 A EP13704603 A EP 13704603A EP 2837163 A1 EP2837163 A1 EP 2837163A1
Authority
EP
European Patent Office
Prior art keywords
network element
address
message
identifier
time
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
EP13704603.3A
Other languages
German (de)
English (en)
Inventor
Volker Blaschke
Timo Lothspeich
Andreas Mueller
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Robert Bosch GmbH
Original Assignee
Robert Bosch GmbH
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 Robert Bosch GmbH filed Critical Robert Bosch GmbH
Publication of EP2837163A1 publication Critical patent/EP2837163A1/fr
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/09—Mapping addresses
    • H04L61/10—Mapping addresses of different types
    • H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5038—Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/622—Layer-2 addresses, e.g. medium access control [MAC] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/672—Short addresses

Definitions

  • the present invention relates to a method for address initialization in a communication system. Furthermore, the invention relates to a communication system, a computer program for carrying out steps of the method and one or more machine-readable storage media, on which instructions for carrying out method steps are stored.
  • the functions of the communication are divided into seven superimposed abstraction layers.
  • the so-called link layer also referred to as "layer 2" regulates the access of the nodes to the communication medium
  • a particular node of such a communication system can usually be explicitly addressed by another node, which is necessary, inter alia, if the access is In this case, each device connected to the communication medium typically has a so-called layer 2 address.
  • the layer 2 addresses used are unique at least on the link on which the respective addresses are used.
  • EUI-48 or EUI-64 addresses managed by the Institute of Electrical and Electronics Engineers (IEEE), which are intended to be globally unambiguous. for example during a production onsuzes) in the device, without thereby generating a potential address conflict.
  • IEEE Institute of Electrical and Electronics Engineers
  • each EUI 48 address is given by 48 bits.
  • Addresses are 64 bits. Long addresses tend to increase the transmission time, resulting in increased energy consumption.
  • Bluetooth technology which is based on the IEEE802.15.1 standard:
  • the "Inquiry procedure" common in Bluetooth offers the possibility of establishing contact between unknown Bluetooth devices by a first device in a network (a "master") so-called “Inquiry” messages sent out.
  • a second device in a network (a "master) so-called “Inquiry” messages sent out.
  • This "Inquiry Response” message contains an identifier that uniquely identifies the second device The identifier can then be used by the first device in a wide The second device can be assigned a unique address on the link, which is therefore suitable for addressing on layer 2.
  • Bluetooth devices generally have their own self-sufficient energy supply.
  • the inquiry method can only be used if the accumulated power consumption of all network subscribers is less than the available peak power of the source, taking into account any power losses (for example from a bus ).
  • this requirement is not generally met, but can be violated in particular when collisions occur. The probability of violation of the requirement tends to increase with increasing number of participants.
  • the object of the present invention is to provide ways in which an address can be assigned to network elements (nodes) while minimizing simultaneous access to a communication medium. Disclosure of the invention
  • the invention proposes a method, a computer program, one or more machine-readable storage media and a communication system having the features of the independent claims 1, 13, 14, 15 respectively.
  • the inventive method is suitable for an address initialization in a communication system having a control entity and at least one network element.
  • the network element has an identifier that can also be referred to as labeling. For example, it may be a globally unique identifier or may be derived from it, or it may be in the form of a specific latency allocated to the network element; Further possible identifiers are described below.
  • the network element sends a message to the control entity.
  • an address is also assigned to the network element. Possible forms of the dependence of the reporting time on the identifier are explained below.
  • the reporting time may be fixed at the beginning of the address initialization or may arise during its course, for example depending on queries sent by the control entity; this is explained in more detail below.
  • the identifier thus determines when the message is sent from the network element to the control entity. This will prevent the network element from sending the message if the control entity sends a message at the same time. If further network elements are contained in the communication system, it can also be avoided (if the functional dependency is appropriately determined) that the network element and one or more of the further network elements transmit messages simultaneously. Thus, the risk of collisions in the address assignment can be reduced.
  • the method according to the invention may be stored in the form of instructions on one or more machine-readable storage mediums, for example integrated in or used by an embedded system. Alternatively or additionally, it may be implemented in a communication system with a control entity and at least one network element.
  • the assignment of the address to the network element preferably comprises that in the communication system the address is associated with the network element. This implies that the network element takes over the address and that a link of the network element with the address is stored in the communication system (eg in the control entity).
  • the control entity preferably has its own address itself. This may be known in advance to the network element (s) in the communication system, for example, or communicated by the control entity, for example together with one or more queries of identifiers or with a start of the address initialization.
  • identifier is preferably of the same type as that of said network element. Examples of possible types are shown below and below:
  • the identifier of the network element is a globally unique identification number, such as an EUI-48 or EUI-64
  • the identifier is a random number representing the
  • Network element can preferably generate self-sufficient. This embodiment is therefore independent of the presence of globally unique addresses. The probability that several network elements have the same identifier, can be kept small by the random number space is chosen appropriately large depending on the number of network elements.
  • the control entity can query various possible identifiers by sending query messages to the network element (s) in the communication system.
  • the control entity advantageously has a plurality of possible identifiers. This plurality may be known to the controller or communicated by a higher-level entity, for example, a central entity that manages an overall network in which the communications system is embedded as a subnetwork.
  • the amount is suitably selected, so that the number of identifiers to be queried can be reduced.
  • a 48-bit wide EUI-48 address can be split into a 24-bit manufacturer ID and a 24-bit wide range, which may be distributed individually by the manufacturer. If one can now assume that there are only network elements with a specific manufacturer ID in a network, then it is not necessary to query 2 48 identifiers but only 2 24 identifiers.
  • the control entity can query with such query messages each one of the possible identifiers. If the identifier of the at least one network element then coincides with the last one queried, the network element sends the message to the control entity at the time of the message.
  • the reporting time is preferably in a time interval of predetermined length from the sending of the last (that is, the matching) query message by the control entity.
  • the time interval can be predetermined such that it allows the network element to receive the corresponding query message, to recognize that the queried possible identifier corresponds to its own identifier and to generate an appropriate message and to send it to the control entity.
  • the time interval is preferably smaller than a polling clock, namely so small that the message is received by the control entity before it sends a new polling message (with a new possible identifier).
  • the network element may also be set up to notify the control entity in a message if the requested identifier does not correspond to its own.
  • the control entity may be arranged to distinguish such a message from a message (which is sent when the identifier is appropriate) and, moreover, to query the next identifier only when a previous response has been received in the form of such a message or in the form of a message.
  • the network element waits (after starting the method) to send the message until it has received a query message with the appropriate identifier.
  • the reporting time depends on the identifier of the network element.
  • control entity is arranged to determine the identity of the network element, for example, by receiving the message in a time interval of predetermined length after sending the corresponding (matching) query message.
  • the message itself may include an indication of the identifier of the network element.
  • the assignment of the address can take place immediately, that is to say before the sending of a further query message by the control entity.
  • all identifiers of the plurality of identifiers that are known or communicated to the control entity can first be queried before the address assignment takes place.
  • the control entity performs alternative block dispatching by address mapping, when the control entity has polled a predetermined number of identifiers, or after finding a predetermined number of network elements that have requested identifiers, and after the Address assignment corresponding block by block other identifiers queried and assigned addresses.
  • the controller entity may be aware of the number of network elements in the communication system or may be notified by a higher-level entity (such as a central entity such as the one mentioned above). In this case, it is advantageous if the control entity stops sending polling messages as soon as it receives a message from each of the network elements Message has been received, with which the corresponding identifier is confirmed directly or indirectly.
  • a higher-level entity such as a central entity such as the one mentioned above.
  • the identification of the at least one network element is given in the form of a specific waiting time which must elapse after a start time before the network element has to send the message to the control entity.
  • the reporting time thus depends on the specific waiting time and thus on the identifier of the network element.
  • the start time can be set, for example, by the control instance or by a higher-level unit.
  • the waiting time can be determined, for example, from a globally unique identification identifier of the network element or from a random number generated autonomously by the network element. In the latter case, analogous to the above-mentioned by choosing a suitable large random number space, the
  • the identifier of the at least one network element may result from its position having it in the network. For example, you can
  • Voltage, current or signal losses resulting from the particular distance or cable length characterize the network element due to its position and interpreted as an identifier or transformed into such.
  • the network can operate with wired and / or wireless technology and / or include an optical system.
  • the location with respect to that trunk bus or fiber may be fixed.
  • the location may define a distance to a base station.
  • a received signal strength of a pilot signal can be typical for this distance and thus for the network element.
  • the at least one network element in the ready state can have a certain size (for example voltage, current, signal strength of a pi lotsignals).
  • the position-dependent measurement result can be stored and used as an identifier.
  • a previous quantization may be useful (in addition to a general A / D conversion) in order to reduce the number of possible values appropriately.
  • This identifier can, as described above, again be polled or interpreted as a random number.
  • the reporting time depends on the identifier by being equal to or resulting from a time when a particular minimum voltage or pilot signal strength is applied to the network element, or by decreasing to an interval of a predetermined length falls at that time.
  • the at least one network element in the ready state can measure a certain size (for example voltage, current, signal strength pilot signal).
  • the size can be changed successively (eg by the central control element).
  • the reporting time can be defined as the point in time at which the measured variable exceeds or falls below a predefined threshold value.
  • the threshold value can be derived in a suitable manner, for example, from a random number or a globally unique identification number.
  • the power supply of the communication system can be put under the control of the controller during the address initialization. This can then gradually provide more energy during initialization. If the at least one network element as well as any further network elements present require a certain minimum voltage on the input side (for example due to a particular voltage regulator), a network element can be made operational by a stepwise increase of the input voltage
  • the message of the network element sent at the time of the message can indicate the identity of the network element. technikelements included. In this way, the control entity can be informed that the network element is present in the communication system and that the address is being assigned to it. Alternatively, the control entity may be arranged to close the identifier from the time or from the time elapsed from a start time at which it receives the message.
  • the message may contain an acknowledgment that the network element is taking over the address.
  • such confirmation may be sent separately in another message.
  • the message may include an indication of which address the network element has accepted. As a result, higher reliability can be achieved, for example, by simple plausibility checks.
  • the first address may be assigned to the network element in response to the message by a message from the controller entity.
  • the network element can then confirm the transfer of the address in another message.
  • control entity may notify the address to the network element prior to the reporting time. If the communication system comprises one or more further network elements, the control entity can announce the new network element (s) a new address upon receipt of the message. A network element whose reporting time has come can then be assigned this new address.
  • the addresses to be allocated are announced in a specific order already at the beginning of the address initialization in the communication system. This is explained in more detail below.
  • the communication system comprises a plurality of network elements.
  • the above-mentioned (at least one) network element is then a first network element with a first identifier that sends a first message to the controller instance at a first reporting time.
  • the first network element is assigned an address, which is referred to here as the first address.
  • a second network element also has an identifier which, like the first identifier, can have one of the characteristics described above and is referred to here as a second identifier.
  • the second network element sends according to this embodiment, at a reporting time, which is referred to here as the second reporting time, a message, which is here called a second message, to the control entity.
  • the second network element is assigned an address, which is referred to here as a second address.
  • the second reporting time depends on the second identifier as described above for the first network element. It can be before or after the first reporting time. Which address is assigned to the first network element and / or which address is assigned to the second network element preferably depends in this embodiment on the time sequence of the two reporting times.
  • a list of possible addresses may be stored which are processed in association in a particular order. If the first reporting time is then before the second, the first network element is assigned an address which comes before the second address in the order; The same applies to the opposite case.
  • the order can be known in advance to the first and the second network element or can be announced, for example, at the beginning of the address initialization. In both cases, if the first reporting time is before the second, the first network element can take over the first address that has not yet been assigned to the order, without the allocation first having to be communicated to it. Preferably, the first network element then sends the first message (or another message, simultaneously or shortly thereafter, that is, before a further step in the Adressinitialmaschine is made is sent) also to the second network element, advantageously even to all network elements in the communication system, or to all network elements to which no address has been assigned. In this way, the other network elements know that the named address has already been allocated and that the corresponding next address is assigned to them if their reporting time is the next one.
  • the assignment of the first address to the first network element can take place immediately after the first message has been sent or can be completed. If the first reporting time before the second, so the assignment can be made in particular before the second reporting time, possibly even before sending another query message by the controller.
  • the address initialization can be carried out in blocks analogously to the case described above.
  • the first address can be assigned to the first network element only after the second reporting time.
  • All of the above embodiments are suitable for use in communication systems having a plurality of network elements, each of which may have a common power supply. They are particularly suitable for address initialization on the data link layer, ie for the case that the address is a layer 2 address (or that the addresses are layer 2 addresses).
  • Figure 1 shows an example of a communication system to which the present invention can be applied.
  • FIG. 2 shows a possible address initialization with identification request by the control entity.
  • FIG. 3 shows an address initialization with block processing and identification query.
  • FIG. 4 shows an address initialization in which the address is sent with the identifier query.
  • Figure 5 shows an address initialization with address notification in advance.
  • FIG. 6 shows a possible address initialization in which the identifier is a specific waiting time.
  • FIG. 7 shows by way of example a typical arrangement of components in a communication system with a linear bus structure.
  • FIG. 8 shows a possible address initialization which is based on position-specific features of the network elements
  • FIG. 9 shows an overall network with two separate communication systems in which the invention can be applied.
  • Embodiment (s) of the invention The communication system 1 shown in FIG. 1 has a control entity 10, a plurality of network elements 101, 102, 103, 104, 105, 110 and a common communication medium 11, via which the network elements and the control entity can communicate with one another.
  • the network elements 101, 102 and 103 have an identifier 1012, 1022 and 1032, respectively, and are assigned addresses 101 1, 1021 and 1031, respectively, in the communication system.
  • the control entity 10 has a set of 100 possible identifiers in the communication system, which it can query if necessary.
  • the control entity shown has its own address 1001 and a set 107 of possible addresses, which it can optionally assign.
  • FIGS. 2 to 6 and 8 show how the control entity 10 and the network elements 101 and 102 exchange messages in the course of time t.
  • network elements may be present; In an alternative embodiment, fewer network elements may be present than shown in the figures.
  • the respective matching features are provided with the same reference numerals and are explained in the description of Figure 2.
  • the respective identifier of the network elements can be, for example, a globally unique EUL address or a random number generated autonomously by each network element.
  • the random number range (from which a random number is drawn) may optionally be suitably limited, for example on the basis of collisions that have occurred from a previous address allocation process and / or on the basis of a (maximum) number of network elements present in the communication system, if this is known.
  • the control entity begins to send query messages 201 and 202 to the network elements, in which it successively polls different identifiers to find out which identifiers are present in the communication system.
  • the control entity has a certain area (ie a certain amount) of identifiers available.
  • the timeout is a fixed, uniform clock.
  • this clock is selected to be so large that it can be ruled out that the control entity is still sending a new query message during an address assignment.
  • control entity 10 in the message 211 may assign a unique layer 2 address to the network element. The acceptance of this address is confirmed by the network element in the message 212, wherein the confirmation message can also be dispensed with.
  • the message 210 is sent by the network element 102 at the time of the message T 10 2. This is done when in a query message (here 202) for the appropriate identifier (here 102) has been asked. Thus, the reporting time T 10 2 depends on the identifier of the network element 102.
  • control entity shown After the expiration of the next time interval A t, the control entity shown sends in the interval cycle further polling messages 203, 204 and 205 in which it in each case asks for a different identifier; As mentioned above, the control entity may alternatively be set up after the address assignment to the
  • Network element 102 to start with the query of other identifiers, without waiting for the expiration of a fixed time interval.
  • the identifier of the network element 101 is polled at the time t 2 . This therefore responds at the time T 10 i, which is thus the reporting time of the network element 101, with the message 213.
  • the network element 101 confirms the identifier.
  • the controller instance assigns an address to the network element.
  • the network element acknowledges acceptance of the address.
  • This message 215 is optional. In an alternative embodiment, the controller instance does not have to wait for a timeout to proceed with the method.
  • the process of address initialization for element 102 is complete and the controller may poll the next identifier. If an acknowledgment (message 212) is dispensed with, the control unit can continue to send message 203 directly after the message 21 1 has been sent, without waiting for a timeout
  • FIG. 3 differs from that shown in FIG. 2 in that the sending of the query messages and the assignment of the addresses are processed one after the other. Thus, a block check is performed. In a first block, all identifiers present in the network are collected by the query messages 201, 202, 203, 204 and 205 as well as the messages 210 and 213. In a second block, the assignment of the addresses and the confirmation of their transfer takes place with the messages 211, 212, 214 and 215.
  • the confirmation messages 212 and 215 may possibly be waived again.
  • a corresponding block processing takes place with inserted address assignment. Not all identifiers available in the network, but only a predetermined number of such identifiers are queried in the first block. In the second block, addresses are assigned to the identifiers collected in this way. In further blocks then other identifiers can be processed analogously.
  • FIG. 4 shows an embodiment in which the query messages 401, 402, 403, 404, 405 and 406 not only each pass through whether a particular identifier is present in the network, but by default also contain the corresponding address to be assigned next.
  • the network elements 101 and 102 with the corresponding identifier must only confirm in the messages 410 and 411 that the corresponding address has been accepted.
  • FIG. 5 shows an embodiment in which the address to be assigned next is respectively announced in a message 501 or 502 in the communication system.
  • the query messages 201 to 205 then again only need to ask for the respective identifier. If the identifier is suitable, the network elements 102 and 101 send the messages 212 and 215 respectively to the message times T 10 2 and T 10 i in which they confirm the acceptance of the respective address.
  • the addresses are assigned in a specific order, which is known in advance to the network elements.
  • the messages 501 and 502 can be dispensed with.
  • the messages 212 and 215 may contain an indication of the respective identifier.
  • the messages 210 and 213 described above could be the messages; they contain no confirmation of the address transfer, but an indication of the identifier.
  • control entity may know the exact number of network elements in the communication system or a maximum number of network elements in the communication system. In these cases, the controller instance may abort the interrogation of the identifiers after the appropriate number of network elements are found. So you do not need to work through the entire space of the identifiers. For example, in the examples above, after the network element 101, the control entity could abort polling of other identifiers if it knows that the number of network elements is limited to two.
  • the order in which the individual identifiers are queried can be selected differently for different embodiments. Also, the order in which the addresses are assigned can be suitably selected.
  • the amount of addresses to be assigned can be set, for example, to 0. beginning and end in order to keep the necessary address space as small as possible.
  • the addresses may be assigned according to a mechanism which ensures that between every two addresses the minimum
  • messages may be suitably combined as appropriate, so that while the same information is exchanged, the number of messages required thereto varies.
  • FIG. 6 shows a message exchange according to a further embodiment of the present invention.
  • the identifier of the network elements corresponds in each case to a specific waiting time.
  • the control entity starts the address initialization process with the message 600 addressed to all network elements in the communication system. From this
  • Start signal waits each network element from its identifier corresponding waiting time.
  • the controller instance keeps monitoring the communication channel and waits for incoming messages. It can be advantageous if not only the control entity observes the channel but also the network elements. For example, a network element may then extend the latency by the time that the channel (for previous address assignments of other network elements) is used. In this way, it is possible to prevent a first network element from transmitting and, at a second network element, the waiting time to expire and also to send it. Otherwise, the time interval in which the waiting time is changed by one unit is preferably chosen to be at least so large that at least the messages 601, 602 and 603 can be exchanged.
  • the network element 102 has the waiting time ⁇ After its expiry, the network element 102 transmits the message 601 to the control entity at the time of reporting T 10 2, thereby reporting the expiration of its own waiting time. The controller then sends in the message 602 the address assigned to the network element 102, whose acceptance confirms the network element in the message 603. Analogously, after expiry of its waiting time Et 10 i, the network element 101 sends a message 604, to which an address is assigned in the message 605, whose acceptance confirms it in the message 606. The confirmation messages 603 and 606 may be omitted.
  • a maximum waiting time t M is provided, after which the process ends. If the control entity knows the number of network elements present in the communication system, the process can alternatively end when all network elements have been found. In this way, the address initialization process can be shortened.
  • the respective waiting time can for example be calculated on the basis of EUL addresses or on the basis of a random number. It can be provided that not the entire range of identifiers, but only a part of the same is interpreted as waiting time.
  • a 48-bit wide EUI-48 address can be split into a 24-bit manufacturer ID and a 24-bit wide range, which may be distributed individually by the manufacturer. If one can safely assume that there are only network elements with a certain manufacturer ID in a network, then it is not necessary to distribute 2 48 identifiers on the time axis but only 2 24 identifiers.
  • the embodiments in which the identifier corresponds to a specific waiting time can be combined with an address announcement in advance or else an announcement of the order of the addresses to be assigned.
  • control entity from the past time between the start of the award process and the receipt of a message on the identifier of a network element can close (for example, by the introduction of time slots).
  • the control entity has the information of which network element (with which identifier) it has received a message without an identifier from the network element must be sent explicitly.
  • FIG. 7 shows a possible arrangement of the network elements in the communication system 1.
  • the common communication medium 11 is a linear bus whose ends are denoted by 120 and 121.
  • the identifier of the network elements is based on their respective position 1043, 1013, 1 103, 1023, and 1053, respectively.
  • the power supply of the network can be placed under the control of the control entity during the assignment of the addresses. This allows the controller instance to initialize the
  • Network gradually provides more and more power to the network, with the result that the network elements will not start up at the same time.
  • a voltage source 123 (as shown in Figure 7), for example: From a start signal 800 at time t 0 , the control instance starts to increase the voltage (slowly), for example beginning with OV. Since the individual network elements are distributed on the bus and therefore there is a different distance (cable length) between each network element and the power supply 123, different voltage losses occur on the cable, whereby a different voltage is applied to each network element on the input side. Furthermore, it can be assumed that each network element has a voltage regulator, which is only ready for operation when the input side of the network element (and thus the voltage regulator) is applied a certain minimum voltage. Since the losses on the cable cause the input voltage to be different for each network element, the slow increase in the input voltage ensures that the network elements do not simultaneously but successively (in terms of time) have the required input voltage and are therefore ready for operation one after the other are.
  • the network element 101 has the required input voltage at the instant ⁇ (which thus becomes the reporting time of the network element).
  • the network element 101 therefore sends a message 801 to the control entity 10. It then assigns to the network element 101 in a message 802 an address whose adoption confirms the network element 101 in the message 803.
  • the network element 102 has the input voltage required there. Accordingly, this network element also sends a message 804 to the control entity, is assigned an address in the message 805 and confirms its acceptance in the message 806.
  • the messages 803 and 806 with confirmation of the address assignment can be dispensed ter circumstances.
  • the voltage controlled by the control entity 10 In order to prevent multiple network elements from becoming operational at the same time, the voltage controlled by the control entity 10 must be increased in correspondingly small steps and / or, if appropriate, a minimum distance (minimum cable length) between two network elements, so that the voltage loss caused by the line has a corresponding effect. As soon as a network element is ready for operation due to the voltage present on the input side, it can send a message to the control instance and thus be assigned an address by it.
  • the control entity can alternatively or additionally be set up, with an increase of the voltage the switching on of a network element on the basis of an increased power consumption or an increased voltage drop or the like. without, or before, sending a message from the network element to the control entity.
  • This Adressinitialmaschinesvon can be modified analogously to the methods described above by the identifier of the transmitting network element is sent in the messages 801 and 804 and a block handling takes place in which several or all addresses are assigned to a collection of several or all existing identifiers.
  • the input voltage (or the input current) can also be measured (with quantization) at each network element, for example.
  • the measured value can then also be interpreted as identifier or random number, so that the approaches described above can be used.
  • the received signal strength of a pilot signal can be measured.
  • This measured value can also be interpreted as identifier or random number, so that the above approaches can be applied analogously, if appropriate again with appropriate quantization.
  • a central entity for example the control entity
  • Identifier eg serial number or EUI-48 / EUI-64 address
  • the corresponding identifiers of the network elements may possibly be collected during the installation process or possibly even through it.
  • the control entity is informed which identifiers are located in the network. Once the controller instance has this information, it can directly assign an appropriate address to the network elements.
  • an overall network 90 is divided into a plurality of subnets 1000, 2000, each subnet being its own
  • Control instance 10 or 20 has.
  • the individual control instances are connected to each other via a suitable communication interface (eg a backbone) 92.
  • the controller 10 may include a block 107 with possible addresses as shown in FIG.
  • the control entity 20 may contain an analog block with possible addresses that it can allocate.
  • the central element 91 may contain a block with possible addresses and specify to the control authorities 10 and 20 which addresses from this block they can allocate. In either case, the address ranges for networks 1000 and 2000 may include one or more common addresses.
  • Identifier is located in which subnet.
  • the central element tells each control instance exactly the identifiers that also fall into its subnet.
  • Each controller instance will be notified directly of all identifiers from the entire network.
  • An optionally available central element is notified of all identifiers from the entire network, and the central element forwards to each control entity all identifiers that exist in the overall network.
  • the role of the central element can also be assumed by a control entity or the central element can also have additional control entity functionality.
  • variants a) and b) can assign suitable addresses directly to the network elements
  • variants c) and d) have the peculiarity that in a subnetwork not all identifiers of the overall network are necessarily present, so that the control entity again " must "try what identifiers are actually present in their network.” This can in principle be accomplished by the concepts set out in relation to Figures 2-8.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention concerne un procédé d'initialisation d'adresses dans un système de communication (1) qui comporte une instance de commande (10) et au moins un élément de réseau (101, 102, 103, 110), ce dernier disposant d'un identifiant (1012, 1022, Δt101, Δt102). Le procédé consiste à envoyer un message (210, 213, 410, 601, 604, 801, 804) de l'élément de réseau à l'instance de commande, l'envoi ayant lieu à un instant d'annonce (Τ101, Τ102) qui dépend de l'identifiant de l'élément de réseau. Le procédé consiste en outre à attribuer une adresse (1011, 1021, 1031) à l'élément de réseau. La présente invention se rapporte en outre à un système de communication qui est mis au point pour exécuter le procédé, à un programme d'ordinateur ayant des moyens de codage de programme pour exécuter des étapes de procédé ainsi qu'à un moyen d'enregistrement lisible par machine ayant un programme d'ordinateur de ce genre.
EP13704603.3A 2012-04-12 2013-02-14 Procédé d'initialisation d'adresses dans un système de communication Ceased EP2837163A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102012205991A DE102012205991A1 (de) 2012-04-12 2012-04-12 Verfahren zur Adressinitialisierung in Kommunikationssystemen
PCT/EP2013/052989 WO2013152884A1 (fr) 2012-04-12 2013-02-14 Procédé d'initialisation d'adresses dans un système de communication

Publications (1)

Publication Number Publication Date
EP2837163A1 true EP2837163A1 (fr) 2015-02-18

Family

ID=47720513

Family Applications (1)

Application Number Title Priority Date Filing Date
EP13704603.3A Ceased EP2837163A1 (fr) 2012-04-12 2013-02-14 Procédé d'initialisation d'adresses dans un système de communication

Country Status (3)

Country Link
EP (1) EP2837163A1 (fr)
DE (1) DE102012205991A1 (fr)
WO (1) WO2013152884A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0980165A2 (fr) * 1998-08-13 2000-02-16 Motorola, Inc. Procédé d'initialisation d'un système de commande distribué

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020043938A1 (en) * 2000-08-07 2002-04-18 Lys Ihor A. Automatic configuration systems and methods for lighting and other applications
US20040217718A1 (en) * 2003-05-02 2004-11-04 Russikesh Kumar Digital addressable electronic ballast and control unit
DE102004055933A1 (de) * 2004-11-19 2006-05-24 Patent-Treuhand-Gesellschaft für elektrische Glühlampen mbH Verfahren zur Vergabe von Kurzadressen in Beleuchtungsanlagen
DE102005057068A1 (de) * 2005-11-30 2007-06-06 Zumtobel Lighting Gmbh Steuerungssystem für mehrere verteilt angeordnete Verbraucher, insbesondere für Lampenbetriebsgeräte, sowie Verfahren zur Inbetriebnahme

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0980165A2 (fr) * 1998-08-13 2000-02-16 Motorola, Inc. Procédé d'initialisation d'un système de commande distribué

Also Published As

Publication number Publication date
WO2013152884A1 (fr) 2013-10-17
DE102012205991A1 (de) 2013-10-17

Similar Documents

Publication Publication Date Title
EP3059930B1 (fr) Procédé de configuration d'un appareil de communication d'un système d'automatisation industriel et appareil de communication
EP3669550B1 (fr) Procédé pour faire fonctionner un ensemble de détection dans un véhicule à moteur sur la base d'un protocole dsi
EP2266297B1 (fr) Attribution automatique d'adresses de bus par contrôle de collision
EP2733910B1 (fr) Système bus, procédé de fonctionnement d'un système bus et système fluidique doté d'un système bus
DE19721740B4 (de) Steuerungsverfahren für den Medienzugriff bei einem seriellen Bus
EP1979790B1 (fr) Procédé et dispositif d'attribution d'adresses dans un système comportant plusieurs unités de générateur disposées de façon parallèle
EP1979198A1 (fr) Procédé et système pour l'affectation dynamique de ressources
EP3669527B1 (fr) Procédé de fonctionnement d'un agencement de capteurs dans un véhicule automobile sur la base d'un protocole dsi
EP2503760B1 (fr) Procédé de réglage d'un réseau de communication à partir d'appareils d'une installation d'automatisation
EP2587772A1 (fr) Procédé de fabrication d'une liaison communicative entre un appareil de programmation et un appareil de terrain technique d'automatisation
DE102017209309A1 (de) Verfahren zum Übertragen von zeitkritischen und nicht zeitkritischen Daten in einem Kommunikationszyklus
WO2006128787A1 (fr) Procede de fonctionnement d'un systeme de bus, systeme de bus et abonne du bus
WO2013152884A1 (fr) Procédé d'initialisation d'adresses dans un système de communication
DE102009054904A1 (de) Verfahren zum Zuweisen einer Polling-Adresse an ein Feldgerät
EP1642207B1 (fr) Attribution d'adresses de station a des abonnes de communication dans un systeme de bus
WO2013152882A1 (fr) Initialisation d'adresses dans des réseaux
AT411806B (de) Bussystem für eine mehrzahl von teilnehmern
EP2156621B1 (fr) Procédé pour faire fonctionner un système de communication, noeud de coordination d'un système de communication et système de communication
EP2255498A1 (fr) Autorisation de fonctionnement d'unités d'automatisation reliées à une installation et installation correspondante
DE102017209428A1 (de) Verfahren und Vorrichtung zur Identifikation in einem Rechnernetzwerk
EP1511272B1 (fr) Procedé d' attribution de serveur pour le clients repartis dans plusieurs resaux et client pour cette precedé
DE102004007151B4 (de) Verfahren und Vorrichtung zur Überwachung und Beeinflussung von Versorgungsmodulen für Verbraucher
DE102004039447A1 (de) Verfahren zur automatischen Adressvergabe
DE102020134467A1 (de) Verfahren zur Bereitstellung eines Lastmanagementsystems
DE102020200819A1 (de) Erweiterung eines Busprotokolls mit Übergabe eines Nutzdatums im Header

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20141112

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20160225

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20180419