NEC Neax 2400 Imx Fusion Network System Manual

							CHAPTER 4 ND-70185 (E)
Page 56
Revision 3.0
This page is for your notes. 
						

							ND-70185 (E) CHAPTER 5
Page 57
Revision 3.0
CHAPTER 5 DATA PROGRAMMING
This chapter explains how to set Fusion Network data, using the following data categories:
 System Data
 Numbering Plan Data
 Station Data
 Fusion Link Data
Figure 5-1 shows the overall data programming procedure:
Figure 5-1   Data Programming Flow Chart
AFMU
ANPD ANPDL
STN
SSC
SSCA
OGC
OGCA
LCR
LCRS
UNIF
:
:
:
------

------
SSC
------
OGC
OGCA
LCR
LCRS
:
:   
:
TELN           Note

ASDT
System Data
Numbering Plan Data
Station Number Data
ACRD
ACRD
ACTK
MBCT
AFCH
AFPC
AFPC
ACAN
AFRT
ASYDN
ASYDL
Fusion Link Data
with FCH
w/o FCH
ALRTN
Physical Number
ALGNL
ALGSL
Telephone Number
ALGNN
ALGSN
Telephone Number
: Available command at NCN. Note: Telephone Number is
           available only in self
           node. NCN:
LN:
ASPA ASPAL
ANPDN
 -----
SSC
SSCA
OGC
OGCA
LCR
LCRS
:
:
:
:



ASPAN

   TELN 
						

							CHAPTER 5 ND-70185 (E)
Page 58
Revision 3.0
DATA PROGRAMMING
Network Data Programming Summary
1. Network Data Programming Summary
This section explains a summary of the data programming of Fusion systems.
1.1 Brand-new Fusion Network
To install the Fusion network as a brand-new system, the overall data programming procedure is as follows.
1.1.1 System Data
 Decide an NCN, and LN on the network.
 Assign System Data for each node. Use the ASYDN command for the NCN and the ASYDL com-
mand for all nodes. The system data includes the size of LDM, NDM, Fusion Point Code (FPC), etc.
Note:The data becomes effective by executing “Non-Load Initial” after setting the FPC.
 Assign unit data using the AFMU command for each node which exists on the network. Note that
the AFMU command is available at NCN only.
 Assign Logical Route Numbers for all routes (external trunk) on the network using the ALRTN
command. Note that the ALRTN command is available at NCN only.
1.1.2 Numbering Plan Data
 ANPDN →  ASPAN (for NCN only): Assign numbering plan data for Telephone Number.
 ANPDL →  ASPAL (for NCN and LN): Assign numbering plan data for Service Codes, Trunk Ac-
cess Codes, etc. other than STN (physical station) and TELN.
 ANPD →  ASPA (for NCN and LN): Assign numbering plan data for Physical Station Number
using STN.
Note:The Numbering Plan data for the LDM and/or NDM cannot use separate Tenant Numbers (TN). Therefore,
be sure to assign the following data on the ASYDL command.
 ASYDL command, SYS1, INDEX 800
b1 = 1 (ASPAL command tenant data table development on LDM = Common)
b2 = 1 (ANPDL command tenant data table development on LDM = Common)
1.1.3 Station Numbering
 Assign Telephone and/or Physical Station Numbers using the following command:
ALGNN →  ALGSN: Assign Telephone Number on the network. (NCN only)
ASDT: Assign Physical Number for each node as required. (available for NCN and LN)
1.1.4 Fusion Link Data
 Assign the Fusion Link data using the following commands:
Fusion with FCH:ACRD →  ACTK →  ACAN →  MBCT →  AFCH →  AFPC →  AFRT
Fusion w/o FCH:ACRD →  ACTK →  ACAN →  MBCT →                AFPC 
						

							ND-70185 (E) CHAPTER 5
Page 59
Revision 3.0
DATA PROGRAMMING
Network Data Programming Summary
1.2 Upgrading a CCIS Network
To install the Fusion system to an existing CCIS network, the overall programming procedure is as follows:
1.2.1 System Data
 Decide an NCN and LN on the network.
 Assign System Data for each node. Use the ASYDN command for NCN and the ASYDL command
for LN. The system data includes the size of LDM, NDM, Fusion Point Code (FPC), etc.  
Note:The data becomes effective by executing “Non-Load Initial” after setting the FPC.
 Assign unit data using the AFMU command for each node which exists on the network. Note the
AFMU command is available at NCN only.
 Assign Logical Route Numbers of all routes (external trunk) on the network using the ALRTN com-
