User's Manual

CHAPTER 8 ND-70185 (E)
Page 176
Revision 3.0
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-5 and Table 8-2 that explain the eight patterns.
Figure 8-5 Patterns of Number Portability
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 IVS
2
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 IVS
2
is managed in the NDM of NCNs within all
FUGs and the NEAX2000 IVS
2
.
(b) Telephone Number data in a NEAX2400 IMX is managed in the NDM of NCN within all
FUGs.
Table 8-2 Patterns of Number Portability
NO.
PATTERN
(Telephone Number is moved from A to B)
NODE REQUIRED DATA CHANGE
Moving a number within the same FUG NCN in Center FUG
Moving a number in an FUG to another FUG NCN in Center FUG
Moving a number in a FUG to a NEAX2000 IVS
2
NCN in Center FUG + NEAX2000 IVS
2
Note 1
Adding a new number to an FUG NCN in Center FUG + NEAX2000 IVS
2
Note 2
Moving a number in a NEAX2000 IVS
2
to an FUG NCN in Center FUG + NEAX2000 IVS
2
Note 3
Moving a number from a NEAX2000 IVS
2
to another
NEAX2000 IVS
2
NCN in Center FUG + a NEAX2000 IVS
2
Note 3
+ another NEAX2000 IVS
2
Note 1
Moving a number within the same NEAX2000 IVS
2
NEAX2000 IVS
2
Note 1, Note 3
Adding a new number in an NEAX2000 IVS
2
NCN in Center FUG + NEAX2000 IVS
2
Note 1
LEGEND
: EX-FCCS : Fusion Group (FUG): FCCS
6
2
FUG(A)
IVS
2
8
5
1
FPC1
NCN(A)
FPC2
FPC4FPC3
FUG(B)
FPC1
NCN(B)
FPC2
FPC3 FPC4
3
4
7
IVS
2
: Enhanced CCIS
1
2
3
4
5
6
7
8