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