JPH07287572A - Network constructing method - Google Patents

Abstract

PURPOSE:To reconstruct a network by restoring a logical path connecting between electronic equipments on one network. CONSTITUTION:Reception-only ports, transmission-only ports, and transmission/ reception ports, which a keyboard 1, a sound source 1, a sound source 2, a sound source 3, a sequencer 2, and a mixer 3 are respectively equipped with, are connected by logical paths L1-L10. The logical paths are virtual transmission lines and constituted by giving a group address to sent data at a transmission port and broadcasting the data, and receiving the data at the reception port where the group address is set. Once a user set the logical paths constituting the network, information on the logical paths is received in reception ports, and when the network is powered on or reset, the original logical paths can automatically be reconstructed on the network.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention, in a network in which a plurality of electronic devices are connected to each other by a logical path constructed on the network, restores and reconstructs the logical path once set at the time of constructing the network. The present invention relates to such a network construction method, and is particularly suitable for application to a network in an electronic musical instrument.

[0002]

2. Description of the Related Art In recent AV systems and the like, a system has been constructed by connecting many electronic devices in association with each other. For example, in an AV system, a television, a video tape recorder,
An audio system, a karaoke device, etc. are each used one or more, and it connects between the related input terminals or output terminals, and the AV system is constructed.
In this case, the electronic devices are connected to each other individually by using coaxial cables, shielded cables, parallel lines, or the like. For electronic musical instruments, MID
Connections as shown in FIG. 17 are made by using an interface called I (Musical Instrument Digital Interface) for connecting musical instruments to each other. It should be noted that this MIDI standard is a unified standard established by domestic and overseas musical instrument manufacturers.

In FIG. 22, a MIDI output terminal OUT of the keyboard 101 is connected to a MIDI input terminal IN of a sequencer (SEQ) 102 via a line L101,
MIDI output terminal OUT of the sequencer (SEQ) 102
Is the MID of sound source 1 (104) via line L102
The MIDI output terminal THRU of the sound source 1 connected to the I input terminal IN is connected to the sound source 2 (1
05) MIDI input terminal IN, and the sound source 2 M
The IDI output terminal THRU is connected to the MIDI input terminal IN of the sound source 3 via the line L104. Furthermore, the output signals from the sound source 1, the sound source 2, and the sound source 3 are transmitted through the lines L105, L106, and L107, respectively, to the mixer 1
No. 03 input terminal (AUDIO IN), and a musical sound is output from the output terminal (AUDIO OUT) of the mixer 103. Here, MIDI output terminals TH of sound source 1 and sound source 2
RU is a terminal that outputs the input of the MIDI input terminal IN as it is.

[0004]

According to the method of connecting a plurality of electronic devices, the number of connecting lines between the electronic devices is large, and the occupied space is required considerably, and once the connection is removed. There was a problem that the wiring work to restore it was difficult. Also in the connection method of the electronic musical instrument, since the MIDI message is serial data and the MIDI line is wired so as to connect each device in series as described above, the MIDI line connecting each device is connected. Takes up a considerable amount of space, and if the MIDI line is accidentally disconnected in one place, the signal is not transmitted beyond that point and the sound is stopped. Furthermore, the connection is disconnected once. Then, there was a problem that the wiring work to restore it was difficult.

Therefore, it is an object of the present invention to provide a network construction method capable of reconstructing a path for connecting a plurality of electronic devices when the network is constructed so that the paths can be reconstructed on the network.

By the way, there is only one physical transmission line (bus) in the network, and a plurality of logical paths are formed on this transmission line to transmit data to or from a target electronic device. You are building a network so that you receive. Then, when a plurality of electronic devices are connected to the network, the electronic device on the receiving side usually has more. Therefore, when the transmitting side stores the information of the logical path, the information is transmitted as the number of electronic devices connected to the network increases. There is a problem that the logical path information stored on the side increases. Therefore, the present invention is a network construction method in which a path connecting a plurality of electronic devices is restored at the time of network construction so that the path can be reconstructed on the network. Another purpose is to provide a method.

[0007]

In order to achieve the above-mentioned object, a network construction method of the present invention has a plurality of electronic devices connected to the network, and a logic constructed between the electronic devices on the network. In a network connected by a physical path, the electronic device has at least one transmission port or a reception port, and the logical path is determined based on path information regarding the transmission port to which the reception port is connected when the network is constructed. The path information is restored and reconstructed on the network, and the path information is recorded on the receiving port side.

Further, the network construction method of the present invention is
In a network of electronic musical instruments, which has a plurality of electronic devices constituting an electronic musical instrument connected to a network, and the electronic devices are connected by a logical path constructed on the network, the electronic device has at least one transmission. It has a port or a reception port, and when the network is constructed, the logical path is restored and reconstructed on the network based on the path information regarding the transmission port to which the reception port is connected. .

Further, in the network construction method, the logical path information is recorded in a portable recording medium, and the recording medium is set in one of the electronic devices connected to the network, whereby The logical path is restored on the network to be reconstructed. Furthermore, the logical path information is such that path information regarding the transmission port to which the reception port is connected is recorded on the reception port side.

[0010]

According to the present invention, based on the stored logical connection information, when the network is constructed, the logical paths connecting the electronic devices on the network are restored and reconstructed. Even if you remove it once, you can easily restore it. Therefore, even when the electronic musical instrument formed by connecting a plurality of electronic devices is disconnected and moved to a stage or the like, each electronic device related to the electronic musical instrument is connected to one transmission line forming the network. The network of electronic musical instruments can be rebuilt simply by turning the power on or resetting.

