NEC Neax 2400 Imx Fusion Network System Manual

							CHAPTER 2 ND-70185 (E)
Page 6
Revision 3.0
GENERAL
Node
4. Node
A Fusion network consists of the following types of nodes:
 Network Control Node
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 Network Control Node are called Local Node. 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 IMX Office Data Specification.
Figure 2-6   Maximum System Configuration
N1
N2
N3
N4
N5
N6
N7
N8
N9 N10 N11 N12 N13N14N15N16
N: NodeFusion network
A Fusion network can have a maximum of 16 nodes. 
						

							ND-70185 (E) CHAPTER 2
Page 7
Revision 3.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 master memory. Figure 2-7 shows how a Telephone Number change
is performed in a Fusion network.
Figure 2-7   Network Data Memory
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 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. 
Centralized
      MAT
Data Change...
copy copy
copyupdating NDM
  at each node
Note
TCP/IP
Note:The data must be manually transferred using the CBCN command when the Fusion system is
configured for the first time or the system is once initialized at the NCN. 
						

							CHAPTER 2 ND-70185 (E)
Page 8
Revision 3.0
GENERAL
Fusion Network Examples
When the NDM (master) is modified, the new data is automatically copied.
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, all nodes must be connected 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
DM
DMDM
LDMLDM
LDM
NDMNDM NDM
(master)
Fusion Link
The standard size of each memory is as follows:
DM (Data Memory):   4M Bytes
LDM (Local Data Memory): 2M Bytes
NDM (Network Data Memory): 2M Bytes
Change...
copycopy NCN
LN LN
NCN: Network Control Node       LN: Local Node
430000TELN410000TELN410001TELN
420000TELN
............................................................
STN: 1000 STN: 3000
STN: 1001STN: 2000
............................................................
........................................................................................................................
Node ANCN
FPC = 1
LN
Node B
FPC = 2LN
Node C
FPC= 3
CCIS 
Network
5xxx
FCCS
FCCS
CCIS CCIS [Closed Numbering]3xxx: CCIS for Node C
2xxx: CCIS for Node B
1xxx: self-Node
4xxxxx: FUSION access
5xxx: CCIS access for
          CCIS Network
STN: Physical Station Number       TELN: Telephone Number     FPC: Fusion Point Code      PC: Point Code (CCIS)PC = 12PC =10
PC = 11
CCIS 
						

							ND-70185 (E) CHAPTER 2
Page 9
Revision 3.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 following conditions as to the 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 -- - --×
430000TELN410000TELN410001TELN420000TELN


............................................................
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
CCIS
81: CCIS for Node B
82: CCIS for Node C
8x: CCIS access for
      CCIS Network
4x...: Fusion access [Open Numbering]
STN: Physical Station Number     TELN: Telephone Number    FPC: Fusion Point Code    PC: Point Code (CCIS)

PC = 12PC =10
PC = 11 
						

							CHAPTER 2 ND-70185 (E)
Page 10
Revision 3.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
430000TELN410000TELN


............................................................
STN (B) STN (A)


............................................................
LN
Node A
CO
FCCS
Node BNCN
COT
Tandem connection FCCS
ACIS is established.
FCCSACIS
calling party 
						

							ND-70185 (E) CHAPTER 3
Page 11
Revision 3.0
CHAPTER 3 SYSTEM CONFIGURATION
Fusion systems can be divided into the following two types:
 Fusion system with FCH
 Fusion system without FCH
Note:Fusion Call Control Handler (FCH): PA-FCHA
This chapter explains the system configuration of each Fusion system.
1. Fusion System without FCH
A sample Fusion system configuration that does not use a DTI to carry D-channel is shown below. In this con-
figuration, the Fusion link is established between nodes using Ethernet. The DTI card carries B-channels only
in this example. Figure 3-1 shows a Fusion System Configuration without FCH.
Figure 3-1   Fusion System Configuration without FCH
PCI Bus
PCI Bus
Fusion Link TSW/INTTSW/INT
MUXMUX
DTI DTI
LANI CPU
CPU 10 Base T
10 Base T Max. 328 ft
Max. 100m Node ANode B This figure shows a Fusion System Configuration without FCH.
TSW (Time Division Switch): PH-SW 10
MUX: PH-PC36
LANI (LAN Interface): PZ-PC19
DTI (Digital Trunk Interface): PA-24DTR
D-channel B-channel
HUB
Max. 328 ft.
Max. 100m
Note
LANI
Note:A maximum of 4 HUBs can be cascaded per route.
Max. 100 mMax. 100 m 
						

							CHAPTER 3 ND-70185 (E)
