NEC NEAX2400 system manual Note 1: Destination node

EX- FCCS

EX-FCCS Features

3.The node that requires the data programming or data change for Number Portability depends on the pattern. See Figure 8-5and Table 8-2that explain the eight patterns.

			6
IVS2	FUG(A)		FUG(B)		IVS2
					7
5	FPC1	FPC2	FPC1	FPC2
			NCN(B)
	NCN(A)
8					3
1
	FPC3	FPC4	FPC3	FPC4
			2		4
LEGEND
: FCCS		: EX-FCCS	: Enhanced CCIS	: Fusion Group (FUG)

Figure 8-5 Patterns of Number Portability

Table 8-2 Patterns of Number Portability

PATTERN

NO.NODE REQUIRED DATA CHANGE (Telephone Number is moved from A to B)

1	Moving a number within the same FUG	NCN in Center FUG
2	Moving a number in an FUG to another FUG	NCN in Center FUG
3	Moving a number in a FUG to a NEAX2000 IVS2	NCN in Center FUG + NEAX2000 IVS2 Note 1
4	Adding a new number to an FUG	NCN in Center FUG + NEAX2000 IVS2 Note 2
5	Moving a number in a NEAX2000 IVS2 to an FUG	NCN in Center FUG + NEAX2000 IVS2 Note 3
6	Moving a number from a NEAX2000 IVS2 to another	NCN in Center FUG + a NEAX2000 IVS2 Note 3
	NEAX2000 IVS2	+ another NEAX2000 IVS2 Note 1
7	Moving a number within the same NEAX2000 IVS2	NEAX2000 IVS2 Note 1, Note 3
8	Adding a new number in an NEAX2000 IVS2	NCN in Center FUG + NEAX2000 IVS2 Note 1

Note 1: Destination node

Note 2: Node to be connected to the FUG where the new number is added

Note 3: Node where Telephone Number is located before the Number Portability activation

4.Telephone Numbers used in the other FUG and the connected NEAX2000 IVS2 system are managed in the new table in NDM (the table differs from the existing table for Telephone Numbers used in self FUG).

(a)Telephone Number data in a NEAX2000 IVS2 is managed in the NDM of NCNs within all FUGs and the NEAX2000 IVS2.

(b)Telephone Number data in a NEAX2400 IMX is managed in the NDM of NCN within all FUGs.

CHAPTER 8 ND-70185 (E)

Page 176

Revision 3.0