NEC Neax 2400 Ipx Fusion Network System Manual

							CHAPTER 2 NDA-24299
Page 6
Revision 1.0
GENERAL
Node
4. Node
A Fusion network consists of the following types of nodes:
 Network Control Node
The Network Control Node, which must be assigned on a Fusion network, manages other nodes on the
network. This node has the Centralized-MAT to collect fault information from other nodes on the network.
Multiple nodes cannot be assigned as a Network Control Node.
 Local Node
All nodes other than the Network Control Node are called Local Nodes. Fault information generated at a
Local Node is sent to the Network Control Node via a Fusion link, allowing the Network Control Node to
collect the fault information. A Fusion network can have a maximum of 16 nodes on the network.
 See
Figure 2-6.
Note:The actual number of nodes varies with system configurations.
 Center Node (for Centralized Billing - Fusion)
This node collects the billing information from other nodes as well as the self-node. For this reason, the
node is called Center Node for Centralized Billing - Fusion. Multiple Center Nodes can be assigned on the
network by specifying the polling destinations, which can be set by the ASYDL command - SYS 1 Indexes
608 through 639. At the Center Node, the user can select “polling destinations” by setting 1 to the FPC of
the corresponding nodes. For more information, see the NEAX2400 IPX Office Data Specification.
Figure 2-6   Maximum System Configuration
N1
N2
N3
N4
N5
N6
N7
N8
N9 N10 N11 N12 N13
 N14
 N15
N16
N: NodeFusion network
A Fusion network can have a maximum of 16 nodes. 
						

							NDA-24299 CHAPTER 2
Page 7
Revision 1.0
GENERAL
Data Memory Configuration
5. Data Memory Configuration
Each node on a Fusion network has the following three kinds of Data Memory:
 Data Memory (DM)
 Local Data Memory (LDM)
 Network Data Memory (NDM) -  Programmable only by the NCN.
When the contents of the NDM are changed at NCN, the new data is automatically copied to the NDM of each
node. The NDM of the NCN functions as primary memory. Figure 2-7 shows how a telephone number change
is performed in a Fusion network.
Figure 2-7   Network Data Memory Note:
The data must be manually transferred with the CBCN command when the Fusion system is
configured for the first time or the system is once initialized at the NCN.
Telephone Number Change 
 
410000     410001 (for self-Node) 
420000     420001 (for Node B) 
430000     430001 (for Node C) 
440000     440001 (for Node D)   
NCN
410000410001
420000420001
430000430001
440000440001
NDM (master)NDM 
NDM 
NDM 
LNLN LN
Node ANode B
Node C
Node D
Centralized 
      MAT
Data Change...
copy copy
copyupdating NDM 
  at each node
TCP/IP
When telephone numbers are changed, the change at the NCN will affect all nodes on the network. In this
figure, data change at Node A is automatically transferred to each node.  
						

							CHAPTER 2 NDA-24299
Page 8
Revision 1.0
GENERAL
Fusion Network Examples
When the NDM (primary) is modified, the new data is automatically copied. See Figure 2-8
Figure 2-8   Network Data Memory Copy
6. Fusion Network Examples
Figure 2-9 and Figure 2-10 show examples of Fusion networks. When incorporating the Fusion system with the
existing CCIS network, connect all nodes via CCIS links.
Note:To connect a CCIS network and Fusion network, use STNs and TELNs respectively.
Figure 2-9   Closed Numbering Fusion-CCIS Network
DMDM DM
LDMLDM
LDM
NDMNDM NDM
(m aster)
Fusion Link
The standard size of each mem ory is as follows:
DM  (Data Mem ory):   4M Bytes
LDM  (Local Data Mem ory): 2M Bytes
N D M  (N etw ork D ata M em ory): 2M  B ytes
Change...
copycopy NCN
LN LN
NCN: Network Control Node       LN: Local Node
430000TELN410000TELN410001TELN420000TELN
  
... ... ... ... ...... ... ... ... ...... ... ... ... ...... ... ... ... ...
STN: 1000 STN: 3000
STN: 1001STN: 2000
  
... ... ... ... ...... ... ... ... ...... ... ... ... ...... ... ... ... ...  
... ... ... ... ...... ... ... ... ...... ... ... ... ...... ... ... ... ...  
... ... ... ... ...... ... ... ... ...... ... ... ... ...... ... ... ... ...
Node ANCN
FPC = 1
LN
Node B
FPC = 2LN
Node C
FPC= 3
C C IS   
Network 
5xxx
FCCS
FCCS
CCIS CCIS [Closed Num bering]
3 xxx : C C IS  fo r N o d e  C  
2 xxx : C C IS  fo r N o d e  B  
1xxx: self-N ode 
4xxxxx: FU SIO N access 
5 xxx : C C IS  a c ce s s fo r 
         C C IS  N e tw o rk
