US 6,333,932 B1Grant

Connectionless communications system, its test method, and intra-station control system

Issue Date:2001-12-25

•13 Claims

•913 Drawing Sheets

Abstract

The quality and performance of the connectionless communications system are improved. When a BOM is received, the destination address DA of the L3-PDU stored in the payload of the BOM is retrieved, and the tag information is obtained from the DA (S11). The output message identifier MID is reserved (S12), and the tag information and output MID are assigned to the BOM (S13). Then, the tag information and output MID are written to the table. When a COM is received, the tag information and output MID are retrieved using the MID of the COM as a key, and the information is provided for the COM (S31and S32). When an EOM is received, the tag information and output MID are retrieved using the MID of the EOM as a key, and the information is provided for the EOM (S41and S42). Then, the output MID is released (S43).

Metadata

Assignee

Fujitsu Limited

Inventors

Yasusi Kobayasi
Yoshihiro Watanabe
Hiroshi Nishida
Masami Murayama
Naoyuki Izawa
Yasuhiro Aso
Yoshihiro Uchida
Hiromi Yamanaka
Jin Abe
Yoshihisa Tsuruta
Yoshiharu Kato
Satoshi Kakuma
Shiro Uriu
Noriko Samejima
Eiji Ishioka
Shigeru Sekine
Yoshiyuki Karakawa
Atsushi Kagawa
Mikio Nakayama
Miyuki Kawataka
Satoshi Esaka
Nobuyuki Tsutsui
Fumio Hirase
Atsuko Suzuki
Shouji Kohira
Kenichi Okabe
Takashi Hatano
Yasuhiro Nishikawa
Jun Itoh
Shinichi Araya

Application Information

Application Number:US 08/518,110

Filing Date:1995-08-21

Priority Date:1995-08-21

Art Unit:7

Classifications

IPC:

H04Q 1104

Field of Search:

370228370242370248370249370260370360370383370389370390370395370422370432370467370498370503370471370253370392370230370417370468370377370396370229370252379114

Patent Drawings (913 sheets)

Description

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] The present invention relates to a connectionless communications system for transmitting data at a high speed, to a method of testing the system, and to an intra-station control system of a switching station for transmitting data at a high speed.

[0004] 2. Description of the Related Art

[0005] Recently, high-performance information processing devices such as work stations, personal computers, etc. have been developed to perform a distribution process in which a number of information processing devices are interconnected through a high speed local area network (LAN). The network connecting such LANs should also be provided with high speed processing capabilities.

[0006] One of the services to realize the above described high speed data communications is a switched multi-megabit data service (SMDS). The SMDS is a connectionless data switching service based on the transfer speed of 1.5 Mbps and 45 Mbps.

[0007] An asynchronous transfer mode (ATM) system is well known as a method of realizing a broadband ISDN, and the SMDS can be provided through an ATM network. In this case, an SMDS processing server (SMDS message handler) is supplied for a predetermined ATM switch, and a permanent virtual circuit or a permanent virtual channel (PVC) connects an SMDS subscriber with the SMDS processing server accommodating the SMDS subscriber. The connectionless data output from the SMDS subscriber is transferred to the SMDS processing server to perform a routing process, etc. at the server.

[0008] The connectionless data normally refers to a variable packet (data frame). However, since the above described PVC is a path to be established in a network, the connectionless data is transferred after being converted (decomposed) into an ATM cell format before it is input to the ATM switch. The cell is a 53-byte structure consisting of a 48-byte payload and a 5-byte header.

[0009] The ATM cell format data is temporarily structured as the layer-3 protocol data unit (L3-PDU) or in a data format of a higher-level layer in the SMDS processing server as shown in FIG. 897 to analyze routing information, etc. according to a destination address DA, a source address SA, etc. stored in the L3-PDU. Then, the data is decomposed again into cells to route the data according to the analyzed information.

[0010] As described above, the conventional SMDS is limited in its speed because input cells are structured in a higher level layer data format (for example, in L3-PDUs) when the SMDS processing server performs a routing process through software of a microcomputer program, etc. Additionally, such processes as a data copying process performed when a group address is specified as a destination address DA, a traffic smoothing process, an action against no reception of an end-of-message cell (EOM: a cell storing the last portion of data when an L3-PDU is decomposed into a plurality of cells) have been processed through software by microcomputers, etc.

[0011] Thus, the conventional SMDS has been limited in its process speed because the processes in the SMDS processing server are performed through various software. Therefore, when connectionless communications data is transmitted using an SMDS, the operations of the transmission line and switch are sped up with the SMDS processing server processes interfering as a bottleneck, thereby preventing an actual high-speed process from being successfully realized. Furthermore, when the above described structuring process in the SMDS processing server, all cells forming each L3-PDU should be temporarily stored. Therefore, the necessary buffer capacity undesirably becomes very large.

[0012] In the SMDS, protocol performance is monitored when a service is offered as follows. That is, the formats of various parameters are checked in the data, and counted is the data which has been rejected by the check (the data which cannot be recognized as valid). A predetermined specific type of check is followed by a counting process performed on the rejected data based on a predetermined algorithm. If the resultant value exceeds a predetermined threshold, then output is a threshold crossing alert (TCA) indicating that the threshold is exceeded. Furthermore, an error log is collected each time data is rejected.

[0013] The following parameters are collected in the error log.

[0014] (1) Destination address DA

[0015] (2) Source address SA

[0016] (3) SNI number (subscriber network interface No.)

[0017] (4) Error type

[0018] In the PVC between the user (subscriber) and the SMDS processing server,

[0019] In the PVC between the user (subscriber) and an SMDS processing server, data is transferred in the cell format as described above (actually, the data is transmitted in the ATM cell format and processed in the L2-PDU in the SMDS processing server. The ATM cell and L2-PDU are based on the 53-byte configuration and simply referred to as cells. However, since the above described error log collection is mostly related to the layer 3, the data is received in the cell format and then reassembled into the L3-PDU in the SMDS processing server.

[0020] As described above, input cells are reassembled in the data format of the higher order layer (for example, L3-PDU) in the conventional SMDS. This prevents the processes from being performed at a high speed in the SMDS.

[0021] The above described services are based on the high reliability of the physical quality of the transmission lines forming the network. Therefore, it is important to test and evaluate the transmission quality of the network.

[0022] The test and evaluation of the transmission lines are activated from the OS center (operation center for managing the network) in the connectionless communications service network, and an inter-station loopback test is conducted to confirm the normality of any inter-station link (path between switches). The inter-station loopback test is described below by referring to FIG. 898. In this embodiment, the test is conducted to check the link between SW station 3 and SW station 6.

[0023] The test is started by issuing a test connectionless packet transmission request message (test start request) from the OS center 1 to SW station 3. The request message contains an identification information ID indicating terminal SW station 6. SW station 3 generates a test packet with the identification address of terminal SW station 6 set as its destination address DA and the identification address of its home station (SW station 3) set as its source address SA. The test packet is output to terminal SW station 6. In SW stations 4 and 5, test packets are processed as normal packets and transferred to terminal SW station 6. On receipt of the test packet, terminal SW station 6 outputs the packet with its DA and SA inverted. That is, the packet is returned from terminal SW station 6 to SW station 3, and it is reported to the OS center 1 upon re-arrival of the packet at the source SW station 3.

[0024] Thus, the OS center 1 checks whether or not the packet is normally transmitted in the network, that is, checks the normality of the transmission line (the link between SW station 3 and terminal SW station 6 in this embodiment). In the procedure, since the source SW station 3 and the terminal SW station 6 mark the time stamp onto the payload field of the packet, the OS center 1 is informed of the transmission time of packets according to the information.

[0025] However, in the above described test method, the information obtained by the test is to be provided for the OS center (operation center), and no method has been provided for the subscriber (terminal unit 2 in FIG. 898) to be autonomously informed of the transmission quality in the network (transmission delay time, etc.). Therefore, if a packet is not normally transmitted from a source subscriber to a destination subscriber, the subscribers cannot detect in which the factor of the fault resides, the subscriber terminal unit or the network transmission line. Thus, the OS center is invoked to recover from the fault, thereby requiring much time and cost.

[0026] FIG. 899 shows an embodiment of the SMDS. In FIG. 899, the SMDS support module analyzes a destination address DA and makes various checks. An SMDS support module S accommodates a plurality of source SMDS subscribers (a) and (b) to analyze a DA and make various checks. The SMDS support module R accommodates a plurality of destination SMDS subscribers (x) and (y) to make various checks. The modules comprising these S and R correspond to the above described SMDS processing server (SMDS message handler).

[0027] Each of the source SMDS subscribers (a) and (b) is connected to the SMDS support module S through the PVCs 1 and 2. The SMDS support module S is connected to the SMDS support module R through the PVC 3. The SMDS support module R is connected to each of the destination SMDS subscribers (x) and (y) through the PVC 4 and 5.

[0028] If the SW shown in FIG. 899 comprises an ATM switch, the connectionless data (SMDS message) output from the source SMDS subscribers (a) and (b) is converted into the cell format in the interface not shown in FIG. 899. The cell is transferred to the SMDS support module S by assigning to the header of the cell a specific VPI/VCI specifying the SMDS support module (VPI/VCI specifying the PVC 1 and 2) as its destination. In the transfer between the SMDS support modules S and R, the VPI/VCI value indicating the PVC 3 is assigned and output. The cell transferred from the SMDS support module R to the destination SMDS subscribers (x) and (y) with a specific VPI/VCI value indicating the PVCs 4 and 5 is output from the SMDS support module R, and arrives at the destination SMDS subscribers (x) and (y). Each of the PVCs is established at the system initialization.

[0029] Since the numbers of the source and destination SMDS subscribers accommodated in the SMDS support modules S and R are limited, a plurality of SMDS support modules are provided if a single SW station accommodates SMDS subscribers in excess of the maximum number. FIG. 900 shows an example of this. In this case, each connection is made by the PVC. FIG. 900 shows an example that SMDS subscribers (a), (b), (x), and (y) are accommodated in the SMDS support module 1 and SMDS subscribers (c), (d), (v), and (w) are accommodated in the SMDS support module 2. The PVC also connects SMDS support module 1 to SMDS support module 2.

[0030] As described above, the data transfer path is set at the system initialization in the SMDS. If the source SMDS subscribers (a) and (b) output SMDS messages, the messages are led to the SMDS support module S through the PVCs 1 and 2, and transferred to the destination SMDS subscribers (x) and (y) through the PVCs 3, 4, and 5. Therefore, it cannot be verified that the SMDS messages output from the source SMDS subscribers (a) and (b) have arrived at the destination SMDS subscribers (x) and (y) through the PVCs.

[0031] If the data cannot be successfully transferred, a complaint is expected from the source SMDS subscribers (a) and (b) or destination SMDS subscribers (x) and (y). The subscriber's complaint should be appropriately verified at the lowest possible cost.

[0032] The PVC test and the transmission time test are described above, and the SMDS needs confirming the normality of the transmitted SMDS data. The method of confirming the normality of data includes checking the BS-size of the L3-PDU, length of the L2-PDU, etc.

[0033] In the BA-size check, it is confirmed whether or not the value for use in checking the payload length of the L3-PDU (CPCS-PDU) is correct. In the BE-tag (beginning tag and end tag) check, the normality of the L3-PDU data can be confirmed by verifying the matching between the leading and trailing tags of the L3-PDU. In the length check, it is confirmed that the assembling and disassembling between the L3-PDU and L2-PDU are normally performed by verifying the relationship between the valid payload length value of the L2-PDU and the BA-size of the L3-PDU.

[0034] When the normality of the L3-PDU is confirmed in the disassembled L2-PDUs, the scale of the circuit becomes undesirably large. Since the BA-size and BE-tag of the L3-PDU and the length of the L2-PDU are checked as being closely related to one another, it is difficult to perform a process for each cell (for each L2-PDU). If the data in the format of the cell input to the SMDS processing server (L2-PDU) is processed after being assembled into the L3-PDU, a high-speed process is prohibited by the software process involved as described above.

[0035] When the connectionless communications service is realized in the ATM switch network, a connectionless data processing server (SMDS processing server in the SMDS) is provided to request the server to check the routing process on the connectionless data output from the subscriber terminal unit and to make various checks. FIG. 901 shows an example of the method of realizing such connectionless communications services. The configuration shown in FIG. 901 is the same as that shown in FIG. 899. That is, a PVC 11 is set between the source SMDS subscriber (a) and the connectionless data processing server CLS 2. A PVC 13 is set between the destination SMDS subscriber (x) and the connectionless data processing server CLS 6. These PVCs are set using a call processor CPRs 3 and 7.

[0036] In the configuration shown in FIG. 901, the connectionless data processing server CLS 2 accommodating the source subscriber (a) and the connectionless data processing server CLS 6 accommodating the destination subscriber (x) are provided in different switch stations. That is, the connectionless data processing server CLS 2 is provided in the SW station 1, while the connectionless data processing server CLS 6 is provided in the SW station 5. These connectionless data processing servers CLS 2 and 6 are connected to each other by the PVC 12. A large-scale relay switch 4, in which the PVC 12 is provided, has the configuration of relaying switches such as SW 1 or SW 5, or is an ATM interconnection switch (AISW).

[0037] When connectionless data is transferred from the source SMDS subscriber (a) to the destination SMDS subscribes (x) with the above described configuration, the data output from the source SMDS subscriber (a) is input to the connectionless data processing server CLS 2 through the PVC 11, and then transferred to the connectionless data processing server CLS 6 through the PVC 12. Then, it is transferred to the destination SMDS subscriber (x) from the connectionless data processing server CLS 6 through the PVC 13. The data is transferred through the PVCs in cell units and routed by the connectionless data processing servers CLS 2 and 6.

[0038] In the conventional connectionless communications service, the connectionless data processing server CLS 2 accommodating the source SMDS subscriber (a) is connected to the connectionless data processing server CLS 6 accommodating the destination SMDS subscriber (x) through the PVC 12 as shown in FIG. 901 if these servers are different from each other. The PVC 12 is set such that it passes through the SWs 1 and 5, and the large-scale relay switch 4. Therefore, the band resource for connectionless services should be preliminarily reserved in the switches to manage the services.

[0039] In the conventional systems, the band resource for each switch is used even when the connectionless service data is not being transmitted, and the band resource management is complicated.

[0040] By contrast, the switches for switching cells such as a B-ISDN (broadband ISDN) switch for providing broadband services, for example, ATM (asynchronous transfer mode) services, an SMDS switch for providing SMDS (switched megabit data service) services, etc. require considerably high performances and functions as compared with the conventional telephone switches or N-IDSN (narrowband ISDN) switches. Therefore, these switches require unique technology for intra-station control.

[0041] The prior art technology and the problems are clearly described below.

[0042] Described below is the problems related to the intra-station control communications technology for communicating the control information between the intra-station devices such as various transmission line interface device (trunk), etc. and the switch processor.

[0043] In controlling the intra-station devices in the conventional switching system, each of the intra-station devices 6 and 7 for operating with an ATM switch 5 is connected through an input control device 4 to a system bus 3 to which a switch processor (CC)1 is connected as shown in FIG. 902 to transfer the control information between the intra-station device and a main storage memory (MM) 2 connected to the CC 1 by the direct memory access (DMA) system.

[0044] In this system, however, all the intra-station devices 6 and 7 should be connected to the system bus 3, and the cable should be mounted to connect the intra-station devices 6 and 7 to the system bus 3.

[0045] Thus, the farther the intra-station devices 6 and 7 are located from the system bus 3, the longer the cable should be, thereby causing the problem of complicated connection.

[0046] Connecting all the intra-station devices 6 and 7 to the system bus 3 causes a conflict for the acquisition of an access right required to access the bus, thereby resulting in the congestion of bus access.

[0047] Furthermore, extending the system bus 3 to each of the intra-station devices 6 and 7 lowers the transmission quality, and may generate a transmission error such as a data error and parity error in the DMA procedure which includes no error control procedure.

[0048] Described next is the problem related to the technology for communicating control information such as call setting information, etc. between a terminal unit and a control device such as a switch processor.

[0049] Controlling a terminal interface device in the ATM switch system, etc. requires communicating control information with a control system device such as a switch processor, etc.

[0050] The conventional technology to communicate control information can be the system in which a physical interface is connected to a terminal unit (TERM) 4 connected from the control system device (MPR1 and PRIF2) to the switch (SW) 3 as shown in FIG. 903 as in the case shown in FIG. 902.

[0051] Since a physical interface is required for each terminal 4 in this system, the entire system configuration is complicated and the problem occurs that the terminal units 4 cannot easily added.

[0052] Described below is the subject related to the technology of testing a switch as an intra-station control system.

[0053] In the ATM switch, etc, a test is conducted whether or not a cell transmission highway is faulty by connecting to a highway a test device for sending cells and retrieving and collecting received cells.

[0054] In this case, a test cell is transmitted after setting the destination information VPI (virtual path identifier), VCI (virtual channel identifier), cell loopback in the test device, and other LSIs through the test device.

[0055] However, such a system requires a complicated configuration of a test device, and takes time in setting a test device.

[0056] Described below is the loopback test in the technology of testing switches.

[0057] With an increasing use of ATM switches and ATM switch network in which the information of different traffic characteristics such as voice, data, animation, etc. can be combined and switched, a test of confirming the normality of an inter-station path has been required. If a fault occurs between the two stations having a lot of stations existing between the two stations in an actual operation, it is required that faults should be detected and corrected at the earliest possible stage. The loopback test method of an ATM switch network is an effective test method for quickly detecting a fault between the stations.

[0058] The ATM switch has just been introduced in the market, and the ATM switch has never been tested between stations. However, the following test method is considered to be an effective inter-station ATM switch network test method based on the conventional electronic switch test method.

[0059] According to this method, if a number of stations exist in the ATM switch network, a test device should be provided for each test device.

[0060] If there are not sufficient test devices, a test device should be shared among stations for the test.

[0061] Furthermore, some stations are not constantly attended by operators and the operators should go to the stations to conduct the test.

[0062] Thus, in the above described method, operators are required to go to trouble in conducting an inter-station test.

[0063] Described next is the subject related to the technology of measuring the performance in a switch according to the intre-station control system.

[0064] The self routing module (SRM) switching method using the ATM is the condition for structuring a broadband ISDN system. However, measuring the performance in the SRM has been a difficult task.

[0065] Finally, the subject related to the control of a trailer in the PLCP, which is a physical layer conversion protocol interfaced in the DS3 format, that is, the digital signal level 3 format, is described below as one of the intra-station control system.

[0066] In the B-ISDN or SMDS service, the DS3 (digital signal level 3) format is used to realize the service of 44.736 MHz.

[0067] FIGS. 904 and 905 show examples of system configurations according to the present invention.

[0068] FIG. 904 shows the configuration in which the BISDN terminal unit is connected to the BISDN switch.

[0069] FIG. 905 shows the configuration in which the SMDS terminal unit is connected to the SMDS switch. The present invention is related to the transmitting units in the BISDN terminal unit and BISDN switch or the SMDS terminal unit and SMDS switch.

[0070] FIG. 906 shows the configuration of the DS 3 multi-frames. The DS 3 frame comprises 85-bit basic frames. The basic frame comprises a 1-bit DS 3 header and an 84-bit DS3 payload. Eight basic frames form a subframe, and seven subframes form a single multi-frame. That is, one multi-frame consists of 56 (8×7) basic frames.

[0071] The ATM cell of the BISDN is a 53-octet cell, and the L2-PDU (level 2 protocol data unit cell) of the SMDS is a 53-byte cell. That is, they are similar in basic configuration, but different in contents of the header and payload and in value of the HEC and HCS.

[0072] FIGS. 907(a) and (b) show the configurations of the ATM cell and L2-PDU cell.

[0073] An ATM cell or L2-PDU cell are not directly stored in the payload of the DS3 reference frame, and transmitted through the frame of the PLCP (physical layer convergence protocol).

[0074] FIG. 908 shows the configuration of the PLCP multiframe interfaced in the DS3 format.

[0075] Each of the ATM cell or L2-PDU cell is stored in a 53-octet PLCP payload in the PLCP frame. The PLCP multiframe is divided into 84-bit segments, and each segment is stored in an 84-octet DS3 payload in the DS3 frame and then transmitted.

[0076] The PLCP frame is a multiframe comprising 12 pairs of a 4-byte PLCP header and 53-byte PLCP payload and a trailer. The PLCP header comprises A1 and A2 bytes, POHI, and POH. The trailer length is 13 or nibbles. A nibble is 4 bits and refers to a half byte. The trailer data is 13 or 14 4-bit patterns “1100”.

[0077] One PLCP multiframe is transmitted at an average of 125 μsec (8 KHz cycle). Variable trailer length defines an average value.

[0078] Described below is the trailer. Since the DS3 frame is transmitted at a speed of 44.736 MHz, 5592 bits are transmitted in the 125-μsec period according to the following equation.

[0079] number of bits=44.736×10⁶(bit/sec)×125×10⁻⁶(sec)=5592 bits [equation 1]

[0080] However, the data forming the DS3 frame comprises a 1-bit frame bit data and an 84-bit DS3 payload, the number of bits in the DS3 payload for the period of 125 μsec is 5592×84/85=5526.211 . . . as not divisible.

[0081] The number of bits in the PLCP multiframe is 57×12×8+13×4=5524 bits when the trailer length is 13 nibbles, and 57×12×8+14×4=5528 bits when the trailer length is 14 nibbles. That is, there is a residue in the DS3 payload in the 125-μsec period when the trailer length is 13 nibbles, and there is a deficiency in the DS3 payload in the 125-μsec period when the trailer length is 13 nibbles.

[0082] To transmit PLCP multiframes at an average speed of 125 μsec (8 KHz cycle), the PLCP multiframes are transmitted with their trailer length changed between 13 and 14 nibbles.

[0083] A C1-byte cycle staff counter is used to display the trailer length (refer to FIG. 908). FIG. 909 shows the definition related to the cycle staff counter.

[0084] As shown in FIG. 908, the C1 byte is cyclically changed on three multiframe cycles. In the first multiframe, C1 refers to FF and the trailer length is 13 nibbles. In the second multiframe, C1 refers to 00_Hand the trailer length is 14 nibbles. In the third multiframe, C1 refers to 66_Hor 99_Hand the trailer length is 13 nibbles for C1=66_Hand 14 nibbles for C1=99_H. The trailer length of 13 or 14 nibbles is determined such that the PLCP multiframes are transmitted at an average speed of 125 μsec (8 KHz cycle).

[0085] Then, there arises a problem as to what the value of C1 of the third multiframe should be, that is, how to control the trailer. Described below is the conventional method of controlling the trailer.

[0086] Assuming that the pattern prefers to 13 nibbles for the third multiframe and the pattern Q refers to 14 nibbles for the third multiframe, the number of nibbles for the trailer changes 13→14→13 for the pattern P, and 13→14→14 for the pattern Q.

[0087] In the 125 μsec period, the number of bits of the DS3 payload is 5592×84/85=5526.211 . . . The number of bits in the PLCP multiframes is 5524 when the trailer length is 13 nibbles, and 5528 when the trailer length is 14 nibbles. Therefore, the cycle of the PLCP multiframe is fast on the cycle of 125 μsec when the PLCP multiframe pattern is P, and is behind on the cycle of 125 μsec when the PLCP multiframe pattern is Q.

[0088] Conventionally, the cycle of a transmitted PLCP frame is monitored, and the phase of the extracted clock is compared with the phase of the 8 KHz clock obtained by dividing 44.736 MHz. If the phase of the PLCP multiframe to be transmitted is forward, the trailer pattern is switched to P. If it is behind, the trailer pattern is switched to Q. Thus, the transmission cycle of the PLCP multiframe is adjusted properly.

[0089] FIGS. 910 and 911 are timing charts showing the circuit configuration and the operation for realizing the above listed functions.

[0090] A PLCP frame cycle monitoring unit 7 monitors the transmission cycle of the PLCP frames to be transmitted from a selector 3 to output a phase comparison pulse S for every third PLCP frame. A dividing unit 6 generates 8 KHz clock by dividing 44.736 MHz clock by 5,592 generated by a clock generating unit 5. A phase comparing unit 8 compares the phase comparison pulse S with the phase of the 8 KHz clock, and outputs a pattern switch signal C as a value of 1 when the phase comparison pulse S is behind and a value of 0 when is forward.

[0091] The selector 3 selects input A1 and A2 according to the pattern switch signal C. That is, the selector 3 selects the pattern P when the pattern switch signal C indicates 0 and selects the pattern Q when it indicates 1.

[0092] The PLCP frame generating units 1 and 2 for the patterns P and Q store an ATM cell or an L2-PDU cell in the PLCP payload and add a PLCP header and trailer to assemble a PLCP frame.

[0093] The pattern P PLCP frame generating unit 1 adds a trailer for indicating the number of nibbles 13, 14, and 13 on three cycles. The pattern Q PLCP frame generating unit 2 adds a trailer for indicating the number of nibbles 13, 14, and 14 on three cycles.

[0094] The DS3 interface unit 4 inserts a PLCP frame into the DS3 payload and adds a DS3 header to assemble and transmit a DS3 frame.

[0095] However, the above described conventional technology selects a trailer pattern according to the phase comparison result, and the transmission order of the pattern P and Q is not fixed.

[0096] As a result, there arises a problem that the complicated operations generate a complicated circuit.

[0097] Additionally, there is a problem of a large deviation of transmission timing.

[0098] The following functions are required to realize the multicasting capabilities (point-to-multipoint connection) in the ATM switch.

[0099] 1. Copying a cell

[0100] 2. Reassigning a VPI/VCI

[0101] The efficiency in use of the resources as a switch is higher when cells are copied at a point nearer to the exit of the exchange station. The copied cells are distributed to each subscriber. The cells distributed to each subscriber has different VPI/VCIs. That is, the VPI/VCI depends on the destination subscriber. The number of bits of the VPI/VCI is equal to or larger than 22 bits. Simply converting the large number of bits undesirably results in large-scale hardware.

[0102] The ATM switch exchange cells in a self-routing system. If a large-capacity system performs a self-routing process, the efficiency of the switch is higher when the multicasting capabilities are supported in the switch. Thus, the entire system can be smaller in size with the cost reduced.

[0103] The services supported in the B-ISDN should include a large number of point-to-multipoint connection services as well as multicasting capabilities. To reduce the scale of the entire switch, the multicasting capabilities added to realize the point-to-multipoint connection should be minimized for smaller scale and cost. Furthermore, the future extension of the multicasting capabilities should be considered.

[0104] In the point-to-multipoint connection, such information as specifies the number of copied cells and the destination of each of the copied cells is required. The information is normally set as tag information added to the cell when it is input to the exchange station. However, since the amount of the above described information is not small, the tag information occupies about 10 bytes. Adding such tag information to a cell makes the entire cell length longer than in the exchange station. That is, when the tag information is longer, the ratio of the actual data to the entire cell becomes smaller, thereby lowering the throughput.

[0105] FIG. 912 shows the configuration of the form of the conventional multicasting capabilities. In FIG. 912, a source terminal 1 multicast-transfers data to destination terminals 4-1-4-5 through an ATM switch 2.

[0106] Line 3 connects the source terminal 1 with the ATM switch 2. The line 3 can multiplex and transmit a plurality of calls (paths). The ATM switch 2 is also connected to the destination terminals 4-1-4-5 through a subscriber line capable of multiplexing and transmitting data. In the ATM switch 2, a virtual path is set according to the destination information written in the cell transmitted by the source terminal 1. In the example shown in FIG. 912, virtual paths 5-1-5-5 are set as paths for transferring cells to the destination terminals 4-1-4-5.

[0107] In the above described multicasting transfer, cells are copied for the destination terminals in the source terminal 1 and transferred through the paths set between the source terminal 1 and the destination terminals 4-1-4-5. At this time, 5 channels are multiplexed in the line 3 to transfer cells to the destination terminals 4-1-4-5. That is, the bands of 5 channels are occupied.

[0108] Thus, since N paths are set between the source terminal and destination terminal when 1:N multicast transfer is made according to the conventional method shown in FIG. 912, the resources for the line 3 and ATM switch 2 have been used more than necessary and the load on the source terminal 1 has been heavy.

[0109] It is expected that the demand for dynamic images will greatly increase. For example, members of companies in the distance have a lot of opportunities to have things settled through conferences over telephone using dynamic images. These services not only satisfy individual subscribers but also promote business smoothly regardless of geographical disadvantages.

[0110] Nevertheless, these services have not been sufficiently offered. That is, the 1:1 communications are more popular than the private line services in the broadband communications network, and the method of controlling the multi-terminal connection, for example, a three-subscriber communications has not been put to practical use.

[0111] Described below is the problem related to the process performed in the event of a failure on a device in the exchange station which processes a transmission line.

[0112] With the ATM switch, a communications line system device in the exchange station processes a number of virtual lines (hereinafter referred to simply as lines) specified by individual VPI/VCIs. When a failure occurs on a communications line system device, how to handle the lines processed by the device is very important in maintaining the quality of the communications.

[0113] When a failure occurs on a communications line system device in the exchange station, a call connected through the line processed by the device is compulsorily terminated by a compulsory release process activated by the fault monitor process for the entire system. Therefore, the subscribers have the problem that the communications may be suddenly terminated.

[0114] The conventional systems have not provided the mechanism of managing the line processed by the communications line system device.

[0115] Described below is the problem relating to the process performed when a failure is detected on the line.

[0116] When a line failure is detected on a single-structured, not duplex, ATM switch, the transmission information such as subscriber information, billing information, traffic information, performance information, etc. is saved by a line switch process in physical line units using a reserved line, etc. conventionally.

[0117] Practically, if a failure is detected on one physical line when a remote concentrator 1 and an ATM switch 2 are connected through a plurality of physical lines as shown in FIG. 913, then the faulty band or an idle band for other lines are not used, but the state of the faulty line is assigned to a new alternate line such as a spare line, etc.

[0118] Therefore, even though large idle bands exist in other lines, they are not utilized effectively, thereby lowering the use rate of the lines.

[0119] To perform a line switch process in physical line units, it is necessary either to reserve sufficient spare lines or to duplex each of the physical lines. As a result, the communications may cost high.

[0120] It is also necessary to duplex the intra-station device such as a communications system device, etc. in the exchange station to maintain the reliability of the communications. If a failure occurs on the intra-station device of the active system, then various communications control data are transferred to the intra-station device of a standby system to stop the operation of the intra-station device which has been a device in the active system and start the operation of the intra-station device which has been an intra-station device of the standby system.

[0121] In this case, various communications control data set in the intra-station device of the active system have been conventionally transferred to the intra-station device of a standby system by a processor controlling the intra-station device. However, since the amount of the various communications control data is large for the ATM switch, etc., a long time is required by the processor to transfer the data from the intra-station device of an active system to the intra-station device of a standby system, thereby disadvantageously affecting the reliability of the exchange station when a failure occurs on the exchange station.

SUMMARY OF THE INVENTION

[0122] A connectionless communications system requires high reliability including the above described SMDS, but there has not been technology developed to improve the entire system. The present invention aims at improving the quality of the connectionless communications system and providing an efficient method of internally controlling a switch for switching cells, etc.

[0123] One of the important configurations of the present invention is designed as a switching process performed in layer 2 protocol data units (L2-PDU) of connectionless communications using a table having a MID (message identifier) as a key.

[0124] According to other aspects related to the above described subjects, the destination address stored in a beginning of message (BOM) cell is retrieved when the BOM cell is received. According to the destination address, the permanent virtual circuit (PVC), which is predetermined and connected to the destination, is recognized to retrieve the routing information (tag information) specifying the PVC. The destination address is referred to so that the MID (output MID) not currently used in the path to the destination can be acquired. The BOM cell is output with the tag information and output MID assigned, and then transferred to the destination through the route according to the tag information. Then, a table storing the above described routing information and output MIDs is generated according to the MID (input MID) obtained when the BOM cell is received. When a continuation of message (COM) cell or an end of message (EOM) cell is received, the above described table is searched by using the MID of the cell as a key to retrieve routing information (tag information) and an output MID.

[0125] The COM cell or EOM cell is assigned the routing information and output MID and is output to be transferred to the destination as in the case of the BOM cell.

[0126] If the destination address stored in the BOM cell is a group address, the group address development table should be referred to. A group address development table is a table storing the information for use in developing a group address into an individual address using an input MID as a key. The table is generated when a BOM cell is received. Upon receipt of the COM cell or EOM cell, a copying process and routing process are performed according to the MID of the cell.

[0127] If a single segment message (SSM) cell is received, the routing process is performed by retrieving the destination address stored by the SSM as in the case of the BOM cell.

[0128] With the above described configuration, the correspondence between the input MID of a BOM cell and the output MID of the routing information (tag information) is written to a table upon receipt of the BOM cell. When a COM cell or an EOM is received, the routing information and output MID are obtained using the input MID of the cell as a key. That is, since a plurality of cells obtained by dividing one connectionless data frame contain a unique information MID for the data frame, common routing information can be extracted using the MID as a key. (A MID is identification information uniquely assigned to each SNI, and different SNIs can be assigned the same MID. Therefore, a system accommodating a plurality of SNIs represents as a MID in a wide sense the value obtained by combining the MID and SNI or a value uniquely obtained based on the two values.)

[0129] Therefore, each cell can be routed with the routing information retrieved for each cell without assembling data transmitted in cell units into a data frame in a higher order layer (without assembling L3-PDUs). In this case, the routing process is performed in cell units (in L2-PDUs), not by the software, at a high speed in the layer 2 as if it were processed by the hardware.

[0130] Since the routing process is sequentially performed in cell units without assembling data frames in the higher order layer, it is not necessary to buffer a number of input cells forming a data frame in a higher order layer, thereby reducing the capacity of memory, etc.

BRIEF DESCRIPTION OF THE DRAWINGS

[0131] FIG. 1 shows the configuration of the broadband network for which the present invention functions effectively.

[0132] FIG. 2 shows the architecture of the broadband system for which the present invention functions effectively.

[0133] FIG. 3 shows the system of realizing the SMDS in the broadband switch.

[0134] FIG. 4 shows a typical hardware configuration of the broadband switching system for which the present invention functions effectively.

[0135] FIG. 5 shows the configuration of a port in the ASSW.

[0136] FIG. 6 shows the configuration of the subscriber interface shelf (SIFSH).

[0137] FIG. 7 shows the connection of the ADS1SH connected to the SIFSH.

[0138] FIG. 8 shows the configuration of the network based on the ASSW.

[0139] FIG. 9 shows the loopback configuration in the SIFSH.

[0140] FIG. 10 shows the configuration of the test generator connected to the SIFSH.

[0141] FIG. 11 shows the configuration of the BSGCSH.

[0142] FIG. 12 shows the important hardware components of the BRSU.

[0143] FIG. 13 shows the important hardware components of the BRLC.

[0144] FIG. 14 shows the configuration of the connections in the BRLC.

[0145] FIG. 15 shows the configurations of the small host switch and large host switch.

[0146] FIG. 16 shows the configuration of the ASSW.

[0147] FIG. 17 shows the principle of the SRM.

[0148] FIG. 18 shows the configuration of the SRM of 4×4 used in the ASSW.

[0149] FIG. 19 shows the position of the virtual channel identifier converter (VCC).

[0150] FIG. 20 shows the configuration of the ATM switch module of the ASSW.

[0151] FIG. 21 shows the subscriber interface/network interface according to the present invention.

[0152] FIG. 22 shows the position of the broadband signaling controller (BSGC) in the ATM switch.

[0153] FIG. 23 shows the position of the SMDS message handler in the ATM switch.

[0154] FIG. 24 shows the configuration of the broadband call processor (BCPR).

[0155] FIG. 25 shows the configuration of the maintenance and operation system (MOS).

[0156] FIG. 26 shows the hardware configuration of the operation and maintenance processor (OMP).

[0157] FIG. 27 shows the configuration of the broadband remote concentrator.

[0158] FIG. 28 shows the configuration of the broadband remote switch unit (BRSU).

[0159] FIG. 29 shows the configuration of the SMDS device.

[0160] FIG. 30 shows the protocol of the SNI in the layer structure.

[0161] FIG. 31 shows the configuration of the layer applied to the SMDS according to the present embodiment.

[0162] FIG. 32 shows the routing of the cell in the SMDS.

[0163] FIG. 33 shows the outline (1) of the system configuration of the DS3-DMDS interface.

[0164] FIG. 34 shows the outline (2) of the system configuration of the DS3-DMDS interface.

[0165] FIG. 35 shows the mapping from the payload of the ATM cell to the DS3 format.

[0166] FIG. 36 shows the DS3 frame format.

[0167] FIG. 37 shows the DS3 PLCP frame format.

[0168] FIG. 38 shows the format of the DS3-SMDS L2-PDU.

[0169] FIG. 39 shows the contents of the access control field.

[0170] FIG. 40 shows the contents of the network control information field.

[0171] FIG. 41 shows the contents of the segment types.

[0172] FIG. 42 shows the hierarchy of the layers in the SMDS service.

[0173] FIG. 43 shows the format of the DS3 umbilical link.

[0174] FIG. 44 shows the DS3-ATM header field.

[0175] FIG. 45 is the block diagram showing the functional configuration of the DS3-SMDS interface.

[0176] FIG. 46 shows the sequence of the alarm in the DS3 layer.

[0177] FIG. 47 shows the priority levels of the alarm in the DS3 layer.

[0178] FIG. 48 shows the detection and recovery conditions of various types of alarm.

[0179] FIG. 49 shows the timing at which an alarm is declared.

[0180] FIG. 50 shows the sequence of the alarm in the DS3 PLCP layer.

[0181] FIG. 51 shows the detection and recovery conditions of various types of alarm.

[0182] FIG. 52 shows the timing at which an alarm is declared.

[0183] FIG. 53 shows the types of performance parameters related to the DS3 layer; the count-up condition of the accumulated value of each parameter; and the alert threshold for the accumulated value of each parameter.

[0184] FIG. 54 shows the types of performance parameters related to the DS3-PLCP layer; the count-up condition of the accumulated value of each parameter; and the alert threshold for the accumulated value of each parameter.

[0185] FIG. 55 shows the data converting process between the DS3-SMDS interface and SIFSH common unit.

[0186] FIG. 56 shows the format of the ATM cell transferred in the switch.

[0187] FIG. 57 is the timing chart of the E-SD signal.

[0188] FIG. 58 is a table showing-the accommodation states of the E-MSD information transferred between the DS3-SMDS interface and SIFSH common unit.

[0189] FIG. 59 shows the contents of each bit of the E-MSD information.

[0190] FIG. 60 is a timing chart of the signal line between the DS3-SMDS interface and SIFSH common unit.

[0191] FIG. 61 is a table showing the accommodation states of the E-MSCN information transferred between the DS3-SMDS interface and SIFSH common unit.

[0192] FIG. 62 shows the contents (1) of each bit of the E-MSCN information.

[0193] FIG. 63 shows the contents (2) of each bit of the E-MSCN information.

[0194] FIG. 64 shows the configuration of the connection of the interface between the DS3-SMDS interface and switch software.

[0195] FIG. 65 shows the protocol stack between the DS3-SMDS interface and switch software.

[0196] FIG. 66 shows the outline of the converting process for the VPI and VCI of an intra-station communications cell between the DS3-SMDS interface and the BSGC.

[0197] FIG. 67 shows the format of the intra-station communications SAR-PDR.

[0198] FIG. 68 shows the format of the intra-station communications L2 frame.

[0199] FIG. 69 shows the format of the L3 frame.

[0200] FIG. 70 shows the process sequence of the DS3-SMDS interface (initialization of the DS3-SMDS interface).

[0201] FIG. 71 shows the process sequence of the DS3-SMDS interface (INS procedure of the DS3-SMDS interface).

[0202] FIG. 72 shows the process sequence of the DS3-SMDS interface (OUS procedure of the DS3-SMDS interface).

[0203] FIG. 73 shows the process sequence of the DS3-SMDS interface (hardware fault/intra-station control communicable hardware fault of the DS3-SMDS interface).

[0204] FIG. 74 shows the process sequence of the DS3-SMDS interface (hardware fault/non-intra-station control communicable hardware fault of the DS3-SMDS interface).

[0205] FIG. 75 shows the process sequence of the DS3-SMDS interface (hardware fault/microprocessor fault of the DS3-SMDS interface).

[0206] FIG. 76 shows the process sequence of the DS3-SMDS interface (hardware fault/cross-connection fault (in the active state) between the SIFSH common and DS3-SMDS interface of the DS3-SMDS interface).

[0207] FIG. 77 shows the process sequence of the DS3-SMDS interface (hardware fault/cross-connection fault (in the standby state) between the SIFSH common and DS3-SMDS interface of the DS3-SMDS interface).

[0208] FIG. 78 shows the process sequence of the DS3-SMDS interface (DS3/PLCP layer alarm process).

[0209] FIG. 79 shows the process sequence of the DS3-SMDS interface (reporting the D/Q-timer at the occurrence of the DS3/PLCP TCA, and collecting PM data).

[0210] FIG. 80 shows the process sequence of the DS3-SMDS interface (reporting the D/Q-timer at the occurrence of the DS3-SMDS interface buffer alarm, and collecting buffer data).

[0211] FIG. 81 shows the process sequence of the DS3-SMDS interface (setting a PVC path test special number VPI and VCI cell).

[0212] FIG. 82 shows the discard start/release threshold for the above described cell in the buffer.

[0213] FIG. 83 shows the implementation position of the above described loopback function in the DS3-SMDS interface PCB.

[0214] FIG. 84 shows the outline of the line loopback test in the DSX-3.

[0215] FIG. 85 shows the outline of the line loopback test in the RLC.

[0216] FIG. 86 shows the outline of the path continuity test of the PVC between the DS3-SMDS interface and the SBMESH and GWMESH.

[0217] FIG. 87 shows the configuration of the SIFSH.

[0218] FIG. 88 shows the configuration of the OBP monitoring function of the individual unit.

[0219] FIG. 89 shows the configuration of the function of monitoring a missing package.

[0220] FIG. 90 shows the configuration of the function of monitoring fuse disconnection in the common unit.

[0221] FIG. 91 shows the active control function.

[0222] FIG. 92 shows the configuration of the HLP01A function.

[0223] FIG. 93 shows the memory map of the DS3-SMDS interface.

[0224] FIG. 94 shows the positioning of SIFSH-A in the system.

[0225] FIG. 95 shows the configuration of the package of the SIFCOM.

[0226] FIG. 96 shows the interface between the SIFSH-A and ATM switch (ASSW).

[0227] FIG. 97 shows the interface timing for the 622 Mbps cell highway in the 50-core flat coaxial cable.

[0228] FIG. 98 shows the interface timing for the system switch signal in the 20-core TD bus cable.

[0229] FIG. 99 shows the relationship between the system switch signal and the active system selection state in the SIFSH-A.

[0230] FIG. 100 shows the configuration of the circuit in the SIFSH-A for selecting a reference clock from the SYNSH.

[0231] FIG. 101 shows the relationship among the instruction, alarm, and selected system states of the COM-E-MSD command in each system.

[0232] FIG. 102 shows the interface timing of the 156 Mbps cell highway.

[0233] FIG. 103 shows the receiving timing of an ATM cell in the upward cell highway from the individual unit to the SIFCOM.

[0234] FIG. 104 shows the receiving timing of an ATM cell in the downward cell highway from the SIFCOM to the individual unit.

[0235] FIG. 105 shows the system control when the SIFCOM of system #0 is an active system.

[0236] FIG. 106 shows the logic of the system control under the ACT controller.

[0237] FIG. 107 shows an example of the circuit configuration of the ACT controller

[0238] FIG. 108 shows the phase relationship between the FCK and CLK and the EMSD data and EMSCN data.

[0239] FIG. 109 shows the state transition of the frame synchronization process.

[0240] FIG. 110 shows the successful/unsuccessful frame synchronization process.

[0241] FIG. 111 shows the pilot signal detection/abnormal process.

[0242] FIG. 112 is a flowchart showing a series of processes of fetching data described in 3.3.2.3.2, 3.3.2.3.3, and 3.3.1.3.4.

[0243] FIG. 113 is a block diagram showing the functions in the individual unit for performing a series of processes of fetching data described in 3.3.2.3.2, 3.3.2.3.3, and 3.3.1.3.4.

[0244] FIG. 114 is a block diagram showing the EMSCN transmission circuit in the individual unit.

[0245] FIG. 115 shows the methods of detecting in the individual unit and reporting an interface fault between the SIFCOM and individual unit, detecting method in the SIFCOM, and a list of the contents of the faults.

[0246] FIG. 116 shows a clock interface along the cell stream in the SIFSH-A and between the individual units.

[0247] FIG. 117 shows the structure of the layer of the intra-station control communications.

[0248] FIG. 118 shows the format of the cell of the ATM layer in the simple LAP-D.

[0249] FIG. 119 shows the format of the SAR-PDU in the simple LAP-D.

[0250] FIG. 120 shows the format of the LAP-D of the layer 2.

[0251] FIG. 121 shows the format of the ATM cell.

[0252] FIG. 122 shows the configuration of the ATM cell header data used in the SIFSH-A.

[0253] FIG. 123 shows the method of using the ATM header data in the SIFSH-A.

[0254] FIG. 124 shows the configuration of the ATM cell header data used in the RMXSH.

[0255] FIG. 125 shows the method of using the ATM header data in the RMXSH.

[0256] FIG. 126 shows the configuration of the ATM cell header data used in the RSGCSH.

[0257] FIG. 127 shows the method of using the ATM header data in the BSGCSH.

[0258] FIG. 128 shows the method of using the SIG/ADS1BLK/ADS1SEL in the SIFSH-A.

[0259] FIG. 129 shows the assignment of the functions in the SIFSH-A and ADS1SH (refer to FIG. 8) of the ATM cell header data defined in FIGS. 122, 123, and 128.

[0260] FIG. 130 shows the position of the MUX in the SIFSH-A.

[0261] FIG. 131 shows the configuration of the serial connection of the SIFSH-A.

[0262] FIG. 132 shows the configuration of the MUX.

[0263] FIG. 133 shows the outline of the configuration of the scheduler.

[0264] FIG. 134 shows the timing of writing an ATM cell to the FIFO (first-in-first-out buffer) scheduler.

[0265] FIG. 135 shows the timing sending an output enable signal.

[0266] FIG. 136 shows the write abnormal process performed when the data length of an input cell is short.

[0267] FIG. 137 shows the write abnormal process performed when the data length of an input cell is long.

[0268] FIG. 138 shows the read abnormal process.

[0269] FIG. 139 shows the threshold set in the buffer in the MUX.

[0270] FIG. 140 shows the position of the DMUX in the SIFSH-A.

[0271] FIG. 141 shows the configuration of the DMUX.

[0272] FIG. 142 shows the cell format in the switch.

[0273] FIG. 143 shows the location of the matching bit of the header used in the DMUX.

[0274] FIG. 144 shows the outline of the umbilical protection switching.

[0275] FIG. 145 shows the threshold set in the buffer in the DMUX.

[0276] FIG. 146 shows the VCC/ATM switch fault.

[0277] FIG. 147 shows the configuration of the table in the VCC memory.

[0278] FIG. 148 is an arrow diagram showing the INS procedure.

[0279] FIG. 149 the status of each system and the process performed by the CC (switching processor).

[0280] FIG. 150 shows the position of the signal processing unit (EGCLAD) in the SIFSH-A.

[0281] FIG. 151 shows the header check area.

[0282] FIG. 152 shows the header insertion area.

[0283] FIG. 153 shows the points of inserting and monitoring the monitoring cell MC, and shows their routes.

[0284] FIG. 154 shows the route of the TCG test.

[0285] FIG. 155 shows the process of detecting an OBP fault in the SIFCOM.

[0286] FIG. 156 shows the process of detecting a package missing fault in the SIFCOM.

[0287] FIG. 157 shows the process of detecting a power package missing fault.

[0288] FIG. 158 shows the process of detecting a IFCOM fuse disconnection fault.

[0289] FIG. 159 shows the process of detecting a downward coaxial flat cable fault.

[0290] FIG. 160 shows the process of detecting an upward coaxial flat cable fault.

[0291] FIG. 161 shows the process of detecting a TD bus cable fault.

[0292] FIG. 162 shows the SIFCOM fault (1).

[0293] FIG. 163 shows the SIFCOM fault (2).

[0294] FIG. 164 shows the umbilical circuit for connecting the host switch to the BRLC.

[0295] FIG. 165 shows the switching sequence of the circuit in the circuit protection.

[0296] FIG. 166 shows the format of the command for switching circuit.

[0297] FIG. 167 shows the internal configuration of the ASSWSH-A.

[0298] FIG. 168 shows the configuration of the connection of the communications line system.

[0299] FIG. 169 shows the signal timing in the interface between the SWMDX and the ATM highway of 622 Mbps.

[0300] FIG. 170 shows the format of the cell in the interface between the SWMDX and the ATM highway of 622 Mbps.

[0301] FIG. 171 shows the interface between the INFA and ASSWSH-A.

[0302] FIG. 172 shows the interface between the SWCNT of the home system and the SWCNT of the mate system.

[0303] FIG. 173 shows the system selection signal and its strobe signal.

[0304] FIG. 174 shows the system selection logic related to the system selection signal.

[0305] FIG. 175 shows the external interface (1) for the SWMX.

[0306] FIG. 176 shows the external interface (2) for the SWMX.

[0307] FIG. 177 shows the external interface (1) for the SWMDX.

[0308] FIG. 178 shows the external interface (2) for the SWMDX.

[0309] FIG. 179 shows the external interface (1) for the SWCNT.

[0310] FIG. 180 shows the external interface (2) for the SWCNT.

[0311] FIG. 181 shows the detailed functions of each block forming part of the ASSWSH-A.

[0312] FIG. 182 shows each block forming part of the SWMDX.

[0313] FIG. 183 shows the functions of each block in the SWMDX.

[0314] FIG. 184 shows each block forming part of the SWMX.

[0315] FIG. 185 shows the functions of each block in the SWMX.

[0316] FIG. 186 shows each block forming part of the SWCNT.

[0317] FIG. 187 shows the functions of each block in the SWCNT.

[0318] FIG. 188 shows each block forming part of the SWTIF.

[0319] FIG. 189 shows the functions of each block in the SWTIF.

[0320] FIG. 190 shows each block forming part of the SCLK.

[0321] FIG. 191 shows the functions of each block in the SCLK.

[0322] FIG. 192 shows the cell discard class.

[0323] FIG. 193 is a block diagram showing the traffic measuring circuit.

[0324] FIG. 194 is a timing chart showing the operation of the traffic measuring circuit.

[0325] FIG. 195 is a timing chart (a) showing the CC access (IN instruction) and shows the address/data format (b).

[0326] FIG. 196 is a timing chart (a) showing the CC access (OUT instruction) and shows the address/data format (b).

[0327] FIG. 197 is a timing chart (a) showing the DMA access (read) and shows the address/data format (b).

[0328] FIG. 198 is a timing chart (a) showing the DMA access (write) and shows the address/data format (b).

[0329] FIG. 199 is a list of IN/OUT instructions.

[0330] FIG. 200 shows the procedure of detecting a fault (when a report is made by the MSCN).

[0331] FIG. 201 shows the procedure of detecting a fault (when status is autonomously reported).

[0332] FIG. 202 shows the basic format of the message box processed by the fault processing task.

[0333] FIG. 203 shows the fault content write data in the message box for a common fault.

[0334] FIG. 204 shows the entire configuration of the position of the SBMESH in the system.

[0335] FIG. 205 shows the route of the SMDS data between SNIs.

[0336] FIG. 206 shows the route of transferring SMDS data from the SNI to the ISSI or ICI.

[0337] FIG. 207 shows the route of transferring SMDS data from the ISSI or ICI to the SNI.

[0338] FIG. 208 shows the route of transferring SMDS data from the ISSI or ICI to the ISSI or ICI.

[0339] FIG. 209 is a block diagram showing the SBMESH.

[0340] FIG. 210 is a block diagram showing the redundant configuration of the SBMESH.

[0341] FIG. 211 shows the logical connection between message handlers MH.

[0342] FIG. 212 shows the disassembling/assembling user information in layers 2 and 3.

[0343] FIG. 213 shows the data configuration of the AAL/SAR of layer 2.

[0344] FIG. 214 shows the method of assigning the output VCI/MID depending on the type of cell.

[0345] FIG. 215 shows routing function at each position in the system, and shows the information in the cell used in the routing function.

[0346] FIG. 216 shows an example of assigning the VCI corresponding to the SNI.

[0347] FIG. 217 shows the assignment (1) of a VPI/VCI between the SNI and SBMH.

[0348] FIG. 218 shows the assignment (2) of a VPI/VCI between the SNI and SBMH.

[0349] FIG. 219 shows an example of assigning a VPI/VCI between message handlers MH.

[0350] FIG. 220 shows the assignment of a VPI/VCI between message handlers MH.

[0351] FIG. 221 shows an example of assigning a MID to each SMLP.

[0352] FIG. 222 shows the concept of data distribution using a group address.

[0353] FIG. 223 shows the information used to identify the SNI to which each cell belongs and the L3-PDU.

[0354] FIG. 224 is a block diagram showing the function of the SBMESH.

[0355] FIG. 225 if a block diagram showing the entire configuration of the SMLP unit.

[0356] FIG. 226 shows the outline (1) of the functions of each block of the SMLP unit shown in FIG. 225.

[0357] FIG. 227 shows the outline (2) of the functions of each block of the SMLP unit shown in FIG. 225.

[0358] FIG. 228 shows the outline (3) of the functions of each block of the SMLP unit shown in FIG. 225.

[0359] FIG. 229 shows the outline (1) of the error flags operated for each block of the SMLP unit shown in FIG. 225.

[0360] FIG. 230 shows the outline (2) of the error flags operated for each block of the SMLP unit shown in FIG. 225.

[0361] FIG. 231 shows the outline (3) of the error flags operated for each block of the SMLP unit shown in FIG. 225.

[0362] FIG. 232 shows the outline (4) of the error flags operated for each block of the SMLP unit shown in FIG. 225.

[0363] FIG. 233 shows the correspondence between the error flag EF and the error name (naming in the TR) and the position (1) of the EF.

[0364] FIG. 234 shows the correspondence between the error flag EF and the error name (naming in the TR) and the position (2) of the EF.

[0365] FIG. 235 shows the correspondence between the error flag EF and the error name (naming in the TR) and the position (3) of the EF.

[0366] FIG. 236 shows the correspondence between the error flag EF and the error name (naming in the TR) and the position (4) of the EF.

[0367] FIG. 237 shows the correspondence between the error flag EF and the error name (naming in the TR) and the position (5) of the EF.

[0368] FIG. 238 shows the timing in the cross-connection select S.

[0369] FIG. 239 shows the format of a cell (header field).

[0370] FIG. 240 shows the sending operation of the line cell and test cell then the test cell is multiplexed.

[0371] FIG. 241 shows the process related to the CRC-10 check.

[0372] FIG. 242 shows the process related to the PL length check for each segment type.

[0373] FIG. 243 shows the process related to the MID value check for each segment type.

[0374] FIG. 244 shows the process related to the MID check for each segment type.

[0375] FIG. 245 shows the process related to the SN check for each segment type.

[0376] FIG. 246 shows the process related to the address format check.

[0377] FIG. 247 shows the process related to the DA check for each segment type.

[0378] FIG. 248 shows the process related to the BA—BA-size check.

[0379] FIG. 249 shows the process timing in the ingress flow check.

[0380] FIG. 250 shows the process related to the simultaneous input number check.

[0381] FIG. 251 shows the process related to the MID timeout check.

[0382] FIG. 252 shows the read/write data to the RMID conversion CAM and MRI CAM.

[0383] FIG. 253 shows the matching and read/write timing of the RMID conversion CAM and MRI CAM for each cell.

[0384] FIG. 254 is a flowchart showing the process of the simultaneous input number limit RMID acquisition/MRI timeout.

[0385] FIG. 255 shows the concept of the degeneration of the RMID.

[0386] FIG. 256 shows the process of normal and abnormal cells in the RMID acquiring unit, simultaneous input limit, and MRI T.O. set/release for each segment type.

[0387] FIG. 257 shows the process related to the header extension (HE) format check.

[0388] FIG. 258 shows the process related to the source address (SA) check for each segment type.

[0389] FIG. 259 shows the process related to the screening of a destination address DA.

[0390] FIG. 260 shows the process related to the matching of a BE tag.

[0391] FIG. 261 shows the process related to the matching check on the BA size.

[0392] FIG. 262 shows the process related to the information length check.

[0393] FIG. 263 shows the discard of an error message in the L3-PDU.

[0394] FIG. 264 shows the discard of a message received after an MRI timeout EOM.

[0395] FIG. 265 shows the process for error memory for each segment type.

[0396] FIG. 266 shows the encapsulation.

[0397] FIG. 267 shows the ISSI header assigned to the information BON between the message handlers (MH).

[0398] FIG. 268 shows the format of the information BON between the message handlers (MH).

[0399] FIG. 269 shows the process related to the carrier selection.

[0400] FIG. 270 shows the outline of the process related to the routing.

[0401] FIG. 271 shows the concept of the process related to the routing.

[0402] FIG. 272 shows the outline of the process related to the carrier screening.

[0403] FIG. 273 shows the broadcast specification bit.

[0404] FIG. 274 shows the process related to the copy of cells.

[0405] FIG. 275 shows the format of the cell after being broadcast.

[0406] FIG. 276 is a flowchart of the copying process on the group address GA field.

[0407] FIG. 277 shows the process related to the output band limit.

[0408] FIG. 278 shows the process of acquiring an output MID.

[0409] FIG. 279 is a flowchart of the process related to the acquisition of the MID.

[0410] FIG. 280 is a list (1) of the SMLP table.

[0411] FIG. 281 is a list (2) of the SMLP table.

[0412] FIG. 282 is the block diagram showing the entire configuration of the RMLP.

[0413] FIG. 283 shows the outline (1) of the functions of each block of the RMLP.

[0414] FIG. 284 shows the outline (2) of the functions of each block of the RMLP.

[0415] FIG. 285 shows the route (1) of the test cell in the PVC test, and shows the SNI loopback test.

[0416] FIG. 286 shows the route (2) of the test cell in the PVC test, and shows the inter-MH (using a specific DA) test.

[0417] FIG. 287 shows the route (3) of the test cell in the PVC test, and shows the inter-MH (using an allocated DA) test.

[0418] FIG. 288 shows the RMLP accommodating the MSCN.

[0419] FIG. 289 shows the RMLP accommodating the MSD.

[0420] FIG. 290 shows the error flag (EF) operated for each function block of the RMLP.

[0421] FIG. 291 shows the data interface of the RMLP and LP-COM, and the format (1) of the cell.

[0422] FIG. 292 shows the data interface of the RMLP and LP-COM, and the format (2) of the cell.

[0423] FIG. 293 shows the data interface of the RMLP and LP-COM, and the format (3) of the cell.

[0424] FIG. 294 shows the data interface of the RMLP and LP-COM, and the format (4) of the cell.

[0425] FIG. 295 shows the data interface of the RMLP and LP-COM, and the format (5) of the cell.

[0426] FIG. 296 is a block diagram showing the functions of the HMH00A.

[0427] FIG. 297 shows the outline of the functions of each block of the HMH00A.

[0428] FIG. 298 shows the block diagram showing the functions of the cross-connection select R.

[0429] FIG. 299 shows the outline of the functions of each block of the cross connection select R.

[0430] FIG. 300 shows the cross-connection of the system in the HMH00A.

[0431] FIG. 301 shows the adjustment of the timing through the FIFO.

[0432] FIG. 302 shows the process of selecting cross-connection data.

[0433] FIG. 303 shows the MSCN point in the cross-connection select.

[0434] FIG. 304 is a block diagram showing the functions of the timing generator R.

[0435] FIG. 305 shows the outline of the functions of each block of the timing generator R.

[0436] FIG. 306 shows the operation of the sell frame (CF) generator.

[0437] FIG. 307 shows the MSCN point in the timing generator.

[0438] FIG. 308 is a block diagram showing the functions of the address filter R.

[0439] FIG. 309 shows the outline of the functions of each block of the address filter R.

[0440] FIG. 310 shows the outline of the VCI/MID matcher conditions.

[0441] FIG. 311 shows the MSCN point in the address filter R.

[0442] FIG. 312 is a block diagram showing the functions of the HMH01A.

[0443] FIG. 313 shows the outline of the functions of each block of the HMH01A.

[0444] FIG. 314 is a block diagram showing the functions of the test cell multiplexing R and 9MG R.

[0445] FIG. 315 shows the MSCN point in the test cell multiplexing R and 9MG R.

[0446] FIG. 316 is a block diagram showing the functions of the MID check R.

[0447] FIG. 317 shows the process related to the MID check.

[0448] FIG. 318 shows the error flag in the MID check.

[0449] FIG. 319 shows the MSCN point in the MID check R.

[0450] FIG. 320 is a block diagram showing the functions of the SN check R.

[0451] FIG. 321 shows an error flag in the SN check R.

[0452] FIG. 322 shows the MSCN point in the SN check R.

[0453] FIG. 323 is a block diagram showing the functions of the encapsulation unit.

[0454] FIG. 324 shows the error flag in the encapsulation unit.

[0455] FIG. 325 shows the MSCN point in the encapsulation unit.

[0456] FIG. 326 is a block diagram showing the functions of the error edit IR.

[0457] FIG. 327 is a block diagram showing the functions of the RMID acquisition R.

[0458] FIG. 328 shows the outline of the functions of each block of the RMID acquisition R.

[0459] FIG. 329 shows the error flag in the RMID acquisition R unit.

[0460] FIG. 330 is a block diagram showing the functions of the MRI timeout check R.

[0461] FIG. 331 shows the outline of the functions of each block of the MRI timeout check R.

[0462] FIG. 332 shows the header format of the TO cell (timeout cell).

[0463] FIG. 333 shows the error flag in the MRI timeout check unit.

[0464] FIG. 334 is a block diagram showing the functions of the GA copy R.

[0465] FIG. 335 shows the outline of the functions of each block of the GA copy R.

[0466] FIG. 336 shows the error flag in the GA copy unit.

[0467] FIG. 337 shows the MSCN point in the GA copy unit.

[0468] FIG. 338 is a block diagram showing the functions of the SNI available R.

[0469] FIG. 339 shows the error flag in the SNI available unit.

[0470] FIG. 340 shows the MSCN point in the SNI available unit.

[0471] FIG. 341 is a block diagram showing the functions of the error edit II R and shows the outline of the functions of their blocks.

[0472] FIG. 342 is a block diagram showing the functions of the SA check R and shows the outline of the functions of their blocks.

[0473] FIG. 343 shows the error flag in the MID check.

[0474] FIG. 344 shows the MSCN point in the SA check unit.

[0475] FIG. 345 shows the matching with the SC attribute in the SA screening R.

[0476] FIG. 346 is a block diagram showing the entire configuration of the HMH02A.

[0477] FIG. 347 is a block diagram showing the functions of the HMH02A.

[0478] FIG. 348 shows the outline of the functions of each block shown in FIG. 347.

[0479] FIG. 349 shows the interface I/F state of the HMH02A.

[0480] FIG. 350 is a table showing the contents of the message control in the HMH02A.

[0481] FIG. 351 is a detailed block diagram showing the simultaneous transmission number limiting unit.

[0482] FIG. 352 shows the management of the message transmission number for a specific SNI.

[0483] FIG. 353 shows the concept of the buffering management.

[0484] FIG. 354 is a block diagram showing the output MID acquiring unit.

[0485] FIG. 355 shows the process of acquiring an output MID.

[0486] FIG. 356 is a block diagram showing the egress flow limiting unit.

[0487] FIG. 357 is a block diagram showing the discard counter unit.

[0488] FIG. 358 is a block diagram showing the CRC-10 generating unit.

[0489] FIG. 359 shows the position in the cell of the CRC-10 polynomial cell generated by the CRC-10 generating unit.

[0490] FIG. 360 is a block diagram showing the clock generating unit.

[0491] FIG. 361 shows the method of generating a clock in the clock generating unit.

[0492] FIG. 362 is a table showing the contents of μP I/F.

[0493] FIG. 363 shows the function of the four PWCBs forming parts of the MH-COM.

[0494] FIG. 364 is a block diagram showing the HMX10A PWCB.

[0495] FIG. 365 shows the monitor items (1) of the HMX10A PWCB.

[0496] FIG. 366 shows the monitor items (2) of the HMX10A PWCB.

[0497] FIG. 367 is a block diagram showing the HMX11A PWCB.

[0498] FIG. 368 shows the monitor items (1) of the HMX11A PWCB.

[0499] FIG. 369 shows the monitor items (2) of the HMX11A PWCB.

[0500] FIG. 370 shows the monitor items (3) of the HMX11A PWCB.

[0501] FIG. 371 is a block diagram mainly showing the VCC function of the HMX12A PWCB.

[0502] FIG. 372 is a block diagram mainly showing the scheduler function of the HMX12A PWCB.

[0503] FIG. 373 shows the monitor items (1) related to the fault correcting process of the HMX12A PWCB.

[0504] FIG. 374 shows the monitor items (2) related to the fault correcting process of the HMX12A PWCB.

[0505] FIG. 375 shows the monitor items (3) related to the fault correcting process of the HMX12A PWCB.

[0506] FIG. 376 is a block diagram showing the functions of the HSF05A.

[0507] FIG. 377 shows the monitor items related to the fault correcting process of the HSF05A PWCB.

[0508] FIG. 378 is a system diagram of the SBMESH clock.

[0509] FIG. 379 is a block diagram showing the functions of the HLM01A PWCB.

[0510] FIG. 380 shows the outline (1) of the functions of each block of the HLM01A PWCB.

[0511] FIG. 381 shows the outline (2) of the functions of each block of the HLM01A PWCB.

[0512] FIG. 382 is a list (1) of checks made in the HLM01A PWCB.

[0513] FIG. 383 is a list (2) of checks made in the HLM01A PWCB.

[0514] FIG. 384 shows the check items and process of the protocol performance monitor in the ingress unit.

[0515] FIG. 385 is a time chart showing the timing of error information.

[0516] FIG. 386 shows each signal in the timechart.

[0517] FIG. 387 shows the method of identifying the cell segment type in the ST identification block.

[0518] FIG. 388 is a timechart showing the processes to be performed when an error occurs.

[0519] FIG. 389 is a timechart showing the access timing of the threshold and count value in the sum of error count process.

[0520] FIG. 390 is a timechart showing the L2/3 individual error counting process.

[0521] FIG. 391 is a timechart showing the layer 3 Bursty error process.

[0522] FIG. 392 is a flowchart showing the method of accessing the E-PDU flag RAM.

[0523] FIG. 393 shows the check items in the egress unit, and the procedure for actions and checks when an NG is detected.

[0524] FIG. 394 is a timechart showing the process of the protocol performance monitor in the egress unit.

[0525] FIG. 395 shows each signal in the timechart.

[0526] FIG. 396 shows the method of identifying the segment type of cell.

[0527] FIG. 397 is a timechart showing the L2/3 individual error count process in the Ingress unit.

[0528] FIG. 398 is a timechart showing the network data collection in the ingress unit.

[0529] FIG. 399 is a timechart showing the data collection process in the ingress unit.

[0530] FIG. 400 is a block diagram showing the billing unit.

[0531] FIG. 401 shows the format of the cell input from the RMLP.

[0532] FIG. 402 shows the data at the SA, carrier, and stored in the RDA accumulation RAM.

[0533] FIG. 403 shows the inside of the DA compression CAM.

[0534] FIG. 404 is a time chart showing the operations performed when an EOM is entered in the billing process.

[0535] FIG. 405 shows the information stored in the RAM storing the data related to the billing process.

[0536] FIG. 406 is a block diagram showing the portion for checking the billing unit.

[0537] FIG. 407 is a block diagram showing the HLP02A of the LP-COM.

[0538] FIG. 408 shows the outline (1) of the functions of each block of the HLP02A.

[0539] FIG. 409 shows the outline (2) of the functions of each block of the HLP02A.

[0540] FIG. 410 shows the format of the cell input from the ASSW to the SDMUX.

[0541] FIG. 411 shows the format of the cell input from the SDMUX to the SMLP(a).

[0542] FIG. 412 shows the format of the cell input from the LP-COM to the SMLP(a).

[0543] FIG. 413 shows the format of the cell input from the SMLP(a) (HMH03A) to the SMLP(b) (HMH04A).

[0544] FIG. 414 shows the format of the cell input from the SMLP(b) (HMH04A) to the SMLP(c) (HMH05A).

[0545] FIG. 415 shows the format of the timeout dummy cell input from the SMLP(B) (HMH04A) to the SMLP (HMH05A).

[0546] FIG. 416 shows the format of the cell input from the SMLP(c) (HMH05A) to the SMLP(d) (HMH06A).

[0547] FIG. 417 shows the format of the I-BOM cell input from the SMLP(c) (HMH05A) to the SMLP(d) (HMH06A).

[0548] FIG. 418 shows the format of the cell input from the SMLP(d) (HMH06A) to the SMUX(HMX12A).

[0549] FIG. 419 shows the format of the cell input from the SMLP(d) (HMH06A) to the LP-COM(HLP02A, HLM01A).

[0550] FIG. 420 shows the format of the cell output from the SMUX to the ASSW.

[0551] FIG. 421 shows the format of the cell input from the ASSW to the RDMUX.

[0552] FIG. 422 shows the format of the cell input from the RDMUX(HMX10A) to the RMLP(a) (HMH00A).

[0553] FIG. 423 shows the format of the cell input from the RMLP(a) (HMH00A) to the RMLP(b) (HMH01A).

[0554] FIG. 424 shows the format of the cell input from the LP-COM(HLP02A) to the RMLP(b)(HMH01A).

[0555] FIG. 425 shows the format of the cell input from the RMLP(b) (HMH01A) to the RMLP(c) (HMH04A).

[0556] FIG. 426 shows the format of the timeout dummy cell input from the RMLP(b) (HMH01A) to the RMLP(c)(HMH04A).

[0557] FIG. 427 shows the format of the cell input from the RMLP(c) (HMH04A) to the RMLP(d) (HMH02A).

[0558] FIG. 428 shows the format of the cell input from the RMLP(d) (HMH02A) to the LP-COM(HLP02A, HLM00A).

[0559] FIG. 429 shows the format of the cell input from the RMLP(d) (HMH02A) to the LP-COM(HLP02A, HLM01A).

[0560] FIG. 430 shows the format of the cell input from the RMLP(HMH02) to the RMUX(HMX12A).

[0561] FIG. 431 shows the format of the cell input from the RMIX(HMX12A) to the ASSW.

[0562] FIG. 432 shows the error flag at the SMLP.

[0563] FIG. 433 shows the error flag at the RMLP.

[0564] FIG. 434 shows the initialization of the MH-COM.

[0565] FIG. 435 shows the flow of the cell in the intra-station communications.

[0566] FIG. 436 shows an example of the VPI/VCI value of the intra-station communications cell.

[0567] FIG. 437 shows the intra-station communications link between the BSGC and SBMESH.

[0568] FIG. 438 show the relationship between the shelf number of the SBMESH and the value of the tag.

[0569] FIG. 439 shows the tag field of the cell specifying a particular SBMESH.

[0570] FIG. 440 shows the tag field of the cell specifying a particular SBMH.

[0571] FIG. 441 shows the process of preventing an error which may occur at the initialization of the LP unit.

[0572] FIG. 442 shows an example of changing a parameter in the subscriber data entry.

[0573] FIG. 443 shows the INS process of the MH-COM.

[0574] FIG. 444 shows the outline of the operations performed when an MH-COM fault occurs.

[0575] FIG. 445 shows the sequence of a fault which is reported by the E-MSCN in the home system and occurs in the standby system.

[0576] FIG. 446 shows the sequence of a fault which is reported by the E-MSCN in the home system and occurs in the active system.

[0577] FIG. 447 shows the sequence of a fault which is reported by the E-MSCN in the mate system and occurs in the standby system.

[0578] FIG. 448 shows the sequence of a fault which is reported by the E-MSCN in the mate system and occurs in the active system.

[0579] FIG. 449 shows the interface between the SBMESH and the BCPR.

[0580] FIG. 450 shows the INF MSCN 32 bits.

[0581] FIG. 451 shows the concept of checking the MSCN point related to the inter-system cross-connection of the MH-COM and LP.

[0582] FIG. 452 shows the relationship (1) between the states of 15 and 17 bits and the fault in the INF MSCN.

[0583] FIG. 453 shows the relationship (2) between the states of 15 and 17 bits and the fault in the INF MSCN.

[0584] FIG. 454 shows the relationship (3) between the states of 15 and 17 bits and the fault in the INF MSCN.

[0585] FIG. 455 shows the relationship (1) between the states of 19 and 21 bits and the fault in the INF MSCN.

[0586] FIG. 456 shows the relationship (2) between the states of 19 and 21 bits and the fault in the INF MSCN.

[0587] FIG. 457 shows the concept of a health check of the LP.

[0588] FIG. 458 shows the ACT signal process in switching system in the MH-COM.

[0589] FIG. 459 shows the loopback test of the SBMESH using the TCG.

[0590] FIG. 460 shows the loopback at the individual unit accommodated in the SIFSH.

[0591] FIG. 461 shows the loopback at the LP of each SBMESH.

[0592] FIG. 462 shows an example of the tag information of a test cell transmitted from the TCG to the SBMESH.

[0593] FIG. 463 shows the process performed on a test cell input to the SBMESH.

[0594] FIG. 464 shows the test for confirming the DMUX and MUX functions of the SBMESH.

[0595] FIG. 465 shows the SNI-SBMESH-A PVC test.

[0596] FIG. 466 shows the existence of a block in the SINF and DT, and a loopback method.

[0597] FIG. 467 shows the MESH-MH PVC test.

[0598] FIG. 468 shows the outline of the method of specifying a DA and the test in specifying the type in the MESH-MH PVC test.

[0599] FIG. 469 shows the result of the PVC test contained in the status as a response to the PVC test result request command.

[0600] FIG. 470 shows an example of the test cell transmission unit fault indicator area.

[0601] FIG. 471 shows an example of the test cell receiving unit fault indicator area.

[0602] FIG. 472 shows the printout result of the SNI-SBMESH PVC test.

[0603] FIG. 473 shows the printout result of the MESH-MH PVC test (using a specific test DA).

[0604] FIG. 474 shows the printout result of the MESH-MH PVC test (using an allocated DA).

[0605] FIG. 475 shows the outline of the MH-COM diagnostics.

[0606] FIG. 476 shows an example of performing the DP as one of the MH-COM diagnostics.

[0607] FIG. 477 shows the details of the RESULT information of the above described performance of the DP.

[0608] FIG. 478 shows the details of the length information of the above described performance of the DP.

[0609] FIG. 479 shows the details of the result information of the above described performance of the DP.

[0610] FIG. 480 shows the details of the diagnostics result notification status of a function test of the LP.

[0611] FIG. 481 shows the format of the E-MSCN of the MH-COM.

[0612] FIG. 482 shows the concept of accommodating the detailed MSCN.

[0613] FIG. 483 shows the format of the E-MSD of the MH-COM.

[0614] FIG. 484 shows the accommodation of the MH-COM control E-MSD area.

[0615] FIG. 485 shows the contents (1) of each point in the MH-COM control E-MSD.

[0616] FIG. 486 shows the contents (2) of each point in the MH-COM control E-MSD.

[0617] FIG. 487 shows the accommodation of the statistic threshold design area.

[0618] FIG. 488 shows the contents (1) of each point in the statistic threshold design area.

[0619] FIG. 489 shows the contents (2) of each point in the statistic threshold design area.

[0620] FIG. 490 shows the accommodation of the COM-E-MSCN mask pattern setting area.

[0621] FIG. 491 shows the contents of the mask specification point of the COM-E-MSCN mask pattern setting area.

[0622] FIG. 492 shows the sequence of the statistic process of the MH-COM.

[0623] FIG. 493 shows an example of an abnormal collection in the MH-COM statistic process.

[0624] FIG. 494 shows the sequence of the abnormal statistic process in the MH-COM.

[0625] FIG. 495 shows the sequence of each process of the LP.

[0626] FIG. 496 shows the position of the gateway message handler (GWMESH) in the system.

[0627] FIG. 497 shows the process of the SMDS data between SNIs.

[0628] FIG. 498 shows the process of the SMDS data for SNI→ISSI or ICI.

[0629] FIG. 499 shows the process of the SMDS data for ISSI or ICI→SNI.

[0630] FIG. 500 shows the process of the SMDS data for ISSI or ICI→ISSI or SNI.

[0631] FIG. 501 is a block diagram showing the configuration of the GWMESH.

[0632] FIG. 502 is a block diagram showing the redundant configuration (duplex configuration) of the GWMESH.

[0633] FIG. 503 shows an example of the configuration of the SMDS network.

[0634] FIG. 504 shows an example of the routing process performed when data is transferred using an individual address.

[0635] FIG. 505 shows an example of the routing process shown in FIG. 504 in a network.

[0636] FIG. 506 shows an example of the routing process performed when data is transferred using a group address.

[0637] FIG. 507 shows a method of transferring data when the source of the data is in the area specified by a group address.

[0638] FIG. 508 shows a method of transferring data when a group-address-specified area is in another local carrier in the LATA for the data transfer source.

[0639] FIG. 509 shows a method of transferring data when a group-address-specified area is in another local carrier external to the LATA for the data transfer source.

[0640] FIG. 510 shows the link between switching systems or between a switching system and another carrier.

[0641] FIG. 511 shows the accommodation conditions for a link set.

[0642] FIG. 512 shows the load splitting algorithm

[0643] FIG. 513 is a block diagram showing the entire configuration of the ICLP of the GWMESH.

[0644] FIG. 514 shows the functions of each block of the ICLP.

[0645] FIG. 515 shows the correspondence between each function of the ICLP and an error flag (1).

[0646] FIG. 516 shows the correspondence between each function of the ICLP and an error flag (2).

[0647] FIG. 517 shows the format (MH-COM→ICLP (ISSIP-BOM)) of a cell input to the ICLP.

[0648] FIG. 518 shows the format (MH-COM→ICLP (ICIP-BOM)) of a cell input to the ICLP.

[0649] FIG. 519 shows the format (MH-COM→ICLP (SIP-SSM)) of a cell input to the ICLP.

[0650] FIG. 520 shows the format (MH-COM→ICLP (SIP-BOM)) of a cell input to the ICLP.

[0651] FIG. 521 shows the format (MH-COM→ICLP (COM)) of a cell input to the ICLP.

[0652] FIG. 522 shows the format (MH-COM→ICLP (EOM)) of a cell input to the ICLP.

[0653] FIG. 523 shows the format (ICLP→MH-COM (ISSIP-BOM)) of a cell output from the ICLP.

[0654] FIG. 524 shows the format (ICLP→MH-COM (ICIP-BOM)) of a cell output from the ICLP.

[0655] FIG. 525 shows the format (ICLP→MH-COM (SIP-SSM)) of a cell output from the ICLP.

[0656] FIG. 526 shows the format (ICLP→MH-COM (SIP-BOM)) of a cell output from the ICLP.

[0657] FIG. 527 shows the format (ICLP→MH-COM (COM)) of a cell output from the ICLP.

[0658] FIG. 528 shows the format (ICLP→MH-COM (EOM)) of a cell output from the ICLP.

[0659] FIG. 529 shows the format of a cell input to the HMH12A of the ICLP.

[0660] FIG. 530 shows the format of a cell output from the HMH12A of the ICLP.

[0661] FIG. 531 shows the format (BOM) of a cell input to the HMH13A of the ICLP.

[0662] FIG. 532 shows the format (COM) of a cell input to the HMH13A of the ICLP.

[0663] FIG. 533 shows the format (EOM) of a cell input to the HMH13A of the ICLP.

[0664] FIG. 534 shows the error flags shown in FIGS. 531 through 533.

[0665] FIG. 535 shows the format (BOM) of a cell output to the HMH13A→HLP03A and HLP07A of the ICLP.

[0666] FIG. 536 shows the format (COM) of a cell output to the HMH13A→HLP03A and HLP07A of the ICLP.

[0667] FIG. 537 shows the format (EOM) of a cell output to the HMH13A→HLP03A and HLP07A of the ICLP.

[0668] FIG. 538 shows the error flags shown in FIGS. 535 through 537.

[0669] FIG. 539 shows the format (BOM) of a cell output to the HMH13A→HMX12A of the ICLP.

[0670] FIG. 540 shows the format (COM) of a cell output to the HMH13A→HMX12A of the ICLP.

[0671] FIG. 541 shows the format (EOM) of a cell output to the HMH13A→HMX12A of the ICLP.

[0672] FIG. 542 shows the error flags shown in FIGS. 539 through 541.

[0673] FIG. 543 is a flowchart showing the check made when the ICLP receives a message.

[0674] FIG. 544 is a flowchart showing the message routing process in the ICLP.

[0675] FIG. 545 supplementarily describes the flowchart of the message routing process.

[0676] FIG. 546 is a block diagram showing the HMH11A.

[0677] FIG. 547 shows the external terminal unit of the HMH11A.

[0678] FIG. 548 shows the circuit (1) of the important part of the HMH11A.

[0679] FIG. 549 shows the circuit (2) of the important part of the HMH11A.

[0680] FIG. 550 shows the circuit (3) of the important part of the HMH11A.

[0681] FIG. 551 shows the circuit (4) of the important part of the HMH11A.

[0682] FIG. 552 shows the circuit (5) of the important part of the HMH11A.

[0683] FIG. 553 shows the circuit (6) of the important part of the HMH11A.

[0684] FIG. 554 shows the output timing of a main signal of the message check LSI of the HMH11A.

[0685] FIG. 555 shows the input/output timing of the cell data of the message check LSI of the HMH11A.

[0686] FIG. 556 shows the timing related to the cross-connection of systems (between NON ACT and RING 1, 2 OFF) in the message check LSI of the HMH11A.

[0687] FIG. 557 shows the timing related to the cross-connection of systems (between NON ACT and RING 1, 2 ON) in the message check LSI of the HMH11A.

[0688] FIG. 558 shows the timing of transmitting data from the SCTL to the message check LSI.

[0689] FIG. 559 shows the timing of transmitting data from the message check LSI to the SCTL.

[0690] FIG. 560 shows the initialization timing from the SCTL to the message check LSI.

[0691] FIG. 561 is a block diagram showing the HMH12A.

[0692] FIG. 562 is a flowchart showing the routing process of the HMH12A.

[0693] FIG. 563 is a flowchart showing the broadcast process of the HMH12A.

[0694] FIG. 564 is a flowchart (1) showing the copy control process of the HMH12A.

[0695] FIG. 565 is a flowchart (2) showing the copy control process of the HMH12A.

[0696] FIG. 566 is a flowchart showing the process of sending a pseueo EOM in the HMH12A.

[0697] FIG. 567 is a block diagram showing the HMH13A.

[0698] FIG. 568 shows the VC-SH LSI for controlling an output band and the circuit configuration near the LSI.

[0699] FIG. 569 shows the circuit configuration of the output MID acquiring unit.

[0700] FIG. 570 shows the configuration of the table used in an output MID acquisition process.

[0701] FIG. 571 is a flowchart showing the process of reserving an output VIC in the output MID acquisition unit.

[0702] FIG. 572 is a flowchart showing the timeout monitor process in the output MID acquisition unit.

[0703] FIG. 573 shows the format of reassigning a VPI/VCI in the HMH13A.

[0704] FIG. 574 shows the configuration of the hardware for executing the reassignment of a VPI/VCI in the HMH13A.

[0705] FIG. 575 shows the configuration of the circuit in the HMH13A for monitoring a fault between the circuit and the home system MH-COM.

[0706] FIG. 576 shows the configuration of the circuit in the HMH13A for monitoring a fault between the circuit and the mate system MH-COM.

[0707] FIG. 577 is a block diagram showing the outline of the function of the OGLP.

[0708] FIG. 578 is a block diagram showing the detailed function of the OGLP.

[0709] FIG. 579 is a block diagram showing the arrangement of the IC of the OGLP.

[0710] FIG. 580 shows the outline of the function of each block of the OGLP and the relationship between the OGLP and an error cell and maintenance cell.

[0711] FIG. 581 shows the error flag (FF) operated for each function block of the OGLP.

[0712] FIG. 582 shows the format of an input cell (BOM between MHs) from the SBMH to the HMH07A.

[0713] FIG. 583 shows the format of an input cell (BOM between SSMs) from the SBMH to the HMH07A.

[0714] FIG. 584 shows the format of an input cell (SIP BOM)from the SBMH to the HMH07A.

[0715] FIG. 585 shows the format of an input cell (SIP SSM) from the SBMH to the HMH07A.

[0716] FIG. 586 shows the format of an input cell (SIP COM) from the SBMH to the HMH07A.

[0717] FIG. 587 shows the format of an input cell (SIP EOM, EOM BETWEEN MHs) from the SBMH to the HMH07A.

[0718] FIG. 588 shows the format of an input cell (BOM between MHs) from another GWMH to the HMH07A.

[0719] FIG. 589 shows the format of an input cell (SSM between MHs) from another GWMH to the HMH07A.

[0720] FIG. 590 shows the format of an input cell (SIP BOM) from another GWMH to the HMH07A.

[0721] FIG. 591 shows the format of an input cell (SIP SSM) from another GWMH to the HMH07A.

[0722] FIG. 592 shows the format of an input cell (SIP COM) from another GWMH to the HMH07A.

[0723] FIG. 593 shows the format of an input cell (SIP EOM, EOM between MHs) from another GWMH to the HMH07A.

[0724] FIG. 594 shows the format of an input cell (BOM between MHs) from another GWMH to the HMH08A.

[0725] FIG. 595 shows the format of an input cell (SSM between MHs) from another GWMH to the HMH08A.

[0726] FIG. 596 shows the format of an input cell (SIP BOM) from another GWMH to the HMH08A.

[0727] FIG. 597 shows the format of an input cell (SIP SSM) from another GWMH to the HMH08A.

[0728] FIG. 598 shows the format of an input cell (SIP COM) from another GWMH to the HMH08A.

[0729] FIG. 599 shows the format of an input cell (SIP EOM, EOM between MHs) from another GWMH to the HMH08A.

[0730] FIG. 600 shows the format of an input cell (BOM between MHs) from another GWMH to the HMH09A.

[0731] FIG. 601 shows the format of an input cell (SSM between MHs) from another GWMH to the HMH09A.

[0732] FIG. 602 shows the format of an input cell (SIP BOM) from another GWMH to the HMH09A.

[0733] FIG. 603 shows the format of an input cell (SIP SSM) from another GWMH to the HMH09A.

[0734] FIG. 604 shows the format of an input cell (SIP COM) from another GWMH to the HMH09A.

[0735] FIG. 605 shows the format of an input cell (SIP EOM, EOM between MHs) from another GWMH to the HMH09A.

[0736] FIG. 606 shows the format of an input cell (BOM between MHs) from another GWMH to the HMH10A.

[0737] FIG. 607 shows the format of an input cell (SSM between MHs) from another GWMH to the HMH10A.

[0738] FIG. 608 shows the format of an input cell (SIP BOM) from another GWMH to the HMH10A.

[0739] FIG. 609 shows the format of an input cell (SIP SSM) from another GWMH to the HMH10A.

[0740] FIG. 610 shows the format of an input cell (SIP COM) from another GWMH to the HMH10A.

[0741] FIG. 611 shows the format of an input cell (SIP EOM, EOM between MHs) from another GWMH to the HMH10A.

[0742] FIG. 612 shows the data interface between the OGLP and LP-COM.

[0743] FIG. 613 shows the format of the cell (BOM between the MHs) for the interface with the LP-COM.

[0744] FIG. 614 shows the format of the cell (SSM between MHs) for the interface with the LP-COM.

[0745] FIG. 615 shows the format of the cell (SIP BOM) for the interface with the LP-COM.

[0746] FIG. 616 shows the format of the cell (SIP SSM) for the interface with the LP-COM.

[0747] FIG. 617 shows the format of the cell (SIP COM) for the interface with the LP-COM.

[0748] FIG. 618 shows the format of the cell (SIP EOM, EOM between MHs) for the interface with the LP-COM.

[0749] FIG. 619 shows the format of the output cell (BOM between MHs) from the HMH10A to the ICI.

[0750] FIG. 620 shows the format of the output cell (SIP BOM) from the HMH10A to the ICI.

[0751] FIG. 621 shows the format of the output cell (BOM between MHs) from the HMH10A to the ICI.

[0752] FIG. 622 shows the format of the output cell (SIP COM) from the HMH10A to the ICI.

[0753] FIG. 623 shows the format of the output cell (SIP EOM, EOM between MHs) from the HMH10A to the ICI.

[0754] FIG. 624 shows the format of the output cell (BOM between MHs) from the HMH10A to the ISSI.

[0755] FIG. 625 shows the format of the output cell (SIP BOM) from the HMH10A to the ISSI.

[0756] FIG. 626 shows the format of the output cell (SIP SSM) from the HMH10A to the ISSI.

[0757] FIG. 627 shows the format of the output cell (SIP COM) from the HMH10A to the ISSI.

[0758] FIG. 628 shows the format of the output cell (SIP EOM, EOM between MHs) from the HMH10A to the ISSI.

[0759] FIG. 629 is a flowchart showing the outgoing routing process in the GWMESH.

[0760] FIG. 630 is a flowchart showing the GA data transfer in the outgoing routing process in the GWMESH.

[0761] FIG. 631 shows an example (1) of a table used in each step of the flowcharts shown in FIGS. 629 and 630.

[0762] FIG. 632 shows an example (2) of a table used in each step of the flowcharts shown in FIGS. 629 and 630.

[0763] FIG. 633 shows an example (3) of a table used in each step of the flowcharts shown in FIGS. 629 and 630.

[0764] FIG. 634 shows the configuration (1) of the circuit of the HMH07A.

[0765] FIG. 635 shows the configuration (2) of the circuit of the HMH07A.

[0766] FIG. 636 shows the timing (1) of writing to the FIFO in the HMH07A.

[0767] FIG. 637 shows the timing (2) of writing to the FIFO in the HMH07A.

[0768] FIG. 638 is a time chart (1) of the signal processed by the HMH07A.

[0769] FIG. 639 is a time chart (2) of the signal processed by the HMH07A.

[0770] FIG. 640 is a time chart (3) of the signal processed by the HMH07A.

[0771] FIG. 641 shows the configuration (1) of the circuit of the HMH08A.

[0772] FIG. 642 shows the configuration (2) of the circuit of the HMH08A.

[0773] FIG. 643 shows the configuration of the circuit of the HMH09A.

[0774] FIG. 644 is a flowchart (write control) of the GA copy process in the HMH09A.

[0775] FIG. 645 is a flowchart (read control) of the GA copy process in the HMH09A.

[0776] FIG. 646 shows the configuration of the circuit of the HMH10A.

[0777] FIG. 647 shows the functions of each block of the HMH10A.

[0778] FIG. 648 is a block diagram showing the functions of connecting the parity check unit of the HMH10A to the units near the parity check unit.

[0779] FIG. 649 is a block diagram showing the functions of the MRI timeout unit of the HMH10A.

[0780] FIG. 650 is a block diagram showing the functions of the MID converting unit of the HMH10A.

[0781] FIG. 651 is a block diagram showing the functions of the cell delay unit of the HMH10A.

[0782] FIG. 652 is a block diagram showing the functions of the error cell discard unit of the HMH10A.

[0783] FIG. 653 is a block diagram showing the functions of the output band control unit of the HMH10A.

[0784] FIG. 654 shows the configuration of the circuit of the VC-SH LSI for restricting the output band and the configuration of the circuits of the unit near the VC-SH LSI.

[0785] FIG. 655 is a block diagram showing the functions of the format converting unit of the HMH10A.

[0786] FIG. 656 shows the process performed by the converting unit.

[0787] FIG. 657 is a block diagram showing the functions of the CRC-10 generating and assigning unit of the HMH10A.

[0788] FIG. 658 shows the operation of the CRC-10.

[0789] FIG. 659 is a block diagram showing the functions of the discard count unit of the HMH10A.

[0790] FIG. 660 is a block diagram of the HMX10A (EDMX/SMUX).

[0791] FIG. 661 is a block diagram of the HMX11A (SDMX/RMUX).

[0792] FIG. 662 is a block diagram of the HMX12A (VCC unit).

[0793] FIG. 663 is a block diagram of the HMX12A (scheduler unit).

[0794] FIG. 664 is a block diagram of the HSF05A.

[0795] FIG. 665 shows the clock system of the SBMESH.

[0796] FIG. 666 is a block diagram showing the functions of the HLM03A.

[0797] FIG. 667 shows the functions (1) of each block of the HLM03A.

[0798] FIG. 668 shows the functions (2) of each block of the HLM03A.

[0799] FIG. 669 shows the check made in the HLM03A.

[0800] FIG. 670 shows the conditions under which the checks are made in the HLM03A.

[0801] FIG. 671 shows the check items of the performance protocol monitor in the incoming unit and the process performed when an error occurs.

[0802] FIG. 672 is a time chart relating to the error notification in the incoming unit.

[0803] FIG. 673 shows each signal on the time chart shown in FIG. 672.

[0804] FIG. 674 shows the identification of segment types.

[0805] FIG. 675 is a time chart showing the process of an error analysis block.

[0806] FIG. 676 shows the check items of the performance protocol monitor in the outgoing unit and the process performed when an error occurs.

[0807] FIG. 677 is a time chart relating to the error notification in the outgoing unit.

[0808] FIG. 678 is a time chart showing the L2/3 individual error count process in the outgoing unit.

[0809] FIG. 679 is a time chart relating to the network data collection in the incoming unit.

[0810] FIG. 680 is a time chart showing the count value read/write relating to the network data collection in the incoming unit of the GWMESH.

[0811] FIG. 681 is a time chart showing the count value read/write relating to the network data collection in the outgoing unit of the GWMESH.

[0812] FIG. 682 shows the classification and procedure of the billing functions.

[0813] FIG. 683 shows the configuration and billing point of the switching system.

[0814] FIG. 684 shows the usage information generated in the LEC network relating to the SMDS between carriers.

[0815] FIG. 685 shows the SA, DA (SIP), DA (ICIP), and compressed carrier information memory of the billing unit of the GWMESH.

[0816] FIG. 686 shows the simplified billing memory.

[0817] FIG. 687 is a block diagram showing the functions of the HLP07A.

[0818] FIG. 688 shows the functions (1) of each block of the HLP07A.

[0819] FIG. 689 shows the functions (2) of each block of the HLP07A.

[0820] FIG. 690 shows the VPI/VCI of the intra-station communications cell.

[0821] FIG. 691 shows the operations performed when a fault is monitored in the MH-COM unit.

[0822] FIG. 692 shows the information in the header field of the cell output from the test cell generator TCG.

[0823] FIG. 693 shows an example (1) of a loopback test conducted using the test cell output from the test cell generator TCG.

[0824] FIG. 694 shows an example (2) of a loopback test conducted using the test cell output from the test cell generator TCG.

[0825] FIG. 695 shows the PVC test between the ICI/ISSI and GWMESH.

[0826] FIG. 696 shows the PVC test between the GWMESH and GWMESH/SBMESH.

[0827] FIG. 697 shows the PVC test between stations.

[0828] FIG. 698 shows the position of the BSGCSH and BSGC in the switching system according to the present invention.

[0829] FIG. 699 shows the terminal point of the intra-station LAPD communciations.

[0830] FIG. 700 shows the terminal point of the subscriber LAPD communications.

[0831] FIG. 701 shows the outline of the functions of the BSGCSH.

[0832] FIG. 702 shows the connection of the hardware between the BCPR-INF-BSGC.

[0833] FIG. 703 shows the control sequence between the BSGC and BCPR.

[0834] FIG. 704 shows the configuration of the intra-switch duplex device control hardware.

[0835] FIG. 705 shows the control model for the signaling signal transmitted from the terminal unit to the switch.

[0836] FIG. 706 shows the control model of the signaling signal transmitted from the switch to the terminal unit.

[0837] FIG. 707 shows the control model of the duplex device signal transmitted from the terminal unit to the switch.

[0838] FIG. 708 shows the control model of the duplex device signal transmitted from the switch to the terminal unit.

[0839] FIG. 709 shows the control model of the VPI/VCI.

[0840] FIG. 710 shows a list of assigning a VPI/VCI.

[0841] FIG. 711 shows the cell discarding function in the BSGC-COM.

[0842] FIG. 712 shows the state of the device of the BSGC.

[0843] FIG. 713 shows the frame format used in the LAPD communications to the subscriber terminal unit.

[0844] FIG. 714 shows the establishing procedure of the intra-station control communications link.

[0845] FIG. 715 shows the establishing procedure of the intra-station control communications link relating to the BRLC.

[0846] FIG. 716 shows the configuration of the program module in the BSGC.

[0847] FIG. 717 shows the configuration of the hardware relating to the INF.

[0848] FIG. 718 shows the bit configuration between the MM (main memory) and BSGC of the data DMA-transferred.

[0849] FIG. 719 shows the congestion control of the receiving system.

[0850] FIG. 720 shows a model of the number of signals processed in the BSGC.

[0851] FIG. 721 shows the initialize command and the format of the INF initial information setting table.

[0852] FIG. 722 shows the usage of a tag SIG/UL/TAGC in the communications in the SIFSH from the BSGC to the SIFSH.

[0853] FIG. 723 shows the usage of a tag SIG/UL/ADS1BLK/ADS1SEL in the communications in the SIFSH from the BSGC to the RMXSH.

[0854] FIG. 724 shows the usage of a tag SIG/UL/TAGC by the SIFSH in the communications from the BSGC to the SIFSH.

[0855] FIG. 725 shows the usage of a tag SIG/UL/TAGC by the BSGCSH in the communications from the ASSW to the BSGC.

[0856] FIG. 726 shows the configuration of the SAR-PDU of the protocol type 3 and the header field of the ATM cell storing the SAR-PDU.

[0857] FIG. 727 shows the SAR-PDU (CPAAL5-PDU) of the protocol type 5.

[0858] FIG. 728 shows the procedure of setting a VCC.

[0859] FIG. 729 shows the procedure of starting VCC copy.

[0860] FIG. 730 shows the procedure of stopping VCC copy.

[0861] FIG. 731 shows the fault range model.

[0862] FIG. 732 shows the method of detecting a BSGCSH-COM fault by the BSGC and of notifying the switching software of the fault.

[0863] FIG. 733 shows the detection point of a fault detected by the checker in the BSGC-COM in transmitting data from the BSGC to the BSGC-COM.

[0864] FIG. 734 shows the state in which a fault is detected in one of the fault points (a), (a)′, (b), and (b)′ shown in FIG. 733.

[0865] FIG. 735 shows the state in which a fault is detected in two of the fault points (a), (a)′, (b), and (b)′ shown in FIG. 733.

[0866] FIG. 736 shows the case in which a fault of a checker in the BSGC-COM is determined after the fault described in note 1 in FIG. 735 and the diagnostics is made.

[0867] FIG. 737 shows the case in which a fault of a checker in the BSGC-COM is determined after the fault described in note 2 in FIG. 735 and the diagnostics is made.

[0868] FIG. 738 shows the detection point of faults detected by the checker in the BSGC when data is transmitted from the BSGC-COM to the BSGC.

[0869] FIG. 739 shows the state in which a fault is detected in one of the fault points (a), (a)′, (b), and (b)′ shown in FIG. 733.

[0870] FIG. 740 shows the fault notification model.

[0871] FIG. 741 shows the case in which a fault of a checker in the BSGC-COM is determined after the fault described in note 3 in FIG. 740 and the diagnostics is made.

[0872] FIG. 742 shows the case in which a fault of a checker in the BSGC-COM is determined after the fault described in note 4 in FIG. 740 and the diagnostics is made.

[0873] FIG. 743 shows the fault notification model.

[0874] FIG. 744 shows the detailed fault factors.

[0875] FIG. 745 shows the accommodation of the BSGC MSCN.

[0876] FIG. 746 shows the detailed factors of the BSGC faults reported to the BCPR by the TM save.

[0877] FIG. 747 shows the detailed factors of the BSGC-COM faults reported by an MSCN detail read command.

[0878] FIG. 748 shows the sequence of detecting the faults in the BSGC-COM.

[0879] FIG. 749 shows the signalling cell format used when an I field is transferred as signaling information.

[0880] FIG. 750 shows the signalling cell format used when an MSD/MSCN is transferred as signaling information.

[0881] FIG. 751 shows the UI format.

[0882] FIG. 752 shows the definition of a common field in each device.

[0883] FIG. 753 is a block diagram (1) showing the functions of the BSGC-COM hardware.

[0884] FIG. 754 is a block diagram (1) showing the functions of the BSGC-COM hardware.

[0885] FIG. 755 is a block diagram (1) showing the functions of the BSGC-COM hardware.

[0886] FIG. 756 shows the functions of the package of the HMX00A in the BSGC-COM.

[0887] FIG. 757 shows the functions of the package of the HMX01A in the BSGC-COM.

[0888] FIG. 758 shows the functions of the package of the HSF00A/HSF04A in the BSGC-COM.

[0889] FIG. 759 shows the interface between the HMX00A package in the BSGC-COM and the SWMDX (HMX03A) package in the ASSWSH.

[0890] FIG. 760 shows the interface to the signal transferred from the SWMDX (HMX03A) in the ASSWSH to the HMX00A package in the BSGC-COM.

[0891] FIG. 761 shows the interface of a signal transferred between the HSF04A package in the BSGC-COM and the SWTIF (HNC00A) package in the ASSWSH.

[0892] FIG. 762 shows the daisy-chain connection of the BSGCSH.

[0893] FIG. 763 shows the configuration of the O & M cell loopback in the INS state of the BSGC and BSGC-COM.

[0894] FIG. 764 shows the logic of setting the loopback corresponding to the loopback configuration related to FIG. 763.

[0895] FIG. 765 shows the cell loopback configuration in the OUS state of the BSGC and BSGC-COM.

[0896] FIG. 766 shows the logic of setting the loopback corresponding to the loopback configuration at the loop point (1) shown in FIG. 765.

[0897] FIG. 767 shows the logic of setting the cell route when the cell is looped back at the loop point

[0898] FIG. 768 shows the logic of setting the VCC when the cell is looped back at the loop point (1).

[0899] FIG. 769 shows the logic of setting the loopback corresponding to the loopback configuration at the loop point (2) shown in FIG. 765.

[0900] FIG. 770 shows the configuration of the hardware of the BSGC.

[0901] FIG. 771 shows the outline of the hardware of the BSGC.

[0902] FIG. 772 shows the memory map of the BSGC.

[0903] FIG. 773 shows the I/O map of the BSGC.

[0904] FIG. 774 shows the BCPR access read/write.

[0905] FIG. 775 shows the transfer data pattern.

[0906] FIG. 776 shows the loop position in the diagnostics between the BSGC and BSGC-COM.

[0907] FIG. 777 shows the VCC read/write test state in the diagnostics made in the OUS state of the #1 system BSGC.

[0908] FIG. 778 shows the basic policy of the continuity test in the active system/standby system/OUS state in the BSGCSH.

[0909] FIG. 779 shows the cell-by-cell loopback position in the BSGCSH-COM.

[0910] FIG. 780 shows the configuration of the hardware of the TC stop function in the BSGC of the active system during the test.

[0911] FIG. 781 shows the signal transmission route from the BSGC to the duplex or simplex device.

[0912] FIG. 782 shows the signal receiving route from the duplex or simplex device to the BSGC.

[0913] FIG. 783 shows the format of the L2-PDU and L3-PDU.

[0914] FIG. 784 shows the table storing tag information and output MID using an input MID as a key.

[0915] FIG. 785 is a flowchart showing the process of retrieving tag information and output MID using an input MID as a key.

[0916] FIG. 786 shows the method of testing a loopback between stations according to the present invention.

[0917] FIG. 787 is a block diagram showing the configuration with which an inter-station loopback test shown in FIG. 786 is conducted.

[0918] FIG. 788 is a flowchart showing the algorithm limiting the faulty point according to the complaint from the subscriber.

[0919] FIG. 789 shows the configuration of the system using the SMDS.

[0920] FIG. 790 shows the transfer route (1) of the test message transmitted at the PVC test between the subscriber and the SMDS support module.

[0921] FIG. 791 shows the transfer route (2) of the test message transmitted at the PVC test between the subscriber and the SMDS support module.

[0922] FIG. 792 shows the position at which a test message is multiplexed in the SMDS support module.

[0923] FIG. 793 shows the position at which a test message is checked in the SMDS support module.

[0924] FIG. 794 shows the transfer route of a test message transmitted in the PVC test between SMDS support modules.

[0925] FIG. 795 is a block diagram showing the configuration of the SMDS support module provided with the test message generating unit and test message check unit.

[0926] FIG. 796 shows the format of the L3-PDU.

[0927] FIG. 797 shows the relationship between the L2-PDU and L3-PDU.

[0928] FIG. 798 is a flowchart of checking the payload length of the L2-PDU.

[0929] FIG. 799 is a flowchart of the BEtag check of the L3-PDU.

[0930] FIG. 800 is a flowchart of the BAsize check of the L3-PDU.

[0931] FIG. 801 shows the configuration of the circuit for making the L2-PDU payload length check, L3-PDU BEtag check, and L3-PDU BAsize check.

[0932] FIG. 802 shows the configuration of the system connected through a private line between connectionless processing servers.

[0933] FIG. 803 is a block diagram showing the function of the connectionless processing servers shown in FIG. 802 and the call processor used by the servers.

[0934] FIG. 804 shows the table managed by the connectionless processing servers shown in FIG. 802.

[0935] FIG. 805 is a flowchart showing the process of the system connected through the private line between the connectionless processing servers.

[0936] FIG. 806 shows another characteristic configuration according to the present invention.

[0937] FIG. 807 shows another characteristic configuration according to the present invention.

[0938] FIG. 808 shows the division of the main storage device and the control information format.

[0939] FIG. 809 shows the control information format.

[0940] FIG. 810 shows the configuration of the circuit of the TAGCMP 10 shown in FIG. 807.

[0941] FIG. 811 is a timing chart showing the operation of the TAGCMP 10.

[0942] FIG. 812 shows the configuration of the circuit of the ADRSDEC 9 shown in FIG. 807.

[0943] FIG. 813 is a timing chart showing the operation of the ADRSDEC 9.

[0944] FIG. 814 shows the configuration of the circuit of the ATMIF 6 shown in FIG. 807.

[0945] FIG. 815 is a timing chart showing the operation of the ATMIF 6.

[0946] FIG. 816 shows another characteristic configuration according to the present invention.

[0947] FIG. 817 shows another characteristic configuration (1) according to the present invention.

[0948] FIG. 818 shows another characteristic configuration (2) according to the present invention.

[0949] FIG. 819 shows another characteristic configuration according to the present invention.

[0950] FIG. 820 shows the memory map in the RAM 4 and 5.

[0951] FIG. 821 shows the configuration of the circuit of the CNTR unit shown in FIG. 819.

[0952] FIG. 822 shows the configuration of the circuit of the ADD 9.

[0953] FIG. 823 shows the configuration of the TG10 shown in FIG. 819.

[0954] FIG. 824 is a timing chart of the TG10.

[0955] FIG. 825 shows the configuration of the CNTR unit for processing priority levels.

[0956] FIG. 826 shows the configuration of the CNTR unit (shown in FIG. 819) for the DMUX unit.

[0957] FIG. 827 shows another characteristic configuration according to the present invention.

[0958] FIG. 828 shows the configuration (1) of the sending pattern selecting unit 4 shown in FIG. 827.

[0959] FIG. 829 shows the operations according to the embodiments shown in FIGS. 827 and 828.

[0960] FIG. 830 shows the configuration (2) of the sending pattern selecting unit 4 shown in FIG. 827.

[0961] FIG. 831 shows the operations according to the embodiments shown in FIGS. 827 and 830.

[0962] FIG. 832 shows the configuration of the switch for realizing the point-to-multipoint function. (a) indicated a trunk system; (b) indicates an input unit copy system; and (c) indicates an internal copy system.

[0963] FIG. 833 is a table showing the features of the three systems shown in FIG. 832.

[0964] FIG. 834 shows the configuration for realizing the point-to-multipoint connection using the internal copy system.

[0965] FIG. 835 shows the system or realizing the above described bit map without extending the cell length.

[0966] FIG. 836 shows the VPI/VCI decoding circuit.

[0967] FIG. 837 shows the configuration of a point-to-multipoint connection.

[0968] FIG. 838 shows the configuration of the buffer and output unit VCCT provided for each output line.

[0969] FIG. 839 is a table of the contents of the output unit VCCT set by the firmware according to the software settings.

[0970] FIG. 840 shows an example of a table on which an output VPI/VCI is set.

[0971] FIG. 841 is a flowchart explaining the process of the VCCT of the output unit.

[0972] FIG. 842 shows the configuration of the switching system whose switch is equipped with a VCCT at its entry point.

[0973] FIG. 843 shows the configuration of the switching system according to the present embodiment.

[0974] FIG. 844 shows the format of a cell in the switch.

[0975] FIG. 845 shows the configuration of the exchange station according to the present embodiment.

[0976] FIG. 846 shows an example of the configuration of the control information for a point-to-multipoint connection.

[0977] FIG. 847A shows the configuration of the buffer of a switch.

[0978] FIG. 847B shows an example of the switching bit map in the point-to-multipoint connection control information.

[0979] FIG. 848 shows another characteristic configuration of the present invention.

[0980] FIG. 849 shows an example in which the multicast function of the present embodiment is applied to the video distribution service.

[0981] FIG. 850 shows the configuration of the multicast device 30.

[0982] FIG. 851 shows the configuration of the system for communications among a plurality of communicators through a multiple communications trunk built in the exchange station.

[0983] FIG. 852 shows the configuration of the system for multiple subscriber communications using a multiple termination unit in the subscriber line.

[0984] FIG. 853 is a process flowchart showing the 3-subscriber communications service in the system shown in FIG. 851.

[0985] FIG. 854 is a flowchart showing the process of the multiple subscriber communications service in the system shown in FIG. 851.

[0986] FIG. 855 is a flowchart showing the process of the multiple subscriber communications service using a group identification number.

[0987] FIG. 856 shows the flowchart of the process in the 3-subscriber communications service in the system shown in FIG. 852.

[0988] FIG. 857 is a flowchart showing the multiple subscriber communications service in the system shown in FIG. 852.

[0989] FIG. 858 is a flowchart of the call waiting service in the system shown in FIG. 851.

[0990] FIG. 859 is a flowchart (1) of a call transfer service in the system shown in FIG. 851.

[0991] FIG. 860 is a flowchart (2) of a call transfer service in the system shown in FIG. 851.

[0992] FIG. 861 is a flowchart showing the point-to-multipoint connection service in the system shown in FIG. 851.

[0993] FIG. 862 is a flowchart of the call waiting service provided by the system shown in FIG. 852.

[0994] FIG. 863 is a flowchart (1) of the call transfer service provided by the system shown in FIG. 852.

[0995] FIG. 864 is a flowchart (2) of the call transfer service provided by the system shown in FIG. 852.

[0996] FIG. 865 is a flowchart of the point-to-multipoint connection service provided by the system shown in FIG. 852.

[0997] FIG. 866 shows the configuration of the ATM switch related to the present invention to solve the 18th problem.

[0998] FIG. 867 shows the characteristic configuration related to the present invention to solve the 18th problems.

[0999] FIG. 868 is a flowchart showing the normal line connecting process with the characteristic configuration related to the present invention to solve the 18th problems.

[1000] FIG. 869 is a flowchart showing the operations of the notifying process in the event of a failure on a device with the characteristic configuration related to the present invention to solve the 18th problems.

[1001] FIG. 870 is a flowchart (1) showing the operations of the automatic line connection switching process in the event of a failure on a device with the characteristic configuration related to the present invention to solve the 18th problems.

[1002] FIG. 871 is a flowchart (2) showing the operations of the automatic line connection switching process in the event of a failure on a device with the characteristic configuration related to the present invention to solve the 18th problems.

[1003] FIG. 872 shows practical examples of use state table 11, device service management table 12, and management information table 13.

[1004] FIG. 873 shows the operations of reassigning an idle band in a non-faulty line to a faulty band.

[1005] FIG. 874 shows the sequence of the processes of reassigning an idle band in a non-faulty line to a faulty band.

[1006] FIG. 875 shows the operations of physically switching a physical line containing a faulty band to a spare line.

[1007] FIG. 876 shows the sequence of the process of physically switching a physical line containing a faulty band to a spare line.

[1008] FIG. 877 shows the process of buffering the ATM cells in order of priority levels.

[1009] FIG. 878 shows an example of assigning priority levels.

[1010] FIG. 879 shows the configuration of the system in which a remote concentrator 1 is connected to a host switch 2 as the basic components of the present embodiment.

[1011] FIG. 880 shows the common principle of the ATM switch system related to the present embodiment.

[1012] FIG. 881 shows the position where the VCC table is accommodated for use by the upward path from the remote concentrator 1 to the host switch 2 in the system in which the remote concentrator 1 is connected to the host switch 2 (HOST 2) shown in FIG. 879.

[1013] FIG. 882 shows the position where the VCC table is accommodated for use by the downward path from the host switch 2 (HOST 2) to the remote concentrator 1 in the system in which the remote concentrator 1 is connected to the host switch 2 (HOST 2) shown in FIG. 879.

[1014] FIG. 883 is a flowchart showing the process of connecting a path contained in the first process example according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[1015] FIG. 884 shows examples of the normal VCC table and reassignment VCC table.

[1016] FIG. 885 is a flowchart showing the process of reassigning a path in the event of a failure contained in the first process example according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[1017] FIG. 886 shows the second process example (upward, before reassigning a path) of the path reassigning process in the event of a failure according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[1018] FIG. 887 shows the second process example (upward, after reassigning a path) of the path reassigning process in the event of a failure according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[1019] FIG. 888 the second process example (downward, before reassigning a path) of the path reassigning process in the event of a failure according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[1020] FIG. 889 the second process example (downward, after reassigning a path) of the path reassigning process in the event of a failure according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[1021] FIG. 890 shows the third process example (upward, before reassigning a path) of the path reassigning process in the event of a failure according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[1022] FIG. 891 shows the third process example (upward, after reassigning a path) of the path reassigning process in the event of a failure according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[1023] FIG. 892 shows the third process example (downward, before reassigning a path) of the path reassigning process in the event of a failure according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[1024] FIG. 893 shows the third process example (downward, after reassigning a path) of the path reassigning process in the event of a failure according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[1025] FIG. 894 shows the configuration of the embodiment of the VCC control device capable of quickly transferring VCC table data.

[1026] FIG. 895 shows the timing of accessing the VCC table through an input cell.

[1027] FIG. 896A shows the timing of accessing the VCC table through a VCC table.

[1028] FIG. 896B shows the timing of copying VCC table data between systems.

[1029] FIG. 897 shows the relationship between the L3-PDU and a cell.

[1030] FIG. 898 shows the conventional inter-station loopback test method.

[1031] FIG. 899 shows the configuration (1) of a common SMDS system.

[1032] FIG. 900 shows the configuration (2) of a common SMDS system.

[1033] FIG. 901 shows the method of realizing the conventional connectionless service.

[1034] FIG. 902 shows another conventional technology.

[1035] FIG. 903 shows another conventional technology.

[1036] FIG. 904 shows the configuration in which the BISDN terminal unit is connected to the BISDN switch.

[1037] FIG. 905 shows the configuration in which the SMDS terminal unit is connected to the SMDS switch.

[1038] FIG. 906 shows the configuration of the DS3 multiframe.

[1039] FIG. 907 shows the configuration of the ATM cell and L2-PDU cell.

[1040] FIG. 908 shows the configuration of the PLCP frame interfaced in the DS3 format.

[1041] FIG. 909 shows the restrictions related to the cycle stuff counter.

[1042] FIG. 910 shows the conventional circuit for transmitting a PLCP multiframe.

[1043] FIG. 911 is a timing chart showing the operation of the conventional transmission circuit of a PLCP multiframe.

[1044] FIG. 912 shows the configuration of a conventional multicast connection.

[1045] FIG. 913 shows the problems of the conventional technology in which lines are switched in physical line units when a failure occurs on the line itself.

EMBODIMENTS

Contents of the Embodiments

[1046] <Part 1> General Descriptions of Embodiments

[1047] 1. Outline of the system according to the present embodiment

[1048] 1.1. General Description

[1049] 1.2. Interface and Service provided by the present embodiment

[1050] 1.2.1. Subscriber Interfaces

[1051] 1.2.1.1. Optical Fiber Interface

[1052] 1.2.1.2. Metallic Interface

[1053] 1.2.2. Network Interface

[1054] 1.2.3. Services

[1055] 1.3. System Configuration

[1056] 1.3.1 Broadband Switch Architecture

[1057] 1.3.2. Switched Multi-megabit Data Service (SMDS)

[1058] 2. Explanation of Hardware according to the present embodiment

[1059] 2.1. ATM Network for small host

[1060] 2.1.1. ATM Subscriber Switch (ASSW)

[1061] 2.1.2. ASSW Subscriber and Network Interface

[1062] 2.1.2.1. Subscriber Interface Shelf (SIFSH)

[1063] 2.1.2.2. ATM DS-1 Shelf (ADS1SH)

[1064] 2.1.2.3. Fiber Interface Shelf (FIFSH)

[1065] 2.1.3. ASSW ATM Switch Module

[1066] 2.1.3.1. ATM Switching Shelf (ASSWSH)

[1067] 2.1.3.2. Daisy Chaining

[1068] 2.1.4. ASSW Other ATM Network Support Equipment and Test Cell Generation

[1069] 2.1.4.1. Subscriber Interface Shelf (SIFSH) for Loopback

[1070] 2.1.4.2. Subscriber Interface Shelf for Test Cell Generator Adapters

[1071] 2.1.5. ASSW Signaling Equipment

[1072] 2.1.6. SMDS Message Handler

[1073] 2.1.6.1. Subscriber Message Handler Shelf (SBMESH)

[1074] 2.1.6.2. Gateway Message Handler Shelf (GWMESH)

[1075] 2.2. Broadband Remote Switching Unit (BRSU)

[1076] 2.3. Broadband Remote Line Concentrator (BRLC)

[1077] 2.3.1. Subscriber Input Ports

[1078] 2.3.2. Umbilical Equipment

[1079] 2.3.3. Network Equipment

[1080] 3. Functions according to the Embodiment

[1081] 3.1. General Descriptions

[1082] 3.2. Host Switch

[1083] 3.3. ATM subscriber switch (ASSW)

[1084] 3.3.1. ATM Switch Module (ASM)

[1085] 3.3.2. Subscriber/Network Interface

[1086] 3.3.3. Broadband Signaling Controller (BSGC)

[1087] 3.3.4. Message Handler (SMDS)

[1088] 3.3.5. Broadband Call Processor (BCPR)

[1089] 3.3.6. Maintenance and Operation System (MOS)

[1090] 3.3.7. Operation and Maintenance Processor (OMP)

[1091] 3.3.8. System Integration Processor (SIP)

[1092] 3.4. Broadband Remote Line Concentrator (BRLC)

[1093] 3.5. Broadband Remote Switching Unit (BRSU)

[1094] 3.6. SMDS Implementation

[1095] 3.7. Traffic Control

[1096] 3.7.1. Call Acceptance Control

[1097] 3.7.2. User Parameter Control (UPC)

[1098] 3.7.3. Priority for Cell Routing

[1099] 3.8. Data Collection

[1100] 4. Others

[1101] <Part 2> DS3-SMDS Interface

[1102] 1. General Descriptions

[1103] 2. Explanation of Line Interface

[1104] 2.1. DS3 Line Interface

[1105] 2.1.1. Payload Mapping

[1106] 2.1.2. DS3 Frame Format

[1107] 3. PLCP Frame Format

[1108] 3.1. DS3 PLCP Frame format

[1109] 4. DS3-SMDS Interface L2-PDU Format

[1110] 4.1. DS3-SMDS L2-PDU Format

[1111] 4.2. Network Control Information

[1112] 4.3. Segment Type

[1113] 4.4. Message Identifier

[1114] 4.5. Segmentation Unit

[1115] 4.6. Payload Length

[1116] 4.7. Payload CRC

[1117] 5. Relationship between L2-PDU and ATM Cell

[1118] 6. DS3 Umbilical Link Format

[1119] 7. Hardware Configuration

[1120] 7.1. General Descriptions

[1121] 7.2. DS3 layer terminating function

[1122] 7.2.1. Process for line faults

[1123] 7.2.2. Detection and Recovery Condition of each alarm

[1124] 7.3. DS3-SMDS Layer Terminating Function

[1125] 7.3.1. Process for line faults

[1126] 7.3.2. Detection and Recovery Condition of each alarm

[1127] 7.4. L2-PDU Header Checking Function (HCS)

[1128] 7.5. L2-PDU Header Pattern Generating Function

[1129] 7.6. Distributed Queue Dual Bus (DQDB) Sequence Function

[1130] 7.7. DS3 Layer/PLCP Layer Performance Monitoring Function

[1131] 7.7.1. DS3 Layer

[1132] 7.7.2. DS3-PLCP Layer

[1133] 7.8. Received L2-PDU Data Converting Function (45 Mbps→156 Mbps)

[1134] 7.9. Transmitted L2-PDU Data Bit Rate Converting Function (156 Mbps→45 Mbps)

[1135] 7.10. Interfacing Function to SIFSH Common

[1136] 7.11. LAP Terminating Function of MSD/MSCN Information

[1137] 7.12. Multiplexing Function of DS3-SMDS L2-PDU Cell and LAP Cell

[1138] 7.13. Demultiplexing Function of DS3-SMDS L2-PDU Cell and LAP Cell

[1139] 7.14 Loopback Function of specified VPI/VCI

[1140] 7.14.1 Loopback Function of Cell provided with “0” bit

[1141] 7.14.2 Loopback Function of Cell provided with specific VCI/VCI

[1142] 7.15 MSCN Data Multiplexing Function

[1143] 7.16 MSD Data Dropper Function

[1144] 8. Maintenance Signal Driver (MSD) Interface

[1145] 8.1. MSD Information

[1146] 8.1.1. E-MSD Hardware Interface

[1147] 8.1.2. E-MSD Accommodation List of DS3-SMDS Interface

[1148] 8.2. Detailed Explanation of the E-MSD

[1149] 8.2.1. Hardware Reset

[1150] 8.2.2. Loopback

[1151] 8.2.3. Pseudo-fault Point

[1152] 8.2.4. AIS Transmission Point

[1153] 9. Maintenance Scanner (MSCN) Interface

[1154] 9.1.1. Hardware Interface for E-MSCN

[1155] 9.1.2. Detailed Explanation of E-MSCN

[1156] 9.2. E-MSCN Process in DS3-SMDS Interface

[1157] 9.2.1. SIFSH Common Interface Fault

[1158] 9.2.2. DS3-SMDS Interface Hardware Fault

[1159] 9.2.3. DS3-SMDS Interface Hardware Fault

[1160] 9.2.4. Faults in Microprocessor

[1161] 9.2.5. Fault in Timer

[1162] 9.2.6. DS3 Layer Alarm

[1163] 9.2.7. Performance Monitor Threshold Crossing Alert

[1164] 9.2.8. Cell Discards in the DS3-SMDS interface

[1165] 9.2.9. Diagnostic Result Report

[1166] 10. Simple LAP-D Protocol of DS3-SMDS interface

[1167] 10.1. Software Interface

[1168] 10.2. Hardware Interface

[1169] 10.3. Setting VPI/VCI

[1170] 10.4 Error Monitor

[1171] 10.5. AAL Interface

[1172] 10.5.1. SAR-PDU Format

[1173] 10.6. Function of AAL

[1174] 10.7 Error Monitor

[1175] 10.8. L2 Interface

[1176] 10.8.1. Functions of L2

[1177] 10.8.2. Frame Format

[1178] 10.8.3. Connection Setting Procedure

[1179] 10.8.4. Monitor of Link State

[1180] 10.8.5. Confirmation Procedure

[1181] 10.8.6. Monitor of Faults

[1182] 10.9. L3 Interface

[1183] 10.9.1. L3 frame Format

[1184] 10.9.2. Communications Procedure

[1185] 10.9.3. Control of Errors

[1186] 11. Management of the state of DS3-SMDS interface

[1187] 11.1. Initialization

[1188] 11.2. Blocking

[1189] 11.3. Setting In-Service

[1190] 11.4. Non-implementation

[1191] 11.5. Processes for faults

[1192] 11.5.1. Monitor of Faults

[1193] 11.5.2. Detection of faults

[1194] 11.5.3. Specifying a fault

[1195] 11.5.4. Monitor of Recovery

[1196] 11.6 Various Process Sequence

[1197] 12. Congestion Control of DS3-SMDS Interface Buffer

[1198] 13. Test and Maintenance

[1199] 13.1. Loopback Function of DS3-SMDS Interface

[1200] 13.1.1. Loopback Function of a cell with 0 bit added at tag area

[1201] 13.1.2. Loopback Function of All Cells

[1202] 13.1.3. Loopback Function of Cell having specific VPI/VCI

[1203] 13.1.4. Line Loopback Function

[1204] 13.2. Test Method

[1205] 13.2.1. DS3-SMDS Line Loopback Test

[1206] 13.2.1.1 Line loopback test at DSX-3

[1207] 13.2.1.2 Line loopback test at RLC

[1208] 13.2.2. Active system on-demand test

[1209] 13.2.3. PVC Path Circuit Test

[1210] 13.2.4. Tests and Diagnostics of DS3-SMDS interface

[1211] 13.2.4.1. ATM Cell Acceptability Test in DS3-SMDS interface

[1212] 13.2.4.2 Hardware normality confirmation test

[1213] 14. Fault Correction

[1214] 14.1. Fault detection point and notification system

[1215] 14.1.1. Contents of Faults

[1216] 14.1.2 OBP Fault

[1217] 14.1.3. OBP Fault in Individual Unit (DS3-SMDS interface)

[1218] 14.1.3.1. +5V OBP Fault

[1219] 14.1.3.2. −5.2V OBP Fault

[1220] 14.1.4. Package Missing Fault

[1221] 14.1.5. Fuse Disconnection Fault

[1222] 14.1.6. Package Error Insertion Fault

[1223] 14.1.7. DS3-SMDS Interface Individual Unit Package Fault

[1224] 15. Functions of each PCB

[1225] 15.1. Functions of each PCB

[1226] 15.1.1. Functions of HAF00A

[1227] 15.1.1.1. LAP Terminating Function for MSD/MSCN information

[1228] 15.1.1.2. Interfacing Function with SIFSH Common

[1229] 15.1.1.3. Multiplexing/demultiplexing function for DS3-SMDS L2-PDU cell and LAP cell

[1230] 15.1.1.4. Loopback Function for Cell assigned Specific VPI/VCI

[1231] 15.1.1.5. Multiplexing Function for MSCN Data

[1232] 15.1.1.6. MSD Data Dropper Function

[1233] 15.1.1.7. Active Control Function

[1234] 15.1.1.8. Microprocessor Interface Function

[1235] 15.1.2. Functions of HLP01A

[1236] 15.1.2.1. 156 Mbps→45 Mbps Data Conversion Function

[1237] 15.1.2.2. 45 Mpbs→156 Mbps Data Conversion Function

[1238] 15.1.2.3. DQDB Process Function

[1239] 14.1.3. Functions of HDT00A

[1240] 15.1.3.1. DS3 Layer Terminating Function

[1241] 15.1.3.2. DS3 PLCP Layer Terminating Function

[1242] 15.1.3.3. Received L2-PDU Header Check Function (HCS)

[1243] 15.1.3.4. L2-PDU Header Pattern Generating Function

[1244] 16. Firmware Interface

[1245] 16.1. General Descriptions

[1246] 16.2. Outline of Interface between Hardware and Firmware

[1247] <Part 3> SIFSH

[1248] 1. General Description

[1249] 1.1. Position of SIFSH in the System

[1250] 1.2. Outline of Functions

[1251] 2. Shelf Configuration

[1252] 2.1. Configuration

[1253] 2.1.1. SIFCOM

[1254] 2.1.2. Individual Unit

[1255] 2.2. Power Source System

[1256] 2.2.1. −48V/CG

[1257] 2.2.2. SAB/SABG

[1258] 2.2.3. +5V/E

[1259] 3. Physical Interface

[1260] 3.1. Switch Interface

[1261] 3.1.1. 622 Mbps Cell Highway Interface

[1262] 3.1.2. System Switch Signal

[1263] 3.2. SYNSH Interface

[1264] 3.3. Individual Unit Interface

[1265] 3.3.1. 156 Mbps cell highway interface

[1266] 3.3.1.1. Upward 156 Mbps Cell Highway Interface

[1267] 3.3.1.2. Downward 156 Mbps Cell Highway Interface

[1268] 3.3.2. E-MSD/E-MSCN Highway Interface

[1269] 3.3.2.1. System Control

[1270] 3.3.2.2. Physical Specification

[1271] 3.3.2.3. Logical Specification

[1272] 3.3.2.3.1. Individual Unit Receiving Specification

[1273] 3.3.2.3.2. Frame Synchronization

[1274] 3.3.2.3.3. Pilot 0/1 Signal Check (detection of stack in EMSD highway)

[1275] 3.3.2.3.4. Twice Reading Process

[1276] 3.3.2.3.5. Individual Unit Sending Specification

[1277] 3.3.2.3.6 Fault Detection

[1278] 3.4. Clock Interface

[1279] 4. Software Interface

[1280] 4.1. Outline

[1281] 4.2. Layer Structure in Intra-station Control Communications

[1282] 4.2.1. ATM Layer Cell Format

[1283] 4.2.2. SAR-PDU Format

[1284] 4.2.3. LAP-D Format (layer 2)

[1285] 5. Allocation of Tag

[1286] 6. Functions

[1287] 6.1. MUX

[1288] 6.1.1. Outline

[1289] 6.1.2. Configuration of MUX

[1290] 6.1.3. Multiplexing Control System

[1291] 6.1.4. Monitor of Buffer

[1292] 6.1.5. Write Control

[1293] 6.1.6. Abnormal Write Process

[1294] 6.1.6.1. Too small cell length

[1295] 6.1.6.2. Too long cell length

[1296] 6.1.7. Read Control

[1297] 6.1.8. Abnormal Read Process

[1298] 6.1.9. Buffer Congestion Control

[1299] 6.2. DMUX

[1300] 6.2.1. Outline

[1301] 6.2.2. Functions

[1302] 6.2.3. Dynamic Tag Matching

[1303] 6.2.4. Monitor of Buffer

[1304] 6.3. VCC

[1305] 6.3.1. Position of VCC

[1306] 6.3.2. Capacity of VCC Memory

[1307] 6.3.3. Inter-System VCC Copy

[1308] 6.3.3.1. Object

[1309] 6.3.3.2. Timing of Inter-system Copy

[1310] 6.3.3.3. Copy Object Information

[1311] 6.3.3.4. Procedure for INS process

[1312] 6.3.3.5. Copy Disable Report

[1313] 6.3.4. Relationship between VCC and SMDS Service

[1314] 6.4. Signaling Process (EGCLAD)

[1315] 6.4.1. Outline

[1316] 6.4.2. Functions of EGCLAD LSI

[1317] 6.4.2.1. ATM Header Check Functions

[1318] 6.4.2.2. ATM Header Inserting Function

[1319] 7. Test and Maintenance

[1320] 7.1. Monitor of Quality of Path using MC

[1321] 7.2. Circuit Test of Test Cell through TCG

[1322] 8. Fault Correcting Process

[1323] 8.1. Fault Detection Point and Notification System

[1324] 8.1.1. Fault Mode

[1325] 8.1.2. OBP Fault

[1326] 8.1.2.1. Individual Unit OBP Fault

[1327] 8.1.2.2. OBP Fault in SIFCOM

[1328] 8.1.3. Package Missing Fault

[1329] 8.1.3.1. Individual Unit Package Missing Fault

[1330] 8.1.3.2. SIFCOM Package Missing Fault

[1331] 8.1.3.3. Power Package Missing Fault

[1332] 8.1.4. Fuse Disconnection Fault

[1333] 8.1.4.1. Individual Unit Fuse Disconnection Fault

[1334] 8.1.4.2. SIFCOM Fuse Disconnection Fault

[1335] 8.1.5. SIFCOM Package Front Connector Missing Fault

[1336] 8.1.5.1. 50-core Coaxial Flat Cable Fault

[1337] 8.1.5.2. 50-core TD Bus Cable Fault

[1338] 8.1.6. Erroneous Package Insertion Fault

[1339] 8.1.7. Individual Unit Package Fault

[1340] 8.1.8. SIFCOM Package Fault

[1341] 9. Line Protection (N+1 System)

[1342] 9.1. Outline of N+1 Protection System

[1343] 9.2. Line Reassignment Sequence

[1344] 9.3. Setting VCC in Standby Line

[1345] 9.4. Switch to Standby Line

[1346] 9.5. Switch Command

[1347] <Part 4>

[1348] 1. Outline

[1349] 1.1. Summary of Function

[1350] 2. Configuration of Device

[1351] 2.1. Configuration of Device

[1352] 3. Interface

[1353] 3.1. Communication Line System

[1354] 3.2. Control System

[1355] 3.3. Clock System

[1356] 3.4 Inter-block Interface in ASSWSH-A

[1357] 4. Detailed Function

[1358] 5. Traffic Control

[1359] 5.1. Cell Discard Class

[1360] 5.2. Congestion Control

[1361] 5.2.1. Congestion Control in SWMX

[1362] 5.2.2. Congestion Control in SWMDX

[1363] 5.2.3. Cell Discard

[1364] 5.3. Traffic Measure Process

[1365] 6. Function of Firmware

[1366] 6.1. INFA Interface

[1367] 6.2. Intra-device hard Interface

[1368] 6.3. Fault Correcting Process

[1369] 6.3.1. Fault Detection

[1370] 6.3.2. Message Box

[1371] 6.4. Self-diagnosis

[1372] 7. Maintenance

[1373] 7.1. Software-hardware interface

[1374] 7.2. Operations

[1375] 7.2.1. State Transition

[1376] 7.2.2. Loading HMX03A

[1377] 7.3. Fault Correcting Process

[1378] <Part 5>

[1379] 1. General Descriptions

[1380] 1.1. Summary

[1381] 1.1.1. Positioning in System

[1382] 1.1.2. Outline of SMDS Data Process

[1383] 1.2. System Configuration

[1384] 1.3. Redundant Configuration

[1385] 2. Process Method

[1386] 2.1. Configuration of Message Handler (MH) Network

[1387] 2.2. Routing System

[1388] 2.3. VPI/VCI and MID Assigning Method

[1389] 2.3.1. VPI/VCI Assigning Method

[1390] 2.3.2. MID Assigning Method

[1391] 2.4. Group Address

[1392] 2.5. Multiplexing

[1393] 2.6. Outline of Functions

[1394] 3. SMLP

[1395] 3.1. Outline of Processes

[1396] 3.2. Configuration

[1397] 3.3. Correspondence between Each Function Block and Error Flag

[1398] 3.4. Process in each Block

[1399] 4. RMLP

[1400] 4.1. Outline of Process

[1401] 4.2. Configuration

[1402] 4.2.1. PVC Test

[1403] 4.2.2. MSCN

[1404] 4.2.3. MSD

[1405] 4.2.4. Correspondence between each Function Block and

[1406] 4.2.5. Data Interface between RMLP and LPCOM

[1407] 4.3. HMH00A

[1408] 4.3.1. Selection of cross-connection

[1409] 4.3.2. Timing Generator

[1410] 4.3.3. Address Filter

[1411] 4.4.1. Test Cell Multiplexing R and 9MG

[1412] 4.4.2. MID Check

[1413] 4.4.3. SN Check

[1414] 4.4.4. Encapsulation

[1415] 4.4.5. Error Edit I

[1416] 4.4.6. RMID Acquisition

[1417] 4.4.7. MRI Timeout Check

[1418] 4.4.8. GA copy

[1419] 4.4.9. SNI Available

[1420] 4.4.10 Error Edit II

[1421] 4.4.11 SA Check

[1422] 4.5. HMH04A

[1423] 4.5.1. SA Screening

[1424] 4.6. HMH02A.

[1425] 4.6.1. Outline of Configuration

[1426] 4.6.2. Outline of Functions

[1427] 4.6.3. Outline of Interface I/F

[1428] 4.6.4. Detailed Explanation

[1429] 5. MH-COM Unit

[1430] 5.1. General Descriptions

[1431] 5.2. RDMX/SMUX Function (HMX10A)

[1432] 5.3. SDMX/RMUX Function (HMX11A)

[1433] 5.4. VCC Function/Test Cell Multiplexing Function/Scheduling Function (HMX12A)

[1434] 5.4.1. VCC Function

[1435] 5.4.2. Test Cell Multiplexing Function

[1436] 5.4.3. Schedule Function (multiplex-LSI control)

[1437] 5.5. LAP Terminating/Starting Clock Distribution (HSF05A)

[1438] 5.5.1. LAP Terminating/Starting Process

[1439] 5.5.2. Distribution of Clock

[1440] 6. Protocol Performance Monitor

[1441] 6.1. Outline

[1442] 6.2. Layer 2 Protocol Performance Monitor

[1443] 6.3. Layer-3 Protocol Performance Monitor

[1444] 6.4. Protocol Performance Monitor in Ingress Unit

[1445] 6.4.1. Process System

[1446] 6.4.2. Detailed Process

[1447] 6.5. Protocol Performance Monitor in Egress Unit

[1448] 6.5.1. Process System

[1449] 6.5.2. Details of Processes

[1450] 7. Network Data Correction

[1451] 7.1. General Descriptions

[1452] 7.2. Network Data Correction Parameter

[1453] 7.3. Network Data Correction in Ingress Unit

[1454] 7.3.1. Process System

[1455] 7.3.2. Details of Processes

[1456] 7.4. Network Data Correction

[1457] 7.4.1. Process System

[1458] 7.4.2. Explanation of Process

[1459] 8. Billing Function

[1460] 8.1. General Descriptions

[1461] 8.2. Billing Process

[1462] 8.3. Checking Function

[1463] 9. LPCOM unit (INF interface unit)

[1464] 9.1. General Descriptions

[1465] 9.2. Outline of Functions

[1466] 9.3. INF Interface Control Procedure

[1467] 9.3.1. INF Interface Control

[1468] 9.3.2. IPF Interface Interruption Control

[1469] 9.4. SMLP/RMLP Control

[1470] 10. Various interfaces

[1471] 10.1. General Descriptions

[1472] 11. Software Interface

[1473] 11.1 Initialization

[1474] 11.1.1. Initialization of MH-COM

[1475] 11.1.2 Initialization of LP unit

[1476] 11.2 INS Process (In-service Process)

[1477] 11.2.1 INS Process of MH-COM

[1478] 11.2.2. INS Process in LP

[1479] 11.3 Fault Monitor and System Switch

[1480] 11.3.1 Fault Monitor of MH-COM

[1481] 11.3.2 MH-COM Fault Reporting and Processing Sequence

[1482] 11.3.3 Fault in Communications through INF with LP

[1483] 11.3.4 Fault detected in MSCN of LP

[1484] 11.3.5 Health Check of LP

[1485] 11.3.6 System Switch

[1486] 11.4 Test and Diagnostics

[1487] 11.4.1 Test using TCG

[1488] 11.4.2 Loopback Test in SBMESH

[1489] 11.4.3 PVC Test between SNI-SBMESH

[1490] 11.4.4 MESH-MH PVC test

[1491] 11.4.5 PVC Test Result Check

[1492] 11.4.6 Diagnostics of MH-COM

[1493] 11.4.7 Diagnostics of LP

[1494] 11.5 MSCN

[1495] 11.5.1 MSCN of MH-COM

[1496] 11.5.2 MSCN of LP

[1497] 11.6 MSD

[1498] 11.6.1 MSD of HM-COM

[1499] 11.6.2 MSD of LP

[1500] 11.7 Billing and Statistic Processes

[1501] 11.7.1 General Descriptions

[1502] 11.7.2 Billing process

[1503] 11.7.3. Protocol Performance Monitor Process

[1504] 11.7.4. Network Data Collection Process

[1505] 11.7.5. Various Cell Number Process

[1506] <Part 6> GWMESH

[1507] 1. General Descriptions

[1508] 1.1 Summary

[1509] 1.1.1 Position in System

[1510] 1.2 System Configuration

[1511] 1.3 Redundant Configuration

[1512] 2. Process Method

[1513] 2.1 Network Configuration

[1514] 2.2 Routing system

[1515] 2.3 Group Address Process

[1516] 2.4. Load Splitting

[1517] 2.4.1 Features of Load Splitting

[1518] 2.4.2. Key Generation

[1519] 2.4.3 Key Assignment

[1520] 3. ICLP

[1521] 3.1 Summary of Process

[1522] 3.2 Configuration

[1523] 3.3 Correspondence between each function block and error flag

[1524] 3.4. ICLP Input/Output Format

[1525] 3.5 ICLP Process Flow

[1526] 3.6 PKG Block

[1527] 3.6.1 HMH11A

[1528] 3.6.2 HMH12A

[1529] 3.6.3 HMH13A

[1530] 4. OGLP

[1531] 4.1 Summary of Process

[1532] 4.2 Configuration

[1533] 4.3 Correspondence between each function block and error flag

[1534] 4.4 Cell Format

[1535] 4.5 Process Flow

[1536] 4.6 PKG Block

[1537] 4.6.1 HMH07A

[1538] 4.6.2 HMH08A

[1539] 4.6.3 HMH09A

[1540] 4.6.4 HMH10A

[1541] 5. MH-COM unit

[1542] 5.1 General Descriptions

[1543] 5.2 HMX10A

[1544] 5.3 HMX11A

[1545] 5.4 HMX12A

[1546] 5.5 HSF05A

[1547] 6. Protocol Performance Monitor

[1548] 6.1 General Descriptions

[1549] 6.2 L2 Protocol Performance Monitor

[1550] 6.3 L3 protocol performance monitor

[1551] 6.4 Protocol Performance Monitor in Incoming Unit

[1552] 6.4.1 Processing Method

[1553] 6.4.2 Detailed Process

[1554] 6.5 Protocol Performance Monitor in Outgoing Unit

[1555] 6.5.1 Process Method

[1556] 6.5.2 Detailed Processes

[1557] 7. Network Data Collection

[1558] 7.1 General Descriptions

[1559] 7.2 Network Data Collection Parameter

[1560] 7.3 Network Data Collection in Incoming Unit

[1561] 7.3.1 Process System

[1562] 7.3.2 Detailed Process

[1563] 7.4 Network Data Collection in the outgoing unit

[1564] 7.4.1 In the above described network data collection

[1565] 7.4.2 Detailed Processes

[1566] 8. Billing

[1567] 8.1 Data Generation

[1568] 8.2 Data Aggregation

[1569] 9. LP-COM (INF)

[1570] 9.1 General Descriptions

[1571] 9.2 Outline of Functions

[1572] 9.3 INF Interface Control Unit

[1573] 9.3.1 INF Interface Control

[1574] 9.3.2 INF Interface Interruption Control

[1575] 9.4 Controlling ICLP/OGLP

[1576] 10. Software Interface

[1577] 10.1 Initialization

[1578] 10.1.1 Initialization of MH-COM

[1579] 10.1.2 Initialization of LP

[1580] 10.2 INS Process

[1581] 10.2.1 INS Process of MH-COM

[1582] 10.2.2 INS Process of LP

[1583] 10.3 Switching Systems

[1584] 10.3.1 Switching systems in MH-COM

[1585] 10.3.2 Switching systems in LP

[1586] 10.4 Fault Monitor

[1587] 10.4.1 Fault Monitor in MH-COM

[1588] 10.4.2 Fault Monitor relating to INF Communications

[1589] 10.5 Test and Diagnostics

[1590] 10.5.1 Test using TCG

[1591] 10.5.2 PVC Test between ICI/ISSI and GWMESH

[1592] 10.5.3 SBMESH/GEMESH—GWMESH PVC Test

[1593] 10.5.4 Inter-station Test

[1594] 10.5.5 Test Functions of Each Unit

[1595] 10.5.6 Self-diagnostics

[1596] <Part 7> BSGCSH

[1597] 1. General Descriptions

[1598] 1.1 Positions of BSGCSH and BSGC in Switch System

[1599] 1.2 Sharing Functions of BSGC

[1600] 1.2.1 Functions of INF

[1601] 1.2.2 Functions of LAPD

[1602] 1.2.3 Intra-station Control Communications Link

[1603] 1.2.4 Interface with ATM Switch

[1604] 1.2.5 Meta-signaling Communications

[1605] 1.3 Number and Assignment Condition of BSGC Port

[1606] 1.3.1 Maximum Number of Ports

[1607] 1.3.2 Required Number of Ports

[1608] 1.3.3 Transfer Speed between BSGC and Other Devices

[1609] 1.3.4 Throughput of BSGC and Port Assignment Condition

[1610] 2. Outline of Functions of BSGCSH

[1611] 2.1 Specification

[1612] 2.2 Higher Order Interface (INF interface)

[1613] 2.2.1 Hardware Configuration under Control of INF

[1614] 2.2.2 INF Interface Control Procedure

[1615] 2.3 Switch Interface (CARP and VCC Interface)

[1616] 2.3.1 Hardware Configuration for controlling intra-switch duplex device

[1617] 2.3.2 Intra-switch Signal Control

[1618] 2.3.2.1 Signaling Control Model (including simplex device)

[1619] 2.3.2.2 Duplex Device Signal Control Model (for common unit)

[1620] 2.3.3 Intra-station Control Communications VPI/VCI

[1621] 2.3.4 Cell Discard System in BSGC-COM

[1622] 2.4 BSGC Device Control

[1623] 2.4.1 State of Device in BSGC

[1624] 2.4.2 BSGC Fault Correcting Process

[1625] 2.5 Communications Control

[1626] 2.5.1 Difference from Q.922

[1627] 2.5.2 Intra-station LAPD Communications (intra-station control communications)

[1628] 2.6 Diagnostic Functions

[1629] 2.6.1 Diagnosis Object Items

[1630] 2.6.2 Intra-station Duplex Device Diagnostic Communications Link

[1631] 2.7 Configuration of Program Module

[1632] 3. INF interface

[1633] 3.1 Hardware Configuration

[1634] 3.2 DMA Bit Configuration

[1635] 3.2.1 Bit Configuration of DMA Transfer Data

[1636] 3.3 INF Control Procedure

[1637] 3.3.1 Command Queue and Status Queue

[1638] 3.3.2 Conflict at command activation and status activation

[1639] 3.3.3 Congestion Control

[1640] 3.3.3.1 Receiving System Congestion Control

[1641] 3.3.3.2 Sending System Congestion Control

[1642] 3.3.3.3. BSGC Congestion Control

[1643] 3.4 Initializing INF

[1644] 3.5 INF Priority Control

[1645] 4. Switch Interface

[1646] 4.1 Assigning Tag

[1647] 4.1.1 Concept of Assigning Tag

[1648] 4.1.2 Assigning Tag in communications from BSGC to ASSW

[1649] 4.1.3 Assigning Tag in communications from ASSW to BSGC

[1650] 4.2 CARP Control Procedure

[1651] 4.2.1 Frame Format

[1652] 4.2.2 Functions of CARP LSI

[1653] 4.2.3 Statistic Functions

[1654] 4.3 VCC Setting Procedure and VCC Copying Procedure

[1655] 5. BSGC Device Controlling Procedure

[1656] 5.1 BSGC Fault Monitor

[1657] 5.1.1 Faulty portion detected in BSGCSH

[1658] 5.1.2 System Management at Fault Occurrence

[1659] 5.1.3 Report to BSGC

[1660] 5.1.4 Recovery Monitor

[1661] 5.1.4.1 Recovery monitor by BSGC

[1662] 5.1.4.2 Recovery Monitor in Switch Software

[1663] 5.1.5 Fault to be detected by the BSGC Hardware

[1664] 5.1.6 Fault detected by BSGC Firmware

[1665] 5.1.6.1 Fault in BSGC-COM (excluding faults of the BSGC)

[1666] 5.1.6.2 Fault in Standby System BSGC

[1667] 5.2 TM Save System

[1668] 5.3 Statistic Function

[1669] 6. Communications Control

[1670] 6.1 Control of Intra-Station Control Communications

[1671] 6.1.1 Signaling Cell Format

[1672] 6.1.2 Difference from Revised LAPD

[1673] 7. BSGC-COM

[1674] 7.1 Hardware Configuration of BSGC-COM

[1675] 7.2 Explanation of Blocks showing Functions of BSGC-COM

[1676] 7.3 Switch Interface

[1677] 7.4 SWTIF Interface

[1678] 7.5 Configuration of Higher/Lower Shelf of BSGCSH

[1679] 7.6 BSGC-COM Loopback Configuration

[1680] 7.6.1 Cell Loopback of BSGC and BSGC-COM in INS State

[1681] 7.6.2 Cell Loopback in OUS State for BSGC and BSGC-COM

[1682] 8. Duplex Process Control

[1683] 8.1 Hardware Configuration

[1684] 8.1.1 BSGC Hardware Configuration

[1685] 8.1.2 General Description of the BSGC Hardware

[1686] 8.1.3 Memory Map

[1687] 8.1.4 I/O Map

[1688] 9. Maintenance and Operation

[1689] 9.1 Diagnostics Functions

[1690] 9.1.1 Diagnostics Object Items

[1691] 9.1.2 Details

[1692] 9.1.2.1 INF Interface BCPR Access Read/Write Diagnosis

[1693] 9.1.2.2 INF Interface DMA Transfer Read/Write Diagnosis

[1694] 9.1.2.3 Diagnostics of Functions in BSGC

[1695] 9.1.2.4 Diagnostics between BSGC and BSGC-COM

[1696] 9.1.2.5 VCC Memory Test

[1697] 9.1.2.6 LAP Link Establishment Test between BSGC and another Device

[1698] 9.2 TC Function

[1699] 9.2.1 Basic Policy

[1700] 9.2.2 Cell-by-Cell Loopback (OUS state)

[1701] 9.2.3 Cell-by-Cell Loopback Position

[1702] 9.2.4 TC Stop Function in Active System BSGC during OUS Test

[1703] <Part 8> Configuration and Function, etc. relating to Present Invention

Description of the Preferred Embodiments

[1704] The embodiments of the present invention are described below in detail by referring to the attached drawings.

[1705] <Part 1>

[1706] The general configuration and function of the present embodiment is described in Part 1.

1. OUTLINE OF THE SYSTEM ACCORDING TO THE PRESENT EMBODIMENT

1.1. General Description

[1707] FIG. 1 shows the configuration of the entire broadband switching system according to the present embodiment. Connected to a broadband host switch 1 are a subscriber terminal equipment, a broadband remote line concentrator 2, a broadband remote switching unit 3, and the like. A customer premises equipment 4 is connected to these units. With this configuration, structured is an economical broadband switching system.

1.2. Interface and Service Provided by the Present Embodiment

[1708] Listed below are various interfaces according to the present embodiment.

[1709] 1.2.1. Subscriber Interfaces

[1710] 1.2.1.1. Optical Fiber Interface

[1711] 156 Mbps interface for providing a user network interface (UNI) of a broadband service integrated digital network (B-ISDN)

[1712] 622 Mbps interface for providing an UNI of the B-ISDN

[1713] 1.2.1.2. Metallic Interface

[1714] 1.5 Mbps Interface for providing a subscriber network interface (SNI) of switched multi-megabit data services (SMDS), frame relay, circuit emulation, etc.

[1715] 45 Mbps interface for providing an UNI of a B-ISDN, SNIs of an SMDS, frame relay, circuit emulation, etc.

[1716] 1.2.2. Network Interface

[1717] 622 Mbps optical fiber interface for providing a network node interface (NNI) of a B-ISDN

[1718] 156 Mbps optical fiber interface for providing an NNI of a B-ISDN

[1719] 45 Mbps metallic interface for providing an NNI of a B-ISDN, SMDS, frame relay, etc.

[1720] 1.5 Mbps metallic interface for providing an NNI of a frame relay

[1721] 1.2.3. Services

[1722] A broadband switching system according to the present embodiment provides the following services.

[1723] Connected ATM High-speed Data Service

[1724] Connectionless High-speed Data Service based on the switched multimegabit data service (SMDS)

[1725] Frame relay service

[1726] Circuit Emulation Service

1.3. System Configuration

[1727] Described below is the system configuration according to the present embodiment

[1728] 1.3.1 Broadband Switch Architecture

[1729] FIG. 2 shows a variation of the broadband switching system according to the present embodiment.

[1730] The basic configuration of the broadband switch refers to an ATM subscriber switch (ASSW) module. The ASSW module comprises a 10 Gbps (gigabit/second) ATM switching module having a redundant configuration; a duplex switch processor; various subscriber interfaces; and network interfaces. A single ASSW module can be assigned as a stand-alone broadband switch.

[1731] An ATM interconnection switch (AISW) is effective as a large capacity switch provided with the capacity larger than that of a single ASSW. To configure a large-scale office, a number of ASSW modules are interconnected through an AISW so that a capacity of 160 Gbps can be realized. With a large-scale configuration in which a number of ASSW modules are interconnected through an AISW, one or more ASSWs can be located remotely to make it function as broadband remote switching device (BRSU) capable of providing complete services.

[1732] The ASSW can also function as host switch to a broadband remote line concentrator (BRLC).

[1733] 1.3.2. Switched Multi-megabit Data Service (SMDS) FIG. 3 shows a system for realizing an SMDS using a broadband switch according to the present embodiment.

[1734] Two typical types of interfaces—OC-3C and DSI/DS3—can be used as subscriber network interfaces (SNI). The OC-3C is a 156-Mbps optical fiber interface while the DSI/DS3 is a 1.5-Mbps/45 Mbps metallic interface. The optical fiber interface allows the subscriber line to be shared between the SMDS subscriber equipment and other B-ISDN equipments. The metallic interface is designed to be dedicated to the SMDS. The broadband switching system according to the present embodiment can directly support an SMDS subscriber network interface.

[1735] Although the SMDS is well applicable to the ATM (the cell format of the SMDS is similar to that of the ATM), the SMDS uses a special message handler called an SMDS message handler (SMDS-MH). The SMDS-MH provides various SMDS-oriented services, e.g., address screening, message routing, group addressing (point to multi-point connection), illegal message checking, etc. Since the SMDS is a connectionless service, the SMDS-MH provides various services for each message and for each cell. Because it is featured by its high-speed process, most services are provided through hardware rather than software.

2. EXPLANATION OF HARDWARE ACCORDING TO THE PRESENT EMBODIMENT

2.1. ATM Network for Small Host

[1736] FIG. 4 shows the configuration of the typical hardware of the broadband switching system according to the present embodiment. FIG. 4 actually shows an ATM network for a small host.

[1737] 2.1.1. ATM Subscriber Switch (ASSW)

[1738] The ASSW provides ports (subscriber interfaces) for various types of subscribers and network interfaces. The subscriber interfaces include subscriber-network interfaces (SNI) in the SMDS, user network interfaces (UNI) in the frame relay, and B-ISDN ATM UNI. The network interfaces include network—network interfaces (NNI) in the frame relays, SMDS, and B-ISDN, and the interexchange carrier interface (ICI) and interswiching system interface (ISSI) in the SMDS. The subscriber interface can also be applied to a circuit emulation.

[1739] FIG. 5 shows the configuration of a port.

[1740] 2.1.2. ASSW Subscriber and Network Interface

[1741] The subscriber and network interfaces are configured and provided in several types of equipment shelves. The shelves include the ATM DS-I shelf (ADSISH), the subscriber interface shelf (SIFSH), and the fiber interface Shelf (FIFSH).

[1742] 2.1.2.1. Subscriber Interface Shelf (SIFSH)

[1743] FIG. 6 shows the configuration of the subscriber interface shelf (SIFSH).

[1744] The subscriber interface shelf (SIFSH) provides necessary power supplies, common cards, and mounting slots to accept up to eight DS3 or OC-3C interface cards of various types. These includes the ATM OC-3C card group (OC3CPG), the ATM DS-3 card group (ADS3PG), the frame relay DS-3 card group (FDS3PG), the circuit emulation DS-3 card group (CDS3PG), and the ADS1SH interface card (ADSINF). The ATM DS-3 card provides both ATM and SMDS interface.

[1745] The ATM OC-3C card group (OC3CPG) provides for ATM cell-switching of information received from ATM facilities via B-ISDN UNI.

[1746] The DS-3 card groups are similar in function to the DS-1 card groups for use in the ADS1SH, except that they provide for operation at the DS-3 rate, rather than the DS-1 rate.

[1747] The SIFSH is also capable of handling the ADS1SH interface card (ADSINF). Each pair of ADSINF cards interface with 4 ADS1SH shelves. A total of 16 ADS1SH shelves may be interfaced per SIFSH. Since each of these ADS1SHs handles 8 DS-1 ports, and 2 ADS1SH shelves can be daisy-chained as described later, 256 DS-1 cards may be handles by a port serving a pair of SIFSHs.

[1748] 2.1.2.2. ATM DS-1 Shelf (ADS1SH)

[1749] FIG. 7 shows the connection of the ADS1SH to the SIFSH.

[1750] The ATM DS-1 shelf (ADS1SH) accommodates a variety of DS-1 interface cards. These include a frame relay DS-1 card group (FDSIPG), an SMDS DS-1 card group (SDS1PG), and a circuit emulation DS-1 card group (CDS1PG).

[1751] The frame relay DS-1 card group provides for segmenting a long frame relay message into individual ATM cells and associating a virtual call identifier with each cell along with the necessary tags associated with cell switching. The card group also receives cells from the ATM fabric and reassembles them into a frame relay format. This adaptation process is referred to as segmentation and reassembly. It permits ATM cell switching techniques to be applied to frame relay traffic.

[1752] The SMDS DS-1 card group provides similar functions. The task provides data as a series of cell-sized data units.

[1753] The circuit emulation DS-1 card group provides for continuous cell adaptation to accept the information from a channel used for full-period traffic. It also breaks it into a series of ATM cells to prepare it for switching through the ATM network. The circuit emulation card group also provides for timing recovery where the signal leaves the network.

[1754] The ADS1SH shelf provides necessary power supplies, common cards, and mounting slots to accept any mix of up to 8 of the 3 DS-1 card types. The output from the shelf is extended to the ADS1SH interface cards (ADSINF) mounted on the subscriber interface shelf (SIFSH). (Refer to FIG. 7).

[1755] 2.1.2.3. Fiber Interface Shelf (FIFSH)

[1756] The fiber interface shelf (FIFSH) provides necessary power supplies and mounting slits to accept up to four OC-12C interfaces. Each interface consists of an ATM OC-12C card group (OC12PG) and a pair of fiber interface card groups (FIFCPG).

[1757] 2.1.3. ASSW ATM Switch Module

[1758] The ATM switch module is implemented as a fabric with a maximum capability of 10 Gbps. It provides for up to 16 ports for ingress and egress of traffic. The switching fabric is implemented in 2 separate portions for upward and downward switching. The forward traffic from subscriber and network ports is presented to the 16 ports on the network provided for upward directed traffic. The return traffic is received from the various subscriber and network interfaces to the ASSW. Some of the network ports are used by the service circuits, providing support to common signaling to the network and message handling for SMDS. FIG. 8 shows an example of the configuration of the network based on the ASSW.

[1759] 2.1.3.1. ATM Switching Shelf (ASSWSH)

[1760] The ATM switching shelf (ASSWSH) houses the entire ATM switching network and its associated power supplies. The switching network is implemented as a 4×4 non-blocking switch providing 10 Gbps. Each of the four 2.5 Gbps ports on the network has 4 associated cell routing multiplexer cards. This provides a total of sixteen 622 Mbps inputs to the network.

[1761] The ATM switch module is always implemented in the same 4×4 size.

[1762] Pairs of multiplexer cards to support each of the 4 network ports may be equipped individually. Each pair of multiplexer cards provides for 4 network ports.

[1763] The shelf also contains 2 pairs of common cards, a pair of cell clock generator cards (CELCLK) for timing, and a pair of parallel ATM interface cards (PIAINF) for connection to the processing equipment.

[1764] 2.1.3.2. Daisy Chaining

[1765] The above described shelves serving subscriber and network interfaces can be connected to the ATM switching network with a single shelf connected to each of the 16 ports on the switch. If a shelf does not provide a full load of 622 Mbps, then it can be daisy-chained to another shelf to develop the load. Daisy-chaining is the process of connecting the first shelf to the switch port, then connecting a second shelf to the first. Two SIFSH shelves may be daisy-chained as shown in FIG. 3-2. These arrangements permit up to 32 shelves to be connected to the 16 input ports to the network.

[1766] 2.1.4. ASSW Other ATM Network Support Equipment and Test Cell Generation

[1767] The traffic from the upward switch fabric may be connected to the downward switch in one of two ways. This can be done with loop-back circuits or by connection to an ATM Interconnection switch (AISW). The loop-back arrangement supports any intra-ASSW connections. Inter-ASSW connections are supported by connections through the AISW.

[1768] 2.1.4.1. Subscriber Interface Shelf (SIFSH) for Loopback

[1769] FIG. 9 shows the configuration of the loop-back of the SIFSH.

[1770] The SIFSH contains up to 8 loop-back card groups (LOOPPGA) to connect up to eight 156 Mbps outlets from the upward network to 8 of the 156 Mbps inlets on the downward network. The shelf also includes the necessary power equipment to support the loop-back cards. Loop-back card group of 622 Mb/s is also available in the future. This may be necessary if a service with bandwidth of larger than 156 Mb/s is introduced.

[1771] 2.1.4.2. Subscriber Interface Shelf for Test Cell Generator Adapters

[1772] FIG. 10 shows the configuration of the test cell generator connected to the SIFSH.

[1773] As shown in FIG. 10, the SIFSHs can also contain test cell generator adapters (TCGADPs) that are used for testing. These TCGADPs are contained in SIFSHs that are located on both ingress and egress.

[1774] The SIFSH of the ASSW. The test cell generator (TCG) is located in the test cell generator shelf (TCGSH) as shown in FIG. 10.

[1775] 2.1.5. ASSW Signaling Equipment

[1776] Each of the port equipment shelves on the system has an associated microprocessor. The broadband signaling controller shelf (BSGCSH) provides for signaling between the broadband call processor (BCPR), various network port microprocessors and for B-ISDN UNI signaling.

[1777] FIG. 11 shows the configuration of the BSGCSH. This shelf is always provided. It provides power supplies, common cards and mounting slots of up to 6 broadband signaling controller card groups (BSGCPGA). The BSGC in the BSGCSH is connected, through an periodical interface type A (INFA) and a periodical interface type T (INFT), to the system bus (BCPR bus) to which the BCPR is connected.

[1778] 2.1.6. SMDS Message Handler

[1779] There are two different types of SMDS message handling equipment, one to support the signaling requirements for subscriber SNI ports, and another to support the signaling for ICI and ISSI trunk ports.

[1780] 2.1.6.1. Subscriber Message Handler Shelf (SBMESH)

[1781] The subscriber message handler shelf (SBMESH) provides for message handling from the SMDS subscriber SNI ports. The shelf is provided whenever any SMDS subscriber SNIs exist as ports on the ASSW or any of the associated BRLCs, or when SMDS traffic is carried over ATM UNI facilities from customer-located terminal adapters.

[1782] Each SBMESH shelf can serve a mixture of DS-1 and DS-3 facilities, up to the capacity of the shelf. The shelf can handle an SMDS information rate of 102 Mbps, where the maximum information rate for DS-3 is 1.17 Mbps. A shelf also can handle up to 32 SNIs. On this basis, a given shelf can handle up to 3 DS-3s or 32 DS-1s. In addition to these restrictions, a switching network is limited to 622 of traffic per port.

[1783] The system permits up to 4 SBMESH shelves to be daisy-chained to a network inlet. If the network is exclusively loaded with SMDS DS-1s, then a network port equipped with 4 daisy-chained SBMESHs can handle up to 12 DS-3s or 128 DS-1s, or a mixture of these two types. If the SMDS ports and traffic for the ASSW exceeds the capacity of a single message handler group, then another port, or several ports, can be chosen to provide more message handling equipment.

[1784] 2.1.6.2. Gateway Message Handler Shelf (GWMESH)

[1785] The gateway message handler shelf (GWMESH) provides message processing and signaling functions for SMDS ICI and ISSI ports on the ASSW.

[1786] Each GWMESH is subject to the same limitations as for the SBMESH shelf. When the SMDS ICI or ISSI are equipped as DS-3s, running at full capacity, then the practical limitation for a GWMESH is 3 DS-3 ICIs and/or ISSIS. When the SMDS ICI or ISSI are equipped as fully utilized OC-3Cs, a message handler shelf must be dedicated to serving the single OC-3C. The system permits up to 4 GWMESH shelves to be daisy-chained to the same inlet. If the requirement exceeds the capability for a single message handler group, then an additional port or ports may be similarly equipped.

[1787] In an office with a small requirement for SMDS, one or more SBMESHs can be daisy-chained with one or more GWMESHs, as long as the per-shelf limits are not exceeded, and the overall traffic does not exceed 622 Mbps. This sort of engineering arrangement is useful in minimizing the port usage for this function.

2.2. Broadband Remote Switching Unit (BRSU)

[1788] FIG. 12 shows the major hardware components of a BRSU. The components of the BRSU are the same as those of the ASSW in the host switch.

2.3. Broadband Remote Line Concentrator (BRLC)

[1789] FIG. 13 shows the major hardware components of a BRLC.

[1790] When it is necessary to provide subscriber interfaces at a location remote from an ASSW, a broadband remote line concentrator (BRLC) can be used.

[1791] The BRLC subtends from the ASSW and is where switching functions are performed.

[1792] The BRLC essentially aggregates the traffic from a cluster of customers and delivers it to the ASSW (where it is connected via one or more umbilicals). The BRLC can either be engineered for full availability or traffic can be concentrated.

[1793] The BRLC consists of the same type of subscriber and network connecting input port equipments as the ASSW. There is no call processor, but there is some common equipment to replace the network between the ports and the umbilicals.

[1794] FIG. 14 shows the connections in the BRLC.

[1795] 2.3.1. Subscriber Input Ports

[1796] The subscriber interfaces are connected to the ports on the BRLC. These ports are implemented by means of several types of equipment shelves. They include the same ATM DS-1 shelf (ADS1SH), and the subscriber interface shelf (SIFSH), that are implemented in the ASSW. The fiber interface shelf (FIFSH) is not used in the BRLC because the maximum capacity of the entire BRLC is 622 Bbps.

[1797] The ATM DS-1 shelf (ADS1SH) houses various types of DS-1 interface card groups. These include a frame relay DS-1 card group (FDSIPG), an SMDS DS-1 card group (SDS1PG), and a circuit emulation card group (CDS1PG). The ADS1SH is described in 2.1.2.2.

[1798] The subscriber interface shelf (SIFSH) houses various network interface cards. The SIFSH accepts ATM OC-3C card groups, various DS-3 cards, or ATM DS-1 shelf interface cards (ADSINF). The SIFSH is described in 2.1.2.1.

[1799] 2.3.2. Umbilical Equipment

[1800] The umbilicals between the BRLC and its serving ASSW can be equipped as DS-3 facilities using ADS3PGA card groups or as OC-3Cs using OC3PGA card groups. The umbilical can also be provided as a single OC-12C using an OC12PGA card group. Since the BRLC is limited to 622 Mbps, the maximum requirement is for 1 OC-12C, or 4 OC-3Cs. The maximum arrangement for DS-3s provides 12 DS-3 facilities and handles nearly 611 Mbps. All of the umbilicals from any given BRLC must be connected to the same ASSW.

[1801] When DS-3 or OC-3 cards are used, the first 4 cards can be mounted in reserved slots in the RMXSH as a minimum cost arrangement. If the number exceeds 4, then a SIFSH can be added to mount an additional 8 cards. If an OC-12C is desired, then a FIFSH shelf can be used. The SIFSH and FIFSH are described above.

[1802] 2.3.3. Network Equipment

[1803] The BRLC does not have a network or the ASSW. As a result, network switching shelves and synchronization shelves are not required. However, various equipment shelves serving subscriber ports and umbilicals expect to interface to a network equipment and expect certain functions in the network equipment. For this reason, the BRLC requires a shelf of equipment to stand in place of the network. This function is performed by the RMXSH shelf.

[1804] The remote multiplex shelf (RMXSH) provides network substitution and also functions as multiplexer. It accepts the ATM from the subscriber interface shelves and multiplexes it to various umbilicals that have been provided. The shelf also established and handles the timing for the multiplexing function.

[1805] The RMXSH shelf provides the clock circuits and multiplex equipment to perform these functions. The shelf is always equipped with a pair of remote multiplex timing generator card group (RMXTPG), a pair of remote multiplex highway card groups (RMXHPG), and a pair of remote multiplex controller card groups (RMXCPG).

3. FUNCTIONS ACCORDING TO THE EMBODIMENT

3.1. General Descriptions

[1806] In this section, the functionality of the broadband switching system components are explained. These components are classified into the following four categories.

[1807] Host switch

[1808] remote switching unit (BRSU)

[1809] Broadband remote line concentrator (BRLC)

[1810] Customer premises equipment

3.2. Host Switch

[1811] The host switch is composed of the following components.

[1812] ATM subscriber switch (ASSW)

[1813] ATM interconnection switch (AISW)

[1814] Broadband main processor (BMPR)

[1815] Maintenance and operation subsystem (MOS)

[1816] Optical ring bus

[1817] The host switch is further classified into the following two types.

[1818] Small host switch

[1819] Large host switch

[1820] FIG. 15 shows the configuration of a small host switch and a large host switch. The ASSW is the basic building block of the broadband host switch. The small host switch is composed of one ASSW, BMPR, and MOS. The large host switch is composed of multiple ASSWs, an AISW, BMPR, and an MOS. The AISW interconnects multiple ASSWs in the large host switch. Migration from the small host switch to the large host switch is possible without interruption of service.

[1821] The optical ring bus is used when a broadband switching system and a narrowband switching system are integrated into a single system.

[1822] The present embodiment mainly relates to small host switches.

3.3. ATM Subscriber Switch (ASSW)

[1823] An ATM switch (ASSW) is a basic component of a broadband switching system. FIG. 16 shows the configuration of the ASSW. The ASSW a throughput capacity of 10 Gbps and is composed of the following components.

[1824] ATM switch module (ASM)

[1825] Subscriber/network interface

[1826] Broadband signaling controller (BSGC)

[1827] SMDS message handler (SMDS-MH)

[1828] Broadband call processor (BCPR)

[1829] 3.3.1. ATM Switch Module (ASM)

[1830] The ATM switch module (ASM) of a broadband switch is composed of a one-stage or multi-stage self-routing module (SRM). The SRM is composed of an N×N switching matrix with a link speed of 2.5 Gb/s. FIG. 17 shows the principle of the SRM. The ATM cell fed into the SRM is routed to an output port according to the tag attached to each cell.

[1831] FIG. 18 shows the configuration of a 4×4 SRM used in the ASSW. in the 4×4 SRM, cells are switched between four input ports and four output ports. The SRM is composed of a specially designed Bi-CMOS very large scale integrated circuit (VLSI) which includes the use of a 2×2 switch matrix. Each cross point has 2.5 Gb/s cell switching capability.

[1832] The principle of cell switching is explained as follows by referring to an example of cell switching from input HW0 to output HW2.

[1833] Each cell is attached with a tag.

[1834] Assume that a cell entering from HW0 is attached with a tag 2. Each switching element checks the tag value and switches only the cell with a tag value equal to the output port number (in this example, only SW02). If multiple cells are to be output to one output port, an access control mechanism avoids the conflict of cells by using a buffer in each cross point.

[1835] FIG. 19 shows the position of a virtual channel identifier converter (VCC). A tag is attached to a cell by the VCC located in a peripheral equipment such as a subscriber/network interface. The VCC specifies a tag value for each cell. Tag values are set according to the software table at the call set up phase of a switched connection, or the set up phase of a semi-permanent connection.

[1836] Tag information is also used in a demultiplexer. The tag specifies the output port of the demultiplexer in the ATM switch module and the peripheral equipment.

[1837] FIG. 20 shows the configuration of the ATM switch module of the ASSW. The ATM switch module of ASSW is composed of two separate 4×4 SRMs for upward and downward switching. The interface with peripheral equipment, e.g. subscriber/network interface, broadband signaling controller (BSGC), SMDS message handler (SMDS-MH), etc. is 622 Mb/s. All subscriber/network interfaces are accommodated in one side of the ATM switch module. On the other side of the ATM switch module are the loopback links, which route the intra-ASSW traffic. When the AISW is introduced, the interface with AISW replaces the loopback link.

[1838] 3.3.2. Subscriber/Network Interface

[1839] FIG. 21 shows the configuration of the subscriber interface (SNI) and network interface (ICI/ISSI) of the present embodiment. As shown in FIG. 21, the subscriber/network interfaces are classified depending on the interface speed.

[1840] High speed: 622 Mbps optical interface

[1841] Middle speed: 156 Mbps optical interface and 45 Mbps metallic interface

[1842] Low speed: 1.5 Mbps metallic interface

[1843] A different shelf is used for each of the above 3 interfaces. The low speed interface is multiplexed once onto an 8 Mbps link and then accommodated in the middle speed shelf. In the case of a middle speed shelf, up to two shelves can be daisy-chained for traffic congestion. The shelf for subscriber interface and network interface is common, so both interfaces can be accommodated in the same shelf. However, since these shelves perform traffic concentration, separate shelves must be used for subscriber and network interfaces if the subscriber/network interfaces require different grades of services.

[1844] The subscriber/network interface is classified into the following four types of services.

[1845] B-ISDN (ATM)

[1846] SMDS

[1847] Frame relay

[1848] Circuit emulation

[1849] A different interface card is used for each of these services, but the shelf is common for all services. The cards for the subscriber side and the network side are also different except circuit emulation.

[1850] 3.3.3. Broadband Signaling Controller (BSGC)

[1851] The broadband signaling controller (BSGC) is a high level data link procedure (HDLC) handler with the ATM interface. FIG. 22 shows the position of the BSGC in the ASSW. The BSGC is controlled by a broadband call processor (BCPR) through an interface (INF) and provides a link access procedure D-channel (LAPD) or a CCS7 signaling. The BSGC controls the communications between the BCPR and the broadband remote line concentrator (BRLC), and also controls the internal communications between the BCPR and the SNI interface.

[1852] 3.3.4. Message Handler (SMDS)

[1853] The SMDS message handler (SMDS-MH) provides various SMDS-oriented functions such as address screening, message routing, group addressing (point to point communications), illegal message checking, billing, data collection, etc. FIG. 23 shows the position of the SMDS-MH in the ASSW. The following two types of message handlers are used in the present embodiment.

[1854] Subscriber message handler (SBMH)

[1855] Gateway message handler (GWMH)

[1856] The SBMH processes messages for the SNI. The GWMH processes messages for the inter-switch interface of the ICI and ISSI.

[1857] 3.3.5. Broadband Call Processor (BCPR)

[1858] FIG. 24 shows the configuration of a broadband call processor (BCPR). The BCPR controls calls for all SNIs. The BCPR includes each of the following units.

[1859] CPU

[1860] Main memory

[1861] Ethernet interface

[1862] INF

[1863] The Ethernet interface is used for communications between the BCPR and the broadband main processor (BMPR). The INF provides an interface between each of various equipments in the ASSW such as the ATM switch module, BSGC, SMDS-MH, etc. and the BCPR.

[1864] 3.3.6. Maintenance and Operation System (MOS)

[1865] A maintenance and operation system (MOS) performs various maintenance and operation tasks. FIG. 25 shows the configuration of the MOS. The MOD includes the following units.

[1866] Alarm panel unit

[1867] Alarm control unit

[1868] Operation and Maintenance processor

[1869] In the system with only the broadband switching capability, the MOS is directly connected to the BMPR through the Ethernet interface, and provides operation and maintenance functions in cooperation with the BMPR. In the system with both narrowband and broadband switching capabilities, the MOS is connected to the broadband switching system and narrowband switching system through the optical ring bus and provides operation and maintenance functions in cooperation with the BMPR of the broadband switching system and the MPR of the narrowband switching system.

[1870] 3.3.7. Operation and Maintenance Processor (OMP)

[1871] An Operations and maintenance processor (OMP) is a front-end processor according to the present embodiment. In addition to providing system supervision/control and testing of lines and trunks, the OMP connects some of the operations systems (OS) to the present system. The OMP hardware components (refer to FIG. 26) are as follows.

[1872] CPU (including memory), disk drives, and a floppy disk drive

[1873] CRT display (used as a graphical user interface (GUI)

[1874] Keyboard

[1875] Mouse

[1876] Hard disk

[1877] Cartridge tape drive

[1878] Asynchronous communications server

[1879] Printer

[1880] X.25 interface

[1881] 3.3.8. System Integration Processor (SIP)

[1882] A system integration processor (SIP) is used when connecting an operations and maintenance processor (OMP) to an optical ring bus. When connected to the optical ring bus through the SIP, the OMP can be used to maintain different applications (narrowband, broadband, etc.).

3.4. Broadband Remote Line Concentrator (BRLC)

[1883] FIG. 27 shows the configuration of the broadband remote line concentrator (BRLC). The BRLC is used to provide subscriber interface at a location remote from the host switch. The BRLC provides traffic concentration only; local switching is not provided. The network interface consists of the umbilical with host switch. Note that the BRLC does not provide standalone (SA) capability if the umbilical is cut.

3.5. Broadband Remote Switching Unit (BRSU)

[1884] FIG. 28 shows the configuration of the broadband remote switching unit (BRSU). The BRSU provides the subscriber interface, network interface, and switching functions at a location remote from the host switch. The BRSU can be controlled only from the large size host switch with the ATM interconnection switch (AISW). The operation and maintenance functions are mainly provided by the host switch, but limited functions are also provided locally. The BRSU provides the same subscriber/network interface as the host switch. The umbilical to the host is similar to the BRLC. However, if the umbilical is cut, the BRSU can operate as a standalone unit and continue to provide intra-switching services.

3.6. SMDS Implementation

[1885] A switched multi-megabit data service (SMDS) is a connectionless high-speed packet data service. FIG. 29 shows the equipment relating to the SMDS. The SMDS traffic is processed by the DS1/DS3 interface unit and the SMDS message handler unit.

[1886] DS1/DS3 Interface Unit

[1887] Termination of level 1 (physical layer) of subscriber interface/network interface

[1888] Termination of ATM layer of SNI level 2

[1889] Performance monitor

[1890] Message Handler

[1891] Termination of SAR of SNI level 2

[1892] SNI level 3 functions (format check, address screening, routing, flow control)

[1893] Data collection (Network traffic management, network data collection, billing)

[1894] The SMDS can be also provided over the B-ISDN (ATM) subscriber interface through the terminal adapter. In this case, the functions of the DS1/DS2 interface are provided by the terminal adapter.

[1895] FIG. 30 shows the protocol of the layer-structure SNI. The SMDS adopts the layer structure shown in FIG. 31. FIG. 32 shows the routing of cells in an SMDS system.

[1896] The flow control is carried out in the following two points.

[1897] User parameter control (UPC) in the DS1/DS3 interface unit

[1898] Traffic shaping at the gateway message handler (GWMH).

3.7. Traffic Control

[1899] Traffic control is realized by the following mechanism.

[1900] Call acceptance control

[1901] Usage control

[1902] Priority in cell routing

[1903] 3.7.1. Call Acceptance Control

[1904] To assure the required quality of a service, such as cell loss and cell delay, the system manages the bandwidth and checks the bandwidth required by each call at the call acceptance stage. The call is processed by peak rate and average rate of the call and the required quality of the service.

[1905] The bandwidth in the system is managed for each virtual path at the following three points.

[1906] Subscriber interface

[1907] Network interface

[1908] 622 Mbps in the system

[1909] The capacity of the above described virtual path is managed in the following two areas.

[1910] Band for each call class (W1): band assigned and managed for each call class

[1911] Common band (W2): band assigned and managed independently of call class

[1912] The W2 area is used for the calls overflowed from W1 and the calls not covered by the W1.

[1913] 3.7.2. User Parameter Control (UPC)

[1914] The user parameter control (UPC) manages the actual traffic of each call. If cells violating the declared rate are detected, then the system discards them or attaches a violation tag.

[1915] The UPC is carried out for a virtual channel (VC), virtual path (VP) or both of them. For subscriber lines, the UPC is carried out for each VC at the subscriber interface part. For the cells violating the declared value, the following action is taken.

[1916] B-ISDN: assigning a tag indicating discard or violation of a declared value

[1917] SMDS: discarding

[1918] In the network equipment (i.e. interface with another switch or BRSU/BRLC), the UPC is carried out for each VP (or VC) at the network interface part.

[1919] 3.7.3. Priority for Cell Routing

[1920] Priority control of cell routing is carried out in various buffers of the multiplexer/demultiplexer and ATM switch module in the system. The control is realized in one queue using two thresholds as follows.

[1921] Threshold for discarding unimportant subscriber's cell

[1922] Threshold for discarding cells with CLP (cell loss priority)=1

3.8. Data Collection

[1923] The system according to the present embodiment collects the following data.

[1924] Automatic Message Accounting (AMA) data

[1925] Performance monitoring data

[1926] Network traffic management data

[1927] Network data collection (NDC) data

[1928] For example, the AMD data is stored in the storage device in the BMPR or SIP and transferred to the OS.

[1929] The performance monitoring data is collected at intervals of 15 minutes or 24 hours. The data is stored in the storage device and transferred to the OS through the OMP at a request from the OS.

[1930] Network traffic data is used for detection and notification of congestion, and is collected if the congestion level exceeds a predetermined threshold level. It is also collected at predetermined intervals (5-minute intervals) and transmitted to the OS at real time through the OMP.

[1931] The NDC data is used for a long-term prediction. The data is stored in the storage unit of the BMPR through the OMP when required by the OS.

4. OTHERS

[1932] The following parts 2 through 7 in the general configuration of the above described present embodiment describe in detail the DS3-SMDS interface (DS3), SIFSH, ASSWSH, SBMESH, GWMESH, and BSGCSH. Part 8 describes the configuration and functions particularly related to the present invention. The DS1-SMDS interface (DS1) is similar to the DS3-SMDS interface in basic functions, only different in transmission speed. Therefore, the detail descriptions are omitted here.

[1933] [0008]

[1934] <Part 2>

[1935] In part 2, the DS3-SMDS is described in detail.

1. GENERAL DESCRIPTIONS

[1936] The DS3-SMDS interface is used as a circuit interface in providing SMDS services via a DS3 transmission line. It is also used as an interface in providing an umbilical link by connecting a broadband remote line concentrator (BRLC).

[1937] A switched megabit data service (SMDS) is a kind of high-speed connectionless data service, and is to be processed as a service of exchanging data by connecting LANs.

[1938] FIG. 33 shows an outline of the configuration of the system mainly comprising the DS3-SMDS interface. FIG. 34 shows the configuration in which a BRLC 2 is connected to a switch 1.

[1939] DS3-SMDS interfaces 1 and 3 shown in FIG. 33 are loaded to a subscriber interface shelf (SIFSH) 6. The DS3-SMDS interface 3 (described as DS#-ATM in FIG. 34) is loaded to an SIFSH 7 in the switch 1 or a remote multiplexer shelf (RMXSH) 7 in the BRLC 2. When the DS3-SMDS interface is loaded to an SIFSH, it can be loaded for up to 8 links. The SIFSH comprises a SIFSH common unit having a duplex configuration which is an interface with an ATM switch, and a line individual unit having a simplex configuration. The DS3-SMDS interface is loaded to the line individual unit. Up to two SIFSHs are cascade-connected and line concentration is conducted at a ratio of 4 to 1.

[1940] In FIG. 33, the DS3-SMDS interface 1 terminates a DS3 layer in a transmission line 2 to provide an SMDS service to receive a frame of the PLCP layer accommodated in the information payload field of the DS3 frame input from the DS3 transmission line 2. The DS3-SMDS interface 1 extracts an L2 protocol data unit (L2-PDU) from the frame of the received PLCP layer. After HCS (HEC)-checking the header of the L2-PDU, it converts 53-octet L2-PDU to 54-octet ATM cell (53/54 octet conversion) to be processed in an ATM switch 5, multiplexes the ATM cell to high-speed upward highways each having a transmission speed of 622 Mbps to transmit it to an ATM switch 3.

[1941] By contrast, the DS3-SMDS interface 1 assembles ATM cells demultiplexed from high-speed downward highways extended from the ATM switch 3 into a DS3 frame in the reverse order of the procedure above. Then it transmits the frame to the DS3 transmission line 2. As shown in FIG. 34, when a broadband remote line concentrator (BRLC) is connected to a DS3 transmission line 4, the DS3-SMDS interface 3 realizes an umbilical link. In this case, the DS3-SMDS interface 3 in the switch 1 is connected to the DS3-DMDS interface 5 in the BRLC 2 through the DS3 transmission line 4 as shown in FIG. 34.

2. EXPLANATION LINE INTERFACE

2.1. DS3 Line Interface

[1942] 2.1.1. Payload Mapping

[1943] FIG. 35 shows the mapping between the ATM cell in the data format of the ATM switch and the DS3 format of the transmission line in the DS3 line interface.

[1944] 2.1.2. DS3 Frame Format

[1945] In FIG. 33, the DS3-SMDS interface 1 terminates the asynchronous DS3 frame format (F13 format) shown in FIG. 35 as the frame format in the DS3 transmission line 2. FIG. 36 shows the detailed configuration of the frame format.

[1946] A multiframe consists of 7 subframes. A subframe consists of eight 85-bit blocks. In the 85-bit block, the first 1 bit is a DS3 overhead unit and the remaining 84 bits form an information payload field (INFO.PAYLOAD).

[1947] In the DS3 line interface, one multiframe is transmitted at a bit rate of 44.736 MHz on a cycle of 106.4 μsec (microsecond).

3. PLCP FRAME FORMAT

3.1. DS3 PLCP Frame Format

[1948] FIG. 37 shows the format of the DS3 PLCP frame of the PLCP layer shown in FIG. 35. The DS3 PLCP frame is transmitted using the information payload (INFO.PAYLOAD) in the subframe in the asynchronous DS3 frame format shown in FIG. 35. In this case, each octet in the frame is sequentially transmitted in 4-bit nibble units. The head of the multiframe or subframe in the DS3 frame format shown in FIG. 35 does not have to synchronize with the head of the DS3 PLCP frame.

4. DS3-SMDS INTERFACE L2-PDU FORMAT

4.1. DS3-SMDS L2-PDU Format

[1949] FIG. 38 shows the format of the DS3-SMDS L2 protocol data unit (L2-PDU) inserted in the PLCP frame shown in FIG. 35 or 37. As shown in FIG. 38 or 35, the DS3-SMDS L2-PDU consists of a 7-octet header, a 44-octet information field (INFO.FIELD), and a 2-octet trailer field (TRAILER).

[1950] An access control field (Access Control or ACF shown in FIG. 35) in the header (HEADER) shown in FIG. 38 is used in detecting a transmission state of the L2-PDU in the transmission line terminating the DS3-SMDS interface. FIG. 39 shows the contents of the access control fields in each of the upward and downward transmission lines in each of the cases when the transmission line in which the DS3-SMDS interface terminates is a subscriber/network interface (SNI), for example, the transmission line 2 shown in FIG. 33 and when it is a network node interface (NNI), for example, the transmission line 4 shown in FIG. 33.

[1951] In FIG. 39, if the transmission line in which the DS3-SMDS interface terminates is an SNI, then a BUSY bit indicates whether or not the L2-PDU containing the bit carries information. If the transmission line terminating the DS3-SMDS interface is an SNI and the transmission line is an upward transmission line (entering the ATM switch), then each bit of RQ0, REQ1, and REQ2 indicates a priority level. If the transmission line terminating the DS3-SMDS interface is an NNI, then the BUSY bit indicates whether or not the L2-PDU containing the bit is valid.

4.2. Network Control Information

[1952] The network control information field (NETWORK CONTROL INFO or NCI shown in FIG. 35) in the header field shown in FIG. 38 is 32-bit data and consists of a 2-bit PT, a 2-bit SP, and an 8-bit HCS as shown in FIG. 40. As shown in FIG. 40, a virtual channel identifier (VCI) is all 1 if the L2-PDU contains information, and all 0 if the L2-PDU contains no information. A payload type (PT) and a segment priority (SP) are to be used in the future in the subscriber network interface (DS3-SMDS SNI), and both contain 00 at present.

[1953] A header check sequence (HCS) is a value obtained by the calculation performed by the generative polynomial G(x)=X⁸+X²+X+1 for the 3-octet data field consisting of the VCI, PT, and SP in the network control information field. Using the calculated value, the network control information field is checked for errors. The three octets consisting of the VCI, PT, and SP have two types of fixed values as shown in FIG. 40. Accordingly, the HCS contains 001000010 if the L2-PDU contains information, and otherwise 00000000.

4.3. Segment Type

[1954] FIG. 41 shows the combination of the segment types (SEGMENT TYPE, or SEGT shown in FIG. 35) in the header field shown in FIG. 38. The segment type indicates a 2-bit value 00, 01, 10, or 11 depending on the type of the L2-PDU among COM (CONTINUATION MESSAGE), EOM (END OF MESSAGE), BOM (BEGINNING OF MESSAGE), and SSM (SINGLE SEGMENT MESSAGE).

4.4. Message Identifier

[1955] The message identifier (MESSAGE IDENTIFIER or MID shown in FIG. 35) in the header field shown in FIG. 38 refers to data related to the L3-PDU, and is described later.

4.5. Segmentation Unit

[1956] In FIG. 38, the segmentation unit (SEGMENTATION UNIT or SEG.UNIT shown in FIG. 35), which is an information field (INFO.FIELD) stores an L3 protocol data unit (L3-PDU) in the SMDS service (refer to FIG. 42 described later).

4.6. Payload Length

[1957] The payload length (PAYLOAD LENGTH, or PLEN shown in FIG. 35) stores the length of valid data contained in the segmentation unit. If the L2-PDU is a BOM or COM, then PAYLOAD LENGTH=44. If the L2-PDU is an EOM or SSM, then PAYLOAD LENGTGH≦44. If the L2-PDU does not contain information, then PAYLOAD LENGTH=00.

4.7. Payload CRC

[1958] The payload CRC (PAYLOAD CRC or PCRC shown in FIG. 35) shown in FIG. 38 is a value calculated by the generative polynomial G(x)=X¹⁰+X⁹+X⁵+X⁴+X+1 for the 48-octet data field consisting of SEGMENT TYPE, MESSAGE IDENTIFIER, SEGMENTATION UNIT, PAYLOAD LENGTH, and PAYLOAD CRC shown in FIG. 5. Using the value, the 48-octet data field is checked for errors. If the L2-PDU contains no information, then PAYLOAD CRC=00.

5. RELATIONSHIP BETWEEN L2-PDU AND ATM CELL

[1959] The DS3-SMDS interface 1 shown in FIG. 33 HCS (HEC)-checks the header of the L2-PDU input from the transmission line 2, and converts the 53-octet L2-PDU into the 54-octet ATM cell to be processed in the ATM switch 5 as described in 4.2. In this case, the segment type (SEGT) and message identifier (MID) in the header field of the L2-PDU, and the segmentation unit (SEG.UNIT), payload length (PLEN), and payload CRC (PCRC) in the payload field of the L2-PDU are stored in the payload field of the ATM cell (ATM CELL PAYLOAD) as shown in FIG. 35. The VCI indicating 1 for all bits (20 bits) in the network control information field (NCI) in the header of the L2-PDU is converted into the values VPI=3F, and VCI=03FF defined as the interface between the DS3-SMDS interface and the SIFSH Common. The VPI/VCI are added to the header field of the ATM cell.

[1960] As described above, the DS3-SMDS interface shown in FIG. 33 converts data between the DS3 format in the transmission line 1 and the ATM cell format to be processed in the common process (COM) shown in SIFTH 6. In this case, the L3 protocol data unit (L3-PDU) transmitting user data in the SMDS service is stored in the segmentation unit in the L2-PDU payload field to be transmitted in both formats.

[1961] That is, as shown in FIG. 42, communication data (user data) is stored in the L3-PDU payload field defined in the SMDS service in the transmitting user terminal unit which communicates through the DS3 transmission line. Then, in the transmitting user terminal unit, the L3-PDU is divided into one or more 44-octet segments. Then, produced are one or more L2-PDUs each containing the segmentation unit in each payload field containing one or more segments. In this case, one or more L2-PDUs generated by one L3-PDU are assigned identifiers (shown in FIGS. 35 and 38) which are called an MID (message identifier or multiplexing identification) and have the same value. This information is required when a subscriber message handler shelf (SBMESH) shown in FIG. 8 which provides SMDS services and is described later does not recognize the L3-PDU, but recognizes on real time only the header field of the L2-PDU to process SMDS data. The user can simultaneously use 16 different MID values in a single subscriber network interface (SNI). That is, the user can simultaneously communicate 16 different SMDS messages in a single SNI. Then, in the transmitting user terminal unit, the L2-PDUs are assembled into PLCP frames, into subframes of DS3 frames, and finally into multiframes of DS3 frames (refer to FIG. 35). Thus, the DS3 frames assembled in the transmitting user terminal unit are transmitted to the DS3 transmission line. Then, the DS3-SMDS interface extracts the PLCP frame from the DS3 frame as described above, extracts the L2-PDU from the PLCP, converts the L2-PDU into an ATM cell, and transmits the cell to the SIFSH common. Thus, the DS3-SMDS interface need not recognize the L3-PDU in the SMDS services.

[1962] When specifying the permanent virtual circuit (PVC) between the SIFSH common and the SBMESH (shown in FIG. 8) based on the values VPI=3F and VCI=03FF added by the DS3-SMDS interface, the SIFSH common replaces the value VPI/VCI added to the header field of the ATM cell containing the L2-PDU of the SMDS service in the payload field input by the DS3-SMDS interface with the value VPI/VCI specifying the SNI which is a DS3 transmission line terminating the DS3-SMDS interface which transmitted the ATM cell. Therefore, the PVC between the SIFSH common and the SBMESH is assigned the value VPI/VCI of the number corresponding to the number of the SNIs terminated by the individual unit such as the DS3-SMDS interface connected to the SIFSH common and used in the SMDS service. The SIFSH common adds a tag to the head of the ATM cell. The tag indicates the transfer of the ATM cell to the SBMESH after being autonomously switched in the ATM switch.

[1963] The SBMESH (described later and shown in FIG. 8) which is connected to the ATM switch (ASSWSH) and provides SMDS services receives, among the ATM cells to be input through the ATM switch, the ATM cell assigned at the header field a specific VPI/VCI value for the PVC used in the SMDS service. It processes the L2-PDU stored in the payload field of the ATM cell. The ATM cell has a protocol hierarchy of ATM layers in layer 2 (L2), and the L2-PDU has the protocol hierarchy of segmentation and reassembly sublayers (SAR) in the ATM adaptation layer (AAL) of layer 2 (L2). In this case, the SBMESH has a protocol hierarchy of layer 3 (L3) as described later in part 5, etc. It does not recognize the L3-PDU (shown in FIG. 42) which user data in the SMDS service is actually stored and transmitted, but recognizes on real time only the header field of the ATM cell and the header field of the L2-PDU to process SMDS data. Practically, the SBMESH processes as the data related to the same L3-PDU the L2-PDUs having the same SNI determined according to the VPI/VCIs assigned to the headers of the ATM cells and having the same value of MID assigned to the header field of the L2-PDUs. As a result, the SMDS services can be provided as connectionless services without disturbing the real time operations specific to the ATM system.

[1964] In a receiving user terminal unit communicating via the DS3 transmission line, a PLCP frame is extracted from the DS3 frame received from the DS3 transmission line, and the L2-PDU is extracted from the PLCP frame. Then, the contents of the segmentation unit in the payload field of the L2-PDU are extracted, and assembled into the L3-PDU according to the MID added to the header field of the L2-PDU. Finally, extracted is the communication data (user data) from the payload field of the L3-PDU.

6. DS3 UMBILICAL LINK FORMAT

[1965] As shown in FIG. 34, is the broadband remote line concentrator (BRLC) is connected to the DS3 transmission line 4, then the DS3-SMDS interface 3 realizes an umbilical link.

[1966] In this case, the data in the transmission line 4 is transmitted in the 53-octet data format as shown in FIG. 43. That is, the data in the transmission line 4 is transmitted as normal ATM cells.

[1967] As shown in FIG. 43, a header field (HEADER) contains 5-octet data consisting of a virtual pass identifier (VPI), a virtual channel identifier (VCI), a payload type (PTI), a cell loss priority (CLP), and a header error check (HED).

[1968] The header error check (HEC) field contains a value calculated by the generative polynomial G(x)=X⁸+X²+X+1 for the header field. Using the value, the header field is checked for errors.

[1969] If the result of the check outputs no error, then it is determined whether or not the values of the VIP and VCI are all 0 as shown in FIG. 44 to determine whether the ATM cell to be processed is an unassigned cell or an assigned cell.

[1970] If a 1-bit error is detected as a result of the error check, it is corrected. If an error of two or more bits is detected, then the error is not corrected but is detected only.

[1971] The DS3-SMDS interface 3 converts the 53-octet ATM cell received from the transmission line 4 into a 54-octet ATM cell to be processed in the ATM switch by removing the 1-octet HEC in the header field and adding a 2-octet tag to the header.

[1972] In this case, the L2-PDU in the SMDS service is stored in the payload field (PAYLOAD) in the ATM cell shown in FIG. 43.

7. HARDWARE CONFIGURATION

7.1. General Descriptions

[1973] The thus explained DS3-SMDS functions are realized by the DS3-SMDS interfaces 1 and 3 shown in FIG. 33 and the subscriber message handler shelf (SBMESH) and the gateway message handler shelf (GWMESH) shown in FIG. 8.

[1974] The functions of each of the units are as follows.

[1975] 1. DS3-SMDS interface unit

[1976] a. DS3 layer terminating function

[1977] b. L2-PDU header terminating function

[1978] 2. SBMESH/GWMESH interface unit

[1979] a. L2-PDU payload terminating function

[1980] b. L3-PDU terminating function

[1981] Listed below in detail are the functions loaded to the DS3-SMDS interface unit.

[1982] a. DS3 layer terminating function

[1983] b. DS# PLCP layer terminating function

[1984] c. Received L2-PDU header checking function (HCS)

[1985] d. L2-PDU header pattern generating function

[1986] e. Distributed queue dual bus (DQDB) sequence function (REQ bit processing function)

[1987] f. DS3 layer performance monitor function

[1988] g. PLCP layer performance monitor function

[1989] h. Reception L2-PDU data converting function (45 Mbps→156 Mbps)

[1990] i. Transmitted L2-PDU data bit rate converting function (156 Mbps→45 Mbps)

[1991] j. MSD/MSCN information LAP terminating function

[1992] k. Interfacing function (53-octet 8-bit parallel-54-octet 16-bit parallel) for SIFSH common

[1993] l. Multiplexing/demultiplexing function for DS3-SMDS L2-PDU cells and LAP cells

[1994] m. Loopback function for specific VPI/VCI

[1995] n. MSCN data multiplexing function

[1996] o. MSD data dropper function

[1997] FIG. 45 is a block diagram showing the functional configuration of the DS3-SMDS interface.

7.2. DS3 Layer Terminating Function

[1998] The DS3 layer terminating function is one of the capabilities loaded to the DS3-SMDS interface, and terminates the DS3 frame format described in 2.1.2. by referring to FIG. 35.

[1999] Practically, the following processes are performed.

[2000] A. At a receiving equipment

[2001] a. Illegality monitoring and error counting for PCM line code (B3ZS code)

[2002] b. Synchronization establishing and error counting for framing bit (F0/F1/M0/M1: refer to FIG. 36)

[2003] c. Confirming and error counting for P bit (parity bit: refer to FIG. 36)

[2004] d. Confirming AIS pattern (refer to FIG. 36)

[2005] e. Confirming yellow alarm bit (X bit: refer to FIG. 36)

[2006] b. At a sending equipment

[2007] a. Generating framing bit (F0/F1/M0/M1: refer to FIG. 36)

[2008] b. Generating P bit (parity bit: refer to FIG. 36)

[2009] c. Generating AIS pattern (refer to FIG. 36) (when the loopback is specified)

[2010] d. Setting yellow alarm bit (X bit: refer to FIG. 39) at red CGA alarm

[2011] e. Converting PCM line code (B3ZS code)

[2012] 7.2.1. Process for line faults

[2013] The DS3-SMDS interface monitors a line fault and notifies the switching system of a fault when generated. The fault notification is automatically followed by a notification of a normal operation if the fault has been removed. If a plurality of faults are detected during the fault monitoring process, then the process is performed only on the most serious fault, and is not performed on the other faults.

[2014] FIG. 46 shows the sequence of the alarm in the DS3 layer. First, if a fault occurs in a transmission line (1.) in (a) in FIG. 46, the DS3-SMDS interface A declares a red carrier group alarm (CGA) (2.) and then transmits a yellow alarm (3). As a result, the DS3-SMDS interface B declares a yellow carrier failure alarm (CFA) (4). Then, in (b) in FIG. 46, the DS3-SMDS interface A transmits an alarm indication signal (AIS) (2.) when a loopback test is conducted (1.). As a result, the DS3-SMDS interface B declares reception of an AIS.

[2015] FIG. 47 shows the priority level of the alarm in the DS3 layer. For example, if a loss of signal (LOS) has been detected, then each of the alarm indication signal (AIS), out of frame (OOF), yellow signal (YEL), PLCP out of frame (POOF), and PLCP yellow signal (PYEL) is masked.

[2016] 7.2.2. Detection and Recovery Condition of Each Alarm

[2017] FIG. 48 shows the detection and recovery condition of each alarm. FIG. 49 shows the timing of the declaration of an alarm.

7.3. DS3-SMDS Layer Terminating Function

[2018] The DS3 layer terminating function is one of the capabilities loaded to the DS3-SMDS interface, and terminates the DS3 PLCP frame format described in 3.1. by referring to FIG. 37.

[2019] Practically, the following processes are performed.

[2020] A. At a receiving equipment

[2021] a. Synchronization establishing and error counting for framing bit (A1/A2: refer to FIG. 37)

[2022] b. Confirming and error counting for PLCP BIP-8 (B1: refer to FIG. 37)

[2023] c. Confirming and error counting for PLCP path status (G1: refer to FIG. 37)

[2024] b. At a sending equipment

[2025] a. Generating framing bit (A1/A2: refer to FIG. 37)

[2026] b. Generating PLCP BIP-8 (B1: refer to FIG. 37)

[2027] c. Generating PLCP path status (G1: refer to FIG. 37)

[2028] d. Generating cycle staff counter (C1: refer to FIG. 37)

[2029] e. Generating SIP level 1-control information (M1/M2: refer to FIG. 37)

[2030] 7.3.1. Process for Line Faults

[2031] The DS3-SMDS interface monitors a line fault and notifies the switching system of a fault when generated. The fault notification is automatically followed by a notification of a normal operation if the fault has been removed. If a plurality of faults are detected during the fault monitoring process, then the process is performed only on the most serious fault, and is not performed on the other faults.

[2032] FIG. 50 shows the sequence of the alarm in the DS3 PLCP layer. In FIG. 50, if a PLCP frame is transmitted in fault (1.) with the PLCP frame in the DS3-SMDS interface B, then the DS3-SMDS interface A detects asynchronization of the PLCP frame and transmits a yellow signal. As a result, the DS3-SMDS interface B declares the reception of the yellow signal.

[2033] 7.3.2. Detection and Recovery Condition of Each Alarm

[2034] FIG. 51 shows the detection and recovery condition of each alarm. FIG. 52 shows the timing of the declaration of an alarm.

7.4. L2-PDU Header Checking Function (HCS)

[2035] As shown in FIG. 33, if the DS3-SMDS interface 1 terminates the DS3 layer in the DS3 transmission line 2 to provide an SMDS service, the DS3-SMDS interface 1 fetches a frame of the PLCP layer accommodated in the information payload field of the DS3 frame input through the DS3 transmission line 2. Then, the DS3-SMDS interface 1 extracts an L2 protocol data unit (L2-PDU) from the frame in the extracted PLCP layer (FIG. 35). Then, the DS3-SMDS interface 1 determines whether the L2-PDU can be a valid cell or an invalid cell by referring to a BUSY bit contained in the access control field (ACF: refer to FIGS. 38, 39, and 35 in the header of the L2-PDU. If the L2-PDU can be a valid cell, then the DS3-SMDS interface 1 determines whether the value of the network control information field (NCI: refer to FIGS. 38 and 35) in the header of the L2-PDU indicates 11111111 11111111 11110000 00100010 or all zero as shown in FIG. 40. If the value of the NCI indicates 11111111 11111111 11110000 00100010, then the DS3-SMDS interface 1 processes as a truly valid cess the L2-PDU to be processed. If the value of the NCI is all zero, then the DS3-SMDS interface 1 increments the count value of the HCS error and performs the protocol monitor process.

[2036] On the other hand, if the BRLC is connected to the DS3 transmission line 4 as shown in FIG. 34, and the DS3-SMDS interface 3 realizes an umbilical link, then the DS3-SMDS interface 3 calculates the HEC (FIG. 43) of the ATM header field. If it determines that no error has arisen in the ATM header field, then it determined whether or not the object ATM cell is a valid cell after checking whether or not the object ATM cell is a free cell. If the DS3-SMDS interface 3 determines as a result of the calculation that an error has arisen at the header field, then it increments the count value of the HEC error and performs a protocol monitor process.

7.5. L2-PDU Header Pattern Generating Function

[2037] As shown in FIG. 33, if the DS3-SMDS interface 1 terminates the DS3 layer in the DS3 transmission line 2 to provide an SMDS service and if the ATM cell transferred from the ATM switch (ASSWSH) 5 shown in FIG. 33 is a valid cell, then the DS3-SMDS interface 1 adds a network control information field (NCI) (refer to FIG. 40) containing the values 11111111 11111111 11110000 00100010 to the beginning of the information contained in the payload field of the ATM cell as shown in FIG. 35, and further adds to the beginning of the field an access control field (ACF) to form an L2-PDU. If the ATM cell transferred from the ATM switch (ASSWSH) 5 is an invalid cell, then the DS3-SMDS interface 1 adds an NCI (FIG. 40), that is, all zero, to the beginning of the information contained in the payload field of the ATM cell as shown in FIG. 35, and further adds to the beginning of the information an access control field (ACF) to form an L2-PDU. Thus, if the ATM cell is converted into an L2-PDU , then the header information (VPI/VCI, etc.) of the ATM cell is discarded. Then, as shown in FIG. 35, a frame of the PLCP layer is generated based on the thus generated L2-PDU, then a DS3 frame is generated based on the frame of the PLCP layer, and the DS3 frame is sent to the DS3 transmission line 2 shown in FIG. 33.

[2038] If the BRLC is connected to the DS3 transmission line 4 and the DS3-SMDS interface 3 realizes an umbilical link as shown in FIG. 34, then the DS3-SMDS interface 3 does not replace the header field for the ATM cell transferred from the ATM switch (ASSWSH), but calculates the HEC for the header field, adds to the header the HEC (FIG. 43) obtained as a result of the calculation, and transmits the ATM cell to the transmission line 4 shown in FIG. 34.

7.6. Distributed Queue Dual Bus (DQDB) Sequence Function

[2039] If the DS3-SMDS interface 1 terminates the DS3 layer in the DS3 transmission line 2 for providing an SMDS service and if a customer premise equipment (CPE), which is a user terminal unit, connected to the DS3 transmission line 2 is, for example, a multi CPE connected to the LAN as shown in FIG. 33, then is subject to the following control. That is, if the CPE cannot capture a blank cell, then the CPE requests for a blank cell by setting to ON the bits of REQ-0 through REQ-2 (FIG. 39) in the access control field (ACR: refer to FIGS. 38 and 35) in the header of the L2-PDU in the transmission line. Then, the DS3-SMDS interface shown in FIG. 33 sends a blank cell when it receives the request bit from the CPE.

7.7. DS3 Layer/PLCP Layer Performance Monitoring Function

[2040] The DS3-SMDS interface monitors the performance of lines and notifies the switching system of the multiplication for each performance parameter and the threshold alarm for the resultant product.

[2041] Even if the switching system receives a notification of a threshold alarm, it does not block the line corresponding to the alarm but processes the alarm as a simple warning and includes the fact in the subsequent maintenance plan.

[2042] Performance parameters are classified into those related to the DS3 layer and those to the PLCP layer. The parameters related to the DS3 layer are further classified into the information about lines and the information about paths.

[2043] The information about the line in the DS3 layer includes the observation of the following three parameters.

[2044] 1. Line code violation

[2045] 2. Line errorred second

[2046] 3. Line severly errorred second

[2047] The information about the path in the layer includes the values of the following 6 parameters.

[2048] 4. CV: P-bit parity code violation

[2049] 5. ES: Errored second

[2050] 6. SES: Severly errorred second

[2051] 7. SFFS: Severly errorred second

[2052] 8. UAS: Unavailable second

[2053] 9. AISS: Alarm indication signal second

[2054] The information about the PLCP layer includes the values of the following 5 parameters.

[2055] 10. PLCP CV: PLCP code violation

[2056] 11. PLCP ES: PLCP errorred second

[2057] 12. PLCP SES: PLCP severly errorred second

[2058] 13. PLCP OOF: PLCP out of frame

[2059] 14. PLCP UAS: PLCP unavailable second

[2060] The DS3-SMDS interface holds the last value obtained every 15 minutes. The obtained result is read every 15 minutes for the switching system. The switching system holds 32 values sequentially obtained every 15 minutes per day (for 8 hours), and thus holds a 7-day record.

[2061] Provided is a FAR END performance monitor unit using a far end block error (FEBE) transmitted through G1 bits (FIG. 37) in the PLCP frame format. The threshold of the function is a default optionally defined by the user.

[2062] 7.7.1. DS3 Layer

[2063] FIG. 53 shows the type of performance parameter about the DS3 layer and the count-up condition of the multiplication for each parameter.

[2064] 7.7.2. DS3-PLCP Layer

[2065] FIG. 54 shows the types of performance parameters of the DS3-PLCP layer, the count-up conditions of the product for each parameter, and the alarm threshold for the product of each parameter.

7.8. Received L2-PDU Data Converting Function (45 Mbps→156 Mbps)

[2066] If it is determined that no error has arisen in the L2-PDU and that the L2-PDU is a valid cell as a result of the L2-PDU header check described in 7.4. above, then the ATM cell obtained by converting the L2-PDU is sent to the ATM switch (ASSWSH) through the SIFSH common (FIG. 8). In this case, if valid cells are consecutively sent from the user equipment, then data to be processed in the ATM switch is subject to higher possibility of burst, thereby probably causing congestion in the ATM switch and undesirably losing cells in the ATM switch. Therefore, if the L2-PDU received from the DS3 transmission line having the bit rate of 45 Mbps is multiplexed to the highway in a switch which has the bit rate of 156 Mbps and is terminated by the SIFSH common, then the DS3-SMDS interface performs a shaping process using a buffer such that the ratio of the valid cells to invalid cells multiplexed.

7.9. Transmitted L2-PDU Data Bit Rate Converting Function (156 Mbps→45 Mbps)

[2067] The bit rate of the L2-PDU transmitted from the SIFSH common is 156 Mbps. Therefore, the data having the bit rate of 156 Mbps is converted into the bit rate of the DS3 layer, that is, 45 Mpbs.

7.10. Interfacing Function to SIFSH Common

[2068] The cell length of the DS3-SMDS L2-PDU is 53 octet, and the cell length of the ATM cell processed by the SIFSH common (SIFSH COM: refer to FIG. 33) is 54 octet. Therefore, the interface between the DS3-SMDS interface and the SIFSH common is required to have the function of converting data length.

[2069] When the L2-PDU is transferred from the DS3-SMDS interface to the SIFSH common, the DS3-SMDS interface checks the HCS (HEC) of the header of the L2-PDU input via the transmission line and then converts the 53-octet L2-PDU to the 54-octet ATM cell to be processed in the ATM switch 5. In this case, stored in the payload field (ATM cell payload) are the segment type (SEGT) and message identifier (MID) in the header field of the L2-PDU, and the segmentation unit (SEG.UNIT), payload length (PLEN), and payload CRC (PCRC) in the payload field of the L2-PDU as shown in FIG. 35. A CVI having “1” in all bits in the network control information field (NCI) in the header field of the L2-PDU is converted into the values, that is, VPI=3F and VCI=03FF, assigned as the interface between the DS3 interface and the SIFSH common. Then, the VPI and VCI are added to the header field of the ATM cell. The header field of the ATM cell is provided with a 2-octet tag indicating the autonomous switching in various multiplexing units and the ATM switch.

[2070] If an ATM cell is transferred from the SIFSH common to the DS3-SMDS interface, then the DS3-SMDS interface checks the leading tag in the ATM cell and deletes the tag if the cell is to be output by the DS3-SMDS interface. Then, the DS3-SMDS interface converts the 54-octet ATM cell into the 53-octet L2-PDU by performing in the reverse order the operation of the transfer of the L2-PDU from the DS3-SMDS interface to the SIFSH common.

[2071] FIG. 55 shows the outline of the above explained converting process. An access control field (ACF: refer to FIGS. 35 and 38) is also converted as shown in FIG. 55. The payload type (PT) and segment priority (SP) (both shown in FIG. 40) having all “0” are transferred as is.

[2072] If the DS3-SMDS interface realizes an umbilical link, then the DS3-SMDS interface converts the 53-octet ATM cell in the transmission line 4 into the 54-octet ATM cell to be processed in the ATM switch by removing from the ATM cell received via the transmission line the 1-octet HEC of the header field and adding the 2-octet tag, and then transmits the converted ATM cell to the SIFSH common. That is, no VPI/VCI conversion is made. If the ATM cell is transferred from the SIFSH common to the DS3-SMDS interface, then the above described operation is performed in the reverse order.

7.11. LAP Terminating Function of MSD/MSCN Information

[2073] Transmitted through the link access protocol (LAPD) are the control information (MDS information) transferred from the switching system to the DS3-SMDS interface and the DS3 layer/PLCP layer fault information (MSCN) transferred from the DS3-SMDS interface to the switching system such as a performance monitor threshold crossing alert, performance monitor counter value, etc. The LAPD is mapped to the ATM cell using the ATM adaptation layer (AAL) protocol type of type 3 or 4. As a result, the above described information is transmitted as an ATM cell between the DS3-SMDS interface and the broadband signaling group controller shelf (BSGCSH)(FIG. 8) through the ATM switch (ASSWSH).

[2074] The hardware fault (such as parity errors) of the DS3-SMDS interface is transmitted by the SIFSH common to the switching system through the LAPD. The determination as to whether the data transferred in a switch refers to the L2-PDU data or the LAPD data can be made according to the value of the bit specified in the tag area of the header field of the ATM cell. FIG. 56 shows the format of the ATM cell transferred in the ATM cell. The determination as to whether the data transferred in a switch refers to the L2-PDU data or the LAPD data can be made according to the value of the SIG bit in the 2-octet tag area added to the head of the ATM.

[2075] Thus, since the DS3-SMDS interface and SIFSH common need not be directly connected to the system bus of the switching system, the load on the system bus can be successfully reduced.

7.12. Multiplexing Function of DS3-SMDS L2-PDU Cell and LAP Cell

[2076] For the ATM cell to be transferred to the SIFSH common, the DS3-SMDS interface multiplexes the MSCN LAPD cell for the L2-PDU data. As for the multiplexing timing of the MSCN LAPD cell, the MSCN LAPD cells are multiplexed for the L2-PDU data when the switching system issues a request for the performance monitor information, etc. using the MSD LAPD cell from the switching system.

7.13. Demultiplexing Function of DS3-SMDS L2-PDU Cell and LAP Cell

[2077] In the ATM cell is transferred from the SIFSH common to the DS3-SMDS interface, then the MSD LAPD cell if multiplexed for the L2-PDU data. Therefore, the DS3-SMDS interface should demultiplex the MSD LAPD cell to process the MSD LAPD information. The demultiplexing process is performed after determining the value of the SIG bit in the tag area of the ATM cell shown in FIG. 56.

7.14 Loopback Function of Specified VPI/VCI

[2078] 7.14.1 Loopback Function of Cell Provided with “0” Bit

[2079] The DS3-SMDS interface is loaded with the maintenance function of looping back a specified cell having a 0 bit at the head of the tag area of the ATM cell shown in FIG. 56.

[2080] 7.14.2 Loopback Function of Cell Provided with Specific VCI/VCI

[2081] The DS3-SMDS interface is loaded with the maintenance function of looping back a cell having a specified VPI/VCI notified of through a simple LAP. The loopback is notified of in a simple LAP format and then activated according to the EMSD information. However, this loopback function and the function of looping back the cell having the “0” bit as described in 7.14.1. are not simultaneously activated because of the configuration of the hardware.

7.15 MSCN Data Multiplexing Function

[2082] The hardware fault (for example, a parity error) information of the DS3-SMDS interface, which cannot be notified of from the DS3-SMDS interface using the MSCN LAPD cell, can be notified of by the SIFSH common to the switching system using a LAPD cell. Therefore, the fault information from the DS3-SMDS interface is transmitted as serial data of 1 Mbps.

7.16 MSD Data Dropper Function

[2083] Common information transferred to the line interface loaded in the SIFSH is terminated in the SIFSH. Therefore, the information to be transferred to the DS3-SMDS interface is transferred as serial data of 1 Mbps as explained in 7.15. above. The DS3-SMDS interface processes thus transferred MDS data.

8. MAINTENANCE SIGNAL DRIVER (MSD) INTERFACE

8.1. MSD Information

[2084] The following information provided for the DS3-SMDS interface from the software of the switching system is first transferred from the software of the switching system to the SIFSH common by way of the BSGCSH (shown in FIG. 8) through the intra-station control communications. Then, the SIFSH common notifies the DS3-SMDS interface of the information in the software process. Such information is referred to as the E-MSD.

[2085] 1. Each type of reset signal

[2086] 2. DS3-SMDS interface state control information

[2087] 3. Pseudo-fault setting information of software fault detecting circuit

[2088] 4. Information simultaneously provided by SIFSH common for each of the individual units, for example, the DS3-SMDS interface.

[2089] The E-MSD information is received by both systems of duplex SIFSH common. The DS3-SMDS interface fetches the D-MSD information transferred from the active SIFSH common. The restrictions on the hardware do not allow the E-MSD information to be supported by a unit for detecting data other than bit stuck. Therefore, the DS3-SMDS interface performs a protecting process on the received E-MSD information to counteract the disturbance of the clock frame pulses at the switch of the SIFSH common systems. That is, only when the DS3-SMDS interface receives simultaneously and consecutively 2 frames of the same information from the SIFSH common, then it processes the information as valid data.

[2090] 8.1.1. E-MSD Hardware Interface

[2091] The interface between the SIFSH common and the DS3-SMDS interface is restricted on its three elements of data, that is, clock (1.215 MHz), FP (frame pulse), and data. The data length of the E-MSD is 256 bits. FIG. 57 is a timing chart of the E-MSD signal.

[2092] 8.1.2. E-MSD Accommodation List of DS3-SMDS Interface

[2093] FIG. 58 shows the list indicating the state of the accommodation of the E-MSD information transferred between the DS3-SMDS interface and the SIFSH common. In this list, each row indicates a byte position and each column indicates the position of the bit in each byte position. The E-MSD data transferred from the SIFSH common is serially received by the DS3-SMDS interface from the D0th bit of the 000th byte to the D7th bit of the 255th byte. In this format, since the area of the 000th byte is generated by the SIFSH common, it actually is the leading data of the 001th byte.

[2094] Since the DS3-SMDS interface does not automatically release various reset signals including the hardware reset signal, the reset signals should always be released after being properly set.

[2095] FIG. 59 shows the contents of each bit of the E-MSD information.

8.2. Detailed Explanation of the E-MSD

[2096] 8.2.1. Hardware Reset

[2097] In the DS3-SMDS interface, the following two reset points are defined as the reset timings at the occurrence of a hardware fault.

[2098] 1. SDFRST (hardware fault reset)

[2099] 2. PPRST (microprocessor reset)

[2100] Since the resettings are not automatically released by hardware, “1” should be set as the setting and “0” should be set as the resetting.

[2101] 8.2.2. Loopback

[2102] In the DS3-SMDS interface, defined are the following three loopback activation points for all cells and the loopback activation points for each cell.

[2103] 1. LOOP-1 (Loopback instruction for all cells at DS3-SMDS interface input unit (at the terminal close to the ASSW)

[2104] 2. LOOP-2 (Loopback instruction for all cells at DS3-SMDS interface output unit (at the terminal connected to the line)

[2105] 3. LOOP-3 (Line loopback instruction to the output DS3 transmission line for all cells from the input DS3 transmission line)

[2106] 4. LOOP-4 (Loopback instruction for a cell assigned “0” bit)

[2107] 5. LOOP-5 (Loopback instruction for a cell assigned specified VPI/VCI)

[2108] 8.2.3. Pseudo-fault Point

[2109] The E-MSD is received by the DS3-SMDS interface and contains a pseudo-fault point specified for a hardware checker provided in the interface. The following 5 types of pseudo-fault points are defined.

[2110] 1. PF-CK (pseudo-fault points for a clock disconnection checker)

[2111] 2. PF-CK (pseudo-fault points for a sell frame pulse disconnection checker)

[2112] 3. PF-PTY (pseudo-fault points for a data parity checker)

[2113] 4. PF-WDT (pseudo-fault points for a watch dog timer checker)

[2114] 5. PTYRST (data parity error reset)

[2115] As in the case of the resettings explained in 8.2.1. above, “1” should be set as the setting and “0” should be set as the resetting. However, since a parity error information should be stored, it is to be reset by the PTYRST. Concerning the pseudo faults, all pseudo-fault points are set ON to activate all checkers in the printed circuit board (PCB) in the DS3-SMDS interface.

[2116] 8.2.4. AIS Transmission Point

[2117] The DS3-SMDS interface transmits an AIS pattern (AISSND) through the DS3 transmission line under the software control to notify an object device of block information such as fault block information.

9. MAINTENANCE SCANNER (MSCN) INTERFACE

[2118] Among the information provided for the software in the switching system from the DS3-SMDS interface, the following information is temporarily transmitted to the SIFSH common by hardware. The SIFSH common notifies the software of the switching system through the intra-station control communications by way of the BSGCSH (FIG. 8). The MSCN information of this type is referred to as extended maintenance scanner (E-MSCN) information.

[2119] 1. Representative points and detailed information of fault information (parity clock loss, cell frame loss) of the signal line between the DS3-SMDS interface and the SIFSH common

[2120] 2. Representative points of the hardware fault information of the DS3-SMDS interface

[2121] 3. Representative points and detailed contents of the faults disabling the intra-station control communications between the DS3-SMDS interface and the BSGCSH

[2122] 4. Representative points of the line fault according to the alarm monitor in the DS3 layer/PLCP layer

[2123] 5. Representative points of the quality control information at the occurrence of buffer congestion in the DS3-SMDS interface

[2124] 6. MSD echo-back information

[2125] 7. Other maintenance and control information between the DS3-SMDS interface and the SIFSH common

[2126] The same contents of the E-MSCN information are output to both systems of the SIFSH common duplicated through the DS3-SMDS interface. The clock and frame pulse used in sending the E-MSCN are provided by the active SIFSH common.

[2127] The SIFSH common notifies the software of the switching system through the intra-station control communications by way of the BSGCSH (FIG. 8) of the valid E-MSCN which was received from the DS3-SMDS interface and has been changed as being different from the latest contents of the E-MSCN information stored in the SIFSH common. The SIFSH common periodically notifies the software of the switching system through the intra-station communications by way of the BSGCSH of the E-MSCN information from each individual unit connected to the SIFSH common in addition to the E-MSCN information from the DS3-SMDS interface.

[2128] 9.1.1. Hardware Interface for E-MSCN

[2129] The clock and frame pulse used in sending the E-MSCN are provided by the active SIFSH common.

[2130] FIG. 60 is a timing chart showing the signal line between the DS3-SMDS interface and the SIFSH common.

[2131] 9.1.2. Detailed Explanation of E-MSCN

[2132] FIG. 61 is a table showing the accommodation state of the E-MSCN information transferred between the DS3-SMDS interface and the SIFSH common. In the table, each row indicates a byte position and each column indicates the position of the bit in each byte position. The E-MSCN data transferred from the DS3-SMDS interface is serially received by the SIFSH common in the order from the D0th bit of the 000th byte to the D7th bit of the 255th byte.

[2133] FIGS. 62 and 63 shows the contents of each bit of the E-MSCN information.

9.2. E-MSCN Process in DS3-SMDS Interface

[2134] 9.2.1. SIFSH Common Interface Fault

[2135] The DS3-SMDS interface monitors the normality of the SIFSH common interface signal line. In the normality monitor, checked are the data parity (including cell enable), clock disconnection, and cell frame disconnection in the direction from the SIFSH common to the DS3-SMDS interface. If a fault is detected in the monitor process, the representative point PE0 (#0 system) or PE1 (#1 system) is set ON. If the representative point is set ON, the detailed information of the SIFSH common interface fault can be confirmed as the contents of the 018th byte shown in FIG. 61.

[2136] The SIFSH common interface fault can be reset according to the FRST signal input via the signal line independently connected to respective duplex SIFSH common systems. If the SIFSH common interface fault has not been corrected after resetting the fault, the above described representative point and detailed information point are set ON again.

[2137] 9.2.2. DS3-SMDS Interface Hardware Fault

[2138] The DS3-SMDS interface hardware fault includes the data parity fault, clock disconnection, cell frame disconnection in the printed circuit board (PCB) and between the PCBs. If a hardware fault has arisen and can be notified of through the intra-station control communications between the DS3-SMDS interface and the BSGCSH (FIG. 8), then the representative point FERR-2 accommodated in the E-MSCN is set ON. The detailed fault information is notified of through the intra-station control communications between the DS3-SMDS interface and the BSGCSH. Refer to the 10. described later for the more detailed information.

[2139] The DS3-SMDS interface hardware fault can be reset according to the SDFRST information accommodated in the E-MSD and the HRST information provided from the SIFSH common. If the DS3-SMDS interface hardware fault has not been corrected after the reset, then the FERR-2 point is set ON again.

[2140] 9.2.3. DS3-SMDS Interface Hardware Fault

[2141] The DS3-SMDS interface hardware fault disabling the intra-station communications between the DS3-SMDS interface and the BSGCSH includes the data parity fault in the direction from the DS3-SMDS interface to the SIFSH common (UHDPT), master 19M clock disconnection (UH19M), and communications control EGCLAD fault (EGPTY). If these faults have occurred, the representative point FERR-1 of the E-MSCN is set ON. Since the intra-station control communications are disabled, the detailed fault information is accommodated in the 019th byte of the E-MSCN.

[2142] These faults can be reset according to the SDFRST information accommodated in the E-MSD and the HRST information provided by the SIFSH common. If the above faults are not corrected after the reset described above, then the FERR-1 point is set ON again.

[2143] 9.2.4. Faults in Microprocessor

[2144] The DS3-SMDS interface comprises a microprocessor for monitoring the performance of the DS3/PLCP layer and for performing intra-station control communications (simple LAPD). When the microprocessor becomes faulty or runs away, the MPE point of the E-MSCN is set ON.

[2145] The fault of the microprocessor can be reset according to the μPRST information in the E-MSD and the HRST information provided by the SIFSH common. If the fault of the microprocessor is not corrected after the reset, the MPE point is set ON again.

[2146] 9.2.5. Fault in Timer

[2147] The DS3-SMDS interface performs processes such as the monitor of the performance of the DS3-PLCP layer based on the 15-minute or 1-day trigger input via the exclusive signal line connected to the SIFSH common. If the trigger to be input via the exclusive line is not entered at a predetermined timing, that is, if a new trigger is entered within 15 minutes+15 seconds after the preceding input timing, then static processes such as the performance monitor process, etc. cannot be performed. Therefore, if a trigger is not entered on a predetermined schedule, then the representative point RIMALM of the E-MSCN.

[2148] The fault of the timer can be reset according to the SDFRST information in the E-MSD and the HRST information provided by the SIFSH common. If the fault of the timer has not been corrected after the reset, then the TIMALM point is set ON again. Since the fault point is accommodated according to the hardware monitor, no special software process is required.

[2149] 9.2.6. DS3 Layer Alarm

[2150] The DS3-SMDS interface monitors the carrier group alarm (CGA) of the DS3/PLCP layer. A plural alarms can be set ON for the CGA alarm. Accordingly, the CGA alarm is issued according to the two bits of representative points of the E-MSCN, that is, the LIALM and the LIFLG indicating the change of the alarm state.

[2151] Described below is the control method. That is, the LIALM point is set ON when the DS3/PLCP layer alarm is detected, and set OFF when the faults associated with all alarms are corrected. When the state of the DS3/PLCP layer alarm indicates a change, the LIFLG point notifies of the state change by the alteration from 0 to 1 or then to 0.

[2152] 9.2.7. Performance Monitor Threshold Crossing Alert

[2153] The DS3-SMDS interface monitors the threshold crossing alert (TCA) on the header check sequence (HCS) (FIGS. 35, 38, and 40) in the network control information field of the DS3/PLCP layer and L2-PDU. The TCA is issued when the monitor detects a value exceeding a predetermined threshold in a 15-minute and 1-day cycles. Therefore, plural TCAs can be simultaneously set ON. Therefore, the TCA is issued according to the two bits of representative points of the E-MSCN, that is, the TCAALM and the TCAFLG indicating the change of the alarm state.

[2154] Described below is the control method. That is, the TCAALM point is set ON when the performance monitor of the DS3/PLCP layer exceeds a predetermined threshold, and set OFF when the state of the timer counting every 15 minutes and every day. When the TCA state of the performance monitor of the DS3/PLCP layer indicates a change, the TCAFLG point notifies of the state change by the alteration from 0 to 1 or then to 0. If the state of the timer counting every 15 minutes and every day has changed, then the TCAFLG point holds the preceding state.

[2155] 9.2.8. Cell Discards in the DS3-SMDS Interface

[2156] The DS3-SMDS interface internally has a buffer of 112-cell capacity to convert the transmission rate of the ATM cells transferred from the SIFSH common from the transmission rate 156 Mbps in the SIFSH common to the transmission rate 45 Mbps of the DS3 transmission line. The occurrence of the cell congestion in the buffer is determined by checking whether or not the number of cells in the buffer has exceeded a queue length threshold set in the buffer. The buffer discards the cell input when the number of cells in the buffer exceeds the above threshold. The cell congestion state in the buffer is notified of by 2 bits, that is, CLOSAL and CLFLG indicating the change of the alarm state.

[2157] Described below is the control method. That is, the CLOSAL point is set ON when the cell congestion is detected in the buffer, and set OFF when all cell discard states are released. When the cell discard state changes, the CLFLG point notifies of the state change by the alteration from 0 to 1 or then to 0.

[2158] 9.2.9. Diagnostic Result Report

[2159] The DS3-SMDS interface is loaded with the self-diagnostic function to confirm the capabilities of the hardware. The self-diagnostic functions can be activated by setting ON the DS3 DEC point in the E-MSD. The diagnostic result is provided by the representative points TSTEND and TSTIND in the E-MSCN. The TSTIND point is set to 1 when the diagnostic result indicates normality, and set to 0 when it indicates abnormality. If the diagnostic result indicates abnormality, then the phase number and test number related to the abnormality can be notified of using the 031th byte in the E-MSCN. After the diagnostics, the DS3-SMDS interface is in a reset-wait state, thereby requiring initialization in the initialization procedure.

10. SIMPLE LAP-D PROTOCOL OF DS3-SMDS INTERFACE

10.1. Software Interface

[2160] FIG. 64 shows the connection of the interface between the DS3-SMDS interface and the switch software. FIG. 65 shows the protocol stack of the interface between the DS3-SMDS interface and the switch software. The switch software refers to the program executed by the processor which controls the processes (call process, switch control process, etc.) of the entire switch.

10.2. Hardware Interface

[2161] As shown in FIGS. 8 and 64, the DS3-SMDS interface communicates with the switch software by setting simple LAP communications with the BSGCSH through the intra-switch path by way of the MDX and ASSWSH. The BSGCSH communicates with the switch processor through an interface (INF).

[2162] The extraction/insertion of an intra-station control communications cell from/to a main signal path (intra-switch highway) and the simple LAP are terminated by the EG-CLADLSI (FIG. 45) in the DS3-SMDS interface.

[2163] There is one LAP link between the DS3-SMDS interface and the BSGCSH only for the BSGCSH of an active system through an ATM switch (ASSWSH) of the active system. As shown by A and B in FIG. 64, a path is set for the ASSWSHs of both active and standby systems. The communications data from the BSGCSH to the DS3-SMDS interface is transmitted to the ASSWSHs of both active and standby systems, and the DS3-SMDS interface selects only the communications data transmitted through the ASSWSH of the active system. Likewise, the communication data from the DS3-SMDS interface to the BSGCSH is transmitted to the ASSWSH of both active and standby systems, and the communications data transmitted through the ASSWSH of the standby system is discarded by the common unit of the BSGCSH in the standby system. The common unit of the BSGCSH in the standby system identifies an intra-office control communications cell by referring to a specified area of a tag added to the header of the received cell.

[2164] The communications link between the DS3-SMDS interface and the BSGCSH is assigned a band of 64 Kbps by default, and the band is preliminarily reserved in a switch. The band is optionally defined at the instruction of the switch software.

[2165] By default, the EG-CLADLSI (FIG. 45) shapes for 64 Kbps the band of the frame of the intra-station communications LAP comprising a plurality of cells. The EG-CLDLSI prevents an intra-station communications cell addressed to its own interface from flowing out of the station by dropping/inserting into a cell forming an intra-station communication LAP frame transferred through the main signal path (intra-switch highway). In this case, the DS3-SMDS interface performs a dropping/inserting process only on an intra-station communications cell input/output upwards (at ASSWSH). No dropping/inserting processes are performed on an intra-station communications cell input/output via the line (DS3 transmission line). If the BRLC is connected to the DS3 transmission line as shown in FIG. 34 to have the DS3-SMDS interface realize an umbilical link, then the DS3-SMDS interface loaded to the RMXSH in the BRLC performs a dropping/inserting process only on an intra-station communications cell input/output upwards (at the station), and no dropping/inserting processes are performed on an intra-station communications cell input/output via the subscriber line. Therefore, the DS3-SMDS interface passes an intra-station communications cell transferred from a downward unit to the BSGCSH.

[2166] The intra-station communications cell between the DS3-SMDS interface and the BSGC has a format shown in FIG. 56 described above.

10.3. Setting VPI/VCI

[2167] The BSGC (FIG. 8) sets an intra-station communications link to the DS3-SMDS interface using the VPI/VCI values assigned by the switch software. The VPI/VCI values are VPI=00 and VCI=03FE. These VPI/VCI values are not changed while the intra-station communications connection is maintained.

[2168] FIG. 66 shows the outline of converting the VPI/VCI of the intra-station communications cell between the DS3-SMDS interface and the BSGC. The tag information required to route the intra-station communications cell from the DS3-SMDS interface to the BSGC is added by the virtual channel converter (VCC) in the SIFSH common (FIG. 8). The tag information required to route the intra-station communications cell from the BSGC to the DS3-SMDS interface is added by the VCC in the common unit of the BSGC.

10.4 Error Monitor

[2169] The DS3-SMDS interface does not directly monitor intra-station communications cells received by the DS3-SMDS interface. Accordingly, the DS3-SMDS interface accepts a cell designating itself through its tag as a valid intra-station communications cell addressed to the interface, and then processes the cell.

10.5. AAL Interface

[2170] 10.5.1. SAR-PDU Format

[2171] FIG. 67 shows the format of the intra-station communications SAR-PDU.

[2172] The ATM adaptation layer (AAL) of type 3 or 4 is adopted as the format of the SAR-PDU.

[2173] The SAR-PDU consisting of a segment type (ST), sequence number (SN), MID (don't care in the intra-station control communications cell), payload, payload byte length indicator (LI), and CRC (CRC-10 for ST, SN, MID, and payload) is stored in the payload of the ATM cell with the ATM header added to the head of the ATM cell.

[2174] Refer to 4. of part 3 to be described later.

10.6. Function of AAL

[2175] The L2 (layer 2) frame used in intra-station communications is mapped in the payload of the SAR-PDU through the CS-PDU (refer to the 4.2.2. and 4.2.3. in part 3). The AAL process performed by the DS3-SMDS interface has the functions of (1) decomposing/composing an L2 frame for a cell; (2) transmitting/receiving an intra-station communications cell; (3) detecting a bit error in the payload of a received cell; and (4) assigning a CRC to the payload of a transmitted cell.

10.7 Error Monitor

[2176] If a bit error is detected in the payload of a cell in the AAL process, then the cell is discarded. The error is stored in the DS3-SMDS interface and displayed as an MSCN. If an SN error or an ST sequence error is detected in the AAL process, them a series of cells determined to be erroneous are all discarded. In the AAL process, accepted as valid cells are those related to the SSM without payload errors, or a series of cells without sequence and payload errors from the beginning of a message (BOM) to the end of the message (EOM). A detected sequence error is held in the DS3-SMDS interface and displayed as an MSCN. No detected errors are corrected in the AAL process.

10.8. L2 Interface

[2177] 10.8.1. Functions of L2

[2178] A simple LAP is the protocol of the L2 in the intra-station communications and has the functions of (1) establishing an L2 link; (2) transmitting and receiving the L3-PDU; and (3) monitoring the state of the L2 link.

[2179] 10.8.2. Frame Format

[2180] FIG. 68 shows the format of the intra-station communications L2 frame. The frame is transmitted as being stored in the payload of the SAR-PDU shown in FIG. 67.

[2181] 10.8.3. Connection Setting Procedure

[2182] The LAP link between the DS3-SMDS interface and the BSGCSH is established when the DS3-SMDS interface is powered or reset, or the implementation of the DS3-SMDS interface to the station data is specified after powering or resetting the BSGCSH. Afterwards, the link is not disconnected by the DS3-SMDS interface or the BSGCSH regardless of the states INS and OUS of the DS3-SMDS interface. Since the connection-response VPI/VCI values are notified of in the set asynchronous balanced mode (SABM) frame transferred by the BSGCSH to the DS3-SMDS interface at the establishment of the link, the link is established at the responsibility of the BSGCSH.

[2183] 10.8.4. Monitor of Link State

[2184] The BSGCSH monitors the state of a link by transmitting a receive ready (RR) frame to the DS3-SMDS interface on a predetermined cycle (every second) and confirming the return of the RR frame from the DS3-SMDS interface. The DS3-SMDS interface does not monitor the state of a link. Therefore, the DS3-SMDS interface does not recognize the disconnection of a link due to any fault.

[2185] 10.8.5. Confirmation Procedure

[2186] According to the L2 protocol using the simple LAP, the L3 information is transferred in an unnumbered information (UI) frame. Therefore, the transfer of the L3 information is not confirmed in the L2, but in the L3 protocol.

[2187] 10.8.6. Monitor of Faults

[2188] No errors of transferred information are detected in the simple LAP protocol.

10.9. L3 Interface

[2189] 10.9.1. L3 Frame Format

[2190] FIG. 69 shows the format of the L3 frame. The frame is transmitted as being stored in the information field of the L2 frame shown in FIG. 68.

[2191] 10.9.2. Communications Procedure

[2192] The procedure of the L3 protocol is followed in a command/response format in which the switch software is a master while the DS3-SMDS interface is a slave. The switch software confirms that the DS3-SMDS interface has received a command by receiving a response to the transmitted command. The DS3-SMDS interface transmits an ACK instead of a response to a command which has no corresponding response. The DS3-SMDS interface generates the value of a transmitted ACK by adding 8000 (HEX) to the received message number. The DS3-SMDS interface does not confirm whether or not the transmitted L3 response has been received by the switch software. If information requires a positive action such as an issue of an alarm, then the information is provided by the DS3-SMDS interface to the switch software using an MSCN.

[2193] 10.9.3. Control of Errors

[2194] To detect an error related to a loss/insertion of a cell in a switch, the switch software adds a sequence number to an L3 frame of each command and transmits it to the DS3-SMDS interface, and the DS3-SMDS interface returns a response corresponding to each sequence number, thereby reserving the command/response correspondence.

11. MANAGEMENT OF THE STATE OF DS3-SMDS INTERFACE

11.1. Initialization

[2195] The DS3-SMDS interface is initialized when the printed wiring circuit board of the DS3-SMDS interface is implemented or powered. Required are the following operations at the initialization.

[2196] (1) Setting an SMDS mode (FIG. 33) or an umbilical link mode (FIG. 34) for the DS3-SMDS interface

[2197] (2) Setting the UNI mode or the ICI and ISSI modes for the DS3-SMDS interface

[2198] (3) Setting the downward DMUX-LSI buffer threshold (when necessary)

11.2. Blocking

[2199] The following processes are performed.

[2200] (1) Setting Block Specification (OUS)

11.3. Setting In-Service

[2201] The following processes are performed.

[2202] (1) Resetting the block specification (OUS)

[2203] (2) Setting/resetting master reset (M-RST)

[2204] (3) Initialization

[2205] (4) Confirming that an in-service completion indicator (INS) is set on the E-MSCN service

[2206] (5) Transferring various initialization data

11.4. Non-implementation

[2207] The following processes are performed.

[2208] (1) Setting Block Specification (OUS)

11.5. Processes for Faults

[2209] 11.5.1. Monitor of Faults

[2210] A fault of the DS3-SMDS interface is monitored by constantly monitoring both MSCNs, that is, a D-MSCN detected by the DS3-SMDS interface and provided for the switch software through the SIFSH common, and an E-MSCN detected by the SIFSH common relating to the faults of the DS3-SMDS interface. In constantly monitoring the MSCN relating to the faults of the DS3-SMDS interface itself or of the line systems, the MSCN from the SIFSH common of the active system is monitored. In constantly monitoring the MSCN relating to the faults of the DS3-SMDS interface and the faults of the interface of the SIFSH common, the MSCNs from the SIFSH common of both active and standby systems are compared with each other. In the latter case, considering the time difference in arrival of data at both systems, a detected fault in one system is made to wait for the fault information of another system for a predetermined time. The type of MSCN to be constantly monitored is notified of using a change flag of a representative NG-OR point set for each type of fault.

[2211] The types of MSCNs to be monitored for faults are listed below, and each type is assigned a representative NG-OR point. The following non-stored alarm may generate a plurality of alarms and therefore are provided with a state change flag.

[2212] (1) Hardware Fault . . . stored type

[2213] 1. specified as a fault of the DS3-SMDS interface

[2214] 2. specified as a fault of the SIFSH common

[2215] 3. fault of the interface between the SIFSH common and the DS3-SMDS interface

[2216] (2) Line System Alarm . . . not stored

[2217] (3) Threshold Crossing Alert (DS3/PLCP layer) not stored

[2218] (4) Cell Discard Start Alert in the DS3-SMDS buffer . . . not stored

[2219] Concerning the stored fault display point, an MSD (SDFTRST) should be set to reset the fault display on the MSCN. A non-stored fault display point is reset by the hardware corresponding to respective points on the specific condition to each point.

[2220] 11.5.2. Detection of Faults

[2221] The processes to be performed when each of the representative NG-OR points is detected are listed below. At each representative NG-OR point, the detailed information indicating the factor of a fault to display a message can be fetched by referring to another area of the MSCN or by directly inquiring of the individual unit through the intra-station control communications.

[2222] (1) At the detection of a hardware fault;

[2223] 1. The DS3-SMDS interface is blocked when a hardware fault possibly specified as a fault in the DS3-SMDS interface 1 is detected.

[2224] 2. When a hardware fault possibly specified as a fault in the SIFSH common is detected, an active ASSWSH system is switched to a new system. If the ASSWSH system cannot be switched, then the DS3-SMDS interface for the hardware in which a fault has been detected is blocked as being inoperable for further use. If a fault exists in a new active system after the switch to the new active system, or if a new fault occurs to switch to a new ASSWSH system, then the new active system stops monitoring faults in the SIFSH common and the DS3-SMDS interface for the system is blocked as being inoperable. In this case, the ASSWSH system is not switched back to the replaced system.

[2225] 3. If a hardware fault is detected in the interface for the SIFSH common, then one of the following determinations is made according to the MSCN information detected and displayed in both DS3-SMDS interface and SIFSH common, and an appropriate action is taken based on the determination.

[2226] (a) A fault which is possibly a DS3-SMDS interface fault

[2227] The DS3-SMDS interface is blocked.

[2228] (b) A fault which is possibly a SIFSH common fault

[2229] An ASSWSH system to be active is switched.

[2230] (c) A fault which is hardly determined to be a DS3-SMDS interface fault or an SIFSH common fault.

[2231] The DS3-SMDS interface is blocked.

[2232] (2) At the detection of a line system alarm;

[2233] The DS3-SMDS interface is blocked.

[2234] (3) At the detection of a threshold crossing alert and a cell discard start alert (cells are discarded in buffer)

[2235] Since the MSCN displays data based on a predetermined statistics process in the hardware, messages are displayed based on the displayed data.

[2236] 11.5.3. Specifying a Fault

[2237] (1) When the ASSWSH is processed as OUS;

[2238] A fault is specifies by automatic diagnostics of a faulty ASSWSH system.

[2239] (2) When the DS3-SMDS interface is blocked;

[2240] Online diagnostics is conducted on the DS3-SMDS interface and a fault is specified. If no faults are confirmed by the online diagnostics, then an ASSWSH system is switched and the diagnostics is manually carried out. A series of processes are manually performed. The online diagnostics refers to the diagnostics actually performed by a switch processor (CC) of an active system regardless of the state of the DS3-SMDS interface.

[2241] 11.5.4. Monitor of Recovery

[2242] (1) ASSWSH and DS3-SMDS interface

[2243] These units are recovered when they are changed from the OUS state to the INS state. If the active system is operated in a faulty state because of the faults detected in both of duplex SIFSH common systems, then the active SIFSH common system is monitored for faults.

[2244] (2) Line System Alarm

[2245] An MSCN monitor constantly monitors the recovery of units. If no blocking factors exist at the time of recovery, a blocked DS3-SMDS interface is released.

[2246] (3) Threshold crossing alert (DS3/PLCP Layer)

[2247] Since an automatic recovery is made at a predetermined timing, recovery is not monitored.

[2248] (4) Cell Discard Start Alert in Buffer

[2249] Recovery is constantly monitored through the monitor of the MSCN.

11.6 Various Process Sequence

[2250] FIGS. 70 through 81 show the sequence of the following processes.

[2251] (1) Initialization of DS3-SMDS interface

[2252] (2) Procedure of INS of DS3-SMDS interface

[2253] (3) Procedure of OUS of DS3-SMDS interface

[2254] (4) Hardware Fault of DS3-SMDS interface

[2255] 1. Hardware fault which enables intra-station control communications

[2256] 2. Hardware fault which disables intra-station control communications

[2257] 3. Micro processor fault

[2258] 4. Communications error between the SIFSH common and the DS3-SMDS interface (active system)

[2259] 5. Communications error between the SIFSH common and the DS3-SMDS interface (standby system)

[2260] (5) DS3/PLCP layer alarm process

[2261] (6) Notification of D/Q Timer (counting every 15 minutes and every day) at the generation of DS3/PLCP TCA (threshold crossing alert); and Collection of PM Data

[2262] (7) Notification of D/Q Timer at the generation of DS3-SMDS interface buffer alarm; and Collection of Buffer Data

[2263] (8) Setting PVC path test special number VPI/VCI cell

12. CONGESTION CONTROL OF DS3-SMDS INTERFACE BUFFER

[2264] The following interfaces function at the printed wiring circuit board of the DS3-SMDS interface.

[2265] (1) DS3 SMDS User Network Interface (UNI) interface

[2266] (3) DS3-SMDS inter-exchange carrier interface (ICI) interface

[2267] (3) DS3-SMDS inter-switching system interface (ISSI) interface

[2268] (4) DS3 umbilical link interface

[2269] If the interfaces (1) through (3) among these interfaces are realized, the DS3-SMDS interface is connected to the SBMESHH and the GWMESH (FIG. 8). Therefore, since the ATM cell transmitted according to the access class of the SMDS is shaped, no overflow occurs in the buffer in which the bit rate is converted from 156 Mbps to 45 Mbps in the DS3-SMDS interface.

[2270] However, if the DS3 umbilical link interface of (4) is realized, the lines such as DSI-SMDS, DS1-frame relay, etc. are accommodated. As a result, an overflow can be caused by the input of the burst data in the buffer which is provided in the DS3-SMDS interface and converts the bit rate from 156 Mbps to 45 Mbps.

[2271] Therefore, the DS3-SMDS interface controls the congestion in the buffer in which the bit rate is converted from 156 Mbps to 45 Mbps based on the pattern of each value of the P bit and CON bit displayed in the tag area in the header of the ATM cell in the format shown in FIG. 56.

[2272] The control data of the buffer is set by the switch software as the E-MSD information through the intra-station control communications. Nine levels of threshold should be set to perform the quality control of the buffer and the priority control. Listed below are the settings of the thresholds.

[2273] (1) Q0: physical FULL

[2274] (2) Q1: logical FULL

[2275] (3) QA: cell discard start threshold with P bit=0, CON bit=0

[2276] (4) QB: cell discard start threshold with P bit=1, CON bit=0

[2277] (5) QC: cell discard start threshold with P bit=0, CON bit=1

[2278] (6) QD: cell discard start threshold with P bit=1, CON bit=1

[2279] (7) QA′: cell discard start threshold with P bit=0, CON bit=0

[2280] (8) QB′: cell discard start threshold with P bit=1, CON bit=0

[2281] (9) QC′: cell discard start threshold with P bit=0, CON bit=1

[2282] (10) QD′: cell discard start threshold with P bit=1, CON bit=1

[2283] FIG. 82 shows the cell discard start/release threshold of the buffer.

[2284] The thresholds Q1, QA, QB, QC, QD, QA′, QB′, QC′, and QD′ are set through the intra-station control communications, and the cell discard is set and discarded as follows.

[2285] (1) When the queue length exceeds the threshold, the state is provided for the microprocessor in the DS3-SMDS interface, thereby notifying the switch software through the intra-station control communications that the cell discard is started. At the insertion of the DS3-SMDS interface PKG and at the reset of the hardware, the cell discard start threshold is set to the value of the maximum buffer length, that is, the initial value.

[2286] (2) If the queue length has been recovered to the cell discard release value, then the state is provided for the microprocessor, thereby notifying the switch software through the intra-station control communications that the cell discard release is started.

[2287] (3) If the queue length has reached the threshold Q1, then the microprocessor is notified of the occurrence of a fault, and even a valid cell is controlled to be prevented from being written into its buffer.

[2288] (4) Each threshold should be set through the intra-station control communications with the following conditions satisfied.

[2289] Q0>Q1>QA>QA′>0 Q0>Q1>QB>QB′>0

[2290] Q0>Q1>QC>QC′>0 Q0>Q1>QD>QD′>0

13. TEST AND MAITENANCE

13.1. Loopback Function of DS3-SMDS Interface

[2291] The DS3-SMDS interface printed circuit board (PCB) has the following four loopback functions for proper sequence and maintenance operations.

[2292] (1) Loopback function of a cell with a 0 bit added to its tag area

[2293] (2) Loopback function of all cells

[2294] (3) Loopback function of a cell assigned a specific VPI/VCI

[2295] (4) Line Loopback function

[2296] FIG. 83 shows the implementation position of the loopback function in the DS3-SMDS interface (FIG. 45).

[2297] 13.1.1. Loopback Function of a Cell with 0 Bit Added at Tag Area

[2298] The DS3-SMDS interface has the loopback function of a cell with a 0 bit added to its tag area. The cell with a 0 bit added to its tag area is generated by a test cell generator (TCG) for a circuit test. Since the DS3-SMDS interface passes only an ATM cell of an active system, a circuit test cell is entered through the ASSWSH of the active system.

[2299] The activate and stop instruction of the loopback function is issued through the 0-LOOP bit in the E-MSD shown in FIGS. 58 and 59. However, according to the configuration of the hardware, the loopback function of a cell having the 0 bit and the loopback function of a cell having the specific VPI/VCI cannot be activated simultaneously.

[2300] 13.1.2. Loopback Function of All Cells

[2301] The DS3-SMDS interface has the loopback functions of all cells at the position (HAF00A or HDT00A shown in FIG. 45) indicated as (1) or (2) in FIG. 83. The loopback function should be activated after the DS3-SMDS interface is blocked.

[2302] The loopback function activate instruction is issued through the LOOP-1 bit (for position (1)) or the LOOP-2 bit (for position (2)) shown in FIGS. 58 and 59 using the E-MSD terminating the SIFSH common.

[2303] The loopback function enables a transmission test to be performed on an ATM cell including DS3/PLCP layer data. However, if the DS3-SMDS interface is operating in a DS3-SMDS service mode (as shown in FIG. 33), then the DS3-SMDS interface passes only the ATM cell having VPI=3F and VCI=03FF (refer to FIGS. 7, 10, and 55). Therefore, the values of VPI and VCI should be set for the cell entered in the DS3-SMDS interface at the test.

[2304] 13.1.3. Loopback Function of Cell Having Specific VPI/VCI

[2305] The DS3-SMDS interface has the loopback function of the cell assigned a specific VPI/VCI at the position (HAF00A shown in FIG. 45) to which a transmission line is connected from the SIFSH common shown as (3) in FIG. 83.

[2306] At the activation of the loopback function, the values of specific VPI/VCI are provided through intra-station control communications. Simultaneously looped back in this loopback function are only the ATM cells having one set of values of VPI/VCI. Therefore, to test the values of another set of VPI/VCI, the loopback function should be activated again after setting the values.

[2307] The activation and stop of the loopback function are directed by the V-LOOP bit in-the E-MSD shown in FIGS. 58 and 59.

[2308] 13.1.4. Line Loopback Function

[2309] The DS3-SMDS interface has the function of looping back the signal input via the DS3 PCM line (DS3 transmission line) at the position (HDT00A shown in FIG. 45) indicated corresponding to (4) in FIG. 84.

[2310] The activation of the loopback function is directed by the LOOP-3 bit in the E-MSD shown in FIGS. 58 and 59.

[2311] The loopback function is used to confirm the normality of the DS3 PCM line in, for example, a construction test.

13.2. Test Method

[2312] Listed below are methods of testing the DS3-SMDS interface using various loopback functions explained above.

[2313] (1) DS3-SMDS line loopback test

[2314] (2) Active system on-demand test

[2315] (3) PVC path circuit test

[2316] (4) DS3-SMDS interface test and diagnostics

[2317] 13.2.1. DS3-SMDS Line Loopback Test

[2318] The line loopback test performed by the DS3-SMDS interface can be realized by a manual loopback test at the DSX-3 and a loopback test at the RCL.

[2319] (1) Line Loopback Test at DSX-3

[2320] In this test, an ATM cell is tested in acceptability, line quality, etc. by manually activating the loopback function at the distribution panel digital signal cross-connect (DSX)-3. To realize the test, a test cell having a random test pattern is generated at the TCG after setting a path between the test cell generator (TCG) and the DS3-SMDS interface, and the test cell is transmitted to the path.

[2321] FIG. 84 shows the outline of the line loopback test of the DSX-3.

[2322] (2) Line Loopback Test at RLC

[2323] In this test, an ATM cell is tested in acceptability, line quality, etc. by manually activating the loopback function at the remote line concentrator (RLC). To realize the test, as in the test explained in (1) above, a test cell having a random test pattern is generated at the TCG after setting a path between the TCG and the DS3-SMDS interface, and the test cell is transmitted to the path.

[2324] FIG. 85 shows the outline of the line loopback test at the RLC.

[2325] 13.2.2. Active System On-demand Test

[2326] The active system on-demand test is conducted at the occurrence of a fault of the DS3-SMDS interface to specify a faulty point by entering a command of a maintainer. In this case, the loopback function explained in 13.1.1. is activated, a cell is generated with a 0 bit added in the tag area in the TCG, and the DS3-SMDS interface loops back only the cells having the 0 bit. Checking this state specifies the faulty point.

[2327] 13.2.3. PVC Path Circuit Test

[2328] If the DS3-SMDS interface operates in a mode of providing DS3-SMDS services (as shown in FIG. 33), then the DS3-SMDS interface is connected to the SBMESH and GWMESH through a permanent virtual circuit (PVC). To conduct a path circuit test of PVC, the DS3-SMDS interface is blocked first. Then, activated is the loopback function described in 13.1.2. by the LOOP2 bit in the E-MSD shown in FIGS. 58 and 59. Then, the SBMESH and GWMESH generate a test cell assigned the same VPI/VCI as the PVC, and transmits the cell to the DS3-SMDS interface, thereby confirming the path circuit test of the PVC.

[2329] FIG. 86 shows the outline of the pass circuit test of the PVC between the DS3-SMDS interface and the SBMESH and GWMESH. In FIG. 86, the MH-COM corresponds to the SBMESH or GWMESH.

[2330] 13.2.4. Tests and Diagnostics of DS3-SMDS Interface

[2331] Listed below are the tests and diagnostics of the printed circuit board of the DS3-SMDS interface.

[2332] (1) ATM cell acceptability test in DS3-SMDS interface

[2333] (2) Hardware normality confirmation test in DS3-SMDS interface

[2334] 13.2.4.1. ATM Cell Acceptability Test in DS3-SMDS interface

[2335] The DS3-SMDS interface is blocked first to conduct an ATM cell acceptability test in the DS3-SMDS interface PCB. Then, the loopback function explained in 13.1.2. is activated by the LOOP-1 or LOOP-2 bit in the E-MSD shown in FIGS. 58 and 59.

[2336] Listed below is the procedure of the ATM cell acceptability test in the DS3-SMDS interface.

[2337] (1) The DS3-SMDS interface PCB is blocked (OUS: out of service).

[2338] (2) The SIFSH common sets LOOP-1 or LOOP-2 in the E-MSD.

[2339] (3) Settings of LOOP-1 or LOOP-2 are confirmed.

[2340] (4) A path is set between the DS3-SMDS interface and the TCG.

[2341] (5) A cell is transmitted from-the TCG.

[2342] (6) A test cell from the DS3-SMDS interface to the TCG is confirmed.

[2343] (7) LOOP-1 or LOOP-2 is released.

[2344] (8) The release of LOOP-1 or LOOP-2 is confirmed.

[2345] (9) The path between the DS3-SMDS interface and the TCG is released.

[2346] 13.2.4.2 Hardware normality confirmation test

[2347] The DS3-SMDS interface PCB is loaded with the self-diagnostics function to confirm the normality of its hardware. By activating the self-diagnostics function, the normality of the hardware of the simplex portion (excluding the communications unit) of the DS3-SMDS interface can be confirmed.

[2348] Listed below are the steps of the self-diagnostics of the hardware in the DS3-SMDS interface.

[2349] (1) Initialization

[2350] (2) Checking the SRAM

[2351] (3) Checking the dual port RAM (simple LAPD process)

[2352] (4) Read/write check of each LSI loaded on the DS3-SMDS interface

[2353] (5) Pseudo-fault check on each checker loaded on the DS3-SMDS interface

[2354] The activation of the self-diagnostics function of the DS3-SMDS interface is directed by the DS3DEC bit in the E-MSD shown in FIGS. 58 and 59. The termination of the self-diagnostics is indicated by the TSTEND bit in the E-MDCN shown in FIGS. 61 and 63. The result of the self-diagnostics is also indicated by the TSTIND bit in the E-MSCN. After the self-diagnostics, the DS3-SMDS interface enters a wait-for-reset state, and the state is released by a hardware reset or microprocessor reset. The self-diagnostics function can be activated only by the DS3DEC bit in the E-MSD shown in FIGS. 58 and 59, but cannot be activated even if the DS3-SMDS interface is powered and reset. The self-diagnostics time of the DS3-SMDS interface requires about 12 seconds after setting the DS3DEC bit ON. Therefore, a total of about 15 seconds are required after the DS3DEC bit is set ON before the result is displayed.

14. FAULT CORRECTION

14.1. Fault Detection Point and Notification System

[2355] Listed below are the fault detection and notification system for each fault state as being associated with each fault correction process in the DS3-SMDS interface loaded in the subscriber interface shelf (SIFTH).

[2356] 14.1.1. Contents of Faults

[2357] (1) OBP fault (OBP fault loaded on each package)

[2358] (2) Fault of lost packages

[2359] (3) Fault of disconnected fuse

[2360] (4) Fault of erroneous insertion of package

[2361] (5) Fault of individual unit package (fault of simplex unit)

[2362] 14.1.2 OBP Fault

[2363] In the SIFSH, power-through packages are loaded separately on both sides of the shelf as shown in FIG. 87. Electric power is supplied for a half shelf independently.

[2364] 14.1.3. OBP Fault in Individual Unit (DS3-SMDS interface)

[2365] A fault of an OBP (power source) loaded on the DS3-SMDS interface 1 is detected in the SIFSH common (SIF-COM, common unit) in both active and standby systems. The fault is detected by monitoring the display of the individual unit OBP fault register in the SIFSH common and the occurrence of a stack in the E-MSCN highway.

[2366] An output of the LED output terminal unit of the OBP indicates an open state in a normal operation and a ground state in an abnormal operation. When an output of the LED terminal unit indicates the ground state, a fault value is set in the OBP fault register.

[2367] FIG. 88 shows the configuration of the OBP monitoring function in the individual unit.

[2368] (1) +5V OBP Fault

[2369] If a +5V OBP fault has arisen in the DS3-SMDS interface individual unit, then a serial highway for the extended maintenance scanner (E-MSCN) information to be provided for the SIFSH common is blocked with a stack. There are representative points indicating the IDs of the individual units in the E-MSCN, and the occurrence of a stack for the points is monitored by the SIFSH common. Therefore, if the SIFSH common detects the indication of a fault through the OBP fault register and detects an occurrence of a stack in the E-MSCN highway, then a +5V OBP fault is detected.

[2370] (2) −5.2V OBP Fault

[2371] If the SIFSH common detects a fault indication through the OBP fault register and does not detect an occurrence of a stack in the E-MSCN highway, then a −5.2V OBP fault is detected.

[2372] 14.1.4. Package Missing Fault

[2373] A package missing fault with a package which forms part of the DS3-SMDS interface 1 is detected by the SIFSH common of both active and standby systems. The fault is actually detected by monitoring the display of the individual unit OBP fault register in the SIFSH common and the occurrence of a stack in the E-MSCN highway. Each individual unit comprises a plurality of packages. If there is a package missing among a plurality of packages, then the +5V power source to be provided in the entire package group in the individual unit is not induced. Accordingly, the SIFSH common monitors the items indicating the ID point of the individual unit in the E-MSCN toward the SIFSH common to detect all “H” (high level) for the items. Then, the SIFSH common determines a package missing only if it receives a package missing notification from the SIFSH common of both active and standby systems. If the SIFSH common receives the package missing notification from only one of the systems, then it determines that an interface fault has occurred between the individual unit and the SIFSH common. The state is checked when the systems are switched.

[2374] FIG. 89 shows the configuration of the package missing monitoring function.

[2375] 14.1.5. Fuse Disconnection Fault

[2376] The individual unit fuse provided for the power package is individually monitored in the SIFSH common of both active and standby systems. An alarm contact-point loop checked by a disconnection of the fuse is monitored in the SIFSH common of both systems.

[2377] FIG. 90 shows the configuration of the fuse disconnection monitoring function in the SIFSH common.

[2378] The disconnection of a fuse causes a package missing fault to be detected because a highway stack simultaneously occurs in a corresponding individual unit. However, a fuse disconnection fault is detected by priority by the firmware in the SIFSH common, and the switch software is notified only of the occurrence of a fuse disconnection fault.

[2379] 14.1.6. Package Error Insertion Fault

[2380] In the SIFSH, a package group comprising a plurality of packages in the individual unit and the SIFSH common can have the configuration in which the OBP can be activated only if all packages are inserted. Therefore, even if a package is erroneously inserted, the shelves are not successfully operated but the packages and their circuit elements are not destroyed.

[2381] 14.1.7. DS3-SMDS Interface Individual Unit Package Fault

[2382] There are following two types of hardware faults of a package in the DS3-SMDS interface individual unit.

[2383] (1) Hardware fault notified of through the intra-office control communications using the E-MSCN from the SIFSH common

[2384] (2) Hardware fault notified of through the intra-office control communications from the DS3-SMDS interface

[2385] First, listed below are the points in the C-MSCN shown in FIGS. 61 through 63 as being related to the faults defined by (1) above.

[2386] 1. MPE (micro-processor fault)

[2387] 2. FEER-1 (fault indicating that the intra-station control communications cannot be established by the DS3-SMDS interface)

[2388] 3. UH19M (SIFSH common transmission click fault)

[2389] 4. UHDPT (upward highway data parity error fault)

[2390] 5. EGPTY (intra-station control communications terminal LSI fault)

[2391] Next, listed below are the points in the C-MSCN shown in FIGS. 61 through 63 as being related to the faults defined by (2) above. The DS3-SMDS interface is required to read detailed data through the intra-station control communications and notifies the switch software of the data so that the SIFSH common can notify the switch software of the NG OR condition.

[2392] 1. FEER-2 (DS3-SMDS interface PCB hardware fault OR condition)

[2393] If the DS3-SMDS interface hardware fault, which is notified of by the intra-station control communications using the E-MSCN from the SIFSH common for the switch software, occurs, then the DS3-SMDS interface is blocked.

15. FUNCTIONS OF EACH PCB

15.1. Functions of Each PCB

[2394] 15.1.1. Functions of HAF00A

[2395] The most important function of the HAF00A (FIG. 45) is an interfacing function with the SIFSH common. Among the functions of the DS3-SMDS interface described in 7., the following functions are loaded.

[2396] (1) LAP terminating function for MSD/MSCN Information

[2397] (2) Interfacing function to the SIFSH common

[2398] (3) Multiplexing/demultiplexing function for DS3-SMDS L2-PDU cell and LAP cell

[2399] (4) Loopback function for specific VPI/VCI cell

[2400] (5) Multiplexing function for MSCN data

[2401] (6) MSD data dropper function

[2402] (7) Active control function

[2403] (8) Microprocessor interface function

[2404] 15.1.1.1. LAP Terminating Function for MSD/MSCN information

[2405] This function is described in 7.11. above, and realized by the EGCLAD LSI (FIG. 45) and the firmware. The functions are shared as follows.

[2406] (1) Terminating function by EGCLAD LSI

[2407] 1. Multiplexing/demultiplexing function for L2-PDU cell and LAP cell

[2408] 2. Terminating function for SAR-PDU

[2409] (2) Terminating function of firmware

[2410] 1. Terminating function for L2 frame interface

[2411] 2. Terminating function for L3 frame interface

[2412] 15.1.1.2. Interfacing Function with SIFSH Common

[2413] This function is described in 7.10 above.

[2414] The interface between the SIFSH common and the DS3-SMDS interface to the L2-PDU cell has 8-bit width of parallel data. The DS3-SMDS interface processes 16-bit width of parallel data at the transmission speed of 9.72 Mbps. Therefore, the HAF00A converts data having the above mentioned data width at the above mentioned transmission speed.

[2415] 15.1.1.3. Multiplexing/demultiplexing function for DS3-SMDS L2-PDU cell and LAP cell

[2416] These functions are explained in 7.12. and 7.13, and realized by the EGCLAD LSI.

[2417] The EGCLAD LSI sets ON the register in the EGCLAD LSI through the firmware when the LAP cell is transmitted. Thus, the EGCLADLSI multiplexes the L2-PDU cell and the LAP cell according to the LAP cell transmission clock (64 Kbps).

[2418] In demultiplexing cells, the EGCLAD LSI demultiplexes the L2-PDU and LAP cells based on the SIG bit (FIG. 56) in the tag area of the received ATM cell, and inserts a blank cell to a time slot at which the LAP cell is demultiplexed.

[2419] 15.1.1.4. Loopback Function for Cell assigned Specific VPI/VCI

[2420] The DS3-SMDS interface has the loopback functions for cells assigned a specific VPI/VCI, that is, the function of looping back a cell assigned a 0 bit in the tag area explained in 13.1.1. and a cell assigned a specific VPI/VCI explained in 13.1.3.

[2421] The functions are realized by the SEL N1 LSI (FIG. 45).

[2422] 15.1.1.5. Multiplexing Function for MSCN Data

[2423] This function is explained in 7.15, and realized by the firmware and hardware. The firmware is interfaced with the hardware through the dual port RAM (FIG. 45). The bits contained in and after the 003th byte shown in FIGS. 61 through 63 are controlled by the firmware, and the control result is written to the dual port RAM. However, the MPE bit in the 017th byte is processed by the hardware.

[2424] Data are sequentially read from the dual port RAM using as an address an output, from the SIFSH common, of the counter operating according to the MSCN interface clock. The read data is assigned a control bit of the 000th and 002nd byte as shown in FIGS. 61 through 63, and the resultant data group is transmitted as the MSCN information to the SIFSH common.

[2425] 15.1.1.6. MSD Data Dropper Function

[2426] This function is explained in 7.16, and realized by the firmware and hardware. The firmware is interfaced with the hardware through the dual port RAM (FIG. 45) as in the case described in 15.1.1.1. The MSD serial data transmitted from the SIFSH common is written to the dual port RAM after being converted into 8-bit parallel data. The written data is read by the firmware on a cycle of 10 ms. If the same data is read consecutively for 2 cycles, then the data is fetched in the firmware.

[2427] 15.1.1.7. Active Control Function

[2428] This function allows the control shown in FIG. 91 to be executed according to the ACT information transferred from the SIFSH common of both active and standby systems.

[2429] 15.1.1.8. Microprocessor Interface Function

[2430] The HAF00A PCB is loaded with the 80C186 processor and outputs processor interface signals of the HAF00A and other PCBs.

[2431] 15.1.2. Functions of HLP01A

[2432] The most important function of the HLPP1A (FIG. 45) is to perform a process specific to the DS3-SMDS.

[2433] Among the DS3-SMDS interface functions described in 7., the following functions are loaded.

[2434] (1) 156 Mbps→45 Mbps data conversion function

[2435] (2) 45 Mbps→156 Mbps data conversion function

[2436] (3) Distributed queue dual bus (DQDB) process function

[2437] The outline of these functions is explained below. FIG. 92 shows the configuration of the function.

[2438] 15.1.2.1. 156 Mbps→45 Mbps Data Conversion Function

[2439] This function is described in 7.9.

[2440] The L2-PDU cess from the SIFSH common is transmitted as 8-bit parallel data at a bit rate of 156 Mbps. The cell is converted in the HAF00A LSI into a cell to be transmitted as a 16-bit parallel data at a bit rate of 156 Mbps. Then, this cell is converted in the HLP01A into a cell transmitted as an 8-bit parallel data at the bit rate 45 Mbps of the DS3 layer.

[2441] The 156 Mbps→45 Mbps data conversion function is realized by the V2 FMUX LSI. The V2 FMUX LSI performs congestion control of the 156 Mbps→45 Mbps data conversion buffer when the DS3-SMDS interface realizes a DS3 umbilical link interface as described in 12. above. The conversion buffer is realized by the DMUX LSI (FIG. 45) in the HLP01A. The congestion control of this buffer is performed using 9 levels of a threshold as explained in 12. by referring to FIG. 82.

[2442] 15.1.2.2. 45 Mpbs→156 Mbps Data Conversion Function

[2443] This is the function explained in 7.4. above.

[2444] The L2-PDU data from the DS3 transmission line is received at a bit rate of 45 Mbps. Then, the data is converted in the HDT00A PCB (FIG. 45) into the data transmitted as an 8-bit parallel data at a bit rate of 45 Mbps, and input to the HLP01A. Then, the data is converted in the HLP01A into the data to be transmitted as a 16-bit parallel data at a bit rate of 156 Mbps, and input to the HAF00A (FIG. 45).

[2445] The 45 Mpbs→156 Mbps data conversion function is realized by the V2 DMUX LSI.

[2446] 15.1.2.3. DQDB Process Function

[2447] This function is explained in 7.6. above.

[2448] 14.1.3. Functions of HDT00A

[2449] The most important function of the HDT00A (FIG. 45) is to interface with the DS3 transmission line. Among the DS3-SMDS interface functions described in 7., the following functions are loaded.

[2450] (1) DS3 layer terminating function

[2451] (2) DS3 PSCP layer terminating function

[2452] (3) Received L2-PDU header check function (HCS)

[2453] (4) L2-PDU header pattern generating function

[2454] 15.1.3.1. DS3 Layer Terminating Function

[2455] This function is explained in 7.2. above.

[2456] 15.1.3.2. DS3 PLCP Layer Terminating Function

[2457] This function is explained in 7.3. above.

[2458] 15.1.3.3. Received L2-PDU Header Check Function (HCS)

[2459] This function is explained in 7.4. above. The header check function is switched between the SMDS service and the umbilical link of the DS3-SMDS interface 1.

[2460] 15.1.3.4. L2-PDU Header Pattern Generating Function

[2461] This function is explained in 7.5. above. As in the case described above of the header check function, the header check function is switched between the SMDS service and the umbilical link of the DS3-SMDS interface 1.

16. FIRMWARE INTERFACE

16.1. General Descriptions

[2462] The DS3-SMDS interface is loaded with the 80C186 processor to realize the following functions.

[2463] (1) DS3 layer performance monitor

[2464] (2) PLCP layer performance monitor

[2465] (3) DS3 layer carrier group alarm (CGA) declaration and release

[2466] (4) PLCP layer carrier group alarm (CGA) declaration and release

[2467] (5) DS3-SMDS interface hardware alarm

[2468] (7) Intra-station control communications (simple LAPD)

16.2. Outline of Interface Between Hardware and Firmware

[2469] The interface between the hardware and the firmware in the DS3-SMDS interface is realized using the control chip select (CS) from the 80C186 processor.

[2470] The control chip select conditions in each interface are listed below, and FIG. 93 is a memory map of the DS3-SMDS interface. FIG. 45 is referred to if necessary.

[2471] (1) SRAM area: controlled by the LCS

[2472] (2) ROM area: controlled by UCS

[2473] (3) EGCLAD LSI dual port RAM area: controlled by the MCS0

[2474] (4) EGCLAD LSI control register area: controlled by the MCS1

[2475] (5) Downward DMUX LSI control register area: controlled by the MCS2

[2476] (6) Upward DMUX LSI control register area: controlled by the MCS2

[2477] (7) Downward SELN1 LSI control register area: controlled by the PCS0

[2478] (8) Upward SELN1 LSI control register area: controlled by the PCS0

[2479] (9) MAPLE2 LSI control register area: controlled by the PCS1

[2480] (10) DS3 LSI control register area: controlled by the PCS2

[2481] (11) DS3 LINE INF (HDT00A) control register area: controlled by the PCS3

[2482] (12) Debugger interface: controlled by the PCS4

[2483] (13) DS3 SWITCH INF (HAF00A) control register area: controlled by the PCS5

[2484] (14) DS3 CONTROL INF (HAF00A) control register area: controlled by the PCS6

[2485] The LCS, UCS, and MCS 0 through 3 are allocated to the memory space while the PCS 0 through 6 are allocated to the I/O space.

[2486] [0009]

[2487] <Part 3>

[2488] The subscriber interface shelf (SIFSH) is explained in detail in Part 3.

1. GENERAL DESCRIPTION

1.1. Position of SIFSH in the System

[2489] FIG. 94 shows the position of the SIFSH shown in FIG. 8 in the system. The SIFSH is hereinafter referred to as the SIFSH-A.

[2490] The subscriber interface shelf type A (SIFSH-A) can be loaded with up to 8 units per shelf of the individual units containing the ATM subscriber interface circuits.

[2491] The following 5 types of the individual units can be accommodated.

[2492] (1) OC3C (156 Mbps optical interface unit) (simplex configuration)

[2493] (2) DS-3 (45 Mbps metallic interface unit) (simplex configuration)(DS3-SMDS interface explained in Part 2)

[2494] (3) ADSINF (ADS1SH concentrator unit) (duplex configuration)

[2495] (4) TCGADP (TCGSH adapter unit) (simplex configuration: two systems of the TCGSH are connected to a single unit)

[2496] (5) LOOP (156 Mbps loop unit) (duplex configuration)

[2497] Each unit of the OC3C, DS-3, and TCGADP has a simplex configuration. Each unit of the ADSINF and LOOP has a duplex configuration. If the units are mounted to the SIFSH-A, then a two-unit set is accommodated. Accordingly, up to 4 sets of the ADS1NF and LOOP units can be loaded per shelf.

[2498] The active/standby control for each unit of the ADS1NF and LOOP can be performed by the SIFSH common unit (hereinafter referred to as the SIFCOM).

[2499] If the SIFSH-A (SIFSH) is mounted to the right of the ASSW (ATM switch) in FIG. 94, then the SIFSH-A functions as shelf exclusive to the load of the LOOP unit. If the SIFSH-A is mounted to the left of the ASSW (ATM switch) in FIG. 94, then the SIFSH-A functions as shelf for loading the individual unit which terminates a subscriber line.

[2500] The SIFCOM in the SIFSH-A performs the intra-station signalling process to the broadband signaling group controller shelf (BSGC) connected to the ASSW through the BSGCSH. The BSGC converts the command issued by the switch software and executed by the switch processor (CC) (not shown in the drawings) by way of the interface type T (INFT) into an intra-station signalling signal, and controls the SIFCOM according to the signal. A fault detected in the SIFCOM and a response to the above described command are provided for the BSGC as intra-station signals and transmitted to the switch software through the INFT.

[2501] A simple LAP-D protocol is adopted to the intra-station signalling process. The simple LAP-D protocol is developed to minimizing the function of the hardware and firmware based on the LAP-D protocol.

[2502] Among the individual units accommodated in the SIFSH-A, each unit of the OC-3C and DS-3 communicates with the BSGC using the simple LAP-D protocol. The TCGADP, LOOP, and ADSINF do not have the simple LAP-D protocol terminating function.

[2503] The SIFCOM analyzes a command received using the simple LAP-D protocol, multiplexes in time divisions the command in an EMSD highway if the analysis result indicates a command to an individual unit, and notifies the individual unit of the result.

[2504] The SCN information from the individual unit is multiplexed in time divisions in the EMSCN highway and notified to the SIFCOM. The SIFCOM detects a change in EMSCN information in each bit, and notifies the switch software through the BSGC using the simple LAP-D protocol of the SCN information containing only the signal of a bit whose data change is detected.

[2505] The SIFCOM demultiplexes an ATM cell corresponding to each individual unit from the downward cell highway which has a transmission speed of 622 Mbps and is connected to the ASSW, and sends it to a downward cell highway which has a transmission speed of 156 Mbps and is connected to each individual unit.

[2506] The ATM cell in the 156 Mbps upward cell highway connected to each individual unit is multiplexes in the 622 Mbps cell highway connected to the ASSW. A scheduler system is adopted to a cell multiplexing system as described later in 6.1.2. The scheduler system multiplexes an upward cell from each individual unit in the arrival order such that the order can be maintained correctly in both active and standby systems. As a result, the systems can be switched in a minimum cell-loss state when the systems are switched in the ASSW and SIFCOM.

[2507] The SIFSH-A can accommodate up to 8 individual units per shelf. However, to improve the multiplexing of cells from the 156 Mbps highway to the 622 Mbps highway, two SIFSH-A can be connected serially. This daisy chain configuration enables the ATM cell in 16 cell-highways of 155 Mbps to be multiplexed in a single 622 Mbps cell-highway.

1.2. Outline of Functions

[2508] The function of the SIFSH-A is described below.

[2509] (1) Multiplexing Cells (156 Mbps cell highway→622 Mbps cell highway)

[2510] Priority control by a scheduler system

[2511] Counting the number of passing ATM cells having specified VPI/VCI for each 156 Mbps cell highway

[2512] Counting the number of discarded cells for each 156 Mbps cell highway

[2513] Counting the number of all passing cells for each 156 Mbps cell highway

[2514] Cell buffer FIFO for 52 cells for each 156 Mbps cell highway

[2515] Monitoring the volume of a cell buffer (queue length)

[2516] 4 levels of congestion control for a cell buffer using P and COM bits

[2517] (2) Demultiplexing Cells (622 Mbps cell highway 156 Mbps cell highway)

[2518] Demultiplexing cells by a cell header tag comparison system

[2519] Dynamic assignment of a comparison tag in consideration of protection line switching

[2520] Counting the number of passing ATM cells having specified VPI/VCI for each 156 Mbps cell highway

[2521] Counting the number of discarded cells for each 156 Mbps cell highway

[2522] Counting the number of all passing cells for each 156 Mbps cell highway

[2523] Cell buffer FIFO for 112 cells for each 156 Mbps cell highway

[2524] Monitoring the volume of a cell buffer (queue length)

[2525] 4 levels of hysteresis congestion control for a cell buffer using P and COM bits

[2526] (3) Header Conversion Function (VCC)

[2527] VCC for each 156 Mbps cell highway

[2528] Memory space of 216 addresses×28 bits per line

[2529] Boundary control of conversion addresses of input VPI/VCI (VPI/VCI=0/16˜8/8)

[2530] Collectively resetting VCC memory

[2531] Copying the contents of the VCC memory to another system when the INS is incorporated

[2532] Passing/conversion variable mode of ATM cell having 0 bit

[2533] (4) Individual Unit Interface

[2534] Transmitting and receiving cells in a 156 Mbps cell highway

[2535] Generating and checking the parity of a cell in a 156 Mbps cell highway

[2536] Passing/discard control of a cell from an individual unit of a standby system (monitoring 0 bit)

[2537] Detecting an individual unit missing

[2538] Specifying the slot number of an individual unit

[2539] Specifying active/standby switching for a duplex device (MUXACTD signal)

[2540] Notifying of completion of active/standby switching from a duplex device (MUXACTU signal)

[2541] Receiving EMSCN information (256 bytes/4 msec) from an EMSCN serial highway

[2542] Transmitting EMSD information (256 bytes/4 msec) to an EMSD serial highway

[2543] Transmitting a hard reset signal

[2544] Transmitting a 64 KHz reference signal

[2545] (5) Switch Interface

[2546] 622 Mbps cell highway interface (78 Mbps×8 bit parallel ECL signal, 50-core coaxial flat cable)

[2547] Generating and checking the parity of a cell in a 622 Mbps cell highway

[2548] Monitoring cell frame and 78M clock disconnection (50-core coaxial flat cable)

[2549] Receiving a system switch signal (20-core cable)

[2550] Monitoring 20-core cable missing through monitoring 2.5 MHz clock

[2551] (6) Daisy Chain

[2552] 622 Mbps cell highway interface (78 Mbps×8 bit parallel ECL signal, 50-core coaxial flat cable)

[2553] Generating and checking the parity of a cell in a 622 Mbps cell highway

[2554] Monitoring cell frame and 78M clock disconnection from a lower order shelf by a higher order shelf (50-core coaxial flat cable)

[2555] Transmitting and receiving a system switch signal (20-core cable)

[2556] Transmitting 2.5 MHz clock from a higher order shelf to a lower order shelf (20-core cable)

[2557] Transmitting a system switch signal from a higher order shelf to a lower order shelf (20-core cable)

[2558] Transmitting and receiving a scheduler control signal

[2559] (7) Intra-station Signalling Through a Simple LAP-D

[2560] Terminating a simple intra-station LAP-D protocol (AAL layer type 3)

[2561] Receiving cell buffer for 11 cells

[2562] Selecting transmission shaping clock

[2563] (8) Connection and Cross-connection

[2564] Connection and cross-connection of VCC copy address data buses

[2565] Connection and cross-connection of VCC copy gate open/close control register

[2566] Communications control through SIC-LSI

[2567] Multicast transmission of an upward signalling cell to both systems

[2568] (9) Clock

[2569] Extracting reference clock from the SYNSH (two systems)

[2570] (10) Test

[2571] Loopback of a test cell in a 156 Mbps cell highway (cell-by-cell/collective selection available)

[2572] Preventing a corresponding test cell from flowing to an individual unit at the loopback of a test cell

[2573] Various self-diagnostics

[2574] (11) Power Source

[2575] −48V 5 system/one-way supply

[2576] Loading each SIFCOM and individual unit with an onboard power module (OBP)

[2577] Automatic power down of the SIFCOM of a corresponding system and other packages because of package missing

2. SHELF CONFIGURATION

[2578] The SIFSH-A is loaded on a high power frame (HPF), and the maximum number of the SIFSH-A is 3 (steps).

2.1. Configuration

[2579] Described below are the SIFCOM and each individual unit.

[2580] 2.1.1. SIFCOM

[2581] The SIFCOM is fixedly loaded on the SIFSH-A and is composed of 5 packages per system as shown in FIG. 95.The HPT01A package in the SIFCOM provides each unit in a single system with a −48V power source. Each of the systems on the right and left of the center of the shelf is power-supplied separately.

[2582] 2.1.2. Individual Unit

[2583] Up to 8 individual units can be loaded on the SIFSH-A.

[2584] Each individual unit is composed of 3 packages per unit. The names of slots accommodating these packages are slots A, B, and C from left to right.

2.2. Power Source System

[2585] The power sources of the SIFSH-A are three types, that is, −48V/CG, SAB/SABG, and +5V/E. However, CG and E are completely separated, and the earth (E) is connected to the signal earth (SG).

[2586] 2.2.1. −48V/CG

[2587] Systems 0 and 1 are separated at the center of the shelf. −48V/CG is power-supplied independently from the power through package to each individual unit and SIFCOM. The power through package is loaded with a maintainer fuse corresponding to each individual unit and SIFCOM. The CG is independently connected to each of the systems on the right and left of the center of the shelf.

[2588] 2.2.2. SAB/SABG

[2589] Systems 0 and 1 are separated at the center of the shelf.

[2590] The SABG is connected to the ALMSH through a misk plate.

[2591] 2.2.3. +5V/E

[2592] +5V is provided in each of the individual units. The earth E is shared among systems 0 and 1.

[2593] The power sources −48V/CG and SAB/SABG of the present shelf are provided by the power through package.

3. PHYSICAL INTERFACE

[2594] Described below are the interface and signal timing between the SIFSH-A and other units.

3.1. Switch Interface

[2595] The SIFSH-A comprises a 622 Mbps cell highway and an interface of a system switch signal line to the ATM switch (ASSW). As shown in FIG. 96, an interface of the 622 Mbps cell highway is established using a 50-core flat coaxial cable between the MUX package (HMX04A) in the SIFSH-A and the SWMDX (HMX03A shown in FIG. 246) in the ASSW. An interface of a system switch signal is established using a TD bus cable between the PRC package (HSF01A) in the SIFSH-A and one of the SWTIF, SWMDX, SWCNT, and SWMX in the ASSW. The TD bus cable consists of 20 cores at the SIFSH-A and 26 cores at the ASSW.

[2596] 3.1.1. 622 Mbps Cell Highway Interface

[2597] FIG. 97 shows an interface timing for the 622 Mbps cell highway in the 50-core flat coaxial cable. The parity of the ISIPT and OSIPT is a vertical odd-number parity for 8-bit data excluding an enable signal.

[2598] 3.1.2. System Switch Signal

[2599] FIG. 98 shows the interface timing for the system switch signal in the 20-core bus cable.

[2600] FIG. 99 shows the relation between the system switch signal and the active system selection state in the SIFSH-A.

3.2. SYNSH Interface

[2601] The SIFSH-A receives a reference clock from the SYNSH through an optical link.

[2602] The PRC package in the SIFCOM fetches an 8 Mbps clock from the SYNSH of both systems #0 and #1 through the optical link as shown in FIG. 100, and selects an 8 MHz clock from system #0 or #1 according to the alarm information from the OL-2 circuit. If a fault has arisen in any of the 8 MHz clock, then selection systems are autonomously switched. Furthermore, a selection system can be specified using a COM-E-MSD command from the switch software. A selected system is notified of for the switch software according to the COM-E-MSCN information.

[2603] FIG. 101 shows the relation among a COM-E-MSD command instruction state, an alarm state, and a selected system state in each system.

3.3. Individual Unit Interface

[2604] Described below are the interface and signal timing between the SIFCOM and individual unit loaded on the SIFSH-A through the back-wiring board (BWB). All interface points between the SIFCOM and individual units explained below are defined according to the polarity and timing in the BWB.

[2605] 3.3.1. 156 Mbps Cell Highway Interface

[2606] The interface of the 156 Mbps cell highways between the common unit and the individual unit is explained below.

[2607] As shown in FIG. 102, the ATM cell in the 156 Mbps low-speed highway is transmitted in the form of TTL level/8-bit parallel. The following 5 types of signals are required as a 156 Mbps cell highway interface.

[2608] (1) clock (CLK: 19.4 Mbps, duty: 50%)

[2609] (2) cell frame pulse (CFP: cell leading identification negative pulse)

[2610] (3) cell enable (CEN: “L” for valid cells, and “H” for invalid cells)

[2611] (4) data bus (DB0˜7)

[2612] (5) parity bit (PB:DB0˜7 and odd-number parity for the CEN)

[2613] 3.3.1.1. Upward 156 Mbps Cell Highway Interface

[2614] FIG. 103 shows the timing of receiving an ATM cell from the upward cell highway from the individual unit to the SIFCOM. The individual unit transmits an upward cell by receiving a cell request signal from the SIFCOM because the management through the scheduler at the SIFCOM requires the upward cells from each circuit to be synchronized.

[2615] 3.3.1.2. Downward 156 Mbps Cell Highway Interface

[2616] FIG. 104 shows the timing of receiving an ATM cell from the downward cell highway from the SIFCOM to the individual unit. The SIFCOM transmits a downward cell by receiving a cell request signal from the individual unit so that the downward cell frame can be synchronized in the SIFCOM of both systems to prevent the generation of duplicate or missing cells in fetching a downward cell in each individual unit in a downward cell fetching process.

[2617] 3.3.2. E-MSD/E-MSCN Highway Interface

[2618] The physical and logical specifications are described below for the EMSD/EMSCN highway between the SIFCOM and individual unit.

[2619] The downward (SIFCOM individual unit) data highway is defined as an EMSD highway. The EMSD is transferred to the SIFCOM through the BSGC (refer to FIG. 94) from the switch software using the simple LAP-D, multiplexed in the EMSD highway, and serially transferred to the individual unit.

[2620] The upward (individual unit→common unit) data highway is defined as an EMSCN highway. The EMSCN is an echo-back (EMSD normally received at the individual unit and looped back to the EMSCN highway) to the EMSD, and fault status information in the individual unit. The EMSCN is multiplexed in the EMSCN highway and serially transferred to the SIFCOM. A change in each bit of the EMSCN is detected in the SIFCOM, and only the signal of the bit whose change has been detected is notified of to the switch software by way of the BSGC through the simple LAP-D communications.

[2621] 3.3.2.1. System Control

[2622] An internal circuit in the individual unit operates according to the EMSD, CLK, and FCK from the SIFCOM of an active system. The EXSCN is transmitted to the SIFCOM of both systems in synchronism with the clock from a selected active system. FIG. 105 shows the system control when the SIFCOM of the #0 system is an active system.

[2623] The active control through an ATC controller is performed based on the logic shown in FIG. 106. FIG. 107 shows an example of the configuration of the circuit of an ACT controller. The circuit which receives an ACT0/ACT1 in the individual unit is necessarily pulled up so that an “L” active control can be performed in both ACT0 and ACT1.

[2624] 3.3.2.2. Physical Specification

[2625] Listed below are the physical specifications of the E-MSD/E-MSCN highway interface.

[2626] (1) Bit rate: 512 Kbps

[2627] (2) Frame length: 256 bytes/frame (4 msec/frame)

[2628] (3) Transmission format: Synchronous serial communications

[2629] (4) Transmission order: MSB (D7 bit/000th byte)→LSB (D0 bit/255th byte)

[2630] (5) Downward transmission signal: clock (CLK): 512 KHz

[2631] Frame clock pulse (FCK): 4 msec cycle, 512 KHz, 1-bit width negative pulse

[2632] EMSD data serial highway

[2633] (6) Upward transmission signal: EMSCN data serial highway (in bit/frame synchronism with END serial highway)

[2634] The bit data in each byte is transmitted in the order from MSB to LSB in the highway, and each byte is transmitted in the ascending order. Bits are numbered from 0 (D0:LSB) to 7 (D7:MSB). Bytes are numbered from 000 to 255 (refer to FIGS. 58 and 61).

[2635] FIG. 108 shows the relationship in phase among the FCK, CLK, EMSD data, and EMSCN data. The specification of each data and the specification of the resettings are shown below.

[2636] Frame clock (FCK): negative logic on the backboard, khz, 1-bit width, 1.95 μsec, generating a negative pulse at 000th byte/D7 bit (head of frame) Clock (CLK): 512 KHz, duty: 50%, the phase relating to the FCK/data being in synchronism with rise edge

[2637] Data: in the order from MSB to LSB; the downward EMSD data highway and the upward EMSCN data highway are synchronized in bit and byte position

[2638] Hard reset (HRST): individual unit hard reset signal; reset with “1” in the BWB and output asynchronously

[2639] Fault reset (FRST): individual unit fault reset signal; reset with “1” in the BWB and output asynchronously

[2640] 3.3.2.3. Logical Specification

[2641] 3.3.2.3.1. Individual Unit Receiving Specification

[2642] Described below is the logical specification of the EMSD receiving process in the individual unit.

[2643] The receiving terminal is protected against SIFCOM interface fault (noises of the EMSD, etc., stack fault, etc.) by frame synchronization, checking a pilot signal, and twice reading processes.

[2644] FIG. 112 is a flowchart showing the operations of these processes. FIG. 113 is a block diagram showing the functions of the individual unit for performing these processes in series.

[2645] 3.3.2.3.2. Frame Synchronization

[2646] The frame synchronization corresponds to step 1 shown in FIG. 112 and the functional portion 1 shown in FIG. 113.

[2647] The number of protection steps for the frame synchronization of the EMSD highway is 1 step each for forward and backward. The stack of the FCK (both L/H stacks) are detected.

[2648] FIG. 109 shows the state transition of the frame synchronization process.

[2649] Practically, data is fetched from a corresponding frame when a normal synchronization FCK is received in a hunting state as shown in FIG. 110, If an abnormal FCK is once received in a synchronization established state, then the frame synchronization state changes into the hunting state and the data are discarded from this point, but the data received immediately before the point is stored until the synchronization is established next time. A normal FCK refers to the fact that the receiving terminal counter value (for example, a carry-out) depending on the CLK/FCK matches the next FCK in timing. An abnormal FCK refers to the fact that they don't match in timing.

[2650] Asynchronization is detected independently for systems 0 and 1. If the asynchronization of the FCK is detected, then the SIFCOM is notified of the fact by the EMSCN (002nd byte/bit D7 [SYNCF]: refer to FIGS. 58 and 59). The fault state is indicated as “H” in the BWB.

[2651] 3.3.2.3.3. Pilot 0/1 Signal Check (detection of stack in EMSD highway)

[2652] The pilot 0/1 signal check corresponds to step 2 shown in FIG. 112 and the functional portion 2 shown in FIG. 113.

[2653] A pilot 0/1 signal is a highway stack monitor bit and pilot 0=“L” and pilot 1=“H” are constantly output from the SIFCOM in the BWB. The accommodation position of the pilot 0 signal in the EMSD is the 000th byte/bit D7, while the accommodation position of the pilot 1 signal in the EMSD is the 000th byte/bit D7 (refer to FIGS. 58 and 59).

[2654] The individual unit detects an EMSD highway stack fault when the alternation of the pilot signals 0/1 becomes irregular. The individual unit discards the data at and after an abnormal point as shown in FIG. 111, and then holds the data received immediately before the abnormal point until a normal pilot signal is detected.

[2655] A stack fault is detected independently for systems 0 and 1.

[2656] The SIFCOM is notified of a stack fault by the EMSC (002nd byte/bit D6 [PLTF]: refer to FIGS. 61 and 62.

[2657] 3.3.2.3.4. Twice Reading Process

[2658] The data fetched in the frame synchronization process described in the 3.3.2.3.2. and the pilot 0/1 signal check process described in 3.3.2.3.3. is stored in a noise erase memory 4 shown in FIG. 113. A comparator 3 compares the contents of the data in the memory with the contents of newly fetched data (step 3 shown in FIG. 112). As a result, if these data match, that is, the same data is received twice consecutively, then the data is written to a data memory 5 shown in FIG. 113 (step 5 in FIG. 112). If these data do not match, then they are discarded.

[2659] A protection process is performed using a DTEN signal (step 4 shown in FIG. 112). The DTEN signal is set to indicate “L” in the BWB by a microprocessor in the SIFCOM. When the intra-shelf units are turned on simultaneously, a rise time conflict occurs after the release of the power-on reset for the SIFCOM and the individual unit, and a value of the EMSD highway becomes uncertain. The DTEN signal is used to control the individual unit such that it cannot fetch the EMSD data. Therefore, the individual unit ignores all EMSD data when the DTEN signal indicates “H”. The DTEN signal is accommodated in the leading bit (000th byte/bit D0) of the EMSD highway (refer to FIGS. 58 and 59).

[2660] 3.3.2.3.5. Individual Unit Sending Specification

[2661] Described below is the logical specification of an EMSCN sending process in the individual unit.

[2662] The EMSCN of an active system transmits an echo-back in response to the EMSD information and the notification of an EMSD highway stack.

[2663] The EMSCN of a standby system transmits data as in the EMSCN in the active system at the same timing.

[2664] A pilot 0/1 signal is inserted to the same accommodation position in the EMSCN highway as in the EMSD highway. Since the signal is used to monitor a stack in the EMSCN highway, it does not indicate an echo-back in response to the EMSD information.

[2665] FIG. 114 is a block diagram showing the EMSCN sending circuit in the individual unit.

[2666] 3.3.2.3.6 Fault Detection

[2667] FIG. 115 is a list of the methods of detecting and notifying in the individual unit of the interface fault between the SIFCOM and the individual unit, and of the method of detecting the fault in the SIFCOM and the contents of the recognized faults.

3.4. Clock Interface

[2668] The clock interface refers to clock systems in the SIFCOM and individual unit along the flow of cells.

[2669] In the SIFCOM, a cell is written to the DMUX buffer in the DMX-LSI in synchronism with a 12.96 MHz clock obtained by dividing a 77.76 MHz clock transferred from the ASSW (ATM switch) into 6 units.

[2670] As shown in FIG. 116, a cell is read from the DMUX buffer in the DMX-LSI to the individual unit in synchronism with a 19 MHz (19.44 MHz precisely) clock transferred from the individual unit. The 19 MHz clock from the individual unit is generated as follows. That is, as shown in FIG. 116, a 64 KHz clock is transferred to the individual unit in the SIFCOM after being obtained by dividing into 128 units an 8 MHz clock received from the SYNSH through an optical link. According to the clock, the PLL module in the individual unit generates a 156 MHz (155.52 MHz precisely) clock. Then, the above described 19 MHz clock can be generated by dividing the 156 MHz clock.

[2671] The PLL module in the SIFCOM also generates a 156 MHz clock according to the 64 KHz clock obtained by dividing into 128 units the 8 MHz clock received from the SYNSH. An upward cell is written to the MUX buffer in the MUX-LSI corresponding to each circuit in synchronism with the 19 MHz clock transferred from the individual unit. The cell is read from the MUX buffer in synchronism with the 13 MHz (12.96 MHz precisely) clock obtained by dividing the above described 156 MHz clock. The read cell is converted from the parallel data format into the serial data format, and transmitted to the ASSW at a bit rate of 78 MHz (77.76 MHz precisely).

4. SOFTWARE INTERFACE

[2672] Described below are the interface between the SIFCOM and the switch software, that is, an ATM layer cell format, SAR-PDU format, and LAP-D layer 2(L2) format. The LAP-D layer 3 (L3) format is explained in 10.9 of part 2. The switch software refers to a program executed in a processor for controlling the entire process of the switch (call process, switch control process, etc.).

4.1. Outline

[2673] The SIFCOM communicates with the switch software by performing an intra-station control communications with the BSGC using a simple LAP through a path in the switch passing through the ASSWSH (refer to FIG. 94). The BSGC communicates with the switch processor through an interface type T (INFT).

[2674] A simple LAP-D is a protocol newly developed by the Applicant of the present invention to reduce the load on the hardware and firmware. Specifically, numbered frames in layer 2, which charge a heavy load on the hardware, can be successfully removed. As a result, only unnumbered frames are processed in layer 2. To avoid missing and duplicate messages, numbered frames are processed in layer 3. Since the number management function is originally indispensable for firmware, the numbered frames in layer 3 do not cause an increased load on the firmware.

[2675] The simple LAP-D frames in layer 2 are stored after being divided into ATM cells each having 54-octet data length and transferred via the highway in the switch, thereby realizing an in-band intra-station communications.

[2676] The in-band communication is a technology required in connecting a broadband remote line concentrator (BRLC: refer to FIG. 34) to a host switch. The in-band communication in the host switch realizes a common control system in the BRLC and the host switch and successfully reduces the number of cables for connecting a control bus to a shelf in the host.

4.2. Layer Structure in Intra-station Control Communications

[2677] FIG. 117 shows the layer structure in the intra-station control communications with the CD-PDU (described later) omitted.

[2678] 4.2.1. ATM Layer Cell Format

[2679] FIG. 118 shows the cell format of an ATM layer in the simple LAP-D.

[2680] 4.2.2. SAR-PDU Format

[2681] FIG. 119 shows the SAR-PDU format for the simple LAP-D.

[2682] The SAR-PDU format can be based on the ATM adaptation layer (AAL) protocol type 3 or 4.

[2683] An SAR-PDU consists of a segment type (ST), sequence number (SN), MID (don't care in an intra-station control communications cell), payload, payload byte length indicator (LI), and CRC (ST, SN, MID, and CRC-10 for a payload). It is stored in a payload of an ATM cell, and provided with an ATM header at its head.

[2684] The payload of the SAR-PDU stores a LAP-D message.

[2685] If the data length of the LAP-D data is 44 bytes (refer to FIG. 749 in part 7), then the message is stored in the payload of a single SAR-PDU. In this case in the SAR-PDU, a single segment message (SSM) is set as an ST and the LI is set to 44 bytes.

[2686] If the data length of the LAP-D is 256 bytes (refer to FIG. 750 in part 7), the message is divided into a plurality of 44-byte segments to be stored in the payloads of plural SAR-PDUs. Accordingly, the LAP-D data is stored and transferred after being divided into a plurality of ATM cells. In this case, the SAR-PDU storing the leading segment is assigned a beginning of message (BOM) for its ST and 44 bytes for its LI. The SAR-PDU storing an intermediate segment is assigned a continuation of message (COM) for its ST and 44 bytes for its LI. The SAR-PDU storing the trailing segment is assigned an end of message (EOM) for its ST and 36 bytes for its LI (refer to FIG. 750 in part 7).

[2687] 4.2.3. LAP-D Format (layer 2)

[2688] FIG. 120 shows the LAP-D format of layer 2. A LAP-D frame is stored in he payload of the SAR-PDU after being properly divided as described in 4.2.2. above.

5. ALLOCATION OF TAG

[2689] FIG. 121 shows the format of an ATM cell processed in the SIFSH-A.

[2690] According to the present embodiment, an ATM cell is routed using a tag added as its header. A part of bits in the virtual path identifier area is used as a tag area. As a result, a VPI which can be defined for the DS1 transmission line is 64 at maximum. All tags for 156 Mbps transmission line are accommodated in the second octet. If a transmission line has a network node interface (NNI), then a total of 6 bits of the MUXM, ADS1-BLK, and ADS1-SEL as shown in FIG. 121 are assigned to the VPI.

[2691] FIG. 122 shows the configuration of the ATM cell header data used in the SIFSH-A. FIG. 123 shows the use of an ATM cell header data in the SIFSH-A.

[2692] FIG. 124 shows the configuration of the ATM cell header data used in the RMXSH (refer to FIG. 34). FIG. 125 shows the use of an ATM cell header data in the RMXSH.

[2693] FIG. 126 shows the configuration of the ATM cell header data used in the BSGCSH (refer to FIG. 94). FIG. 127 shows the use of an ATM cell header data in the BSGCSH.

[2694] FIG. 128 shows the use of a SIG/ADS1BLK/ADS1SEL in the SIFSH-A.

[2695] FIG. 129 shows the allocation of functions of ATM cell header data defined in FIGS. 122, 123, and 128 in the SIFSH-A and ADS1SH (refer to FIG. 8).

6. FUNCTIONS

[2696] The functions of the SIFCOM are explained from the viewpoint of the hardware configuration.

6.1. MUX

[2697] 6.1.1. Outline

[2698] FIG. 130 shows the position (hatched portion) of the MUX in the SIFSH-A.

[2699] The MUX multiplexes in the upward highway to the ASSW the ATM cell (whose header has been converted by a VCC) transferred from individual units #0˜#7 accommodated in the SIFSH-A, and a signalling cell generated by the signal processing unit in the SIFCOM.

[2700] If the SIFSH is connected in series, then the multiplexing control of both MUXes is performed collectively, and the data for two shelves is multiplexed in one upward highway and transmitted from a higher order SIFSH-A to the ASSW. FIG. 131 shows the configuration of the serial connection of the SIFSH-A.

[2701] 6.1.2. Configuration of MUX

[2702] FIG. 132 shows the configuration of the MUX.

[2703] The MUX multiplexes a cell in the 156 Mbps upward highway connected to each individual unit and a signalling cell generated in the signal processing unit (shown in FIG. 130) in the SIFCOM in the 622 Mbps upward highway to the ASSW. The cell transferred from each individual unit is input to the MUX after its header is converted according to the VCC (refer to FIG. 130).

[2704] The MUX comprises a buffer for 52 cells corresponding to each individual unit, and only valid cells are stored in the buffer. Each buffer notifies the multiplexing control unit (scheduler) of a write of a cell each time a cell is written to the buffer. When each buffer receives output permission from the scheduler, it multiplexes a cell by reading the cell in the buffer.

[2705] 6.1.3. Multiplexing Control System

[2706] The multiplexing control of an ATM cell in the 156 Mbps highway extended from each individual unit is performed by a scheduler. A scheduler is assigned to each 622 Mbps upward highway. If the SIFSH-A is connected in series, then the scheduler in the lower order SIFSH-A is not operated, and the multiplexing control of the lower-order SIFSH-A is performed by the scheduler in the higher order SIFSH-A.

[2707] FIG. 133 shows the outline of the configuration of the scheduler.

[2708] If a valid cell is written to a buffer (FIG. 132) for each line, then a write completion signal indicating that a cell in the 156 Mbps highway has been written to the buffer is transmitted from a write control unit (not shown in FIG. 133) in each buffer to the scheduler.

[2709] As shown in FIG. 133, the scheduler contains a FIFO having 18-bit width corresponding to the number of circuits (individual units) to be monitored by the scheduler, samples the write completion signal received from each circuit on a 2.7 μsec cycle, and writes the write completion signal to the FIFO. The 2.7 μsec cycle corresponds to the time required to transmit one cell in the 156 Mbps highway.

[2710] Each bit position in the FIFO is output as an output permission signal to a buffer on a cycle of approximately 700 μsec as shown in FIG. 135 after the priority is determined in a priority control circuit. The approximately 700 μsec cycle corresponds to the time required to transmit one cell in the 600 Mbps highway.

[2711] Each individual unit has a simplex configuration, while the SIFCOM has a duplex configuration. This scheduler multiplexing control system is applied so that the loss of cells can be minimized by matching the sequence of cells in an active system in the duplex portion including the ASSW (ATM switch) with that in a standby system.

[2712] 6.1.4. Monitor of Buffer

[2713] The MUX comprises a dual port RAM having a capacity of 52 cells (8 bits×54 octet×52 cells=22464 bits) per circuit (individual unit) as a buffer used in multiplexing ATM cells in a low-speed input highway into a high-speed input highway, and the RAM is used as a FIFO.

[2714] 6.1.5. Write Control

[2715] Input cells are written to the buffer only if the following conditions are satisfied.

[2716] (1) Input cells are valid.

[2717] (2) The buffer is not full.

[2718] (3) Congestion control is not performed (refer to 6.1.9.).

[2719] 6.1.6. Abnormal Write Process

[2720] If an abnormal cell described in 6.1.6.1. and 6.1.6.2. below is input, then the following abnormal write process is performed. 6.1.6.1. Too small cell length

[2721] If the data length of an input cell is too small as shown in FIG. 136, then the cell is discarded, and written is a cell subsequently input at the corresponding address in the buffer.

[2722] 6.1.6.2. Too long cell length

[2723] If an abnormal cell described in 6.1.6.1. and 6.1.6.2. below is input, then the leading 54-octet data forming the cell is written at the specified address in the buffer, and the following data forming the cell is ignored.

[2724] 6.1.7. Read Control

[2725] A cell is read from each buffer only if the scheduler inputs “H” indicating an output permission signal to the buffer.

[2726] 6.1.8. Abnormal Read Process

[2727] If the scheduler inputs to a buffer an output permission signal at intervals within approximately 700 μsec (refer to FIG. 135) as shown in FIG. 138, then the buffer ignores an output permission signal input at short time intervals, and the cell is read from the buffer according to the subsequent output permission signal.

[2728] 6.1.9. Buffer Congestion Control

[2729] The MUX controls the congestion of each buffer in the MUX according to the pattern of each value of P bit and CON bit (FIG. 121) indicated in the tag area in the header in an ATM cell.

[2730] The buffer congestion control data is set by the switch software as EMSD information through the intra-station control communications. The information is provided by the microprocessor in the SIFCOM for each buffer in the DMUX. A threshold at 9 levels should be set to control the quality and priority at the congestion of a buffer. FIG. 139 shows a determined threshold.

[2731] At the reset of the SIFSH-A hardware, the maximum buffer length, which is an initial value, is set as a cell discard start threshold. If the cell discard is started, then the number of cells discarded according to each threshold corresponding to each of the thresholds Qa, Qb, Qc, and Qd is counted.

[2732] Each threshold should be set through the intra-station control communications such that the following conditions can be satisfied. These conditions are not checked by hardware.

[2733] Q0≧Q1≧Qa≧Qa′>0, Q0≧Q1≧Qb≧Qb′>0

[2734] Q0≧Q1≧Qc≧Qc′>0, Q0≧Q1≧Qd≧Qd′>0

6.2. DMUX

[2735] 6.2.1. Outline

[2736] FIG. 140 shows the position (hatched portion) of the DMUX in the SIFSH-A.

[2737] The DMUX demultiplexes the ATM cell in a high-speed highway down the ASSW or a higher order SIFSH-A connected in series into a cell toward a low-speed highway downward each of the individual units in the SIFSH-A and a signaling cell input to the signal processing unit in the SIFCOM. The cells are demultiplexed according to the tag in the header of each cell.

[2738] 6.2.2. Functions

[2739] FIG. 141 shows the configuration of the DMUX. FIG. 142 shows the format of a cell in the switch. FIG. 143 shows the location of the matching bit of the header to be used in the DMUX.

[2740] The DMUX demultiplexes a cell to each of up to 8 individual units in the shelf and a signaling cell from the 622 Mbps high-speed highway according to the data (hatched portion shown in FIG. 142) of the SIG, UL, and COM in a cell header. Then, the DMUX transmits the former through the 156 Mbps low-speed highway connected to each individual unit, and the latter to the signal processing unit (FIG. 140) in the SIFCOM. In this case, the DMUX comprises a buffer for 112 cells for each individual unit.

[2741] A cell dropper (cell DRP) for each individual unit in the DMUX shown in FIG. 141 determines whether or not a cell is dropped into the 156 Mbps low-speed highway connected to itself by determining whether or not the pattern of each data (hatched portion shown in FIG. 142) of the SIG, UL, TAGC, and COM in the header of an input cell matches the matching pattern (shelf/line ID) (refer to FIG. 143) preliminarily set in itself.

[2742] 6.2.3. Dynamic Tag Matching

[2743] The SIFCOM has the dynamic tag matching function to set a matching pattern shown in FIG. 143 for the DMUX at the instruction of the switch software.

[2744] A tag is autonomously set depending on each line number as a hardware default. The above described dynamic tag matching function is required when an umbilical link is set between a host switch and the BRLC (refer to FIG. 34).

[2745] That is, the SIFSH-A accommodating the umbilical link set for the BRLC requires a redundancy configuration referred to as a circuit protection (N+1 system) described later in 9. In this case, TAGC=“100” is set from the switch software through the microprocessor in the SIFCOM according to command A at the DMUX 0 corresponding to the individual unit accommodating the active circuit of the umbilical link as shown in FIG. 144, while TAGC=“000” is set according to command B at the DMUX 4 corresponding to the individual unit accommodating a standby circuit of the umbilical link. If a fault occurs in the active circuit, then two TAGC values set at DMUX 0 and DMUX 4 are swapped to switch the active and standby circuits.

[2746] 6.2.4. Monitor of Buffer

[2747] Each buffer of the DMUX (refer to FIG. 141) controls the congestion as follows by monitoring the number of cells (length of queue) stored in itself.

[2748] (1) The microprocessor is notified of the present length of queue.

[2749] When the microprocessor issues a request to read the number of cells, the cell count value is moved to a register and the count value is reset (read reset).

[2750] (2) The congestion is controlled according to the threshold of 9 levels as shown in FIG. 145.

[2751] The buffer congestion control data is set by the switch software as the EMSD information through the intra-station control communications. The information is provided by the microprocessor in the SIFCOM for each buffer in the DMUX.

[2752] At a SIFSH-A hardware reset, the maximum buffer length, which is an initial value, is set as a cell discard process start threshold.

[2753] Listed below are the relationships between each threshold and a buffering operation in each buffer.

[2754] (1) If a queue length exceeds threshold QA, then the buffer notifies the microprocessor of it and simultaneously notifies a light controller (not shown in the drawings) in the buffer of a marking cell discard instruction. A marking cell refers to a cell in which P bit and CON bit (refer to FIG. 142) displayed in the tag area of a header are set. Unless the microprocessor specifies the priority control and quality control, the buffer autonomously start the congestion control.

[2755] (2) If the queue length is restored to threshold QA′, then the buffer notifies the microprocessor of it, and simultaneously notifies the light controller in the buffer of the stop of the discard of marking cells. The quality control or priority control is not stopped, but the discard of cells is stopped.

[2756] (3) When the queue length reaches threshold Q1, the buffer notifies the microprocessor of the occurrence of a fault, and simultaneously instructs the light controller to stop the buffering operation even if the cell to be input to the buffer is a valid cell.

[2757] Likewise, the congestion control listed in (1), (2), and (3) is performed on thresholds QB, QC, and QD.

[2758] (4) The DMUX indicates no special relationship between the priority control and the quality control. That is, the priority and quality control are performed independently using control bits corresponding to each control.

[2759] Each threshold should be set through the intra-station control communications such that the following conditions can be satisfied. These conditions are not checked by the hardware. The buffering operation is not guaranteed in the DMUX when the conditions are not satisfied.

[2760] Q0>Q1>QA>QA′>0 Q0>Q1>QB>QB′>0

[2761] Q0>Q1>QC>QC′>0 Q0>Q1>QD>QD′>0

6.3. VCC

[2762] 6.3.1. Position of VCC

[2763] A virtual channel controller (VCC) retrieves on a table a VPI/VCI/TAG (hereinafter referred to as an output VPI/VCI, TAG) corresponding to the VPI/VCI (hereinafter referred to as an input VPI/VCI) assigned to an input ATM cells, and assigns the output VPI/VCI/TAG to the ATM cell.

[2764] The position of the VCC is a duplex portion SIFCOM.

[2765] The VCC is required for each circuit and should be loaded individually. However, it is loaded into the SIFCOM on the following grounds.

[2766] Assume that the VCC is loaded into the individual unit having the configuration of a duplex VCC. Furthermore, assume that the cell transmitted from subscriber line A (A sub) is received by subscriber line B (B sub) as shown in FIG. 146, and the cell transmitted from subscriber line C (C sub) is received by subscriber line D (D dub).

[2767] Under the assumption above, further assume that a fault occurs at the VCC in the individual unit for subscriber A (A sub) as shown in FIG. 146, and that a cell is routed such that it is transferred from subscriber line A (A sub) to subscriber line D (D sub). As a result, cells are concentrated in a specific transmission line in the ASSW, and congestion arises at the position marked with ● (FIG. 146), thereby possibly causing a switch fault. In the worst case, a fault at the VCC corresponding to a single subscriber line may undesirably affect 64 or more circuits.

[2768] In this case, the fault detecting process can monitor an MC (monitoring cell) at a receiving equipment. In this process, a fault can be detected by inserting a monitoring cell (MC1 and MC2 in FIG. 146) in each subscriber line at the sending equipment and monitoring the cell in each subscriber line at the receiving equipment. However, if the above described switch fault has arisen, then both monitoring cell MC1 inserted in subscriber line A (A sub) in which the fault has arisen and monitoring cell MC2 inserted in subscriber line C (C sub) in which no fault has arisen are discarded. As a result, cells cannot be normally monitored, and an exact cause of the fault can hardly be specified.

[2769] If a switch fault has arisen, the systems in the SIFCOM and ASSW are switched. However, since the fault has occurred in the VCC of the individual unit having a simplex configuration, a switch fault will soon occur in a newly active ASSW.

[2770] If the VCC is loaded into the SIFCOM having a duplex configuration of the VCC, then the system of the operating SIFCOM is switched into the system of the SIFCOM containing the VCC indicating no fault, thereby successfully recovering from the fault.

[2771] After the switch of systems, the faulty VCC can be specified using a test cell generator (TCG), etc.

[2772] The VCC can be loaded into the SIFCOM on the above listed grounds.

[2773] 6.3.2. Capacity of VCC Memory

[2774] As shown in FIG. 143, the VCC memory stores two VCC tables in consideration of the future virtual path (VP) services.

[2775] Table 1 (Table-1) is used to retrieve an intermediate VPI using an input VPI (VPI assigned to an input cell) as an address. According to the present embodiment, an input VPI value=an intermediate VPI value assuming that no VP services are provided.

[2776] Table 2 (Table-2) is used to retrieve an output VPI/VCI using an intermediate VPI+input VCI (VCI assigned to an input cell) as an address. According to the present embodiment, an input VPI value=an intermediate VPI value assuming that no VP services are provided.

[2777] 6.3.3. Inter-System VCC Copy

[2778] 6.3.3.1. Object

[2779] Described below is the inter-system copy required in the OUS INS procedure.

[2780] 6.3.3.2. Timing of Inter-system Copy

[2781] The inter-system copy is performed in the OUS INS procedure in a state in which one system is active and the other system is in an OUS state.

[2782] 6.3.3.3. Copy Object Information

[2783] All information set on the VCC table is copy object information. Listed below is the information. The values in the parentheses indicate the number of bits of respective pieces of information.

[2784] (1) Settings of VCC as valid/invalid (1)

[2785] (2) CLP (cell loss priority) copy control (1)

[2786] (3) Output highway specified tag field (8)

[2787] (4) Signaling identification (1)

[2788] (5) Higher order/lower order identification (1)

[2789] (6) SIFCOM specification (1)

[2790] (7) MUX multicast indication (1)

[2791] (8) ADS1-SEL identification (1)

[2792] (9) ADS1-BLK identification (1)

[2793] (10) Quality class (1)

[2794] (11) Intra-system test cell indication (1)

[2795] (12) Congestion control (1)

[2796] (13) Output VPI (8)

[2797] (14) Output VCI (16)

[2798] (15) Distribution connection (fixed to “0”) (1)

[2799] (16) Payload type (3)

[2800] (17) Switch IN/OUT indication (1)

[2801] The VCC table contains a parity bit which is not copy object information but is checked at a reading operation on the VCC table and is generated at a writing operation.

[2802] 6.3.3.4. Procedure for INS process

[2803] The state transition from OUS to INS is carried out after a switch processor (CC) issues a copy start command to instruct the VCC table of an active system to be copied to the VCC table of an OUS system, and after the contents of the VCC table of the active system are all copied to the VCC table of the OUS system.

[2804] Before the copy start command is issued, the CC issues a reset request command to the SIFCOM of the OUS system. The copy process is performed after the contents of the VCC table in the SIFCOM of the OUS system is reset. Furthermore, the SIFCOM of the OUS system notifies the CC of the reset completion notification status after the reset is completed. The reset process enables only the VPI/VCI on the VCC table in the SIFCOM of the active system to be copied to the VCC table in the SIFCOM of the OUS system, thereby shortening the copying time.

[2805] FIG. 148 is an arrow diagram showing the procedure for an INS process. The procedure is described below by referring to FIG. 148.

[2806] If the copy process terminates normally, then the SIFCOMs of both systems notify the CC of a copy completion status. Unless the copy process terminates normally due to an inter-system communications fault, etc. from no response of a corresponding SIFCOM, then a copy disable status is provided for the CC. As a result, the CC determines failure in the copy process and resets again the SIFCOM of the OUS system. If any of the SIFCOMs of both systems issues the copy disable status, then the SIFCOM of the OUS system is reset again. FIG. 149 shows the status of each system and the process of the CC.

[2807] Normally, a set/release command (call process command) is issued by the CC to the SIFCOM of both systems independently. The SIFCOM is configured such that it can receive a call process command in a VCC copy process. During the VCC copy process, the command is issued by the CC not to the SIFCOM of both systems but to the SIFCOM of the active system. This is because the call process command reaches the SIFCOM of the OUS system faster than the SIFCOM of the active system, and the contents of the VCC table in the SIFCOM of the OUS system may be set again to the previous contents through the copy process on the VCC table from the SIFCOM of the active system when the VCC table in the SIFCOM of the OUS system is updated to the new contents. Since preventing the inconsistency through the hardware complicates the protocol and enlarges the scale of the hardware, a call process command is issued only to the SIFCOM of the active system.

[2808] Accordingly, if the state of the SIFCOM is changed from the copy state to the operation state, then required is a protocol for preventing the specification of a call process command from the CC to the SIFCOM of the old OUS system from being lost by the crossing of a command and a status. Listed below are the important points of the protocol.

[2809] (1) The SIFCOM of the active system informs of a copy completion status after completing the copy of the VCC table.

[2810] (2) After receiving the status described in (1) above, the CC issues a copy completion notification command to the SIFCOM of the active system.

[2811] (3) The SIFCOM of the active system copies to the other system all call process commands received before receiving the command described in (2) above. All call process commands received after receiving the command described in (2) above are executed only in its own system and are not copied to the other system.

[2812] (4) When receiving a copy completion notification from the SIFCOM of the active system, the SIFCOM of the OUS system issues a copy completion status to the CC. The items (2) through (4) above are not restricted in timing among them.

[2813] (5) After receiving the status described in (4) above, the CC issues a copy completion notification command to the SIFCOM of the OUS system.

[2814] (6) After transmitting the command described in (5) above, the CC issues an online mode set command to the SIFCOM of the OUS system.

[2815] (7) If the queue stores a call process command to a new standby system while the processes described in (3) through (6) are executed, then the CC issues the command immediately.

[2816] After the process (7) above, the CC issues a call process command independently to each SIFCOM of the active and standby systems.

[2817] 6.3.3.5. Copy Disable Report

[2818] The SIFCOMs of both systems notify the CC of the copy completion if the VCC table has been normally copied. If it cannot be normally copied, then the copy disable report is provided for the CC. The copy disable report is issued if any of the following faults occurs in the inter-system cross connection.

[2819] (1) Timeout

[2820] A copy start request is not issued by the SIFCOM of the OUS system in response to the copy start request from the SIFCOM of the active system.

[2821] A copy start request is not issued by the active system in response to the copy start request from the SIFCOM of the OUS system.

[2822] A copy completion notification is not issued from the SIFCOM of the active system.

[2823] (2) Detection of Parity Error

[2824] A parity error has occurred during the transfer.

[2825] 6.3.4. Relationship between VCC and SMDS Service

[2826] The VCC in the SIFCOM specifies the permanent virtual circuit (PVC) established between the SIFCOM and the SBMESH (FIG. 8) for providing the SMDS service from the specific value (for example, VPI=3F, VCI=03FF) added by the individual unit, and simultaneously changes the value of the VPI/VCI assigned to the header of the ATM cell containing the payload field input from the individual unit of the DS3-SMDS interface, etc. and the L2-PDU of the SMDS service into the value of the VPI/VCI specifying the subscriber network interface (SNI) terminating the individual unit which transmits the ATM cell. Accordingly, the PVC established between the SIFCOM and the SBMESH is assigned the value of the VPI/VCI of the number corresponding to the number of the SNI terminated by the individual unit connected to the SIFCOM and used for the SMDS service. The SIFCOM adds to the head of the ATM cell a tag for use in autonomously switching the ATM cell in the ATM switch and transferring it to the SBMESH.

6.4. Signaling Process (EGCLAD)

[2827] 6.4.1. Outline

[2828] FIG. 150 shows the position of the signal processing unit (EGCLAD) in the SIFSH-A.

[2829] An EGCLAD LSI converts between a simple LAP-D-based frame and an ATM cell to realize the intra-station control communications between the SIFSH-A and the BSGC (FIG. 94).

[2830] The microprocessor and the EGCLAD LSI communicate LAP-D layer 2 frames through the dual port SRAM (DPRAM shown in FIG. 150).

[2831] 6.4.2. Functions of EGCLAD LSI

[2832] The EGCLAD LSI has the following functions to compose and decompose a signaling cell.

[2833] 6.4.2.1. ATM Header Check Functions

[2834] The EGCLAD LSI checks the contents of the hatched portion shown in FIG. 151 in the header of the signaling cell transferred from the BSGC through the ASSW (FIG. 94). Then, the EGCLAD LSI composes the LAP-D frame based on the cell determined to be good as a check result. The EGCLAD LSI writes framed data to the dual port SRAM and sets a reception completion flag, thereby notifying the microprocessor of the existence of a received frame.

[2835] The microprocessor reads the received frame from the dual port SRAM if the flag is set.

[2836] 6.4.2.2. ATM Header Inserting Function

[2837] The microprocessor writes the LAP-D layer 2 frame to the dual port SRAM and notifies the EGCLAD LSI of the write completion through the register.

[2838] After receiving the write completion notification, the EGCLAD LSI reads LAP-D layer 2 frame in the dual port SRAM. Then, the EGCLAD LSI converts the frame into a signaling cell by inserting to the frame the header and trailer indicated as hatched portions in FIG. 152. The EGCLAD LSI sends the signaling cell in synchronism with the shaping clock provided externally.

7. TEST AND MAINTENANCE

[2839] The ATM switch is monitored and tested by the following steps.

[2840] (1) Monitoring the quality of a path using a monitoring cell (MC)

[2841] (2) Circuit test for a test cell using the test cell generator (TCG)

7.1. Monitor of Quality of Path Using MC

[2842] As shown in FIG. 153, an MC is inserted in a subscriber interface at an input terminal. The MC should be inserted at predetermined intervals of cells for each path. The SINF at an output terminal requires the function of monitoring the MC inserted at predetermined cell intervals.

[2843] Monitoring an MC is effective only for an active system because all MCs passing through the ASSW of a standby system are discarded in the SIFCOM at the output terminal of the standby system and do not reach the SINF at the output terminal as indicated by broken lines shown in FIG. 153.

[2844] Accordingly, the quality of a path in the standby system is tested only by the TCG.

[2845] The quality of a path using an MC is monitored in all SINFs, not in the SIFCOM.

7.2. Circuit Test of Test Cell Through TCG

[2846] The circuit test through a TCG is activated by the following tests.

[2847] (1) On Demand Test on Active System

[2848] Fault portion specifying test based on maintainer's command at an occurrence of a fault in the active system

[2849] (2) On Demand Test on Standby System

[2850] Normality confirmation test through online software at the switch of systems

[2851] (3) On Demand Test and Diagnostics Test on the OUS System

[2852] Fault portion specifying test based on maintainer's command at an occurrence of a fault in the standby system

[2853] Diagnostics

[2854] As shown in FIG. 154, since a test of specifying a faulty portion in an active system and a test of confirming normality before switching systems for a standby system are conducted, the SINF and SIFCOM are loaded with the cell-by-cell loopback function for performing a normal process on a user cell and looping back only cells generated by the TCG.

[2855] The cell-by-cell loopback function indicates a loopback for each VPI/VCI. Therefore, the switch software notifies a loopback unit of a VPI/VCI value of a looped-back cell through an MSD.

[2856] Since the test on the standby system or the OUS system through the TCG can only be conducted on a duplex portion, the normality of the dotted portion in FIG. 154 cannot be checked. Accordingly, the normality of the dotted portion is monitored by the monitoring function through the hardware (for example, a loopback function using a parity pilot signal). If a fault occurs at the portion, it is informed of by the MSCN information.

[2857] The OUS system as well as the active system and standby system has the cell-by-cell loopback function and also can activate the entire cell collective loopback function which is activated by the MSD information from the switch software.

8. FAULT CORRECTING PROCESS

8.1. Fault Detection Point and Notification System

[2858] Described below is the fault detection and notification system for each fault mode in correcting faults relating the SIFSH-A.

[2859] 8.1.1. Fault Mode

[2860] (1) OBP fault (OBP fault loaded on each package)

[2861] (2) Package missing fault

[2862] (3) Fuse disconnection fault

[2863] (4) SIFCOM package front connector missing fault

[2864] (5) Package erroneous insertion fault

[2865] (6) Individual unit package fault (simplex unit fault)

[2866] (7) SIFCOM package fault (duplex unit fault)

[2867] a) Individual unit interface fault

[2868] b) Common unit fault

[2869] (8) Individual unit-SIFCOM interface fault (simplex/duplex cross-connected portion fault)

[2870] 8.1.2. OBP Fault

[2871] This fault is described in 14.1.2. in part 2.

[2872] 8.1.2.1. Individual Unit OBP Fault

[2873] This fault is described in 14.1.3. in part 2.

[2874] 8.1.2.2. OBP Fault in SIFCOM

[2875] This fault is detected by monitoring the value of the OBP fault register in the SIFCOM of the mate system to the SIFCOM of the fault monitor object system as shown in FIG. 155.

[2876] The output of the LED output terminal of the OBP indicates a release state in a normal operation and a ground state in an abnormal operation. Therefore, a fault value is set in the OBP fault register when the output of the LED terminal indicates a ground state.

[2877] Since the SIFCOM comprises 4 packages and each package is loaded with an OBP, a signal line connecting the LED output terminals of all these OBP is connected to the SIFCOM of the mate system.

[2878] 8.1.3. Package Missing Fault

[2879] 8.1.3.1. Individual Unit Package Missing Fault

[2880] This fault is described in 14.1.4. in part 2.

[2881] 8.1.3.2. SIFCOM Package Missing Fault

[2882] This fault is detected by detecting the voltage release state of the monitor signal line in the SIFCOM of the mate system to the SIFCOM of the fault monitor object system as shown in FIG. 156.

[2883] 8.1.3.3. Power Package Missing Fault

[2884] This fault is detected by monitoring the state of the loop signal line in the SIFCOM of the mate system to the SIFCOM of the fault monitor object system as shown in FIG. 157.

[2885] 8.1.4. Fuse Disconnection Fault

[2886] 8.1.4.1. Individual Unit Fuse Disconnection Fault

[2887] This fault is described in 14.1.5. in part 2.

[2888] 8.1.4.2. SIFCOM Fuse Disconnection Fault

[2889] This fault is detected by monitoring the state of the signal line connected to the SIFCOM fuse in the SIFCOM of the mate system to the SIFCOM of the fault monitor object system as shown in FIG. 158.

[2890] When this fault is detected, the SIFCOM package missing fault described in 8.1.3.2. is detected simultaneously. However, the fuse-disconnection fault is detected by priority by the firmware in the SIFCOM and the switch software is informed of only the occurrence of the fuse disconnection fault.

[2891] 8.1.5. SIFCOM Package Front Connector Missing Fault

[2892] 8.1.5.1. 50-core Coaxial Flat Cable Fault

[2893] (1) ASSW→Higher Order Shelf→Lower Order Shelf

[2894] The disconnection of a 78 Mbps clock and cell frame pulse (CFP) is detected by the configuration shown in FIG. 159 as a disconnection fault of a 50-core downward coaxial flat cable connected to the ASSW.

[2895] The switch software is notified of the detected software through the SIFCOM of the mate system to the SIFCOM of the fault monitor object system.

[2896] Since the 70 Mbps clock from the ASSW and the CFP are distributed to the lower order shelf, these faults are detected in the higher and lower order shelves simultaneously, and can be notified of from the SIFCOM of the lower order mate system to the switch software.

[2897] (2) Lower Order Shelf ASSW

[2898] As shown in FIG. 160, the detecting unit similar to that shown in FIG. 159 relating to (1) above is mounted to both higher and lower shelves. However, as shown in FIG. 160, the detection output of the lower order shelf is masked. The clock disconnection fault detected in the higher order shelf is provided by the SIFCOM of its system (monitor object system) for the switch software.

[2899] 8.1.5.2. 50-core TD Bus Cable Fault

[2900] This cable transmits a cell write notification signal and a cell output permission signal (6.1.3., etc.) from a higher order shelf to a lower order shelf. The fault of this cable is detected by grounding an idle pin in the cable in the higher order shelf and monitoring the state of the pin in the lower order shelf.

[2901] 8.1.6. Erroneous Package Insertion Fault

[2902] This fault is described in 14.1.6. in part 2.

[2903] 8.1.7. Individual Unit Package Fault

[2904] This fault is described in 14.1.7. in part 2.

[2905] 8.1.8. SIFCOM Package Fault

[2906] The faults in the SIFCOM are classified into the following two types.

[2907] (1) Interface unit fault in individual unit

[2908] (2) Common unit fault

[2909] FIG. 162 shows the component in which a fault occurs. FIG. 163 shows a faulty portion, detection logic, detected portion, fault notifying method, and detection cycle.

9. LINE PROTECTION (N+1 System)

9.1. Outline of N+1 Protection System

[2910] An N+1 protection system is adopted as a subscriber path reassignment control system at the occurrence of a transmission line fault between a broadband remote line concentrator (BRCL; refer to FIG. 34) or a broadband remote line switching unit (BRSU) and a host switch.

[2911] According to the present embodiment, two in-band signaling routes are preliminarily provided to control the BRLC, etc. from the host switch. The two routes are accommodated by different transmission lines. As a result, control can be transferred from the host switch to the BRLC even when a fault occurs in a single transmission line.

[2912] Furthermore, according to the present embodiment, if the host switch is connected to the BRLC via N umbilical lines as shown in FIG. 164, then any of the lines, if a fault has arisen in the line, can be switched to a standby line (line P).

9.2. Line Reassignment Sequence

[2913] All faults in an umbilical line are detected in the individual unit (OC3C or DS-3; refer to FIG. 94).

[2914] A detected line fault is provided as EMSCN information by the individual unit for the SIFCOM, and then transmitted from the SIFCOM to the switch software via the BSGC.

[2915] The EMSCN notification is a fault representative notification, and the detailed fault information is read according to a command request from the switch software to the individual unit.

[2916] The individual unit notifies the switch software of the detailed fault information in response to the command.

[2917] FIG. 165 shows the sequence of reassigning a line in a line protection process.

9.3. Setting VCC in Standby Line

[2918] A standby line is provided with a VCC table whose contents are the same as those of the VCC table of N active lines. If a fault has arisen in any of the active lines, then the faulty line can be switched to a standby line immediately.

[2919] Since the active lines and the standby line are provided with the VCC tables of the same hardware scale, the VPI/VCI assignable to the umbilical line should satisfy the following restrictions.

[2920] (1) Each VPI/VCI set for the N lines should be unique.

[2921] (2) The type of the VPI/VCI set for the N lines should not exceed 2¹⁶.

[2922] (3) A VCC set command to the active lines and a VCC set command to the standby line should be simultaneously issued.

[2923] The above listed restrictions are placed on the SIFSH of the host and the RMXSH of the BRLC.

9.4. Switch to Standby Line

[2924] This function is described in 6.2.3.

9.5. Switch Command

[2925] Both SIFCOM and RMXCOM can adopt the configuration of the serial connection. In this case, the higher order shelf and the lower order shelf are controlled by independent microprocessors. Assuming that the active and standby lines are accommodated in both higher and lower shelves, the command format shown in FIG. 166 is adopted to prevent the effect of the switch command from the active line to the standby line from being different between the serial connection and non-serial connection.

[2926] As shown in FIG. 166, this command only contains the information about the identification number (Unit No.) of a unit which changes a tag value and about the tag value (TAGC) itself. That is, a tag value switch command is issued to each of the switching-from line and the switched-to line (protection line).

[2927] [0010 ]

[2928] <Part 4>

[2929] An ATM switch ASSWSH (ATM subscriber switch shelf) is described in detail in Part 4.

1. OUTLINE

1.1. Summary of Function

[2930] An ATM switch ASSWSH shown in FIG. 8 comprises an ASSWSH-A having a 4×4 panel ATM switching function and a CLKSH-A having a timing signal generating function.

[2931] The ASSW-A has the function of switching cells in the four input ATM highways each having the transmission speed of 622 Mbps to any of the four output ATM highways each having the transmission speed of 622 Mbps. This switching operation is performed according to the routing information written in the tag area in the ATM cell.

2. CONFIGURATION OF DEVICE

2.1. Configuration of Device

[2932] FIG. 167 shows the internal configuration of the ASSWSH-A.

[2933] In FIG. 167, the SWMDX (HMX03A) is an interface for the SIFSH, SBMESH, or BSGCSH (refer to FIG. 8).

[2934] The SWMX (HSR00A) is a switch matrix.

[2935] The SCLK (HTG02A) provides a timing signal generated by a CLKSH-A (HTG00A) for the SWMDX (HMX03A), SWMX (HSR00A), or SWCNT (HSR01A).

[2936] The SWCNT (HSR01A) is connected to a system bus not shown in FIG. 167 via the interface type A (INFA) to relay the communications of control data between the SWMDX (HMX03A), SWMX (HSR00A), or SCLK (HTG02A) and the switch processor (CC).

3. INTERFACE

3.1. Communication Line System

[2937] FIG. 168 shows the connection configuration of the communication line system.

[2938] A signal of the communication line system is connected to the SWMDX via the 50-core flat coaxial cable.

[2939] A signal in the ATM highway (HW) of 622 Mbps comprises 8-bit parallel data (having the transmission speed of 72 Mbps per bit), a parity signal for the data, a 78 MHz clock, a cell frame pulse indicating the head of a cell, and a cell enable signal indicating the validity/invalidity of the cell. All these signals have an interface having a circuit configuration of an emitter-coupled logic (ECL) through a balanced transmission. A JSOU×N signal indicating the existence of cable connection has an interface having a circuit configuration of a transistor logic (TTL) through a non-balanced transmission.

[2940] A parity refers to an odd parity for 8-bit parallel data excluding an enable signal. Parity bits of valid cells only are checked in the input unit of the ATM switch, and parity bits are assigned to valid cells only in the output unit of the ATM switch. The contents of the data in the information field (payload) of an invalid cell are not guaranteed.

[2941] FIG. 169 shows the signal timing of the interface between the SWMDX shown in FIG. 168 or 167 and the ATM highway of 622 Mbps. FIG. 170 shows the cell format in the interface.

3.2. Control System

[2942] As shown in FIG. 167, the ASSWSH-A and CLKSH-A are controlled by the CC not shown in FIG. 167 by being connected to a system bus not shown in FIG. 167 through the switch controller (SWCNT) and interface type A (INFA).

[2943] A switch controller (SWCNT) (FIG. 167) is provided with an inter-system cross-connection interface between the INFAs of both active systems and standby systems. Each block in the SWCNT and ASSWSH-A is connected via a processor data bus and an address bus.

[2944] Each block is controlled mainly by monitoring a fault. In this case, there are two types of fault results, that is, faults notified of by the MSCN to the CC through the INF and those notified of by an event to the CC.

[2945] FIG. 171 shows the interface between the INFA and ASSWSH-A.

[2946] The SWCNT is provided not only with an interface to the INFAs of both systems but also an interface to the SWCNT of the other system. FIG. 172 shows an interface between the SWCNT of its own system and the SWCNT of the other system.

[2947] In addition to the control function in the switch module, the function of the control system of the ASSWSH-A can be an active/standby control function to each terminal unit. As shown in FIGS. 167 and 168, the SWCNT comprises 32 output units corresponding to 32 output highways of 622 Mbps on both ends (sides 0 and 1: left and right sides of the SWMX) through the SWMDX. From the output units through the SWTIF not shown in FIG. 167, a system selection signal and its strobe signal are transmitted at the timing shown in FIG. 173. Since the system selection signal is not a signal indicating an active/standby system, it is output as a signal having the same polarity in both systems. Each terminal unit selects an active system device in the system according to the system selection logic shown in FIG. 174.

3.3. Clock System

[2948] Each device in the ASSWSH-A is operated using the clock of 155.52 MHz generated by the SCLK shown in FIG. 167 according to the clock of 10.368 MHz received from the CLKSH-A.

[2949] The ASSWSH-A and CLKSH-A each comprising two systems are cross-connected among the systems. A clock to be used in the ASSWSH-A is autonomously selected in the ASSWSH-A. If the disconnection of a clock is detected in the CLKSH-A of one system and the system is a master system, then the system is automatically switched to another.

[2950] In the clock system in the ASSWSH-A, each block of the SWMDX and SWMX is assigned a clock of 155.52 MHz, and one cell frame pulse is transmitted every 27th clock for use in reading a buffer in each block.

3.4 Inter-block Interface in ASSWSH-A

[2951] The interfaces among the blocks in the ASSWSH-A are listed below.

[2952] FIGS. 175 and 176 shows the external interfaces relating to the SWMX shown in FIG. 167.

[2953] FIGS. 177 and 178 show the external interfaces relating to the SWMDX shown in FIG. 167.

[2954] FIGS. 179 and 180 show the external interfaces relating to the SWCNT shown in FIG. 167.

4. DETAILED FUNCTION

[2955] FIG. 181 shows the detailed function of each block forming the ASSWSH.

[2956] FIG. 182 shows each block forming the SWMDX shown in FIG. 167. FIG. 183 shows the function of each block.

[2957] FIG. 184 shows each block forming the SWMX shown in FIG. 167. FIG. 185 shows the function of each block.

[2958] FIG. 186 shows each block forming the SWCNT shown in FIG. 167. FIG. 187 shows the function of each block.

[2959] FIG. 188 shows each block forming the SWTIF (not shown in FIG. 167). FIG. 189 shows the function of each block.

[2960] FIG. 190 shows each block forming the SCLK shown in FIG. 167. FIG. 191 shows the function of each block.

5. TRAFFIC CONTROL

5.1. Cell Discard Class

[2961] According to the present embodiment, the cell discard class shown in FIG. 192 is defined in the switch system to provide assured services and non-assured services.

[2962] In FIG. 192, the CLP and P correspond to the CLP bit and P bit in the header of each ATM cell. In the system, the CLP bit is used to quality-control the assured services, while the P bit is used to distinguish the assured services from the non-assured services.

[2963] In the ASSWSH-A, control is performed only to distinguish the assured services from the non-assured services. Therefore, only the P bit is used to control the process. During the congestion, a cell designated for a non-assured service is discarded.

5.2. Congestion Control

[2964] The function of controlling a cell discard class as shown in FIG. 192 is assigned in the ASSWSH-A to the 2.4 Gbps/622 Mbps DMUX unit in the SWMX and the SWMDX. A threshold (Xp) is set for the cell buffer in the LSI as the congestion control. If the length of the queue exceeds the threshold (Xp) in the buffer, then the cell whose P bit is set to 1 is discarded. If the length of the queue is smaller than the threshold (Xp), then the cell discard is suspended.

[2965] 5.2.1. Congestion Control in SWMX

[2966] As shown in FIG. 184, the SWMX comprises the SWCNT LSI and the ATMSW LSI. The SECNT LSI manages the length of the queue in the ATMSW LSI, and the SWCNT LSI outputs a discard instruction to the ATMSW LSI if the length of the queue exceeds the threshold.

[2967] The threshold of the buffer is set by the CC using an SO command in the initialization procedure. In this case, a default value Xp=A8 (H) is set as the above described threshold at the initialization of the firmware. Since the values of the sides can be specified as the parameters of the SO commands, independent thresholds can be set for both sides (sides 0 and 1: on the left and right sides of the SWMX shown in FIG. 168) of the SWMX.

[2968] 5.2.2. Congestion Control in SWMDX

[2969] The 2.4 Gbps/622 Mbps DMUX unit in the SWMDX is provided in the ADMUX LSI shown in FIG. 182. Setting the threshold for the SLI performs congestion control.

[2970] As in the case of the SWMDX, the threshold of the buffer is set by the CC using the SO command in the initialization procedure. In this case, the default value Xp=71(H) is set as the above described threshold at the initialization of the firmware. The same threshold (threshold specified by the SO command) is set in the SWMDX in the same ASSWSH-A regardless of the side.

[2971] 5.2.3. Cell Discard

[2972] Cells may be discarded in the ASSWSH-A due to the congestion, congestion control, faults, etc. At this time the occurrence of the cell discard is reported to the CC and the reporting processes are different between the SEMX and SWMDX. The cell discard reporting processes for the SWMX and SWMDX are described individually as follows.

[2973] In the SWMX, cell discard is regarded as a fault. At the notification of the occurrence of cell discard, “a fault in the SW” in the 22nd bit of the MSCN is determined, and displayed is the input highway of the self-routing module (SRM) in which the cell discard has occurred in the detailed fault data. The fault data is described in detail in 7.

[2974] In the SWMDX, cell discard is not regarded as a fault. Since the 622 Mbps/2.4 Gbps MUX unit in the SWMDX is an STM, the no discard occurs and the discard portion is exclusively the 2.4 Gbps/622 Mbps DMUX unit. The number of times in every 15 minutes that cells are discarded is counted in the traffic measure process described in 5.3. The occurrence of cell discard is recognized by the CC's reading the count value.

5.3. Traffic Measure Process

[2975] In the ASSWSH-A, the number of the following cells is counted in the 2.4 Gbps/622 Mbps DMUX unit as the function similar to the performance monitor in order to manage the status of the network.

[2976] (1) number of passing cells (P=0) per 622 Mbps highway

[2977] (2) number of passing cells (P=1) per 622 Mbps highway

[2978] (3) number of discarded cells (P=0) per 622 Mbps highway

[2979] (4) number of discarded cells (P=1) per 622 Mbps highway

[2980] Each of the above described parameters is collected every 15 minutes with the notification received from the CC every 15 minutes as a trigger.

[2981] FIG. 193 is a block diagram showing the traffic measure circuit.

[2982] The cells are counted according to the output L, V, and H from the ADMUX LSI 1 (FIG. 182) as shown in FIG. 193, and the values are stored in the external RAMs 4 and 5.

[2983] The traffic count is performed for each highway by the 8-bit counters 2 and 3 on the cycle of about 25 μsec. The count value is stored at a specified address in the RAM 4 or 5 through the selector (SEL) 8 and adder (ADD) 9. The adder (ADD) 9 adds up in the next cycle the count value read from the RAM 4 or 5 through the selector (SEL) 6 or 7 and the count value read from the counter 2 or 3 through the selector (SEL) 8, and the sum is stored again at the above described specified address. The TG 10 outputs a switch instruction to the selectors (SEL) 6 through 8 each time it receives a notification from the CC every 15 minutes, and switches the RAM to which the count value is written to the RAM 4 or 5. As a result, the RAM 4 or 5 in which writing of a count value has been stopped stores the count value received in the latest 50 minutes immediately before the switch instruction. The count for the subsequent 15 minutes is performed in the RAM 4 or 5 to which a count value is newly written.

[2984] After the notification at every 15th minute from the CC, each count value is read from the RAM 4 or 5 in which writing of a count value has been stopped. The read count values are stored in the firmware until the CC requests using an SO command to read the count value.

[2985] FIG. 194 is a timing chart showing the operation of the traffic measure circuit shown in FIG. 193. The signals A through E shown in FIG. 194 correspond to the signals A through E shown in FIG. 193.

6. FUNCTION OF FIRMWARE

[2986] The ASSWSH-A contains the firmware in the SWCNT to provide an intra-switch control function and an INFA interface function.

[2987] Described below are the functions of the firmware and the interface between the firmware and hardware.

6.1. INFA Interface

[2988] The interface between the ASSWSH-A and the INFA has a predetermined format in the data bus (SB0 through SB77).

[2989] The information is transferred in this format for the following operations.

[2990] (1) CC access (IN instruction)

[2991] (2) CC access (OUT instruction)

[2992] (3) DMA access (read)

[2993] (4) DMA access (write)

[2994] FIG. 195 is a timing chart (a) of the CC access (IN instruction) and an address/data format (b);

[2995] FIG. 196 is a timing chart (a) of the CC access (OUT instruction) and an address/data format (b);

[2996] FIG. 197 is a timing chart (a) of the DMA access (read) and an address/data format (b); and

[2997] FIG. 198 is a timing chart (a) of the DMA access (write) and an address/data format (b).

[2998] The order received in the ASSWSH-A is classified to each order as shown in FIG. 199 according to the value of the 4 lower bits in the 4th word at the address. Described below is the process in the ASSWSH-A at the reception of each order.

[2999] Activation of a command: The procedure described later in 7.2.1. is followed.

[3000] Retry instruction: When a DMA access is in a prohibition state, the DMA access is retried.

[3001] If the retrial is performed successfully, the DMA access prohibition is released.

[3002] If the retrial is performed but failed, then the DMA access prohibition is maintained.

[3003] If the DMA access is not in the prohibition state, then the order is ignored.

[3004] MSCN read: The contents of the MSCN table in the ASSWSH-A are returned and the table is cleared.

6.2. Intra-device Hard Interface

[3005] The interface between the firmware and each block in the ASSWSH-A is realized by the order from the SWCNT and response in a specified format in a data bus.

6.3. Fault Correcting Process

[3006] 6.3.1. Fault Detection

[3007] The important functions of the firmware in the SWCNT are to collect the fault information in the ASSWSH-A and to notify a higher order device (CC) of the fault information.

[3008] FIG. 200 shows the fault detection procedure followed when a notification is made by the MSCN. FIG. 201 shows the fault detection procedure followed when a status is autonomously notified of.

[3009] If a fault occurs in any block in the ASSWSH-A, then the block causes an interruption for the firmware in the SWCNT and notifies the firmware of the contents of the fault through the response described in 6.1. above.

[3010] An interrupt handler (INTO handler) generates fault notification data (message box: MSG BOX) to be provided for the fault correcting task and activates the fault correcting task.

[3011] The fault correcting task updates detailed fault data according to the contents of the message box. If the contents of the data refer to the fault in the MSCN, then the MSCN table is also updated.

[3012] The above described process is realized by the process modules (1) through (3) listed below.

[3013] Each time a fault is reported from each block, the fault counter (refer to FIG. 231 described later) is updated by the alarm interruption handler listed as (1) above. If the fault refers to a fixed fault, the fault counter is incremented each time it is reported. If a fault refers to an intermittent fault, then the fault counter is not incremented or incremented only a little bit. Therefore, according to the cycle activation task listed as (2) above, it is determined whether a fault reported by each block refers to an intermittent fault or a fixed fault by checking the value of the fault counter.

[3014] 6.3.2. Message Box

[3015] FIG. 202 shows a basic format of a message box processed by the fault correcting task.

[3016] (1) Listed below are the contents of the message box having the format shown in FIG. 202 when the disconnection of the clock of one system is reported from the SCLK.

[3017] (2) Listed below are the contents of the message box having the format shown in FIG. 202 when a common fault other than the disconnection in one system is reported from the SWMX, SWMDX, SCLK, etc.

[3018] FIG. 203 shows the fault content write data in the message box having the format shown in FIG. 202. In FIG. 203, the representations “intra-” and “inter-” indicate that the fault occurs in the package and between the packages respectively. The identification is made according to the contents of the fault (reported in the format described in 6.2. above) in each device.

6.4. Self-diagnosis

[3019] Upon receipt of a self-diagnosis setup command from the CC (switch processor), the firmware in the SWCNT makes a diagnosis of each fault monitoring function according to an order.

[3020] The firmware issues the following orders among the orders described in 6.2. above and performs a diagnostic process and checks the result.

[3021] A self-diagnosis is effective when the state of the ASSWSH-A is blocked. Otherwise, a command illegal is output. Upon receipt of a self-diagnosis setup command, the firmware shifts the state of the ASSWSH-A from a blocked state to a self-diagnostic state.

[3022] The self-diagnostic procedure is described in 7. below.

7. MAINTENANCE

7.1. Software-hardware Interface

[3023] The procedure of maintaining the ASSWSH-A is described including the interface between the switch software and the hardware of the ASSWSH-A.

[3024] The interface between the CC and the ASSWSH-A is performed through the INFA (refer to FIG. 167). The switch software operated by the CC controls the ASSWSH-A by transmitting and receiving a command and status. The interface between the ASSWSH-A and the INFA is performed by the firmware described in 6. above.

7.2. Operations

[3025] 7.2.1. State Transition

[3026] The ASSWSH-A indicates any of the following states.

[3027] (1) Initialization state: A reset signal has been received and the firmware of the device is being initialized.

[3028] (2) Blocked state: A reset completion notification has been issued and an initialize command can be executed.

[3029] (3) Operating state: An online setup command has been received and the intrinsic operations are being performed.

[3030] (4) Fault state: A fault has occurred in the device and the device cannot be operated.

[3031] (5) Self-diagnostic state: The initialization has been completed and a self-diagnosis is being performed.

[3032] 7.2.2. Loading HMX03A

[3033] Up to 4 pieces of the HMX03A (SWMDX) (refer to FIG. 167), which is provided in the ASSWSH-A and assigned the MUX function, can be mounted on either side of the HSR00A (SWMX), that is, a total of 8 pieces can be mounted. Since the HMX03A is mounted by specification, the ASSWSH-A successfully functions only by loading the HMX03A of the number of highways used on the conditions of the station.

[3034] However, the firmware of the ASSWSH-A requires an answer from a package when it accesses the package. Therefore, if there is an unused HMX03A slot, the firmware should recognize the slot in controlling the packet.

[3035] The firmware controls the device according to the following procedure after recognizing the load of a specified HMX03A.

[3036] (1) When the ASSWSH-A is in the initialization state, the firmware sends an individual reset order to each HMX03A and waits for an answer.

[3037] The firmware determines that the HMX03A is mounted for the slot which has sent back an answer, and that it is not mounted for the slot which returned no answer.

[3038] The firmware performs these processes only for load-recognized slots.

[3039] (2) After terminating the initialization of the device, the state of the ASSWSH-A changes into the operating state in which the system initialization is performed from a higher order process. At this time, the firmware is notified of the load state of the HMX03A displayed by the station data stored by the switch software, and the state is compared with the load state recognized by the firmware in the process described in (1) above.

[3040] (3) In the comparing process in (2) above, if there is a slot which is recognized by the firmware as not being loaded with the HMX03A and is displayed according to the station data as being loaded with HMX03A, then the firmware determines that a fault has occurred on the slot. In this case, the firmware determines a “fault in the SW” of the 22nd bit of the MSCN and includes the slot in the detailed fault data.

[3041] (4) In the comparing process described in (2) above, if there is a slot which is recognized by the firmware as being loaded with the HMX03A and is displayed according to the station data as not being loaded with HMX03A, then the firmware determines that a fault has not occurred on the slot. In this case, the subsequent control is performed according to the station information.

7.3. Fault Correcting Process

[3042] The ASSWSH-A has the specification of monitoring a fault as follows.

[3043] (1) A duplex configuration is adopted as a redundant configuration (one shelf for one system).

[3044] (2) Various fault detection processes are performed, and the systems are switched according to the detection result (control by the switch software).

[3045] (3) An intermittent/fixed fault is determined in monitoring a fault, and the determination result is reported to the CC. In determining a fault, if faults are detected 3 times consecutively on a cycle of 0.1 through 1 second, the faults are determined to be fixed faults. Otherwise, the intermittent faults are not reported to the CC.

[3046] (4) Faults are notified of by either the MSCN or an event.

[3047] (5) If a fault is reported, an alarm LED provided for the power source package (not shown in the drawing) is lit under the control of the switch software.

[3048] [0011 ]

[3049] <Part 5>

[3050] In part 5, described in detail is the subscriber message handler (SBMH)

1. GENERAL DESCRIPTIONS

1.1. Summary

[3051] The subscriber message handler shelf (SBMESH) switches data of the SMDS subscriber. The switch is performed actually in cell unit while the message format is checked. As for a protocol, terminated are level 2 (AAL-SAR) and level 3 (AAL-CS,CL) of the SNI interface protocol (SIP) which is a protocol of an SMDS subscriber. In the drawings, the SBMESH-A also refers to the SBMESH.

[3052] 1.1.1. Positioning in System

[3053] FIG. 204 shows the positioning of the SBMESH in the system. It specifically shows the SBMESH (and the GWMESH described in Part 6) in the configuration shown in FIG. 8 and described in Part 1 of the present embodiment.

[3054] Up to 4 SBMESHs can be daisy-chained for each highway connected to the ASSW. An SBMESH group connected to one of the highways is referred to as a subscriber message handler (SBMH) as shown in FIG. 204.

[3055] In FIG. 204, an actual SMDS terminal unit is connected beyond the subscriber network interface (SNI). Likewise, an switching system (SS) is connected beyond the inter-switching-system interface (ISSI), and a LATA SS is connected beyond the inter-carrier interface (ICI).

[3056] The SBMESH (SBMH) comprises an S portion and an R portion, and the data input from the SNI to the system is processed in the S portion of the SBMESH, and the data processed in the R portion of the SBMESH (SBMH) is output from the system to the SNI. The connection between the SBMESH and the GWMESH (WGMH) is described in Part 6.

[3057] 1.1.2. Outline of SMDS Data Process FIG. 205 shows the route of SMDS data between SNIs, and the data is processed in the following procedure.

[3058] 1. The data input from the SNI to the ASSW (UP) through the SIFSH, etc. is transferred to the SBMH(S) via a fixed path or a semi-fixed path in the ASSW (UP). In this case, the VPI/VCI stored in the header of a cell indicates the routing from the SNI to the SBMESH.

[3059] 2. The SBMESH analyzes the destination address (DA) contained in the data, retrieves a route to the SBMH (R) accommodating the destination SNI, and transmits the data to the ASSW (UP).

[3060] 3. The above described data is entered in the SBMH (R) accommodating the destination SNI through the ASSW (UP), LLP, and ASSW (DOWN).

[3061] 4. The SBMH (R) refers to the destination address (DA) in the received data, fetches the data addressed to the SNI accommodating the SBMH (R) (filtering), retrieves the route to the destination SNI, and transmits the data to the ASSW (DOWN). The circuit connecting the SBMH (R) to the destination SNI is connected via a fixed or semi-fixed path.

[3062] FIG. 206 shows the transmission of SMDS data from the SNI to the ISSI or ICI. FIG. 207 shows the transmission of the SMDS data from the ISSI or ICI to the SNI. FIG. 208 shows the transmission route of the SMDS data from the ISSI or ICI to the ISSI of ICI. In these figures, the data is transmitted through the route represented by bold lines.

[3063] Thus, in the case of the data transmission between the SNIs, processes are performed only by the SBMH. When the data is transferred to and from other SS and LATA SS, the processes are performed by the SBMH and GWMH. The actual routing control, the relationship between each route and a VPI/VCI, etc. are described later in detail.

1.2. System Configuration

[3064] FIG. 209 is a block diagram showing the SBMESH.

[3065] As shown in FIG. 209, the SBMESH comprises an MH-COM unit for interfacing with the ASSW and an LP unit for performing actual switching.

[3066] The MH-COM unit comprises an SDMX, RDMX, SMUX, and RMUX. The characters S and R for the MUX and DMX correspond to the SBMH(S) and SBMH(R) shown in FIG. 204. For example, the SDMX multiplexes the data from the SBMESH connected to the downstream of the corresponding SBMESH in a plurality of SBMESHs daisy-chained to the output of the ASSW. The above described DMX fetches the data output from the ASSW to its own SBMESH, and the MUX outputs data from its own SBMESH to the ASSW.

[3067] A link access procedure (LAP) terminating equipment and a VCI converter (VCI) are equipped in addition to the above described configuration although they are not show in FIG. 209. The VCC is set by the LAP. The MH-COM unit has a checking function and detected information is provided with interface to the software through the LAP or the broadband signaling controller (BSGC) described later in Part 7.

[3068] The LP unit comprises an SMLP, RMLP, and LP-COM. The initial characters S and R of the SMLP and RMLP correspond to the SBMH (S) and SBMH (R) and switch data. The LP-COM controls the SMLP and RMLP and interfaces with the software through the INF (interface). The station data required for a switching, subscriber data, information detected by each checking function in the LP unit, billing information, etc. are provided with interface to the software through the INF.

[3069] As described above, up to 4 SBMESHs can be daisy-chained. The data received by the SBMESH is multiplexed and demultiplexed by the SDMX, RDMX, SMUX, and RMUX. On the other hand, the LP unit and the INF is connected one to one. For example, if four SBMESHs are daisy-chained, four transmission lines are required accordingly.

1.3. Redundant Configuration

[3070] As shown in FIG. 210, the MH-COM and LP units have duplex configurations (systems #0 and #1).

[3071] The MH-COM unit has a master/slave configuration exclusive for the ASSW, while the LP unit has an independent master/slave configuration. The master system (for example, #0) and slave system (for example, #1) of the LP unit have basically the same function, and the slave system can actually perform a switching operation. In this case, the billing information obtained through the slave system's switching is not reported to the software.

[3072] There is an inter-system cross-connection between the duplex MH-COM unit and LP unit, that is, between system #0 of the MH-COM unit and system #1 of the LP unit and between system #1 of the MH-COM unit and system #0 of the LP unit. However, no inter-system cross-connection exists between system #0 of the LP unit and system #1 of the INF and between system #1 of the LP unit and system #0 of the INF.

[3073] The RMLP in system #0 of the LP unit receives data from the RDMX of system #0 of the MH-COM unit and data from the RDMX of system #1 of the MH-COM unit. The selector (not shown in the figure) in the input unit of the RMLP selects the data from the master system of the MH-COM unit. Likewise, the SMUX of the MH-COM unit receives data from the SMLP of system #0 of the LP unit and data from the SMLP of system #1 of the LP unit. The selector (not shown in the figure) in the input unit of the SMUX selects the data from the master system of the LP unit.

2. PROCESS METHOD

2.1. Configuration of Message Handler (MH) Network

[3074] A message issued from the SNI is transmitted to a predetermined SMLP in the SBMH through a digital terminal (DT), etc. from the SNI. A message received at the SNI is transmitted from a predetermined RMLP in the SBMH to the SNI. The message is transmitted via a path comprising a permanent virtual circuit or permanent virtual channel (PVC) through the ASSW. Since each of the SMLP and RMLP accommodates a plurality of SNIs, the above described transfer destination is identified by a VCI.

[3075] As shown in FIG. 211, MHs (including the GWMH) are fullmesh-connected. The connection is made using a PVC through the ASSW. However, since each RMLP (receiving SBMH and GWMH) receives a message from a plurality of SMLPs (sending SBMH and GWMH), the message is identified by a VCI specifying each PVC.

[3076] The band (average and peak) of each PVC is, for example, 2.1M between the SNI and the MH, and the DS3-SNI is set to 38.88M. Between MHs, the band is set depending on the number of MHs when the system is set. It can also be set optionally by the system maintainer, etc.

[3077] A message issued to the ISSI or the ICI connects the route from the SMIP in the GWMH accommodating the ISSI or ICI to the ISSI or ICI by the PVC through the ASSW. A message issued from the ISSI or ICI connects the route from the ISSI or ICI to the RMIP in the GWMH accommodating the ISSI or ICI by the PVC through the ASSW. However, since the SMIP or RMIP of each GWMH accommodates a plurality of ISSIs or ICIs, it is individually identified depending on the VCI specifying each PVC.

2.2. Routing System

[3078] A routing process is performed in the SMLP shown in FIG. 209. That is, the data issued by a subscriber terminal unit is entered in the SBMH through a PVC. In the SMLP of the SBMH, the destination address DA of the transfer data is identified. An MH accommodating the destination subscriber terminal unit is identified according to the identified DA. The MH is uniquely assigned a VCI, and the data is output to the ASSW. (The VCI in the SNI normally refers to a specific fixed value indicating that the transfer data is SMDS data. However, a VCC is actually provided between the above described SBMH and the RMLP of the MH accommodating the destination subscriber terminal unit, and the VCI is converted into that indicating the PVC to the MH).

[3079] On the other hand, in the RMLP, the SNI of the destination subscriber terminal unit is identified according to the above described DA. In the VCC provided between the RMLP and the SNI, a VCI specifying the SNI is assigned. Thus, the routing control in the SMLP and RMLP is normally performed according to the destination address DA.

[3080] The destination address DA is a concept defined in message units (L3-PDU units), that is, in layer 3. However, an actual switching is performed in cell units. Described below is the control method.

[3081] The decomposition and assembly of user information in layer 3 are explained by referring to FIG. 212. The user information issued by a subscriber terminal unit has a destination address DA written at the header in layer 3. When the information is converted into data in a 53-byte cell (actually 53 bytes containing the header and trailer for the L2-PDU), which is a data transmission unit, in the AAL/SAR in layer 2, the message in the above described layer 3 is decomposed into a BOM (beginning od message), COM (continuation of message), and EOM (end of message). If this message is small enough to be stored in a single cell, it is put in one type of cell (single segment message).

[3082] FIG. 213 shows the data configuration in the AAL/SAR in layer 2. As shown in FIG. 213, the destination address DA specified by the message of layer 3 is stored in the payload of the BOM (or SSM) in the AAT/SAR of layer 2. The type of cell BOM, COM, EOM, or SSM is stored in the 6th byte as a segment type ST. A message identifier (MID) is an identifier uniquely assigned to each message (or each SNI).

[3083] Upon receipt of a BOM or SSM, the SBMH analyzes the DA stored in the payload and determined the output VCI according to the DA. It then rewrites the VCI of the header into the determined output VCI. It also retrieves an unused MID for the output VCI, and rewrites the MID stored in the input cell into the retrieved MID (output MID). If a BOM is received, it has the routing memory store the correspondence between the input VCI/MID and the output VCI/MID for the subsequent COM and EOM.

[3084] Upon receipt of a COM or EOM, the SBMH reads the output VCI/MID by retrieving the above described routing memory through the input VCI/MID of the cell as a key, and writes the cell at a predetermined position. FIG. 214 is a list showing the method of determining an output VCI/MID.

[3085] Described below are the routing processes.

[3086] (a) Routing from Source SNI to Source SBMH

[3087] The VCI of a cell output from a source SNI has a predetermined fixed value as described above. However, in the VCC provided in the SIFSH between the SNI and the SBMH, the VCI is converted into one predetermined for the source SNI. The cell is assigned tag information such that the cell can be transferred to the SBMESH accommodating the source SNI. The source SBMH allocates the cell to a predetermined SMLP according to the allocated tag.

[3088] Thus, in routing a cell from a source SNI to a source SBMH, a cell is transmitted through a route determined by the VCI, that is, through a predetermined PVC. In the above described routing, the source SNI is accommodated in the DS3-DT card.

[3089] (b) Routing from Source SBMESH (SBMH) to Destination SBMH

[3090] In a source SBMESH, a destination SBMESH is determined according to the DA stored in an input cell for a BOM or SSM, and according to the input VCI/MID of the cell for a COM or EOM. In the source SBMESH, a VCI/MID for a PVC preliminarily provided between the source SBMESH and the destination SBMH is assigned to the cell. Additionally, the cell is assigned a tag such that the cell can be transmitted to the destination SBMH. The SBMH obtains an output VCI/MID according to the DA for a BOM or SSM and according to an input VCI/MID of an input cell to a destination SBMH for a COM or EOM. The obtained output VCI/MID is assigned to a predetermined RMLP as routing information for output.

[3091] (c) Routing from Destination SBMESH to Destination SNI

[3092] A destination SBMESH determines in the RMLP a destination SNI according to the DA for a BOM or SSM and according to an input VCI/MID of an input cell to a destination SBMH for a COM or EOM. In the RMLP, a VCI/MID for a PVC preliminarily provided between the destination SBMESH and the source SNI is assigned to the cell. Additionally, the cell is assigned a tag such that the cell can be transmitted to the destination SNI. The above described routing is an example where the above described SNI is accommodated in the DS3-DT card.

[3093] FIG. 215 shows the above described routing operation.

2.3. VPI/VCI and MID Assigning Method

[3094] 2.3.1. VPI/VCI Assigning Method

[3095] As a rule, a VPI/VCI is assigned the same value in the same PVC regardless of the data transfer direction.

[3096] (1) Assignment Between SNI and SBMH

[3097] A VPI/VCI is assigned a fixed value in the SNI and B-UNI.

[3098] VPI/VCI of a cell transferred from a subscriber to the ASSW in the SNI

[3099] (a) The MSB 8 bits are optionally set.

[3100] (b) The subsequent 20 bits are set to “fffff(h)”

[3101] VPI/VCI of a cell transferred from the ASSW to a subscriber in the SNI

[3102] “00fffff(h)”

[3103] VPI/VCI of an SMDS cell transferred from a subscriber to the ASSW in the B-UNI

[3104] (a) The MSB 4 bits are optionally set (GFC field).

[3105] (b) The subsequent 24 bits are set to “00000f(h)”

[3106] VPI/VCI of an SMDS cell transferred from the ASSW to a subscriber in the B-UNI

[3107] “000000f(h)”

[3108] The VCI between the ASSW and SBMESH is assigned a VPI/VCI uniquely corresponding to each SNI such that the SNI can be correctly identified in the SMLP as shown in FIG. 216.

[3109] FIGS. 217 and 218 show the above described method of assigning a VPI/VCI between the SNI and SBMH. As an example, a method of assigning a VPI/VCI for “from SNI to SMLP (upward)” shown at the middle portion in FIG. 217 is explained below.

[3110] As shown in FIG. 217, a fixed value xxfffff(h) is assigned to the header of the cell in the SNI. Upon receipt of the cell assigned the fixed value of xxfffff(h) from the SNI, the DT (for example, the DS3-SMDS interface explained in Part 2) converts the value into “03f03ff(h)” as if it were hardware. Then, the SIFCOM converts the VPI/VCI into “03f0307(h). The value “07” represented by the lower bits corresponds to the SNI number #7. A cell assigned a value of “03f03ff(h)” as a VPI/VCI is transferred to the SBMH.

[3111] Upon receipt of the cell, the SBMH recognizes from its VPI/VCI that the cell is SMDS data output from the SNI #7.

[3112] (2) Assignment Between MHs (in the station)

[3113] Between SMLP and VC of VCC output by SMLP The VPI uses the value 03f(h) and VCI uses the values 0300 through 03ff(h).

[3114] The number identifying the MH at the receiving equipment is set to the 8 lower bits of the VCI.

[3115] Between VCC output from SMLP and VCC of ASSW at receiving equipment

[3116] A VPI/VCI in this portion is not defined.

[3117] Between VCC of ASSW at receiving equipment and RMLP and SMIP

[3118] The VPI is “03f(h)” and the VCI is a value in the range of 0300 through 03ff(h).

[3119] The value identifying the MH at the sending equipment is set at the 8 lower bits of the VCI.

[3120] FIG. 219 is a table showing the method of assigning a VPI/VCI between the above described MHs. FIG. 220 shows an example of assigning a VPI/VCI between the above described MHs.

[3121] As shown in FIG. 220, “03f0303(h)” is assigned as a VPI/VCI when a cell is transferred from the SBMH #4 to the SBMH #3, and the 8 lower bits indicate the SBMH #3 which is a receiving MH. If the cell is entered in the SIFCOM connected to the SBMH #3 through the switch (AISW), etc., then the VPI/VCI of the cell is converted into “03f0304(h)”, and the 8 lower bits indicate the SBMH#4 which is a sending MH. Thus, the MHs at the sending and receiving equipments are recognized depending on the VPI/VCI

[3122] 2.3.2. MID Assigning Method

[3123] (1) Between SNI and SBMH

[3124] An MID assigning method for a cell to be transferred from the SNI to the SBMH depends on the configuration of the connected subscriber terminal unit. Therefore, the SMLP has the configuration capable of receiving all patterns of MID. The MID can be simultaneously assigned 16 values for each SNI. The MID of the cell transmitted from the SBMH to the SNI can be in the range of 000 through 1ff(h).

[3125] (2) Between MHs

[3126] In the SMLP, the number of MIDs of the cell transmitted to the destination MH is 256 per VCI (that is, per destination MH. As described above, a source MH is identified using the VCI of a received cell at the destination MH. If a plurality of SMLPs which belong to the same source MH (for example, if a single SBMH has a plurality of daisy-chained SBMESH, each SBMESH has its own SMLP) uses the same MID, an SMLP cannot be specified at the destination MH. Therefore, the range of the MID assigned to each SMLP belonging to the same source MH is defined as shown in FIG. 221. The SMLP #0 in FIG. 221 refers to the SMLP provided in the highest order SBMESH in up to 4 daisy-chained SBMESHs, sequentially followed by #1, #2, #3, . . . downward.

2.4. Group Address

[3127] If a destination address DA refers to a group address, the message transferred according to the DA is copied at the SBMH and transferred to all destination SBMHs and source GWMHs in the station. In the destination SBMH, the RMLP accommodating the SNI at the destination group address fetches the message. The RMLP recognizes the number of SNIs belonging to the group address, makes copies for the number of the SNIs, and transfers the copied message to each SNI. FIG. 222 shows the distribution of data using the group address.

2.5. Multiplexing

[3128] The SMLP and RMLP can accommodate a plurality of SNIs. Accordingly, each ENI can be identified for each cell. Since the SMLP and RMLP simultaneously process a plurality of L3-PDUs, they use a VPI/VCI and MID to identify the L3-PDU to which each cell belongs.

2.6. Outline of Functions

[3129] FIG. 224 is a block diagram showing the functions of the SBMESH. Each block shown in FIG. 224 is described later. In FIG. 224, the division of the PWCB is not shown for each observation of the drawings.

3. SMLP

3.1. Outline of Processes

[3130] In the SMLP, a protocol performance check of the SIP L2 and SIP L3 is made for the cell entered after being DMUXed by the MH-COM unit. The destination address DA of the cell is analyzed, and the cell is transmitted to the SBMH accommodating a corresponding SNI (subscriber) and the GWMH accommodating corresponding ISSI and ICI. The SMLP also has the function of converting the SIP L3 format into the ISSI L3 format (half encapsulation).

3.2. Configuration

[3131] FIG. 225 shows the entire configuration of the SMLP.

[3132] The SMLP comprises four printed wiring circuit boards (PWCB) HMH03A through HMH06A. HMH03A and HMH04A mainly perform a protocol performance check. A cell determined to be an error in the check is so identified with an error flag to be transferred together with the cell data. Finally, the cell is discarded at the output unit of the HMH06A. The HMH05A performs routing as a DA analysis and destination MH determination process. The HMH06A mainly performs a PVC band restriction process. FIGS. 226 through 228 show the outline of the functions of each block and the relationship between an error cell and a maintenance cell.

[3133] (1) Error Cell

[3134] An error cell refers to a cell whose master error flag (EF1 MS) is set to NG (ON), and it should be discarded. The SMLP uses memory for various objects, and skips write access to memory if an error cell is detected.

[3135] (2) CRC-10 Error Cell

[3136] A CRC-10 error indicates an error in the data of SIP-L2.

[3137] If an error exists in data, conducting a protocol performance check using the erroneous data may cause another error. Since the L3-PDU (or a SIP-L3 message) is identified from another L3-PDU using an MID, an error caused by a SIP-L3 message may be regarded as an error pointed to by another SIP-L3 message if the MID value is incorrect. Therefore, if a CRC-10 error is detected, no subsequent protocol performance check is made.

[3138] (3) LP Test Cell (diagnosis)

[3139] In the diagnosis of the SBMESH, a test cell is transmitted from the HLP02A, and returned to the HLP02A from each processing unit in the SMLP to check error flags, etc.).

[3140] The diagnosis is conducted when the SMLP is in the OUS state (out of service state). The subscriber data for use in testing corresponding to each SNI is set on a table used in transferring actual data, and not table is provided for test use. Therefore, an LP test cell which will not set an error flag is transferred to the MUX of the MH-COM unit without being discarded. However, since the SMLP is not in the master state (in the OUS state), the above described test cell is discarded by the selector at the input unit of the MUX.

[3141] (4) PVC Test

[3142] (1) PVC test between SBMESH-MHs

[3143] In this test, the HLP02A of the SBMESH (HLP024 is a PWCB in the LP-COM described later) sends a test cell to the SMLP. The SMLP sends the test cell to the RMLP of the destination MH through the ASSW. The RMLP sends the test cell to the HLP02A in the MH to check the normality of the cell. Thus, the PVC test is conducted between the SBMESH and the destination MH. The test cell is transmitted from the HLP02A with a specific VCI value.

[3144] When the test cell identification bit in the VCI (this bit is described in detail later, but is referred to as an 0 bit or bit-7) indicates 1, the test cell is implied and a process is performed for the test. Since the test is conducted in the INS state (in-service state), the protocol performance check is not made to give no effect on normal message.

[3145] (2) PVC test between SNI and SBMESH

[3146] In this test, a test cell is transmitted to the RMLP. The test cell is looped back at the SNI (SIFSH in this embodiment) and input to the SMLP. Each checker in the SMLP performs on the test cell a process similar to that performed on a common cell. A routing unit checks a cell according to the DA. If it is a test cell, it is transmitted as VCI=“FF(h)” to the HLP02A. The test is conducted with the object SNI blocked.

3.3. Correspondence Between Each Function Block and Error Flag

[3147] FIGS. 229 through 232 show the conditions under which each function block and an error flag (EF) for each function block operate. The tables shown in these figures are described below.

[3148] The vertical axis indicates a function block.

[3149] The horizontal axis indicates the states of the error flags EF (EF1 and EF2) and the states of the test between the MESH and PVC.

[3150] Each item is divided into two portions. An upper portion indicates the EF which is set to NG after the function block is checked, and controls the EF described as “ON” if it is set to NG. A lower portion indicates whether or not the function should be operated (if the unit is a checker, it indicates whether or not a check should be made) or whether or not a check result should be provided for the EF.

[3151] FIGS. 233 through 237 show the correspondence between the error flag (EF) and the error name (at TR) and the position of the EF in a cell.

3.4. Process in Each Block

[3152] In the drawings of this chapter, the process described as “own” indicates read/write memory of the hardware.

[3153] (1) Cross-connection Selection S

[3154] According to the act information (SWACTA: home system SW ACT=L; mate system SW ACT=H) of the switch set by the HLP02A, active type data is selected. The ACT control at the switch unit, that is, “retaining ACT” is controlled by the HOL02A. Since the data from the home and mate system switches are not aligned for the header of the cell (not in phase), the data is once written to the buffer and then read from the home and mate systems after adjusting the phase of each of the cells.

[3155] If the SW of the active system is switched, the selector of the data is actually switched. The timing is adjusted between the cells. FIG. 238 shows the timing.

[3156] Since the SMLP receives a TCG cell (test cell generator cell) for use in conducting a switching test for an ATM layer together with other common data, the TCG cell should be invalidated. The TCG cell is identified by an 0 bit at the 14th bit in the tag area. In this block, “enable” indicates “valid”. A cell having an 0 bit set to 1 performs a process of setting “enable” to “disable”. If “enable” is set to “disable”, the parity should be adjusted correspondingly. FIG. 239 shows the format of the cell. In FIG. 239, the 0 bit is shown in shade.

[3157] (2) Test Cell Multiplexing S

[3158] A test cell multiplexing unit multiplexes a test cell from the HLP02A at a timing of an idle cell in the line. The HLP02A optionally transmits a test cell at any timing. When the line is in the idle cell state (when enable (ENB)=H) in the present block, a test cell is multiplexed and transmitted, and notifies the HLP02A of the result using a signal (TSOK) indicating the “test cell multiplexed?”. If a valid cell is transmitted from the line, the signal is set to NG. Unless a valid cell is received as a normal test cell, the TSOK is set to NG.

[3159] If the LP (LP-COM, SMLP, and RMLP) makes a self-diagnosis (“OUS” state during the diagnosis), all cells in the line are masked to “disable” to multiplex only the test cells from the HLP02A. The designation of the LP unit self-diagnosis is set by the MSD in the HMH03A. FIG. 240 shows the outline of the descriptions above.

[3160] (3) CRC-10 Check S

[3161] A CRC division is performed on the payload of a cell to check the existence of an error. EFCC is set to L when the CRC polynomial indicates a value other than 0 (L2 payload CRC violation).

[3162] A process object is a cell having a test bit 1 of the 02nd word (inter-MESH PVC test cell), and is masked with an error edit IS. The EFIRM is set to L to indicate that the L2 header is NG. FIG. 241 is a table showing this correspondence.

[3163] (4) PL Length Check S

[3164] The valid payload length of a cell is checked (for each segment type).

[3165] When the table of FIG. 242 is used, the EFPL is set to L. The cell (L2 payload length error) having the test bit 1 of the 02nd word (inter-MESH PVC test cell) is not an object cell. If a check is made on an inter-MESH PVC test cell, a check is actually made and the check result is masked with an error edit IS. The EFIRM is set to L to indicate that the L2 header is NG.

[3166] (5) MID Value Check S

[3167] If an error is detected in a BOM, EOM, or SSM, the EFIM of the E2 is set to L. If an error is detected in a COM, the KEFIM of the E1 is set to L (BOM/SSM/with invalid MID error).

[3168] Since a cell having a test bit 1 of the 02nd word (inter-MESH PVC test cell) is not a process object, it is masked with an error edit IS. The EFIRM is set to L to indicate that the L2 header is NG. FIG. 243 shows the error condition in the above described test.

[3169] (6) MID Check S

[3170] A check is made on a BOM whether or not the VCI/MID indicates “not active”, while a check is made on a COM and EOM whether or not the VCI/MID indicates “active”.

[3171] The VCI/MID is read from the memory using the VCI/MID as the address (key) at the arrival of the BOM.

[3172] 1. If it is used (‘1’), an error flag (the EFMA of the EF2) is set (MID currently active) and the preceding message is erroneous. Accordingly, the master flag (EFMS) is held.

[3173] 2. If it is not used (‘0’), it is accepted.

[3174] 3. “Used” (‘1’) is written to the memory.

[3175] The VCI/MID is read as an address from the memory at the arrival of the COM.

[3176] 1. If it is not used (‘0’), an error flag (the EFMA of the EF1) is set.

[3177] 2. If it is used (‘1’), it is accepted.

[3178] 3. If it is in the state of 1. above, “no used” (‘0’) is written to the memory. If it is in the state of 2. above, “used” (‘1’) is written to the memory.

[3179] The VCI/MID is read as an address from the memory at the arrival of the EOM.

[3180] 1. If it is not used (‘0’), an error flag (the EFMA of the EF2) is set (EOM with unapproved MID).

[3181] 2. If it is used (‘1’), it is accepted.

[3182] 3. “No used” (‘0’) is written to the memory.

[3183] The SSM is not a process object.

[3184] 1. The test bit of the 02nd word in a cell indicates “1” (inter-MESH PVC test cell).

[3185] 2. Error in a CRC-10 check, PL length check, and MID value check.

[3186] 3. The ENB of the line cell is DSB (invalid).

[3187] If a cell satisfies any of the conditions of 1, 2, or 3 above, the memory is not accessed for the cell. If a cell satisfies the conditions of 1. above, its error flag is set to the value indicating OK. FIG. 244 shows the MID check.

[3188] (7) SN Check S

[3189] The sequence number (SN) is initialized in the BON and SSM, and the sequence of the SN is checked in the COM and EOM.

[3190] The VCI/MID is read from the memory using the VCI/MID as the address (key) at the arrival of the BOM and SSM.

[3191] 1. No error flag (EFSN) is set regardless of the matching between the SN and the read value.

[3192] 2. The value of the SN+1 is written to the memory using the VCI/MID as the address.

[3193] The VCI/MID is read from the memory using the VCI/MID as the address at the arrival of the COM and EOM.

[3194] 1. If the SN and the read value match each other, it is accepted and no error flag (EFSN) is set.

[3195] 2. Unless the SN and the read value match each other, it is rejected and an error flag (EFSN) is set.

[3196] 3. The value of the SN+1 is written to the memory using the VCI/MID as an address.

[3197] 1. The test bit of the 02nd word of the cell indicates 1 (inter-MESH PVC test cell).

[3198] 2. The MID indicates “not active”.

[3199] 3. The ENB of the line cell indicates DSB (invalid).

[3200] If a cell satisfies any of the conditions of 1, 2, or 3 above, the memory is not accessed for the cell.

[3201] If the EFRM indicates the NG (an error in CRC-10 check, PL length check, or MID value check), the memory is not accessed for the cell.

[3202] The error flag (EF2MA and EF1MA) of the cell satisfying the 1. above is masked with an error edit IS.

[3203] FIG. 245 shows the summary of the above described SN check.

[3204] (8) Address Format Check S

[3205] A format check is made on the SA and DA of the header of the SIP.

[3206] If the 4 bits indicating the address type in the SA and DA address fields satisfy the conditions shown in FIG. 246, it indicates an error. If the test bit of the 02nd word of the cell indicates 1 (inter-MESH PVC test cell), the cell is not a process object and masked with an error edit IS.

[3207] (9) DA Check S

[3208] An internal loopback cell is turned back.

[3209] The DA is received at the CAM as an address at the arrival of the BOM and SSM.

[3210] 1. When a non-matching result is output;

[3211] The 15th bit of the 02nd word of a cell indicates 0 (route retrieval is required in a routing process).

[3212] 2. When a matching result is output;

[3213] An error flag (EFSA) is set if the matching address is equal to the SNI ID.

[3214] The COM and CEO are not process objects.

[3215] If the test bit of the 02nd word of a cell indicates 1 (inter-MESH PVC test cell), it is not a process object and is masked with an error edit IS.

[3216] Although the group address is not a check object, a non-matching result is output for the CAM.

[3217] FIG. 247 shows the summary of the above described DA check.

[3218] (10) BA Size Check S

[3219] It is checked whether or not the size of the BA of the SIP L# (L3-PDU) is correct.

[3220] When an error is indicated, the EFBA is set to L. If the test bit of the 02nd word of a cell indicates 1 (inter-MESH PVC test cell), it is not a process object and is masked with an error edit IS. FIG. 248 shows the error conditions of the BA size check.

[3221] (11) Ingress Flow Check S

[3222] The access class is divided into 5 levels for the DS3 class of each SNI, and it is checked whether or not the limited speed is observed. The number of octets is incremented for each class from the leaky packet (9192 oct) of a fixed capacity for each subscriber. It is checked whether or not a BAsize is acceptable for the leaky packet at the arrival of the BOM and SSM.

[3223] At every 32th cell frame (SNI #0 through #31), a predetermined number of octets are incremented from a leaky packet of each SNI (an increment process for each subscriber).

[3224] After the increment process is performed on a single SNI in a single cell frame, it is determined whether or not the BAsize is acceptable for the SNI corresponding to an arrived BOM.

[3225] No increment flow check is required for the access class word 0 and 5 (0 indicates DS1, while 5 indicates DS3). However, the increment process can be performed by setting the number of the increment octets to all 1.

[3226] The firmware sets the number of increment octets for each SNI and buffer capacity (9192: predetermined value).

[3227] A practical process is performed as follows.

[3228] 1. Increment process (a process of each subscriber is performed for each cell frame.

[3229] The number of increment octets is read from the increment octet number memory using the SNI ID (SNI number) as an address (key).

[3230] The read value and the number of increment octet number are added up after reading the buffer capacity from the leaky packet memory using the SNI ID as an address.

[3231] If the sum is larger than 9192, it is written to the leaky packet memory as the buffer capacity of 9192. If it is equal to or smaller than 9192, it is written to the leaky packet memory.

[3232] 2. Data is read from the leaky packet memory using the SNI ID as an address upon receipt of the BOM and SSM, and the BAsize of 32 is subtracted from the read value. If the difference is larger than 0, it is written to the leaky packet memory. If the difference is equal to or smaller than 0, the buffer capacity read from the leaky packet memory is written to the memory as is (without subtraction) and an EF2AC is set.

[3233] 1. The COM and EOM are not process objects.

[3234] 2. The test bit of the 02nd word of a cell is 1 (inter-MESH PVC test cell).

[3235] 3. If the EFIRM indicates L (error in CRC, PL length, or MID value) or the BAsize check outputs an error, then they are not process objects.

[3236] 4. The ENB of the line system cell indicates DSB (invalid).

[3237] If a cell satisfies the condition of any of the above described 1., 2., 3., and 4, the memory is not accessed for the cell. An error flag (EF2AC) of the cell satisfying the condition of 2. above is masked with an error edit IS.

[3238] FIG. 249 shows the above described ingress flow check.

[3239] (12) Error Edit IS

[3240] As error checked by each checker is assigned to each position of the error flag.

[3241] If a flag is set as an error flag EF2, the flag of the EFMS of the EF1 is set. However, the EFMS is not set even if the error is indicated by the EF2MA.

[3242] The 2-bit segment type (ST) and the 10-bit message identifier (MID) are copied to the 00-th word of the cell. The received VCI (the 8 lower bits of the SNI number (SNI ID) is given) is copied to the 01-th word of the cell.

[3243] If the test bit of the 02nd word of a cell indicates 1 (inter-MESH PVC test cell), the error flag of the cell is masked.

[3244] (13) Simultaneous Input Number Check S

[3245] The number of messages simultaneously receivable for each SNI is restricted. If the number of arriving messages exceeds the restriction number (1 or 16), the arriving messages are discarded.

[3246] At the initialization for the restriction number (1 or 16), 0 or 1 (0 indicates the restriction number of 1; and 1 indicates the restriction number of 16) is set in the simultaneous input restriction number memory.

[3247] Process at the arrival of the BOM

[3248] 1. When the number of received messages≠16 (or ≠1) for the SNI (in a normal operation);

[3249] The RMID is read from the RMID management table using a next read counter+SNI ID as an address (key). (The RMID is, as described later, a value obtained by combining the MID and the SNI number, and is uniquely assigned to an SNI and each MID in the SNI).

[3250] The VCI+MID is written to the RMID conversion CAM using the RMID as an address.

[3251] The RMID is written to the 03-th word (LSB 10 bits) of a cell.

[3252] The number of received messages (0 through 16) is incremented (+1).

[3253] If the restriction number is 16 (determined by the value in the simultaneous input restriction number memory), the next read counter (0 through 15) is incremented (+1).

[3254] 2. When the number of received messages=16 (or 1) for the SNI, an error flag (E2EM and EIMS) is set.

[3255] Process at the arrival of the SSMS

[3256] 1. When the number of received messages≠16 (or ≠1) for the SNI (in a normal operation);

[3257] The RMID is read from the RMID management table using a next read counter+SNI ID as an address.

[3258] The RMID is written to the RMID management table using the next write counter+SNI ID as an address.

[3259] The RMID is written to the 03-th word (LSB 10 bits) of a cell.

[3260] If the restriction number is 16 (determined by the value in the simultaneous input restriction number memory), the next read counter (0 through 15) and the next write counter are incremented (+1).

[3261] 2. When the number of received messages=16 (or 1) for the SNI, an error flag (E2EM and EIMS) is set.

[3262] At the arrival of the COM, a matching process is performed using the VCI/MID as a matching address in the RMID converting CAM.

[3263] 1. When a matching result is output;

[3264] The RMID is written to the third word (LSB 10 bits) of a cell using the RMID as the matching address.

[3265] 2. When a non-matching result is output;

[3266] An error flag (E1RM or E1MS) is set.

[3267] At the arrival of the EOM, a matching process is performed using the VCI/MID as a matching address in the RMID converting CAM.

[3268] 1. When a matching result is output;

[3269] The RMID is used as a matching address.

[3270] The RMID is written to the third word (LSB 10 bits) of a cell.

[3271] The RMID is written to the RMID management table using the next write counter+SNI ID as an address.

[3272] The number of received messages (0 through 16) is decremented (−1).

[3273] If the restriction number of 16, the next write counter (0 through 15) is incremented (+1).

[3274] 2. When a non-matching result is output;

[3275] An error flag (E1RM or ElMS) is set.

[3276] The determination as to whether or not a timeout cell (EOM) is issued is made by checking whether or not the master (MS) error assignment memory (1 bit) of the error discard unit indicates 1. If the timeout cell has been issued, the error discard process invalidates the EOM cell.

[3277] No process is performed on the inter-MESH PVC test cell (test bit is 1), but an error cell (EFLMS indicates 1) is processed appropriately.

[3278] FIG. 250 shows the above described simultaneous input number check.

[3279] (14) MRI Timeout S

[3280] The time from the reception of the BOM to the reception of the EOM is monitored, and the MRI timeout is determined.

[3281] An MRI timeout message is detected by entering time in the CAM each time a cell arrives (including an idle cell).

[3282] 1. A matching process is performed for each cell frame at the MRI time CAM using the “used(0)+1+current time” as matching data (process for each cell frame).

[3283] I. When a matching result is output;

[3284] 1. A timeout cell (refer to the following NOTE 1) is generated for an idle cell, and all 1 is written to the RMID conversion CAM and the MRI time CAM.

[3285] 2. “Used(0)+1+all 1” is written to the MRI time CAM using the matching address as an address for a cell other than an idle cell (BOM, COM, EOM, and SSM).

[3286] II. No process is performed when a non-matching result is output.

[3287] 2. After performing a process for each cell frame, the following processes are performed for each cell.

[3288] For an idle cell;

[3289] I. When a matching result is output for the MRI time CAM in the process for each cell frame, the process described in 1-1 above is performed.

[3290] II. If a non-matching result is output for the MRI time CAM in the process for each cell frame, a matching process is performed for the MRI time CAM using the “used(0)+0+all 1” as matching data.

[3291] 1. When a matching result is output, a timeout cell (refer to NOTE 1) is generated and all 1 is written to the RMID conversion CAM and the time CAM as a matching address.

[3292] 2. When a non-matching result is output, no process is performed.

[3293] NOTE 1: An EOM cell (input VCI and input MID are written) having an error flag (E2MT) as a timeout cell is generated. The VCI+MID are read from the RMID conversion CAM using the matching address RMID as an address of the input VCI and MID.

[3294] At this time, in the simultaneous input number check S process described in (13) above, the following process is performed. That is, the matching address RMID is written to the RMID management table using the next write counter+SNI ID (VCI) as an address. Then, the number of received messages (0 through 16) for the SNI ID is decremented (−1). If the restriction number is 16, the next write counter (0 through 15) for the SNI ID is incremented (+1).

[3295] When the BOM is received;

[3296] “Used(0)+1+[timeout point (present time+T)]” is written to the MRI time CAM using the RMID as an address. (For example, T=2.7 μs/cell×64k (16 bit)≠177 ms)

[3297] When the EOM is received;

[3298] 1. “All 1” is written to the RMID conversion CAM and MRI time CAM using the RMID as an address if a matching result is output for the RMID conversion CAM described in (13) above.

[3299] 2. No MRI timeout process is performed if aanon-matching result is output for the RMID conversion CAM described in (13) above.

[3300] No MRI timeout S process is performed on the COM/SSM.

[3301] No process is performed on the inter-MESH PVC test cell (test bit is 1).

[3302] An error cell (EFIMS is 1) is processed appropriately.

[3303] The above listed MRI timeout processes are shown in the drawings. FIG. 251 shows the calculation of the MRI Time. FIG. 252 shows the RMID conversion CAM and the read/write data to the MRI CAM. FIG. 253 shows the timing of each cell. FIG. 254 is a flowchart showing the simultaneous input number restriction RMID acquisition/MRI timeout process.

[3304] Described below is the supplementary explanation of the simultaneous input check S, MRI timeout S, (and RMID acquisition).

[3305] RMID

[3306] Considering the necessary process capacity in the SMLP, up to 32 subscribers (SNI) can be accommodated in one SMLP, and up to 16 simultaneous input restriction number of the L3-PDU is acceptable in one SNI. Therefore, up to 512 L3-PDU can be present simultaneously (32SNI×16 L3-PDU=512).

[3307] The RMID is a management number uniquely assigned to the 512 L3-PDU in the SMLP and consists of a VCI and MID. Using the RMID, an address of each type of table can be degenerated from the 32 VCI×1024 MID=32 kilobits to the RMID of 512 bits, thereby successfully saving the table capacity. FIG. 255 shows the above described degeneration.

[3308] The RMID is acquired (set on the RMID conversion table) at the following points.

[3309] When a normal BOM is received.

[3310] When a normal SSM is received (in the case of the SSM, data is not set on the RMID conversion table even if the RMID is acquired).

[3311] The RMID is released (the RMID conversion table is cleared) in the following cases.

[3312] When a normal EOM is received.

[3313] When an MRI T.O. EOM is received (transmission of the EOM at the MRI timeout)

[3314] When a normal SSM is received (in the case of the SSM, data is not set on the RMID conversion table, and the release process is not required).

[3315] When the RMID is acquired at the reception of an erroneous BOM, COM, or EOM.

[3316] The COM/EOM is assigned the RMID after the already acquired RMID is read from the RMID conversion table based on the VCI+MID.

[3317] FIG. 256 shows processes on normal and abnormal cells in the RMID acquisition unit, simultaneous input restriction, and the MRI T.O. set/releases.

[3318] 1) When the input MID is not fixed;

[3319] The RM refers to an EFlRM and indicates that an NG has been detected in the following checks if the RM is set ON at the entry.

[3320] CRC-10

[3321] PL length

[3322] MID check

[3323] If the result of any of the above listed checks indicates an NG, then the MID value may not be correct and the RMID acquifing unit (including simultaneous input restriction and the MRI timeout check) performs no processes.

[3324] In the following blocks, data is read from or written to the memory using the RMID as an address. The RMID acquiring unit transmits the input MID as an RMID when the RM is set ON and no RMID is received. In this case, the data written using a correct RMID as an address can be destroyed. To prevent this, the RMID value should be 11 1111 1111 if no RMID is acquired (or assigned) and an unused address of the memory is accessed.

[3325] Error discard unit S

[3326] Routing information S

[3327] GA copy S

[3328] VC-SH transmission OK S

[3329] The similar problem may occur in the following blocks. To avoid the problem, no process is performed when the RM is set ON. Normally, if the RMID value is 11 1111 1111, an unused address in the memory should be accessed. The RM can be used without problem, but conformity is also expected.

[3330] BAsize matching, BEtag matching, Length check, output MID acquisition

[3331] Others

[3332] If the BOM indicates “RM ON”, and the COM and EOM in the same L3-PDU indicate “RM OFF”, then the input MID of the BOM may not be correct and the processes are performed on the COM and EOM as if no BOM were entered.

[3333] If the RM is set ON for the EOM, the input MID may not be correct and the RMID or MRI T.O. are not released or cleared. Accordingly, the RMI timeout occurs.

[3334] 2) When a master error NG is detected (RM indicates OFF);

[3335] If an input message indicates a master error NG (EFLMS ON), it is checked on the BOM/COM/EOM/SSM whether or not the RMID as well as the message indicating the OK has been acquired in the input VCI+MID.

[3336] If it has been acquired, the acquired RMID (matching address in the RMID CAM) is assigned as an RMID. Since the MS is set ON, the process of the L3-PDU should be stopped and the RMID is then released and the MRI T.O is cleared.

[3337] If no RMID has been acquired, the RMID is set to 11 1111 1111 and the EFLRM is set ON.

[3338] 3) When OK is received;

[3339] When an OK message is received, it is checked on the BOM/COM/EOM/SSM whether or not the RMID has been acquired.

[3340] If it has been acquired;

[3341] 1. For the BOM: An RMID is assigned to set an MRI T.O. again.

[3342] 2. For the COM: An RMID is assigned (in a normal state).

[3343] 3. For the EOM: After an RMID is assigned, it is released immediately and the MRI T.O. is cleared (in a normal state).

[3344] 4. For the SSM: After an RMID is assigned, it is released immediately and the MRI T.O. is cleared.

[3345] If the RMID has not been acquired;

[3346] 1. For the BOM: An RMID is acquired to set an MRI T.O. (in a normal state).

[3347] 2. For the COM: An RMID is set to 11 1111 1111 and the MS and RM are set ON.

[3348] 3. For the EOM: An RMID is set to 11 1111 1111 and the MS and RM are set ON.

[3349] 4. For the SSM: After an RMID is assigned, it is released immediately (in a normal state).

[3350] 4) When a simultaneous input restriction NG is received;

[3351] A simultaneous input restriction is checked in this block.

[3352] When a BOM/SSM is received, it is set on the simultaneous input restriction table by the firmware. The simultaneous input restriction number (when the restriction number is 1, 0 is set on the table; when the restriction number is 16, 1 is set on the table) is compared with the number of the L3-PDU (the number of received messages) which has received a BOM but not an EOM (no MRI T.O. has occurred). If a matching result is output, an error flag MS and an EM are set ON. At this time, the RMID is set to 11 1111 1111. The RMID is not acquired and the RMI T.O. is not set.

[3353] The number of received messages is counted at the BOM only when the RMID is newly acquired.

[3354] The number of received messages is counted in the following cases.

[3355] When the process normally terminates at the EOM;

[3356] When a timeout EOM is transmitted; and

[3357] When the RM is set OFF, the MS is set ON, and the RMID is acquired at the BOM/COM/EOM.

[3358] 5) When an MRI timeout check is made;

[3359] An MRI timeout check is made in this block.

[3360] The MRI timout check is monitored for each cell regardless of the validity of a received cell. If timeout is detected, the timeout pattern is set on the MRI T.O. table using the corresponding RMID as an address.

[3361] If the cell is invalid, the MRI T.O. table is checked for the existence of a timeout pattern. If a timeout pattern is detected, the VCI+MID read from the RMID conversion table and the RMID are assigned to the T.O. EOM (timeout EOM) and transmitted. At this time, the error flag sets the MS and MT to ON. After the T.O. EOM has been transmitted, the RMID is released and the MRI T.O is cleared. The timeout point of the MRI T.O table is set at the BOM when the RMID is newly set or set again.

[3362] The timeout point of the MRI T.O. table is cleared in the following cases.

[3363] When the process normally terminates at the EOM;

[3364] When a timeout EOM is transmitted; and

[3365] When the RM is set OFF, the MS is set ON, and the RMID is acquired at the BOM/COM/EOM.

[3366] 6) Processing a PVC (between MESH and MH)

[3367] No RMID acquisition, simultaneous input restriction, or MRI T.O. process is performed on a PVC test cell between the MESH and MH. The data of an input cell is output as is together with the area of the RMID and an error flag.

[3368] (15) Hel Check S

[3369] It is checked whether or not the header extension length is set to 3. If the value is other than 3, the EFHE is set to L.

[3370] If the test bit of the 02nd word of a cell is 1 (inter-MESH PVC test cell), the cell is not a process object.

[3371] (16) HE Format Check S

[3372] It is checked whether or not the first 3 octets (first element) of a header extension is set to 3 (element length), 0 (element type), and 1 (element value). If it is set to different values, the EFVE is set to L.

[3373] If the element type represented by the second octet in the second element (next 3 octets) of the header extension indicates 1, then the element length represented by the first octet is checked. If it indicates a value other than 4, 6, or 8, the EFCS is set to L.

[3374] If the test bit of the 02nd word of a cell is 1 (inter-MESH PVC test cell), the cell is not a process object.

[3375] FIG. 257 is a table showing the summary of the above described HE format check.

[3376] (17) SA Check S

[3377] It is checked whether or not the SA stored in the input cell is that entered in the transmission SNI.

[3378] The SA is input to the CAM at the arrival of the BOM and SSM.

[3379] Unless a matching result is output, an error flag (EFSA) is set.

[3380] If a matching result is output, an error flag (EFSA) is set only when the matching address is other than the SNI ID.

[3381] If a matching result is output, no process is performed when the result equals the SNI ID.

[3382] The COM and EOM are not check-objects.

[3383] If the test bit of the 02nd word of a cell is 1 (inter-MESH PVC test cell), the cell is not a process object.

[3384] FIG. 258 is a table showing the summary of the above described SA check.

[3385] (18) DA Screening S

[3386] A sending restriction is placed on a destination SNI.

[3387] Process at the arrival of the BOM and SSM

[3388] 1. It is determined whether the AT (address type) indicates an individual address (IA) or a group address (GA), and reads from the SC attribute memory the attribute to the AT (IA or GA).

[3389] 2. A matching process is performed at the DA screening CAM using the DA as matching data.

[3390] Refer to FIG. 259 showing the SC attribute and the matching state. If it indicates an error, an error flag is set to L.

[3391] The COM and EOM are not process objects.

[3392] If the test bit of the 02nd word of a cell is 1 (inter-MESH PVC test cell), the cell is not a process object.

[3393] (19) BEtag Match S

[3394] It is checked whether or not the BE tags stored in the header of the SIP (L3-PDU) and the trailer match each other.

[3395] If the BEtag of the SIP L3-PDU stored in the payload field of the BOM is stored and the EOM is received, then the stored BEtag is compared with the BEtag stored in the EOM. If they are different from each other, the EFBE is set to L.

[3396] If the test bit of the 02nd word of a cell is 1 (inter-MESH PVC test cell), the cell is not a process object.

[3397] FIG. 260 is a table showing the summary of the above described BE tag.

[3398] (20) BAsize Matching Check S

[3399] It is checked whether or not the BAsize stored in the header field of the SIP (L3-PDU) and the length value stored in the trailer match each other.

[3400] If the BAsize stored in the payload field of the BOM is stored and the EOM is received, then the stored BAsize is compared with the length stored in the EOM. If they are different from each other, the EFLE is set to L.

[3401] If the test bit of the 02nd word of a cell is 1 (inter-MESH PVC test cell), the cell is not a process object.

[3402] FIG. 261 is a table showing the summary of the above described BAsize match check.

[3403] (21) Information Length Check S

[3404] It is checked whether or not the BAsize and the information length of a received L3-PDU match each other.

[3405] Process at the arrival of the BOM

[3406] The number of the necessary cells and the length of the information (PL length) contained in the last cell (EOM) are calculated. The calculation is made according to the equation BAsize+40 oct=quotient+remainder, thereby obtaining a quotient=cell count value and the PL length of the EOM=remainder+40 oct.

[3407] The calculation result is written to the cell count memory and the PL length memory using the RMID as an address (key).

[3408] At the arrival of the COM, a value is read from the cell count memory using the RMID as an address.

[3409] 1. If the read value is 0, an error flag (EFIL) is set.

[3410] 2. If the read value is not 0, the read value is incremented and written to the cell count memory.

[3411] At the arrival of the EOM, a value is read from the cell count memory using the RMID as an address.

[3412] 1. If the read value is not 0, an error flag (EFIL) is set.

[3413] 2. If the read value is 0, a value is read from the PL length memory is read using the RMID as an address.

[3414] The read value is compared with the actual payload length of the EOM. If they are different, an error flag (EFIL) is set.

[3415] If the test bit of the 02nd word of a cell is 1 (inter-MESH PVC test cell), the cell is not a process object.

[3416] FIG. 262 is a table showing the summary of the above described information length check.

[3417] (22) Error Edit II S

[3418] An error checked by each checker is assigned to each position of the error flag.

[3419] If the flag is set at error flag E2, a flag EFMS is set.

[3420] (23) Errorred L3-PDU Control and Encapsulation S

[3421] (1) Errorred L3-PDU control

[3422] The following two processes are performed in this block.

[3423] 1. Discard of Error Message in L3-PDU Units

[3424] When a BON or COM having a master error (EFMS) set ON is received, the master error is set ON in this block for the COM and EOM having the same SNI/MID value received subsequently even if the L2-PDU is normal. FIG. 263 shows the discard of the error message of the above described L3-PDU.

[3425] 2. Discard of Messages Received After the MRI Timeout EOM (reception of pseudo EOM)

[3426] If the MRI timeout is detected, a pseudo EOM is generated at the MRI timeout unit of the HMH04A and then transmitted. In the blocks after the MRI timeout unit, the L3-PDU termination process is performed based on the pseudo EOM. The cells received after the pseudo EOM are processed as follows.

[3427] COM: A master flag (MS-FILAG) is set ON, and subsequent cells are processed as error cells.

[3428] EOM: Discarded as an invalid cell. At this time, a signal is output to count the number of discarded cells.

[3429] FIG. 264 shows the discard of the message received after the above described MRI timeout EOM.

[3430] A master error flag is set for the message of an error cell (for which a master error flag is set) in the process 1 above.

[3431] If a cell is an error cell at the arrival of the BOM, the master error information (hereinafter referred to as an MS) is written to the error memory using the test bit+input VCI+input MID as an address (key), and the timeout information (hereinafter referred to as a DM) is initialized.

[3432] If it is not an error cell, the MS and DM at the corresponding address are initialized (refer to 1 and 2 shown in FIG. 265).

[3433] The MS and DM are read from the memory using the test bit+input VCI+input MID as an address at the arrival of the COM (refer to 3 through 7 in FIG. 265).

[3434] I. If the MS of the read value is erroneous, a master error flag is set for the arriving cell (refer to 4 in FIG. 265).

[3435] II. If the DM of the read value is erroneous, a master error flag is set for the arriving cell (refer to 5 in FIG. 265).

[3436] III. If the arriving cell is erroneous, the MS is written to the corresponding address (refer to 6 and 7 in FIG. 265).

[3437] The MS and DM are read from the error memory using the test bit+input VCI+input MID as an address at the arrival of the EOM (refer to 8 through 10 in FIG. 265).

[3438] I. If no error is detected in the MS and DM of the read values, the DM is written to the corresponding address (refer to 8 in FIG. 265).

[3439] II. If the MS of the read value is erroneous, a master error flag is set for the arriving cell, and the DM is written to the corresponding address (refer to 9 in FIG. 265).

[3440] III. If the DM of the read value is erroneous, the cell is invalidated (refer to 10 shown in FIG. 265).

[3441] (2) Encapsulation

[3442] In the process 2 above, the SIP L3-PDU is converted into the Inter-MH inf. PDU (inter-message-handler interface protocol data unit)(the SIP BOM cell is copied to generate an Inter-MH BOM cell).

[3443] An erroneous cell (marked with a master flag) is not a process object.

[3444] A cell is buffered at the arrival of the BOM and SSM.

[3445] The arriving BOM and SSM are copied to generate an encapsulated BOM (inter-MH inf BOM) (an ISSI header [ES: explicit selection] and a carrier are assigned). The encapsulated BOM cell is then transmitted.

[3446] The arriving BOM is transmitted when an idle cell is detected with the segment type (ST) assigned to the COM.

[3447] The arriving SSM is transmitted when an idle cell is detected with the segment type (ST) assigned to the EOM.

[3448] At the arrival of the COM and EOM;

[3449] I. If the corresponding cell (determined by the RMID) is stored in the buffer, the cell in the buffer is transmitted first (to prevent: the rearrangement of the sequence of cells for the message).

[3450] II. Unless the corresponding cell (determined by the RMID) is stored in the buffer, the cell is transmitted.

[3451] If the cell cannot be written to the buffer;

[3452] 1. The cell is discarded (as an invalid cell).

[3453] 2. To count the number of discarded cells, a discard signal is provided for the HMH06A in synchronism with the cell frame (indicating that one cell is discarded in one cell frame).

[3454] FIG. 266 is a table showing the summary of the above described encapsulation. FIG. 267 is a table showing the ISSI header to be assigned to the inter-MH INF BOM. FIG. 268 shows the cell format of the inter-MH inf BOM.

[3455] (24) Carrier Selection S

[3456] At the arrival of the BOM and SSM;

[3457] 1. If no carrier selection is detected in the second element of the header extension, the explicit selection bit of the ISSI header is set to 0.

[3458] The carrier ID is read from the memory using the SNI ID as an address.

[3459] The read carrier ID is written to the carrier area of the ISSI header.

[3460] 2. When a carrier selection is detected in the second element of the header extension, the explicit selection bit of the ISSI header is set to 1.

[3461] The carrier ID of the header extension is written to the carrier area of the ISSI header.

[3462] 3. An erroneous cell (marked with a master flag) is not a process object.

[3463] The COM and EOM are not process objects.

[3464] FIG. 269 shows the above described carrier selection.

[3465] (25) Routing S

[3466] The route information is retrieved and assigned an output VCI (destination MHID).

[3467] At the arrival of the BOM;

[3468] I. For a group address (GA) (when the address type of the DA is GA (1110)), a broadcast is performed to all SBMH/GWMH in the station.

[3469] 1. A broadcast is specified for the BC area of the 02nd word of the cell. All 0 is written to the VCI area.

[3470] 2. The BC of the 02nd word of the cell and the output VCI are written to the routing information memory using the RMID as an address.

[3471] II. For an individual address (IA) (when the address type of the DA is IA (1100), data is simultaneously read from the intra-station, intra-station number, and inter-station number tables using the DA as matching data. The matching priority is set in the order of the intra-station, intra-station number, and inter-station number tables.

[3472] 1. An SBMH designation VCI is assigned when a matching result is output in the intra-station routing table. The output VCI is read from the intra-station phone number VCI assignment table using the matching address as an address, and is written to the VCI area of the 02nd word of the cell. A broadcast is designated for the BC area.

[3473] The BC and the output VCI of the 02nd word of the cell are written to the routing information memory using the RMID as an address.

[3474] The ISSI carrier area is set to all 0.

[3475] 2. When a matching result is output on the intra-station phone number table, the data is broadcast to all SBMHs.

[3476] A broadcast is specified for the BC area of the 02nd word of the cell. All 0 is written to the VCI area.

[3477] The BC of the 02nd word of the cell and the output VCI are written to the routing information memory using the RMID as an address.

[3478] The ISSI carrier area is set to all 0.

[3479] 3. An GWMH designation VCI is assigned when a matching result is output in the inter-station routing table.

[3480] The output VCI is read from the inter-station phone number VCI assignment table using the matching address as an address, and is written to the VCI area of the 02nd word of the cell. A broadcast is designated for the BC area.

[3481] The BC of the 02nd word of the cell and the output VCI are written to the routing information memory using the RMID as an address.

[3482] 4. Unless a non-matching result is output on the three routing tables, the data is broadcast to all GWMHs in the LATA.

[3483] A broadcast is specified for the BC area of the 02nd word of the cell. All 0 is written to the VCI area.

[3484] The BC of the 02nd word of the cell and the output VCI are written to the routing information memory using the RMID as an address.

[3485] For the COM and EOM, the route information is read from the routing information memory using the RMID as an address and written to the BC area and the VCI area of the 02nd word of the cell.

[3486] FIG. 270 is a table showing the summary of the above described routing process. FIG. 271 is a block diagram showing the above described routing process.

[3487] (26) Carrier Screening S

[3488] A sending restriction is placed on the carrier specified by each SMI.

[3489] At the arrival of the BOM and SSM, a matching process is performed on the SMI ID+carrier of the ISSI header as data by the carrier screening CAM. If a matching result is output, the ISSI carrier area is cleared (all ‘0’) and an error flag (EFEB) is set. FIG. 272 shows the above described carrier cleaning and the state of the carrier.

[3490] (27) GA Copy S

[3491] Cells of the number of the implemented MHs are copied and an output VCI is assigned to transmit a broadcast cell to an implemented MH.

[3492] When a cell arrives, the BC area (12th and 13th bits) of the 02nd word of the cell is checked and a transfer destination MH is determined according to the conditions shown in FIG. 273.

[3493] Process performed when the EBOM arrives

[3494] 1. When there is a space area in the buffer (buffer≠full)

[3495] I 0 is written to the FIFO write NG memory, and the cell is written to the buffer.

[3496] II The cell is read from the buffer and written to the copy memory with the BC area specified. III An output VCI is assigned and 0 is written to the CP area and then the cell is transmitted. It is transmitted without performing any process if the BC area is 00.

[3497] IV If 1 is set in the BC area (in either of the two bits), reading a cell from the buffer is stopped. The MH ID corresponds to the address of the implemented/unimplemented memory (addresses 00 through to the SBMH and addresses 40 through 5F to the GWMH). Data is read from the copy memory (copying cells) and an output VCI is assigned in the address order.

[3498] V When cells are copied, 1 is written to the CP area.

[3499] 2. When the buffer contains no space area (buffer=full);

[3500] I The cell is discarded (as an invalid cell).

[3501] II The number of discarded cells is counted (written to the dual port RAM directly connected to the μ-P bus).

[3502] III 1 is written to the FIFO write NG memory.

[3503] Process performed when the COM/EOM arrives

[3504] 1. When the buffer contains Ea space area (buffer≠full);

[3505] I Data is read from the FIFO write NG memory.

[3506] If the read data indicates 0, the cell is written to the buffer.

[3507] II Cells are retrieved from the buffer and written to the copy memory with the BC area specified.

[3508] III An output VCI is assigned and transmitted with 0 written to the CP area. If the BC area indicates 00, the cell is transmitted with no process performed.

[3509] IV If the BC area indicates 1 (in either of the two bits), reading a cell from the buffer is stopped. The MH ID corresponds to the address of the implemented/unimplemented memory (addresses 00 through 1F to the SBMH and addresses 40 through 5F to the GWMH). Data is read from the copy memory (copying cells) and an output VCI is assigned in the address order.

[3510] V When cells are copied, 1 is written to the CP area.

[3511] 2. When the buffer contains no space area (buffer=full) and the FIFO write NG memory is 1;

[3512] I The cell is discarded (as an invalid cell).

[3513] II The number of discarded cells is counted (written to the dual port RAM directly connected to the μ-P bus).

[3514] III 1 is written to the FIFO write NG memory.

[3515] Process when an error cell is set (setting a master error flag)

[3516] 1. When the BC area indicates 00, the cell is transmitted with no process performed.

[3517] 2. When the BC area is set to a (in either of the two bits);

[3518] An output VCI is assigned and the cell is transmitted without any process if the cells after the BOM are error cells.

[3519] If the cells after the COM/EOM are erroneous cells, 1 is written to the CV area only in the first error cell having the same error message and a normal copying operation is performed. For the second and subsequent error cells, 0 is written to the CV area and an output VCI is assigned. The cell is transmitted with no other processes performed.

[3520] FIG. 274 shows the GA copying operation. FIG. 275 shows the cell format after the broadcast. FIG. 276 is a flowchart of the GA copy process.

[3521] (28) Restriction of the Output Band S

[3522] A restriction is placed on the output (peak rate) for each transmission MH (32 SBMH/32 GWMH).

[3523] The number of messages discarded due to the absence of space areas in the buffer is counted. FIG. 277 shows the above described output band restriction.

[3524] (29) Output MID Acquisition S

[3525] An MID (the same MID can be assigned to different message handler MHs) is assigned to each destination MH. Up to 256 MIDs can be provided for one MH ID. However, MESH #0 can be assigned 1-255; MESH #1 can be assigned 256-511; MESH #2 can be assigned 512-755; and MESH #3 can be assigned 756-1023. The MESHID is identified by the firmware.

[3526] Process performed when the BOM arrives

[3527] 1. When the number of possibly acquired MIDs for the MH ID is not 0 (next read counter ⊂ next write counter);

[3528] An MID is read from the MID management table using the next read counter+MH ID as an address.

[3529] The MID is written to the MID conversion memory using the MH ID+RMID of the cell as an address.

[3530] The read MID is written to the 3rd word of the cell (LSB 10 bits).

[3531] The next read counter (0 through 255) is incremented.

[3532] 1 is written to the flag (1 bit) of the MID conversion memory using the RMID+MH ID as an address.

[3533] 2. When the number of possibly acquired MIDs for the MH ID is 0 (next read counter=next write counter);

[3534] A master error flag (EIMS) and an error flag (E2MN) are set.

[3535] Process performed when a COM arrives

[3536] An MID+flag is read from the MID management memory using MH ID+RMID of the cell as an address.

[3537] 1. If the read flag value is 1, the read MID is written to the 3rd word (LSB 10 bits) of the cell.

[3538] 2. If the read flag value is 0, a master error flag (E1MS+E1MN) is set.

[3539] When the EOM arrives;

[3540] An MID+flag is read from the MID management memory using MH ID+RMID of the cell as an address.

[3541] 1. If the read flag value is 1, the read MID is written to the 3rd word (LSB 10 bits) of the cell.

[3542] The MID releasing operation is performed as follows.

[3543] The MID is written to the MID management table using the next write counter+MH ID as an address.

[3544] The next write counter (0 through 255) is incremented.

[3545] 2. If the read flag value is 0, a master error flag (E1MS+E1MN) is set.

[3546] An error cell (for which a master error flag (MS) is set) is not a process object.

[3547] However, if the MID conversion memory flag is 1 when the COM/EOM arrives, the MID releasing operation is performed.

[3548] FIG. 278 shows the above described output MID acquisition process. FIG. 279 is a flowchart showing the MID acquisition process.

[3549] (30) Discard Count S

[3550] The number of cells discarded at the VC-SH LSI is counted.

[3551] The number of messages discarded at the VC-SH LSI is counted.

[3552] The number of cells discarded at the GA copying unit is counted.

[3553] The number of cells discarded at the encapsulating unit is counted.

[3554] (31) SN Assignment S

[3555] A value obtained by subtracting 1 from the SN is assigned to the BOM.

[3556] No process is performed for Fhe COM and EOM.

[3557] (32) Error Cell Discard S

[3558] The master error (MS) of an error flag discards a rejected cell.

[3559] (33) VPI/VCI Assignment S

[3560] The 01st word (4 bits at MSB and 4 bits at LSB) is assigned 0(H) and the 02nd word (4 bits at MSB) is assigned 3(H).

[3561] (34) μ-P interface S[

[3562] Interfaces with the MNG μP from the HLP02A.

[3563] (35) Timing S

[3564] 9M clock and a cell frame are generated based on the 19M clock and cell frame received from the HLP02A.

[3565] Each block of the SMLP is described above in detail. FIGS. 280 and 281 show a list of SMLP tables.

4. RMLP

4.1. Outline of Process

[3566] A destination address (DA) in a message is referred to and a message only addressed to a subscriber accommodated in the present RMLP is filtered. Then, a route to the destination subscriber is retrieved and the VCI to the line to the destination is written to the cell header. The cell is then transmitted to the SW.

4.2. Configuration

[3567] FIG. 282 shows the entire configuration of the RMLP. FIGS. 283 and 284 show the outline of the functions of each clock shown in FIG. 282. (The item numbers correspond to the numbers 01 through 23 in the figure).

[3568] 4.2.1. PVC Test

[3569] FIGS. 285 through 287 show the route of the test cell processed in the PVC test. FIG. 285 shows the SNI loopback test; FIG. 286 shows the inter-MH (using a specific DA) test; and FIG. 287 shows the inter-MH (using an assigned DA) test.

[3570] 4.2.2. MSCN

[3571] FIG. 288 shows the MSCN of the RMLP.

[3572] 4.2.3. MSD

[3573] FIG. 289 shows the MSD of the RMLP.

[3574] 4.2.4. Correspondence between each Function Block and Error Flag

[3575] FIG. 290 is a table showing an error flag (FF) operated for each function block of the RMLP. The conditions on which function blocks are operated are also described on the table shown in FIG. 290.

[3576] How to refer to the table:

[3577] The vertical axis shows the function blocks.

[3578] The horizontal axis shows the EFs (EF1 and EF2) and the state of the PVC test.

[3579] Each item is divided into upper and lower columns.

[3580] The upper columns show EFs rejected by the check of a function block. If an EF is rejected, the EF represented by ‘ON’ is controlled. The lower columns show whether or not the EFs are processed with the check results.

[3581] 4.2.5. Data Interface Between FRMLP and LPCOM

[3582] FIGS. 291 through 295 show the data interface between the RMLP and the LP-COM and the cell format. Described below is the detailed explanation of the cell format shown in FIGS. 291 through 295.

[3583] IST: Segment type (ST) of the inter-MH interface format

[3584] DM: Result of matching of the DA-CTL LSI of the HMH00A (1: matching; 0: non-matching)

[3585] Output MID: Copy of 5 lower order bits of the output MID

[3586] RDA: Combined area of the D.C. of the 00-th word and the output MID′. The DA-ID is entered corresponding to the DA of the inter-MH interface format. Assigned by the DA CTL LSI of the HMH00A and changed into the D.C. and the output MID′ after the output MI of the HMH02A is acquired.

[3587] Input VCI: The source MH number is represented by 8 LSB bits of the VCI input from the MDX. 15-12 are 4 bits of the MSB; and 03-00 are 4 bits of the LSB.

[3588] BRLC: The BRLC number (umbilical link ID) of the destination SNI is input. If the destination SNI is HOST SW, it is set to 0.

[3589] Output VCI: Indicates a destination SNI. In a test cell, one MSB bit indicates 1.

[3590] PT: Payload type (no process is performed in a processor.)

[3591] CLP: Cell loss priority (no process is performed in a processor.)

[3592] SST: Segment type of the SIP. An encapsulated segment has the same value as the IST.

[3593] SN: Sequence number. An original value is transmitted from the processor to the PM unit/billing unit. Output MID: Message identifier

[3594] 1. An RMID is assigned after VCI and MID are degenerated by the acquisition of the RMID of the HMH01A.

[3595] 2. Changed into an output MID after the output MID of the HMH02A is acquired.

[3596] PL: The PL of the SIP is input.

[3597] CRC: A reassigned PL is input to the billing unit.

4.3. HMH00A

[3598] FIG. 296 is a block diagram showing the function of the HMH00A. FIG. 297 is a table showing the summary of the functions of each block shown in FIG. 296.

[3599] 4.3.1. Selection of Cross-connection R

[3600] Data from MH-COM is selected and transmitted to a processor.

[3601] (1) Outline of Functions

[3602] FIG. 298 is a block diagram showing the functions of selecting the cross-connection R; and FIG. 299 is a table showing the summary of the function of each block.

[3603] 4.3.1-1, 2, and 3 System Cross-connection

[3604] The HMH00A is an entry of the RMLP, and enables cross-connection to another RMLP system. It fetches data from its own MDX through the B.W.B and simultaneously outputs data to another system through front connector B. It also fetches the data of other systems through front connector A (FIG. 300).

[3605] 4.3.1-4 39 MHz FIFO

[3606] The data asynchronously fetched internally and externally is synchronized by reading the data using the V1 DMX LSI, the same clock, and CF. The reading CF is generated by the timing generator R (FIG. 301).

[3607] 4.3.1-5 Selection of Cross-connection Data

[3608] The internal and external data output by the FIFO, whichever is in an active system, is selected by the SWACT. The data is selected in cell frames (FIG. 302).

[3609] 4.3.1-7 Address Filter R Inf.

[3610] An address filter R converts a 39M/16 bit parallel signal into a 13M/48 bit parallel signal using the CSPC-AD LSI because it uses the DA-CTL LSI. The CSPC-AD LSI reassigns a parity because the parity does not contain “enable”.

[3611] (2) MSCN Point

[3612] FIG. 303 shows an MSCN point relating to the cross-connection selecting unit. The polarity is represented as being faulty by ‘H’. A pseudo-fault is represented as a pseudo-fault by ‘H’. The numbers (1 through 4) of the items on the table correspond to those shown in FIG. 298.

[3613] 4.3.2. Timing Generator

[3614] A timing generator generates a clock and a cell frame to be used in the RMLP after receiving a clock and a cell frame from the internal HLP02A.

[3615] (1) Outline of Functions

[3616] FIG. 304 is a block diagram showing the functions of the timing generator R; and FIG. 305 is a table showing the summary of the functions of each block. 4.3.2-1 39 MHz CF Generator

[3617] The VI DMUX read CF requires a timing in which the same cell can be read from both home and mate systems. If the read CF is between the home and mate write CFs, a cell immediately before or after is read. Accordingly, the read CF is delayed by 9τ if a write CF (home or mate) reaches at 6τ before or after the generated CF. It is processed as a read CF after it is written (home and mate) to the V1 DMUX. FIG. 306 shows the above described operations.

[3618] (2) MSCN Point

[3619] FIG. 307 shows the MSCN point relating to the timing generator R. The polarity is represented as being faulty by ‘H’. A pseudo-fault is represented as a pseudo-fault by ‘H’. The numbers (1 through 3) of the items on the table correspond to those shown in FIG. 304.

[3620] 4.3.3. Address Filter R

[3621] It is determined whether or not the cell is to be processed in the home RMLP. The cell is then transmitted to the processor of 155M.

[3622] (1) Outline of Functions

[3623] FIG. 308 is a block diagram showing the functions of the address filter R; and FIG. 309 is a table showing the summary of the functions of each block shown in FIG. 308.

[3624] 4.3.3-1 DA Matcher

[3625] When the BOM and SSM arrive, a matching process is performed between the DA of the cell and the internal data of the table. A matching signal and a matching address are then output, the matching cell is fetched, and matching information and a matching address are assigned to the tag field. No operations are performed when a COM or EOM arrives.

[3626] 4.3.3-2 VCI/MID Matcher

[3627] The COM and EOM are filtered using the VCI/MID of the BOM for which the DA matcher output a matching result so that only a cell containing a message to the internal MESH.

[3628] 4.3.3-3 Enable Control

[3629] The “enable” assigned to a TCG test cell and a cell for which the DA matcher and the VCI/MID matcher output a non-matching result is canceled. The enable-canceled data is reassigned a parity. FIG. 310 is a table showing the summary of the conditions of the VCI/MID matcher.

[3630] (2) MSCN Point

[3631] FIG. 311 shows the MSCN point relating to the address filter R. The polarity is represented as being faulty by ‘H’. A pseudo-fault is represented as a pseudo-fault by ‘H’. The numbers (1 through 5) of the items on the table correspond to those shown in FIG. 308.

4.4. HMH01A

[3632] FIG. 312 is a block diagram showing the functions of the HMH01A; and FIG. 312 shows the summary of the functions of each block shown in FIG. 312.

[3633] 4.4.1. Test Cell Multiplexing R and 9MG R

[3634] When the circuit indicates an idle cell, a test cell from the HLP02A is multiplexed and transmitted to the processor. A 9MCK is generated based on the 19MCK and the FP from the HLP02A.

[3635] (1) Outline of Functions

[3636] FIG. 314 is a block diagram showing the functions of the test cell multiplexing R and 9MG R and a table showing the summary of the functions of each block.

[3637] (2) MSCN Point

[3638] FIG. 315 shows the MSCN point relating to the test cell multiplexing R and 9MG R. The polarity is represented as being faulty by ‘H’. A pseudo-fault is represented as a pseudo-fault by ‘H’. The numbers (1, 2, and 3) of the items on the table correspond to those shown in FIG. 314.

[3639] 4.4.2. MID Check R

[3640] An MID check is performed on the cell data.

[3641] (1) Outline of Functions

[3642] FIG. 316 is a block diagram showing the functions of the MID check R and a table showing the summary of the functions of each block.

[3643] (2) MID Check

[3644] In the MID check R, a process shown in FIG. 317 is performed according to the segment type, DM, and RAM information.

[3645] (3) Error Flag

[3646] If an error is detected in the MID check R, an error flag is set to ‘L’ as shown in FIG. 318 according to the segment type. A test cell (SNI loopback) is not a process object.

[3647] (4) MSCN Point

[3648] FIG. 319 shows the MSCN point relating to the MID check R unit. The polarity is represented as being faulty by ‘H’. A pseudo-fault is represented as a pseudo-fault by ‘H’. The numbers (1 and 2) of the items on the table correspond to those shown in FIG. 316. Since the unit shares the memory with the SN check unit and the encapsulation unit, the MSCN point is shared among the MID check unit, the SN check unit, and the encapsulation unit.

[3649] 4.4.3. SN Check R

[3650] An SN check is performed on cell data.

[3651] (1) Outline of Functions

[3652] FIG. 320 is a block diagram showing the functions of the SN check R and a table showing the summary of the functions of each block. This process is performed simultaneously with the MID check and the encapsulation.

[3653] (2) Error Flag

[3654] If an error is detected in the SN check R, an error flag is set to ‘L’ as shown in FIG. 321 according to the segment type. A test cell (SNI loopback) is not a process object.

[3655] (3) MSCN Point

[3656] FIG. 322 shows the MSCN point relating to the SN check R unit. The polarity is represented as being faulty by ‘H’. A pseudo-fault is represented as a pseudo-fault by ‘H’. The MSCN point is shared among the MID check unit, the SN check unit, and the encapsulation unit. The number 1 of the item on the table corresponds to that shown in FIG. 320.

[3657] 4.4.4. Encapsulation R

[3658] The SIP interface protocol data unit (SIP inf. PDU) is retrieved from the message handler inter-MH interface protocol data unit (inter-MH inf. PDU) to alter the segment type ST.

[3659] (1) Outline of Functions

[3660] FIG. 323 is a block diagram showing the functions of the encapsulation R and a table showing the summary of the functions of each block. This process is performed simultaneously with the MID check and the SN check.

[3661] (2) Error Flag

[3662] FIG. 324 shows an error flag relating to the encapsulation unit. The polarity is represented as being faulty by ‘L’. A test cell is a process object.

[3663] (3) MSCN Point

[3664] FIG. 325 shows the MSCN point relating to the encapsulation unit. The polarity is represented as being faulty by ‘H’. A pseudo-fault is represented as a pseudo-fault by ‘H’. The number 1 of the item on the table corresponds to that shown in FIG. 323. The MSCN point is shared among the MID check unit, the SN check unit, and the encapsulation unit.

[3665] 4.4.5. Error Edit IR

[3666] An error checked by each checker is assigned to each position of the error flag.

[3667] (1) Outline of Functions

[3668] FIG. 326 is a block diagram showing the error edit I R and a table showing the summary of the functions of each block.

[3669] 4.4.6. RMID Acquisition R

[3670] Data is compressed for internal process according to the VCI/MID.

[3671] (1) Outline of Functions

[3672] FIG. 327 is a block diagram showing the functions of the RMID acquisition R; and FIG. 328 is a table showing the summary of the functions of each block shown in FIG. 327.

[3673] (2) Error Flag

[3674] FIG. 329 shows an error flag relating to the RMID acquisition unit. The polarity is represented as being faulty by ‘L’.

[3675] 4.4.7. MRI Timeout Check R

[3676] The MRI timeout of the message received from the HMH00A is determined.

[3677] (1) Outline of Functions

[3678] FIG. 330 is a block diagram showing the functions of the MRI timeout check R; and FIG. 331 is a table showing the summary of the functions of each block shown in FIG. 330.

[3679] (2) Detailed Explanation of Functions

[3680] 1. ST determination of cell

[3681] Refer to the ST acquisition unit because the process is similar to that performed by the ST acquisition unit for MID compression.

[3682] 2. Cell counter

[3683] Cells are counted by two methods, that is, a total cell counting mode and a valid cell counting mode. The modes can be switched by the MSD.

[3684] MRITEM: address 0218, bit 03, 0 for total cell count, and 1 for valid cell count

[3685] 3. Generation of space pattern

[3686] Since the process is similar to that of the MID compressed space pattern unit.

[3687] 4. MRI TIME (AMDCAM)

[3688] 1. The present time is written from the cell counter at the receipt of the BOM.

[3689] 2. The time written to the COM and EOM is compared with the present time.

[3690] 3. If a matching result is output, a timeout pattern is generated and written.

[3691] 4. If a non-matching result is output and an EOM is reached, a space pattern is generated.

[3692] 5. Generation of timeout pattern

[3693] A timeout pattern is output to the MRI TIME according to a matching signal of the MRI TIME.

[3694] 6. Transmission of TO cell

[3695] A timeout cell (TO cell) is generated and transmitted when an invalid cell is detected. FIG. 332 shows the header format of the TO cell.

[3696] A matching address in the timeout pattern indicates the RMID. A destination SNI-ID is assigned and transmitted according to this RMID by the GA copying unit. Accordingly, the destination SNI-ID shown in FIG. 332 is exactly “Don't care” (D.C.), and is assigned a destination SNI-ID by the GA copying unit.

[3697] (3) Error Flag

[3698] FIG. 333 shows an error flag relating to the MRI timeout check unit. The polarity is represented as being faulty by ‘L’.

[3699] 4.4.8. GA Copy

[3700] A cell input at the GA is output to each subscriber.

[3701] (1) Outline of Functions

[3702] FIG. 334 is a block diagram showing the functions of the GA copy R; and FIG. 335 is a table showing the summary of the functions of each block shown in FIG. 334.

[3703] (2) Error Flag

[3704] FIG. 336 shows an error flag relating to the GA copy unit. The polarity is represented as being pseudo-faulty by ‘L’.

[3705] (3) MSCN Point

[3706] FIG. 337 shows the MSCN point relating to the GA copying unit. The polarity is represented as being faulty by ‘H’. A pseudo-fault is represented as a pseudo-fault by ‘H’. The numbers (1 through 5) of the items on the table correspond to those shown in FIG. 334.

[3707] 4.4.9. SNI Available R

[3708] A cell is discarded when it cannot be received due to a DT fault of the SIP, etc.

[3709] (1) Outline of Functions

[3710] FIG. 338 is a block diagram showing the SNI available R and a table showing the summary of the functions of each block.

[3711] (2) Error Flag

[3712] If an error is detected in the SNI available R, an error flag is set to ‘L’ as shown in FIG. 339 according to the segment type. If the highest order bits of the inter-MH COM, EOM and destination SNI-ID indicate ‘1’, it is not a process object. An error cell (SNI loopback) is a process object.

[3713] (3) MSCN Point

[3714] FIG. 340 shows the MSCN point relating to the SNI available R unit. The polarity is represented as being faulty by ‘H’. A pseudo-fault is represented as a pseudo-fault by ‘H’.

[3715] 4.4.10 Error Edit II R

[3716] An error checked by each checker is assigned to each position of the error flag.

[3717] (1) Outline of Functions

[3718] FIG. 341 is a block diagram showing the error edit II R and a table showing the summary of the functions of each block.

[3719] 4.4.11 SA Check R

[3720] In response to the GA message, an internal loopback cell is turned back.

[3721] (1) Outline of Functions

[3722] FIG. 342 is a block diagram showing the SA check R and a table showing the summary of the functions of each block.

[3723] (2) Error Flag

[3724] If an error is detected in the SA check R, an error flag is set to ‘L’ as shown in FIG. 343 according to the segment type. If the highest order bits of the inter-MH COM and destination SNI-ID indicate ‘1’, it is not a process object. If a cell is assigned an EFMS (master flag) it is not a process object.

[3725] (3) MSCN Point

[3726] FIG. 344 shows the MSCN point relating to the SA checking unit. The polarity is represented as being faulty by ‘H’. A pseudo-fault is represented as a pseudo-fault by ‘H’. The numbers (1 and 2) of the items on the table correspond to those shown in FIG. 342.

4.5. HMH04A

[3727] HMH04A realizes only the functions of the SA screening R to the RMLP. Since the 9MGS and the pP interface S are shared with the SMLP, they are not explained in detail here.

[3728] 4.5.1. SA Screening R

[3729] Outline of Functions

[3730] Restrictions are placed on the reception of cells at a destination SNI. The following two methods are adopted to restrict the reception of cells.

[3731] 1. Restrictions are placed on the reception of cells from an entered address (IA) (SC attribute=1).

[3732] 2. Restrictions are placed on the reception of cells from an address other than an entered address (IA) (SC attribute=0).

[3733] These reception restricting methods are stored in the SC attribute memory.

[3734] Process performed when the BOM and SSM arrive

[3735] 1. The attribute of the IA of the SC attribute memory (shared by the DA screening of the SMLP) is read.

[3736] 2. A matching process is performed at the SS screening CAM (physically the same LSI as the DA screening CAM used in the SMLP) using the SA as matching data.

[3737] The table of FIG. 345 showing the state of matching with the SC attribute is referred to. If it is determined as an error, the error flag (EFSS) is set to L.

[3738] The COM and EOM are not process objects.

[3739] If the highest order bit (bit 11 of the 02nd word) of the destination SNI-ID is 1, it refers to an MESH-MH PVC test cell and is not a process object.

4.6. HMH02A.

[3740] The HMH02A controls the band of the SBMESH-RMLP unit and limits the number of transmitted messages. FIG. 346 is a block diagram showing the entire configuration of the HMH02A.

[3741] 4.6.1. Outline of Configuration

[3742] FIG. 347 is a block diagram showing the functions of the HMH02A. In FIG. 347, the horizontal connection mainly refers to the highway HW data system. The vertical connection mainly refers to control data and control signals.

[3743] 4.6.2. Outline of Functions

[3744] FIG. 348 is a table showing the functions of each block shown in FIG. 347.

[3745] 4.6.3. Outline of Interface I/F

[3746] # FIG. 349 shows the state of the interface I/F of the HMH02A. The horizontal connection mainly refers to the HW data system. The vertical connection mainly refers to control data and control signals.

[3747] 4.6.4. Detailed Explanation

[3748] Sequentially described below in detail are the functions according to the above described outline.

[3749] 4.6.4.1. Message Control

[3750] FIG. 350 is a table showing the contents of the message control.

[3751] (1) Restriction of the Number of Simultaneously-transmitted Messages

[3752] A received message is managed for each SNI, and the number (corresponding to the number of MID for each SNI) of messages simultaneously transmitted is controlled. Messages exceeding the restriction number or containing an error are removed from the HW.

[3753] FIG. 351 is a detailed block diagram showing the above described simultaneously transmitted message number restricting unit.

[3754] The simultaneously transmitted message number restricting unit manages the transmission of messages by comparing the number of transmitted messages with the restriction number. Unless the number of transmitted messages exceeds the restriction number when messages arrive, the messages is allowed to be transmitted and the number of the messages are added to the transmission number. If the number of transmitted messages has already reached the restriction number, arriving messages are rejected. The first rejected message is buffered (buffering is described later). The other rejected messages are processed as invalid messages with an error flag set. No process is performed on the subsequent messages over the number of the simultaneously transmitted messages. The restriction number of simultaneously transmitted messages is 1 or 16.

[3755] (1)-1 Management of Transmission Number

[3756] The number of transmitted messages is managed for each SNI. FIG. 352 is a table showing the management of the number of transmitted messages for a specified SNI.

[3757] (1)-2 Removing Error Cells

[3758] The error flags of transmitted cells are monitored. Erroneous cells are processed as invalid cells and removed from the process flow not to be transmitted to the processors after restricting the number of simultaneously-transmitted messages. If an invalid cell is detected, the message related to the cell is also processed as an invalid message. An erroneous cell is entered in error type statistics data and transmitted to the LP-COM for analysis.

[3759] (1)-3 Buffering Control

[3760] Buffering control is performed in message units by identifying a cell belonging to a message to be buffered, accessing a cell memory, and managing the number of cells.

[3761] Data is buffered only if messages cannot be simultaneously transmitted and the cell memory is unused. Although the data is buffered in message units, various messages actually arrive in cell units and therefore it requires control in cell units.

[3762] A determination is made when a message passes the IBOM as to whether or not the message can be buffered. If the determination indicates “yes”, it is so entered. The message entry state is retrieved for the subsequent cell groups, and the cells are processed according to the retrieved state.

[3763] 1. Message write control

[3764] If an arriving cell belongs to a message which can be buffered, it is written to the cell memory. The number of cells written to the cell memory is calculated for each SNI, and managed for each message.

[3765] 2. Message read control

[3766] A buffered message is determined as possibly being read from a buffer when the number of messages simultaneously transmitted to the destination SNI does not exceed the restriction number. If a message is determined as possibly being read from the buffer, it is read in cell units from the cell memory and transmitted at a timing of an idle cell. At this time, the number of cells read from the memory is counted as in 1 above and managed as having been read.

[3767] The state of a message is monitored by comparing 1 with 2 above.

[3768] If 2 is smaller than 1, it indicates that a cell exists in the cell memory. If they are equal to each other, it indicates that the read has been completed.

[3769] FIG. 353 shows the concept of the buffering management.

[3770] (2) Output MID Acquisition

[3771] Since the RMID is a compressed MID after being combined with the SNI in the HMlH01A, it cannot be transmitted as is to the MDX unit. Therefore, an output MID is acquired based on the RMID and then replaces the RMID. Using the MID identifies messages of different types to be transferred to the same VCI (SNI), and also identifies messages in cell units. FIG. 354 is a block diagram showing the output MID acquiring unit.

[3772] As shown in FIG. 355, an output MID is acquired based on the VCI of the IBOM and RMID when the IBOM arrives. An output MID acquisition table (memory shown in FIG. 354) is referred to by using the VCI of the arriving IBOM cell as a key. The VCI of the IBOM cell refers to a specific SNI. An output MID is obtained by adding a predetermined fixed data to the address of data having the SNI corresponding to the VCI of the above described IBOM cell. Then, the message can be entered by writing the RMID to the shadowed area of the address. The entry of the message completes the acquisition of the output MID.

[3773] In the cell groups after the above described IBOM, the VCI/RMID written to the output MID acquisition process of the IBOM is retrieved based on their own VCI/RMID as a key. Predetermined fixed data is added to a resultant address to obtain an output MID. That is, relating to cell groups after the IBOM, the output MID acquisition table is generated when the IBOM arrives and used to obtain the output MID simply by retrieving necessary data from the table using their own VCI/RMID as a key.

[3774] If an IEOM or an error cell arrives, the obtained MID is released by deleting the RMID written to the above described output MID acquisition table in the output MID acquisition process.

[3775] (3) Restriction of Egress Flow

[3776] An egress flow restricting unit classifies received messages for each SNI and controls the output band based on a predetermined band.

[3777] A band is controlled by managing and controlling the time interval of transmitting cells. A cell flow increases if the interval of transmitting cells is shorter, but decreases if the interval is longer according to the basic concept of the ATM.

[3778] Practically, the time interval of transmitting cells is controlled according to the time parameter defined by the band, and the time information is constantly stored and managed for each SNI using the time table. The parameter for use in controlling the band is generated according to the band assigned individually to each subscriber. In the SBMESH unit, the table manipulation, settings, etc. are collectively managed by the μP unit provided for the HLP02A of the LP-COM unit. FIG. 356 is a block diagram showing the egress flow restricting unit.

[3779] (4) Discard Counter

[3780] Cells discarded by the band control through the restriction of an egress flow are counted and the information is transmitted to the PM unit (HLM01A).

[3781] The counter comprises a duplex configuration memory in the RAM. It releases one portion of the memory at the HtM01A's request for data and counts discarded cells in the other portion of the memory. These RAM portions are switched according to a RAMCHG signal from the HLM01A. FIG. 357 is a block diagram showing the discard counter unit.

[3782] (5) Generation of CRC-10

[3783] A CRC-10 generating unit allows the CRC to manage a cell payload unit to ensure the normality and quality of data. Generating and adding a CRC-10 enables a single-bit error to be detected and corrected and also enables a plural-bit error to be detected. FIG. 358 is a block diagram showing the CRC-10 generating unit. FIG. 359 shows the positions where a polynomial of the CRC-10 generated by the CRC-10 generating unit and-a CRC-10 polynomial in a cell are stored.

[3784] 4.6.4.2. Clock Generating Unit

[3785] A clock generating unit receives a master clock and generates a 9 MHz clock for use in a highway HW data process in the RMLP unit and for an external I/F.

[3786] The master clock manages the SBMESH internal clock for the present system, prevents the waste of the resources for the BWB, etc. by transmitting the clock for plural times, and receives a share from the HLP02A. A synchronizing frame pulse (FP) is also distributed to ensure uniform rise and fall of a generated clock. The 9 MHz clock is generated based on the master clock. Its phase is synchronized by the FP, and then the clock runs autonomously (it can be constantly synchronized by the FP). FIG. 360 is a block diagram showing the clock generating unit. FIG. 361 shows the method of generating the clock.

[3787] 4.6.4.3. μP I/F

[3788] This interface receives addresses, data band control signals, etc. from the μP unit provided in the HLP02A, transmits data, and controls and manages each function of internal units. FIG. 362 shows the contents of the μP I/F.

5. MH-COM UNIT

5.1. General Descriptions

[3789] The MH-COM unit comprises the following functions.

[3790] 1. Data is demultiplexed after being transmitted from an ATM switch, and then transmitted to the LP unit

[3791] 2. The data from the LP unit is multiplexed and transmitted to the ATM switch.

[3792] 3. The signaling through the LAP is terminated.

[3793] The MH-COM unit has a duplex configuration exclusive to the ATM switch system, and has a cross-connection for signaling and VCC copying between systems. The MH-COM unit comprises four PWCBs. FIG. 363 shows the PWCBs and the functions of each PWCB.

5.2. RDMX/SMUX Function (HMX10A)

[3794] As shown in FIG. 204, the SBMESH is connected to sides 0 and 1 of the ATM switch (ASSW). Physically, the same cable is used for connection between the ASSW upward side 0 and the SBMESH and between the ASSW downward side 0 and the SBMESH. This cable is connected to the A-conn. of the HMX10A PWCB (another cable is connected to the b-conn. for a daisy chain).

[3795] As shown in FIG. 204, the cable transmits the following two types of data.

[3796] data to be transmitted to the sending terminal of the SBMESH, that is, from the SMLP to the ASSW.

[3797] data to be transmitted from the ASSW to the receiving terminal of the SBMESH, that is, to the RMLP.

[3798] To transmit the data, the HMX10A has the following functions.

[3799] Multiplexing data to be transmitted from the SMLP to the ASSW (SMUX function)

[3800] Demultiplexing data to be transmitted from the ASSW to the RMLP (RDMX function)

[3801] FIG. 364 is a block diagram showing the HMX10A. FIGS. 365 and 366 show the monitor items of the HMX10A.

[3802] The actual RDMX function does not demultiplex data according to the tag information but fetches data to the RMLP according to the destination address DA in consideration of the broadcast of the group address GA. Thus, the HMX10A does not have an actual multiplexing function, but the function is practically performed by the RMLP. The HMX10A transmits the data from the ASSW to the RMLP. The DMUX LSI shown in the figures processes test cells.

5.3. SDMX/RMUX Function (HMX11A)

[3803] As shown in FIG. 204, the SBMESH is connected to sides 0 and 1 of the ATM switch (ASSW). Physically, the same cable is used for connection between the ASSW upward side 1 and the SBMESH and between the ASSW downward side 1 and the SBMESH. This cable is connected to the A-conn. of the HMX11A PWCB (another cable is connected to the b-conn. for a daisy chain).

[3804] As shown in FIG. 204, the cable transmits the following two types of data.

[3805] data to be transmitted to the receiving terminal of the SBMESH, that is, from the RMLP to the ASSW.

[3806] data to be transmitted from the ASSW to the sending terminal of the SBMESH, that is, to the SMLP.

[3807] To transmit the data, the HMX11A has the following functions.

[3808] Multiplexing data to be transmitted from the RMLP to the ASSW (RMUX function)

[3809] Demultiplexing data to be transmitted from the ASSW to the SMLP (SDMX function)

[3810] The HMX11A also has the function of multiplexing and demultiplexing signalling data through the LAP.

[3811] FIG. 367 is a block diagram showing the HMX11A. FIGS. 368 through 370 show the monitor items of the HMX10A.

[3812] Unlike the demultiplexing function of the HMX10A, that of the HMX11A is realized according to the tag information. Therefore, not only test cells but also data to be transmitted to the SMLP is extracted by the DMUX LSI shown in FIG. 367.

5.4. VCC Function/Test Cell Multiplexing Function/Scheduling Function (HMX12A)

[3813] 5.4.1. VCC Function

[3814] FIG. 371 is a block diagram mainly showing the VCC function of the HMX 12A. FIG. 372 is a block diagram mainly showing the scheduler function of the HMX12A. FIGS. 373 through 375 show monitor items in the fault process.

[3815] The cell data from the SMLP and RMLP, and the header field of a TCG cell are converted. The header field is converted by the VCIP-LSI (VCIP of the SMLP, and VCIP of the RMLP) shown in FIG. 371.

[3816] A VCC value is set by writing it from the BSGC to the VCIP-LSI through the HSF05A. The VCIP-LSI reads the information in the header field and converts the header value according to the information written in the RAM.

[3817] 5.4.2. Test Cell Multiplexing Function

[3818] There are two types of SEL-N1-LSIs, that is, one to multiplex a data cell from the SMLP and a TCG cell from the HMX11A, and another to multiplex a TCG cell from the HMX11A. The SEL-NL-LSI multiplexes cells from the SMLP/RMLP as is. However, a TCG cell is multiplexed only after the information in the header field is read and recognized as a TCG cell.

[3819] 5.4.3. Schedule Function (multiplex-LSI control)

[3820] A multiplex-LSI HMX10A provided in the HMX10A and HMX11A is controlled and multiplexed.

[3821] The scheduler function is designed inside the LCA of the HMX12A. There are two LCAs, one for controlling the multiplexing function of the HMX10A and another for controlling the multiplexing function of the LCA.

[3822] The function of the LCA (scheduler function) allows a read enable signal to be sent to each MUX-LSI according to a write notification signal from each MUX-LSI.

[3823] The HMX12A has four connectors on the front panel two of which are used for inter-system cross-connection between signaling data, the other two of which are used to daisy-chain scheduler function signals.

5.5. LAP Terminating/Starting Clock Distribution (HSF05A)

[3824] 5.5.1. LAP Terminating/Starting Process

[3825] FIG. 376 is a block diagram showing the function of the HSF05A. FIG. 377 shows the monitor items on the fault correcting process of the above described HSF05A.

[3826] A signaling cell transferred by the LAP through the BSGC is terminated by the EGCLAD shown in FIG. 376, and the signaling data is processed by the μP. Actually, an MSCN is collected, an MSD is set, an LSI is set and monitored, a VCC copy is performed, a fault monitor is performed, etc. Additionally, the information of a fault inside and outside the MH-COM is notified.

[3827] (1) MSCN/MSD

[3828] The MSCN is used in each package PKG unit and functions as monitor of abnormal electric volume of CK/CF, parity, OBP, fuse, etc. The MSD applies a pseudo fault to a checkpoint of the MSCN.

[3829] (2) Setting/Notifying LSI

[3830] The LSI is set through the LAP using the uP. Furthermore, errors are monitored, cells are discarded, etc.

[3831] (3) VCC Copying

[3832] A VCC copy is performed to copy the VCC information of the presently active system to a next-active system.

[3833] (4) Communications with Another System

[3834] The SIC notifies another system of the start/end of the VCC copy, fault information, etc.

[3835] 5.5.2. Distribution of Clock

[3836] The HSF05A receives a source clock from the SYNSH and uses 64 KHz in the MH-COM and LP-COM. The MH-COM generates 155.52 MHz and generates various timing signals according to the clock. FIG. 378 shows the clock system of the SBMESH.

6. PROTOCOL PERFORMANCE MONITOR

6.1. Outline

[3837] The SBMESH monitors the protocol performance of the L3-PDU of layer 3. The protocol performance monitor operates generally in accordance with the TR-TSV-000774 issue 1 (hereinafter referred to as TR-774 for short) published by Bell Communications Research.

[3838] This protocol performance monitor is realized by the HLM01A. The HLM01A also corrects data as described later.

[3839] FIG. 379 is a block diagram showing the function of the HLM01A. FIGS. 380 and 381 show the outline of the functions of each block in the HLM01A. FIGS. 382 and 383 show checks performed by the HLM01A. The check names shown in FIGS. 382 and 383 correspond to the names shown in FIG. 379.

[3840] The results of the checks above are written to the MSCN register shown in FIG. 379 and provided for the HLP02A. The results of the following items (not described above) are also written to the MSCN register.

[3841] initialization in process

[3842] LCA configuration in process

[3843] cross communications cable missing

[3844] mate system fuse alarm

[3845] timeout of a watchdog timer of the mate system HLP02A

[3846] In FIGS. 382 and 383, no checks are made if the conditions defined for each item are not satisfied for the check items below the check name=PCc. Checks are not made unless a cell is valid.

6.2. Layer 2 Protocol Performance Monitor

[3847] The SBMESH monitors the protocol performance of each of the following parameters of layer 2.

[3848] (1) payload CRC violation

[3849] (2) payload length error

[3850] (3) invalid sequence number

[3851] (4) currently active MID

[3852] (5) BOMs/SSMs having an invalid MID

[3853] (6) EOMs having an unauthorized MID

[3854] If an error notification (to be described later in detail) is received from the SMLP in the HLM01 of the SBMESH, a layer-2 protocol performance monitor is performed on each of the parameters (1) through (6) above through the sum-of-errors algorithm for each input SNI. A threshold for the sum-of-errors algorithm is set for each SNI by the software as a part of the subscriber data.

[3855] The TR-774 defines that the above described threshold is variable in the range of 1 through 2²²-1. In the HLM01A of the SBMESH, the threshold is regarded by the software as being contained in (2^x-1) and as parts of subscriber data. An 8-digit value set by the software is a binary representation of the exponent X of (2^x-1).

[3856] The count value is compared with the threshold in the sum-of-errors algorithm autonomously by the hardware. If a count value exceeds the threshold, it is provided as a flag for the firmware. The firmware periodically monitors the flag. If it detects an ON state, it notifies the software of the ON state. In response to the notification, the software generates a TCA.

[3857] TR-774 defines a current 15-minute counter and 32 previous 15-minute registers as parts of the sum-of-errors algorithm.

[3858] Two 15-minute counters are provided to switch phases in the SBMESH. Within 15 minutes after a phase switch instruction, the software picks up a count value from the 15-minute counter corresponding to the previous 15-minute register. That is, the software provides 32 previous 15-minute registers of the TR-774.

[3859] The 774 also defines the count of errors for each of the parameters (1) through (6). Practically, as in the sum-of-errors algorithm, it defines for each parameter a current 15-minute counter and 32 previous 15-minute registers.

[3860] The SBMESH provides two 15-minute counters as described above for use in a phase switch, and the software provides 32 previous 15-minute registers.

[3861] The definition of the number of digits of the counter and the register is in accordance with the number of digits specified as the sum-of errors algorithm.

[3862] The TR-774 defines that the payload CRC violation described in (1) above and the HCS violation are counted by the same counter, and the previous 15-minute register is shared by both parameters. In the SBMESH, the payload CRC violation described in (1) above is checked by the SBMESH itself, and the HCS violation is checked by the DT. The SBMESH counts the invalid sequence number described in (3) above and the currently active MID described in (4) above are counted according to an error notification from the RMLP (described later in detail). (Since each of the above described checks is made and cells are discarded when an error is detected in the RMLP, the counting operations are performed. The number of digits of each counter is also in accordance with that requested by the sum-of-errors algorithm).

[3863] The above described counting operation is performed for each MH transmitting an errored L2-PDU. In this case, the SBMESH provides two 15-minute counters to switch phases.

6.3. Layer-3 Protocol Performance Monitor

[3864] The SBMESH monitors a protocol performance for each of the following parameters in layer 3.

[3865] (1) invalid BA size field value

[3866] (2) invalid HEL field value

[3867] (3) invalid header extension version element

[3868] (4) invalid header extension carrier selection element

[3869] (5) BEtag mismatch

[3870] (6) non-matching between BA size field and Length field

[3871] (7) incorrect length

[3872] (8) MRI timeout

[3873] (9) invalid DA type

[3874] (10) invalid SA type

[3875] (11) invalid DA assigned to the original SNI

[3876] If an error notification (described later in detail) is received from the SMLP in the HLM01A of the SBMESH, a layer-3 protocol performance monitor is performed on each of the parameters in (1) through (8) above using the sum-of-errors algorithm and Bursty error algorithm for each input SNI.

[3877] The threshold of the sum-of-errors algorithm is set for each SNI by the software as parts of the subscriber data as in the case of layer 2. Also as in the case of layer 2, the count value exceeding the threshold is notified as an error notification to the software through the firmware. In layer 3, as in layer 2, the SBMESH provides two 15-minute counters for a phase switch. The software provides 32 previous 15-minute registers of the TR-774.

[3878] The contents of the log generated when an error occurs relating to each of the parameters (1) through (8) is as follows.

[3879] (a) error detection date (year, month, day, hour, minute, second)

[3880] (b) SNI

[3881] (c) source address

[3882] (d) destination address (including address type)

[3883] (e) special occurrence state

[3884] When a log object error occurs, the hardware sets the contents of (b) through (e) in the log register. The firmware reads the contents of the log from the register and notifies the software of the contents. The contents of the is not provided from the hardware to the firmware. When the firmware fetches the contents of the log other than the (a) above, they are assigned the time information managed by the firmware. The contents of the notification for the software do not contain year/month/day information. The information is managed by the software. The SBMESH realizes the log retrieval through the software.

[3885] The threshold for the Bursty error algorithm is also transmitted from the software to the SBMESH-A as parts of subscriber data as in the case of layer 2. It is not necessarily set for each SNI, and is accumulated and managed by the firmware.

[3886] According to the TR-774, the threshold is variable in the range of 1 through 100. The SBMESH specifies an 8-digit threshold through the software. Ni and Nb are used in the Bursty error algorithm, also transmitted from the software as parts of subscriber data, and set for each SNI.

[3887] According to TR-774, Ni and Nb is defined as variable in the range of 1 through (2²²-1), but this can be processed as a variation of 2^xand the SBMESH processes it as if an 8 software-specified digits represent the exponent X of the above value as a binary.

[3888] According to the TR-774, Ni and Nb should be set for each SS NE, but they are set to the same value for each SNI as described above.

[3889] Refer to the TR-774 for the details of the Bursty error algorithm. That is;

[3890] When Ni L3-PDUs are received, an interval counter is incremented.

[3891] If the number of errored L3-PDUs received exceeds Nb, a bad interval counter is incremented.

[3892] A ratio of the bad interval counter to the interval counter is obtained every 15th minute. If the value exceeds a predetermined threshold, a TCA is generated.

[3893] In the above described procedure, the two counters are autonomously incremented by the hardware. The firmware calculates the ratio every 15th minute. If the ratio exceeds the threshold, it then notifies the software of the information, and the software generates a TCA.

[3894] According to the TR-774, a current 15-minute counter is provided for each of the bad interval, the interval, and the ratio. Furthermore, 32 previous 15-minute registers are provided for each of the bad interval and the interval. The SBMESH provides two 15-minute counters for each of the bad interval and the interval to use them for a phase switch. As in the sum-of-errors algorithm, the SBMESH provides 32 previous 15-minute registers through the software. No current 15-minute counters exist to count the above described ratio.

[3895] The TR-774 defines each of the error counts for the parameters (9) through (11). The configuration of the above described counter and register is the same as that of the sum-of-errors algorithm.

[3896] In the SBMESH, the MRI timeout described above in (10) is counted in response to an error notification from the RMLP (described later in detail). In the RMLP, the counting operation is performed because the above described check is made in the RMLP and data is discarded if a related error is detected. The number of digits is in accordance with the requirements of the sum-of-errors algorithm). The counting is performed for each MH. In the SBMESH, two 15-minute counter are provided for use in switching phases.

6.4. Protocol Performance Monitor in Ingress Unit

[3897] 6.4.1. Process System

[3898] FIG. 384 shows based on the TR-774 the check items in the ingress unit, appropriate actions when an NG is detected, and checking procedure. Additionally, SBMESH-related items are included.

[3899] Parameters are grouped and checked in an alphabetical order. For example, if an NG is detected when a parameter belonging to group A is checked, then each of the parameters in group B and the subsequent groups need not be checked (including the actions taken when an NG is detected). If a plurality of parameters exist in a group, the parameters can be checked in any order.

[3900] “No” is described later.

[3901] The MRI timeout of group A includes the counting and logging when an NG is detected.

[3902] Group 0 indicates the specification unique to the SBMESH.

[3903] The MID assigned error is an error in the SBMESH internal process. An end user blocking indicates a carrier screening error.

[3904] Although the invalid BAsize field and the invalid header extension element length are indicated as being defined by the FR-774, they are not listed above.

[3905] Since each of the parameters belonging to groups B through D is checked in the DT unit, it is not a check object in the SBMESH.

[3906] Each parameter in item 2 of group L and in items 4 through 6 of group M refers to a network data collection and relates to traffic measurement. Therefore, it does not relate to a protocol performance monitor. (However, a number is assigned as described later).

[3907] Each of the parameters in items 2 and 3 of groups J and K is not checked in the SMLP. Therefore, no error notification is issued, but an area is reserved for an error count.

[3908] Although the process is performed by the HLM01A as described above, an error notification to be issued in each check in the ingress unit is received from the SMLP as described above.

[3909] The HLM01A receives data, cell frames, and enable signals from the SMLP. FIG. 385 is a time chart of each signal. FIG. 386 shows the explanation of each signal.

[3910] As shown in FIG. 385, data is received from the SMLP in a 16-bit parallel cell format. In a switch (including the SBMESH), data is processed as 1 cell=54 octets, and 1 cell of input data is 27τ in length at 8M clock.

[3911] One cell comprises a portion of 3τ in length corresponding to an ATM header (the format of the 3τ portion is an internal format of the SBMESH and does not completely match a common ATM header format. As shown in the figures, this portion contains a portion (source SNI ID) indicating the source SNI of the cell) and a remaining 24τ portion. The contents of the cell shown in FIG. 385 are examples of a case where the cell is a SIP-BOM.

[3912] FIG. 387 shows a method of identifying a cell segment type in an ST identification block shown in FIG. 379. Thus, combining the SST shown in FIG. 385 and the value stored in the IST identifies the segment type ST.

[3913] In FIG. 387, the inter-BOM refers to a BOM incremented as a result of a half encapsulation process performed in the SMLP. However, this process is not performed on an erroneous cell. Therefore, no inter-BOM is received. The ISTs of the SIP-BOM and SIP-SSM are 10 and 11 respectively.

[3914] Described below is the error determining method in the error analysis block shown in FIG. 379.

[3915] FIG. 385 shows values 0 through 26 in parentheses at a 9M clock. As described above, 1 cell equals 27τ, and a cell shows 0 at the first τ of the cell, increments 1 for each of the subsequent τ, and indicates 27 at the 27th τ. These values correspond to the “No” of various check items shown in FIG. 384. That is, as the method of identifying an error type according to an error notification signal (2), an error notification signal indicates L, that is, an error, at the portion corresponding to the number 6 in the parenthesis in FIG. 385.

[3916] An invalid sequence number corresponds to “No.6” shown in FIG. 384. That is, the above described example indicates that the cell has the error as a result of various checks in the SMLP. This signal constantly indicates L at the point of the number 26 in the parenthesis regardless of the existence of an error in the cell. This signal is not used to indicate an error but to monitor the stack this signal. 0 is not used for an error notification signal. An error type is determined by the above described method. However, only valid cells are objects of determination. If a plurality of errors exist in a single cell, an error notification is issued for all the errors. Since the check items are arranged in the checking order and the “No” is assigned in this order in FIG. 384, an error correcting process is performed only on an error corresponding to the data for which the error notification signal first indicates L in this block. When a valid inter-BOM (SIP-BOM or SIP-SSM if half encapsulation is not made on an error cell) is received, the SA/DA accumulation RAM shown in FIG. 379 accumulates the SA and DA in the cell. Described below is the reason for the accumulation of the SA and DA.

[3917] The object parameters of the protocol performance monitor of layer 3 are 11 items listed at the beginning of 6.3. above. In the 11 items, a log is requested for (1) through (8) when an error is detected. Since the SA and DA are contained in the inter-BOM (having the same contents as the SIP-BOM and SIP-SSM), no accumulation is required when an error occurs in the SIP-BOM or SIP-SSM. However, if a BEtag mismatch error, etc. occurs, the error is detected when the EOM is received. Therefore, the SA and DA in the inter-BOM of the L3-PDU are accumulated.

[3918] In the SA and DA accumulation method, the identification of the L3-PDU is performed by combining (corresponding to the RMID) the sending SNI ID and the receiving MID in the cell. Accordingly, the data is stored in the RAM using the (source SNI ID+MID) as an address (key). However, as shown in FIG. 385, the source SNI ID field is 6 bits and the number of SNIs accommodated by each SBMESH is 32. Therefore, only 5 lower bits of the field are used together with the 10-bit input MID field. A total of 15 bits, that is, 2¹⁵is used for an address of the RAM.

[3919] If a cell is an SIP-BOM in the groups shown in FIG. 384, a MID currently active is determined. If it is an EOM, an unauthorized MID is determined and counted separately.

[3920] The MRI timeout indicates an error that a timeout occurs without an EOM cell reaching the SMLP. In this case, a pseudo EOM cell is generated in the SMLP and the cell is transmitted together with an error notification indicating the MRI timeout. The sending SNIID and receiving MID in the pseudo EOM cell are the same as those of the corresponding BOM for the reason described below.

[3921] If an error of the object item is determined in an error analyzing block, a process as a protocol performance monitor is suspended. If an error requires a log, the contents of the log are stored in the register (ingress LOG-Reg in FIG. 379).

[3922] The “test” in FIG. 385 indicates whether or not the cell is an MESH-MH PVC test cell. If the field indicates 1, no process is performed relating to a monitor of an ingress protocol performance.

[3923] The “CP” in FIG. 385 indicates that the cell is copied when a GA copy process is performed by the SMLP. If the field indicates 1, no process is performed relating to a monitor of an ingress protocol performance.

[3924] Each counter shown in FIG. 379 stores a count value (for each SNI, error type, etc.) in the RAM, reads and counts a necessary count value, and then stores it in the RAM. The RAM comprises a dual port RAM, and is divided into two, one as a current counter for hardware access, and the other as a previous register for firmware access. The assignment of a phase is not fixed to a RAM address, but is switched according to a phase switch instruction from the firmware issued every 15th minute. The above described RAM is provided with chips for an L2/3 Sum of Err. count value, an L2/3 individual Err. count value, and an L3 Bursty Err. count value as shown in FIG. 379.

[3925] Each of the RAM and counter control blocks shown in FIG. 379 controls the access from the hardware of the RAM. The RAM is autonomously cleared by the hardware (for example, when the system is powered).

[3926] If an error actually has arisen in a cell, an error correcting process is performed (by incrementing the count value, etc.) during the reception of the next cell because, in the case of, for example, an end user blocking, the error type can be determined almost at the end of the cell. FIG. 388 is a time chart showing the process performed at the occurrence of an error.

[3927] As described above, each count value is stored in the RAM. To increment the count value, the count value is read from the RAM, incremented externally, and stored again in the RAM.

[3928] In the layer 3 Bursty Err. process, access is made to obtain a worst PDU count, errored PDU count, invalid count, bad interval count. The access is made in series.

[3929] The count value is incremented conditionally for the value smaller than the errored PDU count. If the conditions are not satisfied, the count value is not incremented. Regardless of the layer 3 Bursty Err. process, the subsequent counting operations are not performed if the count value has reached the maximum counter value determined by the hardware.

[3930] 6.4.2. Detailed Process

[3931] 1. L2/3 Sum of Err. Count

[3932] If an L2/3 Sum of Err. error is reported;

[3933] (1) The count value is incremented (+1) by reading it from the count value storage RAM. Simultaneously, a threshold is read from the threshold RAM.

[3934] (2) The count value incremented as described in (1) above is compared with the threshold. If the result indicates that the count value is larger than the threshold, the Err. flag-Reg. flag is set ON and the result is reported to the firmware.

[3935] (3) The incremented count value is stored in the RAM.

[3936] Although the count value is represented by 24 bits, the reading and writing operations in the RAM are performed three separate times divisionally 8 bits each. The increment of the count value, the comparison with the threshold, and setting a flag-on are performed for each sending SNI.

[3937] If the count value is the maximum value in the case (1) above, it is not incremented as described above in 6.4.1. A parity check is carried out when the threshold is read, a parity is generated when the count value is stored, and the parity check is made when the count value is read.

[3938] FIG. 389 is a time chart showing the access timing of the threshold and the count value.

2. L2/3 INDIVIDUAL ERROR COUNT

[3939] When an error to be individually counted is reported, the following processes are performed.

[3940] (1) A count value is read from the count value storage RAM and incremented (+1).

[3941] (2) The incremented count value is stored in the RAM.

[3942] FIG. 390 is a time chart showing the L2/3 individual error count process.

3. LAYER 3 BURSRY ERR

[3943] When an error relating to Bursry Err. is reported, the following processes are performed.

[3944] (1) An Errored-PDU count value is read from the count value storage RAM and incremented (+1).

[3945] (2) The incremented Errored-PDU count value is stored in the RAM.

[3946] FIG. 390 is a time chart showing the L2/3 individual error count process.

[3947] When an SIP-BOM and SSM are received, the following processes are performed.

[3948] (1) A PDU count value, Errored-PDU count value, interval count value, and bad interval count value are read from the count value storage RAM. Then, only the PDU count is incremented (+1), and the Ni and Nb are read from the Ni and Nb storage RAM.

[3949] (2) The PDU count value incremented in (1) above is compared with Ni. If the result indicates the PDU count value=Ni;

[3950] (a) The interval count value read in (1) above is incremented (+1).

[3951] (b) The Errored-count value is compared with the Nb. Only when the Errored-PDU count value≧Nb, the bad interval count value read in (1) above is incremented.

[3952] (c) The PDU count value and Errored-PDU count value are cleared (set to all 0) and stored in the RAM. The interval count value incremented in (a) above is stored in the RAM, and the bad interval count value is stored in the RAM only when it is incremented in (b) above.

[3953] Unless the result of (2) above indicates the PDU count value=Ni, only the PDU count value incremented in (1) above is stored in the RAM.

[3954] Each of the incrementing and Ni/Nb comparing operations is performed for each sending SNI. A parity bit is checked when the Ni and Nb are read, generated when each count value is stored, and also checked when each count value is read.

[3955] FIG. 391 is a time chart showing the Layer 3 Bursty Err. process.

[3956] The above described Errored-PDU is counted as one error for a plurality of errors in a single L3-PDU, but an error notification is made from the SMLP each time an error occurs. On the other hand, a “1” is written to the E-PDU flag RAM if a burst error occurs in the RAM accessed using an address represented as a source SNI+MID. When an EOM is received, the RAM is read. Only if “1” is read, the Errored-PDU is incremented.

[3957] FIG. 392 shows the method of accessing the E-PDU flag RAM.

6.5. Protocol Performance Monitor in Egress Unit

[3958] 6.5.1. Process System

[3959] FIG. 393 shows the outline of the check items in the egress unit, the actions taken when an NG is detected, and the checking procedure. In FIG. 393, a unique use of the SBMESH is added for the TR-774.

[3960] The groups and Nos. are used similarly as shown in FIG. 384. The classification and the position of the groups are in accordance with the TR-774 for E and F. Other items are the same as those shown in FIG. 384.

[3961] Each parameter of groups B and G is not checked by the RMLP. Therefore, no error notification is made, but an area is reserved to count errors in the PWCB.

[3962] The process is performed by the HLM01A PWCB as described above. However, an error notification of each check made by the egress unit is received from the RMLP as described above.

[3963] The HLM01A furthermore receives data, cell frames, and enable frame signals from the PMLP. FIG. 394 is a time chart of each signal. FIG. 395 shows the explanation of each signal (the signals are the same as those received from the SMLP for the protocol performance monitor in the ingress unit).

[3964] The processes performed in the egress unit are basically indicated by each signal received from the SMLP in monitoring the protocol performance in the above described ingress unit.

[3965] The format of the portion 3τ corresponding to the ATM header is an internal format of the SBMESH, and does not completely match a common ATM header format. As shown in FIG. 394, the cell comprises a field (source MH ID) indicating the source MH of the cell and a field (destination SNI ID) indicating the destination SNI. The cell shown in FIG. 394 is an example of the SIP-BOM.

[3966] The error notifying method followed at an MRI timeout is similar to that of the ingress unit. That is, a pseudo EOM cell is generated in the RMLP, and an error notification indicating an MRI timeout is issued together with the cell. The destination SNI ID in the pseudo EOM cell is the same as that of the corresponding BOM.

[3967] FIG. 396 shows the method of identifying the segment type of a cell in the ST identification block shown in FIG. 379. Thus, combining the IST with the SST shown in FIG. 394 identifies the segment type of a cell.

[3968] Each of the blocks shown in FIG. 379 has the same function and operates the same way as those in the ingress unit.

[3969] The “trial” of the 1τ data 15 shown in FIG. 394 shows whether or not the cell is an MESH-MH VPC test cell. If the cell is an SNI-SBMESH PVC test cell or an MESH-MH PVC test cell, none of the processes relating to the egress protocol performance monitor are performed.

[3970] 6.5.2. Details of Processes

[3971] Since the processes are basically the same as those in the ingress unit, only a time chart of the L2/3 individual Err. count process is shown as FIG. 397.

7. NETWORK DATA CORRECTION

7.1. General Descriptions

[3972] The SBMESH corrects data for the L2-PDU and L3-PDU. The data correction is generally in accordance with the TR-774. The function of the data correction is realized by the HLM01A.

7.2. Network Data Correction Parameter

[3973] The SBMESH corrects network data of each of the following parameters for each SNI.

[3974] (1) Total originating individually addressed L3-PDUs

[3975] (2) Total Terminating individually addressed L3-PDUs

[3976] (3) Total originating L2 PDUs

[3977] (4) Total terminating L2 PDUs

[3978] (5) Total originating group addressed L3-PDUs

[3979] (6) Total terminating group addressed L3-PDUs

[3980] (7) Discarded L3 PDUs due to access class violations

[3981] (8) Discarded L3 PDUs in the Ingress Unit due to exceeding a predetermined maximum value for the number of data units

[3982] (9) Discarded L3 PDUs in the Egress Unit due to exceeding a predetermined maximum value for the number of data units

[3983] (10) Discarded L3 PDUs due to SA screening violations

[3984] (11) Discarded L3 PDUs due to DA screening violations

[3985] (12) Discarded L3 PDUs due to not assigning an SA to a source SNI

[3986] (13) Discarded L3 PDUs due to an unavailable destination SNI

[3987] The above listed (1) through (6) indicate the numbers of the L2 and L3 PDUs including the number of discarded L3 PDUs. In counting the PDUs in and after (7), the number of L3 PDUs discarded for various reasons is counted.

[3988] According to the TR-774, counting the number of L3 PDUs requires the following values.

[3989] Total originating (terminating) L3 PDUs

[3990] Total originating (terminating) group addressed L3 PDUs

[3991] On the other hand, the SBMESH counts each of the following numbers, and the software adds the counted numbers to obtain the total number.

[3992] Total originating (terminating) individually addressed L3 PDUs

[3993] Total originating (terminating) group addressed L3 PDUs

[3994] If an error notification is received from the SMLP or RMLP in the HLM01A of the SBMESH, the network data correction is performed for each of the parameters (1) through (13).

[3995] According to the TR-774, an interval is set as 15 minutes and various data for at least the past 2 intervals is stored.

[3996] The SBMESH provides two 15-minute counters for switching phases as in the configuration of the protocol performance monitor. Within 15 minutes after a phase switch instruction, the software receives and stores a count value from the 15-minute counter corresponding to the previous 15-minute register. That is, the software stores various data of at least the past two intervals.

[3997] According to the TR-774, each of the above listed parameters (7) through (13) requires a log at the occurrence of an error.

[3998] The log should contain the following data.

[3999] (a) Source address

[4000] (b) Destination address (including address type)

[4001] (c) SNI

[4002] (d) State code

[4003] (e) Date of error detection (represented by year, month, day, hour, minute, and second)

[4004] (f) Address screening

[4005] When a log object error occurs, the hardware sets the above listed (a) through (d) in the log register. The firmware reads the contents of the log from the register, and notifies the software of the read contents. The contents of (e) are not transferred from the hardware to the firmware. The contents are assigned the time information managed by the firmware when the firmware fetches the contents of the logs other than (e) and (f). However, the notification to the software does not contain the data of year, month and day, which is managed by the software. (f) is provided by the software, and each function of managing the log contents is realized by the software.

7.3. Network Data Correction in Ingress Unit

[4006] 7.3.1. Process System

[4007] In the parameters (1) through (13) to be corrected in the above described network data correction, the ingress unit processes 7 items, that is, (1), (3), (5), (7), (8), (11), and (12). In the 7 items, four items in and after (7) relate to errors and are processed as in the protocol performance monitor process of the ingress unit described in chapter 6.4.

[4008] The numbers of the L2 and L3 PDUs of (1), (3), and (5) are counted regardless of errors in the L2-PDU or the L3-PDU.

[4009] This process is performed by the HLM01A as described above, but an error notification of various checks of the ingress unit is received from the SMLP. The error notification is also used in the protocol performance monitor, and the process system is the same as the protocol performance monitor process.

[4010] Since the SBMESH receives data in the cell format, the number of L2-PDUs can be easily counted for each SNI, and the ST unit of the L2-PDU is analyzed. The number of L3-PDU is incremented in the case of an SIP-SSM or SIP-BOM. Simultaneously, the SA is analyzed to determine whether or not it is an individually addressed L3 PDU. As described above, half-encapsulated cells are received from the SMLP. However, the cells increased in number through the half-encapsulation are not counted.

[4011] As in the protocol performance monitor, none of the processes relating to the ingress network data correction are performed if the cell is an MESH-MH PVC test cell and a cell copied in the GA copy process.

[4012] The SA/DA accumulation RAM and each of the blocks for timing generation, SNI identification, SA/DA identification, error analysis, and RAM and counter are shared with the protocol performance monitor process. Each counter is the same as that in the protocol performance monitor process.

[4013] FIG. 398 is a time chart showing the process of correcting network data in the ingress unit.

[4014] 7.3.2. Details of Processes

[4015] If valid cells are received as other than inter-BOMs and incremented through the half encapsulation, the following processes are performed.

[4016] (1) (1) An L2 PDU count value is read from the count value storage RAM and incremented (+1).

[4017] (2) The incremented L2 PDU count value is stored in the RAM.

[4018] If an SIP-BOM or an SIP-SSM is received, the following processes are performed.

[4019] (1) An L3 PDU count value is read from the count value storage RAM and incremented (+1). At this time, the SA unit is analyzed to determine whether it is an individually addressed L3 PDU or a group address L3 PDU. The values are individually incremented.

[4020] (2) The incremented L3 PDU count value is stored in the RAM.

[4021] The following processes are performed if errors to be individually counted in the network data correction are reported.

[4022] (1) The incremented error count value is stored in the RAM.

[4023] Although the count value is represented by 32 bits, a reading and a writing operations to the RAM are separately performed each using 16 bits. The value is incremented for each source SNI, but is not incremented if the count value is a maximum value.

[4024] As described above, the L2 and L3 PDU are counted regardless of the existence of an error. The above described error count is not performed only when an error occurs. A parity bit is generated when a count value is stored and it is checked when it is read. FIG. 399 is a time chart showing the data correction process.

7.4. Network Data Correction

[4025] 7.4.1. Process System

[4026] In the parameters (1) through (13) to be corrected in the above described network data correction, the egress unit processes 6 items, that is, (2), (4), (6), (9), and (13). In the 13 items, three items in and after (9) relate to errors and are processed as in the protocol performance monitor process of the egress unit described in chapter 6.4.

[4027] The numbers of the L2 and L3 PDUs of (2), (4), and (6) are counted regardless of errors in the L2-PDU or the L3-PDU. This process is performed by the HLM01A PWCB as described above, but an error notification of various checks of the egress unit is received from the RMLP.

[4028] The error notification is also used in the protocol performance monitor. Other process systems are the same as the protocol performance monitor process. (The protocol performance monitor process is performed for each source MH. However, the network data correction process is performed for each destination SNI. Another difference is that an error type is accumulated for a log notification.)

[4029] Error types are accumulated on the following grounds. That is, a log is required for (9), (10), and (13) when an error is detected. The requirement includes an error type of the error. The error type is determined by the “Inter-BOM”. Since valid SA and DA are determined when the SIP-BOM is received, the error type should be accumulated.

[4030] Since the SBMESH receives data in the cell format, the number of L2-PDUs can be easily counted for each SNI, and the ST unit of the L2-PDU is analyzed. The number of L3-PDU is incremented in the case of an SIP-SSM or SIP-BOM. (Simultaneously, the SA is analyzed to determine whether it is an individually addressed L3 PDU or a group address L3 PDU. As described above, half-encapsulated cells are received from the RMLP. However, the cells increased in number through the half-encapsulation are not counted.)

[4031] As in the protocol performance monitor, none of the processes relating to the egress network data correction are performed if the cell is an SNI-SBMESH PVC test cell or an MESH-MH PVC test cell.

[4032] 7.4.2. Explanation of Process

[4033] The processes are the same as the network data correction process in the ingress unit except that cells are counted for each destination SNI.

8. BILLING FUNCTION

8.1. General Descriptions

[4034] According to the TR-775 (issued by Bell Communications Research) defines the billing process, the SBMESH performs the billing process only relating to a normally transmitted L3-PDU. This billing function is realized by the HLM00A.

8.2. Billing Process

[4035] FIG. 400 is a block diagram showing the billing unit. This billing unit performs a billing process in response to a notification from the RMLP.

[4036] A signal received from the RLML to the billing unit for use in the billing process is cell-formatted, but the cell received for use in the billing process does not contain an error. That is, when the RMLP detects an error, the related cell and the cells associated with the erroneous cell are not transmitted to the billing unit. For example, if an erroneous cell is the BOM of the L3-PDU, the COM and EOM in and after the L3-PDU are not transmitted to the billing unit. Therefore, the billing unit performs its billing process assuming that the received cells are all normal cells having no errors. Additionally, all cells received at the billing unit are half-encapsulated and their BOM contains the information about the SA and carrier in the original L3-PDU, while their EOM contains the information about the data length in the original L3-PDU.

[4037] As described in the general descriptions above, the billing process is performed on a normal L3-PDU (or cells forming parts of the normal L3-PDU). The TR-775 requires the following items.

[4038] (1) destination address DA

[4039] (2) source address SA

[4040] (3) SNI address

[4041] (4) state code

[4042] (5) segment count (number of L2-PDUs)

[4043] (6) packet count (number of L3-PDUs)

[4044] The billing process is performed at the destination equipment. The SNI address can be uniquely obtained by analyzing the destination address DA. Accordingly, the SNI address is obtained by analyzing the DA through the software. The state code indicates whether the billing data refers to a normal L3-PDU or a partially transmitted L3-PDU. Since the billing process is performed only on normal L3-PDUs as described above, the state code is simply defined.

[4045] Each parameter is accumulated in the L2-PDU, L3-PDU, SA, and carrier accumulation RAM shown in FIG. 400. Then the firmware fetches various data from the above listed items and transmits them to the software. The summary of the billing process is described below by referring to the cell format shown in FIG. 401.

[4046] If a half-encapsulated BOM is received by the billing unit, the 64-bit source address SA and the 50-bit carrier information are stored in the SA and carrier accumulation RAM (the I/O is separately processed in FIG. 401, but actually the I/O is processed collectively).

[4047] The 50-bit carrier information comprises a 16-bit ICI carrier ID, a 16-bit incoming network ID, a 16-bit incoming ICI TPS ID, and a 2-bit IIT.

[4048] The address in the above described accumulation RAM for storing data is represented as a 5-bit destination SNI ID and a 5-bit MIE in the BOM.

[4049] In the cell-formatted data from the RMLP, the destination SNI ID is an 8-bit field. However, only the lower order 5 bits are used if the maximum number of the SNI accommodated by each SBMESH is set to 32.

[4050] If a non-half-encapsulated BOM is received by the billing unit, a 9-bit RDA compressed from the 64-bit DA in the BOM and a D bit are stored in the SA, carrier and RDA accumulation RAM.

[4051] The reason for compressing the DA into 9 bits and the D bit are explained later. A storage address is similarly determined as described above using the destination SNI ID and MID in the cell as keys.

[4052] Thus, a RAM of the capacity of 2¹⁰(=1k)×128 bits is required to stored the above listed information. Physically, a 64k×16 bits RAM is enough to store the information. However, since 32 bits are operated in the hardware when the RAM is accessed, two 64k×16 bits RAM are required. FIG. 402 shows a model of data stored in the SA, carrier, and RDA accumulation RAM.

[4053] The destination address DA is compressed into 9 bits only when the number of individual addresses (IA) and group addresses (GA) for each SNI is limited to 8 each. That is, if there are 32 SNIs, a total of 512 addresses are managed, thereby representing each address by 9 bits.

[4054] Concerning the GA, the same DA can be defined for a plurality of SNIs. That is, a normal CAM may cause plural matchings. Therefore, a CAM is divided into blocks such that a single block has 8IA+8GA=16 matching patterns for corresponding SNIs. The SNI ID specifies in which block a specific matching is made. The matching pattern in a CAM is set by the firmware when a subscriber data is received. The interface with the firmware is realized through a command memory and a response memory.

[4055] FIG. 403 shows the image of the DA compression CAM. The DA compression CAM is used when a 64-bit destination address DA is received and a 9-bit RDA is generated as shown in FIG. 400. The firmware stores the correspondence among the RDA, SNI, ID, and DA. If none of the above described matching patterns match the received cell, a D bit is provided to indicate the presence/absence of matching for a compressed DA and stored in the DA, carrier, and RDA accumulation RAM. If the D bit indicates 1 (matching), the billing process is performed. If it indicates 0 (non-matching), the billing process is not performed.

[4056] The billing unit does not operate until a half-encapsulated EOM is received after the RDA is accumulated. Although the number of the L2-PDUs should be counted, it is not counted when the BOM is received (the SA, etc. is accumulated). The count of the L2-PDUs is described later.

[4057] The operation performed when the EOM is received is described by referring to FIG. 404.

[4058] First, the number of L2-PDUs is calculated from the data length information “length” of the L3-PDU in the EOM. The “length” uniquely matches the number of L2-PDUs. Therefore, when the billing unit receives an EOM, the length stored in the EOM is output as the length address as shown in FIG. 400. In FIG. 400, the 16-bit length is assigned as a ROM address. If the maximum value of the length is given, an appropriate number of bits can be assigned based on the maximum value. The length address is assigned a parity for use in a normality check so that a check is made when data is read from the ROM.

[4059] Concurrently read are the SA, carrier, and RDA preliminarily (for example, when a BOM is received corresponding to the EOM, etc.) stored in the SA, carrier, and RDA accumulation RAM using the destination SNI ID and MID of the EOM as addresses.

[4060] First, the 64-bit source address SA is compressed by the SA compression CAM shown in FIG. 400. A total of 256 matching patterns are managed and the compressed SA (RSA) is represented by 8 bits.

[4061] When data is input to the SA and carrier compression CAM, the data should be cell-formatted. Cells are formatted by the CLFM shown in FIG. 400. In the SA and carrier compression CAM, a total of 58 bits comprising the 8-bit RSA and 50-bit carrier are further compressed. In this example, 256 matching patterns are managed and the compressed SA and carrier (RSAC) are represented by 8 bits. The SA compression CAM, SA, and carrier compression CAM perform hardware autonomous operations.

[4062] Practically, it is checked whether or not the input SA and carrier pattern match the internally stored matching pattern. If a matching result is output, the register number is output as an RSA and an RSAC. If a non-matching result is output, the input SA and carrier pattern are entered in an available register, and the register number is output as an RSA and an RSAC. No interface is made with the firmware. (The interface is provided for maintenance).

[4063] Using a total of 17 bits comprising the thus obtained 8-bit RSAC and 9-bit RDA as an address, the L2-PDU, L3-PDU, SA, and carrier accumulation RAM shown in FIG. 400 are. accessed (the I/O is separately processed in FIG. 401, but actually the I/O3 is processed collectively).

[4064] Using the address, the number of the L2-PDUs is read, and the number is added to the L2-PDU forming the L3-PDU corresponding to the EOM. Then, the sum is stored again in the L2-PDU, L3-PDU, SA, and carrier accumulation RAM. Although not yet shown in the figures, the number of the L3-PDUs is read, incremented, and then stored again in the L2-PDU, L3-PDU, SA, and carrier accumulation RAM. Simultaneously, the 64-bit SA and 50-bit carrier are stored. The firmware accesses the L2-PDU, L3-PDU, SA, and carrier accumulation RAM to collect the billing information. Practically, there are two RAM to be switched by the firmware at predetermined time intervals (for example, every minute). In one phase the hardware accesses them, and in another phase the firmware fetches various data.

[4065] The bit width representing the numbers of the L2-PDUs and the L3-PDUs in the RAM is calculated according to the number of cells received in a predetermined time (for example, a minute).

[4066] Since half-encapsulated cells are received in the billing unit, an SSM is counted as 2. 11M cells of 2.7 μs are transmitted, thereby amounting to 24 bits as a bit width. The bit width for the number of the L3-PDUs requires bits smaller than 24.

[4067] Thus, the capacity of the RAM is 2¹⁷(128k)×128 bits for one phase. Physically, eight 512k×8 bits RAM is used for one phase. FIG. 405 shows the RAM for accumulating the billing data. The RAM is directly connected to the μ-p bus. The other phase of the RAM comprising two phases accesses a bank after adding +10 to each bank number.

[4068] FIG. 405 shows a parity bit for use in a normality check made when the hardware accesses the RAM. When the firmware reads data, no process is made. The parity bit is set to 1 when data is cleared.

[4069] In fetching billing data, the firmware recognizes the existence of a destination SNI ID and the DA assignment. Therefore, reading significant information only successfully shortens the operation time.

[4070] In this hardware configuration, 256 variations of the SA-carrier combination for each combination of the destination SNI ID and the DA. (The 256 variations assigned to the combination of one destination SNI ID and DA cannot be different from those assigned to the combination of another destination SNI ID and DA. That is, the 256 variations of the combination can be commonly assigned to the combination of all SNI IDs and DAs.) The maximum value and the number of variations of actual combination can be determined by reading the entries of matching patterns (autonomously made by the hardware) from the SA and carrier compression CAM shown in FIG. 400.

[4071] Thus, the user need not access all RSACs at lower order addresses, thereby reducing the data fetching time.

8.3. Checking Function

[4072] Various checking functions in the billing unit is described below by referring to FIG. 406.

[4073] FIG. 406 shows the output of checking results as follows.

[4074] As a checker in the μP unit, a watch dog timer check, a command response check, and a 16M clock checks are made (refer to the WDTO, CRNG, and CLKa).

[4075] A parity check, a clock check, and a CF check are made at the receiving equipment of the RMLP (refer to PCa, CLKb, and CLKc in FIG. 406).

[4076] A parity check is made for the compressed data entered through each CAM (refer to PCb, PCd, and PCf in FIG. 406).

[4077] A parity check is made for the compressed data output through each CAM (refer to PCc, PCe, and PCg in FIG. 406).

[4078] When data is read from each RAM and ROM, a parity check is made (refer to PCi and PCJ).

[4079] The L2-PDU, L3-PDU, SA, and carrier accumulation RAM are accessed by the hardware and firmware. The above listed parity checks are effective only when access is gained by the hardware, and no parity check is made while the firmware gains access to the L2-PDU, L3-PDU, SA, or carrier accumulation RAM.

[4080] In the RAM comprising two phases, the firmware performs a phase switching control and the hardware fetches data from the phase not accessing data. Since each CAM is provided with interface with the firmware, data is written, read, etc. at the diagnostics. In the compression normality check and the PDU number adding process using “Add” in each CAM, the above listed checks are not made, but a test cell is issued from the test cell generating unit at the diagnostics for detailed checks.

9. LPCOM UNIT (INF interface unit)

9.1. General Descriptions

[4081] The LP-COM unit has the following functions.

[4082] (1) interfacing with the INF and controlling the SMLP and RMLP

[4083] (2) performing an billing process

[4084] (3) performance monitor and data correction (traffic monitor)

[4085] Physically, the following 3 PWCBs are contained.

[4086] (a) HLP02A

[4087] (b) HLM00A

[4088] (c) HLM01A

[4089] The above listed functions (1) through (3) correspond to the PWCB of (a) through (c).

[4090] The billing processes are described in chapter 8, the performance monitor is described in chapter 6, and the data correction is described in chapter 7. Described below is the interfacing function, and the controlling function of the SMLP and RMLP, that is, the HLP02A.

9.2. Outline of Functions

[4091] FIG. 407 is a block diagram showing the HLP02A. FIGS. 408 and 409 shows the functions of each block of the HLP02A.

[4092] The detailed explanation of the functions of the HLP02A is illustrated in FIGS. 408 and 409. The important functions are interfacing with the INF, setting and managing in the LP and each table, and error monitoring and state controlling in the LP and LP-COM.

9.3. INF Interface Control Procedure

[4093] 9.3.1. INF Interface Control

[4094] Described below is the control procedure of the interface using the INF between the SBMESH (MNG-Firm) and the BCPR.

[4095] a. INF Command Activation

[4096] (1) DMA settings are made in the CPU (microprocessor).

[4097] (2) When the BCPR activates a command in an INF order, it specifies the MM address as being shifted 2 bits rightwards (0, 4, and 8 are shifted to 0, 1, and 2). Therefore, when the INF is received, the SBMESH performs the following operations.

[4098] 1. Upon recognition of the command activation, the MM address and the number of commands are received from port A of the SBIF LSI.

[4099] 2. The higher, middle, and lower bits of the MM address is inverted and set in port B of the SBIF LSI

[4100] 3. The transfer length (number of commands×4 words) is set in port F of the SBIF LSI.

[4101] 4. A DMA read start is set in port C of the SBIF LSI.

[4102] b. Notification of INF status

[4103] An MM address specified in a status notification is obtained by a 2-bit rightward shift (that is, 0, 4, and 8 are shifted to 0, 1, and 2 respectively) as specified in the reception buffer notification.

[4104] The message length is indicated as MSB for the left and LSB for the right in the BCPR memory.

[4105] The SBMESH performs the following operations.

[4106] (1) The higher, middle, and lower bits of the MM address is inverted and set in port B of the SBIF LSI

[4107] (2) The transfer length (number of commands×4 words) is set in port F of the SBIF LSI.

[4108] (3) A DMA read start is set in port C of the SBIF LSI.

[4109] The MM address and message length specified in the command and status are as follows.

[4110] (1) An MM address specified in a command is obtained by a 2-bit rightward shift.

[4111] (2) The message length is indicated as MSB for the left and LSB for the right in the BCPR memory.

[4112] In the status notification, the MM address is specified in the reception buffer notification.

[4113] The status queue address and the reception buffer address are as follows.

[4114] (1) The BCPR preliminarily notifies the SBMESH of the status queue and the MM address of the reception buffer.

[4115] (2) The MM address is specified as being shifted 2 bits rightwards.

[4116] (3) A byte length is specified as the message length.

[4117] 9.3.2. IPF Interface Interruption Control

[4118] Described below is the control of the interruption in controlling the INF interface in the SBMESH.

[4119] a. Command activation

[4120] A command is activated by an external interruption INTO. The interruption INTO is reset by a 3-word read of port A.

[4121] b. Transmission of status

[4122] A billing status is transmitted after being generated every minute by the ACC-firm. A log status (when a log object area is generated) is transmitted after being generated by the MSR-firm.

[4123] c. DMA control

[4124] The DMA is controlled by the DMA controller in the CPU. The available DMA channel is 0. The DMA is terminated by either an interruption or a look-in. An interruption is controlled by an INT bit of the DMA control register in the CPU.

[4125] Since the DMA transfer speed of the INF is 4 Mbytes/sec, a 4-byte read of the DMA (tail pointer, look-in, etc.) terminates in 1 μs if the CPU clock is operated by 8 Mhz. Accordingly, the DMA is not terminated by an interruption but by a look-in.

9.4. SMLP/RMLP Control

[4126] The control by the SMLP/RMLP is performed as follows.

[4127] The following state control information is provided by the HLP02A for the SMLP/RMLP.

[4128] ACT/SBY (active/standby) of home system

[4129] Shelf No. (0-3) of home shelf

[4130] Reset at initialization

[4131] Fault reset of each checker

[4132] Settings of each MSD table

[4133] Resetting of each MSD table

[4134] Hardware inhibit state signal (masking the operation of a hardware.

[4135] HLP02A collects the MSCAN information from each package of the SMLP/RMLP and monitors the states.

10. VARIOUS INTERFACES

10.1. General Descriptions

[4136] Described in this chapter is the logical interface among the blocks of the SBMESH (including the interface between the SBMESH and the ATM switch ASSW).

10.2. ASSW→SDMUX (HMX11A)

[4137] FIG. 410 shows the format of a cell (header field) to be input from the ASSW to the SDMUX (refer to FIG. 209 for the route).

[4138] The following three types of cells can be input from the ASSW to the SDMUX.

[4139] 1. Test cell from the TCG

[4140] 2. Signaling cell from the BSGC

[4141] 3. Normal user cell

[4142] For any of the above listed cells, the TAGA and TAGB specify a 622M highway to which a corresponding SBMH is connected. The TAGC also specifies the SBMESH in the SBMH (for example, 0, 1, 2, and 3 in the order from the nearest to the ASSW). Thus, the contents of the tag field are provided by the same method for any type of the cells. Other data are individually provided for each type as follows.

[4143] 1. Test cell from the TCG

[4144] O: 1 (O bit)

[4145] UL: 0

[4146] COM: 0

[4147] SIG: 0

[4148] VPI: 000(H)

[4149] VCI: 03FA(H) or 03FB(H)

[4150] 2. Signaling cell from the BSGC

[4151] O: 0

[4152] UL: 0

[4153] COM: 1

[4154] SIG: 1

[4155] VPI: 000(H)

[4156] VCI: 03FC(H) or 03FD(H)

[4157] 3. Normal user cell

[4158] O: 0

[4159] UL: 0

[4160] COM: 0

[4161] SIG: 0

[4162] VPI: 03F(H)

[4163] VCI: 03xy(H) (where xy indicates an SNI number.

[4164] For example, if the SNI number is 0, xy=00. If the SNI number is 31, xy=1F(H))

10.3. SDMUX (HMH11A)→SMLP (a) (HMH03A)

[4165] FIG. 411 shows the format of a cell to be input from the SDMUX to the SMLP(a). FIG. 411 specifically shows the portion referred to by the SMLP(a) (refer to FIG. 209 for the route).

[4166] The following two types of cells are input from the SDMUX to the SMLP(a).

[4167] 1. test cell from the TCG

[4168] 2. normal user cell

[4169] A signaling cell from the BSGC is not input to the SMLP(a).

[4170] If the 6th bit (O bit) in the first byte is set to 1, that is, if it is a test cell from the TCG, then the test cell is discarded in the SMLP(a) and is not an object of the process. If the bit is set to 0, that is, if it is a normal user cell, then the cell is not an object of the process in the SMLP(a). The VPI/VCI of the normal user cell are as follows.

[4171] VPI: 03F(H)

[4172] VCI: 03xy(H) (where xy indicates an SNI number as described in 10.2 above).

[4173] Thus, the VPI/VCI of a normal user cell is input as is to the SMLP(a) without being rewritten for the state input from the ASSW to the SDMUX. Therefore, the source SNI of the cell can be recognized by the VCI in the SMLP(a). The ST, SN, and MID are input as is, that is, as being input from a source subscriber (received by the SDMUX from the ASSW).

[4174] In the SMLP(a), processes are performed similarly on normal user cells and SNI-SBMESH PVC test cells.

10.4. LP-COM (HLP02A)→SMLP(a) (HMH03A)

[4175] FIG. 412 shows the format of the cell input from the LP-COM to the SMLP(a). FIG. 412 specifically shows the portion referred to by the SMLP(a) (refer to FIG. 209 for the route).

[4176] Cells input from the LP-COM to the SMLP(a) are test cells and classified into the following two types.

[4177] 1. MESH-MH PVC test

[4178] 2. diagnostics

[4179] The MESH-MH PVC test is conducted when data is mastered, while the diagnostics is performed in an OUS (out of services) state.

[4180] 1. in the MESH-MH PVC test

[4181] VPI: 03F(H)

[4182] VCI: 03FF(H)

[4183] 2. in the diagnostics

[4184] VPI: 03F(H)

[4185] VCI: 03xy(H) (where xy indicates an SNI number as described in 10.2. above).

[4186] The 6th bit in the first byte is set to 0.

[4187] In the case of 1 above, the VCI is set to a specific value not used for a normal user cell and identified in the SMLP(a). The value of the specific VCI is, for example, 03FF(H). That is, the value is set to 0000 0011 1111 1111 (B). The underlined 1 indicates that the present cell is the test cell.

[4188] In the case of 2 above, the VPI/VCI is set to represent the diagnostic cell as if it were a normal user cell from any SNI.

[4189] In 1 and 2 above, the ST, SN, and MID are appropriately assigned. However, the MID at the MESH-MH PVC test is set to 10 0000 0000 (the same value is set for the SSM).

10.5. SMLP(a) (HMH03A)→SMLP(b) (HMH04A)

[4190] FIG. 413 shows the format of the cell input from the SMLP(a) (HMH03A) to the SMLP(b) (HMH04A) (refer to FIG. 225 for the route).

[4191] IN the SMLP(a), the following processes are performed on the header field.

[4192] The ST, SN, and MID remain in the same state without rewriting the state input from the SDMUX or the LP-COM to the SMLP(a).

[4193] The SST and input MID are copies of the ST and MID respectively. The RVPI represents the 8 lower bits of the 12-bit VPI input from the SDMUX or the LP-COM to the SMLP(a). The RVCI represents the 8 lower bits of the 16-bit VCI input to the SMLP(a). The SNI-ID(1) represents the 4 higher bits of the RVCI and the SNI-ID(2) represents the 4 lower bits of the RVCI.

[4194] In the SMLP(a), a DA check is made for each cell. It is determined whether or not the cell is to be routed to its own MESH (whether or not the DA of the cell should be assigned to the SNI of a related MESH). If the cell should be routed to its own MESH, the X in the figure is 1. If the cell should not be routed to its own MESH, the X is 0. The process is performed in the SMLP(c), but the own-MESH routing process is not performed in the SMLP(d) (HMH05A). If the cell is input from the LP-COM in the MESH-MH PVC test as described above, then each MSB of the RVCI, and SNI-ID(1) in the figure indicates 1. Similarly, the MSB of the MID also indicates 1. A normal user cell (including an SNI-MESH-MH PVC test cell) is not specifically recognized as a cell from the LP-COM at the diagnostics (as if it were a cell from the SNI).

10.6. SMLP(b) (HMH04A)→SMLP(c) (HMH05A)

[4195] FIG. 414 shows the format of a cell input from the SMLP(b) (HMH04A) to the SMLP(c) (HMH05A) (refer to FIG. 225 for the route).

[4196] The difference from the 10.5. above is RMID. That is, the MSLP(b) generates an RMID (unique in its own SMLP) using the RVCI (indicating a source SNI number in this case) from the SMLP(a) and the MID (unique in the SNI).

[4197] Although an RMID field is represented by 10 bits, 9 lower bits are actually valid. (the RMID occupies up to 0-511(D)) If a cell is input from the LP-COM in the MESH-MH PVC test, no RMID is acquired.

[4198] As described above, if a cell is input from the LP-COM in the MESH-MH PVC test, each MSB of the RVCI and SNI-ID(1) indicates 1 (recognized by the SMLP(c)). Since no RMID is acquired in this case, the LPCOM assigns to the MID a value 512(H) other than the RMID 0 through 511(H).

10.7. SMLP(b) (HMH04A)→SMLP (HMH05A): MRI Timeout Dummy Cell

[4199] FIG. 415 shows the format of a timeout dummy cell input from the SMLP(b) (HMH04A) to the SMLP (HMH05A).

[4200] An IRI timeout check is made in the SMLP(b). If an NG is detected in the check, a dummy cell is transmitted to, for example, inform of the NG.

[4201] In FIG. 415, a blank indicates “don't care”. An area preceded by the header field also indicates “don't care”.

[4202] The ST and SST indicate EOMs. Other input MID, SNI-ID(1), (2), X, and RMID are assigned the value for the original EOM.

10.8. SMLP(c) (HMH05A)→SMLP(d) (HMH06A)

[4203] FIG. 416 shows the format of a cell input from the SMLP(c) (HMH05A) to the SMLP(d) (HMH06A) (refer to FIG. 225 for the route).

[4204] There are three differences from 10.6. above in the BC, RVCI′, and IST.

[4205] The SMLP(c) encapsulates a cell (error cells are not objects of the process).

[4206] 1 cell is added to the header field of the SIP-L3 PDU. Therefore, the IST of the added cell (I-BOM) indicates a BOM, and the original BOM (S-BOM) becomes a COM. The IST of the original SSM (S-SSM) becomes an EOM.

[4207] The SST is not rewritten, but holds the ST as the SIP-L2 PDU. (The SST of the I-BOM is a BOM).

[4208] The SMLP(c) also performs a routing process and the result is provided for the BC and RVCI′. (The routing process is also performed on error cells).

[4209] “BC” is short for broadcast, and specifies the existence of a copy of a cell in the SMLP(d) and a copy object MH. Refer to the following data for details.

[4210] BC=11(B): The cells are copied to all MH (all SBMH+all GWMH).

[4211] BC=01(B): The cells are copied to all SBMH.

[4212] BC=10(B): The cells are copied to all GWMH.

[4213] BC=00(B): No copies are required (if a destination MH can be specified.)

[4214] The RVCI′ reflects the routing process result, etc. as follows.

[4215] If a destination MH is specified as a result of the routing process, a destination MH ID is entered (The SBMH is 00-IF, and the GWMH is 40-5F (if no copies are required)).

[4216] If a destination MH cannot be specified as a result of the routing process, 00 is entered (if no copies are required).

[4217] “FF” is entered for an SNI-SBMESH PVC test cell (in this case, if BC=00 and the cell is an actual cell, the encapsulation process is performed on the present cell. The SMLP(c) recognizes that the DA of the present test PDU refers to a test DA, and sets the RVCI′ as FF.)

[4218] Thus, if the cell is input from the LP-COM of the MESH-MH PVC test, the MSB of the SNI-ID(1) indicates 1. However, this may be ignored in the SMLP(c), but processed as a normal user cell in the encapsulation process and routing process.

10.9. SMLP(c) (HMH05A)→SMLP(d) (HMH06A): I-BOM

[4219] FIG. 417 shows the format of a cell of an I-BOM input from the SMLP(c) (HMH05A) to the SMLP(d) (HMH06A). An I-BOM is generated as a result of the encapsulation process in the SMLP(c).

[4220] The contents of bytes 00 through 07 are the same as those described in 10.8. above. The contents of bytes 08 through 43 and bytes 52 and 53 are the same as the original S-BOM and S-SSM to generate the I-BOM. Therefore, bytes 44 through 52 are rewritten as follows.

[4221] These value indicate that the cells are issued from the SNI.

[4222] RV=all 0

[4223] The value is fixed.

[4224] The ES is 1 when the element type in the header extension of the SIP-L3 PDU is 1 (indicating a carrier selection). Otherwise, it is 0.

[4225] The carrier in FIG. 417 contains a carrier in the header extension of the SIP-L3 PDU when the carrier is selected. Otherwise, it contains a pre-selected carrier. If an NG is detected in the carrier screening process, 0000(H) is stored in this area.

[4226] If an error cell is detected, the above described process is not performed (no encapsulation process is performed).

10.10. SMLP(d)(HMH06A)→SMUX(HMX12A)

[4227] FIG. 418 shows the format of the cell input from the SMLP(d)(HMH06A) to the SMUX(HMX12A) (refer to SMLP→SMUX in FIG. 209 for the route).

[4228] In most cases, the contents received by the SMLP(d) from the SMLP(c) are passed. (Refer to the explanation in 10.8. for the SST, input MID, RVPI, and IST).

[4229] The areas of the SNI-ID(1) and (2), X, and BC are assigned in specific patterns as shown in FIG. 418.

[4230] The RVCI→ is a destination MH ID. (A cell requiring a copy when the SMLP(d) is input (RVCI′) is 00(H). After the cell is copied in the SMLP(d), a destination MH ID is assigned to each cell). The RVCI″ of the SNI-SBMESH PVC test cell is FF(H). (A cell received by the SMLP(d) from the WMLP(c) is passed.)

[4231] An output MID is uniquely assigned for each destination MH ID, but is not assigned to an error cell. Although 10 bits are reserved for an output MID field, 256 variations are actually supported per source MESH. At a destination MH, each MID area is separated from other areas in up to 4 source MESHes forming each source MH so that each MESH can be clearly identified as follows.

[4232] source MESH 0 (source MESH connected to the ASSW):

[4233] available MID 000-FF(H)

[4234] source MESH 1 (source MESH connected nearest to the ASSW after 0):

[4235] available MID 100-1FF(H)

[4236] source MESH 2 (source MESH connected nearest to the ASSW after 1):

[4237] available MID 200-2FF(H)

[4238] source MESH 3 (source MESH connected nearest to the ASSW after 2):

[4239] available MID 300-3FF(H)

[4240] The SN of the I-BOM generated in the encapsulation process in the SMLP(c) is a copy of the SN of the original S-BOM or of the S-SSM.

[4241] The MESH-MH PVC test cell may be ignored in the SMLP(d) and processed as if it were a normal user cell.

[4242] 0000+RVPI shown in FIG. 418 corresponds to the VPI. Since the RVPI represents 8 lower bits of the 12-bit VPI received by the MSLP(a) from the SDMUX or the LP-COM, the VPI of the cell transferred from the SMLP(d) to the SMUX is 03F(H).

[4243] 0000+0011+RVCI″ shown in FIG. 418 corresponds to the VCI. RVCI″ indicates a destination MH ID as described above, and the destination MH ID is 00-1F for the SBMH and 40-5F for the GWMH as described in 10.8. above. As a result, the VCI of the cell to be transferred from the SMLP(d) to the SMUX is represented as follows.

[4244] VCI: 03xy(H) where xy indicates a destination MH ID. (xy=00, . . . when the SBMH indicates 0; xy=IF, . . . when the SBMH indicates 31; xy=40, . . . when the GWMH indicates 0; and xy=5F when the GWMH indicates 31.)

[4245] An SNI-SBMESH PVC test cell is discarded in the SMUX and not output to the ASSW.

10.11. SMLP(d)(HMH06A)→LP-COM(HLP02A, HLM01A)

[4246] FIG. 419 shows the format of the cell input from the SMLP(d)(HMH06A) to the LP-COM(HLP02A, HLM01A).

[4247] In most cases, the contents received by the SMLP(d) from the SMLP(c) are passed. Refer to the explanation in 10.10. for the SST, input MID, RVPI, RVCI″, SN, and output MID.

[4248] The difference from the contents in 10.10. above is as follows.

[4249] CP indicates 0 for original data and 1 for copied data.

[4250] The HMH06A controls data including erroneous data. The HLM01A counts only original cells for L3, L2, error, and GA.

[4251] The LHP02A requires only an SNI-SBMESH PVC -test, but transmits normal user cells. As described above, the RVCI″ of a user cell indicates a destination MH ID (00-1F and 40-5F) and can be distinguished from the RVCI″ of a test cell indicating FF.

[4252] The HLM01A counts errors for the protocol performance monitor and also counts the PDU for the network NW data correction. Data are counted for each source SNI according to the source SNI number obtained from the SNI-ID as described above.

[4253] An error log requires not only a source SNI number but also an ID of a cell from the source SNI. Accordingly, an input MID is analyzed using the MID of the PDU transmitted from the source SNI.

[4254] The RVCI″ of an SNI-SBMESH PVC test cell indicates FF as described above. The MSB of the SNI-ID(1) in the MESH-MH PVC test cell is 1.

10.12 SMUX(HMX12A)→ASSW

[4255] FIG. 420 shows the format of a cell output from the SMUX to the ASSW (refer to FIG. 209 for the route).

[4256] The following two types of cells are output from the SMUX to the ASSW.

[4257] 1. test cell to the TCG

[4258] 2. normal user cell

[4259] A normal user cell is input from the SMLP(d) to the SMUX and assigned additional data or converted in the VCC of the SMUX so as to be represented in the format shown in FIG. 420. The SBMESH is independent of the value of each parameter, and the value is not defined here. A MESH-MH PVC test cell is processed similarly to a normal user cell in the above described points.

[4260] A test cell to the TCG is input from the RDMUX to the SMUX and assigned additional data or converted in the VCC of the SMUX so as to be represented in the format shown in FIG. 420.

10.13 ASSW→RDMUX(HMX10A)

[4261] FIG. 421 shows the format of a cell output from the ASSW to the RDMUX (refer to FIG. 209 for the route).

[4262] The following two types of cells are output from the ASSW to the RDMUX.

[4263] 1. test cell to the TCG

[4264] 2. normal user cell

[4265] Either of the above listed two types of cells specifies a 622M highway to which the SBMH is connected at the TAGA and TAGB. The TAGC depends on each type and requires other parameters as follows.

[4266] A MESH-MH PVC test cell is equivalent to a normal user cell.

10.14 RDMUX(HMX10A)→RMLP(a)(HMH00A)

[4267] FIG. 422 shows the format of a cell input from the RDMUX(HMX10A) to the RMLP(a)(HMH00A) (refer to FIG. 209 for the route).

[4268] The RDMUX is provided only for the interface with the ASSW and transmits data received from the ASSW to the RMLP(a) without rewriting the data.

[4269] A test cell from the TCG is also input to the RMLP(a) and discarded not to be processed. A normal user cell (including a MESH-MH PVC test cell) having 0 in 0 bit is an object of the process of the RMLP(a). The VPI and VCI of the cell are listed as follows.

[4270] VPI: 03F(H)

[4271] VCI: 03xy(H) where xy indicates a source MH ID (SBMH: 00-1F and GWMF: 40-5F)

[4272] A source MH can be specified using the VCI. The ST, SN, and MID are assigned at the MH and entered as is.

10.15 RMLP(a)(HMH00A)→RMLP(b)(HMH01A)

[4273] FIG. 423 shows the format of the cell input from the RMLP(a)(HMH00A) to the RMLP(b)(HMH01A) (refer to FIG. 181 for the route).

[4274] The RMLP(a) passes the contents received from the RDMUX almost without rewriting them. Only the contents to be rewritten By the RMLP(a) are the IST, DM, and RDA.

[4275] The IST is a copy of the ST.

[4276] The RMLP(a) refers to the DA of an input PDU and determines whether or not it should be fetched into its own MESH. The determination is made at the DA in the I-BOM (also I-SSM). The determination result is reflected on the DM and RDA as follows.

[4277] If the IBOM and ISSM are to be fetched to its own MESH;

[4278] DM=1

[4279] RDA: for use in its own MESH (DA ID image in its own MESH

[4280] If the IBOM and ISSM are not to be fetched to its own MESH;

[4281] DM=0

[4282] RDA: don't care

[4283] The above listed values are for the IBOM and ISSM. The ICOM and IEOM indicate “don't care” for the DM and RDA (regardless of fetching them).

[4284] There are two types of MESH-MH PVC test cells, that is, cells provided with a specific test DA and those provided with an allotted DA. The RDA of the IBOM of the former type test cell indicates IFF(H).

10.16 LP-COM(HLP02A)→RMLP(b)(HMH01A)

[4285] FIG. 424 shows the format of a cell input from the LP-COM(HLP02A) to RMLP(b)(HMH01A) (refer to FIG. 209 for the route).

[4286] There are two types of test cells input from the LP-COM to the RMLP(b).

[4287] 1. SNI-SBMESH PVC test

[4288] 2. diagnostics

[4289] The SNI-SBMESH PVC test is conducted when data is mastered, while the diagnostics is performed in an OUS (out of services) state.

[4290] The VPI and VCI are listed below.

[4291] 1. in the SNI SBMESH PVC test

[4292] VPI: 03F(H)

[4293] VCI: 03FF(H)

[4294] 2. in the diagnostics

[4295] VPI: 03F(H)

[4296] VCI: 03xy(H) where xy indicates an MH ID (SBMH: 00-1F and GWMH: 40-5F)

[4297] In the case of 1 above, the VCI is set to a specific value and identified in the RMLP(b). That is, the value of the specific VCI is set to 03FF(H)=0000 0011 1111 1111 (B). The underlined 1 indicates that the present cell is the test cell.

[4298] In the case of 2 above, the VPI/VCI is set to represent the diagnostic cell as if it were a normal user cell from a source MH.

10.17 RMLP(b)(HMH01A)→RMLP(c)(HMH04A)

[4299] FIG. 425 shows the format of the cell input from the RMLP(b)(HMH01A) to the RMLP(c)(HMH04A) (refer to FIG. 282 for the route).

[4300] The RMLP(b) performs the following various processes on the header field of a cell as shown in FIG. 282. The RMLP(b) receives IST, DM, and SN and uses them as is.

[4301] The PL is the contents of the 4 higher bits of the 6-bit payload length field. The 9 lower bits of the 10-bit RDA are valid and actually used as an RDA′.

[4302] A source MH ID is represented by a source MH ID(1) and (2). The 8 lower bits of the VCI described in 10.16 above normally indicates the ID. The 4 higher bits of the 8 bits represent the source MH ID(1), and the 4 lower bits represent the source MH ID(2).

[4303] The BRLC field is assigned a BRLC number (exactly an umbilical link number) obtained in the RMLP(b) and is to be reached by the present cell.

[4304] Likewise, the RVCI is assigned the destination SNI ID of the present cell. The RVCI of a MESH-MH PVC test cell (using a specific DA) indicates FF(H).

[4305] The SST is assigned the ST without encapsulation (that is, back in the SIP).

[4306] The RMLP(b) generates and assigns an RMID (unique in the present RMLP) using a received VCI (corresponding to a source MH ID) and a MID (unique in a source MH). If no RMID can be assigned (the EFMN or EFMD is set ON), the RMID indicates “don't care” and the RVCI is set to EO(H).

10.18 RMLP(b)(HMH01A)→RMLP(c)(HMH04A): MRI Timeout Dummy Cell

[4307] FIG. 426 shows the format of the timeout dummy cell transferred from the RMLP(b)(HMH01A) to the RMLP(c)(HMH04A) (refer to FIG. 282 for the route).

[4308] An MRI timeout check is made in the RMLP(b). If an NG is detected in the check, a dummy cell is transmitted as an NG notification, etc.

[4309] The RVCI contains a destination SNI ID. (The 5 higher bits are all 0). Refer to 10.17 above for the RMID.

[4310] In FIG. 426, the contents of the blank portion and the area preceded by the header field are “don't care”.

10.19 RMLP(c)(HMH04A)→RMLP(d)(HMH02A)

[4311] FIG. 427 shows the format of a cell input from the RMLP(c)(HMH04A) to the RMLP(d)(HMH02A) (refer to FIG. 282 for the route).

[4312] Each of the parameters shown in FIG. 427 are passed in the RLMP(c). Therefore, the contents output by the RMLP(b) are inherited as is by the RMLP(d). (The above described MRI timeout dummy cell is also passed).

10.20 RMLP(d)(HMH02A)→LP-COM(HLP02A, HLM00A)

[4313] FIG. 428 shows the format of a cell to be input from the RMLP(d)(HMH02A) to the LP-COM(HLP02A, HLM00A).

[4314] The HLP02A requires a test cell used in the diagnostics and the MESH-MH PVC test (when an allotted DA is used). No error cells are output from the RMLP(d).

[4315] An output MID is assigned such that it indicates a unique value for the destination SNI. Although 10 bits are reserved for the output MID, only the 5 lower bits are actually used and the 5 higher bits are set to all zero (the 5 lower bits are also set to all zero for the S-SSM). The 5 lower bits represent an output MID′.

[4316] The present cell remains encapsulated If a specific DA of the MESH-MH PVC test is used, the RDA (RDA′ when input to the RMLP(d)) indicates IFF(H), while the RVCI indicates FF(H). These are determined in the RMLP(d) and the cell is prevented from being output.

[4317] The HLP02A requires receiving a test cell in the diagnostics and the MESH-MH PVC test (using an allotted DA). Since a user cell input from the ASSW to the RMLP is rejected during the diagnostics, a test can be conducted. (A cell is fetched according to the RVCI). A cell is also fetched according to the RVCI in the MESH-MH PVC test (using an allotted DA). The RVCI indicates a destination SNI ID.

[4318] The HLM00A requires receiving a billing cell. Billing data contains a destination SNI number which can be determined by the RVCI.

[4319] A billing operation is performed on an incoming cell during the diagnostics. There is no problem during the diagnostics because the MESH is in the OUS state. The billing operation is also performed on the SNI-SBMESH PVC test cell, but the billing data is ignored because the SNI is blocked.

[4320] The billing operation is also performed on the MESH-MH PVC test cell (using an allotted DA), but the billing data is ignored according to the specific SA.

10.21 RMLP(d)(HMH02A)→LP-COM(HLP02A, HLM01A)

[4321] FIG. 429 shows the format of a cell input from the RMLP(d)(HMH02A) to the LP-COM(HLP02A, HLM01A).

[4322] The HLP02A requires a diagnostic test cell and a MESH-MH PVC test cell (using a specific DA), and the HLM01A requires a PM/TM cell. All cells (encapsulated) including erroneous cells are output to the necessary interface.

[4323] The units shown in FIG. 429 are those input to the RMLP(d).

[4324] The HLP02A requires receiving a test cell in the diagnostics and the MESH-MH PVC test (using a specific DA). Since a user cell input from the ASSW to the RMLP is rejected during the diagnostics, a test can be conducted. (A cell is fetched according to the RVCI).

[4325] As described above, when a specific DA of the MESH-MH PVC test is used, the RDA (the RDA′ when input at the RMLP(d)) indicates IFF(H), while the RVCI indicates FF(H).

[4326] Although cells are received during the MESH-MH PVC test (using an allotted DA), HLP02A does not operate in a cell reception mode. Furthermore, cells can be input as SNI-SBMESH PVC test cells. Likewise, the HLP02A does not operate in the cell reception mode.

[4327] The HLM01A requires receiving a PM/TM cell. The PM uses a source MH while the TM uses a destination SNI according to the a source MH ID (1), (2), and RMCI.

[4328] Various operations are performed on received cells during the diagnostics, but the MESH is in the OUS state.

[4329] The 8 lower bits of the VCI input from the RMLP(b) are copied to the source MH ID (1) and (2). Since no PM/TM operations are performed in the SNI-SBMESH PVC test cell, the MSB of the source MH ID(1) of the test cell is set to 1.

[4330] The RVCI indicates FF(H) in the MESH-MH PVC test (using a specific DA). According to the value, the data is masked in the PM/TM operations.

10.22 RMLP(d)(HMH02)→RMUX(HMX12A)

[4331] FIG. 430 shows the format of a cell input from the RMLP(d)(HMH02) to RMUX(HMX12A) (refer to FIG. 209).

[4332] The interface ignores the encapsulation, and no erroneous cells are output.

[4333] The cells are similar to those in 10.20 above. The source MH ID (1), (2), and the BRLC area are specified parameters as shown in FIG. 430.

[4334] The area of 0000 0011 1111 corresponds to the VPI, that is, 03F(H). 0000 0011 RVCI corresponds to the VCI.

[4335] The RVCI indicates a destination SNI ID, that is, in the range of 0300 through 031F.

[4336] The MESH-MH PVC test cell is not transmitted from the interface. Practically, the MSB of 1 is detected in the RVCI, and the test cell is identified. A cell having an allotted DA is transmitted to the RMUX, and the cell is also output to the ASSW. During the test, the SNI is blocked.

10.23 RMUX (HMX12A)→ASSW

[4337] FIG. 431 shows the format of a cell output from the RMUX (HMX12A) to the ASSW (refer to FIG. 209 for the route).

[4338] There are the following 3 types of cells to be output from the RMUX to the ASSW.

[4339] 1. test cell to the TCB

[4340] 2. signalling cell to the BSGC

[4341] 3. normal user cell

[4342] A normal user cell is input from the RMLP(d) to the RMUX, assigned various data and converted into a specific format, resulting in the format shown in FIG. 431. The value of each parameter is ignored by the SBMESH and therefore is not defined here (the descriptions are also applied to the SNI-SBMESH PVC test cell).

[4343] A test cell to the TCG is input from the SDMUX to the RMUX, assigned various data and converted into a specific format, resulting in the format shown in FIG. 431. The value of each parameter is ignored by the SBMESH and therefore is not defined here.

[4344] A signalling cell to the BSGC is also ignored by the SBMESH and therefore is not defined here.

10.24 Error Flag (at SMLP)

[4345] FIG. 432 shows the error flag at the SMLP.

10.25 Error Flag (at PMLP)

[4346] FIG. 433 shows the error flag at the RMLP.

11. SOFTWARE INTERFACE

11.1 Initialization

[4347] The following 2 types of initialization are performed by the SBMESH on the software.

[4348] 1. initialization of the MH-COM

[4349] 2. initialization of the LP unit

[4350] The initialization is performed through the LAP in 1, and through the INF in 2. The initialization is performed on the entire SBMESH in the order of 1 and 2.

[4351] Each of the following cases is described below.

[4352] 11.1.1. Initialization of MH-COM

[4353] (1) Procedure of the initialization of the MH-COM

[4354] FIG. 434 is a flowchart showing the initialization of the HM-COM.

[4355] 1. The intra-station LAP is established simultaneously in the ACT and the SBY.

[4356] 2. An individual reset request (ROW0:D6) is issued from the ACT and SBY. Simultaneously, the reset timer (set to 1 minute for timeout) is started.

[4357] 3. The MH-COM is set as a reset state and the intra-station LAP is disconnected. As a result, the BCPR detects the disconnection of the intra-station communications link. However, the BCPR continues transmitting a request to establish an intra-station communications link until the reset timer indicates timeout (the BSGC continues transmitting the SABM).

[4358] 4. The MH-COM returns an UA in response to the SABM received after the system is reset. Thus, the intra-station communications link is established again.

[4359] 5. The BCPR issues a COM-EMSCN read request command (COM-EMSCN-RD-RQ). A response is returned from the MH-COM (COM-EMSCN-DAT-RP). At this time, the E-MSCN are all masked and the EMSCN bits received by the BCPR are all OK.

[4360] 6. The BCPR sets the mask pattern according to the COM-E-MSD (ROW 180 through 195).

[4361] 7. The BCPR sets a threshold according to the COM-E-MSD if necessary (ROW 36 through 51).

[4362] 8. If the reset timer indicates timeout before the reset is completed, the reset is rejected as a fault.

[4363] (2) Intra-station communications

[4364] The intra-station communications is explained by referring to FIG. 435. FIG. 436 shows an example of the VPI/VCI of the intra-station communications cell.

[4365] A simple LAP procedure is used in the intra-station communications. The E-MSD/E-MSCN and device control relating to the MH-COM are all processed in the simple LAP procedure. The LP and the LP-COM are not controlled.

[4366] Logically, a communications link is set between the BSGC-MH-COM. However, since the MH-COM is duplex, each of the systems has its own communications link. As shown in FIG. 435, the highway of one system contain the intra-station communications cells (ATM cells from simple LAPs) of both systems in BSGC-MH-COM and MH-COM-BSGC.

[4367] The VCI values of the cell in BSGC-MH-COM are different in the two systems. The value is fixed in each system. The MH-COM receives an intra-station communications cell for its own system only according to the VCI, and discards the cells of the other system.

[4368] Although the cell of the MH-COM-BSGC has the same VCI value in the two systems, different COM bits in the ATM are used in the two systems. (If a cell is an intra-station communications cell for its own system, the COM is assigned 1. If it is a cell for the other system, the COM is assigned 0.) The BSGC terminates only the cells to be terminated by itself according to the COM bits and discards the cells for the other system.

[4369] The BSGC can be accommodated in either of the sides 0 and 1 of the ASSW. The SBMESH is connected to both sides 0 and 1 of the ASSW, but the intra-station communications link is established to the BSGC on side O only as shown in FIG. 437.

[4370] Up to 4 SBMESHs are cascade-connected to a 622 Mbps highway in a daisy chain. When a plurality of SBMESHs are connected to a highway, an intra-station communications link is set for each SBMESH. At this time, the VPI/VCI value of the intra-station communications cell of the BSGC-MH-COM is common, but the TAGC value depends on each device.

[4371] The MH-COM obtains the TAGC value (tag C) of the cell to be fetched by itself according to the shelf number of the SBMESH in which it is accommodated, and then fetches the corresponding cells.

[4372] As described above, the MH-COM determines the operation to be performed when a cascade-connection is made according to a TAGC value. The UL under the control of the ATM is not used (fixed at “0”).

[4373] The shelf number of the SBMESH is 0 for a single SBMESH. Each time an SBMESH is added, the value is incremented by 1. The shelf number and the TAGC value of the BSGC-MH-COM intra-station communications cell match each other as shown in FIG. 438.

[4374] (3) Setting a private line

[4375] Private lines (PVC) connect the SNI to MESH, MESH to MH, and MESH to SNI. The private lines are set immediately after the initialization. Described below is the tag field. The VPI/VCI of the private line is described in Chapter 2.

[4376] SNI→MESH

[4377] The SBMESH accommodating the SNI is specified using a tag. (It is assumed that the TAGA and TAGB specify the 600 M highway connecting a predetermined SBMESH.)

[4378] FIG. 439 shows the tag field of the MESH input cell specifying the SBMESH. A predetermined tag specifies the route from the SNI in the BRLC to the host, and assigns the tag if it is routed to the MESH in the host.

[4379] MESH→MH

[4380] The SBMESH (0-3) is not specified, but the SBMH is specified. That is, the 600 M highway of the SBMH corresponding at TAGA and TAGB is specified. FIG. 440 shows the tag field of the cell specifying a specific SBMH.

[4381] MESH→SNI

[4382] The SNI is specified using a tag. The detailed explanation is omitted here.

[4383] The VCC should also be set for a periodical test path using a tag in addition to the case above. The setting of the VCC of the test cell path for use in this test is set and released each time the test starts and terminates respectively.

[4384] 11.1.2 Initialization of LP Unit

[4385] The LP unit starts various processes upon receipt of the online operation activation. The subscriber data, etc. are transmitted later to the LP unit. Accordingly, various types of errors may occur (not hardware error, but protocol performance monitor errors, etc.). To prevent the errors, software processes are performed. The processes are explained by referring to FIG. 441.

[4386] The statistic time information entry 1 shown in FIG. 441 is transmitted in response to the online operation response status from the LP unit. The statistic time information entry 2 is transmitted every 15th minute. Although the subsequent entries are not shown in FIG. 441, they are transmitted every 15th minute. The interval between the 1 and 2 above can be variable in the range from 0 to 14 minutes.

[4387] Although a normal cell is input to the SBMESH in the period (period 3 in FIG. 441) from the online operation activation to the completion of the entry of the subscriber data and various station data as described above, no subscriber data or station data are set. Therefore, error may occur relating to the protocol performance monitor or network data collection, and the error counting starts and may generate a TCA. The error log can-be transmitted from the firmware to the software depending on the error type. Accordingly, the software ignores the error log for period 3, and processes the error log for period 5 as a correct record.

[4388] Since the error count in period 3 is not guaranteed, various count values and TCA in the period (period 4 shown in FIG. 441) up to the statistic time information entry 2 (to be exact, the collecting phase switch) should be ignored.

[4389] Subscriber data entry

[4390] Subscriber data entry commands are processed in SNI units, and are transmitted to an SBMESH for the SNIs (up to 32 SNIs) accommodated in the SBMESH.

[4391] The firmware has all SNIs blocked by default. The block is released for the subscriber who has sent the command as being a subscriber accommodated in the home SBMH. These processes are performed when the process request indicates “add/modify”. If this command indicates “delete” as a process request during the operation, the corresponding SNI is blocked. A single SNI block entry command and SNI block entry release command can block/block-release a plurality of SNIs. Such a command is received to block/block-release SNIs, but it is not generally used to delete/add SNIs, but used to temporarily block the SNI for any factor or release the temporary block.

[4392] Using this command, up to 16 individual addresses, 48 group addresses, 128 screening addresses, and 16 blocking carriers can be set per SNI.

[4393] The same GAID can be assigned to plural SNIs within a single GA (also to plural MESHs and MHs within the same SS).

[4394] At the initialization, the addresses are set for all accommodated SNIs. When SNIs are added or deleted during the operation, the addresses are set for only the corresponding SNIs by this command. When each parameter is altered for an SNI during the process, only the parameter corresponding to the SNI is set by this command (the command alters a parameter to be modified and sends those as is without rewriting them). The following points should be carefully considered when an individual address or group address is deleted.

[4395] FIG. 442 shows an example of deleting C in A, B, C, and D entered as individual addresses.

[4396] Normally D replaces C, but actually the C to be deleted in FIG. 442 is filled with 0 and transmitted. This restriction is placed on the individual address and group address. The screening address and blocking carrier are “filled” when they are deleted.

[4397] The above described restriction is derived from the billing unit. If Ds are filled instead of “all 0s” in the above described example, the billing data for C cannot be distinguished from that for D from the point when Ds are filled to the point when the next billing data is transmitted to the software. Otherwise, the “all 0” can be replaces with newly entered addresses after C is set to all 0 and the billing data for C is then fetched. If an SNI is added or deleted, and if a parameter is changed for an individual address, etc. of an existing SNI using the subscriber data entry command, then an error may occur in the protocol performance monitor, etc. as in the initialization. Thus, the TCA can be generated and a log can be made depending on the type of error. Therefore, an error at the initialization is ignored through the software.

[4398] If an SNI is added or deleted during the operation, an error can be expected. However, since a large-scale error is not estimated, it is recognized as an error and a resultant TCA and log are accepted. Various station data entries

[4399] Station data can be entered using the following commands.

[4400] (1) Station data (individual) entry command

[4401] (2) Station data (group) entry command

[4402] (3) Station data (MH) entry command

[4403] (4) Station data (GWMH) entry command

[4404] (5) Station data (intra-station number) entry command

[4405] (6) Station data (β) entry command

[4406] (1) Station data (individual) entry command

[4407] The unit of this command is SBMESH, and an individual address supported by the SBMESH specified by the parameter (MHAT+MHID+MESHID) in the command is reported.

[4408] Therefore, at the initialization of an SBMESH, this command related to all SBMESHs in the SS including the SBMESH is transmitted to the SBMESH. When there are 32 MHs in the SS and each MH has four SBMESHs connected in a daisy chain, the command is transmitted 128 times to the SBMESH, and transmitted totally 128²times at the initialization of the system.

[4409] If an amendment is made to an individual address of the SNI accommodated in an SBMESH, the amendment is reported in this command to the SBMESH.

[4410] A parameter (MHAT+MHID+MESHID) and a subscriber identifier are used in a plurality of commands, and the parameter commonly used in such plural commands is assigned as commonly recognized.

[4411] An address identifier is assigned to an individual address for the SNI specified by the (MHAT+MHID+MESHID+subscriber identifier).

[4412] The individual address specifying field in the subscriber data entry command can specify 16 individual addresses, sets to 0 the identifier of the individual address first specified in the command message for the SNI, and sequentially sets 1, 2, . . . , 15.

[4413] This command is used to set the routing table in the SMLP. One method is to analyze all DAs in the routing table. The number of command transmissions can be reduced depending on the system configuration. For example, assume that the routing table supports only for 4 SBMH×4 SBMESH×32 SNI×4 IA.

[4414] Even if the system accommodates 32 SBMH and each SBMH comprises 4 SBMESHs, only 0-3 MHIDs can be set on the table. Therefore, the command can be transmitted only 4 SBME×SBMECH=16 times to an SBMESH, and can be totally transmitted only 16×128 times. The number of individual addresses defined in each command can be 21 SNI×4 IA=128.

[4415] Assume that there are 6 SBMHs A, B, C, D, E, and F in the system, there is heavy traffic in the group of A, B, C, and D and in the group of E and F, and there is little traffic between the groups. If an IA for 4 SBMHs is automatically transmitted to all MHs using this command, the group of A, B, C, and D can specify the DA. The group of E and F cannot specify the DA and accept the broadcast. In this case, if an IA for the 4 SBMHs of A, B, C, and D is transmitted to A, B, C, and D, and an IA for the 2 SBMH of E and F is transmitted to E and F using this command, then the group of E and F can also specify the DA, thereby reducing the broadcast.

[4416] (2) Station data (group) entry command

[4417] This command reports the correspondence between the GAID and the group address. Since this command is not used in the SBMESH, there is no need to transmit it to the SBMESH.

[4418] (3) Station data (MH) entry command

[4419] This command is used to assign to an SBMESH a band between the SBMESH and each SBMH (including the SBMESH) and GWMH (SMLP→RMLP). (Simultaneously, the implementation/non-implementation information of each SBMH and GWMH is assigned). The command is transmitted once for each SBMESH.

[4420] This command is transmitted to an SBMESH and another SBMESH with the same implementation/non-implementation information for each SBMH and GWMH and normally different values of band.

[4421] When an amendment is made to a band, it is reported by this command to the corresponding SBMESH. Since this command cannot report only amended portions, non-amended portions are unnecessarily reported. If one of the SBMHs or GWMHs is extended, this command reports it to all SBMESHs.

[4422] At the initial stage, the software does not control the band between the MESH and MH, and the entire bus is reported as a full 155 M band. This command is transmitted in such a case. Since this command reports the MH implementation information as well as the band to the MESHs, the firmware cannot operate by default.

[4423] (4) Station data (GWMH) entry command

[4424] This command reports the correspondence between the GWMH and the number of the station in the LATA under the GWMH (and the number ID of the station in the LATA). The same command is transmitted to all SBMESHs. The number of the station in the LATA under the GWMH refers to the same LATA and is assigned to a separate SS. It does not include the station number of the SS in the home system. This number is defined as an intra-station number described below.

[4425] This command is issued for each SBMESH. When a change occurs, the changed portion is reported to all SBMESHs. The command is used to set a routing table in the SMLP. One command can report up to 512 LATA intra-station numbers. The command format is defined such that the 512 types optionally correspond to the GWMHID. If there are a small number of station numbers supported by the routing table, the command length can be reduced.

[4426] (5) station data (intra-station number) entry command

[4427] This command reports the correspondence between the intra-station number and the intra-station number ID. The same command is issued to all SBMESHs.

[4428] This command is issued for each SBMESH. When a change occurs, the changed portion is reported to all SBMESHs.

[4429] (6) Station data (p) entry command

[4430] This command reports the correspondence between the BRLC number, umbilical link number and β which is a restriction value of the traffic in the umbilical link.

[4431] Although this command is issued once for each SBMESH, the contents of the report for each SBMESH are different from those for each other. When a change occurs, the changed portion is reported to the related SBMESH. The default value for the SBMESH is β=1.

11.2 INS Process (In-service Process)

[4432] Described below are the INS process in the MH-COM and the INS process in the LP. The INS process refers to the process of incorporating an OUS system (a system in an out-of-service state) into an INS system (a system in an in-service system).

[4433] 11.2.1 INS Process of MH-COM

[4434] The INS process of the MH-COM is described by referring to FIG. 443.

[4435] The INS process of the MH-COM mainly copies the contents of the master system VCC table to the VCC of the system to be processed into an INS system. The procedure is described as follows. No diasnostics are made when incorporating the system in the INS process. The INS process is performed on condition that no fault is detected in the corresponding OUS system, and that the initialization is completed and the intra-station communications link has been established.

[4436] 1. The BCPR issues a VCC copy request command (VCC-CPY-RQ) to both ACT and OUS systems.

[4437] 2. The ACT system MH-COM connects its own μP-bus to the OUS system after receiving the VCC-CPY-RQ, and notifies the OUS system of the VCC copy request in the inter-system communications through the SIC. Then, it returns an ACK in response to the VCC-CPY-RQ to the BCPR.

[4438] When the OUS system MH-COM receives the VCC-CPY-RQ from the BCPR and a VCC copy request from the ACT system in the inter-system communications, it disconnects its own system VCC from the bus (thus, enabling the OUS system VCC to be viewed in the I/O space of the ACT system μP-bus). Then, it returns an ACK to the BCPR.

[4439] 3. The ACT system μP starts copying the VCC (the settings of its own system VCC are sequentially read and written to the other system VCC viewed through its own system bus). If the read contents of the copied-from VCC are not set on the table, then the address is not copied but the next address is read.

[4440] The BCPR issues a VCC-SET-RQ only to the ACT system VCC (normally, it is issued simultaneously to both systems) after receiving an ACK in response to the VCC-CPY-RQ from the MH-COMs of both systems (that is, during the copying operation).

[4441] 4. After copying the VCC, the ACT system MH-COM transmits a VCC copy completion notification (VCC-CPY-CMP) to the BCPR. When the ACT system MH-COM receives the ACK in response to the VCC-CPY-CMP, it returns a VCC copy completion notification to the OUS system MH-COM in the inter-system communications.

[4442] The BCPR receives the VCC-CPY-CMP from the ACT system MH-COM, returns an ACK, and immediately issues a VCC-CPY-CMP to both systems.

[4443] 5. After the OUS system MH-COM receives a VCC copy completion notification from the ACT system MH-COM through the inter-system communications, it transmits a VCC-CPY-CMP to the BCPR. After an ACK is received from the BCPR in response to the VCC-CPY-RQ, the a unit connected through the μP-bus restores its own VCC, and issues a VCC copy completion notification to the ACT system MH-COM through the inter-system communications. After the ACT system MH-COM receives the VCC copy completion notification from the OUS system, it disconnects its own system bus from the bus of the other system.

[4444] The above listed processes 1 through 5 put the OUS system in an INS state.

[4445] 11.2.2. INS Process in LP

[4446] This procedure is to perform on only the system to be converted into an INS system the process of initializing the LP on both systems as described in 11.1.2.

11.3 Fault Monitor and System Switch

[4447] The following 5 types of faults are detected in the SBMESH by the software.

[4448] 1. a fault in the LAP link between the SBMESH and the MH-COM

[4449] 2. a fault in the communications using the INF between the SBMESH and the LP

[4450] 3. MSCN in the MH-COM

[4451] 4. MSCN in the LP

[4452] 5. a fault in the health check of the LP

[4453] Each of the above listed cases is explained below, and the system switch is summarized later.

[4454] 11.3.1 Fault Monitor of MH-COM

[4455] A fault in the MH-COM is reported by the intra-station communication LAP to the BCPR through the BSGC. The fault information reported through a simple LAP is referred to as an E-MSCN.

[4456] There are two types of MH-COM faults, that is, a fault to be reported by its own E-MSCN to the BCPR and a fault to be reported through the E-MSCN of the other system. A fault not reported by its own E-MSCN or not accepted even if it is reported is accommodated by the E-MSCN of the other system. Such a fault can be one of the following types.

[4457] μP fault (watch dog timer)

[4458] power source fault (disconnected-fuse/abnormal OBP)

[4459] intra-station communications processing unit fault (EGCLD-LSI fault/signalling DMX fault)

[4460] When a fault occurs in an ACT system (active system), the systems are switched by the ASSW to block the fault in the old ACT system and activate diagnostics. When a fault occurs in an SBY system (stansby system), the systems are not switched by the ASSW to block the fault in the SBY system and activate diagnostics. FIG. 444 shows the operation to be performed when a fault occurs in the MH-COM.

[4461] 11.3.2 MH-COM Fault Reporting and Processing Sequence

[4462] Described below are the MH-COM fault reporting and processing sequences.

[4463] (1) Difference Report

[4464] A fault of the MH-COM is reported by the E-MSCN in the difference report. For example, the BCPR does not periodically issue an E-MSCN read command to collect E-MSCN by itself, but receives a report from the MH-COM each time a fault occurs. The similar process is performed when the system recovers from a fault. That is, a report is transmitted to the BCPR only when a change occurs in the bits of the E-MSCN. The E-MSCN is assigned a mask pattern (set from the BCPR by the E-MSD) and no report is made relating to masked E-MSCN bits even if a change occurs therein.

[4465] However, a COM-E-MSCN-DAT-RQ command can be used to read the E-MSCN from the BCPR at any time. The E-MSCN read through this command is not masked.

[4466] (2) Fault Correcting Process Sequence

[4467] The sequence in a fault correcting process depends on whether the fault is reported by its own system E-MSCN or by other system E-MSCN, and whether the fault correcting system is an ACT system or an SBY system. Described below is the fault correcting process sequence of each case.

[4468] 1. When a fault reported by the E-MSCN of its own system occurs in an SBY system

[4469] 2. When a fault reported by the E-MSCN of its own system occurs in an ACT system

[4470] 3. When a fault reported by the E-MSCN of the other system occurs in an SBY system

[4471] 4. When a fault reported by the E-MSCN of the other system occurs in an ACT system

[4472] FIGS. 445 through 448 show the cases in 1 through 4 as listed above.

[4473] 11.3.3 Fault in Communications through INF with LP

[4474] The SBMESH-A is interfaced with the BCPR through the INFT and the INFA as shown in FIG. 449.

[4475] The fault occurs between the SBMESH and the INFA and the normality of the BCPR, INFT, and INFA is ensured (for the portions not facing the SBMESH).

[4476] The concept to be followed is described below. The fault of the DMA is displayed on the INF MSCN. Basically, it is similar to the fault monitor relating to the communications through the INF between the software and the BSGC, and also to the control timing of the OUS and ALM lamp.

[4477] When a fault occurs in the communications to the master system LP;

[4478] Systems are switched at the LP of the SBMESH. The old master system LP is an OUS system and the diagnostics is started.

[4479] When a fault is detected in the communications to the LP of the slave system, the LP of the slave system is an OUS system and the diagnostics is started.

[4480] The status returned by the SBMESH in response to a command from the software may contain a factor code, but a BS hardware fault is not reported through this parameter.

[4481] 11.3.4 Fault Detected in MSCN of LP

[4482] Check results of various checkers in the LP are reported to the software through the INF.

[4483] The MSCN points are roughly grouped ingo the following four types.

[4484] 1. Points relating to the inter-state cross-connection of the MH-COM and the LP

[4485] 2. NG or point other than 1

[4486] 3. Point other than 1 and 2

[4487] 4. Detailed point

[4488] The above listed 1 through 3 are accommodated in the 32-bit INF MSCN. FIG. 450 shows the 32-bit INF MSCN. 4 is not an INF MSCN, but a detailed MSCN.

[4489] If a fault, etc. is reported in the 32-bit INF MSCN, an INF interruption occurs to the CC (software).

[4490] The above listed 1 indicates the result of a check relating to the inter-system inter connections. FIG. 451 shows the concept of the check.

[4491] The cross-connection from the DMUX of the MH-COM to the LP normally transmits data and clock from the MH-COM to the LPs of both systems independently. However, the system shown in FIG. 451 is used under the physical restrictions (connector necks, etc.).

[4492] The checkers of the data and clock transmitted by the LPs from the DMUX of the MH-COM are the CKaH and CAaM shown in FIG. 451. The trailing H and M indicate the data and clock from the home MH-COM and the mate MH-COM.

[4493] The correspondence to the INF MSCN bit number is as follows.

[4494] CKaH: bits 21, 20, 13, and 12

[4495] CKaM: bits 19, 18, 11, and 10

[4496] The checkers of the data and clock transmitted from the LP to the MUX block of the MH-COM are the CKbH and CKbM shown in FIG. 451. The meanings of the trailing H and M are the same as described above. These checkers are in the MH-COM, and the check results are returned to the sending LPs of the data and clock (for example, the check results of the #0 CKbM of the MH-COM is returned to the LP #1) and accommodated in the INF MSCN.

[4497] The correspondence to the INF MSCN bit number is as follows.

[4498] CKbH: bits 17, 16, 09, and 08

[4499] CKbM: bits 15, 14, 07, and 06

[4500] The clock of the LP is generated in the PLL of the LP and requires finally synchronizing with the clock of the MH-COM. Therefore, the source clock (64k) is provided by the MH-COM for the PLL in the LP so that the inter-system cross-connection can exist with this clock. The LP checks the source clock from the MH-COMs of both systems.

[4501] The correspondence to the INF MSCN bit number is as follows.

[4502] CKaH: bit 01

[4503] CKaM: bit 00

[4504] The bits relating to item 1 above are a total of 18 bits per SBMESH and 36 bits for the two systems. The 36 bits are divided into nine 4-bit groups. Determination is made in each group.

[4505] bits 17 and 15 of systems 0 and 1 of group (1)

[4506] bits 16 and 14 of systems 0 and 1 of group (2)

[4507] bits 09 and 07 of systems 0 and 1 of group (3)

[4508] bits 08 and 06 of systems 0 and 1 of group (4)

[4509] bits 21 and 19 of systems 0 and 1 of group (5)

[4510] bits 20 and 18 of systems 0 and 1 of group (6)

[4511] bits 13 and 11 of systems 0 and 1 of group (7)

[4512] bits 12 and 10 of systems 0 and 1 of group (8)

[4513] bits 01 and 00 of systems 0 and 1 of group (9)

[4514] A normal fault will not generate an NG simultaneously covering two or more groups. However, the fault may occur in the case of the power fault in the MH-COM. For example, if the power fault occurs in the MH-COM #0, the LAP link to the MH-COM is disconnected. Otherwise, since it is determined in the MSCN through the MH-COM #1, the process is performed by referring to the determination. Described below is the reconfiguration of the system in group units.

[4515] Group (1)

[4516] As shown in FIG. 452A, if the two points in the MH-COM (#0) indicate NG, the MH-COM is considered to be faulty. Therefore, if the MH-COM is a master, the systems of the MH-COM are switched with the old master system set as an OUS system and diagnostics is activated. When the MH-COM is a slave, it is set as an OUS system and diagnostics is activated.

[4517] As shown in FIG. 452B, if the two points corrresponding to an LP (#0) indicate NG, the LP is considered to be faulty. Therefore, if the LP is a master, the systems of the LP are switched with the old master system set as an OUS system and diagnostics is activated. When the LP is a slave, it is set as an OUS system and diagnostics is activated.

[4518] As described in FIG. 452C, if one point each of the LP and MH-COM indicates NG, it cannot be determined whether the fault exists in the LP or the MH-COM. In the example shown in FIG. 452C, The MH-COM #0 and the LP#0 are set as OUS system an diagnostics is activated. If the MH-COM #0 is a master or the LP #0 is the master, the systems are switched.

[4519] In FIG. 452C, LP #0 bit 17 indicates NG and bit 15 indicates OK. If bit 17 indicates OK and bit 15 indicates NG, then the MH-COM #1 and the LP #0 are set as OUS systems and diagnostics is-activated. In this case, the LP #1 is also to be checked in the diagnostics result analysis. In the example shown in FIG. 452, The MH-COM can be referred to at four points in the INS mode in both systems.

[4520] FIG. 453 shows an example where one system of the MH-COM is in the SBY or OUS state and only the two points of the master system can be referred to. When one of the LP is in the OUS state, the corresponding two points cannot be referred to. Furthermore, another one point is prevented from being referred to under the condition of the physical inter-connecting configuration.

[4521] FIG. 453A shows the MH-COM #1 in the state other than the INS state (that is, SBY or OUS state) with two points prohibited from being referred to. At this time, two points in the MH-COM #0 indicate NG. Although the MH-COM #0 is faulty, a message is output only.

[4522] FIG. 453B shows the MH-COM #1 in the state other than the INS state with two points prohibited from being referred to. At this time, one point in the MH-COM #0 indicates NG. It cannot be determined whether the MH-COM #0 or the LP is faulty, Since the MH-COM cannot be restructured, the LP #0 is an OUS system and diagnostics is activated in the example shown in FIG. 453B. Normally, systems are switched when the LP #0 is a master system. In FIG. 453B, the LP #0 bit 17 indicates NG, and the LP #1 bit 15 indicates OK. Otherwise, the LP #1 is set to an OUS state and diagnostics is activated. However, the LP #0 is to be checked in the diagnostics result analysis.

[4523] FIG. 454A shows that the LP #1 is in the OUS state and two points in the corresponding LP #1 and a point obtained through the LP in the OUS state, that is, a total of 3 points, are not referred to. The remaining 1 point indicates NG. In this case, only a message is output to indicate that the restructure is not allowed.

[4524] FIG. 454B shows that the LP #1 is in the OUS state and the MH-COM #0 is in a state other than the INS state. At this time, none of the four points can be referred to. This state is defined as a double fault state.

[4525] Group (2)

[4526] Refer to the case of group (1).

[4527] Bit correspondences indicate bit 17 to bit 16, and bit 15 to bit 14

[4528] Group (3) Refer to the case of group (1).

[4529] Bit correspondences indicate bit 17 to bit 09, and bit 15 to bit 07.

[4530] Group (4)

[4531] Refer to the case of group (1).

[4532] Bit correspondences indicate bit 17 to bit 08, and bit 15 to bit 06.

[4533] Group (5)

[4534] FIG. 455A shows an example where two points of the LP (#0) indicate NG. In this case, the LP is faulty. If the LP is a master, then the systems are switched, the old master system is set as an OUS system, and diagnostics is activated. If the LP is a slave, it is set as an OUS system and diagnostics is activated.

[4535] FIG. 455B shows an example where two points corresponding to an MH-COM (#0) indicate NG. In this case, it cannot be determined whether the MH-COM or the LP directly connected to the MH-COM is faulty. Therefore, the MH-COM #0 and the LP #0 are set as OUS systems, and diagnostics is activated for each system. If the MH-COM #0 is a master system or the LP #0 is a master system, the systems are switched.

[4536] FIG. 455C shows an example where only one point indicates NG. In this case, the LP is considered to be faulty. If the LP is a master, then the systems of the LP are switched, the old master system is set as an OUS system, and diagnostics is activated. If the LP is a slave, it is set as an OUS state and diagnostics is activated. In FIG. 455C, the LP #0 bit 21 indicates NG, and the LP #0 bit 19 indicates OK. Otherwise, the LP #0 is set to an OUS state and diagnostics is activated. However, the LP #1 is to be checked in the diagnostics result analysis.

[4537] In the example shown in FIG. 455, the LP can be referred to at four points in both systems INS.

[4538] An example where one system of the LP is in the OUS state is described below by referring to FIG. 456. In this case, two points of the OUS system cannot be referred to. Furthermore, another one point is prevented from being referred to under the condition of the physical inter-connecting configuration. If one system of the MH-COM is in the OUS state, the corresponding two points are prohibited from being referred to.

[4539] FIG. 456A shows that the LP #1 is in the OUS state and two points in the corresponding LP #1 and a point obtained through the LP in the OUS state, that is, a total of 3 points, are not referred to. The remaining 1 point indicates NG. In this case, only a message is output to indicate that the restructure is not allowed.

[4540] FIG. 456B shows an example where the MH-COM #1 is in the OUS state and the corresponding two points are prohibited from being referred to. At this time they as well as the remaining two points indicate NG. Also in this case, a message is output only indicating that the restructure is not allowed.

[4541] FIG. 456C shows that the MH-COM #1 is in the OUS state and the corresponding two points are not to be referred to. At this time, only one point in the remaining two points indicates NG, and the LP is considered to be faulty. Therefore, if the LP is a master, then the systems of the LP are switched, the old master system is set as the OUS state, and diagnostics is activated. If the LP is a slave, it is set as the OUS state and diagnostics is activated. In FIG. 456C, the LP #0 bit 21 indicates NG, and the LP #0 bit 19 indicates OK. Otherwise, the LP #0 is set to an OUS state and diagnostics is activated. However, the LP #0 is to be checked in the diagnostics result analysis.

[4542] FIG. 456D shows an example where the LP #0 is in the OUS state and the MH-COM #1 is also in the OUS state. At this time, none of the four points can be referred to. This state is determined as a double fault state.

[4543] Group (6)

[4544] Refer to the case of group (5).

[4545] Bit correspondences indicate bit 21 to bit 20, and bit 19 to bit 18

[4546] Group (7)

[4547] Refer to the case of group (5).

[4548] Bit correspondences indicate bit 21 to bit 13, and bit 19 to bit 11.

[4549] Group (8)

[4550] Refer to the case of group (5).

[4551] Bit correspondences indicate bit 21 to bit 12, and bit 19 to bit 10.

[4552] Group (9)

[4553] Refer to the case of group (5).

[4554] Bit correspondences indicate bit 21 to bit 01, and bit 19 to bit 00.

[4555] 11.3.5 Health Check of LP

[4556] After the actual operation is started, the following information is communicated between the software and the SBMESH LP.

[4557] 1. Billing information

[4558] 2. Protocol performance monitor information

[4559] 3. Network data collection information

[4560] 4. Error log information relating to 2 and 3 above

[4561] 5. Statistic time information

[4562] The above information 1 and 4 is autonomously transmitted from the LP to the software, but is not transmitted when information to be reported to the software is found. The software does not check whether or not the information 1 above is periodically transmitted. The information 2, 3, and 5 is transmitted every 15th minute. If a fault occurs relating to the INF communications during the actual operation, the fault may exist for 15 minutes in the worst case until the next information 2, 3, and 5 is transmitted. To prevent this, a health check is made for the LP (both master and slave). FIG. 457 shows the concept of the health check.

[4563] The software periodically (for example, every 5th second) issues a health check command to the LP, and simultaneously activates, for example, a 2-second timer. If a health check response is received before the timer reaches its timeout, a normal condition is determined. If the timer reaches its timeout before the response, the fault recognition method is left to the driver software. (For example, the driver software retries 3 times at 2-second intervals and then determines a fault if an NG appears after the three retrials.)

[4564] If a master system of the LP is determined to be faulty, the systems of the LP are switched, the old master system of the LP is set as the OUS state, and diagnostics is activated. If the slave system of the LP is determined to be faulty, the system is set as the OUS and diagnostics is activated.

[4565] The BSGC similarly makes the health check, and additionally determines whether or not the software normally operates in the BSGC (whether or not a health check command is issued periodically).

[4566] 11.3.6 System Switch

[4567] The systems are switched in the SBMESH by the following two methods.

[4568] (1) System switch in the MH-COM

[4569] (2) System switch in the LP

[4570] Each method is described below.

[4571] (1) System switch in the MH-COM

[4572] The systems of the MH-COM are exclusive to the ASSW and independent of the system of the LP. The MH-COM receives an ACT signal from the ASSW via the front cable. The ACT signal to the MH-COM is distributed through an exclusive line not through the intra-station communications LAP.

[4573] The ACT signal to the MH-COM in each system is not a signal reporting the ACT/SBY to the signal receiving system, but a signal reporting whether the present ACT system is a #0 system or #1 system. Therefore, in a normal state (not in a transitional state in which systems are being switched), the information received by the ACT signal receiving unit shown in FIG. 458 is the same in both system.

[4574] When systems are switched, the ACT signals from the ASSW change simultaneously in logic to indicate a new ACT system. Actually, the ACT signals of both systems does not change simultaneously. There is necessarily a moment when the ACT signal received by the MH-COM #0 indicates that the #1 system is an ACT system while the ACT signal received by the MH-COM #1 indicates that the #0 system is an ACT system (or vice versa) in a transitional state.

[4575] The act determination unit is provided in the MH-COM to prevent the state of the system of the MH-COM from becoming unstable in the transitional state. It monitors the ACT signals received by the systems and stores the states of the systems indicated before the ACT signals change until the contents of the ACT signals coincide between both systems.

[4576] If the cable for transmitting the above described ACT signals is lost in the ACT system and if the ACT signal receiving unit of the system is stacked at the ACT system, then the BCPR detects the loss of the cable (the loss of the ACT cable is reported by the E-MSCN to the BCPR), and the ACT signal may not be used to switch the systems. To prevent this, the ACT signal receiving unit which detects the loss of an ACT cable is operated as if it received a signal indicating the other system is an ACT system. The system switch is made in a state in which the commands issued to both systems of the MH-COM match each other. No command is issued or no fault is monitored during the system switch.

[4577] (2) System switch of in the LP

[4578] The systems are switched by changing the ACT state of the INFA.

11.4 Test and Diagnostics

[4579] The following three tests are conducted relating to the SBMESH.

[4580] 1. Test using a TCG

[4581] 2. PVC test between SNI-SBMESHs

[4582] 3. PVC test between MESH-MHs

[4583] Fundamentally, the test 1 above is periodically conducted and the tests 2 and 3 are conducted at the requests of the subscribers. Either the test 2 or 3 can be conducted while the test 1 is being carried out. In this case, the test 1 may have to be waited for while the test 2 or 3 is being conducted.

[4584] Each of the tests and the diagnostics are described below.

[4585] 11.4.1 Test Using TCG

[4586] The SBMESH has a test cell loopback function at the 156M level immediately after the DMUX as in the SIFSH, etc. FIG. 459 shows the loopback test of the SBMESH.

[4587] The actual loopback is performed through the route shown by the bold lines. For example, a test cell from the side 1 of the ASSW (UP) to the SDMX of the SBMESH is looped back to the RMUX as shown in FIG. 459, and sent to the side 1 of the ASSW (DOWN). Likewise, a test data from the side 0 of the ASSW (DOWN) to the SBMESH is transmitted to the side 0 of the ASSW (UP).

[4588] For example, the SIFSH (loaded with the SINF/DS3) can be connected only to the side 0 of the ASSW of both switches. The test data from the side 0 of the ASSW (DOWN) is transmitted to the side 0 of the ASSW (UP). A loopback test of the SBMESH using the TCG is conducted by combining these images.

[4589] In the SBMESH, the MH-COM (SMUX, SDMX, RMUX, and SDMX in FIG. 459) and the LP (SMLP and RMLP in FIG. 459) are duplex, operated in separate master/slave modes, and inter-connected in the two systems. However, the above described test cell is, for example, transmitted from the SMUX of the #0 system if the test cell is received by the RDMX of the #0 system. Thus, the inter-system cross-connection route is not followed, but an input/output is made from the same system regardless of the master/slave correlation.

[4590] This test is periodically conducted in both master and slave systems for the following two purposes.

[4591] (1) Confirming the normality of the switch at the ASSW intersection

[4592] (2) Confirming the DMUX and MUX functions in each shelf (SBMESH in this example)

[4593] For example, in the SIFSH, eight individual units exist under the SIF-COM. Immediately after DMUXing each individual unit, a loopback MUX is performed. FIG. 460 shows a loopback image in the individual unit accommodated in the SIFSH.

[4594] For the confirmation (1) above in the SIFSH, a loopback test should be conducted for any individual unit. Accordingly, a loopback function for the individual unit 0 is adopted. For the confirmation (2) above, a loopback function for one of the individual units 1 through 7 is adopted. Which loopback function should be selected is controlled by the tag information (TAGC) of the transmitted test cell.

[4595] As compared with the SIFSH, the SBMESH has an individual unit (LP in this example) accommodated in the MH-COM. However, up to four SBMESHs can be connected in a daisy chain to the highway from the ASSW. Each shelf corresponds to an individual unit. FIG. 461 shows a loopback image at the LP of each SBMESH.

[4596] For the confirmation (1) above in the SBMESH, the loopback function for the shelf 0 is adopted. For the confirmation (2) above, a loopback function for one of the shelves 1 through 3 is adopted. Which loopback function should be selected is controlled by the tag information (TAGC) of the transmitted test cell.

[4597] FIG. 462 shows the tag information of a test cell (as being input at the SBMESH) to be transmitted from the TCG to the SBMESH. A 600M highway to which the SBMESH is connected is specified at the TAGA and TAGB.

[4598] The VPI of the above described test cell is all 0, and the VCI is 03FA(H) or 03FB(H). However, the SBMESH does not check them specifically, but loops them back with the condition of 0 bit=1. (An 0 bit corresponds to, for example, the 6 bits of the first byte in the cell format shown in FIG. 411).

[4599] The above described test cell is looped back from, for example, the RDMUX to the SMUX in the MH-COM. Simultaneously, a test cell is input from the RDMX to the RMLP, and to the SMLP when it is looped back from the SDMX to the RMUX. It may be discarded under the condition of 0 bit=1 in the RMLP and SMLP.

[4600] After the loopback, the test cell is assigned a tag in the VCC of the SBMESH and returned back to the TCG through the ASSW. However, in the loopback process, no change is made to the tag, VPI, or VCI of the test cell. That is, the test cell is input to the VCC of the SBMESH with its TAG, VPI, and VCI unchanged as being input to the SBMESH. FIG. 463 shows this. Only the process SDMX-RMUX is shown in FIG. 463, but it is also applied to the process RDMX-SMUX.

[4601] The SBMESH has a loopback routes SDMX-RMUX and RDMX-SMUX. They correspond to the loopback route for the TCG connected to the side 0 of the ASSW and for the TCG connected to the side 1 of the ASSW.

[4602] As described above, this test aims at confirming the ASSW and confirming the DMUX and MUX functions in the SBMESH. The test specification does not relate to whether the side 0 or 1 (or both) of the TCG should be used to attain the first purpose (to confirm the ASSW). To attain the second purpose (to confirm the DMUX and MUX functions of the SBMESH), a test using the TCG of the side 0 and the test using the TCG of the side 1 are conducted. FIG. 464 shows the test to confirm the DMUX and MUX functions of the SBMESH.

[4603] As described above, the SDMX performs a DMUX process (that is, specidies a highway) according to the tag information. This test is conducted to test the DMUX function. (Simultaneously, the test is conducted to test the connection to the ASSW, a daisy chain, and the RMUX function.)

[4604] On the other hand, the RDMX is not the DMUX based on the tag information, but the DMUX based on the destination address. Accordingly, this test cannot check the RDMX function, but checks the connection to the ASSW, a daisy chain, and the RMUX function.

[4605] 11.4.2 Loopback Test in SBMESH

[4606] This test is defined in the TR-774 and therefore the detailed description is omitted here. The outline of the method is described below.

[4607] First, the test PDU is output from the device connected to the SNI, looped back at the switch, and checked by the sending device. At the switch, the test PDU is identified by the DA (the DA is preliminarily set), and exchanged-with the SA to loop back the test PDU.

[4608] 11.4.3 PVC Test Between SNI-SBMESH

[4609] This test is conducted upon subscriber's complaint (request and complaint). The VPI and VCI of the test cell are the same as those of the PVC to be tested. That is, the VCC need not be set in the test. FIG. 465 shows the PVC test between the SNI-SBMESH. In the example shown in FIG. 465, the SINF in the SIFSH is tested.

[4610] A test cell is generated by the SBMESH and output. In this example, a test cell is generated by the generating unit (gen.) in the RMLP of the SBMESH. The test cell is transferred to the SINF through the PVC to be tested, and the loopback process is performed on the test cell at the SINF. The test cell is returned through the PVC and received by the SBMESH. It is then checked by the check unit provided in the SMLP of the SBMESH.

[4611] FIG. 466 shows the testing SINF, the existence of a DT block, and the loopback unit (some SINFs and DTs do not be blocked, but an SNI is blocked).

[4612] As shown in FIG. 466, the function of looping back by the test object device to the TCG a test cell from the TCG in conducting this test. That is, when the test is conducted, the periodical test conducted by the TCG should be stopped.

[4613] The test SNI is blocked when the test is conducted. Even if a PDU to be provided for a test SNI is entered from an SNI other than the test SNI to the SBMESH, it is not transmitted to the test SNI. At this time an error count is made in the protocol performance monitor, etc. relating to the above described PDU, but the error is allowable.

[4614] Described below is the procedure of the PVC test. In this test, each command is issued to a master system. Although the command is issued to a slave system, the process can be performed. However, the response status in response to the PVC test result request command is issued from the master system and is checked.

[4615] (1) An SNI block entry command is issued to the SBMESH to report the block of the test SNI. According to the table shown in FIG. 466, the block (DT) accommodating the test SNI is blocked.

[4616] (2) According to the table shown in FIG. 466, a loopback command is issued to the block (DT and SINF) accommodating the test SNI.

[4617] (3) A PVC test start command is issued to the SBMESH.

[4618] The test type is 01, and the test PVC and subscriber identifier refer to the test SNI number.

[4619] A test cell DA refers to an unused individual address type.

[4620] A test cell SA refers to an unused individual address type.

[4621] (4) The timing is to be set to 5 seconds or more.

[4622] (5) A PVC test terminate command is issued to the SBMESH.

[4623] (6) A PVC test result request command is issued to the SBMESH, and a test result of the corresponding response status is checked.

[4624] (7) The loopback specified by the (2) above is released.

[4625] (8) The block specified by the (1) above is released.

[4626] Thus, the PVC test start command, PVC test terminate command, and PVC test result request command are a command set.

[4627] The commands are processed in a logic check in the SBMESH. For example, if a PVC test start command is not received but a PVC test terminate command and a PVC test result request command are received, or if the PVC test start command is received but the PVC test result request command is received without receiving the PVC test terminate command, that is, if the command set is incomplete, then the logic check indicates NG. Practically, the factor code of the status of the (set destroying) command is referred to as indicating an abnormal termination. In the SBMESH, the test result is cleared after the status of the PVC test result request command is returned.

[4628] When a command is issued to the SBMESH as a test procedure, the subsequent step is followed after the status of the command is confirmed. No command set is formed. (As described above, a test SA is provided for the SBMESH for the purpose of preventing an erroneous billing. However, the report is first received by the management firmware of the SBMESH LP, and then transmitted to the billing firmware. If a command set is formed and is provided in series to the SBMESH, then the test cell may arrive to make an erroneous billing before the billing firmware recognizes the test SA according to the notification from the LP management firmware.)

[4629] The process from the command logic check to the prohibition of a command set in the test procedure is the same as that in the MESH-MH PVC test described below.

[4630] 11.4.4 MESH-MH PVC Test

[4631] This test is conducted upon complaint of a subscriber request. Since it is a PVC test, the PVI and VCI of a test cell are the same as those of the test PVC. That is, the VCC is not to be set before the test.

[4632] The MESH-MH PVC test is described below by referring to FIG. 467.

[4633] In the example shown in FIG. 467, the SBMESH(b) and SBMESH(c) are provided in the same MH (MH 1). Then, the SBMESH(a) is connected to the MH 1 through the PVC. In this example, the PVC between the SBMESH (a) and the MH is tested.

[4634] The generating unit (gen.) in the SMLP of the SBMESH(a) generates a test cell, and the test cell is transferred to the MH1 accommodating the SBMESH(b) and (c) along the PVC. The SBMESH(b) and (c) check the DA of the test cell and fetches it if it should be fetched. The test cell is checked in the check unit in the RMLP. Thus, it is determined according to the DA whether or not the cell should be fetched. Therefore, an RDMX function which cannot be checked in the test using tag information can be checked.

[4635] FIG. 467 shows the SBMESH for generating a test cell and the SBMESH for receiving the test cell. These SBMESHs exist in separate shelves in FIG. 467. However, in the MESH-MH PVC, the sending MESH can be included in the destination MH. That is, the SBMESH which generates a test cell can be in the same shelf as the SBMESH which receives the test cell.

[4636] There can be more than one shelf that receives the test cell. That is, a plurality of shelves can receive the test cell. Furthermore, they can be accommodated in the same MH. Although FIG. 467 shows the shelf SBMESH receiving a test cell, but a GWMESH can also receive the test cell. Accordingly, they are represented as “MESH”.

[4637] As described later in detail, this test specifies the DA for the sending and receiving MESHs. The DA used in this test can be specified by the following two methods.

[4638] (1) An unused DA is specified.

[4639] (2) A DA which has been processed by the receiving MESH is specified. (In the SBMESH, an address allocated to the SNI accommodated in the SBMESH is specified.)

[4640] In (1) above, the MESH-MH PVC is mainly tested. For example, the test is conducted when communications cannot be established from a MESH to any subscriber accommodated in another SBMESH. The DA is hereinafter referred to as a “specific test DA”.

[4641] The (2) above is used in the DA test rather than the PVC test. For example, the test is conducted if the communications can be normally established from the MESH to the subscriber accommodated in another SBMESH, but cannot be established only to a specific DA. The DA is hereinafter referred to as an “allocated DA”.

[4642] The test DA can be specified by its individual address type or group address. FIG. 468 shows the outline of specifying the DA and the test with the type specified.

[4643] When the test is conducted, the MESH need not be blocked. In the test using a specific test DA, a test cell is not output from the receiving MESH. By contrast, in the test using an allocated DA, a test cell is transmitted to the destination SNI containing the DA. In this case, the destination SNI is blocked. Thus, since the destination SNI is blocked, a PDU does not reach the destination subscriber accommodated by the SNI even if the PDU to be transmitted from the SNI to the blocked destination SNI is input to the SBMESH.

[4644] Described below is the procedure of the MESH-MH PVC test. In this test, each command is basically issued to a master system. The process can be performed even if a command is issued to a slave system. However, a response status is checked in response to a PVC test result request command to a master system. The “don't care” described below refers to, for example, all 0.

[4645] (1) If an allocated DA is used in the test, an SNI block entry command is issued to the SBMESH and the test SNI block is reported. (If the SNI is accommodated in the SMDS DS1/DS3, the DT itself is blocked.)

[4646] (2) A PVC test start command is issued to a destination MESH. If there are a plurality of destination MESHS, the command is issued individually. If the command is sent and received by the same MESH it is specified in (3).

[4647] The test type is specified as 02 for cases A and B and 03 for cases C and D shown in FIG. 468.

[4648] The transmission identification of 02 is specified.

[4649] The test PVC of “don't care” is specified.

[4650] The subscriber identifier of “don't care” is specified for cases A and B, and an SNI number of the destination SNI including the test cell DA is specified for cases C and D.

[4651] The test cell DA of an unused individual address type/group address type is specified for cases A and B, and a test DA is specified for cases C and D.

[4652] The test cell SA is “don't care” for cases A and B, and an unused individual address type for cases C and D (to prevent an erroneous billing).

[4653] (3) A PVC test start command is issued to the source MESH.

[4654] The test type is 02 specified for cases A and B and 03 specified for cases C and D.

[4655] The transmission identification of 01 is normally specified and 03 is specified if the sending MESH is also the receiving MESH.

[4656] The test PVC of the destination MH MHID is specified for cases A and C, and “don't care” is specified for cases B and D.

[4657] The subscriber identifier is normally “don't care”. If the receiving MESH is also the destination MESH, the “don't care” is specified for cases A and B and the SNI number of the destination SNI containing the test cell DA is specified for cases C and D.

[4658] The test cell DA of an unused individual address type/group address type is specified for cases A and B, and the test DA is specified for cases C and D.

[4659] The test cell SA of “don't care” is specified for cases A and B, and an unused individual address type is specified for cases C and D (to prevent an erroneous billing).

[4660] (4) The timing is to be set to 5 seconds or more.

[4661] (5) A PVC test terminate command is issued to the source MESH.

[4662] (6) A PVC test result request command is issued to the source MESH, and a test result of the corresponding response status is checked. if the source MESH is also the destination MESH, a check to be made by the destination MESH should be carried out.

[4663] (7) A PVC test start command is issued to a destination MESH. If there are a plurality of destination MESHs, the command is issued individually.

[4664] (8) A PVC test result request command is issued to the source MESH, and a test result of the corresponding response status is checked. If there are a plurality of destination MESHs, the command is issued and checked individually.

[4665] (9) The block indicated in (1) above is released.

[4666] In case D, a test cell is copied to be transmitted to all destination SNIs including the test cell DA in the destination MESH. In these cells, only those for the destination SNI specified by the subscriber identifier in the PVC test start command can be checked. Therefore, the steps (2) through (8) should be repeated for all SNIs to test for all the destination SNIs.

[4667] 11.4.5 PVC Test Result Check

[4668] FIG. 469 shows the PVC test results contained in the response status in response to the PVC test result request command.

[4669] There are two types (three types precisely) of PVC tests to be conducted in the same format. FIG. 469 is a table showing the printout examples. The table is printed out when the test results in NG. However, if an SNI-SBMESH PVC test is conducted, the MESH-MH PVC test result indication area (when a specific test DA is used and when an allocated DA is used) need not be printed out.

[4670] The 16-bit test cell transmission unit fault indication area indicates whether or not the test cell transmission unit is in a test cell transmission disable state. If the transmission is disabled, the cause is indicated. The enable/disable of transmission is indicated as follows.

[4671] all-0 pattern for 16 bits: no disable state (OK)

[4672] non-all-0 pattern for 16 bits: disable state (NG)

[4673] FIG. 470 shows an example. If B indicates 1 in FIG. 470, the transmission of the test cell is not completed. If a MESH is not the source MESH in the MESH-MH PVC test, the 16 bits are all zero.

[4674] The 16-bit test cell receiving unit fault indication area indicates whether or not the test cell receiving unit is in a test cell receiving disable state. If the reception is disabled, the cause is indicated. The enable/disable of reception is indicated as follows.

[4675] all-0 pattern for 16 bits: no disable state (OK)

[4676] non-all-0 pattern for 16 bits: disable state (NG)

[4677] FIG. 471 shows an example. If a MESH is not the destination MESH in the MESH-MH PVC test, the 16 bits are all zero.

[4678] The SNI-SBMESH PVC test result indication area is divided into 32 4-bit blocks (cells 0 through 32 in FIG. 469) as shown in the upper 4 rows in FIG. 469. In hardware, the capacity of the test cell receiving unit is 32 cells. Only test cells can be received during this test. Each block indicates whether or not a test cell has been received, and indicates the validity of the contents if the test cell has been received. The summary of the contents of the bit pattern of each block is shown below.

[4679] all zero 4-bit pattern received and normal

[4680] ‘0001’ 4-bit pattern: received but abnormal

[4681] ‘1000’ 4-bit pattern: not received

[4682] There are 6 test cells in a test, and each result is displayed in the area of cells 0 through 5. The area of cells 6 through 31 in the block are all 0. That is, the patterns are as follows.

[4683] all-0 pattern for all blocks: OK

[4684] non-all-0 pattern in any block: NG

[4685] Likewise, the MESH-MH PVC test result indication area (using a specific test DA) can be recognized.

[4686] During the SNI-SBMESH PVC test, or during the MESH-MH PVC test using an allocated DA, the area is entirely all 0. Even during the MESH-MH PVC test using the specific test DA and even if the MESH is not the destination MESH, this area is entirely all 0.

[4687] The MESH-MH PVC test result indication area (using an allocated DA) is also divided into 32 blocks. Since an allocated DA is used in the test, received data is not limited to test cells. For example, if a PDU arrives with a test allocated DA from the MESH not associated with the test, it is received by the test cell receiving unit. Although there are six test cells, all received data are not test cells as described above. Therefore, the entire blocks of cells 0 through 31 is checked.

[4688] It is indicated whether or not each 4-bit block has received a test cell. If yes, then the validity of the contents of the block should be indicated. Furthermore, it should be indicated whether or not the cell is received from a non-test MESH. The outline is described as follows.

[4689] all zero 4-bit pattern: a test cell is received and the contents are normal

[4690] ‘0001’ 4-bit pattern: a test cell is received but the contents are abnormal

[4691] ‘1000’ 4-bit pattern neither a test cell nor a cell from a non-test MESH is received

[4692] all 1 4-bit pattern: a cell is received from a non-test MESH

[4693] During the SNI-SBMESH PVC test or during the MESH-MH PVC test using a specific test DA, this area is set to all 0. Even during the MESH-MH PVC test using an allocated DA, this area is set to all 0 even when the MESH is not the destination MESH. In this test, a test cell may not be received if a cell should be received from a non-test MESH. Therefore, unlike the other tests, a retrial is allowed in this test.

[4694] The checking method is described below in detail for each test type.

[4695] In the SNI-SBMESH PVC test;

[4696] Only one MESH is related to this test. The MESH is a source and destination MESH.

[4697] The software should check in the test result the test cell sending unit fault indication area, test receiving unit fault indication area, and SNI-SBMESH PVC test result indication area. Other areas are insignificant and not objects of a software check. However, the all 0 in the insignificant area is reserved. In this test, a check area of all 0 is accepted as OK, but is indicated as NG if it has any other pattern. FIG. 472 shows the result of this test in the printout format.

[4698] In the MESH-MH PVC test (using a specific test DA);

[4699] Only one source MESH is related to this test. However, there can be a plurality of destination MESHs, and the source MESH can be one of the destination MESHs.

[4700] The software should check in the test result the test cell sending unit fault indication area in the source MESH, and test receiving unit fault indication area and MESH-MH PVC test result indication area (using the specific test DA) in the destination MESHs. Other areas are insignificant and not objects of a software check. However, the all 0 in the insignificant area is reserved. In this test, a check area of all 0 is accepted as OK, but is indicated as NG if it has any other pattern. FIG. 473 shows the result of this test in the printout format.

[4701] In the MESH-MH PVC test (using an allocated DA);

[4702] Only one source MESH is related to this test. However, there can be a plurality of destination MESHs, and the source MESH can be one of the destination MESHs.

[4703] The software should check in the test result the test cell sending unit fault indication area in the source MESH, and test receiving unit fault indication area and MESH-MH PVC test result indication area (using an allocated DA) in the destination MESHs. Other areas are insignificant and not objects of a software check. However, the all 0 in the insignificant area is reserved.

[4704] In this test, a test cell sending unit fault indication area and test cell receiving unit fault indication area of all 0 are accepted as OK, but are indicated as NG if they have any other pattern. The MESH-MH PVC test result indication area (using an allocated DA) is indicated as follows.

[4705] Retrial

[4706] If this area is all 1, all of the 32 cells received by the test cell receiving unit are from the non-test MESH.

[4707] OK

[4708] This area is a combination of an all-1 pattern and an all-0 pattern. That is, there is at least one normal test cell receiving unit, and the others are filled with the cells from a non-test MESH.

[4709] NG

[4710] Six test cells are related to one test. When the test results in NG, the pattern of this area comprises less than 6 blocks of all 0 in 32 blocks and more than 1 block of ‘1000’ pattern. (The description can be applied identically regardless of the existence of an all-1 pattern block. It indicates that the test cess receiving unit does not receive 32 cells and the test cells of the predetermined number are not received (there can be a missing test cell). Furthermore, NG is output when one or more test cells containing abnormal contents are received. In this case, the pattern of this area comprises one or more ‘0001’ in 32 blocks (“don't care” for other blocks). FIG. 474 is the printout of the rest result.

[4711] 11.4.6 Diagnostics of MH-COM

[4712] (1) Diagnostic function of MH-COM

[4713] The diagnostic functions of the MH-COM are listed below.

[4714] (a) Self-diagnostics

[4715] 1. Self-diagnostics for test section

[4716] 2. Diagnostics for construction (P-ON)

[4717] 3. Self-diagnostics activated by the BCPR

[4718] The diagnostic programs of the 1 through 3 above are almost identical.

[4719] (b) Continuity test using TCG

[4720] A continuity test is conducted by generating a test cell by the TCG, switching from the MH-COM unit to this MH-COM at the ASSW, looping back the test cell at the MH-COM, and returning it to the TCG.

[4721] Since the SBMESH interfaces with both sides 0 and 1 of the ASSW, the following two loopback patterns are prepared.

[4722] 1. A test cell is fetched at the SDMX and looped back to the RMUX.

[4723] 2. A test cell is fetched at the RDMX and looped back to the SMUX.

[4724] 1 and 2 above can be specified together.

[4725] The MH-COM loops back the transparency of a received test cell. A passing TCG cell is not processed. Described below is the DEMUX/MUX of test cells.

[4726] (1) S→R direction

[4727] A test cell is fetched at the DMUX-LSI which DMUXes the SMLP data at the SDMX. Therefore, the test cell has the same tag value as the data to the SMLP. The VPI/VCI values are different between a cell to the SMLP and a test cell.

[4728] Only data cells to the SMLP are fetched according to the VPI/VCI in the SMLP, and the test cell is discarded.

[4729] Only a cell in which an 0 bit is set (only a test cell has an 0 bit) in the cells (combination of SMLP cells and test cells) DEMUXed at the SDMX in the receiving SEL-NL is multiplexed to a highway receiving the cells from the RMLP. That is, the VPI/VCI value is “don't care” in the SEL-N1.

[4730] A test cell multiplexed in the highway from the RMLP is converted in its VCI by the RVCC and returned to the TCG.

[4731] (2) R→S direction

[4732] A test cell is demultiplexed from the 622 Mbps from the ASSW through the DMUX-LSI (R-TCG DMUX) exclusive for a test cell of the RDMX. However, the demultiplexing process is performed only by a tag value (regardless of the 0 bit). Therefore, the demultiplexed cell data is not limited to test cells.

[4733] Only data cells to the RMLP are fetched according to the VPI/VCI in the RMLP, and the test cell is discarded.

[4734] Only a cell in which an 0 bit is set in the cells (combination of RMLP cells and test cells) DEMUXed at the R-TCG in the sending SEL-N1 is multiplexed to a highway receiving the cells from the SMLP. That is, the VPI/VCI value is “don't care” in the SEL-N1.

[4735] A test cell multiplexed in the highway from the SMLP is converted in its VCI by the SVCC and returned to the TCG.

[4736] (2) Outline of MHCOM self-diagnostics

[4737] FIG. 475 shows the outline of the MHCOM self-diagnostics.

[4738] (2)-1 TP

[4739] There are three types of TPs, that is, a 1-trial TP, 3-trial TP, and construction TP. The TP is activated by depressing the reset switch on the front panel of the HSF05A when it is powered. Which TP is activated depends on the settings of the dip switch on the HSF05A. The diagnostic result from the TP is displayed on the 7-seg. LED of the HSF05A.

[4740] (2)-2 DP

[4741] An online diagnostics can be activated either from an ACT system to an OUS system or directly in the OUS system. The diagnostics can be activated by the following triggers.

[4742] Activation i) when the diagnostics is activated from an ACT system to an OUS system

[4743] 1. After a mate-system fault is detected (a diagnostics result is reported to the ACT system and reported to the software by the COM-E-MSCN of the ACT system).

[4744] Activation ii) when the diagnostics is activated directly in an OUS system

[4745] 1. After a home-system fault is detected

[4746] 2. Diagnostic command input (a diagnostics result is reported to the software by the COM-E-MSCN of the ACT system in the OUS system LAP).

[4747] (3) Diagnostics result report

[4748] (3)-1 DP result

[4749] After performing the DP, the DP result (OK/NG, length, details) is reported to its own COM-E-MSCN if the diagnostics is activated by the home system, to the mate system through the inter-system communications if the diagnostics is activated by the mate system as shown in FIG. 476, and to the software by the COM-E-MSCN of the mate system.

[4750] i) RESULT: An NG PWCB is set. (FIG. 477)

[4751] ii) length: The number of bytes containing detailed information of the diagnostics NB is clearly described (refer to FIG. 478).

[4752] iii) result: The detailed NG information of the indicated length is described (FIG. 479).

[4753] 11.4.7 Diagnostics of LP

[4754] The diagnostics of the LP is described as follows.

[4755] The main items of the diagnostics are:

[4756] 1. ING interface test

[4757] 2. LP unit function test

[4758] The item 1 above is conducted by the diagnostic program and equivalent to the INF interface test conducted at the beginning of the BSGC diagnostics.

[4759] The item 1 above consists of the following two parts.

[4760] (1) CC access write/read test

[4761] (2) DMA transfer test

[4762] FIG. 480 shows in detail the performance of these tests. FIG. 480 shows the actual results only and the portions such as APID, etc. are omitted.

[4763] In FIG. 480, *1 is the area indicating the diagnostics result of OK or NG. The area is 8 bits indicating an all-0 pattern, that is, NG. If the diagnostics is OK, the area other than *1 is “don't care”. If the diagnostics is NG, the area other than *1 is significant.

[4764] The phase number area, sub-phase number area, and test number area contain an NG phase number, sub-phase number, and test number respectively in right-justified binary numbers.

[4765] The phase number is an autonomous diagnostic phase number, and is not a diagnostic number of the SBMESH LP.

[4766] The NG priority indication area is divided into two parts each indicating for the home or mate systems, and is further divided into 4-bit data to indicate for each PWCB. For example, is the #0 system is processed by the diagnostics, the home system refers to a #0 system and the mate system refers to a #1 system. As described above, the systems are inter-connected between the LP unit and the MH-COM unit. Accordingly, the PWCB in the mate system can be an NG PWCB. An NG PWCB is reported for each PWCB. An NG priority is indicated in right-justified binary numbers.

[4767] In this area, all 0 refers to a non-NG PWCB. In representing data in decimal, 1 indicates the most doubtful PWCB (having the highest NG priority), sequentially followed by 2, 3, . . . However, some cannot be assigned priority numbers. In this case, they are reported as having an equal priority. At a timeout, the diagnostics result report from LP status wait state is released to state an NG PWCB.

[4768] As described above, the diagnostics should be performed on both LP and MH-COM units depending on the NG bit pattern of the INF MSCN of the LP unit (because it cannot be determined which is faulty, the LP unit or the MH-COM unit).

[4769] The diagnostics is performed through the INF in the LP and through the LAP in the MH-COM. Even if it is performed on both LP and MH-COM, it is not performed simultaneously on both units. That is, one unit is processed first, and the other unit is not processed until the first process is completed.

[4770] The reason is explained in the following example. For instance, a pseudo-fault test is conducted such that the parity of the data transmitted to the LP is not damaged as a part of the diagnostics of the MH-COM. (This is to confirm the detection of an NG by means of the parity checker in the MH-COM. The data is transmitted also to the LP.) If the diagnostics of the LP is performed simultaneously and a test is being conducted in which a parity check as a part of the diagnostics of the data from the MH-COM is expected to be OK, then the test results in NG.

[4771] If the test 1 above results in NG, the test 2 is not conducted. The test 1 is divided into (1) and (2), and the test (2) is not conducted if the test (1) results in the test (1).

[4772] The test 2 is an autonomous diagnostics made by the μ-p and comprises a plurality of phases, sub-phases, and tests. If a test results in NG, the autonomous diagnostics is aborted immediately and a diagnostic result notification status is transmitted.

11.5 MSCN

[4773] The following two MSCNs are provided for the SBMESH.

[4774] 1. relating to the MH-COM

[4775] 2. relating to the LP

[4776] The tests 1 and 2 above interface with the software respectively through the LAP and INF. Described below are the details of each MSCN.

[4777] 11.5.1 MSCN of MH-COM

[4778] As described above, the MSCN of the MH-COM is the E-MSCN reported through a simple LAP. The E-MSCN is transmitted to the BCPR basically as a difference report.

[4779] In the case of the SBMESH, faults accommodated in the E-MSCN relate to the MH-COM. The fault information relating to the LP is not included. The fault information of only the MH-COM indicates that the MSCN of the SBMESH is a common unit E-MSCN (COM-E-MSCN). That is, the information does not contain the data of an individual unit. The E-MSCN of the MH-COM does not distinguish NG-OR from detailed information. (All data refer to detailed information points.) The BCPR takes an action according to the contents of each point.

[4780] 1. Format of the MH-COM E-MSCN

[4781] The E-MSCN of the MH-COM is represented by an 8-bit-256-row map as shown in FIG. 481. The 256 rows are grouped into some areas and accommodated in units of action type to be takes upon occurrence of a fault in the BCPR. The E-MSCN is difference-reported, but all the 256 rows are reported to the BCPR if any bit in the format shown in FIG. 481 changes.

[4782] The E-MSCN enables a mask to be specified in word units (in 2-row units) using the E-MSD. No report is made even if a masked bit changes. If a masked bit is transmitted together with a changed unmasked bit (this normally happens), the bit is reported as OK.

[4783] The polarity of the E-MSCN is represented as 0 for OK and 1 for NG (set by NG). The polarity of the blank area in FIG. 481 is set to 0.

[4784] The E-MSCN point of the fault information indication is output as a result obtained by editing at the μP of the HSF05A the output of the checker arranged at each PWCP forming part of the MH-COM. Each checker does not have a protective means. If an NG is detected, the result is stored until the fault reset instruction is received from the μP. The μP periodically monitors the checkers, reads the check results, and repeats the fault-reset operation. If NG is detected twice consecutively in the monitoring method, then it is recognized that the faults occurred at the checker and the E-MSCN point of the checker is set as NG. The monitor cycle of the checkers depends on the purpose of each checker.

[4785] Described below are the details of each area.

[4786] (1) MH-COM control MSD echo area (0-35 rows)

[4787] This area accommodates the echo data of the MH-COM control MSD (E-MSD). The polarity remains the same after the accommodation (the same polarity as the E-MSD).

[4788] (2) Device state indication area (36-39 rows)

[4789] This area accommodates the information about the state of a device such as an ACT state, clock selection, etc., but not fault information of the MH-COM.

[4790] (3) Mate system fault indication area (40-45 rows)

[4791] This area accommodates the fault information about the MH-COM of a mate system. The mate system fault information is reported through an inter-system communications link between MH-COMs or other lines. The system switch of the ASSW is triggered by a fault accommodated in this area and the system in an ACT state.

[4792] (4) Home system fault indication area (46-55 rows)

[4793] This area contains the fault information about the MH-COM of a home system. The system switch of the ASSW is triggered by a fault accommodated in this area and the system in an ACT state.

[4794] (5) Warning indication area (72-83 rows)

[4795] This area contains the warning information in the MH-COM. It is a buffer full/cell discard indicator relating to a buffer which accumulates highway data in the MH-COM. The bit set accommodated in this area can be an ACT system, but cannot directly trigger the system switch of the ASSW.

[4796] (6) Diagnostic result indication area (84-99 rows)

[4797] This area accommodates the result of the online DP for the MH-COM.

[4798] (7) Statistic information indicator area (100-119 rows)

[4799] This area accommodates various statistic data in the MH-COM. The statistic data indicate the number of cells reported and discarded in each multiplexer and demultiplexer.

[4800] 11.5.2 MSCN of LP

[4801] There are the following two types of MSCNs.

[4802] (1) INF MSCN

[4803] (2) detailed MSCN

[4804] As described above, if a fault occurs in the LP of the SBMESH, it is reported to the software as an INF interruption. The software issues an MSCN read command in response to the interruption, and the 32-bit INF MSCN shown in FIG. 450 is obtained in response to the command.

[4805] The software recognizes the type of a fault based on the data. At this time, a detailed fault inquire command is issued if necessary to obtain further detailed information. The detailed MSCN is obtained as a result of this command.

[4806] Detailed MSCN

[4807] FIG. 482 shows the concept of accommodating the detailed MSCN.

[4808] The LP comprises 10 pieces of PWCB, that is, the HMH00A through HMH06A, HLM00A, HLM01A, and HLP02A. Each PWCB is assigned 128 bits and arranged in the order as shown in FIG. 482.

[4809] The area of each PWCB comprises a 64-bit MSCN area accommodating the check result of each checker and a 64-bit MSD echoback area accommodating the echoback of the pseudo-fault point for the checker as shown in FIG. 482.

[4810] The 64-bit MSCN area is divided into four 16-bit blocks.

11.6 MSD

[4811] The following two MSDs are provided for the SBMESH.

[4812] 1. relating to the MH-COM

[4813] 2. relating to the LP

[4814] The tests 1 and 2 above interface with the software respectively through the LAP and INF.

11.6.1 MSD of HM-COM

[4815] The MSD of the MH-COM is accommodated in an intra-station communications LAP and accesses an MSD table on the MH-COM from the BCPR through the BSGC. The MSD through the intra-station communications LAP is referred to as an E-MSD. The E-MSD for the SBMESH accommodates only the MSD point relating to the MH-COM.

[4816] 1. Format of MH-COM E-MSD

[4817] As shown in FIG. 483, the E-MSD of the MH-COM is represented by a 8-bit-256-row map. The 256 rows are grouped into some areas and are separately accommodated according to the meaning of each E-MSD point. The BCPR transmits all 8-bit-256-row areas as well as operation object bits through a COM-E-MSD command. An MH-COM which received the command compares the received E-MSD table with that received previously, and recognizes all changed portions as new settings. Therefore, the BCPR sets the point which is not an object of the operation to the value of the E-MSD table.

[4818] The polarity of the E-MSD is reset by 0 and set by 1. A part of areas on the E-MSD table are echoed back to the E-MSCN. At this time, the polarity of the E-MSD remains unchanged. Described below in details is the area of each MH-COM-MSD shown in FIG. 483.

[4819] (1) MH-COM control E-MSD area (0-35 rows)

[4820] This area accommodates the MH-COM control E-MSD area (0-35 rows). This area is echoed back to the E-MSCN. FIG. 484 shows the accommodation of this area. FIGS. 485 and 486 show the contents of each point of this area.

[4821] (2) Statistic threshold design area (36-51 rows)

[4822] This area accommodates a threshold for each statistic function in the MH-COM. FIG. 487 shows the accommodation of this area. FIGS. 488 and 189 show the contents of each point of this area.

[4823] COM-E-MSCN mask pattern setting area (180-195 rows)

[4824] This area accommodates the mask pattern for the E-MSCN. The mask is set and released in word (2-row or 16-bit) units. A mask-specified E-MSCN point is set as OK. Even if a fault occurs to a mask-specified E-MSCN point, or even if an event of inverting the polarity of the point occurs, no E-MSCN report (difference report) is made. However, a masked point causes the current data to be returned in response to the E-MSCN read request command (COM-EMSCN-DAT-RQ) as if it were not masked. Immediately after the initialization, All fields of the E-MSCN are masked until a mask pattern is specified by the BCPR.

[4825] FIG. 490 shows the contents of this area. FIG. 491 shows the contents of the mask-specified point of this area.

[4826] 11.6.1 MSD of LP

[4827] The LP comprises 10 pieces of PWCB, that is, the HMH00A through HMH06A, HLM00A, HLM01A, and HLP02A. Each PWCB is assigned a 128-bit area. In each PWCB, most MSD points are pseudo-fault points for use in diagnostics. Therefore, the diagnostics of the MSD point of the LP is autonomously made by the μ-p, and only the firmware should be controllable with the software possibly uncontrolled.

11.7 Billing and Statistic Processes

[4828] 11.7.1 General Descriptions

[4829] The following five billing and statistic processes are prepared for the SBMESH.

[4830] 1. Statistic process in the MH-COM

[4831] 2. Billing process in the LP

[4832] 3. Protocol performance monitor process in the LP

[4833] 4. Network data collection process in the LP

[4834] 5. Cell-number processes in the LP (traffic control)

[4835] The process 1 above interfaces with the software through the LAP, and the processes 2 through 5 interface with the software through the INF.

[4836] 1. Statistic process in MH-COM

[4837] The statistic processes in the MH-COM can be performed at the following points.

[4838] (1) SDMX unit (DMUX function 600 Mbps→155 Mbps)

[4839] In the SBMESH, no statistic process is performed in the RDMX.

[4840] (2) SMUX RMUX unit (MUX function 600 Mbps→155 Mbps)

[4841] (3) LAP terminal downward (DMUX function 600 Mbps→155 Mbps)

[4842] (4) LAP terminal upward (MUX function 155 Mbps→600 Mbps)

[4843] (5) R-TCG unit (test cell MUX/DMUX)

[4844] FIG. 492 shows the sequence of the statistic processes.

[4845] (1) Statistic process sequence

[4846] The collection and notification of statistic information can be made through the COM-E-MSD instruction and COM-E-MSCN notification. The statistic process is performed by saving the count data at a time set (15 minutes) instruction and is reported to the BCPR at a read request later. The sequence is listed below.

[4847] (1) A buffer threshold is set for each line MUX and DMUX.

[4848] (2) The statistics is started by a statistics start instruction (for each line MUX/DMUX).

[4849] (3) The counter data is saved at the phase switch (15 minutes) instruction, and simultaneously the counter is reset.

[4850] (4) The statistic data is reported at a statistic information read request.

[4851] (5) The steps (3) through (4) are repeated.

[4852] (2) Statistic information collection error

[4853] Described below are the points to be carefully considered in using a simple LAPD protocol in the intra-station process in the statistic process.

[4854] When a link is reset, an NS (sequence number for a software command number check) is initialized. Therefore, a command can be erroneously set double. FIG. 493 shows an example in which the MH-COM statistic processes are abnormally collected.

[4855] The BCPR indicates a UI timeout because an ACK is not returned in response to the time setting, and another time set command is issued after reestablishing a link. At this time, since the NS is initialized and the NS number check is initialized at the device, the device cannot detect the double setting of the command, thereby erroneously setting the command double. If a command is erroneously set double in switching phases, the 15-minute-interval statistic data collection generates errors. Therefore, the following protection is gained in the application of the MH-COM statistic process.

[4856] (1) If no read request follows a phase switch instruction after starting the statistic process, the subsequent phase switch instruction is ignored.

[4857] (2) The software should issue a statistic information read request to a circuit performing a statistic process after a phase switch instruction.

[4858] FIG. 494 shows the sequence of the processes when a statistic process is abnormally performed.

[4859] Described next is the sequence of the steps 2 through 5.

[4860] FIG. 901 shows the sequence of the steps (2) through (5) above.

[4861] Various counters for protocol performance monitors, network data collection, etc. have two-phase configurations in hardware and switch access phases of the hardware according to a collection phase switch request command from the software.

[4862] In the counting process, the software issues a collection phase switch request command to the SBMESH LP unit at every 00, 15, 30, and 45 minutes. Various count values are read within 15 minutes from a switch to the next switch.

[4863] The performance information request command, traffic measurement information request command, and discarded cell number request command are introduced above. Obviously, the order of the commands is not limited to this example. However, each command (including a collection phase switch request command) should be issued at some second intervals. (If a command group is issued simultaneously, there can be congestion in the firmware).

[4864] The statistic time information command is issued every 15th minute as described above. This command is issued only to correct the time managed by the firmware. There is no special definition for the phase relation between this command and other commands. (The intervals between the commands are set in second unit).

[4865] The above described process is controlled by the software. The following four variations of status are autonomously transmitted by the hardware to the software.

[4866] (1) Billing data notification

[4867] (2) Protocol performance log notification

[4868] (3) Traffic measurement log notification

[4869] (4) TCA notification related to protocol performance monitor

[4870] (1) above is transmitted every minute basically. (2) and (3) are transmitted each time an error which requires a log occurs. However, a filter is applied in hardware and the intervals are set in second unit even if the log is reported the most frequently. (4) above is transmitted each time an error count exceeds the threshold.

[4871] 11.7.2 Billing Process

[4872] Billing data is reported to the software autonomously by the hardware basically every minute according to a billing data notification status. If there is no arrival of a cell within a minute and therefore no billing data to be reported to the software, then the billing data notification status is not issued.

[4873] According to the TR-775, it is instructed that the following data should be collected for a billing process.

[4874] (1) DA

[4875] (2) SA

[4876] (3) SNI address

[4877] (4) condition code

[4878] (5) L2 PDU count

[4879] (6) L3 PDU count

[4880] (7) data collection time]

[4881] In consideration of figure inter-LATA communications, the information relating to carriers is also collected.

[4882] Listed below are correspondences between the information about parameters and carriers (1) through (7) and the parameters in the billing data notification status.

[4883] The DA of (1) above is not defined as an independent parameter in the status. It is obtained by the software according to the WHAT, MHID, MESHID, SNI, ID, and address ID.

[4884] The SA of (2) above is included in the status.

[4885] The SNI address of (3) above is obtained by the software according to the method of the TR-775. (It is not defined as an independent parameter in the status).

[4886] The condition code of (4) above is 0 for no error in L3-PDU, and is defined by the TR-775 depending on each error type for an error in L3-PDU. However, since the hardware o the SBMESH performs a billing process only on no-error L3-PDU, the code is set to 0, and it is assigned by the software.

[4887] The information relating to the L2/L3 PDU count, data collection time, and carriers of (5) through (7) is included in the status.

[4888] The total amount of data is not fixed, but depends on the number of arriving cells, etc. in one minute immediately before. Therefore, if the data cannot be contained in one message of a billing data communications status, then variations of the status are transmitted.

[4889] In hardware, the billing data accumulation RAM has a duplex configuration, and the data transmitted to the software is the data accumulated in the hardware non-access phase (frozen phase). In the billing data notification status, there is a parameter (block number) indicating which of the two phases accumulates the data. Since the billing data can be reported by plural variations of status, the sequence numbers are used as parameters (0 through 4095 available).

[4890] After all billing data are transmitted, a billing transfer completion status is transmitted by the firmware. In response to the billing transfer completion status, the software sends a billing reception completion command in response to which the firmware sends a billing reception completion status, thereby completing a series of billing data transmission.

[4891] To be exact, there is a reception result parameter in the billing reception completion command from the software. If it is an ACK, the process is accepted and the firmware sends a billing reception completion response status, thereby terminating the process. The firmware clears the transmission completion phase of the billing data accumulation RAM.

[4892] If the reception result parameter in the billing reception completion command indicates an NCK, then it is NG and the billing data is transmitted again. All billing data is transmitted again in the re-transmission process. (Furthermore, all billing data is transmitted again for any data re-transmission.)

[4893] If the software detects an abnormal condition (lost numbers) in sequence numbers during the reception of billing data notification status, then (even before receiving the billing transfer completion status) a billing reception completion command, whose reception result parameter is NCK, is transmitted. Upon receipt of the command, the firmware retransmits the billing data. Additionally, when sending a billing transfer completion status, the firmware activates a 200 ms timer and waits for a billing reception completion command from the software.

[4894] When the timeout occurs, the billing data is retransmitted. If the timeout occurs again in retransmitting the data, the process is retried without limit. However, since the billing data is transmitted in 1-minute cycle, the retransmitting process is not continued but aborted.

[4895] As described above, a data collection time parameter is contained in the billing data notification status. A retransmitted parameter has the same value as a parameter of the previously transmitted billing data notification status.

[4896] There is also a data collection start time parameter in the billing transfer completion status. The value is set to a value within a minute from the data collection time parameter value in the billing data notification status preceding the billing transfer completion status.

[4897] According to the hardware configuration of the billing unit, up to 256 types of combination of SA and carrier information can be realized. If the variations exceed 256, the phase is switched even if one minute has not passed since the previous phase switch of the billing data accumulation RAM, and the billing data notification status is transmitted.

[4898] Described above is the transmission of billing data from autonomous firmware. The data can also be transmitted at an inquiry from the software. For example, an adjusting process is performed after deleting a telephone number.

[4899] In this case, the software issues an account adjustment data transfer request command. In issuing the command, a telephone number to be adjusted is included as a parameter. The firmware does not immediately transmits the corresponding billing data in response to the request command, but only transmits an account adjustment data transfer response status. The corresponding billing data is transmitted after the first phase switch of the billing data accumulation RAM upon receipt of the command.

[4900] Before transmitting a normal billing data notification status, the corresponding billing data is transmitted as billing adjustment data notification status. If a request is issued to adjust a plurality of telephone numbers within 1 minute, the corresponding billing data is collectively transmitted. If the corresponding billing data indicates 0, the information indicating that there is no billing data is issued.

[4901] In this step, as in the billing data notification status, there are parameters of block numbers and sequence numbers (a sequence number is assigned as a serial number with that of the billing data notification status to be issued after this status), and a plurality of messages can be generated. A completion notification parameter indicates as to whether or not the billing adjustment data is the final data as the billing adjustment data. The telephone number to be adjusted is included as a parameter.

[4902] The transmitting operation is performed similarly to the normal operation. That is, all data is retransmitted including adjustment data. The billing data is transmitted to the software through the area basically reported according to an INF initial data entry command. If the firmware recognizes that this area is running short, it issues a billing buffer request status to the software, and the area reported by the software according to the billing buffer entry command is used.

[4903] If there is no area notification to the billing buffer request status according to a billing buffer entry command from the software, then the billing data is discarded. The firmware sets a 10-second timer when the billing buffer request status is issued. Only one retrial is allowed at timeout. If there is no notification from the software, the cell is to be discarded.

[4904] 11.7.3. Protocol Performance Monitor Process

[4905] The SBMESH performs a protocol performance monitor process according to the TR-774. Additional explanation is given in this process as described in Chapter 6. The following three protocol performance monitor processes are required.

[4906] (1) Storing various count values at every 15th minute

[4907] (2) Generating a TCA when an error count value exceeds a threshold value

[4908] (3) Occurrence of an error log

[4909] Each of the counters has a duplex configuration for the hardware, and the two phases are switched according to the collection phase switch request command from the software. The software picks up during the 15 minutes to the next issue of the command a count value of the past 15 minutes according to the performance information request command. Each of the various count values for each 15minutes defined by the TR-774 is stored by the software.

[4910] In the process performed in a response status, that is, in response to a performance information request command, no bursty error algorithm is realized, but the L2 #bad intervals, L2 #intervals, and L2 bursty error quotient are processed as “don't care”. The portion not practically defined by the TR-774 is processed as follows.

[4911] L3-PDU transferred count (source): a count value as a part of network data collection

[4912] Errored L3-PDU count (source): a sum of an L3 sum of errors count value counted as a part of a protocol performance monitor and an individual count value.

[4913] L2-PDU transferred count (source): a value counted as a part of the network data collection

[4914] Errored L2-PDU count (source): L2 sum of errors count value counted as a part of the protocol performance monitor

[4915] L3-PDU transferred count destination): a value counted as a part of the network data collection

[4916] Errored L3-PDU count (destination): 0

[4917] L2-PDU transferred count destination): a value counted as a part of the network data collection

[4918] Errored L2-PDU count (destination): 0

[4919] Relating to the L3-PDU transferred count, the cells are counted after dividing DAs into individual addresses and group addresses, and the sum is reported.

[4920] The L3-PDU transferred count and the L2-PDU transferred count include the count values of normal PDUs and errored PDUs.

[4921] The errored PDU count indicates the number of errors relating to the protocol performance monitor and is reported in this status.

[4922] The number of errors at the destination is set to 0. At the source, various checks are made in the L2 and L3. In the case of the L2, each error is individually counted, and is also counted for sum or errors. Accordingly, a sum of errors is also reported. In the case of the L3, errors are either individually counted or counted for a sum of errors. Therefore, each sums are reported.

[4923] In the process in which a TCA is generated when an error count value exceeds a threshold, the firmware autonomously generates a status to the software when the firmware detects that the error count value exceeds the threshold. This relates to the sum of errors algorithm. There are two variations of autonomous status to the L2 and L3.

[4924] The software generates a TCA message in response to an autonomous status, and the message requires an SNI number. The SBMESH contains 32 SNIs and there is a 32-bit area each corresponding to each SNI. The area indicates the existence of the SNI (corresponding to on/off of each bit) exceeding the threshold. The software obtains an SNI number from the bit number. The following points should be carefully considered.

[4925] The hardware error counter has two phases which are switched according to the collection phase switch request command from the software. A new hardware access phase starts counting from 0. For a sum of errors, the count value is increased and exceeding (at SNIx) and an autonomous status is generated to the software. In this status, it is reported that only the SNIx exceeds the threshold.

[4926] Assume that the time further passed (before the next collection phase switch request command) and the SNI y exceeds the threshold. In this case, an autonomous status is generated, and the information is transmitted reporting about a newly exceeding SNI y and the previously exceeding SNI x. At this time, the software adopts the method of, for example, a last look, etc. and generates only the sum of error TCA of the newly exceeding SNI y.

[4927] Regarding a bursty error, the hardware only performs a counting operation, calculates a ratio by being triggered by the collection phase switch request command from the software. If the obtained value exceeds the threshold, it is reported to the software in the autonomous status (different from the sum of errors of the L2 and L3 described above). Like the autonomous status related to the sum of errors, there is a 32-bit area corresponding to each of the 32 SNIs and indicating the existence of an exceeding condition in the SNI represented by on/off of each bit.

[4928] If the hardware of the SBMESH is normal, system 1 exceeds the threshold if system 0 exceeds the threshold. However, an autonomous status is issued by the master system only.

[4929] According to the TR-774, it is requested that the threshold should be altered, the present count should be read, and the present count value should be cleared relating to the protocol performance monitor. These processes can be performed by the limit value change request command, current performance information request command, current performance counter clear request command respectively.

[4930] If an error occurs and it requires logging, it is reported in the protocol performance log notification status. The data (and the autonomous status related to the above described TCA) is transmitted to the transmission area for the software. Basically, the area reported by the INF initial data entry command is used. If the firmware recognizes that the area is running short, it sends a logging buffer request status to the software and uses the area reported by the logging buffer entry command. If no area report is made about the logging buffer entry command from the software to the logging buffer request status, the logging data is discarded. Unlike the billing buffer, this logging buffer does not activate the timer or retrial process.

[4931] 11.7.4. Network Data Collection Process

[4932] The SBMESH performs a network data collection process according to the TR-774. In addition to the detailed explanation in Chapter 7, described below are supplementary descriptions. The following two network data collection processes are required.

[4933] (1) Storing various count values at every 15th minute

[4934] (2) Occurrence of an error log

[4935] Each of the counters has a duplex configuration for the hardware, and the two phases are switched according to the collection phase switch request command from the software. The software picks up during the 15 minutes to the next issue of the command a count value of the past 15 minutes according to the traffic measurement information request command. Each of the various count values for each 15 minutes is stored by the software.

[4936] The following points should be carefully considered about the response status.

[4937] The six count values of total originating L3-PDUs through total terminating group addressed L3-PLUs contain not only the number of normal PDUs but also that of errored PDUs. The two count values of total originating/terminating L3-PDUs refer to the L3-PDU whose DA is of an address type. The true sum is a total of this count value and the total originating/terminating group addressed L3-PDUs. The four count values of and after the L3-PDUs discarded by congestion controls don't include the present hardware which is processed as “don't care”.

[4938] As in the protocol performance monitor process, the present count value can be read and cleared according to the current traffic information request command and current traffic counter clear request command respectively.

[4939] If an error occurs and it requires logging according to the TR-774, it is reported in the traffic measurement log notification status. The data is transmitted to the transmission area for the software. Basically, the area reported by the INF initial data entry command is used. If the firmware recognizes that the area is running short, it sends a logging buffer request status to the software and uses the area reported by the logging buffer entry command. (used in combination with protocol performance log).

[4940] If no area report is made about the logging buffer entry command from the software to the logging buffer request status, the logging data is discarded. Unlike the billing buffer, this logging buffer does not activate the timer or retrial process.

[4941] 11.7.5. Various Cell Number Process

[4942] When the software issues a discarded cell number request command, the number of discarded L2-PDUs and L3-PDUs in the VC-shaper (block having the shaping function) at the output unit of the SMLP and RMLP can be calculated. The count value is used to control the traffic (especially when the SBMESH is increased or decreased in number) of the entire system. A practical usage is determined by the traffic WG.

[4943] As in the protocol performance monitor process, the present count value can be read and cleared by the current discarded cell number request command and current discarded cell number clear request command respectively.

[4944] Various error countings are made in the SBMESH. They are conducted in response to an independent count information request command. When these errors occur, error cells are discarded and the number of the discarded cells is counted. These error count values can be not only read by the command entered by the maintainer, but also used in a fault correcting process.

[4945] These count values can be read and cleared by the current independent count information request command and current independent count clear command respectively.

[4946] [0012]

[4947] <part 6>

[4948] In part 6, the gateway message handler (GWMH) is explained in detail.

1. GENERAL DESCRIPTIONS

1.1 Summary

[4949] The gateway message handler shelf (GWMESH) is a device for converting data between SMDS switches. In the switching process, the message format is carefully considered, but only cells are actually switched. In protocols, level 2 (AAL-SAR) and level 3 (AAL-CS and CL) of the SNI interface protocol (SIP) which is a subscriber protocol of the SMDS are terminated.

[4950] 1.1.1 Position in System

[4951] FIG. 496 shows one switching system and the position of the GWMESH in the system. FIG. 496 mainly shows the GWMESH (and the above described SBMESH) in the entire configuration shown in FIG. 8 in part 1 of this embodiment. The SIFSH containing the DS3, etc. is explained in parts 2 and 3. The SIFSH having the LLP is the SIFSH shown in FIG. 9 of part 1.

[4952] Up to four GWMESHs can be daisy-chained to each highway connected to the ASSW. A GWMESH group connected to a highway is called a GWMH. The relationship between the GWMESH and the GWMH is the same at that between the SBMESH and the SBMH.

[4953] In FIG. 496, the SNI is short for a subscriber network interface to which an actual SMDS subscriber is connected. The ISSI is short for an intra-switching system to which another switching system (SS) is connected. The ICI is short for an inter-carrier interface to which another LATA is connected through a carrier.

[4954] The GWMESHs (GWMHs) are grouped into incoming (IC) units and outgoing (OG) units. Data input through the ISSI or the ICI is processed in the IC unit of the GWMESH, and the data processed in the OG unit of the GWMESH is output to the ISSI or ICI.

[4955] 1.1.2 Route for SMDS Data Process

[4956] FIGS. 497 through 591 illustrate the summary of the routing process of the SMDS data in the SBMESH and GWMESH. The explanation partially doubles that of the SBMESH.

[4957] FIG. 497 shows the process of the SMDS data between the SNIs accommodated in the switching system.

[4958] When data is transferred from SNI-1 to SNI-2, as shown in FIG. 497, the data (message) output from the SNI-1 is terminated by SIFSH 11, decomposed into one or more cells, and input to the SBMH(S) through a fixed path or a semi-fixed path (PVC) set between the above described SIFsh 11 and the SBMH(S). The VPI/VCI specifying the above described PVC is written to the header field of the cell.

[4959] The SBMH(S) recognizes from the address information (destination address DA) stored in the cell that the cell destination subscriber is accommodated in the home switching system, and writes and outputs the value indicating the PVC set between the SBMH(S) and SBMH(R) as the VPI/VCI of the cell.

[4960] The path from the above described SBMH(S) to the SBMH(R) is established through the SIFSH 12 as shown in FIG. 497. According to the configuration of the SIFSH 12 shown in FIG. 9, the VCC is set in the SIF-COM unit as in the SIFSH described in part 3 of this embodiment. When the data is transferred, the cell output from the SBMH(S) is first transferred to the SIFSH 12 and then output to the SBMH(R) through the VCC in the SIFSH 12. These paths are also connected through the PVC.

[4961] The SBMH(R) which received the cell recognizes the SIFSH (SIFSH 11) accommodating the SNI-2 according to the address information stored in the cell, and writes and outputs the VPI/VCI indicating the PVC set between the SBMH(R) and the above described SIFSH 11.

[4962] Thus, in the SMDS data process between SNIs accommodated in the same switching system, no GWMESH is used and the routing is set only through the SBMH(S) and SBMH(R).

[4963] Described below briefly is the path specifying method.

[4964] The VPI/VCI is specified in the SBMH(S) or SBMH(R) according to the address information (DA) stored in the cell. The specification is not performed on all cells, but on each message output from the SNI-1. That is, if the message is decomposed into a plurality of cells, the DA of the message is stored at a predetermined position in the payload of the BOM (SSM if the message is converted into a single cell). The SBMH(S) or the SBMH(R) sets on the table the correspondence between the input VPI/VCI and input MID and the output VPI/VCI according to the above described address information. When the SBMH(S) or SBMH(R) receives the COM and EOM preceded by the BOM, the VPI/VCI to be written to the cell is obtained, assigned, and output by retrieving the table using as a key the input VPI/VCI and input MID in the COM and EOM.

[4965] Thus, a message of any length is routed in cell units. At this time, the routing process of a COM and EOM is performed in hardware only on the input VPI/VCI and input MID. Since the process is not performed in the layer 3 (or layers in higher order) which requires a software process, it can be performed at a high speed. The SBMH(S) or SBMH(R) is described above, but the descriptions can be applied to the GWMH(I) or GWMH(O).

[4966] FIG. 498 shows the process of the SMDS data in SNI→ISSI or ICI. In FIG. 498, the process is performed similarly with the example shown in FIG. 497 up to the steps in which the message output by the SNI is decomposed and input to the SBMH(S). However, since the destination subscriber of the message is accommodated in another switching system in this process, the GWMH is used. That is, in the SBMH(S), the VPI/VCI specifying the PVC set between the SBMH(S) and the GWMH(O) accommodating the above described destination subscriber is written to the header of the cell, and the cell is output. (Actually, it is actually transferred through the SIFSH 12). When the GWMH(O) receives the cell, it writes the VPI/VCI specifying the PVC set between the GWMH(O) and the GWMH(I) of the other switching system to the header field of the cell, and outputs the cell.

[4967] FIG. 499 shows the process of the SMDS data in ISSI or ICI SNI. As shown in FIG. 499, a cell input from another switching system to the present switching system is input to the GWMH(I). In this case, the GWMH(O) of the other switching system writes and outputs the VPI/VCI indicating the PVC between the GWMH(O) and the GWMH(I) of the present system to the header field of the cell. When the above described GWMH(I) recognizes the destination of the received cell as the subscriber accommodated in the present system, it writes the VPI/VCI indicating the PVC between the GWMH(I) and SBMH(R) to the header field of the cell, and outputs it. (Also in this case, the data is actually transferred through the SIFSH 12). The SBMH(R) transfers the above described cell to the destination subscriber.

[4968] FIG. 500 shows the SMDS data process in ISSI or ICI→ISSI or ICI. In this case, the present system relays the data when the data (message) is transferred from the subscriber accommodated in the other switching system to the subscriber accommodated in the other switching system.

[4969] As described above by referring to FIG. 500, the description is the same as that for FIG. 499 where the cell input from another switching system to the present switching system is input to the GWMH(I). When the GWMH(I) recognizes that the destination of the cell refers to the other switching system, it writes the VPI/VCI specifying the PVC between the GWMH(I) and GWMH(O) to the header field of the cell and outputs the cell. Then, the GWMH(O) writes the VPI/VCI indicating the PVC set between the GWMH(O) and the GWMH(I) accommodating the above described destination subscriber to the header field of the cell and outputs the cell. (Also in this case, the cell is actually transferred through the SIFSH 12).

[4970] Described next is the SMDS data process performed according to the address.

[4971] (1) For individual addresses, group addresses other than GAA (home switching system is not the agent of the GA), and embodied SAC

[4972] The data from the ICI and ISSI is transferred to the GWMESH(I) via the fixed or semi-fixed path (PVC) of the ASSW(UP). The GWMESH(I) retrieves the route to the SBMH(R) and GWMH(O) accommodating the destination SNI, ICI, and ISSI by analyzing the address type and destination address (DA:E164 address) in the data, adds the retrieved route to the output data, and outputs the data to the ASSW(UP). the GWMESH(I), SBMH(R), and GWMH(O) are connected through the PVC.

[4973] The data is input to a predetermined SBMH(R) or GWMH(O) through the ASSW(UP), LLP, and ASSW (DOWN). The SBMH(R) or GWMH(O) refers to the DA in the data, filters only the data to the SNI (for the SBMESH) or ICI, and ISSI (for the GWMESH) accommodated in the present switching system, retrieves the route to the destination SNI or ICI, and ISSI, and output the data to the ASSW (DOWN). The SBMH(R) or GWMH(O), SNI or ICI, and ISSI are connected through the PVC.

[4974] (2) For group addresses of GAA

[4975] The processes are the same as (1) above up to the entry of the data from the ICI and ISSI to the present system and the entry to a predetermined SBMH(R) or GWMH(O). The SBMH(R) or GWMH(O) refers to the DA of the filtered data and performs the following processes when it recognizes that the home switching system is the GAA of the GA.

[4976] The SBMH(R) copies data for the subscribers connected to the SNI accommodated by the home switching system, converts the GA into the individual address of each subscriber, assigns the address to each piece of the copied data, and transfers the data.

[4977] When data is transferred to another switching system through the ICI and ISSI, the GWMH(O) copies the data, converts the data into an individual address from the above described GA, and transfers the data.

1.2 System Configuration

[4978] As shown in FIG. 501, the GWMESHs are grouped into MH-COMs and LPs for performing an actual switching process.

[4979] The MH-COM comprises the SDMX, RDMX, SMUX, and RMUX. The unit starting with S corresponds to the GWMESH(I) and that starting with R corresponds to the GWMESH(O). The DMX demultiplexes the data from the ASSW and fetches the data to the home shelf. The MUX multiplexes the data from the home shelf and sends the data to the ASSW. The GWMESH further comprises the LAP terminating unit and VCC not shown in the figures. The VCC is set at LAP from the BSGC. The information about each checker in the MH-COM unit is interfaced with the software by the LAP using the BSGC.

[4980] The LP unit is grouped into the incoming, outgoing, and LP-COM units. The incoming and outgoing units correspond to the GWMESH(I) and GWMESH(O) respectively, and relate to data switching functions. The LP-COM is the control unit for the incoming and outgoing units, and interfaces with the software at through the INF. The various station data, subscriber data, checker information in the LP, and billing information are interfaced with the software through the INF. Hereinafter, the incoming unit of the LP unit is referred to as the ICLP, and the outgoing unit is referred to as the OGLP.

[4981] As described above, up to four GWMESHs can be daisy-chained to each highway of the ASSW with the LP unit and the INF connected one to one. Therefore, when four GWMESHs are daisy-chained to a highway, four paths are required from the INF (precisely INFA).

1.3 Redundant Configuration

[4982] FIG. 502 shows the redundant configuration of the GWMESH.

[4983] Each of the MH-COM and LP are duplex. The MH-COM is a duplex system in the master/slave format exclusive to the ASSW, while the LP is an independent duplex system. A switching operation is performed in the LP of a slave system, but the slave system does not notify the software of the billing information.

[4984] The inter-system interconnection exists between the duplex MH-COM and LP. That is, information can be communicated between the #0 of the MH-COM unit and #1 of the LP unit and between the #1 of the MH-COM unit and #0 of the LP unit. No inter-system interconnection exists between the LP unit and INF.

[4985] For example, data are input from the RDMX of the MH-COM #0 and the RDMX of the MH-COM #1 to the outgoing unit of the LP #0. In the outgoing unit of #0 of the LP unit, the selector (not shown in the drawings) provided at the input unit selects the data from the RDMX of the master system in the above described #0 and #1. Likewise, data is input from the incoming unit of the LP #0 and the incoming unit of the LP#1 to the SMUX of the MH-COM #0. In the SMUX of the MH-COM #0, the selector (not shown in the drawings) provided at the input unit selects the data from the incoming unit of the master system in the above described #0 and #1.

2. PROCESS METHOD

2.1 Network Configuration

[4986] FIG. 503 shows an example of the SMDS network configuration. As shown in FIG. 503, the subscriber terminal (corresponding to CPE) is accommodated in the switching system SS through the SNI. Each SS is connected to each other through the ISSI in a network (corresponding to the LEC, BOC, and ILEC in FIG. 503). The communications with the SS accommodated in another network is made through the ICI. The system shown in FIG. 496 is provided for each SS.

2.2 Routing System

[4987] FIG. 504 shows an example of the routing process performed when data is transferred using an individual address. FIG. 505 shows examples of four types of communications paths shown in FIG. 504 together with the network configuration. In this case, each SS determines a destination by referring to the DA.

[4988] (1) The intra-SS communications refer to the communications between the customer premise equipment CPE(A) and CPE(B) accommodated in the same SS 1. In this case, the SS 1 performs the process shown in FIG. 497.

[4989] (2) The intra-LEC communications refer to the communications from the CPE(A) accommodated by the SS 1 to the CPE(C) accommodated by the SS 2. In this case, the SS 1 performs the process shown in FIG. 498, and the SS 2 performs the process shown in FIG. 499.

[4990] (3) The ex-LEC intra-LATA communications refer to the communications from the CPE(A) accommodated by the SS 1 to the CPE(D) accommodated by the SS 5 in another LEC in the LATA of the SS 1. The SS1 is connected to the SS 3 in the same LEC through the ISSI, and the SS4 is connected to the SS5 in another LEC through the ISSI. In this case, the SS 1 performs the process shown in FIG. 498 and the SS5 performs the process shown in FIG. 499. The SS3 and SS4 perform the process shown in FIG. 500.

[4991] (4) The ex-LATA communications refer to the communications from the CPE(A) accommodated by the SS 1 to the CPE(F) accommodated by the SS 8 in the network of the LATA accommodating the SS 1. The SS1 is connected to the SS 6 in the same LEC through the ISSI. The SS 7 is connected to the SS 8 in another LEC through the ISSI. Furthermore, the SS 6 is connected to the SS 7 in the ICI through the IC network. In this case, the SS 1 performs the process shown in FIG. 498, and the SS 8 performs the process shown in FIG. 499. The SS 6 and SS 7 perform the process shown in FIG. 500.

2.3 Group Address Process

[4992] FIG. 506 shows an example of the process of transferring data using a group address. FIGS. 507 through 509 show examples of the three types of communications paths shown in FIG. 506 together with the network configurations. Each SS refers to a DA (GA in this example). If the SS determines that the GA is within a specified area, the SBMESH or GWMESH accommodated in the SS copies input data and transfers the data to all SSs. The data transfer up to the input to the GA-specified area GAA is the same as the transfer of data having individual addresses as shown in FIG. 504.

[4993] (1) A case in which the home LEC is a GAA refers to the communications in which the CPE(A) accommodated in the SS 1 in the GA-specified area GAA is a data source. In this case, data is copied in the SBMH accommodated in the SS 1. As shown in FIG. 507, the data is transferred to all the other SSs.

[4994] (2) A case in which the other ILECs in the LATA are GAAs refers to the communications in which the data source CPE(E) is accommodated by the SS 2, the ILEC containing the SS 2 is external to the GA-specified area GAA (LEC network (GAA) shown in FIG. 508), and the SS 2 and GAA are in the same LATA. The transfer from the CPE(E) to the SS 4 is the same as the transfer using specified individual addresses. Data is copied in the GWMH accommodated in the SS 4, and the data is transferred to all the other SSs as shown in FIG. 508.

[4995] (3) A case in which the GAA is external to the LATA refers to the communications in which the data source CPE(G) is accommodated in the SS 5, the ILEC having the SS 5 is external to the LATA to which the GA-specified area GAA (LECNetwork (GAA) shown in FIG. 509) belongs (connected through the ICI). The transfer from the FPE(G) to the SS 7 is the same as the transfer using specified individual addresses. Then, data is copied in the GWMH accommodated in the SS 7, and transferred to all the other SSs as shown in FIG. 509.

2.4. Load Splitting

[4996] Load splitting refers to sharing a load among a plurality of links when there are two or more physical (or logical) links in the ISSI connecting two SSs or in the ICI connecting an SS and the POP of other carriers. If there are a plurality of paths between the SSs, that is, if two SSs are connected through different relays SS, the load is not split to the paths. FIG. 510 shows the image of the link.

[4997] As a rule, a message having a pair of the same DA and SA uses the same link as long as the state of the link remains unchanged. Thus, the transfer sequence is maintained between the messages having the same DA and SA. If the DA and SA are picked up at random, the load in each link is balanced. To attain this, the load splitting comprises the following two steps.

[4998] Key generation

[4999] A key to a value in a range (key space) is generated according to the DA and SA of a message.

[5000] Key assignment

[5001] A message is assigned to an actual link according to the key of the message.

[5002] 2.4.1 Features of Load Splitting

[5003] The ISSIs connecting the SSs in the network of the same carrier or the ICIs connecting the SS-POPs, that is, the ISSIs (ICIs) belonging to the same ISSI (ICI) link set are accommodated in the same GWMH (refer to FIG. 511).

[5004] The following load splitting algorithm is applied to the IA data (data having specified individual addresses) and the group address GA data not copied in each SS (GWMH), and the data is then processed in the corresponding GWMESH. The load splitting algorithm is based on a well-known algorithm (for example, TR-1059, issue 2, chapter 9). If plural copies of GA data (that is, the data to be developed to IA) are transmitted to the same link set in each SS, then each ISSI (ICI) link is allocated to each of the assigned IAs.

[5005] Described below is the load splitting algorithm applied when no copies are made.

[5006] 2.4.2. Key Generation

[5007] A 16-bit key is generated by performing a CRC-16 division on a bit string of a DA and SA. Since a key is generated for each piece of data, it is performed by the hardware. The key generation is performed in the following procedure.

[5008] (a) polynomial:

[5009] L(x)=X¹⁵+x¹⁴+x¹³+ . . . +x+1

[5010] generation polynomial:

[5011] G(x)=x¹⁶+x¹²+x⁵+1

[5012] (b) A 128-bit string F(x) is generated for a pair of a DA and an SA to set the MSB of the DA at the MSB and the LSB of the SA at the LSB. That is, if the bit string of the DA is D(x) and the bit string of the SA is S(x), the string is generated by the following equation.

[5013] F(x)=X64·D(x)+S(x)

[5014] (c) The residue R(x) obtained by dividing F(x)·x16+L(x)·x128 by the above described generation polynomial G(x) is set as a load splitting key.

[5015] 2.4.3 Key Assignment

[5016] In assigning a key, a message is assigned to each active link according to the key generated as described above. That is, key space is divided. Each divided key space is assigned to an active link. A key is generated for a message. When the key is in the range assigned in the link, the message is transferred through the link.

[5017] The default value of an assigned key range is proportional to the ISSI/ICI link band. The value can be altered by a command. The assignment can be performed by the software in consideration of the assignment covering plural GWMESHs, and the key is reported for each link to the hardware. In the hardware, the data is obtained in a predetermined link after being processed and determined by the GWMESH according to the generated key.

[5018] FIG. 512 shows the load splitting algorithm.

3. ICLP

3.1 Summary of Process

[5019] The ICLP performs an ICIP/ISSIP L2 and L3 protocol performance check on the cell demultiplexed according to the information of a tag added to the header of the cell in the MH-COM corresponding to the incoming shown in FIG. 501 and input as 156 Mbps data. The ICLP also analyzes the DA (destination address) of the cell and transmits the cell to the SBMH accommodating the corresponding subscriber (SNI) and the GWMH accommodating the corresponding ISSI/ICI.

3.2 Configuration

[5020] FIG. 513 is a block diagram showing the entire configuration of the ICLP. As shown in FIG. 513, the ICLP comprises three PWCBs HMH11A through HMH13A.

[5021] The HMH11A mainly performs a protocol performance check. An erroneous cell is indicated by an error flag transferred concurrently with the cell. After performing a predetermined process on the contents of the error flag, the erroneous cell is finally discarded by the output unit of the HMH13A. The HMH12A mainly performs a routing process which is a DA analyzing and destination MH determining process. The HMH13A mainly performs a band limiting process on the PVC between the ICLP and RMLP/OGLP. FIG. 514 shows the table listing the functions of each block of the ICLP.

[5022] FIG. 514 shows as a supplementary list the functions of the ICLP.

[5023] (1) Checking Order

[5024] The protocol performance check is performed in the order shown in FIGS. 515 and 516.

[5025] When a CRC-10 error occurs at the initial stage of the check, it indicates erroneous data in the ICIP/ISSIP L2. If the protocol performance check is performed using the erroneous data, the error may be further developed. Therefore, if the CRC-10 error is detected, no subsequent protocol performance check should be made to alter the table.

[5026] For example, if a MID value is erroneous, an ICIP/ISSIP L3 message may be implied. This holds true also with payload length error and encapsulation error. Accordingly, if the CRC-10 error occurs, no such checks should be made.

[5027] (2) Error Cell Discard Process

[5028] An error cell is identified by an error flag (EF1 MS) indicating NG (in this case, the flag is set ON at NG), and should be discarded. In the case of “BOM with unexpected MID” (BOM having an MID other than a predetermined value), the cell is not discarded. The memory is used for various uses in the ICLP, and there is the function of skipping the write access to the memory if an error occurs.

[5029] (3) LP Test Cell (diagnostics)

[5030] In the diagnostics of the GWMESH, a test cell is transmitted from the HLP07A (in the LP-COM unit) and returned to the HLP07A through each processing unit in the ICLP unit to check the error flag.

[5031] This diagnostics is made when the ICLP is in the OUS state (out of service state). The subscriber data for use in the test for each link is set on an actual table because there is no test table. An LP test cell having no error flag is not discarded but transmitted to the MUX of the MH-COM. Since this ICLP is not in a master state (that is, in the OUS state), the test cell is discarded by the selector in the input unit of the MUX.

[5032] (4) PVC Test

1. MESH-MH PVC TEST

[5033] The HLP07A transmits a test cell to the ICLP in this test. The test cell is transmitted from the ICLP to the object SMLP/OGLP through the ASSW. The OGLP transmits this test cell to the HLP07A to check the normality of the cell.

[5034] The DA, etc. of this test cell is set by a specific VCI value (FF) and transmitted from the HLP07A. The ICLP recognizes the test cell if the test cell identification bit (bit 7) in the VCI indicates 1, and performs a corresponding process. Since this test is conducted in an INS state (in service state), no protocol performance check is made not to affect a normal message.

[5035] If an allocated-DA test is conducted in this test, the SNI/link of the destination MH is blocked. Refer to the error flag table shown in FIGS. 515 and 516 for details.

2. LINK-GWMESH PVC TEST

[5036] The HLP07A transmits a test cell to the OGLP in this test. The test cell is looped back in the test object link and input to the ICLP. Each checker of the ICLP performs on this cell a process for a normal cell. The routing unit determines whether or not the cell is a test cell according to the DA. If it is a test cell, it is transmitted to the HLP07A with the VCI set to ‘FF’(h).

[5037] This test is conducted with the link blocked. Refer to the error flag table shown in FIGS. 515 and 516 for details.

3. LOOPBACK TEST

[5038] The HLP07A transmits a test cell to the OGLP in this test. The test cell is looped back by a specified SS and input to the ICLP. Each checker of the ICLP performs on this cell a process for a normal cell. The routing unit determines whether or not the cell is an NME cell addressed to the home station according to the DA. If it is an NME cell addressed to the home station, it is transmitted to the HLP07A with the VCI set to ‘FF’(h). Refer to the error flag table shown in FIGS. 515 and 516 for details.

3.3 Correspondence Between Each Function Block and Error Flag

[5039] An error flag (EF) operating for each function block of the ICLP is shown in FIGS. 515 and 516. FIGS. 515 and 516 also show the conditions under which each function block operates. The table shown in these figures is used as follows.

[5040] The vertical axis indicates a function block.

[5041] The horizontal axis indicates an error flag EF (EF1 and EF2) and the state of an inter-MESH PVC test.

[5042] Each item is divided into upper entry and lower entry. The upper entry indicates an EF which turns to NG after a check of a functional block. If the state is NG, an EF described as ON is controlled. The lower entry indicates the conditions under which the functional block should be operated (or the functional block should be checked) or the check result should be reflected on the EF. Refer to the LP-COM in chapter 5 for the correspondence between an error flag (EF) and an error name (name according to the TR) and for the position of the EF.

3.4. ICLP Input/Output Format

[5043] FIGS. 517 through 522 show the formats of an input cell to the ICLP.

[5044] FIGS. 523 through 528 show the formats of an output cell from the ICLP.

[5045] FIGS. 529 and 530 show the formats of an input/output cell of the HMH12A of the ICLP.

[5046] FIGS. 531 through 542 show the formats of an input/output cell of the HMH13A of the ICLP.

3.5 ICLP Process Flow

[5047] FIG. 543 is a check flowchart followed when the ICLP receives a message. FIGS. 544 and 545 show a message routing flow in the ICLP. The numbers 1 through 6 shown in FIGS. 544 and 545 indicate the corresponding processes.

3.6 PKG Block

[5048] 3.6.1 HMH11A

[5049] 3.6.1.1 Summary of Function

[5050] FIG. 546 is a block diagram showing the HMH11A. The HMH11A has the following functions.

[5051] (1) Function of checking the consistency of a message entered from the ICI

[5052] (2) Function of checking the consistency of a message entered from the ISSI

[5053] (3) function of generating a pseudo-EOM to release the function of each unit of the device when a message is lost

[5054] (4) function of converting the cell format of the ICI/ISI into the inter-MESH interface cell format

[5055] 3.6.1.2 External Terminal Unit

[5056] FIG. 547 is a table showing the external terminal of the HMH11A.

[5057] 3.6.1.3 Block Diagram and Explanation of Functions

[5058] FIGS. 548 through 553 show the circuits of the important portions of the HMH11A. FIGS. 554 through 560 shows the timing in checking messages.

[5059] 3.6.2 HMH12A

[5060] FIG. 561 is a block diagram of the HMH12A.

[5061] FIG. 562 is a process flowchart of the routing function of the HMH12A.

[5062] FIG. 563 is a process flowchart of the broadcast function of the HMH12A.

[5063] FIGS. 564 and 565 is a process flowchart of the copy control of the HMH12A.

[5064] FIGS. 566 is a process flowchart of transmitting a pseudo-EOM.

[5065] 3.6.3 HMH13A

[5066] FIG. 567 is a block diagram of the HMH13A. The HMH13A has the following function.

[5067] 1. Output band control

[5068] 2. Output MID acquisition

[5069] 3. VPI/VCI reassignment

[5070] 4. Discarded cell number count

[5071] 3.6.3.1 Output band limit

[5072] The burst property is absorbed by periodically reading data using a buffer memory and the output band from the ICLP to the OGLP or RMLP is controlled. This function can be realized by the VC-SH LSI shown in FIG. 567. FIG. 568 shows the configuration of the circuit of the VC-SH LSI for controlling the output band and the units around it.

[5073] 3.6.3.2 Acquisition of Output MID

[5074] The output MID acquiring unit assigns the MID corresponding to the output VCI. This function is realized by the MOCTL LSI shown in FIG. 567. FIG. 569 shows the configuration of the circuit of the output MID acquiring unit. FIG. 570 shows the table for use in the output MID acquiring process. FIG. 571 is a flowchart showing the process of reserving an output VIC.

[5075] If the EOM of an L3-PDU is lost and the EOM is not input to the HMH13A, the output MID reserved for each L3-PDU is not released from the table shown in FIG. 570. To avoid this, the MOCTL LSI monitors the timeout of the system. FIG. 572 is a flowchart showing the process of the timeout monitor.

[5076] 3.6.3.3 Reassignment of VPI/VCI

[5077] FIG. 573 shows the format of re-assigning a VPI/VCI. FIG. 574 shows the configuration of the hardware for reassigning a VPI/VCI.

[5078] 3.6.3.4 Discarded Cess Number Count

[5079] Since the buffer size is limited in the GA copy unit (HMH12A) and output band limit unit (HMH13A) in the ICLP, cell may be discarded through the overflow of the buffer depending on the burst data size. The discarded cell number count unit accumulates the number of discarded cells according to the discarded cell signal received from the HMH12A, and sequentially adds the result to the number of discarded cells obtained in the output band limit unit, and records the sum to the DP-RAM (a two-phase configuration RAM corresponding to the discarded number write table shown in FIG. 567). The HLM03A accesses the DP-RAM to perform the NDC process.

[5080] 3.6.3.5 Fault Monitor

[5081] The HMH13A is connected to the duplex MH-COMs and therefore has the home system fault monitor function and mate system fault monitor function. FIG. 575 shows the configuration of the home system fault monitor. FIG. 576 shows the configuration of the mate system fault monitor.

4. OGLP

4.1 Summary of Process

[5082] The OGLP refers to the destination address DA in the message input from the MH-COM, filters only the message addressed to the home MESH, and performs an ICIP/ISSIP L2 and L3 protocol performance check. It also determines an output link according to the VCI value, splits a load according to the SA and DA values, performs the GA process, and sends cells to each link.

4.2 Configuration

[5083] FIG. 577 is a block diagram showing the outline of the functions of the OGLP unit. FIG. 578 is a block diagram showing the detailed functions of the OGLP unit. FIG. 579 is a block diagram showing the IC arrangement of the OGLP unit.

[5084] The OGLP unit comprises four PWCBs HMH07A through HMH10A.

[5085] The HMH07A makes a DA filtering, that is, determines whether or not the input data is to be received according to the destination address DA. The HMH08A splits a load, that is, controls the distribution of a load. The HMH09A converts a group address GA into IA, that is, converts the GA into an individual address IA implied by the GA according to the GA of the input data. The HMH10A limits the band of the PVC between the OGLP and OSSI/ICI.

[5086] FIG. 580 shows the outline of the functions of each block of the OGLP unit and the process for error cells and maintenance cells. FIG. 580 shows the functions of the OGLP unit.

[5087] (1) Error Cell

[5088] Error cells are indicated by a master error flag (EFI MS) set ON (as NG), and to be discarded. The OGLP uses the memory for various uses and skips the write access to the memory. Refer to the outline of the functions shown in FIG. 580 for details.

[5089] (2) LP Test Cell (diagnostics)

[5090] In the diagnostics of the GWMESH, the HLP07A sends a test cell and receives it back from each processing unit in the OGLP to conduct an error flag test.

[5091] This diagnostics is made in the OUS state of the OGLP unit. The subscriber data for use in a test for each link is set on an actual table. No test table is provided. Therefore, an LP test cell which has no error flag set is not discarded, but is sent to the MUX of the MH-COM. Since the OGLP unit is not in a master state (OUS) when this diagnostics is made, the above described test cell is discarded by the selector of the input unit of the MUX.

[5092] (3) PCV Test

[5093] 1. MESH-MH PVC test

[5094] The HLP07A transmits a test cell to the ICLP in this test. The test cell is transmitted from the ICLP to the OGLP through the ASSW. The OGLP transmits this test cell to the HLP07A to check the normality of the cell.

[5095] A specific VCI value (FF) of this test cell is set and transmitted from the HLP07A. The ICLP recognizes the test cell if the test cell identification bit (bit 7) in the VCI of the input cell indicates 1, and performs a corresponding process.

[5096] Practically, since this test is conducted in an INS state, no protocol performance check is made not to affect a normal message. Refer to the outline of the functions shown in FIG. 580 for details.

[5097] 2. Link-GWMESH PVC test

[5098] The HLP07A transmits a test cell to the OGLP in this test. The test cell is looped back in the test object link and input to the ICLP. Each checker of the ICLP performs on this cell a process for a normal cell. The routing unit determines whether or not the cell is a test cell according to the DA. If it is a test cell, it is transmitted to the HLP07A with the VCI set to ‘FF’(h).

[5099] This test is conducted with the link blocked. Refer to the outline of the functions shown in FIGS. 580 for details,

4.3 Correspondence Between Each Function Block and Error Flag

[5100] FIG. 581 shows an error flag (EF) operating for each function block of the LP. FIG. 581 also shows the conditions under which each function block operates. The table shown in these figures is used as follows.

[5101] The vertical axis indicates a function block.

[5102] The horizontal axis indicates an error flag EF (EF1 and EF2) and the state of an inter-MESH PVC test.

[5103] Each item is divided into upper entry and lower entry. The upper entry indicates an EF which turns to NG after a check of a functional block. If the state is NG, an EF described as ON is controlled. The lower entry indicates the conditions under which the functional block should be operated (or the functional block should be checked) or the check result should be reflected on the EF.

4.4 Cell Format

[5104] FIGS. 582 through 628 show the format of the cell of each segment type in each unit of the OGLP.

4.5 Process Flow

[5105] FIG. 629 is a flowchart of the routing process of the outgoing unit in the GWMESH. FIG. 630 is a flowchart of the transfer of GA data shown in the flowchart in FIG. 629. FIGS. 631 through 633 are examples of the tables used in each step shown in FIGS. 629 and 630.

4.6 PKG Block

[5106] 4.6.1 HMH07A

[5107] FIGS. 634 and 635 show the configuration of the circuit of the HMH07A. FIG. 634 corresponds to the cross-connection selection and the units around it shown in the entire block diagram shown in FIG. 578. FIG. 635 corresponds to the DA filtering and the units around it.

[5108] FIGS. 636 and 637 shows the write timing to the FIFO shown in FIG. 634. FIGS. 638 through 640 are time charts of the signal processed by the HMH07A.

[5109] 4.6.2 HMH08A

[5110] FIGS. 641 and 642 shows the configuration of the circuit of the HMH08A. FIG. 641 corresponds to the load splitting, DMUX, and the units around them shown in the entire block diagram shown in FIG. 578.

[5111] FIG. 642 corresponds to the test cell multiplexing and the units around it.

[5112] 4.6.3 HMH09A

[5113] FIG. 643 shows the configuration of the circuit of the HMH09A. FIG. 643 corresponds to the GA copy, IC/ILEC unavailable, and the units around it shown in the entire block diagram shown in FIG. 578.

[5114] FIGS. 644 and 645 are flowcharts of the GA copy process in the HMH09A. FIG. 644 is a flowchart of write control. FIG. 645 is a flowchart of read control.

[5115] 4.6.4 HMH10A

[5116] The HMH10A performs the MRI timeout determination, MID conversion, output band limitation, various error count, format conversion, etc. in the outgoing unit (GWMESH(OG)) of the GWMESH.

[5117] FIG. 646 shows the configuration of the circuit of the HMH10A. FIG. 647 shows the functions of each block of the HMH10A. Described below in detail is each function.

[5118] (1) Parity Check

[5119] A parity check is made on 16 data signals and enable signals input from the HMH09A. The parity bit is odd in number. If the check result indicates an error, an ODPC (“H” for an error) is output and passed to the MSCN unit. A compulsory error can be generated through a pseudo-fault input. This function is realized by the TO CTL LSI. FIG. 648 is a functional block diagram showing the connection between the parity check unit and the units around it.

[5120] (2) MRI Timeout

[5121] The MRI timeout determination is made for each message from its BOM to its EOM. When the BOM is reached, “present time” +“timeout time” is written. The time is referred to when the cell arrives, and the matching time is recognized as the timeout. This function is realized by the TO CTL LSI.

[5122] Generating an idle pattern: The MRI TIME (AND-CAM) is initialized.

[5123] MRI TIME (AMD-CAM): An idle pattern is transmitted at a BOM. Timeout is checked for each cell.

[5124] Generating a TO pattern: A TO pattern is output to the MRI TIME (AMD-CAM) at timeout to release the MID.

[5125] Transmitting a TO cell: The timeout is output instead of the BOM of the timeout message through the setting pin OTOO“H”.

[5126] Cell counter: There are a mode in which each arriving cell (of every type) is counted, and another mode in which only valid cells are counted. Only valid cells are counted in a test. The settings are determined by the MSD.

[5127] FIG. 649 is a block diagram showing the function of the MRI timeout unit.

[5128] (3) MID Conversion

[5129] Conversion is made from an input VPI, VI and MID to an output VCI and MID.

[5130] When a BOM arrives, the input VPI, input VCI, and input MID are written to the AMD CAM (Am9910a).

[5131] If a COM and an EOM arrive, the input VPI, input VCI, and input MID are provided for the AMD CAM, and they match the values written when the BOM cell arrives, then the MID conversion is made using the output VCI, output VPI and output MID as matching addresses. The existence of conversion is determined by a mode pin (DIVM), and a releasing process is performed if a conversion bit allocated EOM is indicated. This function is realized by the TO CTL LSI.

[5132] FIG. 650 is a block diagram showing the function of the MID converting unit.

[5133] (4) Delay of Cell

[5134] The cell delay unit delays a primary signal with the delay required by the timeout determination process and MID conversion process. This function is realized by the TO CTL LSI. FIG. 651 is a block diagram showing the function of the cell delay unit.

[5135] (5) Discard of Error Cell

[5136] An error flag is identified to discard an object cell if the error flag (master flag) indicates L. This function is realized by the TO CTL LSI. Described below is the cell discard conditions in each PWCB.

[5137] Discard condition in HMH08A

[5138] BOM unexpected MID

[5139] COM unexpected MID

[5140] EOM unexpected MID

[5141] encapsulation error

[5142] unexpected sequence number error

[5143] Discard condition in HMH09A

[5144] GA bit error

[5145] GA active error

[5146] ISSI/ICI unavailable

[5147] Discard condition in HMH10A

[5148] MRI timeout error

[5149] Exceed maximum number of CDU

[5150] CDU active error

[5151] FIG. 652 is a block diagram showing the function of the error cell discard unit.

[5152] (6) Output Band Limit

[5153] The output band of each message is limited based on a predetermined band. The band is limited by managing and controlling the interval in time unit of cells of a message. If the interval of cells of a message is reduced in time unit, the flow is increased. If the interval is made larger, the flow is reduced. A band limit parameter is generated based on the contract of each subscriber, provided by the μp unit of the LP-COM, and collectively managed for the table manipulation, setting, etc. The function of limiting a flow is managed by the VC-SH LSI.

[5154] FIG. 653 is a block diagram showing the function of the output band limiting unit. FIG. 654 shows the configuration of the circuit of the VC-SH LSI for limiting the output band and the units around it.

[5155] (7) Format Conversion

[5156] The segment type ST(PI) of a cell is identified, and the cell is converted into the format of the ISSI or ICI. This function is realized by the MH10A LCA.

[5157] FIG. 655 is a block diagram showing the function of the format converting unit. FIG. 656 is a table showing the format conversion process.

[5158] (8) CRC-10 Generation and Assignment

[5159] To confirm the normality of data, a CRC operation is performed for the payload field. The operation result is added to the data and output. A CRC check is made by another PWCB. Then, the occurrence of an error is determined by the PWCB. This function is realized by the MH10A LCA. FIG. 657 is a block diagram showing the function for the CRC-10 generation and assignment unit. FIG. 658 shows the CRC-10 operation.

[5160] (9) Count of Discard

[5161] The number of cells suppressed by the output band limit, the number of discard signals from the HWH08A, and the number of discard signals from the HMH09A are counted and the information is sent to the LP-COM unit. The counter used in the counting operation has the RAM of a duplex configuration, releasing one phase at a request for data from the LP-COM unit and performs the discard counting in the other phase. The phase switch of the RAM is controlled by the RAMCHG signal from the LP-COM. This function is realized by the MH10B LCA. FIG. 659 is a block diagram showing the function of the discard counting unit.

5. MH-COM UNIT

5.1 General Descriptions

[5162] The MH-COM comprises four PWCBs (HMX10A, HMX11A, HMX12A, and HSF05A) and has the following functions. The MH-COM unit is a duplex configuration exclusive to the ATM switch (ASSW) and there are cross connections for signaling and VCC copying between systems. A three important functions of the MH-COM are listed above.

[5163] 1. The data received from the ATM switch is demultiplexed and provided for the LP.

[5164] 2. The data received from the LP is multiplexed and provided for the ATM switch.

[5165] 3. The signalling of the LAP is terminated.

[5166] Since the MH-COM of the GWMESH is the same as the MH-COM of the SBMESH, the detailed explanation is not given here, but the outline of the functions of each PWCB is described as follows.

5.2 HMX10A

[5167] FIG. 660 is a block diagram showing the HMX10A. The HMX10A has the following functions.

[5168] 1. Multiplexing the data from the ICLP (incoming unit of the LP) to the 622 Mbps highway and outputting the result to the ASSW (IMUX function) under the scheduler control from the HMX12A.

[5169] 2. Demultiplexing the data input from the 622 Mbps highway at the output terminal of the ASSW according to the destination address DA of the data and transmitting the data to the OGLP (outgoing unit of the LP). Actually, the DA is checked in the BOM cell. If the data should be demultiplexed, the MID information is recorded, and a demultiplexing process is performed by referring to the recorded MID when the COM and EOM cells arrive.

[5170] 3. Demultiplexing a test cell from the test cell generating unit (TCG) according to the 0-bit value input through the 622 Mbps highway at the output terminal of the ASSW.

[5171] (Demultiplexing as a function different from 2 above).

[5172] Between the ASSW and GWMESH, the data from the ASSW to the ICLP and the data from the OGLP to the ASSW are physically accommodated in a single 50-core coaxial flat cable. The cable is connected to the A connector of the HMX10A. A cable connecting a highway to the downward GWMESH is connected to the B connector of the HMX10A in a daisy chain.

5.3 HMX11A

[5173] FIG. 661 is a block diagram showing the HMX11A. The HMX11A has the following functions.

[5174] 1. Multiplexing the data from the OGLP (incoming unit of the LP) to the 622 Mbps highway and outputting the result to the ASSW (OMUX function) under the scheduler control from the HMX12A.

[5175] 2. Demultiplexing the data input from the 622 Mbps highway at the output terminal of the ASSW according to the tag information of the data and transmitting the data to the ICLP. Demultiplexing a test cell from the TCG according to the 0-bit value.

[5176] 3. Between the ASSW and GWMESH, the data from the ASSW to the OGLP and the data from the ICLP to the ASSW are physically accommodated in a single 50-core coaxial flat cable. The cable is connected to the A connector of the HMX10A. A cable connecting a highway to the downward GWMESH is connected to the B connector of the HMX10A in a daisy chain.

5.4 HMX12A

[5177] HMX12A has the following functions.

[5178] 1. Converting VPI/VCI and assigning switching tag information to a cell multiplexed by the HMX10A and HMXllA (VCC function).

[5179] 2. Multiplexing a test cell from the TCG demultiplexed by the HMX10A and HMX11A to the MUX highway of the HMX10A and HMX11A.

[5180] 3. Scheduler function of multiplexing by means of the HMX10A and HMX11A.

[5181] FIG. 662 is a block diagram of the VCC function. FIG. 663 is a block diagram of the scheduler function.

[5182] In the front connectors of the HMX12A, the A.C connector is used for the inter-system cross-connection of signalling data and B and D connector scheduler function signals in a daisy chain.

5.5 HSF05A

[5183] The HSF05A has the following functions.

[5184] 1. Terminating a LAP signal for use in setting a VCC, monitoring the MSCN in the MH-COM unit, controlling the MSD, etc. by way of the BSGC.

[5185] 2. Generating various timing signals for use in the MH-COM according to the source clock (8 MHz) from the SYNSH.

[5186] FIG. 664 is the block diagram of the HSF05A. FIG. 665 shows the clock system of the SBMESH.

6. PROTOCOL PERFORMANCE MONITOR

6.1 General Descriptions

[5187] The GWMESH performs a protocol performance monitor on the L2-PDU and L3-PDU. This protocol performance monitor is in accordance with the TR-TSV-1061 and TR-TSV-1063 (hereinafter referred to simply as TR-1061 and TR-1063) of the Bell Communication Research. This protocol performance monitor function is realized by the HLM03A PWCB. The protocol performance monitor function of the GWMESH is fundamentally the same as that of the SBMESH.

[5188] FIG. 666 is a block diagram showing the HLM03A for carrying out the protocol performance monitor function. The HLM03A is provided in the LP-COM described later. The HLM03A also performs the data collection function described later. FIGS. 667 and 768 show the outline of the functions of each block.

[5189] The HLM03A makes the check shown in FIG. 669 (the check name on the table corresponds to the name of the block diagram showing the functions of the HLM03A). The check result is displayed on the MSCN register shown in FIG. 666 and reported to the HLP07A (also provided in the LP-COM unit).

[5190] In addition to the check result shown in FIG. 669, the HLM03A displays on the MSCN register the following results.

[5191] initialization

[5192] LCA configuration

[5193] cross-connection cable missing

[5194] mate system power source fault

[5195] mate system fuse alarm

[5196] timeout of watch dog timer of a mate system HLP07A

[5197] The items preceded by the check name=PCd shown in FIG. 669 are conditional check item, and are not checked unless the conditions meet. According to the conditions, an object cell should be valid, and each check item shown in FIG. 670 should meet an individual condition.

6.2 L2 Protocol Performance Monitor

[5198] The GWMESH carries out the protocol performance monitor of the following L2 parameters.

[5199] (1) MRI timeout

[5200] (2) invalid payload length error

[5201] (3) payload length error

[5202] (4) MID currently active

[5203] (5) EOM having an unapproved MID

[5204] (6) unexpected sequence number error

[5205] When the HLM03A receives an error notification (described later in detail) from the ICLP unit, it performs the L2 protocol performance monitor by adopting the sum-of-errors algorithm in each input link for each of the above listed parameters (1)-(6).

[5206] Since the method of setting a threshold for the sum-of-errors algorithm and the method of realizing the counter and register defined in the TR-1061 and 1063 are basically the same as those in the descriptions of the SBMESH, the descriptions are omitted here.

[5207] When the HLM03A of the GWMESH receives an error notification (described later in detail) from the OGLP unit, an error count is defined for each parameter of the above listed (1), (4), and (5). Since the method of recognizing the counter and register used in counting errors are described for the SBMESH, it is not described here.

[5208] The above described error count is performed for each message handler MH.

6.3 L3 Protocol Performance Monitor

[5209] The GWMESH performs a protocol performance monitor on each of the following L3 parameters.

[5210] (1) invalid BA size field value

[5211] (2) invalid DA type

[5212] (3) invalid SA type

[5213] (4) invalid protocol ID

[5214] (5) invalid service type

[5215] (6) invalid protocol discriminator

[5216] (7) hop count=0

[5217] (8) invalid ingress interface type

[5218] (9) BE tag mismatch

[5219] (10) BA size field not matching length field

[5220] (11) unavailable ISSI/ICI

[5221] When the HLM03A of the GWMESH receives an error notification (described later in detail) from the ICLP unit, it performs the L3 protocol performance monitor by adopting the sum-of-errors algorithm in each input link for each of the above listed parameters (1)-(10).

[5222] Since the method of setting a threshold for the sum-of-errors algorithm and the method of realizing the counter and register used in the sum-of-errors algorithm are basically the same as those in the descriptions of the SBMESH, the descriptions are omitted here.

[5223] The TR-1061 and 1063 requests the log at the occurrence of an error relating to each of the above listed parameters (2)-(8). The contents of the logs are listed below.

[5224] (a) error detection date (in the form of year, month, day, time, minute, and second)

[5225] (b) link ID

[5226] (c) source address (including an address type)

[5227] (d) destination address (including an address type)

[5228] (e) special originating state

[5229] In the system of the present embodiment, the above listed (b) through (e) are set in the log register. The firmware reads the contents of the log from the register and report them to the software. The contents of the (a) above are not passed from the hardware to the firmware. When the firmware fetches the contents of the log other than the contents of (a) above, the time managed by the firmware is assigned to them. However, the contents are not reported to the software in the form of year, month, and day. This form is managed by the software.

[5230] The GWMESH reports the log of each error to the software when it is detected, and the log data retrieving function, etc. is realized by the software.

[5231] The TR-1061 and 1063 define the error count for each of the above listed parameters (2), (3), (9), and (10). The counting operation of this embodiment is the same as the sum-of-errors algorithm, and the same method of realizing the counter and register is used for the counting operation.

6.4 Protocol Performance Monitor in Incoming Unit

[5232] 6.4.1 Processing Method

[5233] FIG. 671 shows the outline of the check items, operations at the detection of NG, and checking procedure in the incoming unit.

[5234] In FIG. 671, the “GROUP” shows the grouping of parameters. The group G has a unique GWMESH specification not defined by the TR-1061 and 1063 and indicates an error in the GWMESH internal process.

[5235] This process is performed by the HOM03A as described above. Error reports of various checks in the incoming unit are received from the ICLP unit. In addition, the HLM03A receives data, cell frames, and enable signals from the OCLP unit. FIG. 672 is a time chart of each signal. FIG. 673 lists the explanation of each signal.

[5236] As shown in FIG. 672, data are input from the ICLP unit in a 16-bit parallel cell format. Since one cell equals 54 octets in a switch (including the GWMESH), 1 cell of input data has the length of 27τ through the 9M clock.

[5237] One cell consists of 3τ portion corresponding to an ATM header (it is in the internal format of the GWMESH and does not match a common ATM header format. As shown in FIG. 672, this portion contains the portion (source link ID) indicating the source link ID of the cell) and other 27τ portion. The contents of the cell shown in FIG. 672 indicate an example in which the cell is an inter-BOM cell.

[5238] Described below is the method of identifying the cell segment type in the ST identification block shown in FIG. 666. A segment type is identified by the combination of the SST and IST shown in FIG. 672. FIG. 674 shows the relationship between the combination and the segment type. The inter BOM refers to a BOM half-encapsulated in the SMLP unit and indicates an increase.

[5239] The method of determining errors in the error analysis block shown in FIG. 666 is basically the same as the contents described for the SBMESH. Therefore, the explanation is omitted here. However, the SBMESH identifies the SNI when an error is identified, while the GWMESH identifies the links. FIG. 675 is a time chart of an error analysis block process.

[5240] 6.4.2 Detailed Process

[5241] 1. L2/3 sum of err. count

[5242] 2. L2/3 individual error count

[5243] Since the above described processes 1 and 2 are basically the same as the contents of the SBMESH, and are not explained here. For the SBMESH, the count-up operation, threshold comparison, and flag settings are performed in SNI units, while they are processed in source link units for the GWMESH.

6.5 Protocol Performance Monitor in Outgoing Unit

[5244] 6.5.1 Process Method

[5245] FIG. 676 shows the outline of the check items, operations at the detection of NG, and checking procedure in the outgoing unit.

[5246] In FIG. 676, the “GROUP” shows the grouping of parameters as described above. The group E has a unique specification in the GWMESH internal process.

[5247] The protocol performance monitor counts errors for each parameter. The counting operation is performed for each source MH. However, the ISSI/ICI unavailable refers to a log object error.

[5248] This process is performed by the HOM03A as described above. Error reports of various checks in the outgoing unit are received from the OGLP unit. In addition, the HLM03A receives data, cell frames, and enable signals from the OCLP unit. FIG. 677 is a time chart of each signal. FIG. 673 lists the explanation of each signal.

[5249] The signal received by the outgoing unit is basically the same as each signal received by the ICLP unit to perform the protocol performance monitor in the incoming unit.

[5250] The format of the 3τ portion corresponding to an ATM header is the internal format of the GWMESH and does not match a common ATM header format. As shown in FIG. 677, this portion contains the portion (source MH ID) indicating the source MH of the cell and another portion (destination ID) indicating the destination link (destination link ID). FIG. 677 shows an example of the inter-BOM.

[5251] The error notification method of the MRI timeout is the same as that of the incoming unit. That is, a pseudo-EOM cell is generated in the OGLP unit, and an error notification reporting the MRI timeout is transmitted with the cell. The destination link ID in the pseudo EOM cell is the same as that of the corresponding BOM. The cell segment type identifying method if the same as that for the incoming unit as shown in FIG. 674. For each block shown in FIG. 666, this unit has the same function and performs the same operations as the incoming unit.

[5252] The “TRIAL” entered as data 15 in FIG. 677 in line E is a field indicating whether or not the cell is a LINK-GWMESH PVC test cell, and the 2τ-th data 11 “TRIAL” is a field indicating whether or not the cell is a MESH-MH PVC test cell. If the cell is a LINK-GWMESH PVC test cell or a MESH-MH PVC test cell, none of the processes relating to the outgoing protocol performance monitor are performed.

[5253] 6.5.2 Detailed Processes

[5254] The process of counting individual errors is the same as the process described for the SBMESH, and the descriptions are omitted here except the time chart shown by FIG. 678.

7. NETWORK DATA COLLECTION

7.1 General Descriptions

[5255] The GWMESH collects data for the L2-PDU and L3-PDU. The data collection is almost in accordance with the TR-1061 and 1063. The data collecting function is realized by the HLM03A. FIGS. 666 through 668 are block diagram showing the HLM03A and the functions of each block.

7.2 Network Data Collection Parameter

[5256] The GWMESH keeps the network data collection (scheduled measurement made for each link) for each of the following parameters.

[5257] (1) Total originating 12 PDUs

[5258] (2) Total terminating 12 PDUs

[5259] (3) Total originating individually addressed L3 PDUs

[5260] (4) Total terminating individually addressed L3 PDUs

[5261] (5) Total originating group addressed L3 PDUs

[5262] (6) Total terminating group addressed L3 PDUs

[5263] The above listed (1) through (6) indicate the count of L2 and L3 PDUs.

[5264] The GWMESH counts the number of PDUs as listed above as:

[5265] total originating (terminating) individually addressed L3 PDUs; and

[5266] total originating (terminating) group addressed L3 PDUs.

[5267] If the total number of L3 PDUs is calculated, the software adds up these values.

[5268] According to the TR-1061 and 1063, one interval equals 15 minutes, and various data is stored at least for the past 2 intervals. Based on this definition, the GWMESH of the present embodiment provides two 15-minute counters as in the protocol performance monitor to use them when switching the operation phases. Within 15 minutes after issuing a phase switch instruction, the software retrieves a count value from the 15-minute counter corresponding to the 15-previous-minute register, and then stores it. That is, the software stores various data for at least the part two intervals.

7.3 Network Data Collection in Incoming Unit

[5269] 7.3.1 Process System

[5270] In the above listed network data collection object parameters (1) through (6), three items (1), (3), and (5) are processed in the incoming unit.

[5271] The numbers of L2 and L3 PDUs of (1), (3), and (5) are counted regardless of the existence of errors in the L2-PDU or L3-PDU.

[5272] Since the incoming unit receives data in the cell format, the number of L2-PDUs can be easily counted for each link. The ST of the L2-PDU is analyzed and the number of the L3-PDUs is increased if the analysis indicates an inter-BOM. Then, the DA is analyzed to determine whether it is an individually addressed L3-PDU or a group addressed L3 PDU.

[5273] As in the protocol performance monitor, none of the processes relating to the ingress network data collections are performed if the cell is a MESH-MH PVC test cell and a cell copied in the GA copying process in the network data collection. Each block for timing generation, link identification, SA/DA identification, RAM and counter and SA/DA accumulation RAM are also used in the protocol performance monitor process. Each counter stores a count value in the dual port RAM (for each link and L2 and L3 PDU) as shown in FIG. 666 as in the protocol performance monitor process to read a necessary count value, increment the count value, and store the result in the RAM.

[5274] FIG. 679 is a time chart relating to the network data collection in the incoming unit.

[5275] 7.3.2 Detailed Process

[5276] When a valid cell is received, the following processes are performed.

[5277] (1) An L2-PDU count value is read from the count value storage RAM and the value is incremented (+1).

[5278] (2) The incremented L2-PDU count value is stored in the RAM.

[5279] When a valid inter-BOM is received, the following processes are performed.

[5280] (1) An L3-PDU count value is read from the count value storage RAM and the value is incremented (+1). At this time, the DA is analyzed to be determined whether it indicates an individual address L3-PDU or a group address L3-PDU, and the count value is incremented.

[5281] (2) The incremented L3-PDU count value is stored in the RAM.

[5282] The count value is represented by 32 bits and the read/write in the RAM is performed twice in 16-bit units. The count value is incremented for each source link. A count is not incremented if the count value in (1) above indicates the maximum value. As described above, the L2-PDU and L3-PDU values are counted regardless of the existence of errors.

[5283] A parity is generated when a count value is stored, and is checked when the count value is read. FIG. 680 is a read/write timechart of count values relating to the network data collection in the incoming unit.

7.4 Network Data Collection in the Outgoing Unit

[5284] 7.4.1 In the Above Described Network Data Collection object parameters (1) through (6) the parameters to be processed in the outgoing unit are three parameters (2), (4), and (6).

[5285] The count of the L2-PDU and L3-PDU for the (2), (4), and (6) is performed only on normal L2-PDU or L3-PDU having no errors.

[5286] Since data is input to the outgoing unit in a cell format, the number of L2-PDU can be easily counted for each link and the ST of the L2-PDU is analyzed. If it indicates an inter-BOM, the number of L3-PDUs is incremented. Simultaneously, the DA is analyzed and it is determined whether the DA indicates an individual address L3-PDU or a group address L3-PDU.

[5287] If the cell is a LINK-SBMESH PVC test cell or a MESH-MH PVC test cell, none of the processes for the outgoing network data collection are performed. The outgoing network data collection (NDC) unit of the HLM03A also counts the L2-PDU and L3-PDU for billing data. However, the L3-PDU for billing data is counted only for the total terminating L3-PDUs.

[5288] 7.4.2 Detailed Processes

[5289] When a normal cell having no errors is received, the following processes are performed.

[5290] (1) An L2-PDU count value is read from the NDC count value storage RAM and is incremented (+1).

[5291] (2) The incremented L2-PDU count value is stored in the RAM.

[5292] (3) An L2-PDU count value is read from the billing data count value storage RAM and is incremented (+1).

[5293] (4) The incremented L2-PDU count value is stored in the RAM.

[5294] When a normal inter-BOM is received, the following processes are performed.

[5295] (1) An L3-PDU count value is read from the NDC count value storage RAM and is incremented (+1). At this time, the DA is analyzed to be determined whether it indicates an individual address L3-PDU or a group address L3-PDU, and the count value is incremented.

[5296] (2) The incremented L3-PDU count value is stored in the RAM.

[5297] (3) An L3-PDU count value is read from the billing data count value storage RAM and is incremented (+1).

[5298] (4) The incremented L3-PDU count value is stored in the RAM.

[5299] The count value is represented by 32 bits and the read/write in the RAM is performed twice in 16-bit units. The count value is incremented for each destination link. A count is not incremented if the count value in (1) above indicates the maximum value. A parity is generated when a count value is stored, and is checked when the count value is read.

[5300] FIG. 681 is a read/write timechart of count values relating to the network data collection in the outgoing unit.

8. BILLING

[5301] In a billing process, usage information required to support the billing function for the SMDS covering a plurality of carriers between, for example, the XA and SMDS and between the BBC and ILEC, is generated and the usage measurement process is performed. FIG. 682 shows the classification of billing functions and their procedures.

8.1 Data Generation

[5302] (1) Generation for Individual Address Data Transfer

[5303] Billing point (refer to FIG. 683)

[5304] 1. Switching system SS for transferring the ICIP L3-PDU directly to another LEX network or an IC network in the sending LEC network.

[5305] 2. Switching system SS for transferring the SIP L3-PDU directly to the destination SNI in the destination LEC network. However, each SBMH contains the billing function for the intra-station SMDS and the terminal usage information is generated in the SBMH so that the functions can be shared.

[5306] Billing object

[5307] The billing process is performed only on the data determined as successfully transferred L3-PDU according to the protocol check, feature processing results, etc.

[5308] Billing information

[5309] The usage information containing the information shown in FIG. 684 is generated in packet units.

[5310] (2) Generation for Group Address Data Transfer

[5311] Billing point

[5312] 1. SS for transferring each ICIP L3 PDU of a GA and its copy directly to another LEC network or a selected IC network.

[5313] 2. SS for transferring a copied SIP L3 PDU to the destination SNI according to the GA.

[5314] Billing object

[5315] The billing process is performed only on the data determined as successfully transferred L3-PDU according to the protocol check, feature processing results, etc.

[5316] Billing information

[5317] The usage information containing the information shown in FIG. 684 is generated in packet units.

[5318] (3) Contents of Usage Information

[5319] destination address

[5320] destination address consisting of an address type and address subfield

[5321] address type=‘1100’: individual address=‘1110’: group address

[5322] source address

[5323] A source address consists of an address type and an address subfield.

[5324] address type=‘1100’

[5325] SNI address

[5326] If the LEC is a GA agent, an individual address of a GA member is set.

[5327] Unless the LEC is a GA agent, an individual address is set.

[5328] State code

[5329] A transfer state of the ICIP or SIP L3-PDU. “1” indicates normal transfer.

[5330] Identification of outgoing network

[5331] Destination carrier of an ICIP L3-PDU (LEC and IC)

[5332] Identification of the settings of outgoing ICI transfer paths

[5333] Identification of ICI transfer path which sent an ICIP L3-PDU

[5334] Identification of incoming network

[5335] Source carrier of an ICIP L3-PDU (LEC and IC)

[5336] Identification of the settings of incoming ICI transfer paths

[5337] Identification of ICI transfer-path which received an ICIP L3-PDU

[5338] Identification of carrier

[5339] Set is an ICI assigned by the service specific unit of the L3-PDU header described in 5.5.1 of the TR-1060.

[5340] Segment count

[5341] Number of transferred L2 PDUs

[5342] Packet count

[5343] Number of transferred L3 PDUs

[5344] Ingress interface type

[5345] Determination of the code in the incoming/outgoing network identification. If the destination is an IC, the type is “CIC”. If the destination is an ILEC, the type is “NECA”.

[5346] FIG. 684 shows the usage information generated in the LEC network for an inter-carrier SMDS.

8.2 Data Aggregation

[5347] The usage information of an inter-network SMDS is added at time intervals predetermined in the LEC network for the successfully transmitted L3-PDU between a specified SA and DA.

[5348] Time interval=1 minute (same as SBMH)

[5349] Combination of usage information=64K (maximum)

[5350] Cell and packet count=24 bits (maximum)

[5351] Considering the combination of the usage information required to collect billing data, the variations of the combination of SA and DA, each being represented by 64 bits, amounts to 2⁶⁴×2⁶⁴. This requires a lot of memory. Therefore, assuming that up to 64K combination of usage information can be obtained, the memory can be distributed as follows.

[5352] RDA (SIP)+RDA (ICIP)+RSA+RCA=64K×(SA 64 bits+DA (SIP) 64 bits+DA (ICIP) 64 bits+carrier information 37 bits)

[5353] where the carrier information can be 16-bit incoming NW ID, 16-bit incoming ICI TPS, 16-bit outgoing ICI TPS, and 8-bit ingress inf. type.

[5354] Since eight exclusive links of the ISSI/ICI is supported by the GWMESH, the outgoing NW ID and the outgoing ICI TPS can be collectively represented by 3 bits. The lower two bits are used for the ingress inf. type. Therefore, the entire carrier information is represented by 37 bits. FIG. 685 shows the SA, DA (SIP), DA (ICIP), and carrier information compressed memory image.

[5355] A total number of the L2-PDUs and L3-PDUs are written for each address to the billing data accumulation memory. The billing data accumulation memory is accessed by the firmware to collect the billing information. Practically, this memory has a duplex configuration and the firmware issues a phase switch instruction at predetermined intervals (every minute). If the memory becomes full before a predetermined time is reached, then the phases are switched immediately. The hardware gains access in one phase and the firmware retrieves each data in the other phase. The numbers of the L2-PDU and L3-PDU can be written to the billing data accumulation memory for each output link. FIG. 686 shows the memory image.

[5356] The above described billing function is realized in the network data collecting unit, that is, the HLM03A.

9. LP-COM (INF)

9.1 General Descriptions

[5357] The LP-COM has the following functions.

[5358] (1) Interfacing with the INF to control the ICLP and OGLP

[5359] (2) Billing process

[5360] (3) Performance monitor and data collection (traffic monitor)

[5361] Physically, it comprises the following three PWCBs.

[5362] (a) HLP07A

[5363] (b) HLM02A

[5364] (c) HLM03A

[5365] The above listed functions (1) through (3) are performed in the PWCB of (a) through (c) respectively. The HLM02A uses the HLM00A in the SBMESH, but does not perform an actual billing process.

[5366] Refer to chapter 8 for the billing process, chapter 6 for the performance monitor, and chapter 7 for the data collection.

[5367] Described in this chapter are the interfacing function with the INF and controlling function of the SMLP and RMLP, that is, the HLP07A.

9.2 Outline of Functions

[5368] FIG. 687 is a block diagram showing the HLP07A. FIGS. 688 and 689 show the functions of each block of the HLP07A.

[5369] The important functions of the HLP07A are listed below.

[5370] interfacing with the INF

[5371] setting and managing the LP and each table

[5372] monitoring errors in the LP and LP-COM

[5373] controlling states

9.3 INF Interface Control Unit

[5374] 9.3.1 INF Interface Control

[5375] Listed below is the control procedure of the interface using the INF between the GWMESH (MNG-Firm) and BCPR.

[5376] a. INF command activation

[5377] (1) A DMA is set on the CPU (microprocessor).

[5378] (2) When a command is activated in an INF order, the BCPR specifies with the MM address shifted 2 bits to the right (0,4,8 are shifted to 0.1.2). Therefore, when the INF is received, the SBMESH performs the following processes.

[5379] 1. When a command activation is recognized the MM address and the number of commands are received from port A of the SBIF LSI.

[5380] 2. The MM address is set in the port B of the SBIF LSI with the higher, intermediate, and lower orders shifted.

[5381] 3. The transfer length (number of commands×4 words) is set in the port F of the SBIF LSI.

[5382] 4. The DMA read start is set in the port C of the SBIF LSI.

[5383] b. INF status notification

[5384] The MM address specified in the status notification is shifted 2 bits to the right (0, 4, and 8 are shifted to 0, 1, and 2), and is specified by the receiving buffer notification. The message length is from MSB for the left to LSB for the right in the BCPR memory. The GWMESH performs the following operations.

[5385] (1) The MM address is set in the port B of the SBIF LSI with the higher, intermediate, and lower orders shifted.

[5386] (2) The transfer length (number of commands×4 words) is set in the port F of the SBIF LSI.

[5387] (3) The DMA read start is set in the port C of the SBIF LSI.

[5388] The MM address and message length specified in the command and status are as follows.

[5389] (1) The MM address specified in the command is shifted 2 bits to the right.

[5390] (2) The message length is from MSB for the left to LSB for the right in the BCPR memory.

[5391] (3) All data except the MM address is defined in the interface specification.

[5392] The status notification is set similarly. The MM address is the same as that specified in the reception buffer notification.

[5393] The notification of the status queue address and reception buffer address is as follows.

[5394] (1) The BCPR notifies the GWMESH of the MM addresses of a status queue and reception buffer.

[5395] (2) The MM address is shifted 2 bits to the right.

[5396] 9.3.2 INF Interface Interruption Control

[5397] Described below is the interruption control in controlling the INF interface in the GWMESH.

[5398] a. Command activation

[5399] The command activation is processed through an interruption, that is, an external interruption INTO. The INTO interruption is reset by 3-word read from port A.

[5400] b. Transmitting a status

[5401] When a log object error occurs, a log status arising from the MSR-firm is transmitted.

[5402] c. Controlling DMA

[5403] The DMA is controlled by a DMA controller. The available DMA channel is 0. The DMA termination is used as an interruption and look-in. The interruption is controlled by the INT bit of the DMA control register in the CPU.

[5404] Since the DMA transfer speed of the INF is 4 Mbytes/sec, the 4-byte DMA read (tail pointer look-in, etc.) terminates in 1μ second with an 8-MHz CPU clock. Therefore, the DMA termination is not attained by an interruption, but by a look-in.

9.4 Controlling ICLP/OGLP

[5405] The control of the ICLP/OGLP, that is, the state control information from the HLP07A to the ICLP/OGLP, is listed as follows.

[5406] ACT/SBY (active/standby) of the home system

[5407] Shelf No. (0-3) of the home shelf (shelf number)

[5408] Reset at initialization

[5409] Fault reset to various checkers

[5410] Settings to various MSD tables

[5411] Resettings to various MSD tables

[5412] Hardware INHBIT state signal (masking a hardware operation according to an inhibition signal)

[5413] The HLP07A additionally collects the MSCAN information from each package PKG in the ICLP/OGLP to monitor the state.

10. SOFTWARE INTERFACE

10.1 Initialization

[5414] The software performs the following two types of initialization on the GWMESH.

[5415] 1. Initialization of MH-COM

[5416] 2. Initialization of LP

[5417] First, the software initializes the MH-COM through the LAP, and then initializes the LP through the INF.

[5418] 10.1.1 Initialization of MH-COM

[5419] The device control of the E-MSD/E-MSCN relating to the MH-COM is performed through the intra-station communications using the simple LAP (EZLAP). The fixed value shown in FIG. 690 is used as a VPI/VCI of the intra-station communication.

[5420] One EZLAP link is established each in systems 0 and 1 between the BSGC and MHCOM. The intra-station communications cells for systems 0 and 1 are input to both links.

[5421] An MH-COM accepts at the IDMX a cell having switching tag information addressed to the MH-COM. Since intra-station communications cells for systems 0 and 1 have different VCI values, a cell to be processed in the home system is identified by a VCI value and discards the cells for a mate system.

[5422] The VCI value of the intra-station communications cell for system 0 is the same as that for system 1 at the BSGC, and the cells are distinguished by the COM-bit “1” for the cell fetched by a home system and the COM-bit “0” for the cell fetched by a mate system (refer to the explanation in FIG. 410). The system fetches a cell addressed to it and discards a cell addressed to a mate system.

[5423] 10.1.2 Initialization of LP

[5424] The LP is initialized through the INF.

10.2 INS Process

[5425] In the GWMESH, the MH-COM and LP can have system configurations independently. Therefore, the MH-COM and LP independently perform the INS process (in-service process).

[5426] 10.2.1 INS Process of MH-COM

[5427] The MH-COM is controlled using the EZLAP. The main process in the INS process of the MH-COM is to copy a VCC.

[5428] 10.2.2 INS Process of LP

[5429] Only the initialization is performed in the INS process of the LP.

10.3 Switching Systems

[5430] Systems are switched in the GWMESH as follows

[5431] 1. Switching systems by switches in the MH-COM

[5432] 2. Switching systems independently of the MH-COM

[5433] 10.3.1 Switching Systems in MH-COM

[5434] The MH-COM is interlocked with switches and receives a system switch signal through the ASSWSH. Therefore, the system switching procedure of the MH-COM is the same as that of the ASSWSH.

[5435] 10.3.2 Switching Systems in LP

[5436] The ACT is changed in the INFA.

10.4 Fault Monitor

[5437] 10.4.1 Fault Monitor in MH-COM

[5438] The faults in the MH-COM is reported to the BCPR in the MSCN format using the EZLAP. The MSCN contains home system monitor information and mate system monitor information for different processes.

[5439] FIG. 691 shows the operation to be performed when the MH-COM is faulty.

[5440] 10.4.2 Fault Monitor Relating to INF Communications

[5441] The fault monitor on the INF communications are performed in accordance with the BSGC process, and is not described in detail here.

10.5 Test and Diagnostics

[5442] The tests of the GWMESH are the same as those of the SBMESH as listed below.

[5443] 1. Test using a TCG

[5444] 2. PVC test between ICI/ISSI and GWMESH

[5445] 3. PVC test between SBMESH or GWMESH and GWMESH

[5446] 4. Inter-station loopback test

[5447] Fundamentally, test 1 is conducted periodically and tests 2, 3, and 4 are conducted at the request and complaint (claim), etc. of the subscriber.

[5448] 10.5.1 Test Using TCG

[5449] Like the SIFSH, BSGCSH, SBMESH, etc. connected to the highway of another ASSW, the GWMESH has the function of automatically MUXing a test cell input from the ASSW again in the 155M highway immediately after the DMUX, and looping it back to the ASSW. The test cell generated and output at the TCG has the information shown in FIG. 692 in the header field. The rightmost bit in FIG. 692 indicates an 0 bit. The 0 bit of 1 indicates that the cell is a test cell.

[5450] Examples of loopback tests of a TCG cell in the GWMESH are explained by referring to the function image charts shown in FIGS. 693 and 694.

[5451] The following processes (1) and (2) are performed in the IDMX (ODMX) of the GWMESH.

[5452] (1) Data matching according to the TAGC information is fetched

[5453] (2) data matching according to the TAGC information and having an 0-bit=1 is fetched.

[5454] The cell fetched under the condition (1) above is transmitted to the ICLP (OGLP). A cell is discarded if its 0 bit indicates 1, and other cells are processed in a normal routing process. The cell fetched under the condition (2) is looped back in the GWMESH according to the value of the above described 0 bit. The cell is then MUXed and looped back by the ASSW after passing through the VCC of the GWMESH. Unless the VCC for the test cell is set at the MUX, the loopback process is not performed. FIG. 693 shows the function image of only one system. The same image is shown for the duplex GWMESH. In this test, the normality of the switching at the intersection of the ASSW, and the normality of the DMUX and MUX of the GWMESH and SIFSH are checked.

[5455] The operation of the test shown in FIG. 693 is described. First, the test cell generated and output by the CGSH has a VCI₁, and the 0 bit indicates 1. The above described VCI₁specifies the path between the TCGSH and the IDMX of the GWMESH. Since the test cell is fetched under the conditions (1) and (2) above, and the 0 bit of the test cell fetched under the condition (2) indicates 1, it is looped back to the OMUX.

[5456] The VCC is provided at the input terminal of the OMUX and the routing information of the test cell is converted from VCI₁into VCI₂and is output to the ASSW. The VCI₂specifies the path between the OMUX of the GWMESH and the DMX of the SIFSH. As in the GWMESH, the test cell is looped back to the MUX in the SIFSH according to the 0 bit of 1. The test cell is converted from VCI₂into VCI₃in the VCC provided at the input terminal of the MUX of the SIFSH and output again to the ASSW. The VCI₃specifies the path between the MUX of the SIFSH and the IDMX of the GWMESH.

[5457] The GWMESH loops back the test cell to the OMUX as described above, and then converts it from the VCI₃into the VCI₄and outputs it to the ASSW. The VCI₄specifies the path between the OMUX of the GWMESH and the TCGSH.

[5458] Thus, the TCGSH checks the normality of the IDMX and OMUX of the GWMESH (as well as the DMX and MUX of the SIFSH) by receiving the test cell output by the TCGSH itself.

[5459] The operation of the test shown in FIG. 694 is fundamentally the same as that shown in FIG. 693. In this test, the LOOPS replaces the SIFSH and checks the normality of the IMUX and ODMX of the GWMESH. The above described LOOPS corresponds to the LLP shown in FIG. 9.

[5460] 10.5.2 PVC Test Between ICI/ISSI and GWMESH

[5461] Since the trunk of the ICI/ISSI, etc. may be used in other MHs, a test is not conducted in the OUS (out of service) state of the line, but is conducted in the INS (in-service) state. FIG. 695 shows the functional image of the GWMESH in the ICI/ISSI-GWMESH PVC test.

[5462] In this test, the firmware transmits to the OGLP a test cell having the VCI=xxFF(h) (x indicates an optional value) at the instruction from the software. In the OGLP, the test cell is determined to be a test cell if the VCI value of an input cell is xxxx xxxx 1xxx xxxx (b). The routing process is performed on the test cell as if it were a normal user cell, and the test cell is transmitted to the requesting (claiming) trunk. The following operations 1 and 2 are not performed on the test cell.

[5463] 1. predetermined operation on the BA size or length (a predetermined value is subtracted depending on the segment type)

[5464] 2. Protocol check of L2

[5465] The test cell which is output by the GWMESH, passes through the ASSW (downwards), and arrives at the SIFSH is looped back at a predetermined trunk of the SIFSH, and output to the ICLP of the GWMESH for the trunk. The predetermined trunk of the SIFSH has the function of looping back the cell having the VPI/VCI which refers to a PVC test cell.

[5466] In the cells received at the ICLP, the cells whose service types are 48 or 60 are not copied for their BE tags. Furthermore, the cells whose DAs indicate their home SS station numbers and whose service types are 48 or 60 are not processed in a predetermined operation relating to the BA size and length. Then, the VCI value of the above described cell is converted into xxFF(h). The reception of the test cell is reported to the firmware at the MSCN.

[5467] Only the cell having the VCI=xxFF(h) is filtered and fetched by receiving unit of the firmware. The firmware reports the storage position of the received test cell data and has the test result checked by the software. The VCI value of the test cell passed to the highway is not stored in the VCC unlike a normal cell. Therefore, it is discarded at the VCC.

[5468] In the PVC test, the VPI/VCI is obtained from the actual service cell. Therefore, during the test, a cell having a VPI/VCI except the test VPI/VCI can be used for service, but cannot be used for service if the cell has the test VPI/VCI. In the GWMESH, the VPI/VCI values for service are 03F(h) for the VPI, and 0300(h) through 0307(h)(ISSI) and 0310(h) through 0317(h)(ICI) for the VCI.

[5469] 10.5.3 SBMESH/GEMESH—GWMESH PVC Test

[5470] This function is the same as the PVC test function between the MESH and MH of the SBMESH. The combination of the SBMESH and GWIAESH is listed below.

[5471] (a) SMLP-RMLP

[5472] (b) SMLP-OGLP

[5473] (c) ICLP-RMLP

[5474] (d) ICLP-OGLP

[5475] FIG. 697 shows the image of the PVC test between the SBMESH/GEMESH and GWMESH.

[5476] In this test, the firmware transmits to the ICLP a test cell having the VCI=xxFF(h) (x indicates an optional value) at the instruction from the software. In the ICLP, the test cell is determined to be a test cell if the VCI value of an input cell is xxxx xxxx 1xxx xxxx. The routing process is performed using the DA on the test cell as if it were a normal user cell, and the test cell is transmitted to the requesting (claiming) SBMH and GWMH. The BE tag copy and protocol check of layers 2 and 3 are not made for the test cell.

[5477] The test cell looped back at the LLP in the SIFSH shown in FIG. 696 is transferred to the SBMH and GWMH in which the PVC is set, and arrives at the corresponding RMLP or OGLP according to the DA (destination address) described in the test cell. In the cells entered in the RMLP or OGLP, those having the test DA value preliminarily specified by the firmware is converted into the VCI=xxFF(h).

[5478] Only the cell having the VCI=xxFF(h) is filtered and fetched by receiving unit of the firmware. The firmware reports the storage position of the received test cell data and has the test result checked by the software. The VCI value of the test cell passed to the highway is not stored in the VCC unlike a normal cell. Therefore, it is discarded at the VCC.

[5479] The following two types of the DA values are used in this test.

[5480] 1. An allocated DA value

[5481] 2. A specific DA value specifically determined for the test

[5482] Since the VPI/VCI used in the test using 1 above are the same as the actual service cell, the test cell and normal cell cannot be distinguished by their VPI/VCI. Therefore, the cell having the test VPI/VCI cannot be used for service.

[5483] In the test using 2 above, an exclusive internal VCI value is defined for the above described specific DA. Therefore, the test cell can be clearly distinguished from a normal service cell, and the normal service cell does not have an undesirable influence in the test.

[5484] In the GWMESH, the VPI/VCI values for service are 03F(h) for the VPI, and 0340(h) through 035F(h) for the VCI.

[5485] 10.5.4 Inter-station Test

[5486] FIG. 697 shows the function image of the GWMESH in the inter-station test.

[5487] In this test, the firmware transmits to the OGLP a test cell having the VCI=xxFF(h) (x indicates an optional value) at the instruction from the software. In the OGLP, the test cell is determined to be a test cell if the VCI value of an input cell is xxxx xxxx 1xxx xxxx. The routing process is performed on the test cell as if it were a normal user cell, and the test cell is transmitted to the inter-station interface (ISSI and ICI). No operations are performed relating to the BA size or length, or no protocol checks are made.

[5488] The test cell input to the destination station via an inter-station transmission line is transferred to the ICLP of the GWME in which the PVC is set. In the cells received at the ICLP, the cells whose service types are 48 or 60 are not copied for their BE tags. Furthermore, the cells whose DAs indicate their home SS station numbers and whose service types are 48 or 60 are not processed in a predetermined operation relating to the BA size and length. Then, the VCI value of the above described cell is converted into xxFF(h). The reception of the test cell is reported to the firmware at the MSCN.

[5489] The firmware recognizes the reception of a test cell by the MSCN. Only the cell having the VCI=xxFF(h) is filtered and fetched by receiving unit of the firmware. The firmware reports the storage position of the received test cell data. The software exchanges the DA and SA and returns the test cell to the source. The result is reported to the software through the firmware. Thus, a loopback test covering a plurality of stations is conducted. Since the test is a PVC test, the VPI/VCI of the actual service cell is used. The test cell and a normal cell can be distinguished by a service type, and the test can be conducted during the service operation.

[5490] In the GWMESH, the VPI/VCI values for service are 03F(h) for the VPI, and 0300(h) through 0307(h)(ISSI) and 0310(h) through 0317(h)(ICI) for the VCI. Since the ES, hop count ID, and carrier ID similar to those of other user cells are rotated in the hardware in the OGLP, the values set by the firmware are inversely rotated so that correct values can be obtained by the rotation in the hardware.

[5491] 10.5.5 Test Functions of Each Unit

[5492] Summarized below are the functions of each unit required for the above described tests.

[5493] 1. In the ICLP;

[5494] Service type of 48 or 60

[5495] (1) A BE tag is not copied.

[5496] DA for SS of home system and service type of 48 or 60

[5497] (1) Converting VCI into xxFF(h)

[5498] (2) Reporting to MSCN

[5499] (3) No process for BA size or length

[5500] VCI value of xxxx xxxx 1xxx xxxx

[5501] (1) Mask in protocol check (layers 2 and 3)

[5502] (2) Routing with DA (DA of user cell)

[5503] (3) BE tag is not copied.

[5504] 2. In the OGLP;

[5505] Test DA reported by firmware

[5506] (1) Converting VCI into xxFF(h)

[5507] VCI value of xxxx xxxx 1xxx xxxx

[5508] (1) Mask in protocol check (layer 2)

[5509] (2) No process for BA size or length

[5510] 3. In the firmware;

[5511] Since the ES, hop count ID, and carrier ID are rotated in the hardware, the values are inversely rotated in consideration of the rotation in the hardware.

[5512] 10.5.6 Self-diagnostics

[5513] The self-diagnostics can be made by the MH-COM and LP.

[5514] The self-diagnostics of the MH-COM checks the normality of the fault monitor system. That is, it is to confirm that no fault flag in the MSCN in a normal state, and to confirm the fault flag in the MSCN for the process performed for a pseudo-fault point of the MSD.

[5515] The self-diagnostics of the LP confirms the normality of the fault monitor system and conducts a data transparency test in the LP using a test cell.

[5516] The normality test of the fault monitor system is to confirm that no fault flag in the MSCN in a normal state, and to confirm the fault flag in the MSCN for the process performed for a pseudo-fault point of the MSD.

[5517] In the data transparency test of the LP, a test cell is output from the test cell multiplexing unit of the ICLP and OGLP, and checked are the cell, NDC data (network data collection data), and billing data after the incoming process and outgoing process are completed.

[5518] [0013]

[5519] <part 7>

[5520] In part 7, the broadband signaling group controller (BSGC) is described in detail.

1. GENERAL DESCRIPTIONS

[5521] The broadband signaling group controller shelf (BSGC) terminates a layer 2 protocol in the communications of the control information with each subscriber terminal unit and each intra-station device under the control of the broadband call processor (BCPR) (refer to FIG. 698) which function as switch processor. A single BSGC terminates LAPD communications ports 256 through 1024.

[5522] The BSGCSH accommodates six-BSGCs per system. That is, a single BSGCSH can accommodate 2048 through 8192 LAPD communications ports.

1.1 Positions of BSGCSH and BSGC in Switch System

[5523] FIG. 698 shows the position (shown as patched portions) of the BSGCSH and BSGC in the switch system according to the present embodiment.

[5524] FIG. 699 shows the terminal point of the intra-station LAPD communications.

[5525] FIG. 700 shows the terminal point of the subscriber LAPD communications.

[5526] The BSGC shares the four important functions listed below.

[5527] (1) Communications with the BCPR through the INF

[5528] (2) Terminating the layer 2 of each communications control under the control of the BCPR

[5529] (3) Initializing and monitoring the port for an intra-station communications link

[5530] (4) Establishing interface with the ATM switch through the CARP LSI function and the VCC function loaded onto the BSGC

[5531] 1.2.1 Functions of INF

[5532] The BCPR and BSGC are switch processors shown in FIG. 698, and the communications between them are interfaced through an interface (INF). The PIF comprises an interface type T (INFT) and interface type A (INFA) as shown in FIG. 698.

[5533] The INFT is an interface connected to the system bus (TOX-BUS)(refer to FIG. 698) and realizes interface with a device in the BCPR. The interface is of an ECL (emitter-coupled logic) balanced transmission type (32 MHz 1-bit data serial). The INFT consists of four interface terminals and connected to up to four lower order devices with four TD cables. A signal is multiplexed for four highways in each TD cable.

[5534] The INFA is located in the INFT to extend the functions of the interface with the communications line device, and controls the interface between the BCPR and the communications line device (BSGC). The interface can be the V.11 balanced transmission system (4 MHz, 8-bit data serial). The 32 Mbps interface in which a signal multiplexed by the INFT for four highways is demultiplexed into 4 Mbps interfaces for individual highways.

[5535] Up to four INFAs can be connected to one INFT, and up to four BSGCs can be connected to one INFA.

[5536] 1.2.2 Functions of LAPD

[5537] The BSGC terminates a layer 2 protocol in the communications of control information with each subscriber terminal and each intra-station device under the control of the BCPR.

[5538] A subscriber terminal refers to a B-ISDN terminal in a user network interface (UNI) or a frame relay (FR) terminal at the SVC. An intra-station control device refers to a SISFH (refer to part 3), remote multiplex shelf (RMXSH)(refer to FIG. 34, etc.), message handler shelf (MESH, that is, SBMESH and GWMESH)(refer to parts 5 and 6), subscriber line interface (SINF), DS3-SMDS interface (DS3)(refer to part 2), frame relay interface (FR), etc.

[5539] 1.2.3 Intra-station Control Communications Link

[5540] The BSGC terminates the layer 2 in the communications of the control data between the BCPR and all intra-station devices. The communications protocol can be the simple LAPD using a UI frame. To prevent a missing signal, the BCPR and each intra-station device performs a layer 3 missing message monitor process.

[5541] A simple LAPD protocol is adopted to reduce the load on the LAPD communications of each intra-station device.

[5542] The intra-station control communications can be established by simplex devices or duplex devices.

[5543] In the simplex device communications, a signal of an active system passes through the ASSWs (ATM switch) of both active and standby systems. The object devices are various intra-station devices such as a SINF, DS3, DS1 frame relay interface (DS1FR).

[5544] In the duplex device communications, a system-specific signal passes through the ASSW (ATM switch) of each of the active and standby systems. The communications are established through both active and standby systems of each duplex device and two ports for the active system of the BSGC. This system is used to improve the reliability through a duplex communications link in preventing the occurrence of a fault in both systems from a fault in the cross-connection unit of the duplex device. The object communications device can be a SIFCOM in the SIFSH-A (refer to part 3), message handler shelf (MESH, that is, SBMESH and GWMESH)(refer to parts 5 and 6), remote multiplex shelf (RMXSH) (refer to FIG. 34), etc.

[5545] 1.2.4 Interface with ATM Switch

[5546] As described in 10.3 in part 2, the BSGC sets an intra-station communications link to the DS3-SMDS interface using a VPI/VCI value assigned by the switch software.

[5547] Tag information required in routing an intra-station communications cell from the SIFSH to the BSGC is added by the virtual channel converter (VCC) in the SIFCOM (refer to FIG. 8).

[5548] Tag information required in routing an intra-station communications cell from the BSGC to the SIFSH is added by the virtual channel converter (VCC) in the common unit (BSGC-COM) of the BSGC.

[5549] However, when the BSGC communicates with the MESH or LLP (refer to FIG. 699), the BSGC performs the VCC conversion in both directions.

[5550] The VCC is loaded into each of the duplex units of the SIFSH, BSGCSH, and MESH.

[5551] 1.2.5 Meta-signaling Communications

[5552] The BSGC provides a port for meta-signaling communications established to a user network interface (UNI) terminal unit (subscriber terminal unit). The VPI/VCI for use in the procedure of the meta-signaling communications between the BSGC and UNI terminal units can be assigned and communicated by the BCPR. The BSGC does not analyze a meta-signaling message.

1.3 Number and Assignment Condition of BSGC Port

[5553] The port type of the BSGC and the number of ports per BCPR are listed below.

[5554] 1.3.1 Maximum Number of Ports

[5555] (1) Intra-station control communications LAPD port

[5556] The intra-station control communications ports can be simplex device ports or duplex device ports.

[5557] (a) Duplex device communications port

[5558] SIFSH: 2 (daisy chain)×14 (highway)×2 (ACT/SBY)=56 (including SIFSH for loop)

[5559] MESH: 4 (daisy chain)×2 (highway)×2 (ACT/SBY)=16

[5560] RMXSH: 16 (RMXSH)×2 (ACT/SBY)×2 (redundancy)=64

[5561] (b) Simplex device communications port

[5562] SINF: 8 (SINF)×2 (SIFSH)×14 (highway)=224

[5563] DS3: 8 (daisy chain)×2 (SISFH)×14 (highway)=224

[5564] FR: 4 (DSI)×8 (DTC)×4 (MUX)×2 (FIFSH)×14 (highway)=3584

[5565] FR accommodated by RMXSH: 4 (DSI)×8 (DTC)×4 (MUX)×2 (SIFSH)×16 (RMXSH)=4096

[5566] (2) Subscriber Control Communications LAPD Port

[5567] (a) UNI B-ISDN terminal unit 20 (TE)×8 (SINF)×2 (SIFSH)×14 (highway)=4480

[5568] (b) FR at SVC: Same as the FR (3584) of (1)(b), and the FR (4096) accommodated by the RMXSH

[5569] (c) Meta-signaling: Same as the SINF (224) of (1)(b)

[5570] 1.3.2 Required Number of Ports

[5571] (1) Common Units

[5572] SIFCOM: 2 ports (ACT/SBY) for intra-station control communications

[5573] MESH common unit: 2 ports (ACT/SBY) for intra-station control communications

[5574] RMXSH common unit: 4 ports (ACT/SBY and SIFSH) for intra-station control communications

[5575] (2) Individual Unit

[5576] SINF: 2 ports for intra-station control communications and meta-signaling; and n ports for connected terminals

[5577] DS3: 1 port for in.tra-station control communications

[5578] FR/SMDS: 1 port for intra-station control communications; and additional 1 port if the SVC is performed.

[5579] 1.3.3 Transfer Speed between BSGC and Other Devices

[5580] (1) The transfer speed between the BSGC and BCPR (INFA) is 4 Mbyte/sec. The execution speed is approximately 2 Mbyte/sec.

[5581] (2) The clock rate of the ATM switch control LSI is 2 Mbyte/sec.

[5582] (3) The band for the ATM switch is 1 Mbyte/sec.

[5583] (4) The communications between the BSGC and ATM switch are established after the communications procedure is determined between the BCPR (BSGC) and each intra-station device so that signals may not be stagnant in the BSGC. To prevent the signals from being stagnant in the BSGC, the number of ports accommodated in the BSGC are specified as follows (in the case of peak rate assignment).

[5584] (a) 1,024 16-Kbps ports to be accommodated

[5585] (b) 256 64-Kbps ports to be accommodated

[5586] (c) 128 128-Kbps ports to be accommodated

[5587] (d) 64 256-Kbps ports to be accommodated

[5588] The communications speed of the intra-station control communications link is 64 Kbps. Since the shortage of the band is expected in consideration of the concentration rate of the RMXSH, the communications speed can be altered by a command from the BCPR.

[5589] 1.3.4 Throughput of BSGC and Port Assignment Condition

[5590] The throughput of the BSGC is approximately 200 messages per second. The ports accommodated by the BSGC should be assigned under careful consideration of the throughput of the BSGC and the transfer speed indicated in 1.3.3. The subscriber signaling band for use in a signaling process is assigned likewise.

2. OUTLINE OF FUNCTIONS OF BSGCSH

2.1 Specification

[5591] FIG. 701 shows the outline of the functions of the BSGCSH.

2.2 Higher Order Interface (INF interface)

[5592] As explained in 1.2.1, the communications are set between the BSGC and BCPR through te INF.

[5593] 2.2.1 Hardware Configuration under Control of INF (Peripheral Interface)

[5594] FIG. 702 shows the connections of the hardware among the BCPR, INF, and BSGC.

[5595] 2.2.2 INF Interface Control Procedure

[5596] The peripheral (INF) interface can be controlled by the BCPR through an order and DMA transmission.

[5597] The ordering function can be realized as the function of the SBIF LSI in the BSGC. The orders relating to the BSGC include the followings.

[5598] (1) specifying an individual system to specify an active/standby system of the BSGC

[5599] (2) resetting BSGC

[5600] (3) instruction to the BSGC

[5601] (a) command activation: notification request for a command group generated by the BCPR

[5602] (b) retry instruction: retransmission request when a DMA access error occurs

[5603] (c) MSCN read: request to read through MSCN

[5604] (d) test loopback: write request of test loopback data

[5605] (e) reading test loopback data: request to read test loopback data

[5606] FIG. 703 shows the control sequence between the BSGC and BCPR.

[5607] The DMA transfer is activated by a command activation order (step 2). Then, the command group stored at the address in the BCPR memory reported by a command from the BCPR (step 1) is DMA transferred (step 3) to the memory in the BSGC under the control of the BSGC through the SBIF LSI and 80186 DMA function in the BSGC, and each command is processed (step 4). The transferred command group contains a plurality of commands, and the command instructs various requests from the BCPR to the BSGC. A command group is notified from the BCPR to the BSGC at 8-sec intervals. When the command group has been transferred, a command group reception notification is transferred from the BSGC to the BCPR (step 5).

[5608] When the BSGC generates an event to be provided for the BCPR, it generates a status (step 6), and a plurality of status notifications are reported to the BCPR in 8-msec units as status groups (step 7). The BCPR performs a reception process for the reported status (step 8). This is reported as a DMA transfer to the address of the memory in the BCPR preliminarily specified by a command from the memory in the BSGC.

2.3 Switch Interface (CARP and VCC Interface)

[5609] An intra-switch layer 1 is controlled by the CARP LSI mounted in the BSGC. The LSI has the function of assembling and disassembling a frame of an ATM adaptation layer (AAL) protocol type 3, 4, or 5.

[5610] The highway in the switch is determined by the VCC loaded into the BSGC-COM in the BSGC (BSGC common unit), the VCC loaded into the SIFCOM in the SIFSH, and the VCC loaded into the common unit in the MESH as shown in FIG. 704. The contents of the VCCs are set by the switch software executed by the BCPR.

[5611] 2.3.1 Hardware Configuration for Controlling Intra-switch Duplex Device

[5612] FIG. 704 shows the configuration of the hardware configuration for controlling an intra-switch duplex device.

[5613] 2.3.2 Intra-switch Signal Control

[5614] The BCPR preliminarily notifies the BSGC of the attribute of each port and a VPI/VCI. The BSGC initializes each port according to specified information.

[5615] The CARP sets an ATM cell header according to the specified VPI/VCI.

[5616] The switch software executed by the BCPR sets the contents of the VCC loaded into the BSGC-COM in the BSGC, the VCC loaded into the SIFCOM in the SIFSH, and the VCC loaded into the common unit in the MESH.

[5617] The functions of the VCC are listed below.

[5618] (1) The VCC is set by the BSGC, SIFSH, and MESH according to the instruction of the BCPR.

[5619] (2) The VCC is positioned in the duplex BSGC, SIFSH, and MESH. The VCC table of the two systems is copied by each device.

[5620] (3) The VCC is controlled by the BSGC having the smallest number.

[5621] The intra-switch control system is applied if it successfully reduces the loss of cells by switching the systems of ATM switches by transmitting the same signal to the ATM switches of active and standby systems.

[5622] The signal system model is shown as follows.

[5623] 2.3.2.1 Signaling Control Model (including simplex device)

[5624] In this model, a control signal relating to a simplex device and subscriber is transferred in an ATM switches of both active and standby systems.

[5625] FIG. 705 shows the signaling control model of a signal transmitted in the direction from the terminal unit to the switch. In FIG. 705, the system #0 is an active system.

[5626] For example, a signal from the terminal unit is distributed from the duplex ADS1 system to both active and standby systems of the duplex DTC. The signals received from the terminal units and distributed to the DTCs of the active and standby systems are distributed to the active and standby systems of the duplex ADSINFs. Then, the active and standby systems of the duplex SIFCOM fetch the signal from the terminal unit and distributed to the ADSINF of the active system (system #0). The signals from the terminal unit and fetched by the SIFCOM of the active system and standby system are distributed to the active and standby systems of the duplex ASSW. In the BSGCSH, the signal from the ASSW of the standby system is discarded by the BSGC-COM. A signal cell to be discarded is identified by an added tag. The discard process is described in 2.3.4.

[5627] FIG. 706 shows the signaling control model of a signal in the direction from a switch to a terminal unit. FIG. 706 shows that system #0 is an active system.

[5628] For example, a signal from the BSGC is distributed through a BSGC-COM to both active-and standby systems of the duplex ASSW. The signals received from the BSGC and distributed to the ASSWs of the active and standby systems are distributed to the active and standby systems of the duplex SIFCOMs. Then, the active and standby systems of the duplex ADSINF fetch the signal from the BSCG and distributed to the ASSW of the active system (system #0). The signals from the BSCG and fetched by the ADSINF of the active system and standby system are distributed to the active and standby systems of the duplex DTC.

[5629] 2.3.2.2 Duplex Device Signal Control Model (for common unit)

[5630] In this model, a signal related to each system of a duplex device is transferred in the ATM switch of each of the active and standby systems.

[5631] The communications are maintained by both active and standby systems of each duplex devices through the two ports for the BSGC of the active system. The BSGC and BSGC-COM each comprising two systems can be cross-connected. Accordingly, when a switch port of a standby system is accommodated by the BSGC of the standby system, the standby system route in the ATM switch is blocked when the BSGC of the standby system is in an OUS (out of service) state. To avoid this state, the two ports of the BSGC of the active system are connected to the active and standby systems of the duplex device.

[5632] For example, as shown in FIG. 707, the signal transferred to the BSGC from the SIFSH (SIF) of the active system is transmitted to the ASSW of the active system, and the signal transferred from the SIFSH (SIF) of the standby system to the BSGC is transmitted to the ASSW of the standby system.

[5633] The signal input from the device in the active system to the BSGC and the signal input from the device in the standby system to the BSGC are input through different ports of the BSGC. Therefore, they are provided with different tags. However, the BSGC of the active system and the BSGC of the standby system are assigned the same tag.

[5634] The BSGC-COM identifies the cells addressed to the two communications ports by a tag assigned to each signal cell input to the BSGC-COM, and transmits signal cells addressed to the ports to the BSGC without discarding them. The details of the process are described in 4 later.

[5635] The SIFSH transmits signals to the ASSWs of both active and standby systems. At this time, the signal cell transmitted to the standby system is provided with a tag indicating the discard by the BSGC-COM.

[5636] As shown in FIG. 708, when the BSGC transmits a signal to a duplex system, for example the SIFSH, the BSGC transmits the signal to the ASSWs of the active system and standby system from each of the two ports. the signal cell transmitted to both systems is provided with a fixed VCI. The SIFSH of each system receives only the signal from the ASSW of the matching system.

[5637] 2.3.3 Intra-station Control Communications VPI/VCI

[5638] When a signal is transferred from the SIFSH to the BSGC, the VCC in the SIFSH (refer to 6.3 in part 3) determines an output VPI/VCI/TAG specifying the BSGC using the VPI/VCI assigned to the subscriber as an input VPI/VCI as shown in FIG. 709A. The VCC in the SIFCOM is allocated for each SINF (individual unit) in the SINF in the SIFSH containing the SIFCOM.

[5639] If a signal is transferred from the BSGC to the SIFSH, the VCC determines an output VPI/VCI/TAG specifying each destination device/terminal unit using the BSGC card/port number connected to the VCC as an input VPI/VCI as shown in FIG. 709B. The VPI/VCI contains the VPI/VCI for the subscriber terminal unit determined by the meta-signaling. The BSGC card corresponds to the VPI, and the ESGC port corresponds to the VCI. Therefore, the software interface between the BCPR and the BSGC is established by using the above mentioned VCI.

[5640] When the communications are set between the BSGC and RMXSH, each device in the RMXSH is assigned a VPI/VCI similar to that assigned to the terminal unit in the SINF. The VPI/VCI is a fixed value corresponding to the device number.

[5641] FIG. 710 is a list of VPIs/VCIs.

[5642] 2.3.4 Cell Discard System in BSGC-COM

[5643] FIG. 711 shows the cell discard function in the BSGC-COM.

[5644] The DMUX-LSI in the BSGC-COM fetches a signal cell indicating a SIG/UL/TAGC pattern, that is, a tag assigned to the head of an input signal cell, only if the pattern matches a predetermined pattern. As described above in 2.3.2.1, the DMUX-LSI in the BSGC-COM discards a signal from the duplex device input from the ASSW of the standby system according to a predetermined standby condition.

2.4 BSGC Device Control

[5645] Each device in the BSGC is a duplex system and normally operated in a master/slave state.

[5646] The active system of the BSGC is specified depending on the specification of the individual system in the peripheral interface control through the BCPR. Likewise, the active system of the BSGC-COM is specified depending on the specification of the active system of the ASSW connected to the BSGC-COM (refer to FIG. 704).

[5647] 2.4.1 State of Device in BSGC

[5648] The contents of the memory in the BSGC of the master system are copied to the memory in the BSGC of the slave system. The contents of the VCC table loaded into the BSGC-COM of the master system are also copied to the VCC table in the BSGC-COM of the slave system. After copying data to the memory, every order from the BCPR is written to the memory in the BSGCs of both systems.

[5649] As shown in FIG. 712, the BSGC can be in one of the OUS, INS (master/slave), and standby states under the control of the BCPR.

[5650] (1) OUS (out of service) State

[5651] A state in which an INS/SBY activation from the BCPR is expected after the reset process in the BSGC. The determination about the BSGC and ATM switch is made only in this state.

[5652] (2) INS (in service) State

[5653] A state in which the system is operable after initialization is completed in both BSGCs of active and standby systems. The BSGC of the active system can communicate with each intra-station device and subscriber terminal unit because the port of the active system has been initialized.

[5654] (3) Standby (SBY) State

[5655] A state of the BSGC in an INS incorporating process

[5656] Listed below are the operation states in the BSGC of active and standby systems.

[5657] (1) Master/Slave State

[5658] A state in which data has been copied from the master system to the slave system and a duplex and synchronous operation is being performed when both systems are in the INS state. The BSGC of the master system monitors a fault in the BSGC of the slave system.

[5659] (2) Master-standby State

[5660] A state in the INS incorporating state for the BSGC of the standby system

[5661] (3) Master OUS State

[5662] An OUS state of the BSGC of the standby system. The BSGC of the master system does not monitor faults of the BSGC of the OUS system.

[5663] All the above listed states are managed by the BCPR.

[5664] 2.4.2 BSGC Fault Correcting Process

[5665] A fault in each system of the BSGC processor and BSGC-COM (switch unit) is monitored by the BCPR. The hardware for monitoring the faults is configured in the BSGC, and a detected fault is reported to the BCPR with an interruption to the INF. When an interruption is issued to the INF, the BCPR reads the MSCN according to the INF order, analyzes the contents of the fault, and performs a fault correcting process.

[5666] When the BSGCs are switched due to the fault between the BSGC and BSGC-COM, they are switched by the switch (resumption at interrupted point) of the Ph-A of the BSGC.

[5667] The fault of the active/standby system cross-connecting unit can be detected by cyclically monitoring the slave BSGC by the firmware of the master BSGC only when the BSGC is performing a master/slave synchronous operation. The slave BSGC monitors the power disconnection of the master BSGC.

[5668] Monitoring a BSGC-COM fault is stopped after it is detected, and is resumed by the trigger of ASSW INS (starting VCC copy). After the BSGC fault is detected, the BSGC is in a reset; wait state.

[5669] The OUS state is entered after the BSGC/BSGC-COM fault occurs, and the fault is when the automatic diagnostics result indicates OK at the next resumption.

2.5 Communications Control

[5670] The LAPD control through the BSGC is realized as the function of the firmware in the BSGC. The maximum simultaneous connection at the LAPD control equals the number of CARP ports (for example, 256) The BSGC performs the LAPD control on the LAPD communications to subscriber terminal units and the simple LAP communications (intra-station control communications) to intra-station devices.

[5671] 2.5.1 Difference from Q.922

[5672] In the layer 2 control of the LAPD, a revised LAPD is applied based on the CCITT (current ITU-T)-recommended Q.922 (LAPF).

[5673] FIG. 713 shows the frame format of the revised LAPD.

[5674] Listed below are the functions deleted from the Q.922.

[5675] (1) F pattern

[5676] (2) CRC generation/error check

[5677] (3) “0” insertion/deletion

[5678] (4) DLCI multiplex

[5679] (5) ECN, DE, D/C bit specification

[5680] (6) XID frame

[5681] (7) Dynamic window control

[5682] (8) I response reception

[5683] (9) FRMR response

[5684] “0” (fixed) is set in the DLCI and ECN. The layer 2 multiplex (multi-LAP) is not realized, either the “0” is not checked in the receiving equipment.

[5685] 2.5.2 Intra-station LAPD Communications (intra-station control communications)

[5686] In the intra-station LAPD communications control, a link is established between an intra-station device and the BSGC, and a cyclical monitor process is performed. A UI frame is used as a communications message to apply the protocol having the procedure of confirming data in the layer 3. In the BSGC, the sequence of messages is not checked.

[5687] An intra-station control communications link is autonomously established up to the layer 2 according to the information from the BCPIR.

[5688] This function is performed to reduce the load from the INF transfer then the resumption of the BCPR/BSGC operations are resumed. Therefore, this function is effective only when the BCPR/BSGC operations are resumed. When a link is not successfully established or after a link is disconnected, an individual request from the BCPR to establish a link is required.

[5689] Links corresponding to two communications ports for a duplex device are simultaneously established.

[5690] FIG. 714 shows the procedure of establishing the intra-station control communications link. FIG. 715 shows the procedure of establishing the intra-station control communications link for the BRLC.

2.6 Diagnostic Functions

[5691] The BSGC has the function of diagnosing the BSGCSH and providing a communications link for diagnosing the intra-station duplex device such as an ASSW.

[5692] 2.6.1 Diagnosis Object Items

[5693] Described below are the diagnostic functions of the BSGCSH.

[5694] (1) INF interface

[5695] i) CC access read/write

[5696] ii) DMA transfer read/write

[5697] (2) BSGC intra-package functions

[5698] i) deleting no function items based on present SGC diagnosis (MACH-1.2), and entering additional functions.

[5699] (diagnosing all portions accessible by the CPU=self-diagnostics)

[5700] (3) BSGC-SWINF

[5701] i) setting a loop between the BSGCSH and SWINF and testing a sending/receiving cell.

[5702] (4) VCC memory test

[5703] i) read/write test on the VCC table memory in the order starting with the BSGC having the smallest number

[5704] (5) BSGCSH

[5705] i) establishment test on the LAP link between the BSGCSH and other devices

[5706] (6) Cell-by-cell loop test in the BSGC-COM using a TCG (refer to 9.2).

[5707] 2.6.2 Intra-station Duplex Device Diagnostic Communications Link

[5708] The intra-station duplex device diagnostic communications link is established by the procedure similar to the active system BSGC online control procedure. To perform this function, either 0 (online) or 1 (diagnostics) can be specified as a parameter of the online operation activate command.

[5709] The BSGC activation sequence during the online diagnostics is explained in 5.2.

2.7 Configuration of Program Module

[5710] FIG. 716 shows the program module in the BSGC.

[5711] An INF control unit (INF-IOCS) 1 controls the communications between the BSGC and BCPR through the INF (INFA and INFT).

[5712] A device control unit 2 manages a device including the setting of the VCC.

[5713] A patrol control unit 3 checks for health between the BCPR and BCGC.

[5714] An inter-system communications control unit 4 controls the communications between the active and standby systems.

[5715] A memory copy control unit 5 copies the contents of the CPU memory.

[5716] A memory read/write control unit 6 performs a read/write process to the memory according to a command.

[5717] A system switch controlling unit 7 controls the switch of the active and standby systems.

[5718] A watch dog control unit 8 confirms and controls the normal operation of the BSGC.

[5719] A LAPD managing unit 9 manages the LAP link including the establishment of an intra-station LAP.

[5720] A LAPD control unit 10 performs the layer 2 control in accordance with the recommendation Q.922.

[5721] A CARP handler 11 converts VPI/VCI.

[5722] A switch control unit 12 controls the CARP.

3. INF INTERFACE

3.1 Hardware Configuration

[5723] The INF is controlled by the BSGC as a function of the SBIF LSI in the BSGC. FIG. 717 shows the hardware configuration relating to the INF.

3.2 DMA Bit Configuration

[5724] During the DMA access (write/read) the bit configuration is represented as follows among the BCPR, INF, and BSGC.

[5725] 3.2.1 Bit Configuration of DMA Transfer Data

[5726] FIG. 718 shows the bit configuration of the DMA transferred data between the main storage (MM) and BSGC.

3.3 INF Control Procedure

[5727] The present Applicant has established the method of minimizing the DMA transfer through the INFT and INFA under the control of the INF between the BCPR and BSGC to attenuate the load onto the BSGC.

[5728] 3.3.1 Command Queue and Status Queue

[5729] (1) A reception buffer is preliminarily reported in block units.

[5730] In the BSGC, up to two blocks of reception buffers are constantly reserved. If one block becomes full another block is added by the lead of the BCPR.

[5731] (2) A status queue is reported each time an event occurs.

[5732] The BSCG is uniquely provided with an unused pointer for a status queue. The pointer is updated by reading the value of the tail pointer to the status queue in the BCPR only when the entire status queue is used. When the status queue is full, a space monitor process is performed (by reading a tail pointer)at a 128 cycle.

[5733] (3) An end of command notification, which increases the load by reporting a status, is replaced by the following processes.

[5734] i) A command response 7fis made when all processes including the DMA transfer of the I frame in the command group are completed. If an abnormal condition is detected in the entire command group, a command response 55 is returned.

[5735] ii) Simultaneously, end information is prepared for each command for each bit, and output as an NG response when a signal is discarded for any factor in the BSGC. The factor of the NG response can be the shortage of a reception buffer. When the end information indicates NG, the entire command group is normal and a command response 7F is returned.

[5736] iii) The BSPR performs an end of command process at the trigger of the above described response

[5737] (4) Up to 64 commands can be entered in a command group in consideration of the throughput of the BSGC.

[5738] (5) Up to 8 commands can be entered in a status group simultaneously transmitted in consideration of the conflict in a DMA transfer.

[5739] 3.3.2 Conflict at Command Activation and Status Activation

[5740] When a command is activated or a status is activated, the DMA transfer is activated under the control of the BSGC. Described below is the procedure of the process.

[5741] (1) Command activation

[5742] The process of completing the DMA transfer of a command queue and completing the DMA transfer specified in the command queue is performed as a series of processes. The activation of a command from the BCPR is processed as an interruption in the BSGC.

[5743] (2) Status activation

[5744] The process of completing a 1-frame DMA transfer, a status DMA transfer, and the DMA transfer for the update of a head pointer is performed as a series of processes. The status activation to the BCPR is performed at an 8 msec cycle. Events occurring within an 8 msec are collectively DMA-transferred. 1-frame DMA transfer is performed before any other transfer each time an event occurs. Except in a contention of commands, status to be reported to the status queue, if existing, is transmitted repeatedly.

[5745] Commands and status are processed in the DMA transmission termination process as an intra-BSGC interruption or look-in process.

[5746] (3) Contention control

[5747] No contention or interruption occurs in a series of processes in (1) and (2) above.

[5748] Possible contention at the activation is controlled according to the following references.

[5749] i) Intra-BSGC priority control is performed such that the DMA transfer is activated without idle INF transfer.

[5750] ii) The next command is waited for according to the logic in the BSGC until the BSGC completes its internal process on a received command.

[5751] 3.3.3 Congestion Control

[5752] The congestion control in the BSGC can be receiving system congestion control, sending system congestion control, and BSGC congestion control.

[5753] 3.3.3.1 Receiving System Congestion Control

[5754] The congestion control of a receiving buffer is exercised for each link.

[5755] When congestion occurs in a receiving buffer, the RNR is transmitted for each link. The receiving buffer is used with all ports chained to the CARP LSI for controlling the interface with the ATM switch. Therefore, the congestion control of the receiving buffer is exercised among a switch control unit (CARP IOCS) 1, LAPD control unit 2, and INF control unit (INF IOCS) in the BSGC as shown in FIG. 719 (also refer to FIG. 716).

[5756] If a busy receiving buffer prevents the CARP IOCS 1 from hunting the receiving buffer and the receiving buffer from being connected to the CARP, then the CARP is underlined only. However, since the process of the L2 information only is required even during the congestion, the number of buffers required by the CARP (maximum number of control channels) is required in the process between the CARP IOCS 1 and the LAPD control unit.

[5757] The congestion in the receiving buffer occurs in the BSGC when data cannot be transmitted to the BCPR through the INF due to too many transactions in the BCPR. The control of the congestion for the factors of the BSGC is explained in 3.3.3.3.

[5758] 3.3.3.2 Sending System Congestion Control

[5759] The sending buffer congestion control is exercised for each link.

[5760] If the congestion has arisen in the sending buffer, the information as to whether the congestion refers to the first, second, or third congestion is reported to the BCPR.

[5761] The first, second, and third congestion occurs when the use rate of the transmission buffer reaches 70%, 80%, and 100% respectively. The first congestion is reported only when the congestion continues for a predetermined period in the BSGC.

[5762] <Control for the first congestion>

[5763] If the first congestion occurs, the BCPR does not accept a new call.

[5764] After the occurrence of the first congestion, the number of signals processed by the BSGC is maintained and not reduced.

[5765] <Control for the second congestion>

[5766] If the second congestion occurs, the BCPR sends only the required number of signals required by the intra-station LAPD, etc. In the port using UI frames, an ACK (response) wait process is not performed for the transmitted UI frames, and the UI frames stay in the BSGC for a very short time.

[5767] The ESGC gains congestion control (number of buffer count), similar to that over the receiving buffer, between an INF control unit 1and switch control unit 12 shown in FIG. 716 for each port. Furthermore, the BSGC performs the DMA transfer relating to the sending buffer after the INF control unit 1 (FIG. 716) gets a port number in the command field. Accordingly, the sending buffer can be managed in port units. If the sending buffer of the port to be limited is running short in spite of the limit based on the above described first and second congestion control, then new congestion control can be exercised without using the buffer of the other port. This congestion control is referred to as third congestion control.

[5768] <Control for the third congestion>

[5769] (1) When the BSGC receives a buffered-command for the line having no sending buffer, it answers the BCPR with an NG response as end of command group information of the INF.

[5770] (2) The BCPR transmits a DL-EST-RQ (link reset request) to the corresponding line in the BSGC when the end of command group information indicates NG. After reporting the end of command information NG and before receiving the DL-EST-RQ (link reset request), the BSGC continues answering with the end of command information NG in response to the I frame transmission request to the corresponding port.

[5771] (3) All signals in the link of the BSGC are discarded by resetting the link, thereby enabling the communications of new information.

[5772] (4) The BCPR performs a matching-process between the BCPR and a terminal unit or an intra-station device.

[5773] If the third congestion occurs, no retry process is performed because the BSGC is considered not to be normally operating for the reasons listed below in (a) through (c).

[5774] (a) The third congestion is preceded by the restrictions under the control of the first and second congestion control.

[5775] (b) If the I frame stays in the BSGC for more than 200 hours, a corresponding link is autonomously reset according to the logic in the BSGC. However, the logic is not applied to the UI frame.

[5776] (c) If the communications exceed the throughput of the BSGC, the first congestion control is exercised under the BSGC congestion control explained in

[5777] 3.3.3.3. BSGC Congestion Control

[5778] The BSGC monitors the use rate of the CPU in the BSGC every 10 seconds, and calculates the average every minute and every 15th minute. The BSGC issues a congestion report to the BCPR when the state in which the average CPU use rate equals or exceeds 90% is maintained for longer than a predetermined threshold time.

[5779] Upon receipt of the report, the BCPR determines the occurrence of the first congestion in all ports in the BSGC and restricts the setting of a new call.

[5780] FIG. 720 shows the model of the number of BSGC signals under the above described congestion control.

3.4 Initializing INF

[5781] The BCPR notifies the BSGC of the INF control information according to the procedure listed below to communicate with the BSGC through the INF (INFT and INFA).

[5782] (1) At the initialization of the INF control information, only an initialization command is transmitted from the BCPR.

[5783] (2) Set in the initialization command is the address of the INF initialization information setting table storing the INF interface information such as an entered status queue, receiving buffer, etc. The BSGC acquires the INF interface information from the table. The INF initialization information setting table is provided in physical memory space in series.

[5784] (3) FIG. 721 shows the format of the initialization command and INF initialization information setting table.

3.5 INF Priority Control

[5785] In the signal process for the switch software executed by the BSGC and BCPR, the following process system is adopted to perform by priority the fault correcting processes from the SIFSH, etc. In this system, a plurality of transmission queues of messages to be transmitted from the BSGC to the switch software are provided. A signal received by the BSGC is distributed to any of the queues depending on the priority level assigned to the signal.

4. SWITCH INTERFACE

4.1 Assigning Tag

[5786] 4.1.1 Concept of Assigning Tag

[5787] The concept of assigning a tag is explained in 5. of part 3 (refer to FIGS. 121, 126, 129, etc.)

[5788] 4.1.2 Assigning Tag in Communications from BSGC to ASSW

[5789] FIG. 722 shows the method of using the tag SIG/UL/TAGC through the SIFSH in the communications from the BSGC to the SIFSH.

[5790] FIG. 723 shows the method of using the tag SIG/UL/ADS1BLK/ADS1SEL through the SIFSH in the communications from the BSGC to the RMXSH.

[5791] FIG. 724 shows the method of using the tag SIG/UL/TAGC through the SIFSH in the communications from the BSGC to the SIFSH.

[5792] 4.1.3 Assigning Tag in Communications from ASSW to BSGC

[5793] FIG. 725 shows the method of using the tag SIG/UL/TAGC through the BSGCSH in the communications from the ASSW to BSGC. The BSGCSH identifies the above mentioned tag through the DMUX-LSI loaded into the BSGC-COM.

4.2 CARP Control Procedure

[5794] The layer 1 control in the ASSW (ATM switch) interface is gained by the CARP LSI. The LSI has the function of assembling and disassembling an AAL (ATM Adaptation Layer) protocol type frame of type 3, 4, or 5.

[5795] The CARP LSI consists of CARP 1 and CARP 2 to simultaneously assemble and disassemble up to 1024 channels of cells (up to 256 channels in the BSGC by the restrictions of the firmware) under the control of the CPU (80186 system).

[5796] The protocol type 3, 4, or 5 can be set for each port, and these types can be mixed in the BSGC according to the settings through the switch software.

[5797] 4.2.1 Frame Format

[5798] FIG. 726 shows the SAR-PDU of protocol type 3 (as in type 4) and the configuration of the header field of the ATM cell containing the SAR-PDU. FIG. 727 shows the frame (CPAAL5-PDU) of protocol type 5. Refer to 4.2, etc. of part 3. The contents of the ATM header shown in FIG. 726 are set by the CVV in the BSGC-COM. In this case, the identification number of the BSGC is set as a VCI and the port number in the BSGC is set as a VPI in the ATM. The other fields are set to 0.

[5799] The payload of the SAR-PDU of protocol type 3 shown in FIG. 726 stores a LAPD message.

[5800] If the data length of the LAPD data is 44 bytes (refer to FIG. 749), the message is stored in the payload of a single SAR-PDU. In this case, a single segment message (SSM) is set as an ST in the SAR-PDU, and 44 bytes are assigned to an LI.

[5801] If the data length of the LAPD is 256 bytes (refer to FIG. 750), the message is divided into 44-byte segments, and the segments are stored in the payloads of a plurality of SAR-PDU. Therefore, the LAPD data is divided and stored in a plurality of ATM cells, and then transferred. In this case, the beginning of message (BOM) is set as an ST in the SAR-PDU storing the leading segment, and 44 bytes are assigned as an LI. The continuation of message (COM) is set as an ST in the SAR-PDU storing an intermediate segment, and 44 bytes are assigned as an LI. Furthermore, the end of message (EOM) is set as an ST in the SAR-PDU storing the trailing segment, and 36 bytes are assigned as an LI (FIG. 750).

[5802] The frame of protocol type 5 shown in FIG. 727 is divided into 48-byte segments, and the segments are stored in the payloads of a plurality of ATM cells.

[5803] 4.2.2 Functions of CARP LSI

[5804] The transmitting functions for the CARP LSI are listed below.

[5805] (1) write to transmission cell

[5806] (2) generation of SAR-PDU header (numerical control)

[5807] The receiving functions for the CARP LSI are listed below.

[5808] (1) header check

[5809] (2) check of long/short frame

[5810] The BSGC does not check an HEC.

[5811] 4.2.3 Statistic Functions

[5812] The numbers of passing cells and discarded cells are counted by the MUX/DMUX LSI. The number of CRC errors is counted by the CARP LSI.

4.3 VCC Setting Procedure and VCC Copying Procedure

[5813] The BSGC writes data for the VCC of both systems when it receives a VCC copy start request or VCC setting request (for both systems) from the BCPR.

[5814] When the ATM switch is turned into the OUS state, the BSGC writes data for the VCC of one system if it receives a single-system VCC set request.

[5815] The write highway (mate system/home system) of the VCC is specified by the BCPR through a COM INS report.

[5816] FIG. 728 shows the VCC setting procedure. FIG. 729 shows the copy start procedure. FIG. 730 shows the copy stop procedure.

5. BSGC DEVICE CONTROLLING PROCEDURE

5.1 BSGC Fault Monitor

[5817] The fault correcting process to be performed by the BSGC handles the following faults.

[5818] (1) faults of the BSGC itself

[5819] (2) INF interface fault; reporting by interrupting the INFs of both systems

[5820] (3) faults detected by active BSGC

[5821] (a) fault of switch

[5822] (b) standby system inter-system cross connection fault: reported by status. (including a mate BSGC IBP fault)

[5823] Since the fault of the BSGC of the master system should be urgently corrected, it is reported by an interruption to the INF. If a fault occurs in the BSGC itself and the BSGC is an active system, then the systems are switched and the faulty system is recognized as an OUS state. If the BSGC is a standby system, then an ISOL is set in the active system and the faulty system is recognized as an OUS state (refer to 1 and 2 of FIG. 731).

[5824] If a fault occurs in the ASSW, an ASSW fault correcting process is performed. The majority logic is not applied to the BSGC-COM at the system switch (refer to (3) of FIG. 731).

[5825] If a fault indicated by (2) in FIG. 731 occurs, it is not determined whether the fault exists in the BSGC or BSGC-COM. The BCPR reads the factor of the fault from the faulty BSGC having the numbers #0 through #5 of both systems and obtains a normal route, thereby performing a fault correcting process.

[5826] 5.1.1 Faulty Portion Detected in BSGCSH

[5827] FIG. 731 shows the model of the fault range.

[5828] In FIG. 731, fault (1) refers to a fault of the BSGC (watch dog time over, DRAM parity error, etc.). Fault (2) refers to a data parity error between the BSGC and BSGC-COM, disconnection of a clock/cell frame, etc. Fault (3) refers to an alarm from the LSI of the DMUX, MUX, etc. of the BSGC-COM, data parity error in the inter-package communications, etc.

[5829] The report to the switch software is made by an interruption to the INF from the BSGC of the system which detected the fault. The report is made to each of the faults (1), (2), and (3) shown in FIG. 731 using the MSCN.

[5830] 5.1.2 System Management at Fault Occurrence

[5831] (1) BSGC fault

[5832] (fault (1) shown in FIG. 731 or (1) at the rightmost column shown in FIG. 745)

[5833] If an INF interruption occurs from the BSGC of an active system, the BSGC system is switched.

[5834] If an INF interruption occurs from the BSGC of a standby system, an AISOL is set in the active system and the faulty system is recognized as an OUS state.

[5835] (2) Fault between BSGC and BSGC-COM

[5836] (fault (2) shown in FIG. 731 or (2) at the rightmost column shown in FIG. 745)

[5837] This fault is reported from each BSGC of the active and standby systems through an INF interruption.

[5838] The system management according to the report from each fault detection point is shown in and after FIG. 733.

[5839] (3) BSGC-COM Fault

[5840] (fault (3) shown in FIG. 731 or (3) at the rightmost column shown in FIG. 745)

[5841] This fault is reported from each BSGC of the active and standby systems through an INF interruption.

[5842] The BSGC-COM of the faulty system is put in the OUS state, and the BSGC-COM of the non-faulty system is put in the active state. Since the active/standby state of the BSGC-COM is subject to that of the ASSW, the systems of the ASSW are switched in the above described case.

[5843] FIG. 732 shows the method of detecting the BSGCSH-COM fault through the BSGC, and of notifying the switch software of the fault. As shown in FIG. 732, the BSGC has the 2-bit information for the home/mate systems for each fault point of the BSGC-COM. However, the BSGC-COM common fault point (a single fault point for each BSGC-COM system) has 2-bit information for the home/mate system only in the BSGC of the smallest number.

[5844] Described below is the system management method followed when a fault occurs between the BSGC and the BSGC-COM.

[5845] (1) Fault detected by a checker in the BSGC-COM when data is sent from the BSGC to the BSGC-COM

[5846] FIG. 733 shows the detection point of a fault detected by the checker in the BSGC-COM in sending data from the BSGC to the BSGC-COM.

[5847] (1)-1 When 1-bit fault detection bit is set in FIGS. 733(a) through (b)′ (when the fault occurs at a single point);

[5848] If a fault occurs at the fault point (a) shown in FIG. 733, the fault occurs in the data in one of the two destination systems receiving data from the #0 BSGC (#0 system BSGC→#0 system BSGC-COM, and #0 system BSGC→#1 system BSGC-COM). However, no fault occurs in the data of the two destination systems receiving data from the #1 system BSGC. Therefore, the #1 system BSGC is put in the active state and the #0 system BSGC is put int the OUS state. Likewise, FIG. 734 shows the state entered when a fault occurs at one of the fault points (a), (a)′, (b), and (b)′ shown in FIG. 733. A diagnostics process (DP) is carried out on the BSGC in the OUS system to specify the fault point.

[5849] In FIG. 734 (note 1), in setting the duplex communications, the BSGC systems are switched as shown in the above described table. If a fault is detected by the checker in the BSGC-COM in the diagnostics process (DP) activated after the OUS state is determined in the BSGC, the system is maintained after the BSGC-COM of the faulty system is put in the OUS state.

[5850] (1)-2 When a 2-bit fault detection bit is set in FIGS. 733(a) through (b)′ (when faults occur at two or more points);

[5851] The following two cases can be assumed.

[5852] i) If faults are detected at two fault points (a) and (b), or if the faults are from the data sent from the same BSGC as in the case where the faults are detected in the two fault points (a)′ and (b)′.

[5853] ii) If faults are detected at; two fault points (a) and (a)′, or if the faults are from the data sent from the same BSGC-COM checker as in the case where the faults are detected in the two fault points (b) and (b)′.

[5854] In the example i) above, if faults are detected in the two fault points (a) and (b) shown in FIG. 733, then it is determined that the #0 system BSGC is faulty, and the #0 system BSGC is in the OUS state, while the #1 system BSGC is in the active state. If faults are detected in the two fault points (a)′ and (b)′, then it is determined that the #1 system BSGC is faulty, and the #1 system BSGC is in the OUS state, while the #0 system BSGC is in the active state.

[5855] In the case ii above, if faults are detected in the fault points (a) and (a)′ shown in FIG. 733, it is determined that the #0 system BSGC-COM is faulty. Since the system of the BSGC-COM is set subject to the setting of the system of the ASSW, the systems of the ASSW are switched when the #0 system ASSW is a master system, thereby putting the #0 system ASSW in the OUS state and setting the #1 system ASSW as a master system. The systems of the ASSW are not switched when the #0 system ASSW is a slave system, thereby maintaining the #0 system ASSW in the OUS state. If faults are detected in the two fault points (b) and (b)′ shown in FIG. 733, then it is determined that the #1 system BSGC-COM is faulty. Since the system of the BSGC-COM is set subject to the setting of the system of the ASSW, the systems of the ASSW are switched when the #1 system ASSW is a master system, thereby putting the #1 system ASSW in the OUS state and setting the #0 system ASSW as a master system. The systems of the ASSW are not switched when the #1 system ASSW is a slave system, thereby maintaining the #1 system ASSW in the OUS state.

[5856] FIG. 735 shows the state detected when faults are detected at 2 points of the fault points (a), (a)′, (b), and (b)′ shown in FIG. 733. The diagnostics process (DP) is performed on the OUS system BSGC to specify fault points.

[5857] FIG. 736 shows the case in which a fault of the checker in the BSGC-COM is determined after the fault shown in FIG. 735 (Note 1) is detected and the diagnostics process is performed.

[5858] FIG. 737 shows the case in which a fault of the checker in the BSGC-COM is determined after the fault shown in FIG. 735 (Note 2) is detected and the diagnostics process is performed.

[5859] If a fault described in note 3 or 4 shown in FIG. 735 is detected, it indicates that the standby system link to the intra-station duplex device is disconnected. When this fault occurs, the diagnostics process (DP) is not performed, but the BSGC-COM package of the faulty system is switched according to the following references.

[5860] If faults are detected in fault points (a) and (a)′ or (b) and (b)′, the following four cases can be assumed as a fault point.

[5861] i) When the factor of the fault resides in only the BSGC-COM package.

[5862] ii) When the factor of the fault resides in both sending function of the BSGC and receiving function of the BSGC-COM, and when the fault occurs in only one route of the sending function of the BSGC and the receiving function of the BSGC-COM.

[5863] iii) When the fault factor the same as that shown in ii above is present, and when the fault occurs only in the route different from that described in ii above.

[5864] iv) In the above described case i, the system can recover from the fault by exchanging the BSGC-COM packages. In case ii or iii, a maintenance process can be performed because one fault detection bit is set after exchanging the BSGC-COMs. In the case iv above, the same fault will occur again even after the exchange of the BSGC-COMS, and the BSGC-COMs of both #0 and #1 systems are exchanged.

[5865] If faults are detected at both fault points (a) and (a)′, the following procedures are required to specify the BSGC or BSGC-COM for the fault point.

[5866] Condition: the #0 system BSGC is the active system and the #1 system BSGC is the slave system.

[5867] Procedure 1: Since the #1 system BSGC is a slave system, the #1 system BSGC is put in the OUS state, and the diagnostics process (DP) is performed. Fault points can be specified relating to the fault at fault point (a)′ between the #1 system BSGC and #0 system BSGC-COM.

[5868] Procedure 2: Then, the states of systems #0 and #1 of the BSGC are switched. That is, after the #1 system BSGC is put in the OUS state and then set as a slave system, the master/slave states of the #0 and #1 BSGCs are switched. Finally, the #0 system BSGC is set as a slave system and then put in the OUS state. The diagnostics process (DP) is then performed and fault points can be specified relating to the fault at fault point (a).

[5869] If faults are detected at both fault points (b) and (b)′, the fault points can be specified, the BSGC or BSGC-COM, for the fault point according to the above described procedure.

[5870] If the combination other than the two fault detection bits is set, or if 3 or more fault detection bits are set, then double faults are assumed and no system can be restructured. However, a fault message should be output and the contents are designed as a pattern different from the message output at the occurrence of the fault. In this case, the detailed fault contents collected from the BSGCs of both systems are completely output.

[5871] (2) Fault detected by the checker in the BSGC when data is sent from the BSGC-COM to the BSGC

[5872] FIG. 738 shows the detection point of a fault detected by the checker in the BSGC in sending data from the BSGC-COM to the BSGC.

[5873] (2)-1 When 1-bit fault detection bit is set in FIG. 738 (a) through (b)′ (when the fault occurs at a single point);

[5874] If a fault occurs at the fault point (a) shown in FIG. 733, the fault occurs in the data in one system receiving data from the #0 BSGC-COM (#0 system BSGC-COM→#0 system BSGC), and #0 system BSGC→#1 system BSGC-COM). However, the fault factor comes from either the sending function of the #0 system BSGC-COM or the receiving function of the #0 system BSGC. When the fault occurs, it is assumed that the problem resides in the receiving function of the #0 system BSGC and the #0 system BSGC is put in the OUS state and the #1 system BSGC is put in the active state. Then, the diagnostics process (DP) is activated, and it is determined whether the fault point refers to the BSGC-COM or the BSGC. If it is determined that the sending function of the #0 system BSGC-COM has a problem, then the #0 system BSGC-COM is put in the OUS state (the #0 system ASSW is put in the OUS state), the #1 system BSGC-COM is put in the active state (the #0 system ASSW is put in the active state), and the maintenance process is performed.

[5875] FIG. 739 shows the state entered when a fault occurs at one of the fault points (a), (a)′, (b), and (b)′ shown in FIG. 738.

[5876] (2)-2 When a 2-bit fault detection bit is set in FIG. 738 (a) through (b)′ (when faults occur at two or more points);

[5877] The following two cases can be assumed.

[5878] i) If faults are detected at two fault points (a) and (b), or if the faults are from the data sent from the same BSGC as in the case where the faults are detected in the two fault points (a)′ and (b)′.

[5879] ii) If faults are detected at two fault points (a) and (a)′, or if the faults are from the data sent from the same BSGC-COM checker as in the case where the faults are detected in the two fault points (b) and (b)′.

[5880] In the example i) above, if faults are detected in the two fault points (a) and (b) shown in FIG. 733, then it is determined that the #0 system BSGC is faulty. Since the system of the BSGC-COM is set subject to the setting of the system of the ASSW, the systems of the ASSW are switched when the #0 system ASSW is a master system, thereby putting the #0 system ASSW in the OUS state and setting the #1 system ASSW as a master system. The systems of the ASSW are not switched when the #0 system ASSW is a slave system, thereby maintaining the #0 system ASSW in the OUS state. If faults are detected in the two fault points (a)′ and (b)′ shown in FIG. 733, then it is determined that the #1 system BSGC-COM is faulty. Since the system of the BSGC-COM is set subject to the setting of the system of the ASSW, the systems of the ASSW are switched when the #1 system ASSW is a master system, thereby putting the #1 system ASSW in the OUS state and setting the #0 system ASSW as a master system. The systems of the ASSW are not switched when the #1 system ASSW is a slave system, thereby maintaining the #1 system ASSW in the OUS state.

[5881] In the case ii above, if faults are detected in the fault points (a) and (a)′ shown in FIG. 733, it is determined that the #0 system BSGC-COM is faulty, and the #0 system BSGC is in the OUS state, while the #1 system BSGC is in the active state. If faults are detected in the two fault points (b) and (b)′, then it is determined that the #1 system BSGC is faulty, and the #1 system BSGC is in the OUS state, while the #0 system BSGC is in the active state.

[5882] FIG. 740 shows the state where faults are detected at two points in the fault points (a), (a)′, (b), and (b)′ shown in FIG. 738. The diagnostics process (DP) is performed on the OUS system BSGC to specify a fault point.

[5883] FIG. 741 shows the case in which a fault of the checker in the BSGC-COM is determined after the fault shown in FIG. 740 (Note 3) is detected and the diagnostics process is performed.

[5884] FIG. 742 shows the case in which a fault of the checker in the BSGC-COM is determined after the fault shown in FIG. 740 (Note 4) is detected and the diagnostics process is performed.

[5885] If a fault described in note 1 or 2 shown in FIG. 740 is detected, it indicates that the standby system link to the intra-station duplex device is disconnected. When this fault occurs, the diagnostics process (DP) is not performed, but the BSGC-COM package of the faulty system is switched according to the following references.

[5886] If faults are detected in fault points (a) and (b) or (a)′ and (b)′, the following four cases can be assumed as a fault point.

[5887] i) When the factor of the fault resides in only the BSGC-COM package.

[5888] ii) When the factor of the fault resides in both sending function of the BSGC and receiving function of the BSGC-COM, and when the fault occurs in only one route of the sending function of the BSGC and the receiving function of the BSGC-COM.

[5889] iii) When the fault factor the same as that shown in ii above is present, and when the fault occurs only in the route different from that described in ii above.

[5890] iv) In the above described case i, the system can recover from the fault by exchanging the BSGC-COM packages. In case ii or iii, a maintenance process can be performed because one fault detection bit is set after exchanging the BSGC-COMs. In the case iv above, the same fault will occur again even after the exchange of the BSGC-COMs, and the BSGC-COMs of both #0 and #1 systems are exchanged.

[5891] If faults are detected at both fault points (a) and (b), the following procedures are required to specify the BSGC or BSGC-COM for the fault point.

[5892] Condition: the #0 system BSGC is the active system and the #1 system BSGC is the slave system.

[5893] Procedure 1: Since the #1 system BSGC is a slave system, the #1 system BSGC is put in the OUS state, and the diagnostics process (DP) is performed. Fault points can be specified relating to the fault at fault point (b) between the #1 system BSGC and #0 system BSGC-COM.

[5894] Procedure 2: Then, the states of systems #0 and #1 of the BSGC are switched. That is, after the #1 system BSGC is put in the OUS state and then set as a slave system, the master/slave states of the #0 and #1 BSGCs are switched. Finally, the #0 system BSGC is set as a slave system and then put in the OUS state. The diagnostics process (DP) is then performed and fault points can be specified relating to the fault at fault point (a).

[5895] If faults are detected at both fault points (a)′ and (b)′, the fault points can be specified, the BSGC or BSGC-COM, for the fault point according to the above described procedure.

[5896] If the combination other than the two fault detection bits is set, or if 3 or more fault detection bits are set, then double faults are assumed and no system can be restructured. However, a fault message should be output and the contents are designed as a pattern different from the message output at the occurrence of the fault. In this case, the detailed fault contents collected from the BSGCs of both systems are completely output.

[5897] 5.1.3 Report to BSGC

[5898] FIG. 743 shows the fault report model.

[5899] The report from the BSGC-COM <fault detection point> to the BSGC is made according to the level signal.

[5900] The fault of the BSGC-COM <fault detection point> is terminated by the SBIF LSI (refer to 3.1 and FIG. 717), and reported to the switch software by an INF interruption.

[5901] In response to the above described interruption, the switch software reads the detailed fault information by an MSCN read order.

[5902] The MSCN read order resets the MSCN layer in the BSGC and the alarm for the fault occurrence point is nullified.

[5903] 5.1.4 Recovery Monitor

[5904] 5.1.4.1 Recovery monitor by BSGC

[5905] The BSGC does not monitor the recovery from faults. It is considered that the system successfully recovers from a fault when the built-in diagnostics process results in OK.

[5906] 5.1.4.2 Recovery Monitor in Switch Software

[5907] The switch software monitors the recovery from faults (in both active and standby systems) of (1), (2), and (3) introduced at the beginning of 5.4. The system switch of the BSGC and ASSW (system switch of the BSGC-COM) should be managed by the BSGC, and the recovery cannot be monitored by the BSGC. The recovery monitor is performed by the switch software.

[5908] 5.1.5 Fault to be Detected by the BSGC Hardware

[5909] The fault to be detected by the BSGC hardware can be a fault in the INF and in the BSGC itself. The fault is reported to BCPR and the firmware of the BSGC through interruption. The fault is detected and reported by the BSGC hardware of each of the active and standby systems.

[5910] FIG. 744 shows the detained fault factors.

[5911] The fault detected in the INF interface by the BSGC can be directly checked by an MSCN read command. The fault of the BSGC is a representative point in the MSCN. Therefore, the details of the fault should be collected by the MSCN read sequence.

[5912] FIG. 745 shows the accommodation of the BSGC MSCN.

[5913] The MSCN shows each fault occurrence point using a representative point. The fault occurrence point is shown in FIG. 731.

[5914] Correspondence between each bit of the MSCN shown in FIG. 745 and the fault points (a), (a)′, (b), and (b)′ shown in FIGS. 733 and 738 is represented as shown below.

[5915] Correspondence Between FIGS. 745 and 733

[5916] MSCN data of #0 system BSGC→(a): bits 15, 14 (b): bit 12, 11

[5917] MSCN data of #1 system BSGC→(a)′: bits 12, 11 (b)′: bit 15, 14

[5918] Correspondence Between FIGS. 745 and 734

[5919] MSCN data of #0 system BSGC→(a): bits 09, 08 (a)′: bit 06, 05

[5920] MSCN data of #1 system BSGC→(b): bits 9, 08 (b)′: bit 06, 05

[5921] The exact factor of the BSGC fault shown in FIG. 746 is reported to the BCPR through a TM save.

[5922] FIG. 747 shows an exact factor of the fault reported through an MSCN details read command.

[5923] 5.1.6 Fault Detected by BSGC Firmware

[5924] The BSGC firmware performs the two following types of fault monitor.

[5925] (1) Hardware fault of both systems of the BSGC-COM (including the hardware fault between the BSGC and BSGC-COM)

[5926] (2) Fault of standby system BSGC. This fault is monitored by an active system BSGC firmware.

[5927] The above described fault (1) is reported by an interruption from the fault detecting BSGC to the INF. It is explained in detail in 5.4.6.1.

[5928] The above described fault (2) is reported from an active system BSGC as a status. It is explained in detail in 5.4.6.2.

[5929] 5.1.6.1 Fault in BSGC-COM (excluding faults of the BSGC)

[5930] FIG. 748 shows the detection sequence of the fault in the BSGC-COM.

[5931] This fault is detected by the BSGC firmware's detecting the state detected by the BSGC hardware in the 8-msec-cycle look-in process. Then, the INF interruption register is set. When an INF interruption is issued, the BCPR sets a timer of up to 16 msec. When the timer indicates timeout (refer to FIG. 748), a fault generation point is specified by issuing the MSCN read command. The BCPR further issues an MSCN details read command to the interrupting BSGCM to collect detailed information. When the BSGC receives the command, it reports the fault data stored in the register. The BCPR performs the system management process described in 5.4.2 according to the MSCN data and the data obtained in response to the MSCN details read command.

[5932] 5.1.6.2 Fault in Standby System BSGC

[5933] This fault is detected by an active system BSGC's periodical monitoring the fault of the duplex process control unit of the standby system BSGC. The monitor cycle is 2 sec. The monitor is performed only when the active system is operated in synchronism with the standby system. The fault is reported by the active system BSGC as a status.

5.2 TM Save System

[5934] When a processor fault occurs, the BSGC saves the fault information in the memory of the home system. This is referred to as a TM save process. The BCPR detects the BSGC processor fault through an INF interruption. The detailed fault information is read from the memory in the BSGC according to the MSCN read command and MSCN detailed read command issued from the BCPR to the BSGC after the INF interruption, and then transferred to the BCPR.

5.3 Statistic Function

[5935] The BSGC statistic function is provided as the following two methods.

[5936] (A) Function of collecting data by the BSGC firmware according to an instruction from the BCPR. The statistics data is read according to the 15-minute notification from the BCPR. There are the three types of statistics items as follows.

[5937] (1) BSGC CPU use rate

[5938] (2) Numbers of L2 transmission frames and of octets (in port units)

[5939] (3) Number of CRC errors

[5940] The cell statistics is obtained by the statistics function of the D-MUX/MUX LSI loaded into the BSGC-COM. There are three types of statistics items as follows. The BCPR reads the three types of the statistics data each time it issues a statistics read/write request.

[5941] (1) Number of reported cells

[5942] (2) Number of discarded cells

[5943] (3) Number of passing cells with specific VPI/VCI

6. COMMUNICATIONS CONTROL

6.1 Control of Intra-Station Control Communications

[5944] Described below is the interface required by the BSGC for the intra-station control communications. Layer 1 is based on the type 3, that is, the ATM adaptation layer (AAL) protocol type (refer to 4.2.1, etc.) Layer 2 is based on the revised LAPD. The difference from the revised LAPD is described in 6.1.2.

[5945] 6.1.1 Signaling Cell Format

[5946] If an I field is transferred as signalling information, the data length of the LAPD layer 3 (L3) storing I field is 41 octets corresponding to a single segment message (SSM) as shown in FIG. 749. In this case, 4 octets in the 41-octet I field are used for the application of the switch software, and the remaining 37 octets are used as a data field. The 41-octet I field is provided with the information of the LAPD layer 2 (L2), with the information of the AAL type 3, and also with the ATM cell information (refer to FIG. 726).

[5947] If the MSD/MSCN is transferred as signalling information, the data length of the LAPD layer 3 (L3) storing the MSD/MSCN is fixed to 253 octets as shown in FIG. 750. In this case, the 253-octet MSD/MSCN data is provided with the 3-octet LAPD layer 2 (L2), thereby adding up to the 256-octet data. The 256-octet data is divided into 44-octet segments, each segment being provided with the AAL type 3 information, and also with the ATM cell information (refer to FIG. 726). Therefore, the above described 256-octet LAPD data is transferred by six ATM cells. In this case, the valid data length in the payload of the last cell is 44−(6×44−256)=36 octets.

[5948] 6.1.2 Difference from Revised LAPD

[5949] Listed below are the processes unique to the intra-station devices.

[5950] (1) UI frames are used in transferring information. All-0 DLCI is used as an address of the LAPF.

[5951] (2) Signal Priority Control

[5952] A signal from an intra-station device should be provided with a priority level to priority-control from the BSGC the transmission signal to be sent to the switch software executed by the BCPR. The priority level is represented by congestion control bits in the address of the LAPF. FIG. 751 shows the UI format.

[5953] (3) Information Field

[5954] The information field is defined between the BCPR and each device. FIG. 752 defines the common field of each device. In this format, the value of the APID/MESG for each device is centrally managed by the switch software.

[5955] The formats of the simple LAP and full LAPD are different to each other in the following points.

[5956] (a) The maximum message length is 509 bytes for the simple LAP.

[5957] (b) The NS field is fixed to 0 in the full LAPD.

7. BSGC-COM

7.1 Hardware Configuration of BSGC-COM

[5958] FIGS. 753 through 755 are block diagrams showing the functions of the BSGC-COM hardware.

7.2 Explanation of Blocks Showing Functions of BSGC-COM

[5959] FIG. 756 shows the function of the HMX00A package in the BSGC-COM.

[5960] FIG. 757 shows the function of the HMX01A package in the BSGC-COM.

[5961] FIG. 758 shows the function of the HSF00A/HSF04A in the BSGC-COM.

7.3 Switch Interface

[5962] FIG. 759 shows the interface for the signal transferred from the HMX00A package in the BSGC-COM to the SWMDX (HMX03A) package in the ASSWSH (refer to FIG. 167).

[5963] FIG. 760 shows the interface for the signal transferred from the SWMDX (HMX03A) package in the ASSWSH to the HMX00A package in the BSGC-COM.

7.4 SWTIF Interface

[5964] FIGS. 761(a) and 761(b) show the interface of a signal transferred between the HSF04A package in the BSGC-COM and the SWTIF (HNC00A) package in the ASSWSH (refer to part 4).

7.5 Configuration of Higher/Lower Shelf of BSGCSH

[5965] The BSGCSH can daisy-chain up to two shelves. FIG. 762 shows the daisy chain of the BSGCSH.

7.6 BSGC-COM Loopback Configuration

[5966] 7.6.1 Cell Loopback of BSGC and BSGC-COM in INS State

[5967] FIG. 763 shows the configuration of the cell loopback in an INS state for both BSGC and BSGC-COM.

[5968] When a loop is set, the state of a cell enable signal is changed from the gate-stop state to the pass-through state at position A in FIG. 763. FIG. 764 shows the logic of setting the loopback for the loopback configuration shown in FIG. 763.

[5969] 7.6.2 Cell Loopback in OUS State for BSGC and BSGC-COM

[5970] FIG. 765 shows the configuration of the cell loopback in an OUS state for both BSGC and BSGC-COM.

[5971] The loop points are (1) and (2) shown in FIG. 765.

[5972] Control Procedure of Loopback at Loop Point (1)

[5973] When the loopback is set at loop point (1), the state of a cell enable signal is changed from the gate-stop state to the pass-through state at position (1). FIG. 766 shows the logic of setting the loopback for the loopback configuration at loop point (1) shown in FIG. 765.

[5974] For the cell route in the loopback at loop point (1), the upward (BSGC→ASSW) 2/1 cell in the HSF00/04A should be routed toward the test system. FIG. 767 shows the logic of setting a cell route in the loopback at loop point (1).

[5975] FIG. 768 shows the logic of setting the VCC in the loopback at loop point (1).

[5976] Control Procedure of Loopback at Loop Point (2)

[5977] When the loopback is set at loop point (2), the logic of the reset terminal of the CSPC-ADP is set to 1 at position (1). This state is set by the I/O register in the BSGC package. FIG. 769 shows the logic of setting the loopback for the loopback configuration at loop point (2) shown in FIG. 765.

[5978] The cell route in the loopback at loop point (2) is set as in the loopback at loop point (1).

[5979] The logic of setting the VCC in the loopback at loop point (2) is the same as that in the loopback at loop point (1).

8. DUPLEX PROCESS CONTROL

8.1 Hardware Configuration

[5980] 8.1.1 BSGC Hardware Configuration

[5981] FIG. 770 shows the hardware configuration of the BSGC.

[5982] 8.1.2 General Description of the BSGC Hardware

[5983] FIG. 771 shows the outline of the BSGC hardware.

[5984] 8.1.3 Memory Map

[5985] FIG. 772 shows the memory map of the BSGC.

[5986] 8.1.4 I/O Map

[5987] FIG. 773 shows the I/O Map in the BSGC.

9. MAINTENANCE AND OPERATION

[5988] Described below is the maintenance and operation of the BSGCSH.

9.1 Diagnostics Functions

[5989] 9.1.1 Diagnostics Object Items

[5990] The diagnostics object items are listed below.

[5991] (1) INF interface

[5992] i) CC access read/write

[5993] ii) DMA transfer read/write

[5994] (2) Functions in BSGC package: No-function items are deleted from the present SGC diagnostics. Additional functions are entered as (MACH-1.2).

[5995] (All points accessible by the CPU are diagnosed=self-diagnosis)

[5996] (3) between BSGC and SWINF

[5997] i) A loop is set between the BSGC and SWINF and a sending/receiving cell test is conducted.

[5998] (4) VCC memory test: a read/write test of a VCC table memory from the BSGC card of the smallest number.

[5999] (5) BSGCSH: a link establishment test on the LAP to another device

[6000] (6) Cell-by-cell loop test at BSGC-COM using a TCG (refer to 9.2).

[6001] 9.1.2 Details

[6002] Described below are the detailed explanation of each diagnostics item.

[6003] 9.1.2.1 INF Interface→BCPR Access Read/Write Diagnosis

[6004] FIG. 774 shows the BCPR access read/write.

[6005] 9.1.2.2 INF Interface→DMA Transfer Read/Write Diagnosis

[6006] During the DMA transfer test, 1) a command is activated, and concurrently 2) a retry instruction is issued. A command to DMA-write for diagnostics is prepared in the command entered in the BSGC after the activation of the command. The necessary information is (1) an MM transfer address, (2) the number of transferred words, and (3) a transfer data pattern. (1) and (2) are reported directly to the BSGC as being stored in a command. As the data of (3), two patterns are prepared as shown in FIG. 775.

[6007] 9.1.2.3 Diagnostics of Functions in BSGC

[6008] The functions in the BSGC are self-diagnosed.

[6009] 9.1.2.4 Diagnostics between BSGC and BSGC-COM

[6010] The function test is conducted as a single phase of self-diagnosing the BSGC in 9.1.2.3. FIG. 776 shows the position of a loop in the diagnostics between the BSGC and BSGC-COM In FIG. 776, the loop test between the BSGC and BSGC-COM can be the home system BSGC-COM loop test conducted at point (2) and the mate system BSGC-COM loop test conducted at point (3). The loop test at point (1) is a self-loop test of the CARP-LSI.

[6011] 9.1.2.5 VCC Memory Test

[6012] This test is conducted as a single phase of the self-diagnostics in the BSGC. This test phase can only be conducted from the BSGC of the smallest number. This phase can be effective only in the OUS state of the BSGC-COM of either #0 or #1 system. Therefore, the OUS/active/standby information of the BSGC-COM (ASSW) should be reported before starting the test. Before starting this test, the VCC selector compulsory selection register should compulsorily route the output of the 2-1 selector, located before the VCC, toward the test BSGC. FIG. 777 shows the state of the VCC read/write test entered when the #1 system BSGC is making the diagnostics in the OUS state.

[6013] 9.1.2.6 LAP Link Establishment Test between BSGC and another Device

[6014] A command is prepared to compulsorily route the output of the standby system BSGC-COM selector (for selecting a BSGC signal) toward the diagnostics performing BSGC.

[6015] <Test Method>

[6016] The test is conducted in accordance with the inter-device LAP link establishment procedure to be followed by the device control software. Accordingly, no special diagnostics LAP link establishment program is prepared for the BSGC.

9.2 TC Function

[6017] Described below are the functions of the BSGCSH in the continuity test using the TCG.

[6018] 9.2.1 Basic Policy

[6019] FIG. 778 shows the basic policy of the continuity test in the BSGCSH in the active system/standby system/OUS state.

[6020] 9.2.2 Cell-by-Cell Loopback (OUS state)

[6021] There are two systems as follows.

[6022] (1) The process is realized in the BSGC-COM. The loopback point is located as having a transmission speed for the BSGC. That is, no loopback is made under the transmission speed of 622 Mbps. The loopback requires the following conditions (refer to FIG. 782).

[6023] <Condition>

[6024] (a) The cell-by-cell loopback is performed by the SEL N-1 LSI using the AHM.

[6025] (b) The cell-by-cell loopback has the only function of determining the 0 bit of the tag for loopback.

[6026] (c) The tag (TCGBSGCSH) of a test cell (TC) is the same as that used in the standby system duplex device so that it is not dropped in the standby system BSGC-COM.

[6027] (2) The loopback is not realized in the BSGC.

[6028] The output of the BSGC-ASSW direction selector in the standby system BSGC-COM should be compulsorily directed to the standby system BSGC. If a cell is being transmitted from the standby system BSGC, the cell of the duplex device at the standby unit is stopped in the active system BSGC and the loopback is not realized in the BSGC.

[6029] 9.2.3 Cell-by-Cell Loopback Position

[6030] FIG. 779 indicates the position of the cell-by-cell loopback in the BSGC-COM. The loopback position is set in BSGC units (that is, DMUX units).

[6031] 9.2.4 TC Stop Function in Active System BSGC During OUS Test

[6032] FIG. 780 shows the hardware configuration for the TC stop function in the active system BSGC during the OUS test.

[6033] The BSGC is loaded with an MUX to receive cells from both active and standby systems. When one system is in an OUS state, the test cell (TC) from the standby system ASSW should not be received by the active system BSGC. Therefore, the cell from the BSGC-COM, which is in the OUS state before the input into the MUX, is stopped.

[6034] Cells are stopped by setting the I/O register in the active system BSGC.

[6035] FIG. 781 shows the transmission signalling route from the BSGC to the duplex device or simplex device.

[6036] FIG. 782 shows the reception signalling route and test cell route from the duplex device or simplex device to the BSGC.

[6037] [0014]

[6038] <part 8>

[6039] Described in part 8 are the configuration and the function, etc. relating to the present invention.

[6040] FIG. 783 shows the protocol data unit (L2-PDU and L3-PDU) of layers 2 and 3 related to the system of the present embodiment.

[6041] The L3-PDU (described later for the detailed format) contains the destination address DA and source address SA. When the L3-PDU is transmitted, the destination is determined by the destination address DA. Then, a variable length data is stored after the header field.

[6042] If the L3-PDU is transferred in the SMDS over the ATM switching network (ASSW) shown in FIG. 8. it should be converted into a 53-byte-based cell format. At this time, the L3-PDU is converted into the L2-PDU. When the L2-PDU is generated from the L3-PDU, the L2-PDU is decomposed into a BOM cell, COM cell, and EOM cell as described above. (When the L3-PDU is converted into a single L2-PDU, it is output as an SSM.)

[6043] The L2-PDU shown in FIG. 783 is an example of a BOM cell. The leading 5 bytes of a BOM is a header field containing routing information, etc. The detailed description is given above. The 2 bytes preceded by the header field stores a segment type ST, sequence number SN, and message identifier MID (or a multiplex identifier).

[6044] The segment type ST is a 2-bit field and indicates the BOM, COM, EOM, and SSM. The sequence number SN is a serial number assigned to a transferred cell for convenience in detecting the cell if it is lost or mistakenly inserted. A message identifier MID is a 10-bit field and identifies the L3-PDU for each SNI. Therefore, the same message identifier MID is assigned to a plurality of L2-PDUs generated from a single L3-PDU. The message identifier MID is not used double for each SNI. In the system of the present embodiment, up to 16 message identifiers MID can be assigned to each SNI.

[6045] The above described information is followed by a 44-byte user information field (payload). The user information field stores the destination address DA and source address SA of the L3-PDU for the BOM or COM. The user information field is further followed by an information length indicator (LI) and cyclic symbol check CRC. The information length indicator LI is a bit indicating the valid information of a cell. For example, the BOM and COM are represented by 44 bits, and the length of the EOM and SSM depends on the cell.

[6046] Described below is the routing process. The routing process is realized by the SBMH (SBMESH) described in part 5 and the GWMH (GWMESH) described in part 6.

[6047] The SBMESH (or GWMESH) generates a table from which tag information and output MID is retrieved to be assigned to a cell using the MID (input MID) of an input cell as a key as shown in FIG. 784 (in the case of the system of the ASSW as shown in FIG. 8, an input cell is input to the SBMESH in an ATM cell format and processed as an L2-PDU in the SBMESH. For simplicity, both are referred to as cells). The method of generating the table and the routing process using the table are described by referring to the flowchart shown in FIG. 785.

[6048] If a cell is input to the SBMESH (or GWMESH), the segment type ST of the cell is checked in step S10. If the input cell refers to a BOM, then the destination address DA of the L3-PDU stored in the payload field of the BOM is extracted and the route to the destination is determined according to the DA in step S11. Actually, a PVC is preliminarily set between the SBMESH and the destination, and the tag information stored for the DA is retrieved. The tag information is 2-byte information containing tags A, B, and C as shown in FIG. 420.

[6049] In step S12, an output MID is acquired. The output MID is determined such that it is not defined double in the message handler at the destination. Refer to (29) in chapters 3 and 4 in part 5 for details. In step S13, the acquired tag information and output MID is assigned to the above described BOM and output. In step S14, a table storing the retrieved tag information and output MID is generated using the MID (input MID) assigned to the BOM at the input as a key.

[6050] In step S10, if an input cell refers to an SSM, the processes in steps S21 through S23 are performed. The processes in steps S21 through S23 are the same as those in steps S11 through S13. Then, an output MID is released in step S24.

[6051] In step S10, if an input cell refers to a COD, the above described table is retrieved in step S31 using the input MID of the COM as a key. Then, in step S32, the tag information and output MID retrieved from the table are assigned to the COM and output.

[6052] In step S10, if an input cell refers to an EOM, the tag information and output MID retrieved from the table are assigned to the EOM and output in steps S41 and S42 as in the case of the COM. Then, the output MID is released in step S43.

[6053] Thus, the routing process is performed for the BOM and SSM using the DA of the L3-PDU stored in the payload field. For the COM and EOM, routing information is retrieved using the same message identifier MID set for a plurality of cells obtained from a single L3-PDU. Thus, the routing process is performed in cell units on cells of any segment type. Thus, the routing process is performed in L2-PDU units without assembling L3-PDUs.

[6054] Described below is the collection of error log.

[6055] In the system according to the present embodiment, error log is collected in L2-PDU units (cell units). The error log is collected by the SBMESH (or GWMESH).

[6056] The SBMESH (or GWMESH) has a table (RAM) using MIDs and SNI numbers as keys (addresses). The table generating method is basically the same as the method of generating the above described table. The error log collection table stores destination addresses DA and source addresses SA of the L3-PDU using input MIDs and SNI numbers as keys.

[6057] As described above, an input MID is assigned such that it is not assigned double in a single SNI. Therefore, MIDs can be identified even if a plurality of users exist in a single SNI and the users simultaneously transmit data. However, since the SBMESH of this embodiment contains a plurality of SNIs (up to 32 SNIs) and SNI numbers; should be identified to identify all L3-PDUs. In this system, the SNI number is identified by the VCI as shown in FIG. 217.

[6058] When an NG is detected as a result of an error log object check, the above described table is searched using the input MID and SNI number of the L2-PDU as keys regardless of the segment type of the L2-PDU. Thus, the DA and SA of the L3-PEIU corresponding to the L2-PDU are obtained and those associated with errors are stored together with the SNIE number and error type in the interface register for the software.

[6059] The error log is collected by the following triggers.

[6060] (a) After setting each parameter in the above described interface register, an interruption is generated in the software. The software starts collecting the log through the interruption.

[6061] (b) After setting each parameter in the above described interface register, the flag for the software is set ON. The software constantly monitors (looks in) the flag, and starts collecting the log when the flag is set ON.

[6062] (c) Error type 0 does not refer to any specific error type. The software constantly monitors the error type field of the above described interface register, and the field starts collecting the log when the field is not 0 (in this case, the parameter for the error type is set last of all).

[6063] In collecting the log by any of the methods (a) through (c), the software clears the interface register after collecting the log (if (b) above is adopted, the flag is set OFF). Thus, a series of log collecting operation is completed.

[6064] In the descriptions above, only one type of error log parameter can be set in the interface register at a specific timing. If the register is provided with the FIFO of the depth calculated according to the throughput of the software and error occurrence rate, plural types of error log parameters are set simultaneously to collect error log.

[6065] In the above listed methods, the table requires a large capacity to store SAs and DAs. That is, the MID is 10-bit information and another 10 bits are reserved for the SNI number. Therefore, the combination of a MID and an SNI requires a total of 20 bits. The 20-bit addresses amount to 2²⁰=1 megabytes. The DA and SA are 64 bits each. If the combination of a MID and an SNI number is used as a key to the table, the capacity of the RAM for the table is undesirably large.

[6066] Therefore, in the present embodiment, the number of L3-PDUs simultaneously transmitted in any SNI (number of MIDs for each SNI) is defined as up to 16. That is, 10 bits are assigned to an MID field. According to the above mentioned definition, each L3-PDU transmitted simultaneously in any SNI can be identified by 4 bits.

[6067] As a result, the address of 2²⁰=1N for the combination of the MID and SNI can be reduced to 2¹⁴=16K according to this method. In the conversion above, a pattern matcher (conversion table) for the MID and SNI number is used to calculate where in the SNI the 10-bit MID is located (as described above, up to 16 MIDs are simultaneously allowed in each SNI, and the MID is one of the first through the 16th MID).

[6068] In the processes preceded bDy the above described conversion process, the error log collection is performed as described above.

[6069] In this method, a table (RAM) is provided to store DAs and SAs. When an NG is detected as a result of the error log object check, the DA and SA are read from the table and stored in the interface register for the software together with the SNI number and error type.

[6070] On the other hand, the table can be an interface to the software with the DA and SA table storing SNI numbers and error types. That is, the DA and SA of the BOM are stored in the table using the MID and SNI number of the BOM (or the values converted as described above) as an address each tome a BOM arrives. When an NG is detected as a result of the error log object check, the SNI number and error type are written to the table using the MID and SNI number of the L2-PDU as a key (address) for an L2-PDU of every segment type.

[6071] The log collection trigger of the software is effective to any of (a) through (c) above. (c) is most appropriate.

[6072] Thus, in the error log collection method of the present embodiment, error information generated for each L2-PDU can be collected in L3-PDU units without converting into L3-PDU. Furthermore, the capacity of the table required for collecting error log is reduced considerably by performing a predetermined conversion on the combination of an MID and SNI number.

[6073] Described below is the inter-station loopback test to be conducted from a subscriber terminal unit.

[6074] This test is conducted to confirm by the subscriber the quality and normality of the transmission line between predetermined switching station in the network. The outline of the test method is described by referring to FIG. 786. Conducted in this example is the test of the transmission line from subscriber terminal 2 to SW stations 3 and 6 accommodating the subscriber terminal unit 2 in FIG. 786.

[6075] First, a test start request packet is issued from subscriber terminal unit 2 to SW station 3. The test start request packet has a header field whose specific ID indicates a test start request to discriminate it from a packet for transmitting normal data. Practically, a specific test request DA is set.

[6076] When SW station 3 receives the above described test start request packet, it generates a test packet and outputs it to SW station 6. At this time, the destination address DS of the test packet indicates SW station 6, and the source address SA indicates SW station 3. The test packet arrives at SW station 6 through SW stations 4 and 5. SW station 6 exchanges the DA and SA of the test packet and returns the packet to SW 3.

[6077] SW station 3 receives the test packet and collects the test result. That is, SW station 3 (source station) writes the time to the payload field when the test packet is generated, and SW station 6 (destination station) writes to the payload field when the test packet is received. Accordingly, if SW 3 receives the returned test packet, it can be confirmed that the data have been transmitted through the transmission line between SW stations 3 and 6, and the transmission time (transmission delay) can also be informed of. SW station 3 notifies the customer terminal unit 2 of the test result. Thus, the subscriber tests the predetermined transmission line and is informed of the result.

[6078] The above described test method is described in detail by referring to FIG. 787. A customer premise's equipment (CPE) 10 corresponds to the customer terminal unit 2. A customer line control connection less server (CLS-SU) 20 and trunk control connectionless server (CLS-TRK) 30 are, for example, servers provided in SW station 3 shown in FIG. 786. A call processor (CPR) 40 is a processor accessed by the server.

[6079] When the test is activated, a test start request message packet is generated by a loopback test control unit 11 in the CPE 10, and the request packet is transferred as a common user packet over the network. The telephone number (DA) set in the level 3 header field in the test start request message packet is a spacial telephone number (specific DA) defined between the control unit and the network.

[6080] The test start request message packet is terminated by an L3 header analyzing unit 21 in the CLS-SUB 20. The L3 header analyzing unit 21 analyzes the header field of the received packet and determines whether or not the DA of the packet refers to the above described specific DA. Unless it is the specific DA, the packet is processed as a common user packet in a normal routing process. If it is the specific DA, the received cell is recognized as a test start request message packet and transmitted to a specific packet control unit 22 in the CLU-SUB 20.

[6081] The payload field of the test start request message packet stores the ID of the subscriber, station number of the loopback terminal station, time stamp, etc. The CLU-SUB 20 transmits these data to the CPR 40. According to the information, the CPR 40 transfers the test start request t the CLS-TRK 30 in the procedure followed in activating the inter-station loopback test so as to activate the intra-station loopback test from the subscriber.

[6082] When the CLS-TRK 30 receives the above described test start request, a packet generating unit 31 generates a test packet and outputs it. The DA of the test packet is the number of the loopback terminal station stored in the test start request message packet. The SA of the test packet is the value of the ID of the CLS-TRK 30 or the CPE 10.

[6083] The loopback terminal station has the server similar to the CLS-TRK 30. When the CLS-TRK 30 of the terminal station receives a test packet, and realizes the DA of the test packet as the station itself, it exchanges the DA with the SA in an DA/SA inverting unit 32. It also writes to the test packet the time when the CLS-TRK 30 of the destination station received the test packet. Then, it is indicated (backward line indicator) that the loopback process has been performed in the terminal station. After these processes, the test packet is output to the SA set by the exchange of the DA and SA.

[6084] The subscriber is reported as follows when a test packet is looped back at the terminal station. That is, if the CLS-TRK 30 shown in FIG. 787 receives a test packet, it recognizes on the backward line indicator that the packet has been looped back, and notifies the CPR 40 of the test result (delay time, etc.) by transferring the contents of the test packet to the CPR 40. The CPR 40 analyzes the contents of the packet, selects the CLS-SUB accommodating the corresponding subscriber, and issues a test result notification packet issue request. When the CLU-SUB 20 receives the request, it generates a test result notification packet and sends it to the CPE 10. The SA set for the test result notification packet is a special telephone number (specific SA) defined over the network, and is recognized by the loopback test control unit 11 of the CPE 10. Thus, the test information is extracted. The test result notification packet stores the delay time as the test result.

[6085] In the above described procedure, the determination of the test packet is made at a specific DA. The necessary data is stored in another field portion in the header of level 3, and the determination can be made according to the data. If the test packet is not returned to the CLS-TRK 30 within a predetermined time after the CPE 10 issued the test start request, a packet indicating the packet transmission is not in a normal state can be generated and it can be reported to the CPE 10.

[6086] Furthermore, the above described test method can be applied to the connectionless communications using the SMDS. In this case, the CLU-SUB 20 and the CLS-TRK 30 are realized by the SMDS processing server, and a specific identifier, instead of the specific DA, can be set in the header field of the L2-PDU.

[6087] Described below is the method of testing the PVC set in the connectionless communications system using the SMDS.

[6088] First, the range of the influence of the fault of an optional PVC is shown by referring to FIG. 899 showing the prior art technology. The PVC is classified into 3 types as follows.

[6089] 1. Source SMDS subscriber (a)(b)—SMDS support module S (PVC 1, 2)

[6090] 2. SMDS support module S—SMDS support module R (PVC 3)

[6091] 3. SMDS support module R—SMDS subscriber (x)(y) (PVC 4, 5)

[6092] When a fault occurs in the PVC of 1, the source SMDS subscribers (a) and (b) cannot communicate with any destination SMDS subscriber. No communications can be set between the source SMDS subscribers (a) and (b).

[6093] If a fault occurs in the PVC of 2, no source SMDS subscribers accommodated in the SMDS support module S at the source of the PVC can communicate with any destination SMDS subscriber accommodated in the SMDS support module R at the destination of the PVC. That is, the source SMDS subscribers (a) and (b) cannot communicate with the destination SMDS subscribers (x) and (y).

[6094] If a fault occurs in the PVC of 3, no source SMDS subscriber can communicate with any destination SMDS subscriber. For example, if a fault occurs in PVC 4, no subscriber can communicate with any destination SMDS subscriber (x).

[6095] The PVC can be validated as follows.

[6096] (1) The validation is triggered by a subscriber complaint (request or complaint).

[6097] (2) The validation is periodically performed to prevent mixed faults.

[6098] In the case of (2) above, the validation 1 through 3 should be automatically performed.

[6099] In the case of (1) above, the faulty point can be presumed by analyzing the complaint. After the presumption, a suspect PVC is validated. FIG. 788 shows the algorithm.

[6100] When a complaint occurs from a subscriber, it is checked in step S1 whether or not the complaint has come from a single source SMDS subscriber. If the complaint has come from a plurality of subscribers, it is checked in step S2 whether or not the contents of the complaint refer to the incapable communications to a single destination SMDS subscriber. If “yes” in step S2, the fault is considered to have resulted from the PVC of 3 above. If “no” in step S2, then the fault is considered to have resulted from the PVC of 2 above.

[6101] In step S1, if the complaint has come from a single source SMDS subscriber, it is checked in step S3 whether or not the complaint refers to the incapable communications to any destination SMDS subscriber. If “yes” in step S3, the fault of 1 above is determined. If “no” in step S3, it is checked in step S4 whether or not the contents of the complaint refer to the incapable communications to a single destination SMDS subscriber. If “yes” in step S2, the fault of the PVC of 3 above is determined. If “no” in step S2, the fault of the PVC of 2 above is determined.

[6102] Thus, if the complaint has come from the subscriber, then the complaint is analyzed, the faulty portion is detected, and the PVC test explained below is conducted, thereby reducing the recovery time.

[6103] The above mentioned algorithm of analyzing a fault can be performed manually, but can also be automatically analyzed by entering the complaint in the system. In this case, a validation process can be automatically performed based on the analysis result.

[6104] In the PVC validation method, a test message is transmitted to a PVC to be tested to confirm the matching between the received message and transmitted message. For example, to verify the PVC between the source SMDS subscriber (a) and SMDS support module S shown in FIG. 899, the test message generator and test message checker should be provided in respectively the source SMDS subscriber (a) and SMDS support module S. Thus, a test message can be sent and received for validation. To validate the PVC between the SMDS support module R and the destination SNDS subscriber (x), the test message checker and test message generator should be provided in respectively the destination SMDS subscriber (x) and SMDS support module R. Thus, a test message can be sent and received for validation.

[6105] However, since these method requires the test message generator and test message checker for each SMDS subscriber, the system according to the present embodiment has the following configuration.

[6106] FIG. 789 shows the system configuration using the SMDS. The configuration is the same as that of the prior art shown in FIG. 899. In FIG. 899, the SMDS subscribers are described as source and destination subscribers. Actually, there are no source-exclusive subscribers or destination-exclusive subscribers. Subscribers (a) and (b) can be destination SNDS subscribers for the SMDS support module. Subscribers (x) and (y) can also be source SMDS subscribers. Therefore, the configuration shown in FIG. 899 is the same at that shown in FIG. 789.

[6107] To validate the PVC between 1 and 3 above, that is, to validate the fault in the PVC between the SMDS subscriber and SMDS support module, the test message generating unit (test message generator) and a test message check unit (test message checker) are provided in the SMDS support module. Thus, the test message generating unit and test message check unit can be centrally managed, thereby reducing the entire cost.

[6108] A test message loopback function is provided at the terminal to the SMDS subscriber. This function is realized by the following two processes.

[6109] A test message is determined by the VPI/VCI and only the test message is looped back.

[6110] All input messages are looped back.

[6111] If an SMDS subscriber shown in FIG. 789 is actually an SMDS-exclusive subscriber, the loopback can be performed by the latter method. If the SMDS subscriber processes normal ATM cell data in addition to the SMDS, then the former method is recommendable. Since the SMDS message and ATM cell data have different VPIs/VCIs, an SMDS message can be selectively looped back. A service can be continued for the ATM cell data during the validation, and totally improved services can be provided.

[6112] The following two processes can be performed to loopback messages at the terminal to the SMDS subscriber.

[6113] The SMDS subscriber sets the loopback.

[6114] The SMDS subscriber can a loopback instruction from the system (the terminal at the SW).

[6115] FIG. 790 shows the test image of the PVC of 1 above (with the source SMDS subscriber (a)). FIG. 791 shows the test image of the PVC of 3 above (with the destination SMDS subscriber (x)). (A test message appears along the bold line shown in FIG. 791.)

[6116] The tests are conducted according to the same method. That is, a test message generating unit is provided in the SMDS support module R, and the test message generated in the module is transmitted to the SMDS subscriber along the route represented by the bold line shown in FIG. 791. Then, the message is returned to the SMDS support module S along the route represented by the bold line shown in FIG. 791 after being looped back by the SMDS subscriber, and is checked by the test message check unit provided in the module S.

[6117] As shown in FIG. 792, there are two positions where a test message is multiplexed into normal SMDS messages in the SMDS support module R. One method is, as shown in FIG. 792(a), to multiplex the test message to a normal SMDS message and check it in various processes. Another method is, as shown in FIG. 792(b), to multiplex the message during the checks. If the PVC tests are performed exclusively, these methods are not discriminated from each other. However, if the method shown in FIG. 792(a) is adopted, the internal test of the SMDS support module R can be desirably conducted.

[6118] The following three multiplexing methods are shown in FIG. 792.

[6119] simply selecting a normal SMDS message and a test message

[6120] detecting an idle timing of a normal SMDS message in a multiplexing block, reporting the timing to the test message generating unit, and instructing the transmission of the test message.

[6121] The test message generating unit simply transmits a test message, buffers it in the multiplexing block, detects the idle timing of the normal SMDS message, and multiplexes the message.

[6122] In the first method, only a test message is transmitted during the test and a normal SMDS message cannot be transmitted. Therefore, it undesirably influences the subscribers other than the test objects. In the second and third methods, a normal SMDS messages are sent from the subscribers other than the test objects, and a test message can be transmitted during the idle time.

[6123] There are also plural points where a test message is separated from normal SMDS message in the SMDS support module S. As shown in FIG. 793(a), a test message check unit is provided immediately after the reception of the test message. In the method shown in FIG. 793(b), the test message is separated from the normal SMDS message after various checks, and then the message is checked. (Additionally the message can be demultiplexed during the DA analysis, various checks, etc.)

[6124] In this case, if the PVC tests are performed exclusively, these methods are not discriminated from each other. However, if the method shown in FIG. 793(b) is adopted, the internal test of the SMDS support module S can be desirably conducted. The test message checker has the function of fetching only the message having the test object PVC /VCI.

[6125] As described above, in the PVC test of 1 and 3 above, the SMDS support module R comprises a test message generating unit, and the SMDS support module S comprises a test message checker.

[6126] To test the PVC of 2 above, that is, to test the PVC between the SMDS support modules, the SMDS support module S comprises a test message generator and the SMDS support module R comprises a test message checker. FIG. 794 shows the test image. A test message is transmitted along the bold line shown in FIG. 794.

[6127] The multiplexing portion for a test message in the SMDS support module S and the demultiplexing portion for a test message in the SMDS support module R are similar to those shown in the configuration according to FIGS. 793 and 794. In any method, if the PVC tests are performed exclusively, these methods are not discriminated from each other. However, if the message is multiplexed before each check and demultiplexed after each check, the internal test of the SMDS support module can be desirably conducted.

[6128] Assuming that, as shown in FIG. 795, the test message in testing the PVC of 1 and 3 above is multiplexed before each check and the test message in testing the PVC of 2 above is demultiplexed after each check in the SMDS support module R. In this case, the test message generating unit and checker provided for a PVC test can realize the testing of the functions of various checks in and for the home module. This holds true with the SMDS support module S.

[6129] Described below is a more practical test method.

[6130] In any of the tests of the PVC in 1 through 3 above, a test message is prepared in the test message generating unit as a test start instruction. The VPI/VCI for the test PVC is added to the test message and then transmitted. (Otherwise, when a test message is prepared, the VPI/VCI for the test PVC is written as a part of the test message. In this case, the test message is transmitted at the start of the test.)

[6131] A test message is transmitted through the test PVC and enters the test message checker. (As described above, the test message checker is assigned the VPI/VCI for the test PVC so that only a message having the VPI/VCI may be entered and accumulated.) According to the test start instruction, test messages accumulated in the test message checker are read and checked for their contents after a predetermined time period (longer than the time logically required for the test message to arrive at the test message checker from the test message generating unit). (The accumulating unit in the test message checker is cleared before the start of the test.)

[6132] The number of the test messages can be only one, but is commonly plural. (The physical restriction defines the limit of the number.) In this case, the PVC test checks the number of test messages and the contents of the messages.

[6133] In the PVC test of 1 and 3 above, the SMDS subscriber for the test PVC follows the loopback mode. Assume that a message arrives from an SMDS subscriber at the SMDS subscriber for the test PVC in this mode.

[6134] In the above described method of simply selecting a test message and a normal message, all normal SMDS messages are discarded. Therefore, the SMDS message is not transmitted to the SMDS subscriber for the test PVC, causing no trouble in the test. However, in the method of inserting a test message at an idle timing of normal messages, the SMDS message is transmitted to the SMDS subscriber for the test PVC. The VPI/VCI is the same as that for the test PVC, and cannot distinguished from the test message.

[6135] The following two countermeasures can be taken.

[6136] The first method is to recognize the VPI/VCI for the test PVC in the multiplexing unit, check the VPI/VCI of the normal SMDS message, and discard the message when it has the VPI/VCI for the test PVC is received.

[6137] The second method is to preliminarily assign identification information, etc. to the test message without taking any hardware process, and make a determination when it is read by the test message checker. The second method is described below in detail.

[6138] If only one test message is assumed in the test method, determination is made as to whether or not a single message is accumulated in the test message checker.

[6139] If there is no message accumulated, the test is recognized as NG.

[6140] If there is one test message, it is read and determined whether or not it refers to a test message. If it is a test message, its contents are checked whether they are OK or NG. If the message is not a test message, a test retrial is made. To prevent infinite retrial, there is an algorithm prepared to determine no more tests after a predetermined number of retrials.

[6141] If n test messages are assumed in the test method, the test message checker first determines whether or not n messages have been accumulated in the test message checker.

[6142] If then umber is smaller than n, the test is determined as NG.

[6143] If the number is n, the first message is read to be determined whether or not it refers to a test message. If so, its contents are checked and determined whether they are OK or NG. If NG, the entire test result is determined as NG. If OK, the second message is processed similarly. If the first message is not a test message, the second message is processed immediately.

[6144] Thus, the process is repeated for n determinations. If m test messages are received (m≦n) and their contents are completely OK, the entire test result is recognized as OK. If the number of test messages in the above mentioned number n is smaller than a predetermined number m (m can be optionally set), then a retrial is made. To prevent infinite retrial, there is an algorithm prepared to determine no more tests after a predetermined number of retrials.

[6145] This method can be applied to the test of the PVC of 2 above.

[6146] Described below are the BE tag and BAsize check of layer 3 to be confirmed for the normality of the SMDS data, and the length check of layer 2. These checks are made in the SBMESH (or GWMESH) according to the present embodiment.

[6147] FIG. 796 shows the format of the L3-PDU. As shown in FIG. 796, the leading Rsvd field of the L3-PDU is a 1-octet area provided to define the format (not currently used). The BEtag field is 1-octet information to be compared with the BE tag written to the trailer of the L3-PDU. If a matching result is confirmed at a receiving terminal, the data is recognized as normal. The BAsize field is a 1-octet information notifying the data receiving unit of the buffer size. The DA and SA fields are assigned 8 octets each. The data after the SA field before the Info field is not related to the present embodiment.

[6148] The Info field is an area storing actual transfer data. It is variable and up to 9,188 octets. The Rsvd, BEtag, and Length fields in the trailer store the same information as the Rsvd, BEtag, and BAsize fields stored at the head of the L3-PDU.

[6149] The correlation between the L2-PDU and L3-PDU is explained by referring to FIG. 797. As shown in FIG. 797, the BAsize of the L3-PDU can be obtained by subtracting the leading 4 octets of the L3-PDU (Rsvd, BEtag, and BAsize fields) and 4 octets of the trailer (Rsvd, BEtag, and Length fields) from the total length of the L3-PDU. The length of the payload length is obtained by subtracting 7 octets of the header and 2 octets of the trailer from the total length (53 bytes) of the L2-PDU. The length of the payload of the L2-PDU refers to the valid length of the payload. Therefore, the length of the payload of the BOM and COM is 44 octets, but the length of the payload of the EOM and SSM is variable.

[6150] Assuming that the BAsize of the L3-PDU is 100, the conversion of the L3-PDU into the L2-PDU is described below.

[6151] The L2-PDU BOM stores 44 octets containing a part of the header and information fields of the L3-PDU. The L2-PDU COM stores 44 octets containing the information field of the L3-PDU. The L2-PDU EOM stores 20 octets containing data in the information field and trailer field of the L3-PDU. Therefore, the valid payload length of the L2-PDU EOM is 20 octets.

[6152] Described below are the three checks to be made according to the present embodiment. These checks are controlled under the restriction that an error is allowed only at the SSM and EOM, and that the BAsize and BEtag are not NG when the result of the L2 payload length check is NG.

[6153] The three following checks are made according to the present embodiment.

[6154] 1. L2-PDU payload length check at SSM and EOM

[6155] 2. L3-PDU EBtag check

[6156] 3. L3-PDU BAsize check

[6157] Before explaining these checks, the data format is explained briefly. The L3-PDU has the format shown in FIG. 796 as described above. The length of the L3-PDU is represented by octets of a multiple of 4. At this time, it is indicated which part of the L3-PDU data divided into the L2-PDU segment types is put in the segment unit of the L2-PDU. The sum of the SNI and MID is referred to as an RMID.

[6158] (1) L2-PDU Payload Length Check at SSM and EOM (FIG. 798)

[6159] In this check, a predetermined value is subtracted from the BAsize of the L3-PDU for each of the BOM, COM, and EOM (or SSM). Then the BAsize is compared with the valid payload length of the EOM (or SSM), and the normality of the data is confirmed according to a matching result.

[6160] First, the BAsize of the L3-PDU format is extracted. The BAsize is stored in the received BOM, and then stored in the table using the RMID of the BOM as a key (address). The BAsize is then retrieved to subtract 9 from the BAsize value and write the balance to the table again. (When a BOM is received, 36 octets are actually subtracted. However, since the length of the L3-PDU is represented by octets of a multiple of 4, all values including the BAsize are represented in the format using the divisor of 4 for simplicity of calculation as described above.

[6161] If the COM is received and it is assigned the same RMID as the above described BOM, data is read from the table according to the RMID as a key. Then, 11 is subtracted from the read value, and the balance is written again to the table. If there are a plurality of COMs, the process is repeatedly performed.

[6162] If the EOM is received and it is assigned the same RMID as the above described BOM, data is read from the table according to the RMID as a key. If the value is 0, or if the value does not match the valid payload length of the EOM, it indicates an error. If the values match each other, it indicates that the L2-PDU payload is normal.

[6163] Important Points of the Process

[6164] A count value may not match the L2-PDU payload length if, for example, one L2-PDU is lost. If an L2-PDU is lost, the BAsize is not counted down. In this case, the error flag indicates NG only for the L2 length. The L3-PDU BEtag check or the L3-PDU BAsize check does not indicate NG. This holds true when the L2-PDU has increased for any reason.

[6165] The subtraction process using the counter can be performed through the operation circuit. Since the data length is represented by a multiple of 4, 44, 36, and 32 can replace 11, 9, and 8 respectively for simplified operations.

[6166] (2) L2-PDU BEtag (FIG. 799)

[6167] In this check, the BEtags of the header is compared with the trailer in the L3-PDU to monitor the transmission or data by checking the comparison result.

[6168] When a BOM is received, the BEtag of the header field of the L3-PDU stored in the payload is retrieved. The BEtag is stored in the RAM using the RMID of the BOM as a key. No process is performed when a COM is received. When an EOM is received, data is read from the RAM using the RMID of the EOM as a key to compare the read BEtag with the BEtag of the trailer of the L3-PDU stored in the payload of the EOM. If the comparison outputs a matching result, it is determined that the SMDS data is normally transmitted. If the comparison outputs a non-matching result, it indicates abnormal transmission.

[6169] When an SSM is received, the BEtag of the header field of the L3-PDU stored in the SSM payload is compared with the BEtag of the trailer of the L3-PDU.

[6170] (3) L3-PDU BAsize Check (FIG. 800)

[6171] In this check, the BAsize of the header is compared with the LENGTH of the trailer in the L3-PDU to monitor the data transmission by checking the comparison result.

[6172] When a BOM is received, the BAsize of the L3-PDU stored in the payload is retrieved. The BAsize is stored in the RAM using the RMID of the BOM as a key. No process is performed when a COM is received. When an EOM is received, data is read from the RAM using the RMID of the EOM as a key to compare the read BEsize with the LENGTH of the L3-PDU stored in the payload of the EOM. If the comparison outputs a matching result, it is determined that the SMDS data is normally transmitted. If the comparison outputs a non-matching result, it indicates abnormal transmission.

[6173] When an SSM is received, the BAsize of the L3-PDU stored in the SSM payload is compared with the LENGTH of the L3-PDU.

[6174] FIG. 801 is a block diagram showing the above described checks.

[6175] When the L2-PDU is received as SMDS data, a segment type detecting unit 1 recognizes it as a BOM, COM, EOM, or SSM. Simultaneously, a RAM address generating unit 2 obtains an RMID from the SNI and MID of the L2-PDU and sets the value as an access address to a RAM 10.

[6176] The BEtag, BAsize (LENGTH), and L2-Payload-LENGTH are respectively detected by a BEtag detecting unit 3, a BSsize detecting unit 4, and an L2-LENGTH detecting unit 5. The detected values are written at an address generated by the RAM address generating unit 2 in the RAM 10. A down counter 6 performs a predetermined operation (subtraction) on the value read from the RAM 10, and the calculation result is rewritten to the RAM 10. A BEtag comparing unit 7, BAsize comparing unit 8, and L2-LENGTH comparing unit 9 perform the above described comparing operations and output the results.

[6177] Described below is the system connected via a private line to a connectionless data processing server.

[6178] FIG. 802 shows the system configuration according to the present embodiment. In FIG. 802, SW 1-1-1-4 are switches realized by ATM switches. CPR 2-1-2-4 are call processors. CLS 3-1-3-4 are connectionless process servers. CPR 2-1-2-4 and CLS 3-1-3-4 perform various processes while communicating information. A private line 5 can be, for example, a high-speed bus.

[6179] In FIG. 802, subscriber 1 accommodated in SW 1-1 through subscriber 4 accommodated in SW 1-4 indicate a route through which data is transferred in connectionless communications. In this case, the connectionless data output from subscriber 1 is transferred to CLS 3-1 through SW 1-1. The transfer is made through, for example, the PVC. CLS 3-1 interprets a message, determines a call type, etc. in collaboration with CPR 2-1. When it realizes that the call communications mode refers to connectionless communications and the destination is subscriber 4 connected to CLS 3-4, the connectionless data is transferred to CLS 3-4 through the private line 5. Thus, the data is transmitted from CLS 3-4 to subscriber 4 through SW 1-4.

[6180] As described above, the connectionless data is transferred between the CLSs via a private line without switching by the SW.

[6181] FIG. 803 is a block diagram showing the CPR and CLS. A CPR 10 comprises a message interpreting device 11, call type determining device 12, and subscriber data device 13. A CLS 20 comprises an address determining device 21, home CLS data management device 22, and mate CLS data management device 23. FIG. 804(a) shows an example of a table managed by the home CLS data management device 22. FIG. 804(b) shows an example of a table managed by the mate CLS data management device 23. The routing operations of the CPR 10 and CLS 20 are described by referring to the flowchart shown in FIG. 805. In this example, the switch is an ATM switch, and the connectionless communications system is SMDS.

[6182] When a message is received from the switch, it is interpreted in step S1. This is performed by the message interpreting device 11 in the CPR 10. Then, it is determined in step S2 whether or not the received message is in the connectionless service. In the determination, the call type determining device 12 searches the subscriber data device 13 and checks whether or not the calling subscriber is entered in the subscriber data device 13 as a connectionless service subscriber, or checks that the VPI/VCI of the message refers to an SMDS cell.

[6183] In a connection service, the process is performed in step S3. In a connectionless service, the management data for the CLS 20 is retrieved in step S4. First, the table managed by the home CLS data management device 22 is searched to determine whether or not the destination of the data is a terminal unit connected to the home CLS (step S5). If it is a terminal unit connected to the home CLS, a routing process is performed in step S6.

[6184] If the destination of the data is a terminal not connected to the home CLS, a table managed by the mate CLS data management device 23 is searched. If the destination of the data exists in the table, the connectionless data is transferred according to the CLS identification number through the private line 5. If the destination of the data is not detected in the table, the data is discarded.

[6185] When the routing method is followed in cell units in the SMDS, the process shown in FIG. 805 can be performed on the BOM (or SSM). If a COM and EOM are received with the routing information obtained by the process performed on the BOM and stored as a MID (or MID+SNI) of the BOM as a key, then the routing informaion is retrieved using the MID (or the MID+SNI) as a key.

[6186] The transmission method in the private line can be realized by a fixed time slot assignment method, variable time slot random assignment method, and variable time slot control assignment method.

[6187] FIG. 806 shows the configuration based on other features of the present invention and shows a terminal point of the intra-station LAPD communications. In FIG. 806, a switch processor (CC) 1 is a main CPU for controlling a switch, and its program is stored in an MM 2.

[6188] An input/output control unit 4 is connected to a system bus 3 and controlled by the CC 1. The input/output control unit 4 is connected to a LAP control device (BSGC) 5 and an ATM switch 6, and interfaces between each device and the CC 1 through the system bus 3 for the communications of control information.

[6189] The CC 1 transmits control information to the BSGC 5 or ATM switch 6 through the input/output control unit 4. Each of the devices receives the control data, and requests the input/output control unit 4 for a DMA if it needs reading data from the MM 2.

[6190] The input/output control unit 4 sequentially accepts the requests and transfers the control information in the MM 2 to each device using the DMA.

[6191] The BSGC 5, input/output control unit 4, ATM switch 6, and input/output control unit 4 are directly connected via cable.

[6192] The BSGC 5 has an interface based on the intra-station devices 7 and 8, and the LAP, assembles a LAP frame using the data received from the input/output control unit 4, and transfers the frame to each intra-station device. As described as a DS3-SMDS interface in part 2, the intra-station device (SINF) 7 controls a subscriber cell and managed by an intra-station device (SIFSH) 8. The intra-station devices 7 and 8 are connected via cable. As described as a DS3-SMDS interface in part 3, the intra-station device 8 has the functions of concentrating each of the intra-station device 7, identifying a subscriber cell and intra-station control communications cell (signaling cell), and converting an intra-station control communications cell into a LAP frame. As explained in part 4, the ATM switch (ASSWSH) 6 has the function of routing a subscriber cell and an intra-station control communications cell according to the tag information assigned to each cell.

[6193] The intra-station control communications are described in detail in part 7, and also described in 10 in part 2, and 4 or 6 in part 3.

[6194] FIG. 807 shows another configuration according to the present invention.

[6195] In controlling a terminal unit (TERM) 14, a direct memory access (DMA) method is adopted. In this method, read and write are carried out on a divided area of a memory. As shown in FIG. 807, a main memory device (MM) 7 is positioned in the switch.

[6196] FIG. 808 shows the division of the MM 7 and control information format. As shown in FIG. 808, the MM 7 is divided into 2 areas DM 1 and DM 2. The TERM 14 writes the control information to one area DM 1, and the main processor (MPR) 1 reads the control information. The MPR 1 writes the control information to another area DM 2, and the TERM 14 reads the control information. The control information such as the status from the TERM 14, for example, fault information, an answer to a received command is written to the DM 1. The MPR 1 reads the control information to recognize the state of the TERM 14. A command from the MPR 1 is written to the DM 2. The control process is performed in response to the command by the TERM 14's reading the command.

[6197] FIG. 809(a) shows the format of the control information. The control information is represented in a 2-word (1 words=32 bits) format. The configuration is the same as the command in status. The leading 8 bits in the first word indicate the contents of the command and status. If the command refers to a fault information read command, it is defined as 01(H) and the contents are unified for all terminals. The area except the leading 8 bits in the first word refers to an address, and an address in the MM 7 to be accessed is set. The second word indicates a data area in which the information to be written to the MM 7 is set. If the status indicates a fault information notification, the contents of the fault information is set in the format shown in FIG. 809(b). The control information shown in FIG. 809(a) is stored in a control cell in the format shown in FIG. 809(c). The VPI/VCI of the control cell is uniquely assigned in a station.

[6198] The actual control is performed as follows.

[6199] In FIG. 807, a specific VPI/VCI is assigned to each of the TERMs 14. A tag is set in each multiplexing device CMUX 12. If control information is transmitted from the MPR 1 to the TERM 14, the MPR 1 writes the control information such as a command at an address in the MM 7 and notifies the TERM 14 of the necessity of the transmission of a command. A specific command code is used in the notification, and a VPI/VCI for the destination TERM 14 and a tag specifying the routing to the TERM 14 are set in the cell storing the command code. The cell is transmitted to the CMUX 12.

[6200] An SRM 11 routes the cell according to the tag assigned to the cell. When the TERM 14 recognizes that the VPI/VCI of the arriving cell indicates a control cell, a reading process starts for the MM 7. An address in the MM 7 and the number of commands (words) are specified in the data area of a command transmission notification control cell transmitted from the MPR 1.

[6201] The TERM 14 sets an address specified by the control cell from the MPR 1 in the address area in the control cell transmitted by the TERM 14. A VPI/VCI is assigned for the control cell and the cell is transmitted to the CMUX 12.

[6202] The VCC in the CMUX 12 assigns an output VPI/VCI instead of the input VPI/VCI assigned to the input control cell, and sets a specific tag for the input VPI/VCI. The control cell is input to the SRM 11 with other user cells.

[6203] When a cell having a tag for a control cell is received, a tag comparing unit (TAGCMP) 10 notifies an address decoder (ADRS DEC) 9 of the information.

[6204] The ADRS DEC 9 retrieves the address data from the control cell and outputs the address to the address bus 5. As shown in FIG. 808, the MM 7 is divided into two areas DM 1 and DM 2. As viewed from the TERM 14, an area assigned a larger address in the MM 7 is a read area, and an area assigned a smaller address in the MM 7 is a write area. Therefore, the ADRS DEC 9 provides a read/write enable signal for the MM 7 by decoding a higher order bit of the address in the control cell.

[6205] If the TERM 14 transmits a control cell indicating a read of a command from the MM 7 as described above, the ADRS DEC 9 outputs a read address stored in the input control cell to an address bus 5 and outputs a read enable signal to MM 7. As a result, a command group written by the MPR 1 in the DM 2 of the MM 7 is read from the MM 7 to a data bus 4.

[6206] An ATM interface device (ATMIF) 6 fetches the command group read to the data bus 4 and stores them in an ATM cell and inputs it to the CMUX 12. As a result, the ATM cell containing the command group is transferred from the CMUX 12 to the TERM 14 through the downward SRM 11.

[6207] When a status should be transmitted due to an occurrence of a fault in the TERM 14, the TERM 14 generates a control cell and transmits it to the CMUX 12. The control cell contains an address for use in accessing the DM 1 in the MM 7.

[6208] The arrival of the control cell is detected by the TAGCMP 10. The ADRS DEC 9 determines that the address stored in the input control cell is a write address by determining the higher order bit of the address. Then, it outputs the write address to the address bus 5 and outputs a write enable signal to the MM 7.

[6209] The status information stored in the control cell is retrieved by a data converter 8 and transmitted to the data bus 4.

[6210] As a result, the status information stored in the control cell is written to the DM 1 of the MM 7 through the data bus 4.

[6211] A health check is made on a predetermined cycle to monitor whether or not the communications between the MPR 1 and the TERM 14 are constantly normal. The ATMIF 6 has the function of generating an idle pattern for use in the idle check, and transmits the health check cell to the TERM 14 on a predetermined cycle. The TERM 14 receives a cell arriving on the cycle and returns an answer cell. The answer cell specifies a write of a specific pattern at a predetermined address in the DM 1 as control information. The MPR 1 monitors whether or not the communications between the MPR 1 and the TERM 14 are normal by monitoring the address in the DM 1 divided for each TERM 14 on each cycle (refer to FIG. 808).

[6212] FIG. 810 shows the configuration of the circuit of the TAGCMP 10 shown in FIG. 807. FIG. 811 is a timing chart of the operation.

[6213] FIG. 812 shows the configuration of the circuit of the ADRS DEC 9 shown in FIG. 807. FIG. 813 is a timing chart of the operation.

[6214] FIG. 814 shows the configuration of the circuit of the ATMIF 6 shown in FIG. 807. FIG. 815 is a timing chart of the operation.

[6215] FIG. 816 shows other characteristic configurations of the present invention.

[6216] First, a jig 4 for looping back a cell is connected to an output terminal of a multiplexer (MUX) 9 and an input terminal of a demultiplexer (DMUX) 5. Then, a microprocessor specifies a loopback for a selector 6 through an I/O register 11 or for a selector 7 through an independent function.

[6217] The microprocessor 1 executes a test program stored in a RAM 10, etc. As a result, for example, a test cell is transferred through the test route shown by the broken lines in FIG. 816.

[6218] That is, a test cell is transmitted from a LAP communications control unit (LAP) 2 to the MUX 9, and transferred through the route MUX 9→jig 4 (loopback)→DMUX 5→selector 6 or selector 7 (loopback)→routing symbol adding unit (VCC) 8→MUX 9→jig 4 (loopback)→DMUX 5→LAP 2. If a test cell transmitted by the LAP 2 is received by the LAP 2 within a predetermined time period in which the transmitted cell is monitored by the test program, it is determined that the provided test route is normal and the information is recorded in the RAM 10.

[6219] The microprocessor 1 can be designed such that the test program also checks for a fault of each device shown in FIG. 816 and operating under the control of the microprocessor.

[6220] FIGS. 817 and 818 show other characteristic configurations related to the present invention. FIG. 817 shows the entire image. FIG. 818 shows the software control.

[6221] A test is started by entering a test command 5 from a maintenance terminal unit 3 connected to a source station (ATM switch) 1. The input information of the test command 5 refers to the station number of the destination station (ATM switch).

[6222] A test cell sending program 8 receives the test command 5, reads the telephone number of the home station, and generates a test cell. The test cell contains sending route information, a telephone number of the destination station, and a telephone number of the source station as test cell information.

[6223] The test cell is directly inserted to an inter-station connecting device 9 for switching data between stations and transmitted between the stations. If the inter-station connecting device 9 recognizes the telephone number of the destination station in the test cell as that of the home station, a test cell receiving program 11 is activated by the test cell.

[6224] The test cell receiving program 11 determines the sending/returning route information stored in the test cell as test cell information.

[6225] When the test cell receiving program 11 determines the sending route information stored as the test cell information, it outputs a selector cell reception information 6 through an autonomous message to notify the maintainer that the test cell has arrived.

[6226] Then, the test cell receiving program 11 generates an answering test cell. The test cell contains, as test cell information, returning route information, a telephone number of the destination station (telephone number of the source station added to the received test cell), and a telephone number of the source station (telephone number of the destination station added to the received test cell).

[6227] The test cell generated by the test cell receiving program 11 is inserted to an inter-station connecting device 10 and transmitted between the stations. When the test cell is received at the source station which entered the test command, the inter-station connecting device 9 extracts the test cell and the test cell receiving program 12 is activated. If the returning route in the test cell information stored in the test cell is determined, the cell reception information 7 is output and the test terminates.

[6228] FIG. 819 shows other characteristic configuration related to the present invention. The configuration is the same as that shown in FIG. 193 in the traffic measuring process in 5.3 ASSWSH in part 4.

[6229] That is, in the ATM switch (ASSWSH), the following numbers of the cells are counted in the 2.4 Gbps/622 Mbps switch unit or DMUX unit as the function similar to the performance monitor to manage the state of the network.

[6230] (1) number of passing cells (P=0) for each 622 Mbps highway

[6231] (2) number of passing cells (P=1) for each 622 Mbps highway

[6232] (3) number of discarded cells (P=0) for each 622 Mbps highway

[6233] (4) number of discarded cells (P=1) for each 622 Mbps highway

[6234] Each of the above described parameters is collected every 15th minute as being triggered by the 15-minute notification from the switch processor (CC).

[6235] The number of cells is counted according to the output L, V, and H shown in FIG. 819 from an ADMUX LSI 1 (refer to FIG. 182), and the count values are stored in RAM 4 and 5. The traffic is counted on a cycle of about 25μ by 8-bit counters 2 and 3 for each highway. The count value is stored at a specific address in the RAM 4 or 5 through a selector (SEL) 8 and an adder (ADD) 9. On the next cycle, the count value read from the RAM 4 or 5 through a selector (SEL) 6 or 7 is added by the adder (ADD) 9 to the next count value read by the counter 2 or 3 through the selector (SEL) 8. The sum is stored again at the above described specific address. Each time a TG 10 receives a 15-minute notification from the CC, it outputs a switch instruction to the selectors (SEL) 6 through 8 and switches the count value write RAM into the RAM 4 or 5. As a result, the RAM 4 or 5 which has stopped writing count values stores the count value at 15 minutes before the above described notification. The next 15-minute count is performed using the RAM 4 or 5 which has started writing a new count value.

[6236] After the 15-minute notification from the CC, each count value is read from the RAM 4 or 5 which has stopped writing count values. The read count value is stored in the firmware until a count value is read from the CC by an SO command.

[6237] When the numbers of passing and discarded cells at the ATM switch unit or the DMUX unit are counted, the ATM switch unit or the DMUX unit operate at a high speed and have the transmission speed of 2.4 Gbps. If all cells in the ATM switch unit or DMUX unit are valid or the all cells are discarded, then a counter of up to 28 bits is required. Providing such a counter for each information unit makes an undesirably large hardware configuration. According to the present embodiment, a small counter of 4 or 8 bits is provided for the CNTR unit comprising the counters 2 and 3 and selector (SEL) 8. A long-time counting operation can be realized by adding the output to the previous count value within a short time. FIGS. 820, 821, and 822 show the configuration of the circuit of the memory map of the RAM 4 and 5, circuit configuration of the CNTR unit, and adder (ADD) 9 shown in FIG. 819 with the object ATM switch of 2.4 Gbps highway speed, 8-bit capacity of the counters 2 and 3 in the CNTR unit, 8-bit data direction area of the RAM 4 and 5, and 15-minute switch unit time of the RAM 4 and 5.

[6238] The memory map in the RAM 4 and 5 shown in FIG. 820 requires 28 bits for the count value. Therefore, assuming that the data direction area of the RAM 4 and 5 is 8 bits, 4 addresses are required for a count value and each count value is assigned 4 addresses from address 00H.

[6239] FIG. 821 shows the configuration of the circuit of the CNTR unit shown in FIG. 819. The CNTR unit comprises an 8-bit counter 1 for counting the numbers of passing cells and discarded cells (corresponding to the counter 2 or 3 shown in FIG. 819). If a valid cell notification or a discard notification is input from the ATM switch unit of DMUX unit, the counter 1 is incremented according to the notification. Each count value is input to a selector 2 (corresponding to the selector (SEL) 8 shown in FIG. 819), multiplexed according to the control signal from the TG 10 shown in FIG. 819. and then output.

[6240] FIG. 822 shows the configuration of the ADD 9 shown in FIG. 819. The ADD 9 comprises adders 1 and 2 of 4 lower bits and 4 higher bits with a C0 signal embedded between them for carry. In this case, an adding operation is performed 4 times because a piece of information contains 4 addresses. Practically added are only the lowest address, and the remaining 3 addresses are used in a calculation with carry. Therefore, in FIG. 819, the count value entered to the ADD 9 from the CNTR unit is divided into 4 blocks. Only the leading block is an actual count value and the remaining blocks are masked to 0. The output ADDV of the adder 1 is an output of the ADD 9 shown in FIG. 819.

[6241] FIG. 823 shows the configuration of the TG 10 shown in FIG. 819. The TG 10 has a built-in 8-bit counter which controls all timings and RAM. FIG. 824 is a timing chart. The TG 10 switches the RAM 4 and 5 according to the 15-minute notification from the CC.

[6242] With the above described configuration, a long-time counting operation can be realized. The header in the ATM cell contains a CLP bit indicating the priority level of a cell, and the bit is retrieved from the header information from the ATM switch or DMUX unit and added to the counter enable condition in the CNTR unit shown in FIG. 819. As a result, four counters, control signals SL1 and SL2 from the TG10, and four types of maps of the RAM 4 and 5 allow the numbers of passing cells and discarded cells to be counted in priority level units.

[6243] FIG. 825 shows the configuration of the CNTR unit. FIG. 823 shows the configuration of the TG 10.

[6244] The configuration shown in FIG. 819 can be applied to the DMUX unit by the method using the cell header information. The DMUX process is performed according to the tag information normally assigned to the header of a cell. Receiving the information from the DMUX unit allows the numbers of passing cells and discarded cells demultiplexed in output line units to be counted However, as in the case of the priority level, the enable condition of the counter in he CNTR unit, maps of the RAM 4 and 5, the extension of the TG 10 address counter, and the addition of control signals are required. By referring to an object DMUX unit, FIG. 826 shows the configuration of the CNTR unit shown in FIG. 819; FIG. 823 shows the configuration of the TG 10; and FIG. 822 shows the configuration of the ADD 9.

[6245] FIG. 827 shows other characteristic configuration of related to the present invention.

[6246] According to the following explanation, it is assumed that FIGS. 813 through 816 are appropriately referred to even if they are not specified.

[6247] The problem to be solved here is to select the trailer length, 13 nibbles or 14 nibbles, in accordance with proper rules in the period of 125 μsec when a PLCP multiframe is transmitted with the number of bits in the PLCP multiframe set to 5524 bits when the trailer length indicates 13 nibbles and 5528 bits when the trailer length indicates 14 nibbles while the number of the bits transmitted through the DS3 payload is 5592×84/85=5526.211. If the cycle staff counter of C1 bytes is used to indicate the trailer length, the C1 byte is cyclically changed on a three-multiframe cycle (refer to FIG. 815). The more practical problem in this case is to set in accordance with proper rules pattern P of 13-nibble trailer length of the third multiframe with pattern Q of 14-nibble trailer length of the third multiframe.

[6248] Described below is the first configuration to solve the above described problem.

[6249] As described above, the pattern of the number of nibbles of the trailer for the pattern P of 13-nibble trailer length of the third multiframe is a pattern 13→14→13, and the pattern for the pattern Q of 14-nibble trailer length of the third multiframe is a pattern 13→14→14.

[6250] Assuming that the ratio of pattern P to pattern Q is a:b, the ratio m:n of the multiframe of the 13-nibble trailer length to that of the 14-nibble trailer length is calculated as follows.

[6251] m:n=(2a+b):(a+2b) [equation 2]

[6252] Using m and n, the average bit number of the PLCP multiframes can be represented by the following equation.

[6253] (Mm+Nn)/(m+n) [equation 3]

[6254] where M indicates the number of bits of multiframes of 13-nibble trailer length, and M=5524 bits as described above, and N indicates the number of bits of multiframes of 14-nibble trailer length, and M=5528 bits as described above.

[6255] Furthermore, assuming that the number of bits transmitted by the DS3 payload in the period of 125 μsec is X, the following equation exists.

[6256] X=5592×84/85 bits [equation 4]

[6257] Thus, equations 3 and 4 generate the following equation because the number of bits X only has to be equal to the average number of bits of the PLCP multiframe.

[6258] (Mm+Nn)/(m+n)=X [equation 5]

[6259] According to equations 5 and 2 above, the ratio a:b can be represented by the following equation.

[6260] a:b=29:56 [equation 6]

[6261] According to equation 6, if the ratio of pattern P to pattern Q is 29:56, the number of bits transmitted by the DS3 payload is equal to the average number of bits in the 125 μsec, thereby transmitting the PLCP multiframe by the DS3 payload in the 125 μsec period without deficit or excess.

[6262] Considering that the shortest cycle containing pattern P and Q meeting the above described conditions refers to 29+56=85 PLCP multiframes, 29×N patterns P and 56×N patterns Q are transmitted for each of N times 85 (N is an integer of 1 or larger than 1) PLCP multiframe cycles. This is shown in FIGS. 827 and 828. FIG. 829 shows the operation of such a configuration.

[6263] PLCP frame generating units 1 and 2 of patterns P and Q store ATM cells or L2-PDU cells in the PLCP payload and adds a PLCP header and trailer to assemble a PLCP frame. The pattern P PLCP frame generating unit 1 adds a trailer on the three cycles of 13, 14, and 13 nibbles. The pattern Q PLCP frame generating unit 2 adds a trailer on the three cycles of 13, 14, and 14 nibbles.

[6264] With the configuration shown in FIG. 828 corresponding to the sending pattern selecting unit 4 shown in FIG. 827, a selector 2 receives 85×N input values consisting of 29×N 0s and 56×N 1s. The 85×N division counter has the selector 2 cyclically select 85×N input values input to the selector 2 in synchronism with the cycle of the PLCP and output the input value to a selector 3 shown in FIG. 827 as a pattern switch signal.

[6265] The selector 3 selects inputs A1 and A2 according to the above described pattern switch signal. That is, the selector 3 selects pattern P when the pattern switch signal indicates 0 and pattern Q when the signal indicates 1.

[6266] A DS3 interface unit 5 inserts the PLCP frame into the DS3 payload in synchronism with the transmission speed of 44.736 MHz, adds a DS3 header, and assembles and transmits the DS3 frame.

[6267] With the configurations shown in FIGS. 827 and 828, the ratio of pattern P to pattern Q in the PLCP multiframe output from the selector 3 is 29:56 as shown in FIG. 829, thereby transmitting the PLCP multiframe by the DS3 payload in the 125 μsec period without deficit or excess.

[6268] Described below is the second configuration with which the above described problem is solved.

[6269] With the ratio of pattern P to pattern Q of 29:56 defined by the above listed equation 6, 1 is subtracted from the value 29 for pattern P to obtain the half of the value 56 for pattern Q. Based on this, the transmitted PLCP multiframe pattern can be obtained as follows assuming that the cycle of the combination of patterns P and Q contains 85 multiprames. It satisfies the condition of equation 6 with a 28-repetitive pattern and a last-added pattern P.

[6270] a 85-multiframe cycle

[6271] The above listed combinations can reduce the difference in the number of transmitted PLCP multiframes. FIGS. 827 and 830 show the configurations which realize these combinations. FIG. 831 shows the operations corresponding to the configurations.

[6272] With the configuration shown in FIG. 830 corresponding to a transmission pattern selecting unit 4, the selector 2 receives a total of 85 input values consisting of 28 sets of 101 input value groups and an input value of 0. The 85×N division counter has the selector 2 cyclically select 85 input values input to the selector 2 in synchronism with the cycle of the PLCP and output the input value to a selector 3 shown in FIG. 827 as a pattern switch signal.

[6273] With the configurations shown in FIGS. 827 and 830, as in the case of the first configuration, the ratio of pattern P to pattern Q in the PLCP multiframe output from the selector 3 is 29:56 as shown in FIG. 831, thereby transmitting the PLCP multiframe by the DS3 payload in the 125 μsec period without deficit or excess. Since the pattern QPQ is frequently repeated, the difference in the number of transmitted PLCP multiframes can be reduced.

[6274] Described below is the switch having multicasting capabilities.

[6275] The switch according to the present embodiment is based on the ATM switch for switching an ATM cell. In the ATM switch, the following functions are required to realize the multiceasting capabilities.

[6276] 1. Copying a cell

[6277] 2. Reassigning a VPI/VCI

[6278] When a cell is copied, the two following processes are required.

[6279] 1. Copying in a switch

[6280] 2. Copying on the same line

[6281] FIG. 832 shows the configuration of the switch for realizing the point-to-multipoint function. (a) indicated a trunk system; (b) indicates an input unit copy system; and (c) indicates an internal copy system.

[6282] (1) Trunk system: A point-to-multipoint connection cell which is output from a source terminal and distributed to a plurality of subscribers temporarily enters a trunk (for example, a message handler in the SMDS) through a switch. After copying cells and reassigning their VPI/VCIs in the trunk, the cells are transferred again to the switch and distributed to a plurality of destination subscribers.

[6283] (2) Input unit copy system: A block is provided before a switch to copy cells to. A point-to-multipoint cell is copied to the block. The switch only has the function of switching (connecting) a copied cell.

[6284] (3) Internal copy system: A cell is copied in the multistage self-routing (MSSR) configuration.

[6285] In the point-to-multipoint connection cell, information indicating that the cell is a point-to-multipoint connection cell is set. The point-to-multipoint connection cell represents a plurality of destination subscribers by, for example, the VPI/VCI of the cell.

[6286] FIG. 833 is a table showing the features of the three systems shown in FIG. 832.

[6287] If there are a small number (10˜100) of point-to-multipoint connections supported in the system, the trunk system is recommended. If there are a large number (100 or more) of point-to-multipoint connections supported in the system, the input unit copy system or the internal copy system is recommended. If the number of sources requesting the point-to-multipoint transfer is almost equal to that of the lines (channels) of the cell destination subscribers, then the input unit copy system is recommended. If these numbers are quite different, then the internal copy system is recommended.

[6288] As a switch network, even if there is a small difference in number of channels of lines between the source and destination subscribers, there can be a case in which internal copy system is recommended. That is, when a point-to-multipoint connection is provided, a source device does not have to provide a plurality of sources. However, in consideration of available bands, the same band as the point-to-multipoint connection is used. As a result, the input copy system does not have advantageous points as a switching network. If there is large difference between the source and subscriber lines in a switch, the internal copy system is advantageous because it does not require adding blocks (copy function shown in FIG. 832B. Thus, an internal copy system is advantageous especially it is used in a large scale system.

[6289] FIG. 834 shows the configuration for realizing the point-to-multipoint connection using the internal copy system.

[6290] When the point-to-multipoint connection is realized by the internal copy system, a bit map is used. Assuming that there are 64 output paths and the concentration ratio is 4:1 in the MSSR, the output paths to individual lines are 16×4×64=6496 in excess of the number displayed by the bit-map representation. Therefore, the multicast connection system according to the present embodiment is configured as follows.

[6291] 1. 1st stage in the MSSR: point-to-multipoint connection

[6292] 2. 2nd state in the MSSR: bit map for point-to-multipoint connection

[6293] 3. 3rd stage in the MSSR: bit map for point-to-multipoint connection

[6294] 4. DMUX unit: bit map through decoding the VPI/VCI

[6295] The number of bits used in the bit map in the point-to-multipoint connection is defined as follows.

[6296] 1. 1st stage in the MSSR: 3 bits (for an 8×8 switch for instance)

[6297] 2. 2nd stage in the MSSR: 8 bits

[6298] 3. 3rd stage in the MSSR: 8×8 bits

[6299] Each bit in the above described bit map is written to a tag area added to each cell in the switch. In the case above, 9 octets are required for a tag area. However, the size of the tag area in the switch can be optionally set for each switch, and the above described bit map can be realized with the tag information set for 9 octets and the length of each cell set for 64 octets. If the cell length is set to a larger value, the clock should be sped up in performing processes in the switch. For example, if 54-octet cells are normally processed, the clock speed should be 64/54 times sped up.

[6300] FIG. 835 shows the system or realizing the above described bit map without extending the cell length.

[6301] In this case, the bit map processed by the 3rd stage of the MSSR with the configuration shown in FIG. 834 is processed by the external trunk 2. That is, the point-to-multipoint connection cell transmitted to the switch 1 is input to the trunk 2 and copied the number of connections for the 3rd stage of the MSSR in the switch 1. A VCCT 3 is provided at the output unit of the trunk 2 for adding an 8-bit bit map to each of the copied cells and transferring it to the switch 1. Thus, the bit map for the point-to-multipoint bit map can be realized without extending the cell length.

[6302] FIG. 836 shows the VPI/VCI decoding circuit. The VPI/VCI decoding circuit shown in FIG. 836 is provided in, for example, the DMUX unit shown in FIG. 834.

[6303] The table 1 provided in the VPI/VCI decoding circuit is searched using the VPI/VCI of an input cell as an address. The retrieved data is a bit map of 16×4=64 bits.

[6304] The C bit check unit 2 retrieves the bits (C bits) set at a predetermined position in the tag information of an input cell. When the value is 1, it is determined that the input cell is a point-to-multipoint connection cell. The determination result of the C bit check unit 2 is reported to the processor and used when the table 1 is searched.

[6305] The point-to-multipoint connection on the same line is described below. The process on the same line requires the two following functions.

[6306] 1. VPI/VCI decoding function as the copying function on the same line

[6307] 2. VPI/VCI reassigning function at an output terminal

[6308] Reassigning a VPI/VCI at an output terminal requires a VPI/VCI conversion table (VCCT). The VCCT is required for a point-to-point connection and a point-to-multipoint connection. The VCCT is a table from which information (output VPI/VCI, etc.) is retrieved using a VPI/VCI of a cell. If information is to be assigned to all VPI/VCI, the memory of storing 2²⁴pieces of information is required when the number of bits of the VPI/VCI is, for example, 24 bits. Providing such memory is not practical, and the switch according to the present embodiment is configured as follows.

[6309] At the input terminal, a process of reassigning a VPI/VCI of an input cell and a process of assigning tag information are performed. At this time, the path of a newly assigned VPI/VCI only has to identify a path on an output line or each line, and does not have to identify all VPI/VCI. Therefore, an address value much smaller than the number of bits of the VPI/VCI is used as a VPI/VCI at the input terminal. The actual VPI/VCI is retrieved using the address value as a key. Thus, a smaller size of memory is obtained in the switch by using a degenerated VPI/VCI.

[6310] FIG. 837 shows the configuration of a point-to-multipoint connection.

[6311] In the following explanation, the VPI/VCI of a cell input to the switch is referred to as an I VPI/VCI, the VPI/VCI used in the switch is referred to as an S VPI/VCI, and the VPI/VCI set for the cell output from the switch is referred to as an O VPI/VCI.

[6312] The VPI/VCI for which a point-to-point connection is set indicates the following settings. That is, an S VPI/VCI, tag information, and the information (C bit is set to 0) indicating a point-to-point connection are set in the input unit VCCT (IVCC) 1 for each I VPI/VCI as a path set for the I VPI/VCI of an input cell. At the output unit VCCT (OVCC) 2, O VPI/VCI is set for each S VPI/VCI. The decoding table 3 has no settings.

[6313] In a point-to-multipoint connection, an S VPI/VCI, tag information, and the information (C bit is set to 1) indicating the point-to-multipoint are set for each I VPI/VCI in the input unit VCCT (IVCC) 1. The decoding table 3 has a bit map in the DMUX 4 for each SVPI/VCI. The bit map can have one or more output units VCCT (OVCC) 2 in the plurality of output units VCCT. In the output unit VCCT (OVCC) 2, the number of copies for each line and the O VPI/VCI are set for each SVPI/VCI.

[6314] FIG. 838 shows the configuration of the buffer and output unit VCCT provided for each output line.

[6315] With the configuration shown in FIG. 838, the copy process for point-to-multipoint cells is performed using a buffer, and the VPI/VCI reassigning process is performed using a table provided for a point-to-point connection. With the configuration, the hardware can be greatly reduced.

[6316] Upon receipt of a cell output from the DMUX 4, the C bit set at a predetermined position of the tag information of a cell is referred to. If the C bit is 0, it refers to a point-to-point connection. If the line number set in the tag information refers to the number of the VCCT of the output unit, the cell is written to a predetermined class (for example, 0) in the buffer 1.

[6317] If the C bit is 1, it refers to a point-to-point connection. In this case, the bit map set in the decode table 3 shown in FIG. 837 is referred to. If the number of the VCCT of the output unit (line number) is specified, the cell is written to the buffer 1. At this time, the cell is written to more than 1 class in classes 0˜3 according to the class identification information set in the tag information in the cell.

[6318] The cell read process from the buffer 1 is performed according to the information set by the software for managing the switch when a path is set. The software sets the following information.

[6319] 1. Band assigned to each class (contents of the scheduler of the DMUX controller)

[6320] 2. Contents of the table of the VCCT of the output unit (in case of a point-to-point connection, O VPI/VCI for S VPI/VCI: in case of a point-to-multipoint connection, the number of copies, a value of S VPI/VCI for reserving a path, and O VPI/VCI) FIG. 839 is a table of the contents of the output unit VCCT set by the firmware according to the software settings.

[6321] In the case of the point-to-point connection, the E-F bit is set to 1. In the case of the point-to-multipoint connection, one of the O VPI/VCIs corresponding to the destinations is set. Then, the values of S VPI/VCI for reserving the paths of the 0O VPI/VCI are sequentially set to Q-ADD, and O VPI/VCI is set at the address for the S VPI/VCI. At the last address, the E-F bit is set to 1. Otherwise, the E-F bit is set to 0.

[6322] FIG. 840 shows an example of a table on which an output VPI/VCI is set.

[6323] In the example shown in FIG. 840, multicasting transfer is performed for 4 paths (to destinations 1-4) on the same line. The value of S VPI/VCI is a; the value of O VPI/VCI is b0˜b3; and the band assigned to each path is c0˜c3.

[6324] FIG. 841 is a flowchart explaining the process of the VCCT of the output unit. The VCCT of the output unit extracts the tag information and VPI/VCI, etc. added to each cell, copies the cell by referring to the table shown in FIG. 840, and writes the output VPI/VCI for each of the copied cells.

[6325] A class number (i) for use in identifying a class whose cells are next read is determined. The Q-address and E-F bit identified by the determined class number are read from the class process memory, and cells are read from class i in the QCP buffer (step S1-S3).

[6326] If the E-F bit is 0, the S VPI/VCI of the cell read in the above step S3 is set as the Q-address read from the class process memory (steps S4 and S5).

[6327] The O VPI/VCI, Q-address, and E-F bit are read from the output unit VCCT using the S VPI/VCI as an address. For example, if a cell is addressed to the destination 2 in the example shown in FIG. 840, b1, c1, and 0 are retrieved according to the address c0 (step S6).

[6328] The O VPI/VCI read in step S6 is written to the cell and output, and then the Q-address and E-F bit are written to the class process memory (steps S7 and S8).

[6329] The processes in steps S1-S8 are repeatedly performed until the E-F bit indicates 1. When the E-F bit indicates 1, the buffer address, etc. related to class i is released. In the example shown in FIG. 840, the processes in steps S1-S8 are repeatedly performed until the cell addressed to destination 4 is output (steps S9 and S10).

[6330] The self-routing module (SRM) forming part of the MSSR of the switch identifies a path according to the VPI/VCI of a cell input by the switch. The routing in the switch is performed in path units according to the tag information added to a cell. Therefore, at the entry point of the cell, the information designating the routing in the switch of the cell is retrieved according to the VPI,/VCI set in the cell. The function of adding the retrieved routing information to the cell as tag information is required. In the switching process, the function of reassigning the VPI/VCI set in the input cell as an output VPI/VCI is also required.

[6331] For the switch of the MSSR configuration, the above described function (VCCT) may be provided in each SRM. However, the number of bits of a VPI/VCI is 28 for the network-to-network interface and 24 for the user-to-network interface. Providing a plurality of a large table (memory) in which tag information and output VPI/VCI are set for all VPI/VCIs undesirably requires large-scale hardware.

[6332] Therefore, a VCI conversion table (VCCT) for use in realizing the above described functions is provided at the entry point of the switch. According to the VCCT, the tag is added and the VPI/VCI is rewritten.

[6333] FIG. 842 shows the configuration of the switching system whose switch is equipped with a VCCT at its entry point.

[6334] Assume that the table is searched using the VPI/VCI as is with the VCCT. As described above, the VPI/VCI is 28 or 24 bits. Setting the tag information and output VPI/VCI for all the VPI/VCI requires the memory (VCC table) having 228 or 224 addresses. Such large memory is undesirably accompanied by a large-scale hardware configuration. Likewise, the use amount parameter control/network parameter control (UPC/NPC) is searched using a VPI/VCI. In this case, the table searching system using the VPI/VCI as is requires undesirably large memory.

[6335] The switching system according to the present embodiment has the function of converting (degenerating) a VPI/VCI into a memory retrieving address of a smaller number of bits. In the point-to-multipoint connection, cells are copied in a switch and a VCCT is required for each output line.

[6336] FIG. 843 shows the configuration of the switching system according to the present embodiment.

[6337] As shown in FIG. 843, an I VPI/VCI converting unit 1 is provided at the entrance (UPC, before the tag assigning unit) of the exchange station. The I VPI/VCI converting unit 1 converts the VPI/VCI (I VPI/VCI) of an input cell into the VPI/VCI (S VPI/VCI) in the exchange station to be used as a memory retrieving address. An S VPI/VCI converting unit 2 for converting the S VPI/VCI into an output VPI/VCI (O VPI/VCI) is provided at the output unit of the exchange station.

[6338] In the ATM communications service, VP service and VC service are provided. In the VP service, data is transferred in the unit of virtual paths VP accommodating a plurality of virtual channels VC. Therefore, a communications lines can be identified by a VPI only without using a VCI in the VP service. This helps reducing the size of the VCCT.

[6339] First, the service identification information is set to output tag information of each cell indicating the VP service or VC service. The exchange station provides a table for use in the VP service and a table for use in the VC service. An output VPI is set for an input VPI on the table for the VP service. An output VPI/VCI is set for an input VPI/VCI on the table for the VC service. When a cell enters the exchange station, the cell's service identification information recognizes the service type and performs a VPI/VCI conversion according to one of these tables. The process is performed by the I VPI/VCI converting unit 1.

[6340] The cell that has passed the switch recognizes the service type according to the service identification information in the S VPI/VCI converting unit 2. The O VPI/VCI table 3 referred to by the S VPI/VCI converting unit 2 comprises a table for the VP service and a table for the VC service. One of these tables are accessed depending on the service type.

[6341] If the tables for the VP service and VC service are provided individually as in the configuration above, the size of the hardware can be reduced because the table for the VP service is comparatively small.

[6342] Thus, there are various method of degenerating the VPI/VCI. The method of limiting the number of bits used for a VPI/VCI may generate a problem about system operations. Therefore, the memory can be reduced in size by limiting the number of paths that are set simultaneously.

[6343] As described above, a point-to-multipoint connection can be realized without an external device according to the exchange station of the present embodiment.

[6344] Described below is the embodiment of a system of transferring information necessary for the point-to-multipoint connection in parallel with the cell in the exchange station.

[6345] As described above, the functions of copying a cell and reassigning the VPI/VCI of the copied cell are required to realize the point-to-multipoint connection. These functions are performed in cell units.

[6346] FIG. 844 shows the format of a cell in the switch. As shown in FIG. 844, a cell comprises, in a switch, tag information, header, and payload, and is processed in the 8-bit parallel format. The tag information contains routing information in the exchange station, etc. and is added at the entrance of the exchange station according to the VPI/VCI of each cell. In the switch, the cell is controlled (routing control, copy instruction, etc.) by the tag information only. According to the system of the present embodiment, the control information necessary for the point-to-multipoint connection is transferred in parallel with the cell in the exchange station, and is processed in the 9-bit parallel format.

[6347] FIG. 845 shows the configuration of the exchange station according to the present embodiment.

[6348] The cell transferred through the user-to-network interface or network-to-network interface (UNI/NNI) is terminated by the line interface unit 1 provided for each line. The VPI/VCI converting unit (VCCT) 2 rewrites the VPI/VCI of an input cell. The multiplexing unit MUX 3 multiplexes a cell input through a plurality of lines. The switch 4 is an 8×8 buffer type switch. The demultiplexing unit DMUX 5 distributes a cell output from the switch 4 to a predetermined line interface unit 1.

[6349] FIG. 846 shows an example of the configuration of the control information for a point-to-multipoint connection.

[6350] The point-to-multipoint connection control information comprises a switching bit map, DMUX bit map, and subscriber ID. In the switching bit map, the switch has an 8×8 configuration and refers to 8-bit information. In the DMUX bit map, the number of lines distributed by the demultiplexing unit DMUX 5 is 16, and is assigned 16 bits. The subscriber ID identifies a destination subscriber and is assigned 8 bits.

[6351] The point-to-multipoint connection control information in the above described configuration is provided in the VPI/VCI converting unit (VCCT) 2 corresponding to the VPI/VCI stored in the header of the input cell. The information is set when a call is connected. It is not set for a point-to-point connection. The VPI/VCI converting unit (VCCT) 2 transfers the point-to-multipoint connection control information in parallel with an input cell when the cell is transferred to a switch with tag information added. The synchronization is established between a cell and point-to-multipoint connection control information, and they are transferred in the 9-bit parallel format.

[6352] The point-to-multipoint connection according to the present embodiment has the two important functions as follows.

[6353] 1. Copying in the switching unit and DMUX unit.

[6354] 2. Copying and VPI/VCI reassigning in the line interface unit

[6355] First, the copying capabilities in a switch unit are explained. When a cell enters the exchange station, tag information is added-to the cell in the VPI/VCI converting unit (VCCT) 2 shown in FIG. 845. In the tag information, the information indicating that the cell is a point-to-point connection cell or a point-to-multipoint cell is set as C bit information. If the C bit information is 0, it refers to a point-to-point connection and the cell is processed according to the routing information set in the tag information added to the cell in the exchange station.

[6356] FIG. 847A shows the configuration of the buffer of a switch. FIG. 847B shows an example of the switching bit map in the point-to-multipoint connection control information.

[6357] If the C bit information is 1, it refers to a point-to-multipoint connection, and the point-to-multipoint connection control information transferred in parallel with the cell in the exchange station is referred to. In the switch unit, the switching bit map is referred to. At this stage, a cell whose C bit information is set to 1 enters the switch from the input highway 1, and the switching bit map is shown in FIG. 847B. In this case, the cell is written to buffers 12, 13, 15, and 16. Accordingly, the cell input from the input highway 11 is output to the output highway 2, 3, 5, and 6. Thus, the function of copying cells can be realized in the switch unit. Cells can be copied likewise in the DMUX unit.

[6358] Described below are the copying function and VPI/VCI reassigning function.

[6359] Upon receipt of a cell whose C bit is 1, the line interfacing unit 1 determines a point-to-multipoint connection and retrieves a subscriber ID in the point-to-multipoint connection control information. The line interface unit 1 is provided with a table searched using a subscriber ID as a key. The table contains the number of copies and a VPI/VCI assigned to each cell generated by a copying process. The line interface unit 1 accesses the table by the retrieved subscriber ID, copies a cell, and reassigns the VPI/VCI.

[6360] The process of the software of the exchange station related to the point-to-multipoint connection is explained below. Upon receipt of a point-to-multipoint connection request in response to a path setting request (call connection request), the software of the exchange station sets the C bit to 1 corresponding to the VPI/VCI to be assigned to the path. In setting the path, the destination subscriber ID is specified, and the software of the exchange station writes to the table provided in the line interfacing unit 1 according to the specification the number of copies and the VPI/VCI set for each cell generated by the copy.

[6361] When a cell enters the exchange station, the above described hardware made a point-to-multipoint connection according to the information set by the software of the exchange station.

[6362] With the above configuration, a point-to-multipoint connection can be realized in the switch without providing a device for copying a cell external to the switch. Since the point-to-multipoint control information is transferred not as a tag information, but in parallel with the cell in the exchange station, the throughput is not degraded.

[6363] FIG. 848 shows another characteristic configuration of the present invention. FIG. 848 shows an example in which a source terminal 1 multicast-transfers data to destination terminals 4-1-4-5 through an exchange station 2.

[6364] When the source terminal 1 makes a multicast connection, the transfer data (hereinafter referred to as a cell) is transferred to a multicast device 6. That is, the source terminal 1 transmits the cell to the ATM exchange station 2 using the destination address of the multicast device 6. The ATM exchange station 2 connects the path 5 according to the destination address and transfers the cell to the multicast device 6. At this time, the transmission lines between the source terminal 1 and the multicast device 6, that is, the line 3 and path 5 are in the communications state of connection of 1:1.

[6365] Upon receipt of the cell transmitted by the source terminal 1, the multicast device 6 transfers the cell to the destination terminal 4-1. That is, the multicast device 6 transmits the cess to the ATM exchange station 2 with the destination terminal 4-1 set as the destination address of the cell. The ATM exchange station 2 connects the path 7-1 according to the destination address and transfers the cell to the destination terminal 4-1 through the path 7-1.

[6366] Then, the multicast device 6 transfers the cell transmitted by the source terminal 1 to the destination terminals 4-2-4-5 sequentially. At this time, ATM exchange station 2 connects the paths 7-2-7-5.

[6367] The multicast device 6 is provided in the exchange station, and the destination information, etc. is set for each multicast service request from the user. A plurality of multicast services are processed.

[6368] As mentioned above, the multicast device 6 has the ability to copy cells. When the copied cells are distributed to N destination terminals (5 terminal in FIG. 848), the multicast device 6 transfers the cells to each destination terminal sequentially. The amount of the resources is the same as that in the 1:1 connection.

[6369] FIG. 849 shows an example in which the multicast function of the present embodiment is applied to the video distribution service. In FIG. 849, shows an example in which video data stored in the video server 11 is distributed to the subscriber terminals 20-1-20-3.

[6370] The controller 12 controls video data and transfers a video signal to the B-ISDN adapter 13. The B-ISDN adapter 13 transmits the video signal transferred from the controller 12 to the network interface device 15 according to the protocol of the subscriber line interface 14.

[6371] The network interface device 15 converts the transfer data including the video signal into the data in the format processed by the exchange station 16. The exchange station 16 is hereinafter referred to as an ATM exchange station. In this case, the network interface device 15 converts the transfer data including the video signal into an ATM cell. The network interface device 15 sets in each cell the VPI/VCI identifying the multicast device 30 as the destination address, and transmits the cells to the exchange station 16. The VPI/VCI identifying the multicast device 30 is reported by the controller 27 as described later.

[6372] Upon receipt of the cell, the exchange station 16 connects the path 17 for connecting the network interface device 15 with the multicast device 30 according to the VPI/VCI set in the cell to transfer the cell through the path 17.

[6373] FIG. 850 shows the configuration of the multicast device 30.

[6374] The VPI/VCI conversion table 31 is written when a multicast connection requesting call is connected. For example, if a call connection request is issues to multicast-distribute video data stored in the video server 11 to the subscriber terminals 20-1-20-3, then the controller 27 first obtains a VPI/VCI (VPI/VCI 17) specifying the path (path 17) for connecting the network interface device 15 with the multicast device 30. Then, the controller 27 reports the VPI/VCI 17 to the network interface device 15 and reserves the area for the VPI/VCI 17 on the VPI/VCI conversion table 31.

[6375] Then, the controller 27 obtains the VPI/VCIs (VPI/VCIs 1-3) specifying the paths (paths 22-1-22-3) for connecting the multicast device 30 with the network interface devices 23-1-23-3. Then, it writes the VPI/VCIs 1-3 to the area reserved for the VPI/VCI 17 on the VPI/VCI conversion table 31.

[6376] Described below is the operation of the multicast device 30 when it receives a cell. The cell is transferred from the network interface device 15 through the exchange station 16, and is temporarily stored in the receiving unit 32. The control unit 33 searches the VPI/VCI conversion table 31 according to the VPI/VCI set in the cell stored in the receiving unit 32. Since the VPI/VCI set in the input cell is VPI/VCI 17, the VPI/VCIs 1 through 3 are retrieved as output VPI/VCIs. These output VPI/VCIs are passed to the VPI/VCI assigning unit 34. The control unit 33 recognizes the number of the destination subscribers from the retrieved VPI/VCIs.

[6377] Then, the copying unit 35 copies the cell stored in the receiving unit 32 according to the instruction of the control unit 33 and writes it to the output buffer 36. At this time, the VPI/VCI assigning unit 34 sets “VPI/VCI 1” for the cell copied by the copying unit 35. The copying unit 35 copies two cells stored in the receiving unit 32, and the cells are assigned VPI/VCI 2 and VPI/VCI 3 and written to the output buffer 36.

[6378] The control unit 33 first transfers the cell assigned VPI/VCI 1 to the exchange station 21. The exchange station 21 is an ATM exchange station comprising a self-routing module. Upon receipt of the cell, the exchange station 21 connects the path 22-1 between the multicast device 30 and the network interface device 23-1. Therefore, the video data read from the video server 11 is transferred to the network interface device 23-1 through the path 22-1. Then, the data received by the network interface device 23-1 is transferred to the subscriber terminal 20-1 through the controller 25.

[6379] Likewise, the control unit 33 sequentially transfers the cells assigned VPI/VCI 2 and VPI/VCI 3 to the exchange station 21. Upon receipt of the cell, the exchange station 21 establishes the paths 22-2 and 22-3 according to the VPI/VCI values. The cells assigned VPI/VCI 2 and VPI/VCI 3 are transferred to the paths 22-2 and 22-3 respectively, and reach the subscriber terminals 20-2 and 20-3.

[6380] The controller 27 recognizes the use state of the exchange stations 16 and 21 through the connection admission control (CAC) function. The control unit 33 receives from the controller 27 a notification about the use state of the exchange stations 16 and 21. If the exchange station 21 is in the congestion state, the control unit 33 stops the cell read process from the output buffer 36. With the configuration, cells may be discarded in the output buffer 36 when the congestion state of the exchange station 21 continues. However, the entire exchange station can recover from the congestion state.

[6381] As described above, the multicast connection system can reduce the load on the source terminal and the use rate of the line between the source terminal and the exchange station and the operations of the exchange station can be successfully reduced because the data transmitter has only to transmit the same amount of data as the case of the one-to-one connection regardless of the number of the destinations. Therefore, the hardware resources which becomes in an idle state with the configuration (above described lines and exchange stations) can be usefully assigned to other services.

[6382] When a multicast connection service is provided through the conventional exchange stations, it can be realized only by providing the above described multicast device. Since the ATM exchange station greatly depends on the hardware configuration, it is a large merit to realize a multicast connection service without design amendments to the exchange stations.

[6383] FIG. 851 shows the configuration of the system for communications among a plurality of communicators through a multiple communications trunk built in the exchange station. In this example, subscriber A accommodated in the concentrator 1 communicates with subscribers B and C accommodated in the concentrator 2. The 3-subscriber communications are referred to as a TV-telephone conference through voice and images. The concentrators 1 and 2 are connected to the host exchange station 3. The host exchange station 3 is an ATM exchange station comprising a self-routing switch, and a path is set according to the VPI/VCI of each cell. The multiple subscriber communications trunk 4 is connected to the host exchange station 3 in, for example, a switching station, and edits and synthesizes image and voice data transferred in the cell format from each subscriber according to the VPI/VCI of the cell. Then, it adds the edited or synthesized data to the cell assigned the VPI/VCI specifying a destination subscriber and transmits them to the host exchange station 3. The multiple subscriber communications trunk 4 is provided for each multiple subscriber communication.

[6384] Subscriber A is connected to the multiple subscriber communications trunk 4 through the bi-directional virtual path 5 specified by the VPI/VCI=xa. Subscribers B and C are connected to the multiple subscriber communications trunk 4 through the bi-directional virtual paths 6 and 7 specified by the VPI/VCI=xb and VPI/VCI=xc respectively.

[6385] When subscribers A, B, and C start the 3-subscriber communications with the above described configuration, the transmission data from each subscriber is temporarily transferred to the multiple subscriber communications trunk 4 and then transmitted to the destination subscriber after being edited by the multiple subscriber communications trunk 4. Thus, with the above described configuration, the system provides multiple subscriber communications services through the functions of the exchange station.

[6386] FIG. 852 shows the configuration of the system for multiple subscriber communications using a multiple termination unit in the subscriber line.

[6387] The system shown in FIG. 852 uses the multiple termination unit 11 when subscribers A, B, and C enter the 3-subscriber communications. The multiple termination unit 11 is accommodated in the concentrator 1 through a subscriber line. The bi-directional virtual path 12 specified by VPI/VCI=yd connects subscriber A with the multiple termination unit 11. The bi-directional virtual paths 13 and 14 specified by VPI/VCI=ye and VPI/VCI=yf connect subscribers B and C with the multiple termination unit 11 respectively.

[6388] The multiple termination unit 11 can simultaneously process data transferred through a plurality of virtual paths specified by a plurality of VPI/VCIs, and adds the edited or synthesized data to the cell assigned the VPI/VCI specifying a destination subscriber and transmits them to the host exchange station 3. Thus, with the above described configuration, the system provides a multiple subscriber communications through a terminal provided in the subscriber line.

[6389] Described below is the procedure of providing a multiple subscriber communications service in the system shown in FIG. 851 or 852.

[6390] FIG. 853 is a process flowchart showing the 3-subscriber communications service in the system shown in FIG. 851. In this example, subscriber C is called in the 2-subscriber communications state in which subscribers A and B communicate each other, and the 3-subscriber communications state is entered.

[6391] A predetermined VPI/VCI (for example, VPI/VCI=ab) connects subscriber A with subscriber B. In such a 2-subscriber communications state, one of the subscribers A and B issues a 3-subscriber communications request by specifying subscriber C according to a predetermined procedure.

[6392] Upon receipt of the 3-subscriber communications request, the host exchange station 3 calls subscriber C if an unused multiple subscriber communications trunk 4 is available (step S1 and S2).

[6393] The host exchange station 3 receives the response from subscriber C and reports it to the multiple subscriber communications trunk 4 (step S3).

[6394] The VPI/VCIs of a predetermined number are assigned to the multiple subscriber communications trunk 4 to connect each of subscribers A, B, and C with the multiple subscriber communications trunk 4. The host exchange station 3 selects VPI/VCI=xa, xb, and xc as the VPI/VCI specifying the path between each of the subscribers A, B, and C and the multiple subscriber communications trunk: 4. At this time, 3 is set as the number of subscribers being connected (steps S4 and 5).

[6395] Upon receipt of the response of subscriber C in step S3 above, the host exchange station 3 disconnects the path between subscribers A and B, and establishes the paths 5, 6, and 7 between the multiple subscriber communications trunk 4 and each of the subscribers A, B, and C (steps S6 and 7).

[6396] Then, the cells transmitted from each of the subscribers A, B, and C are first transferred to the multiple subscriber communications trunk 4, edited there, and then transferred to the destination subscriber. Thus, the 2-subscriber communications state is switched into the 3-subscriber communications state. If the image and sound data transmitted from the multiple subscriber communications trunk 4 can be contained in the band assigned to one subscriber, there is no need for a band check when the 3-subscriber communications state is entered.

[6397] FIG. 854 is a flowchart showing the process of the multiple subscriber communications service in the system shown in FIG. 851. Described below is the procedure of calling up a number of subscribers in a three or more subscriber communications state.

[6398] In the multiple subscriber communications state, one of the communicating subscribers requests to add the n-th subscriber (subscriber N) to the multiple subscriber communications. Upon receipt of the request, the host exchange station 3 checks if the value n is smaller than the number of users who can simultaneously use the multiple subscriber communications trunk 4. That is, the multiple subscriber communications trunk 4 determined whether or not the number of communicators exceeds the maximum value for the multiple subscriber communications (steps S11 and 12).

[6399] If the maximum value for the number of communicators is exceeded, the process of rejecting the request is performed (step S13).

[6400] If the number of the communicators is smaller than the maximum value, the host exchange station 3 calls the subscriber N and selects the VPI/VCI specifying the path between each of the subscriber N and the multiple subscriber communications trunk 4. At this time, the number of subscribers being connected is updated. That is, the number is set to n. Then, the path between each subscriber N and the multiple subscriber communications trunk 4 is established to enter an n-subscriber communications state (steps S14-18).

[6401] FIG. 855 is a flowchart showing the process of the multiple subscriber communications service using a group identification number. Described below is the case where any subscriber (subscriber D) issues a request for multiple subscriber communications. The multiple subscriber communications service is given to a group of preliminarily designated subscribers, and a group identification number is assigned to each group. The multiple subscriber communications trunk 4 is assigned to the multiple subscriber communications of each group.

[6402] When the host exchange station 3 receives a special number of the multiple subscriber communications service request and a group identification number from a subscriber, it determines whether or not the multiple subscriber communications are being performed in a group designated by the group identification number (steps S21 and 22).

[6403] If the multiple subscriber communications are performed in a group, the host exchange station 3 recognizes the multiple subscriber communications trunk 4 which provides the multiple subscriber communications service, and checks whether or not the number of the communicators exceeds the maximum value for the multiple subscriber communications trunk 4 when one communicator is added to the currently communicating subscribers (step S23).

[6404] Unless the maximum value is exceeded, control is passed to step S26. If it is exceeded, then the process of rejecting the request is performed (step S24).

[6405] When it is determined in step S22 that the multiple subscriber communications are not performed in the group, the multiple subscriber communications trunk 4 in an idle state is obtained, and control is passed to step S26 (step S25).

[6406] The host exchange station 3 selects the VPI/VCI specifying the path between the subscriber D requesting the multiple subscriber communications in step S21 and the multiple subscriber communications trunk 4. At this time, the number of subscribers being connected is updated. Then, a bath is established between the subscriber D and the multiple subscriber communications trunk 4. Thus, any subscriber can take part in the multiple subscriber communications in a specific group (steps S26 through 28).

[6407] FIG. 856 shows the flowchart of the process in the 3-subscriber communications service in the system shown in FIG. 852. In this system, a path is established between the multiple termination unit 11 in the subscriber circuit and each subscriber. The process order is fundamentally the same as that shown in FIG. 853.

[6408] FIG. 857 is a flowchart showing the multiple subscriber communications service in the system shown in FIG. 852. In this system, a path is established between the multiple termination unit 11 in the subscriber circuit and the newly called subscriber. The process order is fundamentally the same as that shown in FIG. 854.

[6409] FIG. 858 is a flowchart of the call waiting service in the system shown in FIG. 851. In this example, subscriber C (the third party) issues a connection request to subscriber A while the two-subscriber communications are performed between subscribers A and B.

[6410] Upon receipt of a connection request from subscriber C to subscriber A in the 2-subscriber communications state between subscribers A and B, then the host exchange station 3 selects the VPI/VCIs in the range where the multiple subscriber communications trunk 4 is available, and sets new virtual paths between the multiple subscriber communications trunk 4 and each of the subscribers A and C (steps S31-33).

[6411] The host exchange station 3 notifies subscriber A that the connection request has been received from the third party. In response to this, subscriber A determines whether or not he or she requests to communicate with subscriber B again after the communication with the third party (subscriber C).

[6412] When the host exchange station 3 receives a request to communicate with subscriber B again after the communications with the third party, the host exchange station 3 sets subscriber B in a standby state and connects subscriber A with subscriber C through the multiple subscriber communications trunk 4 (steps S34-S38).

[6413] When the host exchange station 3 receives a request to terminate the communications between subscribers A and C from subscriber A or C, the host exchange station 3 releases the virtual paths set between the multiple subscriber communications trunk 4 and subscribers A and C, and connects again subscriber A with subscriber B (steps S39-S41).

[6414] When the host exchange station 3 receives a request to stop the communications with subscriber B after the communications with the third party, it disconnects subscriber B. Then, the host exchange station 3 releases the virtual paths set between the multiple subscriber communications trunk 4 and subscribers A and C, and directly connects subscriber A with subscriber C (steps S34, 42, and 43).

[6415] FIG. 859 is a flowchart (1) of a call transfer service in the system shown in FIG. 851. Described below is the connection made by subscriber A between subscriber B and subscriber C (third party) while subscribers A and B are in the 2-subscriber communications.

[6416] When the host exchange station 3 receives from subscriber A a call transfer request and a call transfer destination information indicating subscriber C, it selects the VPI/VCI identifying the range where the multiple subscriber communications trunk 4 is available, and sets new virtual paths between the multiple subscriber communications trunk 4 and subscribers B and C (steps S51-S54).

[6417] The host exchange station 3 calls subscriber C. If subscriber C returns a response, the host exchange station 3 connects subscriber B with subscriber C through the multiple subscriber communications trunk 4 (steps S55 and S56).

[6418] FIG. 860 is a flowchart (2) of a call transfer service in the system shown in FIG. 851.

[6419] When the host exchange station 3 receives from subscriber A who transfers the call after steps S51-S55 shown in FIG. 859, the host exchange station 3 releases the virtual paths set between the multiple subscriber communications trunk 4 and subscribers B and C to directly connect subscriber B with subscriber C (steps S61-S63).

[6420] According to the system shown in FIG. 859 or 860, a call from subscriber B to subscriber A can be transferred to subscriber C.

[6421] FIG. 861 is a flowchart showing the point-to-multipoint connection service in the system shown in FIG. 851. Described below is the case where subscribers B and C access subscriber A (information providing subscriber).

[6422] When the host exchange station 3 receives a point-to-multipoint connection request from subscriber A, it selects the VPI/VCI in the range where the multiple subscriber communications trunk 4 is available and sets a virtual path between subscriber A and the multiple subscriber communications trunk 4 (steps S71 and S72).

[6423] When the host exchange station 3 receives a connection request from subscribers B and C to subscriber A, it selects two VPI/VCIs in the range where the multiple subscriber communications trunk 4 is available and sets virtual paths between the multiple subscriber communications trunk 4 and subscribers B and C. Afterwards, the point-to-multipoint communications can be established through the multiple subscriber communications trunk 4 (steps S73-S75).

[6424] A multicast transfer can be made from subscriber A to subscribers B and C. In this case, subscriber A specifies subscribers B and C as connection-to information in step S73.

[6425] FIGS. 862 through 865 are flowcharts of various services provided by the system shown in FIGS. 852, and correspond to FIGS. 858 through 861 respectively. In the system shown in FIGS. 862 through 865, the multiple termination unit 11 processes virtual paths.

[6426] According to the above described embodiment, the multiple subscriber communications trunk provided for the exchange station or the multiple termination unit provided in the subscriber line give services such as multiple subscriber communications services, call waiting services, transfer services, etc.

[6427] Described below is another characteristic configurations of the present invention. The configuration corresponds to the 18th object of the present invention previously described in the “Subject to be solved by the Invention”.

[6428] The embodiment described below realizes collecting information about the line processed by a device in the exchange station and a correct change of devices in the exchange station when a failure occurs.

[6429] FIG. 866 shows the configuration of the ATM switch. When an ATM cell is transmitted from a subscriber terminal not shown in FIG. 866, it is switched by a communications line switch (SW) 3 through a terminal equipment 1 and common device 2. common device 2. The terminal equipment 1 and common device 2 are communications line system devices for processing more than one line.

[6430] FIG. 867 is a block diagram showing the present embodiment. In FIG. 867, a subscriber data management unit 4, service management unit 5, line connection control unit 6, device management control unit 7, input/output device management unit 8, and line connection management unit 9 are realized as functions of the control program or firmware executed by a central program (not shown in FIG. 867) for controlling the ATM switching system shown in FIG. 866.

[6431] The terminal equipment 1 and common device 2 are the same as those shown in FIG. 866.

[6432] A main storage device 14 stores a use state table 11, device service management table 12, device service management table 12, and management information table 13. The use state table 11 is accessed by the line connection control unit 6 and stores entries of use states and available bands. The device service management table 12 is accessed by the line connection management unit 9 and provided for each of either terminal equipments 1 or common devices 2. Each of them stores entries of the services used by the terminal equipment 1 or common device 2. The management information table 13 is accessed by the service management unit 5 and stores the identification information (VPI/VCI) of the line used by the user, the device number of the terminal equipment 1 or common device 2 which processes the line, and priority/non-priority information.

[6433] The normal line connection process performed with the above listed configuration is described by referring to the flowchart of the operations shown in FIG. 868. In the following explanation, reference numbers S1-S11 indicate the steps on the flowchart shown in FIG. 868.

[6434] The subscriber data management unit 4 receives a line connection request from a subscriber terminal not shown in FIG. 868 (S1).

[6435] The subscriber data management unit 4 determines the type of service according to the connection request (S2), and outputs a line connection request to the service management unit 5 depending on the determined service type. The service management unit 5 transfers the line connection request to the line connection control unit 6 (S3).

[6436] The line connection control unit 6 inquires the device management control unit 7 which manages each of either terminal equipments 1 or common devices 2 which issued the line connection request of the state of each of either terminal equipments 1 or common devices 2 (S4 and S5).

[6437] As a result, when no device management control unit 7 returned an availability state, the above described line connection request is rejected.

[6438] If any of the device management control units 7 returns an availability state, the line connection control unit 6 compares the request band corresponding to the line connection request with the state of the line (virtual line identified by a VPI/VCI) used by the terminal equipment 1 or common device 2 managed by the device management control unit 7 (S6), and determines whether or not the terminal equipment 1 or common device 2 can accept the line (request line) requesting the above described request band (S7).

[6439] If the terminal equipment 1 or common device 2 cannot accept the request line, the line connection request is rejected.

[6440] If the terminal equipment 1 and common device 2 can accept the above described request line, the line connection control unit 6 connects the request line to the terminal equipment 1 or common device 2 by setting the VPI/VCI identifying the request line in the terminal equipment 1 or common device 2 through the device management control unit 7 which manages them (S8).

[6441] Then, the line connection control unit 6 enters the set line and its available band for the use state table 11 (S9). FIG. 872 shows practical examples of the terminal equipment 1, common device 2, and the use state table 11 in the main storage device 14 in the configuration of the ATM switch. The LLP-A, LLP-B, etc. are line processors, and the SHELF-A1, SHELF-B1, SHELF-B2, etc. are line concentrators. They correspond to the common device 2 shown in FIGS. 866 and 867. T1, T2, etc. are line termination. They correspond to the terminal equipment 1 shown in FIG. 866 or 867. Furthermore, SW is a communications line switch and corresponds to SW3 shown in FIG. 866 or 867.

[6442] As shown in the example above, the use state table 11 stores for each line the entries of the use state and available band.

[6443] Then, the line connection control unit 6 notifies the service management unit 5 which issued the line connection request of the device number of the terminal equipment 1 or common device 2 for which a line is connected.

[6444] Based on the notification, the service management unit 5 enters the identification information (VPI/VCI) of the line used by the subscriber, the device number (point) of the device which processes the line, and the priority/non-priority information (described later) for the management information table 13 in the main storage device 14 managed by the service management unit 5 (S10). FIG. 872 shows an example of the management information table 13.

[6445] Furthermore, the service management unit 5 notifies the line connection management unit 9 of the service information managed by the service management unit 5 and the device number of the terminal equipment 1 or common device 2 notified by the line connection control unit 6. According to the notification, the line connection management unit 9 enters the reported services for the device service management table 12 (shown in FIG. 872) in the main storage device 14 identified by the device number (S11).

[6446] Described below by referring to the flowchart shown in FIG. 869 is the reporting process performed by the configuration shown in FIG. 866 or 867 when a system failure occurs. In the description, the reference numbers S12-S16 refer to the steps in the flowchart shown in FIG. 869.

[6447] First, when the device management control unit 7 receives from the terminal equipment 1 or common device 2 managed by the device management control unit 7 a notification that a failure has been detected (S12), the notification is transferred to the line connection management unit 9.

[6448] The line connection management unit 9 confirms the device service management table 12 in the main storage device 14 corresponding to the reported device number and detects the service, on which a failure has been detected, related to the terminal equipment 1 or common device 2 (S13).

[6449] As a result, the line connection management unit 9 notifies each service management unit 5 managing each of the detected services of the detection of a failure reported by the device management control unit 7 on the terminal equipment 1 or common device 2 (S14).

[6450] After receiving the notification of the detection of the failure from the line connection management unit 9, the service management unit 5 retrieves the identification information (VPI/VCI) of the line using the reported terminal equipment 1 or common device 2 from the management information table 13 (FIG. 872) in the main storage device 14 (S20). The retrieval result is reported to the device management control unit 7 corresponding to the terminal equipment 1 or common device 2 on which the failure has been detected (S15).

[6451] The processes in steps S14 and S15 are repeatedly performed on each of the services associated with the terminal equipment 1 or common device 2 on which the failure has been detected by the line connection management unit 9 in S 13.

[6452] After receiving the identification information (VPI/VCI) of the line from each of the service management units 5 corresponding to each service related to the terminal equipment 1 or common device 2, the device management control unit 7 edits the information that a failure has been detected in the terminal equipment 1 or common device 2 managed by the device management control unit 7 and the identification information (VPI/VCI) of the line reported by the service management unit 5. The result of the edition is transmitted to an input/output device 10 through the input/output device management unit 8 (S16).

[6453] Described below by referring to the flowchart shown in FIGS. 870 and 871 is the automatic line connection switching process performed by the configuration shown in FIG. 866 or 867 when a system failure occurs. In the description, the reference numbers S17-S27 refer to the steps in the flowchart shown in FIG. 870, and the reference numbers S28 and S29 refer to the steps in the flowchart shown in FIG. 871.

[6454] First, when the device management control unit 7 receives from the terminal equipment 1 or common device 2 managed by the device management control unit 7 a notification that a failure has been detected (S17), the notification is transferred to the line connection management unit 9.

[6455] The line connection management unit 9 confirms the device service management table 12 in the main storage device 14 corresponding to the reported device number and detects the service, on which a failure has been detected, related to the terminal equipment 1 or common device 2 (S18).

[6456] As a result, the line connection management unit 9 notifies each service management unit 5 managing each of the detected services of the detection of a failure reported by the device management control unit 7 on the terminal equipment 1 or common device 2 (S19).

[6457] After receiving the notification of the detection of the failure from the line connection management unit 9, the service management unit 5 first confirms that the terminal equipment 1 and common device 2 are processed in the automatic line connection switching process. As a result, the service management unit 5 retrieves the identification information (VPI/VCI) of the line which uses the reported terminal equipment 1 or common device 2 from the management information table 13 (FIG. 872) in the main storage device 14 (S20).

[6458] The service management unit 5 notifies the line connection control unit 6 of the detected line connection change request (S21).

[6459] The system can be designed such that the service management unit 5 retrieves by priority the data with the priority/non-priority information in the management information table 13 and issues by priority the connection change request of the related line.

[6460] Upon receipt of the request, the line connection control unit 6 disconnects the request line from the terminal equipment 1 or common device 2 on which a failure has been detected by deleting the VPI/VCI of the request line from the terminal equipment 1 or terminal equipment 1 through the device management control unit 7 for controlling the terminal equipment 1 or common device 2 on which the failure has been detected. Simultaneously, the line connection control unit 6 deletes the request line and the entry of the available band from the use state table 11 in the main storage device 14. The available band is held as the request band corresponding to the line connection change request. Furthermore, the line connection control unit 6 inquires the device management control unit 7 which manages each of either terminal equipments 1 or common devices 2 of the state of each of other terminal equipments 1 or common devices 2 (S22 and S23).

[6461] As a result, when no device management control unit 7 returned an availability state, the above described line connection request is rejected and the line is disconnected.

[6462] If any of the device management control units 7 returns an availability state, the line connection control unit 6 compares the request band corresponding to the line connection request with the state of the line (virtual line identified by a VPI/VCI) used by the terminal equipment 1 or common device 2 managed by the device management control unit 7 (S24), and determines whether or not the terminal equipment 1 or common device 2 can accept the line (request line) requesting the above described request band (S25).

[6463] If the terminal equipment 1 or common device 2 cannot accept the request line, the line connection request is rejected and the line is disconnected.

[6464] If the terminal equipment 1 and common device 2 can accept the above described request line, the line connection control unit 6 connects the request line to the terminal equipment 1 or common device 2 by setting the VPI/VCI identifying the request line in the terminal equipment 1 or common device 2 through the device management control unit 7 which manages them (S26).

[6465] Then, the line connection control unit 6 enters the set line and its available band for the use state table 11 (S27).

[6466] Next, the line connection control unit 6 notifies the service management unit 5 which issued the line connection request of the device number of the terminal equipment 1 or common device 2 for which a line is connected. Based on the notification, the service management unit 5 retrieves data of the line, for which the connection is changed, in the management information table 13 of the main storage device 14 managed by the service management unit 5, deletes from the data the device number of the terminal equipment 1 or common device 2 on which a failure has occurred, and enters the device number of a new terminal equipment 1 and common device 2 reported by the line connection control unit 6 (S28).

[6467] Furthermore, the service management unit 5 notifies the line connection management unit 9 of the service information managed by the service management unit 5 and the device number of the new terminal equipment 1 or common device 2 notified by the line connection control unit 6. According to the notification, the line connection management unit 9 enters the reported services for the device service management table 12 (shown in FIG. 872) in the main storage device 14 identified by the device number (S29). The line connection management unit 9 deletes the entries of the services corresponding to the service management unit 5 which issued the above notification from the device service management table 12 (FIG. 872) in the main storage device 14 for the terminal equipment 1 or common device 2 on which the failure has been detected.

[6468] The processes in steps S19 and S29 are repeatedly performed on each of the services associated with the terminal equipment 1 or common device 2 on which the failure has been detected by the line connection management unit 9 in S 18.

[6469] Described below is the line connection state output process performed on a specified terminal equipment 1 or common device 2 with the configuration shown in FIG. 866 or 867.

[6470] First, the input/output device 10 issues a line connection state output request to the terminal equipment 1 or common device 2.

[6471] The line connection state output request is transferred to the subscriber data management unit 4 through the input/output device management unit 8. The subscriber data management unit 4 notifies the line connection management unit 9 of the device number of the specified terminal equipment 1 or common device 2.

[6472] The line connection management unit 9 detects a service to which the line connection state output request specified terminal equipment 1 or common device 2 is related by confirming the device service management table 12 in the main storage device 14 corresponding to the reported device number.

[6473] As a result, the line connection management unit 9 instructs each of the service management units 5 for managing each of the detected services to output a line connection state of the specified terminal equipment 1 or common device 2.

[6474] Upon receipt of the instruction, the service management unit 5 retrieves the identification information (VPI/VCI) of the line which uses the specified terminal equipment 1 or common device 2 from the management information table 13 (FIG. 872) in the main storage device 14, and notifies the subscriber data management unit 4 of the retrieval result.

[6475] The subscriber data management unit 4 collects the identification information (VPI/VCI) of the line which uses the specified terminal equipment 1 or common device 2 from all service management units 5 related to the line connection state output request. The collection result is output to the input/output device 10 through the input/output device management unit 8.

[6476] Described below is the line connection switch process performed on a specified terminal equipment 1 or common device 2 with the configuration shown in FIG. 866 or 867.

[6477] First, the input/output device 10 issues a line connection switch request to the terminal equipment 1 or common device 2.

[6478] The line connection switch request is transferred to the subscriber data management unit 4 through the input/output device management unit 8. The subscriber data management unit 4 notifies the line connection management unit 9 of the device number of the specified terminal equipment 1 or common device 2.

[6479] The subsequent processes are the same as the processes in and after step S18 shown in FIG. 870.

[6480] However, if the process of switching to the terminal equipment 1 or common device 2 cannot be successfully performed, the line connection switch request is rejected and the state immediately before the issue of the request is maintained.

[6481] According to the embodiment with the configuration shown in FIG. 866 or 867, the terminal equipment 1 or common device 2 can be preliminarily set such that an automatic line connection switch process can be performed when a failure occurs on a device or such that the occurrence of a failure on a device is first reported to the input/output device 10 and, in response to the report, the maintenance staff performs the line connection switch process by specifying the terminal equipment 1 or common device 2 from the input/output device 10.

[6482] Described below is another characteristic configuration of the present invention. The configuration corresponds to the 19th object previously described under the title “Problems to be solved by the Invention”.

[6483] According to the following embodiment, lines are switched successfully in band (VPI/VCI) units when a failure is detected on a line.

[6484] According to the embodiment, it is assumed that a layer 1 line failure (physical line failure) or a layer 2 line failure (device failure) has been detected when a remote concentrator is connected to an ATM switch through a plurality of physical lines.

[6485] In this case, the communications continue for a non-faulty band (VPI/VCI) in the faulty line. Then, the value of the faulty band in the faulty line is compared with the sum of the idle bands in each of the non-faulty lines.

[6486] If the value of the faulty band is equal to or smaller than the sum of the idle bands in each of the non-faulty lines, the band on which a failure has occurred is reassigned to an idle band in a non-faulty line.

[6487] If the value of the faulty band is larger than the sum of the idle bands in each of the non-faulty lines, the physical line containing the faulty band is physically switched to a spare line as in the conventional methods.

[6488] Described below by referring to the explanatory view in FIG. 873 and the sequence shown in FIG. 874 is the process of reassigning for a faulty band an idle band in a non-faulty line performed when the faulty band value is equal to or smaller than the sum of idle bands in each of the non-faulty lines.

[6489] In this example, the communications continue in the non-faulty band (VPI/VCI) of the faulty lines #x and #y as shown in FIG. 873.

[6490] Information about the priority level of each band is added to the header of an ATM cell communicated through each band. Each band on which a failure has occurred in the faulty lines #x and #y is reassigned to an idle band in a non-faulty line in order of priority level starting with the band through which the cell assigned the highest priority level is communicated.

[6491] A band on which a failure has occurred is not reassigned to a non-faulty band in the faulty lines #x and #y.

[6492] FIG. 874 shows a practical sequence of reassigning processes.

[6493] That is, a line failure is detected when an ATM cell is communicated between the line termination connected to the ATM switch and the line termination connected to the remote concentrator (S1).

[6494] In this case, a line failure is detected for each layer in each Vcc control device (S3) by communicating a failure detection signal, a response signal to the failure detection signal, and a signal relating to a performance monitor between the Vcc control device in the ATM switch and the Vcc control device in the remote concentrator (S2). The Vcc control device controls the VPI/VCI identifying each band (virtual line or a connection) in a physical line.

[6495] As a result, each of the bands on which a failure has occurred is reassigned to an idle band in a non-faulty line between the Vcc control device in the ATM switch and the line termination in the ATM switch and between the VCC control device in the remote concentrator and the line termination in the remote concentrator. These reassigning processes are fundamentally the same as shown in S4-S13 in FIG. 874. Therefore, the restrictions are not placed between the ATM switch and remote concentrator hereinafter, but the processes are described as those between the Vcc control device and the line termination.

[6496] First, the Vcc control device stops the process of monitoring the occurrence of a failure (S4).

[6497] Then, between the Vcc control device and line termination, communications are made to confirm the start of the reassignment process for a faulty band (S5).

[6498] The Vcc control device starts buffering the ATM cells input from the line termination to the Vcc control device (S6). In the buffering process, the cells input from the line termination are buffered in the buffer of the Vcc control device according to the priority level as shown in FIG. 877. The information indicating the priority level is added to, for example, a cell loss priority (CLP) bit in the header field of each ATM cell as described above. An ATM cell using the same band is assigned the same priority level information. The buffering process prevents the ATM cell input from the line termination during the reassignment process for a faulty band from being discarded. FIG. 878 shows an example of assigning a priority level.

[6499] Next, the Vcc control device checks the faulty bands in the faulty lines and the idle bands in each of the non-faulty lines (S7). As a result, the Vcc control device determines that the value of the faulty bands is equal to or smaller than the sum of the idle bands in each of the non-faulty lines.

[6500] Then, the Vcc control device sequentially performs the processes in the following steps S8-S11 on the faulty bands in a faulty line in order of priority level starting with the band through which the information assigned the highest priority level is communicated.

[6501] That is, the Vcc control device first deletes the settings of the VPI/VCI for a faulty band on the table of the device (S8).

[6502] Next, the Vcc control device resets the VPI/VCI for the idle band in an appropriate non-faulty line (S9).

[6503] The Vcc control device sweeps to the line termination the ATM cell buffered in the buffer of the Vcc control device according to the current priority levels (S10), and releases the cell buffering process (S11).

[6504] After performing the processes in S8-S11 according to the priority levels, the Vcc control device resumes the process of monitoring the occurrence of failures (S12).

[6505] Finally, the communications are made between the Vcc control device and the line termination to confirm the termination of the reassignment process for a faulty band (S13).

[6506] According to the above listed sequence, a band on which a failure has occurred is reassigned to an idle band in a non-faulty line when the value of the faulty band is equal to or smaller than the sum of the idle bands in each of the non-faulty lines.

[6507] Described below by referring to the explanatory view in FIG. 875 and the sequence shown in FIG. 876 is the process of reassigning for a faulty band an idle band in a non-faulty line performed when the faulty band value is larger than the sum of idle bands in each of the non-faulty lines.

[6508] As shown in FIG. 875, each of the bands on which failures have occurred in the faulty line #x is sequentially reassigned to a band which has recovered from a failure in the spare line #z in order of priority level starting with the faulty band in which the ATM cell assigned the highest priority level information is communicated.

[6509] FIG. 876 shows a practical sequence.

[6510] First, the processes in S1-S6 shown in FIG. 876 are the same as those in S1-S6 shown in FIG. 874.

[6511] After the processes in S1-S6, the Vcc control device checks the faulty bands in the faulty lines and the idle bands in each of the non-faulty lines (S7). As a result, the Vcc control device determines that the value of the faulty bands is equal to or smaller than the sum of the idle bands in each of the non-faulty lines.

[6512] Then, the Vcc control device sequentially performs the processes in the following steps S8-S11 on the faulty bands in a faulty line in order of priority level starting with the band through which the information assigned the highest priority level is communicated.

[6513] That is, the Vcc control device first deletes the settings of the VPI/VCI for a faulty band on the table of the device (S8).

[6514] Next, the Vcc control device resets on the table of the device the VPI/VCI for the idle band in a spare line (S9).

[6515] The Vcc control device sweeps to the line termination the ATM cell buffered in the buffer of the Vcc control device according to the current priority levels (S10), and releases the cell buffering process (S11).

[6516] After performing the processes in S8-S11 according to the priority levels, the Vcc control device resumes the process of monitoring the occurrence of failures (S12).

[6517] Finally, the communications are made between the Vcc control device and the line termination to confirm the termination of the switch from the faulty line to the spare line (S13).

[6518] According to the above listed sequence, the faulty lines are switched to the spare lines when the value of the faulty band is larger than the sum of the idle bands in each of the non-faulty lines.

[6519] According to the above described embodiment, each of the processes of reassigning a band or switching lines is sequentially performed in order from the highest priority level of the band. However, the processes can be performed in order of service of each band.

[6520] Described below is another characteristic configuration of the present invention. The configuration corresponds to the 20th object previously described under the title “Problems to be solved by the Invention”.

[6521] In the embodiment described below, it is assumed that a line failure has been detected when a remote concentrator is connected to a host switch (ATM switch) through a plurality of physical lines as in the above described embodiment. A practical technology is provided to switch lines in the event of the line failure.

[6522] FIG. 879 shows the configuration of the system in which a remote concentrator 1 is connected to a host switch 2 as the basic components of the present embodiment. The remote concentrator 1 is equipped with a plurality of microprocessors (μP) 4. Controlling the microprocessor 4 by a call processor (CPR) 3 in the host switch 2 allows the path from the subscriber accommodated by the remote concentrator 1 to the host switch 2 and the path from the host switch 2 to the subscriber accommodated by the remote concentrator 1 to be properly controlled.

[6523] FIG. 880 shows the common principle of the ATM switch system related to the present embodiment. A virtual path identifier (VPI) and a virtual channel identifier (VCI) which identify the virtual line through which an ATM cell is transmitted are added to the header of the ATM cell. An input multiplexing unit (MUX) 5 has a VCC table 7 on which its contents are set by a microprocessor (μp) 6. When an ATM cell having VPI=AA and VCI=BB is input to the MUX 5, the MUX 5 retrieves VPI=XX and VCI=YY at the output terminal and a self-routing tag #4 by retrieving the address (AA.+BB.) corresponding to the above described VPI=AA and VCI=BB, Then, it converts the VPI and VCI of the ATM cell into XX and YY, adds the tag #4 to the head of the ATM cell, and transfers the ATM cell to a switch unit 8. The hardware switch in the switch unit 8 autonomously switches the ATM cell according to the tag #4 added to the head of the transferred cell and outputs the ATM cell to the route #4 at the output terminal. The MUX unit at the next stage not shown in FIG. 880 performs the similar switching operation according to the VPI=XX and VCI=YY added to the ATM cell.

[6524] FIG. 881 shows the position where the VCC table is accommodated for use by the upward path from the remote concentrator 1 to the host switch 2 in the system in which the remote concentrator 1 is connected to the host switch 2 (HOST 2) shown in FIG. 879. The first upward VCC table is provided in the MUX (multiplexing device) in the remote concentrator 1 for multiplexing the ATM cell from the subscriber accommodated by the remote concentrator 1. The second upward VCC table is provided in the MUX of the host switch 2 for multiplexing the ATM cell from the remote concentrator 1. For example, the VPI and VCI of the ATM cell of the subscriber input from the #a line accommodated by the remote concentrator 1 are converted into the values AAAA and BBBB for the route #1 from the remote concentrator 1 to the host switch 2 according to the principle as shown in FIG. 880 and first upward VCC table. The tag #1 for the route #1 is added to the head of the ATM cell. As a result, the ATM cell is output to the route #1 from the remote concentrator 1 to the host switch 2. Next, the VPI and VCI of the ATM cell input from the route #1 to the host switch 2 are converted into the values XXXX and YYYY for the route #A output from the host switch 2 according to the second upward VCC table. The tag #A for route #A is added to the head of the ATM cell. As a result, the ATM cell is switched in the host switch 2 and output to the route #A.

[6525] FIG. 882 shows the position where the VCC table is accommodated for use by the downward path from the host switch 2 (HOST 2) to the remote concentrator 1 in the system in which the remote concentrator 1 is connected to the host switch 2 (HOST 2) shown in FIG. 879. The first downward VCC table is provided in the MUX (multiplexing device) in the host switch 2 for multiplexing the ATM cell from another host switch connected to the HOST 2 or the subscriber. The second downward VCC table is provided in the MUX of the remote concentrator 1 for multiplexing the ATM cell from the host switch 2. For example, the VPI and VCI of the ATM cell input from the other host switch or subscriber are converted into the values AAAA and BBBB for the route #1 from the host switch 2 to the remote concentrator 1 according to the principle as shown in FIG. 880 and first downward VCC table. The tag #1 for the route #1 is added to the head of the ATM cell. As a result, the ATM cell is output to the route #1 from the host switch 2 to the remote concentrator 1. Next, the VPI and VCI of the ATM cell input from the route #1 to the remote concentrator 1 are converted into the values XXXX and YYYY for the route #a output from the remote concentrator 1 according to the second downward VCC table. The tag #a for route #a is added to the head of the ATM cell. As a result, the ATM cell is output from the remote concentrator 1 to the route #a.

[6526] FIGS. 883 through 885 show the first process example of reassigning a path when a failure occurs according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[6527] FIG. 883 is a flowchart showing the path connecting operations performed by the call processor 3 in the host switch 2, the microprocessor 4 in the remote concentrator 1, and the microprocessor not shown in FIG. 883.

[6528] When a request is issued to connect a bus between the remote concentrator 1 and host switch 2 (yes in determination in S1), the bands of a normal route and a spare route, and a VPI and VCI are reserved for each of the first upward VCC table, second upward VCC table, first downward table, and second downward table (S2). Simultaneously, normal VCC data and reassignment VCC data shown in FIG. 884 are generated. The normal VCC data is transmitted through the normal route and the reassignment VCC data is transmitted through the spare route. A set of the normal and reassignment VCC data is generated for each of the first upward VCC table, second upward VCC table, first downward table, and second downward table.

[6529] Then, only the corresponding normal VCC data is set in the first upward VCC table and the first downward VCC table while the corresponding normal VCC data and reassignment VCC data are set in the second upward VCC table and second downward VCC table (S3).

[6530] As a result, ATM cells are transmitted through the normal route according to the normal VCC data when no error occurs. Unless an ATM cell flows from the route for the reassignment VCC data from the remote concentrator 1 to the host switch 2 with the VPI/VCI set corresponding to the route, the reassignment VCC data on the second upward VCC table is not referred to. Therefore, there are no problems if the reassignment VCC data is preliminarily set on the second upward VCC table. Likewise, unless an ATM cell flows from the route for the reassignment VCC data from the host switch 2 to the remote concentrator 1 with the VPI/VCI set corresponding to the route, the reassignment VCC data on the second downward VCC table is not referred to. Therefore, there are no problems if the reassignment VCC data is preliminarily set on the second downward VCC table.

[6531] FIG. 885 is a flowchart showing the path reassigning operations performed when a failure occurs by the call processor 3 in the host switch 2, the microprocessor 4 in the remote concentrator 1, and the microprocessor not shown in FIG. 883.

[6532] First, a route (transmission line) in which a failure occurs is specified, and the path which uses the faulty route is extracted as a path to be reassigned (S4). In this process, tag information corresponding to the faulty route is detected in each VCC table, and the address (input VPI/VCI) at which the tag information is set is extracted.

[6533] Then, for all paths to be reassigned, corresponding reassignment VCC data (FIG. 884) is set on the first upward VCC table and a clock VCC table 7.

[6534] As a result, the faulty route is disconnected and an ATM cell is transmitted through a spare route according to the reassignment VCC data. At this time, an ATM cell flows from the route for the reassignment VCC data from the remote concentrator 1 to the host switch 2 with the VPI/VCI set corresponding to the route, and the reassignment VCC data preliminarily-set on the second upward VCC table is referred to. Likewise, an ATM cell flows from the route for the reassignment VCC data from the host switch 2 to the remote concentrator 1 with the VPI/VCI set corresponding to the route, and the reassignment VCC data preliminarily set on the second downward VCC table is referred to.

[6535] FIGS. 886 through 889 show the second process example of reassigning a path when a failure occurs according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[6536] According to the above described first process example, only the corresponding normal VCC data is set in the first upward VCC table and the first downward VCC table while the corresponding normal VCC data and reassignment VCC data are set in the second upward VCC table and second downward VCC table. According to the second process example, the corresponding normal VCC data and reassignment VCC data are set also in the first upward VCC table and the first downward VCC table. Simultaneously, a select bit indicating the data referred to at the address as the normal VCC data or assignment VCC data is added to each address on the first upward VCC table and the first downward VCC table.

[6537] FIG. 886 shows the contents of the first upward VCC table and the second upward VCC table when no failure occurs.

[6538] Since the value of the select bit corresponding to the #a line is 0 on the first upward VCC table, the normal VCC data is referred to as VCC data. Therefore, the VPI and VCI of an ATM cell from the subscriber input through the #a line accommodated in the remote concentrator 1 are converted into the values AAAA and BBBB of the route #1 from the remote concentrator 1 to the host switch 2 according to the principle shown in FIG. 880. The tag #1 for the route #1 is added to the head of the ATM cell. As a result, the ATM cell is output to the route #1 from the remote concentrator 1 to the host switch 2.

[6539] At address AA.+BB on the second upward VCC table, the normal VCC data is stored for use when the ATM cell having VPI=AA and VCI=BB is received through the route #1. At address CC.+DD on the second upward VCC table, the assignment VCC data is stored for use when the ATM cell having VPI=CC and VCI=DD is received through the route #4. VPI=AAAA and VCI=BBBB added to the ATM cell input to the host switch 2 through the route #1 are converted into XXXX and YYYY for the route #A output from the host switch 2 by the normal VCC data stored at address AA.+BB on the second upward VCC table. The tag #A for the route #A is added to the head of the ATM cell. As a result, the ATM cell is switched in the host switch 2 and output to the route #A. Since no ATM cells are received from the spare route #4 from the remote concentrator 1 to the host switch 2, the assignment VCC data is not referred to.

[6540] When a failure has occurred, a path can be reassigned as shown in FIG. 887 only by changing the value of the select bit corresponding to the #a line, that is, the path in the faulty route on the first upward VCC table from 0 to 1.

[6541] Since the value of the select bit corresponding to the #a line is 1 on the first upward VCC table, the reassignment VCC data is referred to as VCC data. Therefore, the VPI and VCI of an ATM cell from the subscriber input through the #a line accommodated in the remote concentrator 1 are converted into the values CCCC and DDDD of the route #4 from the remote concentrator 1 to the host switch 2 by the corresponding assignment VCC data on the first upward VCC table according to the principle shown in FIG. 880. The tag #4 for the route #4 is added to the head of the ATM cell. As a result, the ATM cell is output to the route #4 from the remote concentrator 1 to the host switch 2.

[6542] VPI=CCCC and VCI=DDDD added to the ATM cell input to the host switch 2 through the route #4 are converted into XXXX and YYYY for the route #A output from the host switch 2 by the assignment VCC data stored at address CC.+DD on the second upward VCC table. The tag #A for the route #A is added to the head of the ATM cell. As a result, the ATM cell is switched in the host switch 2 and output to the route #A.

[6543] FIG. 888 shows the contents of the first downward VCC table and the second downward VCC table when no failure occurs.

[6544] Since the value of the select bit is 0 on the first downward VCC table, the normal VCC data is referred to as VCC data. Therefore, the VPI and VCI of an ATM cell from another host switch or the subscriber are converted by the corresponding normal VCC data in the first downward VCC table into the values AAAA and BBBB of the route #1 from the host switch 2 to the remote concentrator 1 according to the principle shown in FIG. 880. The tag #1 for the route #1 is added to the head of the ATM cell. As a result, the ATM cell is output to the route #1 from the host switch 2 to the remote concentrator 1.

[6545] At address AA.+BB on the second downward VCC table, the normal VCC data is stored for use when the ATM cell having VPI=AA and VCI=BB is received through the route #1. At address CC.+DD on the second upward VCC table, the assignment VCC data is stored for use when the ATM cell having VPI=CC and VCI=DD is received through the route #4. VPI=AAAA and VCI=BBBB added to the ATM cell input to the remote concentrator 1 through the route #1 are converted into XXXX and YYYY for the route #A output from the remote concentrator 1 by the normal VCC data stored at address AA.+BB on the second downward VCC table. The tag #a for the route #a is added to the head of the ATM cell. As a result, the ATM cell is output from the remote concentrator 1 to the route #a. Since no ATM cells are received from the spare route #4 from the host switch 2 to the remote concentrator 1, the assignment VCC data is not referred to.

[6546] When a failure has occurred, a path can be reassigned as shown in FIG. 889 only by changing the value of the select bit corresponding to the path on the faulty route on the first downward VCC table from 0 to 1.

[6547] As a result, the assignment VCC data is referred to as VCC data corresponding to the path contained in the faulty route on the first downward VCC table. Therefore, the VPI and VCI of an ATM cell from another host switch or the subscriber are converted into the values CCCC and DDDD of the route #4 from the host switch 2 to the remote concentrator 1 by the corresponding assignment VCC data on the first downward VCC table according to the principle shown in FIG. 880. The tag #4 for the route #4 is added to the head of the ATM cell. As a result, the ATM cell is output to the route #4 from the host switch 2 to the remote concentrator 1.

[6548] VPI=CCCC and VCI=DDDD added to the ATM cell input to the host switch 2 through the route #4 are converted into XXXX and YYYY for the route #a output from the remote concentrator 1 by the assignment VCC data stored at address CC.+DD on the second downward VCC table. The tag #a for the route #a is added to the head of the ATM cell. As a result, the ATM cell is output from the remote concentrator 1 to the route #a.

[6549] FIGS. 890 through 893 show the third process example of reassigning a path when a failure occurs according to the embodiment based on the configuration shown in FIGS. 879, 881, and 882.

[6550] In this process example, the configuration shown in FIGS. 879, 881, and 882 is designed, for example, as shown in FIG. 890, to comprise a protection line (P-line) which is a spare route exclusively for use in the event of a failure.

[6551] In this example, the second upward VCC table and second downward VCC table are divided for a normal route and a protection line respectively as shown in FIGS. 890 through 893, and controlled by separate microprocessors 4 (FIG. 879).

[6552] The contents of the first upward VCC table and second upward VCC table when no failure is detected are, for example, shown in FIG. 890. That is, the contents of the first upward VCC table and second upward VCC table for the normal route are the same as those shown in FIG. 881, and the second upward VCC table is blank.

[6553] As a result, the upward routing when no failure is detected is the same as that shown in FIG. 881.

[6554] If a failure has occurred, the contents of the tag for the #a line which is the path on the faulty route on the first upward VCC table are converted from the value #1 for the route #1 into the value #4 for the route #4 which is a protection line as shown in FIG. 891. Then, the VCC data for the path on the faulty route on the second upward VCC table for a normal route is copied to the second upward VCC table for a protection line. Thus, the path reassigning process can be completed.

[6555] As a result, the VPI and VCI of an ATM cell of the subscriber input through the #a line accommodated by the remote concentrator 1 are converted into the values AAAA and BBBB by the corresponding VCC data on the first upward VCC table according to the principle shown in FIG. 880. The tag #4 for the route #4, which is a protection line, is added to the head of the ATM cell. Accordingly, the ATM cell is output to the route #4, that is, the protection line from the remote concentrator 1 to the host switch 2.

[6556] VPI=AAAA and VCI=BBBB added to the ATM cell input from the route #4, that is, a protection line, to the host switch 2 are converted into the values XXXX and YYYY for the route #A output from the host switch 2 by the VCC data stored at address AA.+BB on the second upward VCC table for a protection line. The tag #A for the route #A is added to the head of the ATM cell. As a result, the ATM cell is switched in the host switch 2 and output to the route #A.

[6557] The contents of the first downward VCC table and second downward VCC table when no failure is detected are, for example, shown in FIG. 892. That is, the contents of the first downward VCC table and second downward VCC table for the normal route are the same as those shown in FIG. 882, and the second downward VCC table is blank.

[6558] As a result, the downward routing when no failure is detected is the same as that shown in FIG. 882.

[6559] If a failure has occurred, the contents of the tag for the path on the faulty route on the first downward VCC table are converted from the value #1 for the route #1 into the value #4 for the route #4 which is a protection line as shown in FIG. 893. Then, the VCC data for the path on the faulty route on the second downward VCC table for a normal route is copied to the second downward VCC table for a protection line. Thus, the path reassigning process can be completed.

[6560] As a result, the VPI/VCI of the ATM cell input from another host switch or subscriber are converted into the values AAAA and BBBB by the corresponding VCC data on the first downward VCC table according to the principle shown in FIG. 880. The tag #4 for the route #4, which is a protection line, is added to the head of the ATM cell. Accordingly, the ATM cell is output to the route #4, that is, the protection line from the host switch 2 to the remote concentrator 1.

[6561] VPI=AAAA and VCI=BBBB added to the ATM cell input from the route #4, that is, a protection line, to the remote concentrator 1 are converted into the values XXXX and YYYY for the route #a output from the remote concentrator 1 by the VCC data stored at address AA.+BB on the second downward VCC table for a protection line. The tag #a for the route #a is added to the head of the ATM cell. As a result, the ATM cell is output from the remote concentrator to the route #a.

[6562] According to the above described embodiment, each of the second upward VCC table and second downward VCC table is divided for use with the normal route and protection line and controlled by a separate microcomputer. However, the VCC table for the normal route and the VCC table for the protection line can be controlled by a single microcomputer to realize the above described function.

[6563] Unlike the above described embodiment in which the contents of the tag for the path on the faulty route of the first upward VCC table or the first downward VCC table are rewritten, the ATM cell to which a tag for the faulty route is added can be designed to be output to the route functioning as protection line in hardware.

[6564] According to the above described embodiment, a path can be correctly reassigned in a short time when a failure occurs by preliminarily setting a path for a spare route in addition to the normal route when a path is connected between the remote concentrator 1 and host switch (HOST) 2.

[6565] Described below is another characteristic configuration of the present invention. The configuration corresponds to the 21st object previously described under the title “Problems to be solved by the Invention”.

[6566] An intra-station device such as a VCC control device, etc. comprising a microprocessor containing the VCC table shown in FIG. 880 should be normally duplexed to guarantee the reliability in communications. When a failure occurs in the intra-station device of the active system, various communications control data set in the device are transferred to the inter-station device of the spare system. Then, the operations of the intra-station device which has been a device in the active system are stopped and simultaneously the operations of the intra-station device which has been a device in the spare system are started as a device in a new active system. In the above described example of the VCC control device, the contents of the VCC table contained therein should be transferred to the VCC control device of the spare system.

[6567] Described below is an embodiment of the transfer process correctly and quickly.

[6568] FIG. 894 shows the configuration of the embodiment of the VCC control device having the above described high-speed table data transferring function.

[6569] In FIG. 894, a cell header address conversion circuit 1 converts a cell header of m-bit×n-word size into a size of m×n bit=1 word.

[6570] A VCC table 2 stores a new cell header comprising an output VPI/VCI and a tag at each address for the input VPI/VCI of the cell header of each input cell as described by referring to FIG. 880. If parallel data is input from the cell header address conversion circuit 1, the VCC table 2 outputs a new cell header for the parallel data.

[6571] A various timing generation circuit 3 controls various access to the VCC table 2 when a cell is input, data is read/written by a microprocessor, a table is initialized, or data is copied between systems, etc.

[6572] A delay circuit 4 delays the transfer of input cell data by the process time required for the reassignment of the cell header of the input cell data.

[6573] A cell header insertion control circuit 6 converts the cell header of cell data input from the destination terminal into a new cell header output from the VCC table 2.

[6574] An inter-system copy control circuit 5 controls a process of copying table data of the VCC table 2 in the VCC control device of the system (active system) containing the inter-system copy control circuit 5 to the VCC table 2 in the VCC control device of another system (spare system).

[6575] A table data setting circuit 7 controls processes of reading and writing table data from the microprocessor (for example, the microprocessor 46 shown in FIG. 880) not shown in the attached drawings to the VCC table 2.

[6576] First, the input cell data is input at a timing shown in FIG. 895A.

[6577] The cell header address conversion circuit 1 outputs the cell header in the input cell data as parallel data of m×n bits=1 word at a timing shown in FIG. 895B.

[6578] The parallel data is input to the VCC table 2 according to the timing data output by the various timing generation circuit 3 at the timing shown in FIG. 895C. The VCC table 2 outputs a new cell header at the timing shown in FIG. 895D.

[6579] The new header is latched in the cell header insertion control circuit 6 at the timing shown in FIG. 895E.

[6580] The input cell passing through the cell header address conversion circuit 1 is delayed in the delay circuit 4 and input to the cell header insertion control circuit 6 at the timing shown in FIG. 895F, that is, the timing shown in FIG. 895E.

[6581] The cell header insertion control circuit 6 converts the cell header of the cell input through the delay circuit 4 into a new cell header output from the VCC table 2 and outputs a new output cell header to the ATM switch not shown in the figures at the timing shown in FIG. 895G.

[6582] FIG. 896A shows the timing of accessing the VCC table by the microprocessor.

[6583] The address data for use in accessing the VCC table 2 is set by the microprocessor at the table data setting circuit 7 as the VCC table setting data at the timing shown in FIG. 896A(a).

[6584] Based on the data, the various timing generation circuit 3 outputs the access timing data through the delay circuit 4 different from the access timing data through an input cell output at the timing shown in FIG. 896A(b) to the VCC table 2 at the timing shown in FIG. 896A(c). Synchronously, the table data setting circuit 7 outputs address data to the VCC table 2 at the timing shown in FIG. 896A(d).

[6585] The table data setting circuit 7 writes the table data transferred from the microprocessor to the VCC table 2 at the timing shown in FIG. 896A(e), reads the table data from the VCC table 2, and transfers the data to the microprocessor.

[6586] FIG. 896B shows the timing of copying VCC table data between systems.

[6587] If the inter-system copying is carried out, the various timing generation circuit 3 outputs the inter-system copy timing data different from the access timing data through an input cell and the access timing data through the microprocessor output at the timing shown in FIGS. 896B(a) and (b) to the VCC table 2 at the timing shown in FIG. 896B(c). Synchronously, the inter-system copy control circuit 5 outputs address data to the VCC table 2 at the timing shown in FIG. 896B(d).

[6588] As a result, the table data is output from the VCC table 2 to the inter-system copy control circuit 5 at the timing shown in FIG. 896B(e).

[6589] The inter-system copy control circuit 5 latches the table data output from the VCC table 2, converts the table data into serial data, and outputs the serial data to the VCC control device in another device in synchronism with the clock of the home system generated by the VCC control device in the home system in which the inter-system copy control circuit 5 is built.

[6590] The inter-system copy control circuit 5 in the VCC control device of the mate system not shown in the attached drawings latches the serial data, converts the data into parallel data in synchronism with the clock of the mate system generated by the VCC control device of the mate system, and writes the parallel data to the VCC table 2 of the VCC control device of the mate system.

[6591] In the configuration of the above described embodiment, the inter-system copy control circuit 5 preliminarily stores a series of address data for the VCC table 2 from the microprocessor 4, and sequentially designates the data for the VCC table 2 when the inter-system copy is carried out.

[6592] The table data of the VCC table 2 output from the inter-system copy control circuit 5 of the home system to the inter-system copy control circuit 5 of the mate system can be parallel data, not serial data.

[6593] When the table data is output from the inter-system copy control circuit 5 of the home system to the inter-system copy control circuit 5 of the mate system, the inter-system copy control circuit 5 of the mate system can easily receive the table data according to the unique clock by adding to the table data the data indicating the start and end of the table data.

[6594] When the table data is output from the inter-system copy control circuit 5 of the home system to the inter-system copy control circuit 5 of the mate system, the inter-system copy control circuit 5 of the mate system can detect and correct errors on the received table data by adding to the table data a parity bit.

[6595] As described above, the hardware table having message identifiers MID as keys according to the present invention allows the routing process to be performed in L2-PDU units using a microcomputer program independent of the hardware without analyzing the L3-PDU. Since it is not necessary to assemble the L3-PDU from the L2-PDU in the routing process, the capacity of the hardware for storing a lot of L2-PDUs can be successfully reduced. Furthermore, applying the above described system to error log collection according to the present invention-logs errors related to the L3-PDU in the L2-PDU process.

[6596] The subscriber can be informed of various transmission quality information (network quality information such as the normality of the transmission line, transmission delay time, etc. between a subscriber terminal unit and an intra-network switch node). The subscriber also evaluate the factor of the deteriorated quality of the entire system from the transmission lines to the terminal units. The procedure is also effective in a packet continuity test performed by a craftsman when a new subscriber is entered or a customer claim is processed.

[6597] In the PVC test according to the present invention, the function of generating and checking test data are provided only in the connectionless communications server, thereby realizing the system at a lower cost. The verification of the PVC improves the reliability of the system, and the algorithm of the present invention shortens the time required to correct errors.

[6598] In the SMDS data normality check system according to the present invention, the process is performed for each L2-PDU, and the hardware configuration for making the check can be simplified, thereby considerably reducing the cost.

[6599] Furthermore, since the data is transmitted to and from the servers for the connectionless process through a private line (highway bus) without performing a switching process at a switch, the band resource for the switch can be effectively used and the resource management involved can be simplified. Thus, the switch can be largely improved in performance.

[6600] According to the present invention, only a specific intra-station device has to be connected to the system bus, which simplifies the wiring in the station and is effective in reducing the cost. Furthermore, reducing the number of devices connected to the system bus also reduces the conflicts for the acquisition of a bus access right, thereby reducing the load on the buss access. A remote device can be controlled by the LAP to maintain the transmission quality and easily recover from a transmission error, even if it occurs, under the error control process. Thus, the intra-station devices can be stably controlled to improve the system performance of the ATM switching system.

[6601] Taking full advantage of the features of the ATM allows the terminal units in the network to be controlled and managed using a simple interface and communications format. The in-slot system through a data highway enables the control information to be transmitted at a high speed.

[6602] The present invention realizes an efficient test within a short time by performing a test cell loopback check, which has been made in a test device, through a test program in the switch. Additionally, transmitting cell data from a test device requires no testing units because the loopback jig can replace the testing units.

[6603] According to the present invention, no test environment should be set (setting testing devices, setting an operator in a standby state, etc.), and the test can be conducted by a simple method of inputting a command, thereby conducting an inter-station test among a plurality of stations. A fault is detected at its earliest stage, and the services and reliability of the ATM switch can be greatly improved.

[6604] According to the present invention, cells in the high-speed highway in the ATM, etc. can be counted with a small-scale hardware. The features, performances, and operation states of the ATM switches, etc. can be determined effectively.

[6605] The present invention also determines the pattern transmission rules and simplifies-the operations and the circuit configuration for realizing the operations.

[6606] In addition to the above listed effects, the present invention successfully reduces the difference in the number of transmission frames.

[6607] The present invention can provide a point-to-multipoint connection ability with which the size of a switching system can be reduced and the system can be easily extended at a lower cost.

[6608] The present invention also provides the point-to-multipoint connection ability without additionally providing a device external to the switch.

[6609] The present invention provides a multicast connection efficiently using the hardware resources.

[6610] Furthermore, the present invention provides call processing capabilities of a multi-terminal connection service such as three-subscriber communications using image data in a broadband communications network.

[6611] The present invention also collects information about the lines processed by an intra-switch device and realizes a correct switch of intra-switch devices in the event of a failure.

[6612] When a failure is detected on a line, the present invention correctly switches the line in band (VPI/VCI) units.

[6613] When a failure is detected on a line and the lines are switched in band (VPI/VCI) units, the present invention can provide a practical technology for switching the lines with the configuration comprising a remote concentrator and ATM exchange.

[6614] Furthermore, the present invention correctly and quickly transfers various communications control data set in an intra-station device of an active system to the intra-station device of a spare system.

Claims

Certificate of Correction present

The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.

What is claimed is:

1. A switching system provided in a connectionless communications system for converting a message assigned a destination address into one or more packets, storing the destination in a beginning-of-message (BOM) packet of the packets, and transferring the packets assigned a common message identifier, said system comprising:

determining means for referring to the destination address stored in the BOM packet upon receipt of the BOM packet and determining whether or not the destination of the message refers to a terminal unit accommodated in the switching system which has received the BOM packet;

a first table for retrieving routing information stored in the BOM packet when the destination of the message refers to the terminal unit accommodated in the switching system which has received the BOM packet, and for storing the message identifier set in the BOM packet in association with the routing information;

routing information retrieving means for retrieving the routing information from said first table according to a message identifier set in a continuation-of-message (COM) packet or an end-of-message (EOM) packet in said one or more packets when the COM packet or EOM packet is received;

switching means for switching the COM packet or EOM packet according to the routing information retrieved by said routing information retrieving means;

a second table for storing information designating an output line group having one or more output lines for each switching system provided in said connectionless communications system;

output line determining means for determining an output line group by searching said second table according to the destination address stored in the BOM packet as a key when the destination of the message does not refer to the terminal unit accommodated in the switching system which has received the BOM packet;

a third table for storing the output line group determined by said output line determining means in association with the message identifier of the BOM packet; and

output means for retrieving output line group information from said third table according to a message identifier set in the COM packet or EOM packet in said one or more packets when the COM packet or EOM packet is received, and then outputting the COM packet or EOM packet to a predetermined output line which belongs to the output line group.

2. The switching system according to claim 1, further comprising:

a fourth table storing information for use in developing a group address;

a fifth table storing, in association with the message identifier of the BOM packet, group address development information retrieved from said fourth table according to a group address stored in the BOM packet when the destination address of a received BOM packet refers to the group address stored in said fourth table; and

means for retrieving the group address development information from the fifth table according to the message identifier set in the COM cell or EOM cell when the COM cell or EOM cell is received, and copying the COM packet or EOM packet according to the group address development information.

3. The switching system according to claim 1, further comprising:

buffer means for storing an output packet; and

read control means for controlling a read from said buffer means according to traffic amount for each output line in the output line group.

4. The switching system according to claim 1, further comprising:

discarding means for making a protocol check for each input packet, discarding a protocol-abnormal packet and storing the message identifier set in the protocol-abnormal packet when the input packet is detected as a protocol-abnormal packet, and discarding a packet assigned a stored message identifier.

5. The switching system according to claim 1, further comprising:

pseudo packet generating means for generating and outputting a pseudo EOM packet having the message identifier of a BOM packet when the BOM packet is received but an EOM packet having the message identifier set in the BOM packet is not received within a predetermined time.

6. The switching system according to claim 1, further comprising:

output line assigning means for performing a CRC operation on the destination address and a source address stored in the BOM packet of the message, and for assigning a predetermined output line in the output line group retrieved from said third table according to a value obtained from an operation result.

7. The switching system according to claim 1, further comprising:

band altering means for measuring traffic of each output line and altering a band of each output line according to the traffic.

8. A connectionless communications system having first and second connectionless communications servers respectively for first and second switches for switching fixed-length packets to transmit data between subscribers accommodated in the first and second switches over connectionless communications, and to establish communications by transferring data through permanent virtual circuits (PVC) connecting between each subscriber and the first and second connectionless communications servers, whereby

said first and second connectionless communications servers are connected via a private line;

said first connectionless communications server comprises:

destination determining means for determining whether or not a destination of connectionless communications data from a subscriber accommodated in the first switch is a subscriber accommodated in the second switch; and

transfer means for transferring connectionless communications data to the second connectionless communications server via the private line when the destination of the data refers to a subscriber accommodated by the second switch.

9. An intra-station control device in a switching device for switching cells, comprising:

a counter repeatedly counting a number of cells passing through a switch of the switching device in each first time period;

a calculator calculating a total number of cells counted by said counter in a second time period, the second time period being longer than the first time period, said calculator summing the number of cells counted by said counter in each of the first time periods within the second time period to produce said total number; and

a memory storing the total number of cells calculated by said calculator, wherein the total number of cells stored in said memory is used for calculating a communication bill.

10. The intra-station control device according to claim 9, wherein

said cell count means counts a number of cells passing through the switch for each priority level specified for a cell passing through the switch.

11. The intra-station control device according to claim 9, wherein

said switch for which said cell count means counts the cells is a demultiplexer.

12. The control device according to claim 9, further comprising

discard cell counting means for counting a total number of discarded cells in the predetermined time period, and wherein

the total number of discarded cells counted is stored in said memory.

13. An intra-station control in a switching device for switching cells, comprising:

cell counting means for counting a total number of cells passing through a switch of the switching device in a predetermined time period; and

a memory for storing the total number of cells counted, wherein the total number of cells stored in said memory is used for calculating a communication bill,

wherein said memory comprises first and second storing means, and the total numbers sequentially obtained by said counting means are alternately written in the first and second storing areas.

Patent Citations (33)

Patent	Date	Inventor	Cited By
US4993015	1991-02-01	Fite, Jr.	Applicant
US5170394	1992-12-01	Biber et al.	Applicant
US5251204	1993-10-01	Izawa et al.	Applicant
US5274641	1993-12-01	Shobatake et al.	Examiner
US5278977	1994-01-01	Spencer et al.	Applicant
US5295135	1994-03-01	Kammerl	Examiner
US5331637	1994-07-01	Francis et al.	Applicant
US5339318	1994-08-01	Tanaka et al.	Applicant
US5416842	1995-05-01	Aziz	Examiner
US5550808	1996-08-01	Shimokoshi	Examiner
US5557604	1996-09-01	Usumi et al.	Examiner
US5561662	1996-10-01	Kakuma et al.	Examiner
US5570348	1996-10-01	Holden	Examiner
US5583864	1996-12-01	Lightfoot et al.	Examiner
US5600652	1997-02-01	Kreamer et al.	Examiner
US5602826	1997-02-01	Yoshimura et al.	Examiner
US5638360	1997-06-01	Sugawara	Examiner
US5638364	1997-06-01	Sugita	Examiner
US5742586	1998-04-01	Murakami et al.	Examiner
US5771231	1998-06-01	Watanabe	Examiner
US5940377	1999-08-01	Sakaue et al.	Examiner
US6061330	2000-05-01	Johansson	Examiner
EP347754	1989-12-01		Applicant
EP477553	1992-04-01		Applicant
EP479478	1992-04-01		Applicant
EP482551	1992-04-01		Applicant
EP498967	1992-08-01		Applicant
EP9217014	1992-10-01		Applicant
EP524316	1993-01-01		Applicant
EP552385	1993-07-01		Applicant
EP570630	1993-11-01		Applicant
FR2701618	1994-08-01		Applicant
JP4-87439	1990-07-01		Examiner

Non-Patent Literature (3)

Yokotani T et al: “Bandwidth Allocation for Connectionless Service in Private Networks Bases on ATM Technology” IEICE Transactions on Communications, vol. E77-B, No. 3, (1994).Applicant
Giddy D et al. “An Experimental ATM Network Featuring De-Coupled Modular Control” Communication for Global Users, vol. 1; Dec. 6, 1992.Applicant
Sallbeerg K et al. “ATM Traffic Management at the Initial Deployment of B-ISDN” vol. 71, No.4 Ericsson Review; Jan. 1, 1994.Applicant