That is, data from one transmitting side is set to 1
When 0 receiving sides receive, information of 10 receiving sides is not stored in the transmitting side, and information of 1 transmitting side is stored in each of the 10 receiving sides. This prevents logical path information from concentrating on the transmitting side. Even if products connected to the network are different, if electronic devices with the same function are connected, the newly connected electronic device with the same function will be forced into the network instead of the product that was connected previously. Can be connected to.

Further, when the receiving side stores the logical connection information, the data amount of the connection information can be distributed and stored as compared with the case where the transmitting side stores the connection information, and the network can be operated at high speed. Can be launched.
Furthermore, if the logical path information is stored in a portable storage medium, the same network environment can be created by simply setting the storage medium in the connection management means in a studio or the like equipped with electronic devices having the same function. It will be possible to reproduce. Further, in the network constructed by the network construction method of the present invention, since the network is not serially connected like MIDI, even if the connection of one electronic device is physically disconnected, the subsequent electronic devices are connected. Since data can be sent, there is an advantage that it is unlikely to be in a fatal state.

[0013]

FIG. 1 shows an example of a network of electronic musical instruments constructed by the network construction method of the present invention.
The network shown in this figure is intended to obtain the same connection as the electronic musical instrument system shown in FIG. In addition,
Lines L1 to L10 shown in this figure are logical paths,
It is a virtual connection means built on the network,
It is not a physical connection.

In the figure, reference numerals 1 to 6 denote nodes connected to the network, to which the following functions are assigned, and which are configured as follows. First, reference numeral 1 is a keyboard, and a key data output section (Key Da
It consists of a ta output) and a port (PORT) # 1 dedicated to transmission, and 2 is a sequencer (SEQ; Multi Track).
Sequencer) and Track 1 (Track 1; MIDI Me)
sg. Input) and its receiving-only port (PORT) # 1 or track 16 (Track 16; MIDI Mesg. Input) and its receiving-only port (PORT) # 16, track 1 (Track 1)
; MIDI Mesg.Output) and its dedicated port (PORT)
# 17, Track 2 (Track 2; MIDIMesg. Output) and its dedicated port (PORT) # 18, Track 3 (Trac
k 3; MIDI Mesg. Output) and its dedicated port (PO
RT) # 19, Path Information Mana
ger) and its transmitting / receiving port (PORT) # 50, a control data input / output unit (Control Data Input / Output) and its transmitting / receiving port (PORT) # 60. In this figure, some tracks and their corresponding ports are not shown for easy understanding. The same applies to each of the following devices.

Further, 3 is a mixer (8ch Digital Audio
Mixer) and channel 1 (Audio Data Input)
And its reception-only port (PORT) # 1, channel 2 (Au
dioData Input) and its receive-only port (PORT) #
2, Channel 3 (Audio Data Input) and its receiving port (PORT) # 3, Channel 4 (Audio Data Input)
t) and its receive-only port (PORT) # 4, channel 5
(Audio Data Input) and its receiving port (PORT)
# 5, Channel 6 (Audio Data Input) and its receiving port (PORT) # 6, Channel 7 (Audio Data Input)
Input) and its receiving port (PORT) # 7, channel 8 (Audio Data Input) and its receiving port (PO)
RT) # 8, Path Information Manager
r) and its transmission / reception port (PORT) # 50, a control data input / output unit (Control Data Input / Output) and its transmission / reception port (PORT) # 60.

Reference numeral 4 denotes a PCM sound source 1 (PCM To
ne Generator) and MIDI message input (MI
DI Mesg. Input) and its receive-only port (PORT) #
1, MIDI message input (MIDI Mesg. Input) and its receiving port (PORT) # 2, audio data output (Audio Data Output (L)) and its sending port (PORT) # 10, audio data output (Audio Data)
Output (R)) and its dedicated port (PORT) # 11, Path Information Manager (Path Information Manager) and its transmitting / receiving port (PORT) # 50, Control data input / output unit (Control Data Input / Output) and its transmitting / receiving port (PORT) # 60. Also, 5 is FM
Method sound source 2 (FM Tone Generator), 6 is sound source 3
(Tone Generator), and these configurations are similar to those of the sound source 1. Note that these nodes 1-6
In, the port operates independently by the program of the port, and the functions other than the port operate independently by the application program.

In each of the components thus constructed, the transmission-only port (PORT) # 1 of the keyboard 1 is the reception-only port (PORT) # 1 of the sequencer 2 and the reception-only port (PORT) # of the tone generator 1 through the path L1. 2, the receive-only port (PORT) # 2 of the sound source 2, the receive-only port (PORT) # 2 of the sound source 3, and the send-only port (POR) of the sequencer 2
T) # 17 is connected to the reception-only port (PORT) # 1 of the sound source 1 by the path L2, and the transmission-only port (PORT) # 18 of the sequencer 2 is the reception-only port (PORT) of the sound source 2 by the path L3. ) # 1, and the transmission-only port (PORT) # 19 of the sequencer 3 is connected to the reception-only port (PORT) # 1 of the sound source 2 by the path L4.

