JPH09261232A - Method for controlling plural response communication in atm exchange - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent the increase of communication quantity by permitting a common part to return response data of an instance being a response place/ item which is set in a command where an individual part to be a response object is designated to a center control part by means of a responce status. SOLUTION: The command/responce status is exchanged in order to collect response data of plural interface devices (individual part) under a districution/ line concentration device between an ATM switch (center control part) and the distribution/line concentration device (common part). The ATM switch designates the interface device to be the response objecta to the command to be transmitted to the distribution/line concentration device and also sets the instance being the response place/item in the device. Then, the distribution/ line concentration device analyzes then command and returns response data of the instance which is set in the command to the ATM switch by the response status. Thus, the enlargement of communication quantity is prevented even when plural point data is collected for the same item, etc.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention responds to a single command request as in a case where an ATM switch or the like as a central control unit in an ATM switch collects data from interface devices or the like as a plurality of individual units. And a communication control method when a plurality of individual units notify a plurality of response statuses.

As a next-generation switching system, ATM (Asynchrono
us Transfer Mode) Exchange technology was agreed by ITU-T,
Broadband ISDN (Integrated Service Digital Network)
Research is actively conducted in each institution as a technology to realize rk).

FIG. 2 shows the structure of an ATM exchange system on which the present invention is based. In the figure, an ATM switch accommodates a plurality of distribution / concentrator devices, and each distribution / concentrator device accommodates a plurality of interface devices. In the following description, the ATM switch will be referred to as a CC (central control unit), the distribution / concentrator device will be referred to as a common unit, and the interface device will be referred to as an individual unit.

Communication between the CC and the common part is performed by DMA (Direct M
emory Access) Communication is performed, and when the CC requests collection of billing data etc. to the common part, the CC issues a command to the common part, and the common part sends a response status to the CC. The process is completed in one sequence of sending back.

This ATM exchange has a data collection function and collects not only the billing data collected in the common section but also a plurality of data such as the number of passing cells and the number of discarded cells at each point in the common section. . In addition, the individual unit also collects PM (performance monitor) data.

Control of sucking up these data to the CC is also performed by the DMA communication, but conventionally, the command issued by the CC is different for each individual unit, and the response status to the command is also different for each individual unit. Ship back separately. Furthermore, even if there are multiple points or items to be monitored in one individual unit, the CC issues separate commands for each point or item even when requesting data collection for one individual unit. , Receiving the response status for each of these points and items.

For this reason, the amount of command / status data exchanged between the CC and the common section becomes enormous and the C
The amount of communication between C and the common part becomes enormous and congestion occurs. As a result, other control functions (path control, etc.) that require real-time processing will be greatly affected.
Some kind of control is required.

Conventionally, as a countermeasure against this, a method of lowering the priority of commands of the data collection function and raising the priority of other control functions (path control, etc.) has been adopted.
This method is not a method of reducing the absolute amount of data exchanged by the data collection function, but the fact is that no study has been made on a method of substantially reducing the communication amount in the past.

Therefore, an object of the present invention is to provide a plurality of commands with a single command even when it is desired to collect data of a plurality of points for the same item or to perform the same control for a plurality of interface devices. The purpose of the status response is to prevent an enormous amount of communication.

[0010]

SUMMARY OF THE INVENTION The present invention is a multiple response communication control for transmitting / receiving a command / response status for collecting response data of an individual section under the common section between a central control section and a common section in an ATM switch. It is premised that it is a method.

In order to solve the above-mentioned problems, according to one aspect of the present invention, the central control unit designates an individual unit to be a response target in a command transmitted to a common unit and makes a response in the individual unit. Multiple responses in the ATM switch, in which one or more instances that are locations / items are set, and the common unit analyzes the command and returns the response data of the instance set in the command to the central control unit according to the response status. A communication control method is provided. According to this method, since a plurality of instances can be designated by one command and the corresponding response data can be received with at least one response status, the communication amount between the central control unit and the common unit can be greatly reduced.

In another aspect of the present invention,
The tail information section is set in the command transmitted from the central control section to the common section, and the all-instruction is specified in the tail information section to instruct the response for all instances that are response points / items in the individual section. , A common part analyzes the command and returns the response data of all the instances to the central control part with one or more response statuses, thereby providing a multi-response communication control method in an ATM switch. According to this method, all the instances can be designated by one command, and the corresponding response data can be received with at least one response status, so that the communication amount between the central control unit and the common unit can be greatly reduced.