mand. Note that the ALRTN command is available at NCN only.
1.2.2 Numbering Plan Data
 ANPDN →  ASPAN (for NCN only): Assign numbering plan data for Telephone Number.
 When “Operator Call” or “Priority Call (ATT)” is used on the Fusion network, replace the existing
numbering plan data for these features using the ANPDL and ASPAL commands.
Note:The Numbering Plan data for the LDM and/or NDM cannot use separate Tenant Numbers (TN). Therefore,
be sure to assign the following data on the ASYDL command.
 ASYDL command, SYS1, INDEX 800
b1 = 1 (ASPAL command tenant data table development on LDM = Common)
b2 = 1 (ANPDL command tenant data table development on LDM = Common)
1.2.3 Station Numbering
 Assign Telephone Numbers using the following commands:
ALGNN →  ALGSN: Assign Telephone Number at network level. (NCN only)
1.2.4 Fusion Link Data
 Assign the Fusion Link data using the following commands:
Fusion with FCH: ACRD →  ACTK →  ACAN →  MBCT →  AFCH →  AFPC →  AFRT
Fusion w/o FCH: ACRD →  ACTK →  ACAN →  MBCT →                AFPC
Note:When the Fusion system is incorporated in an existing CCIS network, all nodes must be linked via CCIS on
the network.
If there are any nodes linked via ACIS alone, add the CCIS link before the installation of the Fusion link
(See Figure 5-2.) Please refer to CCIS-related manuals for more detailed information. 
						

							CHAPTER 5 ND-70185 (E)
Page 60
Revision 3.0
DATA PROGRAMMING
Network Data Programming Summary
1.3 Fusion Link Data
 Assign the Fusion Link data using the following commands:
Fusion with FCH: ACRD ➔ ACTK ➔ MBCT ➔ AFCH ➔ AFRT ➔ AFPC ➔ AC A N
Fusion w/o FCH: ACRD ➔  AFPC
Note:When the Fusion system is incorporated in an existing CCIS network, all nodes must be linked via CCIS on
the network.
If there are any nodes linked via ACIS alone, add the CCIS link before the installation of the Fusion link
(See Figure 5-2 below.) Please refer to CCIS-related manuals for more detailed information.
Figure 5-2   Fusion-CCIS Network


........................................................................
Node A
PC=10
80
Node B
PC=11
81 Node C
82CCIS ACIS
PSTN


........................................................................

............................................................................................................
Add CCIS link.
PC: Point Code (CCIS)
PC=12 
						

							ND-70185 (E) CHAPTER 5
Page 61
Revision 3.0
DATA PROGRAMMING
Network Data Programming Summary
Figure 5-3 shows how to upgrade an existing CCIS network, focusing on the Numbering Plan. The example data 
setting assumes the existing network uses this particular numbering. For more detailed information on how to assign 
Telephone Numbers, please see Assignment of Telephone Numbers.
Figure 5-3   How to Upgrade the Numbering Plan Data of an Existing CCIS Network

Before Upgrading
STN: 2000
A
CB
80

82
81
STN: 2000
STN: 2000 CCIS
CCIS
PSTN
13-H
1. xxxx xxxx 0010 1222
4. x0010 1110 10110 1FFF
7. E23C CAAB12 000 0000
CCIS network
ATTCON 0
PC=10
PC=12PC=11
MAT
9
PC: Point Code
STN: 2000LSTN: 430000
8280
81
STN: 2000
STN: 2000 CCIS
CCIS FCCSFCCS
PSTN
13-H
1. xxxx xxxx 0010 1222
4. x0010 1110 10110 1FFF
7. E23C CAAB12 000 0000
CCIS-Fusion network
ATTCON 0
PC=10
PC=12 FPC=3PC=11
MAT
9
PC: Point Code FPC: Fusion Point Code
Numbering Plan Data of Node A
(before upgrading)
Numbering Plan Data of Node A
(after upgrading)
100: Priority Call 1 (ATT)
101: Priority Call 2 (ATT)
102: Priority Call 3 (ATT)
2xxx: Physical STN
8x: CCIS access code
9: CO call
 0: Operator Call

- Numbering Data (example)
100: Priority Call 1
101: Priority Call 2
102: Priority Call 3
   0: Operator Call
- Numbering Data (example) Numbering Plan (Example) before Upgrading
Numbering Plan (Example) after Upgrading
After Upgrading
Assign this  using the ANPDN
and ASPAN commands.
Numbering Plan Data for Telephone Numbers
To assign Telephone Numbers 4xxxxx, set the Numbering Plan data at Network Control Node (in this instance Node A) as follows:
ANPDN ASPAN
1st DC = 4     NND = 6 1st DC = 4     SSC = 16 (Logical Number)2xxx: Physical STN
8x: CCIS access code
9: CO call
4xxxxx: Telephone Number
FPC=1
FPC=2
TELN: 410000
TELN: 430000TELN: 420000
Assign these codes using ANPDL
and ASPAL commands if these features
are provided on the Fusion network. 
						

							CHAPTER 5 ND-70185 (E)