Also, the transmission-only port (PORT) of the sound source 1 #
10 is a reception-only port of the mixer 3 (PO
RT) # 1 and the transmission-only port (PORT) # 11 of the sound source 1 is connected to the reception-only port (PORT) # 2 of the mixer 3 through the path L6, and the transmission-only port (PORT) of the sound source 2 ( PORT) # 10 is connected to the reception-only port (PORT) # 3 of the mixer 3 by the path L7, and the sound source 2
Transmission-only port (PORT) # 11 of the mixer 3 is connected to the reception-only port (PORT) # 4 of the mixer 3 by the path L8, and the transmission-only port (PORT) # 10 of the sound source 3 is connected to the path L.
9 is connected to the reception-only port (PORT) # 5 of the mixer 3, and the transmission-only port (PORT) # 11 of the sound source 3 is connected.
Is a receive-only port (POR
T) connected to # 6.

As described above, the logical paths L1 to L1 are connected between the ports.
By connecting with L10, the same operation as the electronic musical instrument shown in FIG. 22 can be performed. This logical path is a virtual transmission path as described above, but the transmission port assigns a group address to the transmission data and broadcasts it, and the reception port to which the group address is set receives the logical path. Is configured.
Therefore, the data transmitted from the transmission port on this logical path can be received by the plurality of reception ports. If the user once sets the logical path that makes up the network and the receiving port stores the information of that logical path, the original logical path can be set at power-on or reset. Can be rebuilt and rebuilt on the network. Further, the logical path information can be reconstructed on the network by storing the logical path information in a portable storage medium, for example, a floppy disk, and setting the floppy disk in the connection management device. Is.

Next, the network construction method of the present invention will be described in detail with reference to a flow chart. Of the nodes connected to the network of the present invention, a flowchart of a main routine of a sound source is shown in FIG. 2 as an example. In this figure, for example, when the power source is turned on and started, the function of the sound source module is initialized in step S100, for example, the normal function initialization such as dump processing is performed so that an abnormal sound is not generated, and then step S110. At this, the function of the network, which will be described later, such as recognition of the address of the own node and what is connected to other nodes, is performed. Then, by scanning the buffer in which the data input from the network is set in step S120, it is determined in step S130 whether the data is network-related data, and if it is determined that the data is network-related data, In S140, the reception processing is performed as the data for managing the network operation.

If it is determined that the data is not network-related data, the data received in step S150 is determined to be musical tone control information, and the musical tone control information is used to control the tone generation state such as tone generation processing or mute processing. Is done. However, the operation in step S150 is an example in the case where the node is the sound source, and the process according to the function is performed in the other nodes. And step S14
0, or when step S150 ends, panel processing is performed in step S160.
This panel process includes a process in which the user manually constructs a logical path on the network by the panel setting.

By this panel processing, once the path management table is created in each node, the logical path can be reconstructed based on the path management table thereafter. Next, in step S170, a process of transmitting data to the network is performed. The data is transmitted to the network by creating a port of a virtual program called a port and transmitting it from the application program to the port. Also, the protocol of the port information table is multicast (mu
lticast) is broadcast without specifying the address of the communication partner by specifying the corresponding group number. Then, the process returns to step S120, and the above-described operations of steps S120 to S170 are repeated.

Next, in FIG. 4, step S of the main routine.
10 shows a flowchart of a network function initialization process executed at 110. When the network function initialization process is started, first, when the network is started in step S300, the node number of the own device is obtained by an algorithm for recognizing the node number. Next, in step S310, background network processing, which will be described later, is started, and the node that has become the configuration management node
In background network processing, the transmitted packets are monitored, the node number is broadcast from each packet, the node number is collected, and the packet is further transferred to the upper layer or processed according to the service request of the packet. And so on. Then, the node number of the own device obtained in step S300 is broadcast on the network in step S320. The data of the broadcasted node number is received and automatically recorded by the node that has become the configuration management node.

Further, the configuration management node, which recognizes the network configuration and broadcasts a configuration information completion packet after the recognition, waits for this configuration information completion packet in step S330, which is the configuration management node configuration information completion. It is a step to wait until. It should be noted that the configuration management node has an algorithm such that there is a node with a margin among the nodes connected to the network. Then, when a packet indicating that the network configuration information is completed is obtained, the node specific information of the own node is notified to the configuration management node through the network in step S340. This node unique information is the unique address of the self node, the node information, and the device unique number. The unique address is the unique number of the low-level electronic device, which is different for each product. What is the function of the node information? The device unique number is a number unique to a higher-level device, and the same number is given to electronic devices having the same function.

FIG. 5 shows a node table of such node-specific information. In this figure, for example, node number 1
Has a unique address of "aaaa.aaaa", node information of "MIDIKeyboard", and device unique number of "AAAAAAAA". When the configuration management node receives the node management information as described above from all the nodes, it broadcasts a node information completion packet on the network. The step of waiting for this packet is step S350.
That is, the management node waits until it finishes collecting the node-specific information of all the nodes. As a result, the node table shown in FIG. 5 is completed. Therefore, when the node information completion packet is obtained, the node specific information of another node is acquired from the configuration management node in step S360, and the node table of the own node is created.