STN: Physical Station Num ber       TELN: Telephone Number     FPC: FUSION Point Code        PC:  Point  Code  (CCIS) 
 PC = 12PC =10
PC = 11
C
C
IS
  
						

							NDA-24299 CHAPTER 2
Page 9
Revision 1.0
GENERAL
Fusion Network Examples
Figure 2-10   Open Numbering Fusion-CCIS Network
[conditions for telephone number digits]
When incorporating the Fusion system with the CCIS network, consider the conditions in Table 2-1 as to the 
available telephone number digits.
Table 2-1 Available Telephone Number Digits
×: Available -: Not available
Note:When the network is Open Numbering, the “digits” in the table above must be the number of “office code
digits + telephone number digits”.
Telephone Number 
CompositionDisplay
Inter-Office 
ServiceMCISMDR
D
termATTCON/
DESKCONCCIS Fusion
4 digits or less   Note 
×× × ×××
4~8digits  Note ×-×-××
9 digits or more  Note -- - --×
430000TELN410000TELN410001TELN
420000TELN
  
. .. ... ... .. . .... .. ... ... .. . .... .. ... ... .. . .... .. ... ... .. . ...
STN: 2000 STN: 2000
STN: 2001STN: 2000
  
. .. ... . .. ... .... .. ... . .. ... .... .. ... . .. ... .... .. ... . .. ... ...
  
. .. ... ... .. . .... .. ... ... .. . .... .. ... ... .. . .... .. ... ... .. . ...
  
. .. ... ... . .. .... .. ... ... . .. .... .. ... ... . .. .... .. ... ... . .. ...
Node A
80 NCN
FPC = 1
LN
Node B
81
FPC = 2LN
Node C
82
FPC= 3
CCIS 
Network 
8x
FCCS
FCCS
CCIS
CCIS
C
CI
S
81: CCIS for Node B 
82: CCIS for Node C 
8x: CCIS access for 
     CCIS Network 
4x...: Fusion access [Open Numbering]
PC = 12PC =10
PC = 11 
						

							CHAPTER 2 NDA-24299
Page 10
Revision 1.0
GENERAL
Tandem Connections via Fusion Link
7. Tandem Connections via Fusion Link
Tandem connections via FCCS-ACIS can be established. In Figure 2-11, STN (A) can place a tandem call via
FCCS-ACIS.
Figure 2-11   Tandem Connections via Fusion Link
430000TELN410000
TELN
  
... ... ... ... ...... ... ... ... ...... ... ... ... ...... ... ... ... ...
STN (B) STN (A)
  
... .. . ... ... ...... .. . ... ... ...... .. . ... ... ...... .. . ... ... ...
LN
Node A
CO
FCCS
Node BNCN
C
OT
Tandem connection FCCS 
ACIS is established.
FCCSACIS
calling party 
						

							NDA-24299 CHAPTER 3
Page 11
Revision 1.0
CHAPTER 3 SYSTEM CONFIGURATION
Fusion systems can be divided into the following two types:
 Fusion system with FCH
 Fusion system without FCH
Note:FCH (Fusion Call Control Handler) : PA-FCHA
This chapter explains the system configuration of each Fusion system.
1. FUSION System without FCH
An example system configuration of Fusion system which does not use a DTI to carry D-channel is shown
below. In this configuration, Fusion link is established between nodes via Ethernet. The DTI card carries B-
channels only in this example. See Figure 3-1 below.
Figure 3-1   FUSION System Configuration without F CH Note:
A maximum of 4 HUBs can be cascaded between the originating node and the incoming node.
(Restriction by operating condition of Ethernet.)
PCI Bus
PCI Bus
Fusion Link TS W /IN TTS W /IN T
MUXMUX
DTIDTI
LANI CPU
CPU 10 Base T
10 Base T M ax. 100m Node ANode B This figure shows a Fusion System  Configuration without FCH.
TSW  (Tim e Division Switch): PH-SW  10
MUX: PH-PC36
LA N I (L A N  Interfa ce ): P Z -P C 19
DTI (Digital Trunk Interface): PA-24DTR
D-channel B-channel
HUB
M ax. 100m
Note
LANI 
						

							CHAPTER 3 NDA-24299
Page 12
Revision 1.0
SYSTEM CONFIGURATION
Fusion System with FCH
2. Fusion System with FCH
2.1 System Configuration
A sample system configuration of Fusion system which uses a DTI to carry D-channel is shown below. In
this configuration, Fusion link is established between nodes via the T1 link. See Figure 3-2 below.
Figure 3-2   Fusion System Configuration with   FCH
PCI Bus
PCI Bus 10 Base T
............
Fusion Link
D/I D/I TSW /INTTSW /INT
MUXMUX
FCH
FCH FCHFCH DTIDTI
HUB
HUB
LANI
LAN I CPU
CPU
10 Base T10 Base T Node ANode B This figure shows a Fusion System Configuration with FCH.
TSW  (Tim e Division Switch): PH-SW  10
HUB: PA-M96
MUX: PH-PC36
LANI (LAN Interface): PZ-PC19
FCH (Fusion Call Control Handler): PA-FCHA
DTI (Digital Trunk Interface): PA-24DTRB-channel / D-channel
ch 0ch 23D-channel (exam ple)
10 Base T 
						

							NDA-24299 CHAPTER 3