Page 62
Revision 3.0
DATA PROGRAMMING
Assignment of System Data
2. Assignment of System Data
STEP 1: ASYDL and ASYDN
Assign the number of data memory blocks for the Network Data Memory (NDM) and the Local Data
Memory (LDM). Use the ASYDN command for the NCN. Use the ASYDL command for all nodes.
Figure 5-4 shows ASYDL Indexes 513 and 514 as an example.
Figure 5-4   Assignment of Memory Block
(1) Assign the following data to all nodes.
 ASYDL, Index 513 Local Data Memory (LDM) usage
Assign 1 for bit(s) corresponding to the data memory block to be used as Local Data Memory (LDM).
Assign 01H for systems having 2M-LDM.
 ASYDL, Index 514 Network Data Memory (NDM) usage
Assign 1 for bit(s) corresponding to the data memory block to be used as Network Data Memory (NDM).
Assign 01H for systems having 2M-NDM.
Allowable memory block of LDM and NDM assigned by ASYD are shown in Figure 5-5.
Figure 5-5   LDM and NDM Allocation (ASYDL)
(2) Assign the data to NCN only.
 ASYDN, Index 514 Network Data Memory (NDM) usage
Assign 1 for bit(s) corresponding to the data memory block to be used as Network Data Memory (NDM).
Assign 01H for systems having 2M-DM.
NCN: Network Control Node
LN: Local Node
ASYDN ASYDL
LN
LNLNLN
LNLN
LN LNNCN
The ASYDN command is used at NCN only. Use the ASYDL command at all nodes.
Index 514 (NDM)=01H
ASYDLIndex 513 (LDM)=01H
Index 514 (NDM)=01H Index 513 (LDM)=01H
Index 514 (NDM)=01HNote
Note:    ASYDL must be assigned at each node on the network.
Each bit corresponds to one block having 2M Bytes.
    NDM blocks
  (INDEX 514)
   LDM blocks
 (INDEX 513)
block #4
block #3
block #2
block #1
block #0
block #2
block #1
block #0
Relationship between Bit and Block Number
INDEX Bit  (Setting)Meaning
  513
(LDM)
  514
(NDM)0       (1)
1       (0) Note
2       (0) Note
3       (0)
4       (0)
5       (0)
6       (0)
7       (0)
0       (1)
1       (0) Note
2       (0) Note
3       (0) Note
4       (0) Note
5       (0)
6       (0)
7       (0)Memory Block #0
Memory Block #1
Memory Block #2





Memory Block #0
Memory Block #1
Memory Block #2
Memory Block #3
Memory Block #4



Not used
Not used
Note:  These bits are normally assigned as 0 (i.e. 01H is normally set for both INDEX 513 and 514). The flagging of the bit(s)
             is possible, but only in case that your system should use the bit-corresponding Memory Block(s) for some reasons. 
						

							ND-70185 (E) CHAPTER 5
Page 63
Revision 3.0
DATA PROGRAMMING
Assignment of System Data
STEP 2: ASYDL
Assign the self-Fusion Point Code (self-FPC) at each node. FPC ranges from 1 to 253. Use the ASY-
DL command. (Index 512 b0-b7)
 Index 512 self-Fusion Point Code
Assign a unique FPC for each node. 
Figure 5-6   Self-FPC Assignment
STEP 3: ASYDL and ASYDN
Assign other system data using the ASYDL/ASYDN command.
When Timing Start is used, assign the following data.
Index 161 b6 : 0/1=-/Timing Start using “#” code
b7 : 0/1=-/Timing Start using “*” code
Index 170 b4 : 0/1=Timing Start out of Service/Timing Start in Service 
Note 1
Index 640 Fusion Point Code (FPC) of node providing ATTCON Note 2
Index 704~735  (ASYDL)
FPC of the node to which ATTCON transfers the Day/Night changeover
information. 
Note 3
Assign FPC of a terminating node for House Phone, Off-Hook Alarm and Ring Down (IC) calls from
PSTN. Day/Night information is transferred from the terminating node.
Note 1:When Timing Start is in service, Called Sub Address for ISDN Network cannot be dialed.
Note 2:This data is necessary at each node. Assign the self-FPC at the terminating node.
Note 3:This data is necessary at the node providing ATTCON.
NCN: Network Control Node
LN: Local Node
LN
LNLNLN
LNLN
LN LN
NCN1
2 1011
1221
22
23 24 This figure shows an example of FPC assignment. Assign a unique FPC for each node.
ASYDL Index 512 (b0-b7) 
						

							CHAPTER 5 ND-70185 (E)