Next, in step S370, a port is created according to the function of its own node. First, a port number is assigned, and the port is an input port, an output port, or an input / output port. Information is created and a port information table as shown in FIG. 7 is created. This port creation will be described later,
In step S370, each transmission-only port has acquired a unique group number. Then, step S38
At 0, for example, it is determined whether or not the path management table as shown in FIG. 8 exists in the own node. When it is determined that the path management table exists, the path is reconfigured in step S390. Further, in step S390, if a packet is lost or the partner node cannot react, the path connection (path reconfiguration retry) is attempted again for the path that could not be configured in the first time. Further, in step S410, a path that cannot be connected even by the path reconfiguration retry is assumed to have no corresponding electronic device, and is forcibly connected to an electronic device having the same function. Next, the process returns as in the case where it is determined in step S380 that there is no path management table. When an electronic device is newly connected to the network, there is no path management table. For electronic devices that do not have a receiving port, see step S
The processing steps 380 to S410 are not implemented.

Next, FIG. 6 shows a flowchart of the port creation processing executed in step S370 of the network function processing processing. When the port creation process is started, a port information table is created in step S500 in association with the internal function of the own device. For example, in the sequencer, a port information table as shown in FIG. 7 is created. However, the group number is given in the following steps. That is, in step S510, information of one port, for example, port number 1, is extracted, and in this extracted information in step S520, whether or not the protocol is multicast and whether the type of the port is type. ) Is for sending only (TX ON
LY), and if the protocol is multicast and the port type is transmission-only, the transmission-only port acquires a unique group number on the network in step S530.

Further, the acquired group number is recorded in the port information table in step S540. For example, as in the port information table shown in FIG.
0 ”is recorded. Next, as in the case where it is determined in step S520 that the protocol is not multicast or the port type is not transmission-only,
In step S550, it is determined whether there is an unprocessed port. If there is an unprocessed port, step S510.
Then, the operation for the transmission-only port to acquire the group number is repeated as described above. When it is determined that all ports have been processed and there are no unprocessed ports, the process returns. Note that in FIG. 7, “d” recorded in the group number column indicates that nothing is written, or even if written, it is ignored and not used.

By the way, although the background network processing is started in step S310 of the network function processing, when the background network processing is started, as shown in FIG. 3, step S200 is performed.
In step S210, the packet is monitored, and special processing is performed in step S210. For this special processing, the node that has become the configuration management node collects the node number from each of the broadcast packets and collects the node-specific information. However, nodes that do not realize special functions, such as the configuration management node, do not implement this special processing. Further, in step S220, it is determined whether or not the packet is broadcast, or whether or not it is addressed to its own node, and if it is determined to be broadcast or addressed to its own node, in step S230 it is determined whether or not it is a packet to be passed to an upper layer. If it is determined that the packet is not a packet to be passed to the upper layer, various tables are referred to in response to the service request in step S240, and the data of the own node is returned. Here, the reply to the inquiry about the port attribute at the time of setting the path and the reply to the request from the user for the port information table are returned.

If it is determined in step S230 that the packet should be passed to the upper layer, step S25.
At 0, the packet is transferred to the upper layer. Then, if it is determined in step S220 that it is not a broadcast and is not addressed to its own node, and if the processing in step S240 or step S250 is completed, the processing returns to step S200, and the processing in steps S200 to S220 described above. Is repeated.

Next, a flow chart of the path reconfiguration processing is shown in FIG. When this path reconfiguration processing is started, the path setting state of the path management table is first cleared in step S600. The path management table of the mixer is shown in FIG. 8. The path setting state in the rightmost column of this path management table is cleared by this step.
The following description will be given with reference to this path management table. Next, in step S610, data is acquired from the top of the path management table, and in step S620, it is determined whether or not the transmitting side unique address exists in the node table. If the path connecting the receiving port of the own node is the top row of the path management table shown in FIG. 8, the sender unique address is the node with "dddd.dddd". This is to determine whether or not the electronic device having the address is connected to the network, and if it is determined to be present, the process proceeds to step S630.

In step S630, the attributes of the transmission / reception port are confirmed, and in step S640, the presence of the port is confirmed and it is determined whether the attributes match. This determination is made by referring to this node table by utilizing the fact that the node table common to all nodes shown in FIG. That is, by searching the node table, the unique address "dddd. Dddd" can be found at the node number 4. Also, regarding the receiving side port number 1, the existence of the receiving side port number 1 of the own node can be confirmed, and since the attribute is also recognized, the existence has been confirmed and it must be the multicast receiving port. The attributes of are also recognized. Furthermore, for the sender port, the unique address in the path management table is "dddd.dd.
dd ”, so if you refer to the node table, this transmission port will be the PCM tone generator (PCM Tone Gene
It is confirmed that the port is the transmission port of the rator), the existence of the port is confirmed first, and further, from this path management table, the transmission side port number is "10" (note that the group number also has the number "10"). , Which is not related to this number.).

Therefore, referring to the port information table of the PCM sound source (not shown), it can be seen that the transmission port with the port number "10" is the multicast transmission port, so the ports connected by the path are the reception port and the transmission port. Since it is recognized and its attributes match, step S6
Go to 50. In this step S650, the group number of the transmission port is acquired by referring to the group number column of the port information table on the transmission side, and registered in the port information table of the own node as the group number of the reception table of the reception side node. As a result, it becomes possible for the receiving port in which the same group number is registered in the receiving port to receive the data broadcast by the transmitting side with the group number.