In another aspect of the present invention,
The central control unit sets the tail information section in the command to be transmitted to the common section, and sets the tail information section to the response point / individual section.
A plurality of instance designations for instructing a response for a part of the instance which is an item is set, and the common unit analyzes the command and returns response data of the designated instance to the central control unit with one or more response statuses. A method for controlling multi-response communication in an ATM exchange is provided. According to this method, multiple instances can be specified with one command and the corresponding response data can be received with at least one response status.
The amount of communication between common parts can be significantly reduced.

In another aspect of the present invention,
The central control unit sets, in the command to be transmitted to the common unit, one or more lists specifying the individual units to be responded out of the individual units under the common unit, and the common unit analyzes the command and sets the command to the command. There is provided a multiple response communication control method in an ATM exchange in which response data of a set list is returned to the central control unit according to a response status. According to this method, you can specify multiple lists with one command,
Since the corresponding response data can be received with at least one response status, the amount of communication between the central control unit and the common unit can be greatly reduced.

In another aspect of the present invention,
The central control unit sets the tail information section in the command to be transmitted to the common section, and sets the list / all designation for instructing responses for all the individual sections under the common section in the tail information section. A multi-response communication control method in an ATM exchange is provided in which the response data of all lists designated by analyzing the command are returned to the central control unit according to one or more response statuses. According to this method, you can specify the entire list with one command and receive the corresponding response data with at least one response status.
The amount of communication between the central control unit and the common unit can be significantly reduced.

In another aspect of the present invention,
The central control unit sets the tail information part in the command to be transmitted to the common part, and sets in the tail information part a plurality of list designations instructing a response for a part of the individual parts under the common part. A multi-response communication control method in an ATM exchange is provided, which analyzes the command and returns response data of a designated list to the central control unit according to one or more response statuses. According to this method, a plurality of lists can be designated by one command, and the corresponding response data can be received with at least one response status, so that the amount of communication between the central control unit and the common unit can be greatly reduced.

[0017]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the drawings. This embodiment is applied to the ATM exchange having the configuration shown in FIG.