Page 64
Revision 3.0
DATA PROGRAMMING
Assignment of System Data
Index 800
For ASYDL b0 : 0/1 = ALGNL, ALGSL on a UGN (TN) basis/-
b1 : 0/1 = ASPAL on a TN basis/-
b2 : 0/1 = ANPDL on a TN basis/-
b4 : 0/1 = AFRSL, ASTPL, AUNEL on a TN basis/-
b5 : 0/1 = ASTPL on a TN basis/-
b7 : 0/1 = AAEDL on a TN basis/-
For ASYDN b0 : 0/1 = ALGNN, ALGSN on a UGN (TN) basis/-
b1 : 0/1 = ASPAN on a TN basis/-
b2 : 0/1 = ANPDN on a TN basis/-
b4 : 0/1 = AFRSN, ASTPN on a TN basis/-
b5 : 0/1 = ASTPN on a TN basis/-
b6 : 0/1 = ARSCN on a TN basis/-
b7 : 0/1 = AAEDN on a TN basis/-
When “different numbering development on a TN basis ” is not required, set the above bits.
Figure 5-7   ASYDN Command Display (example)
Note 4:
Be sure to execute “Non-Load Initial” after setting the FPC data. The assigned FPC becomes effective by
this operation.
1
This figure shows the display of the ASYDN command Index 514 as an example. 
						

							ND-70185 (E) CHAPTER 5
Page 65
Revision 3.0
DATA PROGRAMMING
Assignment of FPC and MG and UNIT into Network
3. Assignment of FPC and MG and UNIT into Network
3.1 AFMU
Assign the module accommodation data by giving Module Group Number and Unit Number on an FPC
basis. This data is necessary to allocate unique Network ID (NID) to each MG/UNIT of the whole Fusion
network nodes. Note This data can be set at the NCN only.
Note:A unique NID is assigned to each MG/UNIT, automatically by entering the AFMU data.
 When the Fusion network is configured for the first time :
Enter the AFMU command data for all the Fusion network nodes (FPCs). Then, a unique NID is
assigned automatically to each MG/UNIT in the assigned order.
 When the Fusion network is already configured and a module/unit is to be expanded:
Enter the AFMU command data related to the expanded module/unit. Then, a unique NID number, just
next to the last existing NID number, is automatically assigned to the expanded module/unit.
Figure 5-8   Assignment of Module Accommodation Data
The AFMU command display should look similar to the following.
Figure 5-9   AFMU Command Display
MG=1
MG=0
U 0 U 0
U 1 U 1
U 2 U 2
U 3U 3 PBX
MG=1
MG=0
U 0 U 0
U 1 U 1
U 2U 3 PBX
MG=0
U 0U 1 U 2U 3 PBX
MG=1
MG=0
U 0 U 0
U 1 U 1
U 2 U 2
U 3U 3 PBX
FPC = 1,    MG = 0,	UNIT = 0
	UNIT = 1
	UNIT = 2
	UNIT = 3
                  MG = 1,	UNIT = 0
	UNIT = 1
	UNIT = 2
	UNIT = 3
                               
FPC = 11,  MG = 0,	UNIT = 0
	UNIT = 1
	UNIT = 2
	UNIT = 3
                  MG = 1,	UNIT = 0
	UNIT = 1
	UNIT = 2
	UNIT = 3
                               
FPC = 13,  MG = 0,	UNIT = 0
	UNIT = 1
	UNIT = 2
	UNIT = 3
                  MG = 1,	UNIT = 0
	UNIT = 1                                FPC = 12,  MG = 0,	UNIT = 0
	UNIT = 1
	UNIT = 2
	UNIT = 3
                               
LNNode
B
LNNode
C
LN
Node
DNode A
Node B
Node C
Node D
NCN
This figure shows an example data assignment for this particular network.
Data Assignment at NCN
FPC=1
FPC=12
FPC=11
FPC=13
Node
A
MAT

MG (Module Group Number): 0 - 7FPC (Fusion Point Code): 1- 253
FPC1UNIT1 MG0
WRT?
Y AFMU (Assignment of FPC and MG and UNIT for Network Data Memory)

MG (Module Group Number): 0 - 7 FPC (Fusion Point Code): 1- 253
U (Unit Number): 0 - 3
Note:For more information on each parameter, please see the “Office Data Specification” manual.