Then, in step S670, the path setting state of the path management table is set to "1". This "1"
Indicates that the path setting state is completed as shown in FIG. If it is determined in step S620 that the unique address does not exist in the node table, the presence of the port is not confirmed in step S640, or the attributes do not match, the path management table is set in step S660. The state is set to "3". This "3" indicates that it is in the hold state as shown in FIG. Next, step S
Similar to the case where the processing of 670 is completed, step S68.
If it is determined that the next data exists, the process returns to step S610,
The path reconstruction process is repeated. Further, when it is determined that there is no data next, the process is returned as it is.

Here, in step S620,
As an example of the case where it is determined that the unique address does not exist in the node table, the unique address of the receiving side port number 5 of the path management table shown in FIG. 8 is “ffff.
This unique address cannot be found even by referring to the node table shown in FIG. In this case, the product at the time of creating the path management table is not connected to the network, the process branches to "NO" in step S620 and the process of step S660 is performed. At this time, if an electronic device having the same function as the unconnected product is connected to the network, a path is forcibly set between the unconnected product and this electronic device instead of the unconnected product. For this reason, the path setting state of the path management table is set to "3" indicating the hold state. By the above processing, when the node is a mixer, the path management table shown in FIG. 8 is obtained.

Next, a flowchart of the functional path reconfiguration is shown in FIG. 11. In the functional path reconfiguration processing, the processing is performed for the paths that are not connected in the path reconfiguration processing. When the processing of this functional path reconfiguration is started, in step S700, data of "path setting state = 3" is acquired from the management table.
For example, in the case of the path management table shown in FIG. 8, first, the data of the port number 5 on the receiving side is acquired, and in order to recognize whether or not a node having the same function is connected, this device side unique number "FFFFFFFF" Is searched with reference to the node table shown in FIG. In this case, since the device unique number “FFFFFFFF” can be found in the node number 6 of the node table, it is determined “YES” in step S720, and the process proceeds to step S730.

In this step, the attributes of the transmission / reception port are confirmed in the same manner as in step S630 shown in FIG. 10, and it is further determined in step S740 whether the attributes of the transmission / reception port match. Note that the existence of the port is not confirmed in step S740 if the device-specific number on the transmission side can be searched.
This is because it can be seen that an electronic device having the same function is connected, and it can be considered that a port exists. However, a port existence confirmation process may be performed. Next, in step S750, a warning is issued to the user to request confirmation of the path connection. If the user permits the path connection, it is determined in step S760 that the connection is possible, and step S7
At 70, the group number of the transmission port is acquired and registered as the group number of the reception port in the port information table of the reception side node.

Further, in step S800, the path setting state of the path management table is set to "2" indicating the path connection state under the warning as shown in FIG. Then, in step S810, the user is inquired whether or not to update the path information, and when the user permits the update, it is determined that the update is performed in step S820, and step S8
At 30, the transmission side unique address of the path management table is rewritten with the corresponding unique address of the node table. The path connected in step S770 is a temporary connection, and if the electronic device newly connected to the network does not connect temporarily but continues to connect thereafter, the user determines the path in step S820. Try to update the information. If this path information is not updated, the user will need to permit path connection each time the network is started up.

If the sending device unique number cannot be found by searching the node table in step S720, or if the attributes of the transmission / reception port do not match in step S740, the path of the path management table is found in step S790. As shown in FIG. 9, the setting state is set to "5" indicating the unconnectable state. Further, when it is determined in step S760 that the user does not permit the connection, the path setting state of the path management table is set to "4" indicating the unconnected state under the warning in step S780. Then, when it is determined in step S820 that the user does not permit the update, and in step S78.
When 0, step S790, and step S830 are completed, the process proceeds to step S840, it is determined whether there is next data, and if it is determined that there is next data, the process returns to step S700. The functional path reconstruction processing as described above is repeatedly performed. If it is determined that there is no next data, the process returns. When the above functional path reconfiguration processing is performed, the mixer path management table shown in FIG. 8 is rewritten to the path management table shown in FIG. However, in this case, the path information is updated.

Next, step S in the main routine
A flowchart of the network reception process executed at 140 is shown in FIG. When the network reception process is started, it is determined in step S900 whether the data received from the network is a reset signal,
If it is determined that the signal is the reset signal, all the functions of the own node are reset in step S920. This reset signal is for resetting the network when a new node is connected to the network.
As described above with reference to FIG. 1, since each node is independently separated into an application program part and a port program part, it is possible to reset only the port program. When the signal is sent from the end of the network, etc., due to the effect of the propagation delay time of the network,
It may collide with the data sent by other nodes and continue to make noise or run away. Therefore, we are resetting all the functionality of the node here.

If it is judged that the signal is not the reset signal, it is judged in step S910 whether or not it is a load request for the path management table. In steps S900 to S950, for example, the path management stored in the floppy disk is managed. This is a process for constructing a path using a table. That is, the path management table load request is a load request for rewriting the path management table of each node with the path management table stored in the floppy disk or the like set in the connection management device. Therefore, when it is determined that the received data is the path management table load request in step S910, the functions other than the network part of the own node are stopped in step S930. This stop does not simply stop, but also stops the function so that it does not hinder the path reconfiguration. That is, in the case of a sound source, all the musical tones being generated are stopped, and in the case of a sequencer, recording / reproduction is stopped.

Next, in step S940, the load permission is notified to the connection management device which is the load request sending source.
Next, in step S950, the path management table transferred from the connection management apparatus is rewritten so as to be a new path management table. As a result, a new path is reconfigured using the new path management table. Then, the process proceeds to step S960 as in the case where it is determined that the data received in step S910 is not the path management table load request. Steps S960 to S980 are processes for dumping the information in the path management table to a floppy disk or the like. It is determined whether the data received from the network in step S960 is a path management table dump request, and the path management table is determined. If it is determined to be a dump request, the dump permission is notified to the connection management device that is the dump request source in step S970.