Page 13
Revision 1.0
SYSTEM CONFIGURATION
Fusion System with FCH
Note:
When a direct connection is added to the existing Fusion system with FCH card between the two nodes, it
is required to execute Make Busy operation (MB Key ON/OFF) on the FCH cards to prevent from packet
loop.
Figure 3-3   Add a Direct Connection to Fusion System with FCH
On other occasions for adding direct connection (connect cross cable between the HUBs) to the Fusion
network consists of multiple nodes, also perform the MB key ON/OFF operation on just a single FCH card
to prevent from packet loop. See Figure 3-3
When the system applies dual configuration, MB Key ON/OFF operation is to be executed to an FCH card
on each #A/#B side.
2.2 Redundancy of FUSION Link
FCH (PA-FCHA) card handles a Fusion link, occupying one time slot of a frame by D/I function equipped on
the DTI card. In terms of redundancy, Fusion system (with FCH) can have one of the following configurations.
 Redundant Configuration (LANI, HUB, FCH, and DTI)
 Redundant Configuration (HUB, FCH, and DTI)
 Redundant Configuration (FCH and DTI)
 Non Redundant Configuration
FCH
CPU
LANI
HUB
CPU
LANI
DTI DTI
FCH
HUB
DTIFusion Link
1.5M
MB key ON/OFF
Node B Node A
10BASE-T
DTI
Connect the HUBs with a cross cable
DTI : Digital Trunk Interface FCH : Fusion Call Control Handler  LANI : LAN Interface 
						

							CHAPTER 3 NDA-24299
Page 14
Revision 1.0
SYSTEM CONFIGURATION
Fusion System with FCH
Figure 3-4 shows LANI, HUB, FCH, and DTI in a fully redundant configuration. 
Figure 3-4   Redundant Configuration (LANI, HUB, FCH, and DTI)
Figure 3-5 shows HUB, FCH, and DTI in a redundant configuration.
Figure 3-5   Redundant Configuration (HUB, FCH, and DTI)
Figure 3-6 shows FCH and DTI in a redundant configuration.
Figure 3-6   Redundant Configuration (FCH and DTI)
FCH0
FCH1DTIDTI HUB1
....
....
HUB0 CPU#0
CPU#1
10 Base T
10 Base T
to the same route
Redundancy   
LANI#0-A
LANI#0-B
LANI#1-A
LANI#1-B
PCI Bus
FCH
FCHDTIDTI HUB
....
....
HUB LANI#0 CPU#0
PCI Bus
LANI#1 CPU#110 Base T
10 Base T10 Base T10 Base T
10 Base T
to the same route
Redundancy
PCI Bus
FCH
FCHDTIDTI
....
HUB LANI#0 CPU#0
PCI Bus
LANI#1 CPU#110 Base T
10 Base T10 Base T
10 Base T
to the same route
Redundancy 
						

							NDA-24299 CHAPTER 3
Page 15
Revision 1.0
SYSTEM CONFIGURATION
Fusion System with FCH
Figure 3-7   Non-Redundant Configuration
Note:
Be sure that the system configurations shown below are not available. The Node composed of dual-HUB
system cannot apply to the opposite side against a Node with single-HUB configuration.
Figure 3-8   Unavailable System Configurations
PCI Bus
FCHDTI
....
HUB LANI#0
CPU#0
PCI Bus
LANI#1 CPU#110 Base T
10 Base T10 Base T
In this case, no redundancy is taken as to Fusion link.
[Pattern 1]
Node A: CPU=single, HUB=dual, LANI=dual
Node B: CPU=single, HUB=single, LANI=single
[Pattern 2]
Node A: CPU=dual, HUB=dual, LANI=dual
Node B: CPU=single, HUB=single, LANI=single
HUB-B
HUB-A
FCH
FCH
DTI
DTI
DTI
DTI
HUB-A
FCH
FCH
LANI-A
LANI-B
LANI-A
CPU#0CPU#0
10BASE-T
10BASE-T
10BASE-T10BASE-T10BASE-TPCI Bus
PCI Bus PCI Bus10BASE-T
10BASE-T
HUB-B
HUB-A
FCH
FCH
DTI
DTI
DTI
DTI
HUB-A
FCH
FCH
LANI-A
LANI-B
LANI-A CPU#0
CPU#1
CPU#0
10BASE-T
10BASE-T
10BASE-T10BASE-T10BASE-TPCI Bus
PCI Bus PCI Bus
10BASE-T
10BASE-T