FIG. 1 shows the basic format of a command issued from the CC to the common part. This command consists of a command header, a list, and a tail information part. The command header defines the content of the command. The list is a common part and / or individual part (hereinafter,
(Also collectively referred to as individual units collectively). The tail information section is added as an option when the data length of the command or the data length of the status exceeds a predetermined length to enable command / status communication.

The command header stores a command number, command length, application identifier APID, message code MSGCD, list number, and tail pointer. Of these, the application identifier APID and the message code MSGCD define what the command is requesting. The number of lists indicates the number of individual parts requested by the command.
The following list is provided for each individual part of the request target. The tail pointer is a word boundary and is designated by a byte. When it is "0", it means that there is no tail information part.

The list is composed of a list header and one or more instances, and is provided for each individual part requested by the command as described above. The list header is an individual unit device address that points to an individual unit corresponding to the list,
It consists of the list length, the number of instances contained in the list, and the instance length. The instance is made up of data describing its contents, and is prepared for each point or item to be monitored in the individual unit. For example, in the example of FIG. 1, there are first to nth instances.

The tail information section is composed of tail size, function information and other tail information, and detailed contents will be described later.

The common unit always collects and holds the monitor data of each individual unit housed in itself, or collects the monitor data from each individual unit as necessary. When the common unit receives a command from the CC, it analyzes the contents, knows what the command requires based on the command header, and further knows which individual unit the request requires based on the list header of the list. . Then, for the requested individual unit, the monitor result (response data) according to the instance contents described in the list is edited into a response status and returned to the CC.

The response status from the common part to the CC has the same structure, but in the response status, a status header is provided instead of the command header. The structure of this status header is similar to that of the command header. The list of response status contains the response data of each instance together with the list header. The structure of the list header is similar to that of the command list header. The response data of the instance is data as a response entity requested to be monitored (for example, billing result information for billing collection command).

As described above, the commands and statuses exchanged between the CC and the common unit combine a plurality of individual units to be requested and the instances in each individual unit into one format. The amount of communication in is greatly reduced.

FIG. 9 shows the format of the command and response status when the tail pointer = 0, that is, when the tail information section is not added. When the data length of the command and response status falls within the predetermined length, communication is performed in such a format without adding the tail information part. As shown in FIG. 9, in the request command from the CC to the common part, the tail pointer in the command header is set to “0”, and the lists 1, 2 ... To be done. Each list contains a list header and instances 1 to n of the number of instances (= n) written in the list header. Each instance contains the data of the read pointer.

On the other hand, the response status from the common part to the CC comprises a status header and a list. The tail pointer in the status header is set to "0". The list corresponds to the list of requested commands, and the response data of each instance corresponding to the command is stored therein. That is, the monitoring results of a plurality of individual parts requested by one command (command shown in FIG. 9) from the CC to the common part are transferred from the common part to the CC in the form of one status.
Will be returned to Therefore, the amount of communication between the CC and the common unit can be significantly reduced.

Next, the case of using the tail information section will be described in detail. Figure 3 shows the case of using the tail information section.
It is a figure which shows the simple communication sequence of the command / response status between CC and a common part. In the normal operation, the inquiry order and inquiry order response, and the ACK order and ACK order response in this sequence are transmitted / received by combining the command / response status with only the command header, tail information, and a single list. .

First, the outline of this sequence is as follows.
In FIG. 3, the CC issues an inquiry order as a command to the common unit, and the common unit returns an inquiry order response as a response status to the CC in response to the inquiry order. The inquiry order specifies the request content of the command and the amount of response data that can be received, and the inquiry order response is a reply to it. The common part follows the inquiry order response and then the autonomous status (# 1, #
2) is sent to CC. The autonomous status includes a list of response data of each individual unit. If one autonomous status is not enough, a plurality of autonomous statuses will be transmitted in succession.

When the CC receives the amount of response data designated by the inquiry order, the CC sends the ACK order to the common unit. This ACK order specifies the "normal" code and the amount of response data if further requesting the transfer of additional response data. When ending, specify the "end" code.
If an ACK order (normal) is sent to the common part, the common part responds by sending back an ACK order response, followed by an autonomous status (# 3, # 4) for transferring additional response data. ) Is sent. If this autonomous status is also insufficient, one or more will be transmitted in succession. When the CC has received all the necessary response data, it sends an ACK order (end) to the common part, and the common part returns an ACK order response to end the sequence.

The data format of each command / status having the tail information portion transmitted / received in the sequence of FIG. 3 will be described in detail below.

First, the inquiry order consists of a command header, a single list, and a tail information section in the format of FIG. 1. The tail pointer in the command header specifies the number of bytes in the tail information section, and the tail information section is the figure. Four
The format is as shown in. In FIG. 4, each item has the following meaning. The subscript h in all the following explanations
Represents a hexadecimal number, and the subscript b represents a binary number.

Function information: 0001 _h = instance ALL designation 0002 _h = instance multiple designation 0003 _h = list ALL designation 0004 _h = list multiple designation Event: 00100000 _b = ALL designation inquiry WS value: CC designation

Here, the "function information" is "0001 _h ".
When is, it means that the instance ALL is specified and response data is requested for all the instances.
“0002 _h ” indicates that multiple instances are designated and response data is requested for a part of all the instances. When “0003 _h ”, list ALL is designated and all the lists are designated. It indicates that response data is requested, and when “0004 _h ”, it indicates that a plurality of lists are designated and response data is requested for a part of all the lists. "Event"
Indicates an ALL designation inquiry when "00100000 _b ". "WS value" is the window size, CC
The CC itself specifies the amount of transfer data that can be accepted.

Next, the inquiry order response consists of a status header, a single list, and a tail information section. The tail pointer in the status header specifies the number of bytes in the tail information section, and the tail information section is shown in FIG. Format it. In FIG. 5, each item has the following meaning.

Function information: The value set in the inquiry order is set Event: 00110000 _b = inquiry response 00110001 _b = inquiry response (including data) Status number: data read side (0 to n side) WS value: common part Designation (CC designation WS ≥ common part designation WS) However, when the response status includes data, it is 0. Cause code: 00 _h = normal 01 _h = abnormal 02 _h = resend request 03 _h = resource busy transmission SHW number: Number of response SHWs when ALL is specified (1 for instance ALL) Total number of messages: Number of all messages notified by ALL specified response Common part sequence number: Transmission message number recognized by common part Number of messages: Transmission within individual part Number of messages Number of instances: Number of connection points in individual parts

Here, the value set in the inquiry order is set as it is as the "function information". The "event" is "00110000 _b " indicating that it is an inquiry response, and "00110001 _b " is the case where the inquiry response itself, which will be described later, includes response data. The "status number" is filled in on the data reading surface (0th to nth surface).
The “WS value” specifies the amount of data that the common unit can respond to, and is a value smaller than the WS value specified by the CC. However, it is 0 when the inquiry order response itself, which will be described later, includes response data. When the "cause code" is "00 _h ", it means that it is normal. When the "01 _h " is abnormal, it means "0".
“2 _h ” represents a resend request, and “03 _h ” represents resource busy. Inquiry order for "number of sent SHW" is A
It is the number of response SHWs when LL is specified. "Total number of messages"
Is the total number of messages notified by a response when the inquiry order specifies ALL. "Common part sequence number" is the transmission message number recognized by the common part, "number of messages"
Is the number of messages sent in the individual part, "the number of instances"
Is the number of connection points in the individual part. The "common sequence number", "message number", and "instance number" correspond to the contents of the list transferred as response data in the subsequent autonomous status.

Next, the autonomous status is composed of a status header, a list and a tail information part as shown in FIG. 1. The tail pointer in the status header specifies the number of bytes of the tail information part, and the tail information part is The format is shown in FIG. In FIG. 6, each item has the following meaning.

The function information: Event value set in the inquiry order is set: 01110000 _b = autonomous status Status Number: data read surface (0 to n surface) Common Sequence Number: transmission message ID individual unit sequence number: Submit Message number

Here, the value set in the inquiry order is set in the "function information". "Event" is "01
"110,000 _b " indicates that the status is autonomous.
The "status number" is filled in on the data reading surface (0th to nth surface). The "common part sequence number" is the transmission message number of the common part, and the "individual part sequence number" is the transmission message number of the individual part.

Next, the ACK order consists of a command header, a single list, and the tail information section. The tail pointer in the command header specifies the number of bytes in the tail information section, and the tail information section has the format shown in FIG. And In FIG. 7, each item has the following meaning.

Function information: The value set in the inquiry order is set Event: 01000000 _b = ACK normal 01000010 _b = ACK end 10000000 _b = forced termination Status number: The status number notified from the lower order in the immediately preceding sequence However, it is ignored during forced termination WS value: CC designation (WS value handled in the next sequence is specified) Common part sequence number: Next sequence number expected status response Individual part sequence number: Next status response Expected sequence number

Here, the value set in the inquiry order is set in the "function information". "Event" is "0
“1000000 _b ” indicates that the ACK is normal and notifies the normal reception of the requested response data, and further requests the transfer of the response data.
_b "represents that requests termination of the sequence and notifies the normal reception of the response data requested a ACK completion, not normally received the response data" 1000000 _b "has requested a kill Even if it represents a request to forcibly terminate this sequence. The "status number" echoes back the status number notified from the lower order in the immediately preceding sequence, but is ignored when the "event" is forcibly terminated. As for the “WS value”, the CC specifies the WS value handled in the next sequence when the “event” is normal. The "common part sequence number" is the sequence number of the common part for which a status response is expected next, and the "individual part sequence number" is the sequence number of the individual part for which a status response is expected next.

Next, the ACK order response consists of a status header, a single list, and a tail information part. The tail pointer in the status header specifies the number of bytes of the tail information part, and the tail information part is shown in FIG. Format it. In FIG. 8, each item has the following meaning.

Function information: The value set in the inquiry order is set Event: 01010000 _b = ACK normal response 01010010 _b = ACK end response 10010000 _b = Forced end response Status number: Data read side (0 to n side) WS Value: Common part specified (CC specified WS ≧ common part specified WS) Reason code: 00 _h = normal 01 _h = abnormal 03 _h = resource busy Number of notification messages: Number of messages to be notified within the specified WS Number of notification instances: specified Number of instances to be notified in the specified WS Common part sequence number: Sequence number to send status response next Individual part sequence number: Sequence number to send status response next

Here, the value set in the inquiry order is set in the "function information". "Event" is "0
“1010000 _b ” represents a normal response in which the requested response data can be transmitted, which is an ACK normal response.
"010 _b " indicates the end of ACK, and "1010000 _b "
Indicates forced termination. For the "status number", fill in the data reading surface. The "WS value" specifies the amount of response data that the common part can respond to, within a range that does not exceed the WS value specified by the CC. “Factor code” is “00 _h ”, normal, “01 _h ”
Is abnormal, and "03 _h " is resource busy. Enter the number of messages to be notified in the specified WS in "Notification message count", and specify the number of notification instances in the specified WS.
Enter the number of instances to be notified within. The "common part sequence number" is the sequence number of the common part which transmits the status response next, and the "individual part sequence number" is the sequence number of the individual part which transmits the status response next.

Next, each format of the inquiry order, inquiry order response, and autonomous status in each situation in which the list and the instance are variously specified is shown.

(1) Instance Number Designation (Status Number = 1) = No Tail Information FIG. 9 shows a communication format in the case of instance number designation. This communication format is used when there is no tail information section. It is applied, for example, in the case of path setting, NDC reading by a maintenance person command, billing collection (fixed length), and the like.

In this case, it consists of only one request command and one response status. In order to realize request control for multiple instances with one command, the number of instances = n is specified in the list header, and multiple instances 1 to n are set side by side in the command. The maximum number of designated instances is set so that the message length of the response status can accommodate all response data of all instances 1 to n within one status. If there are multiple lists, set them side by side in one command.
Even in that case, the number of list specifications is adjusted so that the message length of the response status can accommodate all response data within one status.

(2) Instance ALL designation (number of statuses ≧ 1) = tail information exists FIG. 10 shows a communication format in the case of instance ALL designation. This format is, for example, PM reading, NDC regular collection, statistical data, billing collection (fixed length)
Used in cases such as.

Since the inquiry order realizes the request control for all the instances with one command, the function information in the tail information section is set to 0001 _h (instance ALL specified), the event is set to ALL specified inquiry, and WS is set.
For the value, specify the window size that can accept data on the CC side. The maximum number of data collections per time is within this window size WS value managed by software. The list consists only of the list header and the first instance,
Set the ALL target instance to the first instance.

In the inquiry order response, the amount of data that can be responded by the tail information is designated by the common value by the WS value, and the number of response instances is entered in the list. In the autonomous status following the inquiry order response, response data as response entities of all the instances (1 to n) are written in the list. The number of this autonomous status is managed by tail information.

(3) Multiple Instance Designation (Number of Statuses ≧ 1) = Tail Information Present FIGS. 11 and 12 show communication formats when multiple instances are designated. This format is applied to, for example, protocol error log, frame trace, ALL general command, and the like. In this case, control information such as multiple instances and WS values is specified in the tail information part of the inquiry order, and the number of instances is specified in the list header. The maximum specified number of instances is the number of instances that can be specified by one command. ALL cannot be specified in the list instance.

FIG. 11 shows one command (inquiry order).
In this case, only one instance is specified, but the message length of the response status (autonomous status) is variable, and all response data cannot be accommodated within one status. The function information in the tail information section of the inquiry order is 0002 _h (instance plural designation), the list header includes the number of instances = 1, and the instance 1 includes the read pointer information. The number of autonomous statuses is managed by the tail information. In the example of FIG. 11, since the response data amount of the instance 1 is large, it is divided into two autonomous statuses # 1 and # 2.
Sends the first half of the response data of the instance 1 to the CC and the second half of the response data of the instance 1 with the autonomous status # 2.

FIG. 12 shows one command (inquiry order).
In this case, a plurality of instances are specified, the message length of the response status (autonomous status) is variable, and all response data cannot be accommodated within one status. Function information in the tail information of the inquiry order is set to 0002 _h (multiple instances specified), the number of instances in the list header to list = n, respectively instance 1~n include the read pointer information.
The number of autonomous statuses is managed by the tail information, and in the example of FIG. 12, since the response data amount of all the instances 1 to n is large, it is divided into two autonomous statuses # 1 and # 2, and the number of instances in the autonomous status # 1 = The response data of the instances 1 to x is represented as x, and the instance x is represented as the number of instances = y (where x + y = n) in the autonomous status # 2.
The response data of +1 to n is transmitted to CC.

(4) List number specification (number of status =
1) = No tail information This communication format (not shown) does not include a tail information part, and is applied, for example, when setting a plurality of paths, reading a plurality of pieces of fault information, and collecting charges (variable length).

In order to realize the control of requests to a plurality of individual parts with one command, the number of lists is specified in the command header, and a plurality of lists are arranged and set in the command. The maximum number specified in the list is set so that the message length of the response status can be accommodated within one status in consideration of the instances in the list.

(5) List ALL designation (number of statuses ≧
1) = With tail information FIG. 13 shows a communication format when the list ALL is specified. This format is, for example, initial setting of all interface device units, billing collection all-PVC, and SV after restart.
It is applied to C etc.

In order to control the request for all lists with one command (inquiry order), the function information of the tail information is set to 0003 _h (list ALL specified), and WS is set.
Specify the value. Further, the list of all targets is set in the list of the first list with the number of lists of command header = 1. The maximum number of data collections performed once is within the window size WS value managed by software. The autonomous status is composed of a plurality of items. In the autonomous status # 1, the number of status header lists = x, and the response data is entered in each of the lists 1 to x. In the autonomous status # 2, the number of status header lists = y ( However, as x + y = n), the response data is entered in each of the lists x + 1 to n.

(6) Multiple list designation (number of statuses ≧
1) = Tail information exists Even if one list is specified with one command (inquiry order), the message length of the response status is variable, and if the status cannot be accommodated within one status, one command The information instance specifies multiple lists and control information such as WS. The number of lists is specified in the list header. Specify the list length in the command header. The maximum number of lists that can be specified is the number of lists that can be specified with one command. ALL cannot be specified in the list / instance. Commands are limited to those that terminate at least the common part.

Next, some specific examples of communication sequences between the CC (ATM switch) and the common unit (concentrator) will be described with reference to FIGS. 14 to 20.

FIG. 14 shows a concrete example of the communication sequence of the start declaration in the multi-instance response communication. The inquiry order is set as “function information = ALL designation or plural designation command number = xxxx sequence number = 00-00 WS value = a”.

For this inquiry order, if the number of instances that can be returned by the common part is n and the total number of messages is m, the inquiry order response is "command number = xxxx instance number = n total message number = m WS value = a '. (However, a ≧ a ′) Status number = yyy ”is set.

FIG. 15 is a diagram showing a specific example of a communication sequence when data is set in the inquiry order response itself. The inquiry order sets “function information = ALL designation or plural designation command number = xxxx sequence number = 00-00 WS value = a”.

With respect to this inquiry order, if the common part has the number of instances n that can be returned and the total number of messages m, and these response data can be contained in one response status, the inquiry order response will be , The response data is included in the list, and “command number = xxxx instance number = n total message number = m WS value = a ′ (where a ≧ a ′) status number = yyy” is set.

Further, in response to the inquiry order response, the CC shall return an ACK order for terminating the communication sequence, and the ACK order shall be "event = end command number = xxxx sequence number = Don't care (ignore ) WS value = Don't care (ignore) Status number = yyy "is set.

The common part is the AC for this ACK order.
Set "event = end command number = xxx WS value = Don't care (ignore) status number = yyy" in the K order response. This ends the communication sequence.

FIG. 16 shows a specific example of a communication sequence when WS value control is performed in multiple-instance response communication. The inquiry order sets “command number = xxxx sequence number = 00-00 WS value = 4”.

For this inquiry order, the number of instances n that can be returned by the common part and the total number of messages are 4, and these are the capacity that can be transmitted with the WS value = 2. Therefore, the inquiry order response is “command number = xxxx Status number = yyy Sequence number 00-00 WS value = 2 Instance number = n Total message number = 4 ”

There are two autonomous statuses to be transmitted following this inquiry order response, and each autonomous status puts response data in the list. Then, the first autonomous status # 1 is set as "command number = xxxx status number = yyy sequence number 00-00", and the second autonomous status # 2 is "command number = xxxx status number = yyy sequence number 01." -00 "is set.

In response to this autonomous status, the CC still has a receivable memory capacity of WS value = 2 minutes, and therefore requests the transfer of response data in the ACK order. The ACK order in this case sets “event = normal command number = xxxx status number = yyy sequence number = 02-00 WS value = 2”.

Since the common part has been able to collect further transferable response data (for the memory capacity of WS value = 2) for this ACK order, this can be CCed in the ACK order response.
Notify and transfer the response data. In the ACK order response in this case, "event = normal response command number = xxxx status number = yyy sequence number = 02-00 WS value = 2" is set.

There are two autonomous statuses following this, and each autonomous status puts response data in the list. The third autonomous status # 3 counted from the beginning is set as "command number = xxxx status number = yyy sequence number 02-00", and the fourth autonomous status # 4 is "command number = xxxx status number. = Yyy sequence number 03-00 ”.

For the autonomous statuses # 3 and # 4,
The CC shall return an ACK order that ends the communication sequence, and the ACK order (end) shall be "event = end command number = xxx status number = yyy sequence number = Don't care (ignore) WS value = Don '"t care (ignore)" is set.

The common part uses the AC for this ACK order.
In the K order response (end response), set “event = end response command number = xxxx status number = yyy sequence number = Don't care (ignore) WS value = Don't care (ignore)”. This ends the communication sequence.

FIG. 17 shows a specific example of a communication sequence of forced termination processing in multiple instance response communication. When the CC wants to perform forced termination during communication, it issues an ACK order for forced termination. This ACK order (forced termination) sets "event = forced termination command number = xxxx status number = yyy sequence number = Don't care (ignore) WS value = Don't care (ignore)".

The common part uses the AC for this ACK order.
Set "Event = forced termination response command number = xxxx status number = yyy sequence number = Don't care (ignore) WS value = Don't care (ignore)" in the K order response (forced termination response). This forces the communication sequence to end.

In FIG. 18, since the inquiry order response (including response data) from the common part did not reach the CC, the CC
The specific example of the communication sequence when the inquiry order retransmitted from is rejected by the common part is shown. FIG.
In 8, the common part returns an inquiry order response including response data to the first inquiry order from the CC, but it is assumed that this inquiry order response has not been received by the CC. The CC issues the inquiry order again to the common unit when the inquiry order response is not received even after the lapse of a predetermined time. Although this inquiry order is received by the common part, the common part recognizes that there is some abnormality in the communication between the CC and the common part because the inquiry order has the same content, and the NG data (abnormality exists) in the inquiry order response. (Data to notify) is sent back to the CC.

FIG. 19 shows another specific example of the communication sequence for retransmitting the inquiry order. In FIG. 19, for the first inquiry order from the CC, the common unit returns an inquiry order response carrying response data, but it is assumed that this inquiry order response has not been received by the CC. The CC notifies the common unit of the forced termination by the ACK order when the inquiry order response is not received even after the lapse of a predetermined time. The common unit returns an ACK response (forced termination response) in response to this ACK order (forced termination), and once forces the communication between the CC and the common unit. After that, the CC again issues an inquiry order having the same content, and the common unit returns an inquiry order response (including response data) in response to the inquiry order.

FIG. 20 shows a specific example of a communication sequence in the case where the autonomous status is not normally received by the CC in the multiple instance response communication and the CC is resent. The inquiry order sets "sequence number = 00-00 WS value = 4".

For this inquiry order, the number of instances that can be returned by the common part is n and the total number of messages is 8. Since these are the transmission capacity with the WS value = 4, the inquiry order response is "sequence number 00- 00 WS value = 4 number of instances = n total number of messages = 8 ”.

There are four autonomous statuses to be transmitted subsequent to this inquiry order response, and the autonomous status of each is "sequence number 00-00""sequence number 01-00""sequence number 02-00""sequence number 03". -00 "is set.

However, of these, the sequence number 01-
The autonomous status of 00, 02-00, 03-00 is CC
It is assumed that it was not successfully received. Since the CC has not received all the requested response data, 01-00 is set as the sequence number for which the next status response is expected by the ACK order (normal), and the retransmission is requested.
In this case, the ACK order (normal) sets "sequence number = 01-00 WS value = 4".

The common part returns A to this ACK order.
In the CK order response, "sequence number = 01-00 WS value = 2" is set and transmitted, and subsequently, the autonomous status of "sequence number 01-00" and "sequence number 02-00" is transmitted.

Since the CC has not yet received all the response data, it again requests the retransmission of the response data of sequence number 03-00 or later in the ACK order (normal). In the same manner, the resend request and the response data are transferred, the ACK order (end) is finally issued from the CC, and the common part responds with the ACK order response (end response) accordingly, and the communication sequence ends. .

[0085]

As described above, according to the present invention,
Even if you want to collect multiple points of data for the same item, or if you want to perform the same control for multiple interface devices, you can send multiple status responses with a single command Can be prevented from enlarging.

[Brief description of drawings]

FIG. 1 is a diagram showing a structure (format) of a multi-response communication message.

FIG. 2 is a diagram showing a configuration of an ATM exchange.

FIG. 3 is a diagram showing an outline of a sequence using a tail information section.

FIG. 4 is a diagram showing a configuration of a tail information part of an inquiry order (CC → common part).

FIG. 5 is a diagram showing a configuration of a tail information part of an inquiry response order (common part → CC).

FIG. 6 is a diagram showing a configuration of a tail information part of an autonomous status (common part → CC).

FIG. 7 is a diagram showing a configuration of a tail information part of an ACK order (CC → common part).

FIG. 8 is a diagram showing a configuration of a tail information part of an ACK order response (common part → CC).

FIG. 9 is a diagram showing a communication format when the number of instances is designated.

FIG. 10 is a diagram showing a communication format when an instance ALL is specified.

FIG. 11 is a diagram showing a communication format in the case of multiple instance designation (part 1).

FIG. 12 is a diagram showing a communication format in the case of multiple instance designation (part 2).

FIG. 13 is a diagram showing a communication format when list ALL is specified.

FIG. 14 is a diagram showing a start declaration of a multi-instance response communication sequence.

FIG. 15 is a diagram showing a case where data is set in an inquiry order response.

FIG. 16: WS of Instance Multiple Response Communication Sequence
It is a figure which shows control.

FIG. 17 is a diagram showing forced termination processing of a multiple instance response communication sequence.

FIG. 18 is a diagram showing an example of a sequence rejected by resending an inquiry order.

FIG. 19 is a diagram showing an example of an inquiry order retransmission sequence.

FIG. 20 is a diagram showing retransmission control of a multiple-instance response communication sequence.

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Hiroyuki Sasai, Hiroyuki Sasai, 3-9-18 Shin-Yokohama, Kohoku-ku, Yokohama-shi, Kanagawa Prefecture Fujitsu Communication Systems Ltd. (72) Miho Tsuchiya Shin-Yokohama, Kohoku-ku, Yokohama-shi, Kanagawa Prefecture 3-9-18 Fujitsu Communication Systems Limited

Claims (6)

[Claims] 1. A multi-response communication control method for transmitting and receiving a command / response status for collecting response data of an individual section under the common section between a central control section and a common section in an ATM exchange, the central control section Specifies the individual part that is the response target in the command to be sent to the common part, and
Multiple response communication control in the ATM switch in which one or more instances as items are set, and the common unit analyzes the command and returns the response data of the instance set in the command to the central control unit according to the response status. Method. 2. A multi-response communication control method for transmitting and receiving a command / response status for collecting response data of an individual section under the common section between a central control section and a common section in an ATM exchange, the central control section The tail information part is set in the command transmitted from the common part to the common part, and the instance information is set in the tail information part to instruct the response for all the instances that are the response points / items in the individual part. Is a multi-response communication control method in an ATM switch, which analyzes the command and returns the response data of all the instances to the central control unit according to one or more response statuses. 3. A multi-response communication control method for transmitting / receiving a command / response status for collecting response data of an individual section under the common section between the central control section and the common section in an ATM exchange, the central control section Sets the tail information part in the command to be sent to the common part and
A plurality of instance designations that instruct a response for a part of the instance that is the item is set, and the common unit analyzes the command and returns the response data of the designated instance to the central control unit with one or more response statuses. Multiple response communication control method in ATM switch. 4. A multi-response communication control method for transmitting and receiving a command / response status for collecting response data of an individual section under the common section between a central control section and a common section in an ATM switch, the central control section Sets to the command to be sent to the common part one or more lists that specify individual parts to be responded among the individual parts under the common part, and the common part analyzes the command and sets it to the command. A multi-response communication control method in an ATM exchange, wherein response data of a list is returned to the central control unit according to a response status. 5. A multi-response communication control method for transmitting / receiving a command / response status for collecting response data of an individual section under the common section between the central control section and the common section in an ATM exchange, the central control section Sets the tail information part in the command to be transmitted to the common part, and sets the list / all designation instructing the response to all the individual parts under the common part in the tail information part. A multi-response communication control method in an ATM exchange, wherein the response data of all lists designated by analysis are returned to the central control unit according to one or more response statuses. 6. A multi-response communication control method for transmitting and receiving a command / response status for collecting response data of an individual section under the common section between a central control section and a common section in an ATM exchange, the central control section Sets the tail information part in the command to be sent to the common part, and sets a plurality of list designations instructing a response for a part of the individual parts under the common part in the tail information part, and the common part sets the command A multi-response communication control method in an ATM exchange, wherein response data of a list designated by analysis is returned to the central control unit according to one or more response statuses.