Further, in step S980, the information in the path management table of the own node is dumped to the dump request sending source. The connection management device collects the information of the sent path management table for all the nodes and records it in a floppy disk or the like. Then, as in the case where it is determined in step S960 that the data received from the network is not the path management table dump request,
Will be returned.

Next, FIG. 14 shows a flowchart of processing executed by the connection management device. When the connection management device is powered on and the processing is started, the network function is initialized because the connection management device is also one of the nodes.
This initialization of the network function is performed by the same process as that shown in FIG. 4, but since the path management table is not required, the process branches to "NO" in step S380 and returns. Returning to FIG. 14 and continuing the description, next, whether or not a floppy disk or the like has been inserted into the connection management device is detected in step S1010. This detection is repeated until the disk is inserted. When it is detected that the disk is inserted, the command is awaited in step S1020, and when either the load command of the path management table or the dump command of the path management table arrives,
Which command has arrived is determined in step S1030, and if it is determined that the command is a load command of the path management table, path information (unique address, node information,
Read the device unique number).

Then, in step S1050, it is determined whether or not all the nodes corresponding to the node data (unique address or device unique number) of the path information are present, and it is determined that all the nodes corresponding to the node data of the path information are present. If so, step S1060
Move to. Here, not only the device corresponding to the unique address but also the device corresponding to the device unique number is applicable. It is expected that electronic devices having different functions but having the same function are replaced and connected to the network. Because. In step S1060, a load request for the path management table is sent to one node, and in step S1070, after receiving the load permission from the partner node, the path management table is loaded by sending it to the partner node.

Then, in step S1080, it is determined whether or not the path management table has been transmitted to all the nodes, and if there is a node that has not transmitted the path management table, the process returns to step S1080 and the same processing as described above is performed. It is repeated until the path management table is transmitted to all the nodes. In this way, when the path management table is transmitted to all the nodes, the reset signal is transmitted to all the nodes in step S1120, and all the nodes are reset. If it is determined in step S1050 that all the nodes corresponding to the node data of the path information do not exist, step S1090.
At, it is confirmed whether or not only those that can be connected are forcibly connected.

Here, when it is detected in step S1100 that the user has forcibly permitted the connection, the path management table is transmitted only to the node corresponding to the node data in the path information in step S1110. . In this case, when there are a plurality of applicable nodes, the path management table is sequentially transmitted to the applicable nodes. Then, in step S1120, a reset signal is transmitted to all nodes to reset all nodes, and step S
Proceed to 1130. Further, also when it is determined in step S1030 that the command is not the path load command, the same as when it is determined in step S1110 that the user does not permit the forced connection, step S113.
Then, it is judged whether the command is a dump command of the path management table or not.

If it is determined that the command is a dump command of the path management table, in step S1140, the path to the node having the PIM (path information management unit; Path Information Manager) among all the nodes of the node table is passed. Send a dump request for the management table. Then, after receiving the dump permission in step S1150, the path management table sent from the other node is received, and in step S1160, it is determined whether or not the path management tables from all the corresponding nodes have been received. If it is determined that the path management table has not been received from the corresponding node in step S1,
Returning to 140, the same processing as described above is repeated until the path management tables are received from all the corresponding nodes.

When the path management tables are received from all the corresponding nodes, each node data is added to the path management table ordered in step S1170 and stored in the floppy disk or the like, and the process is returned. The disk is not limited to a floppy disk, but may be a hard disk, an optical disk, or the like.
FIG. 15 shows an example of the storage state when a floppy disk is used.
It shows in (a). In the case shown in this figure, a unique address, a device unique number, and a path management table are sequentially stored for each node. Further, as shown in FIG. 9B, data for each node including a group number, a transmission unique address, a transmission side device unique number, and reception side information may be stored.

Next, step S160 of the main routine.
FIG. 16 shows a flowchart of the panel processing executed in. This panel process is a process of setting a path to be initially constructed at the same time as performing the normal panel process. When the panel process is started, the normal panel process is first performed in step S1200. Next, step S12
If it is determined in 10 that the path connection processing is to be performed and it is determined that the path connection processing is to be performed, step S1220
At, the electronic device connected to the network is displayed on the display based on the node table.

At this time, since the connecting port information is not obtained from the node table, step S1230.
In step 1, the port information regarding the node designated by the user is retrieved from the corresponding node and this port information is displayed on the display. Next, the user connects the ports designated by referring to the display as a path. In this connection, the ports are connected by matching the group number of the transmission port with the group number of the reception port as described above. Further, the path management table is rewritten based on the connected path in step S1250. Then, the process returns as in the case where it is determined that the path connection process is not performed in step S1210.

The reconstruction of the path information in the above-described network construction method is briefly summarized as follows. (1) The transmitting side determines the group number for each path (2) The receiving side inquires the group number of the transmitting side for each path (3) The receiving side inquires the group number of the port information table and rewrites it with the data (4 ) The receiving side receives data according to the group number of the port information table According to this method, the receiving node inquires the group number of the transmitting node individually, so if there are many receiving nodes, it will cause unnecessary traffic. .