Page 12
Revision 3.0
SYSTEM CONFIGURATION
Fusion System with FCH
2. Fusion System with FCH
2.1 System Configuration
A sample Fusion system configuration that uses a DTI to carry D-channel is shown below. In this configu-
ration, the Fusion link is established between nodes via the T1 link. Figure 3-2 shows a Fusion system con-
figuration with FCH.
Figure 3-2   Fusion System Configuration with FCH
2.2 Redundancy of Fusion Link
The FCH (PA-FCHA) card handles a Fusion link, occupying one time slot of a frame by D/I function located
on the DTI card. In terms of redundancy, the Fusion system (with FCH) can have one of the following config-
urations.
 Redundant Configuration (LANI, HUB, FCH, and DTI)
 Redundant Configuration (HUB, FCH, and DTI)
 Redundant Configuration (FCH and DTI)
 Non-Redundant Configuration
PCI Bus
PCI Bus 10 Base T
............
Fusion Link
D/I D/I TSW/INTTSW/INT
MUXMUX
FCH
FCH FCHFCH DTIDTI
HUB
HUB
LANI
LANI CPU
CPU
10 Base T10 Base T Node ANode B This figure shows a Fusion System Configuration with FCH.
TSW (Time 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 (example)
10 Base T 
						

							ND-70185 (E) CHAPTER 3
Page 13
Revision 3.0
SYSTEM CONFIGURATION
Fusion System with FCH
In Figure 3-3 LANI, HUB, FCH, and DTI are shown in a fully redundant configuration. This configuration is 
available for Release 3 or later software.
Figure 3-3   Redundant Configuration (LANI, HUB, FCH, and DTI)
In Figure 3-4 HUB, FCH, and DTI are shown in a redundant configuration.
Figure 3-4   Redundant Configuration (HUB, FCH, and DTI)
In Figure 3-5 FCH and DTI are shown in a redundant configuration.
Figure 3-5   Redundant Configuration (FCH and DTI)
FCH0
FCH1DTIDTI HUB1
....
....
HUB0 CPU#0
CPU#1
10 Base T
10 Base T
to the same route
Redundancy n this case, LANI, HUB, FCH, and DTI are composed in a fully redundant configuration. Note that this configuration is available for 
elease 3 or later software.
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
In this case, HUB , FCH, and DTI are composed in a redundant configuration.
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 In this case, FCH and DTI are composed in a redundant configuration. 
						

							CHAPTER 3 ND-70185 (E)
Page 14
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
In Figure 3-6, no redundancy is shown in the Fusion link.
Figure 3-6   Non-Redundant Configuration
3. System Considerations
3.1 Fusion Network Conditions
This section explains how to design a Fusion network. In the following diagram, a Fusion Link is printed
in a thick line while a CCIS link is printed in a dotted line.
Condition 1: The maximum number of nodes on a Fusion network is sixteen (16) nodes.
Figure 3-7   Fusion Network Topologies
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.
23
1
4
Node A     Node B     Node D     Node C
Node A     Node D     Node C
Node A     Node B     Node C
Node A     Node C
21Node D     Node A     Node B     Node C
Node D     Node B      Node C

2
3
4
Node ANode B
Node B
Node B
Node B
Node CNode C
Node DNode D
Node ANode A
Node ENode C
Node DNode D
Node C
FCCS
FCCS
FCCS FCCS
FCCS
FCCSFCCS
FCCS FCCS
FCCS
FCCSFCCS
FCCS
FCCS
FCCSFCCS
1
2
1
example 1
example 3example 4
example 2
Node A
Routing  from  Node A               Node CRouting  from  Node D               Node C 
						

							ND-70185 (E) CHAPTER 3
Page 15
Revision 3.0
SYSTEM CONFIGURATION
System Considerations
Condition 2: A maximum of four (4) nodes can be connected as tandem nodes.
Figure 3-8   Fusion Tandem Connections
Condition 3: The available connection-route number ranges from 1 to 1023.
Condition 4: The available connection-trunk number of each route ranges from 1 to 4095.
Figure 3-9   Maximum Number of Ports between Nodes
FCCS
FCCS
FCCS
Tandem Connection over FCCS links Node A
Node B
Node C Node D
max 4 nodes
A maximum of 4095 ports can be assigned on a 
connection-route basis between nodes.
DTI 
card
DTI 
card
:
:
:
::
:
:
::
:
:
::
:
:
:
D ch
D chB ch
DTI 
cardDTI 
card
DTI 
cardDTI 
card
DTI 
cardDTI 
card
DTI 
card
D ch: Data Link
B ch: Connection Trunk T1
T1T1
T1 IMXIMXIMX
max 4095 ch
C_RT
Max 4095 trunks per connection-route