The second network construction method of the present invention which can solve this will be described below. The outline of the procedure of this second network construction method is as follows. (1) The sender determines the group number for each path (2) The sender broadcasts the group number and unique address first (3) The receiver receives this and assigns the group number based on the unique address Setting (4) The receiving side receives the data according to the group number of the port information table As described above, in the second network building method, the receiving side triggers the reconfiguration in the above-mentioned network building method. It is designed such that the transmitting side triggers reconfiguration. Therefore, the reconfiguration only needs to be broadcast once, and is simple without incurring unnecessary traffic.

Next, a method for constructing the second network will be described. Regarding the same processing as the above-mentioned network construction method, the explanation thereof will be omitted and different processing will be explained with reference to the flowchart. First, the flowchart of the main routine of the electronic device connected to the network, for example, the main routine of the sound source, is the same as that shown in FIG.
The network function initialization process executed at 10 is different. Therefore, a flowchart of the network function initialization process is shown in FIG. 17, but in this network function initialization process, the node table as shown in FIG. 5 is not created.

When this network function initialization processing is started, as shown in FIG. 17, when the network is started in step S1300, the node number of its own machine is obtained by the algorithm for recognizing the node number. This node number is not a fixed number, but a dynamically determined node number is obtained. Next, in step S1310, the process waits until the bus reset ends. In other words, the configuration management node waits until it finishes collecting the path configuration information. Next, in step S1320, background network processing, which will be described later, is activated, and further, in step S1330, port creation processing for creating a port according to the function of the own node is executed, and the process returns.

FIG. 19 shows a flow chart of this port creation process. When the port creation process is started, a port information table is created in step S1500 in correspondence with the internal function of the own device. For example, in the sequencer, a port information table as shown in FIG. 7 is created. However, the group number is given in the following steps. That is, in step S1510, information of one port, for example, port number 1, is extracted, and in this extracted information in step S1520, whether the protocol is multicast or not, and the type of port (type) ) Is for sending only (TX
ONLY), if the protocol is multicast and the port type is transmission only, the transmission dedicated port acquires a unique group number on the network in step S1530.

Further, in step S1540, the acquired group number is recorded in the port information table. For example, as in the port information table shown in FIG.
0 ”is recorded. Next, in step S1550, the unique address, node number, port number, and group number are broadcast. As a result, the receiving side can obtain the group number broadcast together with the unique address of the transmitting side port number to be connected. Next, in the same manner as when it is determined in step S1520 that the protocol is not multicast or the port type is not transmission-only, it is determined in step S1560 whether there is an unprocessed port, and there is an unprocessed port. Returns to step S1510, and the operation for the transmission-only port to acquire the group number is repeated as described above. When it is determined that all ports have been processed and there are no unprocessed ports, the process returns.

Next, step S of the network function processing.
A flowchart of the background network processing started in 1320 is shown in FIG. When this background network process is activated, the packet is monitored in step S1400, and in step S1410 it is determined whether the packet is a broadcast or addressed to its own node. If it is determined to be a node,
In step S1420, it is determined whether the packet should be passed to the upper layer. If it is determined that the packet is not a packet to be passed to the upper layer, it is determined in step S1430 whether or not the packet is a group number notification packet, and the group number notification packet broadcast in step S1550 of the port creation processing is determined. In this case, the process branches to step S1460 and the path reconfiguration processing is performed.

If it is determined that the packet is not the group number notification packet, various tables are referenced in response to the service request in step S1440, and the data of the own node is returned. Here, the reply to the inquiry about the port attribute at the time of setting the path and the reply to the request from the user for the port information table are returned. If it is determined in step S1420 that the packet should be passed to the upper layer, the packet is transferred to the upper layer in step S1450. If it is determined in step S1410 that it is not a broadcast and is not addressed to its own node, or if the process of step S1440, step S1460, or step S1450 is completed, the process returns to step S1400, and steps S1400 to S1460 described above are performed. The process of is repeated.

Next, FIG. 20 shows a flowchart of the path reconfiguration processing executed in step S1460 of the background network processing. When this path reconfiguration processing is started, the path setting state of the path management table is first cleared in step S1600. The path management table in this case is shown in FIG. 21 (a) using a mixer as an example, but unlike the one shown in FIG. 8, the column of the transmission side device unique number is omitted. This is because the functional path reconfiguration processing is not performed in the second network construction method.

Here, the "path setting state" in the rightmost column of this path management table is cleared in step S1600. The following description will be given with reference to this path management table. Next, step S1
At 610, it is determined whether or not there is path information in the path management table that has already been obtained, that matches the sender information that is a combination of the sender unique address and the sender port number, and it is determined that there is path information. Then step S16
At 20, the group number broadcast from the transmitting side is acquired and registered as the group number of the receiving port in the port information table of the receiving node.

Then, in step S1630, as shown in FIG.
As shown in 1 (a), the path setting state of the path management table is set to "1". This "1" indicates that the path setting state has been completed as shown in FIG. Furthermore, the process returns as in the case where it is not determined in step S1610 that the path information in the path management table matches the sender information. When the group number broadcast from the transmitting side cannot be acquired, the path setting state in the path management table is set to "0", and the connection is disabled as shown in FIG.

As described above, in the second network construction method, the unique address, the node information, the port number, and the acquired group number are once broadcasted in the case of the transmission dedicated port which is the protocol multicast, so that the receiving side broadcasts. The group number of the transmission port to be connected is acquired from the information obtained. For this reason, the path reconfiguration processing can be executed only by performing simple communication. However, since the receiving side, which grasps the actual condition of the path, does not trigger, it becomes difficult to deal with the failure of the reconfiguration. Therefore, the broadcasting from the transmitting side may be performed a plurality of times. Alternatively, when there is an unestablished path on the receiving side (which can be determined by detecting the path setting state column of the path management table being “0”), after a predetermined time, a specific path is determined. A broadcast request or a path reconfiguration request from the sender may be broadcast.

In the above description, the electronic musical instrument network has been described as an example, but the present invention is not limited to the electronic musical instrument network, and consumer electronic devices such as a television, a video tape recorder, an audio device, and karaoke. It can be applied to a network construction method for connecting intelligent electronic devices such as devices.

[0065]

As described above, according to the present invention, based on the stored logical connection information, a logical path for connecting electronic devices on the network is restored and rebuilt on the basis of the stored logical connection information. Therefore, even if you disconnect the connection once, you can easily restore it. Therefore, even when the electronic musical instrument formed by connecting a plurality of electronic devices is disconnected and moved to a stage or the like, the network is configured.
The electronic musical instrument network system can be reconstructed by connecting each electronic device related to the electronic musical instrument to the transmission line of the book and turning on or resetting the power source. In addition, even if the products connected to the network are different, if an electronic device with the same function is connected, the newly connected electronic device with the same function will be forcibly connected to the network instead of the product that was previously connected. Can be connected.

Further, if the receiving side stores the logical connection information, the data amount of the connection information can be distributed and stored as compared with the case where the transmitting side stores the connection information, and the network can be operated at high speed. Can be launched.
Furthermore, if the logical path information is stored in a portable storage medium, the environment of the same network system can be set by simply setting the storage medium in the connection management means in a studio or the like equipped with electronic devices having the same function. Will be able to be reproduced. Further, in the network system of the present invention, since the network is not serially connected like MIDI, even if one electronic device is disconnected, data can be sent to the subsequent electronic devices. Therefore, it becomes difficult to be in a fatal state.

[Brief description of drawings]

FIG. 1 is a diagram showing a network of electronic musical instruments constructed by a network construction method of the present invention.

FIG. 2 is a flowchart of a main routine in the network construction method of the present invention.

FIG. 3 is a row chart in the network construction method of the present invention.

FIG. 4 is a flowchart of network function initialization in the network construction method of the present invention.

FIG. 5 is a diagram showing a node table in the network construction method of the present invention.

FIG. 6 is a diagram showing a flow chart of port creation in the network construction method of the present invention.

FIG. 7 is a diagram showing a port information table in the network construction method of the present invention.

FIG. 8 is a diagram showing a path management table in the network construction method of the present invention.

FIG. 9 is a table showing state contents of a path setting state in the network construction method of the present invention.

FIG. 10 is a diagram showing a flowchart of path reconfiguration in the network construction method of the present invention.

FIG. 11 is a diagram showing a flowchart of functional path reconfiguration in the network construction method of the present invention.

FIG. 12 is a diagram showing a path management table in the network construction method of the present invention.

FIG. 13 is a diagram showing a flowchart of network reception processing in the network construction method of the present invention.

FIG. 14 is a diagram showing a flowchart of a connection management device in the network construction method of the present invention.

FIG. 15 is a diagram showing an example of a storage state of a floppy disk in the network construction method of the present invention.

FIG. 16 is a diagram showing a flowchart of panel processing in the network construction method of the present invention.

FIG. 17 is a flowchart of network function initialization in the second network construction method of the present invention.

FIG. 18 is a flowchart of background network processing in the second network construction method of the present invention.

FIG. 19 is a diagram showing a flowchart of port creation in the second network construction method of the present invention.

FIG. 20 is a diagram showing a flowchart of path reconfiguration in the second network construction method of the present invention.

FIG. 21 is a diagram showing a path management table and a table showing the contents of a path setting state in the second network construction method of the present invention.

FIG. 22 is a diagram showing a network of a conventional electronic musical instrument.

[Explanation of symbols]

 1, 101 keyboard 2, 102 sequencer 3, 103 mixer 4, 104 sound source 1 5, 105 sound source 2 6, 106 sound source 3 L1 to L10 logical path L101 to L107 line

Claims (4)

[Claims] 1. A network having a plurality of electronic devices connected to a network, wherein the electronic devices are connected by a logical path constructed on the network, wherein the electronic device has at least one transmission port or The logical path is restored and reconstructed on the network based on the path information related to the transmission port which has a reception port and is connected to the reception port when the network is constructed, and the path information is received. A network construction method characterized by being recorded on the port side. 2. A network of electronic musical instruments, comprising a plurality of electronic devices constituting an electronic musical instrument connected to a network, wherein the electronic devices are connected by a logical path constructed on the network. Has at least one transmission port or reception port, and when the network is constructed, the logical path is restored and reconstructed on the network based on path information regarding the transmission port to which the reception port is connected. A network construction method characterized by the following. 3. The logical path information is recorded in a portable recording medium, and by setting the recording medium in one of the electronic devices connected to a network,
3. The network construction method according to claim 1, wherein the logical path is restored on the network and reconstructed. 4. The network construction method according to claim 2, wherein, as the logical path information, path information regarding the transmission port to which the reception port is connected is recorded on the reception port side.